I was doing some testing of installing and backing up various roms using TWRP. After I'd finished all my tests I got ready to return to OOS.
For whatever reason, I now find myself with the phone showing the OOS boot animation sequence but never completing the boot process.
The phone is unresponsive to the power button (even holding it down for more than one hour) - I can't turn the phone off or reboot into some other mode . It does not connect to the PC at all, even in EDL mode with the vol up+vol dn buttons pressed.
So I'm hoping that it will eventually shut down when the battery runs out and then I may be able to boot up into bootloader or recovery again.
In the mean time, does anybody have any suggestions for getting the phone out of its endless rebooting state?
Well, all is now OK. I let the phone run until the battery was drained.
Then I plugged the battery in and rebooted to bootloader, wiped /data using fastboot -w.
At that point I could have used any number of ways to get my phone back, but I chose to do it as follows:
Next I booted into TWRP, took a backup of EFS to find out where it was expecting to find backups, which was /data/media//TWRP/BACKUPS/<serial.id> and then I pushed a system backup (boot, dtbo, and super) there, restored it and rebooted the system.
Once the system had rebooted (and /data is now properly formatted), I returned to TWRP, pushed my other files and backups, restored my data backup and rebooted back to my working system.
Related
I will try to give a decent amount of detail.
My G-tablet apparently ran out of battery, without me knowing. I tried to boot it up and it booted mostly in to android (enough for me to see battery at 0%) and then died.
I let it charge but next time I booted, though android loaded, none of my apps worked. I was also unable to boot in to recovery by holding the volume down button. As a last desperate attempt I went to Privacy - Wipe Data, which prompted the device to shut down.
When it started back up, I receive the message "Booting recovery kernel image", note WITHOUT holding the button (and without the recovery button held text).
From recovery I do a wipe of data partition and try to boot again. Same message, straight to recovery.
I say ok, I will flash the ROM again (vegantab), so I flash the ROM and reboot. Boot straight to recovery again.
One last try, I go to restore and try to restore a image from a few months ago. Restores successfully BUT, straight to recovery again.
No matter how I try to reboot, on the screen with the birds I get "booting recovery kernel image". It's like it isn't even TRYING to boot off the boot partition, and instead decides to load the recovery kernel no matter what I do.
So basically, I am now stuck in recovery and no amount of flashing / formatting can convince the thing to attempt a normal boot. Ideas?
edit: Fed up and in frustration I decided to format all partitions from recovery, including system and boot. After formatting the boot partition I now get the "Magic Value Mismatch" error message. Googling for solutions has returned around 95 different guides to fixing a gtablet, all with various completely different directions and outdated dead links to files. So if anyone has links to a MODERN guide to recovering through nvflash with files that actually exist, let me know.
Hey go to the gtablet for dummies website and download the nvflash 1.2 branch with clockworkmod. You do know how to nvflash right? Just press down your gtablet power button with volume - at the same time. That will put your gtablet in nvflash mode that is a black screen.
The nvflash you downloaded will have a folder with several files, if you are a windows user just put your tablet in nvflash mode and then Run the batch file located in the nvflash folder. Then wait for the process to finish and if the gtab doesnt reboots after everything is finished just reboot it by yourself
Remember you have to install windows drivers if your gtab is not being recognized.
Sent from my MB865 using xda app-developers app
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
RightHanded said:
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
Click to expand...
Click to collapse
Unfortunately you might be stuck in a catch-22 situation here. In order to access the files you'd need to unlock the bootloader, but in doing so you'd lose those files. Without usb debugging already enabled I can't see a way out of this.
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
EDIT: Managed to fix it eventually through: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 (part 2) writing the command in TWRP.
Phone finally boots normally again.
RightHanded said:
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
Any other way to fix this problem?
Click to expand...
Click to collapse
Exactly what did you flash? Full filename please. No errors occurred?
Heisenberg said:
Exactly what did you flash? Full filename please. No errors occurred?
Click to expand...
Click to collapse
Hopefully the stock cyanogen OS.
First I've tried to flash cyanogenmod 12 through TWRP (file is found here: https://forums.oneplus.net/threads/cm12s-yng1tas17l-installation-guide-review-change-log.304615/)
Afterwards I was still stuck in bootscreen, so I've looked for another solution.
Which made me find this guide: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
After flashing this file (probably the same thing) the problem still remained.
Eventually after multiple wipes/factory resets (which did not solve the problem) I've entered the command in TWRP and after reboot it finally worked again.
So I basically flashed my phone twice, once through TWRPS and the other through the batch file (perhaps ADB?).
Also no errors occured which stopped the flashing and commands. Did have to reinstall TWRP and reboot instantly in it by holding the volume down button multiple times. This doesnt happen anymore though.
Only had to install google apps for CM12 (gapps), for which I used TWRP in recovery mode.
Currently reinstalling most apps on my phone and no problems yet.
I tried booting into recovery today, and my R7 Plus just boots normally. It gives the vibrate indication, and then the OPPO logo flashes on for a split second... but then it gives up booting into recovery, the screen goes black again, and the phone boots normally.
If I hold down volume [-] and power, it keeps flashing the Oppo logo and then black screening every second until I let go of the buttons. It seems to me like it keeps trying to boot into recovery and then something goes wrong. After I let go of the buttons, it boots normally.
Booting to recovery through Flashify didn't work; it gave the same Oppo logo-flash before turning back and booting normally.
For some more background, after rooting my phone, I did some deleting of .com files and other Oppo-associated apps/files; I'm not a fan of ColorOS and any Oppo bloatware, so I probably deleted some pretty important stuff. Actually, I'm pretty sure I deleted something important along the way.
I would like to do a clean install to get all of the key firmware modules/files back, I can't do that without access to recovery. I tried unrooting and installing an official update, but that failed since I can't access recovery. What's more, I can't re-root because, again, recovery isn't available; Oppo Tools isn't working.
If I do a factory reset, does that restore all of the ColorOS data, including restoring deleted OS files, or does it just delete my user data and I still won't be able to boot into recovery? Is there a way to flash a stock ROM without recovery mode being available?
sendraww said:
I tried booting into recovery today, and my R7 Plus just boots normally. It gives the vibrate indication, and then the OPPO logo flashes on for a split second... but then it gives up booting into recovery, the screen goes black again, and the phone boots normally.
If I hold down volume [-] and power, it keeps flashing the Oppo logo and then black screening every second until I let go of the buttons. It seems to me like it keeps trying to boot into recovery and then something goes wrong. After I let go of the buttons, it boots normally.
Booting to recovery through Flashify didn't work; it gave the same Oppo logo-flash before turning back and booting normally.
For some more background, after rooting my phone, I did some deleting of .com files and other Oppo-associated apps/files; I'm not a fan of ColorOS and any Oppo bloatware, so I probably deleted some pretty important stuff. Actually, I'm pretty sure I deleted something important along the way.
I would like to do a clean install to get all of the key firmware modules/files back, I can't do that without access to recovery. I tried unrooting and installing an official update, but that failed since I can't access recovery. What's more, I can't re-root because, again, recovery isn't available; Oppo Tools isn't working.
If I do a factory reset, does that restore all of the ColorOS data, including restoring deleted OS files, or does it just delete my user data and I still won't be able to boot into recovery? Is there a way to flash a stock ROM without recovery mode being available?
Click to expand...
Click to collapse
Hi there, i know its been a long time. But i wanna know, have you solved your problem? If yes, could you please share how to fix it. Because im in the same situation right now.
Thank you.
Hi there, having just the old casual phone crisis. I was running cyanogenmod 12.1 for awhile and decided to finally upgrade to a nougat 7.1 build.
I tried using this one https://forum.xda-developers.com/google-nexus-5/development/rom-dark-rom-t3492150 using adb sideload as I had tried a earlier one and the gapps messed up so I wasn't able to put twrp back on the phone. The rom said it had installed successfully but I wasn't able to sideload gapps, I kept getting an error status 255. I went ahead and just tried to load the rom without gapps and see if I could install it slowly through APKs. I managed to get past the initial android load and the services started up, and it got in an endless crash loop because the phone service wouldn't start. So I went to try and flash another rom and was going to delete the cache. When I went to delete the cache the phone hung for about an hour so I tried to just reset it into recovery mode again.
Now when I hold the power button and volume down key to into fastboot mode I can. I have access to the initial screen with the four options, but when I try to start recovery mode or start the phone my screen goes black, and it'll flash the dead android symbol with the error saying unable to mount cache, it only flashes it for like half a second then goes black and repeats every 10-15 seconds.
I tried holding power down, doing volume up, and letting go to do a hard factory reset but it does nothing. I also can't seem to access the adb sideloading anymore, I'm very scared that it's hard bricked, is there anything I can do at all to fix this.
Flash a new version of the recovery via fastboot. Then do a full wipe. After that install the ROM only! Reboot recovery (not system but recovery) then reflash the ROM (no wipe) and add everything else. Hope this helps you out.
The phone may not boot the ROM without wiping data if installing a 7.1 ROM over a 5.1.1 ROM.
I apologize as I've been out of flashing ROMs for over 4 years now.
I unlocked my OP6 bootloader, added TWRP, the flashed Lineage 11.
One of my apps wont play nice with root so I tried to go back to stock.
I tried to use TWRP 3.5.2_9-0 to restore my TWRP backup I made of the stock ROM after unlocking and obtaining root, it ended in a 'extracttarfork() process ended with error=255' at the point of trying to restore system. I tried it a couple of times only trying to restore system, boot and data.
Now I'm in a jam.
The phone boots up but goes right to 'Qualcomm CrashDump Mode' with error 'Attempted to kill init! exitcode=0x0000000b complete_and_exit'.
If I hold vol down + power it takes me to the TWRP loading screen and gets stuck there.
edit: I can now boot into fastboot by holding power, once booting I let go and hold vol up + vol down at the same time. I can then use my PC from fast boot to boot into TWRP.
Any help with this would be greatly appreciated. I made a mistake somewhere and I'm not sure where.
edit: After following this guide https://www.droidwin.com/restore-oneplus-6-stock-via-fastboot-commands/ I am now at the point where my device is boot looping and if I hold volume down during the loop I get to the OnePlus recovery.
edit last: Finally found MSM worked to get me back to stock. https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
Hopefully if anyone matches the issue I had this post will help. Lots of different guides for MSM, the above link was easy and worked without any special downloads, setups or files.
Glad u got ur phone booted again. Yeah, for me the best way to revert everything back on normal state is just re flash the entirephone with MSM dowload tool.
I hope this could help the others.