Related
[solved]
I'd like to start out by saying that even though this is my first post, I've been an XDA lurker for years, having used you guys as a resource for trying out new roms and improving devices I've owned including my Eris, Incredible and now Rezound. That being said, I'm not what I'd call a noob. I achieved S-off on my second attempt with the wire trick, and my Hboot posts as 2.21.2121 with the Juopunutbear tag at the top. I loaded a nandroid backup that I had prior to going S-off, of scott's cleam rom 4.3 based on the leaked 3.11 RUU I believe. On to my problem.
On my loaded nandroid backup, the sd card doesn't work. If I install a new rom, it works, but it crashes. It doesn't matter what I install, it will crash after a few minutes after booting even with a clean wipe of data/cache/dalvik. I'm using AmonRa 3.15 recovery, which magically disappeared on my phone after going S-off. Basically what I'd like to do is start over. I'd like to reinstall the bear hboot 2.21 (if that's the best thing to do, if it won't brick it.) I've read that installing the same hboot over itself on some devices will cause a brick. Next I'd like to install Scott's CleanROM (I think 4.4 is the newest) and start from scratch. I just don't want to end up bricking my phone, and the Rezound is a bit different from the other phones I've used. I'm familiar with ADB, and I've MD5 checksummed everything I've downloaded, but I'm open to the possibility that I've made an error somewhere. You guys are a great resource and I'm both sorry to finally have to be "that guy" that asks a question, but also happy that I'll have this problem resolved with your help. I've looked in the other threads before coming here.
I think my answer lies here:
http://forum.xda-developers.com/showthread.php?p=25550906
will try and report back asap.
Update: The above link worked for me, everything is running ok now.
jordosaxman said:
[Possibly solved]
I'd like to start out by saying that even though this is my first post, I've been an XDA lurker for years, having used you guys as a resource for trying out new roms and improving devices I've owned including my Eris, Incredible and now Rezound. That being said, I'm not what I'd call a noob. I achieved S-off on my second attempt with the wire trick, and my Hboot posts as 2.21.2121 with the Juopunutbear tag at the top. I loaded a nandroid backup that I had prior to going S-off, of scott's cleam rom 4.3 based on the leaked 3.11 RUU I believe. On to my problem.
On my loaded nandroid backup, the sd card doesn't work. If I install a new rom, it works, but it crashes. It doesn't matter what I install, it will crash after a few minutes after booting even with a clean wipe of data/cache/dalvik. I'm using AmonRa 3.15 recovery, which magically disappeared on my phone after going S-off. Basically what I'd like to do is start over. I'd like to reinstall the bear hboot 2.21 (if that's the best thing to do, if it won't brick it.) I've read that installing the same hboot over itself on some devices will cause a brick. Next I'd like to install Scott's CleanROM (I think 4.4 is the newest) and start from scratch. I just don't want to end up bricking my phone, and the Rezound is a bit different from the other phones I've used. I'm familiar with ADB, and I've MD5 checksummed everything I've downloaded, but I'm open to the possibility that I've made an error somewhere. You guys are a great resource and I'm both sorry to finally have to be "that guy" that asks a question, but also happy that I'll have this problem resolved with your help. I've looked in the other threads before coming here.
I think my answer lies here:
http://forum.xda-developers.com/showthread.php?p=25550906
will try and report back asap.
Click to expand...
Click to collapse
I am suprised that this post thread has 0 replies and 200 views but it is most likely because this has been answered in a few threads already. At the bottom of the first post in the link http://forum.xda-developers.com/showthread.php?t=1612035 (happens to be titled S-off with instructions) you will see a dropbox link for a modified hboot for ics. Follow instructions and you should be up and running again.
It wasn't the Hboot, I followed all the instructions as listed in the S-off thread including the ICS hboot. After following this:
http://forum.xda-developers.com/showthread.php?p=25550906 (the s-off instructions)
my problem is fixed. I used the 3.11.605.22-RUU-PH98IMG.zip found on one of Bored's rom postings in the thread, since none of the others I found had an MD5 included or would download right.
So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
First, a big big thanks to Virus!! My phone info:
Sprint EVO3D CDMA
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.0000
RADIO-1.06.00.1216
eMMC-boot
Jun 8 2011, 17:20:22
TWRP v1.1.1
I previously flashed Freeza's v2.17.651.5 firmware and then the Stock ROM + root Shooter_S_Sprint_WWE_2.17.651.5_odex.zip which I'm currently running.
I've read this entire post OTA_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2-2.17.651.5 along with mpgrimm2's post Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 8-20-12 and just want to ask before I "leap"! My steps as far as I see it:
1. Run my backups (Titanium, etc) and create a TWRP nandroid.
2. Flash the Stock 2.89.651.2-2.17.651.5 firmware
3. Install the superwipe zip (presumably install zip via TWRP recovery?)
4. Flash the Stock Rooted 2.89.651.2-2.17.651.5 ROM
5. If necessary, flash the BT fix.
At this point I should be up and running the DEODEX'd version of the Stock ICS ROM as if I'd done the ICS OTA. Question here is whether I'll hit compatibility problems with any apps I have installed? I know hard to say w/o knowing what all I've got installed, but if problems I figure just uninstall the app and find something compatible... Any other problems I could expect or should look for?
If for some reason I wanted to go back to my current GB ROM nandroid before the ICS update, I can just reflash hboot 1.40 and restore the nandroid made in my step 1? Do I need to worry about reflashing any other 2.17 firmware? It sounds like I can just restore my nandroid on hboot 1.58 but thinking I'd rather be back at hboot 1.40.
I too have run into the "remote: not allowed" error when using fastboot to flash images. From mpgrimm2's post, it's looks to be because my radio is s-off while my stock hboot 1.40 is technically not s-off? To have a fully functional fastboot via pc, I'd need to flash JBear hboot 1.40 (for GB) or JBear hboot 1.58.5858 (for ICS) from Ramjet's Pick your bootloader!, right? Seeing that I'm ok with flashing by booting into recovery, is there any other advantages (or disadvantages) to using the JBear hboots?
Sorry for the long post, but wanted to be complete... All help is greatly appreciated!
It looks like you have it right. To clarify one point, you don't need to downgrade firmware to run GB (I don't think that's even possible). Just the hboot.
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
It looks like you have it right. To clarify one point, you don't need to downgrade firmware to run GB (I don't think that's even possible). Just the hboot.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
Thanks for the confirmation on my steps and being able to revert if I want to...I figured I would want to keep some of the updated firmware but wasn't sure what all could/should keep.
Although like the idea of being able to use fastboot fully, thinking best to just stick with the stock hboot for now...
Again thanks and if anyone has any other thoughts, they're always welcome!
I delayed doing the ICS update using the steps above, have read through the new pages/posts on the http://forum.xda-developers.com/showthread.php?t=1808150 post, and now have a few last questions before I jump in! Sorry if seem obvious, but have done the reading but now a bit confused or need clarification. I could just do it and recover if necessary, but rather ask up front.
If reading right, doing the Superwipe in step 2 will format both my phone and sdcard, cleaning out and recreating the partitions. Does this mean I'll have to use my TB Pro backups to restore all my personal apps & data? And if so, will I encounter any issues restoring such thing as my call log (or just restore the data and I'll be ok)? Reading up on Superwipe gets me thinking it deletes everything when I thought flashing this would be like an OTA update and keep my current apps, etc. Sorry again it's been awhile since flashing the stock 2.18.651.5 rooted ROM and just not remembering!
Also part way through the threads, there's mention of needing to first flash a ROM that will boot on 1.58 hboot or will get boot looping. I figure if my 2.18.651.5 GB rooted ROM won't boot after step 1, I'd just have to remove the firmware P86IMG file from the sdcard to proceed to step 2. The OP doesn't mention this - or is this a different situation than mine?
Lastly, on P.59, mpgrimm2 recommends flashing the full stock RUU to clean out all bits & pieces that might be left (I'm figuring it's the RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe) and reinstalling a custom recovery to have the stock rooted ICS. Is this a special case for one person or an alternative to the 3 step method? And it would mean I'd be reinstalling all apps and restoring all my data afterwards, right? Should I even consider this route if the three steps do an upgrade and keep my apps/data?
Thanks and sorry again for so many questions - just getting a headache keeping all straight and sorting through what's special case scenarios...oh and one last, is this Sense 3.5 or 3.6 - the OTA on HTC's site is listed as 3.6, right?
That's correct sir. It is 3.6
Hey guys, brand new here. I've actually browsed the forum for MANY other things in the past but never had to register because I've never had a question that hadn't been answered, but I think I might finally have one.
I have an Evo 4G LTE that's been giving me all kinds of problems. I followed qbking77's video on how to install sdk tools, how to unlock the bootloader, and how to root the device. All of that worked perfectly with no problems whatsoever. Problems started arising when I tried to install my first ROM. I chose the "CleanRom 1.5" because I really liked the simplicity of it, the overclocking capabilities, and the look. So I went ahead and booted into my recovery (TWRP 2.4.4.0), did a factory reset, cleared cache, then tried to install the ROM. After I first "swipe to confirm flash", the "CleanRom" text pops up with all the developers names and etc, so it loads correctly. Then, a few seconds into the flash, whenever it gets to flashing the boot image, the phone just turns off and restarts. I am then stuck at the HTC splash screen until I hold the power button down for 10 seconds and boot back into recovery.
I thought this had to be the ROMs fault, maybe it was corrupt. I re-downloaded it from a different computer and tried again. The same thing happened. Then I tried to install the exact one that qbking77 installed in his "how to" video, CleanRom 1.0 (older version). I downloaded this and tried again, and the same thing happened.
So then I took my suspicions to TWRP. I have the latest installed (2.4.4.0). I did a few searches and found that other people were also having trouble installing roms on 2.4.4.0 with their Evo 4G LTEs, and everyone was saying to downgrade to a more "stable" version. Most people said 2.3.1.0 was the best and most stable, so that's what I tried. After installing it (using THIS guide), I boot into recovery and TWRP loads up just fine, but none of my touch inputs work. The only button that does anything is the power button, which locks TWRP. Then I can't swipe it to unlock it again because it doesn't register the touch inputs.
I then tried to downgrade all the way down to 2.1.8, which is what qbking77 was using in his video tutorial. Also didn't work. Same touch input issue. After more reading, all the replies that I found for people who were having the touch input problem for their devices said "Upgrade to the newest version to fix", which obviously I can't do because that version doesn't flash ROMs correctly (at least on my device).
I've ran out of ideas, any help would be greatly appreciated.
Thanks in advance,
John
Honestly I didn't read all your post ( I'm tired and high) but from what I did read it seems your s-on. If you didn't run lazypanda/dirty racoon or face palm then you're S-ON. This means you have to flash your boot IMG seperately either thru fast boot or flash IMG GUI.
There's a thread called "DON'T PANIC" stickied in general or q&a. All your questions will be answered there.
Good luck man. Once you read that thread you'll be all set.
You should really look into going S-OFF. Just read up on it before you go got it.
Edit............
I read some more. It seems you've upgraded your phone to the latest so you have the new touch panel driver which means your limited to the ROMs you can run. You can only use ROMs based off the new firmware 3.16. You should download meanrom. I think its got a S-ON kernel flasher built right into the ROM and I think you'll be all set with the touch panel driver too. You may have to read a few OPs to get the answers you need.
Again if you were S-OFF you would have a kit more options
Sent from my EVO 4G LTE using xda premium
Yeah, corc is right...the latest firmware has an updated touch panel driver in it that will only work with twrp 2440 (which is why your touchscreen didn't work on 2310) and roms on the 3.16 base. I would recommend getting s-off and downgrading just the touch panel driver, then going back to twrp 2310...any rom should flash just fine then (the new tp driver is not required) and you'll have the added benefit of not needing to flash the kernel separately like you would while s-on.
Sent from my EVO LTE
Thanks for the information, guys! I found a guide on how to get s-off (looks like I'll have to use Ubuntu, though), but I couldn't find any information on downgrading the touch panel driver. Is there an extra step in downgrading it, or does it downgrade with 3.15?
Thanks, sorry for my nubness,
John
No need to apologize for wanting to learn, that's what the forums exist for
Since you're on the latest firmware, which means you have the latest hboot, you'll need to use baby racun from the unlimited.io site to downgrade your hboot (link in the dirty racun thread, stickied in Original Development). At that point you can run dirty racun to get s-off. I think the downgrade from baby racun only affects hboot (I didn't use this method so can't be 100%, but the bootloader is the only thing that matters really when it comes to s-off, so that's my hunch), which means you'll still have the latest tp driver that's giving you problems. So once you're s-off, you can flash the tp img that's under the 3.15 section in this thread to get your touch screen back:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Sent from my EVO LTE
Last bit of advice. Read as much of those threads as you can. Information is all you need to get where you wanna be
Sent from my EVO 4G LTE using xda premium
I had the same trouble with my firmware being too updated for AOSP-based ROM's. But my choice of ROM is Viper4G from Venom anyway, so it doesn't matter. For me, it's easier to load a ROM that's compatible with the latest firmware than to downgrade the firmware.
Viper4G is a bit bloated, though, at about 700 MB. It's based on the Sense ROM, and it contains the Gapps and Sprint bloat. I remove most of the Gapps and Sprint stuff, but the ROM is preloaded with a bunch of goodies, including SuperSU, CPU Spy, OC_Daemon, FX file manager, Venom Tweaks, aLogcat, and it supports Swype2Unlock & Sweep2Wake (though I don't have a compatible kernel for it yet). And, with the right kernel, you could overclock. Plus, I much prefer the Sense UI, but that's just personal preference....
First and foremost I want to say what I don't see a lot of from newbs around here: "Thank You". I have lurked this website for months, trying to learn the right way to do all sorts of things and I think you are all awesome for taking time out of your lives to do all of this for us.
I really hope that my questions aren't stupid and I can learn a little something from this in the process
I have read, and researched and read and researched and I think in all of my reading I have just gotten myself REALLY confused.
Here is my device:
Evo 3D (shooter) CDMA
Hboot 1.58
unlocked
S-ON
It took a lot of doing but I successfully rooted and lived in stock happy as a clam for a few days.
I first tried to install PAC rom [Halo + Android 4.2.2] and got numerous install errors (which I now believe is from installing in 4ext instead of fastboot)
so I tried CM 10.1 ...
I was stuck in a bootloop with CM 10.1 (which I now have learned may be secondary to the Hboot being the wrong version)
I decided I was in over my head and went to look for my ROM manager recovery (which was apparently lost on my internal mem), but I can't find my CWM recovery either [I preformed them both using the ROM manager app, right after root NOT in fastboot]
I attempted to boot another ROM which I thought was compatible with Hboot 1.58 (Team dirt unoffical slimbean v1.1) made sure I got my gapps right...and Im still stuck in bootloop (now just of slimbean instead of CM)
So I said screw it and tried to install the RUU after relocking and start over. But I keep getting an error message that my hboot version is wrong.
Finally, what I am looking for help with is the following:
1. Help to fix bootloop as I would like to really try the PACMAN Rom
2. Help to determine what the RUU error is so that I can return to stock rooted if I don't like PACMAN
3. Where the F*** are my recoveries????
4. Just a little bit of sympathy: I acknowledge that I am a newb but I have read, read and read some more and quite frankly am terrified of getting screamed at for missing something simple. Please believe this was my last option because I now that right now I am merely soft bricked and don't want to turn a nice phone into a paperweight (Which is why I haven't tried the URT tool yet, to downgrade Hboot, Im nervous that Ill really mess up)
I am sorry to be so wordy... but you all say be detailed and as a Paramedic I'm just trying to give you the best "past medical history" possible.
Thank you guys again for all you do to help us not so tech savy...
please let me know what (if any) more info is needed or requested.
Be safe,
Doc
I can only answer 1 question and that is to why you can't get any cm10+ roms to work and that is because your running hboot 1.58. Jellybean roms do not work on hboot 1.57 or 1.58. You must downgrade your hboot before you can run anything jellybean. But first you have to use the juopunutbear exploit to s-off your device and flash a new hboot. Here's the link to the thread I used. http://forum.xda-developers.com/showthread.php?p=24530433
Sent from my Evo V 4G using Tapatalk 4 Beta
the RUU error is probably because you are trying to run a gingerbread RUU. with your hboot, only ICS RUUs will work for now. If you have taken the March OTA (2.95.651.5) then there is no RUU that will work for you until you downgrade mainver.
This guide has all the instructions if you want to s-off and downgrade (there are some additional instructions for people who have taken the march ota)
if you choose to do the juopunutbear exploit you'll need ubuntu linux (or an ubuntu livecd)
As others have said you need a lower hboot for anything other than ics.
To do that you need s off.
To get s off you need a booting Rom.
You need to do the following
Install 4ext recovery (highly recommended)
Enable smart flash in 4ext, this is because you're still s on
Now flash a stock based Rom, butterz, negalite blu, or stock
Now you need to follow instructions to obtain s off.
Good luck
Sent from my HTCEVOV4G using xda app-developers app
Re-Lock device using htcdevway . flash a stock gb or ics.
I cant seem to find your Thanks button. Because I would click it a thousand times! That link was exactly what I needed and I'm running rooted, stock ICS and playing to my hearts content . Thank you so much :good:
EM|NEM said:
the RUU error is probably because you are trying to run a gingerbread RUU. with your hboot, only ICS RUUs will work for now. If you have taken the March OTA (2.95.651.5) then there is no RUU that will work for you until you downgrade mainver.
This guide has all the instructions if you want to s-off and downgrade (there are some additional instructions for people who have taken the march ota)
if you choose to do the juopunutbear exploit you'll need ubuntu linux (or an ubuntu livecd)
Click to expand...
Click to collapse