Search results

T810 0803 veriosn fails to boot Update: Flash the 0803 version. It fails to boot again

T810 17.1 fails to boot Did a 17.1 clean flash from 16.0 with format data for T810. But it kept booting back to TWRP 3.4 and not into the system. The flashing went smoothly with no problem. Appreciate your help and thanks for the great work to keep the T810 going forward. Update: Flash the...

Flashed v6 via magisk manager on LG v30+ pie stock ROM but it killed all GPS signals. It didn't detect any GPS signals at all. Return back to stock gps.conf, all is well again. Appreciate much help

It looks like this is the case and has to do with magisk, the way it roots. Thanks

It's Samsung Note 8 TGY latest stock N9500ZHU6DSK2 with Dec 2019 security patch. https://www.sammobile.com/samsung/galaxy-note-8/firmware/SM-N9500/TGY/download/N9500ZHU6DSK2/306898/

Hi, here is my attempt for the 2/2 update. It failed to boot up again. Did a clean fresh of the stock ROM, then TWRP, format data, reboot to fresh magisk 20.3, then Disable-versity, then reboot to system. It failed to boot up and kept looping. Here are the logs:

Thanks for the heads up. Will keep our fingers crossed. :):):)

Tried Magisk-v19.3.zip + Disable_Dm-Verity_ForceEncrypt_01.19.2020.zip that didn't work as expected. Where can I get Disable_Dm_Verity_ForceEncrypt_5.21.2019.zip? Thanks.

Note 8 - N9500-TGY can't Magisk root Hello, I have samsung Note 8 - N9500 with latest stock ROM 12/9/19 can't Magisk root. TWRP installed well without looping. Here is what I did: 1. N9500-TGY stock ROM odin installed 2. Flash TWRP, then Format data, then reboot to TWRP again 4. Flash magisk...

Will definitely give it a try. BTW, the OEM unlock went missing. Any way to get it back? What particularly version of BL you would suggest? Many thanks again ...

That didn't work either. The CHC loader N9500ZCS5DSJ3_N9500CHC5DSJ3_CHC was flashed together the rest of TGY as suggested. It kept rebooting and failed to boot up. The download screen showed "Qualcom Secureboot: ENABLE". The others were all OFF. Any idea? Appreciate very much your help ...

Failed on SM-N9500 TGY Hong Kong latest stock ROM Failed on the latest stock ROM SM-N9500 TGY Hong Kong N9500ZHS5DSI1. TWRP installed via odin v3.13 with success but it failed to boot up. The boot screen showed "custom" and a symbolic lock on it. It kept rebooting. Appreciate your help.

Unlock tool for ZS550KL is now available on Asus official web site. It support all OS versions to unlock the boot loader. I got it to unlock Orio 8.0 for TWRP and Magisk 18.1, and it works great. https://www.asus.com/us/Phone/ZenFone-3-Deluxe-ZS550KL/HelpDesk_Download/ Version UnlockTool...

I did a clean flash for lineage-16.0-20190311-UNOFFICIAL-gts210wifi following the instructions on OP page. It kept looping and fails to boot up. Help is appreciated. Thank you.

Is there a possibility for the duos build available some time later? Thanks for the continuing support of this phone. Much appreciated ...

I took the leap to have a clean flash lineage-16.0-20190221-UNOFFICIAL-trlteduos. Everything went well and smooth. Great ROM! Many thanks ... However the stock camera gives "Camera error, Can't connect to the camera." which doesn't happen in 15.1. Otherwise the rest is working well so far...

You nailed it. Now it's working. Many thanks ... :good:

Just wanted to report that I flashed AospExtended-v6.2-flo-20190208-1407-UNOFFICIAL.zip with succees and it booted up well. However Magisk 18.1 didn't work. I flashed it via TWRP with no success and can't get it rooted. Appreciate your help and thanks for all the efforts. Greatly apprecited

Just wanted to report that usb tethering is not working on v4.7.1 duos though wifi hotspot is working fine. v4.7.1 duos has been my main driver so far. It works great. Update: It's my fault setting the firewall rules. USB tethering is working fine.

Only one sim working so far. That's is good enough for me. Let's hope that the duos will be resolved soon but it looks like a tough one to crack. The stock camera is working fine. I use a 3rd party app instead.

Dirty flash without a problem, running nicely with Magisk. Many thanks and greatly appreciated! :good::good::good:

Have a clean V3.8 flash, however, phone couldn't recognize codes such as *777# and gave error. Other than that the ROM has been running great. Many thanks ...

This S8 camera port works really well for Note 5 Duo SM-N9200 Hong Kong version Android 7.0. Many thanks. I also took the liberty of updating the zip to the latest Samsung Camera 7.5.58, and Samsung Gallery 5.3.07.403. They are fast and work great.

that's great. it's fun poking around to get it to work.

I've been reading through earlier posts this past hours. Now got your reply. It works. Many thanks.

Hi, I'm coming from LineageOS. Having v3.4 and Gapps-nano flashed clean but I couldn't get through the first screen when I picked "Set u as new". It kept coming back to the first setup screen. Any help is appreciated. Thanks.

