have a rooted Honor 8 (FRD-L09).
So, I installed the new Magisk. I have been prompted to reboot.
So, I rebooted, and my phone asked me my password for decrypting the OS. I never encrypted the system. I tried 0000, my pin and others, but nothing did it, so I factory reset my phone.
The system did not load.
I looked up online for custom ROMs to boot, but none of them worked.
And that's my big errir : I wiped /system partition because it was a recurring error.
Now I have a bricked phone, with no OS on it.
What to do ?
Hello,
Did you flash a custom recovery (TWRP)?
What the phone do if you press & keep all buttons ( "Power" , "Vol-" and "Vol+" )?
delete
Update : I reinstalled the TWRP and fixed /system, but HURupdater ignore the update.zip and /data isn't writter (also, every line in TWRP starts with "Unable to mount /data")
Gabmiral said:
Update : I reinstalled the TWRP and fixed /system, but HURupdater ignore the update.zip and /data isn't writter (also, every line in TWRP starts with "Unable to mount /data")
Click to expand...
Click to collapse
Have you format /data partition and reboot ti ricovery?
Related
Hey all. I have a rooted TF700 with CM 10.2 on it. I have encrypted the tablet (via SETTINGS - SECURITY - ENCRYPTION). I'd like to do a "Factory Data Reset" - it's my understanding that this will remove the encryption, along with all my user data. This is what I'd like to do.
However, when I go to SETTINGS - BACKUP & RESET - FACTORY DATA RESET, it doesn't work. It asks me to enter my password, then asks me to 'erase everything', and when I click it, it reboots as if to perform the reset. I get the little android guy after it reboots, then the ASUS screen, then CM boot screen. However, the tablet boots like normal, is still encrypted, and all my user data is still there.
I recently upgraded from CM 10.1 to 10.2 - getting the gapps package to install took several tries for some reason, but eventually it worked. I have clockwork recovery installed, but because the tablet is encrypted I am unable to mount or format the /data partition from clockwork.
Anyone have a clue how I can get the 'Factory data reset' to work, or otherwise decrypt my tablet? Thanks!
Factory reset is done by your recovery. Which recovery (and version) is currently installed? Maybe you need to choose "format data" explicitly in the recovery.
_that said:
Factory reset is done by your recovery. Which recovery (and version) is currently installed? Maybe you need to choose "format data" explicitly in the recovery.
Click to expand...
Click to collapse
I cannot touch (either mount or format) /data from Clockwork recovery because it is encrypted by android. any attempt to do so, and I get an error
"ERROR cannot (mount/format) /data!"
doing the 'Factory Data Reset' from within Android is supposed to decrypt and wipe /data, but that is not working.
I flashed TWRP and got rid of Clockwork recovery - that enabled me to mount /data in recovery (TWRP asks for my password to decrypt /data when TWRP starts), which is something. However, when I go into /data using the terminal I only see the lost+found directory and nothing else?
However, formatting /data from TWRP doesn't work, neither does a reset. They just give me errors.
I then tried abd shell - mke2fs -T ext4 /dev/block/mmcblk0p8
but that gives me a '/dev/block/mmcblk0p8 is apparently in use by the system; will not make a filesystem here!' error, even after unmounting it manually (umount -a)
Next, I tried using TWRP to reinstall CM 10.2. After that, the boot process took 40 minutes or so. Once it came up, there was no user data and cyanogenmod was fresh (yay!) - but the partition is still encrypted - it asks for password during boot, even though the OS has no password lock on it.
In addition, my WIFI is now not working!
anyone have a clue here? I REALLY want to remove the encryption on the /data partition!
I wanted to follow up here with closure. Im not exactly sure WHY what I did worked, but it did, and maybe it can help someone else.
last I left off, I had CM11 installed, but no wifi, and the partition was still encrypted. At this point, I decided to try to downgrade again to CM10.2
Now, when the tablet was booting, it was asking me for my password to decrypt so it can boot. Except now, after loading CM11 and going back to 10.2, the password wasn't working and couldn't boot. I was convinced I was bricked.
I went back into recovery, and reloaded CM11. This time, when it came up asking for my password to decrypt before booting, it worked. So something in CM11 changed the encryption on /data so that CM10.2 couldn't read it anymore.
once I was booted into CM11 (still with no wifi), I went to SETTINGS - BACKUP & RESET - FACTORY DATA RESET again. This time, it worked! Asked for my password, said are you sure, then rebooted. BOOM, /data was no longer encrypted! CM11 came up, and with the fresh /data partition, wifi even worked!
For other reasons (Netflix) Ive since gone back to 10.1, but now /data isn't encrypted, so wiping and flashing is easy and works great now.
It seems there is a bug in CM10.2 (or android) where the FACTORY DATA WIPE doesn't work with encrypted /data partitions, but CM11 was able to do that just fine.
Hi,
I wanted to reset my 510 to a fresh 4.4.4 install. So I decided to "restore to factory settings" within the android system settings menu.
kitkat CM12 4.4.4 by shreps was working fine before, I just wanted to get rid of the data in order to give the tablet away.
now I'm stuck with a soft bricked device, it seems:
- when starting the tablet, the CM screen shows, but freezes after a while
- flashing any CM version in CWM 6..0.5 by shreps shows a "error: can't mount /data"
- wipe cache / data shows the same error
- wipe dalvik cache doesn't seem to respond in any way
- I reflashed CWM 6.0.5 using fastboot flash recovery, but to no success..
what options do I have now? can I format and remount the /data partition via ADB? do I need to go to stock?if, so, how?
Thanks for your ideas!
ok, via
fastboot -w -v
i could reformat the data partition somehow.
I still got an
E:unknown volume for path [/sd-ext]
error, but it continued and works for now.
huedrant said:
ok, via
fastboot -w -v
i could reformat the data partition somehow.
I still got an
E:unknown volume for path [/sd-ext]
error, but it continued and works for now.
Click to expand...
Click to collapse
Glad you dot it going.
I just pulled my 701 out of retirement (broke my Sony z2 screen trying to change my battery) so taking a look in here.
The data format has always been a bit twitchy, but I run the latest version of TWRP for KK. I remember bricking my original Data partition wiping it because some bozo used the wrong partition info making the original recovery for JB. Exchanged the tab.
I recall the bootloader version had to match what version of the ROM you installed (JB, KK, etc), and maybe the recovery also (can't remember). Latest TWRP for KK seems to work for me as I installed Pac Rom before I retired it. TWRP Ver 2.7.1.0
As with the "Path to ext SD", that's always been there if I recall. Just means you have to install a ROM from internal memory. Although my TWRP seems to mount it fine.
But I will say, feels like I've entered the dark ages again.
I searched for an answer and noticed it's a common issue. I am trying to flash a kernel on to my already flashed rom. I was wondering if there is a more current fix. More importantly, how can this be avoided in the future. Thank you guys!
Its caused by a bug/error with either the filesystem or encryption.
Did you wipe data after flashing the new ROM? Data from stock usually doesn't work with custom ROMs.
Do you have a PIN/password on Android?
Are you using the latest build of TWRP?
Press the menu button at the bottom of the screen in TWRP and post what the error message is in the red text.
It's caused by no root access
djhulk2 said:
It's caused by no root access
Click to expand...
Click to collapse
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
KemikalElite said:
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
Click to expand...
Click to collapse
I've debated on doing this. I'm not worried about losing pictures texts etc as they're backed up.
I read that it essentially leaves the device with no OS. If that's wrong please let me know!
I have found that if I choose Slot A and reboot system it reboots me in to TWRP. If I choose Slot B it runs the OS like normal (except I still have issues using Facebook and it's services).
The ROM works and I can perform all the custom mods on it. I just want to flash a kernel and the problem persists. 0 mb in storage.
It's trial and error at this point. Fail fast fail forward. I have another phone I can use but I love the OnePlus. Any help will be appreciated!
https://andi34.github.io/faq/faq_twrp.html
I'm not willing to risk it until I know how to get the custom ROM on to the storage to flash it.
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Never heard of formating data removing the OS, that would be if you wipe the system and normal wipe is like a factory data reset and therefore will not wipe your phone of the OS
djhulk2 said:
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Click to expand...
Click to collapse
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Try this in recovery, sometimes its known to work.
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to EXT2.
Repeat the same process selecting Ext4
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to back to EXT4.
Try formatting data after this.
drey4211 said:
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Click to expand...
Click to collapse
Since you dont care about the data on the phone I would just do 1 of 2 things. 1st I would reflash twrp on to you phone if that doesn't work then I would just grab the fastboot ROM and just flash your phone back to full stock reroot and install twrp from scratch. I would not try to start repairing partitions. I wouldn't want to worry about screwing up the EFS partition
Well in an update, I formatted the
Storage and now I'm stuck in bootloader screen. It's unlocked but I'm having a hard time flashing a ROM through adb.
I use the twrp version 3.3.1-2
Best would be to just use fast command to boot it
But it should be under wipe/format data/then type in yes
That was what I was trying to have you avoid. If your can boot to fastboot download the fastboot ROM I told you to and run the flash-all.bat file. If your on 9.5.8 make sure you use the fastboot ROM of the same version. Do not flash azip of a different version firmware like 9.5.7.
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
I essentially soft bricked my device. Called OnePlus and they got me up and running. That's awesome that they have that service!
Are you removing all security? Pattern, pin and fingerprints? Are you decrypted? Never had an issue with flashing a ROM causing these issues which is why I'm asking. Something you've done at some point is causing this
I'm not sure what that was. Ironically enough I am now stuck in TWRP boot loop. Hopefully I can figure this out otherwise I have to call oneplus again.
I will admit I may not know everything but it's trial and error. I don't have anyone to really teach me this so I try to read the forums and learn. You guys have been great!
ajsmsg78 said:
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
Click to expand...
Click to collapse
I've the same issue.. did you find a fix? So annoying
hey, something similar happened to me and I am already very frustrated, I had done the whole process of installing the havoc os ROM and everything was going well, until when installing the MagisK from TWRP, it remained on the loading screen (a white circle and It started again and it did not start), I went back to TWRP and reinstalled the backup but when the process is going to finish the following appears: "failed to mount '/ product' (structure needs cleaning), it does not allow me to swipe, install, literally nothing process because it tells me that at the end. I need help, I already fixed the mount system but I haven't found anything for this ...
Did you backup that partition too?
Nvm I just remembered.
The /product partition in Android 9 is an extension of the /system partition
Try format it then mount it again then restore the backup.
Kenora_I said:
Nvm I just remembered.
The /product partition in Android 9 is an extension of the /system partition
Try format it then mount it again then restore the backup.
Click to expand...
Click to collapse
I lost the backup and it does not allow me to carry out any process literally, in the end it throws me that error, the only thing I did was format from the pc, reinstall another version of HavocOs and it came out the same, but I connected it to my pc and it showed me the Havoc battery charging animation, but fails to get past samsung home screen, again ...
Hi All,
I'd urgently need confirmation and/or tipp from seasoned "brick recovery artists" ;-)
Key questions:
(a) In the scenario presented below, can I recovery from soft brick without loosing data (incl. encrypted external sdcard)?
(b) If no - is there a way to recover directly from a TWRP backup (to pre-encryption status)?
Thanks a million!
-----the issue------
To dirty flash to my S9+ rooted and encrypted device, I tried to perform a dirty flash. See CustomROM thread here.
How the issue unfolded:
1. downloaded the latest v7.4
2. moved v7.4 install file to external sd
3. booted into twrp and performed system partition backup (system image, system, recovery, boot)
4. initiated via twrp a dirty flash
4.1 received error messager after 1 second: damaged zip file
5. rebooted into sysem - WORKED
5.1 realized my SDcard was not mounted and the system tried to "encrypting sdcard 10%/11%/..."
5.2 shut down system immediately
6. repeated step 5 with same results
7. booted into twrp and tried to restore from backup (system image, system, recovery, boot)
7.1 received error message "extracttarfork() process ended with error=255"
8. rebooted into system and rebooted into twrp
9. performed full restore only "system image"
10. booted into system - same as before, in step 5; immediately shut down
11. tried to boot into twrp without success; bootloader 1 error message: "could not do normal boot. INVALID KERNEL LENGTH"
I am a bit screwed here, i think?
the funny thing is that
(a) a OS boot still required me to enter my encryption pin
(b) the OS itself had no sdcard access/mounting issues apparently, same for TWRP partially. HOWEVER, the TWRP system backup was stored on my external SD card - How was TWRP even able to perform a restore from it, if it could not read /data and the sdcard in the first place?
solved. Please close