Database Users

Accidentally flashed non WWE ROM

Hi Guys,
I'm a little stuck. By accident I flashed: RUU_Ace_HTCCN_CHS_1.75.1400.4_Radio_12.35a.60.140f_26.04.03.30_M_release_162585_signed.exe when I meant to get the WWE version.
When I try install the proper version: RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed I get an ERROR [140]: BOOTLOADER VERSION ERROR.
So I am stuck with a chinese version of android with all these weird looking apps on it. Can anyone put me in the right track here please?

higgo22 said:
Hi Guys,
I'm a little stuck. By accident I flashed: RUU_Ace_HTCCN_CHS_1.75.1400.4_Radio_12.35a.60.140f_26.04.03.30_M_release_162585_signed.exe when I meant to get the WWE version.
When I try install the proper version: RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed I get an ERROR [140]: BOOTLOADER VERSION ERROR.
So I am stuck with a chinese version of android with all these weird looking apps on it. Can anyone put me in the right track here please?
Click to expand...
Click to collapse
I have the same problem, who can help please ?

you guys did a clean flash? rename the rom.zip to PD98IMG.zip then flashed?
try checking if you have radio S-off on the bootloader.
top middle should display if u are SHIP S-ON or SHIP S-OFF
judging by the looks of it you guys are S-ON ;x
i dont know if fastboot or adb works tho... if u can get the 1.32.405.6 rom to flash over then u are safe.
maybe you can try booting to the bootloader and run fastboot flash system system.img ? or maybe flashing the recovery partition manually to clockwork mod?
to do fastboot or adb you need android SDK and java SDK "x86" the x64 giving problems.
please read at development section

i dont know if this would work but give it a try, get the 1.32.405.6 file and find
mainver: 1.32.405.6 on the android_info.txt and change it to 1.75.1400.5 ? ;p then flash? :O

randomdud said:
i dont know if this would work but give it a try, get the 1.32.405.6 file and find
mainver: 1.32.405.6 on the android_info.txt and change it to 1.75.1400.5 ? ;p then flash? :O
Click to expand...
Click to collapse
Unfortunately does not work

randomdud said:
you guys did a clean flash? rename the rom.zip to PD98IMG.zip then flashed?
try checking if you have radio S-off on the bootloader.
top middle should display if u are SHIP S-ON or SHIP S-OFF
judging by the looks of it you guys are S-ON ;x
i dont know if fastboot or adb works tho... if u can get the 1.32.405.6 rom to flash over then u are safe.
maybe you can try booting to the bootloader and run fastboot flash system system.img ? or maybe flashing the recovery partition manually to clockwork mod?
to do fastboot or adb you need android SDK and java SDK "x86" the x64 giving problems.
please read at development section
Click to expand...
Click to collapse
Hi Mate. Yeah I tried a clean flash and it stated the the main rom was older and didn't work. I also tried 1.32.405.6.
I'm trying to flash system.img but it is saying:
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.005s
I'm trying to S-OFF but Visionary doesn't seem to be working with this version. I attempt temproot and I get a black screen after a few moments. Is there any other way I can S-OFF so I can try and install cyanogen or something?

higgo22 said:
Hi Mate. Yeah I tried a clean flash and it stated the the main rom was older and didn't work. I also tried 1.32.405.6.
I'm trying to flash system.img but it is saying:
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.005s
I'm trying to S-OFF but Visionary doesn't seem to be working with this version. I attempt temproot and I get a black screen after a few moments. Is there any other way I can S-OFF so I can try and install cyanogen or something?
Click to expand...
Click to collapse
hmm, maybe try fastboot oem unlock ?

1.75 and 1.72 are unhackable YET!
Sent from my Desire HD

Then I'm stuck with a semi-bricked phone
On this 1.75 Chinese version - I cannot connect to my mobile network or use the google market.
I guess I am stuck waiting for WWE 1.75

You'r right
Sent from my Desire HD

