Database Info

Bootloader /loop

Hi
So i was reading a little bit about bootloader flashing etc. as i get a shield tablet 32gb from friend he get replacement i dont know what he did with it but right now tablet is looping all the time going to "bootloader" without presing any key
when i choose continue its saying - cold booting linux then booting failed etc
and he's trying to download something but without the luck
so i try to unlock the bootloader and everything goes ok till
""""
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 4.571s
""""
And that's it is there anyway to fix it ? anyone found solution or its completly dead ?
sorry for spelling :/

Ok first control you have adb driver istalled correctly on PC...
Secondo try using minimal sdb..
If he got it replaced from Nvidia it's possible that tablet is deactivated, and then you can do nothing

What does it say on the bootloader screen? If it was bricked because it was a old replaced tablet, you wouldn't get to the bootloader.

I've tried everything but my phone just won't turn on

Yesterday I tried to update my phone to android 6.0 but something must have gone wrong during the process because now my phone is stuck in a bootloop, I've tried as hard as i can to fix it but nothing is working. I tried to do a hard factory reset and wiped my phones memory but it won't turn on, I really don't know what to do because I cannot afford to get a new phone.

ineedhelplz said:
Yesterday I tried to update my phone to android 6.0 but something must have gone wrong during the process because now my phone is stuck in a bootloop, I've tried as hard as i can to fix it but nothing is working. I tried to do a hard factory reset and wiped my phones memory but it won't turn on, I really don't know what to do because I cannot afford to get a new phone.
Click to expand...
Click to collapse
If you can get into the bootloader, reflash your firmware to get it back to working condition.

damianx5 said:
If you can get into the bootloader, reflash your firmware to get it back to working condition.
Click to expand...
Click to collapse
Yes I can get into the bootloader but my computer isn't recognizing that my phone is plugged in, it just says charging

ineedhelplz said:
Yes I can get into the bootloader but my computer isn't recognizing that my phone is plugged in, it just says charging
Click to expand...
Click to collapse
Make sure you have all the drivers installed and that you have adb and fastboot files as well.

If you still cant access to transfer files, search for "adb push and pull" commands at google to directly send files to and from your devices.

I am having the same issue!
Here is the difference:
Updated phone to the new OS and my phone went into a boot loop. Booted my phone in Fastboot to try to Factory Reset, it won't reset, it just goes back into Boot Loop... *sobs* I've looked everywhere to find a solution to the following problem, and I'm posting here in order to avoid making unnecessary forums.
My Issue:
As stated above, I updated my phone and it went into boot loop. I am trying to flash it to the previous version, but because I can not factory reset my phone I can not flash my phone. I can not unlock the Bootloader because my USB Debugging is disabled and can not be enabled because my phone is bricked.
I've tried clearing the cache - wipe_data | wipe_cache | fastboot format userdata
I've tried
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
********** fastboot (serial number)
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.546s]
writing 'recovery'...
OKAY [ 2.699s]
finished. total time: 3.245s
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\Name\AppData\Local\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
Only to later find it did not work due to my Bootloader being Locked...
Here's what I'd like to know: How do I Factory Reset my phone OR Unlock my Bootloader from my computer? Heck, why not tell me both, I can really use the help as this is my only phone and Motorola REFUSED to fix my phone due to some magical liquid damage... to a water resistant phone... that was never once touched by liquid of any kind... but I digress... [...vents on]
About my Phone:
Model XT1548
Rooted: No
Bootlader: Locked
Flashed: No (I believe)
Cause of Problem: Update to Marshmallow
_________________________________________________________
BTW: I made a new thread for this because I wasn't sure if posting here would get any help. HERE

Could you get it working?

Random Reboots, Then Phone Bricked Itself! Help Recover My Kid's Disneyland Videos!

