(((SOLVED)))bricked phone failed <remote: sparse flash write failure> - Huawei P9 Questions & Answers

Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it

IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
I'm having the same issue on my P9 Plus. Did you manage to fix it somehow?

Command not allowed = bootloader is NOT unlocked. But maybe the bootloader shows "unlocked" but it isnt.
WHat you should try:
Rollback to Marshmallow via Dload method (sdcard needed)

xtcislove said:
Command not allowed = bootloader is NOT unlocked. But maybe the bootloader shows "unlocked" but it isnt.
WHat you should try:
Rollback to Marshmallow via Dload method (sdcard needed)
Click to expand...
Click to collapse
I don't think this would work since all of this happened because I tried to overwrite both recovery and recovery2 with twrp which ended up soft bricking my phone. So basically the only thing that would flash is the recovery, recovery2 and boot images.

felroric said:
I'm having the same issue on my P9 Plus. Did you manage to fix it somehow?
Click to expand...
Click to collapse
Yes, I did.
You have to flash the same version of Android you wiped before.
It happened with me when I wiped N system then I tried to install MM, the solution was just flash N system.

IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
What is your BULID NUMBER?
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
You get error every time cause your frp is lock

Rafa Mistry said:
What is your BULID NUMBER?
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
You get error every time cause your frp is lock
Click to expand...
Click to collapse
My build number before wiping was L19C185B385
Yes, I know that but it wasn't because of Locked FRP it was because of installing MM software without installing the rollback package

IDontKnowAnythingAtAll said:
My build number before wiping was L19C185B385
Yes, I know that but it wasn't because of Locked FRP it was because of installing MM software without installing the rollback package
Click to expand...
Click to collapse
Your twrp is installED?

Rafa Mistry said:
Your twrp is installED?
Click to expand...
Click to collapse
Well, My phone is working now. But yeah I had twrp

IDontKnowAnythingAtAll said:
Well, My phone is working now. But yeah I had twrp
Click to expand...
Click to collapse
I have the same problem. How did you fix it?

Related

Problems with VZW Developer Edition Rooting

Please bare with me, I am probably a "C" student in the knowledge of this stuff. I've successfully rooted and rom'd the Galaxy Nexus many times but I'm having trouble with the new Moto X.
I unlocked without issue
Tried to follow the TWRP instructions (which clearly assume some existing knowledge). Not quiet sure what happens with Mfastboot but I got that from a download.
The TWRP flash failed. Can't remember the exact message but I think it was a binary size error.
Now the phone will not boot at all, it just goes back to the bootloader.
I am currently running the repair from the Motorola Device Manager and then I'll have to start again.
So what might be wrong ?
Bricked for a second time.
Here is the error
C:\MOTOX>mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
sending 'recovery' (7 KB)...
OKAY [ 0.238s]
writing 'recovery'...
Invalid boot image
FAILED (remote failure)
finished. total time: 0.518s
homemadehitshow said:
Bricked for a second time.
Here is the error
C:\MOTOX>mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
sending 'recovery' (7 KB)...
OKAY [ 0.238s]
writing 'recovery'...
Invalid boot image
FAILED (remote failure)
finished. total time: 0.518s
Click to expand...
Click to collapse
The img file should not be 7 KB. It's around 9 MB. Make sure that you have left clicked the link for the file from the other thread and go to the goo.im page. Then download from there. If you try to right-click the link and "save as", you'll get that 7 KB file.
thesourgin said:
The img file should not be 7 KB. It's around 9 MB. Make sure that you have left clicked the link for the file from the other thread and go to the goo.im page. Then download from there. If you try to right-click the link and "save as", you'll get that 7 KB file.
Click to expand...
Click to collapse
This.
Make sure your bootloader is unlocked and that you have the 4.4 compatible twrp file downloaded (check md5). Sounds like you've got the bootloader part done but do not have the recovery file rather you've saved the link.
Sent from my XT1060 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2534850
There he has the file you'll need. It should be about 9.62 MB in size. Be sure to compare the MD5 with the one on goo.im: cb7808078a6746dc87e6eaeb4f145dc0
Yes, file size was wrong and it worked after I redownloaded it.
Thanks.

Mate S no OS Installed

