I need to return a rezound to stock. I purchased it @ retail but have since gotten one via craigs list for nearly half price.
I was running an ICS rom.
First attempts with using RUU in windows resulted in ruu not seeing the phone via USB. The phone was locked @ the time and in fastboot usb mode.
I have tried many of the threads doing things like setting mainversion low etc.. still wont detect the phone . Tried pulling the zip and doing it from hboot but it says hboot mainversion is older.
Im sort of lost and on my last day here. I am currently on cleanrom so it looks kinda like stock, I realize it will still says relocked but i dont want anything else out of place if possible...
Flash the newest ICS CleanRom, Scott has it in his rom to get you back to mainver 1.00.000.00. This will allow you to pull the zip and do it from hboot. But make sure you using the right RUU. If you have hboot 2.11 you have to run RUU 2.01.xxx.xx.
Ok flashed to the latest, now as far as the ruu zip.. im in linux so i cant just grab them from the windows temp folder i have been dl them..
if using the downloads from scotts do i need to do both the smaller 3.xmb one and the larger472.xmb one? do this after re-locking correct?
UPDATE SOLVED
This issue was the ruu file there was the older one once i searched out the new one by name and found it all is well.
Thanks for the clear concise answer EmerikL
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
gjash said:
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
Click to expand...
Click to collapse
Hey man the phone isn't bricked if you have a pulsating dim red power light, alot of people came across the problem of actually killing batteries trying to brick their phones. If its pulsating just leave it charging on the wall socked for a while bit if it is a very very dim constant red light it is bricked and you would have to use a compatible computer that takes the drivers for your phone. Read through the thread you linked and search for your issue, it is a common one
****'ll Buff Out
gjash said:
I was attempting to downgrade my hboot 1.50 to hboot 1.40 and followed directions here here. I intentionally bricked it and believe I did that correctly. I'm in Japan and downloaded the RUU for my phone and extracted the ROM from it. Everything was fine and I believe it was bricked according to directions, but the phone is not recognized when I connect to my linux machine or any machine. It's just totally bricked. At this point, could anyone point me to some tools or tips so I can attempt to unbrick it? It's a great phone and I'd like to revive it. Thanks!
gjash
Click to expand...
Click to collapse
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
closeone said:
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
Click to expand...
Click to collapse
Thanks, it's just dead as can be. I did eventually get it recognized by linux on the live cd and it successfully went through it's routine to get to hboot 1.40. The next step should be to install RUU 1.13. It's a KDDI phone. I used this
RUU_Shooter_K_S_KDDI_JP_1.11.970.2_Radio_1.02.00.0906_NV_1.39_01C_release_246058_signed.exe
for initially bricking it. I extracted the ROM first. That part went smoothly . I think I did everything right and i'm where i should be now but it just doesn't do anything... nothing. I did try to mess with emmc_recover but no luck yet. When I do the RUU I just keep getting "error 170 usb connection error." I've tried uninstalling/re-installing/different versions of HTC drivers. I keep messing with it for a bit and hopefully something gives! Oh and battery, no battery, I can't get anything. If I could get it recognized on the PC I think I'd have a shot! Thanks again,
gjash
runcool said:
The evo3d was designed for americans. We don't support the Japan people do to over population of your race. Also if you used your head you'd notice that the computer you're using likely is in the crappy Japan language no one uses. Therefore, you need to try another computer and it'll work. We can't support every computer out there. The Drivers won't work for every type of computer on the planet.
To make this racist reply short, it's your computer. you gotta try another computer. Try using an older system. I'll have to open it up to figure out which drivers they put in there, but I know for a fact it won't work on my computer. I'd have to use it on another as well.
They should put that in the instructions. hmmm But after trying another computer, get back with us.
ps again, you said you "tried it on other computers" model numbers of those and what language are they in? It does make a difference. But I'm glad you speak english or I'd just laugh. I'm really mean today. so sorry. hahaha. Let me know if I'm right.
ps again. remember drivers drivers and drivers. drivers only work with certain types of hardware.
edit, you said linux machine, BUT DID YOU EVEN INSTALL the drivers on it? lmao!?
Click to expand...
Click to collapse
Your a complete douche bag! Its people like you that drag society down! If I met you in person I would ***** SLAP you so hard it would not be funny!
The last I checked we all bleed red.
@op I am glad you got it worked out unfortunately I can not help because I have no idea who your carrier is. What I do know is if you update to ruu 2.17.651.5 you will be back on Hboot 1.5 but with S-off.
Sorry that is all the info I can give you.
@gjash,
Sorry for the poor manners of some users here.
I thought the hboot 1.50 downgrade was just for EVO3D Cdma phones on Sprint USA, unless I missed something. Your phone/carrier has the same bootloader?
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
@gjash,
Sorry for the poor manners of some users here.
I thought the hboot 1.50 downgrade was just for EVO3D Cdma phones on Sprint USA, unless I missed something. Your phone/carrier has the same bootloader?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Hi, yeah it's an EVO 3d Cdma. It's the same as the Sprint one. I should be able to get up and going but there really seems to be a lack of resources, a wiki or anything. I guess I just haven't found where it's hiding. I kinda put it off to the side, but I hope to revive it one day. Do you know the purpose of flashing RUU 1.13 after overwriting the hboot? I'm at that point now and I'm looking for another route to where I wanna go. Thanks!!
gjash
gjash said:
Hi, yeah it's an EVO 3d Cdma. It's the same as the Sprint one. I should be able to get up and going but there really seems to be a lack of resources, a wiki or anything. I guess I just haven't found where it's hiding. I kinda put it off to the side, but I hope to revive it one day. Do you know the purpose of flashing RUU 1.13 after overwriting the hboot? I'm at that point now and I'm looking for another route to where I wanna go. Thanks!!
gjash
Click to expand...
Click to collapse
After downgrading/flashing Hboot 1.40, the goal of the RUU is to install an earlier fully working Stock Rom (S-On still) that came with the same Hboot 1.40 that is pushed to the phone with the downgrade tool/process. Hopefully you can find an early KDDI ruu with Hboot 1.40 for this part. This allows you to run " http://Revolutionary.io 's rooting/S-Off tool to gain "S-Off" and install a custom Recovery like Revolutionary CWM Recovery 4.0.1.4 (or 4Ext Recovery).
From there (make a nandroid backup) you can update the firmware/radio if needed (make sure hboot 1.50 isn't included) and flash a current rooted rom (stock or custom) that matches your radio/baseband as appropriate. Maybe there is a current rooted stock KDDI RUU (PG86IMG.zip) without the hboot 1.50 or someone (like Mr.Esp, freeza, or xhausx) can help you pull the stock rom apart for this step.
You can also flash the SuperUser zip (app & binary) from custom recovery to gain root on a currently installed stock rom once you have S-Off.
That's my LIMITED understanding, but I'm not 100% sure about your situation overseas since I thought all foreign carriers outside the U.S. used GSM devices.
closeone said:
Hi there gjash. I'm sorry for the way some people are acting here. May I ask who your cell phone carrier is? Is it KDDI, or do you have a Sprint phone? Can you also link to the RUUs that you used for the phone?
Please let me know anything you can tell me about the phone. Don't post any numbers. Was your HBOOT version 1.50 before?
Also, if you put the battery back into the phone, does it power on at all? If it does, it's not bricked.
~co~
Click to expand...
Click to collapse
Well, I've gotten to the step where I need need to install RUU 1.13. I'm hoping it would take that, but I keep getting an "Error 170 USB connection error" The phone is identical to the sprint one. I believe! I have no lights or anything. Seems dead. Thanks for any help!
gjash
Can't really do anything at the moment. I can't flash RUU 1.13 and I can't get it to be recognized on USB so I could use ADB and try pushing something to it. I have no idea! This is a learning thing at this point. I did root my Asus transformer before though! Thanks for any help!
gjash
gjash said:
Well, I've gotten to the step where I need need to install RUU 1.13. I'm hoping it would take that, but I keep getting an "Error 170 USB connection error" The phone is identical to the sprint one. I believe! I have no lights or anything. Seems dead. Thanks for any help!
gjash
Click to expand...
Click to collapse
First, I think your phone needs to be booted to the new bootloader and in "Fastboot USB" mode displayed on it for the .exe to work.
I am also willing to bet that this is where you need to run the earlier KDDI ruu.exe file that had hboot 1.40 included...
I'm not sure, but "RUU_Shooter_K_S_KDDI_JP_1.09.970.5_Radio_1.02.00.0906_NV_1.39_01C" is an earlier version than the one you bricked with in your previous post. It's listed in Football's CDMA Stock Rom Collection thread, but I don't know which Hboot is included in it.
Closeone or Unknownforce posted in their thread recently about starting the .exe and right before the flash running %temp% in "run" command or something to find the "ROM.zip" that the exe flashes to the phone (this is what gets named to PG86IMG.zip & manually flashed in bootloader sometimes).
- once you have the .zip, you can open it up with 7zip or similar and see what Hboot version is in there (see attached example).
Edit: Here is the post:
closeone said:
But take the RUU .EXE that you upgraded your phone with already and grab the ROM out of there.
To get to your temp directory: press the Windows key and R on your keyboard at the same time. Type in this exactly: %temp%
Rename the rom.zip to PG86IMG.zip and put it on your SD card.
Click to expand...
Click to collapse
I haven't made any progress. I'm assuming I need to use emmc_recover to overwrite the boot partition and maybe the misc partition. So can someone help me figure out identifying the partition, how I can get linux to recognize the device so I have a chance to recover? Also, at this point I settle for anything working, any Hboot, whatever... It would be nice if I could post in the original thread, hmmmm. moderator, can you help there?
thanks,
gjash
Keep an eye on Unknownforce's thread, starting at Post 1912. Looks like ZiT777 is in the same situation and able to provide info to Unknownforce about your phone's hardware.
mpgrimm2 said:
First, I think your phone needs to be booted to the new bootloader and in "Fastboot USB" mode displayed on it for the .exe to work.
I am also willing to bet that this is where you need to run the earlier KDDI ruu.exe file that had hboot 1.40 included...
I'm not sure, but "RUU_Shooter_K_S_KDDI_JP_1.09.970.5_Radio_1.02.00.0906_NV_1.39_01C" is an earlier version than the one you bricked with in your previous post. It's listed in Football's CDMA Stock Rom Collection thread, but I don't know which Hboot is included in it.
Closeone or Unknownforce posted in their thread recently about starting the .exe and right before the flash running %temp% in "run" command or something to find the "ROM.zip" that the exe flashes to the phone (this is what gets named to PG86IMG.zip & manually flashed in bootloader sometimes).
- once you have the .zip, you can open it up with 7zip or similar and see what Hboot version is in there (see attached example).
Edit: Here is the post:
Click to expand...
Click to collapse
You are right... both KDDI 1.09 and 1.11 have Hboot 1.50. I guess the trying Sprint 1.13 wouldn't be an option? That's the question and I can't really find out as the KDDI ones and the Sprint ones don't work because I always get USB 170 connection errors. So kinda stuck, but greatly appreciate the help!
gjash
mpgrimm2 said:
Keep an eye on Unknownforce's thread, starting at Post 1912. Looks like ZiT777 is in the same situation and able to provide info to Unknownforce about your phone's hardware.
Click to expand...
Click to collapse
I will start looking there... I was thinking that the KDDI Evo 3d is CDMA and it would have the same partition layout. I'd like to determine that and go from there. Can someone explain the sprint evo 3d partition layout? thanks!
gjash
I'm willing to mess with this phone so if any developers have something I can do, please let me know. Otherwise, I just try to get back to stock.
I extracted original hboot from latest KDDI RUU and renamed it hboot.img and then executed 'downgrade'
I got this error:
Waiting for device...
Found the Correct Device!
Writing image file!
dd: opening `/dev/sdf34': Permission denied
FAILED!!
Any ideas? Thanks!
gjash
I've got nothing on that error (may need to be named hboot_1.4.nb0 ), but if I recall correctly, the earlier version of the downgrade tool had the option in it to manually change misc_version to an earlier one so that you could flash an RUU. I think Closeone's LiveCD v3.4 had it.
mpgrimm2 said:
I've got nothing on that error (may need to be named hboot_1.4.nb0 ), but if I recall correctly, the earlier version of the downgrade tool had the option in it to manually change misc_version to an earlier one so that you could flash an RUU. I think Closeone's LiveCD v3.4 had it.
Click to expand...
Click to collapse
Getting closer I think... I just needed to do a sudo ./downgrade and it flashed fine. Now I have a red light on which is more than I had before. I will go to windows now and try to flash the KDDI RUU. thanks for the help.
gjash
Update:
I'm back up where I started. I used Unknownforce's hboot downgrade but renamed the original hboot from the KDDI RUU to hboot.img, according to Unknownforce's direction (thanks!). After I did that, the phone just booted up normally. I thought I would have to flash the RUU but wasn't necessary. I think with some changes this whole exploit could work with the japanese cdma version of the Evo 3D. If anyone can outline what I'd need to do, it might be fun. especially that I already ordered another phone, but I won't actually need it.
gjash
Does your device happen to be the KDDI ISW12HT?
(I assume it is from what you've said)
Do you know the exact model you have?
The current CDMA models that I'm aware of are the:
X515c: CDMA800, CDMA1900, ESMR800, WiMAX 2.5-2.7GHz (the sprint one)
X515d: CDMA800, CDMA1900 (I forget)
X515e: CDMA900, CDMA2100 (the HTC rider)
The ISW12HT is listed as having CDMA800, CDMA2100, which arnt any of those 3.
Do you happen to know what submodel you have? I have no idea how to check as I've never touched one.
I'm wondering if it's the X515b or a yet unknown one (by unknown I mean with regards to the model number)
I've already listed all the common and less-common models on the wiki: HTC Evo 3D - XDA wiki.
But I have no idea what the ISW12HT's model is, and a fair amount of googling turns up little.
If you could poke around your device/box/manual and find it I'd appreciate it
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
wards.jfasa said:
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
Click to expand...
Click to collapse
im going to say a bad ruu re unlock and start over i dont know if its on xda too but on scotts roms site it has info to lock without the re locked showing good luck
I am having the same problem, but I found a way around it. If I boot the kernel through fastboot it will boot up. (You'd need to re unlock). My hboot doesn't really work anymore..
------
3(d)vo one s
Newts my hero.
evo bryan said:
im going to say a bad ruu re unlock and start over i dont know if its on xda too but on scotts roms site it has info to lock without the re locked showing good luck
Click to expand...
Click to collapse
Im not even sure at this point how to re-unlock it. i am wondering if i should have flashed to an older ruu though.
How do I extract the kernel from the ruu? or is there a download available? I have searched....just cannot find it.
wards.jfasa said:
How do I extract the kernel from the ruu? or is there a download available? I have searched....just cannot find it.
Click to expand...
Click to collapse
flashimage gui is able to do it inside android, im guessing it stores it in a tempory folder, let me see if i can find the temp folder where it stores before rebooting to flash it...........brb
did you check this post http://forum.xda-developers.com/showthread.php?t=1627897
This helped me out when I was Juopunutbear S-OFF'ing my phone. But I was at Hboot 1.50.
http://androidforums.com/evo-3d-all...mware-upgrade-ruu-flash-unbricking-guide.html
Pretty good guide.
wards.jfasa said:
Hi Guys,
I feel strange, in that I have been rooting phones since the g1 (and literally every other android device on tmobile & sprint since then) and I've never run into this:
I was running Eternity rom, but wanted to send the device in for a warranty repair, so I followed the available instructions to take my Evo3d back to stock. Everything seemed to go fine, except that now the phone will ONLY boot into the bootloader.
I did re-lock the bootloader as per the instructions here on xda, so now at the top of the screen i get:
Relocked
Security Warning!
and S-On ( i was never s-off)
Does anyone know of a way to get me back up and running? Btw, it was the PG86IMG.zip ruu 2.17 u flashed.
Im in a big jam here now...no phone for work purposes
Click to expand...
Click to collapse
The security warning is because you are using a custom rom so will not be able to use the RUU through the bootloader.
What you need to do is download the RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00. 1216_signed.exe from here
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209
If you then run that exe while your phone is in fastboot and connected to your pc it will factory reset your phone and put you back on stock rom and kernel.
Hi all,
I was hoping for a little help. I got my phone last summer on At&t and immediately converted the Developer's Edition. The phone is currently rooted,
has s-off and is on a KitKat Rom.
The above said, would I be able to get back to stock? I've Googled it and can only find instructions on Stock to Developer's, not the other way around.
TIA
infg3570
infg3570 said:
Hi all,
I was hoping for a little help. I got my phone last summer on At&t and immediately converted the Developer's Edition. The phone is currently rooted,
has s-off and is on a KitKat Rom.
The above said, would I be able to get back to stock? I've Googled it and can only find instructions on Stock to Developer's, not the other way around.
TIA
infg3570
Click to expand...
Click to collapse
did you s-off ? did you change your CID ?
just change your CID back to AT&T
fastboot oem writecid CWS__001
and flash the AT&T RUU
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
did you s-off ? did you change your CID ?
just change your CID back to AT&T
fastboot oem writecid CWS__001
and flash the AT&T RUU
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
Thank you! All though I have email notification set up for replies, I never received one. Interesting is that my CID remains the At&t and i currently have s-off. When I RUU.exe (I downloaded the same the other night), I get an error and it restarts my phone. I'm wondering if it's because I have a KitKat Rom already installed and the software number is slightly higher than the RUU? The software number is 4.18.502.7 (my phone). I think the RUU is 502.1.
Thanks again,
infg3570
infg3570 said:
Thank you! All though I have email notification set up for replies, I never received one. Interesting is that my CID remains the At&t and i currently have s-off. When I RUU.exe (I downloaded the same the other night), I get an error and it restarts my phone. I'm wondering if it's because I have a KitKat Rom already installed and the software number is slightly higher than the RUU? The software number is 4.18.502.7 (my phone). I think the RUU is 502.1.
Thanks again,
infg3570
Click to expand...
Click to collapse
If your s-off use my decrypted RUU here
http://www.androidfilehost.com/?fid=23329332407580500
instructions are here
http://forum.xda-developers.com/showthread.php?t=2695749
clsA said:
If your s-off use my decrypted RUU here
http://www.androidfilehost.com/?fid=23329332407580500
instructions are here
http://forum.xda-developers.com/showthread.php?t=2695749
Click to expand...
Click to collapse
I tried as you have suggested your decrypted file. Unfortunately, I get an error when trying to run it via ADB in fastboot.
I've rooted when I first got the phone last summer using Revone method/tool. All worked fine and i had continued updating the OS a few times with stock rooted phones.
The last that i updated to was a stock rooted odex kitkat ROM found here http://forum.xda-developers.com/showthread.php?t=2676986
Only thing that seemed wrong was that I couldn't reinstall any of my apps requiring root. The error that would pop up is "Could not install to SD card".
Now, I have to say that I noticed that with some updates, it seems that new ROMS don't clean up the old files/framework even after fully wipes. It seems to back it up in some folders (sdcard0, sdcard00, sdcard000 etc). All though the sdcard folder seems clean and refreshed, the others mentioned had all my old files in there. Since I've updated to kitkat, I can no longer view these folders (I used to use Root Explorer, but now since the kitkat install - I can't). What caused me to notice was the fact that my storage, in the 'Other:' section, shows 20GB out of 32. So, I used ES File Mgr to see if I can create some space by deleting the so-called backup folders. I think that was a bad mistake because now, even after a full data wipe, I still can't:
* Install root-required apps
* flash the zip file you provided
* use the exe version of the zip you provided (still get an error with that as well)
* Clear the 20gb of data I don't need
* get back to the At&t carrier brand from the Developer's Edition that i switched it to back last summer.
Fortunately the phone works fine, but is this hopeless? Anything I can do to get this going again (really thing I messed things up)
Is there anything else I can try?
thank you,
infg3570