This is a standard US Google Pixel 128GB that I picked up in January from Swappa. I have not ever modified it in any way. Never been dropped or abused either.
Since early April, the phone would randomly freeze and reboot itself. Sometimes it would be days between reboots, sometimes it would reboot multiple times even before it finishes booting. It's usually random, but I noticed it would always reboot if I am recording a really long video (5-10 minutes). Audio also failed once (no sound could be heard from speaker or earpiece) even after rebooting multiple times. Three days ago, while recording a long video of my kid at Disneyland, it froze. This time, the reboot failed to. The screen flashes some garbled stuff on the screen. Only difference this time is that I know the internal flash memory was almost full before I even started recording the video.
I can't get the phone to boot at all. If I press the vol-down button (doesn't even need the power button), I can get to the bootloader menu. In the bootloader menu, if I choose "Start," Restart bootloader," or "Recovery mode," the screen will flash again forever (I've waited hours). If I choose "Barcodes," then I will see all the proper IME/SKU/Serial numbers and barcodes. Choosing "Power off" works too, if it's not plugged in -- if it's plugged into power, the screen will flash a "static" screen endlessly. I took a video of this happening at Disneyland.
https://youtu.be/VlQ_PpZQ9SY
https://youtu.be/5m8_u0nQ4hE (the flashing screen)
After I got back from vacation, I plugged it into a Windows PC. No ADB access, but I can get fastboot to see it. Trying to reflash the lastest stock image (https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3) fails with this:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.810s]
writing 'bootloader_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.919s
rebooting into bootloader...
OKAY [ 0.052s]
finished. total time: 0.055s
< waiting for any device >
Click to expand...
Click to collapse
The screen would flash the same garbage as it tried to reboot into bootloader. I hold down the volume-down button to get back in and it continues:
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.430s]
writing 'radio_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.542s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
< waiting for any device >
Click to expand...
Click to collapse
Once again the screen would flash the same garbage as it tried to reboot into bootloader. I hold down the volume-down button to get back in and it continues:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: FA6C70300873
checking product...
OKAY [ 0.052s]
checking version-bootloader...
FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1703151359'.
finished. total time: 0.367s
Press any key to exit...
Click to expand...
Click to collapse
That's it. The bootloader screen does show BL and Baseband versions as "N/A", but can't these be overwritten? And is it normal for the device to say LOCKED? This is everything on my bootloader screen:
BL: N/A
Baseband: N/A
Product/Variant: sailfish-US-PVT
Serial Number: FAxxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Toshiba
DRAM: 4096MB Hynix LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Click to expand...
Click to collapse
If it'll help, I can get better photos/videos of the phone. The screen flashes some random distorted Google/Android logos and some "static"-looking pixels.
Any clue about what I should do? I would like to be able to get my photos/videos from the phone. I would also like to be able to recover the phone. Doing both would be awesome. I'm not sure if there is a hardware issue or software issue, but this phone has been horrible since April.

I think either your phone is bricked or your hardware has failed. Fastboot error shows that it cannot identify your bootloader so you have to get a replacement through Google. Check Google photos to see if there are backups of the videos.

Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.

Tulsadiver said:
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Click to expand...
Click to collapse
But wouldn't stock recovery support adb commands? I never checked but if it does he could adb pull files off of sdcard

UPDATE: Someone suggested I try draining the battery and try rebooting. Didn't think it would help, but was desperate, so I left the phone on. A few hours later, it shutoff. I put it back on a charger overnight. Now I can't even start it again. This thing is a brick. So disappointed in Google.
justinxfan said:
I think either your phone is bricked or your hardware has failed. Fastboot error shows that it cannot identify your bootloader so you have to get a replacement through Google. Check Google photos to see if there are backups of the videos.
Click to expand...
Click to collapse
I make sure to backup every night while charging and on WiFi, but this happened at Disneyland and I had the entire day's videos not yet backed up. :crying:
Tulsadiver said:
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Click to expand...
Click to collapse
danielt021 said:
But wouldn't stock recovery support adb commands? I never checked but if it does he could adb pull files off of sdcard
Click to expand...
Click to collapse
adb didn't see the device. Just fastboot.

ken830 said:
UPDATE: Someone suggested I try draining the battery and try rebooting. Didn't think it would help, but was desperate, so I left the phone on. A few hours later, it shutoff. I put it back on a charger overnight. Now I can't even start it again. This thing is a brick. So disappointed in Google.
I make sure to backup every night while charging and on WiFi, but this happened at Disneyland and I had the entire day's videos not yet backed up. :crying:
adb didn't see the device. Just fastboot.
Click to expand...
Click to collapse
Yep sounds like the boot loader is screwed. Phone is a brick. She thing happened to my Nexus 7. I had to replace the motherboard.

