I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?
Boot into recovery and wipe your cache and dalvik cache again
mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use
I still want to keep my phone rooted. This wont kill the root right?
No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner
Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):
I'm going to install cm10 right now them go back to stock rooted and see what's up with this
There's no issues going back and forth. You probably flashed a bad ROM
yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.
DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10
redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.
Related
I've been playing around with a Nexus S 4G that I have lying around and never used, and I've ran into a few problems, but you've all been helpful. I rooted all my old EVO 4G's without any problem, but the other day I rooted my NS4G using a one click/simple root and downloaded ClockWorkMod etc. But now for some reason It seems like I've almost lost my root? Is that possible? I still have the little unlocked symbol when booting up.
I've searched this forum and Google and haven't found anything, which could possibly be because I don't know what to look for. I've never had this happen :/
Currently running the stock 2.3.7
Nobody? I just need a little help.
Did you flash a superuser.zip after you installed clockworkmod?
SeeNah said:
Did you flash a superuser.zip after you installed clockworkmod?
Click to expand...
Click to collapse
I thought I had... But no lol
Thank you. Sorry for pretty much making a useless thread :/
Its the Q&A forum ask away! Lol
Did flashing it work for you though?
SeeNah said:
Its the Q&A forum ask away! Lol
Did flashing it work for you though?
Click to expand...
Click to collapse
Yes, it did. Thank you!
Now I just need to re figure out how to backup my stock rom on rom manager. I need to do that if I'm going to flash a custom rom onto my NS4G correct? I've never actually gone that far with my phones lol.
Slap-Yourself :) said:
Yes, it did. Thank you!
Now I just need to re figure out how to backup my stock rom on rom manager. I need to do that if I'm going to flash a custom rom onto my NS4G correct? I've never actually gone that far with my phones lol.
Click to expand...
Click to collapse
Okay lol hold on so just go make sure you
1. Unlocked the bootloader right?
2. Flashed a custom recovery (clockworkmod)?
3. Flashed superuser for root access?
4. Now you have a stock rooted ROM?
If you have/did all that then yeah you could backup your stock rooted ROM, you don't need to back it up but its helpful just incase you mess something you could always restore it to start all over
And you could backup any ROM you install incase you didn't know, just remember when you install different ROMS make sure to do a proper full wipe which includes data/factory reset/wiping DALVIK cache, and formatting system and boot in the "mount" option in CWM. And now I think your good lol
SeeNah said:
Okay lol hold on so just go make sure you
1. Unlocked the bootloader right?
2. Flashed a custom recovery (clockworkmod)?
3. Flashed superuser for root access?
4. Now you have a stock rooted ROM?
If you have/did all that then yeah you could backup your stock rooted ROM, you don't need to back it up but its helpful just incase you mess something you could always restore it to start all over
And you could backup any ROM you install incase you didn't know, just remember when you install different ROMS make sure to do a proper full wipe which includes data/factory reset/wiping DALVIK cache, and formatting system and boot in the "mount" option in CWM. And now I think your good lol
Click to expand...
Click to collapse
Unlocked Bootloader? If I boot in fastboot it says Unlocked. Is this what you mean?
I have ClockWorkMod, but I haven't done anything with it.
I have superuser from the root
and I was working with a stock ROM the whole time....
I think I'm ok lol
So I'll back up my ROM, and flash a Nightly CM9? And back that up as well? Just perform a factory data reset before doing so, right?
Slap-Yourself :) said:
Unlocked Bootloader? If I boot in fastboot it says Unlocked. Is this what you mean?
I have ClockWorkMod, but I haven't done anything with it.
I have superuser from the root
and I was working with a stock ROM the whole time....
I think I'm ok lol
So I'll back up my ROM, and flash a Nightly CM9? And back that up as well? Just perform a factory data reset before doing so, right?
Click to expand...
Click to collapse
Yeah if it says unlocked your good to go. The super user.zip you first flashed won't be needed once you flash different ROMS, it was only needed for stock because you didn't install a ROM you just unlocked the boot loader and super user just gave you root access that didn't come with stock.
Yeah backup your stock ROM JUST in case you encounter a boot loop so you can just restore and start over, you don't need to back up CM9 that's completely your choice if you want . Its convenient though if you like CM9 but still like to flash other ROMS that way you can just go back if you miss CM9 without doing the whole setup process.
And a full wipe is
Data/factory reset
Then wipe dalvik under "advanced"
Then wipe system and boot under the "mount" option in CWM
stellar said:
Yeah if it says unlocked your good to go. The super user.zip you first flashed won't be needed once you flash different ROMS, it was only needed for stock because you didn't install a ROM you just unlocked the boot loader and super user just gave you root access that didn't come with stock.
Yeah backup your stock ROM JUST in case you encounter a boot loop so you can just restore and start over, you don't need to back up CM9 that's completely your choice if you want . Its convenient though if you like CM9 but still like to flash other ROMS that way you can just go back if you miss CM9 without doing the whole setup process.
And a full wipe is
Data/factory reset
Then wipe dalvik under "advanced"
Then wipe system and boot under the "mount" option in CWM
Click to expand...
Click to collapse
I'm not sure if I'm supposed to post links to videos or not. But I'm in love with some of the features this guy has on his NS4G
https://www.youtube.com/watch?v=IKdyAm3CgHc
He said it was a nightly etc.
The hidden status bar and bottom menu hidden is amazing. I also like the inverted G-Mail and Facebook. Is this all separate from the Nightly ROM?
I've been having a problem with phone calls putting them on speaker. The volume of the external speaker is comparable to the volume of the ear piece. This is only in calls, music and notifications seem to be fine. It was fine before I rooted, but seems to be goofed up on JB roms. I rooted with the brand new 2.20 root method. I tried things like Volume+ and nothing seems to make a difference. I've tried all the basic things like wiping cache/dalvick. What are the chances it's a bad device?
you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.
DvineLord said:
you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.
Click to expand...
Click to collapse
yes, i posted it there because at the time i thought the problem was specific to that rom (i think it started with the codename rom). but after being on more than one rom (i'm now on the jb build 4) i don't think it is. or it may be specific to jb roms. i'm not sure. i thought i would ask before i just go flashing away... i'm also wondering if anybody else is having this problem.
i followed you all the way till "fix permissions", is this another tab in twrp?
with all the changes right now with CM10 which is base for alot of jb roms its hard to determine the cause. unless you are using a jb aosp build before the kernel changes which is basically anything after 10/01 then you might have some unique issues.
fix permissions is under advanced
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.
Didn't work, but sandy just knocked out the power so I think this can wait a while haha
Sent from my One X using xda app-developers app
ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.
Crappyvate said:
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.
Click to expand...
Click to collapse
i will definitely take this under consideration
DvineLord said:
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.
Click to expand...
Click to collapse
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.
ck4794 said:
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.
Click to expand...
Click to collapse
relock bootloader and ruu...if that does not do it you have a hardware issue.
i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?
ck4794 said:
i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?
Click to expand...
Click to collapse
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
That's also why you should always do a clean install/full wipe/factory reset when you experiment with different roms (aosp/sense)
Crappyvate said:
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
Click to expand...
Click to collapse
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.
ck4794 said:
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.
Click to expand...
Click to collapse
good luck. :highfive:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?
ck4794 said:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?
Click to expand...
Click to collapse
http://dl3.htc.com/application/htc_o...s_08022012.exe
Crappyvate said:
http://dl3.htc.com/application/htc_o...s_08022012.exe
Click to expand...
Click to collapse
bad link
ck4794 said:
bad link
Click to expand...
Click to collapse
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3
Crappyvate said:
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3
Click to expand...
Click to collapse
i saw some where i think that this ruu would get me back to square one, unrooted. is there anything like that i should know about before i run this ruu? also i've never run an ruu, is it one of those i put it on my c: drive run it and it will do the work?
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!
elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.
Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
bweN diorD said:
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
Click to expand...
Click to collapse
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
ajh305 said:
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
Click to expand...
Click to collapse
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
bjoostema said:
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
Click to expand...
Click to collapse
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
EDIT: I tried another 4.3 rom and booted it up. Set some things up then updated su binaries and restarted and let it sit there at the unlocked bootloader warning for 15 minutes with no changes.
bweN diorD said:
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
Click to expand...
Click to collapse
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
ajh305 said:
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
Click to expand...
Click to collapse
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
bjoostema said:
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
Click to expand...
Click to collapse
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
ajh305 said:
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
bjoostema said:
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
Click to expand...
Click to collapse
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
ajh305 said:
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
Click to expand...
Click to collapse
Awesome man! I'm glad it booted up for you welcome to the 4.3 side!
ajh305 said:
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
Click to expand...
Click to collapse
glad you got it fixed but i have to ask, in the sequence above why are you restoring a backup? you should be going right from stock to 4.3. also, some people have issues with twrp and 4.3, thats why i suggested cwm.
I'm not sure why I restored the backup. I didn't think coming from stock would work for some reason.
Sent from my XT926 using xda app-developers app
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
sgtslaughter64 said:
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
Click to expand...
Click to collapse
This was the only thing that worked for me. You could maybe try updating to the most current recovery instead of the one listed.
the only 2 issues i have seen to cause this problem are covered in the post a few below, and fixed it every time. my only suggestion would be to install cwm after rooting, then reboot, then continue with the steps. just my preference, it may not matter.
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
You can always flash the factory images here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You can flash any ROM and that should fix your issue
You will not lose your unlocked bootloader unless you flash the stock one which is in the factory images
Your bootloader will not relock unless you lock it yourself using fastboot. Flashing roms or factory images won't lock it by themselves.
And even if it somehow did, one fastboot command and you're unlocked again.
And as far as root goes....it takes 5 minutes to reroot.
So just flash whatever factory image you need and then custom recovery, and you're done. Maybe need to download superSU from play store after.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
justinisloco said:
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
Click to expand...
Click to collapse
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
xfranchize said:
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
Click to expand...
Click to collapse
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
vin4yak said:
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
xfranchize said:
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
Click to expand...
Click to collapse
Maybe your flashing a bad version of GApps since the force closes are on google Calander?
Are you using a 4.4.2 GApps?
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
gee2012 said:
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
Click to expand...
Click to collapse
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
xfranchize said:
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
gee2012 said:
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
Click to expand...
Click to collapse
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
gee2012 said:
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
Click to expand...
Click to collapse
Okay ill give it a shot, thanks alot. Ill update here if im successful.
Sent from my Nexus 5 using Tapatalk