//Header information
***UNLOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
eMMC-boot
Hey guys, I recently acquired an EVO 3D in a trade deal and even though I don't want it (I plan on selling it but the cash deal + EVO 3D was worthy), I ended up being hellbent on rooting it last night. Success. Great, I threw Cyanogenmod7 on there and realized I'll have to undo the root/ROM to sell it later. I used what I believe is referred to as the REVOLUTIONARY method (using HTCDev.com, some terminal commands on my Mac, etc.)
Anyhow, didn't think it would be hard to undo what I did and I guess I was wrong. Let me tell you what I've tried so far.
I've tried using the PG86IMG.zip flash and nothing. No option (VOL UP or VOL DOWN) to even TRY installing it. Just quickly flashes the green text "No Image!" under each category (it goes too fast for me to read it) and I'm back at the boot menu. I've tried using different copies of the PG86IMG.zip with the same results (latest site acquired from: Goo-inside me, or something like that).
I've also tried using the RUU*.exe method on a Windows 7 machine. I've installed the drivers, everything checks out just fine until it actually tried to update the ROM. What happens here is that the phone reboots (as expected) and though the splash screen is different (black background with silver/gray hTc logo, semi-reflected) from the usual splash screen (white background with hTc in green), nothing happens. The software on the Windows 7 machine says "Waiting for bootloader" - which never shows up. Then it quickly gives me an error stating that the USB cable between the PC and the phone needs to be checked. Of course, there's no disconnect anywhere in the cables.
Please help! I planned on selling this device but if it's stuck in Cyanogenmod7, especially with no Google apps (couldn't get Gapps*.zip to work but whatever, not really concerned about that right now), there's no way I could sell this thing. I'm fairly knowledgeable in the basics of these matters as I have a rooted EVO 4G as well.
Anyone wanna buy an EVO 3D? HAHA
you could always flash a stock rooted rom .
You've gotta relock through adb before running the RUU.exe; then it'll work.
Hit the thanks if I helped
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
zer0xity said:
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
Click to expand...
Click to collapse
It's because of the pg86img.zip you can delete/move it away from the root of your sd card and get back into recovery... but you shouldn't need to, follow these steps:
1) Turn off phone
2) Hold power+vol down
3) Choose fastboot
4) Plug into your PC if you're not already
5) When you see FASTBOOT USB on the phone screen go back to your command prompt where you have your adb.exe, fastboot.exe, etc.
6) Type: " fastboot oem lock "
7) Aaaand you're done w/ the relocking go crazy and run your RUU.exe, don't reboot the phone or anything just run your RUU while your phone's still in HBOOT.
Edit: Oh, the adb I was talking about would kind of make everything easier; in command prompt: adb reboot bootloader AND THEN fastboot oem lock
Two steps, mhm.
I'm on it! Standby...
Okay, the adb stuff - can I do that from terminal in Mac? I tried doing it while in the appropriate folder where all that adb stuff is and I typed: adb reboot bootloader (ERROR: command not found), then I tried just: reboot bootloader (not permitted). I did try: ./fastboot-mac oem lock (successful. header now says *** RELOCKED ***).
Tried the RUU*.exe stuff on the Windows machine while in that state and again an alleged problem with the USB connection...
Sounds like we're close?
BAM! Got it. You put me on the right track with that last post. RUU still wouldn't do the reversion even though I had some drivers installed on Windows so I had to find some other drivers (some HTC3*.exe file, 13MB) and ended up running those for it to recognize the phone.
+1 to you, sir. Thank you so much!
Glad it all turned out well.
Related
Hello everyone, been a lurker for some time, but have never needed to post before until today. I'm accustomed to rooting and installing custom roms but I've never had anywhere close to as much difficulty as Im having with this tf201. Heres the situation:
Not sure if you'd call this bricked, as I have total access to fastboot, adb, and CWM Recovery (version 5.8.3.4 touch btw). However my most recent attempt ended with totally wiping from the volume down+power menu (whatever its called). I can not turn the tablet off, as it automatically boots to the asus splash screen (and goes no further, naturally). It is unlocked, and my drivers do work (both fastboot and adb recognize the device), but I can not flash or push anything to the sdcard (with adb its a protocol failure, with fastboot I get "sending zip....OKAY writing zip....FAILED [remote : [FileOperationFailed]]) Don't know if it needs to be said, but I also can't simply drop the file on the sd card as if it were a media storage device as "my computer" does not recognize that it is connected (Oh I am using the naked universal drivers from http://forum.xda-developers.com/showthread.php?t=1998650 )
So yeah, Im at a loss as it seems like no one has had this particular problem before (also my connector cable works fine, so its not that). Any help would, of course, be greatly appreciated.
EDIT: On the tablet after trying to flash with fastboot it returns "Failed to process command flash:zip error (0x30003)"
Really? Not a single person has any idea? Could really use some help here...
GrimAgent said:
Really? Not a single person has any idea? Could really use some help here...
Click to expand...
Click to collapse
You do not flash zips with fastboot.
First of all tell me where your "NVIDIA" logo is when you first power on, bottom center or bottom right?
The nvidia logo is in the bottom center of the "EEE PC Splash"
This is going to sound stupid, but did you verify the MD5 before you tried to flash it?
GrimAgent said:
The nvidia logo is in the bottom center of the "EEE PC Splash"
Click to expand...
Click to collapse
You are still on the ICS bootloader if NVIDIA is bottom center.
Go here http://www.teamw.in/project/twrp2/93 and follow the instructions for "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)"
You will need to get the ICS blob file. Never flash the wrong recovery for what bootloader you are on or you can brick your device.
If you get it working and you want to upgrade to Jellybean bootloader there is instructions in post 2 of the Hairybean Rom thread. "Upgrade instructions for ICS"
edit.. to make it a bit easier for you.
Get this file http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.4.4.0-tf201-ICS.blob
Rename it to twrp.blob
Place the twrp.blob in the same folder as your fastboot exe
Go into fastboot and type
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for it to finish and then type
fastboot -i 0x0B05 reboot
see if that works.
Damn, I had a feeling it was the bootloader issue that I messed up. I went searching all over for how to find out which one I had once I realized my potential mistake. Gonna give these steps a try
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
GrimAgent said:
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
Click to expand...
Click to collapse
If you now have twrp on there you dont need to push a file. Place the file on an external SD card on the root and plug it in before starting prime.
When going into TWRP go into install and select external SD. Pick your rom and then flash it.
Thanks a lot flumpster, everything's good now and Ive got cyanogen up and running smoothly. You've brought my tablet back to life and Ive learned a valuable lesson
I pretty much screwed my phone so bad, and I can't seem to the find any solution anywhere...
Here's what I did in order:
-tried rooting it with this guy's guide [link taken down since im a new member, but it's on htconeroot dot com//htc-one-root/how-to-root-htc-one-windowsmaclinux/]
[keep in mind it's S-On with HBoot 1.55]
-found out TWRP wasn't updated so I replaced it with a newer one (2.6.3)
-now rooted device
-wanted to restore to normal stock settings so I downloaded the Guru Reset M7 1.26.502.15 and put it in my root folder
-went to recovery to install the guru reset ZIP
-things install, but touch screen doesn't work
problems now:
-can't turn off phone on main screen (tried holding down power, but doesn't restart phone past the 3 second mark)
-can't boot into bootloader from restart
-ruu doesn't work
can anyone provide me with help? please and thank you
EDIT: few things to keep in mind
-everytime i use RUU 3.17.502.3, it loads up black screen with HTC logo int he middle, then I can turn off the phone.
-when loading up, i can load into bootloader
-when choosing recovery/factory reset, it brings up the software update screen, but then goes to red triangle
-at red triangle screen, i can reboot system through android recovery system.
-back at square 1, touch screen doesn't work, etc.
All I can say is that I am in the same waters, phone stuck in bootloop, or goes to triangle of death, and PC WILL NOT recognize phone at all so without driver support, I am screwed too.
Added: All I did was unlock through HTCDev, and all hell broke loose, loaded up AIO, and phone freaked upon flashing TWRP. 1.55 HBoot, 4.3 ATT update.
hack14u said:
All I can say is that I am in the same waters, phone stuck in bootloop, or goes to triangle of death, and PC WILL NOT recognize phone at all so without driver support, I am screwed too.
Added: All I did was unlock through HTCDev, and all hell broke loose, loaded up AIO, and phone freaked upon flashing TWRP. 1.55 HBoot, 4.3 ATT update.
Click to expand...
Click to collapse
Here's a solution:
-get into bootloader mode
-fastboot
-plug usb in
-open cmd, then get to where your HTC One rooting stuff is (for example, everything was in a folder on my desktop)
-type "fastboot oem lock"
-your phone should say "relocked"
-open the latest RUU you have
-run things normally
that's how i fixed mine, lemme know if you have any more questions.
i also don't know why your phone has to be "relocked" in order to update it's software.
pztrixwsup said:
Here's a solution:
-get into bootloader mode
-fastboot
-plug usb in
-open cmd, then get to where your HTC One rooting stuff is (for example, everything was in a folder on my desktop)
-type "fastboot oem lock"
-your phone should say "relocked"
-open the latest RUU you have
-run things normally
that's how i fixed mine, lemme know if you have any more questions.
i also don't know why your phone has to be "relocked" in order to update it's software.
Click to expand...
Click to collapse
A thousand thanks, you are my new hero! And if you run the RUU, then go back and re-unlock the bootloader, it only says "unlocked" not tampered.
That's why we need to wait for the issue with Rumrunner S-off for our phones to get squared away. So we can flash other carrier or older software.
---------- Post added at 06:51 PM ---------- Previous post was at 06:40 PM ----------
Has anybody had success with Rumrunner for 3.17.502.3 yet? I have been hitting a wall and am not the only one. The phone is freezing on adb at test 2.1. We have tried flashing the RUU and doing it again, but it fails every time in the same way.
Here's what I get:
Code:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (22/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
Specifically looking for somebody with 3.17.502.3 to chime in if they've tried it, or one of the most awesome devs that work tirelessly so we common folk may find new ways to nearly-brick our phones :silly:
hack14u said:
A thousand thanks, you are my new hero! And if you run the RUU, then go back and re-unlock the bootloader, it only says "unlocked" not tampered.
Click to expand...
Click to collapse
Yea no problem bro, i was in your position for the whole day and i stumbled upon a billion sites and eventually trial and error'd the whole way through
Check the discussion in other thread about 4.3 and s-off. We have tried quite a few different things with no luck so far. I even posted in HTC one forums in the support thread. Hoping they will release something soon for our hboot 155.
Sent from my HTC One using xda app-developers app
I have been following all the posts about rooting and I managed to soft-brick my phone. I was able to temp root the phone, but I could never get superCID because the modified CID would never take. I didn't get errors, it just didn't stick. Anyway, I flashed the recovery for 2.17, but my phone took an OTA update to 2.19 a few days ago, and now I am stuck on the main screen but without the sense unlock ring. The screen works, and I can access the phone's drive and sd card, and I can adb. The bootloader shows ****TAMPERED***** (been that way for a while), and Bootloader is LOCKED. FIREBALL PVT SHIP S-ON RL, HBOOT is 1.15.0000.
Any ideas to recover to a fully booted phone?
yes had the same thing happen to me. download the ruu exe. from here http://www.androidruu.com/?developer=Fireball i used 217.605.2 ruu. put phone in fastboot connect it to computer and run ruu exe. on ur computer
I followed your reply but am not having any success . . . yet.
I go through the RUU.exe screens where I verify that I want to "upgrade" from image version 2.19.605.2 to image version 2.17.605.2.
Then RUU.exe runs to the point where it tells me the process will take 10 minutes. It then gets to "waiting for bootloader........" and the phone looks like it is rebooting and a black "HTC" screen appears. Bootloader never appears. A Windows 8 Systray error message then appears saying "USB Device Not Recognized - The last USB device connected has lost communication with the computer [or something like that]" The RUU.exe program then states: "ERROR [171] USB Connection Error. Check the following: (1) phone is connected to USB cable; (2) PC is connected to USB cable" There is no further option than to EXIT the RUU.exe. (Yes, my cable is connected to a USB 2 port).
I tried to do this twice with the same error message and the same disappointing results. The phone stays locked on the black HTC screen and I need to pull the battery to change this locked state.
I have no trouble communicating with the phone with ADB and I have root (#) at ADB Shell. I JUST loose USB communications with the phone as soon as it goes tries to load bootloader. I originally tried to run RUU.exe the way you stated by putting the phone into fastboot and then running RUU.exe, but then the program would not find the phone. What am I missing here? I have HTC drivers loaded, but I keep getting the comm error. Any more ideas?
Maybe I need to flash a recovery for 2.19.605.2? Any idea where I might find that?
OK, not sure why I didn't do this sooner, but I did a factory reset from Bootloader and it seems I am back again running the 2.19.605.2. Not sure if I can root this new OTA version using the 2.17.605.2 procedures or not, but I may give this a break for a bit.
Yeah u can't downgrade to 2.17 if ur on 2.19
Sent from my XT1060 using xda app-developers app
Hey so this issue is actually solved. If you want to see the process that I went through to get to the solution, please do! Its not that hard, I promise. Maybe a little stressful, but totally doable. Cheers!
----------------------------------------------------------------
I'm currently stumped on how to fix this issue that I'm currently having with my HTC Rezound at the moment. I did not buy this from any Verizon retailer, I bought it online in 2012. Anyway, the only issue that I've had the past few months is just that my battery kept dying super quickly and that my phone would randomly shut off after flashing Liquid Smooth ROM on my phone. I originally live in California but I moved to Spain, so any option of "take it to a retailer" or "take it to a cellphone repair shop" is not practical since NOBODY in Granada has ever heard of this phone.
The last time I had my phone operational was when I was using Mobile Data to chat with one of my friends on an app when it died, as usual. This time, I wasn't home to immediately plug it into the charger. One other thing I'd like to point out is that the number one reason why I think my battery kept dying so quickly is that while I was in Morocco, I was using an adapter to charge my phone. Maybe the difference in voltage fried my battery, not sure.
Anyway, I was out for at least 3-4 hours before I finally got home to put it on the charger. I plugged it in and went to bed without even looking at my phone. Woke up the next morning to power it up to find that not even the orange light is on (or green when fully charged). I unplug it, plug it back in and nothing happens. I take out my battery, keep it out for a couple hours and put it back in. I hold the Power button until the phone vibrates, screen turns on with the green HTC logo on a white screen, and then turns off. I take out the battery a couple more times and still same thing. I decide to leave the battery out for 2 hours and then put it back into the phone and directly to charge. The orange light turns on for about 3-5 seconds before turning off.
If I try to push the power button, nothing happens unless I take out the battery again. So I leave the battery to charge but then my phone started to get a little warm. Instead I just disconnect and leave the battery out of the phone for about 3 weeks until I had 2 spare new batteries shipped to me here in Spain. Once I got the batteries, I tried once again to get my phone working by replacing the batteries. Orange light comes on for 3-5 seconds before going out and its the same thing as before. I plug it into my laptop, use the CMD "adb devices" and I get nothing listed or "error: device not found". I can only boot into hboot by using Power + Down Volume and thats about it. By the way, its S-OFF and rooted with a custom ROM (Liquid Smooth) and the recovery should be Amon Ra.
If I get to fastboot/hboot and I select Factory Reset, Recovery, or Reboot, the screen dims, vibrates a bit and flashes the HTC logo on a white screen for 3 seconds before turning off. As of now, I can't connect to my phone through the PC as it doesn't even read via USB port, HTC Sync doesn't read, and I can't reach my phone through CMD prompt. Does anyone have any information on how I could fix this? And even though I have read most articles about the orange light thing and clockworks recovery, I'm still open to any/all solutions.
Update #1
Since I have not gotten any help from any community members or from other people, I decided to pursue this on my own to the best of my abilities. I decided to start looking up different articles with the same symptoms that I have and to see what the solutions were. Long story short, I combined a few solutions and one of the things some people did was just reinstall stock ROM altogether. For now, I am happy to say that I can access my phone via Command Prompt, but ONLY with "fastboot" commands. I came to this realization when I was looking up how to install stock ROM when one of the commands was to put "fastboot reboot-bootloader" and I happily had much success. Just make sure you're in FASTBOOT USB or else it won't work. I also ended up reinstalling all my HTC Drives and HTC Sync. At the moment, I cannot access internal memory via USB nor connect to HTC Sync. Also, to see what other commands that are available to your disposal, you can type "fastboot help".
Update #2
Since the last post, I've been looking around. Found out that the best solution would be to flash a stock RUU onto the phone. Requirements before flash would be to erase everything but the only command I can get to erase is with "fastboot earse cache" and thats about it. Everything else is unsuccessful. Anyway, instead of just going straight to downloading and flashing stock RUU, I accidentally decided to try following a procedure I read step by step by first locking bootloader with the command "fastboot oem lock" command and phone immediately shuts off. I try to power on again but just does same as before: boots to green HTC logo on white, stays on a for a few seconds, and turns off. This time, though, without the bootloader coming up. I believe I have bricked my phone.
Can you still get to Fastboot? If so, unlock again, and then download the latest TWRP recovery, and try:
fastboot boot recovery.img
replace recovery.img with the name of the recovery image file for TWRP.
Once that is done, look at your mounts and see if you can access any partitions.
Update #3
acejavelin said:
Can you still get to Fastboot? If so, unlock again, and then download the latest TWRP recovery, and try:
fastboot boot recovery.img
replace recovery.img with the name of the recovery image file for TWRP.
Once that is done, look at your mounts and see if you can access any partitions.
Click to expand...
Click to collapse
Alright so right now I am EXTREMELY happy!!! Thank you so much for the advice. My phone happened to not get into fastboot anymore for some reason after I thought I bricked it. The final attempt I made before going to bed that night was to put my Micro SD into my phone and attempt to get into fastboot one last time and by some miracle my phone decided to. This is the steps I took to get my phone back operational so please excuse the length. At the moment, its not completely solved until I get my phone 100% operational, but this is what I have so far. I listed a few notes before I started so here goes.
Update #3:
HTC Rezound 2014:
- S-OFF and rooted with Liquid Smooth ROM and Amon Ra recovery
- fastboot oem LOCKED (no bootloader access available)
- batteries all low powered, 1 fried (3 total)
- when plugged, charging light turns on for 3-5 seconds and turns off without charging battery or
allowing phone to power back on; requires battery pull to restart process
- Power + volume normally takes to bootloader; recovery, factory reset, and reboot option fail
- when attempting to boot, phone will vibrate, power on to green HTC logo on white screen and then
turns off to black
- any attempts to turn on phone result in said description and requires battery pull after each attempt
Current issues:
Batteries are not fully charged
Cannot access bootloader because of last command in console, "fastboot oem lock"
PC cannot read devices despite drivers installed and fully working USB cord
Possible causes:
- Extra batteries just aren't fully charged to allow phone to fully boot
- System files are corrupted; no recovery, no boot.img, no OS; nothing for the phone to read to start up
Attempt 1:
- Plug phone with battery inside and cover off
- Clear memory off SD card
- Remove battery and insert SD Card
- Note: Battery has little to no power
- Plug into USB cord connected to computer
- Before orange light comes on, hold down Power + Down Volume
- Failed; repeat (unplug from phone, battery pull and reinsert)
- Attempt to leave battery to charge for 8 minutes via USB
- Charge attempt failed; orange light turns on for 3 seconds before turning off
Attempt 2:
- Remove phone cover, take out battery and reinsert
- Hold Power + Down Volume and go into Fastboot USB
- If successful, plug into PC via USB cable
- Open console (Shift + Right Click in folder AndroidSDK\platform-tools)
- For list of fastboot commands, type in the console (which should read slike C:\AndroidSDK\platform-tools\) "fastboot help" without quotations
- To make sure you are connected, type the command "fastboot reboot-bootloader"
- If the phone reboots into FASTBOOT USB after the command, then you're good
- Type in the command "fastboot devices" to make sure your devices can be read by your computer (should show up like HT18BY892363 fastboot)
- Since the last thing I did on my phone was "fastboot oem lock", use the command "fastboot oem unlock" and hope for success
- Command prompt will read something like:
...
<bootloader> [ERR] Command error !!!
OKAY [ 0.014s ]
finished. total time: 0.017s
- Type into command "fastboot oem get_identifier_token"
- Submit Identifier Token to HTC Dev (need to create an account)
- Download file and save in platform-tools folder with the adb.exe and fastboot.exe files
- Type "fastboot flash unlocktoken Unlock_code.bin" into console
- Select "Yes" option and phone will reboot as follows: vibrates, shows HTC logo on white screen for 3 seconds and turns off
- Unplug phone from USB, take out battery and reinsert
- Hold Power + Down Volume and boot into FASTBOOT USB; should read "*** UNLOCKED ***" at top of screen
- Using TWRP 2.8.0.1F, extract "recovery.img" into "platform-tools" folder
- Type command "fastboot boot recovery.img" and profit!
Glad you got it working!
acejavelin said:
Glad you got it working!
Click to expand...
Click to collapse
I actually have another issue now. I have managed to install TWRP onto my phone but when I attempt to flash a RUU I downloaded, I get this error:
Installing '/external_sd/PH98IMG.zip' . . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/'external_sd/PH98IMG.zip'
Error flashing zip '/external_sd/PH98IMG.zip'
Updating partition details . . .
E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/devlog
E: Unable to mount storage.
Your partition table is corrupted... Being S-Off you have an option, you need to run an EXE RUU, not flash a ph98img... I think the last one was 3.12.605.12 and you run it from a Windows PC with the phone in download mode... If that doesn't work only a JTAG programming can fix it, if it can be fixed. Once you get to this point that all partitions are not mountable, it is tough to recover, if it can be done at all. You have about a 50/50 chance at best.
acejavelin said:
Your partition table is corrupted... Being S-Off you have an option, you need to run an EXE RUU, not flash a ph98img... I think the last one was 3.12.605.12 and you run it from a Windows PC with the phone in download mode... If that doesn't work only a JTAG programming can fix it, if it can be fixed. Once you get to this point that all partitions are not mountable, it is tough to recover, if it can be done at all. You have about a 50/50 chance at best.
Click to expand...
Click to collapse
So how would I go about finding an EXE RUU? Do I just google "HTC Rezound 3.12.605.12 RUU exe"? And I apologize for the noobish questions, this is actually my first time getting this bad with my Rezound haha. I found this article (although it isn't associated with the phone) and was wondering if I should give it a try or not. http://forum.cyanogenmod.org/topic/6433-solved-messed-up-partitions-on-internal-storage/
shock_and_awe said:
...
E: Unable to mount '/system' <<<<<< THIS is the real problem
E: Unable to mount '/devlog
Click to expand...
Click to collapse
Without /system being mountable, or even formatable, there isn't much you can do..
Since ALL partitions are unmountable it likely means the PIT (Partition Information Table) for the internal 16GB storage area is corrupted and it needs to be recreated.
This MAY be fixable manually if you have a Linux machine, and understand the partitioning of THIS device... The Linux part I have no issue with, but I no longer own the is device and do not have a copy of the partition table to help you repartition it.
Honestly, for all the work involved, why not just grab a cheap phone online and use it? I mean you can get a Galaxy Nexus, a replacement Rezound, or a handful of other LTE devices for under $100 on swappa.com
acejavelin said:
Without /system being mountable, or even formatable, there isn't much you can do..
Since ALL partitions are unmountable it likely means the PIT (Partition Information Table) for the internal 16GB storage area is corrupted and it needs to be recreated.
This MAY be fixable manually if you have a Linux machine, and understand the partitioning of THIS device... The Linux part I have no issue with, but I no longer own the is device and do not have a copy of the partition table to help you repartition it.
Honestly, for all the work involved, why not just grab a cheap phone online and use it? I mean you can get a Galaxy Nexus, a replacement Rezound, or a handful of other LTE devices for under $100 on swappa.com
Click to expand...
Click to collapse
I see what you mean. Honestly I would get another phone if I could but I'm no longer living in the States, I'm studying in Spain. Shipping is super expensive so I'll have to go local or figure something out. Its the only phone I have at the moment but I'll most likely just get another phone for cheap. I really appreciate the help and the advice though. If anything, this will be my "side project" to work on when I'm SUPER bored and fix it for sh**s and giggles.
shock_and_awe said:
I see what you mean. Honestly I would get another phone if I could but I'm no longer living in the States, I'm studying in Spain. Shipping is super expensive so I'll have to go local or figure something out. Its the only phone I have at the moment but I'll most likely just get another phone for cheap. I really appreciate the help and the advice though. If anything, this will be my "side project" to work on when I'm SUPER bored and fix it for sh**s and giggles.
Click to expand...
Click to collapse
Spain has mostly GSM service, correct? Why not look into cheap devices locally? Amazon.es has several devices under 200 euros, Moto G, Moto E (89 euro), LG G2 mini, Xiaomi Red Rice, BQ Aquaris E5, etc... Or local classifieds online.
Update #4
SOLVED!!!
The solution (as it appears to be on a few success stories) is to completely install an Official Stock RUU. You just have to be content with losing ALL your data (if there was anything to save in the first places). What I ended up doing was using a microSD adapter this whole time and I would not have been able to get my phone back without it. This is what I did (following the installation of TWRP Recovery):
Official Stock RUU:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
Update #4 (Final):
For this process I used a microSD adapter, in which I plugged into my laptop and put the required files in there.
- Download file from Android Police and rename to "PH98IMG.zip"
- Using your storage device (whatever way you choose just do this) put the .zip file onto the SD card
- Place the SD card into your phone and boot into HBOOT using Power + Down Volume
- Wait a few minutes until the PH98IMG.zip is finished loading and press Volume Up for "Yes" when asked "Do you want to start update?"
- After about 10-15 minutes, the phone will ask you to reboot the system
- Profit!!!
- Don't forget to remove the PH98IMG.zip file from your SD card or else every time you boot into HBOOT, it will reload the file
acejavelin said:
Spain has mostly GSM service, correct? Why not look into cheap devices locally? Amazon.es has several devices under 200 euros, Moto G, Moto E (89 euro), LG G2 mini, Xiaomi Red Rice, BQ Aquaris E5, etc... Or local classifieds online.
Click to expand...
Click to collapse
I actually JUST fixed my phone haha but yeah there are a few local mobile phone stores here (like Phone House) where they sell discounted phones. I appreciate all the help and thank you so much for everything. Above all else, thank you for sticking through with this post
Glad its working!
A couple of weeks ago I bricked my HTC Inspire with the ACE toolkit. I've spent the last couple of weeks trying to get it back. At some point I just kept getting the HTC white screen and/or bootloader. While I thought I had ClockworkMod recovery in place, I don't. I've tried copying a PD98IMG.zip directly to the SD card. And, HBOOT will read the PD98IMG.zip, it just doesn't seem to apply it.
So this is what I have done so far to fix it:
1. Installed full Android SDK. With some special USB drivers, I am able to get Froyo files fastboot flashall & its says boot & system were both written successfully.
2. When I reboot the phone it starts the HTC Recovery. Its says "This application will set your phone to factory new condition. It is designed for AT&T Branded HTC Inspire only. Using it...blah,blah,blah....Hit OK to continue or Cancel to reboot to recovery?".
3. So I click OK and it says Running "gfree -s on -c CWS_0001"....Please wait. It goes thru this and seems to install OK & says Success GFree has returned your device to s-on and CID: CWS_001. Press OK to copy factory image to your SD card and continue the process..." So I let it do that with an OK.
4. At the end of the Factory Reset install, it says "Success Your device is s-on and a factory RUU has been copied to your SD card. Pressing OK will reboot you to HBOOT where you will be prompted to go ahead with the RUU install. Press vol-up when prompted." When I look in the Android window behind this message it says: "cp: can't stat 'data/rom.zip' no such file or directory. Copying complete".
5. If I hit OK, one of 3 things happens: a.) HBOOT is shown b.) HTC white screen stays on or c.) it tries to do the Factory Reset install once more.
This is where I am stuck.
6. No matter what I have been able to continue getting Android-SDK to talk to it with fastboot commands using the special USB drivers.
I feel like I am just missing something on this.
UPDATE
I am able to connect to the device with Droid Explorer.
Please, if anyone can help, I would appreciate it.