kuceens007 said:
You'r right
Sent from my Desire HD
Click to expand...
Click to collapse
lol seems to be so. was hoping that someone around would know how to change the data on 1.32.405.6 to 1.99.999.9 so at least it would flash over replacing the 1.72 or 1.75 roms lol. then we can manually flash over the 1.72 system.img boot.img and clockwork the su and su.apk for root xD well someone here in xda might know how to do that ;p but that dude just aint me

try this i had to use it once when i flash the last chinese ver 1.60 and visionary was forcing close http://forum.xda-developers.com/showthread.php?t=843014.i have attached 2 files needed you will get the rest from the link.

update hboot now I have S-ON

I upgraded my hboot from the old version to the new 0.35 to get gingerbread but now the hboot which I flashed shows that I'm S-ON which means I can't write on system so how do I go back to S-OFF, I don't get it?

It is every unlikely you were ever S-OFF, to my knowledge on 2 people on this forum are S-OFF, and I am one of them.
The N1 is different to a lot of other phones and will let you mount /system as RW even with S-ON.
Ps. For the record, updating HBOOT doesn't affect the security status, mine went from .33 to .35 and remained S-OFF.

+1 Rusty
You weren't S-OFF before.

thanks didn't know you could write on system with S-ON, thats good

For the record - mine is S-OFF too..so there is 3

Hooray!
Is it an engineering HBOOT or a shipping one?

Guys,
I have same thing and I am unable to update my hboot .
fastboot gives me this error : sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
How do I fix this?
FWIW, I have a factory unlocked N1.
PS: Newbie here, please be easy with me.

From the factory it's SIM unlocked, but not bootloader unlocked. If you want to flash with fastboot, use 'fastboot oem unlock' first.
If not, flash via recovery.

siddharthsai said:
For the record - mine is S-OFF too..so there is 3
Click to expand...
Click to collapse
count me in; I was s-off before hboot upgrade, after the upgrade, I am still s-off.

Yes i believe its engineering

Excuse my ignorance... what is "S-ON" and/or "S-OFF" ???

S is security. If it's off you can lock the bootloader again.

My DHD is nearly bricked. Please help.

I have a T-Mobile UK DHD that I'd fully rooted, Eng-Off, Radio S-Off & SuperCID
I was running a LeeDroid ROM but yesterday it began frequently locking up so I tried to do a wipe and reinstall the ROM but at the end of the ROM installation after "Writing boot.img" it said:
assert failed: write_raw_image ("/tmp/boot.img","boot")
E:Error in /sdcard/LeeDrOiD_HD_V2.0.0.zip
(Status 7)
Installation aborted.
I also kept getting the messages E:Can't mount CACHE:recovery/log & E:Can't open CACHE:recovery/log
I then tried to install the stock 1.32 RUU but that stuck at the Updating User Data stage at 40%.
I'm now stuck with the bootloader options and simply have a white screen with the below and warning triangles bottom left & right.
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
MICROP-0438
RADIO-26.04.02.17_M2
eMMC-BOOT
Oct 11 2010, 12:47:02
RUU (This is highlighted yellow)
I have tried ADB but the device isn't shown as attached. However, Fastboot shows it attached but I've had no success pushing the ROM this way either. Below is copy of the cmd window:
C:\AndroidSDK\tools>fastboot boot PD98IMG.zip
creating boot image...
creating boot image - 301006848 bytes
downloading 'boot.img'...
OKAY [ 47.302s]
booting...
FAILED (remote: not allowed)
finished. total time: 47.302s
Can anyone offer any assistance as I've run out of ideas and fear I've bricked it.

you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?

The message you get about being unable to write boot suggests you are no longer S-off, whilst bootloader suggests you have s-off, l would start from scratch and s-off again and then try reinstalling the rom

