Ok, I believe that I have officially soft bricked my phone. I guess for any help to be given I should give a little background.
These are the things that I did to the phone when I got it about 2 months ago:
Unlocked bootloader using steps on HTC dev
Installed Philz Touch CWM
Rooted
Ok, so a few days ago I got a notification that there was a KitKat OTA update available. I knew that because I had a custom recovery installed that I wouldn't be able to let the OTA install by itself. So, I went ahead and downloaded the OTA and tried to flash it via CWM, it didn't work. I reverted to the stock recovery and tried it again, nothing. Then I did something, I can't remember exactly what I did. I think I took the firmware zip out of the OTA and tried to install that using CWM, but it failed because zip was corrupted. After that it will only boot into Hboot. From what I've read it being able to get to Hboot still is a good sign and that it can probably be saved. Does anyone have any ideas on how to get it up and running again? I really appreciate any help that can be given.
--Makertronic
What's the version of the hboot? Upload a photo of the screen if you can, so we can know how to help
Screen Picture
Here's that picture of the screen.
Makertronic said:
Here's that picture of the screen.
Click to expand...
Click to collapse
Here is what you need to do, it will mostly revive your phone (thanks to @TehFlash for writing it and the guys who host the files).
After you get back into your phone again, I recommend you S-OFF your device, and then downgrade to JB HBOOT then run the RUU and then reboot into JB and do the OTA to get to KitKat properly.
in need of some help
i can no longer do this on my own, i've had my phone for about 6 months or so now, and about february i successfully rooted my device. like the OP i got the notice a few days ago for the KK OTA and tried to install it and it obviously didn't work. now i've gotten a new computer since then and don't remember all the programs and files i had/need to install this new rom. i did try downloading a KK .zip and installing it from the philz touch bootloader and that didn't work either, so now my device is soft brcked. my hboot is the same as the OP, i clicked on that link and couldn't really understand what it was saying to do. if someone could dumb it down a bit for me and explain it some in greater detail, it would be heavily appreciated.
YES!!!! Thank you.
Ok everything works perfectly now. Thank you so much. And thanks to TehFlash for the post. Also, @TehFlash what do you mean downgrade to Jellybean Hboot. Do you mean just follow the same steps as before just use the Jellybean Hboot? And do you recommend any good methods for getting s-off?
--Makertronic
Makertronic said:
Ok everything works perfectly now. Thank you so much. And thanks to TehFlash for the post. Also, @TehFlash what do you mean downgrade to Jellybean Hboot. Do you mean just follow the same steps as before just use the Jellybean Hboot? And do you recommend any good methods for getting s-off?
--Makertronic
Click to expand...
Click to collapse
instructions for getting s-off http://forum.xda-developers.com/desire-601/help/how-to-s-off-t2814086/post54103450
if u wanna run the ruu, u need to downgrade to jb hboot with s-off bec the ruu only works with jb. we dont have the KK ruu yet. u r s-on u cant downgrade to jb hboot
Now a new problem.
Ok, I finally got around to following the s-off instructions and it doesn't seem to be working. I am not able to get an ADB connection now that the phone is updated to KitKat. Anyone know what the problem could be? I tried installing new drivers and uninstalling HTC sync like the instructions at http://rumrunner.us/instructions/ says, but still nothing. Any help is appreciated.
--Makertronic
Makertronic said:
Ok, I finally got around to following the s-off instructions and it doesn't seem to be working. I am not able to get an ADB connection now that the phone is updated to KitKat. Anyone know what the problem could be? I tried installing new drivers and uninstalling HTC sync like the instructions at http://rumrunner.us/instructions/ says, ut still nothing. Any help at all is appreciated.
--Makertronic
Click to expand...
Click to collapse
Can you access the recovery menu? Does fastboot recognize the device? Can try setting up drivers on another computer?
What does it say when u type adb devices?
I am able to access the recovery menu, and fastboot sees the phone.
When I do adb devices it gives this output:
Code:
PS C:\Users\Tyler\Documents> adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Disable usb debugging then enable usb debugging
Tried that, still nothing.
--Makertronic
Update adb http://stackoverflow.com/questions/15305725/i-cant-upgrade-from-adb-version-1-0-29 then type adb kill-server then type adb start-server then type adb devices
Related
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
I've heard of several people being successful on 4.03.605.2 with the 3.14.605.5 ControlBear version.
Only other advice I can offer is don't give up, try different wires if you're having trouble, and pay attention to the troubleshooting page if you decide you want back out and try again later. I've S-OFF'ed three Rezounds. The first took 3 days, the second 2 minutes, and the third 30 minutes.
dplane said:
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
Click to expand...
Click to collapse
i did s-off with viper's rom and the .5. i was on global too, don't let it scare you or you will not get it. i couldn't get the timing for the life of me. first two hours was a hassle, then i had to get my other battery(thought i bricked my phone) then i relized that they had a metrnome with the correct timing and it worked the first time. but use a different memory card. all of these things can be found under the s-off instructions.:good:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Thanks for the responses and moral support folks!
Collin, I may have to hit you up for that assistance soon, I'd rather be safe then sorry so I might feel better if I have someone to "hold my hand"
May not get around to it til Sat afternoon or Sunday though.
famouscollin said:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Click to expand...
Click to collapse
I'm working with the same situation as the OP. You posted a link to a second recovery to flash after Amon Ra, I've tried that link and it forces me to request access. Which recovery is it and is there another link or are you able to give me access to that one?
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Sax1031 said:
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Click to expand...
Click to collapse
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
neowisdom1031 said:
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
Click to expand...
Click to collapse
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Sax1031 said:
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Click to expand...
Click to collapse
If you're able to flash back to stock that would be the best place to start for S-OFF
neowisdom1031 said:
If you're able to flash back to stock that would be the best place to start for S-OFF
Click to expand...
Click to collapse
I flashed back to the first ICS RUU.
I think I know why it said permission denied. Because I didn't have actual root access.
At the point of trying the wire trick.
Edit: Achieved S-OFF. Thanks so much guys. Going from 3 days ago of flashing my first rom. To having to relock the device, run the first ICS Ruu, then doing the wire trick. Hell of a learning curve on these things. Thanks everyone for all the help.
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
neowisdom1031 said:
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
Click to expand...
Click to collapse
Fwiw I also was able to go s-off using this ruu and flashing supersu from a temporary amon ra. Not as tough as it thought.
Sent from my ADR6425LVW using xda app-developers app
.
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
michaelbsheldon said:
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
Click to expand...
Click to collapse
It shouldn't matter. ControlBear has its own versions of everything it needs.
Sent from my HTC Rezound using Tapatalk 2
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Izeltokatl said:
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Click to expand...
Click to collapse
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
famouscollin said:
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
Click to expand...
Click to collapse
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Izeltokatl said:
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Click to expand...
Click to collapse
you can try backing up your sd cards and partition them before you start the control bear process, and your sure you have root access correct? via rootchecker, tatanium backup or somethin gand usb degugging checked? if your still having issues look for apophis' thread named "so you need assistance, WE ARE HERE TO HELP" post in that thread im sure he can help you walk thru it..
When I bought my rezound used it had a constant boot loop issue. That's why I got it fairly cheap. I immediayly ran the global ruu hoping it would boot. It still boot looped. I was able to unlock, flash recovery and install newts xxx. I have tried to boot other romsand they give me issues too. Is there any way I can s off in my current configuration because I am pretty confident another ruu from my sd card just won't boot. Has anyone had success being on a custom Rom w global firmware hboot 2.27?
[SOLVED - See Post #9]
Hey everyone,
So, I have some experience with rooting/ROMs, bootloaders and recoveries, all specifically on my HTC Droid Incredible (Yep, the original). But that's long in the tooth these days, and getting rather difficult to stand the slower speeds and all.
I decided to pick up a used phone, in this case an HTC Rezound, to repair and serve as my default. Cracked digitizer, but that's an easy fix, and it works for the moment which is all that matters. Turns out there was one more problem with it - it doesn't boot Android. It gets stuck in a bootloop if you allow it to boot, but it does go to hboot if you boot it up and hold the VOL down key, as expected. I cannot boot into recovery.
I tried flashing the 4.03.605.2 RUU from AndroidPolice - same problem. So, I'm not sure where the issue lies. I'd like to start by just getting the phone back to stock, and booting into Android if anyone can help me. I should be able to do everything properly from there.
I'm not entirely certain if HBOOT is stock - it shows the Android on the skateboard at the bottom - I'm not sure if that's a custom HBOOT or not, and I can't seem to find any specific reference to it. It is LOCKED with S-ON, so, I've been assuming that it hasn't been tampered with too deeply, someone just hosed an upgrade and I'm not sure how to go about getting it fixed.
Any help is deeply appreciated.
- Katie
lolatvincent said:
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
Click to expand...
Click to collapse
This might be able to help you too. You have adb and fastboot on your computer right?
lolatvincent said:
This might be able to help you too. You have adb and fastboot on your computer right?
Click to expand...
Click to collapse
Yes, I do. Thank you, I'll check that out!
Like I was saying, I knew it wasn't bricked, I just didn't know how to go about doing it. I think I get where I need to go with that.
ncc74656m said:
Yes, I do. Thank you, I'll check that out!
Like I was saying, I knew it wasn't bricked, I just didn't know how to go about doing it. I think I get where I need to go with that.
Click to expand...
Click to collapse
Flash a recovery in a zip right after you finish the ruu using the same method (no need for reboot).
To get root again you might want this: downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
lolatvincent said:
Flash a recovery in a zip right after you finish the ruu using the same method (no need for reboot).
To get root again you might want this: downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
Click to expand...
Click to collapse
Ok, no such luck. I did the RUU flash and then tried rebooting, no go, tried reflashing from my SD after that, nothing. I'm not sure what to do now. :/
Update
Small update - I did the HTC bootloader unlock and successfully got Amon Ra flashed onto it. Now working on getting Android to boot. *sigh* This thing is a serious pain in the... :angel:
If I get it to work, I'll be sacrificing a ram, or at least some RAM. :fingers-crossed:
Still, I'm open to any suggestions or help anyone can offer. Thank you!
I would make a nandroid now and keep it as is for a bit just to make sure it functions okay.
Then if all is good flash a ROM!
I'm running ViperRez and it's very good. Doesn't seem to stream bluetooth media but all else is good. Very nice daily driver. There might be an update coming which will hopefully fix the bt steaming.
feralicious said:
I would make a nandroid now and keep it as is for a bit just to make sure it functions okay.
Then if all is good flash a ROM!
I'm running ViperRez and it's very good. Doesn't seem to stream bluetooth media but all else is good. Very nice daily driver. There might be an update coming which will hopefully fix the bt steaming.
Click to expand...
Click to collapse
Heh, that would be doing things the SMART way. I'm going to do the unofficial CM9 which has BT streaming media, but not phone - sadly, something I'm much more interested in. I am wondering if I can't get the stock ICS or JB on there and just stick with that, since I do like using my BT headset. But since I've had no luck so far getting that to go on there, I think I'll take my chances with CM9 first, and go from there.
If I get that, I'll back it up thoroughly and then try my hand at putting the stock 4.03 on instead.
Solved!
Ok, so, I got CM9 booted!
The short of what I did was the following steps:
1) HTC Dev Bootloader Unlock
2) Installed Amon Ra
3) Installed CM9 using the S-ON instructions found at the site below - I can't link yet, so forgive me.
Code:
http://forum.xda-developers.com/showthread.php?t=1885553
4) Letting the bootloader flash the Kernel failed, so I had to do it manually by following the instructions for S-ON below in case of a parsing failure:
Code:
http://www.androidauthority.com/rezound-android-4-0-4-ics-cyanogenmod-9-cm9-rom-unofficial-120696/
5) Boot and done!
ncc74656m said:
Ok, so, I got CM9 booted!
The short of what I did was the following steps:
1) HTC Dev Bootloader Unlock
2) Installed Amon Ra
3) Installed CM9 using the S-ON instructions found at the site below - I can't link yet, so forgive me.
Code:
http://forum.xda-developers.com/showthread.php?t=1885553
4) Letting the bootloader flash the Kernel failed, so I had to do it manually by following the instructions for S-ON below in case of a parsing failure:
Code:
http://www.androidauthority.com/rezound-android-4-0-4-ics-cyanogenmod-9-cm9-rom-unofficial-120696/
5) Boot and done!
Click to expand...
Click to collapse
Oh! I misread your last post above mine and thought you had gotten it back to stock.
Your issue was exactly what you figured out, that when you are s-on you need to flash the kernel separately after flashing a ROM or else you'll get stuck. If you s-off that will be automated but s-off makes it easier to brick your phone. I don't flash often so I'm staying s-on.
Sorry I misread your post, I could've let you know about that.
feralicious said:
Oh! I misread your last post above mine and thought you had gotten it back to stock.
Your issue was exactly what you figured out, that when you are s-on you need to flash the kernel separately after flashing a ROM or else you'll get stuck. If you s-off that will be automated but s-off makes it easier to brick your phone. I don't flash often so I'm staying s-on.
Sorry I misread your post, I could've let you know about that.
Click to expand...
Click to collapse
No worries, it happens, thank you!!!!
My evo is rooted, ive got twrp recovery installed, and i recently tried flashing a rom and its not working for me . i have S-ON and i heard you need S-OFF to flash roms properly. Ive been looking around for a tool to S-OFF my evo on windows(HBOOT 2.09.0000) and i have yet to find one! is there a tool available to do this? if so, is it going to factory reset my device? will i ave to re-root and unclock the boot loader? as you can probably tell, Im new to the whole rooting and rom ing thing. I would like to be able to flash roms, so any help would be appreciated, thanks!
iamstafford said:
My evo is rooted, ive got twrp recovery installed, and i recently tried flashing a rom and its not working for me . i have S-ON and i heard you need S-OFF to flash roms properly. Ive been looking around for a tool to S-OFF my evo on windows(HBOOT 2.09.0000) and i have yet to find one! is there a tool available to do this? if so, is it going to factory reset my device? will i ave to re-root and unclock the boot loader? as you can probably tell, Im new to the whole rooting and rom ing thing. I would like to be able to flash roms, so any help would be appreciated, thanks!
Click to expand...
Click to collapse
Try the method I described in the thread I came up with this morning - if you're comfortable with doing everything. It wasn't too hard to do. I just had to convert the jargon into words I could understand.
Try using the Moonshine method first though! It's easy and straightforward - if it will recognize your device (which it wouldn't recognize mine for some reason).
Here's what I did.
Good luck!
iamstafford said:
My evo is rooted, ive got twrp recovery installed, and i recently tried flashing a rom and its not working for me . i have S-ON and i heard you need S-OFF to flash roms properly. Ive been looking around for a tool to S-OFF my evo on windows(HBOOT 2.09.0000) and i have yet to find one! is there a tool available to do this? if so, is it going to factory reset my device? will i ave to re-root and unclock the boot loader? as you can probably tell, Im new to the whole rooting and rom ing thing. I would like to be able to flash roms, so any help would be appreciated, thanks!
Click to expand...
Click to collapse
Take a look at the link in my sig. It should answer some of your questions.
Sent from my EVO using xda premium
iamstafford said:
My evo is rooted, ive got twrp recovery installed, and i recently tried flashing a rom and its not working for me . i have S-ON and i heard you need S-OFF to flash roms properly. Ive been looking around for a tool to S-OFF my evo on windows(HBOOT 2.09.0000) and i have yet to find one! is there a tool available to do this? if so, is it going to factory reset my device? will i ave to re-root and unclock the boot loader? as you can probably tell, Im new to the whole rooting and rom ing thing. I would like to be able to flash roms, so any help would be appreciated, thanks!
Click to expand...
Click to collapse
A second what venkman21 says, moonshine is the easiest method and works with all versions of Windows. Took me about 7 minutes and I was s-off and loving it. Good luck.
Sent from my EVO using xda app-developers app
SoFaKiNgStOkeD said:
A second what venkman21 says, moonshine is the easiest method and works with all versions of Windows. Took me about 7 minutes and I was s-off and loving it. Good luck.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I tried moonshine. it didnt work! i have usb debugging on, i installed the android sdk tools and yes they are working properly. i am hooked up to a usb 2.0 port. but, whenever i run the program, it says Error ccannot check for updates, and at times it says error, run distiller again and read. any help?
iamstafford said:
I tried moonshine. it didnt work! i have usb debugging on, i installed the android sdk tools and yes they are working properly. i am hooked up to a usb 2.0 port. but, whenever i run the program, it says Error ccannot check for updates, and at times it says error, run distiller again and read. any help?
Click to expand...
Click to collapse
I get the same error messages. For the update one, make sure your firewall and anti-virus are off. That solved mine. For the "Error run distiller again" issue, that's what brought me here. Pleases let me know if you solve this!
iamstafford said:
I tried moonshine. it didnt work! i have usb debugging on, i installed the android sdk tools and yes they are working properly. i am hooked up to a usb 2.0 port. but, whenever i run the program, it says Error ccannot check for updates, and at times it says error, run distiller again and read. any help?
Click to expand...
Click to collapse
I think the "run distiller again and read" part means you pushed some buttons and otherwise touched or maimed your phone while Moonshine is working. I solved my issue. I was unzipping Moonshine to one folder then cutting the visible files out and pasting them to a separate folder. This left behind a hidden file. Solved problem by unzipping directly to my SDK platform tools folder which contains adb.exe and fastboot.exe. Worked first try. I'd already stopped firewalls, turned off anti-virus and tried to switch to usb file sharing during install (which is why I was told to "read". None of those were required this time. Never touched phone even though it was not in correct file sharing mode, and it still worked.
I'm trying to fix my friends phone and basically what he did was he tried rooting it and installing a custom recovery but some how messed up and erased the ROM and the recovery. So now the phone just shows the hboot or fastboot screen and wont boot passed that. Now Im not trying to read to much just to fix his phone. He should be doing this but whatever I said I'd help. Basically Im looking for one of those PG86IMG files with the stock ROM in it. I found one but it said it was older then the one on the phone or something. I think I found HTC's stock ROM that uses the exe to load the ROM to the phone just haven't had time to try it and thats my last idea I have and if that doesnt work ill probably give him back the phone and say I cant do much for it. Also in the Hboot screen it says relocked and s-on. So yeah any help would be greatly appreciated. :fingers-crossed:
Is the phone a CDMA (Sprint) Version or GSM Version?
JnNn98 said:
Is the phone a CDMA (Sprint) Version or GSM Version?
Click to expand...
Click to collapse
It's CDMA. Do you by chance know where I can find a recovery update.zip? So then I could just get a recovery on his phone? But idk if a recovery will help since his hboot is relocked and s-on, but if you can put a recovery on with it locked then I could flash a custom ROM. I think.
I used to have a GSM Evo 3D but I think with steps there aren't huge differences only files. First you absolutely must unlock the bootloader properly. Try to unlock it with the HTC Dev site. If you've done it correctly the bootloader should say "UNLOCKED". You have to be in the bootloader to do this anyway so it shouldn't be a problem. Are you familiar with using the ADB and Fastboot commands?
Yeah I know how to use ADB done it a couple of times but I'm not too familiar with the ADB commands. The problem I had with ADB this time was it could see the device even though I installed drivers. This is my most common problem with ADB once i get it connected then it's cake. That was on a windows PC though. I feel like I have better luck with ADB and fastboot on linux so maybe I'll try that tonight. I didnt try too hard to get ADB working but even if I get it unlocked I still need a recovery. Well i suppose you can push a recovery through adb. Yeah I should probably just get ADB working with it lol.
evily2k said:
Yeah I know how to use ADB done it a couple of times but I'm not too familiar with the ADB commands. The problem I had with ADB this time was it could see the device even though I installed drivers. This is my most common problem with ADB once i get it connected then it's cake. That was on a windows PC though. I feel like I have better luck with ADB and fastboot on linux so maybe I'll try that tonight. I didnt try too hard to get ADB working but even if I get it unlocked I still need a recovery. Well i suppose you can push a recovery through adb. Yeah I should probably just get ADB working with it lol.
Click to expand...
Click to collapse
Sorry for the late reply. And I suppose you meant ADB couldn't see the device lol. TBH ADB in my opinion should be a tool that works every time not a hit-or-miss. (Try checking if you have all the necessary files in the ADB folder, check the Java version etc.) If ADB works you can then UNLOCK the Bootloader. (http://www.htcdev.com/bootloader/) So I've been digging around the CDMA forums and I found this: http://forum.xda-developers.com/showthread.php?t=1239821 With the bootloader unlocked you can just write the recovery onto the phone through ADB (Follow the steps outlined in the guide.) Once that's done I would suggest to Wipe the Data, Cache, and Dalvik cache (If there is anything to wipe lol) in the recovery. With that done you should flash a stock based rom. Like this one: http://forum.xda-developers.com/showthread.php?t=1668918 Hope it works.
JnNn98 said:
Sorry for the late reply. And I suppose you meant ADB couldn't see the device lol. TBH ADB in my opinion should be a tool that works every time not a hit-or-miss. (Try checking if you have all the necessary files in the ADB folder, check the Java version etc.) If ADB works you can then UNLOCK the Bootloader. (http://www.htcdev.com/bootloader/) So I've been digging around the CDMA forums and I found this: http://forum.xda-developers.com/showthread.php?t=1239821 With the bootloader unlocked you can just write the recovery onto the phone through ADB (Follow the steps outlined in the guide.) Once that's done I would suggest to Wipe the Data, Cache, and Dalvik cache (If there is anything to wipe lol) in the recovery. With that done you should flash a stock based rom. Like this one: http://forum.xda-developers.com/showthread.php?t=1668918 Hope it works.
Click to expand...
Click to collapse
Thank you very much for this information! I'm currently at work right now so I cant work on the phone atm but I will give it a try once I get home. Again thank you for responding to my question. I have a good feeling this will do the trick!
No Problem. Just tell me if it works or not. (Hopefully it does)
JnNn98 said:
No Problem. Just tell me if it works or not. (Hopefully it does)
Click to expand...
Click to collapse
Im evily2k's friend who has the phone. I tried the steps for unlocking the bootloader from htc's website and i have succesfully unlocked!
allakazam15 said:
Im evily2k's friend who has the phone. I tried the steps for unlocking the bootloader from htc's website and i have succesfully unlocked!
Click to expand...
Click to collapse
Good good good, just install the recovery and you should be all set. I suggest once you a working ROM to install 4ext Recovery. It's the best one for the 3D.
Hi there. So im a huge noob and could use an experienced persons help. I have this Amaze 4G that i unlocked bootloader for, had running Android 4.3 Evervolv rom and all was well. I then needed to sim unlock and the code didn't work and I read I needed to unroot and flash stock. I'm trying to do just that using Hasoons toolkit but can't get much help since the thread is closed. My HBOOT is 1.93.0002 and I try to do the Mainver Error fix and It says device not found. I definetly have the drivers updated as I had to go through all that just to have my device detected in fastboot. I wan't to flash stock Telus RUU. Can anyone please help me?
-Note I also accidentally relocked bootloader without downgrading or unrooting. I quickly unlocked it again, but my device was wiped so I can't boot into any rom. I only have 4EXT recovery and bootloader/fastboot available. I am S-on. Can anyone point me or describe a step by step process to get unrooted or and flashed to stock telus? I will gladly donate $$ for any helpful info as well!
butthurtlocker said:
Hi there. So im a huge noob and could use an experienced persons help. I have this Amaze 4G that i unlocked bootloader for, had running Android 4.3 Evervolv rom and all was well. I then needed to sim unlock and the code didn't work and I read I needed to unroot and flash stock. I'm trying to do just that using Hasoons toolkit but can't get much help since the thread is closed. My HBOOT is 1.93.0002 and I try to do the Mainver Error fix and It says device not found. I definetly have the drivers updated as I had to go through all that just to have my device detected in fastboot. I wan't to flash stock Telus RUU. Can anyone please help me?
-Note I also accidentally relocked bootloader without downgrading or unrooting. I quickly unlocked it again, but my device was wiped so I can't boot into any rom. I only have 4EXT recovery and bootloader/fastboot available. I am S-on. Can anyone point me or describe a step by step process to get unrooted or and flashed to stock telus? I will gladly donate $$ for any helpful info as well!
Click to expand...
Click to collapse
First let's take things one step at a time. If s-on you should still be able to run any of the source built AOSP ROMs like evervolv, PAC, or CM. So if you want to get your handset up and running all you need to do is just push one into your SD card either in recovery or with an adaptor on your PC. Just download one of them to your PC. If you have adb working on it when you enable usb debugging in recovery you'll have access to both your internal SD partition and your SD card. Then just copy the zip to one of them. Then turn off the usb and flash the ROM as usual. Once your phone is back up and running you can read the threads to find out what you need to do the other things you want on your device.
I hope this helps
Ciao
Odysseus1962 said:
First let's take things one step at a time. If s-on you should still be able to run any of the source built AOSP ROMs like evervolv, PAC, or CM. So if you want to get your handset up and running all you need to do is just push one into your SD card either in recovery or with an adaptor on your PC. Just download one of them to your PC. If you have adb working on it when you enable usb debugging in recovery you'll have access to both your internal SD partition and your SD card. Then just copy the zip to one of them. Then turn off the usb and flash the ROM as usual. Once your phone is back up and running you can read the threads to find out what you need to do the other things you want on your device.
I hope this helps
Ciao
Click to expand...
Click to collapse
Thanks for the reply man! That's the thing i have a few issues. First off i can't mount storage via 4ext recovery it always just says failed. I also have no SD card to load a ROM onto. And even when i was up and running i couldn't unroot. I have the toolkit and every guide says to hit mainever fix but my device was never recognized even though i have all the drivers
In recovery format your internal SD then reboot back into recovery. This should allow you to at least be able to mount it. It's file system probably got corrupted while you were monkeying around. Then follow the instructions I posted above. This should at least get you back up and running. For the other procedures you're going to need an external SD card, because you won't be able to flash the factory image from your internal storage unless you're familiar with adb. I don't believe you can do the mainver fix until after s-off, but I'm not 100% on that since I'm s-on and never tried it. Once you're back up and running then we'll try to proceed with the other steps.
This isnt a big problem man if you have recovery you can doo any thing and do as odysseus says
Sent from my HTC_Amaze_4G using Tapatalk