Related
Hi everyone.
Here's my build of TWRP 3.0.3-0 for Huawei P7.
Features:
Supports USB OTG, so you can use USB flash drive as external storage for backups, zip installations.
Added feature to make backup/restore of internal storage.
Added feature to make backup/restore of oeminfo partition. This partition contains info about vendor and current installed version. So in case if you want to rollback to 4.4.2, for example, or revert back your previous vendor version, you can just restore oeminfo from backup with 4.4.2 version or other vendor and flash appropriate firmware without flashing transition package, vendor and without getting "cust fail" error.
Combined with stock EMUI 3.1 recovery. In case of power-on by holding power + vol+ or rebooting into recovery by command or any 3rd party application: will boot in TWRP. In case of local update, OTA-update, factory reset from menu or "force update" (3buttons method): will boot into EMUI recovery. Thus you don't have to flash stock recovery before OTA-update, flashing official firmware or doing factory rest.
Off-mode charger updated from EMUI 3.1 (for 4.4.2)
custom.bin and cust symlinks are saved/restored (if they were exist) in case of Wipe/Format Data. So there is not gonna be "cust" issues after factory reset in TWRP.
Excluded SuperSU from build.
Enabled encrypted data support.
Screen lock by power button replaced with screen off.
Requirements:
Unlocked bootloader
Android 4.4.2 - 5.1.1
Installation:
Reboot in fastboot mode
Flash image via fastboot
Code:
fastboot flash recovery TWRP_P7-3.0.3-0.img
fastboot reboot
From TWRP: Press "Install" and select zip-archive
Notes:
Because internal storage is not a separate block device and just a subfolder of "userdata" partition, before you can make backup/restore of internal storage, first you should do Mount -> Data.
Download: TWRP_P7-3.0.3-0.img
For TWRP: TWRP_P7-3.0.3-0.zip
Previous:
Download: TWRP_P7-3.0.2-0.img
For TWRP: TWRP_P7-3.0.2-0.zip
Download: TWRP_P7-3.0.0-0.img
For TWRP: TWRP_P7-3.0.0-0.zip
Thanks for supportion the P7 devices, greate job
Is it possible, to restore 2.8.7.0-backups?
pokko said:
Is it possible, to restore 2.8.7.0-backups?
Click to expand...
Click to collapse
I can't tell you for sure about backups made by araca's 2.8.7.0 - I don't know his partition layouts and backup naming method, but if you were using my build of 2.8.7.0, then yes, you can.
Anyway, it's better to make a new backup, for any case...
Thanks . works great on my p7 especially the factory reset with cust .
can you explain how i can build similar twrp for the mate S . your help will be much appreciated
Hi !
Whenever I use 3buttons method my phone goes to EMUI recovery ,
Whenever I use 3rd party application my phone goes to TWRP recovery !
There is no update file on my storage so in both cases my phone should go to TWRP recovery ! What is the problem ? Please solve this !
andromodgod said:
can you explain how i can build similar twrp for the mate S . your help will be much appreciated
Click to expand...
Click to collapse
What do you mean by similar?
You'll have to make device tree to build TWRP. Mate S is much different from P7, so I think I couldn't help you with it.
mohammadsaa said:
Hi !
Whenever I use 3buttons method my phone goes to EMUI recovery ,
Whenever I use 3rd party application my phone goes to TWRP recovery !
There is no update file on my storage so in both cases my phone should go to TWRP recovery ! What is the problem ? Please solve this !
Click to expand...
Click to collapse
There is not any problem. 3 buttons method is used for "force update". If you want to boot into TWRP, use "power" + "vol+" instead of 3 buttons. Read the first post attentively!
@Kostyan_nsk_one question, why if internal storage is a subfolder of user data in recovery the size of internal storage partition is bigger of data partition?
complicazio said:
@Kostyan_nsk_one question, why if internal storage is a subfolder of user data in recovery the size of internal storage partition is bigger of data partition?
Click to expand...
Click to collapse
TWRP excludes /data/share folder from backup of /data folder. Thus, if you have a lot of photos, music, etc in your internal storage, its backup size will be greater than size of /data backup.
Kostyan_nsk said:
TWRP excludes /data/share folder from backup of /data folder. Thus, if you have a lot of photos, music, etc in your internal storage, its backup size will be greater than size of /data backup.
Click to expand...
Click to collapse
Well, thus if I want to do a nandroid backup I have to check data and internal storage, not only data partition because of default it's not selected internal memory
complicazio said:
Well, thus if I want to do a nandroid backup I have to check data and internal storage, not only data partition because of default it's not selected internal memory
Click to expand...
Click to collapse
It's not mandatoryly for nandroid backup. Depends on what kind of data you want to save. /data contains user applications and system settings; /data/share (i.e. internal storage) contains your personal data (screenshots, photos, music, videos, etc) if you didn't moved them to sd-card. It's up to you, what to backup and what not.
@Kostyan_nsk I appreciate your work. I have already built TWRP for my Huawei device but I am struggling to fix custom.bin and /data/cust symlink being destroyed after factory reset. I have placed the necessary code in partitions.cpp under Wipe partition block. Can you tell me which method you used to fix this?
@Kostyan_nsk When I do a backup in the internal memory then via es file Explorer goes into TWRP folder in sdcard0 (internal memory) it is empty, and if I go into the folder media / share / 0 / TWRP I find the backup. They are not the same thing? While if I do backup in the external sdcard its all ok.
Sent from my Paris using XDA-Developers mobile app
Hi,, I am new here ... i think this very nice .. do you tell me how is instal for my phone p7?
albelushi7 said:
Hi,, I am new here ... i think this very nice .. do you tell me how is instal for my phone p7?
Click to expand...
Click to collapse
Read first post
RangerP7 said:
Read first post
Click to expand...
Click to collapse
What is the first post?
I mean instal twrp!!
How?
If you mean Buckup I do this ?!!
I'm new don't forget this hhh
Think you
albelushi7 said:
What is the first post?
I mean instal twrp!!
How?
If you mean Buckup I do this ?!!
I'm new don't forget this hhh
Think you
Click to expand...
Click to collapse
First post on first page
Kostyan_nsk said:
Hi everyone.
Here's my build of TWRP 3.0.0-0 for Huawei P7.
Features:
Supports USB OTG, so you can use USB flash drive as external storage for backups, zip installations.
Added feature to make backup/restore of internal storage.
Added feature to make backup/restore of oeminfo partition. This partition contains info about vendor and current installed version. So in case if you want to rollback to 4.4.2, for example, or revert back your previous vendor version, you can just restore oeminfo from backup with 4.4.2 version or other vendor and flash appropriate firmware without flashing transition package, vendor and without getting "cust fail" error.
Combined with stock EMUI 3.1 recovery. In case of power-on by holding power + vol+ or rebooting into recovery by command or any 3rd party application: will boot in TWRP. In case of local update, OTA-update, factory reset from menu or "force update" (3buttons method): will boot into EMUI recovery. Thus you don't have to flash stock recovery before OTA-update, flashing official firmware or doing factory rest.
Off-mode charger updated from EMUI 3.1 (for 4.4.2)
custom.bin and cust symlinks are saved/restored (if they were exist) in case of Wipe/Format Data. So there is not gonna be "cust" issues after factory reset in TWRP.
Excluded SuperSU from build.
Enabled encrypted data support.
Screen lock by power button replaced with screen off.
Requirements:
Unlocked bootloader
Android 4.4.2 - 5.1.1
Installation:
Reboot in fastboot mode
Flash image via fastboot
Code:
fastboot flash recovery TWRP_P7-3.0.0-0.img
fastboot reboot
From TWRP: Press "Install" and select zip-archive
Known issues:
Because internal storage is not a separate block device and just a subfolder of "userdata" partition, before you can make backup/restore of internal storage, first you should do Mount -> Data. Otherwise you will get error, saying that TWRP can't mount "storage". So don't bother if you'll see this error.
Download: TWRP_P7-3.0.0-0.img
For TWRP: TWRP_P7-3.0.0-0.zip
Click to expand...
Click to collapse
Download ADB/FASTBOOT
Download TWRP_P7-3.0.0-0.img
And put it into the ADB / FASTBOOT folder
Install drivers of your phone
Connect your phone to your computer
Enable USB debugging on your phone
Open ADB and type:
"adb devices" (you should see now your device)
"adb reboot bootloader"
Now you should see at the bottom unlocked or locked. That means if your bootloader is unlocked. You need to unlock your bootloader to install a custom recovery.
If you see unlocked...
"fastboot flash recovery TWRP_P7-3.0.0-0.img"
That's it
Reboot your phone.
RangerP7 said:
First post on first page
Download ADB/FASTBOOT
Download TWRP_P7-3.0.0-0.img
And put it into the ADB / FASTBOOT folder
Install drivers of your phone
Connect your phone to your computer
Enable USB debugging on your phone
Open ADB and type:
"adb devices" (you should see now your device)
"adb reboot bootloader"
Now you should see at the bottom unlocked or locked. That means if your bootloader is unlocked. You need to unlock your bootloader to install a custom recovery.
If you see unlocked...
"fastboot flash recovery TWRP_P7-3.0.0-0.img"
That's it
Reboot your phone.
Click to expand...
Click to collapse
There are some nots ==
Where is ADB or link ADB/Fastboot
Where is folder Fastboot
albelushi7 said:
There are some nots ==
Where is ADB or link ADB/Fastboot
Where is folder Fastboot
Click to expand...
Click to collapse
Use the power of Google, maybe the force will be with you and you will find it
And please! inform you about flashing things on your phone. First learn how it work (your phone, bootloader, recovery, system, adb/fastboot) and after that start work...
If you are just flashing random **** on your phone without knowing what your are doing I will promise you, in less then one week you will ask for help because your phone won't start anymore...
RangerP7 said:
Use the power of Google, maybe the force will be with you and you will find it
And please! inform you about flashing things on your phone. First learn how it work (your phone, bootloader, recovery, system, adb/fastboot) and after that start work...
If you are just flashing random **** on your phone without knowing what your are doing I will promise you, in less then one week you will ask for help because your phone won't start anymore...
Click to expand...
Click to collapse
I know that
But This new for me ?
I want install this twerb ,because I think phone be better..
Just Try ?
Think you ?
hi,
I bought a new Huawei P10 lite phone, unlocked the bootloader, installed TWRP and with this I installed SuperSU via microSD card.
Everything worked fine, until now. Now I want to backup my current modified stock ROM, but TWRP failes.
I got the problem very fast: TWRP can read all files and folders on the microSD car, but not in the internal storage folder.
The file structure is like the following:
acct
boot
cache
config
data
...
etc
external_sd <-- the microSD card
mnt
...
sbin
sdcard
storage
...
Click to expand...
Click to collapse
Everything can be read by TWRP, except the sdcard folder.
Here he only shows strange names (crypted I guess):
something like:
2h8P9lGY8I1A884LMsBjaA
2u+nb0LdBNopRSa5LehsvB
75aTrCvYkWG+R+lrcRz6WA
DcwYkwSKokq8Rm5lYc4YYC
...
Click to expand...
Click to collapse
This strange folders occure within TWRP itself and also if I mount the storage to the computer via TWRP.
I also can not modify, delete or add anything in this cryted folder.
So what am I doing wrong? Why is this crypted and can not be read?
During my research I found this post on reddit with the same problem. But the solution is not clear to me and also not working.
Thanks for any help
greetings
Christopher
PS.: Here some specific information about the phone:
brand new Huawei P10 lite
model WAS-LX1A
build nr. WAS-LX1AC432B102
no updates avaible, checked twice
EMUI 5.1 with Android 7.0
TWRP v3.1.0-2 from here (named "TWRP_P10_Lite_Beta.img")
Hey
It's because your files are encrypted due to forceecnryption and dm-varity in the kernel you can try formating the data to see if it removes the encryption from the data.
My infos may not be correct you can read more about dm-varity and forceecnryption in the internet
aburezk said:
Hey
It's because your files are encrypted due to forceecnryption and dm-varity in the kernel you can try formating the data to see if it removes the encryption from the data.
My infos may not be correct you can read more about dm-varity and forceecnryption in the internet
Click to expand...
Click to collapse
Ok, thanks a lot. This was helful so far.
From what I read, I now must flash a new "boot.img" in order to disable force encryption. But where do I get such a file for my Huawei P10 lite (WAS-LX1A)? I did not found one. Maybe the phone is too new? Or am I just blind?
greetings
christopher2007 said:
Ok, thanks a lot. This was helful so far.
From what I read, I now must flash a new "boot.img" in order to disable force encryption. But where do I get such a file for my Huawei P10 lite (WAS-LX1A)? I did not found one. Maybe the phone is too new? Or am I just blind?
greetings
Click to expand...
Click to collapse
you can't find it anywhere
aburezk said:
you can't find it anywhere
Click to expand...
Click to collapse
Ok, so too new ... damn. That is very bad.
christopher2007 said:
Ok, so too new ... damn. That is very bad.
Click to expand...
Click to collapse
I managed to disable force encryption on my device
Download this and flash it
Backup your data and wipe data from twrp
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I tryed no-verity-opt-encrypt-6.0.zip but now do not start anymore... I have restore boot and system but none... what can I do? I think i will sell this p10 lite...
simona70 said:
I tryed no-verity-opt-encrypt-6.0.zip but now do not start anymore... I have restore boot and system but none... what can I do? I think i will sell this p10 lite...
Click to expand...
Click to collapse
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
ChipCollector said:
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
Click to expand...
Click to collapse
I solved using "update_data_full_public.zip" and clearing /data, after restoring previuos boot.img and system.img .
My phone was WAS-LX1AC432B102 4gb EMUI5.1 Android 7.0. I had bricked before and the only way to unbrick was to use "Warsaw-L21_C432B182_EU_SERVICE_androidhost.ru"
I do not trust to install data into a phone i can't backup and restore with TWRP... there is another way to make /data not crypted?
Exist the hope one day TWRP read also crypted /data or it is better search another phone?
ChipCollector said:
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
Click to expand...
Click to collapse
Hey, I am having the exact same problem, my phone is soft bricked after no-verity-opt-encrypt-6.0.zip. (https://forum.xda-developers.com/p10/help/stuck-device-booting-flashing-rom-t3713503).
I know the build of my phone, and I downloaded the update.app and extracted it to boot.img, recovery.img, system.img, but how exactly can I restore it in the fastboot mode. What commands?
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
Anymore I think P10lite is a lost cause. I sell to my mother. I bought a xiaomi redmi note 4 global. Never again a Huawei. What a disappointment.
You'll sale your phone to your? Mother? To your mother?
Anyway the same story is on redmi note and all xiaomi
Phones
All the Chinese are difficult to modify.
I was have all Nexus thru 2011 very easy phones but the Chinese... My...
I have a doubt, I have bundled it when trying to install root on my device and I ended up in bootloop what I did was install a (official) rom which when entering the internal files, the folders were with strange names appear, so you recommend removing the credentials (decrypt), to be able to install root? My Device is Xiaomi mi A2
Bro did you find a solution..I am having same problem help
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
chimeralounge said:
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
Click to expand...
Click to collapse
Legend. This fixed the same issue we were facing on the t510 Samsung tablet. Saved us a lot of trouble. Thanks for this.
memz180 said:
Legend. This fixed the same issue we were facing on the t510 Samsung tablet. Saved us a lot of trouble. Thanks for this.
Click to expand...
Click to collapse
-----------
Cool, glad to help! In fact, this issue happened to me once again a few weeks back, when LegacyOS updated. I had this "f*** here we go again" moment, but before wiping, I decided to use TWRP > Advanced > Fix Content. Not only I got the system working again, but *all my data was intact*. System updates are messing file tables, apparently.
I want to marry TWRP.
chimeralounge said:
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
Click to expand...
Click to collapse
God bless you! i've struggle with this s]+t for hours!
what worked for me is installing siankatabg-twrp , now i can see names fine
after that i changed back to official version (which was missy before) and still fine !!!!!!!!
then installed orange fox (which was missy before) and still fine !!!!!!!!
WTH !!!!!!!!!!!!
so i think best shot (if u dont have siankatabg-twrp) is installing codeworkx (Lineage recovery) make sure all good then go back to ur favorite.
lemme know if its works
Thanks to @seadersn and @SGCMarkus, Markus's new TWRP makes things extremely simple now.
What you need:SGCMarkus's TWRP
fstab.judypn with forceencrypt set to encryptable.
magisk
and the .magisk file
Instructions:
1. Follow the instructions to boot and install TWRP on SGCMarkus's TWRP thread
2. While you're still in TWRP, mount vendor and push the fstab.judypn with:
Code:
adb push path/to/fstab.judypn /vendor/etc
3. Format data via TWRP.
4. Push the .magisk to /data (For dm-verity reasons. It will restore the fstab.judypn with forceencrypt enabled) with:
Code:
adb push path/to/.magisk /data
5. Flash Magisk.
You're done! No bootloops this time. XD
i want to try this at some point. When i did before, the screen was black. Thanks for the guide!
I need to get US pie on my device but will be doing this
i got some issues..
i cant mount system_root and i saw there is no /system_root/system/priv-app folder... so i took modified LGSettings.apk to sd card and i put it to /system/system/priv-app/LGSettings... then i format userdata in fastboot,i got twrp loop.....
dreamss29 said:
i got some issues..
i cant mount system_root and i saw there is no /system_root/system/priv-app folder... so i took modified LGSettings.apk to sd card and i put it to /system/system/priv-app/LGSettings... then i format userdata in fastboot,i got twrp loop.....
Click to expand...
Click to collapse
Flash the magiskpatched boot img included in the files
I just had my bootloader unlocked. I am trying to install TWRP, but if I flash stockpiemagisk.img or TWRP-judypn-2019-07-01.img then use the buttons to choose a factory reset I just get bootloops. I select yes both times, just like normal and it loops until going to a fastboot screen. I can then flash the original magisk_patched.img I got from the guy who unlocked my bl, but no TWRP. Even he wasn't sure why this is happening. Any ideas anyone?
Also, in case its related, I lost download mode and can't get that back even by flashing an original backup of laf_b or the lgup compatible laf. I had download mode and flashed Pie before the bl unlock...
Edit: I got download mode back. Turns out when he was unlocking the bootloader he flashed abl_b incorrectly. Once I flashed it correctly DL mode works... Now for TWRP...
NVM.... found the problem...
I have an issue. After clearing the userdata procedure, this attached images is what I get. It's a reddish boot-up screen. The Active Slot also defaulted to B (as opposed to A). I have a fastboot-loop. I am wondering where I went wrong. I completed a successful procedure on another device hours ago. LGUP does not function as well. The phone defaults to Fastboot.
I am able to get to TWRP but the fastboot-loop has changed. The image attached is what I get. I suppose in my attempt to remedy, the wrong Laf files have been flashed. It's V405UA20a
Hello mister
Actually is it possible to flash this stockpie.img on a V406EBW ?
Regards
Fred
avaie said:
I have an issue. After clearing the userdata procedure, this attached images is what I get. It's a reddish boot-up screen. The Active Slot also defaulted to B (as opposed to A). I have a fastboot-loop. I am wondering where I went wrong. I completed a successful procedure on another device hours ago. LGUP does not function as well. The phone defaults to Fastboot.
Click to expand...
Click to collapse
I have exactly the situation you described (fastboot loop + pink letters screen when I try to get into DL mode). If you've managed to rectify this, can you please give me directions. Thanks.
crubbish said:
I have exactly the situation you described (fastboot loop + pink letters screen when I try to get into DL mode). If you've managed to rectify this, can you please give me directions. Thanks.
Click to expand...
Click to collapse
Hi - I eventually lost root and the system factory-reset after an attempt to boot into TWRP. I have scheduled to have VLAD reflash the entire phone. My bootloader is unlocked though but don't think much can be done. There might be other variables that might be affected.
If there is a guide to using Octoplus, it will be appreciated. It also seems telegram is the new medium for development.
avaie said:
I have scheduled to have VLAD reflash the entire phone. .
Click to expand...
Click to collapse
That's what I plan to do as well. Thanks for responding!
crubbish said:
That's what I plan to do as well. Thanks for responding!
Click to expand...
Click to collapse
All the best.
will try out to follow up this info
When I follow step 3 "Format data via TWRP", at the end of the format it says:
"Updating partition details...
...done
Full SELinux support is present.
WTP Enabled
Formatting Data using mke2fs...
Done.
You may need to reboot recovery to be able to use /
data again.
Updating partition details...
...done
UNABLE TO MOUNT STORAGE, DECRYPTION NEEDED FIRST"
I don't think that's good... Or is it?
Please Clarify/Help
I have managed to get TWRP installed and working but did not notice to do this. I went ahead and used Android already only to find that I need to do this.
I have booted into TWRP but cannot select vendor to mount it. Everything except system and vendor (and USB-OTG because there is not attached) will let me check them. But not vendor.
Do I have to go all the way back and re-install TWRP and to this before I do ANYTHING else? Do I have to do this while I am still in TWRP loaded from the image on my PC?
I realize this will loose all I have done within Android and that is the price I pay for not reading in detail. But I want to make sure this is the last time.
Thanks!
Not What I Expected - Decryption Failed!
I went ahead and re-installed TWRP from fastboot per the Markus thread After rebooting back into TWRP I then followed instructions in the 1st post here.
I could not mount vendor but I saw messages saying it was busy. So I assumed it was not unmounted and went ahead with the push to /vendor/etc. It reported successful from adb. And in TWRP file manager I can see a file named /vendor/etc and in the terminal I can cat its contents which look like what I see on my PC.
I then wiped the /data only using advanced wipe and it used makefs, not format.
I then pushed .magisk to /data and it too reported successful from adb.
I then flashed magisk and that seemed successful as well. Inside to TWRP's file manager, I was able to see the .magisk and various folders under /data. This seemed promising enough.
I finally rebooted to system and got shown what is in the attached screenshot. At that point, I had no option but to agree to the reset. When I touched that button, I was returned to TWRP. So I powered off from TWRP and tried to restart the phone. Once again I get the same decryption unsuccessful.
So I seem to be in a TWRP loop. How to proceed? Thanks
whitedavidp said:
I went ahead and re-installed TWRP from fastboot per the Markus thread After rebooting back into TWRP I then followed instructions in the 1st post here.
I could not mount vendor but I saw messages saying it was busy. So I assumed it was not unmounted and went ahead with the push to /vendor/etc. It reported successful from adb. And in TWRP file manager I can see a file named /vendor/etc and in the terminal I can cat its contents which look like what I see on my PC.
I then wiped the /data only using advanced wipe and it used makefs, not format.
I then pushed .magisk to /data and it too reported successful from adb.
I then flashed magisk and that seemed successful as well. Inside to TWRP's file manager, I was able to see the .magisk and various folders under /data. This seemed promising enough.
I finally rebooted to system and got shown what is in the attached screenshot. At that point, I had no option but to agree to the reset. When I touched that button, I was returned to TWRP. So I powered off from TWRP and tried to restart the phone. Once again I get the same decryption unsuccessful.
So I seem to be in a TWRP loop. How to proceed? Thanks
Click to expand...
Click to collapse
Well, as they say, if at first... I went through the steps here again. I made sure I hit the format button instead of wipe. And I made triple sure that everything was where it seemed to need to be and looked right. When I finally rebooted to system, I am now in Android setup as expected. To see if there is still encryption (ie, TWRP can see and backup /data) remains to be seen. Cheers
whitedavidp said:
Well, as they say, if at first... I went through the steps here again. I made sure I hit the format button instead of wipe. And I made triple sure that everything was where it seemed to need to be and looked right. When I finally rebooted to system, I am now in Android setup as expected. To see if there is still encryption (ie, TWRP can see and backup /data) remains to be seen. Cheers
Click to expand...
Click to collapse
Sadly, once finished with a minimal Android setup I went back into TWRP and /data shows nothing. In backing up, it shows /data as 0 bytes. So I presume this means I am still encrypted. Is there no way out of this hell? Thanks
whitedavidp said:
Sadly, once finished with a minimal Android setup I went back into TWRP and /data shows nothing. In backing up, it shows /data as 0 bytes. So I presume this means I am still encrypted. Is there no way out of this hell? Thanks
Click to expand...
Click to collapse
Here's the thing I would try. Load up LGUP and reload a stock kdz. Make sure that before you begin futzing with the phone, you are booting from Slot A.
Then retrace all the steps carefully. And don't set up anything on the phone until you have reached nirvana (bootloader unlocked, unencrypted, Magisk installed).
You'll get there.
[NG]Owner
Hi everyone. Got a puzzle for you forensic data recovery guys out there. I am a fool having a bad day today. For the first time in 10 years of screwing with Android, I backed up my ROM with twrp and also backed up my sms and calls, but then managed to somehow forget to copy those files off the internal storage before trying to flash my phone to LineageOS and botching the internal storage. Here is what happened.
0) Before state: Rooted (I think) and for sure running OxygenOS 5.0.3, flashed via TWRP. TWRP version 3.2.1-0. 128 GB OnePlus 3T
1) Backed up System, data, etc to backup on internal storage via TWRP. Booted into OS and backed up SMS and calls to .xml file.
2) Wiped data, system, cache and dalvik/art cache.
3) Downloaded LineageOS w/ microG via zip in TWRP and attempted to install. Received error that I needed to update the modem to at least 9.0.3.
4) Mounted storage from TWRP and copied in Stable9.0.3+Firmware+Modem_OnePlus+3T.zip. Ran the install and was successful.
5) Installed lineage-17.1-20200826-microG-oneplus3.zip via TWRP. Left prompt to install TWRP checked and booted into OS.
6) Upon boot, saw the message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt.
7) Rebooted back into TWRP to mount storage. Could not get anything to mount because it would not accept my decrypt passcode.
8) Figured TWRP bug, flashed twrp-3.4.0-0-oneplus3.img via fastboot. Could decrypt now with passcode but all storage read 0MB
9) Flashed modem back to OnePlus3T_5.0.3-25-05-18-FIRMWARE-flashable.zip via adb sideload method which is what I assume I was running before since that was the OS version. Rebooted
10) Booted back into TWRP, discovered I still couldn't see files. Downgraded TWRP back to 3.2.1-0 via fastboot.
11) Unable to decrypt from TWRP or even install zips. No change at any point in the OS. Flashed TWRP back to 3.4.0.0.
12) Ran adb shell twrp decrypt XXXXXX (where XXXXXX is my pin) which gave me this message:
Attempting to decrypt data partition or user data via command line.
(then it returned to shell so I assume it worked)
13) Ran an ADB pull command (adb pull /dev/block/dm-0 backup.img). There is obviously something there because it downloaded 111 GB worth of .img file (which I'm 99% certain was the amount of space I had used on the phone). Tried to open the .img file with multiple EXT4 programs and they all said the file/partition was corrupt.
14) Tried to wipe data via TWRP. Failed to wipe because it couldn't be mounted. Followed this:
https://************/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/
15) Ended up with MTP mount of 101 GB free space. Everything seems to be lost on the phone at present. No programs I use to recover the data off the MTP mount (just doing a raw file scrape) can see it as a OnePlus in Windows.
After finding a better guide on XDA, it sounds like this is a known issue that happens when you go from 5.0.x to 9.x on this phone where your encryption breaks and you lose all files. Unfortunately I saw that about 15 minutes after step 14...
My next thoughts would be to:
a) downgrade everything (ROM, firmware, etc) and then try to push the 111 GB .img file back to the phone via ADB, then flash a stock OnePlus 5.0.3 ROM over it to see if I could get the internal storage to mount again. Don't even need to boot into the OS--just to get the internal storage mounted again through TWRP.
--OR--
b) convert the .img file to a .raw and then possibly a .vhd and use Recuva or something to scan the image of the phone and see if I can find those .xml files and maybe a twrp backup if I'm lucky. Although if the entire .img contents is still encrypted and not actually just a corrupt android filesystem, I think I am hosed on this option.
I would prefer option a) but I didn't know if anyone had any insight on this. I thought maybe there would be a way for me to get into the filesystem via ADB maybe and clear out some botched encryption cache or keystore/etc in order to get it to mount again. I'm also not sure if you're able to downgrade the firmware or modem either from 9 to 5 (even though I never got errors on downgrade). Thoughts? Am I just royally hosed?
Tried option b. Nothing but garbage. I made a backup of the .img file this time... so still would be willing to try option a) unless anyone thinks that this is impossible.
Edit: yep... may be too late... https://forum.xda-developers.com/on...-9-0-3-5-0-8-firmware-barrier-t3941164/page18
To my knowledge the data partitions content is unrecoverable lost after the reboot from 5) to 6). The img contains the messed up (and still encrypted) dm0 container but without the enctyption footer which is "outside" the dm0 container in sda15 (aka userdata) partition. To decrypt the img you are missing the device dependent key (an encrypzed partition can be decrypted only on the device the enctyption has been done on) as well as the encryption footer (which is messed up after the reboot).
Format data (not only wipe!) and start over.
Thanks for the reply. That makes sense and is what I was afraid of.
I wonder if it would be possible to regenerate the crypto footer by doing something like this to get the HMAC keys and then flashing a rom to recreate the cryptofooter and then editing the key values to reflect the old cryptofooter values based on the KeyMaster extraction via this exploit.
http://bits-please.blogspot.com/2016/06/extracting-qualcomms-keymaster-keys.html?m=1
It might depend on how much of the cryptofooter is left and whether or not 5.0.3 is vulnerable to these CVEs...
I’m not sure if I know enough about the KeyMaster structure to know how to rebuild it even if I were able to retrieve the HMAC keys.
I also know TWRP now supports EDL so perhaps there is something with a Qualcomm tool I could yse to assist.
Obviously this would mean security issues for everyone on these older builds if I am able to regenerate the crypto footer.
Are you aware of adb commands or likewise that I could run to survey the KeyMaster damage?
As stated: to my knowledge the data is lost after the first reboot with the 9.0.x bootloader.
If you search the official los thread (don't remember if 17 or 16) you'll find some detaled postings on restoring the keys after updating the bl from 5.0.x to 9.0.x. The user, who has examined that has failed, but perhaps it helps to shine some light on your questions.
I am just new to this flashing custom roms or firmware and twrp also. And dumb enough to not back it up.
I wanted to install arrow os in my phone. When I was about to wipe data, cache and dalvik, I accidentally checked metadata also and wiped. Then problems created more problems.
problems right now:
I cant put a file in my storage
Internal Storage is just blank on my pc
No OS
TWRP on both slots
please help me i really needed help and knowledge about it
I hope the attachment helps
EDIT--
Solutions to my problems:
WHEN you softbrick your phone and you only have fastboot and nothing else
Thanks to this guy..
SOLUTION: download your original firmware but choose the fastboot one and not recovery after download just unzip. Double click flash_all.bat and its back to square one.
WHEN you dont know how to flash or the file you have is .img
SOLUTION: find a guide in xda because apparently you can install a .img file in "fastbootd" mode
the guides here: https://forum.xda-developers.com/t/...sues-all-without-any-custom-recovery.4337099/
COMMENT: not the usual thats what on top of youtube search.
WHEN you see errors in twrp/orangefox recovery you might get panic and search for solution.
COMMENT: try to find and use a solution that doesnt delete something first. In my experience it got bricked even more.
Thanks to the people who commented back on my post and helping me get to know what to do next.
Try putting the stock ROM on a SD card or usb (if you have a dongle).
georg3_ said:
Try putting the stock ROM on a SD card or usb (if you have a dongle).
Click to expand...
Click to collapse
SD card that you put on beside the sim? if yes
Do I download stock ROM in official website? Cus I dont have 1 right now
then flashing it there by using twrp? is that how its gonna run? because i really dont wanna assume and create another problem
Try flashing this stock ROM (global) from a SD card, in TWRP. It's a recovery package, so you can install it as any zip.
Also, can you boot into fastboot/bootloader from TWRP?
Plus, where did you get the ArrowOS image? There are no builds, official or not.
georg3_ said:
Plus, where did you get the ArrowOS image? There are no builds, official or not.
Click to expand...
Click to collapse
I found it here
It is made my myst33d and it is a beta build
im getting a sd card right now to test it out
And yes I still can go to fastboot/bootloader from twrp
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
raikiro1 said:
I cant seem to find my file in twrp... even in file manager
Click to expand...
Click to collapse
Is the twrp detecting your sd card？try click on the Install image and change to install zip
can you sideload?
I can now see it, I think I reflashed twrp, now I can, but I cant install because of failed to mount system_root and I have done change file system of data to Ext4. when it resets it comes back to f2fs
edit: change file system of data to Ext4 failed
edit2: thank you guys really for commenting back and helping me
is no verity affecting it? cus I am not able to install it now
you should format data and put the arrow build in it, maybe it will work
J6idot said:
you should format data and put the arrow build in it, maybe it will work
Click to expand...
Click to collapse
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
raikiro1 said:
I cant seem to find my file in twrp... even in file manager
the file is int .tgz must I change it to .zip?
Click to expand...
Click to collapse
Must change it to zip.
EDIT: Extract the file, there's a zip or img inside.
raikiro1 said:
I have changed the data to Ext4, fomarted, wiped again the data,dalvik and cache
I have a Redmi Note 10S Rosemary from xiaomiupdater but I still cannot install the rom cus there is a error " Error installing zip file /sdcard1/thefile."
I tried to install no verity opt encrypt but failed and says updater process ended with ERROR: 1
Error installing zip file "sdcard1/thefile"
Click to expand...
Click to collapse
Try to sideload it, maybe it'll work.
georg3_ said:
Must change it to zip.
Click to expand...
Click to collapse
Should have said "extract the file, there's a zip or img inside", don't change the file extension.
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
raikiro1 said:
Update: I found the guide how to sideload ... just change the Ext4 to F2fs
[Tutorial] TWRP ADB Sideloading
Alternative solution: OTG usb flash drive - With one of these, you can store a ROM zip safely, and still format ‘userdata’ to f2fs or EXT4. TWRP ADB Sideloading Requirements: Mac | Linux | Windows PC / Laptop and TWRP Custom Recovery Moto G...
forum.xda-developers.com
and I was able to sideload it and then got MIUI finally
what worried me is there were still errors like system_root, vendor and product... and its running fine now I guess but im back on track to make it to arrow OS.... I hope no mistakes this time like deleting metadata.
Thank you all who replied to this post , I really do. Thank you
Click to expand...
Click to collapse
no problem next time installing, stick to sideloading, less room for error
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
A12 shouldn't be a problem.
Probably you should flash another vbmeta.img.
OR
I don't know if there is an .img twrp around, but if there is you can:
Code:
fastboot boot {recovery.img}
and then [Advanced]>[Install Recovery Ramdisk].
raikiro1 said:
I cant seem to install TWRP recovery again it justs bootloop .. I dont know why anybody knows?
Whenever I fastboot boot twrp3.6.1-rosemary it fails, says too many links, and when I fastboot reboot recovery it boot loops
flashboot flash boot twrprosemary says okay in slot A and I even put it to B and flash it there sadly
the problem might be because its A12 ... just an update
Click to expand...
Click to collapse
what vbmeta are you using?