I just rooted the device only to find that the recovery mode no longer works on this device, I think I may have flashed the recovery partition with a wrong img file and now it boots into fire os just fine, But the recovery mode is no longer working. Any tips would be helpful at this point. I've tried using the backup that I did prior to flashing the recovery, but nothing seems to be working.
MIKE804076 said:
I just rooted the device only to find that the recovery mode no longer works on this device, I think I may have flashed the recovery partition with a wrong img file and now it boots into fire os just fine, But the recovery mode is no longer working. Any tips would be helpful at this point. I've tried using the backup that I did prior to flashing the recovery, but nothing seems to be working.
Click to expand...
Click to collapse
you are going to have to flash back to stock with the latest FireOS or find the same version you are on now and flash that. There's no guarantee that will work. I'm surprised you could even get the device to boot at all. So I'm not sure what you did but you shouldn't have even been able to flash recovery. So please describe the steps you took during this whole process.
Related
First, I searched and read all relevant threads concerning this issue. The five threads that showed up in the search did not help me solve my issue.
So on to my problem. I can no longer flash any rom onto my device. I attempted to flash the first official CM10 nightly (which I recently found out was not flashing properly for others) and had no success. I simply got a black screen and nothing more. I eventually got back into TWRP (v2.2.1.4) to try and Nandroid restore, but I noticed that /data was not formatting and the restore failed. Every time I would slide the bar across to confirm the restore TWRP would reboot itself. I then flashed CWM (v6.0.1.0) and the same problems were there. After that I flashed an earlier version of TWRP and successfully restored the backup. I'm not 100% sure how it was successful. So I decided to try flashing another ROM and no go. Same problems. Anyone have any ideas? When I was using CWM I got the error message below.
Code:
E: unable to locate volume information
E: unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file'
E: unable to format data
I'm running Bugless Beast with Motley #219
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
aznxk3vi17 said:
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What rom did you attempt to flash?
elementur said:
What rom did you attempt to flash?
Click to expand...
Click to collapse
So do I.I attempted to flash the first official CM10 8.18 nightly and had no success. I just got a black screen.Even more I boot into bootloader and choose to boot into recover but just stay at google logo.I try to flash recover once more,but just can't boot into recover!!
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Shano56 said:
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Click to expand...
Click to collapse
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
phiracle said:
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
Click to expand...
Click to collapse
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
android1234567 said:
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
Click to expand...
Click to collapse
Thank You Very Much!!!
I am having much the same problem as the OP. I finally rooted my Nexus 7 using WugFresh's Nexus Root Toolkit. It seemed all went well. I chose to use TWRP in a first attempt to install a ROM (I was on rooted stock), and following the instructions for installing my chosen ROM I went into it to wipe cache, Dalvic Cache and data. Both cache and dalvic cache wiped without issue, but when I attempted to wipe /data TWRP simply reported that it failed. With that failing, I did not attempt to install a rom. I was still able to boot out of recovery, but even with repeated attempts wiping data always failed. Is any one aware of any solution or have any suggestions. Thank you!
Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!
OK I had an issue awhile back where my phone really took a crap. Not sure what happened, it is not rooted. But it would not boot, would just go to a dead android. No recovery, nothing. So 2 days of playing around with different programs, I finally got it to boot normally and all seemed well. Now I got a message for a new update and it reboots and does nothing. If I check for updates it downloads it again and does the same thing.
So I tried to boot to recovery and I don't have a recovery now. I get to the fastboot screen(I think that's what it's called) and select recovery. Just reboots. I connected to my laptop and issued the adb reboot recovery, same thing, just reboots. Adb reboot bootloader works however.
So if I have no recovery, how do I re install the recovery? I'm to the point where I might just buy a new one, as fast charging doesn't even seem to work anymore but I'd rather not, I really like this phone.
Thanks for any help you can give.
I believe if you download the proper firmware for your phone, you should be able to extract the recovery image and flash it through ADB. ( fastboot flash recovery recovery.img). As long as you have Asus drivers and ADB installed, you should be able to. I'm sure this is how I reflashed my recovery after I accidentally wiped it.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Thanks Quicksilver, I'll give that a try. I was a lot more up on all this stuff a few years ago when I used to root every device I got. I've been happy with the stock Zenfone 2 so I haven't messed around with this stuff for a long time!
You're welcome Bluze. I hope this for you.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
That didn't work. It seemed to flash recovery.img ok, but still no recovery mode.
Wow, I don't know what exactly worked but I have a recovery now. I finally just bit the bullet and unlocked the bootloader, then used a tool that supposedly roots and installs Clockworkmod. Well, it didn't work. Sort of. I was able to get to cwm recovery one time before I rebooted but it was all back to "normal" (no recovery and not rooted). Rom Manager would hang when I tried to reboot to recovery. So I downloaded SuperSU and installed it manually. Ta Da! Root! Tried to reboot to recover and dead android. Pressed power and volume up and for the first time, it rebooted to stock recovery! Still no CWM, and I'm not sure it will work on Zenfone 2 but hey, I got my recovery back! Now I won't be able to do OTA upgrades but at least I can do them manually!
Quicksilver, your suggestion should have worked. It didn't, but thanks for the help!
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
almost looks like it can't mount the system
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
I have no idea how it happened but I got my system mounted again that was my problem. I'm back.
thread can be closed
keeganjk said:
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
Click to expand...
Click to collapse
thanks for the reply mate
snipeez1987 said:
thanks for the reply mate
Click to expand...
Click to collapse
yw
snipeez1987 said:
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
Click to expand...
Click to collapse
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
ipredatorv said:
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
Click to expand...
Click to collapse
Awesome. I'll keep that in mind. I'm sure I'll mess it up again lol. Hopefully not though.
Hey, I'm new here when it comes to writing forum posts, so bare with me.
I've had this tablet for a few years now and I had flashed it with one of Magendanz roms (Nexus Stock) and I wanted to change to the LineageOS rom he had. I downloaded the .zip file and copied it to my sdcard and tried to get into TWRP to flash it. I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since. I have tried using Odin to flash the rom that way, but for some reason it'll keep doing a boot loop after it's done flashing and restart. I can try going back to the stock firmware if it's a final option to get this tablet working again, but I would love to see if I can get LineageOS to work.
DengekiMatsuko said:
I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since.
Click to expand...
Click to collapse
I had a similar issue once. It turned out that after flashing, not all the partitions mounted properly.
Are you still using TWRP? Boot to recovery, and go into "Mount". Make sure the system and other partitions are actually ticked. That solved the problem for me, and I was able to successfully boot to the system.
Hopefully your issue is that simple!
I managed to brick my Tab A 10.1 (2019) last year by dirty flashing ROMs I shouldn't have. I properly munted it, I couldn't even get into recovery. But I could still get into download mode with a USB cable plugged in to my laptop (it needed to be plugged in for download mode to come up). I flashed the stock ROM, which made it bootable again, which then allowed me to re-flash TWRP and then Magendanz' LOS18.1 ROM.
If you completely break your tablet, reflashing the latest stock ROM for your region is a great way to get back to a familiar starting point. You can then follow people's guides online to get where you want to be.