did anyone got any leads on this... the same issue with my pixel 128gb... unfortunately it is out of warranty. a working solution would be a great help.

AlphaOrion said:
did anyone got any leads on this... the same issue with my pixel 128gb... unfortunately it is out of warranty. a working solution would be a great help.
Click to expand...
Click to collapse
Sorry to hear this, but I didn't have any solution except for replacing the entire phone. You should contact Google anyhow.

this is so disappointing...I wonder how many people this has happed to already, I was using the phone and it just randomly shut off and wont turn back on..almost exactly what the OP is experiencing...obviously phone is now out of warranty and apparently motherboard needs to be replaced (which is ridiculous!!)….I've never had a phone brick on me ever, never thought it would actually happen, especially on stock everything.
---------- Post added at 08:02 AM ---------- Previous post was at 07:57 AM ----------
Maybe its me....but it seems like more and more people are having this issue...looks like as the hardware gets older the more prone to partition being corrupted....this is not acceptable for a 2 year old phone

I have had numerous pixel replacements. One of them was a hard brick like yours. Even took it to iFixit and they confirmed it was dead. So it may not be uncommon.

I just don't get if photos and videos were so important if no one ever does a weekly backup? Use Google drive, use Google photos, use your USB cable to PC if you don't trust Google.
Phones break, get over it. You want a fast phone? Expect it to die even faster. 2 years for a phone is normal, if you don't think it is get then budget phones are there, with the long life low hardware aspect

I had TWRP and Magisk flashed. Now I wanted to go back, flashed factory, locked the bootloader and now I can only boot into fastboot. Everything elsa ends in a bootloop with a short flashing Google logo.

OMG @ XDA Please help bootloop Update Oreo No more battery charge No TWRP acces etc

I am truly and deeply sorry to insist somehow on my troubles and I beg :crying: any one here on XDA to help me anyhow...
I have read thousands of pages here at XDA and none would go on my way or just make things go forward a little...
Sorry for my way of saying things ... I'm French and worse ...confused .
Trying to make it simple... :
HUAWEI MHA-L09 C432 B198 // before it went out officaly I wanted to flash this Oreo update... Was thinking doing things as per instructions... update went kinda well until reboot :
Got an error message on boot (Func 14 iom3 image and error 1 system failed verify ) - this error causes constant bootloop .
Since this error my battery wont charge ! It flashes and blink red light and eventually boot to error message ... no time to VOL up + power to recovery.
won't charge even in fastboot mode which I can still access to discover two things :
sometimes i get the COLD boot or the failedVerify screen at fastboot mode. NVM .
Bootloader unlocked OK - TWRP 3.1.1 (or version before 3.0.2.2) says instaled OK - Cannot boot into it as baterry empty - which will NOT charge through fastboot screen .
Or plugged into the wall, as soon as there is enough charge the bootloop ERROR UPDATE SYSTEM AGAIN Func NO 14 iom3 Func NO 1 system failed verify will go on and on ... and on as long as plugged in usb or onto the wall .
Have tried to flash system again from extracted data of previous rom (b198) , everything seemed okay , boot.img / recovery.img and system.img ... all okay.
But still cannot reboot correctly and worse cannot restore through TWRP or any other mean my saved folder which contains a lot of files BEFORE UPDATING to OREO
Have tried DLOAD folder with differents stock versions etc.. rayglobe_knife... HWOTA and SRKtool;.. nothing goes my way .
Well how can I - i don't know just an idea - either :
WIPE and FORMAT INTERNAL storage
OR may be ? flash C636 and re flash to C432 ...
OR may be RESTORE my saved folder done with twrp but restore it WITHOUT twrp considerating that I cannot boot into it du to that battery thingy problem.
OR do you have another strategy to do anything ? (push through fastboot to sdcard ? r ? something more technical ?)
I cannot assume that deboggage usb is on, neither oem is on neither allow unknown sources is on . They were before update to Oreo ..
I just don't know here I stand anymore .
It has been so many days I am stucked with this ! incroyable .
I am short of ideas, of hope and so desesperate to get back my so loved mate 9 onto the road as i need it for my work ... pfff forgot that ...:crying: :crying: :crying:
Please any idea would be very welcome starting at the fact that those ideas WILL HAVE to be possible through FASTBOOT and (VOL- power key) only.
I think .
DO YOU ?

