Hello fellow F3 owners, I need your help
A few days ago, I dropped my phone and broke the screen. I wanted to backup all files to my pc so I connected the phone to my computer, but before I did so, I restarted the phone, I have no idea why I did that. Upon the completion of the restart, I get the message "Wait Until Your Device is Fully Rebooted Before Opening Apps" when I try to open any app whatsoever.
When I open the phone, at the lockscreen, I have a pattern that I successfully insert, and the phone opens. The same pattern in TRWP does not decrypt the data.
Given the fact that it accepts the pattern password, I think that if I had a USB connection I would have managed to recover decrypted content from the internal storage space of the phone. Or is the error I'm getting caused by the fact that the content is now encrypted and the apps can no longer read it?
If so how can I recover all the encryption keys to backup them, and then how can I try to fix this problem? Or if the keys have been altered, can they still be generated again (if the phone is the same, as well as the IMEI or serial number, etc.)?
I understand that if I solve this problem, I will either recover my phone as before or at least I can decrypt and access the data and make a backup.
It is very frustrating to see that the necessary information is still there, but I cannot access it.
"Wait until your device is fully rebooted"
What specifically is showing that message? The OS (MIUI) or what? Is it a notification or a popup?
Modern Android has encrypted /data by default. This is on every phone nowadays.
If TWRP isn't showing your files, despite having entered correctly your password, try OrangeFox Recovery instead: https://orangefox.download/device/alioth
The "recovery.img" inside the ZIP is fastboot bootable. Else, you can flash the ZIP to install OrangeFox Recovery.
Boot into your phone normally and then remove the pin/ pattern to disable secure lock. Now if you boot into TWRP, it won't ask for pin/ pattern.
Sounds like your recovery is built for a different android version. Sometimes android updates make changes to the encryption process - this happened with A12 release, but not A13 - so if your recovery decrypts using the A11 method it will fail even with the correct pass.
motbot said:
When I open the phone, at the lockscreen, I have a pattern that I successfully insert, and the phone opens. The same pattern in TWRP does not decrypt the data.
Click to expand...
Click to collapse
So easy. Just flash TWRP which can decrypt the android version you have.
You should also consider backing up your raw files to a hard drive or PC. Safer than backing it up with TWRP and facing the risk of not being able to recover them. TWRP can mess up sometimes.
laid1995 said:
So easy. Just flash TWRP which can decrypt the android version you have.
You should also consider backing up your raw files to a hard drive or PC. Safer than backing it up with TWRP and facing the risk of not being able to recover them. TWRP can mess up sometimes.
Click to expand...
Click to collapse
Yup I once lost vacation photos & videos, because TWRP copied them, showed no errors, but many of the files were corrupt. The photos had visible glitches and only few frames of my videos were playable by VLC media player.
cyanGalaxy said:
Yup I once lost vacation photos & videos, because TWRP copied them, showed no errors, but many of the files were corrupt. The photos had visible glitches and only few frames of my videos were playable by VLC media player.
Click to expand...
Click to collapse
Exactly. I ceased taking TWRP back ups.
laid1995 said:
So easy. Just flash TWRP which can decrypt the android version you have.
You should also consider backing up your raw files to a hard drive or PC. Safer than backing it up with TWRP and facing the risk of not being able to recover them. TWRP can mess up sometimes.
Click to expand...
Click to collapse
Thanks for the reply, how do I find the twrp that can decrypt the android version I have?
motbot said:
Thanks for the reply, how do I find the twrp that can decrypt the android version I have?
Click to expand...
Click to collapse
I gave you an OrangeFox link, try it.
cyanGalaxy said:
I gave you an OrangeFox link, try it.
Click to expand...
Click to collapse
Thanks, my screen is black now and unresponsive.
My PC Can't detect phone but I cant still control it with scrpy.
Problem is, I can't seem to transfer any files to my phone. Very ood.
This is what the error looks like:
{
"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"
}
What is your ROM?
motbot said:
Thanks for the reply, how do I find the twrp that can decrypt the android version I have?
Click to expand...
Click to collapse
Usually it's noted in the filename like [email protected]_1_A12.zip / [email protected]_0_A11.zip
motbot said:
Thanks, my screen is black now and unresponsive.
My PC Can't detect phone but I cant still control it with scrpy.
Problem is, I can't seem to transfer any files to my phone. Very ood.
This is what the error looks like:
View attachment 5851993
Click to expand...
Click to collapse
That's not Alioth
cyanGalaxy said:
That's not Alioth
Click to expand...
Click to collapse
Its not my device. Just a screenshot of the message I receive.
I will send when I get home exact same message from my device if needed
DarthJabba9 said:
What is your ROM?
Click to expand...
Click to collapse
Hey,
It's the default europe or global miui cant remember. (not xiamiu.eu)
Latest version available on poco F3
Related
I was trying to install Edxposed following a step-by-step video guide to be able to use Mock Mock location. I had various unsuccessful tries with YAHFA, so while it was still downloaded and installed (checked safetynet and it was fine), I tried installing SandHook to see if it worked, but then i noticed SafetyNet had been tripped. I proceeded to uninstall every module i had in hope to fix the issue to no avail. Unfortunately i do not have any screenshots from the installation errors or before the safetynet triggered. I have the latest Magisk and twrp installed. I don't have any way of making a full system backup, so preferentially a solution that doesn't format my data, but if it's unavoidable i can do it.
Device: Oneplus 5T
Os: 9.0.10
Android 9
Model: ONEPLUS A5010
{
"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"
}
@Oneplus 5T guy
If phone's boot-loader is unlocked:
By means of ADB pull phone's /data partition to PC, boot phone in boot-loader mode, then by means of FASTBOOT re-flash Stock ROM and finally by means of ADB push saved /data partition back to phone.
jwoegerbauer said:
@Oneplus 5T guy
If phone's boot-loader is unlocked:
By means of ADB pull phone's /data partition to PC, boot phone in boot-loader mode, then by means of FASTBOOT re-flash Stock ROM and finally by means of ADB push saved /data partition back to phone.
Click to expand...
Click to collapse
sorry, im kind of dumb to all of this, i usually just install Magisk with no problems and thats the end, but how could i see the /data partition on my pc? i can only see it in a rooted file explorer on the device.. And whatdo you mean with "ADB pull" ?
re-flash Stock ROM
Click to expand...
Click to collapse
Should i have an image for it or do i download it? (i can search for it if necessary)
Oneplus 5T guy said:
sorry, im kind of dumb to all of this, i usually just install Magisk with no problems and thats the end, but how could i see the /data partition on my pc? i can only see it in a rooted file explorer on the device.. And what do you mean with "ADB pull" ?
Should i have an image for it or do i download it? (i can search for it if necessary)
Click to expand...
Click to collapse
After some extensive searching for what to do, I have downloaded a clean installation of the OS, but I currently am having issues with reinstalling Magisk in the new updated TWRP 3.4. It is important to note that apparently SafetyNet is partially reverted to its original state, only leaving "ctsProfile: false" and "basicIntegrity: true", which hopefully means with the MagiskHide feature, should become all true. If anyone has any insight or possibly a fix for it, it would be much appreciated.
Oneplus 5T guy said:
I was trying to install Edxposed following a step-by-step video guide to be able to use Mock Mock location. I had various unsuccessful tries with YAHFA, so while it was still downloaded and installed (checked safetynet and it was fine), I tried installing SandHook to see if it worked, but then i noticed SafetyNet had been tripped. I proceeded to uninstall every module i had in hope to fix the issue to no avail. Unfortunately i do not have any screenshots from the installation errors or before the safetynet triggered. I have the latest Magisk and twrp installed. I don't have any way of making a full system backup, so preferentially a solution that doesn't format my data, but if it's unavoidable i can do it.
Device: Oneplus 5T
Os: 9.0.10
Android 9
Model: ONEPLUS A5010
Click to expand...
Click to collapse
you can actually erase google play store data and reboot, it helps.
darrenliew96 said:
you can actually erase google play store data and reboot, it helps.
Click to expand...
Click to collapse
i had tried that and it did not work, to fix the problem i ended up having to delete all my data, since every time i restored it, the safety net tripped again. I simply deleted everything including the OS then made a clean install of everything, including TWRP Magisk and the OS. Reinstalling TWRP probably wasnt really necessary, but since i did it all in one go, i can't say for sure. The phone is working fine now, but the safetynet is partially triggered (ctsProfile: False), which did not block me from using any apps whatsoever. Reinstalling Magisk and using HideMagisk fixed it and it is back to True.
Hello, the error described in the title appeared when i tried to dirty flash the Miui 13 update european version for the Poco F3 on top of Miui 12.5.7. Before flashing the rom i forgot to mount some partitions, including the cited ones, giving me the error. Now i can't mount the required partitions, can't flash the old system nor the newer and TWRP says there isn't an OS installed, as such it goes into a bootloop.
Does someone know what to do?
I tried using the MiFlash tool 2020.3.14.0 to flash the fastboot rom versionof Miui 12.5.7 but it outputs to "The name of the directory is not valid"
Pillow fan said:
Hello, the error described in the title appeared when i tried to dirty flash the Miui 13 update european version for the Poco F3 on top of Miui 12.5.7. Before flashing the rom i forgot to mount some partitions, including the cited ones, giving me the error. Now i can't mount the required partitions, can't flash the old system nor the newer and TWRP says there isn't an OS installed, as such it goes into a bootloop.
Does someone know what to do?
I tried using the MiFlash tool 2020.3.14.0 to flash the fastboot rom versionof Miui 12.5.7 but it outputs to "The name of the directory is not valid"
Click to expand...
Click to collapse
No doubt you have, but just to check... you have extracted to .tgz file to reveal a .tar, which also needs extracting (i use 7zip) until you have a folder that contains the images folder etc etc.
Also, it could help having Mi Flash and the above folder containing the images in the root of C drive, rather than deep in the drive with a long title - eg D:\ANDROID\Xiaomi\alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global
EDIT: oh and be sure to uncheck the flash all and lock option in MiFlash (bottom right corner), or your bootloader will be locked after flashing...
reg66 said:
No doubt you have, but just to check... you have extracted to .tgz file to reveal a .tar, which also needs extracting (i use 7zip) until you have a folder that contains the images folder etc etc.
Also, it could help having Mi Flash and the above folder containing the images in the root of C drive, rather than deep in the drive with a long title - eg D:\ANDROID\Xiaomi\alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global
EDIT: oh and be sure to uncheck the flash all and lock option in MiFlash (bottom right corner), or your bootloader will be locked after flashing...
Click to expand...
Click to collapse
I just controlled and it seems what i did while trying to flash the fastboot rom is completely wrong since i tried to flash the recovery version. I have downloaded the fastboot rom now but i will have to try to install it tomorrow
The rom was flashed succesfully this time but it still goes into the mi recovery when trying to boot. i flashed twrp to see if i could flash the rom from there and now all partitions can be mounted except for /data. When trying to decrypt it using the pin passcode it says Password Failed. is it because i also had the fingerprint and face unlock? When i still couldn't mount the other partitions I always used the pin passcode to decrypt storage. Has the passcode been changed when flashing with the mi flash tool? I don't have a recent system and data backup nor a backup of the internal storage so this issue is devastating to me, i want to save my data at all costs
EDIT: I tried reflashing twrp from fastboot and now I also can't mount the /cust partition with error "Structure needs Cleaning"
Perhaps someone else may offer some better advice, but as far as I can tell your original system is gone. Once you accept this sad fact, you need to flash fastboot rom using miflash choosing the option 'clean all' (NOT CLEAN ALL AND LOCK) to flash the system clean again, after flashing you can expect an error that miflash couldn't lock the device, this is usual. then your device will restart and take quite a few minutes to boot again. don't bother to flash twrp again yet, just the system running first
reg66 said:
Perhaps someone else may offer some better advice, but as far as I can tell your original system is gone. Once you accept this sad fact, you need to flash fastboot rom using miflash choosing the option 'clean all' (NOT CLEAN ALL AND LOCK) to flash the system clean again, after flashing you can expect an error that miflash couldn't lock the device, this is usual. then your device will restart and take quite a few minutes to boot again. don't bother to flash twrp again yet, just the system running first
Click to expand...
Click to collapse
So i have to accept that all my data is gone? No chances of decrypting the data partition? I'll wait and see if someone has something that could work, if nothing else does i guess i'll have to accept the reality. Thank you anyway
I experienced pretty much the same thing as you in the past (i.e. 'failed to mount' and 'no OS installed' errors); unfortunately, the internal storage is most likely wiped. Happy to be corrected for your sake, but I am in agreeance with @reg66.
EDIT: formatting
Sauceunny said:
I experienced pretty much the same thing as you in the past (i.e. 'failed to mount' and 'no OS installed' errors); unfortunately, the internal storage is most likely wiped. Happy to be corrected for your sake, but I am in agreeance with @reg66.
EDIT: formatting
Click to expand...
Click to collapse
TWRP doesn't display the "OS not installed error" and before flashing the fastboot rom version the data partition could be decrypted normally with the lockscreen passcode. Does this mean that Mi Flash encrypted the data partition with a different key?
Thank you to @reg66 and @Sauceunny , I have decide to wipe the memory of the phone as i have deemed it to be too much work to save some chats and images while the most important files are stored as a backup. I will have to plan the next update or changing rom more thorougly next time.
I have the same problem with my S21 ultra
Error on product, vendor and ODM
So i can't install stock ROM because of this error.
Doesnl anyone have an idea?
{
"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"
}
i cant mount system
i use poco f3
cant someone help me for fixed
how tp fixed..
please help
I'm facing the same errors except "Odm" I don't know what to do I tried to flash pixel experience rom in my mom's redmi note 10 using "twrp" it's just just in it. Please help me out
Download fastboot rom, use miflash to flash it (select clean all without lock) and dont play with mom's phone again. Watch a miflash tutorial on youtube if you're new to this.
hello my name is petrus and i have a lg g8 LMG820M ATT with unlocked bootloader, i installed a custom rom ArrowOS 12.1 that worked perfectly, however i went to root with qfil and accidentally ended up replacing boot_b.bin by boot_a.bin , now the phone is stuck on fast boot screen
it already starts directly in fastboot and the text "ACTICE A/B slot - _a" no longer appears on the fastboot screen, there was no backup of boot_b.bin so I don't know how to solve it
Is there anything I can do to get it back? Or did he become a piece of garbage?
{
"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"
}
vini14zimm said:
hello my name is petrus and i have a lg g8 LMG820M ATT with unlocked bootloader, i installed a custom rom ArrowOS 12.1 that worked perfectly, however i went to root with qfil and accidentally ended up replacing boot_b.bin by boot_a.bin , now the phone is stuck on fast boot screen
it already starts directly in fastboot and the text "ACTICE A/B slot - _a" no longer appears on the fastboot screen, there was no backup of boot_b.bin so I don't know how to solve it
Is there anything I can do to get it back? Or did he become a piece of garbage?
View attachment 5656703
Click to expand...
Click to collapse
No, not a piece of garbage lol. Given the tools available for the G8; qfil, the programmers firehose, engineering abl, it's almost impossible to brick the device.
So, lesson learned; always make a backup. It sounds like you copied the boot partition for the slot that had at&t rom on it, to the slot that had ArrowOS on it? If so, sounds like just finding a copy of the ArrowOS boot partition should work?
Which version are you running? Someone may have that boot partition available.
AsItLies said:
No, not a piece of garbage lol. Given the tools available for the G8; qfil, the programmers firehose, engineering abl, it's almost impossible to brick the device.
So, lesson learned; always make a backup. It sounds like you copied the boot partition for the slot that had at&t rom on it, to the slot that had ArrowOS on it? If so, sounds like just finding a copy of the ArrowOS boot partition should work?
Which version are you running? Someone may have that boot partition available.
Click to expand...
Click to collapse
yes that was exactly it, i understand i will never do anything without backup, i was using Arrow-v12.1-alphalm-UNOFFICIAL-20220627
so if someone has lg g8 and is using Arrow v12.1 alpham send boot_b.bin and I copy it using QFIL will my device boot again?
vini14zimm said:
yes that was exactly it, i understand i will never do anything without backup, i was using Arrow-v12.1-alphalm-UNOFFICIAL-20220627
so if someone has lg g8 and is using Arrow v12.1 alpham send boot_b.bin and I copy it using QFIL will my device boot again?
Click to expand...
Click to collapse
Well, if all that's changed is the boot partition it should boot again. But I checked on tele group and no one responded with it.
You may have to download the rom and see if you can extract the boot partition from it.
II have the same problem, were you able to solve it?
i need help
yonaikymatos said:
II have the same problem, were you able to solve it?
Click to expand...
Click to collapse
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying
vini14zimm said:
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying
Click to expand...
Click to collapse
Okay, think this is what you need. BUT!! I'm not 100% it is... SO! first thing you do is back up the boot image from the slot you want to replace it with this one. That way, if it doesn't work, you can just reflash the one you backed up and you're none the worse.
Second: IF, when flashing this image to the boot partition (loading it in qfil speak), you get a warning message about 'over flow of data' (or something to that effect), immediately stop, do not continue, as that's an indication it will not only not work but make your situation worse. Good luck
sorry, xda not allowing me to attach, follow this gdrive link for file.
vini14zimm said:
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying
Click to expand...
Click to collapse
I already solved it I'm going to attach the boot_b .bin
https://drive.google.com/file/d/1DANvrF-iklHQxr3bIOixv9orD376oG8U/view
the file is boot-a Android 11 Canadienc.bin
flash using qfil on a boot_b
AsItLies said:
Okay, think this is what you need. BUT!! I'm not 100% it is... SO! first thing you do is back up the boot image from the slot you want to replace it with this one. That way, if it doesn't work, you can just reflash the one you backed up and you're none the worse.
Second: IF, when flashing this image to the boot partition (loading it in qfil speak), you get a warning message about 'over flow of data' (or something to that effect), immediately stop, do not continue, as that's an indication it will not only not work but make your situation worse. Good luck
sorry, xda not allowing me to attach, follow this gdrive link for file.
Click to expand...
Click to collapse
I put arrowOS-boot.img in place of boot_b.bin using Qfil but I'm still at the fast boot screen, is there anything else I can do?
yonaikymatos said:
I already solved it I'm going to attach the boot_b .bin
https://drive.google.com/file/d/1DANvrF-iklHQxr3bIOixv9orD376oG8U/view
the file is boot-a Android 11 Canadienc.bin
flash using qfil on a boot_b
Click to expand...
Click to collapse
for some reason it's not being possible to put your boot-a Android 11 Canadienc.bin in place of my boot_b.bin , when I try to get this message Send image fail:Firehose Fail:FHLoader Failrocess fail , it doesn't seem like a good sign
vini14zimm said:
for some reason it's not being possible to put your boot-a Android 11 Canadienc.bin in place of my boot_b.bin , when I try to get this message Send image fail:Firehose Fail:FHLoader Failrocess fail , it doesn't seem like a good sign
View attachment 5659247
Click to expand...
Click to collapse
Don't use a usb 3.0 port when using qfil. You have to use a usb 2.0 port. Qfil is old software and was not designed for the higher speeds.
This is important whether making a backup of a partition of flashing a partition, either way with 3.x ports the image can get corrupted.
AsItLies said:
Don't use a usb 3.0 port when using qfil. You have to use a usb 2.0 port. Qfil is old software and was not designed for the higher speeds.
This is important whether making a backup of a partition of flashing a partition, either way with 3.x ports the image can get corrupted.
Click to expand...
Click to collapse
I put it in a usb 2.0 port and it was the same, this file does not seem to be compatible
Is there anything else I can do to save the device?
vini14zimm said:
I put it in a usb 2.0 port and it was the same, this file does not seem to be compatible
Is there anything else I can do to save the device?
View attachment 5664851
Click to expand...
Click to collapse
I'd suggest joining the tele group for that rom and asking there if anyone can give you the version of the boot partition you need.
AsItLies said:
I'd suggest joining the tele group for that rom and asking there if anyone can give you the version of the boot partition you need.
Click to expand...
Click to collapse
kinda had the same problem lol on 2023... anyways tried to fix it the way of netmsm, deleting all partitions, hard bricked i could say, kinda worked, but as far as i could do, it went to fastboot loop, to LG Bootlloooping lol, any recommendations
Hello thanks for reading,
I've spent about 2 days trying to figure this one out so any help would be greatly appreciated.
I've flashed it back to stock rom "hotdogb_14_O.22_210127.ops" with the MSM tool and flashed recovery TWRP to it, but I am consistently receiving the error
" Failed to mount '/system_ext' (Block device required)" in TWRP when i'm trying to write zip files and disable encryption.
when it comes to install anything, I get this same message and it fails - where am I going wrong? i've tried wiping it and repair as ext4 but nothing, same deal... any ideas?
Thanks in advance
tehnooks said:
Hello thanks for reading,
I've spent about 2 days trying to figure this one out so any help would be greatly appreciated.
I've flashed it back to stock rom "hotdogb_14_O.22_210127.ops" with the MSM tool and flashed recovery TWRP to it, but I am consistently receiving the error
" Failed to mount '/system_ext' (Block device required)" in TWRP when i'm trying to write zip files and disable encryption.
when it comes to install anything, I get this same message and it fails - where am I going wrong? i've tried wiping it and repair as ext4 but nothing, same deal... any ideas?
Thanks in advance
Click to expand...
Click to collapse
Use twrp v1 on twrp.me ?
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
HueyT said:
Use twrp v1 on twrp.me ?
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
Click to expand...
Click to collapse
Giving it a try right now, fingers crossed, I used a different version that boots before but not this one it seems. I'll let you know
Thanks for your time replying
Use twrp v1 on twrp.me ?
HueyT said:
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
dl.twrp.me
Click to expand...
Click to collapse
Didn't work, same issues, i'm at my wits end someone help me pretty please! Here's a screenshot
{
"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"
}
Does this no matter what I install, even if I go to format and wipe data always fails at that point, what command or trick am I missing guys? *begs*
Bootloader unlocked?
HueyT said:
Bootloader unlocked?
Click to expand...
Click to collapse
Yeah, all unlocked and ready to go else wouldnt let me boot into twrp without that first. I tried it with the latest version of android 11 and it didn't have the same message but still gave me a cant mount /opm (or something close to this) error message.... I feel like its something simple that I just lack the knowledge of
tehnooks said:
Yeah, all unlocked and ready to go else wouldnt let me boot into twrp without that first. I tried it with the latest version of android 11 and it didn't have the same message but still gave me a cant mount /opm (or something close to this) error message.... I feel like its something simple that I just lack the knowledge of
Click to expand...
Click to collapse
Did u "mount data" while in twrp before formatting data?
Morning Huey, No I did not, I am about to try it again right now just restoring via MSM and i'll give it a go
I've been following the guide at https://www.kali.org/docs/nethunter/installing-nethunter-on-the-oneplus-7/
but it's not for the 7T so maybe theres something missing, ive even tried using the older versions they suggest on there with no luck so far
HueyT said:
Did u "mount data" while in twrp before formatting data?
Click to expand...
Click to collapse
doesn't let me mount data before formatting data ;(
tehnooks said:
doesn't let me mount data before formatting data ;(
Click to expand...
Click to collapse
Remove screenlock before rebooting into twrp as your twrp is not decrypting data on 11.0.9.1
I'm downgraded to the last android 10 version as the guide says (but for hotdog) but always get the same error no matter what, I never set a screenlock or password or even a fingerprint, will update to 11 and latest update and try it again but it said can't mount /opm or something similar doing it that way. I feel like i'm just missing something really simple about the whole thing but i've followed the guides to a T
{
"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"
}
Hello, dear owners of this beautiful device.
After an unsuccessful attempt to get root, such a warning appeared, plus the ability to lock the screen disappeared. As a result, I didn't get root either and problems arose)
Could you show the instructions how to fix everything step by step and get root? Thanks)
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
redmgicUSER8 said:
Hey, so I have the same problem as you. I was installing the patched boot.img file when I rebooted, but there was no magsik app. After I tried to flash the same file again, except I put in some vbmeta file because some website said so, now my phone's files are corrupted. I got into fastboot mode and put through recovery mode, and did a data wipe and one final reboot, but even that did work because it said my phone is corrupt. The last thing I will try is to install TWRP, remove the old data, and install the update to restore the previous ROM files. I'll let you know if anything works. Just try ur methods and let me know if they worked. Sure is an expensive paperweight if it doesn't work...
Click to expand...
Click to collapse
did anything happen?
Stusick said:
Did anything happen?
Click to expand...
Click to collapse
Nothing yet... I'm trying to contact the support team. They can only do so much remotely
i have this error also what should i do?
the phone not boot up
the red warning are stuck
yakir150 said:
i have this error also what should i do?
the phone not boot up
the red warning are stuck
Click to expand...
Click to collapse
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
okay i try it and still no luck the same problem
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
[email protected] said:
Download global V3.19 rom from: https://rom.download.nubia.com/Europe&Asia/NX729J/V319/NX729J.zip
Download QPST and QFIL flash tool from: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file. Install the driver (provided in the download) and these two programs.
You could then flash this rom V3.19 using QFIL flash tool. If you can flash this rom successfully your phone will work.
Click to expand...
Click to collapse
my phone is eu and using 4.18
can i use 3.19?
it's ok?
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
For QFIL, use Flat Build and in the configuration use ufs. Good luck!
yakir150 said:
my phone is eu and using 4.18
can i use 3.19?
it's ok?
Click to expand...
Click to collapse
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
[email protected] said:
Your version V4.18 will be replaced by V3.19. This V3.19 version can be flashed through edl mode. I could not find V4.18 in this format. The two roms are very similar. They are both global roms.
Click to expand...
Click to collapse
okay i will try and let you know
thank you very much
yakir150 said:
okay i try it and still no luck the same problem
Click to expand...
Click to collapse
If QFIL does not work, you need to do side load the rom multiple times again then it might work!
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
izsdeaman said:
turn off the red rm8 notification (Your device is broken. It is unreliable and may not work)
- enter command on PC: adb reboot "dm-verity enforcing"
- on phone for rooted device with termux: reboot "dm-verity enforcing"
Click to expand...
Click to collapse
The command on PC shows "Too many arguments." The Termux one works. Thanks!
[email protected] said:
Your boot loader must be unlock
Reboot to recovery, choose English when you see "Wipe data" type
adb reboot sideload
Once your phone boots into sideload mode (When you see the two error line at the bottom of the screen) type
adb sideload NX729J-update.zip
When the transfer is successful ( with a transfer of 2.0 display) you can wipe the data twice with the first and second options and reboot the phone. If you are lucky, the phone will boot
Click to expand...
Click to collapse
Tahnk you very very very much.