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
Related
Hello all, I've been a long time lurker around here, and I first want to thank all the devs for all their hard work in making this such a great device. In anticipation of a fully working ICS build in the near future, is there anything I need to do before flashing an ICS ROM? I'm currently running CM7 with HBOOT 0.57 with S-On. Do I need to get S-off in order to flash ICS, or can I just flash it as I would any new Gingerbread ROM? Also, what other, if any, benefit is there to obtaining S-off?
you are using CM7 but with S-On? i thought before rooting the phone, we need to s-off the first?
lokodoe said:
you are using CM7 but with S-On? i thought before rooting the phone, we need to s-off the first?
Click to expand...
Click to collapse
Rooting does not require to remove security (s-off).
S-off allows you to flash recoveries, hboots, radios via fastboot, which I think is classed as being safer than via recovery.
It also allows you write access to system while android is booted.
lokodoe said:
you are using CM7 but with S-On? i thought before rooting the phone, we need to s-off the first?
Click to expand...
Click to collapse
I originally had the old version of Froyo (or was it Eclair?) that came with the phone. This was before an update that made S-on prevent the installation of CWM. Back then, I was able to use the Unrevoked method to root and install clockwork recovery. I can't remember all the details, but needless to say, S-on with HBOOT 0.57 back then did not prevent root, CWM, or the flashing of ROMs, and possibly kernels. I've flashed new CM7 ROMs up to one that was stable and after the gps was fixed, so everything works fine. I believe I'm running CM nightly 184.
This is why I'm wondering if the installation process if different for CM9 than for CM7. I don't know if S-On will interfere with the new version of android.
Edit: Here is the thread for unrevoked that I followed way back when. http://forum.xda-developers.com/showthread.php?t=788737
DanGeorges said:
Rooting does not require to remove security (s-off).
S-off allows you to flash recoveries, hboots, radios via fastboot, which I think is classed as being safer than via recovery.
It also allows you write access to system while android is booted.
Click to expand...
Click to collapse
Sorry for my noobishness, but does this mean I can still flash an ICS ROM through my usual way in recovery? I remember reading somewhere that the flashing process for ICS is slightly different than Gingerbread ROMs. Also, I don't really care about being able to write to the system directory unless that has some advantage that I am unaware of.
Goodbye_Alltel said:
Sorry for my noobishness, but does this mean I can still flash an ICS ROM through my usual way in recovery? I remember reading somewhere that the flashing process for ICS is slightly different than Gingerbread ROMs. Also, I don't really care about being able to write to the system directory unless that has some advantage that I am unaware of.
Click to expand...
Click to collapse
Yes - you should be able to flash ICS without s-off.
DanGeorges said:
Yes - you should be able to flash ICS without s-off.
Click to expand...
Click to collapse
Alright. Thanks for clearing that up. I'll of course be sure to make a full backup and wipe everything before flashing ICS (I'm holding out until gps and camera are fixed because I use both quite freqently).
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
bjb_nyj101 said:
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
Click to expand...
Click to collapse
Try either viper rom or mean bean rom, both have instructions and a s-on kernel installer, just read the first 4 posts and follow the instructions to the dot... Good luck!
Sent from my EVO using xda app-developers app
jocarog said:
Try either viper rom or mean bean rom, both have instructions and a s-on kernel installer, just read the first 4 posts and follow the instructions to the dot... Good luck!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Thank you for the quick reply.
So is being S-ON the reason for this problem? Why is that?
Also, is it worth the trouble of me getting S-OFF? I don't want to brick my phone, and apparently that's possible with Rancun?
bjb_nyj101 said:
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
Click to expand...
Click to collapse
tl:dr version - No, but do it.
You don't NEED to be S-Off, but I STRONGLY suggest you do go S-Off. I was dev unlocked for a long time and it was a pain in my pants to do almost anything.
First things first, are you making sure to wipe everything before you flash? You need to make sure to wipe system, restore, and wipe caches before you flash. Every time, S-On or S-Off. No. Matter. What.
If you don't want to go s-off and that doesn't work, use an app called Flash Image GUI. It's a dollar and works wonders. I have no affiliations with the app or the dev, but it made my life a lot easier when I would flash. What you would do is browse for a kernel image (your rom), check Kernel Image, make sure the two boxes are checked at the bottom and flash the image. When that was done, you have to boot into your recovery and install your kernel again after wiping.
That worked for me every time.
mstrblueskys said:
tl:dr version - No, but do it.
You don't NEED to be S-Off, but I STRONGLY suggest you do go S-Off. I was dev unlocked for a long time and it was a pain in my pants to do almost anything.
First things first, are you making sure to wipe everything before you flash? You need to make sure to wipe system, restore, and wipe caches before you flash. Every time, S-On or S-Off. No. Matter. What.
If you don't want to go s-off and that doesn't work, use an app called Flash Image GUI. It's a dollar and works wonders. I have no affiliations with the app or the dev, but it made my life a lot easier when I would flash. What you would do is browse for a kernel image (your rom), check Kernel Image, make sure the two boxes are checked at the bottom and flash the image. When that was done, you have to boot into your recovery and install your kernel again after wiping.
That worked for me every time.
Click to expand...
Click to collapse
Yup, I'm definitely wiping every time.
So with Flash Image GUI, I flash my ROM with the app, reboot to recovery, then flash the ROM again?
You should get S-OFF to make your life easier, it's free and the easiest way is facepalm... Everything is in the original development thread, is real easy, and yeah your headache/bootloops are due to the need of flash the kernel separately, with S-OFF the process is easier and in one step... Venom team also has a kernel installer for s-on and it's free... Mean bean includes it for free but you have to follow the special instructions for s-on in the OP, good luck!
Sent from my EVO using xda app-developers app
I'm going to make this a lot easier than everyone else has been. No offence people.
DO YOU WANT TO BE HAPPY!? ARE YOU HAVING PROBLEMS IN THE BEDROOM!? IS WORK GETTING YOU DOWN!? FEAR NO LONGER!!!! WITH THE BEST DEVELOPERS ON THIS PLANET HERE TO PROVIDE YOU WITH ALL THE TOOLS YOU NEED TP SATISFY YOUR EVERY NEED! I PRESENT TO YOU: just S-OFF dude.
Enjoy.
Delakit said:
I'm going to make this a lot easier than everyone else has been. No offence people.
DO YOU WANT TO BE HAPPY!? ARE YOU HAVING PROBLEMS IN THE BEDROOM!? IS WORK GETTING YOU DOWN!? FEAR NO LONGER!!!! WITH THE BEST DEVELOPERS ON THIS PLANET HERE TO PROVIDE YOU WITH ALL THE TOOLS YOU NEED TP SATISFY YOUR EVERY NEED! I PRESENT TO YOU: just S-OFF dude.
Enjoy.
Click to expand...
Click to collapse
LOL you made me laugh... Get S-OFF or keep s-on and read a lot to get it to work... Is just an extra step on every single flash...
Sent from my EVO using xda app-developers app
bjb_nyj101 said:
Yup, I'm definitely wiping every time.
So with Flash Image GUI, I flash my ROM with the app, reboot to recovery, then flash the ROM again?
Click to expand...
Click to collapse
Yep - and in recovery just flash it like you would normal app wiping everything if I remember correctly.
Mnstrblueskies responses and verbage are confusing the situation. I'm fairly literate about this and his posts are making my head spin.
If you are S-on, the kernel doesn't get flashed. You need to use flash image GUI app or fastboot to flash the kernel (i.e.boot.IMG) before or after flashing ROM. Preferably before, I suppose. Or use the HTC dumlock feature in TWRP (I'm not real familiar, but instructions are in their op/thread) (I'm S-off).
The easiest way to update firmware/radios will require S-off. If you're already on the latest OTA (3.16), you'll have the latest touch panel drivers and will only be able to use sense 3.16 based ROMs, no AOSP or older sense. This can be remedied by getting S-off and downgrading your TP drivers.
Good luck
Sent from my EVO using xda premium
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
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Need to wait for hboot to be modded to have that removed
Wonders_Never_Cease said:
Need to wait for hboot to be modded to have that removed
Click to expand...
Click to collapse
Ah okay thanks. Wasnt sure if Hboot was universal or if it was by build.
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Wonders_Never_Cease said:
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Click to expand...
Click to collapse
I'm on build 2.22.401.5 running VenomOne rom, S-Off, rooted all the good stuff. Will your hboot mod work for mine?
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Wonders_Never_Cease said:
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Click to expand...
Click to collapse
OK and I can just install either one of those hboots over my existing one and it wont brick my phone or is this more to this?
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Wonders_Never_Cease said:
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Click to expand...
Click to collapse
Found it, thanks man. Gonna mess with it a little later.
CavyS said:
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Click to expand...
Click to collapse
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
thinkhope said:
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
Click to expand...
Click to collapse
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
CavyS said:
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
Click to expand...
Click to collapse
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
Click to expand...
Click to collapse
It was just easier for me to fallow a set of instructions going step by step than jumping around just to avoid 1 easy step.
thinkhope said:
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah still works, you might of read that Firewater for some people doesnt work on 4.4.3. For me Firewater worked and I'm S-Off for some people it doesnt and you have to use Sunshine in that case.
thinkhope said:
So the toolkit still works??
Click to expand...
Click to collapse
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
redpoint73 said:
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
Click to expand...
Click to collapse
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Click to expand...
Click to collapse
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
redpoint73 said:
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
Click to expand...
Click to collapse
I definitely did have the evita. Had to alter the cid to make htc dev believe it was a different phone or something like that, if I remember correctly.
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Well, sounds easy enough. I will be attempting later tonight after work. Thanks for all of your help. If it's OK, mind if I PM you if something goes wrong?
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Click to expand...
Click to collapse
S-off is needed to flash radio, hboot, SIM unlock, and some other things. But not for root or to flash ROMs. Pretty much similar to how things were on the EVITA; with the exception that boot.img will flash automatically along with the ROM (not possible on most hboots on the EVITA, and had to be flashed manually with fastboot).
It sounds like you are already on the "official" 2.23 software (Android 4.4.3) by OTA? If so, you don't need to update firmware (radio, hboot, etc.) as the OTA already updated it. Otherwise, s-off is needed to flash the firmware manually; which is pretty much required for any 2.xx Sense based custom ROMs (otherwise there will be serious bugs like very long boot times, broken WiFi, Bluetooth). While s-off is not strictly needed to flash the ROM (it will flash correctly) things just won't run right if firmware is outdated. This is the only reason you would "need" to have s-off for flashing ROMs. AOSP and GPE ROMs won't suffer this issue.
But if you are already on the new OTA, this isn't an issue for flashing any ROM. You can verify by looking at the hboot version and baseband. If you are on hboot 3.18 and baseband 1.19; your firmware is up to date, and won't be an issue for running any ROMs.
thinkhope said:
mind if I PM you if something goes wrong?
Click to expand...
Click to collapse
I actually prefer you just posting to the forums. Either to an existing relevant thread, or start a new one if a relevant one does not already exist.
Couple reasons for this:
- Info given to you can help others reading the forums, and benefit the community as a whole instead of being hidden away in PM
- You can get help from more than just one user. I don't claim to even remotely know everything, and often its helpful to have more than one set of eyes on a problem (especially the tougher ones). And I might not even be online to help.
In particular for the 2nd point: my wife and I are going to be having a baby, with scheduled induction tomorrow (Sept. 5) unless it happens by itself sooner. So I won't be available to help you when that happens, anyway!
In any case, good luck!