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....
Related
Ok I just got finished watching the NOOB video. I looked, & searched & looked some more for the answer to my question, but as you see I am still having to ask it..
I have been rooting, (& even bricking) phones since Nexus 1, Most of the time i just read forums and find any problems that get me stuck. The problem I'm having now has to do with Flashing new Kernels
Ok so the details. I have a Sprint Evo 3D, I rooted my phone when i got it. Since then i have not been able to put a new kernel on my phone. I have installed several different ROMs trying to fix this but still nothing. I am currently running Warm two-point-three, but I cannot change the kernel from what was on my phone before the past 3 roms i installed. I have tried Kernel manager. Flashing from recovery, & flashing from a root manager. But yet still no new kernel. I even used a format all zip and still am not able to change the kernel.
( side note. I have not been able to turn on my Wi-Fi either. Im not sure if it has anything to do with the kernel but im pretty sure it does seeing as how the past 4 ROMs i put on my phone did the same thing. )
sorry about the length but i just wanted to be as specific as i could
Thanks
I would take a wild guess and say you are on HBOOT 1.5 and have to flash through fastboot. There are seveal threads on flashing HBOOT 1.5.
schmeggy929 said:
I would take a wild guess and say you are on HBOOT 1.5 and have to flash through fastboot. There are seveal threads on flashing HBOOT 1.5.
Click to expand...
Click to collapse
Yes sir i am. I used to flash the same way on my Evo 4G without having to fastboot. Did i do something wrong or is there a way that i can flash kernel straight from my phone with out having to be at a computer to fastboot????
either go to CMDA or GSM development section and search for how to flash with HBOOT 1.5. there are video tutorials to help as well.
If on CDMA go here:
http://forum.xda-developers.com/showthread.php?t=1306248
schmeggy929 said:
either go to CMDA or GSM development section and search for how to flash with HBOOT 1.5. there are video tutorials to help as well.
If on CDMA go here:
http://forum.xda-developers.com/showthread.php?t=1306248
Click to expand...
Click to collapse
Thank you. I used your advice and did find this.
"If you have hboot 1.5 you have to use flashimage gui made by joeykrim on the market. It's a easy app and it safley flashes it for hboot 1.5 users since we still have s-on"
I hope this helps other people as well. (it does cost .99)
no problem hope it works out. Hear that flashgui app works great and makes flashing rom/kernels easy.
aprater118 said:
Ok I just got finished watching the NOOB video. I looked, & searched & looked some more for the answer to my question, but as you see I am still having to ask it..
I have been rooting, (& even bricking) phones since Nexus 1, Most of the time i just read forums and find any problems that get me stuck. The problem I'm having now has to do with Flashing new Kernels
Ok so the details. I have a Sprint Evo 3D, I rooted my phone when i got it. Since then i have not been able to put a new kernel on my phone. I have installed several different ROMs trying to fix this but still nothing. I am currently running Warm two-point-three, but I cannot change the kernel from what was on my phone before the past 3 roms i installed. I have tried Kernel manager. Flashing from recovery, & flashing from a root manager. But yet still no new kernel. I even used a format all zip and still am not able to change the kernel.
( side note. I have not been able to turn on my Wi-Fi either. Im not sure if it has anything to do with the kernel but im pretty sure it does seeing as how the past 4 ROMs i put on my phone did the same thing. )
sorry about the length but i just wanted to be as specific as i could
Thanks
Click to expand...
Click to collapse
To tie up any lose ends you might have in the logic between flashing on the EVO and flashing on the EVO 3D with HTC's unlock method, I've provided a fairly detailed answer previously in a few posts on here so I'm going to quote. Feel free to ask any other questions you might have if the details don't add up.
http://forum.xda-developers.com/showpost.php?p=18793336&postcount=2
The WiFi error is caused by a mismatch between the WiFi module and the currently loaded kernel. The WiFi module is stored in /system/lib/modules/bcm4329.ko . The kernel is stored in the boot partition.
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The result is the kernel module for WiFi is loaded but the kernel itself is not loaded. This creates a mismatch between a WiFi module loaded from the ROM and the matching kernel not being loaded as HTC does not allow it to be loaded from the traditional recovery boot method.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues with the EVO 3D on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
Click to expand...
Click to collapse
Thanks alot guys. It did help alot & I have been going really deep into it lately... (that what she said yea yea lol) anyway. The app does still have bugs when trying to flash a new recovery img for some reason so i did still have to use fast boot for that.
@joeykrim, From that last post you obviously know alot of the inside of the roms. More specific the locations & what the different files do. I have another question about file specifics if you can help that would be great. Ill send you an email.
aprater118 said:
Thank you. I used your advice and did find this.
"If you have hboot 1.5 you have to use flashimage gui made by joeykrim on the market. It's a easy app and it safley flashes it for hboot 1.5 users since we still have s-on"
I hope this helps other people as well. (it does cost .99)
Click to expand...
Click to collapse
Yep just use flashimage gui from the market and you are all set. Otherwise you need to use adb from a USB cable which is a drag.
have you tryed the g u i app from the market it will flash flashes kernal's also
Wow wrong thread
Typed by ---- oh wait! I'm schizophrenic!
[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.
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
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.
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