[SOLVED] How to unbrick SNE-LX1 - No booting - Huawei Mate 20 Lite Questions & Answers

Hello reader and helper,
my smartphone do not show anything. No logo, no bootloop, no recovery, no anything. Only thing I can get is testpoint.
I think the USB settings are set to standard. No manufacturing mode, but I am not sure anymore.
What I had done:
I unlocked bootloader with the HCU clients and a three day subscription. After that, I flashed TWRP 3.2.1-0 from unofficialTWRP (did not found the one here) in "recovery_ramdisk". And at last I tried to install Magisk. While installing Magisk I got following errors:
unable to mount /cust
unable to mount /product
unable to mount /system
unable to mount /vendor
unable to mount /odm
I changed all filesystems to exFAT and back to FAT4, and TWRP were able to mount them. Only /odm not. I could not change it.
At last I tried to update with TWRP. I installed update_sd_base.zip from a newer version of the device and now the device can not start anymore.
Is there a way with an unbrick tool to install a base software or is HCU Client able to unbrick with a subscription?
What did I do wrong? Changing partitions or installing the update?

Update on question:
With the help of DC Phoenix 0.0.0.173 I recovered my smartphone.
In DC Phoenix in the tab "Update Firmware" and the needed Update files for the device and testpoint enabled, I were able to recover the device. I needed a few tries and a timed licence. I am running Android 9.0.1 and flashed TWRP. Now I have the same errors with "unable to mount ..." (all five). I would like to install Magisk.
Help appreciated. But I would mark the question as solved. Device starts again.

If you have flashed the stock firmware and can get back into E-Recovery you should be able to flash the device again with them partitions.
Else your FRP tripped and thats not a pretty one to fix.

Related

Huawei P10 Lite, TWRP Error 9, pls HALP

Hello everyone,
My phone is in what it seems to be erecovery loop, I tried flashing images via fastboot extracted from update.app file, didnt work at all.My phone is unlocked, I flashed twrp again and downloaded latest stockrom version for my country(asked a friend about it since he has the same phone), I put those 3 files on my usb and connected it to my phone.Opened it in twrp, when i try to flash update.zip i get Error 9.I tried pretty much anyting i could find on this forum and other sources from google, nothing rly seems to work and there isnt anything at all for error 9.Do u guys by any chanse know what is the problem here?
device: Huawei P10 Lite WAS-LX1C432B194 (latest version for my country, Serbia, Eu)
phone unlocked, twrp installed, can do fastboot commands
This is what i get when trying to flash that update.zip
Code:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Formatting Cache using make_ext4fs...
Wiping data without wiping /data/media ...
Done.
Updating partition details...
...done
Installing zip file '/usbotg/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
mountencrypt: failed to mount /data: Success
script succeeded:resut was []
check_write_data_to_partition,write data error
[COLOR="Red"]E:unknown command [errno][/COLOR]
update_huawei_pkg_from_ota_zip: update package from
zip failed
[COLOR="red"]Updater process ended with ERROR: 9
Error installing zip file '/usbotg/update.zip'[/COLOR]
Updating partition details...
...done
There is already a thread for this problem: https://forum.xda-developers.com/mate-7/help/softbricked-device-fix-t3159742/page5
LwannaCM said:
There is already a thread for this problem: https://forum.xda-developers.com/mate-7/help/softbricked-device-fix-t3159742/page5
Click to expand...
Click to collapse
I already firgued it out, but tnx for the response.
I bought sd card(didnt have one), did dload method, since normal one approach didnt work i used force update approach(dload moved to sd card, power off, hold vol+ + vol- + power button and it installed) also i needed to flash stock recovery beforehand(so it removes twrp, used fastboot to do it, phone was unlocked, power off connect to PC via usb cable and hold down vol- right away, then flash it through fastboot), it cant do force update with twrp still installed.Once it was done i normally booted to stock rom, phone was no longer unlocked, now i unlocked it flashed twrp and rooted it, everything works just fine.Hope it helps some1 with the same problem.
source: https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 , there is guide thing for both normal and force update
Thank for the help. It gives me a clue but I am still struggling as the force update approach get stuck at 5%. Thanks anyway.

XT1900-7 no permissions in TWRP

