Related
I've done it again. I think I need to be stopped! lol
I had a perfectly fine phone running the original orange 4.1.1 software. I decided to root it or something and now I'm stuck on the white intro screen.
I can get into the hboot or whatever it's called by holding down power and vol down, but once in there everything I try just takes me back to the white screen.
Factory reset just takes me back to white screen
Recovery shows me a pic of my phone with a green arrow, then a red warning sign. Sometimes from there I can get into recovery (of sorts), but theres nowhere there for me to restore my backups
Any ideas? Thanks in advance
You should probably reflash CWM
TToivanen said:
You should probably reflash CWM
Click to expand...
Click to collapse
How can I load it in?
cblanc said:
How can I load it in?
Click to expand...
Click to collapse
did the fastboot flash recovery thing on the recovery file, it all seemed to work fine (although it only took 1.3 seconds.
I then did a fastboot reboot and it's stuck at the htc page again...
cblanc said:
did the fastboot flash recovery thing on the recovery file, it all seemed to work fine (although it only took 1.3 seconds.
I then did a fastboot reboot and it's stuck at the htc page again...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1859714
read it all the way through and follow all instructions,its a bit daunting at first.you can either use adb or there are a couple of tools on the dev page..
Hmm. I've been out for a few hours, left it on charge as when I tried the RUU it said I didn't have enough power. Now it wont start up at all....
They're is a thread somewhere that covers this problem,do a search for low battery stuck in recovery.
Sent from my EndeavorU using xda app-developers app
If you have enough power to flash this recovery
http://db.tt/K8Aoto6o
The phone charges if you leave it in this recovery
Or check this thread
http://forum.xda-developers.com/showthread.php?t=1658084
Excellent, it looks like I can now charge my phone. Hopefully once it's charged a while I can flash on a new RUU
HI all, I'm hoping I'm on the end stretch now lol..
I have a fully charged phone, but tried to install the RUU but it wasn't having any of it, saying that it was the incorrect version. I have the latest that was on the page (was about a month old) it's saying my image version is 3.16.61.6 and it wants to change it to 1.28.061.9, but then it can't
Any ideas? Cheers
Do these fastboot commands
Fastboot oem readcid
Fastboot getvar version-main
Post them here please
readcid - orang001
version main - 3.16.61.6
Thanks
Yes you need a ruu or a nandroid backup that starts with 3.16 with and orange cid ! You tried to downgrade he hboot with an older ruu and that is impossible due to not having S-OFF ......
I found this on another page, will that work do you think?
billd2439 said:
Hi Matt,
Here's the Orange UK Jellybean nandroid. Users will need the stock 3.16 recovery to complete the install
CID ORANG001 Firmware 3.16.61.6 Sense 4+ Baseband 5.1204.163R.30 build 3.16.61.6 CL 128187
https://www.dropbox.com/s/x7q0bkzv9hbnuqz/Orang001JB.rar
Should be clean with no personal info on it.
Bill
Click to expand...
Click to collapse
Sorry didn't see that one !!!! Its not in the OP yet ..... Yes use that one !!! That's exactly what you need !!!
Edit : I only checked the OP, but Matt is on holiday so the OP is not updated :thumbup:
Great stuff, do I still need to do all wiping and flashing of boot?
Cheers for this, you've been a great help
Yes do a full wipe and flash the boot.img from the nandroid with fastboot ! You got lucky mate
Lets hope so
Finally downloaded the ruu, don't want to do it wrong. What commands do I need to type?
Cheers
Its not a ruu .... its a nandroid backup and its probably a .rar file ... Unpack it and put it on the phones sd card looking like this
Sdcard\clockworkmod\backup\time and date folder\backup files
Copy the boot.img from those backup files to the fastboot folder
Flash it in fastboot usb mode
Fastboot flash boot boot.img
Fastboot erase cache
Enter the custom recovery and do a full wipe/factory reset and restore the nandroid backup from the menu backup & restore
Boot it up to see if its running !
Ah, see there's mu issue, the phone's still not getting past the HTC logo at the beginning. I can't get the backup on my phone can I?
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
my friend had rooted my ONEX created a backup . i am currently running ARHD want to back to stock to enjoy OTA update. bt the problem is that in the clockworkmod recovery there are two backups. i dnt knwo which one is of stock .
Try just restoring any one of the nandroid backups and check in settings to see if it is the right one. Nandroid backups don't take a long time to restore so don't worry.
Sent from my HTC One X using xda app-developers app
diamond225 said:
Try just restoring any one of the nandroid backups and check in settings to see if it is the right one. Nandroid backups don't take a long time to restore so don't worry.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
can u give me the steps on how to restore.. plss
Copy the boot.img from the nandroid backup and flash it with fastboot commands then do a full wipe in recovery and then restore the nandroid
Mr Hofs said:
Copy the boot.img from the nandroid backup and flash it with fastboot commands then do a full wipe in recovery and then restore the nandroid
Click to expand...
Click to collapse
i am noob and i am flashing it for the first time just want to ask i have to use fastboot commands in bootloader
do i need to flash the recovery ..?
juliethakkar90 said:
i am noob and i am flashing it for the first time just want to ask i have to use fastboot commands in bootloader
do i need to flash the recovery ..?
Click to expand...
Click to collapse
You have to flash the boot.img with fastboot commands and yes the phone has to be in the bootloader/fastboot usb mode
Then a full wipe in the custom recovery and restore the nandroid ! After that you check the phone works and that the rom is stock .....
Then you flash back the stock recovery to be able to update , because the custom recovery won't let you update officially !
I have it for you ... I just need the software number when you are done
Mr Hofs said:
You have to flash the boot.img with fastboot commands and yes the phone has to be in the bootloader/fastboot usb mode
Then a full wipe in the custom recovery and restore the nandroid ! After that you check the phone works and that the rom is stock .....
Then you flash back the stock recovery to be able to update , because the custom recovery won't let you update officially !
I have it for you ... I just need the software number when you are done
Click to expand...
Click to collapse
kk wil do in an hour. m just charging my phone.
juliethakkar90 said:
my friend had rooted my ONEX created a backup . i am currently running ARHD want to back to stock to enjoy OTA update. bt the problem is that in the clockworkmod recovery there are two backups. i dnt knwo which one is of stock .
Click to expand...
Click to collapse
You can prolly check the dates on both updates - worst case scenario just do another nandroid and try restoring both its just 2 options so your 50%-50%
Mr Hofs said:
You have to flash the boot.img with fastboot commands and yes the phone has to be in the bootloader/fastboot usb mode
Then a full wipe in the custom recovery and restore the nandroid ! After that you check the phone works and that the rom is stock .....
Then you flash back the stock recovery to be able to update , because the custom recovery won't let you update officially !
I have it for you ... I just need the software number when you are done
Click to expand...
Click to collapse
i did backup came back to my stock ROM
i did my veriosn is 1.29.751.12 wantt a recovery
No problem
http://db.tt/W5IJ8asG
Mr Hofs said:
No problem
http://db.tt/W5IJ8asG
Click to expand...
Click to collapse
Mr.Hofs i should flash this in bootloader and i should type
fastboot flash recovery Stock recovery 1.29.img ??
and thank you MR. hofs :good:
juliethakkar90 said:
Mr.Hofs i should flash this in bootloader and i should type
fastboot flash recovery Stock recovery 1.29.img ??
and thank you MR. hofs :good:
Click to expand...
Click to collapse
Yes that's correct, i dont know of the command accept spaces in the recovery name otherwise you have to rename the file to recovery.img
Fastboot flash recovery recovery.img
You know what i mean
You might want to rename it without the spaces, or maybe stick quotes around the filename, or use tab completion of the filename to properly escape the spaces.
BenPope said:
You might want to rename it without the spaces, or maybe stick quotes around the filename, or use tab completion of the filename to properly escape the spaces.
Click to expand...
Click to collapse
done ... and thank you both of you and is there a way to know i did everything correct..
If fastboot said success, it succeeded, if it said failed, it failed.
BenPope said:
If fastboot said success, it succeeded, if it said failed, it failed.
Click to expand...
Click to collapse
i went to the recovery and there is 3 green icons and 1 red icon.. ??
Explain a bit more the steps you took, is this happening while updating ? Or just entering the recovery from the bootloader ?
Mr Hofs said:
Explain a bit more the steps you took, is this happening while updating ? Or just entering the recovery from the bootloader ?
Click to expand...
Click to collapse
i jst went in to recovery from the bootloader ... thn i saw icons ..
No problem, just warning signs that you are entering a part we actually shouldn't
More important is :
Can you update now ? Check in settings info software
Mr Hofs said:
No problem, just warning signs that you are entering a part we actually shouldn't
More important is :
Can you update now ? Check in settings info software
Click to expand...
Click to collapse
i will update 2mrw morning (INDIA) and thank you ben :good:
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
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