Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Flash a different kernel.
Period
your welcome
TehZam said:
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
Click to expand...
Click to collapse
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
KonoeKyon said:
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'll try and post back to you!
TheAxman said:
Flash a different kernel.
Period
your welcome
Click to expand...
Click to collapse
If you don't mind me asking, what kernel are you using?
mixlex said:
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
Click to expand...
Click to collapse
I have used the Touchwiz kernal.
blyndfyre said:
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
Click to expand...
Click to collapse
Tried that and done that, no go.
________________________________________
Thank you everybody for the help.
what procedures are you using for all of this? is there a specific guide you are following?
xBeerdroiDx said:
what procedures are you using for all of this? is there a specific guide you are following?
Click to expand...
Click to collapse
So at first I used this [ROOT] Root Samsung Galaxy S4 with Motochopper. Same problem.
Went back to stock and used this
[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13. Same problem encountered.
Went back to stock and did it again using Same problem with this one as well.
It happens with every custom rom besides the stock rom and Cyanogenmod Rom. I can't even reboot to do anything .
Thanks for the help guys, I greatly appreciate it.
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
TheAxman said:
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
Click to expand...
Click to collapse
Yes, I do have a backup. It happens to every custom ROM that I have encountered with.
Stock & Cyanogenmod roms work fine when rebooting.
Would you mind sharing what kernel you are using? I jused used faux kernel. Same thing.
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
xBeerdroiDx said:
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
Click to expand...
Click to collapse
Sorry for the confusion, I used your guide!
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
TheAxman said:
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
Click to expand...
Click to collapse
yep I am that sure haha.
jetlitheone said:
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
Click to expand...
Click to collapse
Your method worked! Thank you very much, I greatly appreciate it.
Related
Hi,
I flashed the Google 4.3 S4 Rom and used TWRP 2.5.0.2 and Goo with instructions I found on the boards.
- I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
So now the problems:
1) I originally installed it and it was constantly stuck on 'Samsung Galaxy S4' Screen, couldn't proceed barely got into recovery and reflashed; this worked and it booted google and i realized why this happened is because i accidentally erased my data.
2) The second time, I simply turned off my phone and turned it back on, again i was stuck on 'Samsung Galaxy S4' Screen, no way of doing anyhing except turnging off the phone and trying again and again to get to recovery, I then flashed to 4.3 again off the external.
3) I simply tried to open facebook and the phone booted and went on to the 'Samsung Galaxy S4' Screen and is stuck again! Even when I reboot through Team Win Recovery v2.5.0.2 to System I get the same boot loop.
I am super frustrated with this, what can I do and at this point I'm getting to the point where I would like some help to go back to stock. I would also like some input as to why this is happening if anyone has any suggestions or help it would be greatly appreciated.
Thank You.
notorious99 said:
Hi,
I flashed the Google 4.3 S4 Rom and used TWRP 2.5.0.2 and Goo with instructions I found on the boards.
- I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
So now the problems:
1) I originally installed it and it was constantly stuck on 'Samsung Galaxy S4' Screen, couldn't proceed barely got into recovery and reflashed; this worked and it booted google and i realized why this happened is because i accidentally erased my data.
2) The second time, I simply turned off my phone and turned it back on, again i was stuck on 'Samsung Galaxy S4' Screen, no way of doing anyhing except turnging off the phone and trying again and again to get to recovery, I then flashed to 4.3 again off the external.
3) I simply tried to open facebook and the phone booted and went on to the 'Samsung Galaxy S4' Screen and is stuck again! Even when I reboot through Team Win Recovery v2.5.0.2 to System I get the same boot loop.
I am super frustrated with this, what can I do and at this point I'm getting to the point where I would like some help to go back to stock. I would also like some input as to why this is happening if anyone has any suggestions or help it would be greatly appreciated.
Thank You.
Click to expand...
Click to collapse
Have you try using Odin to go back to stock?
shizs14 said:
Have you try using Odin to go back to stock?
Click to expand...
Click to collapse
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
notorious99 said:
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
Click to expand...
Click to collapse
Rule #1. Learn Odin before attempting anything on Samsung phones
notorious99 said:
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
Click to expand...
Click to collapse
You need to read these threads and make sure to read the threads linked in these threads that have to do with your phone...
http://forum.xda-developers.com/showthread.php?t=2301762
and
http://forum.xda-developers.com/showthread.php?t=2312444
You can use the forum's search function to help you find specific information. Good luck.
agreed, odin should be the first thing any noob should learn.
Scott, you da man...
scott14719 said:
You need to read these threads and make sure to read the threads linked in these threads that have to do with your phone...
http://forum.xda-developers.com/showthread.php?t=2301762
and
http://forum.xda-developers.com/showthread.php?t=2312444
You can use the forum's search function to help you find specific information. Good luck.
Click to expand...
Click to collapse
So I flashed a different rom (4.2.2 google) and I tested turning my phone off and then on again, and SAME issue, it boot loops at the S4 screen, what is the deal with that specifically? does anyone have any ideas?
notorious99 said:
So I flashed a different rom (4.2.2 google) and I tested turning my phone off and then on again, and SAME issue, it boot loops at the S4 screen, what is the deal with that specifically? does anyone have any ideas?
Click to expand...
Click to collapse
Which google rom 4.2.2? there are a few, meaning where did you get the rom?
Which kernel did you use?
you say you have this...both roms require a certain kernel. Depending on whose rom you flashed.
I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
TheAxman said:
Which google rom 4.2.2? there are a few, meaning where did you get the rom?
Which kernel did you use?
you say you have this...both roms require a certain kernel. Depending on whose rom you flashed.
I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
Click to expand...
Click to collapse
THE ROM
Google Edition 4.2.2 - v1.3 - http://d-h.st/Lm8
posted here: http://forum.xda-developers.com/showthread.php?t=2341376
MY KERNEL as it is on my phone currently is:
Baseband: 1337MVLUAMDJ
Kernel: 3.4.0-Google-Edition, [email protected]#1,
Build Number: JDQ39.1337
AND I'm using TWRP Custom
-----------------------------------------
notorious99 said:
THE ROM
Google Edition 4.2.2 - v1.3 - http://d-h.st/Lm8
posted here: http://forum.xda-developers.com/showthread.php?t=2341376
MY KERNEL as it is on my phone currently is:
Baseband: 1337MVLUAMDJ
Kernel: 3.4.0-Google-Edition, [email protected]#1,
Build Number: JDQ39.1337
AND I'm using TWRP Custom
-----------------------------------------
Click to expand...
Click to collapse
Ok, now we're cooking, thanks for the info...
I haven't tried that rom yet, I am going to d/l it and give it a shot. Be back shortly.
ODIN back to stock, and start over from there, and take care to flash/erase properly. backup user apps/data if you can (there are non-root options) and restore when you finish flashing 4.3 and are sure its stable.
Ok..back...I flashed this rom I booted with the kernel supplied in rom. Hmm..it is kernel related for sure. Have you posted the issue in that roms thread? May want to give that a shot.
I'm on canadian S4 aswell and I also flashed the 1.3 Google edition but flashed faux kernel. Works like a charm.
Sent from my SGH-I337 using Tapatalk 4 Beta
Thank you to all you guys. I successfully used odin to get back to stock. I still have no idea why I had so many problems but will try the Google Rom again when I feel more comfortable.
Thanks again!
notorious99 said:
Thank you to all you guys. I successfully used odin to get back to stock. I still have no idea why I had so many problems but will try the Google Rom again when I feel more comfortable.
Thanks again!
Click to expand...
Click to collapse
Proper wiping steps is key when changing ROM bases. Do a factory reset, wipe both caches, format /system, and if coming from TW, format the internal also.
Here is a post by TeamWin on wiping for Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.
http://teamw.in/whattowipe
These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.
rugmankc said:
Here is a post by TeamWin on wiping fro Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.
http://teamw.in/whattowipe
These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.
Click to expand...
Click to collapse
The internal wiping isn't necessary, but it does get rid of TW folders that you don't need if switching to AOSP.
I think you could delete them individually as opposed to formatting entire internal with other rom backups/kernels/gapps etc. I also have music/pics on internal too. Also, I like some will go back and forth btwn aosp and tw. So, I would want to keep them. I never did that, but read about some having issues after Formatting Data
All IMHO--
rugmankc said:
I think you could delete them individually as opposed to formatting entire internal with other rom backups/kernels/gapps etc. I also have music/pics on internal too. Also, I like some will go back and forth btwn aosp and tw. So, I would want to keep them. I never did that, but read about some having issues after Formatting Data
All IMHO--
Click to expand...
Click to collapse
You're right, it's an overkill. Just my OCD nature kicks in sometimes.
+1
I understand OCD hence my wiping twice--hey sometimes 3x
Monk has nothing on me, If you are familiar with that tv show--
I am OCD thru and thru--
I tried searching the ROM thread but with 70 pages worth of comments, it's hard to see anything even if i search using keywords.
My issues is, i tried installing Alpha S4, everything goes well, i go though aroma installer, the rom installs, boots up fine, i can play around with it for a while, restore all my apps, setup 3minit and all my other stuff. My problem is once i reboot, i get stuck on the boot logo for ever and ever. No matter what i do, clear cache and dalvik (which usually works for this issue) i just keep getting stuck. It's not a boot loop, because it doesn loop, it just hangs there.
I'm not sure what to do, ive formatted and re-installed the ROM at least 6 times today, no matter what i do, i get the same issue. At first i though, maybe if i reboot after setting up my apps, or each time i change 3minit settings, but now i've just let the rom boot, skipped the startup screens and rebooted and i get locked up again
Any suggestions?
I Have i337m, used bioshock kernel, if that helps
polish_pat said:
I tried searching the ROM thread but with 70 pages worth of comments, it's hard to see anything even if i search using keywords.
My issues is, i tried installing Alpha S4, everything goes well, i go though aroma installer, the rom installs, boots up fine, i can play around with it for a while, restore all my apps, setup 3minit and all my other stuff. My problem is once i reboot, i get stuck on the boot logo for ever and ever. No matter what i do, clear cache and dalvik (which usually works for this issue) i just keep getting stuck. It's not a boot loop, because it doesn loop, it just hangs there.
I'm not sure what to do, ive formatted and re-installed the ROM at least 6 times today, no matter what i do, i get the same issue. At first i though, maybe if i reboot after setting up my apps, or each time i change 3minit settings, but now i've just let the rom boot, skipped the startup screens and rebooted and i get locked up again
Any suggestions?
I Have i337m, used bioshock kernel, if that helps
Click to expand...
Click to collapse
Is it a 4.3 rom? And what recovery are you using?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
its a 4.2 rom and i'm using twrp...here is what a member in the rom thread suggested, i'll try it and report back
GrandMasterB said:
You are using TWRP and you have selected 'format data' and typed YES to continue. Either way the only way to fix it is to Odin back to stock and make sure you don't do it again. Its a TWRP/S4 bug that has not been fixed yet. I still prefer TWRP personally but you have to make sure you don't select the 'format Data' button or use shabbys or philz recovery instead.
Click to expand...
Click to collapse
polish_pat said:
here is what a member in the rom thread suggested, i'll try it and report back
Click to expand...
Click to collapse
it worked for anybody with the same issue...dont wipe data in twrp
polish_pat said:
it worked for anybody with the same issue...dont wipe data in twrp
Click to expand...
Click to collapse
What version of twrp did you use?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
What version of twrp did you use?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
the latest goomanager provides...not sure what it is, i'm guessing its 2.6.1.0
I have a Canadian S4 and rooted using the twrp method and then installed the vigin google play edition rom. Everything worked fine at first when I installed it but i was fiddling around after in twrp and thought i should format the internal storage and start completely fresh and now if I install any rom including my original backup the device will boot up into the system fine for the first time but if the device resets after that it just hangs on the galaxy S4 logo and i have to reboot into recovery and flash again. Any ideas on how i could fix this? Thanks!!!
Try this, in twrp go into advanced wipe and wipe dalvik cache, cache, system, data and android secure. Then flash your nandroid.
I don't have a nandroid I have a twrp backup
Jaygrippa said:
I don't have a nandroid I have a twrp backup
Click to expand...
Click to collapse
That is a nandroid.
Dont use TWRP for the S4
From what I have experience and I believe others have as well, if you used TWRP to format where you had to type yes, you are pretty much screwed trying to get things working properly again. Maybe it is certain phones, sd cards, roms, who knows, but after I typed yes in TWRP to format everything, I could flash a rom but couldnt restart and things were buggy. I had to use odin to flash back to stock, re-root and flash the rom again. Now everything is 190% considering my battery life went from 6 hours to 28 with medium usage.
I have always loved TWRP on my other phones, but for the S4, its more frustration and using with caution than its worth.
Another word of caution, use windows to fix your phone. Im on linux and its too much of a pain in the ass to use odin/heimdall to go back to stock for newbs. On windows I went to stock and rooted again in no time.
Good luck!
jd1639 said:
That is a nandroid.
Click to expand...
Click to collapse
After doing that stuff in twrp should I flash right back to my backup of stock touch wiz or straight into the ROM of my choosing? Whenever I would have to reflash I would have to format he internal memory or it wouldn't work
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
You might have to. I had the same problem today where if the phone rebooted I would just get a black screen. I ended up using Odin with the stock rom, reinstalling twrp and then restoring my backup. I'm pretty sure it was a rom I flashed that caused the initial problem and only Odin would clear things up.
Start Over
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
ericchaffey said:
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
Click to expand...
Click to collapse
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Now the only problem is i have to find a Fido ROM
Jaygrippa said:
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Click to expand...
Click to collapse
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
ericchaffey said:
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
Click to expand...
Click to collapse
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Jaygrippa said:
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Click to expand...
Click to collapse
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
jd1639 said:
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
Click to expand...
Click to collapse
ya even they dont have a specific "Fido" firmware...
Anyone know if I can just use the Rogers ROM its pretty much the same company
Jaygrippa said:
Anyone know if I can just use the Rogers ROM its pretty much the same company
Click to expand...
Click to collapse
It'll work. It'll just put their bloatware on and the boot animation will be theirs
Reflashed
Ok so i reflashed to the stock rom using odin and bam it works again, im just wondering what is a good way now too root, and install the same rom i had
This will have everything you need http://forum.xda-developers.com/showthread.php?p=42320391
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Jaygrippa said:
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Click to expand...
Click to collapse
Glad to here it. Have fun.
I tried 2 ROMs: Alliance and Extreme Debloat. If I try to turn off the phone it gets stuck at the booting down logo. This happens when I try to restart it, when I try to boot into SafeStrap, or any other way I attempt to power off the phone.
If I pull the battery & boot up, at the SafeStrap splash screen, even when hitting the "Recents" button it does not let me get into SafeStrap.
How do I fix this? What's the cause?
Haloman800 said:
I tried 2 ROMs: Alliance and Extreme Debloat. If I try to turn off the phone it gets stuck at the booting down logo. This happens when I try to restart it, when I try to boot into SafeStrap, or any other way I attempt to power off the phone.
If I pull the battery & boot up, at the SafeStrap splash screen, even when hitting the "Recents" button it does not let me get into SafeStrap.
How do I fix this? What's the cause?
Click to expand...
Click to collapse
Odin back to stock, re-root and try it again. I'm not sure what causes this but it happened to me a few times with my old Note 3 and SafeStrap.
Misterxtc said:
Odin back to stock, re-root and try it again. I'm not sure what causes this but it happened to me a few times with my old Note 3 and SafeStrap.
Click to expand...
Click to collapse
Doing this now. Thanks for the prompt reply.. I've been going insane
How I rooted originally: Installed towelroot successfully, then installed safestrap, booted into recovery, backed up system, created ROM slot #1, and installed a ROM.
Did I do something incorrectly?
edit: p.s. nice avatar
Haloman800 said:
Doing this now. Thanks for the prompt reply.. I've been going insane
How I rooted originally: Installed towelroot successfully, then installed safestrap, booted into recovery, backed up system, created ROM slot #1, and installed a ROM.
Did I do something incorrectly?
Click to expand...
Click to collapse
Not really but I stay away from ROM slots because there is a bug with having to pull the battery on reboot. Re-download the latest SS because the first one had a problem with memory corruption witch sounds like happened to you. If you can get into stock recovery try clearing cache or factory resetting from there. Either way you will have to reset. It's safe to flash to the stock slot as long as you have a good backup.
Edit: Thanks on the avatar, quite a few people like it. Hopefully it helps someone out.
Misterxtc said:
Not really but I stay away from ROM slots because there is a bug with having to pull the battery on reboot. Re-download the latest SS because the first one had a problem with memory corruption witch sounds like happened to you. If you can get into stock recovery try clearing cache or factory resetting from there. Either way you will have to reset. It's safe to flash to the stock slot as long as you have a good backup.
Click to expand...
Click to collapse
So after I ODIN I should:
1. Re-root
2. Re-download & install SS
3. Backup, then wipe everything & install in the main ROM slot
?
Haloman800 said:
So after I ODIN I should:
1. Re-root
2. Re-download & install SS
3. Backup, then wipe everything & install in the main ROM slot
?
Click to expand...
Click to collapse
Yup, run towelroot and update SU from SS.
Worked perfectly. Thanks!!
Haloman800 said:
Worked perfectly. Thanks!!
Click to expand...
Click to collapse
Cool, I'm glad it worked for you.
Today and after deciding to simply restart my Nexus 6P, it booted into TWRP menu, I tried to reboot again, but no luck. can someone please help?
is there a way to get off the TWRP menu and boot my phone normally?
Note: The root used to simply work fine for about a month now.
Did you take an update? Rom details? You basically said you stuck a fork in a microwave and it sparked.
Gytole said:
Did you take an update? Rom details? You basically said you stuck a fork in a microwave and it sparked.
Click to expand...
Click to collapse
Rooted my phone, and it was working fine for about a month, I done nothing unusual, All i did is restart my phone and it went to the TWRP menu, thats all. Im stuck there now.
I don't recall doing an update or whatever. Im using "BETA-SuperSU-v2.67-20160121175247.zip"
Any Idea how to get off the TWRP menu and boot my phone normally? Please help
MahmoudEMH said:
Any Idea how to get off the TWRP menu and boot my phone normally? Please help
Click to expand...
Click to collapse
Have you tried wiping the caches and/or data? Have you tried reflashing whatever ROM you're using? Have you tried flashing the factory images with fastboot?
Heisenberg said:
Have you tried wiping the caches and/or data? Have you tried reflashing whatever ROM you're using? Have you tried flashing the factory images with fastboot?
Click to expand...
Click to collapse
Yes to each one of those questions.
MahmoudEMH said:
Yes to each one of those questions.
Click to expand...
Click to collapse
I will have to call you out here buddy. If you have indeed tried to flash all factory images, you won't even have TWRP in the first place.
Go to this wonderful guide by the wonderful @Heisenberg, and scroll down to "10. How To Flash The Factory Images (And Return To Stock)". You will find very clear instruction on how to return your phone to its factory stock state. This will most likely get rid of the problems you're facing.
MahmoudEMH said:
Yes to each one of those questions.
Click to expand...
Click to collapse
If you had flashed the full factory images I don't see how it's possible at all to be in your current situation. Explain how you flashed them, and exactly what you flashed please.