FuM8 said:
I am truly and deeply sorry to insist somehow on my troubles and I beg :crying: any one here on XDA to help me anyhow...
I have read thousands of pages here at XDA and none would go on my way or just make things go forward a little...
Sorry for my way of saying things ... I'm French and worse ...confused .
Trying to make it simple... :
HUAWEI MHA-L09 C432 B198 // before it went out officaly I wanted to flash this Oreo update... Was thinking doing things as per instructions... update went kinda well until reboot :
Got an error message on boot (Func 14 iom3 image and error 1 system failed verify ) - this error causes constant bootloop .
Since this error my battery wont charge ! It flashes and blink red light and eventually boot to error message ... no time to VOL up + power to recovery.
won't charge even in fastboot mode which I can still access to discover two things :
sometimes i get the COLD boot or the failedVerify screen at fastboot mode. NVM .
Bootloader unlocked OK - TWRP 3.1.1 (or version before 3.0.2.2) says instaled OK - Cannot boot into it as baterry empty - which will NOT charge through fastboot screen .
Or plugged into the wall, as soon as there is enough charge the bootloop ERROR UPDATE SYSTEM AGAIN Func NO 14 iom3 Func NO 1 system failed verify will go on and on ... and on as long as plugged in usb or onto the wall .
Have tried to flash system again from extracted data of previous rom (b198) , everything seemed okay , boot.img / recovery.img and system.img ... all okay.
But still cannot reboot correctly and worse cannot restore through TWRP or any other mean my saved folder which contains a lot of files BEFORE UPDATING to OREO
Have tried DLOAD folder with differents stock versions etc.. rayglobe_knife... HWOTA and SRKtool;.. nothing goes my way .
Well how can I - i don't know just an idea - either :
WIPE and FORMAT INTERNAL storage
OR may be ? flash C636 and re flash to C432 ...
OR may be RESTORE my saved folder done with twrp but restore it WITHOUT twrp considerating that I cannot boot into it du to that battery thingy problem.
OR do you have another strategy to do anything ? (push through fastboot to sdcard ? r ? something more technical ?)
I cannot assume that deboggage usb is on, neither oem is on neither allow unknown sources is on . They were before update to Oreo ..
I just don't know here I stand anymore .
It has been so many days I am stucked with this ! incroyable .
I am short of ideas, of hope and so desesperate to get back my so loved mate 9 onto the road as i need it for my work ... pfff forgot that ...:crying: :crying: :crying:
Please any idea would be very welcome starting at the fact that those ideas WILL HAVE to be possible through FASTBOOT and (VOL- power key) only.
I think .
DO YOU ?
Click to expand...
Click to collapse
Bump please

warranty?

It's bricked, you cannot flash anything on it in that state, needs to go back to the factory to be fixed. And if it is showing that on the screen it won't be covered under warranty as it is evidence that you tried to flash an unauthorized rom, what happened is that the flash of Oreo didn't complete and the repartitioning for Oreo did not complete, mine did the same thing, motherboard replacement was the suggested fix.

Have you tried this with the full oreo update package?

Thank you @ Shadowprince94 - Revjamscarver & Szilard66 for dropping by :good:
Have you tried this with the full oreo update package?
- As expected (I have tried before to get into TWRP) I have no time at all to unplug and VOL up/Power key to enter TWRP that the phone turns itself off... du to battery not charging more than 1% I guess.. - I can only get in fastboot mode for a few minutes... but seems not enough to boot into twrp ... fastboot/rescue mode can be plugged to CPU for 10mn before turning the phone off, charging a couple of minutes, then booting back into that bootloop...
ANYWAYz or MANNERS that I can flash those files by fastboot mode... for instance extracting them and ... flash them one by one ? - oh my bad, tried already flashing the ZIP files directly : ended with a "fastboot/ CMD stopped working - and worse... flashing boot.img / recovery.img and system.img had worked without results...
see pictures...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Today 01:06 AM
revjamescarver
It's bricked, you cannot flash anything on it in that state, needs to go back to the factory to be fixed. And if it is showing that on the screen it won't be covered under warranty as it is evidence that you tried to flash an unauthorized rom, what happened is that the flash of Oreo didn't complete and the repartitioning for Oreo did not complete, mine did the same thing, motherboard replacement was the suggested fix
I don't want to read this ! - I once got it bricked already (but not that much) and successfully recovered it by rebranding it to c636 and then c432.. but I could use at this time twrp... Any idea how much this would cost ? about ?.. FunkyHuawei would not be of any use probably ? ... olalalala
Today 12:03 AM
Szilard666
warranty? None , bought it from CashConverter in Genève and had no box, cable or whatsoever but the mobile itself... 450 F.CH though + cannot lock bootloader (command not allowed) and confirm it is unlocked when trying to unlock it ...

