I own the Nexus 9 (Wi-fi model) and am running Android 6.0 MRA58N, rooted with the TWRP recovery. I wanted to to update to android 6.0.1 so downloaded the latest factory image (MMB29R) from Google's website. I rebooted to TWRP so I could flash the new image. When I realized that you cannot flash system.img through TWRP I had already flashed the boot.img. I attempted to reboot only to get stuck in a bootloop. "Luckily me" I had taken a backup through TWRP previously (boot, data and system). So I went again in TWRP, factory reset and restored (successfully as per the message) the backup. Now every time I boot I see Google's logo, then the "Your device is corrupt" message, that I'm seeing since I installed TWRP (it doesn't seem to affect anything) and then a blank screen that goes on forever.
I had this backup moved to my hard drive and the moved it back to my device. Tried the "fix permissions" option in TWRP as well. No go.
Any suggestions?
I managed to fix it by installing the system, cache, boot and vendor partitions from the new build and the data partition from my nandroid backup.
same happen to me yesterday..what i did is,reboot into fastboot.and then flash vendor, system, boot, cache and also recovery..i have twrp install,but it show 0mb on internal storage.flash stock recovery fix that problem..and after that i flash twrp,supersu and elementalx again..it fix my problem
Sent from my Nexus 9 using Tapatalk
Related
hi all, my friend got mediapad and he wanted custom rom so I flashed twrp recovery and his tablet became bricked, it shows huawei logo, then white screen and then after few seconds it shuts down, I tried to restore my backup to his tablet (CM10.1) via twrp and then it booted without problems but when I do wipe data/actory reset, the white screen and bootloop appears again, where is the problem? in twrp recovery? should I choose cwm for his device? twrp shows error "E: unknown filesystem datamedia" (also on my device but mine works without problems)
thanks for any help
441Excelsior said:
hi all, my friend got mediapad and he wanted custom rom so I flashed twrp recovery and his tablet became bricked, it shows huawei logo, then white screen and then after few seconds it shuts down, I tried to restore my backup to his tablet (CM10.1) via twrp and then it booted without problems but when I do wipe data/actory reset, the white screen and bootloop appears again, where is the problem? in twrp recovery? should I choose cwm for his device? twrp shows error "E: unknown filesystem datamedia" (also on my device but mine works without problems)
thanks for any help
Click to expand...
Click to collapse
Did you say you did a restore then you wiped data/factory reset?
Try opening twrp wipe data, wipe the system perform factory reset, then installed fresh version of cm10.1
but this happen also with stock recovery and stock rom install (dload folder), it starts installation (green android with gearbox) and after 2 seconds it restarts (and keep looping) it looks like corrupted partitions and it started after twrp flash
maybe you need to enter to fastboot mode and then push stock's ROM one-by-one like ICS beta back to honeycomb
what partitions must I flash ? are their names same as img files in rom's zip?
Hi all,
So I was happily running the 20190722 PE (Pixel Experience) on beryllium-V10.3.6.0.PEJMIXM-9.0-vendor-firmware with DFE and Magisk 19.3 flashed from TWRP 3.3.0. All files from official sources including the Official Telegram.
I come to discover I am 2 updates behind on PE so I created a NANDROID backup of the boot, system, and restore. I then cleared the dav and cache per usual and dirty flashed the ROM.
I then proceed to reboot the phone and it begins to encrypt itself. Given that I am a brilliant engineer, I proceed to interrupt it and restart the phone into TWRP. It loads and prompts a password. I have forgotten to DFE.
At this point I know that I have completely screwed up so, following the ongoing consensus on these forums, I format in TWRP, rebooting and clearing as instructed. I then go to restore the NANDROID. No go, boot loop.
After reading more, conclude that I need to flash the vendor FW and use it to reset/clear the phone and reinstall TWRP via FASTBOOT then flash the NANDROID. Nope, boot loop.
Going farther I discover that I need to flash the NAN on top of it’s working ROM/FW.
I go and flash the previously working ROM AND FW with dfe. To I double check I boot that and it boots properly to Android Setup.
Great! I use TWRP to flash the NANDROID. It boots to a lighted black screen. Pushing power I can get it to come up with a power/reboot/lock down menu that moves around the screen. This will actually restart or turn it off (didn’t touch the last).
I have tried this in various combinations with both my new NAN as well as a known working one.
Any ideas/thoughts/insults/ (I can take it)?
Try flashing 10.3.7.0 and then PE and immediately after DFE. However, I'm not sure it you won't lose everything. When doing your backup from TWRP, choose everything except System & Vendor. These 2 will be covered by System Image & Vendor Image.
HTH
Hello
I was at RUI C07 stock firmware.
I've managed to unlock the bootloader and to install TWRP 3.4.0. Then I've tried to flash derpfest (android 10), LineageOS and RevengeOS.
All of them seems to have flashed successfully, but TWRP always warns that there is no OS installed when I try to reboot. When I do reboot, it tries to load something, fails and goes back to TWRP.
What is the problem? Should I try to flash vbmeta? Where can I find it? I'm completely lost.
Thanks in advance
I've just followed the "unbrick guide" and there was little developement...Now the phone boots to fastboot/bootloader by default. I can boot to recovery if I request it. But if I just turn on the system or if I request system, it stops at the bootloader.
What a roller coaster ride!
What seems to have worked for me was to flash yet another ROM (crDroid). But this time I made sure that I've formatted DATA, and then I've wiped vendor, system, caches, internal disk.
I may have forgotten to format the data partition before, which might have been the cause for so much trouble.
If you are reading this, don't forget to format the data partition before flashing a custom ROM, at east when coming from the stock rom.
Hello. I was using recently official LegionOS. I wanted to try Havoc so i've flashed it using OrangeFox Recovery. The device didn't boot, got stuck on Xiaomi logo, vibrated and rebooted to recovery. I tought it was maybe faulty file so i've flashed other rom that I was using before - Fluid. Same result here, I tried now to restore my backup (all partitions without internal) with EvolutionX. Still nothing, phone has rebooted to recovery and I saw that all files have been encrypted. Now i can't do anything other than full wipe. Is there any option to rescue these files from internal storage? I've tried TWRP but it didn't help.
tvv0rus said:
Hello. I was using recently official LegionOS. I wanted to try Havoc so i've flashed it using OrangeFox Recovery. The device didn't boot, got stuck on Xiaomi logo, vibrated and rebooted to recovery. I tought it was maybe faulty file so i've flashed other rom that I was using before - Fluid. Same result here, I tried now to restore my backup (all partitions without internal) with EvolutionX. Still nothing, phone has rebooted to recovery and I saw that all files have been encrypted. Now i can't do anything other than full wipe. Is there any option to rescue these files from internal storage? I've tried TWRP but it didn't help.
Click to expand...
Click to collapse
format data and flash
So, I can't restore my backup due to the error above. When I restore my backup, I get that error and a reboot loops me straight back into TWRP. You can read all that stuff below if you need the backstory.
(I had Lineage OS 18.1 installed and wanted to restore a backup from two weeks ago. So, I booted into TWRP, did a normal factory reset and restored the Backup of Lineage. However, it put out an error regarding something in root (structure needs cleaning). I tried rebooting into system, but it ended in fastboot mode. So I googled it and one thread said you can solve that by formatting system. "System" is backed up anyway, so I thought there was no harm, wiped it and restored the same backup once again. No error this time.
However, when I rebooted into system, the unlock pattern didn't work any more, even though I never changed it and always use the same one. I had to reboot into recovery, and now the TWRP unlock pattern didn't work either. Had to skip it and did another reset.
Now, every time I restore a backup (and those backups contain basically every partition available) it works, but when I reboot into system it just stops at the boot logo, then reboots into recovery. Basically a boot loop plus. Tried a fresh flash, same loop.
Also, all of my pictures and downloaded files are gone, because it's encrypted. I had to wipe data, which led to the whole encryption issue going away, however, I'm still stuck in that loop.
Does anyone know how to solve this cluster****? How do I get it to boot into system?
Edit: Managed to flash LIneage new after wiping data and system and it actually boots, hallelujah, but when I flash the back up I'm still at square one with the same fail and it fails to boot. )