Related
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
please help me! I tried to flash a new rom and after doing the 'fastboot flash boot boot.img' command it keeps restarting. The phone is booting to the lock screen and i can only see the wallpaper, and after 2 seconds it restarts.
Details please. What ROM did you flash and what ROM did you come from? What guide or method did you follow to install the new ROM? What backups do you have available? If none, then what is you CID and Mainver number to see someone has provided a nanadroid backup for you to use.
capusniac said:
please help me! I tried to flash a new rom and after doing the 'fastboot flash boot boot.img' command it keeps restarting. The phone is booting to the lock screen and i can only see the wallpaper, and after 2 seconds it restarts.
Click to expand...
Click to collapse
P.S. i tried to do nandroid restore, and a factory reset but it won't help
It could be because of incompatibility with the current system and/or userdata
Did you:
1) flash the right system.img for this boot.img. it should be provided with the ROM
2) do a factory reset / erase userdata
To install system you do:
Fastboot flash system system.img
To erase userdata:
Fastboot erase userdata
You can also send me the result of the logcat untill the device reboots if adb debugging is enabled
Can you specify also which ROM are you using
Sent from my Galaxy Nexus using xda premium
requiem11 said:
Details please. What ROM did you flash and what ROM did you come from? What guide or method did you follow to install the new ROM? What backups do you have available? If none, then what is you CID and Mainver number to see someone has provided a nanadroid backup for you to use.
Click to expand...
Click to collapse
i don't know what rom it had on it because the phone wasn't mine. I tried to flash http://forum.xda-developers.com/showthread.php?t=1745176
cid: htc_orang309
i saved the nandoid back up on computer
Verify djodjoni's suggestions and instructions. Post what you've learned.
I thought I recognized your username. You've posted recently. hboot 1.36 but ICS rom loaded, so you are looking for a jellybean rom that works with your new Hboot that some dodgy repair shop loaded. I take it you've opted for ViperX. Is this right?
requiem11 said:
Verify djodjoni's suggestions and instructions. Post what you've learned.
I thought I recognized your username. You've posted recently. hboot 1.36 but ICS rom loaded, so you are looking for a jellybean rom that works with your new Hboot that some dodgy repair shop loaded. I take it you've opted for ViperX. Is this right?
Click to expand...
Click to collapse
yes, and it was at the gsm because of the same problem, but previously it stopped at the htc logo
where i have to put the boot.img file to flash it? i want to be sure not to harm my phone even more
I'm not using the ViperX ROM, I'm actually using stock, but great instructions for flashing roms is available here:
http://forum.xda-developers.com/showthread.php?t=2069904
i flashed the rom but after the htc and venom boot animation it stops at the htc logo and not entering lock screen like earlier
Can somebody help me solve this problem?
Ur doing smth wrong. what exactly are you doing there? Step by step.
Also can you do adb shell?
yuhuu
i solved the problem. I found another cid orang309 nandroid back up and it worked!!!
when i tried to restore with my back up, where was the same problem. But now it works fine.
Also i had android version 4.0.3 which they installed at gsm repair, and it was laggy, but now i have 4.0.4 and works just fine)))
btw you don't know when we'll receive 4.1.2? because when i bought it, it had 4.1.2
Hi,
I'll try to be breif and to the point as much as possible.
I have upgraded to 4.2.2 using this ROM
However, my Hboot was at 0.95.0000, S-ON. I followed the instruction of the JBFWTOOL21 on youtube
So the ROM booted properly. But don't have any service. When I go to "About phone", my IMEI, baseband version and network are all "unknown". So I'm not sure what causing this issue.
I attempted to reflash my previous CM9 ROM, but it doesn't get in an infinite loading loop at boot.
I'm not quite sure what to do next.
Thx,
Gen
Have you still the same HBoot? You should upgrade your hboot if your cid allows it.
The new ROM‘s need Hboot 1.31 minimum
D4rk_nVidia said:
Have you still the same HBoot? You should upgrade your hboot if your cid allows it.
The new ROM‘s need Hboot 1.31 minimum
Click to expand...
Click to collapse
I went from HBoot 0.95.0000 to 1.33.0000.
My CID was HTC__621. The JBFWTOOL21 upgraded it during the process.
gentai said:
I went from HBoot 0.95.0000 to 1.33.0000.
My CID was HTC__621. The JBFWTOOL21 upgraded it during the process.
Click to expand...
Click to collapse
You flashed the corret boot.img or(it´s inside the zip)?
Fastboot>flash boot.img it>Recovery>flash ROM>Boot
But before you do that flash the newest TWRP 2.5
http://techerrata.com/file/twrp2/endeavoru/openrecovery-twrp-2.5.0.0-endeavoru.img
Fastboot.exe flash recovery openrecovery-twrp-2.5.0.0-endeavoru.img
Fastboot.ese erase cache
You can try to flash another ROM like SlimBean or something.
I had a similar process.
1. Flash ROM in recovery
2. Flash Gapps in recovery
3. Flash boot.img in fastboot
I just tried with SlimBean, but the radio state is still at Off. Here is the process that was done
1. Downloaded TWRP2.5 as you instructed
2. Download SlimBean 4.2.2 from their website
3. Flash TWRP2.5 using fastboot
4. Extracted SlimBean's boot.img from .zip
5. Flash boot.img using fastboot
6. Transfered ROM and Gapps
7. Flash ROM using recovery
8. Flash Gapps using recovery
9. Booted
Unfortunately, I still have no baseband and no network.
I have also access *#*#4636*#*# and set the network to "GSM auto". Didn't do anything
I have attempted with
CM9: cm_endeavoru-ota-eng.noeri-003
That also did not work. Since multiple CM10 ROM and 1 CM9 ROM failed, it's fair to conclude that the ROM version might not have anything to do with it. I'll try to change my approach and research about the radio and what can make the baseband screw up.
Alright, so I am feeling like the problem is because I flashed the wrong hboot. Now I'm trying to get 0.95.00 back onto it.
gentai said:
Alright, so I am feeling like the problem is because I flashed the wrong hboot. Now I'm trying to get 0.95.00 back onto it.
Click to expand...
Click to collapse
you can't get back older hboot....it should work all...did you really wiped completely ? factory reset, dalvik cache and cache? try also wipe system...and flash back if not try a custom kernel...repack it and flash it also the zip where the boot.img is inside...
Yep, I tried it again. After some more research, there are a few people that had the same symptoms. It appears that it is a hardware fault with the radio.
There are also other weird symptoms that happened even before I flashed Jelly Beans, such as battery draining, phone overheating, random system restart. That might support a hardware failure of some kind.
For now, I am using a HTC Desire as my backup phone. I'll do some more testing when I have time.
gentai said:
Yep, I tried it again. After some more research, there are a few people that had the same symptoms. It appears that it is a hardware fault with the radio.
There are also other weird symptoms that happened even before I flashed Jelly Beans, such as battery draining, phone overheating, random system restart. That might support a hardware failure of some kind.
For now, I am using a HTC Desire as my backup phone. I'll do some more testing when I have time.
Click to expand...
Click to collapse
In original development or so there is codecx who made a flashable zip for radio ...just try this...if it won't work try to do a factory reset over the bootloader
Gesendet von meinem HTC One X mit Tapatalk 2
One-X-master said:
In original development or so there is codecx who made a flashable zip for radio ...just try this...if it won't work try to do a factory reset over the bootloader
Click to expand...
Click to collapse
Would you have a forum thread. I only found mentions of it on XDA and Google. This was the only radio thread on XDA:
http://forum.xda-developers.com/showthread.php?t=2233949
Two days before the 4.2.2 version started rolling out for India, I had my phone rooted with CWM recovery installed. When i downloaded the new 4.2.2 update and tried to install it, the installation stopped after the phone rebooted into CWM recovery. I replaced the CWM with the default recovery, which put my phone's hboot version to 1.36.0000.
I did a factory reset and re-downloaded the upgrade. Now, during installation after reboot, the loading bar stops at about 25% and phone displays the red triangle with exclamation mark.
while looking for solutions, i came across this thread which has a stock recovery for 3.14. I installed it but the hboot version is still 1.36 after a fastboot reboot-bootloader
Will flashing stock recovery for 3.14 help?
menancer said:
Two days before the 4.2.2 version started rolling out for India, I had my phone rooted with CWM recovery installed. When i downloaded the new 4.2.2 update and tried to install it, the installation stopped after the phone rebooted into CWM recovery. I replaced the CWM with the default recovery, which put my phone's hboot version to 1.36.0000.
I did a factory reset and re-downloaded the upgrade. Now, during installation after reboot, the loading bar stops at about 25% and phone displays the red triangle with exclamation mark.
while looking for solutions, i came across this thread which has a stock recovery for 3.14. I installed it but the hboot version is still 1.36 after a fastboot reboot-bootloader
Will flashing stock recovery for 3.14 help?
Click to expand...
Click to collapse
Have you relock your bootloader?
It is relocked now. I'm trying to unlock it
I relocked the bootloader after reading somewhere that OTA upgrades need locked bootloaders.
I downloaded the update and ran it, Now I am getting a message below HTC logo: "this build is for development purposes only do not distribute outside of htc without written permission. Failure to comply may lead to legal action."
There is also a ***Security Warning*** message below the ***Relocked*** one.
Help!
menancer said:
Two days before the 4.2.2 version started rolling out for India, I had my phone rooted with CWM recovery installed. When i downloaded the new 4.2.2 update and tried to install it, the installation stopped after the phone rebooted into CWM recovery. I replaced the CWM with the default recovery, which put my phone's hboot version to 1.36.0000.
I did a factory reset and re-downloaded the upgrade. Now, during installation after reboot, the loading bar stops at about 25% and phone displays the red triangle with exclamation mark.
while looking for solutions, i came across this thread which has a stock recovery for 3.14. I installed it but the hboot version is still 1.36 after a fastboot reboot-bootloader
Will flashing stock recovery for 3.14 help?
Click to expand...
Click to collapse
You must to unlock your bootloader install stock ROM and Stock Recovery after this you can receive OTA. If you are not full stock you can't update via OTA. Everything must to be STOCK.
I got a nandroid backup from this thread: http://forum.xda-developers.com/showthread.php?t=1975140 for my CID (038), if i restore it via CWM (i'll have to flash CWM) for this, will that help?
menancer said:
I got a nandroid backup from this thread: http://forum.xda-developers.com/showthread.php?t=1975140 for my CID (038), if i restore it via CWM (i'll have to flash CWM) for this, will that help?
Click to expand...
Click to collapse
yes install nandroid backup via CWM. First flash CWM after this nandroid,flash boot.img and stock recovery.img. After this receive OTA
yes install nandroid backup via CWM. First flash CWM after this nandroid,flash boot.img and stock recovery.img. After this receive OTA
Click to expand...
Click to collapse
So let me confirm = CWM > Restore nandroid > boot.img > stock recovery img
correct?
menancer said:
So let me confirm = CWM > Restore nandroid > boot.img > stock recovery img
correct?
Click to expand...
Click to collapse
Yes, that's it
Just be sure that you flash the stock boot and recovery and DO NOT FLASH THE NEW HBOOT IN ANYWAY (TRYING MANUAL UPDATE METHODS! You can't downgrade the hboot and once upgraded, touch won't work in the recovery or the 4.1.1 ROM)
i'm not able to restore the nandroid backup using CWM, so i flashed the recovery and boot img...but now when i go to recovery, it shows me another CWM titled "yes-no adv-wipe recovery CWM based v6.0.2.7"...i really have no idea how it got there!
I have another HTC One X (belongs to my office), it is on 4.1.1 (just like mine is currently). My phone and this phone have everything in common except the build number and Kernel version.
The office HTC One X has the following -
build # 3.14.707.24
Kernel -
3.1.10-g1a2ac1c
[email protected] #1
SMP PREEMPT
mine has -
build #3.14.720.24
Kernel -
3.1.10-g62b3f63
[email protected] #1
SMP PREEMPT
menancer said:
i'm not able to restore the nandroid backup using CWM, so i flashed the recovery and boot img...but now when i go to recovery, it shows me another CWM titled "yes-no adv-wipe recovery CWM based v6.0.2.7"...i really have no idea how it got there!
I have another HTC One X (belongs to my office), it is on 4.1.1 (just like mine is currently). My phone and this phone have everything in common except the build number and Kernel version.
The office HTC One X has the following -
build # 3.14.707.24
Kernel -
3.1.10-g1a2ac1c
[email protected] #1
SMP PREEMPT
mine has -
build #3.14.720.24
Kernel -
3.1.10-g62b3f63
[email protected] #1
SMP PREEMPT
Click to expand...
Click to collapse
Becoz of you flashed recovery form nan backup, recovery changed but it's OK, you do full wipe before restore the nan backup, try with this recovery.
I'm receiving MD5 mismatch error when i try to restore the nan backup. I tried it after doing a full wipe.
On the other HTC One X that i have, there is no recovery i.e. the screen shows the red exclamation mark with red triangle.
I just came across this thread: http://forum.xda-developers.com/showthread.php?p=44480718 in post #2, the poster has suggested to get stock recovery and boot.img from http://forum.xda-developers.com/showthread.php?t=1546970 this thread (Android Revolution HD)
The boot and recovery versions are 4.18.401.2
my version is 3.14.720.24
menancer said:
I'm receiving MD5 mismatch error when i try to restore the nan backup. I tried it after doing a full wipe.
On the other HTC One X that i have, there is no recovery i.e. the screen shows the red exclamation mark with red triangle.
I just came across this thread: http://forum.xda-developers.com/showthread.php?p=44480718 in post #2, the poster has suggested to get stock recovery and boot.img from http://forum.xda-developers.com/showthread.php?t=1546970 this thread (Android Revolution HD)
The boot and recovery versions are 4.18.401.2
my version is 3.14.720.24
Click to expand...
Click to collapse
Re: Android Revolution HD; is not yours, nothing to do its.
Delete the nan backup in your device storage and put it again in device and try .
Well I tried copying nan backup again, but this time, the process stopped after erasing boot.img, and now the phone is stuck on the white HTC screen and wont go ahead.
menancer said:
Well I tried copying nan backup again, but this time, the process stopped after erasing boot.img, and now the phone is stuck on the white HTC screen and wont go ahead.
Click to expand...
Click to collapse
Try to flash boot.img form nan backup and reboot again.
did that...didn't work. i've given it to a local mobile repair store as i can't invest much time in this any longer
Thanks for all your help!
menancer said:
did that...didn't work. i've given it to a local mobile repair store as i can't invest much time in this any longer
Thanks for all your help!
Click to expand...
Click to collapse
If in the name of nand backup have space delete it or rename the nand to nandbackup.zip and try again.
the nandbackup name is this: 2013-06-22.08.11.45
This name format is used by CWM recovery for its backups.
menancer said:
the nandbackup name is this: 2013-06-22.08.11.45
This name format is used by CWM recovery for its backups.
Click to expand...
Click to collapse
try to rename to nand backup to nand only and flash the boot.img from nand and flash the nand again. MD5 you can get and for bad download try download again
It worked!
I just got my phome after a week of travelling through mobile repairs and HTC service centre.
I flashed the boot.img and recovery.img from the nand backup, Then restored the same backup from the CWM recovery. During the restore process, i got the error "error while restoring /sdcard/.android_secure" after which, the restoration stopped. Upon reboot, the phone started normally. Everything appears to be stock. I'm attaching images so that you guys can confirm it as well.
I got the stock recovery.img from this link: http://d-h.st/VIZ, worked properly this time.
Right now i'm downloading the OTA upgrade on my phone...let's see what happens this time.
Update: It worked!!!! though i locked the bootloader (fastboot oem lock) before starting the upgrade.
Thank you all for the help!!!
OK so sorry about my English.
I have my phone stuck. I was using the cyanogenmode 10.2.0 whit out any problems. then i accidentally update it via automatic update, and after updated it get stuck to boot loop. So i thought that i can fix it restoring my backup... But it get stuck on HTC intelligent screen. and no matter how long i wait it does not boot to android. I can get to bootloader (hboot 1.36.000) and recovery mode also (CWM 6.0.4.8) but i cannot flash any rom to the sdcard. The phone doesn't show up in my mac usb drives. I also tried to push the new .img file to the sdcard but the adb usb doesn't find any devices. i have try to put new boot.img but doesn't help anything.
So i need help here....
Thanks for the advices anyway.
Gesaco said:
OK so sorry about my English.
I have my phone stuck. I was using the cyanogenmode 10.2.0 whit out any problems. then i accidentally update it via automatic update, and after updated it get stuck to boot loop. So i thought that i can fix it restoring my backup... But it get stuck on HTC intelligent screen. and no matter how long i wait it does not boot to android. I can get to bootloader (hboot 1.36.000) and recovery mode also (CWM 6.0.4.8) but i cannot flash any rom to the sdcard. The phone doesn't show up in my mac usb drives. I also tried to push the new .img file to the sdcard but the adb usb doesn't find any devices. i have try to put new boot.img but doesn't help anything.
So i need help here....
Thanks for the advices anyway.
Click to expand...
Click to collapse
post the result from command fastboot getvar version-main
after this we will see what to do
Thant said:
post the result from command fastboot getvar version-main
after this we will see what to do
Click to expand...
Click to collapse
Ok so it give me this:
version-main: 3.16.69.3
finished. total time: 0.006s
Gesaco said:
Ok so it give me this:
version-main: 3.16.69.3
finished. total time: 0.006s
Click to expand...
Click to collapse
now if you don't have worranty Unlock your bootloader via htcdev.com after this flash Philz 5.15.9 recovery mount sd card find nandroid backup 3.16.69.3 copy to sd card and restore it after this you can flash stock recovery and update the phone
or flash custom rom
hmm..
Ok So i did all that and i find the phone as a storage drive. So i not find the old backup 3.16.69.3 so i cannot continue. I try to copy the old cm10.2 .0 but it just say: Installing update...
Installation aborted.
At the first time it said status 7 so i deleted the lines from the script. Doesn't help.
So i cannot flash a custom rom, not from the recovery. Didn't tried with console/fastboot...
Gesaco said:
Ok So i did all that and i find the phone as a storage drive. So i not find the old backup 3.16.69.3 so i cannot continue. I try to copy the old cm10.2 .0 but it just say: Installing update...
Installation aborted.
At the first time it said status 7 so i deleted the lines from the script. Doesn't help.
So i cannot flash a custom rom, not from the recovery. Didn't tried with console/fastboot...
Click to expand...
Click to collapse
install sense rom for now
did not help...
Thant said:
install sense rom for now
Click to expand...
Click to collapse
So i download this http://forum.xda-developers.com/showthread.php?t=2423735 and its start very good but after 15sec it boot and get stuck to "HTC quietly brilliant" screen...
I wipe data/reset factory settings and flashed new boot.img to this one. it still get stuck.
Gesaco said:
So i download this http://forum.xda-developers.com/showthread.php?t=2423735 and its start very good but after 15sec it boot and get stuck to "HTC quietly brilliant" screen...
I wipe data/reset factory settings and flashed new boot.img to this one. it still get stuck.
Click to expand...
Click to collapse
This rom is for evita/htc one xl. You need to use an endeavoru/htc one x rom
Sent from my One X using XDA Premium 4 mobile app
it works!!!!
So it really works!! After i tried to install this version for One X xl (i do have also try with same endeavoru version) and waiting for at least 30 min with the HTC screen, i decided to try the backup again. So back to recovery and give a shot. And it works!!! I assume that because this backup was made before i had install the Cyanogenmod it need the SENSE to work again. I thought that the backup was from the cyanogenmod but it was from time before it. So now i have it restored to rev.hd rom. Lot to learn about this world, lot of mistakes to make an try to fix them.... but when you finally get it right (with very good advice from good people) it's rewarding feeling.
Thanks everyone, lets try not to make that error again.:good:
When you get to bootloader check if it says evita or endeavoru
Sent from my One X using XDA Premium 4 mobile app
yes
Yes it do say that it is Endeavoru. I think that the real problem was that i did not flash the boot.img right. probably the .img file was different that the one i got. (10.2.0) Since the update came true OTA of Cyanogenmode (did i understand it right?) I should have flash the new boot.img from the 10.2.1 zip file via fastboot to get this work. I just assume...
Gesaco said:
Yes it do say that it is Endeavoru. I think that the real problem was that i did not flash the boot.img right. probably the .img file was different that the one i got. (10.2.0) Since the update came true OTA of Cyanogenmode (did i understand it right?) I should have flash the new boot.img from the 10.2.1 zip file via fastboot to get this work. I just assume...
Click to expand...
Click to collapse
Yes if the update have kernel change you must to flash every time boot.img from the update archive or rom archive we don't have S-OFF. But have one way to do this Check in Original section for Kernel Lighter it give the chance to flash boot.img via recovery and Aroma file manager but read all before try something