I decided I was going move back to stock verizon software from 2.41.617.3 and try out ViperROM. I would use the software I had on hand, execute the 1.85.605.8 RUU, and then OTA to nougat. During the RUU process, I seen on the device screen it was updating the hboot, then acted like it restarted but never powered back on. After letting the device lay dead still connected to the USB for a day, I've removed the SD/SIM, plugged it into a wall charger, tried to power on and hard reset, and getting nowhere.
My question is there a way resurrect this phone using Qualcomm HS-USB QDLoader or similar tools? or did I just brick with no return?
ricanbeans said:
I decided I was going move back to stock verizon software from 2.41.617.3 and try out ViperROM. I would use the software I had on hand, execute the 1.85.605.8 RUU, and then OTA to nougat. During the RUU process, I seen on the device screen it was updating the hboot, then acted like it restarted but never powered back on. After letting the device lay dead still connected to the USB for a day, I've removed the SD/SIM, plugged it into a wall charger, tried to power on and hard reset, and getting nowhere.
My question is there a way resurrect this phone using Qualcomm HS-USB QDLoader or similar tools? or did I just brick with no return?
Click to expand...
Click to collapse
what firmware was on the the phone prior to trying to RUU?
ricanbeans said:
I decided I was going move back to stock verizon software from 2.41.617.3 and try out ViperROM. I would use the software I had on hand, execute the 1.85.605.8 RUU, and then OTA to nougat. During the RUU process, I seen on the device screen it was updating the hboot, then acted like it restarted but never powered back on. After letting the device lay dead still connected to the USB for a day, I've removed the SD/SIM, plugged it into a wall charger, tried to power on and hard reset, and getting nowhere.
My question is there a way resurrect this phone using Qualcomm HS-USB QDLoader or similar tools? or did I just brick with no return?
Click to expand...
Click to collapse
To confirm, you basically went from the US unlocked N 2.41.617.3 firmware to the VzW MM RUU, correct?
Quick question.
Why did you flash the VzW MM RUU instead of the N RUU?
aer0zer0 said:
what firmware was on the the phone prior to trying to RUU?
Click to expand...
Click to collapse
BS_US001 2.41.617.3
andybones said:
To confirm, you basically went from the US unlocked N 2.41.617.3 firmware to the VzW MM RUU, correct?
Click to expand...
Click to collapse
Yes you're correct.
andybones said:
Quick question.
Why did you flash the VzW MM RUU instead of the N RUU?
Click to expand...
Click to collapse
I wasn't aware at the time that someone had posted the nougat RUU zip yet and HTC Sync Manager didn't have the nougat RUU available. I had the 1.85.605.8 RUU exe downloaded already from when I S-OFF'd. I've downgraded this phone before from 2.41.605.12 to 1.85.605.8 before no problems using the same RUU exe file. I let the RUU start, went and made breakfast, came back the software was stuck and the phone was dark.
ricanbeans said:
BS_US001 2.41.617.3
Yes you're correct.
I wasn't aware at the time that someone had posted the nougat RUU zip yet and HTC Sync Manager didn't have the nougat RUU available. I had the 1.85.605.8 RUU exe downloaded already from when I S-OFF'd. I've downgraded this phone before from 2.41.605.12 to 1.85.605.8 before no problems using the same RUU exe file. I let the RUU start, went and made breakfast, came back the software was stuck and the phone was dark.
Click to expand...
Click to collapse
Very sorry, my friend. Quite unfortunate.
I stick to the sd-card method usually.
But there's no reason I see why this happened to you.
:-/
So you had The US unlocked firmware? Did you complete converting it back to vzw cod and mid prior to trying to RUU?
aer0zer0 said:
So you had The US unlocked firmware? Did you complete converting it back to vzw cod and mid prior to trying to RUU?
Click to expand...
Click to collapse
yes, right before I applied the RUU. The MID was the same @ 2PS65000 and I switched the CID back @ VZW__001.
ricanbeans said:
yes, right before I applied the RUU. The MID was the same @ 2PS65000 and I switched the CID back @ VZW__001.
Click to expand...
Click to collapse
Just sounds like bad luck then. I've done that same thing before with no repercussions.
Verizon will replace it if they don't know.
I hard bricked mine due to a firmware downgrade. The phone completely died.
But I got Verizon to replace it for free, since they didn't know what I did. And several months later no charge. So yeah, just call them and get a warranty replacement.
Spinkness said:
Verizon will replace it if they don't know.
I hard bricked mine due to a firmware downgrade. The phone completely died.
But I got Verizon to replace it for free, since they didn't know what I did. And several months later no charge. So yeah, just call them and get a warranty replacement.
Click to expand...
Click to collapse
I called HTC since I bought the phone off Swappa and it's still under warranty. Hopefully they don't get it working and realize what I was doing :fingers-crossed:
Doing a little bit of morning internet browsing and seen this intresting tidbit. I knew HTC Sync caused an ADB server mismatch sometimes in command prompt, but this lil piece of info would have been nice before running an RUU exe. I suppose installing an RUU via SD card is sounds like the safer bet from now on.
ricanbeans said:
Doing a little bit of morning internet browsing and seen this intresting tidbit. I knew HTC Sync caused an ADB server mismatch sometimes in command prompt, but this lil piece of info would have been nice before running an RUU exe. I suppose installing an RUU via SD card is sounds like the safer bet from now on.
Click to expand...
Click to collapse
This has been known information for quite sometime.. Nothing new to the 10. Usually one will install hTC Syncvto get the drivers, then uninstall hTC Sync as the drivers stay.
I always run RUU on SD-Card myself because I feel it's the safest way. I'm always afraid of losing power or something and my PC shuts off mid RUU.
andybones said:
This has been known information for quite sometime.. Nothing new to the 10. Usually one will install hTC Syncvto get the drivers, then uninstall hTC Sync as the drivers stay.
I always run RUU on SD-Card myself because I feel it's the safest way. I'm always afraid of losing power or something and my PC shuts off mid RUU.
Click to expand...
Click to collapse
Exactly, as OCD as I am, I have all ruu's on separate 4GB microsd's, labeled and such. I only use fastboot or exe on rare occasions
ricanbeans said:
I called HTC since I bought the phone off Swappa and it's still under warranty. Hopefully they don't get it working and realize what I was doing :fingers-crossed:
Click to expand...
Click to collapse
I doubt they will. Most likely they'll part it out or toss it. Not really worth the fuss for them.
I can't even count how many rooted/s-off/bootloader unlocked devices I've replaced, and never had any problems. Sure they say your warranty is now void, but if it's hard bricked that bad, it's not coming back, and they'll never know!
aer0zer0 said:
Exactly, as OCD as I am, I have all ruu's on separate 4GB microsd's, labeled and such. I only use fastboot or exe on rare occasions
Click to expand...
Click to collapse
That is a little OCD, but probably should be considered "best practices." A good use for those old too-small 4g microsd cards, too. Good suggestion. Thanks.
hgoldner said:
That is a little OCD, but probably should be considered "best practices." A good use for those old too-small 4g microsd cards, too. Good suggestion. Thanks.
Click to expand...
Click to collapse
My travel kit... I still have all my 7, 8 ,9 ruu's the same exact way
Related
it gets to writing signiture and says it cant update this rom. is there a newer ruu from sprint. it used to work till i got my replacement phone in.
I had same issue..
what I did was (and this only worked cuz I had this already done) Rooted the phone with RA 1.5.2 recovery and flashed Fresh 1.0
once I got it to successfully load into fresh.. then I ran the RUU 1.29 and it worked..
still cant get it to let me un root it. it says that it is the wrong rom to do it. is there a new ruu
Have you tried flashing while in quick boot?
sorry to be such a newb. but what is quick boot and how do i get to it
Power your phone off. Hold the volume down button and power it on. You will get a menu and one of the options is quick boot (I think it's volume up but I'm not positive).
With it hooked up to your computer, check device manager in windows and make sure you don't have any missing phone drivers. If you don't then run the RUU.
ok trying that now. and no errors with drivers
still doesnt work as soon as it gets to updating signature it stops. i dont get it. i have done it a million times with no problems. now it wont work
do you have "usb debugging" turn OFF?
I can confirm testing it with debugging off it still doesn't work. I've tried a million times as well, same problem. I'm not sure if we have to flash the stock rom image before doing so, but in flashrec it only gives me the option of backing up image before actually flashing one and I get an error "Backup Failed: Could not run command" not sure if that has anything to do with it
RUU 1.29 CDMA Sprint
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.
mulcahyd said:
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.
Click to expand...
Click to collapse
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.
flipzmode said:
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.
Click to expand...
Click to collapse
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...
obannvi said:
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...
Click to expand...
Click to collapse
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?
flipzmode said:
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?
Click to expand...
Click to collapse
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...
obannvi said:
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...
Click to expand...
Click to collapse
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.
flipzmode said:
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.
Click to expand...
Click to collapse
I just dont understand why its sluggish. It was never sluggish before. I figure by reverting back to stock and then re-freshing it, it should be ok.
You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.
flipzmode said:
You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.
Click to expand...
Click to collapse
I'll give it a shot. I do have a nand backup of my original install before I installed Fresh...I did that prior and then I installed Fresh again...
Didnt work, still sluggish. I did a wipe through the recovery menu so we'll see what happens.
Hi, Sorry to start a new thread but I have a specific Android 2.1-invoked difficulty. (I think. Indeed, I hope.)
This is my phone. I can give the serial number if it helps anyone.
hero cvt ship s-on
hboot-1.76.007 (hero10000)
m1crop-010f
touch panel-syn0104
radio-6.35.06.18
Aug 4 2009, 19:43:30
My Hero is completely unmolested. Just a Hero supplied by my subcontracted Vodafone supplier. I have done nothing to it except load apps. It is not rooted. I think. Until yesterday, I did not know what "rooted" meant. Well, not in this context, and unless you are Australian you will not get that joke.
So I got the OTA ROM notice to upgrade - supposedly the prep part of Android 2.1. I accepted it and it all went fine. No problem - all done. Rebooted and running 2.73.405.5...
Nothing happened for a fortnight until Sunday evening when the second OTA part came through. I accepted. It downloaded, the 75% wait thing happened, it rebooted... It stopped at the famous triangle warning screen. I waited, waited, waited, went to bed and got up. "Hero" it said - it is hung at the Hero screen. I rebooted a few times. Nothing. Stuck. Took the battery out for a few hours, took the SDcard out, swapped SDcard, took out the SIMcard, put them back. Nothing. Hung at Hero screen. So I read a few websites = "Reflash the ROM, you fool". OK, how do I do that? And so I found the two boot methods...
Rebooting with VOL DOWN works - ie it is available but does nothing. FASTBOOT can be seen but does nothing. RESET DEVICE does nothing. HBOOT fails and says no image. USB connection is found by Windows - it appears as a device in Control Panel but reflashing the RUU.exe from the HTC website gets error 170. No connection. Hsync is loaded, says not connected. Obviously I cannor mount it. So I extracted the rom.zip from the official RUU and did the HOME+POWER Android System Recovery sdcard and update.zip malarkey. It found the zip but says "No signature". Now, this is the official HTC ROM from the website, matched to my serial number - extracted from the EXE because the EXE won't work because it won't connect - and it says no signature. I thought that that was impossible. Reading about, I think that that happens when trying to put strange ROMs onto unrooted phones. And I have no idea how to even begin doing stuff like that even if I had an interest in it.
And so I have stopped before I turn the bloody thing into a paperweight. If it is not already one such.
BTW it is under warranty. Should I just send the damn thing back to HTC?
One other message I do not understand is that when I load the system recovery, the first thing that comes up (in yellow, under the blue menu choices) is "E:can't open /cache/recovery/command". I have no idea what that means but it may mean something to somebody. There are no directories like that on the SDcard so I guess that it is referring to the internal memory.
I have tried to give as much info as I can but I am not an Android freak. I am though pretty IT savvy and at a loss to understand what has happened. I think that my phone may be branded to somewhere I do not understand but that does not explain why the official ROM has a signature issue. Or am I just a dim noobie?
Any and all help will be gratefully and humbly accepted. Thanks. Great phone BTW.
And another thing...
I did have a thought that maybe the signature part of the gig resided in a part of the RUU that isn't in the ROM.ZIP and that maybe that is why it is failing. Alas, I have no idea if that is the case or not. If it is the case, I will need advice as to how to make the phone connect to the USB so that I can use the RUU.EXE - which screen would be best etc.
Thanks again.
Are you on Windows 7? If so you may want to find an xp machine as I know people with Windows 7 including me have problems. I use a Windows XP virtual machine.
Good idea
Good idea, Andrew. Thanks. I'll report back.
menelaus said:
Good idea, Andrew. Thanks. I'll report back.
Click to expand...
Click to collapse
It will work, remember to install the HTC SYNC application and enable debugging on the phone. Good luck.
P.S I like your terminology "My Hero is completely unmolested. " lol...
Excellent!
Windows 7 it was, Andrew, thank-you. You are a Genioid. Although I have never had a problem before.
Now, shall I try updating to 2.1 again before restoring all my stuff.... Yes!
Thanks again. Much appreciated.
menelaus said:
Windows 7 it was, Andrew, thank-you. You are a Genioid. Although I have never had a problem before.
Now, shall I try updating to 2.1 again before restoring all my stuff.... Yes!
Thanks again. Much appreciated.
Click to expand...
Click to collapse
Good luck...
Or not.
andrewb84uk said:
Good luck...
Click to expand...
Click to collapse
Well, that was fun. Update failed again with...
can't chown/mod system/xbin
It seems that this is related to having an old SPL. That is all very boring and technical. I am back to my trusty RUU and will wait for a month or two before trying the update again. I have a living to earn.
Thanks for your help, Andrew.
I've searched the forum, found some good information but I am still coming up short on getting my phone to normal.
My (Rooted) Hero was perfect until I installed a beta version of Opera Mini Browser and then it went all hinky.
Some of the touch screen keys stopped working and parts of the screen have become unresponsive.. The entire phone (software) is now unstable.
I have tried a Nandroid recovery to no avail.
I've tried the steps available at the below link but still come up short.
http : // developer. htc. com / adp. html
Are there any steps or instructions specifically for the Hero to flash with a new factory image/radio/system?
Also, I'm a little sketchy on fastboot.
Any help would be appreciated. I almost Hulk Smashed the phone but I remembered I got excellent information from this site when I installed my first ROM.
Thank you.
I apologize that my search for this information didn't keep me from making a thread about it.
fix it
just find the latest, or any, RUU.
run that. it'll take everything back to the way it came
try this one: ftp://hero:[email protected]/HTC Sprint Hero MR 2.27.651.6.exe
it's not the Newest, but almost the newest.
http://www.htc.com/us/support/hero-sprint/downloads/
if that doesnt work
rideascooter said:
just find the latest, or any, RUU.
run that. it'll take everything back to the way it came
try this one: ftp://hero:[email protected]/HTC Sprint Hero MR 2.27.651.6.exe
it's not the Newest, but almost the newest.
Click to expand...
Click to collapse
rideascooter said:
http://www.htc.com/us/support/hero-sprint/downloads/
if that doesnt work
Click to expand...
Click to collapse
Agreed, an RUU should fix it
I have tried to update the RUU.
The process starts, the screen on my Hero reads HTC and then nothing.
The installer then displays an ERROR 171 message regarding USB connection.
I guess I should have mentioned that in the first post.
Also I have tried to reflash the current ROM with the same results. The touch screen is dead in certain areas in portrait mode but not landscape mode. The same for the touch keyboard.
Any other suggestions?
RUU doesn't work. The update process starts and then the phone disconnects from the computer.
Easy10pins said:
Any other suggestions?
RUU doesn't work. The update process starts and then the phone disconnects from the computer.
Click to expand...
Click to collapse
have you tried running the RUU from fastboot?
Easy10pins said:
Any other suggestions?
RUU doesn't work. The update process starts and then the phone disconnects from the computer.
Click to expand...
Click to collapse
get a new usb cable... try, try again... patience, yoda...
riggsandroid said:
have you tried running the RUU from fastboot?
Click to expand...
Click to collapse
Can you explain fastboot and how to do it on the Hero?
Easy10pins said:
Can you explain fastboot and how to do it on the Hero?
Click to expand...
Click to collapse
I believe iy is a low level boot menu
I used it to run the ruu when it kept failing the usual way.
To access it poeer off your phone and turn it on while pressing vol up + home and you should see a white screen and it will say fastboot usb. then run the ruu.
It should complete.
hfelton said:
get a new usb cable... try, try again... patience, yoda...
Click to expand...
Click to collapse
I have several different USB cables and have tried them all including the one that came with the phone.
riggsandroid said:
I believe iy is a low level boot menu
I used it to run the ruu when it kept failing the usual way.
To access it poeer off your phone and turn it on while pressing vol up + home and you should see a white screen and it will say fastboot usb. then run the ruu.
It should complete.
Click to expand...
Click to collapse
AWESOME! I knew I could find the answers here. The phone is currently updating.
Now to find a decent ROM to reinstall.
Any suggestions?
Easy10pins said:
AWESOME! I knew I could find the answers here. The phone is currently updating.
Now to find a decent ROM to reinstall.
Any suggestions?
Click to expand...
Click to collapse
Let it finish before you claim victory.
CM6. 1 is good as well as AOSP.
Well did it work?
Froyo Powered HTC Hero
Gentlemen,
Thank you for your assistance. Although I was able to install the latest RUU, the touch screen is still unresponsive. I can't say the phone is bricked but it's pretty much useless at this point.
Everything was good until I installed the beta for Opera Mini mobile. Then things went screwy. Oh well.
Good thing I had all of my apps and data backed up to the SD card so when my Samsung Moment comes in, I can get back up to speed quick.
Thanks again for all of your assistance.
I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.
live_free said:
I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.
Click to expand...
Click to collapse
what sbf did you flash? is it att bell etc? need some more info to help you out.
aideneisley3 said:
what sbf did you flash? is it att bell etc? need some more info to help you out.
Click to expand...
Click to collapse
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204
live_free said:
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204
Click to expand...
Click to collapse
STEPS:
1) Have the correct Motorola drivers installed for your PC (i.e. x32-bit or x64-bit).
2) Download RSD Lite (Links above) & install on your PC.
3) Choose a sbf file to download and flash from Motorola Atrix Firmware Super Thread: http://forum.xda-developers.com/showthread.php?t=1125944
If you are currently running firmware 4.5.91, I suggest that you only flash back to this firmware version. Flashing back to a eariler sbf/firmware version may have unintended consequences, the most serious of which is bricking your device.
*Note: U.S. AT&T users should only flash AT&T sbfs, internationl users should only flash their particular sbf versions.
4) Read the above sbf hints, trick, etc. to help prevent RSD Lite problems/errors.
5) Open RSD Lite and load the sbf file that you downloaded.
6) Put your device in RSD Protocol Mode by powering OFF, and upon powering back ON, hold both the power button and the volume UP button. Device should now say "Entering RSD Protocol Mode."
7) Connect your device to your computer via the usb cable, and select your device by clicking/highlighting it in RSD Lite.
8) Select START in RSD Lite and let the sbf flash process fully complete before disconnecting the device from the PC. There will be several reboots and the process make take 5 - 10 minutes to complete a FULL sbf flash.
9) If you have any errors or problems as a question, prefably in the Q&A section.
this is what i have done and worked for me! good luck
i copied this from the noob guide found here http://forum.xda-developers.com/showthread.php?t=1154600
Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.
live_free said:
Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.
Click to expand...
Click to collapse
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!
aideneisley3 said:
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!
Click to expand...
Click to collapse
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.
live_free said:
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.
Click to expand...
Click to collapse
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
aideneisley3 said:
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
Click to expand...
Click to collapse
Yes. Same exact problem.
live_free said:
Yes. Same exact problem.
Click to expand...
Click to collapse
oh ok well then i'd have to agree with you then maybe it is a hardware problem... sorry i wasn't much help.
it wouldn't hurt as a last ditch effort to use motorola's software update program that you can download from their site it will tell you that there is no update and ask if you want to use it to restore your phone basically it reflashes it...
haha thats all i got. maybe someone else could offer more help.
good luck! =]
live_free said:
I did everything properly and now am in a boot loop, and I've done a battery pull.
Click to expand...
Click to collapse
apparently not.
in his defense replacement phones are refurbished (cough... broken and maybe fixed to like new). motorola gave me a replacement with broken senor so the screen didn't turn off when i was in a call and that was out of the box and when they replaced that one the screen was messed up it had super bright spots all over the screen so it is possible that it is moto's fault.
not saying it is moto's fault but that it is possible lol
Evening all,
I have a DHD that is stuck in HBOOT/FASTBOOT, or at least that and the stock recovery program is all I can get to.
I tried an AAHK, and it basically tried to do a downgrade and has left the phone with no data, still at s-on, and I can't find an operator RUU(three uk) to flash it back to a useable state.
Is there a three RUU available?
I'm running around in circles as I can't make a gold card, due to not having another DHD available to retrieve the MMC2. All I need is a goldcard and then I can flash a WWE, but I cant find anywhere to make one without the phone or a similar one.
I dont think it turned the microsd properly into a gc, before it tried to downgrade. Is their anyway I can test to see if the memory card has been successfully goldcarded?
Any help would be greatly appreciated.
Thanks
James
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Teichopsia said:
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Click to expand...
Click to collapse
Mine has a lot of those symptoms to be honest. If I vol down/power to get to Hboot, it sits there with no keys being able to be pressed, just highlighted blue FASTBOOT and not even checking for files on memory card
If I just turn it on, it sits at the three splash screen, which i assume is the equivalent of the HTC one for branded phones.
I have now turned it on and left it on as per those linked threads, in the hopes the sd is a proper gold card and it is just slow. Fingers crossed.
Thanks for the pointer
James
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Teichopsia said:
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Click to expand...
Click to collapse
Well what I did, was follow the AAHK instructions, cleaned up my environment etc, went through the install. When it asked to do the downgrade, I said yes, then it asked about wiping and was I sure, so I said yes. It then rebooted the phone and it is now as it is. I pulled the battery and tried vol-down/power, which brings up HBOOT, but it doesnt let me do anything, vol keys and power do not work and it doesnt start looking for image files.
From that thread, it was mentioned it just could be going very slow, and people have just left it overnight. This is what I have done now, and will see if it has accessed the files on the memory card and downgraded properly in the morning.
Thanks
James
Have you tried looking for the RUU here?
Last I remember when aahk downgrades, you will be asked to reboot to basic recovery twice
Panic over, thankfully! Not my phone, you see!
It was so easy to root my S2 and the X10 before that, and the iP3G before that(and custom winmo, and nokia etc etc), I said give it to me, i'll sort you out with some ICS rom action.
Then it all went wrong as explained in my previous posts.
2 days later, i finally found the H3G RUU I needed to get an system on it. Silly branded phones. Took 4 hours to download as it was on a throttled download service(my 100MB leased line usually eats 300MB in seconds, but not this time)
So long story short, into FASTBOOT USB, ran the RUU and it completed and put froyo on the phone, and as a happy coincidence it was at a level that didn't need a downgrade, so AAHK ran through like a trooper, busybox installed and hey presto, ENG S-OFF. IceColdSandwich installed through cwm and one happy mate, who then proceeded to ring his wife and tell her to rent a film, as he would be tinkering with the phone all night lol
It was getting to the point I was going to have to give him my S2, and as I've just taken possession of a Sony SmartWatch, I didn't want to do that!!
Thank for everyone's help and pointers, not sure what went wrong the first time(probably a memory card/incompatibility/goldcard problem), but all sorted now.
James