Database Users

Cannot flash with Phone flash tools

I messed up my Yoga 2 1050 by trying to load an unlocked boot image from here (http://forum.xda-developers.com/thi...-tab-2-unlocking-daaa-deee-daaa-dooo-t3241260), I have tried using the Phone flash tool with the correct file but it fails at 50%, here is the log attached if anyone can help.
When I first power on a message EFILINK ERROR(image -start-partition 596This partition does not appear to contain a boot image shows up.
Thanks

corasman said:
I messed up my Yoga 2 1050 by trying to load an unlocked boot image from here (http://forum.xda-developers.com/thi...-tab-2-unlocking-daaa-deee-daaa-dooo-t3241260), I have tried using the Phone flash tool with the correct file but it fails at 50%, here is the log attached if anyone can help.
When I first power on a message EFILINK ERROR(image -start-partition 596This partition does not appear to contain a boot image shows up.
Thanks
Click to expand...
Click to collapse
so you got your un-repairable tab back from lenovo
as a reminder, when you attempted to unlock the bootloader instead of the correct fastboot flash ESP 1050f-esp-patched you did a fastboot flash boot 1050f-esp-patched so instead of flashing you ESP partition you flashed the boot one with a (incompatible) ESP image, resulting, of course, in a bricked tab (as now the boot partition contains no valid image to be booted)
as advised, what you did to fix is fine (ie flashing back a stock rom), but you must use this Intel Phone Flash Tool (uninstall your existing one then install the new one) because the one you are using will not complete to flash a lollipop stock rom

Thanks ionioni
I did as you said, removed the old phone flash and installed the "lite" version.
I have run the new one and unfortunately it failed, it seems when the command for 25 second sleep is issued the tablet is taken out of fastboot as the screen shows the android system recovery page then.
I have enclosed the log file.

corasman said:
Thanks ionioni
I did as you said, removed the old phone flash and installed the "lite" version.
I have run the new one and unfortunately it failed, it seems when the command for 25 second sleep is issued the tablet is taken out of fastboot as the screen shows the android system recovery page then.
I have enclosed the log file.
Click to expand...
Click to collapse
when installed the new intel phone tool you must leave the dnx driver checked, install also the other file intelandroiddrv....exe, reboot and try again
if still not working try to flash a kitkat rom (have you restored the bios somehow?)

ionioni said:
when installed the new intel phone tool you must leave the dnx driver checked, install also the other file intelandroiddrv....exe, reboot and try again
if still not working try to flash a kitkat rom (have you restored the bios somehow?)
Click to expand...
Click to collapse
O.K. I'll do as you say
No I have not touched the bios

corasman said:
O.K. I'll do as you say
No I have not touched the bios
Click to expand...
Click to collapse
yeah, i read both logs and you should focus on (re)installing the Phone Flash Tool and drivers (first uninstall the existing and the drivers related and reboot)

ionioni said:
yeah, i read both logs and you should focus on (re)installing the Phone Flash Tool and drivers (first uninstall the existing and the drivers related and reboot)
Click to expand...
Click to collapse
Thank you for your help ionioni, it seems that I have really messed this one up.
I'll try again in the morning and see if I have better luck then.

corasman said:
Thank you for your help ionioni, it seems that I have really messed this one up.
I'll try again in the morning and see if I have better luck then.
Click to expand...
Click to collapse
it's not that hard, come on...
1. uninstall the existing Phone Flash Tool(nvm that you already installed the new one) and the drivers associated from Add/Remove programs and reboot
2. install the new Intel Phone Flash tool and the driver from the zip file linked (unplug the tab from usb before installing), to be sure also install at the end the DnX driver attached (this step is normally not needed as it should be automatically installed when the new Intel Phone Flash tool installation is run)
3. flash using the lollipop stock rom (the one you used so far with (L) at end is ok)
10 minutes for all these operations

I can confirm that information. Today I was installing new rom, and have problem with uploading data. I've installed newer version of Phone Flash Tool LITE instead of classic PFT, and DNx driver and it works good for me

O.K you talked me into it.
Just to be different I tried to do it on my Daughters laptop,and it still failed, it just seems to take it out of fastboot within a second or two of starting.

corasman said:
I tried to do it on my Daughters laptop,and it still failed, it just seems to take it out of fastboot within a second or two of starting.
Click to expand...
Click to collapse
if it fails again, attach the log from the Intel Phone Flash Tool and also detail what is the tab doing during these operations

O.K
I have fresh installed the "lite" tool and all the drivers including the DnX one.
The yoga is put into fastboot by pressing volume up and down together while powering on, this shows fastboot starting,then connect to laptop(tried on two different ones)start "lite" tool and load XML (also tried starting tool before connecting Yoga) file from same folder as files are in, press start to flash and within a second or two the screen on the Yoga change to the Android System Recovery screen and thats how it stays.
The attached log is from my Daughters Laptop.

corasman said:
O.K
I have fresh installed the "lite" tool and all the drivers including the DnX one.
The yoga is put into fastboot by pressing volume up and down together while powering on, this shows fastboot starting,then connect to laptop(tried on two different ones)start "lite" tool and load XML (also tried starting tool before connecting Yoga) file from same folder as files are in, press start to flash and within a second or two the screen on the Yoga change to the Android System Recovery screen and thats how it stays.
The attached log is from my Daughters Laptop.
Click to expand...
Click to collapse
try and start your tab in normal fastboot mode (from the recovery console select 'reboot to bootloader' or use from power off the combo keys Pwr & Vol+ or Pwr & vol- one of these two should bring you to the Fastboot/Droidboot menu) and from there tell me what the ifwi entry says... BLADE_21....

ionioni said:
try and start your tab in normal fastboot mode (from the recovery console select 'reboot to bootloader' or use from power off the combo keys Pwr & Vol+ or Pwr & vol- one of these two should bring you to the Fastboot/Droidboot menu) and from there tell me what the ifwi entry says... BLADE_21....
Click to expand...
Click to collapse
BOOTLOADER VERSION -
IFWI VERSION- Blade_21.86c.004.R23.1504091154 FFD8_IA32_R
SIGNING - ?
SECURE_BOOT - ?
E: No valid installer medium found

corasman said:
BOOTLOADER VERSION -
IFWI VERSION- Blade_21.86c.004.R23.1504091154 FFD8_IA32_R
SIGNING - ?
SECURE_BOOT - ?
E: No valid installer medium found
Click to expand...
Click to collapse
ok, somehow your bios is (still) a kitkat version (sure you didn't restored the bios using the restore bios tool? or lenovo did? nvm anyways)
you need to flash the kitkat stock rom, use this one (you can use the already installed lite flashing tool, no need to reinstall anything, just download and extract the stock rom and flash from dnx mode). after that remember to configure your region code and then you can update to lollipop using OTA's (don't flash the lollipop rom as this is only to be used after you have already updated to lollipop using OTA's and you need a fresh lollipop over your existing one)

ionioni said:
ok, somehow your bios is (still) a kitkat version (sure you didn't restored the bios using the restore bios tool? or lenovo did? nvm anyways)
you need to flash the kitkat stock rom, use this one (you can use the already installed lite flashing tool, no need to reinstall anything, just download and extract the stock rom and flash from dnx mode). after that remember to configure your region code and then you can update to lollipop using OTA's (don't flash the lollipop rom as this is only to be used after you have already updated to lollipop using OTA's and you need a fresh lollipop over your existing one)
Click to expand...
Click to collapse
I will do that, the download seems very slow though at the moment, I'll let you know how it goes.

corasman said:
I will do that, the download seems very slow though at the moment, I'll let you know how it goes.
Click to expand...
Click to collapse
will be fine, you had a kitkat bios and everything choked right from the start (remember that the bios must match the rom you re/install, so for eg if you have kitkat on your tab don't flash a lollipop rom or the other way around, as this will not upgrade/downgrade the bios too and you will get unexpected behavior or bricks, to upgrade to lollipop from kitkat use ota's and after you are on lollipop you can flash a lollipop stock rom if needed sometime)

I now have Droidboot Provision OS
with selection of
Reboot
RebootDroidboot
Recovery
SPupdate
Power off
which do I choose

corasman said:
I now have Droidboot Provision OS
with selection of
Reboot
RebootDroidboot
Recovery
SPupdate
Power off
which do I choose
Click to expand...
Click to collapse
what were the steps you performed? normally that one is the screen that the tab is showing during the flashing yet you must see some activity on the Intel Flash Tool log window and in the bottom of your tab screen. if you see it the it's ok and just wait for it to finish, if not then you must start your tab in DnX mode (screen saying "Fastboot starting...") then load flash.xml from the extracted kitkat stock rom in Intel Phone Flash Tool and "Start flashing"

ionioni said:
what were the steps you performed?
you must start your tab in DnX mode (screen saying "Fastboot starting...") then load flash.xml from the extracted kitkat stock rom in Intel Phone Flash Tool and "Start flashing"
Click to expand...
Click to collapse
Something has worked
I am now at a screen to set the Language and region ,but it will not move on.

Doogee X5 Max Pro Root Recovery OTA

******************Root Recovery Doogee X5 max pro*******************
Your waiting Time IS Now Finished Here is Complete Guide to Root Doogee X5 Max Pro install twrp And More,
Hit :good:
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
Install twrp-
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly, rename twrp to recovery.img
type fastboot flash recovery recovery.img to flash recovery
Type fastboot reboot
Rooting-
Download BETA-SuperSU.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in twrp. Go to Install zip, find SuperSU.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Other Solutions-

i have doogee x5 max-s (i geuss limited editon in algeria ) with mtk6735 . i do evrything and all steps but when i reboot to recovery mode i have ( no command ) in the screen .... how to fix that ? sorry for my ****ty english XD

I had the same Issue but i have found a solution!
After you have flashed the twrp recovery, dont reboot the phone! the "recovery.sh" will replace the twrp on every boot!
Just pull off the battery after flashing, disconnect usb and put the battery back in to the phone.
Now get in to the recovery by pressing volume up and power button together until the select bootmode menue appears.
select recovery with the volume up button and enter with the volume down button.
and now you should be in the twrp main menue.
i hope it works for you too!
greetz from the lizard

It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.

pitro1 said:
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
Click to expand...
Click to collapse
use sp flash tools to flash recovery, scatter also added with twrp

Flash does not pass the file in the download only option, the process does not start. I reinstalled ROM by firmware mode all ok, but the process of passing recovery on command 12 and 13 of the error message. I manually copied the recovery to the sd and internal memory but also from the error. Does not find the file speaks that it is not a command found.

pitro1 said:
It does not work from step 12, "can not load Recovery.img".
Click to expand...
Click to collapse
Don't use Capital R's
fastboot flash Recovery Recovery.img
Code:
fastboot flash recovery recovery.img

Doogee X5 Max Pro - Update 01/16/2017 + TWRP-3-0-2 & SuperSU-v2.79
Working root for Update 01/16/2017
Title: Doogee X5 Max Pro
Listed: 01/19/2017 11:21 pm
ROM Version: ROM Android 6.0
Doogee X5 Max Pro - Update 01/16/2017
TWRP-3-0-2 + SuperSU-v2.79
Use This Version Flashtool
SP_Flash_Tool_v5.1620.00.000

XN Logos said:
use sp flash tools to flash recovery, scatter also added with twrp
Click to expand...
Click to collapse
Until today I could not do root on x5 max pro. In the method below even downloading the twrp when starting with the power + volume down button start with a menu in Chinese and if you start with volume up + power goes in the default recovery mode.

Same as Pitro1 I am on 16.01 update and I cannot install twrp no matter what I try.
I tried x32 and x64. I tried rebooting directly on recovery or first load system and then adb reboot recovery. I tried to format all first (now I lost my Imei and so on lol). I downgraded and updated again. Downgrading works only with 26.12 version. All others are giving me Colorado lines on the screen and nothing else...
OEM unlock, file transfer, adb, fastboot, drivers detection, are all working good. Only I cannot install twrp...
Also I cannot write nvram nor with SN Writer 2.1504 nor with Imei & SN Writer 1.7.2, MetaAP mode fails all the time...
I'm just about to send it back...

How i rooted my Doogee X5 Max Pro
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20

i returned the phone as i had no imei anymore.
i got a new one, i did not put any sim or whatsoever, i just unlocked bootloader, and updated to 16.01 version
then i tried to install twrp via fastboot and it did not work, i did it with sp flash tools as advised and removing the battery prior (don't forget to!). it worked !

Stripe_nl said:
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
Click to expand...
Click to collapse
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?

Hi. I have tried to root my x5 max pro with flash tools to load TWRP, but it always restarts normally and the TWRP does not come out. I found you and I started to try this method to load the TWRP. Does everything good, unload bootloader and load recovery, but loading the TWRP gives me error .:
Device unauthorized.
This adb's $ ADB_VENDOR_KEYS is nor set; Try adb kil-server if that seems wrong
what I do?

rooting X5 Max pro in Ubuntu 16.04
Hi all, this is my first china phone and I basically bought it only to experiment, I'm a linux power user but this is the first time I 'play' with an android OS.
thanks to multiple guides and posts on this and other forums I'm getting somewhere and learning a lot about how to manage an android OS, I'm sharing a bit of info I unovered about doing this under ubuntu but I'm also stuck and in need of guidance, please help me.
Linux specific issues:
I'm running ubuntu 16.04 LTS, installed fastboot and adb tools from ubuntu repos, with these tools and no other modification to my system I could follow the tutorial on how to unlock the OEM bootloader with adb and fastboot.
accordingly to this post about SP flash tool in linux you might need to blacklist a modem manager module in order for SP flash tool to connect to the phone, you also need to install usb development tools (package libusb-dev) and check through dmesg that your linux OS can actually properly read mediatek usb devices.
After following the above mentioned instructions (both the linux sp flash tool tutorial and the bootloader unlocking howto) I could get SP flash tool linux (multiple version) to see the phone after you connect it while SP flash is downloading the new recovery image and flash it with an ok message.
If you get stuck with a BROM error 1013 remember to start sp flash tool with root privileges.
Phone specific issues:
I can get SP flash tool to flash my phone recovery with an ok message confirmation but the phone keeps rebooting with doogee recovery and not twrp. I'm on the newest stock ROM update (20170116) as of current post date. I've been using 32 bit TWRP images from multiple sources and linux version 5.1620 of spflash tool from their website
so my questions are as following:
1) after reading other posts I think I might have to play with different versions of SP flash tool and TWRP until I get the right combination, I think I might be using 64bit spflash tool for linux to flash a 32bit rom or something like that, can anybody confirm precise version number of the stock rom, TWRP and SP flash tool that worked out for you?
2) should I try to install the whole stock ROM posted in this chinadevices thread before trying to flash only TWRP recovery? please also check the linked thread for multiple custom ROM being ported to this phone, please also note that the full stock rom this poster uploaded (it's in the "all firmware" link) contains another flashing tools with chinese instruction called MultiDownloadTool.
www.china-devices.com/forum/index.php?threads/doogee-x5-max-pro-mt6737-custom-roms.20527/
3) I don't have access to a windows installation right now, but I do have a Win10 VM under Vmware workstation 12 pro, so I could try windows version of sp flash tool, do you guys think that USB passthrough would work?

ibrooks said:
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Click to expand...
Click to collapse
Same here. May a work around would be finding out the oem commands in fastboot. I have seen a tutorial to get them, but you have to be root: https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/

I search a simple method
Why all so complicate? I am searching for a simple way to root.
For my old Doogee X5, I discovered just
update-ROOT-DOOGEE_X5.zip
Copy the zip to the micro-SD-card
Settings -> Phone info -> Update -> menu "update local" -> choose zip from micro-SD-card.
Start update.
That's all!
Now I search for such a simple solution for my new Doogee X5 MAX pro.
I do not want any methods with "volume down power", because my X5 MAX pro has the menus after "Volume down power" start in Chinese language.

Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/

This version finally works ! Thank you
Neaw said:
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
Click to expand...
Click to collapse
Hi there,
I just tried the first file you posted, (twrp-x32-rom), and this one works for me after all previous attempts to boot up TWRP failed. Thanks for the link !
What I had tried before:
I have a relatively new X5 Max Pro, which I ordered a week ago. I updated the firmware to the newest version (20170116) using the OTA update function.
Then I tried to flash TWRP using the files from "needrom.com" which seem to have worked on older versions of the phone/firmware, but did not work for the newer versions.
I tried 32bit and 64bit TWRP versions and flashed them with SP flash tool, but when pressing Vol+/Power the phone would not boot into TWRP recovery. Insted, when selecting "Recovery" from the boot menu, the phone would show the Doogee logo in silver, then blink once, then boot up normally. When repeating this process, then phone boots into Stock recovery, indicating that the TWRP I flashed was replaced by stock recovery.
However, I just flashed the recovery.img from "TWRP LATEST" (the first file posted by Neaw) with SP flash tools and was finally able to boot into TWRP. I installed the superSU-zip 2.79 included in the link, and I am now rooted. Once again, thanks for posting this :good:
Greetz, Ollek74

Doogee X5 MAX! SERIUS PROBLEM......
Hello Guys i have a serious problem with my phone.....i have Malware on it and i cant uninstall it or anything alse.....the worst thing is that my phone not responding in any connection except that charging.....i can't have access on my storage cause this is not allowed or gives the choice! i tried everything but nothing nor the usb debugging or anything else please give me your help!!!!

Error in installing twrp

Hy everyone ineed help..
I have h990ds in nouget android security before 2016.
I try to root but in the middle of proses,its error, i try to flashing by lgup but the screen only flashboot mode. :crying::crying:
The some words in my screen:
Fastboot mode(red color)
Product name_msm8996 64gb
Varian_msm8996 64gb
Hw version_rev10
Bla...
Serial number -lgus996af7da36 (my type h990ds)
Secure boot-disable
Lock state_lock
[1090]
[1140]fastboot mode started
There 3 steps .bat after runfirsttime.bat
An i click step3 after step 2.

nuqudlover said:
Hy everyone ineed help..
I have h990ds in nouget android security before 2016.
I try to root but in the middle of proses,its error, i try to flashing by lgup but the screen only flashboot mode. :crying::crying:
The some words in my screen:
Fastboot mode(red color)
Product name_msm8996 64gb
Varian_msm8996 64gb
Hw version_rev10
Bla...
Serial number -lgus996af7da36 (my type h990ds)
Secure boot-disable
Lock state_lock
[1090]
[1140]fastboot mode started
There 3 steps .bat after runfirsttime.bat
An i click step3 after step 2.
Click to expand...
Click to collapse
The good news is that you've got the dirtysanta bootloader installed (that's why it's reporting us996) so you should be able to fix it without using LG UP and having to redo most of the process.
Install twrp by doing fastboot flash path/to/twrp.img .then pull the battery when done. Then enter twrp by using to volume key method (hold volume down, press power until the screen turns on, then tap power repeatedly until a menu asking to factory reset appears, say yes (while twrp is installed it won't actually wipe anything).)
Flash a rom (a stock one is here), and magisk.
If you can't use an sdcard to get them accessible to the phone in twrp, in twrp you can go into advanced then sideload and connect to a PC and do adb sideload path/to/rom-or-magisk.zip

Phoenix591 said:
The good news is that you've got the dirtysanta bootloader installed (that's why it's reporting us996) so you should be able to fix it without using LG UP and having to redo most of the process.
Install twrp by doing fastboot flash path/to/twrp.img .then pull the battery when done. Then enter twrp by using to volume key method (hold volume down, press power until the screen turns on, then tap power repeatedly until a menu asking to factory reset appears, say yes (while twrp is installed it won't actually wipe anything).)
Flash a rom (a stock one is here), and magisk.
If you can't use an sdcard to get them accessible to the phone in twrp, in twrp you can go into advanced then sideload and connect to a PC and do adb sideload path/to/rom-or-magisk.zip
Click to expand...
Click to collapse
After use adb fastboot flash recovery twrp.img, there's new problem.
Using volume key mode my screen is blank, just like broken TV.. :crying::crying:

nuqudlover said:
After use adb fastboot flash recovery twrp.img, there's new problem.
Using volume key mode my screen is blank, just like broken TV.. :crying::crying:
Click to expand...
Click to collapse
to totally back out and bring your phone to totally stock use download mode (from powered off hold volume UP while connecting to the pc). The screen will be still messed up but it will still work on the pc.
Use patched LG UP in partition dl mode to flash everything with a stock h990(ds) kdz.
Once you start using dirtysanta next time (if you decide to try again) be very very careful when using LG UP (easier to just use stock flashabile zip) unless you want to redo the above and flash EVERYTHING back to stock (if you ever flash the aboot partition in LG UP and anything ISN'T stock it will brick you! This mostly applies to partition dl mode since upgrade mode flashes everything, but partition dl mode is the only mode you can even potentially flash things and keep root (but I don't encourage this... its easier and saferto just use zips in TWRP to flash firmware (mostly stock basedrom or so called stock flashible zips tend to also flash all of the firmware except parts needed to keep root. )

Phoenix591 said:
to totally back out and bring your phone to totally stock use download mode (from powered off hold volume UP while connecting to the pc). The screen will be still messed up but it will still work on the pc.
Use patched LG UP in partition dl mode to flash everything with a stock h990(ds) kdz.
Once you start using dirtysanta next time (if you decide to try again) be very very careful when using LG UP (easier to just use stock flashabile zip) unless you want to redo the above and flash EVERYTHING back to stock (if you ever flash the aboot partition in LG UP and anything ISN'T stock it will brick you! This mostly applies to partition dl mode since upgrade mode flashes everything, but partition dl mode is the only mode you can even potentially flash things and keep root (but I don't encourage this... its easier and saferto just use zips in TWRP to flash firmware (mostly stock basedrom or so called stock flashible zips tend to also flash all of the firmware except parts needed to keep root. )
Click to expand...
Click to collapse
I already use lgup pacher, when connected the message unknown model
Can i using flash laf.bin from fastbootmode?

nuqudlover said:
I already use lgup pacher, when connected the message unknown model
Can i using flash laf.bin from fastbootmode?
Click to expand...
Click to collapse
But did you use partition dl mode? It alone bypasses the model checks.
Partition dl mode isn't in regular lg up, you need the special patched version I linked (replace the files of your regular lg up with the special version)

Phoenix591 said:
But did you use partition dl mode? It alone bypasses the model checks.
Partition dl mode isn't in regular lg up, you need the special patched version I linked (replace the files of your regular lg up with the special version)
Click to expand...
Click to collapse
I already put your special patched to my Lgup..

nuqudlover said:
I already put your special patched to my Lgup..
Click to expand...
Click to collapse
Try uppercut then. Use upgrade mode if it works but partition dl mode is missing. Note uppercut asks for lg up version 1.14 . I can't remember what version the patched one is but you may have to reinstall that version instead.

Google Pixel 3a (sargo) brick - error boot prepare

Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.

GioPan_ said:
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
Click to expand...
Click to collapse
Do you have tryied to run the official google tool in Windows to try to rescue it?

Estebiu said:
Do you have tryied to run the official google tool in Windows to try to rescue it?
Click to expand...
Click to collapse
Yes, I wrote in the post, I tried both the command line tool and the chrome version. Btw i'm on linux

Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)

GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
I'll try this...

GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
Does this work if adb not working? I only have fastboot.

WriteLovey said:
Does this work if adb not working? I only have fastboot.
Click to expand...
Click to collapse
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.

GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.

WriteLovey said:
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
Click to expand...
Click to collapse
All is well. I'm back on my Pixel, yeah!

GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I just had an encounter with this. I was rooting my device (Pixel 3A) and messed up my partitions through accidentally attempting a downgrade which broke all my ****. I was unable to easily reset this device to factory, so it took me several days to figure out and root. I'm getting better though as a hacker, because a year ago this would have taken me a month.
I was able to enter recovery mode (lying down Android, NO COMMAND). From this recovery mode, adb devices -l recognized my device, although I was unable to get a shell.
At first, ADB was telling me the device was authorized, but I messed with a bunch of other stuff (tried to flash a bunch of different partitions and monkey around in general trying to install Magisk) and then ADB started telling me it wasn't authorized when I used devices -l.
Once it said unauthorized, I was unable to issue the device any commands with ADB, so I just used hardware keys to get into recovery mode. From there, I selected OTA update, and it got into sideload mode. At that point, I used adb sideload with the OTA package that I downloaded here https://developers.google.com/android/ota
^^^ That operation did successfully restore my device to factory
This following guide here describes the details of how to use hard keys to enter recovery on this phone (don't download anything from there tho, and make sure your adblock is on)
How to Hard Reset your new Google Pixel 3a [Tutorial]
In this article, you will learn how to start your Google Pixel 3a up into the Recovery Mode and perform the Hard Reset to make it work perfectly again.
thedroidguy.com

I just wanted to say, I've been wrestling this hardbrick for a couple of days with my Pixel 3a.
I've finally overcome it by sideloading the most recent OTA update after using a hard key combo to get into recovery mode. The hard key combo is hold Power Button, tap Volume Up, then release both. Then, all you need is to use the command:
adb sideload <OTA.zip>
^^^OTA wasn't the actual filename though, you can download OTA packages for Pixel 3A here: https://developers.google.com/android/ota
the OTA binaries are NOT the same as the factory images, which is here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Sideloading the OTA package brought my phone back from only having fastboot and recovery mode, even when flash-all.sh from the official downloaded firmware failed. Now I know how to undo damage that I cause by rooting this thing. Since I sideloaded newest firmware, it was also like applying an update. I easily got root after that, and I've logged the process. I'll make it into a guide soon

I'll just note that if you accidentally flashed the TWRP boot image instead of simply booting into it, I believe all you have to do is flash the stock boot.img to fix the problem. Obviously you can sideload the entire rom image, but that shouldn't be necessary.
Using the Windows computer (or whatever computer you are sending ADB commands from), download the full stock image directly from Google. Unzip it and then upzip the folder inside. You should find the boot.img file inside that folder. Take that file and then flash it to the phone using the normal ADB command: fastboot flash boot boot.img
While I haven't tried this myself recently, it should work in theory. The command "fastboot flash boot twrp.img" flashes the boot partition with a non-working twrp image, so replacing the faulty image with the stock boot.img should fix the problem.

If I did the same I would first attempt to manually put device in bootloader/aka fastboot mode then fastboot flash the stock boot.img , sudo fastboot flash boot boot.img --slot all
I only read the op (first post here);but I betcha that would have worked. Then sudo ./flash-all.sh and let it do it's thing.

Any stock ROM?

I flashed an unofficial TWRP, and I cannot boot my phone now.
Are there any restore-images?

I need restore images as well for the att model

Profnex said:
I need restore images as well for the att model
Click to expand...
Click to collapse
i need too xD

Oil-Man said:
I flashed an unofficial TWRP, and I cannot boot my phone now.
Click to expand...
Click to collapse
Have you tried booting into 'Recovery Mode'?
(hold VolumeUp at boot; or VolumeDown, and select Recovery Mode from the menu)
Most of the TWRP images I've tried were unable to boot the phone,
but _do work_ in recovery mode.
Oil-Man said:
Are there any restore-images?
Click to expand...
Click to collapse
The Hydrogen uses the A/B system; so, you'll always have (a possibly older)
image in the other boot slot; unless, of course, you installed TWRP to both...
You can, and probably already have, also find links to both stock and patched
boot images in the rooting thread.

draxie said:
Have you tried booting into 'Recovery Mode'?
(hold VolumeUp at boot; or VolumeDown, and select Recovery Mode from the menu)
Most of the TWRP images I've tried were unable to boot the phone,
but _do work_ in recovery mode.
The Hydrogen uses the A/B system; so, you'll always have (a possibly older)
image in the other boot slot; unless, of course, you installed TWRP to both...
You can, and probably already have, also find links to both stock and patched
boot images in the rooting thread.
Click to expand...
Click to collapse
I have flashed both, unfortunatily.

I'm still searching for a programmer that is compatible with the RHO. I have dissected a few of the files from the dump that was provided, however it seems that even with the dumps I cannot for the life of me get the phone out of EDL mode, I recently was able to use UAT and for some reason I got the red LED indicating the battery does indeed charge, duh. Any help on this would be appreciated, oh and another question, who is cloudminds, and what does this device have in common with the Mi Mix 2? The USB ID is the same for these 2 devices. which i found to be odd until realizing that Xiaomi may have been one of the companies involved in manufacturing this phone. If that is the case, can I somehow rewrite the Mi Mix 2 programmer with the correct RHO information? any help with getting from EDL to fastboot would be amazing

AFAIK, CloudMinds is the ODM behind the phone.
All firmware updates were hosted on their domain,
and the certificates used to sign them are also theirs.
An old trick for getting out of EDL mode (assuming
that there's _some_ other working firmware on there),
that may or may not work on the RED Hydrogen One,
was to keep holding the power button for a LOOOOONG
time: in excess of 5 whole minutes... Have you tried?
Does that help?