I hate to do this but I this is my last resort to getting my phone back working. I currently can not get pass splash screen. Phone was already rooted running cm7 and I wanted to go back to one of my old nandroid so I flashed CW 2.5.1.2. It was working fine but was running slow so I did a data format and wipe cache and ever since then it will not boot up. I am getting a E:Cant' mount CACHE:recovery/command and log message when recovery loads up.
I can get into fastboot and recovery fine but I cant seem to flash any of my nandroids anymore. I have about 5 of them and none work. I can't flash any roms either. It seems as if my root may be gone because when Im in adb shell and run su it does not give me root and I cannot mount any systems in recovery. I tried everything from trying to flash to stock through hboot and even flashing new recovery in fastboot but that did not work since I do not have ENG HBOOT. Tried rerooting and unrooting it again but I always have to go into that /data/local but I am never able to gain access. I do still have S-OFF but that seems to be about it. Oh yeah and I cant even do a wipe data/factory reset. Says E:format_root device: can't find mmc partition.
So if someone knows anything else I could try to get this resolve that would be cool.
Ok lets start don't panic all is not lost yet you can still have root with S-OFF and have access fastboot and recovery. I am not sure why you reverted back to older CWMR2.5.1.2 as if you had CWMR3.0.0.6 you could have done it without fastboot but makes no diff now.
First go try "fastboot erase system -w" and then boot in to recovery and do full factory wipe and then flash as you normally would do.
BlackSHELF said:
Ok lets start don't panic all is not lost yet you can still have root with S-OFF and have access fastboot and recovery. I am not sure why you reverted back to older CWMR2.5.1.2 as if you had CWMR3.0.0.6 you could have done it without fastboot but makes no diff now.
First go try "fastboot erase system -w" and then boot in to recovery and do full factory wipe and then flash as you normally would do.
Click to expand...
Click to collapse
I reverted back to that one thinking that it would enable me to flash a none cm7 rom.
Here is what I got. From my understanding I am getting this because I do not have ENG HBOOT but please correct me if Im wrong
C:\android-sdk-windows\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.020s
Hmmm I just reread your OP and you saying you somehow lost root trying to unroot and reroot, so I am not sure about the current status.
NOMRAL CASE:
http://forum.xda-developers.com/attachment.php?attachmentid=516463&d=1297577207
^ download that and unzip it and get the recovery.img for 3.0.0.6 and try "fastboot flash recovery recovery.img" as that would do if not try the below.
EXTREME CASE:
http://www.filefactory.com/file/caa....140e_26.03.02.26_M_release_155771_signed.zip
File: PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.1 40e_26.03.02.26_M_release_155771_signed.zip
MD5: 49D07F0EE7DE1765A6A84CB12FA53110
Size: 312 MB
^ go download the file and then rename it from "PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60. 140e_26.03.02.26_M_release_155771_signed.zip" to "PD15IMG.zip" (make sure its not PD15IMG.zip.zip) and put it in root of your SDCard. Go in to bootloader and follow the instructions. This will get you to stock rom/radio from there you can redo all your stuff.
BlackSHELF said:
Hmmm I just reread your OP and you saying you somehow lost root trying to unroot and reroot, so I am not sure about the current status.
NOMRAL CASE:
http://forum.xda-developers.com/attachment.php?attachmentid=516463&d=1297577207
^ download that and unzip it and get the recovery.img for 3.0.0.6 and try "fastboot flash recovery recovery.img" as that would do if not try the below.
EXTREME CASE:
http://www.filefactory.com/file/caa....140e_26.03.02.26_M_release_155771_signed.zip
File: PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.1 40e_26.03.02.26_M_release_155771_signed.zip
MD5: 49D07F0EE7DE1765A6A84CB12FA53110
Size: 312 MB
^ go download the file and then rename it from "PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60. 140e_26.03.02.26_M_release_155771_signed.zip" to "PD15IMG.zip" (make sure its not PD15IMG.zip.zip) and put it in root of your SDCard. Go in to bootloader and follow the instructions. This will get you to stock rom/radio from there you can redo all your stuff.
Click to expand...
Click to collapse
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3426 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.180s
The other file did not work either. It had "Fail-PU" for all the files it tried to flash
Did you try the PD15IMG.zip from bootloader? Download it make sure its not corrupted that is why I provided you with md5 hash to verify. Then put the file in root of your sdcard and then boot in to bootloader, it will scan it and follow the instruction to revert back to original.
BlackSHELF said:
Did you try the PD15IMG.zip from bootloader? Download it make sure its not corrupted that is why I provided you with md5 hash to verify. Then put the file in root of your sdcard and then boot in to bootloader, it will scan it and follow the instruction to revert back to original.
Click to expand...
Click to collapse
Yes I just verified it and it is not corrupt. Thats the way I did it and came up fail-pu
lilterro said:
Yes I just verified it and it is not corrupt. Thats the way I did it and came up fail-pu
Click to expand...
Click to collapse
Hmmm never seen or heard of that I am taking fail pu means failed partition update. What does your HBOOT ver say on the screen? I am not sure what happened but seems like it soft-brick ATM still not sure how you lost root. Hopefully someone who has little more knowledge can shed some light.
BlackSHELF said:
Hmmm never seen or heard of that I am taking fail pu means failed partition update. What does your HBOOT ver say on the screen? I am not sure what happened but seems like it soft-brick ATM still not sure how you lost root. Hopefully someone who has little more knowledge can shed some light.
Click to expand...
Click to collapse
Ok thanks anyway. I am normally able to wok my out of alot of these issues that come up with flashing but this one got me stumped to.
HBOOT-0.86.0000
perm-brick no fix
lilterro said:
Ok thanks anyway. I am normally able to wok my out of alot of these issues that come up with flashing but this one got me stumped to.
HBOOT-0.86.0000
Click to expand...
Click to collapse
I am having the very same problem i am very good at fixing my mistakes but this one is impossible i get that same fail-pu but only difference is mine is s-on and it was never rooted only temp-root i was trying to perm-root and that's when it crashed will not boot up any more and i can't boot into recovery because it never been rooted and i don't know how to do ( C:\android-sdk-windows\tools>fastboot flash recovery recovery.img ) looks like something for the pc and i tried factory reset it will just freeze with the 3 androids skating i go to fastboot and i see bootloader, reboot, reboot bootloader and power down but those did nothing i even offered $100 through paypal to the first person how fixes it but it's an impossible task so there is a full brick out there people say its not but i see different.
perm-brick no fix
Related
Hi,
I have a tmobile mytouch 3g 1.2 (3.5mm jack phone). I tried to root my phone and it failed during the SYSTEM---UnZipping process. (it stuck there forever). I then looked at options of unrooting it. When I apply SAPPIMG.zip it says Main Version Older! Update Fail!
Then I reboot the phone in recovery mode (tried to reset to factory settings and then reboot). The phone gives me the below error upon startup. The only thing i can see is an notification bar.
the process android.process.acore has stopped unexpectedly. "FORCE CLOSE"
Please can someone help me how to get my phone working? Appreciate all your help!
If you go to tmobile.com then go to there forum under android development you will see a topic called how to unroot the mytouch. In that topic they have a link for the original sappimg .. download to your zip cars in the root of the card (no folders) then just boot into hboot and apply the sappimg. I have done it many times so I know it works. Then when you go to root your just us the universal androot method. Feel few to pm me i
ent from my HTC Magic using XDA App
Type this in fastboot:
Code:
fastboot getvar version-main
Then we can try to see if we can update it.
If not, you can always try to flash RUU.
The system starts, that's a good thing -> you have adb access!
Just don't go around and flash all kind of sapphire.nbh/zip...
Wait intil you have the right info :0)
I have had this problem and solved it. I would either get this acore stopped working error or just a loop in the boot screen. I think what caused this is there is not enough internal room for the ROM and gapps. Make sure you wipe everything. Do you have a nandroid backup? Can you get into recovery? Which recovery do you have installed? Do this, make a goldcard. Use fastboot to reroot the phone because you may have halfway unrooted it and made root useless. Boot into recovery and wipe. Install from sd any MyTouch ROM without Gapps. This should get you into the OS and now you can use other methods of getting your phone back. When I got here I used nandroid backup to get my phone back to a date it was when it worked and have had no problems since.
mumilover said:
Type this in fastboot:
Code:
fastboot getvar version-main
Then we can try to see if we can update it.
If not, you can always try to flash RUU.
The system starts, that's a good thing -> you have adb access!
Just don't go around and flash all kind of sapphire.nbh/zip...
Wait intil you have the right info :0)
Click to expand...
Click to collapse
I tried the command - fastboot getvar version-main
it just says < waiting for device > and then nothing happens...
also when i run the adb devices command, it does not display my devices. (But i have the number noted down when i tried to root the phone which failed...) can this number be used in any manner for anything
housry23 said:
I have had this problem and solved it. I would either get this acore stopped working error or just a loop in the boot screen. I think what caused this is there is not enough internal room for the ROM and gapps. Make sure you wipe everything. Do you have a nandroid backup? Can you get into recovery? Which recovery do you have installed? Do this, make a goldcard. Use fastboot to reroot the phone because you may have halfway unrooted it and made root useless. Boot into recovery and wipe. Install from sd any MyTouch ROM without Gapps. This should get you into the OS and now you can use other methods of getting your phone back. When I got here I used nandroid backup to get my phone back to a date it was when it worked and have had no problems since.
Click to expand...
Click to collapse
i did not take any nandroid backup ...i got into revovery boot...but whn i did the wipe clean option and reboot i get this error.
to make a gold card i would need to have the USB debugging enabled right? I am not able to go past the error screen (Home does not work, settings does not work )
and when i run the adb devices command, it does not display my devices. (But i have the number noted down when i tried to root the phone which failed...)
is there any other way to enable the USB Debugging as I am not able to open settings or even see anything on my phone...?
Would there be any option that's something like doing a System Restore to an earlier date on Windows OS on the computer?
please let me know the next steps...appreciate all of your help...
It's driver related.
Fix the drivers and try again to run the commands.
mumilover said:
It's driver related.
Fix the drivers and try again to run the commands.
Click to expand...
Click to collapse
You mean re-install the USB drivers for mytouch 3g? i tried that but still nothing happens...
Well you have to...
In fastboot mode this command shall give you the device nr .
Code:
fastboot devices
If not, the drivers are still bad!
You could also try to do a HARD RESET from hboot ( volume - together with power)...
mumilover said:
Well you have to...
In fastboot mode this command shall give you the device nr .
Code:
fastboot devices
If not, the drivers are still bad!
You could also try to do a HARD RESET from hboot ( volume - together with power)...
Click to expand...
Click to collapse
Thanks for the steps. I got the version details.
by executing the fastboot getvar version-main in fastboot mode.
version-main: 2.53.707.2
finished. total time: 0.001s
What will be the next steps...how to I update?
ganesh.raj.ms said:
Thanks for the steps. I got the version details.
by executing the fastboot getvar version-main in fastboot mode.
version-main: 2.53.707.2
finished. total time: 0.001s
What will be the next steps...how to I update?
Click to expand...
Click to collapse
Hey, i tried the below. can you please let me know if this is correct? and what do i do next?
userdebug-img-14721_1.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.0013
Baseband Version.....: 2.22.23.02
Serial Number........: HT03TPB01582
--------------------------------------------
checking product... FAILED
Device product is 'sapphire'.
Update requires 'trout'.
finished. total time: 0.042s
how do i try to rectify the checking product...FAILED???
OK....
Let's get the facts right.
You tried to root with wrong guide.
The sapphire.zip/nbh image you used if for the 32A.
How do i know that ?
Well the main version nr tells me that you have flashed this:
2.53.707.2 SEA WWE test-signed (from this page: http://forum.xda-developers.com/showthread.php?t=659403)
That's why you have troubles!
The solution....
I need all your fastboot info.. ALL.
Then i can figure out what to do. Or else i will work in the dark...
mumilover said:
OK....
Let's get the facts right.
You tried to root with wrong guide.
The sapphire.zip/nbh image you used if for the 32A.
How do i know that ?
Well the main version nr tells me that you have flashed this:
2.53.707.2 SEA WWE test-signed (from this page: http://forum.xda-developers.com/showthread.php?t=659403)
That's why you have troubles!
The solution....
I need all your fastboot info.. ALL.
Then i can figure out what to do. Or else i will work in the dark...
Click to expand...
Click to collapse
Is it the below that you want?
[FONT="]SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009,22:33:27[/FONT]
Yes...
You have the right radio/spl combo. That's good.
The problem is that your main version is set to high.
If you try to flash any RUU for the 1.2 magic, you will get main-version older error...
Even if you use a goldcard.
Do you still have access to adb?
Even for a little... then we can flash a custom recovery and get the system back.
Even if your system don't start up... as long you can boot more then 20 sec and you don't get reboots.
If not, then we have to flash a 32A sappimg.zip using a goldcard.
From there we flash custom recovery. Then eng spl. Then flash system,boot, userdata. Then flash the 1.2 spl... Then we are done :0)
So it's a long one... but first test if we have adb access.
Code:
adb devices
mumilover said:
Yes...
You have the right radio/spl combo. That's good.
The problem is that your main version is set to high.
If you try to flash any RUU for the 1.2 magic, you will get main-version older error...
Even if you use a goldcard.
Do you still have access to adb?
Even for a little... then we can flash a custom recovery and get the system back.
Even if your system don't start up... as long you can boot more then 20 sec and you don't get reboots.
If not, then we have to flash a 32A sappimg.zip using a goldcard.
From there we flash custom recovery. Then eng spl. Then flash system,boot, userdata. Then flash the 1.2 spl... Then we are done :0)
So it's a long one... but first test if we have adb access.
Code:
adb devices
Click to expand...
Click to collapse
adb devices does not give me anything...its not working
Does the computer recognise the device?
Maybe it's driver related...
PS: check your pm
Hi,
I made a mistake in loading a android froyo build to my HTC my touch 4g.
And now, my htc my touch 4g won't boot up. It stucks in teh 'My Thocuh HD' screen.
Can you please tell me how can I recover my phone?
Either load the original factory software?
or
Load cyanogenmod?
Thank you.
How did you load it? Standard procedure is to make a backup first... So go back into recovery and restore it.
Tell us more about what you did? What hboot and recovery do you have?
Sent from my CM7 HTC Glacier
After I build a ginger bread build, i did
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And then the phone now hangs in flash screen.
Can you please tell me how can I recover from it now?
hap497 said:
After I build a ginger bread build, i did
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And then the phone now hangs in flash screen.
Can you please tell me how can I recover from it now?
Click to expand...
Click to collapse
Since you can get into the HBoot, if it were me i'd load the PD15IMG and start all over.
neidlinger said:
Since you can get into the HBoot, if it were me i'd load the PD15IMG and start all over.
Click to expand...
Click to collapse
exactly what i was going to suggest.
I assume you mean pd15img from here:
ttp://filespart.com/p/pd15img-mytouch-4g.html
What do you mean i can get to 'HBoot'? I now do a 'adb devices', it does not show my touch 4g anymore.
Thank you for all the help.
hap497 said:
I assume you mean pd15img from here:
ttp://filespart.com/p/pd15img-mytouch-4g.html
What do you mean i can get to 'HBoot'? I now do a 'adb devices', it does not show my touch 4g anymore.
Thank you for all the help.
Click to expand...
Click to collapse
This is the PD15IMG.img
download it and store it to the root of the SD card. When you go to turn the phone on hold the power button and the volume down button. IT will pick up that image and ask if you want to restore the phone according to the PD15IMG.
Thanks. I download PD15IMG.zip and copy it to the root of the SD card. But when i boot up the phone under HBoot. It said 'no image PD15IMG.zip is found'
So, what happens when it fails? And says " - Fail -PU" Partition update fail
hap497 said:
Thanks. I download PD15IMG.zip and copy it to the root of the SD card. But when i boot up the phone under HBoot. It said 'no image PD15IMG.zip is found'
Click to expand...
Click to collapse
Not work mytouch 4g
hello buddy
hepl me please
this happend
BOOTLOADER FAIL-PU
BOOT FAIL-PU
RECOVERY FAIL-PU
SYSTEM FAIL-PU
USERDATA FAIL-PU
SPLASH1 FAIL-PU
TP
TP BYPASSED
RADIO?V2 UPDATING
RADIO?CUST
DO YOU WANT TO START UPDATE
VOL UP YES
VOL DONW NO
UPDATE IS IN PROGRESS....
DO NOT POWER OFF THE DEVICE!
I've been 30 minutes and DO NOT PASS THE SAME
HELP ME PLEASE
SCOTTY85
WHAT I SAID IT WORKED
http://s3.subirimagenes.com:81/fotos...95imag0062.jpg
http://s3.subirimagenes.com:81/fotos...01imag0060.jpg
http://s3.subirimagenes.com:81/fotos...ffffffffff.jpg
http://forum.xda-developers.com/showthread.php?t=901477
I donwloaded this too but not work
already test as 5 ROM
you can tell me where could found 1
thanks
God bless you
I hope you answer.
eams1986 said:
Not work mytouch 4g
hello buddy
hepl me please
this happend
BOOTLOADER FAIL-PU
BOOT FAIL-PU
RECOVERY FAIL-PU
SYSTEM FAIL-PU
USERDATA FAIL-PU
SPLASH1 FAIL-PU
TP
TP BYPASSED
RADIO?V2 UPDATING
RADIO?CUST
DO YOU WANT TO START UPDATE
VOL UP YES
VOL DONW NO
UPDATE IS IN PROGRESS....
DO NOT POWER OFF THE DEVICE!
I've been 30 minutes and DO NOT PASS THE SAME
HELP ME PLEASE
SCOTTY85
WHAT I SAID IT WORKED
http://s3.subirimagenes.com:81/fotos...95imag0062.jpg
http://s3.subirimagenes.com:81/fotos...01imag0060.jpg
http://s3.subirimagenes.com:81/fotos...ffffffffff.jpg
http://forum.xda-developers.com/showthread.php?t=901477
I donwloaded this too but not work
already test as 5 ROM
you can tell me where could found 1
thanks
God bless you
I hope you answer.
Click to expand...
Click to collapse
you're done...
read here:
http://forum.xda-developers.com/showpost.php?p=13709837&postcount=22
hap497 said:
Thanks. I download PD15IMG.zip and copy it to the root of the SD card. But when i boot up the phone under HBoot. It said 'no image PD15IMG.zip is found'
Click to expand...
Click to collapse
I am having this problem, and I am stuck.
I also get the md5 mismatch when trying to do a restore.
hoostie said:
I am having this problem, and I am stuck.
I also get the md5 mismatch when trying to do a restore.
Click to expand...
Click to collapse
1) do not flash the PD15IMG from the recovery image.
2) if you have a wrong PD15IMG then you need to re-download and check the MD5 again.
neidlinger said:
1) do not flash the PD15IMG from the recovery image.
2) if you have a wrong PD15IMG then you need to re-download and check the MD5 again.
Click to expand...
Click to collapse
I am not trying to flash the pd15img from restore. Sorry thats separate. I made a nandroid backup before i wiped the phone, and I get an md5 error on that. And the phone wont let my flash any other roms either.
Now I dont know what to do.
Where can I find an alternate pd15.img. Sorry I am lost and I just dont know what to do.
***edit, nevermind. I figured it out. Thanks
I'm also getting fail-pu but only on the first item in the list bootloader. When using adb and trying to read the mmcblk I get can't read mbr. So I'm thinking the mbr is corrupted. If that is the only issue keeping pd15img.zip from updating is it possible to fix the mbr? or does having one fail-pu in that list mean a fried eMMC? I'm sure if there is a fix for the mbr my MT4G could be salvaged without replacing the motherboard. My issue started with a bunch of failed auto-updates. The last thing it tried to update was SKYPE,thats when I notice more failed updates. I rebooted and all seemed fine. The next day I went grocery shopping and in front of the Frootloops section, my calculator started crashing. FDW loader stopped responding. I received a sms message and fdw crashed again. So I rebooted and ironically it went into bootloops as I reached for the fruitloops. Pulled the battery and rebooted into hboot then into clockworkmod recovery .I had cyanogenmod 7 7.01, did not try to update to the newest one,but noticed that clockworkmod recovery did somehow auto update into 5.0.2.0 Thats where my issue must have come from. I noticed the dreaded E:can't mount /cache/ so I rebooted again in the middle of a supermarket and noticed pd15diag.zip was not found in hboot. Went home and tried everything I could find with Google. While using ADB (can't remember the exact commands) I noticed the MBR was unabled to be read. which is why I get the fail-pu in the bootloader. If other people are getting this and not fail-pu on everything in the list, there might (a really slim chance) of recovery from this. Is there another way to determine that the eMMC chip is fried?
here is the output I get when updating PD15IMG.zip this is on hboot-0.85.2007 Glacier PVT ENG S-OFF
1 bootloader -- fail-pu
2 boot
3 recovery
4 system
5 userdata
6 splash1
7 tp
8 tp
9 radio_v2
10 radio_cust
partition update fail!
update fail
press <power> to reboot.
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.
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
Hi I have the XT1570, running unlocked and with rooted but stock 5.1.1. I have run in to some issues with the recovery part.
Firstly I wanted to go back to the recovery and flash a stock recovery so I could get the OTA for MM, i did that using fastboot, and the flash worked fine according to fastboot, however once i rebooted into recovery it would not load, got an error message, I forget now something about dumping back to bootloader.
Anyway i fixed it got TWRP back on again, then tried a different stock recovery, same thing same error, so i thought I would easily get back to TWRP by the same method, flash again. I was wrong, now fastboot told me , target reported max download size of 536870912 bytes
error: cannot load 'twrp-2.8.7.1-clark': No error
Remember this is the exact same TWRP image i have just flashed not 5 mins before.
So i thought ok then, maybe an old image is in there taking up space or something.
C:\Users\David\Desktop\Mfastboot\Mfastboot>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.017s]
finished. total time: 0.019s
Now I get the message:
Invalid boot image header.
Error:failed to load kernel
Boot up failed.
I presume I have deleted everything in the recovery partition, and so messed it up good, but I dont know how to fix it at this point.
I also erased the cache along the way (via fastboot) as I tried to get the OTA update to work anyway just to see what would happen, so I had to erase the cache to cancel updates
I must reiterate, I can boot into Android and use my phone no issues, at all, just I have no recovery at all and this means updates arent going to work, also i cant seem to find a reliable source for a stock recovery.
Some step by step help would be appreciated, as I am not an expert by any means on this.
Thank you.
Also my device was bought in China as that is where I am, it does indeed have the code name XT1570, dual sim, I would assume it is basically the same as the XT1572 asian. I do also have an original backup of the phone after unlocking bootloader, before root, which was my next port of call after changing the recovery back to stock.
fixed it i was just being foolish, someone delete this thread it is of no use.
Can you explain how you fixed it? I too have deleted the recovery in an attempt to flash twrp, but now neither twrp nor the stock recovery are there?
Tapatalk'd from my Twisted, Racing Nexus 5