Greetings.
could not really find anything within this forum that would describe my problem adequately, so I will just ask here, hoping someone had the same.
I recently received this device (XT1900-7), successfully unlocked bootloader and went on to boot and install TWRP.
Booting it temporarily is childs play, but doing anything else within TWRP seems to be pointless. Flashing the TWRP installer results in a bootloop when trying to access TWRP.
To flash LineageOS 16.0 a persistent installation of TWRP is not required (right?) so I really do not care that much about it failing to install properly, I will be just fine with flashing LineageOS from the temporary TWRP.
Here comes the trouble though. I have not yet tried to wipe anything, as I suspect it of not working properly in my case.
Trying to run a backup, something I always prefer to do before wiping and flashing anything, is not possible due to permissions error - it fails to create the TWRP folder. I am also unable to push anything via adb to /sdcard and the contents of /sdcard are rather confusing. There are folders whose names contain random numbers and letters. Checking inside these folders shows that they seem to have an unlimited amount of subfolders.
Opening a terminal in TWRP (as well as adb shell) throws linker warnings (/system/etc/ld.config.txt seems to be missing for /sbin/toolbox) about it being unable to read said file. It does so with every command I submit to the shell.
When I unmount /data I am able to push to the device (though still not to /sdcard - again missing permissions).
Also when switching to slot B it gives me "Error changing bootloader boot slot to B" with "Failed to mount /vendor (invalid argument)".
Relevant data:
I have not done a firmware update, it is still running on Android 7.1.1 and I do not intend to do an update since the stock rom is to be replaced by LineageOS anyways.
As mentionend: XT1900-7, 64GB mmc, 4GB DRAM and so on...
I am able to push files to /tmp for example which allows me to flash the twrp-installer.
Edit: TWRP version is the latest available (3.3.1-0)
Is there anyone who had similar issues and might provide help?
No need to ELI5, I'm at least experienced in Linux, not that much in Android. Previous phone was a G4 Play which was pretty straightforward (unlock, fastboot flash recovery and flash away whatever I felt like).
If you need any more information I will be happy to provide it.
Thanks in advance to anybody that can give me a hint or clue to solve this.
Well. Nvm. It works flawlessly with twrp-3.2.1-1. Seems to be something with latest version. Thx anyways

The problem with installing the firmware on the Asus me 176cx 8gb KitKat 4.4.2

Help revive my device.
After updating the tablet from the playmarket of the Youtube application, the tablet freezes, after a reboot, it hangs on the Asus logo and a spinning circle. I couldn’t enter the droidboot from the buttons and, following the instructions from the 4pda forum, after downloading the service firmware, unpacked it to drive C into the folder, then went to the firmware folder by pressing shift + the right mouse button opened the command window and launched the
droidboot with the fastboot boot droidboot.img
fastboot continue
commands booted into the droidboot and in the folder with the firmware clicked on the update_image file, the firmware process started which took a very long time about 7 hours, at the end the tablet rebooted but only until the first screen saver. I waited a long time, but it did not boot. I turned it off. After that, by pressing a combination of buttons, I was able to enter the droidboot, the serial number of the tablet was missing, through a dead robot I was able to enter the recovery.
Then, according to another instruction from 4pda, through a temporary twrp, I tried to install the Ul-KO13-WW-3.2.23.182-user firmware, the installation process started, but it did not install, but the serial number returned and the tablet again hung on the Asus logo and a spinning circle.
I checked the
fastboot oem start_partitioning
fastboot flash /tmp/patrition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
commands after each command was OK. So the flash memory of the tablet is working.
After I checked the root, the rights remained. USB debugging in the developer menu was turned on even when the tablet was working. Then I decided to try installing the service firmware 201 again, as I wrote above, and again unsuccessfully, the serial number flashed again. . And again, through a temporary twrp, I began to install 182 firmware.
And the serial number failed, it was not restored, but the recovery now showed that it costs 182 firmware. After that, when checking, I found out that no root su. I got a complete crash. I tried again to install 201 firmware and now it costs WW 3.2.23.201 in recovery.
On the advice of a person from the 4pda forum, I tried to restore images of 201 firmware boot.img fastboot.img recovery.img via twrp v2.8.7.0 from the 4pda forum, but again unsuccessfully. I showed the person who helped me install the firmware images 201 that twrp gave me an installation error, it read:
Updating partition details ...
E: Unable to mount '/ factory'
E: Unable to mount '/ config'
E: Unable to mount '/ data'.
The person who helped me said that there was no markup table, or rather, the system section was written, but could not find the other sections, since he wrote this script for Android 5. And on KitKat version 4.4, he did not test this script. Now I'm desperate, I really need a tablet in working condition. Because I am very poor, and I do not have money to buy another tablet, I have been sick for 5 years. I live on disability benefits, they pay me $ 50 a month and I can’t buy another one. I beg everyone to help with tips and instructions on how to restore tablet firmware. I need a worker. I need your help.
Even when connecting to a laptop on a Windows 7 tablet in twrp 2.8.7.0 mode, the tablet is detected as K013, but it does not see the internal drive and only shows a microSD card, I suggest that this is because the firmware is installed incorrectly and there are no firmware sections? ? If Who knows, you can install any custom firmware that fits on my tablet.
If someone can write me instructions for restoring the firmware. If anyone has encountered a similar problem, give information and instructions for restoring partitions with links from where to download what and step-by-step instructions for restoring.
Sorry text wrote through translator. I hope the problem is described clearly and someone can help me with the firmware.
I thank everyone in advance who will respond and help restore the firmware.
P.S. I decided to try to flash through Intel Flash Tool Lite, I launched service 201 firmware, reached the 57% band and issued FAILED. I turned off the tablet, I decided to try running TWRP, running the script, and now there are only two errors:
E: Unabled to mount / and
E: Unabled to mount / config, and the amount of internal memory Internal Storage (3916MB) !!! And before that, it was zero and in the device k013 on the laptop it shows the storage along with the memory card. Here's an interesting process

