My Nexus 6 was running TWRP 2.8.X.X and on CM13. I decided to flash a different ROM but first, I updated TWRP to 3.0.2.0.
When I did the "Wipe" before flashing the new ROM, TWRP apparently wiped my entire system. Now TRWP is telling me that there is no OS installed???.
I'm going to "Sideload" a ROM so that I may re-flash my phone but my question is that TWRP is telling me that my system is "Read Only". Should I first let TWRP change my system to "Read/Write" or will I be able to flash my ROM and restore my phone if I leave it "Read Only"??
I'm a little confused because TWRP never asked me before about modifying my system. It wasnt until I updated that TWRP asked me this?.
It's not bricked. I wipe my os all the time. You will need to use an otg to flash a rom and you'll be fine. Or you need to use add pull/push to get a rom into the internal storage then flash.
Changing your system to read/write should be no problem. I'm no expert but, I would imagine writing to your system partition requires writing permissions to be enabled.
I "adb sideloaded" a ROM and restored my Nexus 6 but everytime I reboot from recovery, TWRP tell me that there is no "OS installed"???. I'm not going to worry about it since everything is working. Must be a bug that happened when I updated TWRP??
you'll find your answers in the TWRP thread...
Related
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
mobone32 said:
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
Click to expand...
Click to collapse
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
mobone32 said:
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
Click to expand...
Click to collapse
you should be able to install TWRP by using the command, "mfastboot recovery twrp.img"
regarding CM11, I don't think is needed anymore to go from CM10 to CM12. it was at one time, but I believe CM or TWRP made some updates so that step is no longer necessary.
but before we can help you further, let us know what ROM you are on now and what ROM you want to be on next.
also, this thread is very helpful: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Ok I got TWRP on there. Now I would like to get to lolipop 5.1 one way or another. I've always liked CyanogenMod (of course) but want to try CyanHacker. http://forum.xda-developers.com/moto-x/development/rom-cyanhacker-lollipop-ghost-t3033367
Right now I'm on a stock sprint rom I got with kitkat 4.4.4
Here's what I was going to do: (copied from forum)
1. mfastboot flash the latest TWRP if you aren't already at that point. I won't help you on fastboot things as you should already know- look around in the forums for info.
2. BACKUP YOUR STUFF- don't want to lose things without being able to get them back, right?
3. Flash the downloaded CM11 snapshot.
(Heres where I'm stuck. This is where I soft bricked it last night. I tried just now to apply the update using twrp and it just fails. It also fails at rooting my phone.)
4. Let CM11 fully boot and go through the setup screen- just skip everything and get to the homescreen.
5. Reboot into Recovery and wipe EVERYTHING- system, data, dalvik cache, cache, etc.
6. Flash your Lollipop ROM.
7. Flash PA-gapps.
8. Flash SuperSU.
9. Wipe cache/dalvik cache.
10. Reboot.
11. ???
12. Profit.
Thanks for any help!
so firstly, let me make this clear, i had Android 6 stock rom working initially, i installed TWRP and rooted the phone with SU
All was working fine until i decided to try and wip the phone to test either a lineage os build or the new EMUI 5
However after performing factory reset, the /data partition is now broken.
I know i'm not the only one that has encountered this issue, but i would at least like a straight forward answer in order to resolve the problem.
Stock recovery now doesn't seem to be an option as when i send it to the phone, i reboot and TWRP still exists.
i have tried via fastboot and from within TWRP, i still get the /data partition error if trying in TWRP to flash recovery.
surely there is a proper solution for this, as this is a software issue not a hardware issue.
i would appreciate your assistance and can provide whatever required information necessary.
i did not pay $500 for this phone for it to be a useless brick
I noticed something here about modaco-rc3 recovery, which i am downloading to try, if it flashes properly, as i suspect this /data partition issue is preventing much of anything from being modified now.
i look forward to your responses and will reply to this with an update after trying to flash modaco recovery if successful
The data partition of the EMUI roms are different than what for example lineageos needs (I think because of encryption).
You need to flash the stock recovery via fastboot, then wipe and format data from there, then TWRP should be able to mount the partition again. In TWRP you can format the partition again to the format according to what is necessary for the rom you want to install.
christopherpfister said:
You need to flash the stock recovery via fastboot, then wipe and format data from there, then TWRP should be able to mount the partition again. In TWRP you can format the partition again to the format according to what is necessary for the rom you want to install.
Click to expand...
Click to collapse
I am just downloading 4.1 stock rom i found finally on Huawei website after much buggering around last night, clearly it was a long day.
Will get this flashed with the stock recovery that I was able to put back on thanks to SRKTool
Will update again shortly, thank you for the reply.
failed to mount system for rom install
now this is just getting silly...
so i was able to restore stock rom with the dload folder procedure and EMUI recovery restored with SRKTool
successfully then unlocked bootloader, put on twrp-3.0.2-0-eva-modaco-rc3, did the data wipes and tried to install lineage os zip.
(the original problem of going back to stock rom is solved, but this is still ongoing as to now why a custom rom will not load)
now i get the infamous ERROR: 7
after
could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4
mount: failed to mount /dev/block/bootdevice/by-name/system at system: no such file or directory
....this is all seeming far too difficult to install any custom rom on this unit, what is happening?
same issue
I'm having a similar issue, any updates?
this is what i've done.
lenovo k3 note with twrp 2.8.7.2_K3_CUOCO92 and rom K3_LOLLIPOP_5.0_ROW_v1.12
i wanted to install one of the latest nougat rom. so i downloaded a twrp 3.1.1.1 made for the k3 note. i flashed the image from my old twrp and replaced choosing the RECOVERY partition.
Flashed ok, i tested a rom, AospExtended-v4.4-aio_otfp-20170708-1051- i flashed it and it worked.
OK BUT.............. i did not wipe the data partition because i received AN ERROR. the new nougat rom was ok but it was a superdirty flash with all the old apps that were crashing. what to do?
i enter into twrp, i REMEMBER that i had the data partition ENCRYPTED so i format it and after doing this i was able to do every wipe i want, included data.
OH PERFECT...... THIS IS WHAT I THOUGHT. i made a full wipe of the rom wiping 4 thinkg : data , internal storage, cache and dalvik cache.
reboot and BOOM. black screen. i press 3 or times the power button and the creen goes on... i am into twrp. from this moment i never returned to see my SYSTEM!
i tested other roms, same problem. i thought it was a twrp problem.... so i installed from the twrp an IMAGE of other twrp... i tested 2 or 3 other twrps specific for my phone k3 note.
I HAD LITTLE BENEFITS with another one.... just because when i press to reboot into system... the phone reboots into twrp AND I CAN SEE IT because the screen is ON, whilst with the "latest" twrp i found...... despites the flashing procedure was ALL CORRECT without errors, at the reboot i always entered into twrp...... BUT INTO A BLACK SCREEN MODE, like if the screen was on...touch enabled, but OFF backligt, and the only way to revive it it is to press power 2 or 3 times, to see the home of the twrp.
i've also found that on MOUNT.......... i always see SYSTEM unflagged, ok i flag it, reboot into system, actually reboot into twrp and system is UNflagged, i try the same thing ALSO flagging READ ONLY...... , idem reboot, twrp.
SEEMS THAT i cannot boot to system anymore. but..... if the twrp was fault, why for the first time let me flash the phone? i really entered into the nougat rom! i found all my old apps and files, but of course it was a DIRTY FLASH, i just wanted to make some wipes.....re flashi the rom.... but oddly i missed the possibility to return anymore to the system.
what could i do at the moment?
how to flash a original image? how to see if this recovery is ok? i donkt 'know where to find my answers......
ah last thing, while into the recovery i was always able to transfer files from pc to phone, but from minutes i am NO MORE ABLE to see the internal memory of the phone.
my computer does not see anything!!! so i am fukked i think....... i did not make anything different.
i only made a lot of wipes... a lot of flashing a lot of testin into recovery. i was able to see it from my pc and put new files through pc. now NO.
solved. i flashed with flash tools an old original firmware android 5.0, then i flased latest twrp with flashtool.... and then flashed the zip of a custom rom.
BL
if u have backup then restore ur stock version or reeboot??
Hello,
I have always been on root but somehow something changed.
Since I tried to flash the newest stable stock (5.0.1), nothing works anymore.
No matter if I flash dm-verity disabler, supersu or magisk, dm-verity gets triggered everytime and my phone just says "decryption unsuccessfull" and won't boot.
I've tried everything to fix this, including: different versions of supersu/magisk, reflashing TWRP recovery, even going completely back to stock, locking the bootloader and everything.
Also I read somewhere that you can flash dm-verity disabler and wipe data to completely remove the encryption, but TWRP showed an error message, something like "failed to wipe, cannot mount /data".
In the end I got stuck with no ROM and I couldn't even access stock recovery anymore because it had the weird password bug, so I had to use the unbrick tool to get it working again.
Can someone tell me what I'm doing wrong?
I have always been on root since the early Nexus 5 days, but now I feel really stupid because I must be missing something obvious, so thank you in advance for any help.
Cheers
What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?
If by chance you are trying to flash OpenBeta 21, I have yet to avoid my data getting encrpyted when trying to flash. And personally, I must have been doing something incorrect ever since I got the phone, because almost every time I've flashed a stock OxygenOS ROM I have triggered encrpytion. In my situation it never seemed to matter if I flashed Magisk, SuperSU, a custom kernel, or even just a modified boot.img along with the disable encryption file... I don't know the steps you're taking, but what I do is this: once I get the "Encryption Unsuccessful" message when trying to boot, I just reboot to fastboot and type "fastboot format userdata". And since flashing stock OxygenOS usually overwrites TWRP with the stock recovery despite my best efforts to avoid it, I tend to go ahead and flash TWRP while I'm booted into fastboot. After, I boot into TWRP; at which point encryption has been removed, yet the total amount of storage available to me is less than 30GB (I have the 128GB model.) You have to go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data. That restores my device back to 111GB free of 113GB. I then transfer over and flash Magisk and whatever other mods I wanted. After that my device is no longer encrypted and works just how I want it to. Hope that helps with your issue.
What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?
Click to expand...
Click to collapse
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data.
Click to expand...
Click to collapse
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
kaeptn1 said:
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're not using Blu Spark 8.61 TWRP, then I suggest you install it and try again.
If all else fails, do as @lordcheeto03 suggested and format userdata in fastboot - but note that this will completely wipe your data, including internal storage. Then install TWRP, then flash 5.0.1 and anything else you want.
Sent from my OnePlus3T using XDA Labs
kaeptn1 said:
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're getting the encryption unsuccessful error, I don't think you format data in that manner, you gotta use fastboot and fastboot format userdata to remove encryption THEN boot into TWRP to do that.
I tried to boot into recovery to make a backup but TWRP has disappeared - no recovery whatsoever. Phone boots to system only. How can this have happened? I've been using Omni for the past month or so with no problems and updating every Sunday.
To recap, I have not done any modifications since the last opdate.Tried to boot into recovery and it is gone. Since only using Omini ROM I thought it was a ROM issue but no one in the Omni thread as been able to help so posting it here.
I can probably flash it again but am puzzled why is should just vanish.
The recovery might have got updated and the last update has overwritten TWRP, so it may be the cause of disappearance, but I'm not sure. You should've got standard recovery bundled with ROM.
And yes, just flash TWRP and it should work again. No need to flash Magisk or custom kernel, since you're on custom ROM.
Recovery partitions may have been corrupted. Try fastboot erase cache, and then fastboot flash recovery (TWRP). See if it boots into TWRP then.
TRWP installed again
Many thanks to all.
Recovery back! Still don't know why it disappeared.