Sorry to hear that. Motherboard replacement is not cheap, will cost around slightly less, then a used phone.

FuM8 said:
Thank you @ Shadowprince94 - Revjamscarver & Szilard66 for dropping by :good:
Have you tried this with the full oreo update package?
- As expected (I have tried before to get into TWRP) I have no time at all to unplug and VOL up/Power key to enter TWRP that the phone turns itself off... du to battery not charging more than 1% I guess.. - I can only get in fastboot mode for a few minutes... but seems not enough to boot into twrp ... fastboot/rescue mode can be plugged to CPU for 10mn before turning the phone off, charging a couple of minutes, then booting back into that bootloop...
ANYWAYz or MANNERS that I can flash those files by fastboot mode... for instance extracting them and ... flash them one by one ? - oh my bad, tried already flashing the ZIP files directly : ended with a "fastboot/ CMD stopped working - and worse... flashing boot.img / recovery.img and system.img had worked without results...
see pictures...
Today 01:06 AM
revjamescarver
It's bricked, you cannot flash anything on it in that state, needs to go back to the factory to be fixed. And if it is showing that on the screen it won't be covered under warranty as it is evidence that you tried to flash an unauthorized rom, what happened is that the flash of Oreo didn't complete and the repartitioning for Oreo did not complete, mine did the same thing, motherboard replacement was the suggested fix
I don't want to read this ! - I once got it bricked already (but not that much) and successfully recovered it by rebranding it to c636 and then c432.. but I could use at this time twrp... Any idea how much this would cost ? about ?.. FunkyHuawei would not be of any use probably ? ... olalalala
Today 12:03 AM
Szilard666
warranty? None , bought it from CashConverter in Genève and had no box, cable or whatsoever but the mobile itself... 450 F.CH though + cannot lock bootloader (command not allowed) and confirm it is unlocked when trying to unlock it ...
Click to expand...
Click to collapse
U can try HCU-CLIENT and Dc Phoenix to unbrick your phone.
http://hcu-client.com
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Sent from my LON-L29 using XDA Labs

@FuM8
This is well worth a shot, not free but much much cheaper. It's got me out of trouble once.
Mostar088 said:
U can try HCU-CLIENT and Dc Phoenix to unbrick your phone.
http://hcu-client.com
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Sent from my LON-L29 using XDA Labs
Click to expand...
Click to collapse

thank you guys, take good notice of your suggestions and going to have a serious look deeper into that...
I would prefer than going to a Huawei shop where they'll probably charge me for system, battery and god knows what else !
thanks a bunch to all of you for your interest and help .

Fastboot mode
FuM8 said:
thank you guys, take good notice of your suggestions and going to have a serious look deeper into that...
I would prefer than going to a Huawei shop where they'll probably charge me for system, battery and god knows what else !
thanks a bunch to all of you for your interest and help .
Click to expand...
Click to collapse
If you can get into regular fastboot mode (not that error screen) there is hope, funky Huawei has an unbrick tool that could possibly work but that all depends on exactly what happened to cause the error, if you were in the middle of flashing Oreo and it was interrupted then your partitions probably got messed up and that generally is not fixable through fastboot or those other "tools" that are out there, without knowing exactly what you did there is really no way to tell. If you flashed Oreo then flashed nougat twrp to try to flash back from Oreo to nougat, your partitions got messed up and while the factory "can" fix it it would be cheaper to just replace the motherboard. Around $150-$200 from what I hear. But then again it all depends on exactly what you did when you got the error

