Database Users

[Q] Xt907 Freezes at bootloader unlock screen on 4.3 Roms

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!

Nexus 4 won't boot any ROM!

My friend gave me his Nexus 4 to fix, for some unknown reason it does not boot. It earlier worked fine and was running Stock 5.1.
So I tried to fix it by loading the latest Factory Image from Google's website. I downloaded the latest build. extracted it, and followed the instructions given on their website. I was able to successfully install the OS by using the Flash-All script. The phone rebooted once the flashing process got over.
But the phone never booted, it got stuck on the circles flying around boot animation. I did the entire process again and waited for 45 minutes but it still did not boot. I went in the Stock Recovery and wiped the Cache and did a factory reset and still the same. I even tried locking and unlocking the bootloader again but still no result.
After doing all this I decided to install CyanogenMod 12.1 Snapshot, so I downloaded the latest version of TWRP and installed it. Booted into TWRP.
Wiped Dalvik, Cache, Data and System. Flashed the ROM, the ROM installed successfully. But now even CM12.1 won't boot!
How am I supposed to make this phone boot?
Please help me.
Thanks in Advanced.

Same problem
cyborgmanu said:
My friend gave me his Nexus 4 to fix, for some unknown reason it does not boot. It earlier worked fine and was running Stock 5.1.
So I tried to fix it by loading the latest Factory Image from Google's website. I downloaded the latest build. extracted it, and followed the instructions given on their website. I was able to successfully install the OS by using the Flash-All script. The phone rebooted once the flashing process got over.
But the phone never booted, it got stuck on the circles flying around boot animation. I did the entire process again and waited for 45 minutes but it still did not boot. I went in the Stock Recovery and wiped the Cache and did a factory reset and still the same. I even tried locking and unlocking the bootloader again but still no result.
After doing all this I decided to install CyanogenMod 12.1 Snapshot, so I downloaded the latest version of TWRP and installed it. Booted into TWRP.
Wiped Dalvik, Cache, Data and System. Flashed the ROM, the ROM installed successfully. But now even CM12.1 won't boot!
How am I supposed to make this phone boot?
Please help me.
Thanks in Advanced.
Click to expand...
Click to collapse
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.

mose_nd said:
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
Click to expand...
Click to collapse
I also posted this is the Nexus 4 Community on Google Plus. I am going to try out what they said.
Here is the link:
https://plus.google.com/117172821556811787798/posts/dzVorg3JSUw

SOLVED!
mose_nd said:
I have the same problem, and I am trying to download factory 4.4.4 image.
guys help us plz.
Click to expand...
Click to collapse
Hey I fixed it! It finally booted up.
You need to use the first Factory Image, that is, the Android 4.2.2 Jelly Bean Factory Image.
Once you have flashed the image, the phone will boot up quickly - Mine booted in around 5 minutes I guess.
Here is the link - https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz

Nexus 6p bootloop (NOT same as Infamous BLOD)

Hi! Guys I have a problem, which doesn't resemble the BLOD, so here is what has happened. I was running stock android June build on 6p, rooted. And my phone started random reboots. I thought it could be fixed with either stock or custom rom. So I decided to flash AOSPA. I went into twrp but could not flash it, phone rebooted each time. I tried stock images via flash all command as well as manual. No rom worked although I could flash kernel etc. I used The Flash's custom twrp and fixed data and was able to flash rom easily, but it bootlooped on google logo, and rebooted. Now I can flash roms etc but it bootloops. Although Tesla rom did go into bootanimation before bootlooping.
So what can I do? Is it software related? What do you guys say!
PS. I did look into other threads, nothing was similar, although I did try a few mentioned fixes.

osamaasif786 said:
So what can I do? Is it software related? What do you guys say!
Click to expand...
Click to collapse
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat

v12xke said:
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
Click to expand...
Click to collapse
It gives no error and did try the flash-all.bat method no luck.

osamaasif786 said:
It gives no error and did try the flash-all.bat method no luck.
Click to expand...
Click to collapse
I'd say you were squarely in a small group of people who are able to access and fully use Recovery but still boot loop after formatting and installing a clean image. If you've already tried a factory reset from the stock recovery I think you are done. Hardware issue. Replacing the motherboard is a fix, but not economically viable.

I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.

Exodusche said:
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Click to expand...
Click to collapse
Which modified one, can you share the link?

osamaasif786 said:
Which modified one, can you share the link?
Click to expand...
Click to collapse
Cortex ROM it's flashable stock firmware with extras . Though my symptoms where the same I hope I'm not giving you false hope. Worth a shot though.

