My shift is not booting any roms i flash. I have clockwork installed and i am wiping everything 4 times before installing, boot cache system data ect, but its not working, everything is getting stuck at the white htc boot screen.
What version of clockwork recovery are you on?
thats exactly what im thinking it is too now, its 2.5.1.8
Update your recovery and you should be good
Current clockworkmod is 3.2.0.1
i think somebody had an issue like this the other day. once they updated their recovery everything worked fine. good luck!
Yep! I just went into fastboot and RUU'd and then rerooted, installed the newest clockwork and voilà flashed and booted up fine!
FrankAmato said:
Yep! I just went into fastboot and RUU'd and then rerooted, installed the newest clockwork and voilà flashed and booted up fine!
Click to expand...
Click to collapse
You didn't need to ruu and reroot.. you could have just flashed the latest recovery via Rom Manager. Glad you got it working though
i completely wiped everything off the phone, and was in boot loops trying to flash roms, so i had pretty much no other choice. (i didnt have a nandroid basically )
FrankAmato said:
i completely wiped everything off the phone, and was in boot loops trying to flash roms, so i had pretty much no other choice. (i didnt have a nandroid basically )
Click to expand...
Click to collapse
Ahh, gotcha. Well lesson learned.. Always keep a nandroid
Related
Hello!
I was on the HKTW build as of yesterday. I have Tenfar's recovery and CWM installed too.
I attempted to install Kennith Penn's Alien Rom V2 and it seems like its flashing no problem... However, I get stuck in a boot loop.
I tried restoring to a previous back up , and that loops now too
So, I attempted to flash 2.3.4 Fruit cakes ( http://www.multiupload.com/U1EOJVAKPO ) and it seems that it is flashing it properly, because I got back my stock "AT&T" boot logo (from the factory) but, that goes into a boot loop too...
Can anyone please help point me in the correct direction of getting my device to boot the rom/ image properly? Is there a setting I need to ensure is checked on CWM (like mounts or something?) ... at this point, I cant even boot into Tenfars recovery... just CWM...
This sucks!
Thanks in advance for any help!!!
ssmr2t said:
Hello!
I was on the HKTW build as of yesterday. I have Tenfar's recovery and CWM installed too.
I attempted to install Kennith Penn's Alien Rom V2 and it seems like its flashing no problem... However, I get stuck in a boot loop.
I tried restoring to a previous back up , and that loops now too
So, I attempted to flash 2.3.4 Fruit cakes ( http://www.multiupload.com/U1EOJVAKPO ) and it seems that it is flashing it properly, because I got back my stock "AT&T" boot logo (from the factory) but, that goes into a boot loop too...
Can anyone please help point me in the correct direction of getting my device to boot the rom/ image properly? Is there a setting I need to ensure is checked on CWM (like mounts or something?) ... at this point, I cant even boot into Tenfars recovery... just CWM...
This sucks!
Thanks in advance for any help!!!
Click to expand...
Click to collapse
Bootloops in 99.9% cases means that you need to wipe.
1. Go back into CWM, wipe data / factory reset, wipe cache, go to advanced and wipe dalvik cache.
2. Flash the desired rom.
3. Go into CWM again and do all the wipes again.
And you should boot no probs.
p.s. these 3 steps should your blue print to installing any rom btw. even you want to backup apps - use TB.
thank you for your help....ive actually dome all of that and still no go
ssmr2t said:
thank you for your help....ive actually dome all of that and still no go
Click to expand...
Click to collapse
Have you tried wiping via fastboot?
moto-fastboot -w
p.s. do you have the latest CWM recovery? there can be problems if you arent using the latest one.
xploited said:
Have you tried wiping via fastboot?
moto-fastboot -w
p.s. do you have the latest CWM recovery? there can be problems if you arent using the latest one.
Click to expand...
Click to collapse
+1. i was having the same problem not too long ago and that fixed my problem.
Ok so first off I was successful in rooting the phone, installing twrp rec., flashing loki files, and then flashing wicked rom with ktweaker tw kernel. I made a backup of the stock rooted rom before wicked was flashed. Then my troubles started when I wanted to go back to my stock backup. The rom booted but has serious issues like black screen with only status bar working and then eventually freezing. I also made a backup of a working wicked and tried restoring that but then I just get stuck in boot loop. Any help would be greatly appreciated.
what twrp version
did you wipe all before restoring
you could try to install Phils cwm recovery, folks say it works great and will restore twrp backups also
thesystem90 said:
Ok so first off I was successful in rooting the phone, installing twrp rec., flashing loki files, and then flashing wicked rom with ktweaker tw kernel. I made a backup of the stock rooted rom before wicked was flashed. Then my troubles started when I wanted to go back to my stock backup. The rom booted but has serious issues like black screen with only status bar working and then eventually freezing. I also made a backup of a working wicked and tried restoring that but then I just get stuck in boot loop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Follow full wipe procedures, have the same recovery you made the backup with, and try again.
rugmankc said:
what twrp version
did you wipe all before restoring
you could try to install Phils cwm recovery, folks say it works great and will restore twrp backups also
Click to expand...
Click to collapse
I flashed the stock firm. Soft brick averted. Did the same goo manager recovery method, but now i'm thinking of flashing that cwm as ppl have reported the same nandroid backup issues with twrp. My version is 2.5.0.2. I will keep trying to get twrp for a while with others users till i get sick of it (semi twrp fan). Any further advice would be cool. Oh and I did a factory twrp wipe the first time this problem occurred.
I wipe data caches and system before flashing. No more advice. Had newest TWRP hang on Team Win screen. Several manual reboots into recovery till it worked. Maybe I better do restore to see if it works.
Sent From My 32gb Samsung Galaxy S4 Running Tapatalk 4 Beta
Hi guys I've been searching and cant seem to find an answer. My xt907 is rooted and my boot loader is unlocked I'm running CWM. If i install any 4.3 roms they work great for initial boot but as soon as i reboot it hangs at the warning boot loader unlocked screen. And the only way i can get the phone working again is to get to ap fastboot and use the DROID_RAZR_M_Utility_1.20 to factory reset everything. If i flash a 4.2.2 rom i don't have any problems. Any ideas guys ? Ive searched and cant seem to find an answer anywhere. Thanks in advance!
My first flash of 4.3 did this... after that I used twrp and haven't had it happen since...
Sent from my XT907 using xda app-developers app
The latest TWRP+mounting system prior to data/system wipes will probably solve your problems. Also, if you have a backup stored, you shouldn't need to fastboot every time.
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Ryan F said:
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Click to expand...
Click to collapse
twrp 2323???
You need twrp 2630
see my goodies.
aviwdoowks said:
twrp 2323???
You need twrp 2630
see my goodies.
Click to expand...
Click to collapse
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
Fastboot!
Extract the recovery.img from the zip.
But why do that, just flash the zip from your twrp you now have installed
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
I believe the one that Avi has is a .zip, not a .xml, so it needs to be flashed in recovery. Load it up on your SD, boot into the recovery you have now, flash the new recovery, and then reboot recovery.
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
aviwdoowks said:
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Click to expand...
Click to collapse
Okay, I downloaded the zips again to make sure. This freezing at bootloader screen has happened with every of the dozen or so roms I've tried installing over the past 6 months since I unlocked the bootloader.
RikRong said:
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
Click to expand...
Click to collapse
Could you clarify a little bit?
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
What's the FDR option?
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
Ryan F said:
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
Click to expand...
Click to collapse
Following the above steps didn't solve it The rom installs fine, boots up for first time normally, but still freezes on the bootloader screen after a restart.
Try geting to the bootloader options & choose normal pwr up.
The new twrp will stick at the big M sometimes.
Then the file is bad or you are missing the install steps. FDR (Factory Data Reset) is the first option you get when you go into the wipe menu, before you go into advanced options. Make sure you're wiping system too, after you mount. If it doesn't work, then it's a bad file or you're still doing something wrong. Upgrading to the most current TWRP and mounting system fixed the issues for 99% of the people. The other 1% just have one of those phones that is "quirky."
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
beady1 said:
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
Click to expand...
Click to collapse
Part of your problem is because you are using SS. If you're BL is unlocked, get rid of SS and use CWM or TWRP. SS is not a real recovery replacement, your stock recovery is still there. That's probably part of the reason you had issues.
possibly but i have 0 issues now so its not a big deal.
I have the stable Cyanogenmod 10.1 installed on my phone now. I'm able to restart my phone without any consequences finally. Yay.
I also tried the cm-11-20131221-NIGHTLY-xt907.zip build. That one would initially start up fine, but a restart gave me the frozen bootloader screen. I tried it twice, redownloading it, too. Gah, it's frustrating not being able to try out different roms, but at least I have one that works!
Well, thanks for the help guys. I'd still like to be able to install other roms, so if anyone else has something I can try, I'll do it!
I was having issues with my phone not getting a GPS fix. So, I figured I'd try a few different ROMs. I was on this rom, http://forum.xda-developers.com/showthread.php?t=2771110, and everything worked great except the GPS. I then did a TWRP backup and installed Cyanogen 11. It booted fine into it, but I still couldn't get a GPS lock. So, I thought, maybe it's a kitkat issue with my phone. So, I tried installing this rom, http://forum.xda-developers.com/showthread.php?t=2595586, after doing a full wipe except for internal storage. It sat at "formatting", as the OP says it may, but it finally finished. Then, it wouldn't boot. It just sat at the LG logo screen. I went back into TWRP and tried a few wipes (cache, dalvik, and data), but it still wouldn't boot. So, I decided to restore my TWRP backup of Lam Hoang 7.1, and now it is still stuck at the LG logo, and won't boot.
Any help would be appreciated!
Try a different recovery. I'd start with Philz recovery. After flashing Philz recovery I'd reflash the most recent ROM listed in your second link. In my experience twrp has given me quite the trouble. Good luck.
Sent from my SAMSUNG-SGH-I317.
CharliexCharger said:
Try a different recovery. I'd start with Philz recovery. After flashing Philz recovery I'd reflash the most recent ROM listed in your second link. In my experience twrp has given me quite the trouble. Good luck.
Sent from my SAMSUNG-SGH-I317.
Click to expand...
Click to collapse
Can I restore a TWRP backup with Philz recovery?
ledvedder said:
Can I restore a TWRP backup with Philz recovery?
Click to expand...
Click to collapse
Not that I've ever been made aware of.
Sent from my SAMSUNG-SGH-I317.
ledvedder said:
Can I restore a TWRP backup with Philz recovery?
Click to expand...
Click to collapse
Yes you can but you cannot restore a philz backup with twrp
Sent from my Potato powered G2 D800
How? When I go into restore backup in Philz and select my backup, it just shows me a bunch of files (some with a .md5 extension).
I got it back up. Flashed Philz and installed a rom. Then, I restored one of my backups, and it booted fine.
ledvedder said:
I got it back up. Flashed Philz and installed a rom. Then, I restored one of my backups, and it booted fine.
Click to expand...
Click to collapse
Awesome. Twrp just seems buggy from time to time.
Sent from my SAMSUNG-SGH-I317.
Still have no GPS though. I wish I knew why, because it used to work fine.
Hello,
I've rooted my own note 3 and flashed Temaseks unofficial cm 12 rom. Everything works perfect so I decided to do the same thing for my father. It all went well, first I rooted his phone, then I flashed CWM and flashed cm 12 by temasek. The rom works fine but I forget to install the Gapps. So I tried to install Gapps but I got an error "Failure Status 6". I googled on that error and someone told it has to do something with CWM. I tried to flash a different version of CWM but now I can't reboot into recovery mode anymore. So I can't flash anything.
I flashed another version of CWM but this one also doesn't work. Whenever I try to boot the phone into recovery mode, the blue line shows up. Rebooting into recovery mode, but after a few secs, the phone just boots the normal way. Is there anyone that can help me to get CWM back to work? In the mean time I'll try to flash TWRP by Odin.
Thanks in advance!
So I flashed latest version of CWM: Buildversion; 6.13.0, CWM Base Version V6.0.4.7. I can reboot into recovery now but still can't install Google Apps due to failure status 6. On my own Phone I run a different version of CWM, but when I try to flash it, the phone won't boot into recovery mode anymore. It only boots into recovery when I flash this V6.0.4.7 . How can I get rid of this version and flash an older version of CWM?
You'll probably have to Odin back to stock and start over...
Morningstar said:
You'll probably have to Odin back to stock and start over...
Click to expand...
Click to collapse
You mean If there is no other way to get the Google Apps on the phone, I have to go back to stock. I did make a backup with CWM on the while it was running custom firmware. Now I have 4 files on my comuter, 3.tar and 1.md5 . If I recover them, I will still have this not working CWM version on my phone right? Isn't there a easier way to delete CWM, can I flash TWRP over CWM and see if it will install these Gapps?
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Morningstar said:
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Click to expand...
Click to collapse
I appreciate your effort, thank you. The recovery issue is solved. I flashed Chainfires Root script and that installed the stock recovery. However, when I tried to install and older CWM version I got back in the recovery reboot cycle. But once I installed the latest CWM it booted in recovery. So I flashed Chainfires Root once again and had the stock recovery back. From there on I tried to install TWRP but got the recovery boot cycle again. My phone is now running android 5.0.2 and I think that's the problem.... :S I'll try again to flash Chainfires Root script to get the stock recovery back. From there on I will try to flash the link you gave to me with Odin and hope that will fix it. Do you have any ideas on what I'm doing wrong?
Your version of TWRP works so far. It reboots into RecoveryMode. Now I'll wipe and try to install Temaseks Cm 12 followed by Gapps! Thanks so far!
Okay, it's solved. Can't thank you enough for you help. Bless you!!
No problem. Glad you got it figured out!
[emoji106]