@ revjamescarver :
thanks for that.
Well I was indeed flashing the 3 zip files , from memory, I was into the update.zip one and then my phone rebooted to show this error...
I can access fastboot/rescue mode , for instance, trying to relock the bootloader will end with the "command not allowed" .
I have , apparently, successfully flashed a twrp-3.0.2-2-hi3660.img, the others did not work, so I assume my system still consider that it is in the mha-L090c432b198 version. .
But cannot boot into twrp .
I tried as well the commands "fastboot -w" , result:
"erase successful, but not automatically formatting."
"can't determine partition type"
"failed command not allowed"
that 3 times ...
from all those fastboot commands underneath ,
(bootloader) command list
(bootloader) dmesg
(bootloader) last_dmesg
(bootloader) clearaspflag
(bootloader) refurbish
(bootloader) get_identifier_token
(bootloader) checkKeycardID
(bootloader) get_tamper_flag
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) enter
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) erase_phone_storage
(bootloader) erase_nfc_record
(bootloader) gotohboot
(bootloader) resetgift
(bootloader) ats
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readmeid
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) ddr2gbh
(bootloader) ramdump2gbh
(bootloader) ddr2gstatus
(bootloader) get_temp
(bootloader) writemeid
(bootloader) lock
(bootloader) readusername
(bootloader) writeusername
(bootloader) resethtcdebugflag
(bootloader) load_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) load_modem_emmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
wouldnt it be one that might get me a little forward ? to erase or better (in my dreams) to restore the save I have done from TWRP before flashing ?
I just cannot believe that motherboard or even the baterry (not charging) are somehow faulty .
I am convinced there is a way of doing something, as a noobish I just don't know what and how. .. as suggested before I am just , now, so confused of what I done, how I done it etc... i don't even remember the commands to erase internal storage and show you a printscreen of it !
I had a break from it but now I am determined to give it another try.. the question is what and how ...
By fastboot with which commands... by putting on sdcard something ? by formatting internal system, then how ? this is really fustrating... update went well and .. olala.
Do you believe that funky Huawei could in any mean do something for me ? or the others tools suggested by members in posts before ? or else I'd better call 911 huawei services center here near Marseille and let it up to them ?
As every one I am not fortunate, less to say, so I cannot afford anymore than a $40-50 bill to, for instance, try Funky. But will it be worth it ? for just a liuttle step forward?
I am totaly lost and so is my mate .
Any ideasor questions more than welcome.
thank you ever so much for your interest in my troubles..

FuM8 said:
@ revjamescarver :
thanks for that.
Well I was indeed flashing the 3 zip files , from memory, I was into the update.zip one and then my phone rebooted to show this error...
I can access fastboot/rescue mode , for instance, trying to relock the bootloader will end with the "command not allowed" .
I have , apparently, successfully flashed a twrp-3.0.2-2-hi3660.img, the others did not work, so I assume my system still consider that it is in the mha-L090c432b198 version. .
But cannot boot into twrp .
I tried as well the commands "fastboot -w" , result:
"erase successful, but not automatically formatting."
"can't determine partition type"
"failed command not allowed"
that 3 times ...
from all those fastboot commands underneath ,
(bootloader) command list
(bootloader) dmesg
(bootloader) last_dmesg
(bootloader) clearaspflag
(bootloader) refurbish
(bootloader) get_identifier_token
(bootloader) checkKeycardID
(bootloader) get_tamper_flag
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) enter
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) erase_phone_storage
(bootloader) erase_nfc_record
(bootloader) gotohboot
(bootloader) resetgift
(bootloader) ats
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readmeid
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) ddr2gbh
(bootloader) ramdump2gbh
(bootloader) ddr2gstatus
(bootloader) get_temp
(bootloader) writemeid
(bootloader) lock
(bootloader) readusername
(bootloader) writeusername
(bootloader) resethtcdebugflag
(bootloader) load_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) load_modem_emmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
wouldnt it be one that might get me a little forward ? to erase or better (in my dreams) to restore the save I have done from TWRP before flashing ?
I just cannot believe that motherboard or even the baterry (not charging) are somehow faulty .
I am convinced there is a way of doing something, as a noobish I just don't know what and how. .. as suggested before I am just , now, so confused of what I done, how I done it etc... i don't even remember the commands to erase internal storage and show you a printscreen of it !
I had a break from it but now I am determined to give it another try.. the question is what and how ...
By fastboot with which commands... by putting on sdcard something ? by formatting internal system, then how ? this is really fustrating... update went well and .. olala.
Do you believe that funky Huawei could in any mean do something for me ? or the others tools suggested by members in posts before ? or else I'd better call 911 huawei services center here near Marseille and let it up to them ?
As every one I am not fortunate, less to say, so I cannot afford anymore than a $40-50 bill to, for instance, try Funky. But will it be worth it ? for just a liuttle step forward?
I am totaly lost and so is my mate .
Any ideasor questions more than welcome.
thank you ever so much for your interest in my troubles..
Click to expand...
Click to collapse
I would try Dc Phoenix an HCU-CLIENT to fix the phone, in worst case u can flash empty board Firmware and fix it with HCU-Client.
If method 1 does not work u can try method 2.
U need 19 credit to use it 1credit = 1€
Then u have 72h to try it, u can flash how many times u want within 72h.
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Sent from my LON-L29 using XDA Labs