The only was I recover my phone without replacing is using https://forum.xda-developers.com/nexus-6p/general/boot-images-bootloop-t3633723 < method from here... but the phone is lag af as it is only running 1 core on stock july build. Good luck for that.

I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.

TheTickReborn said:
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
Click to expand...
Click to collapse
So have you used fastboot to FORMAT system, userdata and cache? Did each format command complete with no errors?

ZE552kL (Soft Bricked)

I have bricked my phone the issue I am facing is I don't own and can't afford an SD card to sideload the rom onto my phone is there a 7.0 stock based rom that is flashable via TWRP or? Really need some ideas need to fix this device.

If you have access to TWRP, then plug your phone into your computer and it'll mount your internal sdcard. Copy any Rom you want onto it and flash as normal (remember to wipe cache and dalvik!). If you get the "error 7" output, edit your updater script and do it again. If you get a bootloop after successfully flashing, flash the latest magisk zip (I assume you use root?) or noverity file if not.

wang1chung said:
If you have access to TWRP, then plug your phone into your computer and it'll mount your internal sdcard. Copy any Rom you want onto it and flash as normal (remember to wipe cache and dalvik!). If you get the "error 7" output, edit your updater script and do it again. If you get a bootloop after successfully flashing, flash the latest magisk zip (I assume you use root?) or noverity file if not.
Click to expand...
Click to collapse
I use root and both but when I decided to remove root and was looking at installing another rom it failed now I don't see any twrp flashable roms for my device would you know of any? I tried stock but it can't be flashed from TWRP sadly I have no bootable rom at the moment.

@mastermarkofroms
EVERY Rom that can be flashed through stock recovery can be flashed through TWRP.
....all you need to do is edit the updater script as I said above. Give it a shot
Edit: you softbricked your phone removing root? Just perform a factory reset, you'll lose your personal data but it'll boot. Remember to wipe cache and dalvik.

wang1chung said:
@mastermarkofroms
EVERY Rom that can be flashed through stock recovery can be flashed through TWRP.
....all you need to do is edit the updater script as I said above. Give it a shot
Edit: you softbricked your phone removing root? Just perform a factory reset, you'll lose your personal data but it'll boot. Remember to wipe cache and dalvik.
Click to expand...
Click to collapse
I have never modified that before what would I need to modify to get it working?

@mastermarkofroms
Open the Rom archive and edit the updater script (/META-INF/com/google/android/updater-script) to remove the first 7 lines (sometimes more or less) of code, so the script starts at "ui_print....." now. Save it, and load it onto your sdcard and flash.

wang1chung said:
@mastermarkofroms
Open the Rom archive and edit the updater script (/META-INF/com/google/android/updater-script) to remove the first 7 lines (sometimes more or less) of code, so the script starts at "ui_print....." now. Save it, and load it onto your sdcard and flash.
Click to expand...
Click to collapse
I will give that a shot turns out a factory reset did not start up device so this is my last choice as I can still access recovery
edit: so after modifying the script it did flash without an issue but it still has failed to boot reloading the bootloader.

Flash magisk or the no verify file

wang1chung said:
Flash magisk or the no verify file
Click to expand...
Click to collapse
the no verify file was flashed when I rooted this device

Which Rom did you flash?
You performed a factory reset and wiped dalvik and cache after flashing? How long did you wait after rebooting? Usually takes 5-10min on the first boot.
Edit: you flashed the no verity file after flashing the rom today, right?

wang1chung said:
Which Rom did you flash?
You performed a factory reset and wiped dalvik and cache after flashing? How long did you wait after rebooting? Usually takes 5-10min on the first boot.
Edit: you flashed the no verity file after flashing the rom today, right?
Click to expand...
Click to collapse
I tried flashing Unofficial LineageOS 14.1 for ZE552KL by basenode with opengapps it just failed to flash not an error 7 it actually gave me a wrong device error although I know I have the ze552kL model. and since then it don' boot it tries to you see the asus logo and it just restarts again in a boot loop

Flash magisk right now, then wipe cache and dalvik

Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .

[email protected]@ said:
Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .
Click to expand...
Click to collapse
Thanks for the info will give that a shot as soon as I do get home from work. Just ablittle annoyed that first phone I have ever bricked

[email protected]@ said:
Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .
Click to expand...
Click to collapse
Any ideas where I can find the no verity file? I dont see it on the forum unless I am blind

