Related
Hey there,
so I wanted to update LineageOS to the latest nightly (1st August) coming from an April nightly. I did it OTA, entered TWRP, installed the update and got stuck in TWRP, which is apparently a known issue with TWRP 3.0.2.0. But I didn't know that, and tried to fix it by installing a backup of CM 13 WITHOUT wiping data, because I did not want to lose my data. Stupid, I know.
I then found a fix to leave TWRP and tried booting into CM 13 but now I'm stuck in a bootloop when the phone is connected to my pc. . It shows the CM logo, then prepares apps, shows the logo, prepares apps, logo, and so on... When I unplug it, it gets stuck at "Preparing Apps"
I can't enter Download mode or Recovery mode using the keys and adb/fastboot commands don't work while the phone is turned off or booting.
Any ideas what I can do?
Hello, what is your device?
If battery is removable, remove battery then put it back and try to boot to download mode
Its an LG 2 Mini and i have done that already.
Do you know how i could possibly fix the issue with rebooting when connected to my computer? Maybe then i can recover it via adb
Turn off the phone
Keep holding down Volume Up button.
Put a USB cable that is connected to pc
Continue holding Volume Up button throughout download mode until fastboot mode appears and you can release the Volume Up button.
If that didn't work try with volume down
I'm in Download mode now, thanks! However i can't use adb or fastboot commands, even though i have the right drivers installed.
In the Windows device manager it shows it as" "LGE Android MTP device" with Code 10 Error (the device couldnt be started)
Anyone knows how to proceed?
lionboy33 said:
In the Windows device manager it shows it as" "LGE Android MTP device" with Code 10 Error (the device couldnt be started)
Anyone knows how to proceed?
Click to expand...
Click to collapse
What do you get when you try to use fastboot commands?
"waiting for any device"
Fastboot devices is also empty
---
I believe it's a problem with my adb or my drivers, because I can't get it to work with my other phone either
Sorry for being late, try installing usb drivers again from the lg site
I did, but it didnt help
On Linux Mint it shows "unable to mount LGE Android Phone"
lionboy33 said:
Hey there,
so I wanted to update LineageOS to the latest nightly (1st August) coming from an April nightly. I did it OTA, entered TWRP, installed the update and got stuck in TWRP, which is apparently a known issue with TWRP 3.0.2.0. But I didn't know that, and tried to fix it by installing a backup of CM 13 WITHOUT wiping data, because I did not want to lose my data. Stupid, I know.
I then found a fix to leave TWRP and tried booting into CM 13 but now I'm stuck in a bootloop when the phone is connected to my pc. . It shows the CM logo, then prepares apps, shows the logo, prepares apps, logo, and so on... When I unplug it, it gets stuck at "Preparing Apps"
I can't enter Download mode or Recovery mode using the keys and adb/fastboot commands don't work while the phone is turned off or booting.
Any ideas what I can do?
Click to expand...
Click to collapse
First of all, when restoring a backup, wipes are not necessary because the partitions are automatically formatted during the restore process. It wipes data for you, anything there would have been wiped anyway even though you were trying to avoid losing data, it is intentionally designed to do this so that you don't have conflicts with existing data.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
First of all, when restoring a backup, wipes are not necessary because the partitions are automatically formatted during the restore process. It wipes data for you, anything there would have been wiped anyway even though you were trying to avoid losing data, it is intentionally designed to do this so that you don't have conflicts with existing data.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
What i meant when i said i didnt wipe data was that i didnt choose to restore data when restoring the backup - just system and boot
lionboy33 said:
What i meant when i said i didnt wipe data was that i didnt choose to restore data when restoring the backup - just system and boot
Click to expand...
Click to collapse
but this shouldn't cause troubles and the system should boot :/
try with another cable or usb port
run
`sudo fastboot devices`
-Hope- said:
but this shouldn't cause troubles and the system should boot :/
try with another cable or usb port
run
`sudo fastboot devices`
Click to expand...
Click to collapse
I assume the backup i tried to restore was corrupted then maybe...
I tried several cables, none worked I believe its a problem with drivers on the device, because it didnt get in a bootloop with a non data usb cable
lionboy33 said:
I assume the backup i tried to restore was corrupted then maybe...
I tried several cables, none worked I believe its a problem with drivers on the device, because it didnt get in a bootloop with a non data usb cable
Click to expand...
Click to collapse
Linux usually comes with needed files by default, just install the platform tools package + fastboot and adb package and try again i don't think you would need to install drivers.
lionboy33 said:
What i meant when i said i didnt wipe data was that i didnt choose to restore data when restoring the backup - just system and boot
Click to expand...
Click to collapse
Yeah, that would have caused problems.
You can't use data from one ROM in a different ROM. When you restored, you left the data from LOS, the system and boot from CM13 won't work with the data from LOS.
For future reference, don't mix data from other ROMs, they don't play well in most cases.
Using advanced restore to only restore certain partitions usually only works when using the same ROM or an older/newer version of the same ROM.
If you can get back into recovery somehow, you'll probably need to do advanced wipes to wipe system partition and data partition then flash a ROM. Wipe cache and dalvik/ART cache after flashing the ROM, then reboot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Yeah, that would have caused problems.
You can't use data from one ROM in a different ROM. When you restored, you left the data from LOS, the system and boot from CM13 won't work with the data from LOS.
For future reference, don't mix data from other ROMs, they don't play well in most cases.
Using advanced restore to only restore certain partitions usually only works when using the same ROM or an older/newer version of the same ROM.
If you can get back into recovery somehow, you'll probably need to do advanced wipes to wipe system partition and data partition then flash a ROM. Wipe cache and dalvik/ART cache after flashing the ROM, then reboot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I can't enter recovery, it always just boots normally. I can only enter Download mode without fastboot access
lionboy33 said:
I can't enter recovery, it always just boots normally. I can only enter Download mode without fastboot access
Click to expand...
Click to collapse
Keywords "if" and "somehow"
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Does flashtool detect the phone ?
We can zero the laf partition to force the phone in fastboot mode but we must proceed in caution if you want to.
-Hope- said:
Does flashtool detect the phone ?
We can zero the laf partition to force the phone in fastboot mode but we must proceed in caution if you want to.
Click to expand...
Click to collapse
No, flash tool doesn't recognize it
Can anyone tell me what is the reason for the failure to flash the third-party ROM? The phone has been unlocked, and the twrp that was swiped is twrp-3.3.1-24-I01WD-Q-mauronofrio.img. The method I swiped in is to double-clear and then select the rom to flash in. The flash is successful but the system cannot be restarted Boot, can only be stuck in fastboot, seek solutions
There are a couple of similar threads from people with similar problems. Have a look and see if you can solve your issue. If not, feel free to ask again and provide more detailed information about what you did and what did not work.
Unofficial twrp can be successfully brushed in with adb, and the success rate is also high. The probability of official twrp brushing in is greater, but it can also be brushed in, but the official twrp brush third-party rom is easy to fail, the reason is unclear, unofficial twrp brush It is easy to succeed in the third-party rom, but why can't the boot be stuck in fastboot after the unofficial twrp is flashed into the rom?
Because zenfone6 is the ab partition, I think this may be the main reason for not booting. Is it possible that the two partitions are not flashed into the system, and only one partition is flashed into the system, so it will not boot!
I flashed in the rom twice and couldn't boot. The specific method of flashing the phone is: the mobile phone system is the latest system, first use adb to flash into the unofficial twrp (twrp-3.3.1-24-I01WD-Q-mauronofrio.img), flash in Successfully, the phone automatically enters twrp, and then flashes the unofficial twrp in zip format again (twrp-3.3.1-24-I01WD-installer-mauronofrio.zip), restart twrp, click wipe, and swipe to complete. Click lnstall, select rom, and swipe to complete, and click wipe again to complete the slide. Click lnstall, select rom to complete the flashing, click to restart the system, the phone cannot boot, only fastboot.
The above method can not boot, I connected the phone to the computer and re-brushed into twrp with adb. Note: When I first flashed into twrp, the phone did not restart to twrp, but booted to the official system to restore the factory interface, etc. After the operation of the mobile phone is completed, boot up and enter the desktop. I turned on the USB debugging. At this time, the mobile phone can enter the unofficial twrp. Then I flashed into the rom again, and then did not restart the system. I restarted twrp, but the mobile phone reached fastboot again. What I thought was Restart twrp when flashing for the first time, flash once, so that both partitions can flash into the system, but twrp cannot be restarted, only fastboot!
Guiqiu you guys to solve my problem, can't the phone be broken?
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password
#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though
Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!
#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?
you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.
I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
sergio-bodyweb said:
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
Click to expand...
Click to collapse
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
plegdroid said:
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
plegdroid said:
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
Click to expand...
Click to collapse
Of course, thx.
i have used my phone and all was fine, but i wanted to reboot it and something went wrong. first it has stuck in boot loop, i waited ~10 minutes and tought it'll boot but no, then i tried enter a Recovery (twrp) and it just doesnt want to boot even in recovery. So i went to fastboot and flashed a new verion of twrp, but it still won't boot. All the times when i have been stuck in a bootloop i just cleared caches wia twrp and phone booted fine but now i really doesn`t know what i can do to rescue it and not lose my data. So maybe there is a way i can wipe caches without accessing the recovery menu? =(
if i force bootloader to load from fastboot it throws me back into a fastboot.
Poco x3 nfc (surya) Android 12 Pixel Experience (official from their website)
also i have tried alot of recoveries ( bunch of twrps, 3 orange foxes, PE recovery) no one works, TWRP&OF just hangs on splash screens and PErecovery is just a black screen. i just have no clue what do i do. i can try flash rom from a fastboot but then i will lose all my data.
i have no much knowlege about logging in android, here is adb logcat https://pastebin.com/6bSFURBM
EnderDremurr said:
i have used my phone and all was fine, but i wanted to reboot it and something went wrong. first it has stuck in boot loop, i waited ~10 minutes and tought it'll boot but no, then i tried enter a Recovery (twrp) and it just doesnt want to boot even in recovery. So i went to fastboot and flashed a new verion of twrp, but it still won't boot. All the times when i have been stuck in a bootloop i just cleared caches wia twrp and phone booted fine but now i really doesn`t know what i can do to rescue it and not lose my data. So maybe there is a way i can wipe caches without accessing the recovery menu? =(
if i force bootloader to load from fastboot it throws me back into a fastboot.
Poco x3 nfc (surya) Android 12 Pixel Experience (official from their website)
also i have tried alot of recoveries ( bunch of twrps, 3 orange foxes, PE recovery) no one works, TWRP&OF just hangs on splash screens and PErecovery is just a black screen. i just have no clue what do i do. i can try flash rom from a fastboot but then i will lose all my data.
i have no much knowlege about logging in android, here is adb logcat https://pastebin.com/6bSFURBM
Click to expand...
Click to collapse
Try this tool: https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
Try this tool: https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
does that thing works on linux? sadly i have no pc with a windows now
EnderDremurr said:
does that thing works on linux? sadly i have no pc with a windows now
Click to expand...
Click to collapse
You can flash fastboot ROMs on Linux with fastboot and adb tools
or
https://forum.xda-developers.com/t/tool-linux-miflash-for-linux.3708847/
https://www.bettermobileapp.com/article/10416422/[TOOL][Linux]+MiFlash+for+Linux
https://gist.github.com/duyfken/574f570f40f813604849bd40d9e1a048
To check .
do a search
NOSS8 said:
You can flash fastboot ROMs on Linux with fastboot and adb tools
or
https://forum.xda-developers.com/t/tool-linux-miflash-for-linux.3708847/
https://www.bettermobileapp.com/article/10416422/[TOOL][Linux]+MiFlash+for+Linux
https://gist.github.com/duyfken/574f570f40f813604849bd40d9e1a048
To check .
do a search
Click to expand...
Click to collapse
hi, i have one more question, is there way i can check my phone`s internal memory from adb ( for dead sectors etc.) i think my internal memory just have died somehow
EnderDremurr said:
hi, i have one more question, is there way i can check my phone`s internal memory from adb ( for dead sectors etc.) i think my internal memory just have died somehow
Click to expand...
Click to collapse
Start by format data,miflash can do it.(will erase the data and create a new partition if necessary).
And use this TWRP https://androidfilehost.com/?w=files&flid=318270
just flash stock rom with miflash and select save user data and done, will flash the entire rom without lose your personal data
tutibreaker said:
just flash stock rom with miflash and select save user data and done, will flash the entire rom without lose your personal data
Click to expand...
Click to collapse
From an AOSP rom to MIUI?