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.
Hi:
I unlocked and successfully rooted my Nexus 10 (JB 4.3). Also have TWRP 2.6.1 installed. It worked fine with the stock rom rooted. Then I tried to install Custom Rom.. Paranoid Android..3.99. Everything went smooth until.I got stuck in BOOTLOOP. Reading the forums posts, I went back to recovery and wiped cache/dalvik cache.. and rebooted.. This time it proceeded with the ANDROID IS UPGRADING...but at the end of this once I got the lock screen..the dreaded UNFORTUNATELY SYSTEM UI has STOPPED window pops up and this is where I am stuck.
I have since then booted into recovery and cleaned cache and reinstalled custom roms.. PA, STOCK, CM 10.2 many times but of no use. The tablet is stuck at the SYSTEM UI HAS STOPPED.
Is there any way to fix this... ? ANY HELP WILL BE GREATLY APPRECIATED
I would be glad to get back to FACTORY SETTINGS if I can. Note that I can push files from my MAC using "ADB" and then use recovery.
THANK YOU IN ADVANCE FOR YOU ALL.
Edit: Well guess what... I did not see FACTORY RESET in TWRP all along (BEING DEFAULT ACTION) and was just wiping cache/dalvik cache before rebooting. FACTORY RESET is a life saver.... it works. Hope this helps others in similar situation. I am back on CM 10,2 and running.
Excellent. That was gonna be my suggestion, but glad you got it figured out.
Sent from my Nexus 10
vicky4112 said:
/snip
Click to expand...
Click to collapse
In the future, learn to use fastboot. ADB only helps you if you have a custom recovery that can run ADB onboard, which isn't always the case (for example, if you kill your internal storage). What could have saved you here would have been:
fastboot wipe userdata
fastboot wipe data
fastboot update -w /path/to/stock-image.zip
It's harder to kill fastboot on Nexus devices, so it's worth learning.
Rirere said:
In the future, learn to use fastboot. ADB only helps you if you have a custom recovery that can run ADB onboard, which isn't always the case (for example, if you kill your internal storage
Click to expand...
Click to collapse
Alternatively, TWRP can mount an otg-usb device. Totally saved my tush the other night.
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!
To make a long story short, after unlocking bootloader and rooting a friend of mine thought it would be a GREAT idea to install Layers on a stock ROM... after that my phone goes black after the Motorola screen. Ended up wiping the OS off the phone and didn't have a chance to do a nandroid backup... I can get into TWRP just fine... is there anyway to get this thing working again... btw i tried the WIndows Tool with no success and tried it on a Mac with Terminal with no luck... Any ideas?
What exactly have you tried so far. The solution to issues like this is typically to get hold of a factory system image and ADB reflash the system partition while in fastboot mode.
See this post http://forum.xda-developers.com/showpost.php?p=63074207&postcount=89
The same happened to me and I if you are able to boot into TWRP, then you can follow the exact steps to re-flash the image files and be able to restore to factory stock.
Im on the latest Februarys version. Bootloader is unlocked. Flashed twrp-3.0.2-0-clark then this Is where I think I muffed up. installed SU 2.76. Then read somewhere to reflash 2.62. Right now im stuck on the blue M with circles. I need some help. I don't know where or what to do next. Ive read as much as I can but to no avail. If some one can help me I would appreciate and input.
StankFiss said:
Im on the latest Februarys version. Bootloader is unlocked. Flashed twrp-3.0.2-0-clark then this Is where I think I muffed up. installed SU 2.76. Then read somewhere to reflash 2.62. Right now im stuck on the blue M with circles. I need some help. I don't know where or what to do next. Ive read as much as I can but to no avail. If some one can help me I would appreciate and input.
Click to expand...
Click to collapse
Did you try wiping cahe and dalvik cache by rebooting into TWRP?
Do you have nandroid backup of your original ROM? if you have the backup then restore it.
Always make nandroid backup using TWRP before flashing anything like SUperSU / Viperfor andoird or any other custom kernel.
Thanks
Unfortunately I don't have a backup. in my excitement I proceeded. I did wipe dalvik cache. There has to be way out of this. But my knowledge is limited with android.. Im use to the old days of using RSD Lite to install image again. Is there a way to that:?
Well I done it now. It says no OS. When it boots it stuck on bootloader has been unlocked screen. Someone please help me. To restore to stock. Thanks in advance.
Nevermind figured it out myself. Any1 new to this and did what I did. go here http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833