Hi, so just yesterday i decided that I wanted to go back to my stock rom, so i read up and learnt that I needed to flash stock recovery to successfully install the OTA update. I was rooted and the update didnt work so I flashed the recovery image for sense 4.0. It then allowed me to update to sense 4.1. There was then a minor update, 1.28 mb i believe and after that i was able to download the Jellybean OTA. When I download the jellbean OTA and try to install it through my stock recovery however, it comes up with an error saying E: error in OTA_ENDEAVOR_U_JB_45_S_Optus_AU_3.14.980.27-2.17.980.6_release_299170pamoph3dsqv4al9a and then it comes up with an error saying error opening E:/sdcard/external or something like that. I really have no idea what the problem is, my phone is not bricked, im just stuck on sense 4.1. My software information is listed below
My HTC one X is an optus branded phone and its CID is OPTUS_001
android version- 4.0.4
htc sense version- 4.1
software number- 2.17.980.6
htc sdk api level- 4.2.3
kernel version- [email protected] #1SMP PREEMPT
baseband version- 2.1204.135.20
Any advice or help would be GREATLY appreciated, i cant find anyone else who has the same problem
Which recovery did u flash back .... With what number did it start with ?
Mr Hofs said:
Which recovery did u flash back .... With what number did it start with ?
Click to expand...
Click to collapse
it was a recovery for 2.17, i got it from here https://www.dropbox.com/s/wbav46spkbznovp/stock recovery 2.17.img
http://forum.xda-developers.com/showthread.php?t=2043818&page=2 the problem that is happening at the top of page 2 is exactly what is happening to me, do you know where I could find an RUU for optus?
Yeah that's the right one (my link)
Did you change anything to the rom when it was rooted .... removing apps/bloatware ?
Ow and you can't install an ota by yourself in a stock recovery so the error messagges are in place.
Did u try to check software updates in the settings menu of the phone again and try to install it again from there ?
Mr Hofs said:
Yeah that's the right one (my link)
Did you change anything to the rom when it was rooted .... removing apps/bloatware ?
Ow and you can't install an ota by yourself in a stock recovery so the error messagges are in place.
Did u try to check software updates in the settings menu of the phone again and try to install it again from there ?
Click to expand...
Click to collapse
OHHH i was worried that the error messages were meaning that my phone needed to be re-flashed or something i am redownloading the OTA update now and I will try and install it, i will re post when its done. I didnt remove any bloatware from the stock rom, it is completely stock, all that is changed is I updated it to sense 4.1 then there was a minor update that said it had a few bug fixes and some power improvements
:thumbup:
Mr Hofs said:
:thumbup:
Click to expand...
Click to collapse
i was also wondering if you might know, when i updated to sense 4.1, it completely wiped my "sd card", all my files were gone except from the default ones, was that meant to happen?
Euhm well i can't recall really, at least when i went from 4.0.4 to 4.1 it certainly did not wipe my sdcard.
And i can't really say if it wipes the phone blank because i updated from a clean stock rom without any extra apps on it
But beware the chance is big that it will indeed puts the phone to a stock JB rom
Mr Hofs said:
Euhm well i can't recall really, at least when i went from 4.0.4 to 4.1 it certainly did not wipe my sdcard.
And i can't really say if it wipes the phone blank because i updated from a clean stock rom without any extra apps on it
But beware the chance is big that it will indeed puts the phone to a stock JB rom
Click to expand...
Click to collapse
oh ok, no problem. So i just downloaded and attempted to install the OTA for jellybean, in the bootloader it got to about 1/4 then came up with the red triangle. I then pressed the volume up and power button and it showed me what happened, this is in order
finding update package...
opening update package...
verifying update package...
installing update...
copying fotaboot to /data/system for customize reload...
verifying current system...
assert failed: apply_patch_check("/system/lib/libGLESv1_CM.so". "edc4c7834196831836c73d0374529a0278c". a52756f5a63c9827632587d025ee28f67739bd97")
E:error in /interna;_sdcard/download/OTA_ENDEAVOR_U_JB_45_s_Optus_AU_3.14.980.27-2.17.980.6_release_299170pamoph3dsqv4a19a.zip
(status 7)
installation aborted.
Any ideas on whats the problem?
Hmm no don't know that error code, did you install some other boot.img (a custom one) like one with sweep to wake feature or such ?
It goes wrong at patching, so my guess its rom related
Can you do these fastboot commands
Fastboot getvar version-main
and
Fastboot oem readcid
Post them please.....
You van try this one more time, reboot the phone and check the download folder with a Explorer app like es file explorer. If there is the OTA file, delete it and try once more
Mr Hofs said:
Hmm no don't know that error code, did you install some other boot.img (a custom one) like one with sweep to wake feature or such ?
It goes wrong at patching, so my guess its rom related
Can you do these fastboot commands
Fastboot getvar version-main
and
Fastboot oem readcid
Post them please.....
You van try this one more time, reboot the phone and check the download folder with a Explorer app like es file explorer. If there is the OTA file, delete it and try once more
Click to expand...
Click to collapse
Ok my version main is 2.17.980.6 and my CID is OPTUS001, as for the boot image, it is the one that i used for my stock rom back when it was still sense 4.0
Another option is if it keeps on failing ! (Because i really am starting to think that the rom is not completely stock, wether you know it or not)
Download the corresponding nandroid backup here
http://forum.xda-developers.com/showthread.php?t=1975140
Its there i just checked.......
Flash back the custom recovery (this one)
http://db.tt/Krlm4dPs
Rename it to recovery.img and flash it with fastboot command
Fastboot flash recovery recovery.img
Fastboot erase cache
Then copy the boot.img from that nandroid and flash it also
Fastboot flash boot boot.img
Enter the recovery and do a full wipe, except sdcard
Mount the sdcard as a usb drive in the recovery and copy the nandroid to the phones sdcard looking like this
Clockworkmod\backup\date and time folder\backup files from the nandroid
Then restore the nandroid and reboot to check if the rom boots up ....
after that you flash the 2.17 stock recovery back and you can update again.
This way you are 100% stock ! :thumbup:
I'm off to bed now, going for a holiday but i will check in on how you are doing sometime in the morning......the last method i described can't go wrong ! When the update fails after that then there is something serious wrong with the phone or a longshot ..... the OTA from the carrier is corrupted somehow
Mr Hofs said:
Another option is if it keeps on failing ! (Because i really am starting to think that the rom is not completely stock, wether you know it or not)
Download the corresponding nandroid backup here
http://forum.xda-developers.com/showthread.php?t=1975140
Its there i just checked.......
Flash back the custom recovery (this one)
http://db.tt/Krlm4dPs
Rename it to recovery.img and flash it with fastboot command
Fastboot flash recovery recovery.img
Fastboot erase cache
Then copy the boot.img from that nandroid and flash it also
Fastboot flash boot boot.img
Enter the recovery and do a full wipe, except sdcard
Mount the sdcard as a usb drive in the recovery and copy the nandroid to the phones sdcard looking like this
Clockworkmod\backup\date and time folder\backup files from the nandroid
Then restore the nandroid and reboot to check if the rom boots up ....
after that you flash the 2.17 stock recovery back and you can update again.
This way you are 100% stock ! :thumbup:
I'm off to bed now, going for a holiday but i will check in on how you are doing sometime in the morning......the last method i described can't go wrong ! When the update fails after that then there is something serious wrong with the phone or a longshot ..... the OTA from the carrier is corrupted somehow
Click to expand...
Click to collapse
i did everything on the list, but when it boots up, it goes past the optus logo, then does that little HTC one x animation, then stays on theat screen
Then you didn't do a full wipe, did u also wiped the dalvik cache ?
And flashed the correct boot.img from the nandroid backup ? Did it confirm that flashing was oke
And for how long did u wait already, when it changed to that screen ? May take a while
You can't flash an OTA manually, you have to get it booting with the nandroid backup and then replace CWM with the stock recovery and then relock the bootloader to get the OTA (relock might not be needed but I would do it just in case)
EddyOS said:
You can't flash an OTA manually, you have to get it booting with the nandroid backup and then replace CWM with the stock recovery and then relock the bootloader to get the OTA (relock might not be needed but I would do it just in case)
Click to expand...
Click to collapse
Look 2 posts above and the 4th post
Mr Hofs said:
Then you didn't do a full wipe, did u also wiped the dalvik cache ?
And flashed the correct boot.img from the nandroid backup ? Did it confirm that flashing was oke
And for how long did u wait already, when it changed to that screen ? May take a while
Click to expand...
Click to collapse
ok, first i flashed the boot.img, then i did a factory reset from clockwork mod, then i wiped the cache partition, then i wiped the dalvik cache, i tried restoring it again, everything goes fine, but when i boot up it just does a bootloop, it seems theres something wron with the boot.img
Mr Hofs said:
Look 2 posts above and the 4th post
Click to expand...
Click to collapse
umm.........i just realised something..........what version of HBoot am i meant to have? or does it not matter? because mine is crrently 1.12 and ive been reading that for jellybean roms you need newer
Thats very strange ! One problem I had a while back was that the nandroid was not properly copied to the sdcard ! Can you check if the nandroid folder on the phone is the same size as the nandroid you downloaded to the computer. The nandroid actually restored itself but it also went in a bootloop......the guy was 2 days busy already to get it straight !!!
---------- Post added at 01:00 PM ---------- Previous post was at 12:51 PM ----------
When you are on HBoot 1.12 you can only flash ics roms, but i assume you are restoring the 2.17 based nandroid with the same cid as yours ? 2.17 is the ics based version that belongs to your hboot
Mr Hofs said:
Thats very strange ! One problem I had a while back was that the nandroid was not properly copied to the sdcard ! Can you check if the nandroid folder on the phone is the same size as the nandroid you downloaded to the computer. The nandroid actually restored itself but it also went in a bootloop......the guy was 2 days busy already to get it straight !!!
Click to expand...
Click to collapse
yep theyre both the same size :/ i was wondering would my bootloader have to be locked to get the OTA on my stock rom that was working? and also would trying out the RUU method http://forum.xda-developers.com/showthread.php?t=2054979 here be a good idea? that too says the bootloader should be locked
Related
Flashed android rev hd rom 12 now in boot loop!
I followed the guide and flashed the boot.img first but keeps on boot looping. I have flashed rooms before on previous android phones so have a bit of experience. My version number starts 2.17 maybe I am missing something.
Any help is much appreciated
Thanks
You need to flash the new firmware first. With that you need compatible CID.
If you don´t wanna flash the new firmware use ARHD 9.72.
Hello and thanks for the replies. I may of read the instructions wrong bit I thought it said flash boot img then run superwipe and then flash the rom from CWM. my cid is VODAP001 and wanted the jb Rom. Is 9.7.2 jb? I was thinking of going back to stock ruu but dont think it has been released yet as cannot find my version. When I rooted the phone when it was on stock I made a backup via Rom manager but even when I try to run this in CWM it states files not found!
Sorry to be a pain your help is much appreciated
Sent from my HTC One X using xda app-developers app
Sg231179 said:
Flashed android rev hd rom 12 now in boot loop!
I followed the guide and flashed the boot.img first but keeps on boot looping. I have flashed rooms before on previous android phones so have a bit of experience. My version number starts 2.17 maybe I am missing something.
Any help is much appreciated
Thanks
Click to expand...
Click to collapse
1+ me2 am in bootloop
Your phone is branded and therefore you cannot flash JB Sense ROMs, 9.7.2 is Ice cream sandwich.
u can have jb only when ur operator release it. what for official update from htc for ur model(cid)
now if u have backup of ur stock rom , just restore it. and if it is still bootlooping flash stock kernel modules.
mwanksh takes
faxel said:
u can have jb only when ur operator release it. what for official update from htc for ur model(cid)
now if u have backup of ur stock rom , just restore it. and if it is still bootlooping flash stock kernel modules.
Click to expand...
Click to collapse
thanks for your reply on this. I cannot restore my backup as when I enter CWM recovery either manually or by rom manager and locate the backup I have made it will not restore. When i try to restore it just states files not found!! I have checked on the phone SD storage and it is clearly there but for whatever reason it won't restore. Not sure what else I can do now. If I have to wait for my carrier Vodafone to release the official OTA jellybean update that's fine I will do that no problem, but how can I get back to stock rom? I have checked and there is no official RUU for my version yet so I cannot get back to stock and wait for the official OTA update even if I wanted too.
Maybe I am missing something i'm not sure but if you could help that would be much appreciated
thanks again
Dont Worry!
Just Go to Recovery and mount ur sd card.
Put Someother ROM(ICS) and its boot.img and flash that
aman360elite said:
Just Go to Recovery and mount ur sd card.
Put Someother ROM(ICS) and its boot.img and flash that
Click to expand...
Click to collapse
ya. just like he said if u have custom recovery download a rom like viperX and put it htcstorage (storage card),(Just Go to Recovery and mount ur sd card.)
remember to follow the instruction given by the rom devoloper in his rom thread (how to install rom)
aman360elite said:
Just Go to Recovery and mount ur sd card.
Put Someother ROM(ICS) and its boot.img and flash that
Click to expand...
Click to collapse
Hello
Thanks for your help. Just to clarify, I have the ARHD 9.72 (ICS) ROM on my SD card along with the superwipe that i was advised to run before flashing this ROM. With regards to boot.img it was advised to run this via fastboot type command before then running superwipe and then flashing the rom via CWM. Do i need to perform this boot.img via fastboot command before mounting the SD card and then flashing the ROM?
thanks
Sg231179 said:
Hello
Thanks for your help. Just to clarify, I have the ARHD 9.72 (ICS) ROM on my SD card along with the superwipe that i was advised to run before flashing this ROM. With regards to boot.img it was advised to run this via fastboot type command before then running superwipe and then flashing the rom via CWM. Do i need to perform this boot.img via fastboot command before mounting the SD card and then flashing the ROM?
thanks
Click to expand...
Click to collapse
before going to recovery u have to go fastboot and erase cache and flash the boot,img
phone hboot connect to pc
in pc using cmd type "fastboot flash boot boot.img"(u should keep ur boot.img in fastboot folder)
than type "erase cache"
than go to recovery and mount sdcard. copy rom to it. than flash it after full wipe
faxel said:
before going to recovery u have to go fastboot and erase cache and flash the boot,img
phone hboot connect to pc
in pc using cmd type "fastboot flash boot boot.img"(u should keep ur boot.img in fastboot folder)
than type "erase cache"
than go to recovery and mount sdcard. copy rom to it. than flash it after full wipe
Click to expand...
Click to collapse
thanks for the reply, i will try this yonight when i get home and reply back to you and let you know how i get on if that's ok? I am in work so don't have access to fastboot etc just my phone.
thanks
That's exactly what happened to me two days ago.. flashed the 12.0, then boot looped, then flashed the recovery but the stock rom boot looped too and my pc wouldn't recognize the phone so I adb pushed 9.7.2 and flashed it but it boot looped as well, so what I did was to download HTC SYNC and have the drivers, then flash boot.img first and then flash the rom, still didn't work so I tried the opposite - first flash the rom and only then flash the boot.img, and IT WORKED!!!!!
MaorSwan said:
That's exactly what happened to me two days ago.. flashed the 12.0, then boot looped, then flashed the recovery but the stock rom boot looped too and my pc wouldn't recognize the phone so I adb pushed 9.7.2 and flashed it but it boot looped as well, so what I did was to download HTC SYNC and have the drivers, then flash boot.img first and then flash the rom, still didn't work so I tried the opposite - first flash the rom and only then flash the boot.img, and IT WORKED!!!!!
Click to expand...
Click to collapse
hello, glad to hear it's not just me....and you got sorted out! I will have a go at this tonight. The only concern I do have now though is how I would get back to stock rom if needed to receive OTA Jelly bean update when it is released. I cannot find any RUU for my vodafone UK branded version 2.17 CID VODAP001
THANKS
aman360elite said:
Just Go to Recovery and mount ur sd card.
Put Someother ROM(ICS) and its boot.img and flash that
Click to expand...
Click to collapse
Hello
Just wanted to update you on this issue. I have tried again to restore from my backup saved on the SD card storage but no luck. I went into recovery and mounted the sd card but still whener i try to flash the backup i get 'no files found!'
I have managed to get ARHD 9.7.2 installed at the minute but would prefer stock to get h OTA update do you have any ideas please? I have checked the files in my backup and I have the following but just cannot restore the phone from this backup!
boot.img
nandroid.md5
recovery.img
cache.ext4.tar
data.ext4.tar
system.ext4.tar
Your help is much appreciated
Sg231179 said:
Hello
Just wanted to update you on this issue. I have tried again to restore from my backup saved on the SD card storage but no luck. I went into recovery and mounted the sd card but still whener i try to flash the backup i get 'no files found!'
I have managed to get ARHD 9.7.2 installed at the minute but would prefer stock to get h OTA update do you have any ideas please? I have checked the files in my backup and I have the following but just cannot restore the phone from this backup!
boot.img
nandroid.md5
recovery.img
cache.ext4.tar
data.ext4.tar
system.ext4.tar
Your help is much appreciated
Click to expand...
Click to collapse
Did you changed the name of the folder in any way ?
It must be clockworkmod\backup\the files ....
Verstuurd van mijn HTC One X
MarcelHofs said:
Did you changed the name of the folder in any way ?
It must be clockworkmod\backup\the files ....
Verstuurd van mijn HTC One X
Click to expand...
Click to collapse
hello and thanks for your reply, the details of the backup are as below
clockworkmod/backup/2012-10-30-22.50.49
hope this helps, maybe it's something simple i'm not doing as unsure.
thanks
Sg231179 said:
hello and thanks for your reply, the details of the backup are as below
clockworkmod/backup/2012-10-30-22.50.49
hope this helps, maybe it's something simple i'm not doing as unsure.
thanks
Click to expand...
Click to collapse
ANY help is much appreciated from you guys on this issue. It's doingy head in...got the back up files in CWM/backup folder on sd card i have seen them but cannot flash. CWM appears to show all the folders that are on the sd card so this looks like it is seeing the sd card but when tying to flash recovery I always get the 'file not found' error...everytime!
thanks again
Sg231179 said:
hello and thanks for your reply, the details of the backup are as below
clockworkmod/backup/2012-10-30-22.50.49
hope this helps, maybe it's something simple i'm not doing as unsure.
thanks
Click to expand...
Click to collapse
Ah oké sorry the folder name should be fine ! Somehow corrupted maybe
Verstuurd van mijn HTC One X
Hi All,
Been having issues with my HTC One X for the past week now and haven't been able to solve it via google or searching this forum, so was hoping one of you kind people can assist a bit.
I do apologise if this issue has already been posted and I missed it, if you can link me I'll be eternally grateful.
Basically, had a few issues annoying me with my HTC so wanted to stick a custom ROM on it. Did some searching about, eventually got a plan together to unlock and root it. All went fine, unlocked it (S-On still) got TWRP recovery on it (Chose this as the ROM I was looking at claimed to be not compatible with CWR) and was booted back into my stock droid.
First thing I did after a successful boot was to go back into recovery and make a full backup (I may have not ticked the Cache and _android.secure)
Played about with the phone again a bit, getting some of the apps back on as it had been wiped, then made a second backup (This one I know I ticked all the boxes for)
Next I tried putting CleanROM on, but could get past the white HTC screen boot loop, after various reflashing the Boot.IMG and clearing cache, so fired up TWRP and restored back to my second backup. All back to normal.
Used the phone as normal for a day or so then I tried flashing another ROM (ViperX) same thing as CleanROM (White HTC screen boot loop) and then went on to try Team Baked's ROM. Managed to get this working successfully, however the ROM was not to my liking and decided to go back to my stock backup. Here's where the issue started.
Now, when restoring the backup the phone boots as far as displaying my background and the status bar at the top, however I cannot pull the status bar down and the ring to unlock the phone with doesn't appear. It sits here for a few second and then reboots. Boot loop.
I've tried clearing cache, restoring various different ways and restoring the boot.img (though I'm not sure I have the right one) but nothing works.
The last variation I tried for restoring involved:
1. Clearing the phone via TWRP (System Restore/Clear Cache/Clear Davik/Clear System/Clear SD Card (heard this can cause issues)/Clearing Android.Secure in that order)
2. Reboot into recovery
3. Repeat step 1 (in case of locked files)
4. Reboot into Recovery
5. full restore (With MD5 check enable)
6. Clear Cache and Dalvik (Tried with just cache, also done Fastboot clear cache in another attempt)
7. Attempt to boot into OS.
As I mentioned earlier, I'm not sure if I have the right boot.IMG for my phone Model/kernal/other, to be honest I'm not entirely sure of the requirements. The details of my phone I've collected so far are:
Getvar version-main (Not sure if this is kernal or what) = 2.17.771.3
hBoot = 1.12.0000
radio = 2.1204.135.20H
CID = H3G_001
Basically, as far as I can tell from the masses of reading I've been doing, I won't be able to update to custom JB for a while so want to get back to my stock ICS and then OTA to JB when my carrier releases their version, then maybe sometime in the future when the ROM specific to my phone has been cracked consider switching to a custom.
on a final note, I've tried flashing both my backups, same result. I've also tried restoring the stock recovery and doing a system recovery with that. It appears to go through the motions (phone with green arrows? Also had the red exclamation mark, but only once of the 3 attempts) then reboots and it's still the same issue.
Thanks for reading through, any advice would be much appreciated. Used to love my phone but now can barely stand to look at it.
Cheers,
Sean
Ok, so I've now downloaded a different boot.img which should be for stock ics and after flashing that, then flashing stock recovery and doing a system restore via bootloader I will 50% of the time get the lock screen and when I unlock it I see the white HTC screen of the initial setup, then it sticks there a while and reboots. It also reboots after left at the lock screen.
To me this seems like it's doing a check or looking for a certain piece of software/file that's missing but is required to finish the start-up process. Anyone any ideas?
Even if someone can point me in the right direction for an RRU for my phone as football's RRU's seem to be the only one that has the one I need but as of 5 days before all this happened the site they're hosted on doesn't allow 500+MB downloads for free members
Cheers,
Sean
**EDIT** Just done a full device wipe then restored only the SYSTEM partition and manually flashed the boot, then when I restarted it sat on the white HTC on the device setup but eventually loaded up, allowed me to complete the device setup and then loaded into the OS. All seemed fine aside from the phone being stuck in turning off airplane mode. Rebooted it to see if that would clear it up and now I'm back to bootloops before the lock screen appears (I just get my background and status bar)
So you have a nandroid backup ! Then do this
Wipe all in recovery and i mean ALL except the sdcard obvious ! system,data,caches,dalvik cache...
Then boot back into fastboot usb mode and flash the boot.img from the nandroid. Taken with TWRP the boot.img is called something like
Emmc.boot.win (or at least similar to this)
You can flash this file with fastboot command
Fastboot flash boot name of the boot.img (.win in this case)
Then enter the recovery and full wipe if you didn't o that already !
Restore the nandroid and boot it up :thumbup:
Should work
Perfect! Thanks so much man, I never even thought to flash the .wim, thought it had to be .img. Just successfully booted fully back into my old system. Hopefully will stay stable the next hour or so but looking good!
Thanks again,
Sean
Need help!!!
I'm facing the same problem with my device, i have ulocked bootloader from HTCdev and flash TWRP recovery, was trying to flash Maximus but unfortunately after flashing Maximus in TWRP my device stuck on boot logo.
Hboot: 1.12.0000
CID: HTC__J15
version-main: 2.17.415.2
Please help.
Did you flash boot.img through fastboot?
Sent from my HTC One X
TToivanen said:
Did you flash boot.img through fastboot?
Sent from my HTC One X
Click to expand...
Click to collapse
Yes, the one came with Android_Fastboot_KIT_V12.x
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Mr Hofs said:
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Click to expand...
Click to collapse
Then, i have done the mistake there. Now, please guide me what i need to do to get out of this problem.
I have forget to mention my device still S-ON
Please guide, sorry for troubling.
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Mr Hofs said:
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Click to expand...
Click to collapse
Thank you so much.
No problem mate ! :thumbup:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Slaverty said:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Click to expand...
Click to collapse
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
sfawad81 said:
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
Click to expand...
Click to collapse
Yes.
Copy the boot.img from the backup to your PC (you can mount SD card as USB from TWRP), flash it:
fastboot flash boot boot.img
And restore backup from TWRP.
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Slaverty said:
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Click to expand...
Click to collapse
Thanks alot, got it back as it was before.
Need to clear a doubt; will I be able to update my device with the OTA, as my device is unlocked, S-ON & TWRP installed?
I hope so, I'm in the same boat as you. From what I've been reading, it should still be possible as long as you put back the stock recovery and relock the bootloader.
This website offers links to download the stock recovery
http://www.androidauthority.com/one-x-revert-stock-recovery-76854/
As for relocking the bootloader, I think the process is to run this command whilst in Fast Boot USB mode
fastboot oem lock
After it's run there should be a purple "RELOCKED" at the top of your bootloader menu.
Remember to flash the recovery BEFORE you relock the bootloader
You do not have to lock the bootloader, just the stock recovery is needed ....
Stock rom (out of the box stock)
Stock boot.img
Stock recovery
Here is the 2.17 based stock recovery for those who needs it
http://db.tt/U5CK4noo
Hello to everyone.
I was having custom ICS rom, when I found out that there is OTA to JB for my HOX. So I reverted to stock using RUU method and got the OTA update. I had the stock JB rom. I made the nandroid backup and wanted to flash custom JB rom (ViperX Rom). I unlocked my bootloader again, got custom recovery (CWM 5.8.4.0). Then I flashed the boot.img from the rom's zip package and erased cache. I made a full wipe using CWM. Then, using recovery I flashed the custom rom (Viper). The whole process went without any problems, but after rebooting I got stuck oh the white htc logo.
Reverting to stock using my backup ended up on the white logo again. I cannot flash any rom (tried Sense and CM roms) coz every time I got that f...g white screen.
My bootloader is unlocked, hboot 1.36, S-ON model. Custom recovery (CWM 5.8.4.0). I've been trying for four days to get my HOX back to life.
Can anyone, please help me with that.
I don't know what's wrong with your phone, but if you just want to revert back to your backed up ROM, try flash boot from your backup first, and then restore backup. Or try reinstall RUU, maybe...
Die you use the right command for flashing the boot.img ?
Fastboot flash boot boot.img
and NOT
Fastboot boot boot.img ?
TommY.KillER said:
I don't know what's wrong with your phone, but if you just want to revert back to your backed up ROM, try flash boot from your backup first, and then restore backup. Or try reinstall RUU, maybe...
Click to expand...
Click to collapse
I tried to flash the stock boot.img before restoring backup - with no luck
I cannot reinstal RUU, coz I cannot find one, ie RUU 3.16.69.2 (if I am right).
@Mr Hofs
Yes, I used the proper command: fastboot flash boot boot.img and erased cache. It seems that I do everything right, but I still get the bootloop.
Oke, so now the bootloader is unlocked ?
Re-copy the boot.img file from the nandroid folder to the fastboot folder...just to be sure
Flash it with fastboot command and enter the recovery
Then
Wipe data/factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then restore the nandroid again !
Sent from my HTC One X using xda premium
Mr Hofs said:
Oke, so now the bootloader is unlocked ?
Re-copy the boot.img file from the nandroid folder to the fastboot folder...just to be sure
Flash it with fastboot command and enter the recovery
Then
Wipe data/factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then restore the nandroid again !
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Did what you said. Still nothing
bartdeli said:
Did what you said. Still nothing
Click to expand...
Click to collapse
hmmm so all the steps are covered, could you do me a favour ? flash a new custom ICS rom from scratch....sounds stupid but i had a case a while back that had the updated hboot but also got several errors ....
Mr Hofs said:
hmmm so all the steps are covered, could you do me a favour ? flash a new custom ICS rom from scratch....sounds stupid but i had a case a while back that had the updated hboot but also got several errors ....
Click to expand...
Click to collapse
Hey, you are THE MAN. Seems to be working. I am on viper 2.6 now!!!
What now?
Give me your main version number
Fastboot getvar version-main
Sent from my HTC One X using xda premium
Mr Hofs said:
Give me your main version number
Fastboot getvar version-main
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
2.17.69.2 - I have that RUU if that's what you mean
Yes but the ruu is crap because you already have the 1.36 hboot. Try this
Do a full wipe again and get your 2.17.69 nandroid from here
http://forum.xda-developers.com/showthread.php?t=1975140
Restore it with its boot.img
Then flash back this 2.17 stock recovery
http://db.tt/U5CK4noo
And start updating again and again .....
Mr Hofs said:
Yes but the ruu is crap because you already have the 1.36 hboot. Try this
Do a full wipe again and get your 2.17.69 nandroid from here
http://forum.xda-developers.com/showthread.php?t=1975140
Restore it with its boot.img
Then flash back this 2.17 stock recovery
http://db.tt/U5CK4noo
And start updating again and again .....
Click to expand...
Click to collapse
OK. Will start tomorrow (or today in the morning, coz it's after midnight )
Thank you for your help so far.
No problem ! I hope to see some good news tomorrow
Sent from my HTC One X using xda premium
Mr Hofs said:
No problem ! I hope to see some good news tomorrow
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I cannot revert to stock recovery. I got an error: cannot load "recovery.img"
My command was fastboot flash recovery recovery.img. The file is in the fastboot folder.
When I was trying to get back to stock for the first time I also had that error. That is why I had to use the RUU to revert to stock.
What now?
did you rename my file to recovery.img ?
Mr Hofs said:
did you rename my file to recovery.img ?
Click to expand...
Click to collapse
yes
are you hiding extensions in windows for the filenames, so that it's not called
recovery.img.img ? seen that problem also before !
Mr Hofs said:
are you hiding extensions in windows for the filenames, so that it's not called
recovery.img.img ? seen that problem also before !
Click to expand...
Click to collapse
No, I do not hide the extensions. I can see the extensions for all the files.
My fastboot folder below.
Ow yeah i see, what could be the problem here ?!
Does the nandroid work ? Except for the stock recovery ?
Try this ... enter the recovery and wipe the cache partition and dalvik cache ....
Then reboot into the bootloader
Adb reboot bootloader (works when you are in recovery)
Keep the phone there and reboot the pc and try again .....
Mr Hofs said:
Ow yeah i see, what could be the problem here ?!
Does the nandroid work ? Except for the stock recovery ?
Try this ... enter the recovery and wipe the cache partition and dalvik cache ....
Then reboot into the bootloader
Adb reboot bootloader (works when you are in recovery)
Keep the phone there and reboot the pc and try again .....
Click to expand...
Click to collapse
yes, I am on stock with custom recovery.
That "adb reboot bootloader" shall I write in cmd in fastboot usb?
I cannot post in the original thread, so I have to post it here....I really like the ROM, but I am stuck at logo..
I pushed the boot.img, i installed the kernell, i did a full wipe/cash, flashed the ROM and I am stuck at the logo
Help?
Thank you!
Vorphs said:
I cannot post in the original thread, so I have to post it here....I really like the ROM, but I am stuck at logo..
I pushed the boot.img, i installed the kernell, i did a full wipe/cash, flashed the ROM and I am stuck at the logo
Help?
Thank you!
Click to expand...
Click to collapse
Just try everything all over again. You should be fine.
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
recovery
full wipe
flash ROM
choose full wipe in AROMA
[email protected]|-|oR said:
Just try everything all over again. You should be fine.
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
recovery
full wipe
flash ROM
choose full wipe in AROMA
Click to expand...
Click to collapse
Im at the 6th try right now Now its stuck at the HTC logo...does it have anything to do with the fact that I am using CLM recovery? Or am I having a old HBOOT?
Vorphs said:
Im at the 6th try right now Now its stuck at the HTC logo...does it have anything to do with the fact that I am using CLM recovery? Or am I having a old HBOOT?
Click to expand...
Click to collapse
What is your hboot version? It certainly has strong impact to it. Did you have any JB ROM before?
Watch out your battery, too!
P.S. did you mean CWM? It's the one I am using, too.
[email protected]|-|oR said:
What is your hboot version? It certainly has strong impact to it. Did you have any JB ROM before?
Watch out your battery, too!
P.S. did you mean CWM? It's the one I am using, too.
Click to expand...
Click to collapse
HBOOT is 0.95.0000, and yes I had JB ROM before. Battery is around 30% but its pluged in
P.S. Yes, CWM
Vorphs said:
HBOOT is 0.95.0000, and yes I had JB ROM before. Battery is around 30% but its pluged in
P.S. Yes, CWM
Click to expand...
Click to collapse
You must have had AOSP ROM! For Sense ROMs you must upgrade HBOOT (read OP in mwilky's thread)!
What is your cid (if you know it)? Or, try fastboot getvar version-main, to check it. This will indicate which RUU/nandroid you should get, if you want to upgrade.
Thank you! Ill get to it tonight
I am not able to update HBOOT
I got my CID and RUU, unlocked, installed the ROM but there are no OTA updates and the HBOOT is still 0.95, android 4.0...I tried to flash the zip for my CID 032 from here http://forum.xda-developers.com/showthread.php?t=1957376, but I cannot flash it from fastboot - i get "error cannot load firmware.zip unknown error"
Lock the bootloader, its needed before running the ruu and its needed for the firmware flash.
Mr Hofs said:
Lock the bootloader, its needed before running the ruu and its needed for the firmware flash.
Click to expand...
Click to collapse
I did the HBOOT update, im on 1.39 now, but after flashing CWM i cannot see that root "0" folder on my SD card, so i cannot flash the ROM...i tried via fastboot but i got an error, Now I see that I have S-ON, even though I already used the unlock_code...
Vorphs said:
I did the HBOOT update, im on 1.39 now, but after flashing CWM i cannot see that root "0" folder on my SD card, so i cannot flash the ROM...i tried via fastboot but i got an error, Now I see that I have S-ON, even though I already used the unlock_code...
Click to expand...
Click to collapse
S-ON doesn't have anything to do with your possibility to see SD card. Try in CWM "mount USB storage". That should work.
S-on stays that way. We dont have s-off. Enter the recovery and mount the sdcard as a mass storage device (usb drive) copy the Rom.zip to the root of the sdcard and flash it.
The option is in mounts and storage - last option
[email protected]|-|oR said:
S-ON doesn't have anything to do with your possibility to see SD card. Try in CWM "mount USB storage". That should work.
Click to expand...
Click to collapse
Already tried that, but still i only see a few folders there...the JBFWTOOL warned me that it could wipe everything But why is it still S-ON?
Because we don't have s-off....its not developed/hacked yet. And if everthing is deleted you need to install a new clean rom including flashing the boot.img file
Mr Hofs said:
Because we don't have s-off....its not developed/hacked yet. And if everthing is deleted you need to install a new clean rom including flashing the boot.img file
Click to expand...
Click to collapse
Got it! Used your method and it worked perfectly, ty! ROM is great, but it seems I have lost all my files from the SD-CARD...
That's the risk of flashing and not reading and backing up before
Mr Hofs said:
That's the risk of flashing and not reading and backing up before
Click to expand...
Click to collapse
Well, they said use titanium and i did, but somehow everything got wiped...maybe its still a issue with that root folder "0"?
If you can reach in that 0 folder .... It might still be in there
Mr Hofs said:
If you can reach in that 0 folder .... It might still be in there
Click to expand...
Click to collapse
I tried to find it but its gone My SD card is 99% empty so for sure everything is gone...
LE: hmmm...there is something weird here, if I check storage on my phone it says that the phone storage is almost empty, BUT App Storage is 4.90GB/6.76GB...wth is going one here?
Top bad. Sorry for your loss
Hello I bought my new HOX yesterday... as I flashed custom JB ROM I found out that my HOX is faulty (3,5 jack and g-sensor)... then I went back to stock from this topic
http://50.23.216.69/showthread.php?t=1546970
flashed ROM and reflashed stock recovery, in the end I relocked my bootloader... however I cant install OTA I get into stock recovery when its updating...
the reason why Im doing this is, that I dont want them to tell me something like "yeee you messed with your phone and you screwed it yourself, we wont take responsibility" or something like that...
Is that your true version number ?
Fastboot getvar version-main
Post it here please
version-main: 3.20.401.3
thanks for swift reply ^^
Oke flash this recovery and try to update again
http://db.tt/pO3jumMa
If it fails report back, then we get you a stock nandroid backup.
sadly it failed again
btw I have my own stock nandroid "2013-08-10.13.41.17_JRO03C", but im not sure what version of the recovery should I flash then... or do you think will be better to use your nandroid?
Use your stock nandroid then. Flash the recovery.img and boot.img from the nandroid, restore it and then flash back the 3.14 stock recovery.
okay and one more question, now I know that I have to flash boot.img after flashing ROM, is this the same with recovery.img ? Or did I just understand you wrong now?
I mean ...
restore nandroid
fastboot flash boot boot.img
fastboot flash boot recovery.img (or not?)
flash 3.14 recovery
try OTA
No,
Do it like this then :
Flash boot.img from the nandroid backup folder :
Fastboot flash boot boot.img
Fastboot erase cache
Then full wipe in recovery and restore the nandroid. Then flash the stock 3.14 recovery
Fastboot flash recovery recovery.img
Fastboot erase cache
Dont relock the bootloader until you are certain you are full stock
oh my god... im such a ... I did wrong... i coppied my backup to wrong directory (clockworkmod/xxxx.xxx.xxx.xxx) and there should be another folder clockworkmod/backup/xxxx.xxx.xxx.xxx .... awwwwwww! I already deleted everything... Mounting USB storage from CWM doesnt seem to work... do you have any idea what can I do now? There should be a way via fastboot maybe mhm?
Oke do this :
Flash this recovery first
http://db.tt/SPXdFfPw
After that you mount the sdcard as a mass storage device, it may take a while before it pops up in windows ! May take a minute or so .....
Then unpack this nandroid backup to the sdcard, and specific folder (i packed the folder tree)
Then flash the boot.img from my nandroid backup to be sure its the correct one and restore my nandroid backup.
Then flash back the stock 3.14 recovey again and try to update again
I have PhilZ Touch 5 already, do you mean to use Aroma File Manager?
it says no clovkworkmod/aromafm/aromafm.zip ... so maybe i need to flash it first
Reflash the philz recovery. Can't hurt .....
http://db.tt/BBiLrMPm
My stock backup.
Inside recovery you go to mounts and storage and then tap the last option in the list (mount as mass storage) then wait until it pops up as usb drive on the pc !
well nope, i still cant get that connection via recovery... damn, thats one big downside of not having an microSD slot :/
It works....i know it does. Mass storage works in that recovery.
Wait long enough, give it time to mount as a mass storage device !
This is what you need to see. Mount usb storage !
figured out that I had to install newer version of MTP device drivers it works now... ahaha :victory: okay mate, you had been soooo helpfull and kind, thanks a lot! I will do what you said earlier and hopefully I will get full stock
Keep me posted
yeeeees I think we got there buddy! non rooted stock nandroid number 3.20.401.3, no updates available for me... I think we are ready to relock that son of a phone!
Did you updated the phone once from 401.1 to 401.3 ?
nope, I just restored my stock so I guess it was on latest version... so I guess the problem was because I was flashing wrong stock version (from that topic i posted earlier)