Related
Ok, so I was running a custom ROM (I don't even recall which specific one at the moment....one of the Cromi ROMs). I tried to wipe it and install a new version, and the install didn't go as smoothly as planned. I can still load the TWRP recovery system, and begin attempting to install any ROM, but when it gets to the point where it says it's installing, the bar across the bottom that should show progress disappears almost instantly and the next button becomes available. When I go to reboot, it warns that there is no OS installed. Of course if I continue anyway, it won't boot beyond the Asus splash screen. There are errors in multiple places saying that it can't mount /system. I saw this error in the log file generated, I saw it during reboot, and there was some point in the TWRP screens where I saw it, but can't recall where at this moment. If I go into the Mounts section, System is not checked and I cannot check it.
I tried following the instructions on the unbricking thread and got stuck. I fear this has likely only made matters worse.
Following these steps:
Code:
fastboot erase boot
fastboot erase staging
fastboot format system
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery.img
fastboot reboot-bootloader
I was able to successfully erase the partitions mentioned, then when I tried to flash the first time, I actually screwed up and didn't have the blob file I needed, so now I go back, and obviously I can't re-erase the other files, but formatting system still works, so I know I'm getting good communication with the device. Then trying to flash the blob to staging, I get:
sending 'staging' (1379 KB)...
FAILED (command write failed (No such device or address))
Any thoughts or suggestions would be greatly appreciated. I've currently got an expensive paperweight.
This is my Situation:
I was using a ROM Based in Android 5.1.1 in specific ([5.1.1_r29] Team Razor), everything was good but I read that I had to update bootloader and radio but never saw a link, looking for internet for help found this GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip version to install via RSD Lite, everything was good, but when I tried to flash the recovery I get that I couldnt flash it 'cuz is not compatible:
Code:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
My device start normally, but I want too install the Recovery and root it, I couldnt find any information about my problem or a real solution.
I've read about flash a system.img but what "system.img"?, I'm looking for some help, if anyone pass thru this and have the answer would be awesome if you share it.
Thank you in advance.
[SOLVED]
Unzip mfastboot.exe into \platform-tools\
flashing: mfastboot flash recovery recovery.img
done!
The info in your post is kind of confusing. What does ghost_retail*.xml.zip have to do with looking for a custom recovery which is what I am guessing you want on your "working" device? All you could get out of the .xml.zip file would be something like stock_recovery.img which wouldn't allow you do recoveries. Sounds like you want to download TWRP (or Philz) from somewhere and boot into fastboot mode, then use "fastboot flash recovery {whatever_recovery.img}" to flash the custom recovery.
If that's not your intent then post back and try to explain better. It seems like you had things "working well" on TR511 but still decided to update BL & Rad anyway. There's no need to update anything if it's all working OK and there's no new features (like a working speakerphone or something) in there for you.
Also: the 'reported output' in your
Code:
section is pretty inconclusive for troubleshooting. It almost sounds as if you tried to flash (or RSDLite) something huge like the entire image (805,306,368 bytes?). I've built lots of recoveries and they average more like 5-10MB. , not 800MB. Also it says something about "battery low" in there. I'm lost on that output ;;)
And another note: System.img has little or nothing to do with getting recovery back together. It's just the packed up version of /system/.... in the "SYSTEM" partition.
Maybe for starters: tell us once again what ROM is working right now including version. Then tell us what recovery you want to flash. Someone can likely help out if we know those things. You appear to have unlocked BL since you're flashing ROMs so there's hope.
Anyway, good luck.
[QUOTE="Mexickano, post: 64350799, member: 4488447"]This is my Situation:
I was using a ROM Based in Android 5.1.1 in specific ([5.1.1_r29] Team Razor), everything was good but I read that I had to update bootloader and radio but never saw a link, looking for internet for help found this[B] GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip[/B] version to install via RSD Lite, everything was good, but when I tried to flash the recovery I get that I couldnt flash it 'cuz is not compatible:
[code](bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
My device start normally, but I want too install the Recovery and root it, I couldnt find any information about my problem or a real solution.
I've read about flash a system.img but what "system.img"?, I'm looking for some help, if anyone pass thru this and have the answer would be awesome if you share it.
Thank you in advance.[/QUOTE]
I was on 5.1.1 and downgraded to 5.1 stock, everything ok till now?
when I'm trying to flash TWRP this appears
Code:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
Mexickano said:
I was on 5.1.1 and downgraded to 5.1 stock, everything ok till now?
when I'm trying to flash TWRP this appears
Code:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
Click to expand...
Click to collapse
Thanks. I'm assuming the battery low message is just a confused response and not really true? Also, I see that the recovery.img (whatever you are calling TWRP) is ~8.5MB which seems fine. It looks like fastboot on the PC (whatever) isn't happy talking to the xt1053 booted into fastboot/bootloader. Could you try doing a "fastboot devices" and show the output back here? If it's anything other than an OK ID number for the device, then it might be interesting.
I'll attach a version of fastboot I just recently used to flash a recovery in case you want to try it.
Another thing: I've never had this happen myself, but have heard about it a few times: When booted, use some explorer to look in your /system folder for a file with a name like this "recovery-from-boot.p". If it's there, supposedly it will keep forcing the default non-custom recovery to be written regardless of what you do. I'm sure there's a work-a-round for that like ..
What about using the "Fastboot boot "your-custom-recovery.img" if you have that "recovery-from-boot.p" problem? It should take you into the recovery you're trying to write without bothering to write it to the recovery partition. From there, you would be root if you can open the TWRP console, and get rid of the recovery-from-boot.p file, install root, etc, then finally, flash recovery with whatever combination of stuff ^^ it takes.
hachamacha said:
Thanks. I'm assuming the battery low message is just a confused response and not really true? Also, I see that the recovery.img (whatever you are calling TWRP) is ~8.5MB which seems fine. It looks like fastboot on the PC (whatever) isn't happy talking to the xt1053 booted into fastboot/bootloader. Could you try doing a "fastboot devices" and show the output back here? If it's anything other than an OK ID number for the device, then it might be interesting.
The battery message is because the Battery is low, that's it, no big deal.
I can boot into fastboot w/o issues and I will post back the result of "fastboot devices".
I'll attach a version of fastboot I just recently used to flash a recovery in case you want to try it.
how can I use it, excuse my ignorance, but I see a .exe inside a .zip
Another thing: I've never had this happen myself, but have heard about it a few times: When booted, use some explorer to look in your /system folder for a file with a name like this "recovery-from-boot.p". If it's there, supposedly it will keep forcing the default non-custom recovery to be written regardless of what you do. I'm sure there's a work-a-round for that like ..
What about using the "Fastboot boot "your-custom-recovery.img" if you have that "recovery-from-boot.p" problem? It should take you into the recovery you're trying to write without bothering to write it to the recovery partition. From there, you would be root if you can open the TWRP console, and get rid of the recovery-from-boot.p file, install root, etc, then finally, flash recovery with whatever combination of stuff ^^ it takes.
Click to expand...
Click to collapse
There's a "recovery-from-boot.p" but I cant delete it or change the name because I'm not root, can I be root without installing Recovery?
Mexickano said:
There's a "recovery-from-boot.p" but I cant delete it or change the name because I'm not root, can I be root without installing Recovery?
Click to expand...
Click to collapse
Should be able to work around that, but the workaround is to find a way to become root, so I was mentioning this in the last post of mine:
What about using the "Fastboot boot "your-custom-recovery.img" if you have that "recovery-from-boot.p" problem? It should take you into the recovery you're trying to write without bothering to write it to the recovery partition. From there, you would be root if you can open the TWRP console, and get rid of the recovery-from-boot.p file, install root, etc, then finally, flash recovery with whatever combination of stuff ^^ it takes.
Click to expand...
Click to collapse
I'm trying to think of ways to do this above and I think that is actually one of them and there should be another way as well.
Way one: There's a fastboot command "fastboot boot "{name-of-your-recovery-img-for-twrp}". That command causes it to boot (well, if all goes well) into recovery without writing recovery. If it works, you're a root user because that's how recovery is. In TWRP, I'm sure there's a console command as well as a file explorer or some kind. You'll have to remount as read-write /system partition. From a console it'd look like this "sudo mount -o remount,rw /system" (I'm pretty sure that's it). You can look it up or try it with a w where the rw is right now. Also you can just do a plain "mount" command and look at the output to see what it's mounted as in case you need it.
If you get into whatever file explorer twrp has available, then navigate to that file 'recovery_from_boot.p' and see if the file system is in read-write mode by trying to rename it (like to recovery_from_boot.p.orig). If that doesn't work, then go to the special commands or advanced (sorry, not recalling twrp that well) and mount /system as read-write whatever that takes, like an unmount & a mount. Then go back to file explorer and do the rename. I hate deleting files I'm not 100% sure about, but you can do what you like there.
Way two: If you can boot into the version of twrp.img on your PC, then I'm not seeing why you can't install root from it too. Worth a try. You might have some other remaining problem between whatever fastboot you've got on the pc and the bootloader, but it's worth a shot. There's a number of write-ups on how to do this if you google it. Anyway, once you've rooted you can reboot and you should only lose recovery, not root. Once booted, install supersu, etc. usual stuff, then if it all checks out, flash the recovery and it should stay once you've dumped that file.
Way two and a half: If I understand how the normal boot works on androids, then you should be able to avoid having recovery erased at least one time by using the buttons either to go directly to recovery (volume_up + power) or (volume_down+volume_up + power) RIGHT after you flash recovery. I'm just thinking that /system isn't going to execute if you pick the right combo of buttons to get into recovery but it'll be a pita because you have to burn recovery then hit it on the first boot after or it's gone.
Cheers.
hachamacha said:
Way one: There's a fastboot command "fastboot boot "{name-of-your-recovery-img-for-twrp}". That command causes it to boot (well, if all goes well) into recovery without writing recovery. If it works, you're a root user because that's how recovery is. In TWRP, I'm sure there's a console command as well as a file explorer or some kind. You'll have to remount as read-write /system partition. From a console it'd look like this "sudo mount -o remount,rw /system" (I'm pretty sure that's it). You can look it up or try it with a w where the rw is right now. Also you can just do a plain "mount" command and look at the output to see what it's mounted as in case you need it.
there is a "recovery-from-bot.p", I cant delete it, rename it or anything else since I aint get root privileges.
I can get into fastboot and when I type fastboot devices I get:
TA0000143X fastboot
If you get into whatever file explorer twrp has available, then navigate to that file 'recovery_from_boot.p' and see if the file system is in read-write mode by trying to rename it (like to recovery_from_boot.p.orig). If that doesn't work, then go to the special commands or advanced (sorry, not recalling twrp that well) and mount /system as read-write whatever that takes, like an unmount & a mount. Then go back to file explorer and do the rename. I hate deleting files I'm not 100% sure about, but you can do what you like there.
Way two: If you can boot into the version of twrp.img on your PC, then I'm not seeing why you can't install root from it too. Worth a try. You might have some other remaining problem between whatever fastboot you've got on the pc and the bootloader, but it's worth a shot. There's a number of write-ups on how to do this if you google it. Anyway, once you've rooted you can reboot and you should only lose recovery, not root. Once booted, install supersu, etc. usual stuff, then if it all checks out, flash the recovery and it should stay once you've dumped that file.
I cant boot into recovery because I can't flash the Recovery, that's the reason why I created this topic because I CANT flash recovery.
Way two and a half: If I understand how the normal boot works on androids, then you should be able to avoid having recovery erased at least one time by using the buttons either to go directly to recovery (volume_up + power) or (volume_down+volume_up + power) RIGHT after you flash recovery. I'm just thinking that /system isn't going to execute if you pick the right combo of buttons to get into recovery but it'll be a pita because you have to burn recovery then hit it on the first boot after or it's gone.
I cant get into Recovery because there is no Recovery flashed.
What about that fastboot.zip, how I flash it or install it because I see a fastboot.exe inside the zip.
Cheers.
Click to expand...
Click to collapse
I need to know if there's a way to flash another bootloader or anything else?
If I try to delete the "recovery-from-boot.im" in fastboot this message appear:
X:\Android\sdk\platform-tools>fastboot erase /system/recovery-from-boot.img
(bootloader) Variable not supported!
erasing '/system/recovery-from-boot.img'...
(bootloader) Invalid partition name /system/recovery-from-boot.img
FAILED (remote failure)
finished. total time: 0.094s
FINALLY!!
I solved putting mfastboot.exe into /platform-tools/ and typing
mfastboot flash recovery [recovery].img
Thank you for your effort and time.
Mexickano said:
I need to know if there's a way to flash another bootloader or anything else?
If I try to delete the "recovery-from-boot.im" in fastboot this message appear:
X:\Android\sdk\platform-tools>fastboot erase /system/recovery-from-boot.img
(bootloader) Variable not supported!
erasing '/system/recovery-from-boot.img'...
(bootloader) Invalid partition name /system/recovery-from-boot.img
FAILED (remote failure)
finished. total time: 0.094s
FINALLY!!
I solved putting mfastboot.exe into /platform-tools/ and typing
mfastboot flash recovery [recovery].img
Thank you for your effort and time.
Click to expand...
Click to collapse
Cool! I think I also was trying to say "try other versions of fastboot" (like mfastboot). Good deal.
Hi everyone.
I am having a problem getting my atrix hd to load stock rom.
I have downloaded the stock att rom (MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml_.zip)
I use fastboot and the sd card to install cm roms but this does not work it says (installing update... then installation aborted...)
What i dont understand is what to do with the xml file before i flash it. Or do i flash multiple files from the xml.
Any help or a point in the right direction would be greatly appreciated.
Another acceptable fix would to be able to unlock my network from cm 10.1 everything i have read says it cant be done but i dont see why.
Follow up
Ok so I found that the .xml file can be loaded with RSD lite in windows. Since I use linux I found the script for flashing xml files with fastboot from root junkie. I followed the instructions and got it to start flashing. During the first file upload it returns an error md5 mismatch. So I found another "stock" image and tried again to the same end. I then compared the md5 sums to the ones in the .xml file and they are correct so there downloading to the pc fine.
Today I borrowed a windows computer and downloaded RSD lite and the "stock" roms. When RSD tries to flash to the phone I get the same md5 mismatch but it adds "phone returned fail". I can still flash back to cwm useing fastboot and boot in to cm just like before I started this.
Any ideas as to why the stock images won't flash?
I'm beginning to wonder if the usb cable could be questionable. Is it posable that it may load cwm over a kinda bad cable?
I tried removing the md5 sums from the xml file. It then flashed to the device with a few errors. Now the phone just boots directly to fastboot it says reason flash fail. But now I can't flash cwm back I keep getting FAILED (data transfer failure (value too large for defined data type)).
Now I have bought another motorola atrix hd rooted ubl and installed cwm. I created a zip of its image from cwm and installed it on my old atrix. I know thats a little much to have to do but i couldnt find a working image for the atrix hd. Now the phone comes on and most things work good But I have now LTE radio no WiFi and no bluetooth they worked in cm before all of the trying to get back to stock. Im not sure if the problem was caused by the install from the cwm zip or from some of the messing around i did first. I have found info about flashing "NON-HLOS.bin" but when i try i get the following.
$ fastboot flash modem NON-HLOS
.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28172 KB)...
OKAY [ 2.509s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 4.414s
I have read that there is a special mfastboot for windows but i only have ubuntu. I suppose this could be why the flash from RSD for linux didnt work. Could that be possible?
Am i going to have to get a windows computer to do this?
After trying to reboot post failure of modem flash I had fastboot forced because of a failed flash. I tried to flash the logo file from the same image as the modem file and the logo worked fine then the phone booted fine but still no radios
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Or just use the MSM tool. Job done
All with varying levels of interpretation, steps, descriptions, and the solution. Not all are useful.
I had the same issue and this worked perfectly to get my device up and running again. Thanks again!!
Hi all!
Here is plan B!
First of all - BEFORE you do some upgrade - make OPSwitch backup and copy to PC !!!!!
If you stuck - it's mean that something is badly damaged and wrong. Some of the files reside in the areas where upgrade tools (including Fastboot!) can't change and repair them.
We don't have time, knowledge to sort out WHAT was damaged.
We make all straight from beginning:
1. MSM tools - make your phone like from the Factory with "clean" install (ver 9 for now)
2. "FlashAll" то ver 10E
3. If you need - install "global"
4. If you need - install TWRP and Magisk
5. Restore your backup from PC
At the end you will have "clean" phone with all programs working
EASY!!!
Same as OP, I wanted to flash twrp.img.
I had my OP7Pro stuck in 'fastboot mode', I thought. It wouldn't respond to any commands from console (device not found) and I couldn't turn it off with the power button any more.
For noobs, just like me, I learned that I just had to press the powerbutton + volume up button. My phone rebooted after this.
Now making a backup before rooting and such, phew.
vegatr0n
I was stuck in Fastboot after switching slots. Excelent stuf! 2,3 clicks , done! Thank you!
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Many people have found this problem. Thank you, I am working again.
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
nitinvaid said:
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
Click to expand...
Click to collapse
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
vegatr0n said:
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
Click to expand...
Click to collapse
Nope...
I was able to reboot holding both vol+ and - and power
I bricked my tmobile oneplus 7 pro and dont know which file is safe to try can anyone please point me in the right direction?
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
moonbosques said:
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
Click to expand...
Click to collapse
Sounds like you're having problems with Windows Defender. I also got the same error messages suddenly once week ago. I did sfc /scannow and all that but all files were intact. After rebooting the PC two times the problem was gone, really strange.
Skickat från min GM1913 via Tapatalk
Anyone here know what fastboot rom i can use to fix my bricked tmobile oneplus 7 pro?
Can you explain this strange effect, please
pitrus- said:
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
Click to expand...
Click to collapse
After an update to Android Q twrp an root was lost.
I was going the normal way like this:
1. In fastboot boot twrp.img
2. In twrp install twrp.zip
3. Reboot to twrp
4. In twrp install magisk.zip
After this the phone stuck a while on this orange splash screen and then reboot to bootloader.
Reboot --> the same effect
Then:
1. Boot into twrp
2. install twrp.zip
3. Reboot system
Everything ok, but no root
Just one method is working for me:
1. Download the full package of OOS 10.x.x
2. Extract the boot.img
3. Patch boot.img with Magisk
4. Flash on fastboot boot magisk_patched.img
5. reboot
My phone is rooted now but without twrp.
Why can twrp an Magisk not work together?
And why I can´t find any information for this problem on the internet?
Well, since TWRP lives in the boot partition on this phone, you will have to boot TWRP using fastboot boot TWRP. Then you flash the unofficial TWRP build 74 installer zip downloaded from the link below (the one from twrp.me only works on OOS 9 and not 10). Reboot phone back into Magisk to switch slot, flash Magisk installer zip which will then install Magisk to both boot slot a and boot slot b. Reboot phone and you should have both Magisk root and working TWRP.
https://r.tapatalk.com/shareLink/to...2&share_fid=3793&share_type=t&link_source=app
Skickat från min GM1913 via Tapatalk
Fails anyway
Bricked my OnePlus and now I'm left with bootloader (no os, no twrp). Everything leads back to bootloader. Any attempts to apply fastboot boot lead to "Load Error". Now I tried with that tool and ended up with this:
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odb_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
P.S. Full log:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e434a4c8
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: я╗┐require product=msmnile
Setting current slot to 'b' OKAY [ 0.002s]
extracting boot.img (96 MB) to disk... took 0.776s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.389s]
Writing 'boot_b' OKAY [ 0.406s]
extracting dtbo.img (16 MB) to disk... took 0.151s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.393s]
Writing 'dtbo' OKAY [ 0.047s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.395s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
I am getting this error, any ideas what is going wrong? (please see attachment)
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Hi,
When I download I cant find it on my downloads. I have to go into my files app then I can find the zip there. And when I try patch it, it says "unknown image format". Therefore the installation fails.
How can I fix this. I also haven't been able to install TWRP.
thanks
What zip file? Do you mean the Magisk installation zip? You can't use that unless you're already rooted (and then you need to install it from the modules section of the Manager) or through TWRP. But if you're already rooted it's easier to just do a direct install from the Manager anyway.
The patch file option in the Manager is for a boot or recovery image (depending on what device you have, see the installation instructions).
twrp
thanks for your reply.
Im also having trouble with installing twrp. I have unlocked the bootloader on my huawei p8 lite 2017 and have downloaded all the tools and flash img needed to flash it. However when use command " fastboot flash recovery twrp-3.4.0-0-prague.img" it says:
Sending 'recovery' (13458 KB) OKAY [ 0.532s]
Writing 'recovery' OKAY [ 0.340s]
Finished. Total time: 0.909s
then when I use " fastboot boot twrp-3.4.0-0-prague.img" it says
Sending 'boot.img' (13458 KB) OKAY [ 0.500s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
How can i fix this. Thanks in advance.
The recovery seems to have installed correctly, so instead of running the command to boot the image, try just using the option directly in the bootloader (usually navigated to by using the volume keys) to boot into recovery.
Didgeridoohan said:
The recovery seems to have installed correctly, so instead of running the command to boot the image, try just using the option directly in the bootloader (usually navigated to by using the volume keys) to boot into recovery.
Click to expand...
Click to collapse
Hi,
When i boot into recover I get another error which is as follows:
ERROR MODE
ATTENTION!
PLEASE UPDATE SYSTEM AGAIN
(Green android bot image)
ERROR!
Func NO : 11 (recovery image)
Error NO : 2(load failed!)
Thanks
You need to take this to your device's forum. That's the best way to get help with stuff like this...
Judging by this thread, you're using the wrong command:
https://forum.xda-developers.com/p8...nt/recovery-twrp-huawei-p8-lite-2017-t4113153