20mark said:
you cant just flash rom via ADB. you need recovery. Do you have clockwork mod recovery?
Click to expand...
Click to collapse
I used to but it's been wiped as part of the the failed RUU installation. Power On/Vol Down now does nothing
ghostofcain said:
The message you get about being unable to write boot suggests you are no longer S-off, whilst bootloader suggests you have s-off, l would start from scratch and s-off again and then try reinstalling the rom
Click to expand...
Click to collapse
Do you mean Eng or Radio off? Can I do that with no bootloader options or recovery?
How would you suggest installing the ROM and which one?
Thanks for any advice.

I've just tried jkolo's easy S-Off tool but I get an error message pop-up "Module or hboot fail. Aborting."

So what happenes when you choose the recovery option?
Oh and btw don't worry too much about the void warranty, I've read of a few people who've had to send phones back to HTC without being able to revert to stock first and they've been successful - obviously this is a last resort.

EmprtArea said:
So what happenes when you choose the recovery option?
Click to expand...
Click to collapse
I don't have a recovery option on the Phone.

So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
If you need the image it here: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.6-ace.img

EmprtArea said:
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
Click to expand...
Click to collapse
I haven't tried that yet but fear the 1st line may wipe my only way of communicating if the 2nd part doesn't work

well you say you haven't got the recovery option anyway, so you could leave that line out I only put it because that's what I'd do.
HOWEVER: I'm no expert.
Question after Re-reading your post: Are you worried you'll delete fastboot? I'm sure that's not what I'm suggesting. But as it's your £500 device wait for someone else to confirm.

