Database Info

[Q] HTC Sensation what fastboot options safe to use

Hi
Are there any further fastboot options that are safe to use to maybe clear out anything nasty in there ?
Thanks

spturner said:
Hi
My sensation is currently in a bootloop state despite having flashed a stock rom supplied by football.
Are there any further fastboot options that are safe to use to maybe clear out anything nasty in there ?
I'm clutching at straws here to get this thing working !
Thanks
Click to expand...
Click to collapse
Hi,
Do you mean you flashed a RUU,and you are still getting bootloops?
Have you tried booting without your sim card,and/or your sd card?

Still getting bootloops when restarting.

spturner said:
Yes, flashed new RUU. All ran fine.
When it came to the reboot step I removed the SD card.
Still getting bootloops when restarting.
Have also tried the process via a USB connection with my PC. Same result. Boot loops.
I have removed the SIM throughout all of this.
It seems odd that the flash works fine. No errors at all, but the boot loop still exists.
Click to expand...
Click to collapse
Hi,
Can you get it into safe mode? (Power + volume up)
Do it with your sim card and sd card in.
If it boots,switch off all radios (Airplane mode)
Then, reboot normally.

malybru said:
Hi,
Can you get it into safe mode? (Power + volume up)
Do it with your sim card and sd card in.
If it boots,switch off all radios (Airplane mode)
Then, reboot normally.
Click to expand...
Click to collapse
Thanks for the suggestion

spturner said:
Thanks for the suggestion
Just tried what you said, but no, can't get into safe mode.
Thanks again though.
Click to expand...
Click to collapse
Hi,
Are you s-off?
What's your hboot and firmware?
Which RUU did you run?

If you are soft and have super cid
Change back to your original cid.. Then try to boot and see
To check the cid
fastboot getvar cid
To write another cid
fastboot oem writecid "the cid'
Eg:
fastboot oem writecid HTC__001
Sent from my HTC Sensation using xda premium

Could it be a hardware failure ? Would I still be able to flash a rom if the internal memory or motherboard was messed up ?
Any advice appreciated. I’m totally new to all this, but picking it up as I go along.
Thanks

spturner said:
Here’s the full story as briefly as I can tell it
Bought the phone on ebay a few months ago. Excellent condition. Noted that the IMEI on the phone wasn’t the same as the IMEI on the box. Didn’t think a lot about it. Carried out a full factory reset and phone worked perfectly for about 2 months.
One day I noticed when I powered it up that it went into a boot loop. Showed the HTC white screen 3 times before it did finally burst into life. Thought nothing of it.
A few days later I left it on charge overnight, but it didn’t charge. There was also a notification to say something like “unknown error has occurred, fault report sent to HTC”. After powering off and back up again the phone recharged fine and worked fine.
Then a week or so ago it went into a permanent bootloop. Vibrate, white HTC screen, vibrate, White HTC screen (repeat for ever).
I posted on these forums and was advised to get as much info from the phone (It’s locked and S-ON).
Tried running the HTC unlocker from HTC website, but this failed several times. Maybe the reason why the IMEIs on the phone and box do not match is because a motherboard had been replaced during its warranty period by the previous owner, at least this is what I have read seems to happen? So, I’m stuck with S-ON
I was also advised to contact user football to get a stock RUU. Gave him all my phone info and he supplied the file within 24 hours.
RUU_PYRAMID_ICS_hTC_Asia_WWE_3.33.707.51_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_284970_signed.exe
All attempts at loading it up have been good. No errors at all. Have run it from PC and from MicroSD card.
However, on rebooting it just goes back to being stuck in a bootloop.
This is all the info I have from the phone –
HTC Sensation (ICS stock, S-ON)
CID = HTC_044
Vendor = HTC-ASIA-SEA-WWE
main_version = 3.33.707.51
HBOOT-1.27.0000
Radio-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
After loading up the rom, I did a “fastboot getvar all” and got this –
bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.707.51
(bootloader) serialno: HTxxxxxxxxxx (numbers hidden for posting)
(bootloader) imei: xxxxxxxxxxxxxxx (numbers hidden for posting)
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4020mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So, that’s where I’m at.
Could it be a hardware failure ? Would I still be able to flash a rom if the internal memory or motherboard was messed up ?
Any advice appreciated. I’m totally new to all this, but picking it up as I go along.
Thanks
Click to expand...
Click to collapse
all the RUU flashing and still no success ..then the problem mostly tends towards hardware failure
try one thing ..try to do factory reset from the bootloader if the option is there (i think it has that option )
otherwise ...go to stock recovery ...
once you select the recovery ..from bootloader
you'll be welcomed with a triangle mark ..then press all three buttons together (power ,vol up and vol down)
then you will get some options ..select factory reset and do it ..then try to reboot and see
hope this works ..otherwise ..its hardware error

After selecting Factory Reset there is a few seconds delay then it just bootloops
After selecting Recovery it immediately bootloops. (No delay)

spturner said:
Thanks. Tried what you suggested.
After selecting Factory Reset there is a few seconds delay then it just bootloops
After selecting Recovery it immediately bootloops. (No delay)
Looks like I’m running out of options.
Nexus 4 will have to be ordered in the New Year I guess. Goodbye HTC you piece of junk.
Thanks
Click to expand...
Click to collapse
Wait a sec.. Does the bootloader at the top say "UNLOCKED"? then re lock the bootloader and flash the ruu again
Re lock command
fastboot oem lock
Sent from my HTC Sensation using xda premium

Unfortunately though, no, it shows LOCKED.

[Q] Fastboot works, ADB does not

So I'm having USB related issues with my Nexus 5 after waking up today. The phone will not charge if powered on. It will not detect a USB connection while powered on either. Currently running stock rom/bootloader. The will charge while powered off, but only for period of around 10s, before the screen turns off then back on for another 10s period of charging, over and over. I'm trying to complete returning to stock on my device because to me it seems to be a hardware related issue. So now the crux of the problem. Working with USB works in fastboot mode, but not when the device has been powered on.
OS: Mac OSX 10.8
Device OS: Latest android 4.4.2
Build: KOT49H
Code:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) off-mode-charge: true
Any ideas how I can try and push the files I need to my device to reset the tamper flags?

If you're still rooted get bootunlocker from the play store. Use it to reset the tamper flag
Sent from my Nexus 5

jd1639 said:
If you're still rooted get bootunlocker from the play store. Use it to reset the tamper flag
Sent from my Nexus 5
Click to expand...
Click to collapse
This got me thinking. I ended up emailing myself the bootunlocker zip from the Unrooting thread to get it over to my device. Pretty surprised I didn't think of this earlier.

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?

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