Related
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
stealth0wnz said:
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
Click to expand...
Click to collapse
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
Here is a link showing how to adb push - http://forum.xda-developers.com/showthread.php?t=1667929
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
speedbal said:
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
Click to expand...
Click to collapse
I guess you gotta learn this stuff at some point, thanks for your help! i forgot that you could push files!
now a brand new issue is that anytime i flash ANYTHING to the phone, adb doesn't see the device anymore.
anyone know what's up with that?
URGENT
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
SteveRogers1776 said:
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
Click to expand...
Click to collapse
New nightlies of CM12.1 needs the bootloader to be updated to newer version (HHZ12H).
Following the link to flashable zip of new bootloader: https://www.androidfilehost.com/?fid=23991606952613145 (Credit to @mo976)
Flash it in recovery
Wipe the cache
Reboot into bootloader and select recovery.
Flash CM12.1 rom.
I just tried what you recommended . Maybe I'm doing it wrong but I'm still getting "error updating binary zip" when trying to load anything on twrp
Hi There, need some help if you can...any educated and experienced help would be appreciated thanks.
After downloading my stock firmware and extracting via Huawei update Extractor all the image files ( System, user data, Cache, etc) I backed up oeminfo and cust files via Rayglobe Knife and saving the extracted update.app file to my dload folder on SDCard and successfully resetting my phone to factory using the vol+/- and power method I was quietly confident to make the jump and flash a rom the Android 7.0 (N) Nougat beta on Huawei posted by Somboons
I followed the instructions and dirty flashed this thru TWRP as instructed which seemed to go ok until I tried to reboot, the phone booted to stock recovery so I wiped Dalvik, Cache and Factroy reset, this completed and it all went down hill from there, basically now just stuck at boot screen saying that its about to reboot but never moves unless I use button combos
(OK so yes I feel stupid now and I'll beat myself up so you don"t have to, but I reallyt thought that I could always get back to stock via my SDCard)
What I can do...
Phone can only boot to eRecovery ( with WIFI failed message )
I can go into fastboot ( shows Bootloader and FRP unlocked)
What i can't do...
Cant access my update file on SDCard....Trying to boot using vol+/- and power to access my dload/update.app file on my SDCard just freezes at initial boot screen and tells me to push vol up button for 3 second and this takes me to eRecovery where all i can do is reboot or shut down.
I can't adb sideload files " no SU Binary detected"
What I've tried...
I have tried Rayglobe knife UNBRICK option placing my extracted boot, cust, system, recovery .img files but his fails with my PC popping up and saying this operation can't be performed on this PC please contact developer so this fails.
I then tried to fastboot flash all the image files which seemed to work successfully but no changes to the situation.
I have tried to fastboot flash the update.app which went thru the sparse process of all seven files and then come up with error command can not complete ( something in those words)
I have tried to fastboot new stock recovery from my rom as well as TWRP recovery but nothing works even if it says seems to have completed in the adb command prompt.
I have a feeling this is to do with the encryption of the rom and now my system cannot recognise my partition and without recovery I have no way of mounting my sdcard.
Thank god I have my old and reliable Lumia 1520 to fall back on untill I get this sorted.
Any Help would be appreciated....thanks in advance
Are you able to boot into Huawei recovery?
Mickie.C said:
Hi There, need some help if you can...any educated and experienced help would be appreciated thanks.
After downloading my stock firmware and extracting via Huawei update Extractor all the image files ( System, user data, Cache, etc) I backed up oeminfo and cust files via Rayglobe Knife and saving the extracted update.app file to my dload folder on SDCard and successfully resetting my phone to factory using the vol+/- and power method I was quietly confident to make the jump and flash a rom the Android 7.0 (N) Nougat beta on Huawei posted by Somboons
I followed the instructions and dirty flashed this thru TWRP as instructed which seemed to go ok until I tried to reboot, the phone booted to stock recovery so I wiped Dalvik, Cache and Factroy reset, this completed and it all went down hill from there, basically now just stuck at boot screen saying that its about to reboot but never moves unless I use button combos
(OK so yes I feel stupid now and I'll beat myself up so you don"t have to, but I reallyt thought that I could always get back to stock via my SDCard)
What I can do...
Phone can only boot to eRecovery ( with WIFI failed message )
I can go into fastboot ( shows Bootloader and FRP unlocked)
What i can't do...
Cant access my update file on SDCard....Trying to boot using vol+/- and power to access my dload/update.app file on my SDCard just freezes at initial boot screen and tells me to push vol up button for 3 second and this takes me to eRecovery where all i can do is reboot or shut down.
I can't adb sideload files " no SU Binary detected"
What I've tried...
I have tried Rayglobe knife UNBRICK option placing my extracted boot, cust, system, recovery .img files but his fails with my PC popping up and saying this operation can't be performed on this PC please contact developer so this fails.
I then tried to fastboot flash all the image files which seemed to work successfully but no changes to the situation.
I have tried to fastboot flash the update.app which went thru the sparse process of all seven files and then come up with error command can not complete ( something in those words)
I have tried to fastboot new stock recovery from my rom as well as TWRP recovery but nothing works even if it says seems to have completed in the adb command prompt.
I have a feeling this is to do with the encryption of the rom and now my system cannot recognise my partition and without recovery I have no way of mounting my sdcard.
Thank god I have my old and reliable Lumia 1520 to fall back on untill I get this sorted.
Any Help would be appreciated....thanks in advance
Click to expand...
Click to collapse
I have solved so
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
warsangel said:
I have solved so
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
A very big thanks ....this worked with no hitches except I now have no service now have to find unlock code for sim and get rid of the Ascend 7 splash screen that appears before the original Huawei Boot screen.?
After the above issues with thanks to warsangel's suggestion to use DC_Phoenix, I have managed to get my phone back up and running...got sim working so I now can detect my network and call and text using HCU client.
I now want to get rid of the annoying splash screen on bootup that shows Huawei Ascend spalsh screen before the mate 8 factory Huawei animated boot up screen. I still cannot access my dload folder on SDCard using vol-/+ and power button combo and if I dial in to manufacturers settings using*#*#2846579#*#* when i select upgrade from sd card i get a "PT failed do you still want to continue" if i click yes it re installs the firmware but makes no changes at all. Does any one have any other ideas. Of how to clear the splash screen and get the phone working back on Mate 8 button and bootup settings. Everything else works perfectly just a couple of things that will niggle at me...just want to get it back to out of the box as I have the Original Firmware zip file for this phone and region. cheers
bluheart said:
Are you able to boot into Huawei recovery?
Click to expand...
Click to collapse
Hi blueheart...no I can't, I think this is my problem, I can get to fast boot and I can't fastboot anything now because the boot loader is locked with a different code than the original one that I paid for with dc-unlocker. I have manged thru HCU cLIENT to get my original imei number and serial number but this serial number doesnt show up when I fastboot devices, lists one that come with the Phoenix firmware I flashed which is an Ascend as this was a NXT image closest to my NXT-L09.
My problem still is that I seem to go in to 2G and lose the signal all the time, I'm thinking I need to enter more details in CDMA repair in HCU Client or am I going about this the wrong way???
Oh bru, no idea!
HCU client is good enough. Keep trying dload if your bootloader is locked, it will flash for sure. Phone isn't easy to brick.
bluheart said:
Oh bru, no idea!
HCU client is good enough. Keep trying dload if your bootloader is locked, it will flash for sure. Phone isn't easy to brick.
Click to expand...
Click to collapse
Cheers Mate, managed to get to dload/update now but this doesnt seem to give a full reset, but modem is holding a signal but intermittently will drop into no service. I managed via HCU to re enter my imei and serial but a different serial number showsup in my settings still ??? getting back to where i need to but the signal dropping is a real problem. The next step is to try and get bootloader unlocked....any advice from any one.... if I fastboot flash modem will this be enough to bring my base band back or is there another file I should be looking at? cheers
You need to have cust and oem info of your own area for best signal
bluheart said:
You need to have cust and oem info of your own area for best signal
Click to expand...
Click to collapse
Thanks....I have my backup oeminfo it isnt a .img or .app file it just says oeminfo (type=file) can i fast boot this ? or do I have to use SRKtool as I don't want to unlock bootloader.
DC-Phoenix tool lets me fastboot .img files via backdoor and app files can I convert the oeminfo file to and .img file?
Cheers
How did you do the back up?
You can flash via fastboot
bluheart said:
How did you do the back up?
You can flash via fastboot
Click to expand...
Click to collapse
Backup was done through Rom Manager but the back up isn't an image it's a series of files like system.ext4, boot.emmc.win etc with MD5 info files. I've re-rooted device and tried to use rom manager to restore but when it boots to TWRP recovery nothing happens??? and I can't see any of the files if I go into the twrp folder on the SDcard because they aren't zip or img file.
My biggest problem even after doing full factory reset, wipe cache or install my original firmware update.app file, it doesn't seem to over write the image file that I used to recover my phone with the DC-Phoenix app, every thing indicates that it has been successful, but when I boot up,, It never goes to the stock setup mode where you would normally, choose your region, set your pin etc....it's like my install is only a shell or part of my install is not overwriting the dgtks firmware file I used which was a Huawei Ascend 7. The system re-defaults after rest to this firmware. Anyone help me to get rid of it and get back to my stock please?
I can use my stock update.app but it's not installing over the NXT AL10_M00A095_Factory_firmware_Android_6.0_EMUI_4.0.dgtks that I use ( this was the closest firmware that they had ) I think I need to format my whole system to ext4 ??? especially the partition that it storing this data that is preventing me to get my stock firmware back....any help or advice on this ...thanks
Yes format via Huawei recovery then flash
Or
Root and flash via TWRP after unzipping
bluheart said:
Yes format via Huawei recovery then flash
Or
Root and flash via TWRP after unzipping
Click to expand...
Click to collapse
just to update....I tried formatting and resetting all partitions to ext4 format most of the partitioning was successful with the exception of Systrem and Cust...TWRP would allow me to do these....I did numerous wipes via TWRP and Stock RECOVERY but unfortunately even with a full update.app via sdcard / dload folder and fastboot update.app (my firmware) via DC-Phoenix I couldn't seem to get a full factory stock install, same problems as discussed above and file system always goes to Encrypting screen and then I end up with the Ascend 7 screen and settings with obviously the wrong base band for my region. So I hate to admit defeat, but I've relocked bootloader, reset as much as I can and sent off to the Huawei Workshop to see if they can reset all the partitons back to normal.
Hahaha
Cool, let's see
bluheart said:
Hahaha
Cool, let's see
Click to expand...
Click to collapse
Update: well I dodged a bullet today....I sent my Mate 8 away 5 days ago to the Huawei tech support up the other end of the country and it arrived back today, back to stock and they replaced the main board with no cost to me at all. I was sure that they would call foul play and charge me but I obviously did such a number on the phone and then cleaned up all traces that they couldn't make that call lesson learn't and I see a few other people having similar problems with the Beta Nougat Rom....that you may need to post a big warning and send them to this posting so they are fair warned. I think this thread is done....I might just leave my phone alone and no tweaking for a while
Absolutely true!
XDA is not a playground for kids
You need courage to keep the Mate's balls on fire and get burnt with the nuclear reactions while keeping the blame on self
spent the last 3 weeks ( NO LIE ) trying every method under the sun to get my device rooted
easy recowvery
Hard Recowvery
manual ADB and flashing img
tot updates
kdz downgrades
basically everything
im not sure what else to do if its even possible at this point
Device details
tmobile locked LG G5 (h830)
OEM unlocked
its on 20a firmware ( coming from 20i )
ive rooted and installed twrp on may phones so i have a vast knowledge of these things
a few observations are
phone seems like its rewriting stock recovery on each reboot
fastboot won't accept any commands, i get "writing 'recovery'...FAILED (remote: unknown command)"
both hard recowvery and easy recowvery work up to the part of twrp install then it reboots to nothing
FINAL NOTE
im wondering if t-mobile is blocking the fastboot commands since im on temp unlock via device unlock app
if thats not a thing idk whats wrong im hoping one of you great minds can help this poor soul
Anyone?
Did you check oem unlock in developer options
rflores said:
Did you check oem unlock in developer options
Click to expand...
Click to collapse
thanks for replying ,
yes i did
its greyed out now but its been off
the fastboot commands says its unlocked as well
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
speters04 said:
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
Click to expand...
Click to collapse
thanks for this reply
i will try this as soon as i get home
thanks in advance
speters04 said:
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
Click to expand...
Click to collapse
providing an update
Ive just tried everything listed in you post specifically and failed , so i tried like 2 more time ,
it reboots into stock recovery so still no TWRP ,
boot loader is unlocked , cause i just checked again , and its still not accepting any commands
Adb flash commands do not work for the lg g5... You have to root with either easy recowvery or hard recowvery. You have to be on 20a firmware.
speters04 said:
Adb flash commands do not work for the lg g5... You have to root with either easy recowvery or hard recowvery. You have to be on 20a firmware.
Click to expand...
Click to collapse
thanks for reply;
none of those work for me either, I've been trying all this time
it says its successful in deploying commands, but when it restarts I see the LG logo two times, then it boots back up
( i assume its rewriting recovery there )
Can you explain the exact process you are trying? It is kinda hard to diagnose the issue without knowing the full process you are trying. I have rooted several lg g5 phones with the autorecowvery tool.
I had the same issue after returning from 20k to 20a. I didn't have this problem doing the same from 20f. T-Mobile might've introduced some security kink at 20i that sticks across updates. I was only able to flash twrp after flashing 20a with UPPERCUT to enter LGUP, booting into 20a, allowing debug in developer options, then running easyrecowvery with verification disabled (press 5 for advanced options, then 7 I think, then 0 to return to main menu, then 1 or 2). With verification enabled, easyrecowvery will just take you to the non-existent Android recovery screen and leave you there. I think that's where you're stuck??
speters04 said:
Can you explain the exact process you are trying? It is kinda hard to diagnose the issue without knowing the full process you are trying. I have rooted several lg g5 phones with the autorecowvery tool.
Click to expand...
Click to collapse
well lets use Autorecowvery for example
ive exhausted all options there and Ive gotten the success messages , does its fancy restarts and success messages all around , but when it restarts to install the "no-verity-opt-encrypt" it reboots and comes right back to android . ( note it reboots 2 times at this point , so i know its rewriting stock recovery )
see below
https://ibb.co/eq5ctR
It seems like you have a recovery flash. Have you tried adv reboot recovery? If not then you need to try that. You can also use hardware combination to get into recovery. You have to select yes both times and it will reboot to recovery. If it doesn't then start over with the auto recowvery. Also, it is very important that you download twrp and copy it to your internal storage on the root. Also, once it is there you have to name it to recovery. Don't use the .img when renaming it because you end up with recovery.img.img... Sometimes it takes a few tries on the recowvery method... Hope this helps!
speters04 said:
It seems like you have a recovery flash. Have you tried adv reboot recovery? If not then you need to try that. You can also use hardware combination to get into recovery. You have to select yes both times and it will reboot to recovery. If it doesn't then start over with the auto recowvery. Also, it is very important that you download twrp and copy it to your internal storage on the root. Also, once it is there you have to name it to recovery. Don't use the .img when renaming it because you end up with recovery.img.img... Sometimes it takes a few tries on the recowvery method... Hope this helps!
Click to expand...
Click to collapse
well ive used
- "adb reboot recovery"
- hardware keys ( whenever i do this it wipes the phone ) , so i wont be trying that much cause i have stuff on it now , phones not encrypted tho
ive tried all 4 versions of twrp and renamed them all , countless times ive tried everything ive searched and read
When you first get into TWRP for the very first time, I believe it is a must to "FORMAT DATA" before you flash supersu and 'no-verify' zips
dtgo said:
well ive used
- "adb reboot recovery"
- hardware keys ( whenever i do this it wipes the phone ) , so i wont be trying that much cause i have stuff on it now , phones not encrypted tho
ive tried all 4 versions of twrp and renamed them all , countless times ive tried everything ive searched and read
Click to expand...
Click to collapse
I know this might sound silly, but have you extracted the twrp file and then renamed it to recovery? Have you tried downloading on your phone and then extracting it on your phone and then renaming it? After I looked at the image you shared it seems like the flash seems to have an error and the only thing that makes any sense to me is a bad download of twrp or an unextracted version. I've ran into that error before and it drove me nuts until I figured it out...
poog said:
When you first get into TWRP for the very first time, I believe it is a must to "FORMAT DATA" before you flash supersu and 'no-verify' zips
Click to expand...
Click to collapse
well ive been working to get to this screen it NEVER happens , i already know im set when im there
the phone isnt encrypted so i know i wont have to format data , since , format data removes encryption
speters04 said:
I know this might sound silly, but have you extracted the twrp file and then renamed it to recovery? Have you tried downloading on your phone and then extracting it on your phone and then renaming it? After I looked at the image you shared it seems like the flash seems to have an error and the only thing that makes any sense to me is a bad download of twrp or an unextracted version. I've ran into that error before and it drove me nuts until I figured it out...
Click to expand...
Click to collapse
ive tried both your suggestions plus more
copied to the phone and renamed
downloaded on the phone then renamed
dowloaded on pc and renamed then copied to phone
used adb to push and rename to phone
still having challenges with this
do you think its a dead case guys
OP isn't the only one with this hair-pulling problem...I too downgraded a new H830 from 20M (? I can't remember which one exactly since I've LG-Uppercutted 20A and troubleshooted this constant problem so many times now)---I get the exact same error as OP, also with the highly suspicious 'greyed-out OEM Unlock' (in the Developer Options of the Settings).
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,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.