Related
I haven't seen this written anywhere yet but I've found something weird with the TWRP loop, months back I used the asus system wipe and got stuck in the TWRP loop because I supposedly erased all the data and file structures on my system but every now and then I keep checking for fixes and playing around with the tablet, today I charged it up again and went into TWRP, on the PC (win 7) ran the cmd "ADB reboot bootloader", for the hell of it I chose the middle option, the android, is said cold booting linux, the chrome asus logo came up with the spinning dot animation and I just waited and then it began updating my app's and my system loaded right up, everything was there. There's no sd-card in the external slot so it's pulling straight from the tablet, wifi connected, all my apps began updating from the marketplace, I can download, TWRP just says the tablet is blank. It seems to have no root access anymore though, hopefully this can be helpful. Also if I reboot it goes right back to TWRP but if I run the reboot bootloader cmd and choose the android it starts right back up without having to update everything again.
pariahcomplex said:
I haven't seen this written anywhere yet but I've found something weird with the TWRP loop, months back I used the asus system wipe and got stuck in the TWRP loop because I supposedly erased all the data and file structures on my system but every now and then I keep checking for fixes and playing around with the tablet, today I charged it up again and went into TWRP, on the PC (win 7) ran the cmd "ADB reboot bootloader", for the hell of it I chose the middle option, the android, is said cold booting linux, the chrome asus logo came up with the spinning dot animation and I just waited and then it began updating my app's and my system loaded right up, everything was there. There's no sd-card in the external slot so it's pulling straight from the tablet, wifi connected, all my apps began updating from the marketplace, I can download, TWRP just says the tablet is blank. It seems to have no root access anymore though, hopefully this can be helpful. Also if I reboot it goes right back to TWRP but if I run the reboot bootloader cmd and choose the android it starts right back up without having to update everything again.
Click to expand...
Click to collapse
so if you can get to bootloader. why dont you fastboot flash the blob file for the latest update? this would install system and new bootloader and stock recovery. from there regaining control of tablet. then just fastboot flash twrp and flash a custom rom....just a thought but if your getting into bootloader you should be able to flash blob.
I tried that right when I saw fast boot coming up, nothing would go through, I did fix it by using the method posted by Buster by using fast boot to systematically erase everything one by one then flash new firmware, just thought this info might be helpful, it's almost like twrp becomes a separate partition when you use asus wipe since everything is still there and bootable
kaos420 said:
so if you can get to bootloader. why dont you fastboot flash the blob file for the latest update? this would install system and new bootloader and stock recovery. from there regaining control of tablet. then just fastboot flash twrp and flash a custom rom....just a thought but if your getting into bootloader you should be able to flash blob.
Click to expand...
Click to collapse
I'm having issues and this won't help me. I flashed the JB version of twrp 2.5 instead of the 4.2 one and am getting a bootloop on the Asus screen. I reflash the update blob and it just doesn't boot
It IS Lupus said:
I'm having issues and this won't help me. I flashed the JB version of twrp 2.5 instead of the 4.2 one and am getting a bootloop on the Asus screen. I reflash the update blob and it just doesn't boot
Click to expand...
Click to collapse
search i have seen a guide for your specific issue on how to correct. it i was under q&a.
kaos420 said:
search i have seen a guide for your specific issue on how to correct. it i was under q&a.
Click to expand...
Click to collapse
I figured it out. I downgraded my bootloader back to 4.1(I know it went because I had the fastboot USB icon back) flashed the correct recovery and wiped everything. My data partition got corrupted. Got back into a working environment and flashed 4.2.1 again, with the proper recovery.
Sent from my HTC6435LVW using xda app-developers app
It IS Lupus said:
I figured it out. I downgraded my bootloader back to 4.1(I know it went because I had the fastboot USB icon back) flashed the correct recovery and wiped everything. My data partition got corrupted. Got back into a working environment and flashed 4.2.1 again, with the proper recovery.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
alternativly this should work as well for latest fw
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
(just for reference)
cheers
-Buster
Buster99 said:
alternativly this should work as well for latest fw
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
(just for reference)
cheers
-Buster
Click to expand...
Click to collapse
This is how I ended up fixing mine, can't thank you enough Buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
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
Hello, i recently installed the new official lollipop 5.0 android, however it was working like crap so i decided to change with custom firmware.
Heres what i did.
Unlock bootloader
install custom recovery
root with super SU
install custom rom.
It worked, and android started up, however, i cant connect to cellular network anymore, i waited like 10 minute to detect it but it wont, then i tried a different rom, didnt help. Did i bricked my phone? Is there anything to do?
Im with Virgin canada
Thanks
Can you access the bootloader? If yes, then you did not brick it. You probably didn't completely wipe the stock ROM before you flashed the custom one. Also, not a good idea to flash SuperSU before flashing your ROM.
Everything is working has usual, except i cant connect to LTE anymore. I flashed TWRP instead of Clockwork recovery, ill try again with this one...
From where you are now with TWRP installed:
1. In TWRP, go to "Wipe" then go into the advanced wipe options and wipe every partition except the internal storage.
2. Flash ROM.
3. Flash Gapps if needed.
Google "APN"
theesotericone said:
Google "APN"
Click to expand...
Click to collapse
From what ive seen, i have to set it up myself?
Also i currently has no ROM installed, and none in my SD card, i tried sideload but it failed, is there a way to transfert the ROM to my memory card in TWRP? If i have to click USB-OTG for it, then nothing happen when i do.
insistents said:
From what ive seen, i have to set it up myself?
Also i currently has no ROM installed, and none in my SD card, i tried sideload but it failed, is there a way to transfert the ROM to my memory card in TWRP? If i have to click USB-OTG for it, then nothing happen when i do.
Click to expand...
Click to collapse
Push the ROM zip file to your phone from within TWRP, don't sideload it. You shouldn't even need to do that though. TWRP now supports MTP so your internal storage should appear when you connect the phone to the PC when you're in TWRP.
So you went from having possible APN issues to completely wiping your device? Slow down before you actually do brick it. Read the stickies. All the info you need is already here.
Brushstroke said:
Push the ROM zip file to your phone from within TWRP, don't sideload it. You shouldn't even need to do that though. TWRP now supports MTP so your internal storage should appear when you connect the phone to the PC when you're in TWRP.
Click to expand...
Click to collapse
-snip
Had to turn off MTP
theesotericone said:
So you went from having possible APN issues to completely wiping your device? Slow down before you actually do brick it. Read the stickies. All the info you need is already here.
Click to expand...
Click to collapse
I followed the stickies, im not sure what i could have missed.
insistents said:
I tried "adb push rom.zip /sdcard/"
but it say
error: device not found
Click to expand...
Click to collapse
Nevermind.
insistents said:
Hello, i recently installed the new official lollipop 5.0 android, however it was working like crap so i decided to change with custom firmware.
Heres what i did.
Unlock bootloader
install custom recovery
root with super SU
install custom rom.
It worked, and android started up, however, i cant connect to cellular network anymore, i waited like 10 minute to detect it but it wont, then i tried a different rom, didnt help. Did i bricked my phone? Is there anything to do?
Im with Virgin canada
Thanks
Click to expand...
Click to collapse
Try wiping your cache in TWRP.
Brushstroke said:
My bad. TWRP, as far as I can tell, only allows sideloading as far as ADB commands are concerned. Can you not mount the SD using the Mount option in TWRP?
Click to expand...
Click to collapse
I managed to push files by disabling MTP
However, im still waiting on that colour dot loading screen...
insistents said:
I managed to push files by disabling MTP
However, im still waiting on that colour dot loading screen...
Click to expand...
Click to collapse
Which screen are you referring to?
Brushstroke said:
Which screen are you referring to?
Click to expand...
Click to collapse
Boot screen, where there are flying colour dot.
By the way, i only have managed to enter TWRP recovery once, for all the other time, there only was the Teamwin picture, then it reboot to android each times...
insistents said:
Boot screen, where there are flying colour dot.
By the way, i have to do "fastboot flash recovery recovery.img" each time if i want to acess TWRP
Otherwise it wont work, when i go to recovery mode, i can see the TeamWin picture appear for a few second, then the phone reboot to android.
Click to expand...
Click to collapse
Well, did you flash a ROM or factory image? Earlier you said there was no ROM installed.
And about that TWRP issue...not too sure. That could be the recovery_from_boot.p file restoring the stock recovery. Are you seeing an android with a red exclamation point?
Brushstroke said:
Well, did you flash a ROM or factory image? Earlier you said there was no ROM installed.
And about that TWRP issue...not too sure. That could be the recovery_from_boot.p file restoring the stock recovery. Are you seeing an android with a red exclamation point?
Click to expand...
Click to collapse
There was none earlier untill i managed to push a rom in the memory card, but now the Rom just wont start, its stuck in the boot screen so i will try a different ROM.
Nope no red exclamation point, when i choose recovery mode, the Google boot screen appear, then the Teamwin logo appear for a few second, then screen goes black and then google logo is back, and finnaly android boot up...
Ah well i think i fixed the recovery, i used an older version and now its starting properly.
insistents said:
There was none earlier untill i managed to push a rom in the memory card, but now the Rom just wont start, its stuck in the boot screen so i will try a different ROM.
Nope no red exclamation point, when i choose recovery mode, the Google boot screen appear, then the Teamwin logo appear for a few second, then screen goes black and then google logo is back, and finnaly android boot up...
Click to expand...
Click to collapse
Which ROM is this? And since you've already wiped the SD card once and the ROM won't boot, why not just flash the factory image so you'll have a clean slate to start with?
Factory image = Official firmware?
okay,
yes another bootloop,
current state: power on device>starts up>starts to "optimize apps"> finishes and wants to boot to system but restarts entire process
Phone is completely stock, locked bootloader, unrooted, cyanogen stock recovery.
I can boot into recovery and fastboot mode just fine
but like i said it was completely stock so i didnt have USB debugging enabled on the phone so i think thats why windows device manager isnt recognising my phone as a adb bridge, and i cant connect to it
i think thats the problem
windows file explorer also isnt showing anything
i tested fastboot and i can command the phone that way but im not sure what to do next
i want to keep my data intact however
is there any possible solution to this?
Yes, start to revovery, then go to advanced and do a factory reset.
After that you must configure you device again, but the data on you internal storage would not be deleted.
Gesendet von meinem A0001 mit Tapatalk
superspletti said:
Yes, start to revovery, then go to advanced and do a factory reset.
After that you must configure you device again, but the data on you internal storage would not be deleted.
Gesendet von meinem A0001 mit Tapatalk
Click to expand...
Click to collapse
Really? My media wouldnt be touched if I did this? What does it do then?
mastersen901 said:
Really? My media wouldnt be touched if I did this? What does it do then?
Click to expand...
Click to collapse
I'm pretty sure factory reset deletes your data. Isn't that what it's supposed to do anyways? Maybe he's thinking of a custom recovery? If you go into factory reset you can wipe your cache without messing with your data.
woodhaus said:
I'm pretty sure factory reset deletes your data. Isn't that what it's supposed to do anyways? Maybe he's thinking of a custom recovery? If you go into factory reset you can wipe your cache without messing with your data.
Click to expand...
Click to collapse
Yeah I already tried that and it had no effect
So was it as i did it yesterday. All my music files, my eBooks, my fotos were not deleted. When you have synchronized your contacts, fotos or whatever
with Google, you will get the data back, when you login. http://androidforums.com/threads/factory-reset-what-is-it-and-why-would-you.646432/
Gesendet von meinem A0001 mit Tapatalk
mastersen901 said:
okay,
yes another bootloop,
current state: power on device>starts up>starts to "optimize apps"> finishes and wants to boot to system but restarts entire process
Phone is completely stock, locked bootloader, unrooted, cyanogen stock recovery.
I can boot into recovery and fastboot mode just fine
but like i said it was completely stock so i didnt have USB debugging enabled on the phone so i think thats why windows device manager isnt recognising my phone as a adb bridge, and i cant connect to it
i think thats the problem
windows file explorer also isnt showing anything
i tested fastboot and i can command the phone that way but im not sure what to do next
i want to keep my data intact however
is there any possible solution to this?
Click to expand...
Click to collapse
Today released factory img
Fastboot instructions here
Section 8
geowolf1000 said:
Today released factory img
Fastboot instructions here
Section 8
Click to expand...
Click to collapse
This wont work as I havent unlocked my bootloader though.
mastersen901 said:
This wont work as I havent unlocked my bootloader though.
Click to expand...
Click to collapse
Sideload flashable signed zip
Download from here
geowolf1000 said:
Sideload flashable signed zip
Download from here
Click to expand...
Click to collapse
Hey, I just tried to sideload that file, It didn't fail but it just abruptly stopped and went to the stock recovery's main menu at like 50%. Is it supposed to say it finished?
The file is official update from cyanogen support page
Sideload is official method from cyanogen and cyanogenmod
woodhaus said:
Hey, I just tried to sideload that file, It didn't fail but it just abruptly stopped and went to the stock recovery's main menu at like 50%. Is it supposed to say it finished?
Click to expand...
Click to collapse
Here
geowolf1000 said:
Here
Click to expand...
Click to collapse
This answers my question--->
"The installer does not necessarily display an "Install complete." message. You can tell the install is complete if there were no fatal error messages and you have regained control over the menu."
woodhaus said:
This answers my question--->
"The installer does not necessarily display an "Install complete." message. You can tell the install is complete if there were no fatal error messages and you have regained control over the menu."
Click to expand...
Click to collapse
Did work? Have able to gain update?
geowolf1000 said:
Did work? Have able to gain update?
Click to expand...
Click to collapse
Currently my phone boots up but I get an error saying com.android.phone & android.process.acore failed and my phone just restarts. So It boots, but I cant use it because the errors constantly pop up..
EDIT:Also, just for some more info, I sideloaded cm 13.1 and that's when I get into the bootloop(optimizing apps/reboot) but then I tried sideloading cm 12.1 which allowed my phone to boot up and I was able to open my lock screen but then I get all those error pop ups, which makes it impossible to click anything. when I click an app it just restarts my phone, so i'm pretty sure it's some sort of incompatibility with cm versions. maybe I should sideload cm 13? maybe It would help to get a link to the correct sideload-able zip of cm 13 and I'll try that.
Cyanogen or cyanogenmod?
Cyanogenmod need specific gapps per version
Cyanogen is preinstalled gapps
Be more specific
Android procces acore can be fix if clear contact data from settings/ apps.
geowolf1000 said:
Cyanogen or cyanogenmod?
Cyanogenmod need specific gapps per version
Cyanogen is preinstalled gapps
Be more specific
Android procces acore can be fix if clear contact data from settings/ apps.
Click to expand...
Click to collapse
Ah well I didn't know there was a difference.. The zip I downloaded was this (http://builds.cyngn.com/cyanogen-os...be76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
cm-12.1-YOG4PAS1N0-bacon-signed.zip - so cm Im guessing is cyanogenmod. So for a cyanogenmod zip I need to sideload a cm12.1 compatible gapps? and as for clearing contact data, I would be able to but the errors kinda prevent me from using my phone at all.
woodhaus said:
Ah well I didn't know there was a difference.. The zip I downloaded was this (http://builds.cyngn.com/cyanogen-os...be76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
cm-12.1-YOG4PAS1N0-bacon-signed.zip - so cm Im guessing is cyanogenmod. So for a cyanogenmod zip I need to sideload a cm12.1 compatible gapps? and as for clearing contact data, I would be able to but the errors kinda prevent me from using my phone at all.
Click to expand...
Click to collapse
Its cyanogen and does not need gapps
Just tap ok when message appear and quick and patient step by step navigate to settings /apps and clear contact data.
geowolf1000 said:
Its cyanogen and does not need gapps
Just tap ok when message appear and quick and patient step by step navigate to settings /apps and clear contact data.
Click to expand...
Click to collapse
Ok so I've been trying to do that, but it's really not possible. The errors pop up endlessly and the phone reboots after 10-15 seconds of turning on.
Hi,
I'm in the same exact situation as the OP except that my phone WAS rooted with TWRP recovery and ADB debugging was enabled before it entered a bootloop. I cannot manually enter TWRP using hardware keys (it just shows a black screen), but I can do it using "fastboot boot recovery.img". I can also obviously enter fastboot mode. I was intitially trying to upgrade my phone to the latest COS 13.1 from COS 12.1 (skipping COS13.0). I was told that the problem might have happened because I allowed TWRP to install SU after flashing COS 13.1, but I don't see how that could have been the cause because I have done it with every update in the past without a problem.
I just remembered that I did a nandroid backup last February so I flashed it and have now been waiting for 3 minutes for my phone to leave the boot screen (Cyanogen letters w/ black background), but it doesn't seem like it's going to leave the screen anytime soon.
Please help.
EDIT: never mind
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.