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!
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.
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
danlk2 said:
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
Click to expand...
Click to collapse
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
irishrally said:
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
Click to expand...
Click to collapse
Wow, that didn't even cross my mind, I did this and I've got the rom up and running now. Thanks a lot.
Ok, so I've tried to replicate this with different ROM's and I still get the same result. I have an AT&T i337 Galaxy S4 rooted with Motochopper and installed TWRP 2.6.0 via Goomanager, and tried different google edition roms and stock touchwiz roms. I'll install a rom, get it up and running [install my apps,theme,etc]. Then I'll do a random reboot, and the phone just stays at the Samsung Unlocked Custom screen, for about 5 minutes, then it'll act as if I just installed the ROM i just previously set up as if it was a new setup...I don't understand any of this, am I missing something (are you not allowed to reboot the phone). Any help would be greatly appreciated!
Any questions as to how I install my roms. 1.Boot Into Recovery, 2.Wipe Data format data wipe cache 3.Select Install on TWRP, 4.Choose Rom, 5.Choose Loki-Doki, 6.Let it all install 7. wipe cache and dalvik again 8.boot system 9.Setup android, install apps, themes, 10.Reboot...then it goes back into the Samsung Unlocked Custom Screen, wait 5 mins and I will have to run through the android setup again, as if it forgot that I just installed it. All my apps, themes, customizations are gone.
Happens with ANY custom ROM i choose, google edition OR stock touchwiz roms.
do I need to flash loki doki everytime I reboot? So for example...reboot, go into recovery, flash loki-doki, boot? I've never encountered so much problems with rebooting my phone with any custom roms...
Thanks guys!
i dont use twrp but i've heard things about formatting /data causing problems. maybe someone with more twrp expertise can chime in with a fix.
you could consider some other possible options and if you dont have any success, you may want to consider starting over via stock firmware/odin. when you go through the root process again and twrp is installed in casual (i think 2.5.0.0), stay on it. dont update to a newer release. either that or change custom recoveries. after you've made a backup:
wipe data/factory reset
wipe cache & dalvik
format /system (not /data)
then flash the rom and loki-doki or an at&t loki'd kernel (like ktoosez).
wipe your caches again if you'd like and reboot.
let the phone sit for 5 or more minutes, reboot and just setup your gmail account stuff. not everything. give it another reboot to see if it stuck.
I have been having this same issue as of late, and I am using TWRP 2.5.0.2 and 2.6.0.0. It seems that the only thing I can use is a CM type ROM, I can't get TW to reboot at all after the initial boot. I am factory restoring now and going to use CWM and then try SHOshock 2.1
---------- Post added at 07:18 AM ---------- Previous post was at 06:42 AM ----------
Okay factory restoring through odin and using CWM or OUDHS works just fine. That's what you need to do.
i ran into this problem as well a few weeks back , the problem is twrp , if you do a full wipe where you type in "yes" and it resets to factory defaults , your phone will reboot 1 time only , after that it will get stuck on that screen , only way i found to fix it was to flash back to stock thyen reroot and install twrp again., then never do a full wipe where you have to type "yes"
hope it helps....
No Ax, not more of the SAME questions over and over, please, do not get...But...NO Ax, get outta here....
TRY A DIFFERENT LOKI KERNEL for your device.
WHY LOKI-DOKI?
Not sure if this is entirely the same problem (sorry Ax if this is a duplicate from something else) but for non AOSP ROM's I've tried using loki doki and for every subsequent reboot I get the screen where it says AT&T recognizes an unsupported software on my device.
This has happened on two different ROM's which just caused me to be gun-shy and go back to CM, which allows me to reboot whenever I want with no worries.
For non-AOSP ROM's do I need to loki doki after every single reboot?
the_liv80 said:
Not sure if this is entirely the same problem (sorry Ax if this is a duplicate from something else) but for non AOSP ROM's I've tried using loki doki and for every subsequent reboot I get the screen where it says AT&T recognizes an unsupported software on my device.
This has happened on two different ROM's which just caused me to be gun-shy and go back to CM, which allows me to reboot whenever I want with no worries.
For non-AOSP ROM's do I need to loki doki after every single reboot?
Click to expand...
Click to collapse
No prob, we cool, this is exactly why I stress a loki kernel, why? because you know that kernel works EVERY TIME. I have never used loki doki yet, nor am I about to start, I listed what, some 50 roms in my guide and I flashed every one of them with 1 kernel and 1 only. The wrong kernel does numerous things like, the unsupported screen, hangs at samsung logo, throw you into a bootloop, and in some instances will throw you into the recovery loop. I have seen many when I flashed the roms, but I worked my way out of 3/4 of them with out having to odin back to anything. Now no one get confused, loki kernels for att/verizon, your carriers kernel for all others.
Thanks @TheAxman - tried using the Loki kernel from your guide on both Omega ROM and Mint Jelly. Got a boot loop again on MJ and couldn't get passed the stupid acore process failure on Omega...plus, I had the added benefit of Omega wiping Data after I chose not to.
So.....ended up having to format and reflashed CM.
I got into this issue just now I was trying to wipe it clean cause I'm about to sell it now it's stuck on the Samsung Galaxy S4 screen. I'm running on the Canadian variant I337M. I too was using TWRP. What do I do?
xBeerdroiDx said:
i dont use twrp but i've heard things about formatting /data causing problems. maybe someone with more twrp expertise can chime in with a fix.
you could consider some other possible options and if you dont have any success, you may want to consider starting over via stock firmware/odin. when you go through the root process again and twrp is installed in casual (i think 2.5.0.0), stay on it. dont update to a newer release. either that or change custom recoveries. after you've made a backup:
wipe data/factory reset
wipe cache & dalvik
format /system (not /data)
then flash the rom and loki-doki or an at&t loki'd kernel (like ktoosez).
wipe your caches again if you'd like and reboot.
let the phone sit for 5 or more minutes, reboot and just setup your gmail account stuff. not everything. give it another reboot to see if it stuck.
Click to expand...
Click to collapse
thats most likely his issue.
Slade8525 said:
thats most likely his issue.
Click to expand...
Click to collapse
Seems like it.
---------- Post added at 11:47 PM ---------- Previous post was at 11:44 PM ----------
th3xeroeagle said:
I got into this issue just now I was trying to wipe it clean cause I'm about to sell it now it's stuck on the Samsung Galaxy S4 screen. I'm running on the Canadian variant I337M. I too was using TWRP. What do I do?
Click to expand...
Click to collapse
What device do you have? I337m?
TheAxman said:
Seems like it.
---------- Post added at 11:47 PM ---------- Previous post was at 11:44 PM ----------
What device do you have? I337m?
Click to expand...
Click to collapse
Yup can I use ODIN too?
th3xeroeagle said:
Yup can I use ODIN too?
Click to expand...
Click to collapse
Sorry, was on my phone lastnight, did not see that.
Odin stock, after it finishes do a factory reset. You should be ok after that.
samsung-updates.com
ive tried a whole bunch of roms and the behavior seems to be very consistent.
Here's the scenario, same for every rom:
-boot into TWRP, advanced wipe -> wipe everything
-flash rom over adb sideload
-reboot system
-rom comes up just fine the first time, log into google, restore apps
-any time i reboot after, it sits on "Galaxy s4" boot screen, if I then reboot into recovery, TWRP asks for password because it can't mount partitions.
-only way ive found to get out of this is to format data, then reflash.. only until the first reboot again.
stock rom works flawless, the only custom rom that also worked flawless was task650's AOKP 4.2 rom, which was strange but i used it for couple months. now since i i updated to his latest 4.3 release the same issue came up, so i tried again a number of different roms.. no luck
ive exausted my google-fu and these forums, can someone please help... is this a kernel issue? bad hardware? am i just doing something very simple very wrong?
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
jd1639 said:
In twrp, just do the standard wipe, the one that you just swipe the wipe. I think your wiping too much.
Then install the Rom, kernel, and what else you may need, no need to side load it
Click to expand...
Click to collapse
same thing, except this time it didnt even boot once, stuck on "galaxy s4" logo, then rebooting back into TWRP prompted a password coz it couldnt mount anything...
i think it gets stuck on boot logo because it cant mount partition same way TWRP cant, but i have no idea why it wouldnt be able to after a reboot or what could be screwing it up
Why don't you try flashing a new recovery?
I downloaded Imperium ROM from a thread on xda and installed it. I wiped data, wiped cache and dalvik and installed zip. Then I rebooted and it showed a downloading screen, after a little bit of research it's called download mode or ODIN mode. Now what's happening is whenever I try to reboot, it shows the S4 i9505 screen (i think it's called a splash screen, thats what someone called it) and freezes. After about 10-15 seconds, reboots into recovery. I've got CWM installed and I've ran out of ideas. The volume buttons are not being touched and for some reason recovery and download mode are always being booted into, never the OS.
I'm also new so anything I've done wrong, I'd love to know.
CWM recovery is outdated and should not be used anymore. Instead only use TWRP. Flash it trough Odin in the same way you flashed CWM.
You say that you only wiped data, cache and dalvik. You also HAVE to wipe /system. Otherwise the rom will probably not boot.
Lennyz1988 said:
CWM recovery is outdated and should not be used anymore. Instead only use TWRP. Flash it trough Odin in the same way you flashed CWM.
You say that you only wiped data, cache and dalvik. You also HAVE to wipe /system. Otherwise the rom will probably not boot.
Click to expand...
Click to collapse
Update I tried to install albe95's s6 port. I've noticed something and it's that both ended up with Statuc 7 or some word that started with "S" and had the number 7. Googled that and turns out it's bad. I formatted /System and installed the ROM, it worked!
I guess there was just no OS to boot into. Going to try installing Imperium now.
Status 7 errors can occur if the recovery is outdated. What recovery is on the phone?