In trying to encrypt my phone under one of the latest nightlies of CM13 the encryption process failed but left TWRP trying to unlock a corrupted system partition.
So I can't get into TWRP and my system tries to infinitely load.
Is there a way to fix this soft brick?
Can I just fastboot erase (system, cache, data?) some partitions so they're clean and TWRP tries to start so
I can flash a good rom from my memory card?
And does TWRP actually store anything essential to TWRP on any of those partitions? (system, cache, data?)
And are there any other partitions I need to wipe to ensure a unencrypted system so TWRP finds nothing
exisisting to unlock and just tries to start up looking at a empty system?
Actually format[:[<fs type>][:[<size>]] <partition> is what I'd need to use isn't it?
fastboot format system
fastboot format cache
fastboot format data ?
So yeah i'm a right that this is all i need to do to fix my device is fastboot format the partitions,
or will it make the situation worse?
But at this point without the security of a recovery I really don't want to blind shoot and try and fix without out atleast running it by someone asking if it's a good idea, I'm still a little 'green' with Android.
For all I know TWRP keeps some essential files on atleast one of the major partitions, and
may go into a worse state of I format them to remove the encryption, but right now it seems
like the fix, and i know that doing a full clean format on my device will remove encryption
as I've had my device successfully fullly encrypted many times and this is the first nasty issue
I've run into on doing a total clean upgrade and then encrypt.
Shouldn't have screwed around without it forgetting I need to receive a call on it in the morning. >_>
>_< never mind I can click the cancel button and access TWRP without mounting the partion (hello), well
if anyone would have replied thanks anyway, I figured out the problem myself.
Related
So i became a hacker (Obvoiusly) and ive had some issues but i always find a way to fix them and im glad i became a hacker ! <3 but alas i have problems once more :'/. See i was using cm7 BATF2 Or something along those lines, and ive had multiple problems but kept it due to lazyness of backing up and restoring my phone. but now it seems my phone keeps bootlooping unless i flash a new rom, so i flashed cm9 0.3.1. Sure i lost everything but i need a phone and quickly </3 :/.
But there seems to be a problem.....
Whenever i try to use cwm recovery (Button only 5.0.2.8 i believe) i cant factory restore because it cant reach a certain part of android (If im right its android secure.) and skips the format.
So i have literally no space on my phone.
Can someone help me with this and maybe some other issues??
Thanks in advance
-heyhey24 <3
This may work for you:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
LG Optimus F3 for Virgin Mobile:
I hosed my /data partition.
The fix after much research is to use adb to 'erase' (not format) 'userdata' folder/parition? Reason being is that my f3 can't connect to a PC anymore, some hardware thing or related to this issue perhaps, so I cant run adb on it to fix my /data mount issue I am having from CWM. I can flash a rom but it won't boot because of this.
The fix is in the userdata erase. Can someone make me a .zip that will achieve this userdata erase? The command is fastboot erase userdata. It's messed up a situation yes I know....if my usb wasn't f'ed up I could probably do this myself in a minute.
So to summarize:
My usb to pc doesn't work (it will charge though and it's not a driver thing)
CWM flashes a rom error free.
A reboot after flash goes back into cwm recovery.
Everything mounts fine except /data in CWM recovery.
I can't use fastboot due to my usb to pc issue.
Help?
Flashable zip would be my only hope to easily save this phone.
My theory is that my internal memory "/data?" is corrupted and can't be mounted. My fault I believe.
I look forward to your help.
hi folks,
I wanted to update on lollipop but no success.
I don't know why but my Z2 (locked bootloader, rooted, 4.4.4. custom rom, philzdualrecovery) don't work as it should.
In flashtool I stuck in "reading device information" by flashing a stock rom.
In recovery (TWRP or PhilzTouch) I cannot format all my partitions. System, cache and boot did work but data not!
(I formatted system, cache and boot for preparing for a new rom.)
I see "/data" as an empty partition with 0 MB size. What happened? Entering recovery only works with an insered SD Card. Fastboot mode works also.
I tried to erase partitions but fastboot-cmd said "failed: remote command not allowed" (or something like that).
Have you any idea? Do you need more information?
Thanks alot!
So, I was trying to format my SD Card, partition table & all, since Marshmallow's adoptable storage feature messes up the partition table. Since my SD Card doesn't work in my pc, I have to use dd in recovery. This wasn't a big deal since I've already done this successfully 2 or 3 times already. So, since I knew the path of the SD Card already, I typed "dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=1" . Except, I made a slight mistake & typed /dev/mmcblk0 instead of /dev/mmcblk1.
Thankfully, fastboot still worked, so all I had to do is fastboot flash partition gpt.bin to repartition my phone. Or so I thought. When I type this, it says "(bootloader) Preflash validation failed". I already know from prior experience that this error happens when you try to flash an old version of gpt or bootloader. However, these files are from the latest stock rom version, which is "SURNIA_BOOST_5.1_LPI23.29-18-S.2_cid9_subsidy-DEFAULT_CFC.xml".
So, is there anyway I can fix this, or am i hard bricked? Do I just need a newer firmware?
EDIT: Just found a newer firmware, however it is not for my country or carrier. Nevertheless, I am still downloading it & I'm going to see if it can unbrick it or not.
Update
OK, so flashing the gpt.bin from the newer firmware worked, & I was able to flash TWRP, but now I have a different problem. The recovery can't mount system, cache, or data. Attempting to wipe these does nothing. When I try to format these in fastboot, I get the message "Formatting is not supported for filesystem with type 'raw'.".
What do I do now?
Flash only system pertision then data then boot. Via fastboot with original firmware of ur model no
I fixed it! Turns out constantly formatting & rebooting with TWRP actually worked.
Twrp updated from 3.5 to 3.6. I'm on A19. Rooted with Magisk 24.3. I flashed TWRP 3.6.img with Twrp 3.5. Flash OK, reboot in recovery mode OK. System reboot OK. Reboot in recovery mode to test Ok. Reboot system and there bootlooped with red point and white point turning.
I can reboot in TWRP. Il fastboot boo.img, vbmeta.img. Same pb Bootlooped.
I have a nandroid backup (data/boot/cache/DTBO/NVCFG/NVDATA/NVRAM/Persist/Persist Image/Protect F/protect S/Recovery/VBMeta).
I tried ti restore these partitions without erasing partitions. Restore OK but noway to boot. Bootlooped
I wipe all partitions. Restore without Data partition (with data, I have an error). Same bootlooped
I am trying to restore the data partition only. I have this error "Failed to mount '/data' (Invalid argument)
I have no more idea, I'm a little desperate. No solution ? Return the smartphone for repair?
1) flash stock recovery and stock boot via fastboot
2) flash patched vbmeta via fastboot with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
2) format data via stock recovey
3) let it reboot to system
4) flash twrp via fastboot
5) restore only /data via twrp
6) reboot to system
7) UI will be broken, reboot again to fix it
8) remove any pin / password / pattern form the settings, and redo it.
9) Re flash twrp and magisk to root.
Thank you very much for this procedure Raygen. I was indeed able to recover my phone and restart it but it is very unstable. I had bootloopers again after reinstalling TWRP and Magisk. Now I have a problem with my security code or my fingerprints. Looks like they don't take them into account when I want to hand over a security code. Another problem is the camera no longer works. The app does not start. I tried to install the oneplus camera app loaded on Telegram v 3.422.2 but the installation failed.
A proposal to solve these problems ? Reinstall a partition other than Data that I backed up by Nandroid or is it back to OnePlus?
Try to restore the /persist partition from the twrp backup.
take a read here: https://forum.xda-developers.com/t/...rprint-to-become-completely-disabled.4363067/
Thanks very much. By restoring the "persist" partition, I recovered the camera and the fingerprints function. I hope the bootloops will stop there. Thank you very much, you are my saviour.
My OnePlus Nord 2 Indian version got hard bricked and I can't go in recovery or fastboot mode it is in a bootloop on OnePlus logo .
Any help???