As I have noticed, many users on this forum have problems finding the right recovery for their phones hboot. Therefore, I decided to clarify a few things and sort the existing recoveries here again.
First of all, if you want to install a recovery, you have to determine the hboot version of your Desire X. To do that, you first shut down your phone, then you hold volume down button and press the power button at once to get into bootloader. There, you can verify the version.
The following is really important:
For hboot version 1.24 and below, you need a recovery made for ICS (Android 4.0).
For hboot version 1.25 and above, you need a recovery made for JB (Android 4.1).
Here I'll list the recoveries again so you can easier distinguish which one you need.
Recoveries for ICS:
http://forum.xda-developers.com/showthread.php?t=2099513 (TWRP, Look for the download for ICS hboot, which is discontinued)
http://forum.xda-developers.com/showthread.php?t=2278346 (Official CWM)
http://forum.xda-developers.com/showthread.php?t=2075212 (neXus Recovery, based on CWM)
http://forum.xda-developers.com/showthread.php?t=2296517 (PhilZ Touch, CWM based, just use ICS version)
Recoveries for JB:
http://forum.xda-developers.com/showthread.php?t=2099513 (TWRP, just use latest version, for now it is 2.6.3.0)
http://forum.xda-developers.com/showthread.php?t=2296517 (PhilZ Touch, CWM based, just use JB version)
http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66 (neXus Recovery, based on CWM - fixed version for JB by atis112)
That's it for now. If you need help on anything, post here please rather than starting a random Q&A thread; me and others can help much quicker then. If you need help, be sure to provide us with your hboot version.
If you find something I should add here, please let me no.
Some background info for users who want to know more about our hboot versions:
In the official JB update from HTC, the partition table from our hboot got changed. Before, we got 4 MB for boot partition (on ICS); we now have 16 MB for boot partition. Main reason for this is that the kernel for JB is bigger than 4 MB so the partition needed more space. But instead of just increasing the size of boot partition and resizing the other partitions accordingly, HTC changed the whole table so the device numbers have changed now. That's the reason for the mess with the recoveries for ICS or JB, because if you install a wrong recovery, you get ROMs installed to the wrong partition and backups / restores will malfunction.
Here is the partition table for JB (output of cat /proc/emmc):
Code:
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 00c7f600 00000200 "recovery"
mmcblk0p27: 00fffc00 00000200 "boot"
mmcblk0p24: 3bdffe00 00000200 "system"
mmcblk0p26: 0f000000 00000200 "cache"
mmcblk0p25: 4cfffe00 00000200 "userdata"
mmcblk0p28: 017ade00 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p31: 46800000 00000200 "fat"
mmcblk0p29: 00011c00 00000200 "extra"
If someone would be so nice to provide me with the output of "cat /proc/emmc" on ICS, it would be really nice if he or she shoot me a PM so I can update this post, because I dont have it anymore (as I'm using JB like most users here). Thank you!
For me JellyBean TWRP Recovery 2.5 is more stable than 2.6...
I'm using 2.6 for quite a time now, no problems so far. But 2.5 is linked above too, it's in the same thread as the 2.6 one, so users can choose.
When I get home today, I'll put some background info about hboot in second post like partition tables, etc.
Second post updated. Hope this helps...
Hi i have GB h-boot 1.25 and stable TWRP 2.6.0.3 everything work fine ex. Dalvik cache when i swipe cache i have "Dalvik failed"
Wysłane z mojego HTC Desire X przy użyciu Tapatalka
Try TWRP 2.5.0.0 for JB. I never experienced issues with the 2.6.0.3, but it may be different for other people as few members here have this problem.
Here is one more recovery http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66
mefistoreyon said:
Here is one more recovery http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66
Click to expand...
Click to collapse
Added to the list, thanks. When I did the guide, it was late in the evening and I remembered this one, but was too lazy to track the link...
dansou901 said:
Added to the list, thanks. When I did the guide, it was late in the evening and I remembered this one, but was too lazy to track the link...
Click to expand...
Click to collapse
No problem, I just use it from long time , but i dont see it anywhere except the link that i post.But it works good :good:
BTW good guide, there is aways one user that asking about that :good:
rooting htc desire x
dansou901 said:
As I have noticed, many users on this forum have problems finding the right recovery for their phones hboot. Therefore, I decided to clarify a few things and sort the existing recoveries here again.
First of all, if you want to install a recovery, you have to determine the hboot version of your Desire X. To do that, you first shut down your phone, then you hold volume down button and press the power button at once to get into bootloader. There, you can verify the version.
The following is really important:
For hboot version 1.24 and below, you need a recovery made for ICS (Android 4.0).
For hboot version 1.25 and above, you need a recovery made for JB (Android 4.1).
Here I'll list the recoveries again so you can easier distinguish which one you need.
Recoveries for ICS:
http://forum.xda-developers.com/showthread.php?t=2099513 (TWRP, Look for the download for ICS hboot, which is discontinued)
http://forum.xda-developers.com/showthread.php?t=2278346 (Official CWM)
http://forum.xda-developers.com/showthread.php?t=2075212 (neXus Recovery, based on CWM)
Click to expand...
Click to collapse
hey, so i started rooting my device (htc desire x) and i am done with unlocking the bootloader....i have been following this link(http://forum.xda-developers.com/showthread.php?t=2316662) ...but now i am stuck on the 2nd step ,it says 'Once you update via OTA for the JB Update, Your HBoot becomes JB Hboot instead of the old ICS Hboot so you need a JB Hboot compatible Custom Recovery to flash the Super User and Root'
i dont know what that means..my device has hboot 1.25 version ...is it necessary to have jb hboot version before moving onto the 2nd step??????
please help..
thanks in advance...
1.25 is JB HBOOT
havv said:
1.25 is JB HBOOT
Click to expand...
Click to collapse
thank you
Need help to install custom rom for hboot 1.15
dansou901 said:
As I have noticed, many users on this forum have problems finding the right recovery for their phones hboot. Therefore, I decided to clarify a few things and sort the existing recoveries here again.
First of all, if you want to install a recovery, you have to determine the hboot version of your Desire X. To do that, you first shut down your phone, then you hold volume down button and press the power button at once to get into bootloader. There, you can verify the version.
The following is really important:
For hboot version 1.24 and below, you need a recovery made for ICS (Android 4.0).
For hboot version 1.25 and above, you need a recovery made for JB (Android 4.1).
Here I'll list the recoveries again so you can easier distinguish which one you need.
Recoveries for ICS:
http://forum.xda-developers.com/showthread.php?t=2099513 (TWRP, Look for the download for ICS hboot, which is discontinued)
http://forum.xda-developers.com/showthread.php?t=2278346 (Official CWM)
http://forum.xda-developers.com/showthread.php?t=2075212 (neXus Recovery, based on CWM)
http://forum.xda-developers.com/showthread.php?t=2296517 (PhilZ Touch, CWM based, just use ICS version)
Recoveries for JB:
http://forum.xda-developers.com/showthread.php?t=2099513 (TWRP, just use latest version, for now it is 2.6.3.0)
http://forum.xda-developers.com/showthread.php?t=2296517 (PhilZ Touch, CWM based, just use JB version)
http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66 (neXus Recovery, based on CWM - fixed version for JB by atis112)
That's it for now. If you need help on anything, post here please rather than starting a random Q&A thread; me and others can help much quicker then. If you need help, be sure to provide us with your hboot version.
If you find something I should add here, please let me no.
Click to expand...
Click to collapse
Hi dev, I've hboot 1.15, android 4.1.1, flashed official CWM for ICS for ViMiRo rom. Followed each steps exactly as mentioned in the XDA threads for DX. Once the installation gets finished and rebooted, I'm struch with HTC logo screen. Pls guide me to resolve this.
Chethan012 said:
Hi dev, I've hboot 1.15, android 4.1.1, flashed official CWM for ICS for ViMiRo rom. Followed each steps exactly as mentioned in the XDA threads for DX. Once the installation gets finished and rebooted, I'm struch with HTC logo screen. Pls guide me to resolve this.
Click to expand...
Click to collapse
You're sure it is 1.15 and not 1.25? I don't remember version 1.15...
Chethan012 said:
Hi dev, I've hboot 1.15, android 4.1.1, flashed official CWM for ICS for ViMiRo rom. Followed each steps exactly as mentioned in the XDA threads for DX. Once the installation gets finished and rebooted, I'm struch with HTC logo screen. Pls guide me to resolve this.
Click to expand...
Click to collapse
Just post ONCE and only at APPROPRIATE place. You should not be posting the same thing again and again everywhere u feel like
ur query shall be answered at one place where you post and wont get unnoticed.
Thank You.
My hboot version is 1.15
YouWeThink said:
Just post ONCE and only at APPROPRIATE place. You should not be posting the same thing again and again everywhere u feel like
ur query shall be answered at one place where you post and wont get unnoticed.
Thank You.
Click to expand...
Click to collapse
Sorry about that, was bit desperate to get solution. My hboot version is 1.15 pls check the attachment. Waiting for your solutions
As you have S-ON, you need to flash a JB kernel with size lower than 4 MB. Otherwise it won't fit on the boot partition of that old hboot. Just flash the kernel via fastboot. I think there was an old version of Infinity kernel which fitted on that partition, take a look in Original Development section.
dansou901 said:
As you have S-ON, you need to flash a JB kernel with size lower than 4 MB. Otherwise it won't fit on the boot partition of that old hboot. Just flash the kernel via fastboot. I think there was an old version of Infinity kernel which fitted on that partition, take a look in Original Development section.
Click to expand...
Click to collapse
dualsim, dont bother.
Related
Hello Everybody,
Mine is a GSM EVO 3D WITH s-on. Currently I am have cyanogenmod with nothing working except calls, music and sms. I did not notice the fact that i had to s-off before installing cyanogenmod. Also before I installed cyanogenmod, I made a backup of my rom using ROM manager v5.0.2.0. Then after I installed cyanogenmod, it got stuck in a boot loop, I tried to restore my backed rom using bootloader. It did not restore because there CWM version mismatch I guess between v5 and v4. [In ROM manager, cwm is showing v5.0.2.0 but in bootloader it is v4.0.3] I got a error telling that system.img not found while trying to restore ROM. i BADLY NEED TO RESTORE MY ROM. How can I restore my backup? The files in my backup are as follows:
.android_secure.vfat
boot.img
cache.ext4
data.ext4
nandroid.md5
recovery.img
system.ext4
Should I be converting the cwm v5 files to v4?
Also I needed the stock kernel file. Help me regarding this.
Is this the stock kernel file?
Hi,
I found this link. Is this the stock kernel file? It was mentioned "Based On HTC Evo3D GSM ICS Source 3.0.16"
Code:
https://github.com/Coolexe/shooteru-ics-crc-3.0.16-e733189/downloads
Please help me regarding this. Which rom can I use for S-ON device
Your problem is more than likely a kernel one. When you flash roms with a s-on device it won't flash the kernel that came with it. They do not have access to the boot partition unless you flash through fastboot after you install the rom. Same goes for backups. To solve your problem manually flash 4ext recovery through fastboot. This recovery has smart flash which allows you to flash kernels through recovery. Then you gotta find a compatible rom for s-on devices. Check through the gsm dev section. Some roms and kernels do not play nice with s-on. Hboot neither. Check to make sure your rom is compatible with your current hboot. Aosp roms usually don't play nice with newer hboots so keep that in mind.
Please hit the thanks button if I helped you. It's 100% free.
Hi,
Thank you for the reply. But The problem is I am unable to access Android Market or use the internet on my cyanogenmod that is currently installed. What is the alternative??
Jsparta26 said:
Your problem is more than likely a kernel one. When you flash roms with a s-on device it won't flash the kernel that came with it. They do not have access to the boot partition unless you flash through fastboot after you install the rom. Same goes for backups. To solve your problem manually flash 4ext recovery through fastboot. This recovery has smart flash which allows you to flash kernels through recovery. Then you gotta find a compatible rom for s-on devices. Check through the gsm dev section. Some roms and kernels do not play nice with s-on. Hboot neither. Check to make sure your rom is compatible with your current hboot. Aosp roms usually don't play nice with newer hboots so keep that in mind.
Please hit the thanks button if I helped you. It's 100% free.
Click to expand...
Click to collapse
Do you have the right radios flashed for your rom?
Hi,
I am not sure about what radios mean. I just tried installing cyanogenmod on a S-ON device and got stuck in a bootloop, later when it managed to pass the boot screen, I was not able to access any of the features other than call, sms and music.
What Should I do?
Jsparta26 said:
Do you have the right radios flashed for your rom?
Click to expand...
Click to collapse
Radios are based off of the firmware software that governs all the the network and phone call modules. Having older firmware may cause problems for certain roms. Check to see if you have the latest. You can do this by searching for PG86IMG radios in the gsm dev section based on what country that phone is based on. Make sure you rename the file PG86IMG in all caps and place it on the root of your sdcard. Boot in into bootloader and let your phone detect and update. Make sure your relock bootloader first through fastboot on your computer. Fastboot oem lock is the command. You may have to start all over but at least your phone will be working again. My next suggestion is to gain s-off before you flash cyanogenmod again. You can look through the stickys in gsm dev section for the root guide. S-off will solve your problem and you will give functionality to your Rom. Good luck
What will happen when I flash these radios? What is the next step?
Jsparta26 said:
Radios are based off of the firmware software that governs all the the network and phone call modules. Having older firmware may cause problems for certain roms. Check to see if you have the latest. You can do this by searching for PG86IMG radios in the gsm dev section based on what country that phone is based on. Make sure you rename the file PG86IMG in all caps and place it on the root of your sdcard. Boot in into bootloader and let your phone detect and update. Make sure your relock bootloader first through fastboot on your computer. Fastboot oem lock is the command. You may have to start all over but at least your phone will be working again. My next suggestion is to gain s-off before you flash cyanogenmod again. You can look through the stickys in gsm dev section for the root guide. S-off will solve your problem and you will give functionality to your Rom. Good luck
Click to expand...
Click to collapse
Hey folks, this is urgend!
Why? Well, I wanted to do my girlfriend a favour and root her device and did so successfully, but it seems I cannot boot into any real ROM. The only ROM that successfully booted was the unofficial port of CM9. I uninstalled it because I would like to flash a daily driver for her. And that was when I tried fulmix.ROM as well as mySENSEdx+ v3. Here is my setup:
* TWRP 2.5 (official release)
* Formatted with SuperWipe JB
* Unlocked bootloader
Issues; When having flashed the ROM and installed boot.img through fastboot, all I get is a blackish screen, the device reboots every 5 minutes. Strange: I seem to not be able to perform a factory reset through TWRP. It always tells me that either cache or another smaller partition is inaccessible. Did I miss something while rooting? Any recommendations as how to solve this freaking issue will be REWARDED!
You are using the wrong recovery for your hboot. Your hboot version seems to be 1.25, but you are using a recovery made for hboot 1.24 and below. So go in Android Development Section and download TWRP for JB, flash that via fastboot and ROM installing as well as factory reset should work again.
1. Your main problem is the recovery. Don't use the official release but use the one for JB hboot from this thread : http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2
2. In order to make sure that recovery is correct for your device, make sure you do have a 1.25 hboot (boot to bootloader and recheck that)
ckpv5 said:
1. Your main problem is the recovery. Don't use the official release but use the one for JB hboot from this thread : http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2
2. In order to make sure that recovery is correct for your device, make sure you do have a 1.25 hboot (boot to bootloader and recheck that)
Click to expand...
Click to collapse
Thank you so much! To anwer your questions:
1. Will flash it ASAP after work. Is SuperWipe JB correct if want to flash your ROM?
2. It definately is. Would you Please tell me why the official TWRP will not work? Just curious..
SecUpwN said:
Thank you so much! To anwer your questions:
1. Will flash it ASAP after work. Is SuperWipe JB correct if want to flash your ROM?
2. It definately is. Would you Please tell me why the official TWRP will not work? Just curious..
Click to expand...
Click to collapse
1. Superwipe is not necessary. Just select wipe and do swipe to factory reset in TWRP is enough.
2. The official one is based on old files before JB is released to DX (e.g official TWRP for One X for the latest JB 4.2.2 hboot 1.73, touch is not working because it is based on old files)
ckpv5 said:
1. Superwipe is not necessary. Just select wipe and do swipe to factory reset in TWRP is enough.
2. The official one is based on old files before JB is released to DX (e.g official TWRP for One X for the latest JB 4.2.2 hboot 1.73, touch is not working because it is based on old files)
Click to expand...
Click to collapse
Everything is working good now. Any chance of an updated TWRP or 4EXT?
SecUpwN said:
Everything is working good now. Any chance of an updated TWRP or 4EXT?
Click to expand...
Click to collapse
Latest we have is TWRP 2.6.3.0, and it will probably be the latest for a while
GtrCraft said:
Latest we have is TWRP 2.6.3.0, and it will probably be the latest for a while
Click to expand...
Click to collapse
Does it work with Desire X without any issues?
SecUpwN said:
Does it work with Desire X without any issues?
Click to expand...
Click to collapse
No problems at all
GtrCraft said:
No problems at all
Click to expand...
Click to collapse
Can you help me here, please?
SecUpwN said:
Can you help me here, please?
Click to expand...
Click to collapse
Why don't you just flash a recovery and install rom from there.
Because flashing a recovery results in a "signature error" - means no recovery is flashable. This phone is not even able to get S-OFF yet, guess this is since the ROM itself is "corrupt" due to the HBOOT downgrade. Or am I getting this wrong?
Maybe... If I recall it correctly, the revolutionary scripts first interaction with the phone requires adb which isn't possible through bootloader. Do you have the stock recovery installed and can you boot into it? If yes, maybe adb can access your phone from there. If this is possible, try to run revolutionary from within the recovery...
dansou901 said:
Maybe... If I recall it correctly, the revolutionary scripts first interaction with the phone requires adb which isn't possible through bootloader. Do you have the stock recovery installed and can you boot into it? If yes, maybe adb can access your phone from there. If this is possible, try to run revolutionary from within the recovery...
Click to expand...
Click to collapse
That's the point: This phone doesn't have a recovery and flashing one is not possible. That's why flashing a complete RUU is trivial here. Are you able to find the adequate 1.22 RUU as a ZIP zo be flashed through fastboot?
Do you have the download link for the appropriate RUU? I can then extract it for you and load it up again, but I don't know which file you need exactly, as there are many RUUs on AndroidRuu...
dansou901 said:
Do you have the download link for the appropriate RUU? I can then extract it for you and load it up again, but I don't know which file you need exactly, as there are many RUUs on AndroidRuu...
Click to expand...
Click to collapse
Thank you so much! You'll find it here.
SecUpwN said:
Can you help me here, please?
Click to expand...
Click to collapse
I've got you covered friend
Sent from my C525c using Xparent Skyblue Tapatalk 2
Please help. I have unlocked this phone through HTC Dev. I have flashed a custom recovery. Somewhere through this process, the original installation of the factory rom from VM was deleted. That doesn't bother me because I was never going back to it anyway, but If I had it right now, I wouldn't be here. I have tried to use the RUU exe in fastboot and the RUU zip in recovery from here. Neither will install, exe throws errors and the zip returns [bad]. I have also tried the [ROM] NegaLite-BluRom-JCFunk | 2.95 | Sprint/VM | Sense/Apex/Nova | 03/25/2014. This eventually installed, but will not boot even with installing boot.img separately. I followed all directions to the best of my ability, but by no means am I saying I did correctly, but I am pretty sure I did. So to recap - I have whats in the title, but no rom whatsoever installed that can be accessed. Any takers?
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Click to expand...
Click to collapse
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
oD33z said:
Before I proceed in explaining anything, please let me Thank You JCFunk for lending me a hand in my endeavors. This is my first crack at a HTC device. So I'm a newb at locks, hboots, and HTC specifics. So, Thank You!
I scanned through a lot of information and I moved to quickly, thinking I would ace this project and not particularly following a guide step by step. I know I should just wire trick this phone. I am wanting to get to hboot 1.40 and use Revolutionary to S-OFF. Once that is achieved load a kitkat rom. This is just a project, not used for daily phone use - no service.
I tried this step first and it returned:
Main Version is older.
Update Fail!
Press <POWER> to reboot.
Would I be correct to say if I flashed the SetMainVersionLOW.zip that this method would likely work?
Also, if I am overcomplicating this(other than wire-trick) and there is an easier method, please advise.
D33z
Click to expand...
Click to collapse
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
Philz recovery not working well for 3d, I use 4ext or my unofficial twrp.
Click to expand...
Click to collapse
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
oD33z said:
Does your unofficial twrp support SELinux? I am assuming it does but just checking. Is it available for download and if so where?
Click to expand...
Click to collapse
here's the thread
http://forum.xda-developers.com/showthread.php?t=2831444
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
jcfunk said:
How good are you with linux, or do just use windows? Never did wire trick myself, I've always done Unknownforce hboot downgrade. Which I can now do in about 15 min.
s-off not required, there's many way to bypass unlocked limitations.
Your main var is to high because htc never released a current ruu, so the ota pushed version higher but no ruu to match.
what can I help you do?
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Click to expand...
Click to collapse
I am great with linux, but was under the assumption it needed to be burned to cd and that USB was not an option, please advise if not the case. I have read a ton and I remember reading about Unknownforce, but cant remember if thats the case or not.
Off topic: I learned from you that it has to be locked to go stock, but does it need to be unlocked to flash your rom or locked as well?
Unlocked for custom, locked for stock.
Here is unknownforce ultimate tool,
there was a live cd version made for windows users scared of linux.
I use tiny core linux for this, Ubuntu tries to mount all the partitions and you only have a 5 second window when they are writeable. I have used Ubuntu, at first, but preferred tinycore.
But first you are going to need to get stock.zip to install.
http://forum.xda-developers.com/showthread.php?t=1653777
I would do fastboot boot recovery.img
Then install negalite, so atless you can boot the phone
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------
here is 4ext recovery I would use this one first until you get used to things, best recovery for 3d.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
oD33z said:
Is 4ext > TWRP unofficial? I am currently on your unofficial TWRP and installing the latest negalite.
Click to expand...
Click to collapse
did you fastboot boot?
There are several custom recoveries out there.
Here is thread for 4ext
http://forum.xda-developers.com/showthread.php?t=1408936
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
What I meant was, in your opinion, is the 4ext a better recovery than the unofficial TWRP?
During the install of Negalite at the point of -Setting Up Kernel Over-Clock Settings
under this it reads: assert failed: write_raw_image("/tmp/newboot.img","boot")
Is this a red flag of something not going right in any way?
After this I click Next>Recovery>Wipe Dalvik>Reboot and it boots into Fastboot. Whats happening at this point?
Since I am basically starting from scratch and the end goal is to have a kitkat rom and possibly S-OFF(if its a must to do so).
What all needs to be done as far as formatting, tweaks, or anything else to achieve the best performance, space, or anything you can think of?
Thats if you dont mind sharing. I appreciate your time and if I can be of service to you in any way, I will.
I am currently on the 4ext recovery with 1GB sd-ext 0 swap and formatted Ext4.
fastboot boot recovery.img
flashrom.zip from recovery
reboot, wipe dalvik, reboot
Negalite.zip installed with no errors whatsoever.
Thank You.
Beautiful smooth running rom btw.
Does all that above sound like I did the right things as for setting up and installing?
4ext is most stable, the unofficial has new features like f2fs and selinux, but 95% stable.
fastboot boot recovery.img is an old work around, also used to flash boot.img with fastboot. That is ok with roms that include a whole boot.img but roms like mine use a dynamic boot.img. Basically the installer makes the boot.img using your choices.
From what I know about Kitty kat I think you need to downgrade hboot or be s-off. Not sure I've stayed on ics for stability because I still use this phone. Also there is a new version of negalite on svn, just takes hours for me to upload a zip version.
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
Revision 7
Are you sure this is the latest?
oD33z said:
Revision 7
Are you sure this is the latest?
Click to expand...
Click to collapse
Lol, yes since I updated it a few weeks ago
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
I should have worded that different really, the revision numbers threw me, I honestly was just making sure I was in the right place. 48mb smaller, anything stripped?
jcfunk said:
Some more info please, hboot version? Which recovery. s-on makes things harder.
To flash stock need to be relocked, stock will not flash from recovery.
If you put rom.zip, stock zip, in root of sdcard and rename to PG86IMG.zip. hboot will flash automaticly.
Or if you have a copy of the custom recovery img file on your computer, you can do a fastboot command that will let you boot from it and give it full write access.
fastboot boot recovery.img, then you can retry to flash negalite
img must be in directory you use fastboot in.
Click to expand...
Click to collapse
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
oD33z said:
I tried installing your new negalite the same way as I do the old version and at the end of the install procedure I get an error about set permissions. After that - reboot, wipe dalvik, reboot - it just reboots into recovery. I tried many times with SmartFlash enabled and disabled. I go back and install r121 with no problems.
Click to expand...
Click to collapse
Here. Try this
https://www.androidfilehost.com/?fid=23578570567720169
Sent from my DOWNGRADED EVO 3D, remember all development is done on my phone, not a computer
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