[RECOVERY][TWRP 3.3.1][9.0] Galaxy J5 (2017) [26.05.2020]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0 by Blue Dogerino​
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
FEATURES:
built from Pie kernel source
built in full 64bit mode
updated TWRP source to 3.3.1 (9.0 version)
Full F2FS Support
fully compatible with all Oreo and Pie roms
WORKING:
Boots
Backup
Restore
All Wipes
Supports unconditional flashing
File manager
Brightness Slider
Flashing
chmod
MTP
Broken:
Nothing for the moment, but if you notice anything please do let me know
Downloads:
Get IMG
Get TAR
Installation:
1. If you have TWRP already:
Boot into TWRP recovery
Select Install, Install IMG
Select TWRP-3.3.1-j5y17lte-26052020.img
Swipe to flash
Restart your phone to recovery and you have new recovery.
Alternative method
Boot into download mode.
Get ODIN
select AP in Odin and select TWRP-3.3.1-j5y17lte-26052020.tar and click start.
To use stock rom, you need to wipe data partition, otherwise the phone will bootloop.
Kernel Source : https://github.com/Doge-Jxy17lte/kernel-exynos7870
XDA:DevDB Information
[RECOVERY][TWRP 3.3.1][9.0] Galaxy J5 (2017) [26.05.2020] , Tool/Utility for the Samsung Galaxy J5
Contributors
bluedogerino, ananjaser1211, corsicanu
Source Code: https://github.com/bluedogerino/twrp-j5y17lte
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2020-05-26
Created 2020-05-26
Last Updated 2020-05-29
Very good to have an updated version that supposedly takes into account the newer security updates!
Thank you a lot for your efforts!
Any trick needed after downloading from Odin?
RMM-state bypass, no-verity, some cache to wipe?...
Or does it simply need plain Odin download?
I'd like just to know before embarking against Pie security...
Every time I try something, it's popping out a new nightmare...
Some other known problem while then flashing Magisk?
I'm aiming at LOS17.1 and letting Google crap behind me...
Well...
I take the lack of replies as an affirmation that there aren't neither installation problems nor ancillary programs to install.
Let's hope there are no bad surprises, and go on.
:crying:After trying to install this TWRP on Android Pie 9 J530FXXU6CSK9_J530FITV6CSL1_ITV I have to report that it fails.
Install trials report follows.
Installation started on downloading TWRP-3.3.1-j5y17lte-26052020.tar by Odin (Auto-reboot unticked) and then entering into TWRP recovery.
All normal. Having anything to install nor to control, I jumped to reboot session and made a system reboot. That reboot failed into infinite reboot.
I then stopped it and came back to download page from Odin, to control the status of the various flags.
They all were good: Current binary: Custom(0xC), KG State: Checking, FRP LOCK: Off, OEM LOCK: Off, Secure download: enabled, warranty void: 1 (0x0500), AP SW REV: B:6 K:4 S:4.
Restarted and went into TWRP recovery. Mount : Data cannot be mounted, System unmounted (not ticked) and same for cache, EFS, USB OTG. MicroSD mounted (ticked). Tried to mount System (ticked) and rebooted to system. Infinite reboot again.
PWR OFF, then recheck of Odin download page, that remained as before. Reenter in TWRP, check mount: system unticked. Try to format Data (yes), had back the following messages: "Unable to mount '/Data' and unable to find crypto footer Failed to mount '/data' (invalid argument) Unable to recreate /Data/media folder Updating partition details... Failed to mount '/data' (invalid argument)... done. Full SELinux support is present Unable to move to /data/media/TWRP/.twrps. MTP enabled Formatting Data using mk2efs... Done You may need to reboot recovery to be able to reuse /Data again Updating partition details... Done."
PWR OFF, then reboot into TWRP. Now on Mount, Data, Cache, MicroSD are mounted, NOT system. Force system mount.
Reboot to system: infinite loop.
Reboot to Odin screen: same data as before.
Reboot to TWRP: wipe Dalvik, cache, etc...
Force system mount then reboot to system. Infinite loop.
SURRENDER AND REINSTALL PIE FROM ODIN. :crying: :crying:
Edit: After reinstalling Pie from Odin PC file I have discovered that the nasty b...d reverted AGAIN KG STATE TO PRENORMAL. GRRR! I HATE PIE SECURITY!
Alvin50 said:
:crying:After trying to install this TWRP on Android Pie 9 J530FXXU6CSK9_J530FITV6CSL1_ITV I have to report that it fails.
/snip/
Edit: After reinstalling Pie from Odin PC file I have discovered that the nasty b...d reverted AGAIN KG STATE TO PRENORMAL. GRRR! I HATE PIE SECURITY!
Click to expand...
Click to collapse
At last I succeeded in installing this TWRP, but as an upgrade of the former TWRP-3.3.0-j5y17lte-20190417.tar.
I had to before install it with Odin, then followed the procedure indicated at this old post of mine:
https://forum.xda-developers.com/showpost.php?p=80223502&postcount=82
then, from that recovery, installed TWRP-3.3.1-j5y17lte-26052020.img, that I previously loaded into my external SD, selecting to flash recovery.:victory:
I didn't reinstall RMM and no-verity after having them installed with the first TWRP.
At a first sight all appears to be well.:highfive::highfive:
But I stress that it appears to be impossible to directly install it from Odin. I'm presently too stressed to keep up with testing, but it would be interesting re-tarring this image and then re-trying direct install by Odin.:fingers-crossed:
Alvin50 said:
:crying:After trying to install this TWRP on Android Pie 9 J530FXXU6CSK9_J530FITV6CSL1_ITV I have to report that it fails.
Install trials report follows.
Installation started on downloading TWRP-3.3.1-j5y17lte-26052020.tar by Odin (Auto-reboot unticked) and then entering into TWRP recovery.
All normal. Having anything to install nor to control, I jumped to reboot session and made a system reboot. That reboot failed into infinite reboot.
I then stopped it and came back to download page from Odin, to control the status of the various flags.
They all were good: Current binary: Custom(0xC), KG State: Checking, FRP LOCK: Off, OEM LOCK: Off, Secure download: enabled, warranty void: 1 (0x0500), AP SW REV: B:6 K:4 S:4.
Restarted and went into TWRP recovery. Mount : Data cannot be mounted, System unmounted (not ticked) and same for cache, EFS, USB OTG. MicroSD mounted (ticked). Tried to mount System (ticked) and rebooted to system. Infinite reboot again.
PWR OFF, then recheck of Odin download page, that remained as before. Reenter in TWRP, check mount: system unticked. Try to format Data (yes), had back the following messages: "Unable to mount '/Data' and unable to find crypto footer Failed to mount '/data' (invalid argument) Unable to recreate /Data/media folder Updating partition details... Failed to mount '/data' (invalid argument)... done. Full SELinux support is present Unable to move to /data/media/TWRP/.twrps. MTP enabled Formatting Data using mk2efs... Done You may need to reboot recovery to be able to reuse /Data again Updating partition details... Done."
PWR OFF, then reboot into TWRP. Now on Mount, Data, Cache, MicroSD are mounted, NOT system. Force system mount.
Reboot to system: infinite loop.
Reboot to Odin screen: same data as before.
Reboot to TWRP: wipe Dalvik, cache, etc...
Force system mount then reboot to system. Infinite loop.
SURRENDER AND REINSTALL PIE FROM ODIN. :crying: :crying:
Edit: After reinstalling Pie from Odin PC file I have discovered that the nasty b...d reverted AGAIN KG STATE TO PRENORMAL. GRRR! I HATE PIE SECURITY!
Click to expand...
Click to collapse
u need to wipe the data, after installing twrp, as the system is encrypted and twrp doesnt support that.
After wiping the data, the system will boot up fine! :highfive:
bluedogerino said:
u need to wipe the data, after installing twrp, as the system is encrypted and twrp doesnt support that.
After wiping the data, the system will boot up fine! :highfive:
Click to expand...
Click to collapse
I did it in the first trials, and it didn't work, while it worked for the former TWRP version 3.3.0 I then used to update to your 3.3.1. I presently dislike to repeat the trial as it took me a lot of useless time. Maybe I try again in the future.
Anyway thank you for your work again.
Kind regards
Hi,
i installed this recovery image without any problem.
One thing is strange: If i go to reboot and i choose "to system" it wait for a second and before swiping to the right it reboots...
Is that expected?
And the STOCK ROM does not boot, but i think this is related because i did not install Magisk and dm-no-verify, or?
kind regards
jaggedN said:
Hi,
i installed this recovery image without any problem.
One thing is strange: If i go to reboot and i choose "to system" it wait for a second and before swiping to the right it reboots...
Is that expected?
And the STOCK ROM does not boot, but i think this is related because i did not install Magisk and dm-no-verify, or?
kind regards
Click to expand...
Click to collapse
Works fine for me with magisk installed
Hi, noob here.
Is there any way i can just boot and not flash this recovery? I need adb shell once to get some data, but i can't afford to wipe the device..
LE: i have no root, no unlocked bootloader
axross said:
Hi, noob here.
Is there any way i can just boot and not flash this recovery? I need adb shell once to get some data, but i can't afford to wipe the device..
LE: i have no root, no unlocked bootloader
Click to expand...
Click to collapse
What do you mean with "just boot"?
A phone boots up every time it's switched on, if it doesn't boot, it's bricked someway.
Can you please better detail?
Why can't you unlock the bootloader?
Please also tell which model is your phone and with which OS.
Kind regards
Alvin50 said:
What do you mean with "just boot"?
A phone boots up every time it's switched on, if it doesn't boot, it's bricked someway.
Can you please better detail?
Why can't you unlock the bootloader?
Please also tell which model is your phone and with which OS.
Kind regards
Click to expand...
Click to collapse
What I meant to say was if i can use TWRP just once to access adb shell, then somehow revert to stock recovery, because as far as i saw, i cannot flash a custom recovery without unlocking the bootloader and wiping the data, and that's not what i'm aiming for . USB debugging is disabled and i cannot enable it, as the phone is password locked (it belonged to a deceased relative and i tried every possible combination i could think of)
The phone is a Samsung Galaxy j5 2017 duo with android 9.0 (i think)
Sorry for being ambiguous in the previous message and thanks for the reply
axross said:
What I meant to say was if i can use TWRP just once to access adb shell, then somehow revert to stock recovery, because as far as i saw, i cannot flash a custom recovery without unlocking the bootloader and wiping the data, and that's not what i'm aiming for . USB debugging is disabled and i cannot enable it, as the phone is password locked (it belonged to a deceased relative and i tried every possible combination i could think of)
The phone is a Samsung Galaxy j5 2017 duo with android 9.0 (i think)
Sorry for being ambiguous in the previous message and thanks for the reply
Click to expand...
Click to collapse
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
Alvin50 said:
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
Click to expand...
Click to collapse
I mentioned above, the phone is password locked and i don't know the password.
So... No way to activate developer options/usb debugging. It's a challenge i face for some days now
I can't risk flashing TWRP and wiping the data, because i want to recover that data...
axross said:
What I meant to say was if i can use TWRP just once to access adb shell, then somehow revert to stock recovery, because as far as i saw, i cannot flash a custom recovery without unlocking the bootloader and wiping the data, and that's not what i'm aiming for . USB debugging is disabled and i cannot enable it, as the phone is password locked (it belonged to a deceased relative and i tried every possible combination i could think of)
The phone is a Samsung Galaxy j5 2017 duo with android 9.0 (i think)
Sorry for being ambiguous in the previous message and thanks for the reply
Click to expand...
Click to collapse
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
---------- Post added at 02:17 PM ---------- Previous post was at 02:01 PM ----------
axross said:
I mentioned above, the phone is password locked and i don't know the password.
So... No way to activate developer options/usb debugging. It's a challenge i face for some days now
I can't risk flashing TWRP and wiping the data, because i want to recover that data...
Click to expand...
Click to collapse
No, you didn't mention it... That's clearer now.
I faced similar problem some years ago, but my needs were simpler as I only had to unlock a phone I bought,whose old owner made a bad factory reset, forgotting to first delete his Google account. So my need wasn't on saving phone data. I found some help on youtube videos that, installing some apparently harmless software exploited a way to reset this Google account. But It was on Oreo, now Pie is harder to fool. If I well remember it began allowing touch control and then, through it, gaining Internet access, but I cannot imagine a way to overcome the passsword lock. Maybe you are lucky looking on Youtube.
Edit: please look there, maybe you succeed:
https://thedroidguy.com/how-to-unlo...ou-forget-the-pin-pattern-or-password-1092270
Kind regards
Alvin50 said:
You can find the exact version of your OS if you go to settings ->"about phone" and look for "Android version". I'm not quite sure of it, because I presently am not on stock ROM and there are possible differences.
You can use ADB shell independently of TWRP, also from the standard custom recovery, But I cannot figure why you would do this way. If you simply want to see the internal storage of your phone, it's enough to have it connected to your PC via USB, then you'll see its internal and SD storage like they were added disks. If, by other hand, you want to install some program, TWRP is the surest and easiest way. Anyway, also to get control of your USB, you have to enable the developer's options, that can also lead to bootloader unlocking. That can be done looking on system to find "build number" and then tapping ten times over it.
I' ll stay waiting for your reply, to better understand
Kind regards
---------- Post added at 02:17 PM ---------- Previous post was at 02:01 PM ----------
No, you didn't mention it... That's clearer now.
I faced similar problem some years ago, but my needs were simpler as I only had to unlock a phone I bought,whose old owner made a bad factory reset, forgotting to first delete his Google account. So my need wasn't on saving phone data. I found some help on youtube videos that, installing some apparently harmless software exploited a way to reset this Google account. But It was on Oreo, now Pie is harder to fool. If I well remember it began allowing touch control and then, through it, gaining Internet access, but I cannot imagine a way to overcome the passsword lock. Maybe you are lucky looking on Youtube.
Edit: please look there, maybe you succeed:
https://thedroidguy.com/how-to-unlo...ou-forget-the-pin-pattern-or-password-1092270
Kind regards
Click to expand...
Click to collapse
Thanks for the idea, but Android device manager and Samsung find my device were not previously configured for the phone
HELP!!!
Guys my phones stuck in bootloop , after trying to root it .
IT's running on pie ((SM-J530F/DS)
What do i do?
Should i install a stock rom?
And it wont even go into recovery mode!!!
Ps: I still wanna root it
:crying::crying:
Malong24 said:
Guys my phones stuck in bootloop , after trying to root it .
IT's running on pie ((SM-J530F/DS)
What do i do?
Should i install a stock rom?
And it wont even go into recovery mode!!!
Ps: I still wanna root it
:crying::crying:
Click to expand...
Click to collapse
Please detail better...
1) Have you yet installed TWRP? Which version?
2) Can you go to Odin download screen and report the status messages in the first rows of that page?
3) How did you try to have root?
My first suggestion is that you revert to your stock ROM by Odin, and regain your phone control.
Then restart the rooting process, caring of details: "The Devil hiddens himself into details"...
Kind regards
Malong24 said:
Guys my phones stuck in bootloop , after trying to root it .
IT's running on pie ((SM-J530F/DS)
What do i do?
Should i install a stock rom?
And it wont even go into recovery mode!!!
Ps: I still wanna root it
:crying::crying:
Click to expand...
Click to collapse
You should reflash stock using odin, install TWRP again, format data, install a new ROM and root that using magisk.
Hey, I hope this thread is not dead, but I can't get out of the bootloop after flashing TWRP. I install it normally with Odin (as AP), then I immediatly enter recovery and it seems fine. When I try to wipe Data it gives me errors, that i can't wipe, the only option is to format data. After this i can wipe Data, but when rebooting it's stuck in a bootloop. I can still access TWRP and Download mode though. I'm running stock Android Pie, but I'm going to try it with stock 8.1 too.
Spoiler: Error
Code:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage.
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount 'data' (Invalid argument)
unable to wipe /data.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
EDIT: Well I guess I 'fixed' it on my own. I tried what happens if I try to root it with the magisk.zip et voilá it booted just fine

Advanced advice for internal storage recovery after attempted flash to LineageOS 17

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.

Categories

Resources