hello , for infos, would funkyhuawei and/or DC Phoenix work if only fastboot mode is accessible ?
@ Mostar088 : when you say
"I would try Dc Phoenix an HCU-CLIENT to fix the phone, in worst case u can flash empty board Firmware and fix it with HCU-Client."
please tell me the way or order to do so , about that "in worst case flash empty firmware" and then fix it with HCU-client...
how could I flash this empty firmware and as well how could I flash it and then fix it with ...HCU client ? from DCPhoenix ?
Please give me detail on the "how to do this " please !!!! thank you very much for your help, very very much, thank you, for trying and making me understand the full steps to complete this . (never used funkyHuawei or DCPhoenix either ... or HCU-Client etc...)
all the best

FuM8 said:
hello , for infos, would funkyhuawei and/or DC Phoenix work if only fastboot mode is accessible ?
@ Mostar088 : when you say
"I would try Dc Phoenix an HCU-CLIENT to fix the phone, in worst case u can flash empty board Firmware and fix it with HCU-Client."
please tell me the way or order to do so , about that "in worst case flash empty firmware" and then fix it with HCU-client...
how could I flash this empty firmware and as well how could I flash it and then fix it with ...HCU client ? from DCPhoenix ?
Please give me detail on the "how to do this " please !!!! thank you very much for your help, very very much, thank you, for trying and making me understand the full steps to complete this . (never used funkyHuawei or DCPhoenix either ... or HCU-Client etc...)
all the best
Click to expand...
Click to collapse
Hi,
If u flash empty board Firmware u need to know your imei and serial nr, if u still have the box from the phone? Because u will loose imei and serial after flash. Best solution is FunkyHuawei, if fastboot works it's a wery big chance u can fix your phone.
U have yo ask in there support, u can ask durrarra here about FunkyHuawei.
https://forum.xda-developers.com/mate-9/how-to/root-updates-rebranding-unbricking-t3702226
Support forum for DcUnlocker here.
https://forum.dc-unlocker.com/forum/modems-and-phones/huawei
HCU-client Support here.
http://forum.gsmhosting.com/vbb/f1004/
Sent from my LON-L29 using XDA Labs

FuM8 said:
thank you guys, take good notice of your suggestions and going to have a serious look deeper into that...
I would prefer than going to a Huawei shop where they'll probably charge me for system, battery and god knows what else !
thanks a bunch to all of you for your interest and help .
Click to expand...
Click to collapse
The best way around this is to try to boot the device into recovery mode.. even if you have a battery not charging.. plug usb cable. try to issue adb commands and reload the chinese version of nougat.. if you can flash the oeminfo.bin file, you half way there...
theres always a work around. i messed up with the oreo beta update and had boot loop. but managed to figure out a way to flash my phone

