Related
Hi. I'm trying to find out how to fix this for the last few days, but so far without success. After flashing Android Revolution HD 6.0.3 from this thread http://forum.xda-developers.com/show...42&postcount=4, my hboot became locked. I didn't think it would be much of a problem, because I read that I can still flash ROMs, but then I saw this message:
"With 6.0.x ROMs I strongly recommend flashing 11.65.3504.00U_11.19.3504.29_2 radio
--- Don't flash RADIO from ClockworkMod recovery! Extract downloaded file and read the guide inside! ---"
I downloaded the file, read the instructions, but it's not letting me flash the radio since it's locked.
So how can I unlock the bootloader again, without messing sth else up?
I'm sorry if somebody answered similar question already.
Thanks in advance.
tx3m said:
Hi. I'm trying to find out how to fix this for the last few days, but so far without success. After flashing Android Revolution HD 6.0.3 from this thread http://forum.xda-developers.com/show...42&postcount=4, my hboot became locked. I didn't think it would be much of a problem, because I read that I can still flash ROMs, but then I saw this message:
"With 6.0.x ROMs I strongly recommend flashing 11.65.3504.00U_11.19.3504.29_2 radio
--- Don't flash RADIO from ClockworkMod recovery! Extract downloaded file and read the guide inside! ---"
I downloaded the file, read the instructions, but it's not letting me flash the radio since it's locked.
So how can I unlock the bootloader again, without messing sth else up?
I'm sorry if somebody answered similar question already.
Thanks in advance.
Click to expand...
Click to collapse
You are probably on HBOOT 1.23?
If you're using fastboot, it wont work (nothing should be locked as long as your phone still says S-OFF)
Copy the PG58IMG.ZIP to your sd card root, and reboot into bootloader, and simply follow the instructions.
Make sure you delete the file asap or it will keep trying to reinstall .
mrew42 said:
You are probably on HBOOT 1.23?
If you're using fastboot, it wont work (nothing should be locked as long as your phone still says S-OFF)
Copy the PG58IMG.ZIP to your sd card root, and reboot into bootloader, and simply follow the instructions.
Make sure you delete the file asap or it will keep trying to reinstall .
Click to expand...
Click to collapse
Yep I am on hboot 1.23. When you download the recommended radio, it's in an archive named Radio_11.65.3504.00U_11.19.3504.29_2.rar . It contains instruction, adb files, and a file named radio.img . So do I just create an archive named PG58IMG.ZIP, containing only the radio.img file, or there is something else?
And the other thing is that it will be best if I can unlock the bootloader again, because I just found out that I'm not able to flash new splash screen too. I guess that there will be many more things that wont work.
tx3m said:
Yep I am on hboot 1.23. When you download the recommended radio, it's in an archive named Radio_11.65.3504.00U_11.19.3504.29_2.rar . It contains instruction, adb files, and a file named radio.img . So do I just create an archive named PG58IMG.ZIP, containing only the radio.img file, or there is something else?
And the other thing is that it will be best if I can unlock the bootloader again, because I just found out that I'm not able to flash new splash screen too. I guess that there will be many more things that wont work.
Click to expand...
Click to collapse
The bootloader will ignore the extraneous stuff so you could just rename as PG58IMG.RAR and that should work.
Also, even though your Bootloader screen says *** LOCKED ***, as long as you have S-OFF, all you have lost is some of the fastboot commands.
Job done
mrew42 said:
The bootloader will ignore the extraneous stuff so you could just rename as PG58IMG.RAR and that should work.
Also, even though your Bootloader screen says *** LOCKED ***, as long as you have S-OFF, all you have lost is some of the fastboot commands.
Job done
Click to expand...
Click to collapse
I just tried what you said, but I got a message saying: "No image or wrong image found", or something similar to that.
Other ways to flash the radio?
Get your desired radio image from http://forum.xda-developers.com/showthread.php?t=1178143, it's already in the appropriate zip file.
Sent from my HTC Sensation XE with Beats Audio using XDA App
tx3m said:
"With 6.0.x ROMs I strongly recommend flashing 11.65.3504.00U_11.19.3504.29_2 radio"
Click to expand...
Click to collapse
I suppose you flashed the 3.12 firmware. That firmware has the 11.65 radio included
Sent from my Kindle Fire using Tapatalk
ar4l said:
I suppose you flashed the 3.12 firmware. That firmware has the 11.65 radio included
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Well, not really. At least not in my case. My radio version is 11.21....(that's what it shows in the bootloader menu). So I need to find a way to flash the radio. I hope that this could prolong my battery life, because right now with light/medium use, I'm able to use the phone for about 8-10 hours, before the battery is dead, which I find absolutely unsatisfactory.
So if anybody knows how I can unlock the hboot 1.23, or flash the radio I need, that would be awesome )
Hi guys!
Sorry another n00b question but just wanted to make sure...
So I am one of those that got tired to waiting for the OTA and finally decided, at least for now, to try one of the ICS ROMs. I've done some on GB so I'm vaguely familiar with flashing and all that but since it's my first time with ICS I'd like to ask you experts out there.
Basically I just want to make sure that if/when TMo finally pushes out the "official OTA", I can give that a try also. I guess my fear is that I've been reading how it's difficult...or impossible?...to go back to stock since I have to flash my firmware.
Can you go back to 100% Stock TMo GB from ICS?
I currently have already S-Off, root (superuser), and S Cid to 11111111 in preparation. I figure while I wait for TMo, at the very least, I can run my phone rooted to let apps like AutoKiller Memory help my phone run better. I also did a backup using 4EXT.
My next step is to take the plunge but before I do, I'd like to know that I can go 100% back. I've done it with GB ROMs but wasn't sure about ICS because of the whole firmware thing.
Can someone LMK if it should be no problem? Much appreciated for guiding a n00b like me! You guys are awesome!!!
It's not hard...
http://forum.xda-developers.com/showpost.php?p=21989089&postcount=2
This is how I do it:
1. Place firmware on root of sdcard.
2. Use 4ext recovery control to reboot to recovery (power menu).
3. Restore my stock nand from 4ext recovery.
4. Use 4ext recovery to reboot into bootloader (power menu).
5. Select "bootloader" from fastboot menu and let hboot detect the firmware. (volume up for "yes")
6. Let it complete and press power to reboot when prompted...
All my roms, nands, firmwares, radios, etc... are backed up on my sdcard. As long as I've got a good charge on the battery I can go back and forth between BG and ICS multiple times without ever connecting to a PC or pulling my battery...
If you don't have a nand of your stock rom then just flash the 1.50.531.1RUU... And restore your CID.
Thanks for the info GROGG88! So this will restore my firmware too? So basically using the RUU should get me back to full stock including the firmware? Or do I need to downgrade the firmware manually first?
Also noticed that in the link you gave, it has Hboot 1.17. Does it matter that my original is 1.18?
Again apologies for new n00b questions! Thanks for all your help!!!
If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
It really depends on whether or not you backed up an unmodified version of your stock GB...
I'm going to post download links for the 1.50.531.1 RUU and a PG58IMG.zip version of it in the General section. You can use the PG58IMG.zip to restore individual components by extracting the files, removing whatever you don't want, and archiving the files you do want back into a zip...
GROGG88 said:
If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
It really depends on whether or not you backed up an unmodified version of your stock GB...
I'm going to post download links for the 1.50.531.1 RUU and a PG58IMG.zip version of it in the General section. You can use the PG58IMG.zip to restore individual components by extracting the files, removing whatever you don't want, and archiving the files you do want back into a zip...
Click to expand...
Click to collapse
Thanks again GROGG!!!
GROGG88 said:
If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
It really depends on whether or not you backed up an unmodified version of your stock GB...
I'm going to post download links for the 1.50.531.1 RUU and a PG58IMG.zip version of it in the General section. You can use the PG58IMG.zip to restore individual components by extracting the files, removing whatever you don't want, and archiving the files you do want back into a zip...
Click to expand...
Click to collapse
Can you LMK when you post those files as well as the link! Much appreciated!!!
Files can be found here: http://forum.xda-developers.com/showpost.php?p=25561199&postcount=1
GROGG88 said:
Files can be found here: http://forum.xda-developers.com/showpost.php?p=25561199&postcount=1
Click to expand...
Click to collapse
Thanks GROGG88!
Also wanted to ask...I know you mentioned that after the procedures I will have everything stock but still with S-Off. Do you know if I can receive OTA with S-Off or will I have to adb and make it S-On again making the phone COMPLETELY stock.
Thanks again for all your help! I might have to follow these procedures sooner than I thought with the latest announcement about the OTA ICS!
GROGG88 said:
If you go by the guide in the link I posted then you'll be able to restore a stock nand if you have one. After that you can flash 1.18 hboot and stock recovery.
The easiest way would be to flash the RUU which will put EVERYTHING back to stock including firmware, but you'll keep s-off (which is good).
Sorry another related question...why is it good to keep s-off? Advantage?
Sorry again for all the questions! Hoping to expand my knowledge!
Click to expand...
Click to collapse
You can use the OTA with s-off. You want to keep s-off so that you can flash a custom recovery and re-root after the update. You can s-off the new bootloader, but it involves a new procedure that involves jumping a wire from a terminal to ground that many are not comfortable with.
It is much better to keep s-off...
GROGG88 said:
You can use the OTA with s-off. You want to keep s-off so that you can flash a custom recovery and re-root after the update. You can s-off the new bootloader, but it involves a new procedure that involves jumping a wire from a terminal to ground that many are not comfortable with.
It is much better to keep s-off...
Click to expand...
Click to collapse
Good to know! Thanks! So the new procedure requires you to do something physical to your phone? That sounds just wrong...I guess they really don't want s-off, huh?
I'll definitely keep s-off so I won't have to jump through these hoops!!!
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
shgadwa said:
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
Click to expand...
Click to collapse
Just flash the correct one like you flashed the wrong one. The boot loader does not and should not be relocked, it should be unlocked.
shgadwa said:
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
Click to expand...
Click to collapse
is all you flashed, the boot.img or did you flash leedroid too? If you flashed leedroid then do the following:
plug it in to USB while it bootloops type adb reboot recovery
from there you can access your nandroid backup assuming you made one.
if you didn't make a backup then yeah you'll have to flash the 1.85 RUU. To do this, relock the bootloader from adb fastboot oem lock
run the RUU unlock the bootloader then install your recovery and push root files via recovery.
Much easier than having to re-root 1.85 with the new exploit etc.
If he can get to recovery then he can try pushing a ROM to the SD and flashing it first instead of flashing the RUU and all that hassle.
mbh87 said:
If he can get to recovery then he can try pushing a ROM to the SD and flashing it first instead of flashing the RUU and all that hassle.
Click to expand...
Click to collapse
I keep forgetting we have adb through recovery now. Good call. But do we have USB?
Latest TWRP is suppose to have both ADB and USB
You should always back up
Sent from my HTC One XL using Tapatalk 2
kkoshko1 said:
You should always back up
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Amen.
nandroid is always my first step when flashing a ROM
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
mbh87 said:
Latest TWRP is suppose to have both ADB and USB
Click to expand...
Click to collapse
I didn't see any need in backing up because I assumed all would go well and also I don't have any data on here that I want. Lesson learned well though. I will always back up. Now I've gotta get it working...
shgadwa said:
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
Click to expand...
Click to collapse
You should only supercid once, doesn't need to be re done, no matter locked or unlocked. Can you get to fastboot, try to ruu back...I dunno if this helps but that's what I would try
Sent from my HTC One XL using Tapatalk 2
shgadwa said:
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
Click to expand...
Click to collapse
Download your previous Unlock_code.bin and flash the unlock token again. Your CID should still be SuperCID, installing Rooms or RUUs don't change the CID.
kkoshko1 said:
You should only supercid once, doesn't need to be re done, no matter locked or unlocked. Can you get to fastboot, try to ruu back...I dunno if this helps but that's what I would try
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Thats actually why I re-locked. I've read that before installing an ruu, you need to re-lock.
I can get to fastboot. I tried to unlock via fastboot but it quickly timesout. I'm currently downloading 1.85 .exe ruu. I will give that a try as soon as its done downloading unless you guys have a better idea.
rohan32 said:
Download your previous Unlock_code.bin and flash the unlock token again. Your CID should still be SuperCID, installing Rooms or RUUs don't change the CID.
Click to expand...
Click to collapse
Thats a great idea! How do I do that via fastboot? I would assume fastboot flash Unlock_code.bin, but that doesn't work. As far as I know you can only flash .img. Or update .zip. What am I doing wrong?
shgadwa said:
Thats a great idea! How do I do that via fastboot? I would assume fastboot flash Unlock_code.bin, but that doesn't work. As far as I know you can only flash .img. Or update .zip. What am I doing wrong?
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin
gunnyman said:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Thanks! That worked perfectly. Now I just need to find a AT&T boot.img.
Man, this international version is really throwing me off. I wish it was called something entirely different. It'd make it a lot easier. Its technically not the same phone at all anyway. Must be a marketing thing.
Anyways, I need to find a AT&T boot.img. I could get it from here http://forum.xda-developers.com/showthread.php?t=1689824 but I'm not sure if thats AT&T. It does say 1.82 is AT&T but mentions nothing else of 1.85 and 1.88. I am downloading the ruu for 1.85 but thats taking forever.
If anyone has a working 1.85 AT&T boot.img or knows where I can get one (maybe the link I gave is correct?)... please let me know.
Again, thank you for your help!
shgadwa said:
Thanks! That worked perfectly. Now I just need to find a AT&T boot.img.
Man, this international version is really throwing me off. I wish it was called something entirely different. It'd make it a lot easier. Its technically not the same phone at all anyway. Must be a marketing thing.
Anyways, I need to find a AT&T boot.img. I could get it from here http://forum.xda-developers.com/showthread.php?t=1689824 but I'm not sure if thats AT&T. It does say 1.82 is AT&T but mentions nothing else of 1.85 and 1.88. I am downloading the ruu for 1.85 but thats taking forever.
If anyone has a working 1.85 AT&T boot.img or knows where I can get one (maybe the link I gave is correct?)... please let me know.
Again, thank you for your help!
Click to expand...
Click to collapse
Link is correct. Pay attention to the subforum. It specifically says AT&T One X, if that is the section you are in.
Just flash an att rom no need to flash boot.img seperately anymore it gets flashed in recovery. All you had to do to begin with is use fastboot to flash recovery then flash a new rom in recovery.
To stop the bootloop just hold the power button down til the buttons flash when the screen goes black hold the volume down button and it will boot into hboot. It's a safety feature htc built in because of no battery access, and it works no matter where you are at in the boot process.
You can use sick sense its an att build and flashes the boot.img while flashing the rom.
smokin1337 said:
Just flash an att rom no need to flash boot.img seperately anymore it gets flashed in recovery. All you had to do to begin with is use fastboot to flash recovery then flash a new rom in recovery.
To stop the bootloop just hold the power button down til the buttons flash when the screen goes black hold the volume down button and it will boot into hboot. It's a safety feature htc built in because of no battery access, and it works no matter where you are at in the boot process.
You can use sick sense its an att build and flashes the boot.img while flashing the rom.
Click to expand...
Click to collapse
Thank you. I do know how to get into hboot. I flashed boot.img and it is now working!
NVM saw your edit lol...
Hey all. Im currently running 1.85 and im trying to update. I downloaded the 2.20 RUU from HTC, as well as the latest Sync Manager and Drivers. I put the phone in Fastboot USB and go to run the RUU. It starts to update but then randomly fails and I have to recover each time. Any idears?
if your bootloader was unlocked did you run "fastboot oem lock"
DvineLord said:
if your bootloader was unlocked did you run "fastboot oem lock"
Click to expand...
Click to collapse
Yes it is and no I didn't. What is it?
its the only way you will be able to ruu. so run the command then run the ruu.
DvineLord said:
its the only way you will be able to ruu. so run the command then run the ruu.
Click to expand...
Click to collapse
I'm not familiar with how to do that. Is there a tutorial?
fastboot oem lock
run the ruu exe
???
profit
synn21588 said:
I'm not familiar with how to do that. Is there a tutorial?
Click to expand...
Click to collapse
all the resources available to the hox are here http://forum.xda-developers.com/showthread.php?t=1671237
Why on earth would you want to run the 2.20 RUU? It will update the hboot, which plugs the hole by which kernels can be flashed from the recovery. You will need to push the boot.img separately via fastboot every time you flash a ROM (or other alternate methods).
If you just want the stock 2.20 firmware, install the stock pre-rooted 2.20 ROM avaiable from Development. Or a more updated on, since there are stock pre-rooted ROMs available up to 2.42 now. If you want the newer radios, those are posted in Development as well.
redpoint73 said:
Why on earth would you want to run the 2.20 RUU? It will update the hboot, which plugs the hole by which kernels can be flashed from the recovery. You will need to push the boot.img separately via fastboot every time you flash a ROM (or other alternate methods).
If you just want the stock 2.20 firmware, install the stock pre-rooted 2.20 ROM avaiable from Development. Or a more updated on, since there are stock pre-rooted ROMs available up to 2.42 now. If you want the newer radios, those are posted in Development as well.
Click to expand...
Click to collapse
So I can just flash the latest ROMs without updating to the latest firmware? I already unlocked my boot loader and have TWRP installed
synn21588 said:
So I can just flash the latest ROMs without updating to the latest firmware? I already unlocked my boot loader and have TWRP installed
Click to expand...
Click to collapse
Yes. Flash away.
redpoint73 said:
Yes. Flash away.
Click to expand...
Click to collapse
Sweet. Thanks
Help please. I am running Htc one x 2.20 rooted. I Installed a back up of the factory rom of 2.2.0 and relocked the device to use RUU to get it back to stock and i Followed the Program instructions, but it fails and I don't know if it is because I am running the same version or what I need to get it back to stock. I ended up making it say security warning but when i booted back in to the bootloader the security warning is gone.
You run the ruu in fastboot after running "fastboot oem lock"
DvineLord said:
You run the ruu in fastboot after running "fastboot oem lock"
Click to expand...
Click to collapse
Thanks a lot. Also Think fire wall and anti virus program may have had problems as I just thought of that this morning.
Help im new!
Soo i recently got my htc one x on android jelly bean 4.2.2 from at&t and is there a method or easy root method for this version? 4.2.2, with 5.18? I really want to try and root my phone but i know nothing about messing with all these types of files, and i dont want to risk destroying my phone.
Im not sure if there is already a post or something about this and if it is im sorry, these forums are a bit overwhelming and i am new.
I would very much appeircate any help or info on being able to easily root my htc one x 4.2.2, 5.18 at&t white.
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
timmaaa said:
The recent at&t update patched the last exploit for gaining SuperCID in order to unlock the bootloader. Long story short, there's no way for you to root your phone since you took the update. If you had done it before taking the update you'd be fine. You'll have to wait and see if a dev comes up with a new exploit for the new firmware.
Sent from my Evita
Click to expand...
Click to collapse
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
There is a perfectly easy way to unlock your bootloader on the 3.18 software, it isn't a stupid phone, nor is the exploit hard to achieve, hundreds if not thousands of people have done it. It's as simple as entering a few adb/fastboot commands.
You can't root on 5.18 because the update patched the weakness that was exploited in the 3.18 software/firmware. It takes time for devs to crack these things and the update has only just been released. It's not even sure whether the devs will want to spend any time finding a crack for a phone that's relatively old now. This is why you never take an update without first unlocking/rooting, unless you're comfortable with the fact that you won't be able to (it is a well established fact that updates patch exploits).
Sent from my Evita
5.18!to 3.18 ruu
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
brenntard said:
I also took the update unaware I would not be able to root again...
Would it be possible to run the stock 3.18 ruu and then root?
Click to expand...
Click to collapse
Bootloader details please.
Sent from my Evita
timmaaa said:
Bootloader details please.
Sent from my Evita
Click to expand...
Click to collapse
Tampered
Relocked
Evita put ship s-on rl
Hboot-2.18.0000
Radio-1.35a.32.45.27
Opendsp-v33.1.0.45.1128
Emmc-boot
It's weird, I tried using the all in one toolkit and was able to unlock the boot loader, get twrp recovery working and flash supersu. The only problem I ran into was when I opened supersu it said the binaries need to update. The first time I updated them and it was fine then the phone shut off and supersu would always need updated when opened...I downloaded titanium backup and was able to get root access before my phone restarted and I had to update supersu again... It is now relocked, obviously, but easy enough to unlock again using the toolkit
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Yes it says me CID is 11111111. Why would supersu be acting so funny and constantly telling me to update the binaries...supersu seems relatively useless at this point. do i need supersu to flash a custom ROM?
Forever95 said:
Well that sucks because even when i was on 4.1.1 i could not root my stupid phone. There was no easy way to do it on 4.1.1 3.18, and now i cant do crap with this 4.2.2 on 5.18. why would i not be able to root it if other people can root their phones that are on 4.3 and higher like the Htc One.
Click to expand...
Click to collapse
Lack of research. A working root method exists for 3.18, both a "manual" method and two "Toolkits" for those that can't handle the manual method.
Also, you should never never never install an OTA update unless you know what has been patched, changed, etc. Updates frequently will patch existing root exploits, and therefore leaving you in the spot you find yourself in.
Other devices (such as the One) can be rooted with later firmware, simply because that device has more developer interest. It requires the right talented developer(s) putting in the time and effort to find the exploit method. Its still possible on this device with 5.18. All it takes is the right guy and the proper amount of motivation. But as the device is getting older, and devs are moving to other phones, those chances do get more unlikely.
UPDATE!
timmaaa said:
You're in a different category because you had gotten SuperCID in the past I assume. That's the main determining factor in whether you can unlock the bootloader. You should be fine as long as you still have SuperCID.
Code:
fastboot oem readcid
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for the help. i know officially have an s-off device that is unlocked and rooted ready to run custom ROMS.
My next question would be how do i flash a kernel and why would i flash a kernel?
cant flash ROM
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
brenntard said:
Please help,
SO i downloaded the CM10.2.1ROM for the evita along with the gapps package provided. after putting them onto my phone i went into twrp and tried flashing them it starts to flash but then comes up with an error
E:Error executing updater binary in zip '/sdcard/cm10.2.1/pa-gapps-full-
Error flashing zip '/sdcard/cm10.2.1/pa-gapps-full-4.3-20131102-signed.zip
updating partition details...
thast what my screen reads after trying to flash the zip. What can i do?
Click to expand...
Click to collapse
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
timmaaa said:
It's most likely because your hboot is too new (2.18) and hasn't been included as a compatible hboot in the installer script. You can flash the 2.15 firmware from Turge's stock Sense 5 ROM thread to overcome this problem. But first you'l need s-ff to do that. So I'd suggest installing the Kickdroid ROM, then you can get s-off, then you can flash the firmware, then you can flash that ROM.
Click to expand...
Click to collapse
That sounds easy enough.. I was able to gain s-off through the face palm method earlier today so now i just need to flash the 2.15 firmware. in the thread it says to "make sure you flash your current ROM's boot.img after" is this necessary if i am using the stock 4.2.2 sense 5 ROM already, does the download include the radio? do i need a different radio?
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
timmaaa said:
The firmware is taken from the update that included that stock ROM so you might not have to flash the boot.img afterwards, if your phone doesn't boot thought that's why. The firmware package does include the radio, and it isn't suggested your change the radio because that'll cause a mismatch resulting in signal loss and reboots.
Sent from my Evita
Click to expand...
Click to collapse
awesome! im gonna try that tonight.
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
timmaaa said:
Download the file from the thread and follow the instructions precisely. It isn't flashed through recovery like a ROM would be, it's flashed in rebootRUU mode using fastboot.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much for your help! i succesfully flashed the firmware and amnow running CM10.2.1. If i want to flash a 4.4 ROM do i need a different recovery? im currently using 2.5.0.0
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
timmaaa said:
Yes you do need a different recovery to flash KitKat ROMs, it's the unofficial modified TWRP 2.6.3.0 from our Original Android Development section that you want. Even if you don't want to flash a KitKat ROM you need to change your recovery, the one you're currently running is very buggy and will cause major issues when flashing anything.
Download either the modified version of TWRP 2.6.3.0 (for KitKat ROMs) from here, or TWRP 2.6 (for any other ROM) from here.
Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
Click to expand...
Click to collapse
I guess the all in one toolkit hasn't had an update in a while...
thanks again for all the help, really appreciated
i have been working to get a custom rom on my device for roughly a month now and today was the day it finally happened
glad to say i learned a lot thanks to help from people like you in this great forum