Related
Ok, now i've read through various magic and dream forums, and i think i've got this, but i wanted to check...it's not my phone and i don't want to get fired
I could tell you all the background that got me to this point, but it's really long winded and would bore you to death.
Basically, i have been given a bricked phone that i need to recover for the company i work for. Someone tried to update it with a heroimg.zip file and it trashed it.
Fastboot and Hboot work fine and i only have the boot.img, system.img and recovery.img files to do it.
If i understand this right, i should be able to flash these img files to the device while in fastboot.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot recovery recovery.img
fastboot reboot
Should that work? I've happily used the amon RA recovery to do update.zip updates on my own phones, but company procedures and stuff won't let me do anything other than leave it as standard.
I don't claim to understand adb/fastboot really, but i think those are the commands i need to flash the img files across manually.
am i right? Just hoping someone here who is a lot more intelligent than I can just confirm it before i totally kill the damn thing!
Don't know if this helps, but Paul has the 'stock' shipping (ie unmodified and unrooted) update.zip files on Modaco here
You could use the latest one of these after Fastbooting the latest AmonRA. That way, you're not flashing AmonRA to the device or anything like that. This should give you a stock Hero with no modifications to it.
But then again, your company might not like this either. In that case, I haven't tried those commands, but they should, in theory, work (I've used 1 or 2 to flash a custom boot.img so I could modify the ramdisk, but that's about it for me)
that's why i figured they might work...i've used the boot.img one to flash a recover on mine, but i was just working from a 'how to guide'.
still not got my head around the commands yet. Not as confident playing with these things as i was on WinMo in the past...
any chance you boot the custom recovery from fastboot and flash the update.zip from there?
maddie said:
any chance you boot the custom recovery from fastboot and flash the update.zip from there?
Click to expand...
Click to collapse
TBH, if you're not comfortable with the commands for flashing yet, I would not try and learn on a work phone.
To do it this way, as suggested before, download an update.zip from Modaco for the latest 'stock' official Hero build.
Now download the latest AmonRA recovery image and put it in a folder to hand. Rename it to recovery.img for ease of typing later on.
Install the Android SDK if you don't have it already, and boot the phone to fastboot (Power + Back IIRC)
Now type into a command prompt window
Code:
fastboot devices
and make sure the phone's serial number appears.
Code:
fastboot boot C:\recovery.img
to boot the custom AmonRA recovery image (not the stock one!)
Optional step here is to do a 'wipe' if there is something wrong with the data (user) partition, but this depends on circumstances.
Once in the recovery image, choose to apply a named update file, and point it to the file on the root of the SD Card (put it there from within Windows Explorer. You will need to use a card reader or another phone to do this since this one is 'bricked'.
Now wait patiently for the flash to happen. It is usually done for me in 10 mins when flashing a Modaco ROM, but if it stops working, DO NOT TURN IT OFF OR UNPLUG THE BATTERY!!! (sorry for caps, but it's really important as this seems to be no.1 cause of proper 'bricks')
Phone should then reboot into new ROM.
I should add ... that following the anon2122 guide will leave your phone "stock" as in... there will be no way to tell that anything has been done... no lasting recovery image, a stock ROM etc etc..
anon2122's method is the way to go.
Your method wont work unless the phone has an "S-OFF" SPL... You likely don't! If you happen to ... then your steps will work fine. Although ... You may also need to wipe the user data if the phone doesn't boot after your steps!
Code:
fastboot erase cache
fastboot erase userdata
Thanks for all the tips guys, they did indeed help.
In the end, it turned out that the phone was S-Off, as we do tend to get some test rigs in at various points.
I've got the recovery image already installed on my personal phone, but for various reasons couldn;t use it in this case.
But thatnks for the help, and it's all working now.
And yes, i did need to do a wipe afterwards.
Thanks all. That's some more commands i understand now.
Good to hear that it worked.
Thanks for letting us know, since it is all too often that the OP doesn't let others who may find this thread in future know whether the fix worked or not.
well, that's why i responded. It winds me up no end when people don;t bother to tell you if it worked or not.
And i did learn something new as i was not aware of the erase commands. Yet another thing to add to my little box of tricks....
Hello everyone,
I think this might be my first post here.
Anyways, I have a rather depressing problem. I have my phone rooted running cm 6.1, and when i was about to go to sleep last night, it randomly started to reboot. At first i did not think anything of it because i have had my phone do this several times with cm. But then i became more concerned, it would go into a boot loop at the splash screen (htcEVO4g). Once again, i have had this happen before and i would do a wipe and reinstall the rom, but this time it did not work. I could not get into recovery. I am able to access only the boot loader.
So, i tried to install the stock pc36img. Now when i start my phone, it vibrates 5 times followed by the flashing green led. it also does this when i try to go into recovery. I am still able to get into the bootloader.
i tried doing the ruu thing, and different pc36img
I just got back from the sprint store. After waiting 3 hours, they were not able to fix it. I had told them it was rooted and everything.
If there is no way to fix it, is there at least a way i can turn s-on? That way, i can send it back to sprint.
That is odd. As far as I know, if you used unrevoked forever at any point, the only way to get s on is to flash the unrevoked s on tool, using recovery. But you don't have recovery. If I were you, I would use your computer to format your sd card to fat 32 ( after backing it up, of course) , then put a pc36img on your sd card, and try to flash again using the bootloader. You could also try putting a pc36img of amon ra recovery on your sd card, and flashing that with the bootloader. Maybe you can get recovery back, and flash a rom, or the s on tool. Hope you get it worked out.
Sent from my PC36100 using XDA App
If I were you I would try the newest pc36img.zip and if that does nothing a pc36img.zip of Amon ra. If that doesn't work go to the last link in my sig about splash screens. In that tut I give, I say how to manually run an ruu. Use the pc36img.zip with the fast boot commands from the thread. Hope this helps.
i tried formatting the sc card, and that did not do anything. How can i connect my phone to adb?
marzban123 said:
i tried formatting the sc card, and that did not do anything. How can i connect my phone to adb?
Click to expand...
Click to collapse
Just Download the android SDK and follow the steps. There are some pretty excellent tutorials on XDA and other sites that will walk you through the whole process.
I want to weigh in here for just a moment. There is no way your phone is completely botched, unless it has experienced physical damage (including any overheating). By the way, you running any SBC kernels?
I would look into learning your way around ADB, I think it's a necessary tool for anyone who wants to flash and alter their android phones, unfortunately things have become so easy that many out there haven't had to learn these tools and how to use them.
Seriously, go mess with ADB, I am sure you can get it running again.
Some good info here http://forum.xda-developers.com/showthread.php?t=865204 on using ADB and other methods that may help you.
marzban123 said:
I had told them it was rooted and everything.
Click to expand...
Click to collapse
ouch... they should give you new phone for being honest
ok, so i connect the phone, and in device manager i see "Android Bootloader Interface"
i opened up command prompt, and tried to push a file to the phone and i got this
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Andrew>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb push PC36IMG.zip /sdcard/
error: device not found
C:\android-sdk-windows\tools>
you sure your usb cable is good? id run the RUU to go back to stock & unroot you. then start over from scratch.
i just tried a different cable. No luck
I have already tried a stock ruu, that still does not let me get into recovery or turn s-on
your sorta up ****s creek here if you told sprint you rooted. they probably flagged your account.
is your sd card good? try another, fully formatted for fat32 only. then try the s-on flashable zip. that's all i can think of for you to do. if you need another evo, im sure you can pick one up for cheap on craigslist.
nobody ever took my information
Is there an s-on flashable zip?!?! where can i find it? i have searched before with no luck
first of all, adb doesnt work in bootlaoder. select fastboot, then plug in. you should see fastboot usb come up on the phone. now try using fastboot commands instead. not sure where to download fastboot commands. i have the mac ones if you need them. then do this
with the pc36img.zip ON YOUR COMPUTER:
after flashing s-on tool http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
fastboot oem rebootRUU
you should see a black screen with silver htc lettering
fastboot flash zip pc36img.zip (do this command with the pc36img.zip in the same directory as fastboot)
you should see a green bar appear under htc and a bunch of lines on the comp. make sure it successfully completes, then type:
fastboot reboot
done.
but make triple sure you are s-on first.
thank you very much, that makes things ALOT clearer.
I am still a huge noob to this stuff so i need to ask you some silly questions:
i found out the commands for fastboot in a wiki,
http://wiki.cyanogenmod.com/index.php?title=Fastboot
but i dont really understand how to use them. can someone please give me a little clarification.
well, first check your sdk and see if you have fastboot.exe. i know the mac one doesnt come with it. if you dont google it. if you do, cd to the directory (hold shift and right click in the folder. select open command prompt here) and boot phone into fastboot. make sure it is in fastboot usb mode. then do the commands.
i have the fast boot exe and i am in command prompt.
when i say i am a noob, i really mean it.
for example, when i try a simple command like checking the serial number, i will input
c:\android-sdk-windows\tools>fastboot <-s>
or
c:\android-sdk-windows\tools>fastboot -s
or
c:\android-sdk-windows\tools>fastboot <serial number>
it says
the syntax of the command is incorrect.
i really dont know how to use this stuff
ok forget the last post,
i figured that out
what partition do i want to flash and with what file?
No partition just use the pc36img.zip in ruin more and type fastboot flash zip pc36img.zip.
Sent from my PC36100
C:\android-sdk-windows\tools>fastboot flash zip PC36IMG.zip
sending 'zip' (171727 KB)... OKAY [ 30.475s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 30.477s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
i researched the "(remote: not allowed)" error message, and everyone says its cause when the phone is set to s-on. However, on my phone it says s-off.
what the heck?
hey guys im a long time reader here. and i think i bricked my brand new verizon nexus. i just got done doing super boot to unlock it and also put clock mod on there. and now the phone will not boto past the word google. just stays on google for a min or so then reboots. im not sure what to do beause there is no sd card to mount (i dont know how to mount it its not working in recvovery mode.) can any one help me with a step by step to fix this. i cant fugure it out. i guess that was a dumb move on my part. =( please help!
I had this same issue, unlocked the bootloader, but then it would not boot past the white google. I tried so many things. Here is how I fixed mine.
First install 7zip or some sort of program that can deal with .tar and .tgz files assuming you don't already have it.
Download the stock image for your phone, I assume you are talking about the Galaxy Nexus LTE Verizon phone. Get that from here You need the mysid version, not the yakju. For a direct link to download the mysid version, click here
Extract that file to your desktop or wherever, you will have a file called "mysid-icl53f-factory-65895fa8.tar" then extract that so you have the following files visable:
bootloader-toro-primekk15.img
flash-all.sh
image-mysid-icl53f.zip
radio-cdma-toro-i515.ek05.img
radio-toro-i515.ek02.img
You can DELETE the radio-cdma-toro file, you don't need it for the LTE version (i hope, haha)
Put these files in your C:/android-sdk-windows/platform-tools folder. Do NOT further unzip the image.mysid zip file.
Put your phone into bootloader menu, plug in your USB cable to your computer, start your command prompt inside the platform-tools folder (in white space, shift+right click).
Type the following (taken from this thread and modified with correct file names)
Assuming you have windows computer
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
This took a few mins to install, And my phone then rebooted itself and worked! (I don't think I had to manually reboot it).
It took me 5 good hours to find all this info and finally get my phone working again, hope it works for you! I was in a panic, that's for sure!
Btw, the phone's bootloader is still unlocked, but I have not yet tried to gain root access.
Please let me know if this worked for you.
Ive done the same
Can you post what I would need to put in terminal for mac. Im kinda new to this
Hahahahahahahahahahahahahahaahahahahah not even a day
nononononono the same thing happened to me!!
Just do a battery pull and put it back in!
doublea500 said:
nononononono the same thing happened to me!!
Just do a battery pull and put it back in!
Click to expand...
Click to collapse
It does not work for some people. I let mine sit for a half hour and did at least 20 battery pulls. It never went past the white google screen
---------- Post added at 04:13 AM ---------- Previous post was at 04:11 AM ----------
cvv1984 said:
Can you post what I would need to put in terminal for mac. Im kinda new to this
Click to expand...
Click to collapse
I linked to the thread where I got the commands in my post.. anyways.. replace the file names with the ones as above
For OSX, replace "fastboot" with "./fastboot" (i would assume)
Well this did nothing for me. Got to the stage where it rebooted the phone, everything was looking good and reading as "okay" in command prompt. Then when it went to reboot it went right back to google screen. It shows the google logo for about five seconds, then it shuts off for a second, vibrates and logo comes back on. I am at a loss here and don't know what else I can do to fix this thing.
And yes, I just got it today
I followed the instructions to reimage back to stock and still have the same problem. As sublimejhn says it just keeps rebooting in that initial start up screen. Not a fun night.
SlopeSurfer said:
I followed the instructions to reimage back to stock and still have the same problem. As sublimejhn says it just keeps rebooting in that initial start up screen. Not a fun night.
Click to expand...
Click to collapse
I'll keep you posted if I make any progress if you'll do the same!! I have never had an issue rooting, installing roms or anything else on any other phone until now. This is not exactly the phone I want to have bricked, hopefully we can figure this out
Same Problem here, just hangs forever (15min+) at the Google splash screen.
I think I found the problem with mine. I cant mount (or do anything) with the /data part of the phone.
I think its corrupted or something. I realized this when I was trying to do a nandroid restore/backup and could never mount or format the /data
--------edit----------
What Easyski posted work like a charm for me. Thx dude
fly_guy said:
Same Problem here, just hangs for ever (15min+) at the Google splash screen.
I think I found the problem with mine. I can mount (or do anything) with the /data part of the phone.
I think its corrupted or something. I realized this when I was trying to do a nandroid restore/back and could never mount or format the /data
--------edit----------
What Easyski posted work like a charm for me. Thx dude
Click to expand...
Click to collapse
Well that's cool. I have tried it 3 times now and it's a no go for me, but good to hear someone got theirs working again. Now if only the rest of us could get out of this!! At this point I don't even care about root, I just want my phone back
before I tried his steps I flash the stock recovery, stock boot.img, and lock it back.
so maybe try doing that, then use the steps above. I was about to give up myself. Was doing one last scroll of the forums when I saw this thread
Ok, got mine working now. Not sure why this helped, but here's what I did, I typed everything exactly as follows:
fastboot-windows flash bootloader bootloader-toro-primekk15.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-toro-i515.ek02.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-mysid-icl53f.zip
I don't know if it is the fact that I wasn't using fastboot-windows (can't see why that would matter, since both fastboot and fastboot-windows appear to be the same file), or the addition of that stupid '-w' before the update (got this from another thread), or if the 5th time was just a charm!! But either way, hopefully someone else can get up and running now too
yea 'fastboot' wouldnt work for me, had to use 'fastboot-windows.exe'
I guess the 5th time is a charm. It's working. I didn't think it was going to at first. It did get in the boot animation but then restarted over again. After looping in the boot animation for awhile if finally finished and started working. The only thing I did different on the 5th try was put in the "-w" on the image update.
Persistence counts. Thanks for all the support.
SlopeSurfer said:
I guess the 5th time is a charm. It's working. I didn't think it was going to at first. It did get in the boot animation but then restarted over again. After looping in the boot animation for awhile if finally finished and started working. The only thing I did different on the 5th try was put in the "-w" on the image update.
Persistence counts. Thanks for all the support.
Click to expand...
Click to collapse
that -w makes all the difference.
easyski said:
I had this same issue, unlocked the bootloader, but then it would not boot past the white google. I tried so many things. Here is how I fixed mine.
First install 7zip or some sort of program that can deal with .tar and .tgz files assuming you don't already have it.
Download the stock image for your phone, I assume you are talking about the Galaxy Nexus LTE Verizon phone. Get that from here You need the mysid version, not the yakju. For a direct link to download the mysid version, click here
Extract that file to your desktop or wherever, you will have a file called "mysid-icl53f-factory-65895fa8.tar" then extract that so you have the following files visable:
bootloader-toro-primekk15.img
flash-all.sh
image-mysid-icl53f.zip
radio-cdma-toro-i515.ek05.img
radio-toro-i515.ek02.img
You can DELETE the radio-cdma-toro file, you don't need it for the LTE version (i hope, haha)
Put these files in your C:/android-sdk-windows/platform-tools folder. Do NOT further unzip the image.mysid zip file.
Put your phone into bootloader menu, plug in your USB cable to your computer, start your command prompt inside the platform-tools folder (in white space, shift+right click).
Type the following (taken from this thread and modified with correct file names)
Assuming you have windows computer
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot update image-mysid-icl53f.zip
This took a few mins to install, And my phone then rebooted itself and worked! (I don't think I had to manually reboot it).
It took me 5 good hours to find all this info and finally get my phone working again, hope it works for you! I was in a panic, that's for sure!
Btw, the phone's bootloader is still unlocked, but I have not yet tried to gain root access.
Please let me know if this worked for you.
Click to expand...
Click to collapse
Hi Guys,
I'm afraid I have the same problem. I was downloading on my Galay Nexus.(GSM version) since I'm in the Netherlands and suddenly the phone rebooted on it's own. Now the phone keeps on rebooting on the splash screen. The bootloader is unlocked and the phone has been rooted. I would like to follow the instructions above only I need the GSM version of the rom of the galaxy nexus. Does anybody have a link to that
Any help would be very much appreciated
Thanks a lot
Edit:addtional information When I try to restore a backup an error is given when trying to restore perhaps something is wrong with the memory?
Looking at all the problems people seem to have gotten from Superboot, I'm glad I rooted mine manually.
Educational with the added bonus of knowing that you cannot **** up your phone like this in the process.
Also: Seriously lol at the phone is available in the US for -1- day and XDA is already filled with "OMG i bricked/ruined my phone"-threads.
You guys are teh best!
josteink said:
Looking at all the problems people seem to have gotten from Superboot, I'm glad I rooted mine manually.
Educational with the added bonus of knowing that you cannot **** up your phone like this in the process.
Also: Seriously lol at the phone is available in the US for -1- day and XDA is already filled with "OMG i bricked/ruined my phone"-threads.
You guys are teh best!
Click to expand...
Click to collapse
The same thing happened on the Galaxy S2 thread when that first got released loads of people bricked their phones by messing about.
I guess some peeps have money to burn!
odd error on update step
I did get an odd error on the update step...
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
but it still installed those in the update sequence...
it seemed to work, but should i be worried?
Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.
Freesoft64 said:
Hello, I have like eight hours of continuous searching for solve this problem.
I installed like two months ago the Android Revolutionary HD 6.1.5 ROM, i did S-off, Radio-off, Root, etc, following the tutorials of XDA. But i installed the actualization of ARHD 6.2.0 and it works very nice but one day later when i was talking by the phone it stopped, then sense was not responding, and it finally restarted alone.
The big problem is it was only showing the HTC logo and then the screen puts black.
I get into HBoot and it searches for PD98IMG.zip
i putted the PD98IMG.zip in the card and it says this:
- Sd checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nhb]
No image or wrong image!
Loading...[PD98img.zip]
I say yes and it shows:
- Image unzipping fail!
Update Fail!
Press <POWER> to reboot
I tried a lot of RUU`s, like 13 and i can´t find one who works, the only who was acepted was ono withe the recovery only. With USB it does not work either.
I sent it to the company who sold me it and they have no idea about...
I hope you can help me, i am a little dissapointed, because i tried all the RUU`s what i founded in the web.
Thank you very much, Freesoft.
Click to expand...
Click to collapse
Try to go into recovery mode. What exactly is the problem. If it is not booting in...go to recovery and select fix permissions... this will solve any problems. If not try to install a rom with full wipe and reboot. If you flash a PD98IMG.zip then once again you need to root, S OFF, etc etc....
Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.
JagDave said:
Stop what you are doing before you brick your phone.
The PD98 error you are getting happens to all rooted DHD's, and is nothing to worry about (delete it from your sd card). RUU's are for stock devices, or for returning to stock.
Check to make sure you haven't screwed up your root access, and flash a ROM .zip file from the developers thread (in recovery, from your sd card). And always check the checksum before flashing.
Sent from The App that Time Forgot.
Click to expand...
Click to collapse
Well, actualy, i can`t get into Recovery, it reboots and the screen turns black, the only thing what the phone admits is PD98IMG.zip.
Thank you very much for responding!
Delete that file from your SD card, and check if you can get into recovery. If yes, download superWIPE for ARHD, and ARHD rom and install it ( it's different base i think, so you have to superWipe it )
PD98IMG.zip is the radio, if that's what you need they can all be found here:
http://forum.xda-developers.com/showthread.php?t=996630
Might be worth flashing the latest and seeing if your phone behaves enough afterwards to let you get into recovery.
I take it you are trying from bootloader?
Also does your computer recognize the phone on usb?
Sent from The App that Time Forgot.
Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.
JagDave said:
Sounds to me your Recovery has an error.
Download and extract Android Flasher http://forum.xda-developers.com/showthread.php?t=794638
Boot into Bootloader & select fastboot
Use AndroidFlasher to install a new Recovery image.
Link to my copy of of the previous 4ext Touch recovery, so it should work.
Extract the image to wherever you extracted AndroidFlasher and make sure you select 'already in fastboot' prior to flashing.
Then you should be able to get into Recovery. Full wipe, install ROM, etc.
Hope this solves your problem.
Click to expand...
Click to collapse
I am trying all this and i think it will work, the problem is my phone is "SHIP S-OFF"
But i don`t know hot to change from Ship to ENG...
Thank you very much for the answer, from now in one week i think my DHD will work again
If memory serves, you only need Eng to change the radio.
But don't quote me on that
Sent from The App that Time Forgot.
I have tried this http://forum.xda-developers.com/showthread.php?t=1396253
The PD98IMG.zip worked, so i am glad my desire is not bricked yet.
I still not having access to recovery, my phone is SHIP S-OFF not ENG S-OFF and i can`t change the Recovery, i can`t install the SDK drivers for bootloader.
I tried too with Android Flasher, and there doesn`t work because my phone is not ENG S-OFF.
My questions are this: how i can change now to ENG S-OFF?
What else i can do for revive the Desire HD?
Thank a lot for responding this post, i don`t know what i`ll do without all of you!
Personally I see no reason to Eng soff. You can still flash radios and recoveries with just regular soff. Just its done in a different way.
In that thread you posted their is a link for cwr in a pd98img. Just follow the directions I wrote.(its the first section)
But if you are set on getting Eng soff in the dev section you can use jkoljo tool.
Your second question confuses me. You said your phone is now working so what do you mean by reviving your phone?
Well, i tried ADB, the problem now is when i installed the drivers, in the command prompt i cant find my phone.
I was trying with this:
C:\adb devices
List of devices attached
In Device Manager it appairs like: Android Phone>Android ADB Interface
What i can do now?
I know I'm a little annoying, but I will really appreciate your help if we make it work!
Anyone can help with ADB with desire hd?
Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.
earthbrother said:
Well to be able to use command prompt on your computers first off would be to add the adb path which is normally C:\Program Files (x86)\Android\android-sdk\platform-tools or in C:\Program Files (x86)\Android\android-sdk\tools
Then you'll be able to use adb commands.
if not while in command prompt, just use the cd command to get in that directory so you can use the adb.exe
per exemple;
cd C:\Program Files (x86)\Android\android-sdk\tools
then you'll be able to use commands has
adb push [the file which should be in the same place] /data/local/tmp
Then if you just want to run command on your cell interface just write
adb shell
if you're in root you should start to write beside a #
it would look
<C:\[path]>adb shell
# [here you'll run command on your cellphone]
because if you run in command prompt right away
<C:\>adb device
without having the file to get the adb.exe
But as for using adb shell, if your device is connected and activated in debugged mode you'll be fine.
Click to expand...
Click to collapse
I did that, it doesn`t work because it says "error: device not found" i tried reinstalling many times the ADB drivers and another few with the path file, no results. With "adb devices" it says "list of devices attached" then, nothing.
I am really gratefull with all your answers, i hope we can made it work
I have a question more, it`s posible to put it in "debugging mode" from HBOOT?
Thanks a lot!
So, nobody can help me? that who help me will be rewarded!
You said only the recovery pd98 works. Reflash it. After it reboot and hangs take out battery and SD card. Reinsert battery and enter boot. Wait for it to scan, then reinsert sdcard and enter recovery. Wipe and reflash a rom or backup
Edit - still confused, from your pm you suggested that your dhd doesn't work? I need a simple yes it boots or doesn't, before we can go anywhere
Sent from my Desire HD using XDA App
Hello everybody,
This is my first post on XDA, although I've visited the site oftne
Anyways:
Yesterday I successfully rooted my One X and unlocked its bootloader. I also installed CWM recovery.
As the day came to a close I tried to install LC_MOD in an attempt to change the multitasking softkey to a menu button.
I did not make a backup, and the phone had no backups.
Needless to say the phone wouldnt boot. I panicked and in blind fear sortof erased everything off of my phone. everything. What I basically did was i went into advanced settings and formatted my /sdcard and all those other folders, hoping that would solve the issue (a simple data/cache wipe didnt work). So much data has been erased from the phone that I cannot even mount usb storage through CWM because im missing a file.
So, I come to you all, you gods of the tech world, with my head bowed, to ask for your help. I have literally tried everything in my power to fix the issue. I tried to install custom roms manually, that didnt work. I tried to install an RUU, and even that didnt work (the software could not detect my device). This was all made even more difficult because I myself have a mac, and much of the software I had to use was windows based, which led me on a journey to create a virtual machine.
I know i messed up, and what I'm really hoping someone out there cn do is upload one of their own backups of their One X's software, and show me how to use that to restore my phone.
Somebody out there please please help me :'(
Hi;
There is a reason all developers here shout out loud:
1- BACKUP YOUR PHONE BEFORE YOU F*** IT UP
2- DO NOT DO ANYTHING UNLESS YOU ABSOLUTELY KNOW HOW TO
But anyways, you ruined it, you should get it back, Hopefully you did not drain the battery below 30%, in that case keep on reading the next paragraph, but if you dropped the battery below 30, you should go to CWM Recovery, connect your phone to charger, and wait until it's charged properly...
After charging the phone, you need the correct RUU for your phone... As it seems, you don't know what you're doing, so go to fastboot, type this command:
Code:
fastboot oem readcid
Then post the code here in this topic, so someone can help you find the correct RUU for your phone...
After that go to THIS topic and follow the part where it says "If you DON'T have custom rom or Nandroid backup on internal SD card"
Thanks
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Xial649 said:
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Click to expand...
Click to collapse
Don't worry, with the correct version of RUU you can restore your phone...
Sent from my HTC One X using XDA
Next?
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Xial649 said:
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Click to expand...
Click to collapse
Your phone is from Voda Germany, and most probabely your correct RUU is this:
Code:
http://www.filefactory.com/file/t7qugfd3ey9/n/RUU_ENDEAVOR_U_ICS_40_Vodafone_CH-DE_1.26.166.2_Radio_1.1204.90.13_release_251279_signed.exe
Download it. Hopefully it would be the correct RUU for your phone.
1- Now open the exe file you just downloaded and make sure that it fully started.
2- Don't click anything, just open "Computer" (formerly known as my computer) in windows and enter %temp% in your address bar.
3- You will now see some folders, just search through these folders for the ROM.zip (using windows search function)
4- When you found it, copy it to your desktop.
5- Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
6- Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
7- Go to your One X, go into the bootloader and go into fastboot mode. then connect your phone to computer.
8- Open CMD and navigate to the folder in which you have the two images and the fastboot file. (using cd command and after that the address you want to go to)
9- Now type in that
Code:
fastboot flash boot boot_signed.img
10- Now this one
Code:
fastboot flash system system.img
if all this is successful, you can just reboot your phone and everything is OK.
If you can't do any of these, let us now, we will help you through it...
Good lock
---------- Post added at 03:52 PM ---------- Previous post was at 03:41 PM ----------
In other note, RUUs are build to do an stand alone recovery of your phone. So you can first try, just running the RUU application and following the instruction given in the RUU. it may work correctly
This is good
Alright so i got everything going after downloading the RUU and it was in the process of restoring my phone, but then it said my battery went below 30% so i needed to recharge. At that point i had to leave, and so I noticed that if i left my phone in the booting animation (HTC logo) the LED light indicated that the phone was charging. Since I wasnt entirely convinced that my CWM recovery was actually charging the phone, i left it on booting while connected to my pc and hopefully itll be fully charged and ready to be restored tomorrow..... I really appreciate all the help you've given me man you've practically saved my life here , and I'd like to say that you've made my first cry for help a simple and smooth one.... Thank you very much my friend :victory: :highfive:
Problem
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Xial649 said:
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Click to expand...
Click to collapse
That's another method you can try, boot_signed is the stock kernel (and yes it's that small) and the recovery_signed is the stock recovery...
Since my previously mentioned method didn't work, do this:
1- flash the boot_signed.img into your device (fastboot flash boot boot_signed.img)
2- flash the recovery_signed.img in the device (fastboot flash recovery recovery_signed.img)
3- erase cache (fastboot erase cache)
4- lock your phone (fastboot oem lock)
5- now try again to flash the system image (fastboot flash system system.img)
And also, try having around 40% battery to do all this, don't let the battery drops under 30%
ALRIGHT!!!!
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Xial649 said:
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Click to expand...
Click to collapse
Your phone is "Vodafone Germany" version and the link I gave you is the "Voda DE" which seems right, but you can try that as well, doesn't heart...
No, for original ROM (RUU) you should have a locked boot-loader, unlocking is just for custom ROMs.
ok
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Xial649 said:
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Click to expand...
Click to collapse
The two first commands should work on a LOCKED boot-loader, so I think step 1 would not be necessary... If your phone is locked you should be able to do all steps 2, 3, 5 without problem (step 1 and 4 are the exact opposite of each other and if the phone is locked already I think can be skipped)
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Xial649 said:
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Click to expand...
Click to collapse
Any luck in running the RUU itself directly?
i gave up
alright so nothig worked. Not the manual flash, and not the RUU itself. So ive resolved to visit my local help center for HTC devices, and see what they can do, if they cant fix it the least they can do is send it to the german branch for repairs. Thanks for all your help mate, you've really proven to be a great guide, but I guess something just isnt clicking in this case :/.......... i love u man
I'm not sure if this would work.
If you are still htcdev unlocked:
1. Enter bootloader in fastboot usb
2. Fasboot flash recovery -your recovery .img here"
3. Boot into recovery
4. Go to "mounts and storage"
5. Mount SD(I think this is right) and your sd should show up in your pc
6. Copy your rom zips and other zips you need/want
7. Unmount SD
8. By this time you should be able to flash your rom
9. Make sure you flash boot.img again in bootloader.
Hope this helps
Sent from my HTC One X using xda app-developers app
Isn't it mount usb storage?
Sent from my HTC One X using XDA Premium App
You couldn't mount the USB storage / sdcard because you were running CWM from the bootloader. If you connect it to the pc you can put the recovery file you flashed into the fastboot folder and do:
fastboot boot *recoveryfilename*.img
Then you can mount the sdcard etc.
If you have photos and things you don't want an ruu to get ride of, you can fix the ROM. You broke it by trying to install an deodrexed mod for an odexed Rom. If you're interested I can tell you how to fix it.
You could also take this opportunity to install a custom Rom, with which I can also help.