Related
Long story short i soft bricked my LG LS665 (Tribute 2),flashing recoveries and boot with the wrong file now i get a secure boot error 1003. I do have a back ups of all my partitions but it is in zip format and have no way to flash it because i can only boot into download mode, no recovery or adb. Does any one know how i can get it to boot into fastboot so i can re flash my backups, I have tried to dd the laf partition as mentioned many times on this forum but does not work. In download mode i can connect through the DIAG com port and use send_command, ls, and such but i do not know where the laf partition resides. it would also be possible to flash the KDZ file also but i can not find one and LG or Virgin Mobile will not hand it out they want to do an in house repair so if i could convert my zip back up to a KDZ that would work but i would not know where to begin on that. Any help is appreciated. TYIA:good:
i have the same problem
plz help me if u can
Can you possibly email me zip backups stoneman4504 at hotmail dot com I kingrooted supersume and installed supersu into system and rebooted to bootscreen without doing any bsckup :-/ San hoping that your backup zips was stock recovery flashable thanks in advance
hi
hi. somebody have the zip files? i brick my device too
wajiema said:
Long story short i soft bricked my LG LS665 (Tribute 2),flashing recoveries and boot with the wrong file now i get a secure boot error 1003. I do have a back ups of all my partitions but it is in zip format and have no way to flash it because i can only boot into download mode, no recovery or adb. Does any one know how i can get it to boot into fastboot so i can re flash my backups, I have tried to dd the laf partition as mentioned many times on this forum but does not work. In download mode i can connect through the DIAG com port and use send_command, ls, and such but i do not know where the laf partition resides. it would also be possible to flash the KDZ file also but i can not find one and LG or Virgin Mobile will not hand it out they want to do an in house repair so if i could convert my zip back up to a KDZ that would work but i would not know where to begin on that. Any help is appreciated. TYIA:good:
Click to expand...
Click to collapse
can you please email me the zip backups.
ihateyourdumbf[email protected]
thanks
http://androidforums.com/threads/lg-tribute-2-boost-reference-guide.935920/
here is a backup file in zip
HI,
I’ve been having problems with my OPO and I don’t know what to do next.
I was getting stuck in a boot loop – which appeared to be a common issue:
http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/
I had to fastboot oem unlock to run this fix, so I decided whilst I was there to install a custom ROM (SultanROM).
A few days later I got the boot loop issue again, but this time, the fix linked above didn’t work. I thought it wasn’t applying correctly, and so I tried to reinstall the sultan ROM and re-run the Make_Ext4fs fix. Unfortunately, it hasn’t gone well!
The current position is I can now boot in to fastboot or to recovery (TWRP 2.8.7.0), but I think I might have deleted (adb erase) the system partition (because I thought I could easily reflash it, and it wasn’t booting). Now, if I try to boot in to system it gets stuck on the screen with the oneplus logo and doesn’t get any further. I can connect via fastboot (bootloader) or ADB (TWRP). I have used ADB sideload to flash a ROM and I have tried flashing a ROM.ZIP within TWRP but it doesn’t seem to work (most times it cannot mount/find system but sometimes if I “wipe” the phone in TWRP and then flash it *seems* to flash OK (“Operation successful”) but still won’t boot.
Is there a toolkit than can completely rewrite everything on the phone and could fix this? Or any other suggestions?
I don’t have a backup, idiotically as I wasn’t thinking I was doing anything permanent and wasn’t bothered about keeping any of my files.
Thanks!
James
PS – unfortunately my home broadband is broken so I can’t load/try many tools or easily find anything because the only internet access I have is at work, where many things are blocked. I am going over to a friend’s tonight (aprox 5 hours) to try and fix my phone at his house, so any suggestions before that greatly appreciated.
http://forum.xda-developers.com/showthread.php?t=2826541
I would suggest you try taking your phone back to stock COS12.1 and after its installed set it up normally, go back to fastboot and flash a custom recovery, boot TWRP make a backup then proceed to flash a custom ROM. Copy that back up to your computer just in case and also make EFS backups for a rainy day
Sent from my A0001 using Tapatalk
Any way to get "system profiles" tile back in quick settings panel?
Renosh said:
http://forum.xda-developers.com/showthread.php?t=2826541
I would suggest you try taking your phone back to stock COS12.1 and after its installed set it up normally, go back to fastboot and flash a custom recovery, boot TWRP make a backup then proceed to flash a custom ROM. Copy that back up to your computer just in case and also make EFS backups for a rainy day
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks! This process worked and I am back to stock. Unfortunately, still suffering from the boot loop. Frustrating! I'm in touch with OPO Support now... Apparently they can be slow...
jamesking420 said:
Thanks! This process worked and I am back to stock. Unfortunately, still suffering from the boot loop. Frustrating! I'm in touch with OPO Support now... Apparently they can be slow...
Click to expand...
Click to collapse
You probably corrupted your EFS partition somehow. You can try this guide
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
And here I'll link what happened to me and it seems nothing could fix it but these commands from the guide above helped get me out of the bootloop
http://forum.xda-developers.com/showpost.php?p=63611589&postcount=914
Try this stuff if the support guys from OnePlus are unable to help
Renosh said:
You probably corrupted your EFS partition somehow. You can try this guide
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
And here I'll link what happened to me and it seems nothing could fix it but these commands from the guide above helped get me out of the bootloop
http://forum.xda-developers.com/showpost.php?p=63611589&postcount=914
Click to expand...
Click to collapse
Thanks,
That seems to indicate I just need to unlock, flash persist.img and then it should all be OK?
jamesking420 said:
Thanks,
That seems to indicate I just need to unlock, flash persist.img and then it should all be OK?
Click to expand...
Click to collapse
Well it should but if that doesn't work try the options in the second link I posted those worked for me
Sent from my A0001 using Tapatalk
Renosh said:
Well it should but if that doesn't work try the options in the second link I posted those worked for me
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks! And if I erase them (as per second link), do I need to flash them again afterwards?
Reading it again, you mean to erase those two partitions, and then *after* run the flash command. (Initially I thought you meant you ran those two erase commands after you ran the flash command!)
Cheers!
Sorry for the possibly silly question!
Greetings. Today i soft-bricked my phome . All the apps stopped responding so i decided to do a backup that i made a while ago in TWRP. All i restored was: proinfo, nvram, protect_f, protect_s, uboot, para, Boot, Recovery, logo, secro, tee, frp and nvdata. I dunno what happend because when i swiped to restore, the size of the backup was only 1MB ( it usually shouled be 68-69MB). This is how i soft-bricked my phone, when i power him up it boots for about 5 seconds with the boot logo then the screen become totally black. I can still enter Recovery mode and i can even acces the Internal & SD Card MTP from my PC.
If anyone has a Allview P7 Pro with TWRP and he wants to help me, please do a Backup in TWRP with the following things: proinfo, nvram, protect_f, protect_s, uboot, para, Boot, Recovery, logo, secro, tee, frp and nvdata and then post the backup right here. I would be much pleased because otherwise i should go with it to the warranty, and it takes about 2 weeks. Thank you so much for the help.
Sketch RPG2 said:
Greetings. Today i soft-bricked my phome . All the apps stopped responding so i decided to do a backup that i made a while ago in TWRP. All i restored was: proinfo, nvram, protect_f, protect_s, uboot, para, Boot, Recovery, logo, secro, tee, frp and nvdata. I dunno what happend because when i swiped to restore, the size of the backup was only 1MB ( it usually shouled be 68-69MB). This is how i soft-bricked my phone, when i power him up it boots for about 5 seconds with the boot logo then the screen become totally black. I can still enter Recovery mode and i can even acces the Internal & SD Card MTP from my PC.
If anyone has a Allview P7 Pro with TWRP and he wants to help me, please do a Backup in TWRP with the following things: proinfo, nvram, protect_f, protect_s, uboot, para, Boot, Recovery, logo, secro, tee, frp and nvdata and then post the backup right here. I would be much pleased because otherwise i should go with it to the warranty, and it takes about 2 weeks. Thank you so much for the help.
Click to expand...
Click to collapse
Your warranty was voided when your rooted your device or installed TWRP. You won't be able to take advantage of the warranty unless you restore the device to full stock with stock recovery instead of TWRP and without root. With the modifications you made they'll know you altered the device.
Why didn't you just make a standard backup in TWRP using the default settings? A backup with default parameters should be all you needed, then restoring that backup with default parameters should have been all you needed.
You might have to flash your full stock firmware to restore your device because I doubt there is much available for your device here and there probably aren't very many users with your device and of those, I doubt any of them will have what you need. It's worth trying to find it though, just not sure if you will.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Your warranty was voided when your rooted your device or installed TWRP. You won't be able to take advantage of the warranty unless you restore the device to full stock with stock recovery instead of TWRP and without root. With the modifications you made they'll know you altered the device.
Why didn't you just make a standard backup in TWRP using the default settings? A backup with default parameters should be all you needed, then restoring that backup with default parameters should have been all you needed.
You might have to flash your full stock firmware to restore your device because I doubt there is much available for your device here and there probably aren't very many users with your device and of those, I doubt any of them will have what you need. It's worth trying to find it though, just not sure if you will.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Nevermind, i just hard bricked it, so hard it won't even boot. I did this so they don't observe i was tampering with the phone. I wiped everything (even /system partition). I did this a while ago and it worked. I tried reversing everything but the phone got stuck in USB Debugging off and i couldn't enable it, not even in terminal/adb/fastboot. Without USB Debugging i couldn't flash the stock recovery, without the stock recovery i wasn't able to get my warranty back. This was the best decission, i once sent the phone to warranty even with TWRP installed (AND ACCESIBLE) and somehow they still fixed the phone. I got very scared because i had no way to remove or swap TWRP with stock recovery. What i did was create a Boot backup, replace it with a empty .txt file and changed the .txt file to boot.emmc.win and then i restored. Now not even the boot image is shown )). I'm a "BRICKER"".
Sketch RPG2 said:
Nevermind, i just hard bricked it, so hard it won't even boot. I did this so they don't observe i was tampering with the phone. I wiped everything (even /system partition). I did this a while ago and it worked. I tried reversing everything but the phone got stuck in USB Debugging off and i couldn't enable it, not even in terminal/adb/fastboot. Without USB Debugging i couldn't flash the stock recovery, without the stock recovery i wasn't able to get my warranty back. This was the best decission, i once sent the phone to warranty even with TWRP installed (AND ACCESIBLE) and somehow they still fixed the phone. I got very scared because i had no way to remove or swap TWRP with stock recovery. What i did was create a Boot backup, replace it with a empty .txt file and changed the .txt file to boot.emmc.win and then i restored. Now not even the boot image is shown )). I'm a "BRICKER"".
Click to expand...
Click to collapse
Intentionally hard bricking is an option also sometimes, a bit unethical, but still an option.
But sometimes it can be difficult to intentionally completely brick a device. It almost seems easier to accidentally hard brick than it does to intentionally do it, lol.
Sent from my SM-S903VL using Tapatalk
It really does =), if you believe me, I struggled for 2 hours trying to brick the phone so it doesn't boot in recovery. I think it's better to have the phone 2 weeks in "intensive" warranty than voiding it permanently.
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.
Why nobody use orangefox?
is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable
joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.
CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?
Hey all. I just upgraded my OP 7 Pro to the 10.3.2, and I had magisk write the bootloader to the unused slot... but I forgot to run the retention script and I restarted my phone. At first it seemed like all hope was lost, but I have been able to flash and kinda boot into the latest unofficial TWRP, but that just results in an unresponsive screen with the TWRP background, and sometimes just flashes it as well. I can still adb shell into my phone at this point but I don't know where to go from here to fix my situation. I was hoping to at least be able to grab my data. I did at least do a backup with TWRP before doing the upgrade, but that obviously does not back up my pictures and such.
Does anyone have any suggestions or am I screwed and have to start over?
EDIT: I said forget it and just formatted. I got a few things working, but the damage was already done and I lost my data. No big deal.
This thread can be deleted now.
On a pc download the right recovery for your Phone. Be sure you have it for android Q!
Then in commandline: "Fastboot boot recovery.img"
From there
Flash the twrp installer
Flash magisk.
Take the recovery from https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943
Take care!