Hello
I have an Amaze 4G x715e
Yesterday i unlocked the bootloader and installed twrp recovery. Then i went to install cm10 rom. First i took nandroid backup of my stock and when cm10 finished installing it hangs at "welcome- select language" and then restarts !!!
how can i restore my backup if I m on s-on. there is no disc image file in backup folder as all are win files. when i restore same thing happens phone keeps on restarting!! but doesnt boot.
my Hboot version is 1.92.000
S-on
Pls help what should i do ?????
thanx
I had this exact same problem.
It is because you are S-ON and do not have SuperCID
Use this thread to get your device working again!!!!!!
http://forum.xda-developers.com/showthread.php?p=46376931#post46376931
I would suggest trying to get S-OFF using Ubuntu and then doing SuperCID
If you cannot attain S-OFF, there is a rom that worked for me perfectly I will link you to.
http://forum.xda-developers.com/showthread.php?t=2482651
I still highly suggest that you get S-OFF and SuperCID before you flash any more roms.
Here is a full guide on how to get it
http://forum.xda-developers.com/showthread.php?t=2167596
help me out please
Darin_Ram said:
I had this exact same problem.
It is because you are S-ON and do not have SuperCID
Use this thread to get your device working again!!!!!!
http://forum.xda-developers.com/showthread.php?p=46376931#post46376931
I would suggest trying to get S-OFF using Ubuntu and then doing SuperCID
If you cannot attain S-OFF, there is a rom that worked for me perfectly I will link you to.
http://forum.xda-developers.com/showthread.php?t=2482651
I still highly suggest that you get S-OFF and SuperCID before you flash any more roms.
Here is a full guide on how to get it
http://forum.xda-developers.com/showthread.php?t=2167596
Click to expand...
Click to collapse
Hello,
I am currently downloading Sultan ROM 2.0 because i am S-on and forgot to backup the original OS. (basically empty phone, I think) However, I managed to get TWRP 2.6 on for recovery. After I get the ROM and move it on to the SD card, I should install it from TWRP, right? (removing cache, dalvik etc) Hope I get back and running so I can get build out of source codes.
My question is, is kernel compile(from source) for HTC amaze x715e (the asian HTC amaze?) is possible or not.
I believe the kernel source that HTCdev site provides is only for HTC amaze 4G. (or is it the same?)
Thanks in advance.
spencerjang90 said:
Hello,
I am currently downloading Sultan ROM 2.0 because i am S-on and forgot to backup the original OS. (basically empty phone, I think) However, I managed to get TWRP 2.6 on for recovery. After I get the ROM and move it on to the SD card, I should install it from TWRP, right? (removing cache, dalvik etc) Hope I get back and running so I can get build out of source codes.
My question is, is kernel compile(from source) for HTC amaze x715e (the asian HTC amaze?) is possible or not.
I believe the kernel source that HTCdev site provides is only for HTC amaze 4G. (or is it the same?)
Thanks in advance.
Click to expand...
Click to collapse
You're asking many things that can easily be found on the threads that are pinned to the top of the the various forums here. Before proceeding I strongly suggest you read them first, because judging by the content of your post you are getting ahead of yourself and are already heading for serious problems. If you are s-on with an Asian or unbranded Amaze you will soon find yourself with an expensive paperweight if you continue along your current path.
You must first attain s-off and SuperCID before flashing an ICS ROM, and you must first flash a factory ICS ROM image before you can flash an after-market ROM like Sultan. This is because none of the after-market ROMs have radio basebands, and without an ICS radio you won't have communication or data with any ICS and newer ROMs you may flash. Also TWRP is practically useless on an S-on handset because it will be unable to flash a kernel image, so it won't boot-up.
As I said, read all of the pinned threads located at the top of the various forums here, all of the info you seek is located there, including links to other posts with important information. In a nutshell you will need to proceed as follows: You will have to flash back to the appropriate GB ROM for your handset. Then if you haven't already, go to the HTC-dev site and get the binary unlock blob and save it (you will need it again). Attain s-off and SuperCID. Once these have been successfully accomplished you must flash a factory ICS image to get the radio. Once you have the proper ICS radio and you're s-off you can flash any ROM you like.
Cutting corners will only cause problems for you later, then your next post will be a cry for help in the Amaze unbricking project thread.
Good luck.
spencerjang90 said:
Hello,
I am currently downloading Sultan ROM 2.0 because i am S-on and forgot to backup the original OS. (basically empty phone, I think) However, I managed to get TWRP 2.6 on for recovery. After I get the ROM and move it on to the SD card, I should install it from TWRP, right? (removing cache, dalvik etc) Hope I get back and running so I can get build out of source codes.
My question is, is kernel compile(from source) for HTC amaze x715e (the asian HTC amaze?) is possible or not.
I believe the kernel source that HTCdev site provides is only for HTC amaze 4G. (or is it the same?)
Thanks in advance.
Click to expand...
Click to collapse
Okay so as @Odysseus1962 said, you need to get S-OFF and SuperCID first.
And TWRP is useless in this scenario because it does not have smartflash, which like Ody said, can flash kernel images.
Really there's limitations to what you can do right now. I think if you find an Asian GB RUU to flash you would be back to your original phone but if you want to be on ICS you need to do everything we told you in the previous post. Otherwise you will be very sad for a bricked phone.
Again, follow this thread step by step to get back to a working phone.
http://forum.xda-developers.com/showthread.php?p=46376931#post46376931
Get the phone working first, that is priority. ICS can wait. It is not running away.
Thanks!
Darin_Ram said:
Okay so as @Odysseus1962 said, you need to get S-OFF and SuperCID first.
And TWRP is useless in this scenario because it does not have smartflash, which like Ody said, can flash kernel images.
Really there's limitations to what you can do right now. I think if you find an Asian GB RUU to flash you would be back to your original phone but if you want to be on ICS you need to do everything we told you in the previous post. Otherwise you will be very sad for a bricked phone.
Again, follow this thread step by step to get back to a working phone.
http://forum.xda-developers.com/showthread.php?p=46376931#post46376931
Get the phone working first, that is priority. ICS can wait. It is not running away.
Click to expand...
Click to collapse
Yes you are right, I need to get it back to working before I have ICS or anything. I really don't have any preference about GB or ICS anyways.
I spent about 2 weeks looking for information about this phone but then I found out that this one was the asian version, not the 4G. (Do they have much difference from HTC Amaze 4G?!)
As a newbie, I got confused and understood something wrong and went off to a wrong direction.
Anyways I'll follow with the thread that you've posted.
Thanks again.
New question
Thank you I now have it back to normal.
What I want to do is, I would like to compile the kernel for this device from source. I see that there are several versions of kernel sources in HTCdev site. Should I grab T-Mobile version and compile accordingly? and flash it using Hasoon's Kit?
Compile it from source and thats just it, no more.
Or do I have to go with what @Odysseus1962 said and get SuperCID, S-off and etc??? AND THEN go ahead with kernel compile?
It doesn't matter if the android is GB or ICS. (I think I'll go with GB though)
Thank you.
spencerjang90 said:
Thank you I now have it back to normal.
What I want to do is, I would like to compile the kernel for this device from source. I see that there are several versions of kernel sources in HTCdev site. Should I grab T-Mobile version and compile accordingly? and flash it using Hasoon's Kit?
Compile it from source and thats just it, no more.
Or do I have to go with what @Odysseus1962 said and get SuperCID, S-off and etc??? AND THEN go ahead with kernel compile?
It doesn't matter if the android is GB or ICS. (I think I'll go with GB though)
Thank you.
Click to expand...
Click to collapse
There's an excellent article at xda university about kernel compilation, as well as, several excellent threads in the main development forum on the main board. The HTC sources are a good place to start however you'll need to prepare your build box correctly. This is where the info threads I mentioned come in handy. Compiling the kernel for android requires cross-compilation and installation of the proper toolchain since you're more than likely planning on building from an x86 or amd64 based machine.
As to which sources to select, there are several versions on the HTC-dev site that are directly compatible with the Amaze. However IIRC there is only one that includes the sources for the TI chipset which is required for Bluetooth functionality. That source is the one that's considerably larger than the others and is the one you should use for your build.
You don't need s-off to build kernels since that's done on your PC. You might run into problems installing on your device, but I'm not sure. This is because of a CID mismatch with your build (no CID) and what is expected by the ROM you have installed. It's just a generally accepted idea that if you plan on developing for an HTC device you should be unlocked, s-off, SuperCID, and in the case of the Amaze, on the latest ICS radio baseband. This gives you the freedom to install anything you want, without external limitations on your handset.
The only time this isn't an absolute requirement is if you own a version that came with an ICS image on it or where one is available to install. Since they have the proper radio they can flash any ROM, provided they flash with 4ext recovery with smart-flash enabled. I hope this helps.
Good Luck.
Odysseus1962 said:
There's an excellent article at xda university about kernel compilation, as well as, several excellent threads in the main development forum on the main board. The HTC sources are a good place to start however you'll need to prepare your build box correctly. This is where the info threads I mentioned come in handy. Compiling the kernel for android requires cross-compilation and installation of the proper toolchain since you're more than likely planning on building from an x86 or amd64 based machine.
As to which sources to select, there are several versions on the HTC-dev site that are directly compatible with the Amaze. However IIRC there is only one that includes the sources for the TI chipset which is required for Bluetooth functionality. That source is the one that's considerably larger than the others and is the one you should use for your build.
You don't need s-off to build kernels since that's done on your PC. You might run into problems installing on your device, but I'm not sure. This is because of a CID mismatch with your build (no CID) and what is expected by the ROM you have installed. It's just a generally accepted idea that if you plan on developing for an HTC device you should be unlocked, s-off, SuperCID, and in the case of the Amaze, on the latest ICS radio baseband. This gives you the freedom to install anything you want, without external limitations on your handset.
The only time this isn't an absolute requirement is if you own a version that came with an ICS image on it or where one is available to install. Since they have the proper radio they can flash any ROM, provided they flash with 4ext recovery with smart-flash enabled. I hope this helps.
Good Luck.
Click to expand...
Click to collapse
Thanks again for the quick reply.
I am now done with S-off (wire trick took me like 20 tries ) and getting SuperCID.
Now my bootloader shows LOCKED, hboot 1.92, S-OFF. Then I am going for kernel compile for the exact stock sources.
ruby-gb-crc-2.6.35-4a1059e. (and of course cross-compiled it) Now I have a zImage with me but won't flash with 'fastboot boot zImage'. I'll look for the solutions in the forum.
I have to say sorry for not reading the main threads and making you bothersome.
Thanks again.
Related
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 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
So while in process of s-off once I got to the part when you "fastboot oem rebootRUU" that went through. But right after trying to flash a zip im stuck looking at the blk HTC screen. I was given a "<Failed <remote: 99 unknown fail>". Now its just stuck.
I've been trying to figure out what happened but just have no where else to turn. Please lend a hand.
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
aarsyl said:
I think I already know the answer to this question, but what version is your firmware? Just for your knowledge, there hasn't been an RUU since ICS, or maybe the first release of JB. So, odds are, you flashed the wrong RUU.
But good news, you *might* not be bricked. Have you tried rebooting? This really your only option, anyway. Try to get into the bootloader. Flash a new recovery if the RUU has already wiped it, and flash a compatible rom.
Please also list your bootloader info.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
It's not a full RUU in the normal sense. It's the one for Facepalm.
To the OP, did you gain SuperCID prior to running those commands? If not, then the process will fail. You should simply be able to hold the power button down & reboot your phone. Also, as stated above, list your device info so we can make sure you're using the right S-off exploit.
Sent from my HTC EVO 4G LTE
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
z3r0t0l0rEnCe said:
So I did get the phone into the bootloader. I was trying to do the rumrunner s-off but being I was so damn tired lastnight I ended up forgetting a step. I am currently unlocked and rooted. I also somehow deleted my backup like a idiot and wiped the os. So I'm stuck from this point where I need to go.
So where we stand as of now:
bootloader unlocked
rooted
twrp 2.6.3.0
firmware 3.17.651.4
hboot 2.09
radio 1.13.11.0830
Click to expand...
Click to collapse
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
aarsyl said:
Happens to all of us. Don't worry about wiping the OS. Look for Captain Throwback's stock rooted rom, and flash a custom kernel along with it, like the Dirty MAC kernel or Arc reactor. Doesn't matter which one...rumrunner just needs a custom kernel.
Captain Throwback's stock 3.17 base
http://forum.xda-developers.com/showthread.php?t=2468418
Dirty MAC kernel
http://forum.xda-developers.com/showthread.php?t=2178307
Arc Reactor
http://forum.xda-developers.com/showthread.php?t=1873824
After you flash these, then reboot into Android, set your phone to stay awake during charge Settings-->Display and Buttons, and also set SuperSU to automatically grant root access (open the app, swipe right twice, and scroll down a little). This way, you don't have to touch your phone. If you touch it, the process will fail....even to unlock the phone to grant root access. And of course, turn on USB debugging in Developer Options.
After you do all of these, then run the exploit.
Click to expand...
Click to collapse
This is odd to me, because I ran rumrunner at least 3 times using just my stock ROM (no custom kernel or anything), and it worked fine every time. I guess the new version of rumrunner added some limitations to make it more generic.
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
z3r0t0l0rEnCe said:
whats bothering me is that even after i check the MD5, it keeps failing to install capt zip. think maybe i can just use adb to push the zip file? just not sure how to word the command right to get it to load
Click to expand...
Click to collapse
No, don't. If it fails, don't force it. Reflash TWRP 2.6.3 (not the kit kat version), and try to flash again.
@Captain_Throwback: Yes, I didn't remember needing a custom kernel when I used Dirty Racun, but rumrunner needs it now. Keep in mind that rumrunner isn't for this device exclusively. Maybe that's the purpose of the custom kernel.
i'd wager you're trying to flash files that aren't recovery flashable, then lying to the people who are trying to help you.
i got it running again using capt stock rooted rom. attempting rumrunners s-off again now that i got this part working.
Are you using a custom kernel?
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
now s-off and updated rumrunners hboot. now onto flashing roms finally.
Thank you all that helped me with my stupidness and not reading directions.
Last post. I can't say it enough that you must read read read when it comes to directions. If I would of followed directions as directed I would of never ran into the issues I did. It was a learning experience.
One thing for sure that I took from this experience is adb and directions. I've learned a lot in the last 24hrs alone.
I'd like to thank Capain_throwback and everyone in the irc for the help and you all here that assisted me.
Sent from my EVO using XDA Premium 4 mobile app
Hi,
Can someone help me please. I am looking for a rom for my AT&T US, HTC One M8. I'm running 4.4.2, Hboot 3.16, Radio 1.16..., and 1.58.502.1 firmware.I have the 3.4 kernel. I am unlocked, TWRP latest custom recovery, and rooted with SuperSU. I am S-On. I can't S-Off and can't update my Firmware. I need it to work in the US, so what rom can I flash that will work. When I go to Dev sites every rom I see only has the 4.4.3/4.4.4 versions with the new Firmware, for my device. When I try to flash .zip's through TWRP, Aroma gives me a success, but it auto reboots and I get stuck in boot loop... I am able to recover the stock image, but can't get a custom rom to stick. I have watched hours of videos and read hundreds of pages of threads. HELP
Thank You,
-Shane
HitShane said:
Hi,
Can someone help me please. I am looking for a rom for my AT&T US, HTC One M8. I'm running 4.4.2, Hboot 3.16, Radio 1.16..., and 1.58.502.1 firmware.I have the 3.4 kernel. I am unlocked, TWRP latest custom recovery, and rooted with SuperSU. I am S-On. I can't S-Off and can't update my Firmware. I need it to work in the US, so what rom can I flash that will work. When I go to Dev sites every rom I see only has the 4.4.3/4.4.4 versions with the new Firmware, for my device. When I try to flash .zip's through TWRP, Aroma gives me a success, but it auto reboots and I get stuck in boot loop... I am able to recover the stock image, but can't get a custom rom to stick. I have watched hours of videos and read hundreds of pages of threads. HELP
Thank You,
-Shane
Click to expand...
Click to collapse
There are 4.4.2 roms still available but your best bet is pay the $25 for sunshine s-off utility that way you can update your firmware and run whatever rom/kernel you want.
If you've tried the flash various ROMs, and they all won't boot, then the problem is not what ROM, but something else.
adb erase cache
Then, flash recovery again. Possibly re-download recovery, to make sure the file is not corrupt.
redpoint73 said:
If you've tried the flash various ROMs, and they all won't boot, then the problem is not what ROM, but something else.
adb erase cache
Then, flash recovery again. Possibly re-download recovery, to make sure the file is not corrupt.
Click to expand...
Click to collapse
^^ I did that when I rooted the phone. I used the HTCDev to unlock it. I used Fastboot and adb in cmd from my PC to install TWRP and the Recovery file and clear the cache. Should I reflash recovery again???
I have wiped and tried factory resets before installing a rom. The problem is that I can't find the download link for an old rom for my specific phone. I need the 1.58.502.1 version (Don't I ?), so that I don't have to change my Firmware through S-OFF... When I find a rom that did make one that would work on my device, they have already updated the OP download link with their latest version to run with the updated AT&T 4.4.3/4.4.4 and 2.22.1540.3.
* I have the newest TWRP installed with the 24MB Recovery.img. I have SU installed with privileges. The phone passes rooted tests. Phone is S-ON... *
iRunLinux said:
There are 4.4.2 roms still available but your best bet is pay the $25 for sunshine s-off utility that way you can update your firmware and run whatever rom/kernel you want.
Click to expand...
Click to collapse
^^I have seen even sunshine fail with the latest devices from AT&T.
?----->Does anyone have a good link to a rom that will run on my; AT&T HTC One M8 running 4.4.2 & 1.58.502.1, (1.16.21331931.LA11G)? It was bought a month ago from an AT&T store...
Thank You,
-Shane
HitShane said:
Should I reflash recovery again???
Click to expand...
Click to collapse
I just told you to adb wipe cache and flash recovery again. Why are you asking me this? A lot of issues with TWRP not flashing ROMs can be solved by wiping cache and flashing again (probably just a bad initial install).
HitShane said:
I need the 1.58.502.1 version (Don't I ?), so that I don't have to change my Firmware through S-OFF...
Click to expand...
Click to collapse
Any ROM that is not 2.xx Sense based.
I haven't checked every single thread/link, but most (if not all) 1.54 and 1.58 based Sense ROMs on my Index thread seem to be working:
http://forum.xda-developers.com/showthread.php?t=2751432
This also includes the stock rooted 1.58 ROM, if you wish to go that route.
HitShane said:
^^I have seen even sunshine fail with the latest devices from AT&T.
Click to expand...
Click to collapse
You sure? I haven't seen sunshine fail for anybody, much less AT&T, which hasn't had their software updated for sometime now. Regardless of how new the device is, its still the same 1.58 software, which is 3 months old at this point.
firewater, on the other hand is known to fail for more recent AT&T versions.
918
redpoint73 said:
I just told you to adb wipe cache and flash recovery again. Why are you asking me this? A lot of issues with TWRP not flashing ROMs can be solved by wiping cache and flashing again (probably just a bad initial install).
Any ROM that is not 2.xx Sense based.
I haven't checked every single thread/link, but most (if not all) 1.54 and 1.58 based Sense ROMs on my Index thread seem to be working:
http://forum.xda-developers.com/showthread.php?t=2751432
This also includes the stock rooted 1.58 ROM, if you wish to go that route.
You sure? I haven't seen sunshine fail for anybody, much less AT&T, which hasn't had their software updated for sometime now. Regardless of how new the device is, its still the same 1.58 software, which is 3 months old at this point.
firewater, on the other hand is known to fail for more recent AT&T versions.
Click to expand...
Click to collapse
So for instance on your Index, I followed the link to ViperOneM8 1.6.0. This takes you to the Dev page for that rom. I follow the page to downloads that directs me another page. Along the way I find out that it looks like ViperOneM8 1.8 is the last update before 2.xx. The download page only has the most recent ViperOneM8_2.2.0.zip, or they offer the OTA increments of each previous version. Those aren't large enough to be the whole rom. How do I find the legacy full roms?
-Shane
HitShane said:
So for instance on your Index, I followed the link to ViperOneM8 1.6.0. This takes you to the Dev page for that rom. I follow the page to downloads that directs me another page. Along the way I find out that it looks like ViperOneM8 1.8 is the last update before 2.xx. The download page only has the most recent ViperOneM8_2.2.0.zip, or they offer the OTA increments of each previous version. Those aren't large enough to be the whole rom. How do I find the legacy full roms?
Click to expand...
Click to collapse
I think you picked one of the few (maybe the only one) that doesn't link to an actual 1.xx ROM. Just pick any other one.
EDIT: Oh, wait InsertCoin also. Will update the Index to show those as 2.22 ROMs.
Devs usually don't keep their legacy versions posted. Most you can do is ask if another member has the zip.
redpoint73 said:
I think you picked one of the few (maybe the only one) that doesn't link to an actual 1.xx ROM. Just pick any other one.
EDIT: Oh, wait InsertCoin also. Will update the Index to show those as 2.22 ROMs.
Devs usually don't keep their legacy versions posted. Most you can do is ask if another member has the zip.
Click to expand...
Click to collapse
Thank you for all of the information. I guess the roms develop faster than I can get a phone for them It baffles me that a version for each baseline of a current device isn't listed. I guess I should flash back to the most current stock rom and wait for the OTA from AT&T. I might try the S-Off for $25, but I have seen a lot of chatter about newly bought M8 ATT devices not working. Something about them having a patch from HTC...
-Shane
info first: hboot 1.25.0002, S-ON, unlocked, cid: HTC__032
fastboot and recovery work and connect with computer, any rom i flash doesn't boot (shows the boot logo, logo disapears with a light backlight only and stays that way. also i flashed a couple of roms and the current logo is from one that should be overflashed, but i don't know what i did different then)
the cache partition has 0 size and seems to cause troubles, tried all 3 recoveries to delete/repair cache partition but doesn't work. should i try to repair it via adb shell?
help :-/
three things:
1. you know you can only use jellybean based roms with hboot 1.25? try one of the sense5 roms.
2. you know you have to flash the kernel (boot.img) seperately via fastboot for every rom you flash?
3. you know there are different recovery versions for ics (hboot 1.24) and jellybean (1.25)?
realCyphox said:
three things:
1. you know you can only use jellybean based roms with hboot 1.25? try one of the sense5 roms.
2. you know you have to flash the kernel (boot.img) seperately via fastboot for every rom you flash?
3. you know there are different recovery versions for ics (hboot 1.24) and jellybean (1.25)?
Click to expand...
Click to collapse
i was following the stickied tutorial - http://forum.xda-developers.com/showthread.php?t=2076675
1. i'm flashing only 4.1 based roms as from http://forum.xda-developers.com/showthread.php?p=35735267#post35735267
2. read somewhere that kernel - boot.img is automatically flashed with the rom and you only reflash to use another kernel? will definitely try your suggestion
3. as per the tutorial, i'm only using 1.25 recoveries (in twrp adb doesn't seem to work, so using PhilZ Touch, CWM based atm)
also as per the tutorial i made a nandroid? backup with twrp if thats of any use? so i first unlocked, flashed twrp and then made backup
flashing the kernel automatically when flashing the rom is only possible when the phone`s S-OFF. and afair its only implemented in vimiro roms.
yes, you dont HAVE to flash the kernel every single time, for example when you move from one jellybean sense-rom to another. but you definitely have to do it when you`re going from sense to cyanogenmod, or even from cyanogenmod 10 to 10.1, from cyanogenmod back to sense and so on.
realCyphox said:
flashing the kernel automatically when flashing the rom is only possible when the phone`s S-OFF. and afair its only implemented in vimiro roms.
yes, you dont HAVE to flash the kernel every single time, for example when you move from one jellybean sense-rom to another. but you definitely have to do it when you`re going from sense to cyanogenmod, or even from cyanogenmod 10 to 10.1, from cyanogenmod back to sense and so on.
Click to expand...
Click to collapse
It's possible with S-ON and is very easy to do (day 1 noob level easy.) See this thread http://forum.xda-developers.com/showthread.php?t=2191723
Will_Xda said:
It's possible with S-ON and is very easy to do (day 1 noob level easy.) See this thread http://forum.xda-developers.com/showthread.php?t=2191723
Click to expand...
Click to collapse
didnt work for me at all. and have a look at the last post. duh.
realCyphox said:
didnt work for me at all. and have a look at the last post. duh.
Click to expand...
Click to collapse
That would probably suggest your dumber than a day 1 noob or you/ OP has not got the latest TWRP available for DX installed,which is quite important... duh.
This has worked for me numerous times when bouncing from various roms/ kernels on HTC desire X and sensation and is very similar to a zip supplied in quite a few viper rom threads that are used for the exact same purpose
DAAAAAAAAAAMN
flashing the kernel afterwards solved the problem, it even says so in the tutorial, reading comprehension problem or PEBKAC, anyway ofcourse i had to try another custom rom just for fun (and risk of breaking stuff again )
where do i send the money to?
kinda offtopic, any other general advice? like should i try S-on? is there a big difference between the roms? custom recoveries?
thx again
potepuh said:
DAAAAAAAAAAMN
flashing the kernel afterwards solved the problem, it even says so in the tutorial, reading comprehension problem or PEBKAC, anyway ofcourse i had to try another custom rom just for fun (and risk of breaking stuff again )
where do i send the money to?
kinda offtopic, any other general advice? like should i try S-on? is there a big difference between the roms? custom recoveries?
thx again
Click to expand...
Click to collapse
Looks Like your already S-ON buddy, S-OFF allows further access to the device so you can achieve things such as SuperCID and flash kernel's from recovery (can still do this S-on)
As there is further access to these files there is a potentially higher risk of hard bricked device if not careful when playing around with these files you would have access to.
Had the Desire X quite early on from release date and have not S-OFF'd since (no need for me)
Will_Xda said:
That would probably suggest your dumber than a day 1 noob or you/ OP has not got the latest TWRP available for DX installed,which is quite important... duh.
This has worked for me numerous times when bouncing from various roms/ kernels on HTC desire X and sensation and is very similar to a zip supplied in quite a few viper rom threads that are used for the exact same purpose
Click to expand...
Click to collapse
sorry about the "duh", that was unnecessary.
im pretty sure i used the latest twrp at that time when i tried. the flashing process just didnt come to an end. so the "looping" assumption sounded accurate.
edit: yes, if you dont need supercid, s-off is pretty useless.
"normally" s-off its also usefull to deactivate the write-protection of the system-partition, but all custom kernels out there have some kind of hack to bypass this even with s-on.
Will_Xda said:
Looks Like your already S-ON buddy, S-OFF allows further access to the device so you can achieve things such as SuperCID and flash kernel's from recovery (can still do this S-on)
As there is further access to these files there is a potentially higher risk of hard bricked device if not careful when playing around with these files you would have access to.
Had the Desire X quite early on from release date and have not S-OFF'd since (no need for me)
Click to expand...
Click to collapse
yeah my phone is S-on, my mistake, was tired
i understand that S-off is permanent root (which i get with supersu) and supercid means i can flash other language roms?
i'm sticking to S-on and trying out different roms
thx again for help