Thanks for the heads up. Just figured that some of the apps require app permission via settings>Apps>app permission in order to gain access to storage or other apps etc. It's part of google security updates I guess. As such the new ROM runs very smoothly. Thanks for your work, much appreciated...

Thanks for all good suggestions. I do have TWRP 3.0.2.0 and SU 2.74 beta, but used PureNexus_Dynamic_GApps_6.x.x_6-21-16 instead. Will try other gapp version as well. Keep fingers crossed. Thanks again.

Did a clean flash again, this time without 3rd party kernel. Restore apps via Titanium app, while keeping the device old ID. Problem still persists. Besides, Google map can't access device's location, Osmand app too having similar issue. Problem in such installation steps didn't happen in...

With the latest 20160621 and Quanta v10 flashed, root explorer app is having trouble accessing to photos, media and files on the device. The ALLOW icon is simply not responding when pressed. My previous ROM version has no trouble on the device. Any help is appreciated. Thanks.... Update...

5.1.1 cf-root works flawlessly for SM-N910S 6.0.1 too.

Just for the heads up. Galaxy Note 4 SM-N910S 6.0.1 just released on May 3 2016 on SAMmobile. http://www.sammobile.com/firmwares/database/SM-N910S/ Update: version 5.1.1 CF-Auto-root works flawlessly on 6.0.1

Samsung Galaxy Note 4 SM-N910S 6.0.1 just released on May 3 2016 Hi, Samsung Galaxy Note 4 SM-N910S 6.0.1 was released on May 3 2016 on SAMmobile. http://www.sammobile.com/firmwares/database/SM-N910S/ I appreciate your CF-Auto-Root for this ROM. Thanks... Update: version 5.1.1 CF-Auto-root...

Update to the latest 5.1.1 ROM, and follow the steps on the page. You're good to go. http://forum.xda-developers.com/note-4/general/root-note-4-sm-n910c-t2977948

stuck with kernel is not seandroid enforcing - N910S 5.1.1 stock I'm on Note 4 SM-N910S 5.1.1 stock and flash with v0.2 via odin. Now I'm stuck with 'kernel is not seandroid enforcing' during reboot. I've read the ram fix posted on page #5 but no way I can apply the fix as I have no access...

failed to write on SD card Not sure if this issue has been covered before. I have a Samsung Galaxy 4S active 4.4.2 Kikat phone. Using v5.3.8 ftp via wifi, the transferred file failed to write on the external SD card. Thoguh Root Explorer handles both read/write without problem. Any idea...

I did have a clean flash but it looks like the screen filter may have messed up with the control. Thanks for heads up, really appreciate much.

Brightness control seems not working Feb 25 build has been running great so far. Very smooth and I like the simplicity of the build. The only glitch so far is the brightness control. Once the the adaptive mode was turned off, the manual mode did not work at all. After reboot, the manual worked...

ART is up and running Did a clean flash with the new build 0224. Then turned on ART. WOW! ART is up and running. There is some overall improvement in responsiveness but not noticeably much particularly in running Google Maps 3D which is my main interest. It is always fun and challenge to...

GPS not picking up signals I have a clean wipe flash of the latest build 1.0.2 The GPS seems not picking up any signals. Wonder if anyone has a similar problem? :confused::confused::confused:

I tried the new build with clean wipe. Then turned on ART but it kept looping and failed to boot up after more than half hour. I used GAPP pico. Is there a need to repartition the SD before turning on ART? Many thanks again.

SD delay problem fixed OK. I downloaded the ROM again from another link, and it fixed the SD delay problem. Looks like the previous download was corrupted. Thanks for looking into the issue. :o:o:o

Can't mount SD after flash I did a complete wipe and flash 2015-0-5 build with gapp pico 88mb. Install went well but having SD mount delay during reboot. It kept coming to recovery having SD mount delay error. Now back to the previous build without a hitch. Any idea...

GPS not function Just flash the latest build 9/7. Everything seems working fine except the GPS not detecting any signal. Wonder if that's mine or a known issue. :confused::confused: Any help is much appreciated.

Edit: Clean wipe and 4.4.3 Gapps min. Still had 'Setup wizard has stopped'. Can't boot. Edit: Just found out that I was using 4.4.2 Gapps. Will try and see Had a clean wipe yet got 'setup wizard has stopped'. Can't got it boot.:(:(:(

Problem fixed. Many thanks... Just wonder why the two files were gone, the rest was intact in \efs?? What had I done wrong?

Those two /efs files (/efs/imei/.nvmac.info, /efs/buyer_code.dat) are missing. Where can I get it back?

Sorry, I can't follow what you meant "The answer is in the post you quoted." I had flashed the kernel file you posted and the volume keys are all working. However the menu keys are no longer not working when the player is up and running. That means when I press the home or returns buttons...

Thanks for the information. Now, the player is up and running but the menu buttons are no longer working, I can't switch menu or change screen :(:( It's a US version player I'm using. Any idea?

Thanks. I got it to work. But the three menu keys are not working after it comes back to a normal screen. It is US version I'm using.