mastermarkofroms said:
Any ideas where I can find the no verity file? I dont see it on the forum unless I am blind
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/ze...20kl-ota-upgrade-doesnt-t3706856/post74571792

[email protected]@ said:
Here https://forum.xda-developers.com/ze...20kl-ota-upgrade-doesnt-t3706856/post74571792
Click to expand...
Click to collapse
Problem solved back on stock thanks for all the help @everyone

mastermarkofroms said:
Problem solved back on stock thanks for all the help @everyone
Click to expand...
Click to collapse
I thought you ask for the LOS rom.

I did the thing is had it installed and everything but my phone kept freezing and lagging with it not sure why as I had nothing on there that would of caused it. But the lag once I got it working was just unbearable for me

mastermarkofroms said:
I did the thing is had it installed and everything but my phone kept freezing and lagging with it not sure why as I had nothing on there that would of caused it. But the lag once I got it working was just unbearable for me
Click to expand...
Click to collapse
Which rom?

[SOLVED] Bootloop since TWRP installation

Hi Everyone,
The first thing I did after flashing TWRP on my RN7 was a BackUp with TWRP of all my partitions. (It was the first time i launched it, so i also saved the Miui Recovery).
Then I tried to boot on the system but I get stucked in the "Redmi by Xiaomi" screen.
I tried to install an AOSPExtended Rom but it didn't worked.
I flashed Orange Fox and retrayed to flash AOSPExtended. It didn't worked either because it was designed for violet and not for Lavander (facepalm).
I tried an Unofficial LineageOS found on XDA, the installation worked but I'm stuck in a bootloop since.
The Redmi by Xiaomi screen starts over and over. I can't even turn off my phone.
I tried to reboot after wiping Cache, System, Vendor, Data and Dalvik (just to see if I would be able to turn it off) but same result.
Do you have any Ideas?
Thanks a lot!

Which rom did you have while taking the first backup?
Wipe System, Data, Cache, then reboot the recovery and then restore the backup of System, Data and Boot. Don't restore recovery. See if this works.

Lisatio said:
Hi Everyone,
The first thing I did after flashing TWRP on my RN7 was a BackUp with TWRP of all my partitions. (It was the first time i launched it, so i also saved the Miui Recovery).
Then I tried to boot on the system but I get stucked in the "Redmi by Xiaomi" screen.
I tried to install an AOSPExtended Rom but it didn't worked.
I flashed Orange Fox and retrayed to flash AOSPExtended. It didn't worked either because it was designed for violet and not for Lavander (facepalm).
I tried an Unofficial LineageOS found on XDA, the installation worked but I'm stuck in a bootloop since.
The Redmi by Xiaomi screen starts over and over. I can't even turn off my phone.
I tried to reboot after wiping Cache, System, Vendor, Data and Dalvik (just to see if I would be able to turn it off) but same result.
Do you have any Ideas?
Thanks a lot!
Click to expand...
Click to collapse
Flash a custom ROM with the latest OrangeFox, then format the data partition (Menu->Manage Partitions->Data->Format data->"yes"), then reboot to system.
Do NOT try to restore your TWRP backups.

I finally tried an other Lineage Os Rom from XDA and it finally worked.
But I don't really know why.
The first one I tried to install was in fact a Potato OS... (You can download it from the same page!)
But still, this ROM was for Lavander too, I don't understand why it didn't worked....
Anyway my phone is OK now! Thanks a lot!

DarthJabba9 said:
Flash a custom ROM with the latest OrangeFox, then format the data partition (Menu->Manage Partitions->Data->Format data->"yes"), then reboot to system.
Do NOT try to restore your TWRP backups.
Click to expand...
Click to collapse
What would happen if I tried to restore my Backup?

Lisatio said:
What would happen if I tried to restore my Backup?
Click to expand...
Click to collapse
What would happen is :crying: Returning to MIUI from a custom ROM is a can of worms. There are instructions here: https://wiki.orangefox.tech/en/guides. But even that is not guaranteed to do the job.

DarthJabba9 said:
What would happen is :crying: Returning to MIUI from a custom ROM is a can of worms. There are instructions here: https://wiki.orangefox.tech/en/guides. But even that is not guaranteed to do the job.
Click to expand...
Click to collapse
Thanks a lot, I won't try then!
Do I have to Edit my thread title with a [SOLVED] sign?

Lisatio said:
...Do I have to Edit my thread title with a [SOLVED] sign?
Click to expand...
Click to collapse
I think that would be a good thing, otherwise, people will stumble upon it, and keep posting.