Related
Hi,
some of them have seen my interest on this tab,
unfortunately, it seems it has gone a bit too far.
today,i made a reset through the parameters, and it stuck (had a custom recovery and root)
trying to hard reset did not help
now, i've got an 0x19000008 error when trying to erase userdata with hard-reset procedure
and i'm struck on iconia tab logo
trying to recover my backup using nikagl recovery without data partition did not help as it remains block
i still have access to fastboot
what is your advice on that ??
which trick might help or is it good for service ?
i have the same problem with you!
then welcome
my tab is at acer service from last monday. status is "under repair'
wiating for news..
jokerzlh said:
i have the same problem with you!
Click to expand...
Click to collapse
can you describe clearly what you did and what you have currently ?
BENETNATH said:
Hi,
some of them have seen my interest on this tab,
unfortunately, it seems it has gone a bit too far.
today,i made a reset through the parameters, and it stuck (had a custom recovery and root)
trying to hard reset did not help
now, i've got an 0x19000008 error when trying to erase userdata with hard-reset procedure
and i'm struck on iconia tab logo
trying to recover my backup using nikagl recovery without data partition did not help as it remains block
i still have access to fastboot
what is your advice on that ??
which trick might help or is it good for service ?
Click to expand...
Click to collapse
i installed the nikagl CWM recovery (version5.8.5), I entered the CWM and tried to wipe data/factory reset, it stuck!
i reset and back to CWM, this time i only flash the zip, but it stuck again!
after that i can't enter the system anymore, i'm stuck on iconia tab logo like you.
so i try to enter fastboot and install the stock recovery, then i use it to flash the update.zip in SD card, but every time the flash will stuck in 1/5 of the whole progress bar, I changed it with other rom zip, or even change the SD card, it didn't work anyway! but It used to be fine with my tab.
anyone can help us? :crying:
can you use fastboot and try this command
fastboot erase userdata
and
fastboot erase cache
BENETNATH said:
then welcome
my tab is at acer service from last monday. status is "under repair'
wiating for news..
Click to expand...
Click to collapse
your tab will be repaired soon, i think.
but i have nowhere to repair, because the A510 doesn't go to market of China mainland this moment!
btw, i really realy hate to fill in the code in the image! so hard for me to read.
jokerzlh said:
your tab will be repaired soon, i think.
but i have nowhere to repair, because the A510 doesn't go to market of China mainland this moment!
btw, i really realy hate to fill in the code in the image! so hard for me to read.
Click to expand...
Click to collapse
sad for you the absence of repair service..
can't you get a repair where you purchased (internet vendor) ?
no image for me
BENETNATH said:
can you use fastboot and try this command
fastboot erase userdata
and
fastboot erase cache
Click to expand...
Click to collapse
I had a try, but it seems doesn't work.
erasing 'userdata' ... failed <remote:<19000008>>
erasing 'cache' ... failed <command write failed <NO Such file or directory>>
ok, seems your data partition is corrupted.
the only escape way would be to have nvflash tools, which we currently do not have..
so two option:
1) wait until the dev manage to get a solution, with a unusable brick
2) send to repair center and possibly pay to have a working device..
BENETNATH said:
ok, seems your data partition is corrupted.
the only escape way would be to have nvflash tools, which we currently do not have..
so two option:
1) wait until the dev manage to get a solution, with a unusable brick
2) send to repair center and possibly pay to have a working device..
Click to expand...
Click to collapse
when i use the command you gave, there're some text on tab screen:
white text: StorMgr Formatting UDA
red text: Failed to process command erase:userdata error ( 0X19000008 )
I think you are right! I can only wait.
thanks for your help
it seems that on some device, keeping trying worth the cost
so i would suggest that if you plan to wait, you should try from time to time some hard reset procedure (vol down + lock switch triggering on boot)
eg . http://forums.lenovo.com/t5/IdeaPad...er-Error-0x19000008-after-Factory/td-p/759121
good news, i just have an email from acer customer service.
they gave me a tracking number to get my device back
Nice
That was a quick repair. Does Acer charge you for anything (repairs or at least shipping)?
it seems that the whole thing was free, will confirm when i have the package
but at least i did not receive any quote before repairing..
and for the first shipment i'd received a free shipping card.
now, i hope that the tab will be completely fixed (partition bricked, and my headphone jack was non working)
BENETNATH said:
it seems that on some device, keeping trying worth the cost
so i would suggest that if you plan to wait, you should try from time to time some hard reset procedure (vol down + lock switch triggering on boot)
eg . http://forums.lenovo.com/t5/IdeaPad...er-Error-0x19000008-after-Factory/td-p/759121
Click to expand...
Click to collapse
thanks, but i'm not lucky!
i tried many many times, it still show:
Erasing userdata...
Unrecoverable Bootloader Error (0x19000008)
it's time to give it up:crying:
let it rest a bit, and watch olympic games
then try again one day or the other..
sorry, no other solution. or find a way to have it repaired (send it to me )
BENETNATH said:
good news, i just have an email from acer customer service.
they gave me a tracking number to get my device back
Click to expand...
Click to collapse
congratulation!
---------- Post added at 11:29 PM ---------- Previous post was at 11:15 PM ----------
BENETNATH said:
it seems that the whole thing was free, will confirm when i have the package
but at least i did not receive any quote before repairing..
and for the first shipment i'd received a free shipping card.
now, i hope that the tab will be completely fixed (partition bricked, and my headphone jack was non working)
Click to expand...
Click to collapse
waiting for your test report.
When you go to get your device back, is that possible to ask Acer for some Official Flash Tool or some thing like that?
that was my initial plan if they asked for some money (ok to pay, but with nvflash tool )
I already tried to ask Acer for a flash tool but they told me they cannot provide any. Updates will ony come OTA.
We have top hope that a tool will be leaked like for the Tegra2 devices.
MOTO G XT1068
Hi folks!!! Moto g xt1068, after several roms flash and tries of every kind my phone wont wake up, it just remains in logo, i does go to fastboot mode but i cant hard reset, once it did but it appeared fail 0 nowadays it wont react to de first command with lying android, please help!!! I would need to know what to do, some process to restaure the whole system of the phone it self, i repeat, i dont know what was actually done with this phone, it came to me on bootloop, and i cant unbrick it
I have flashed 5.2, 4.4.4, several times, on fastboot, and logs were just perfect. HELP please.
Pomar91 said:
MOTO G XT1068
Hi folks!!! Moto g xt1068, after several roms flash and tries of every kind my phone wont wake up, it just remains in logo, i does go to fastboot mode but i cant hard reset, once it did but it appeared fail 0 nowadays it wont react to de first command with lying sndroid, please help!!! I would need to know what to do, some process to restaure the whole system of the phone it self, i pepeat, i dont know what was actually done with this phone, it came to me on bootloop, and i cant unbrick it
I have flashed 5.2, 4.4.4, several times, on fastboot, and logs were just perfect. HELP please.
Click to expand...
Click to collapse
do you know if the bootloader is unlocked? if not, that may limit what you can flash and boot. are you wiping the data after flashing the firmware?
are you flashing everything in the stock firmware, or just parts?
if unlocked and didnt wipe, try fastboot -w
if locked, flash the newest firmware available, even that may not be good enough if the absolute newest isnt avaiable, then use the wipe command.
finally, i have no experience with your device. im just stating common practice from other motos i have owned.
Yeah, thanks for replaying, I did.unlock bootloader bootloader in order to better work with fastboot, but I'm pretty sure such command was included, d wipe one, as I followed several co.vibration of commands I found here at xda, thanks again for attention and time, what u mean is hard reseting by fastboot seen I can't by d phone in fastboot mode right?
What do u think? When ever u have d time 4 sure, maybe u recommend me to an expert, do you know one?
Pomar91 said:
Yeah, thanks for replaying, I did.unlock bootloader bootloader in order to better work with fastboot, but I'm pretty sure such command was included, d wipe one, as I followed several co.vibration of commands I found here at xda, thanks again for attention and time, what u mean is hard reseting by fastboot seen I can't by d phone in fastboot mode right?
Click to expand...
Click to collapse
right
if you flash ALL the partitions in the stock file, and wipe (-w) with an unlocked bootloader, its extremely rare to not boot.
I have been trying this smartphones home fixing and motog is always been ok, it's just weird this, could u recommend me to an expert,and thanks so much
Pomar91 said:
What do u think? When ever u have d time 4 sure, maybe u recommend me to an expert, do you know one?
Click to expand...
Click to collapse
im actually quite knowledgeable with moto, just not your specifically.
there really is no special fix. if you flash all stock partitions, and all pass/install properly, there isnt much else you can do to fix it.
Ok my friend and allow me to call u that, I will review everything I have done, and I will freak u out with details ,logs screen shots, all of the d stuff, isn't it this d way u guys learn? So we both will get better, how about that, maybe tomorrow I will get u whole procedure, maybe u can send me the whole.commands list, a really complete one, another thing. What about kernel and cwm?
Pomar91 said:
Ok my friend and allow me to call u that, I will review everything I have done, and I will freak u out with details ,logs screen shots, all of the d stuff, isn't it this d way u guys learn? So we both will get better, how about that, maybe tomorrow I will get u whole procedure, maybe u can send me the whole.commands list, a really complete one, another thing. What about kernel and cwm?
Click to expand...
Click to collapse
yea, that would be good, copy all the text from the fastboot terminal so i can see it.
kernel is flashed as part of the stock firmware. cwm is a custom recovery and thats not something we need to think about until its fixed.
Man, even if we can't fix this at the end, I'M LIKE SO GRATEFUL FOR UR TIME, WE WILL IMPROVE together, won't let u down
Hey, @Pomar91, what our friendly fellow is telling you about was the wiping part. Did you do that? That might be the problem - the cause for your bootloop.
tetakpatalked from Nexus 7 flo
Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?
Pomar91 said:
Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?
Click to expand...
Click to collapse
yes its the same as a hard reset, its what i was asking you in my first reply if you did it.
fastboot -w <--this is the hard reset fastboot command
---------- Post added at 06:35 PM ---------- Previous post was at 06:34 PM ----------
Pomar91 said:
Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?
Click to expand...
Click to collapse
one more thing, please use the "Quote" button when you reply, so i know you replied to me. thanks
Thanks I will check it out, he did talk.about it, I thought it was a short form, let say the lad version I did flash was kit Kat, successfully flashed, so now I just go and try this command on fast boot, like there should be no need for reflashing, right, just this last command, I'm I right?
Pomar91 said:
Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?
Click to expand...
Click to collapse
On the example of an entire firmware flash on moto G (which is my preferred way to do it manually, one by one command) you can see the lines including "erase" what my point was:
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system xxxfilename
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
tetakpatalked from Nexus 7 flo
Pomar91 said:
Thanks I will check it out, he did talk.about it, I thought it was a short form, let say the lad version I did flash was kit Kat, successfully flashed, so now I just go and try this command on fast boot, like there should be no need for reflashing, right, just this last command, I'm I right?
Click to expand...
Click to collapse
right
and please stop using the "quick reply" button and use " "reply" thanks
---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------
tetakpatak said:
On the example of an entire firmware flash on moto G (which is my preferred way to do it manually, one by one command) you can see the lines including "erase" what my point was:
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
hmm, will these new motos actually re-write the partition table using fastboot? the older ones wouldnt. you had to use mfastboot.
bweN diorD said:
hmm, will these new motos actually re-write the partition table using fastboot? the older ones wouldnt. you had to use mfastboot.
Click to expand...
Click to collapse
Possibly some of the partitions had to be enlarged after KitKat. Numerous devices have been doing that step due to ever growing Android OS
I think it was the procedure for the 1st gen Moto G
Do you own it? I have just flashed it on some occasions for friends and family who own it.
tetakpatalked from N7100
all i got
Ok people, i didnt do the whole procedure again, as im sure i have done it properly. The erasing two last steps have been done two. I also used an auto restore script that contains all of the commands, and I have tried before successfully. For sure it includes erase data and cache, now I have found some problems, like preflash validation failed, and preflash validation for tz failed too, the rest just seems ok. So the problem with appear at Motorola screen while flashing in two pink lines I have captured for you. But I do have some other details. After unlock B logo, and Motorola logo, the one in blue, the phone does that part with the world, like that one that turns into many thins with the airplane, and the earth turning around, after it will just go to the black screen, were it will just remain. One of you said something about using Mfasboot and not fastboot it self, I don’t even know the diference, thanks, im sending shots about it. As I don’t know if this auto script I talked about actually works, im gonna retry manually to send u the shots, im using mfastboot this time I guess, I used the v2 zip on the rom file. So as u see I did not finish as the error appears the same preflash validation and for tz, as the same screen showed in the cellphone. That is it.
Another thing, im using 4.4.4 retail, I guess this is stock rom, maybe its all about that, thanks a lot friends, that s all I got.
dudes i dont know how to make this message reach all of u that are helping, please could u help me with that.
that is it friend
all i got
Ok people, i didnt do the whole procedure again, as im sure i have done it properly. The erasing two last steps have been done two. I also used an auto restore script that contains all of the commands, and I have tried before successfully. For sure it includes erase data and cache, now I have found some problems, like preflash validation failed, and preflash validation for tz failed too, the rest just seems ok. So the problem with appear at Motorola screen while flashing in two pink lines I have captured for you. But I do have some other details. After unlock B logo, and Motorola logo, the one in blue, the phone does that part with the world, like that one that turns into many thins with the airplane, and the earth turning around, after it will just go to the black screen, were it will just remain. One of you said something about using Mfasboot and not fastboot it self, I don’t even know the diference, thanks, im sending shots about it. As I don’t know if this auto script I talked about actually works, im gonna retry manually to send u the shots, im using mfastboot this time I guess, I used the v2 zip on the rom file. So as u see I did not finish as the error appears the same preflash validation and for tz, as the same screen showed in the cellphone. That is it.
Another thing, im using 4.4.4 retail, I guess this is stock rom, maybe its all about that, thanks a lot friends, that s all I got.
dudes i dont know how to make this message reach all of u that are helping, please could u help me with that.
maybe u know what exactly stock rom for xt1068 brasil moto g
aanother thing, this mobile screent shot is the same mistake i got for the auto restore and the manual on fastboot
Pomar91 said:
Ok people, i didnt do the whole procedure again, as im sure i have done it properly. The erasing two last steps have been done two. I also used an auto restore script that contains all of the commands, and I have tried before successfully. For sure it includes erase data and cache, now I have found some problems, like preflash validation failed, and preflash validation for tz failed too, the rest just seems ok. So the problem with appear at Motorola screen while flashing in two pink lines I have captured for you. But I do have some other details. After unlock B logo, and Motorola logo, the one in blue, the phone does that part with the world, like that one that turns into many thins with the airplane, and the earth turning around, after it will just go to the black screen, were it will just remain. One of you said something about using Mfasboot and not fastboot it self, I don’t even know the diference, thanks, im sending shots about it. As I don’t know if this auto script I talked about actually works, im gonna retry manually to send u the shots, im using mfastboot this time I guess, I used the v2 zip on the rom file. So as u see I did not finish as the error appears the same preflash validation and for tz, as the same screen showed in the cellphone. That is it.
Another thing, im using 4.4.4 retail, I guess this is stock rom, maybe its all about that, thanks a lot friends, that s all I got.
dudes i dont know how to make this message reach all of u that are helping, please could u help me with that.
Click to expand...
Click to collapse
is there any possibility you can post the actual fastboot dialogue right into the post? not a screen shot.
So as you may know... I tried a little too hard and bricked my Mate 8.
I can get into flashboot with a black screen. I dug through the flashboot image and found some things that might help. Namely, doing the following:
fastboot flash rescue_recovery RECOVERY.IMG (from any Huawei rom version)
fastboot getvar rescue_enter_recovery
This will boot my phone into a mode where the light blinks green three times and red one time. It says it's some kind of HiSuite recovery mode that's being launched, from Fastboot, but no USB device is detected by the computer when it's plugged in.
I think this may be the entrypoint to recovering the phone (My guess is bootloader is the issue and needs to be reflashed, but can't be from fastboot). But I can't figure out how to proceed from here, having no recognized USB device. Putting recovery files on an SD card does nothing.
The other thing I've tried is using HiSuite with the phone in this mode, where it's recognized (it's a fastboot device so it should be...) but trying to do any kind of recovery from HiSuite says my device is not supported. NXT-AL10 is listed in supported devices so my guess is it's because of the unlocked bootloader.
What I'm hoping is that someone can try running the commands from fastboot and see if they get the same green/red light blinking status. Also, hoping that someone might find a way to flash an update.app from there. I can't get into any recovery mode other than that and fastboot, and flashing the permitted partitions (system, cache, userdata, recovery, cust) from flashboot doesn't help.
Thanks for anyone who can offer anything. If I can get my device working, I'll resume my work on finding various firmware versions and fixing the notification bug, but until then, I'm out of luck. My device is from China, so local Huawei Japan can't help me, too, sadly.
Can you fastboot other partitions except 5 partitions above ?
My idea , Maybe other parttition has problem but we can't know what partitions. If we fastboot flash other partitions maybe help.
Sent from my HUAWEI NXT-L29 using Tapatalk
im presuming uve most likely already checked that option, but just to make sure: the italian knife tool includes an experimental unbrick option for such emergency cases. maybe acer73 can provide some input there, since i havent used that option yet (might just be the inbuilt erecovery, in which case its useless for you, but hey, better be thorough, right?)
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
My tool don't work in this case. Duraaraa I give you in pm a Link for bulk driver
Just to update, the only partitions fastboot lets you flash are the ones mentioned above... cust, system, cache, recovery, userdata
There are also two special things that can be flashed, which aren't known publicly. One is called slock (I've yet to figure out how to use this) the other is rescue_recovery (this is what I was trying to work with.)
As for the information sent to me by acer, I appreciate it but unfortunately I don't see any such device as USBVID_12D1&PID_3609&REV_0000 so I can't do much with it.
duraaraa said:
Just to update, the only partitions fastboot lets you flash are the ones mentioned above... cust, system, cache, recovery, userdata
There are also two special things that can be flashed, which aren't known publicly. One is called slock (I've yet to figure out how to use this) the other is rescue_recovery (this is what I was trying to work with.)
As for the information sent to me by acer, I appreciate it but unfortunately I don't see any such device as USBVID_12D1&PID_3609&REV_0000 so I can't do much with it.
Click to expand...
Click to collapse
bro my mate 8 was working fine with fastboot but now i cant flash any thing
it alwayes sayes failed command not allowed
my bootloader is already unloacked
i dont know what happend
rowihel2012 said:
bro my mate 8 was working fine with fastboot but now i cant flash any thing
it alwayes sayes failed command not allowed
my bootloader is already unloacked
i dont know what happend
Click to expand...
Click to collapse
Probably you turned on the "find my phone" feature.
duraaraa said:
Probably you turned on the "find my phone" feature.
Click to expand...
Click to collapse
i dont have this feature in my l29
rowihel2012 said:
i dont have this feature in my l29
Click to expand...
Click to collapse
Is it possible that you had that option activated in your previous ROM and now it's still active even if you can't find it anymore in your latest flashed ROM?
themissionimpossible said:
Is it possible that you had that option activated in your previous ROM and now it's still active even if you can't find it anymore in your latest flashed ROM?
Click to expand...
Click to collapse
When i flashed the chines rom i actvate it
But i restored my stock gsm backup from twrp then flashed the latest gsm update
This could be from the chines???
How could i fix this??
rowihel2012 said:
When i flashed the chines rom i actvate it
But i restored my stock gsm backup from twrp then flashed the latest gsm update
This could be from the chines???
How could i fix this??
Click to expand...
Click to collapse
IMHO this option is somehow hardcoded and not changeable/resettable flashing a new ROM.
Otherwise it will be easy for a thief to disable this protection system...
interesting, so basically hed have to somehow reflash the chinese rom and manually disable that function in order to get his phone going again....
themissionimpossible said:
IMHO this option is somehow hardcoded and not changeable/resettable flashing a new ROM.
Otherwise it will be easy for a thief to disable this protection system...
Click to expand...
Click to collapse
so how do disaple this feature?
---------- Post added at 03:40 PM ---------- Previous post was at 03:30 PM ----------
so if i replaced my mate 8 with other one i will have the same problem?
rowihel2012 said:
so if i replaced my mate 8 with other one i will have the same problem?
Click to expand...
Click to collapse
I don't think so, on the new phone just remember not to activate the Find my phone option before flashing.
themissionimpossible said:
I don't think so, on the new phone just remember not to activate the Find my phone option before flashing.
Click to expand...
Click to collapse
If you enable this option, you can use the eRecovery to flash the rom freshly over again. On first bootup it will ask for your huawei ID and password to activate the phone. So you can't get around it by flashing. You need to know your huawei ID to set up the phone, then you can just not enable the option.
duraaraa said:
If you enable this option, you can use the eRecovery to flash the rom freshly over again. On first bootup it will ask for your huawei ID and password to activate the phone. So you can't get around it by flashing. You need to know your huawei ID to set up the phone, then you can just not enable the option.
Click to expand...
Click to collapse
just sold it
will get new one after 2 dayes
i hope this problem not found with the new one :laugh:
i sure hope u told the buyer about the fastboot problem, otherwise thats considered fraud
jbmc83 said:
i sure hope u told the buyer about the fastboot problem, otherwise thats considered fraud
Click to expand...
Click to collapse
dont worry the buyer dont love rooting
hahah
---------- Post added at 02:34 AM ---------- Previous post was at 02:22 AM ----------
themissionimpossible said:
I don't think so, on the new phone just remember not to activate the Find my phone option before flashing.
Click to expand...
Click to collapse
but how could find my phone feature block fastboot to flash img?
weard .at the same time i tried fasher app and worked fine
:silly:
rowihel2012 said:
but how could find my phone feature block fastboot to flash img?
Click to expand...
Click to collapse
There must be active some anti-theft countermeasures, to block removing that protection simply by flashing via fastboot...
rowihel2012 said:
dont worry the buyer dont love rooting
hahah
---------- Post added at 02:34 AM ---------- Previous post was at 02:22 AM ----------
but how could find my phone feature block fastboot to flash img?
weard .at the same time i tried fasher app and worked fine
:silly:
Click to expand...
Click to collapse
so you didnt tell him... remind me never to buy anything from you[emoji14]
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
Some time ago I bought a Honor 6 bricked by a firmware upgrade.
I done some reading, I asked friends but I couldn't fix it. I opened a topic here and many people tried to help me. Nothing worked... I contacted some experienced people from this, and a Romanian forum, but no success. I was trying to fix it for 2 months now.
Eventually, I came across a solution made by DC-Unlocker Team.
I bought some credits to be able to run the solution and with a few mouse clicks my phone was repaired. Now it works perfectly. I do have some questions to ask about several issues in Honor 6, but let me describe how I fixed my phone with this solution.
I would like to underline that I am in no way related to the DC-unlocker Team.
The software can repair most of the Honor firmware problems:
Bricked phones, bootloop, stuck in fastboot mode
It can write full firmware update.app in fastboot mode
Can flash phones with locked bootloader or FRP. (No need to get the bootloader unlock code)
The whole procedure is detailed here, but let me describe the steps which I took. I also attach few screenshots of the process.
1. Make sure, that you install Huawei Hisuite (for drivers), or Universal ADB driver.
2 Enter fastboot mode on the phone and connect it to your computer. Remove the SD card if there is one installed in the phone.
3. Check if computer detects the phone is fastboot mode, run fastboot devices command
4. The firmware repair process will need 15 credits (which will cost 15 euro). You can buy the credits here
Credits are deducted immediately, but you can flash the same phone any time you want for 72 hours.
5. After you buy the credits, download the software client here
Supported models and features here
6. Start the program. It will ask your credentials for the DC-unlocker server. You receive those credentials when you buy the first time credits.
7. In the DC Phoenix software, select fastboot mode, select "App files" tab.
8. Carefully chose the update.app for recovery. Be careful, not to flash a different hardware variant (in a H60-L12 flash only H60-L12 firmware and so on). Not doing so will probably break your phone forever. The program does not check compatibility, nor the phone in this mode.
9. Open the update app by clicking right end of the line "Update file".
10 Click "Update". Program will unpack the update.app and will start to flash all the chosen img packs.
Here I got really scared, because first write was unscuccessful, I got this message: "PTABLE partition UPDATE ... FAILED
I thought that I threw away my money. But program managed really well: "Activating Backdoor: DONE"
After this step, everything went well: "Writing device finished OK"
11. Power cycle your phone. It should start normally.
12. On the dc-unlocker site they say: "Then you need to repeat flashing, but now in upgrade mode". I did not ran this step. I made a full factory reset and started OTA upgrades. Phone is now version: EMUI4.0.1_H-60-L12_6.11.1.
It has Android 6, EMUI 4.0.1.
At one moment I thought that is better to go back to a previous version and flashed an older tested firmware, it worked without any problems..
Although my experience is limited to this phone only, I recommend this solution. Please feel free to ask, I will try to answer any questions.
So the software deactivates itself after 72h?
zinko_pt said:
So the software deactivates itself after 72h?
Click to expand...
Click to collapse
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
janos666 said:
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
Click to expand...
Click to collapse
But is there any refund in case it doesn't work?
zinko_pt said:
But is there any refund in case it doesn't work?
Click to expand...
Click to collapse
No, there are no refunds, but if you have a phone with only firmware error and you chose the right firmware, there are big chances that the program will recover your phone.
But if security damaged, you will need factory file.
method 2 can help in 99% cases, but only if there 100% compatible file.
They have only H60-L04 factory file.
Repairing by this method, will erase phone security data (simlock, IMEI and other numbers)
You will lose all numbers!, IMEI will be 0000000000000000
You can repair missing numbers with third party software, like HCU client
You can use DC-unlocker credits on HCU client, software will require 8 credits for repair service.
Thanks. When there's no other solution it might be handy.
i'm intrested in this.
I have an Honor 6 plus pe-ul00 i can't fix the brick.
with that can i flash any firmware for my device (pe-ul00) and get it to work?
Split74 said:
i'm intrested in this.
I have an Honor 6 plus pe-ul00 i can't fix the brick.
with that can i flash any firmware for my device (pe-ul00) and get it to work?
Click to expand...
Click to collapse
Hi!
I don't see this device on the supported phones list.
You should contact their support to confirm if the program works with your device.
They are very kind and helpful. If you need a contact email, I can send in private.
Best regards,
Janos
janos666 said:
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
Click to expand...
Click to collapse
U shouldn't need to do this to flash back to stock. Sounds like a scam
Tmobilefan906 said:
U shouldn't need to do this to flash back to stock. Sounds like a scam
Click to expand...
Click to collapse
It seems that you did not understand me.
If you read this topic you will learn that in some cases, flashing back the 4 img's will not help.
In some cases you cannot access 3 button recovery or TWRP (although you flashed it correctly), to be able to do a complete flash write.
This was the case when this program (which you call a scam!) proved a life-saver.
I am very happy that I could restore my phone because I like it very much.
janos666 said:
It seems that you did not understand me.
If you read this topic you will learn that in some cases, flashing back the 4 img's will not help.
In some cases you cannot access 3 button recovery or TWRP (although you flashed it correctly), to be able to do a complete flash write.
This was the case when this program (which you call a scam!) proved a life-saver.
I am very happy that I could restore my phone because I like it very much.
Click to expand...
Click to collapse
It was my OPINION dude. Didn't mean to offend.
Tmobilefan906 said:
It was my OPINION dude. Didn't mean to offend.
Click to expand...
Click to collapse
Yep, the SW works OK ..
First it extracts the IMG files from the UPDATE.APP - same as Huawei Update Extractor. Then it flashes all IMG files (+-) using fastboot - but here is the catch.. it uses an undocumented feature of fastboot:
fastboot.exe oem backdoor get
And then generates the necessary unlock file/sequence which it then feeds to the phone using:
fastboot.exe flash slock XXX_Unlockcode.bin
So indeed it does work - I've used it, you can go between EMUI3.1 and 4.0/0.1 no problem - if we knew how to generate the unlock file for the "backdoor" - we would be all set However we don't and the generated file changes with every "oem backdoor get" request..
But 15EUR seems almost reasonable for this (I'd prefer 10EUR hehe) - otherwise, we would need to use parted and dd the necessary partitions which is more dangerous and we don't have a large enough community of users to dump the necessary partitions..
janos666 said:
Hi!
I don't see this device on the supported phones list.
You should contact their support to confirm if the program works with your device.
They are very kind and helpful. If you need a contact email, I can send in private.
Best regards,
Janos
Click to expand...
Click to collapse
It worked! Fail on normal flash the It issued that damn BACKDOOR install and now i'm back!
Got only 2 "problems":
1. I got 2 IMEI CODES
2.I can't see all my internal storage:
I tried a wipe internal storage + factory reset with emui rec and with twrp, but nothing. TWRP say something like: Can't wipe ..data/... No such directory
Inviato dal mio PE-UL00 utilizzando Tapatalk
I will think about this issue, but a quick idea is: you could try a full firmware update from SD card with the 3 button method and a factory restore after.
Happy to hear that buddy... I threw away a honor 6 about two months ago, was stuck in fastboot for more than a month, if had it, I am sure, this would have fixed it.:crying:
Another Honor 6 saved with this method, this time a H60-L02
I guess you really threw away your money, because you can extract the update.app with huaweiupdateextractor( free ) and flash the cust.img system.img boot.img and recovery.img with adb and fastboot. But if you had the “Command not allowed error“ when you try to flash, even your software wouldnt have helped you, because it basically does the same as i explained above.
Sent from my H60-L04 using XDA-Developers Legacy app
---------- Post added at 12:24 AM ---------- Previous post was at 12:15 AM ----------
Edit: the unlock bin can be easily made by editing one current .bin, by replacing it with the current unlock code.
Sent from my H60-L04 using XDA-Developers Legacy app
I can confirm i fix my Honor 6 hard brick with Dc Phoenix
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
Lukalion said:
I guess you really threw away your money, because you can extract the update.app with huaweiupdateextractor( free ) and flash the cust.img system.img boot.img and recovery.img with adb and fastboot. But if you had the “Command not allowed error“ when you try to flash, even your software wouldnt have helped you, because it basically does the same as i explained above.
Sent from my H60-L04 using XDA-Developers Legacy app
---------- Post added at 12:24 AM ---------- Previous post was at 12:15 AM ----------
Edit: the unlock bin can be easily made by editing one current .bin, by replacing it with the current unlock code.
Sent from my H60-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It was impossible for my L02 to be fixed using unbrick fuction of multi tool
You did not do the step i said in Edit
Sent from my H60-L04 using XDA-Developers Legacy app
I already wrote something like this in a similar thread, but for another device (read the device name wrong), so I thought i should post it in the right place.
I have been playing too much with stuff that i probably shouldn't have been so hasty about. So i have finally arrived here on the ERROR MODE (with unstoppable boot loop), which looks exactly like the bootloader only it says ERROR MODE instead of whatever, where i can't get into any other type of recovery or fastboot mode, no matter what button combinations i do. I previously could get to the fastboot mode, but i was still stuck so..... I made the very wise choice of relocking (since i hadn't tried that) my device, and now I can't even access fastboot (nothing. tried every button combination i can think of). So I am sitting here wondering if this is the end of the journey with my... relatively new phone... So, yes. No way of accessing anything and my phone is in a reboot loop i can't stop. Only thing is the error code i get "ERROR!":
"Func NO : 16 (lpm3 image)"
"Error NO : 1 (security verify failed!)"
Is there hope? or no?
Also noticed the light flashes green 3 times then red 1, then continues this pattern. Idk if that's useful or not.
Here's a pic.
It doesn't seem to have fastboot connection here, either.
OP were you ever able to fix this issue?
@Kimuchuu its not clear from OP had you relocked your bootloader if yes then you cant modify your system you need to have unlocked bootloader inorder to perform system modifications.
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
You can be really happy that they sent you a new one, but it's not a unique case, in CZ there were few people who had same or similar issue and Repair service gave them new phone too.
Kimuchuu said:
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
Click to expand...
Click to collapse
You got lucky they sent you a new one considering that you messed up the previous one. Take good care this time.
Sent from my Honor 8 using XDA Labs
Kimuchuu said:
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
Click to expand...
Click to collapse
thats nice to hear ,man you are lucky
How exactly did you reach out to the service center?
I'm in the same situation and right now im typing the e-mail.
Im wondering what to write in the hope of getting a new one, too.
oberfeldwedler said:
How exactly did you reach out to the service center?
I'm in the same situation and right now im typing the e-mail.
Im wondering what to write in the hope of getting a new one, too.
Click to expand...
Click to collapse
In which country do you live? Just go to the nearest authorized Huawei service center. You can find them in Google.
Sent from my Honor 8 using XDA Labs
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
BigBrad75 said:
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
Click to expand...
Click to collapse
A guide how you solved your problem would help others who screwed their device to solve their problem
Update: I let the battery drain completly in this error mode and after plugging it in the Huawei eRecovery appeared...
i think i can dLoad it and get it back to work...
---------- Post added at 11:41 AM ---------- Previous post was at 11:35 AM ----------
BigBrad75 said:
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
Click to expand...
Click to collapse
But your bootloader wasn't locked i guess...
oberfeldwedler said:
Update: I let the battery drain completly in this error mode and after plugging it in the Huawei eRecovery appeared...
i think i can dLoad it and get it back to work...
Click to expand...
Click to collapse
But did you try the first option in erecovery?
Sent from my Honor 8 using XDA Labs
adriansticoid said:
But did you try the first option in erecovery?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
No success
Then i tried to unlock my bootloader but got ERROR MODE again...
I'm letting the battary drain so i can enter eRecovery. Hopefully dLoad works.
By the way does anyone know whats the difference between Recovery.img an recovery2.img?
I remember flashing one of them before relocking my bootloader.
oberfeldwedler said:
No success
Click to expand...
Click to collapse
Then dload is your next choice.
Sent from my Honor 8 using XDA Labs
oberfeldwedler said:
No success
Then i tried to unlock my bootloader but got ERROR MODE again...
I'm letting the battary drain so i can enter eRecovery. Hopefully dLoad works.
By the way does anyone know whats the difference between Recovery.img an recovery2.img?
I remember flashing one of them before relocking my bootloader.
Click to expand...
Click to collapse
Recovery is the one which installs ota updates . Erecovery is an emergency recovery. It can help u restore ur phone to previous version by flashing full original firmware
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLOADER
oberfeldwedler said:
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLAODER
Click to expand...
Click to collapse
Well , great that unbricked and your last line , it is to be in bold . Thanks for it. Headsup:victory:
oberfeldwedler said:
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLAODER
Click to expand...
Click to collapse
yup thats the main point if you are not fully stock and soft bricked you are not advised to lock your bootloader. Once you locked your bootloader you can no more modify your system.