Hi one and all
Thank you all very much for your time and help.
unfortunately I do not have access to my computer for a while...
that said I keep this thread in pdf format on my sdcard to, in the futur, try all différents options you guys gave me.
well I terribly miss my mate 9 but have not gave up on getting it back to life, thanks to your so precious advices.
take all good care in this freezing winter (I'm living in a mountains so about 1m high of snow around here), thank you ever so much for being so helpful and committed to the XDA community.
À bientôt

Water damage, need to format before fixing

Hi, I had nearly finished setting up my brand new Pixel 3a when I made a classic mistake - & dropped it into a toilet. I pulled it out almost instantly, but the damage had been done. I tried to turn it off, but it wouldn't even let me do that as the screen was completely non responsive & whatever I did kept on rebooting it. It was set to ask for a pin on boot, but I can't type it in as the touch screen doesn't work. The whole screen is completely black, so I can't see anything either. I used Google's Locate my Phone & set it to wipe it for me, but the alarms that I set on the phone keep on going off at the times that I set, so it obviously hasn't wiped it. Sometimes I get some life by pressing Vol Down + Power whilst plugged into via USB - & it comes back with:
Code:
$ adb devices
List of devices attached
03JAY2VCL7 unauthorized
or
Code:
$ adb reboot fastboot
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
All I need to do is to factory reset it, as the data on the phone has security implications & I need to erase it before it gets scrapped (or, slim chance, repaired).
I had connected it to my workstation to copy lots of files across, & I'm sure that I turned on ADB Debugging & Dev Mode, so I'm not sure why I get "device unauthorized"
Can anyone tell me the keys to press to tell it to factory reset please?
TIA, Justin

OK, possible progress.
I pressed Vol Down then Power, & held everything down for about a minute. ADB no longer showed any devices, but fastboot did as root..!
Code:
[email protected] /home/user $ fastboot devices
03JAY2VCL7 fastboot
so I tried this:
Code:
[email protected] /home/user $ fastboot erase data
erasing 'data'...
FAILED (remote: Fastboot command (erase:) is not allowed when locked)
finished. total time: 0.140s
Ahh, it's locked...!
Code:
[email protected] /home/user $ fastboot getvar all
(bootloader) product:sargo
(bootloader) serialno:03JAY2VCL7
[SNIP]
(bootloader) unlocked:no
OK, maybe this will work?
Code:
[email protected] /home/user $ fastboot flashing unlock
...
OKAY [ 0.143s]
finished. total time: 0.143s
I wonder...
Code:
[email protected] /home/user $ fastboot getvar all
(bootloader) product:sargo
(bootloader) serialno:03JAY2VCL7
[SNIP]
(bootloader) unlocked:yes
OK, that looks good...
Code:
[email protected] /home/user $ fastboot erase userdata
erasing 'userdata'...
OKAY [ 4.619s]
finished. total time: 4.619s
OK, that looked really good. So, my question is now did I manage to erase the data on the phone?
I thought that an OEM Unlock also did a factory reset? Am I right in that? Also, I thought that the "fastboot erase data" removed all of my user data? Am I right in that too?
Basically, am I OK now, is the phone completely erased (as much as I can, under the circumstances)

I see this authorization issue every month when I use adb to sideload updates. When you plug the phone into your computer, it pops up a prompt to "Allow USB debugging" before it is allowed. Once authorized, I am not sure how long the authorization lasts for. I think it may be until the next reboot. But for sure, it is not persistent because every month I have to re-authorize it from the same computer as I did last month.
What I find confusing is that even though I check the box that says to remember the authorization, it still asks every time I connect it. Why does this authorization not persist?
So the problem is that you can't authorize the connection. I have a program called scrcpy that mirrors the phone screen onto your computer and lets you use your computer keyboard and mouse, but it has exactly the same problem as it uses adb so you have the same popup where you have to authorize the connection before it can work.
Maybe when it dries out some the screen will start to work again? This phone is one of the easiest on the market to open up: https://9to5google.com/2019/05/10/google-pixel-3a-teardown/ I think if I were really stuck, I would try removing the screen, draining out any liquid and then gently drying it with a heat gun. You can leave the screen connected while doing this and if the screen starts to work then you can authorize the connection.
I did some more thinking about this and it seems like the best solution might be to try to get the phone booted into recovery mode using the power and volume keys. In this case, there is not an authorization prompt. The problem is that you won't be able to see the screen prompts so you will be working blind. https://www.hardreset.info/devices/google/google-pixel-3-xl/recovery-mode/ "Wide data/factory reset" is probably what you want.
Good luck!