hello,excuse me for my english but i have an problem with my mate s.firmware installed is b145 europe and after i unlock the bootloader and frp i have root and installed twrp.after this operation i have disable option developer in setting and i reboot in twrp for advanced wipe without internal storage.
my phone is in bootloop logo huawei.i have put the dload directory but not work in the recovery stock..return Always on twrp recovery.volume+ ,+ vol- and power go into fastboot mode but not accept command for flash boot.img recovery.img and etc etc because frp is locked!
i'm desperate...please help me..i have used twrp 2.8.7.0 and supersu 2.49..memory of internal storage is 24.7 gb free..i think the system is intact!!thanks
can you reach twrp?
if so, then reboot into bootloader through twrp..then in bootloader you can flash the stock boot.img and recovery.img of the b145..
after that you should be able to reboot normal..
Gesendet von meinem Mate S CRR-L09 B321
Thanks for your support..yes i can reach in twrp and in the bootloader..but My answer is :must i do flash of stock boot.img and recovery.img through fastboot e rescuemode?if so i made it yet and it doesnt work because frp is locked and i have return error with adb fasttool!!
SuperSU 2.42
frisko76 said:
hello,excuse me for my english but i have an problem with my mate s.firmware installed is b145 europe and after i unlock the bootloader and frp i have root and installed twrp.after this operation i have disable option developer in setting and i reboot in twrp for advanced wipe without internal storage.
my phone is in bootloop logo huawei.i have put the dload directory but not work in the recovery stock..return Always on twrp recovery.volume+ ,+ vol- and power go into fastboot mode but not accept command for flash boot.img recovery.img and etc etc because frp is locked!
i'm desperate...please help me..i have used twrp 2.8.7.0 and supersu 2.49..memory of internal storage is 24.7 gb free..i think the system is intact!!thanks
Click to expand...
Click to collapse
Try flashing SuperSU 2.42 from TWRP and see if you´re able to boot. When I installed versions newer than 2.45 I ended up in bootloop.
Edit: Sorry, I mean 2.62 is the right one and over 2.65 will end up in loop. Anyway, try 2.62.
ok..i try this way to install supesu 2.62..this screenshot is result when i reboot into bootloader trought twrp..i not understand because i have this error :command not allowed
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>fastboot flash boot bo
ot.img
target reported max download size of 471859200 bytes
sending 'boot' (23552 KB)...
OKAY [ 0.632s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.632s
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>fastboot flash recover
y recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31372 KB)...
OKAY [ 0.855s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.865s
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>
excuse me but i not post an image!
i have tried to install supersu 2.62 but return message error no os install and the device not have supersu do you want to install??i already installed supersu and i have this message after?..i tried to install supersu 2.75 and i have only the message no os installed..but the phone are same in bootloop....can i search an tool for erase frp tool?for Samsung exist and for sony experia..for huawei?
hello,i verified only method for resume device is use dc unlocker for price 15credit... ...but i have an other idea..i have an other huawei mate s,original stock recovery..can i try to unlock bootloader and developer option , install twrp and try backup for use in the other device ???..is same firmware b145 eu...it could be right way for resume my device?thanks

Potentially Bricked Device, Help please!

Hello, I'm really hoping someone can offer me some assistance with this issue.
I currently have a rooted P9 but had some issues earlier which resulted in the /data partition being unable to be mounted. I have tried everything I have read online to attempt to fix this. I cannot format or advanced wipe in TWRP, I am unable to wipe through bootloader and I have no idea what to do now. I am still able to boot to system but cannot flash stock rom or format partitions. The data partition is in the f2fs format which I believe means that it is encrypted. I have installed this recovery and am still having the same issues, I can't think of anything else I can do so I am open to any suggestions or support. I have the latest TWRP installed.
When trying to flash stock recovery I get
"target reported max download size of 471859200 bytes
sending 'recovery' (35180 KB)...
OKAY [ 0.744s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.750s"
However when I managed to install stock earlier it said that there was an error getting the package info failed. I don't know what has changed but it now won't allow me to flash recovery whereas it would before.
Thanks!

HELP! Pixel (sailfish) bricked? after OTA and Magisk Update

Hi All,
So this morning I got 2 nags on my phone... 1) for the Android February Security Update to 9.0, and 2) for the Magisk Manager Update to 7.0.0
I followed this procedure (newbie alert!) to update both of them...
1. Magisk Manager → Uninstall → Restore Images. Do not reboot or you will have Magisk uninstalled.
2. Update the system and let it install completely. Do not press the reboot button.
3. Magisk Manager → Update → Install to Inactive Slot for OTA.
4 Once Magisk installation is done, press the reboot button in Magisk Manager.
When I did this, I got the white boot screen with the G Google logo, and then the screen went black.
I waited, and waited.
I used the fingerprint to unlock the screen... nothing.
I pressed the power button to turn on the screen... nothing.
I waited.
I then held the power butoon for freaking ages and then it rebooted back to the usual unlocked bootloader warning and did the same thing again.
HELP! please!
Paully
Pixel (sailfish) stock Android 9.0 with Magisk and Titanium Backup Pro root
OK, I have managed to get the phone up-and-running by ...
1. Hold buttons (Power + VOL DOWN) to get in to the bootloader.
2. USB cable > fastboot devices
3. USB cable > fastboot boot twrp-3.2.3-1-sailfish.img
4. TWRP > Reboot > Slot A
...and the phone seems fine.
I can reboot it as normal.
However, I cannot reboot to Recovery... seem to have lost TWRP, which I can reinstall again.
However, I am going to wait until I get a reply first.
Paully
I know that Magisk has OTA support.
As a sailfish owner too, I remember when Pixels were not supported by Magisk OTA system, I just get used to flash it manually in a 5 minutes procedure.
All I always do is flash the new factory image (removing the "-w" at the bottom line of the flash-all script, so it will upgrade without wiping) and then simply fastboot boot twrp and reflash magisk.
Never had a single problem doing this. I don't know what guide you followed, but the procedure you did looks like correct.
If you prefer this automatic way, try follow the official guide that topjohnwu made.
Hope it helps
As far as I know (I don't own a device where this is applicable), it's still recommended to not install TWRP at the same time as Magisk on A/B devices. Since they both alter the boot image, you might end up with issues like bootloops. Only boot TWRP...
It's not certain that this was the source of your issue, but it's one possibility. Other possibilities might include modules that are incompatible with the update, etc.
Other than that, the official docs linked above should work fine.
TENN3R said:
I know that Magisk has OTA support.
As a sailfish owner too, I remember when Pixels were not supported by Magisk OTA system, I just get used to flash it manually in a 5 minutes procedure.
All I always do is flash the new factory image (removing the "-w" at the bottom line of the flash-all script, so it will upgrade without wiping) and then simply fastboot boot twrp and reflash magisk.
Never had a single problem doing this. I don't know what guide you followed, but the procedure you did looks like correct.
If you prefer this automatic way, try follow the official guide that topjohnwu made. Hope it helps
Click to expand...
Click to collapse
Thank for the tip about editing the ./flash-all script to remove the -w ... neat.
More research is required, as am new to Magisk, but the second poster to reply to this has mentioned that TWRP and Magisk do not sit well together, and it never occurred to me that I don't really need TWRP actually installed, if I can always get to a laptop and USB cable!
Thanks for your reply... I dunno, the things we do to keep stuff "easier".
Paully
Didgeridoohan said:
As far as I know (I don't own a device where this is applicable), it's still recommended to not install TWRP at the same time as Magisk on A/B devices. Since they both alter the boot image, you might end up with issues like bootloops. Only boot TWRP. It's not certain that this was the source of your issue, but it's one possibility. Other possibilities might include modules that are incompatible with the update, etc. Other than that, the official docs linked above should work fine.
Click to expand...
Click to collapse
Thanks for your reply.
Now I think about it, as long as I can get to my laptop and a USB cable, I don't need to _install_ TWRP if I need to do stuff.
So, the Pixel with 9.0 is currently in this state...
* SLOT A with Security Patch level: 5 December 2018
* Magisk patched boot image not installed
* TWRP not installed?
* Magisk Manager app installed
I think SLOT B is broken?
How do I do this properly? Are there STEP BY STEP instructions somewhere?
Do I uninstall TWRP, or is it already hosed when Magisk 'restored images' and then 'patched'???!
Yours, a bit worried...
Paully
plittlefield said:
Thank for the tip about editing the ./flash-all script to remove the -w ... neat.
More research is required, as am new to Magisk, but the second poster to reply to this has mentioned that TWRP and Magisk do not sit well together, and it never occurred to me that I don't really need TWRP actually installed, if I can always get to a laptop and USB cable!
Thanks for your reply... I dunno, the things we do to keep stuff "easier".
Paully
Click to expand...
Click to collapse
That's right, since december (I think?) looks like Magisk and TWRP have some incompatibilities, before I always flashed them together with no problems at all.
A useful "trick" about flashing without a pc would be using Franco Kernel manager, as he added support for a flasher even without having twrp installed. Just select the zip and tap on flash. That's kinda magical.
Of course for this you need to buy his app, but as of today it's a pretty universal kernel manager, not only restricted for his kernel. I find it very useful.
TENN3R said:
That's right, since december (I think?) looks like Magisk and TWRP have some incompatibilities, before I always flashed them together with no problems at all.
Click to expand...
Click to collapse
OK, so what do I do now to remove Magisk, TWRP and then start again?
plittlefield said:
OK, so what do I do now to remove Magisk, TWRP and then start again?
Click to expand...
Click to collapse
Seriously, a web page on this very problem!
https://magiskroot.net/uninstall-magisk-module-twrp/
plittlefield said:
Seriously, a web page on this very problem!
https://magiskroot.net/uninstall-magisk-module-twrp/
Click to expand...
Click to collapse
That particular link is for removing modules through TWRP, so not anything to do with your problem (or have I misunderstood you completely)...
But, I mainly wanted to give a warning: be very wary of any site that has to do with Magisk and isn't directly mentioned by @topjohnwu in the release thread. There are some really scammy sites and take apps out there trying to benefit from Magisk's popularity.
Thanks. I'll not use that site then.
I could do with some help on how to remove both TWRP and Magisk then start again but not installing TWRP.
Cheers anyone!
plittlefield said:
Thanks. I'll not use that site then.
I could do with some help on how to remove both TWRP and Magisk then start again but not installing TWRP.
Cheers anyone!
Click to expand...
Click to collapse
From my understanding (again, remember I have no experience with A/B devices), all you need to do is to flash the stock boot image. Possibly to both slots, but someone that has experience with A/B devices would be a better source of information, or better yet: check your devices forum for info.
Once you have the stock image installed all you need to do is to boot TWRP and flash the Magisk zip.
Understood, that sounds reasonable.
Cheers everyone.
Yep, going back to stock boot image on Pixel are just 2 commands. Extract the boot.img from the stock factory image, then in fastboot:
- fastboot flash boot_a boot.img
- fastboot flash boot_b boot.img
Then reboot
TENN3R said:
Yep, going back to stock boot image on Pixel are just 2 commands. Extract the boot.img from the stock factory image, then in fastboot:
- fastboot flash boot_a boot.img
- fastboot flash boot_b boot.img
Then reboot
Click to expand...
Click to collapse
OK, so I am currently running PQ1A.181205.002.A1, Dec 2018 in Slot A (it won't boot from Slot B)
Do I download the OTA image or the FULL image? I guess they contain the same bootloader image...?
bootloader-sailfish-8996-012001-1811131534.img
Thanks in advance.
Paully
Images are only in the full factory image, not ota.
If you wanna stay on december update, download the december factory image otherwise grab the latest february, edit the script to keep data and flash so it will upgrade everything with no wipes.
If you wanna flash only the december boot image, you can find it in the zip, which is inside another zip in the factory image.
Pay attention, the boot is exactly called "boot.img", I tell you because inside that zip there is another file called "boot-a" or something similar, this is NOT the one you wanna flash
OK, so that worked.
I flashed the February factory image without wipe...
Code:
Sending 'bootloader_a' (32424 KB) OKAY [ 1.401s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 13.421s]
Finished. Total time: 14.934s
rebooting into bootloader OKAY [ 0.042s]
Finished. Total time: 0.193s
Sending 'radio_a' (57140 KB) OKAY [ 2.403s]
Writing 'radio_a' OKAY [ 1.102s]
Finished. Total time: 3.625s
rebooting into bootloader OKAY [ 0.042s]
Finished. Total time: 0.343s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1811131534
Baseband Version.....: 8996-130181-1811270246
Serial Number........: FA69M0304045
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.050s]
Checking version-baseband OKAY [ 0.050s]
extracting boot.img (29 MB) to disk... took 0.178s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (1944 MB) to disk... took 14.619s
archive does not contain 'system.sig'
extracting system_other.img (312 MB) to disk... took 3.222s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB) to disk... took 1.987s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Sending 'boot_a' (29761 KB) OKAY [ 1.301s]
Writing 'boot_a' OKAY [ 0.655s]
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 23.023s]
Writing sparse 'system_a' 1/4 OKAY [ 4.642s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 22.421s]
Writing sparse 'system_a' 2/4 OKAY [ 4.345s]
Sending sparse 'system_a' 3/4 (524284 KB) OKAY [ 22.368s]
Writing sparse 'system_a' 3/4 OKAY [ 4.341s]
Sending sparse 'system_a' 4/4 (418060 KB) OKAY [ 17.867s]
Writing sparse 'system_a' 4/4 OKAY [ 3.545s]
Sending 'system_b' (319668 KB) OKAY [ 13.160s]
Writing 'system_b' OKAY [ 3.048s]
Sending 'vendor_a' (265748 KB) OKAY [ 10.768s]
Writing 'vendor_a' OKAY [ 2.838s]
Setting current slot to 'a' OKAY [ 0.404s]
Rebooting
Finished. Total time: 156.038s
Should I be able boot from Slot B because it doesn't do anything if I try?
Paully
Do I need to worry about using Slot B?
plittlefield said:
Do I need to worry about using Slot B?
Click to expand...
Click to collapse
I never changed slots after a flash, neither selected to which slot flash zips, I think it's all manager by the installer scripts, same for magisk, twrp, kernel, ...
Once you flash and reboot you're ok
TENN3R said:
I never changed slots after a flash, neither selected to which slot flash zips, I think it's all manager by the installer scripts, same for magisk, twrp, kernel. Once you flash and reboot you're ok
Click to expand...
Click to collapse
OK, thanks

I bricked my OnePlus 7 Pro (was stuck and fastboot) and how I fixed it

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

Categories

Resources