Hey guys, so heres my history
Stock HTC One M8 on Verizon, rooted with weaksauce, then s-off with firewater (took one chug), then installed cwm unnofficial until twrp came out. when the 2.7.0.2 came out, I flashed it via terminal emulator. Suddenly, I could not boot past the recovery. it just would boot into recovery every time I rebooted. So I used the TWRP terminal emulator to flash it once more, thinking that would help. Now the phone wont boot at all, just rumbles and vibrates like its turning on and crashing off. Holding vol up+power and vol down+power does not seem to work, and im going to be so upset if I just bricked my phone. Does anyone have some tips?
wonkizzle said:
Hey guys, so heres my history
Stock HTC One M8 on Verizon, rooted with weaksauce, then s-off with firewater (took one chug), then installed cwm unnofficial until twrp came out. when the 2.7.0.2 came out, I flashed it via terminal emulator. Suddenly, I could not boot past the recovery. it just would boot into recovery every time I rebooted. So I used the TWRP terminal emulator to flash it once more, thinking that would help. Now the phone wont boot at all, just rumbles and vibrates like its turning on and crashing off. Holding vol up+power and vol down+power does not seem to work, and im going to be so upset if I just bricked my phone. Does anyone have some tips?
Click to expand...
Click to collapse
You are not bricked. Try flashing the stock recovery which can be found in this thread.
http://forum.xda-developers.com/showthread.php?t=2708291
droidkevlar said:
You are not bricked. Try flashing the stock recovery which can be found in this thread.
http://forum.xda-developers.com/showthread.php?t=2708291
Click to expand...
Click to collapse
How can I flash it if it wont even boot? The screen wont come on and it just rumbles.
wonkizzle said:
How can I flash it if it wont even boot? The screen wont come on and it just rumbles.
Click to expand...
Click to collapse
You cant get into fastboot?
Mode: press and hold Volume Down and Power simultaneously. You will soon see the LOCKED text and then you can release the keys.
droidkevlar said:
You cant get into fastboot?
Mode: press and hold Volume Down and Power simultaneously. You will soon see the LOCKED text and then you can release the keys.
Click to expand...
Click to collapse
No, the screen (barely) lights up for a split second, then shuts off, and vibrates. This repeats over and over. Ive tried holding all the buttons for 90 seconds, still just vibrates. Ive tried all button combinations for as long as I thought it was needed, and nothing is bringing any picture back to the screen. Just vibrations.
wonkizzle said:
No, the screen (barely) lights up for a split second, then shuts off, and vibrates. This repeats over and over. Ive tried holding all the buttons for 90 seconds, still just vibrates. Ive tried all button combinations for as long as I thought it was needed, and nothing is bringing any picture back to the screen. Just vibrations.
Click to expand...
Click to collapse
Not sure what else to try, but I know you're not hard bricked. You are just softbricked. I would go into the M8 channel on irc. andirc.net and channel is #m8
jcase and others hang out there and can be able to help you.
wonkizzle said:
Hey guys, so heres my history
Stock HTC One M8 on Verizon, rooted with weaksauce, then s-off with firewater (took one chug), then installed cwm unnofficial until twrp came out. when the 2.7.0.2 came out, I flashed it via terminal emulator. Suddenly, I could not boot past the recovery. it just would boot into recovery every time I rebooted. So I used the TWRP terminal emulator to flash it once more, thinking that would help. Now the phone wont boot at all, just rumbles and vibrates like its turning on and crashing off. Holding vol up+power and vol down+power does not seem to work, and im going to be so upset if I just bricked my phone. Does anyone have some tips?
Click to expand...
Click to collapse
What did you type into terminal emulator?
This thread might be of help to you: http://forum.xda-developers.com/showthread.php?t=2718562
sparky_005 said:
What did you type into terminal emulator?
This thread might be of help to you: http://forum.xda-developers.com/showthread.php?t=2718562
Click to expand...
Click to collapse
In my haste, before anyone figured out that the TWRP team listed the wrong partition to flash to, I decided to try and flash it again once more, using the same command I did before:
"su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43"
Only this time I did it within the terminal emulator in TWRP, thinking maybe I hit a typo the first time or something, and also since adb didnt list my device on my computer. And THATS when it all went to ****.
Firstly, it only vibrates every 10-15 seconds, stuck in a bootloop and crashing. Only when I hold Volume Down in between vibrates does the phone go into the bootloader. But theres the next problem.
Screen does not illuminate anymore, and I can only see whats going on when I shine a flashlight onto the screen. It will only go to the bootloader, will not load recovery, will not factory reset, fastboot getvar all returns a garbled mess of text that does not resemble the S/N or IMEI, and it seems anything I try to load through fastboot is fruitless. I need some real pros to see this thread, or im ****ed. And I didn't get insurance on the phone when I ordered it, so a replacement is out of the question. Im real upset that I ****ed myself here. I dont hold anyone responsible but myself, but I really wish the proper command would have been included in the instructions instead of flashing it to the wrong partition, twice.
wonkizzle said:
In my haste, before anyone figured out that the TWRP team listed the wrong partition to flash to, I decided to try and flash it again once more, using the same command I did before:
"su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43"
Only this time I did it within the terminal emulator in TWRP, thinking maybe I hit a typo the first time or something, and also since adb didnt list my device on my computer. And THATS when it all went to ****.
Firstly, it only vibrates every 10-15 seconds, stuck in a bootloop and crashing. Only when I hold Volume Down in between vibrates does the phone go into the bootloader. But theres the next problem.
Screen does not illuminate anymore, and I can only see whats going on when I shine a flashlight onto the screen. It will only go to the bootloader, will not load recovery, will not factory reset, fastboot getvar all returns a garbled mess of text that does not resemble the S/N or IMEI, and it seems anything I try to load through fastboot is fruitless. I need some real pros to see this thread, or im ****ed. And I didn't get insurance on the phone when I ordered it, so a replacement is out of the question. Im real upset that I ****ed myself here. I dont hold anyone responsible but myself, but I really wish the proper command would have been included in the instructions instead of flashing it to the wrong partition, twice.
Click to expand...
Click to collapse
As a side note, when you use fastboot getvar all or fastboot getvar serialno this is what happens "F:\Android-adb>fastboot getvar serialno
serialno: ≤º┴╛ ╤■ù╩■ù╚■u♀ "
Another side note, any type of attempt to flash with fastboot ends up with this: "target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.500s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.508s "
atirx7man said:
As a side note, when you use fastboot getvar all or fastboot getvar serialno this is what happens "F:\Android-adb>fastboot getvar serialno
serialno: ≤º┴╛ ╤■ù╩■ù╚■u♀ "
Another side note, any type of attempt to flash with fastboot ends up with this: "target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.500s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.508s "
Click to expand...
Click to collapse
This. He's been helping me figure this out. Anyone help?
wonkizzle said:
This. He's been helping me figure this out. Anyone help?
Click to expand...
Click to collapse
check your PM.
By the way, in the PM I said to boot to bootloader with power + vol up but meant power + vol down
dsEVOlve said:
check your PM.
By the way, in the PM I said to boot to bootloader with power + vol up but meant power + vol down
Click to expand...
Click to collapse
I will report back with results as soon as I can.
dsEVOlve said:
check your PM.
By the way, in the PM I said to boot to bootloader with power + vol up but meant power + vol down
Click to expand...
Click to collapse
Followed your directions exactly dsEVOlve. While the flash does complete successfully, it still did not fix the problem. Now, does flashing this way only flash recovery? I had another member who wrote some zip files trying to fix the serial number issue by replacing the mfg and misc folders. Both failed flashing through fastboot so I'm wondering if this method might have some way of working.
As I said, everything that we attempt to flash through fastboot returns the error FAILED (remote: not allowed)
Your help is greatly appreciated.
If you're a Verizon customer, take the phone back and tell them it won't turn on at all. They'll get you a new one.
Sent from my #6F6E71 M8
atirx7man said:
Followed your directions exactly dsEVOlve. While the flash does complete successfully, it still did not fix the problem. Now, does flashing this way only flash recovery? I had another member who wrote some zip files trying to fix the serial number issue by replacing the mfg and misc folders. Both failed flashing through fastboot so I'm wondering if this method might have some way of working.
As I said, everything that we attempt to flash through fastboot returns the error FAILED (remote: not allowed)
Your help is greatly appreciated.
Click to expand...
Click to collapse
Yes, it only had a recovery image in the ZIP. The ZIP you got from someone else wasn't bootloader flashable and now we've established that nothing can be flashed at this point except through the bootloader.
So you weren't able to boot to recovery through the bootloader after it updated?
I suppose the next thing I would try is reflashing the hboot through bootloader. You would follow the same process but with one of the bootloader flashable ZIPS from here: http://forum.xda-developers.com/showthread.php?t=2709976
dsEVOlve said:
Yes, it only had a recovery image in the ZIP. The ZIP you got from someone else wasn't bootloader flashable and now we've established that nothing can be flashed at this point except through the bootloader.
So you weren't able to boot to recovery through the bootloader after it updated?
I suppose the next thing I would try is reflashing the hboot through bootloader. You would follow the same process but with one of the bootloader flashable ZIPS from here: http://forum.xda-developers.com/showthread.php?t=2709976
Click to expand...
Click to collapse
Alright, just finished trying the hboot flash through bootloader. Same results. Flashes, says to press power to reboot, remove the sdcard and take file off, reboot into a bootloop with no screen illumination.
The only other change I notice is that the flag at the top that used to say "Unlocked" now says "Relocked"
atirx7man said:
Alright, just finished trying the hboot flash through bootloader. Same results. Flashes, says to press power to reboot, remove the sdcard and take file off, reboot into a bootloop with no screen illumination.
The only other change I notice is that the flag at the top that used to say "Unlocked" now says "Relocked"
Click to expand...
Click to collapse
I'll think on it some more but I'm out of ideas. The fact that it is relocked means you probably flashed the stock hboot which might hamper any future efforts. Might want to flash the no red text version to see if it unlocks but it won't fix any of the bigger problems.
dsEVOlve said:
I'll think on it some more but I'm out of ideas. The fact that it is relocked means you probably flashed the stock hboot which might hamper any future efforts. Might want to flash the no red text version to see if it unlocks but it won't fix any of the bigger problems.
Click to expand...
Click to collapse
I know this is for S3; but would some variant of this work? http://forum.xda-developers.com/showpost.php?p=47911843&postcount=165
OP, PM me, I've worked with a few devices like this already.
Hey drache, you already dealt with this phone you tried to help me with it on irc. We had no luck.
Sent from my HTC6435LVW using xda app-developers app
Related
Ok so I unlocked and rooted the my TF700 but had not yet installed any new roms or recovery on it, I was getting round to that but other things to do etc. So one day the battery ran out and when I powered it up bleary eyed one morning it said it could not boot due to being encrypted. I had not encrypted it. So the only option I had was to wipe the device.
Done so back with a working device for some weeks. Then the other day I powered it off. When I powered it back on boot-loop, gets to the point of Asus inspiring inovation persistent perfection (yeah right).
No problem I thinks I'll just use fastboot to save the day because when I boot it says "Device Unlocked" and I can get to the RCK/ANDROID/WIPE screen. So run fastboot and it says it writes to the device but I don't believe it as the copying of an image takes ~130seconds and the writing 0.094s.
So I think I am in this half-locked limbo and I am assuming there is no way out of this.
I've tried a stock rom on the sd card which gets up the Android with a spinning blue vector in his chest but this goes on for about 5 minutes and reboots again back to boot loop.
How did it get half unlocked and if its half unlocked then surely its not unlocked so how does that affect the warranty, I may just send it back and see what happens? I am annoyed because I had not got around to messing around with custom roms etc... I also thought it wouldnt OTA update I am guessing maybe this is what happened when it complained about the encrypted device.
I really am about to give up and use it for chopping onions, a very expensive chopping board.
Not sure if anyone has any bright ideas but I'm all out...
Slarty Bartfast said:
Ok so I unlocked and rooted the my TF700 but had not yet installed any new roms or recovery on it, I was getting round to that but other things to do etc. So one day the battery ran out and when I powered it up bleary eyed one morning it said it could not boot due to being encrypted. I had not encrypted it. So the only option I had was to wipe the device.
Done so back with a working device for some weeks. Then the other day I powered it off. When I powered it back on boot-loop, gets to the point of Asus inspiring inovation persistent perfection (yeah right).
No problem I thinks I'll just use fastboot to save the day because when I boot it says "Device Unlocked" and I can get to the RCK/ANDROID/WIPE screen. So run fastboot and it says it writes to the device but I don't believe it as the copying of an image takes ~130seconds and the writing 0.094s.
So I think I am in this half-locked limbo and I am assuming there is no way out of this.
I've tried a stock rom on the sd card which gets up the Android with a spinning blue vector in his chest but this goes on for about 5 minutes and reboots again back to boot loop.
How did it get half unlocked and if its half unlocked then surely its not unlocked so how does that affect the warranty, I may just send it back and see what happens? I am annoyed because I had not got around to messing around with custom roms etc... I also thought it wouldnt OTA update I am guessing maybe this is what happened when it complained about the encrypted device.
I really am about to give up and use it for chopping onions, a very expensive chopping board.
Not sure if anyone has any bright ideas but I'm all out...
Click to expand...
Click to collapse
Sorry, from your description I don't quite get what exactly you did. What did you try to write with the fastboot command? To me your problem sounds like a bootloader problem.
I understand you still have fastboot access to your device? If so, I'd suggest to follow the steps described here at "Scenario Two":
1. Load a custom recovery, e.g. TWRP with the fastboot method.
2. Download the recovery + bootloader package as described in the CROMi-X thread.
3. Boot into recovery and flash that package.
If you get to this point you should be able to flash any custom (JB based ROM), recommend the CROMi-X.
Hope this helps!
FordPrefect said:
Sorry, from your description I don't quite get what exactly you did. What did you try to write with the fastboot command? To me your problem sounds like a bootloader problem.
I understand you still have fastboot access to your device? If so, I'd suggest to follow the steps described here at "Scenario Two":
1. Load a custom recovery, e.g. TWRP with the fastboot method.
2. Download the recovery + bootloader package as described in the CROMi-X thread.
3. Boot into recovery and flash that package.
If you get to this point you should be able to flash any custom (JB based ROM), recommend the CROMi-X.
Hope this helps!
Click to expand...
Click to collapse
I tried this, so try writing open recovery.
[email protected]:~/Downloads$ md5sum openrecovery-twrp-2.6.3.1-tf700t.blob
0c55d6d437d96644df5ae16408b15795 openrecovery-twrp-2.6.3.1-tf700t.blob
[email protected]:~/Downloads$ mv openrecovery-twrp-2.6.3.1-tf700t.blob twrp.blob
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 0.795s]
writing 'recovery'...
OKAY [ 0.083s]
finished. total time: 0.878s
Now the flashing RCK option has stopped flashing, if I try to reboot:
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 reboot
rebooting...
It just sits here not rebooting. The only way back is to use the pinhole to reboot.
finished. total time: 46.183s
[email protected]:~/Downloads$
Then if I leave it, it boot loops again.
If I hold volume down I get back to the RCK/Android/WipeData fastboot screen. If I try RCK I just get an android lying on its back. If I try from the sd card it spins for ~5 mins then reboots and back to boot loop.
So its almost as if its not writing anything with fastboot.
Slarty Bartfast said:
I tried this, so try writing open recovery.
[email protected]:~/Downloads$ md5sum openrecovery-twrp-2.6.3.1-tf700t.blob
0c55d6d437d96644df5ae16408b15795 openrecovery-twrp-2.6.3.1-tf700t.blob
[email protected]:~/Downloads$ mv openrecovery-twrp-2.6.3.1-tf700t.blob twrp.blob
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 0.795s]
writing 'recovery'...
OKAY [ 0.083s]
finished. total time: 0.878s
Now the flashing RCK option has stopped flashing, if I try to reboot:
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 reboot
rebooting...
It just sits here not rebooting. The only way back is to use the pinhole to reboot.
finished. total time: 46.183s
[email protected]:~/Downloads$
Then if I leave it, it boot loops again.
If I hold volume down I get back to the RCK/Android/WipeData fastboot screen. If I try RCK I just get an android lying on its back. If I try from the sd card it spins for ~5 mins then reboots and back to boot loop.
So its almost as if its not writing anything with fastboot.
Click to expand...
Click to collapse
ok, thanks for the clarification. However, that is exactly what I would have done ... you have checked the download file and fastboot seems to transfer it. From then on you should be able to boot into recovery.
Forgive me please for a dumb question ..but have you tried to boot the "classic" way? Like switching the device off and then power on with the Volume minus key pressed? Other than this, I am sorry but I don't have any further suggestion
Slarty Bartfast said:
I tried this, so try writing open recovery.
[email protected]:~/Downloads$ md5sum openrecovery-twrp-2.6.3.1-tf700t.blob
0c55d6d437d96644df5ae16408b15795 openrecovery-twrp-2.6.3.1-tf700t.blob
[email protected]:~/Downloads$ mv openrecovery-twrp-2.6.3.1-tf700t.blob twrp.blob
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 0.795s]
writing 'recovery'...
OKAY [ 0.083s]
finished. total time: 0.878s
Now the flashing RCK option has stopped flashing, if I try to reboot:
[email protected]:~/Downloads$ sudo fastboot -i 0x0B05 reboot
rebooting...
It just sits here not rebooting. The only way back is to use the pinhole to reboot.
finished. total time: 46.183s
[email protected]:~/Downloads$
Then if I leave it, it boot loops again.
If I hold volume down I get back to the RCK/Android/WipeData fastboot screen. If I try RCK I just get an android lying on its back. If I try from the sd card it spins for ~5 mins then reboots and back to boot loop.
So its almost as if its not writing anything with fastboot.
Click to expand...
Click to collapse
Some things about your fastboot commands are very interesting..
First, what was the operating system that you were using. Second, your recovery name is not the same as you tried to fastboot with the command. Third, I think that you may do something incorrect with fastboot because your bootloader is fine and please be careful with your bootloader. If something is wrong with your bootloader, it is hard to bring it back unless you have your NVflash blobs... Last, you are still with the stock recovery and did not have a custom recovery installed yet.. Also, it seems that you have a bootloop. Any way, I think that you are still good depending on what you want to do with your device...
LetMeKnow said:
Some things about your fastboot commands are very interesting..
First, what was the operating system that you were using. Second, your recovery name is not the same as you tried to fastboot with the command. Third, I think that you may do something incorrect with fastboot because your bootloader is fine and please be careful with your bootloader. If something is wrong with your bootloader, it is hard to bring it back unless you have your NVflash blobs... Last, you are still with the stock recovery and did not have a custom recovery installed yet.. Also, it seems that you have a bootloop. Any way, I think that you are still good depending on what you want to do with your device...
Click to expand...
Click to collapse
Linux, I renamed the recovery as per the instructions at the TWRP teamwin page (cant post links)
It seems that although it says the device is unlocked I cannot write anything to the device and it is stuck in a boot loop, wont flash the stock image from the sd card either. I have been searching for a solution now for a week and can't seem to find anything.
Slarty Bartfast said:
Linux, I renamed the recovery as per the instructions at the TWRP teamwin page (cant post links)
It seems that although it says the device is unlocked I cannot write anything to the device and it is stuck in a boot loop, wont flash the stock image from the sd card either. I have been searching for a solution now for a week and can't seem to find anything.
Click to expand...
Click to collapse
Your finished times are way too fast - mine are 10 times this so I suspect it hasn't written the recovery blob correctly. Did you notice it put a blue time bar on the screen when doing the write?
sbdags said:
Your finished times are way too fast - mine are 10 times this so I suspect it hasn't written the recovery blob correctly. Did you notice it put a blue time bar on the screen when doing the write?
Click to expand...
Click to collapse
Yes I noticed that in comparison to other peoples output that it is too quick.
No there is no blue time bar put on the screen. After you fastboot the recovery the green block that pulses on the selected option RCK for example, stops pulsing and then I have to pinhole reset.
I am thinking that the unlock didn't correctly unlock the device orthe time it would not boot requiring a data wipe because it said the device was encrypted, I guess somehow it got an OTA although it shouldn't have received one. But I cant understand how the unlock could be reverted because the consensus is it cannot.
If the unlock didnt work I may try an RMA on the grounds that its not properly unlocked therefore the T&C for unlocking is not really valid as I would have expected to have an unlocked device.
Slarty Bartfast said:
Yes I noticed that in comparison to other peoples output that it is too quick.
No there is no blue time bar put on the screen. After you fastboot the recovery the green block that pulses on the selected option RCK for example, stops pulsing and then I have to pinhole reset.
I am thinking that the unlock didn't correctly unlock the device orthe time it would not boot requiring a data wipe because it said the device was encrypted, I guess somehow it got an OTA although it shouldn't have received one. But I cant understand how the unlock could be reverted because the consensus is it cannot.
If the unlock didnt work I may try an RMA on the grounds that its not properly unlocked therefore the T&C for unlocking is not really valid as I would have expected to have an unlocked device.
Click to expand...
Click to collapse
I seriously doubt your arguments will get you anywhere with Asus since they don't support unlocking, but I've never heard of a "partial unlock". Either it works or it fails.
I suspect your problem is related to "bleary eyed", the encryption and data wipe you did. Or a driver issue on your PC.
If you cannot install a custom recovery via fastboot, I would try to flash the stock firmware and start at square 1.....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Slarty Bartfast said:
Linux, I renamed the recovery as per the instructions at the TWRP teamwin page (cant post links)
It seems that although it says the device is unlocked I cannot write anything to the device and it is stuck in a boot loop, wont flash the stock image from the sd card either. I have been searching for a solution now for a week and can't seem to find anything.
Click to expand...
Click to collapse
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot... Good luck..:fingers-crossed:
LetMeKnow said:
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot...
Click to expand...
Click to collapse
Are you sure? The bootloader mounts the /data partition to read some Android setting? Does not look plausible to me.
LetMeKnow said:
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot... Good luck..:fingers-crossed:
Click to expand...
Click to collapse
Thats a good question, I would have thought so (always do for everything else) but now you mention it. I can't say for sure. And it won't accept the stock recovery from sd card, 5 minutes of spinning blue thing in chest then reboot into boot loop...
Is it time to start chopping onions?
berndblb said:
I seriously doubt your arguments will get you anywhere with Asus since they don't support unlocking, but I've never heard of a "partial unlock". Either it works or it fails.
I suspect your problem is related to "bleary eyed", the encryption and data wipe you did. Or a driver issue on your PC.
If you cannot install a custom recovery via fastboot, I would try to flash the stock firmware and start at square 1.....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Thats the wierd thing, I did not encrypt the tablet, just discovered it with the green android telling me it needed to do a full data wipe because the tablet was encrypted, I've never encrypted any of my android devices. After this process it worked fine again. Then last time I powered it off it came back up in a boot loop.
I've put the stock firmware on an sd card and the it spins for a few minutes 3 or so then reboots into boot loop.
Slarty Bartfast said:
Thats a good question, I would have thought so (always do for everything else) but now you mention it. I can't say for sure. And it won't accept the stock recovery from sd card, 5 minutes of spinning blue thing in chest then reboot into boot loop...
Is it time to start chopping onions?
Click to expand...
Click to collapse
Well, I can kind of confirm this. Without having done scientific research, but recently I fought my fastboot connection as well. It turned functional only after I checked the USB debugging thing.
_that said:
Are you sure? The bootloader mounts the /data partition to read some Android setting? Does not look plausible to me.
Click to expand...
Click to collapse
That was how I learned to fastboot. I never have problem with fastboot. I can do a test for you when I fastboot twrp 2.6.3.1 without usb debugging..
Edit: @_that
You are an expert in this area. Do you have any good advices for someone in need? Do you know why some users can not flash anything even though they follow the instructions closely? It would be nice if you can share your knowledge with new users like us...
LetMeKnow said:
That was how I learned to fastboot. I never have problem with fastboot. I can do a test for you when I fastboot twrp 2.6.3.1 without usb debugging..
Click to expand...
Click to collapse
Would be interesting.
LetMeKnow said:
Edit: @_that
You are an expert in this area. Do you have any good advices for someone in need? Do you know why some users can not flash anything even though they follow the instructions closely? It would be nice if you can share your knowledge with new users like us...
Click to expand...
Click to collapse
The real experts in this area are those who brought you wheelie and flatline... for me it looks very confusing. The twrp.blob md5sum matches mine, and I don't understand why it finishes so fast, says "OKAY" but doesn't work. If there was a problem with the fastboot protocol or with writing to flash memory, I'd expect some error message. Anyway, maybe try a different/newer fastboot binary or another USB port or another PC? I assume it's Linux on the native machine and not a VM?
I've seen a bootloader which would not flash anything in the case where someone cross-flashed a TF300 bootloader on the TF700, but I assume the OP has never tried such a crazy thing. Check the bootloader version, it should be 10.6.1.14.x.
LetMeKnow said:
Did you turn on or tick the USB debugging in the developer options? You need to turn it on in order to fastboot... Good luck..:fingers-crossed:
Click to expand...
Click to collapse
Like this
http://www.youtube.com/watch?v=q53_9tuD5HA
Next thing I ****ing know some arse is ****ing defending ASUS. Total Fanny boys.Dont help me much.May as well cut ****ing onions.
Slarty Bartfast said:
Like this
http://www.youtube.com/watch?v=q53_9tuD5HA
Next thing I ****ing know some arse is ****ing defending ASUS. Total Fanny boys.Dont help me much.May as well cut ****ing onions.
Click to expand...
Click to collapse
Wow nice response to people trying to help you.......
sbdags said:
Wow nice response to people trying to help you.......
Click to expand...
Click to collapse
I agree. Figured some people prefer failing over learning.
Enjoy your new cutting board. Should work great on peppers too. Probably will last you longer screen down - just some friendly advice....
sbdags said:
Wow nice response to people trying to help you.......
Click to expand...
Click to collapse
Indeed. Seemed like a good idea at the time. Fed up with this rubbish now, gpl'd but still managing trying to foist essentially drm on it. I think what annoys me most is the insidious and slow corruption of the ideal. Must say its partly my own fault, i have stood by and done nothing.
Apologies anyway.
Think I'll buy a Rasberry Pi.
So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?
Nastybutler said:
So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?
Click to expand...
Click to collapse
you need to unlock the bootloader
Daniele12 said:
you need to unlock the bootloader
Click to expand...
Click to collapse
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.
VijayBais said:
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.
Click to expand...
Click to collapse
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)
Keithn said:
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)
Click to expand...
Click to collapse
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.
VijayBais said:
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.
Click to expand...
Click to collapse
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?
Keithn said:
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?
Click to expand...
Click to collapse
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s
I know this won't help VijayBais, but after a while I guess the stock kernel and everything settled in and it stopped random restarting and when I did restart, after installing apps and whatnot, it booted right back up. Now that I'm on 5.1, I haven't had any issues with it freezing up, or random restarts. Crisis averted.
VijayBais said:
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s
Click to expand...
Click to collapse
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?
Keithn said:
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?
Click to expand...
Click to collapse
No, I haven't done any factory reset till now.
Even the recovery option doesn't proceed to further options on bootloader page.
You can't get into the recovery menu? When you chose it and get the dead android do you quickly tap the power+volume up combo?
Hey so I am having a problem unlocking the bootloader.
This is my friends phone and he messed it up bad. What he told me is that he was trying to install a custom ROM on his phone which was already rooted and unlocked. When he went to install it he told me that the ROM locked his bootloader and earased everything on the phone.
When I got the phone it would only boot into fastboot and nothing else. The screen would just be blank.
I have run that color installed and now I get the opo screen when i turn it on and I can also boot into fastboot. I cannot boot into recovery because it is gone I think.
When I try and install the recovery through fastboot I cannot because the bootloader is still locked.
I also tried loading up the custom recovery with the command fastboot boot recovery recovery.img
This doesn't work because I am getting the error "cannot load 'recovery' : Permission denied
I am out of ideas and any help will be greatly appreciated.
smertz said:
Hey so I am having a problem unlocking the bootloader.
This is my friends phone and he messed it up bad. What he told me is that he was trying to install a custom ROM on his phone which was already rooted and unlocked. When he went to install it he told me that the ROM locked his bootloader and earased everything on the phone.
When I got the phone it would only boot into fastboot and nothing else. The screen would just be blank.
I have run that color installed and now I get the opo screen when i turn it on and I can also boot into fastboot. I cannot boot into recovery because it is gone I think.
When I try and install the recovery through fastboot I cannot because the bootloader is still locked.
I also tried loading up the custom recovery with the command fastboot boot recovery recovery.img
This doesn't work because I am getting the error "cannot load 'recovery' : Permission denied
I am out of ideas and any help will be greatly appreciated.
Click to expand...
Click to collapse
I think your friend is giving you dodgy information, flashing a ROM doesn't lock the bootloader. So can you get into recovery at all by using the recovery button combo? Hold power to turn the phone off. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
Heisenberg said:
I think your friend is giving you dodgy information, flashing a ROM doesn't lock the bootloader. So can you get into recovery at all by using the recovery button combo? Hold power to turn the phone off. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
Click to expand...
Click to collapse
I am sure there is something he isn't telling me.
I have tried booting into recovery and I will hold down the button for several minutes but it never boots into recovery.
The phone will only boot into fastboot.
smertz said:
I am sure there is something he isn't telling me.
I have tried booting into recovery and I will hold down the button for several minutes but it never boots into recovery.
The phone will only boot into fastboot.
Click to expand...
Click to collapse
There isn't much you can do then, without recovery and without being able to unlock the bootloader you're pretty much stuck.
Heisenberg said:
There isn't much you can do then, without recovery and without being able to unlock the bootloader you're pretty much stuck.
Click to expand...
Click to collapse
Darn. I was hoping there was some other way of unlocking the booloader. I know I can install a recovery if it was only unlocked.
smertz said:
Darn. I was hoping there was some other way of unlocking the booloader. I know I can install a recovery if it was only unlocked.
Click to expand...
Click to collapse
That's right, recovery install requires an unlocked bootloader. It doesn't really fit your situation but this might be worth looking into.
Heisenberg said:
That's right, recovery install requires an unlocked bootloader. It doesn't really fit your situation but this might be worth looking into.
Click to expand...
Click to collapse
Thanks! But I have already tried it. The second half of it requires that you have an unlocked bootloader to use fastboot.
smertz said:
Thanks! But I have already tried it. The second half of it requires that you have an unlocked bootloader to use fastboot.
Click to expand...
Click to collapse
Oh yeah, I forgot you mentioned that in the OP. Well there's really nothing you can do unfortunately.
Heisenberg said:
Oh yeah, I forgot you mentioned that in the OP. Well there's really nothing you can do unfortunately.
Click to expand...
Click to collapse
Ugh darn I was hoping there was something I could do. Thanks for the help!
Good day, its my first thread here, so I'm sorry for my english and terminology.
My Photon Q had CM-13-Nightly installed, bootloader unlocked and Clockwork recovery installed. Everything was working fine, till few days ago. Phone was left unused with drained battery, so I charged it and powerd on. After that, all app started to crash one after another. I was trying to do factory reset from recovery, erase everything from bootloader menu or using bootloader commands (bootloader erase data, bootloader -w) but nothing worked. I still have my system, with same apps, wallpaper etc and apps still crash. Are these all symptoms of damaged partition or internal storage? Will be thankful for any help
Erasing in bootloader/fastboot mode can be dangerous... be careful.
I would just factory reset and reinstall the ROM. Don't use ClockworkMod for recovery tho, use TWRP. CWM hasn't had updates in a long time (and frankly I'm surprised it was able to flash the latest CM).
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
greedo85 said:
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
Click to expand...
Click to collapse
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
HTML:
C:\fastboot>fastboot flash recovery twrp-2.3.0.0-asanti_c.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6702 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 1.786s]
finished. total time: 2.298s
arrrghhh said:
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
Click to expand...
Click to collapse
greedo85 said:
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
Click to expand...
Click to collapse
I think you can safely ignore the bootloader message.
As for flashing TWRP, did you boot TWRP immediately after flashing, or did you boot Android?
I believe you need to make sure you boot TWRP immediately after flashing, otherwise CM Recovery will blow it out.
After flashing TWRP hold power until the device shuts off, release, and now hold power + vol down to enter recovery. Please use the latest version of TWRP from kabaldan, or the latest official TWRP.
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
greedo85 said:
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
Click to expand...
Click to collapse
Sorry it's power + vol UP (according to my own guide...)
3. Hit power - device turns off. Hold vol up + power, then release power when the screen comes on - continue holding vol up. When you see the moto logo dim a bit, release vol up. You should now be in TWRP!
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
greedo85 said:
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
Click to expand...
Click to collapse
I'm not sure why people have issues with this... I always thought it was how they 'completed' the flashing process. I don't recall being able to reproduce the condition.
Perhaps boot Android then boot TWRP? Or try to reboot directly to recovery from the fastboot cli? Try something different... or just fastboot boot the TWRP image? There is a problem in the process, I'm just not sure 'where' since I don't have the phone in front of me.
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
greedo85 said:
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
Click to expand...
Click to collapse
IIRC this device will let you 'fastboot boot' images directly - I think I suggested this - have you tried it?
I'll dig around and see what else I can find from the TWRP thread. I was pretty sure it had to do with the process, but I could be mistaken.
Edit - I'll flash CM Recovery on my old Q and see if I can recreate this as well. It's always bothered me...
How would I boot images directly? From where?
greedo85 said:
How would I boot images directly? From where?
Click to expand...
Click to collapse
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
arrrghhh said:
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
Click to expand...
Click to collapse
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
greedo85 said:
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
Click to expand...
Click to collapse
I guess they only allow fastboot booting kernels... at least I used to do that on this device.
So I just flashed CM Recovery no problem. Going to flash back TWRP.
Is there anything I can do now to put this phone back to work?
greedo85 said:
Is there anything I can do now to put this phone back to work?
Click to expand...
Click to collapse
I'm... kind of at a loss. Make sure you have the latest TWRP. I just downloaded the latest CM Recovery, fastboot flash recovery <cmrecimg> and it rebooted to Android on its own. I reboot to recovery, CM Recovery is installed. All good.
I reboot to bootloader mode, grab the latest official TWRP, fastboot flash recovery <twrpimg>, this time when I unplugged it was still in fastboot mode. So I hit the power button, phone turns off. Then I hold power + vol up until I see the screen turn on. Continue to hold vol up, but release power. Then when the screen dims (or when recovery starts if you can't tell) release vol up.
Maybe that'll help you? Good luck.
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
greedo85 said:
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
Click to expand...
Click to collapse
Dunno why it would make any difference at this point, but have at it.
Hi!
Okay, this case is really weird and of course is thanks to my negligence. I'm gonna post it hoping someone can help me, or at least keep other people aware about trying stupid things lol
I tried to update to Nougat with an unofficial method (I don't consider necessary to tell what method...) and I just messed it up, badly. I'll try to give a detailed explanation:
The phone has the bootloader unlocked. After trying to update to Nougat, it got stuck when rebooting. After the unlocked bootloader warning message, the phone won't go further than that, it just stays there. If I hold and press the power button for more than 10 seconds the phone won't shut down, it will restart to get stuck again after the unlocked BL warning, making impossible to turn it off completely.
I try to enter to stock recovery by pressing vol + and power button at the same time (tried other combinations, vol - and power button & vol -, vol + and power button) but I have no luck, it just gets stuck at the same point.
I already tried extracting BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img from an official update.app and flash them in that order via fastboot (yeah, I can enter to fastboot mode). The process is successful in terminal (I use Linux) but when I reboot the phone, it gets stuck again after the warning.
The only recovery that is actually working is TWRP, the one ported for the Honor 8 (flashed via fastboot), but it won't let me install any custom ROM, it just stays in "patching image unconditionally" forever, making me press and hold the power button but this won't shutdown the phone, it reboots, gets stuck and... so on *infinite loop*
Btw, when I wipe cache, dalvik and data in TWMP, the message "failed to mount /cust" with red letters appears, so it's probably a very corrupted system partition. also, It's impossible to repair the custom partition. This appears:
Repairing Custom using e2fdck...
/sbin/e2fsck -fp /devblock/mmcblk0p44 process ended with ERROR: 8
Unable to repair Custom.
Click to expand...
Click to collapse
Tried HiSuite from Huawei (in Windows) and it doesn't even recognize the phone.
Hope somebody could possibly give a solution, if there's any. If not, I'm afraid I have a beautiful paperweight now...
Oh yeah, one very important part: my Honor 8 is the US version (FRD-L04), and yes, I'm making sure I'm getting the current update.app for this model.
Any help would be greatly appreciated. Thanks in advance.
Hi There
you try this method.
Get a SD CARD
make a directory at the card root name dload
put your best update.app in the directory (the most older version the best)
insert into your phone 2nd sim slot
try everyway to make the 3 button combo.
hope this help
edit: you need stock recovery to do this
chongns said:
Hi There
you try this method.
Get a SD CARD
make a directory at the card root name dload
put your best update.app in the directory (the most older version the best)
insert into your phone 2nd sim slot
try everyway to make the 3 button combo.
hope this help
edit: you need stock recovery to do this
Click to expand...
Click to collapse
Hey, thanks!
unfortunately, as far as I know is that for this method I have to enter to stock recovery, but then again, I can't get in. The phone gets stuck trying any combination of pressed buttons... But I'll try it.
Edit: Trying your method right now, hope it goes well...
El Brillantinas said:
Hey, thanks!
unfortunately, as far as I know is that for this method I have to enter to stock recovery, but then again, I can't get in. The phone gets stuck trying any combination of pressed buttons...
Click to expand...
Click to collapse
Yes, but since you r able to go into TWRP, can your use adb command like adb reboot bootloader than flash stock recovery image?
after that since it is keep rebooting, you can hold your volume up and down all the way to force update.
IDK if this work. but no harm to try it, since it is "very hard brick"
Edit: Fastboot erase {partition} before flash back the image maybe help
chongns said:
Yes, but since you r able to go into TWRP, can your use adb command like adb reboot bootloader than flash stock recovery image?
after that since it is keep rebooting, you can hold your volume up and down all the way to force update.
IDK if this work. but no harm to try it, since it is "very hard brick"
Click to expand...
Click to collapse
Yep, I'm trying it now and right now is installing the update (the EMUI logo with the circular progress bar). Hope it works *crossed fingers*
Edit: No luck. After the process finished, it says:
Software install failed!
Get help from: http//www.emui.com/emotionetcetc.
Click to expand...
Click to collapse
El Brillantinas said:
Yep, I'm trying it now and right now is installing the update (the EMUI logo with the circular progress bar). Hope it works *crossed fingers*
Edit: No luck. After the process finished, it says:
Click to expand...
Click to collapse
I assume you having the update.app from a L04 full firmware, not the OTA.
for the not able to repair partition like custom maybe you can erase it using fastboot erase command and fastboot flash it back
or you can fastboot erase all the known partition like system, cache, data, custom etc.... and fastboot flash back the image.
i assume your fastboot still able to access
chongns said:
I assume you having the update.app from a L04 full firmware, not the OTA.
for the not able to repair partition like custom maybe you can erase it using fastboot erase command and fastboot flash it back
or you can fastboot erase all the known partition like system, cache, data, custom etc.... and fastboot flash back the image.
i assume your fastboot still able to access
Click to expand...
Click to collapse
I did it!!
I could bring it back following some of your methods. Here's how I achieved it:
-Formatted the Custom partition in fastboot.
-Flashed BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img again.
-Forced the update by putting the entire firmware in the dload folder located in the sdcard, it failed at the end, but I rebooted by pressing and holding the power button.
-The phone passed beyond the point where it was getting stuck (finally!), but now it got stuck in the Honor 8 blue screen. Rebooted it again doing coldboot.
-Entered to stock recovery, wiped everything.
Then I just rebooted it and Voalá! It started all new!
Guess it was not that hard brick haha. I'll have to change the name of the topic.
A million thanks @chongns, you rock!
El Brillantinas said:
I did it!!
I could bring it back following some of your methods. Here's how I achieved it:
-Formatted the Custom partition in fastboot.
-Flashed BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img again.
-Forced the update by putting the entire firmware in the dload folder located in the sdcard, it failed at the end, but I rebooted by pressing and holding the power button.
-The phone passed beyond the point where it was getting stuck (finally!), but now it got stuck in the Honor 8 blue screen. Rebooted it again doing coldboot.
-Entered to stock recovery, wiped everything.
Then I just rebooted it and Voalá! It started all new!
Guess it was not that hard brick haha. I'll have to change the name of the topic.
A million thanks @chongns, you rock!
Click to expand...
Click to collapse
Good to know you succeed.
please tag a moderator to move your thread to Guide, News and Discussion section..
most of the time ppl search solution at there.
Guide in another Huawei phone XDA forum.
http://forum.xda-developers.com/mate-8/general/fuss-debrick-restore-mate-8-t3457969
Moderatos, can you please move this topic to the Guides and discussion section? Thanks in advance.
Glad you fixed it bro. That was very critical.
El Brillantinas said:
Moderatos, can you please move this topic to the Guides and discussion section? Thanks in advance.
Click to expand...
Click to collapse
good to hear u go phone back , and there is another guides already exist to restore a framware throw the same method , thank you for sharing ur experience .
Here's the issure I'm having. My Honor 8 FRD-L04 is stuck at a hard brick. It won't reach the recovery. I tried to flash images using fastboot. But I end up with the error: FAILED (remote: Command not allowed)
Any help would be appreciated
bho01 said:
Here's the issure I'm having. My Honor 8 FRD-L04 is stuck at a hard brick. It won't reach the recovery. I tried to flash images using fastboot. But I end up with the error: FAILED (remote: Command not allowed)
Any help would be appreciated
Click to expand...
Click to collapse
Is your frp status lock in fastboot?
faizalotai said:
Is your frp status lock in fastboot?
Click to expand...
Click to collapse
No it's unlocked
bho01 said:
No it's unlocked
Click to expand...
Click to collapse
Your phone status?
faizalotai said:
Your phone status?
Click to expand...
Click to collapse
Still can't get into recovery and I'm still getting the "FAILED(Command not allowed)" error whenever I try to flash stock images
bho01 said:
Still can't get into recovery and I'm still getting the "FAILED(Command not allowed)" error whenever I try to flash stock images
Click to expand...
Click to collapse
I mean your phone status in fastboot.
Its comes with frp and phone status..both have to be unlocked in order to flash images.
Try using the dload method of flashing
faizalotai said:
I mean your phone status in fastboot.
Its comes with frp and phone status..both have to be unlocked in order to flash images.
Click to expand...
Click to collapse
Also unlocked