EmprtArea said:
So can you use fastboot to do this successfully?
fastboot erase recovery
fastboot flash recovery clockwork-recovery.img
If you need the image it here: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.6-ace.img
Click to expand...
Click to collapse
No luck
Code:
C:\AndroidSDK\tools>fastboot flash recovery recovery-clockwork-3.0.0.6-ace.img
sending 'recovery' (3334 KB)...
OKAY [ 0.560s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.562s

Everytine you try writing it fails what else can you do?
Sent from my Desire HD using XDA App

I'd jump to thinking you're not ENG S-Off anymore (got to say probably the failed 1.32 flash that did it. And you can't use that tool so look for an alternative description of how to get there.
If you can't use ADB I don't know how to get there.
If somehow ADB does start working then the CyanogenMod wiki might be useful.
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Root_Guide

If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
Sent from my Desire HD using XDA App

I've got backups of:
hboot_original.bin & part7backup-1294609557.bin
Are they of any help?
I can't see any way to gain Eng-Off without root so I'm at a loss.
The frustrating thing is I don't know what happened in the 1st place that froze my phone and kicked all this off. I'm guessing I have a hardware fault of some sort
Would T-Mobile exchange or repair under warranty, despite the mods I'd made?

Aamir.Badat said:
If you lost s-off while flashing the 1.32 rom then I also suspect you lost root.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'm starting to regret trying that as a solution now

I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:
http://forum.xda-developers.com/showthread.php?p=9139950
I'm not an expert on these things, so I don't know if this would work for you. I would suggest waiting for someone with a bit more experience than me to join the discussion, as I don't know how similar your circumstances are to the ones in that thread. Do you get any error messages on your PC when you run the RUU? I take it that it finds your phone, whereas in the thread above the RUU wasn't seeing the phone.
However I thought reading that might give you some hope. Worth reading the thread all the way through.

I think what disabled most of your options was flashing a stock ruu. It overwrites hboot and the recovery.
Edit: since the ruus fail installing, maybe someting is off with your device, NAND error or someting.

this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!

preacher65 said:
I remembered something similar being posted on these forums a few months ago, so I had a search and found this thread:
http://forum.xda-developers.com/showthread.php?p=9139950
I'm not an expert on these things, so I don't know if this would work for you. I would suggest waiting for someone with a bit more experience than me to join the discussion, as I don't know how similar your circumstances are to the ones in that thread. Do you get any error messages on your PC when you run the RUU? I take it that it finds your phone, whereas in the thread above the RUU wasn't seeing the phone.
However I thought reading that might give you some hope. Worth reading the thread all the way through.
Click to expand...
Click to collapse
Thanks for the tip. I'll have a read and may give that a go.
KamikaZeeFu said:
I think what disabled most of your options was flashing a stock ruu. It overwrites hboot and the recovery.
Edit: since the ruus fail installing, maybe someting is off with your device, NAND error or someting.
Click to expand...
Click to collapse
I don't get errors, the RUU just freezes and I have to pull the plug.
danrobz said:
this sort of thing doesnt happen if you are flashing custom roms though right? its making me nervous now!
Click to expand...
Click to collapse
The errors started when I was on a Custom ROM but my suspicion is that it's a hardware fault to blame. If I can't fix this then whilst the custom ROM probably didn't cause the damage, the general unlocking etc may have voided my warranty.

[Q] can't boot to recovery and can't charge when turned off

Hi everyone! here's my situation, my phone is turned off and when I try to charge it, it would have a solid orange light on the LED which is alright. But when I unplug the charger, the orange LED stays lighted and the only way for orange light to go away is to take out the battery.
Also, I cannot boot to recovery. It hangs on the T-mobile mytouch splash screen. I have a stock rom with 3.0.2.4.
Thanks in advance for answering!
EDIT: 3.0.2.4 is the clockwork recovery version and I can boot normally. just wanted to go to recovery and be able to charge while phone is off..

blue_algae said:
Hi everyone! here's my situation, my phone is turned off and when I try to charge it, it would have a solid orange light on the LED which is alright. But when I unplug the charger, the orange LED stays lighted and the only way for orange light to go away is to take out the battery.
Also, I cannot boot to recovery. It hangs on the T-mobile mytouch splash screen. I have a stock rom with 3.0.2.4.
Thanks in advance for answering!
Click to expand...
Click to collapse
Can you boot into HBoot/Bootloader/fastboot/Engineering Screen?
Do you have the Engineering Screen on the phone or the stock one?

thanks for the assistance! will try that now..

neidlinger said:
Can you boot into HBoot/Bootloader/fastboot/Engineering Screen?
Do you have the Engineering Screen on the phone or the stock one?
Click to expand...
Click to collapse
I can go to HBoot then fastboot and the selection at the bottom changes to bootloader, reboot, reboot bootloader and power down. if I select bootloader, it goes back to the initial screen.

blue_algae said:
I can go to HBoot then fastboot and the selection at the bottom changes to bootloader, reboot, reboot bootloader and power down. if I select bootloader, it goes back to the initial screen.
Click to expand...
Click to collapse
do you see an option for recovery?

yes, though selecting that would display the t-mobile my touch 4g screen and will just hang. same thing happens if I boot to recovery using rom manager.

blue_algae said:
yes, though selecting that would display the t-mobile my touch 4g screen and will just hang. same thing happens if I boot to recovery using rom manager.
Click to expand...
Click to collapse
Okay do you have the Engineering bootloader?
you top few lines of the Hboot screen should look like
Code:
GLACIER PVT ENG S=OFF
HBOOT-O.85.2007 (PD150000)

I have a slightly different one:
Code:
GLACIER PVT ENG S-OFF
HBOOT-O.85.2007 (PD1510000)
or was it a typo error? thanks again for the help!

blue_algae said:
I have a slightly different one:
Code:
GLACIER PVT ENG S-OFF
HBOOT-O.85.2007 (PD1510000)
or was it a typo error? thanks again for the help!
Click to expand...
Click to collapse
are you talking about the - / = deal?
Then yes it was typo.
okay we need to flash you a recovery...
this is a simple process.
make sure you have ADB installed on your computer
[use the link in my signature if you don't]
once you have it up and running plug your phone into the computer
boot in hBoot
then download the attachment and store just the recovery.img to the tools folder of your SDK if you have the entire SDK, or the c:\adb folder if you use True_blue's
once you have done that change your target folder to the folder where you stored the recovery.img and type
Code:
fastboot devices
you should see your serial number
if you do see it type
Code:
fastboot flash recovery recovery.img
you should see something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if you do navigate to "recovery" and select it.

This is what I have:
Code:
GLACIER PVT ENG S-OFF
HBOOT-O.85.2007 (PD1510000)
Regarding the typo, I was pertaining to hypen (mine) against an equal sign (yours) and PD151000(mind) to PD150000(yours).
do I have the correct values?

blue_algae said:
This is what I have:
Code:
GLACIER PVT ENG S-OFF
HBOOT-O.85.2007 (PD1510000)
Regarding the typo, I was pertaining to hypen (mine) against an equal sign (yours) and PD151000(mind) to PD150000(yours).
do I have the correct values?
Click to expand...
Click to collapse
Yes you do. you can flash a recovery image like i mentioned above.
I was going off memory, i didn't physically boot in HBoot.

Thanks mate! That worked! I can now boot to recovery. will try charging while phone is off in a bit.
btw, what went wrong? my new recovery file (3.0.2.4) was not supported?

blue_algae said:
Thanks mate! That worked! I can now boot to recovery. will try charging while phone is off in a bit.
btw, what went wrong? my new recovery file (3.0.2.4) was not supported?
Click to expand...
Click to collapse
I have no idea what went wrong. I do no trust flashing recoveries via Clockwork ROM manager for that very reason i typically download the recovery then flash it via ADB commands. to risky in my way of thinking.
just make sure to update your recovery that version is 3.0.0.6.

ok, will update it now as well. can I use any recovery version 3.0.2.4? I mean that version can be found on various threads for different phones on this board. do I just pick one or it should be made for mt4g?

blue_algae said:
ok, will update it now as well. can I use any recovery version 3.0.2.4? I mean that version can be found on various threads for different phones on this board. do I just pick one or it should be made for mt4g?
Click to expand...
Click to collapse
Here. this is the one i pulled off my my phone.
just flash it like you did the other one and you'll be a-okay.

cool! thanks mate for the updated recovery. I've just tried charging my phone while turned off and I was able to. really great.
btw, where do you get the recoveries? I don't want to get it from rom manager moving forward.

blue_algae said:
cool! thanks mate for the updated recovery. I've just tried charging my phone while turned off and I was able to. really great.
btw, where do you get the recoveries? I don't want to get it from rom manager moving forward.
Click to expand...
Click to collapse
well i have ROM manager on my phone, but i use it to download the ROM to my SDcard then flash manually from their. it's a little more work but it's worth to me.
From what i've been putting together i think Koush is putting a web site together and we can just snag them from there. But that is just rumors as of now.

Same Phone But......
neidlinger said:
are you talking about the - / = deal?
Then yes it was typo.
okay we need to flash you a recovery...
this is a simple process.
make sure you have ADB installed on your computer
[use the link in my signature if you don't]
once you have it up and running plug your phone into the computer
boot in hBoot
then download the attachment and store just the recovery.img to the tools folder of your SDK if you have the entire SDK, or the c:\adb folder if you use True_blue's
once you have done that change your target folder to the folder where you stored the recovery.img and type
Code:
fastboot devices
you should see your serial number
if you do see it type
Code:
fastboot flash recovery recovery.img
you should see something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if you do navigate to "recovery" and select it.
Click to expand...
Click to collapse
Hi brother,
hi have the same phone with same problem but boot is different.
GLACIER PVT SHIP S-OFF
HBOOT-0.89.0005
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Apr 14 2011,13:18:22
but when i put recovery i get this error.
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (3426 KB)... OKAY [ 1.156s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.172s
Where is my falt or what else i can do
Need please help
Thanks
Br, Raja

You have the 2.3.4 gingerbread update which there is no official way to root it yet...what you must do is downgrade to froyo 2.2.1 and then root from there. Seeing as how you found this thread, I know you are one of the few who know how to search-there are several threads about downgrading and think it is in the wiki as well...
Edit: Just noticed you were s=off-were you rooted before?

Downgrade to 2.2.1 problem

Following this guide http://forum.xda-developers.com/showthread.php?t=1178912
I'm having trouble on the final downgrading step. I've followed all other instructions and everything is working great until I try to reboot into the bootloader and downgrade. When I get into the bootloader and press the power button it takes me to the HBOOT screen and freezes. I tried doing the fastboot method also and it transfers the zip, but then is stuck at the "writing 'zip'..."
md5 matches for the PD15IMG.zip
Any ideas?
Also on the HBOOT screen the top 2 line say:
"GLACIER PVT SHIP S-OFF
HBOOT-0.89.0006"

No ideas on this? I also tried it over again using Ubuntu and no luck

i'm having trouble changing the version number =/. sorry to thread jack

S-OFF means your phone was already rooted, and you don't need to do anything. Look in Developers section, find a thread for re-rooting S-OFF device, it contains PD15IMG with only recovery in it. Flash it.

I'm not sure which thread the PD15IMG with recovery is in. Do you know the title or have a link to it?
Also, why would flashing the PD15IMG w/ recovery not make HBOOT freeze like flashing a completely stock PD15IMG does? If it is actually S-OFF shouldn't it accept the stock 2.2.1 PD15IMG anyways?
EDIT: nevermind, I'm guessing I should be using the PD15IMG from this thread?
http://forum.xda-developers.com/showthread.php?t=1200147
I tried using one of those and HBOOT still freezes as soon as I get to it

Yes, that's the one.
I don't know why you get the freezing - it shouldn't be freezing anyway, stock or not.

Jack_R1 said:
Yes, that's the one.
I don't know why you get the freezing - it shouldn't be freezing anyway, stock or not.
Click to expand...
Click to collapse
Yeah, I'm at a loss as to what to do now. Everything requires using hboot to flash and that's not working

Use another SD card.
Format it in Windows.
Put recovery PD15IMG.ZIP on it.
Attempt flashing in bootloader.
If it doesn't work:
Extract recovery.img from the PD15IMG.ZIP that you downloaded.
Set up fastboot.
Change your bootloader to fastboot mode (select FASTBOOT with power button).
Verify that you see your phone by running "fastboot devices" from command prompt.
Flash recovery by executing "fastboot flash recovery your_extracted_recovery_image.img".

Tried using another SD card and I finally got it working. I can't believe I didn't think to try that lol. Thank you so much.

Jack_R1 said:
S-OFF means your phone was already rooted, and you don't need to do anything. Look in Developers section, find a thread for re-rooting S-OFF device, it contains PD15IMG with only recovery in it. Flash it.
Click to expand...
Click to collapse
Tried manual downgrade could not load image in hboot said was wrong img.
Tried fastboot downgrade stuck htc screen cmd reads can't load stockrom. Now it could be I have the wrong file named stockrom. of the PD15IMG file.I could unlock my bootloader either following htcdev.com i get this message and another one
Please Help me this is Driving me Nuts!!!
FAILED (status malformed (1 bytes))
finished. total time: 0.021s
C:\android-sdk\platform-tools>
GLACIER PVT SHIP S-On
HBOOT-0.89.0006

commandersafi said:
Following this guide http://forum.xda-developers.com/showthread.php?t=1178912
I'm having trouble on the final downgrading step. I've followed all other instructions and everything is working great until I try to reboot into the bootloader and downgrade. When I get into the bootloader and press the power button it takes me to the HBOOT screen and freezes. I tried doing the fastboot method also and it transfers the zip, but then is stuck at the "writing 'zip'..."
md5 matches for the PD15IMG.zip
Any ideas?
Also on the HBOOT screen the top 2 line say:
"GLACIER PVT SHIP S-OFF
HBOOT-0.89.0006"
Click to expand...
Click to collapse
I have wanted to downgrade my mytouch 4g to stock rom , when I flash it it's stuck at "sending "zip" <319593 KB>..." what to do next?
I have used methot "Fastboot Downgrade"
following error says ; FAILED <data transfer failure <too many links>
FAILED <satatus read failed <too many links>>
Thanks