Hey - I was attempting to return my device to stock, but I appear to have messed up. I have no idea if my device is XT1032 or XT1034, but I've tried flashing both device images, and flashed between CWM and stock a lot of times now, and I can't get my device to boot past the "bootloader unlocked" warning. I also appear to have a new option on Fastboot for some reason: "QCOM" instead of the previous toggle that switched between 'default' and 'tty0' if I recall correctly. I have no idea what I've done that's modified the bootloader like that.
I've got CWM 6.0.5.1 flashed on it right now, but I tried using 'adb push' to install stock images, and that doesn't fix my problem with passing the bootloader warning.
Has anyone got anything I can try to resolve this with? I've heard that GPEifying a device can fix that kind of problem but seeing as I do not know the exact model, I won't try that just yet.
EDIT: Solved, thanks.
I suggest you be very careful with fastboot, it's easy to destroy your phone with it.
You can flash stock via custom recovery using these zips:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
lost101 said:
I suggest you be very careful with fastboot, it's easy to destroy your phone with it.
You can flash stock via custom recovery using these zips:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
Alright then. We'll see how that goes.
EDIT: Worked perfectly. I didn't think of using those, because they made my phone no longer able to uninstall apps or access certain settings, but I'd rather that than bootlooping, so thank you.
Related
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Just go into recovery clear all cache,kavik cache that should do
NerdNoob1210 said:
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
bozzykid said:
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Click to expand...
Click to collapse
Yes. This is my first time doing so, excuse my lack of knowledge on the subject. In retrospect, I suppose I should have known there must be a different method with which I install it. Secretkloud gave me a good suggestion though. Is there a reason in particular as to why I can't do OTA updates with custom recovery installed?
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
I just downloaded the zip from my phone and flashed it from Phillz recovery. It worked very well and the update was successful. Thanks for pointing me to Phillz recovery by the way. It's the only functional recovery image that allows me to mount the sdcard.
NerdNoob1210 said:
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
Click to expand...
Click to collapse
Copy the one you have in your phone onto your PC. Smallest chance of error if you do it that way...
it's not easy getting out of the loop.
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
NerdNoob1210 said:
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
thanks for the suggestion tho. it was a good idea.
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Thanks for trying to help. I have followed your advice and opened a thread
NerdNoob1210 said:
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey Guys. Im running cm12s on my oneplus one, and i would like to switch to oxygenOS because they are getting the touchscreen firmware fixes. Ive flashed recoveries onto multiple phones without this issue before.
I downloaded twrp, booted the phone into fastboot, unlocked it, got the success signal, flashed it, again, success, and then rebooted. Then i powered down and booted to recovery aaaand..... stock recovery. WTF? So i wipe all user data and clear the cache with the stock recovery and try again. Nope. Its still the stock recovery. i dont understand it. I tried with CWM aswell. It says success, so why did it not work? I booted into the OS and checked developer settings, and disabled update recovery and all that, Nevertheless, when i flash TWRP or CWM, it does not work. I dont understand how this could happen.
I followed the steps from the Official guide on the official oneplus forum, It wont let me post a link.
I am using an OEM samsung cable.
Can anyone help me?
fastboot reboot-bootloader ; just after recovery flash.
Orphee said:
fastboot reboot-bootloader ; just after recovery flash.
Click to expand...
Click to collapse
Alright, I've just tried that. After flashing it, i Ran this command and as expected it rebooted back to the bootloader. Nothing else todo there, so i rebooted and booted to the recovery. It STILL boots to the stock recovery! So i tried again, but this time, i flashed it a second time after rebooting to the bootloader, but that still has not worked. is my unit defective? I will try now with another computer.
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
I figured it out!
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
theangrynoob5 said:
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
Click to expand...
Click to collapse
CM didn't just do that to you, it's happened to every single person who's tried to flash TWRP after taking the Lollipop update, that's why the question is included in the FAQ thread.
XDA Moderator
Transmitted via Bacon
HI,
I’ve been having problems with my OPO and I don’t know what to do next.
I was getting stuck in a boot loop – which appeared to be a common issue:
http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/
I had to fastboot oem unlock to run this fix, so I decided whilst I was there to install a custom ROM (SultanROM).
A few days later I got the boot loop issue again, but this time, the fix linked above didn’t work. I thought it wasn’t applying correctly, and so I tried to reinstall the sultan ROM and re-run the Make_Ext4fs fix. Unfortunately, it hasn’t gone well!
The current position is I can now boot in to fastboot or to recovery (TWRP 2.8.7.0), but I think I might have deleted (adb erase) the system partition (because I thought I could easily reflash it, and it wasn’t booting). Now, if I try to boot in to system it gets stuck on the screen with the oneplus logo and doesn’t get any further. I can connect via fastboot (bootloader) or ADB (TWRP). I have used ADB sideload to flash a ROM and I have tried flashing a ROM.ZIP within TWRP but it doesn’t seem to work (most times it cannot mount/find system but sometimes if I “wipe” the phone in TWRP and then flash it *seems* to flash OK (“Operation successful”) but still won’t boot.
Is there a toolkit than can completely rewrite everything on the phone and could fix this? Or any other suggestions?
I don’t have a backup, idiotically as I wasn’t thinking I was doing anything permanent and wasn’t bothered about keeping any of my files.
Thanks!
James
PS – unfortunately my home broadband is broken so I can’t load/try many tools or easily find anything because the only internet access I have is at work, where many things are blocked. I am going over to a friend’s tonight (aprox 5 hours) to try and fix my phone at his house, so any suggestions before that greatly appreciated.
http://forum.xda-developers.com/showthread.php?t=2826541
I would suggest you try taking your phone back to stock COS12.1 and after its installed set it up normally, go back to fastboot and flash a custom recovery, boot TWRP make a backup then proceed to flash a custom ROM. Copy that back up to your computer just in case and also make EFS backups for a rainy day
Sent from my A0001 using Tapatalk
Any way to get "system profiles" tile back in quick settings panel?
Renosh said:
http://forum.xda-developers.com/showthread.php?t=2826541
I would suggest you try taking your phone back to stock COS12.1 and after its installed set it up normally, go back to fastboot and flash a custom recovery, boot TWRP make a backup then proceed to flash a custom ROM. Copy that back up to your computer just in case and also make EFS backups for a rainy day
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks! This process worked and I am back to stock. Unfortunately, still suffering from the boot loop. Frustrating! I'm in touch with OPO Support now... Apparently they can be slow...
jamesking420 said:
Thanks! This process worked and I am back to stock. Unfortunately, still suffering from the boot loop. Frustrating! I'm in touch with OPO Support now... Apparently they can be slow...
Click to expand...
Click to collapse
You probably corrupted your EFS partition somehow. You can try this guide
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
And here I'll link what happened to me and it seems nothing could fix it but these commands from the guide above helped get me out of the bootloop
http://forum.xda-developers.com/showpost.php?p=63611589&postcount=914
Try this stuff if the support guys from OnePlus are unable to help
Renosh said:
You probably corrupted your EFS partition somehow. You can try this guide
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
And here I'll link what happened to me and it seems nothing could fix it but these commands from the guide above helped get me out of the bootloop
http://forum.xda-developers.com/showpost.php?p=63611589&postcount=914
Click to expand...
Click to collapse
Thanks,
That seems to indicate I just need to unlock, flash persist.img and then it should all be OK?
jamesking420 said:
Thanks,
That seems to indicate I just need to unlock, flash persist.img and then it should all be OK?
Click to expand...
Click to collapse
Well it should but if that doesn't work try the options in the second link I posted those worked for me
Sent from my A0001 using Tapatalk
Renosh said:
Well it should but if that doesn't work try the options in the second link I posted those worked for me
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks! And if I erase them (as per second link), do I need to flash them again afterwards?
Reading it again, you mean to erase those two partitions, and then *after* run the flash command. (Initially I thought you meant you ran those two erase commands after you ran the flash command!)
Cheers!
Sorry for the possibly silly question!
I got my OnePlus 7 Pro today and tried to install Magisk by patching the boot.img. After trying to flash the patched image, I now have an issue where rebooting the devices leads me straight back to the bootloader. Trying to enter recovery also leads me straight back to the bootloader. I tried flashing the original boot.img I extracted from the OTA update file provided by OnePlus, but it still isn't working. I do not have TWRP or any custom recovery installed. Any help would be much appreciated. I noticed similar threads, however they all installed twrp, though I haven't yet as trying to run "fastboot boot twrp.img" always resulted in it booting to a screen saying "fastboot mode" which wasn't terribly helpful.
Edit: Its not the tmobile/5g/carrier version. I purchased it through OnePlus' website though I forget the exact model number.
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Faith1105 said:
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Click to expand...
Click to collapse
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
mnbvcxzl90 said:
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
Click to expand...
Click to collapse
Ok, so, trying to restore stock seems to have failed miserably.... any advice is most welcomed qq
OK.... so trying to unbrick the device using the msm stuff, I couldn't even make it to the downloader screen. After holding volume +/- and powering off, my screen is now black HOWEVER the phone gets detected by windows when I plug & unplug it. I have no idea what to do anymore. Someone please help
Figured I'd give the solution here in case someone else is in the same exact problem as me:
Follow the instructions over at https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I tried to de-brick it using the fastboot roms and all that, no dice. The only thing that seems to have worked was following the above and using the msm tool. Everything wiped, but hey, at least the phone is bootable again and now I have a way to fix it should this happen again. Yay for happy endings.
Edit: Also, following Faith1105's advice, flashing twrp to boot instead of trying to just boot it first worked successfully and from there I was able to install magisk.
Edit 2: Now wifi isn't working.... why life, why...
Edit 3: OK: EVERYTHING IS GOOD NOW. Twrp ran into a boot loop issue, used twrp to flash the most recent android 10 zip, rebooted and was greeted by stock recovery, then used that to wipe absolutely everything and reboot. After skipping through initial setup and making use wifi was working I rebooted again and this time tried booting twrp the way the usual instructions say to, this time it worked for whatever reason so once that started I used twrp to flash twrp's installer and magisk. It looks like everything is working correctly now. If you have the same issue maybe this stuff will work for you or maybe not: I don't know, and honestly I'm now brain dead lol.
I have been trying to flash lineage-14.1-20190213-nightly-xt897-signed to my xt897 using TWRP 3.0.2 and all has seemed to go well, however I now can not boot past the "Warning Bootloader Unlocked" screen. I can still access TWRP. Makes no difference whether sideload or within TWRP. I have tried several other images. All have the same issue. I did not make a back up, and can not find a stock rom online. Does anybody have a copy of the stock rom image, or would somebody be able to help me get this thing to boot?
dezgrz said:
I have been trying to flash lineage-14.1-20190213-nightly-xt897-signed to my xt897 using TWRP 3.0.2 and all has seemed to go well, however I now can not boot past the "Warning Bootloader Unlocked" screen. I can still access TWRP. Makes no difference whether sideload or within TWRP. I have tried several other images. All have the same issue. I did not make a back up, and can not find a stock rom online. Does anybody have a copy of the stock rom image, or would somebody be able to help me get this thing to boot?
Click to expand...
Click to collapse
Just search your phone bro. Then add stock ROM.