Related
I hope I did enough research and the problem isn't super simple.
I have the G900W8 On Telus, I just did the lolipop update OTA to 5.0. Everything work perfect no issues. Before now I have not tried to root it.
I first followed the Guide found on /r/galaxys5 which had instructed me to use odin to Install TWRP 2.8.5.0, which I did and got the pass screen. After the reboot, I shut down then Vol + Home and Power it took me to the default recovery after it flashed the android figure with the open chest, and the Text "NO COMMAND".
After this failed I went to try philz_Touch_6.26.6-klite following another guild I had found and same issue when trying to boot into recovery.
I was going to try flashing to CF Auto root but the download for the G900W8 android version was listed as 4.4.2 and I didn't want to change it being the wrong version so I skipped it.
I then tried the Towel root from the sticky on this forum. I had downloaded the app, install it and when i opened it and clicked "Make it Rain" it said your device is not compatible.
So I am out of ways that I could find about rooting my device, As far as i can tell my version isn't yet compilable with rooting until an update comes out.
Also another note I just checked and my Knox hasn't been tripped yet so I feel like i was missing something.
CF Auto Root will work, I used it on mine on 5.0 too
Also had exactly the same problems trying to flash TWRP first, said it had worked but hadn't flashed anything even after 3 attempts,
CF Auto Root worked first time, then I used TWRP Manager to flash TWRP Recovery
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Remember that flashing custom anything will trip KNOX and possibly void your warranty depending where you live
*Detection* said:
CF Auto Root will work, I used it on mine on 5.0 too
Also had exactly the same problems trying to flash TWRP first, said it had worked but hadn't flashed anything even after 3 attempts,
CF Auto Root worked first time, then I used TWRP Manager to flash TWRP Recovery
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Remember that flashing custom anything will trip KNOX and possibly void your warranty depending where you live
Click to expand...
Click to collapse
Well the cf auto root worked, then i booted into recovery and installed Super su but I got a boot loop.
Tried doing both factory wipe and cashe wipes but no fix so i'm downloading the w8 5.0 image and will try flashing back to stock then repeating the process
Thehurst said:
Well the cf auto root worked, then i booted into recovery and installed Super su but I got a boot loop.
Tried doing both factory wipe and cashe wipes but no fix so i'm downloading the w8 5.0 image and will try flashing back to stock then repeating the process
Click to expand...
Click to collapse
Are you sure it was a boot loop? Wiping the caches / factory reset will force ART to recache everything which can take upwards of 10 minutes on first boot
*Detection* said:
Are you sure it was a boot loop? Wiping the caches / factory reset will force ART to recache everything which can take upwards of 10 minutes on first boot
Click to expand...
Click to collapse
I only waited about 2 mins on the loop. I just started the boot again hopefully it isn't a loop then I'll let it run for at least 10 then try the wipe again and try another 10 before I flash anything else
Thehurst said:
I only waited about 2 mins on the loop. I just started the boot again hopefully it isn't a loop then I'll let it run for at least 10 then try the wipe again and try another 10 before I flash anything else
Click to expand...
Click to collapse
Yea give it 10-15 for first boot, it does take a stupidly long time
*Detection* said:
Yea give it 10-15 for first boot, it does take a stupidly long time
Click to expand...
Click to collapse
So I tried waiting 20 mins then i re wiped, and i Just finished waiting another 30 with no boot just the repeating samsung screen . Should i flash to the stock rom now? uisng odin ?
Very strange, I did the exact same process and had no issues
Yea, grab a stock ROM and flash with ODIN, you might need to boot into recovery and factory reset after flashing if it gets stuck, Ive heard a few people saying that fixes it
*Detection* said:
Very strange, I did the exact same process and had no issues
Yea, grab a stock ROM and flash with ODIN, you might need to boot into recovery and factory reset after flashing if it gets stuck, Ive heard a few people saying that fixes it
Click to expand...
Click to collapse
Well I flashed stock and its working as a phone again, now i'm scared of trying to root it , but I might as well try again now that I know I have a working stock.
Thehurst said:
Well I flashed stock and its working as a phone again, now i'm scared of trying to root it , but I might as well try again now that I know I have a working stock.
Click to expand...
Click to collapse
Yea it's easy enough to fix with ODIN, might as well try again
I flashed CF-Auto Root with ODIN 3.09 iirc then rebooted into the OS fully
Installed TWRP Manager from Play Store and flashed TWRP using that
This is the CF I used
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
From here
http://forum.xda-developers.com/showpost.php?p=51421228&postcount=3
Just realised, you said you flashed SuperSU in recovery - CF-Auto root already installs SuperSU, no need to flash it again, that's likely why you ended up in a boot loop
*Detection* said:
Yea it's easy enough to fix with ODIN, might as well try again
I flashed CF-Auto Root with ODIN 3.09 iirc then rebooted into the OS fully
Installed TWRP Manager from Play Store and flashed TWRP using that
This is the CF I used
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
From here
http://forum.xda-developers.com/showpost.php?p=51421228&postcount=3
Just realised, you said you flashed SuperSU in recovery - CF-Auto root already installs SuperSU, no need to flash it again, that's likely why you ended up in a boot loop
Click to expand...
Click to collapse
That makes sense. It seems to be working perfectly now. Just confirmed Root and rebooted from recovery with TWRP. Thanks for the support in fixing my phone
Thehurst said:
That makes sense. It seems to be working perfectly now. Just confirmed Root and rebooted from recovery with TWRP. Thanks for the support in fixing my phone
Click to expand...
Click to collapse
Great
So I rooted my tablet and flashed it with twrp. But it was a long time ago that I did that. And rit running on Android 4.4.2. But to day I wanted to update it to android 5.0. It gave me an error and it said that I had to try downloading the update with keis and I did. Everything was going smoothly until it rebooted and now I'm stuck on bootloop with no backup. When I tried to boot into recovery I gave me the original samsung recovery can anyone help with this fix
MadMac19 said:
So I rooted my tablet and flashed it with twrp. But it was a long time ago that I did that. And rit running on Android 4.4.2. But to day I wanted to update it to android 5.0. It gave me an error and it said that I had to try downloading the update with keis and I did. Everything was going smoothly until it rebooted and now I'm stuck on bootloop with no backup. When I tried to boot into recovery I gave me the original samsung recovery can anyone help with this fix
Click to expand...
Click to collapse
Don't use Kies, it is literally awful. Use one of the SM-T530NU firmware files from this thread and flash it with Odin v3.10 (I would recommend factory resetting in stock recovery before you use Odin). Then you can root again using TWRP, just follow this method
Note: I have the exact same model as you and everything I just said worked fine for my tablet.
Thank you
thisisapoorusernamechoice said:
Don't use Kies, it is literally awful. Use one of the SM-T530NU firmware files from this thread and flash it with Odin v3.10 (I would recommend factory resetting in stock recovery before you use Odin). Then you can root again using TWRP, just follow this method
Note: I have the exact same model as you and everything I just said worked fine for my tablet.
Click to expand...
Click to collapse
one quick question is Factory Reset the same as data wipe with recovery
MadMac19 said:
one quick question is Factory Reset the same as data wipe with recovery
Click to expand...
Click to collapse
Correct
thisisapoorusernamechoice said:
Correct
Click to expand...
Click to collapse
thanks it worked
thisisapoorusernamechoice said:
Correct
Click to expand...
Click to collapse
is there any good Rom for my device like CM-12.1
MadMac19 said:
is there any good Rom for my device like CM-12.1
Click to expand...
Click to collapse
Go to the development section and check out either BlissPop or Resurrection remix. Both are based off CM12.1. The versions made for the SM-T530 work on our SM-T530NU. I use BlissPop, it's great.
Update: Links, BlissPop and Resurrection Remix. Use TK Gapps (either nano or micro) or jajb's minimal gapps, and whichever you use you might want to check out the debloat script on the minimal gapps thread
i am not sure what i did here. this is rather unusual.
i pulled the n910c out of the box, downloaded the twrp image from the twrp website being official.
i flashed it using odin.
booted the phone and when it reaches the samsung logo it bootloops.
i can enter TWRP just fine though.
whats going on?
(i didnt power the phone on at first, i just went straight to putting twrp on it).
cylent said:
i am not sure what i did here. this is rather unusual.
i pulled the n910c out of the box, downloaded the twrp image from the twrp website being official.
i flashed it using odin.
booted the phone and when it reaches the samsung logo it bootloops.
i can enter TWRP just fine though.
whats going on?
(i didnt power the phone on at first, i just went straight to putting twrp on it).
Click to expand...
Click to collapse
problem resolved.
installed one of the available kernels via twrp. all booting now.
i just went with spacex kernel. not sure which is best yet.
Hi,
I'm on this since morning today and still stuck.
I'm flashing the stock 6.0.1 image (https://github.com/motoxplay/stock/...562_LUX_RETASIA_DS_6.0.1_MPD24.107-52.xml.zip) via FASTBOOT successfully.
After the first boot, I flash the recovery (http://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656) which also goes fine.
But when I flash SuperSU (https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip) ... it gets stuck at the boot logo.
It must be 20th time I reflashed the ROM trying various things. What am I doing wrong??
Thanks
flash su2.63-3 works on 6.0.1
bablu048 said:
flash su2.63-3 works on 6.0.1
Click to expand...
Click to collapse
Strange why 2.65 STABLE won't work.
Anyway, can you please link me to it?
ibr4him said:
Strange why 2.65 STABLE won't work.
Anyway, can you please link me to it?
Click to expand...
Click to collapse
here http://forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202
m too stuck there..please help me ..my phone is not turning on
my nexus 6p just recently crashed while using it, and began to boot loop.
the only thing i can do is boot to fastboot. no splash screen, no recovery.
rom installed was StatixOS android pie, Recovery was TWRP 3.2.3-0, and rooted with Magisk 17.
i had everything except for magisk for a week or so, before eventually flashing magisk, and used it for about another week until now.
i know statixOS rom informed of flashing a BLOD fix if i was on 4 cores, which i did not do since, to my knowledge, i was still using all 8. i am aware of the 6p having bootlooping issues and have tried flashing the fix from here: https://www.xda-developers.com/nexus-6p-bootloop-fix/
i have also tried the modified recovery.img from the statixOS post with no results.
any help would be apreciated.
Okay, something similar happened to me today. The only difference being that I just flashed Magisk and it started happening immediately. I am able to flash a system image and get it to boot once. But Once booted though it loses the recovery. So I tried flashing the twrp before that first boot which asks for a password to decrypt the device and it was not encrypted in the first place. Any password I tell it just erases is the phone next time it boots. If I leave the system image I can get one good boot. So this boot is good I can load my info to the phone but it has so little battery that it dies before I can do much else. Once dead if I try to boot it, it loops. So I flash another system image and the cycle repeats. So I also tried flashing a stock image then adb sideloading a custom ROM and although the progress bar on the phone fills up, the percentage that my dos window shows only gets to about 46%. The phone states that it loaded successfully but the ROM won't boot. I think this is because its encrypted? That's just a guess, as I am no dev of any kind.
I don't think your issue is caused by the same problem.
Yours might be caused by magic, and I've read v17 has had issues in the past.
I can't get into recovery at all, regardless of what I flash.
Even the nodded versions of tarp to use 4 cores.
RTyper56 said:
my nexus 6p just recently crashed while using it, and began to boot loop.
the only thing i can do is boot to fastboot. no splash screen, no recovery.
rom installed was StatixOS android pie, Recovery was TWRP 3.2.3-0, and rooted with Magisk 17.
i had everything except for magisk for a week or so, before eventually flashing magisk, and used it for about another week until now.
i know statixOS rom informed of flashing a BLOD fix if i was on 4 cores, which i did not do since, to my knowledge, i was still using all 8. i am aware of the 6p having bootlooping issues and have tried flashing the fix from here: https://www.xda-developers.com/nexus-6p-bootloop-fix/
i have also tried the modified recovery.img from the statixOS post with no results.
any help would be apreciated.
Click to expand...
Click to collapse
well i think this same thing happened to me while trying to flash the same rom, the only other issue is that my vol down doesnt work so i have no way of booting into fastboot that i am aware of. my phone is useless now.
---------- Post added at 06:40 PM ---------- Previous post was at 06:38 PM ----------
i think there is something wrong with that modded recovery and rom. this is kinda strange.
My 6p also crashed after flashing the latest statix os and magisk. It crashed in the middle of the night. Now it goes into indefinite bootloop showing the google logo and warning screen. I tried flashing stock firmware several times and also the 4 core patch but still no signs of life. Please update if anyone has a fix. Tried the 4 core twrp too. but cant get even to the recovery.
Sterben Pistole said:
well i think this same thing happened to me while trying to flash the same rom, the only other issue is that my vol down doesnt work so i have no way of booting into fastboot that i am aware of. my phone is useless now.
---------- Post added at 06:40 PM ---------- Previous post was at 06:38 PM ----------
i think there is something wrong with that modded recovery and rom. this is kinda strange.
Click to expand...
Click to collapse
You need to open the phone, I know it sucks.
Anyhow, I just managed to help one member from the StatiXOS community by let him flash this recovery.
Try to flash it via fastboot and try to boot up into recovery.
imjuz4you said:
My 6p also crashed after flashing the latest statix os and magisk. It crashed in the middle of the night. Now it goes into indefinite bootloop showing the google logo and warning screen. I tried flashing stock firmware several times and also the 4 core patch but still no signs of life. Please update if anyone has a fix. Tried the 4 core twrp too. but cant get even to the recovery.
Click to expand...
Click to collapse
Did you wipe the internal storage after you flashed StatiXOS? This step is necessary.
oshithedead said:
Did you wipe the internal storage after you flashed StatiXOS? This step is necessary.
Click to expand...
Click to collapse
I was running Statix rom for a day before it crashed on me. I installed magisk and the EX kernel on top of the statix build. My phone crashed in the middle of the night while i was sleeping.
I found my phone low on battery next morning and when i put the phone on charging I found it bootlooping endlessly.
I tried entering recovery through bootloader but phone was not going into recovery. No matter what option i click on the bootloader i.e. factory reset or recovery, it shows the warning screen and then the google logo and restarts to do the same. I tried flashing stock rom and it flashes without any errors. But still the same result, BOOTLOOP. I cannot get my phone into recovery be it stock or twrp.
I even tried flashing the 4 core recovery in the OP, but 6p is still adamant on the bootloop cycle.
RTyper56 said:
my nexus 6p just recently crashed while using it, and began to boot loop.
the only thing i can do is boot to fastboot. no splash screen, no recovery.
rom installed was StatixOS android pie, Recovery was TWRP 3.2.3-0, and rooted with Magisk 17.
i had everything except for magisk for a week or so, before eventually flashing magisk, and used it for about another week until now.
i know statixOS rom informed of flashing a BLOD fix if i was on 4 cores, which i did not do since, to my knowledge, i was still using all 8. i am aware of the 6p having bootlooping issues and have tried flashing the fix from here: https://www.xda-developers.com/nexus-6p-bootloop-fix/
i have also tried the modified recovery.img from the statixOS post with no results.
any help would be apreciated.
Click to expand...
Click to collapse
typical thing happened to my phone yesterday guess the phone is dead for good cause i did everything that possible same as your procedures with no luck whatsoever
imjuz4you said:
I was running Statix rom for a day before it crashed on me. I installed magisk and the EX kernel on top of the statix build. My phone crashed in the middle of the night while i was sleeping.
I found my phone low on battery next morning and when i put the phone on charging I found it bootlooping endlessly.
I tried entering recovery through bootloader but phone was not going into recovery. No matter what option i click on the bootloader i.e. factory reset or recovery, it shows the warning screen and then the google logo and restarts to do the same. I tried flashing stock rom and it flashes without any errors. But still the same result, BOOTLOOP. I cannot get my phone into recovery be it stock or twrp.
I even tried flashing the 4 core recovery in the OP, but 6p is still adamant on the bootloop cycle.
Click to expand...
Click to collapse
there's your problem. Don't install any custom kernels, especially since EX hasn't been updated for Pie. Also, you may have a dud battery. Have you re-flashed TWRP?
oshithedead said:
there's your problem. Don't install any custom kernels, especially since EX hasn't been updated for Pie. Also, you may have a dud battery. Have you re-flashed TWRP?
Click to expand...
Click to collapse
My current situation is that no matter what i flash through my bootloader, let it be twrp, stock rom, 4 core recovery or each individual file from the stock image through fastboot commands, it restarts to bootloop.
My battery was replaced few months back and was giving me solid standby time, so cant blame it. All i am trying is to get to boot my phone to recovery which it refuses. Cant understand whether its the file system that is damaged, but my flashes returns me no error, and also i formatted through fastboot whichever partition i could. Still cant see any life.
I am having the same issue. I was running Statix with no custom kernel or magisk for about a week. My device just randomly went into boot loop. I tried to flash back to stock file by file... still bootloop. I flashed that 4 core patch and the twrp... still bootloop. I can get into recovery, but I don’t know what to do from there because no matter what I flash, it always ends up in bootloop. Any ideas?
Jertlok said:
You need to open the phone, I know it sucks.
Anyhow, I just managed to help one member from the StatiXOS community by let him flash this recovery.
Try to flash it via fastboot and try to boot up into recovery.
Click to expand...
Click to collapse
Do you have any other suggestion than this? It doesn't seem to work.:crying:
imjuz4you said:
Do you have any other suggestion than this? It doesn't seem to work.:crying:
Click to expand...
Click to collapse
did you ever get this figured out had the exact same thing just happen to me.