Related
I was a newbie, and i didn't take a backup from my stock rom, and i couldn't find it at all as it was "1.29.709.12" so with help of a friend of mine we managed to install ARHD 7.1.0 instead.
and after a while i decided to install CyanogenMod9 Beta1, so i toke a CWM 5.8.4.0 recovery backup and installed it and everything was fine, then i came across an unleashed cm9 v18 which has more fixes and i installed it, but the BT was not working at all, so i managed to get back to the backed up CM9 but the same problem occurred and the BT is not working at all, it doesn't even wanna change the on/off button.
so i tried to revert to the ARHD 7.1.0 and i restored it but it loops in quietly brilliant screen, i used aa super wipe patch and i installed it again and the same behavior happening, looping and looping
now the only rom that opened up is the "IceCold build 7"
please guys advice me what shall i do, every time i clear cash, I install the proper boot.img, wipe data/factory reset, and wipe cash partition. then whats wrong with my steps? why it doesn't work?
I advise you to stop fuking about and learn before you play.... its kind of like school but its more expensive.
crsnwby said:
I advise you to stop fuking about and learn before you play.... its kind of like school but its more expensive.
Click to expand...
Click to collapse
thanks for your advise, i promise i won't play again, but what about the this situation am in? any recommendations, tweaks, that can solve my problem will be really appreciated.
i need to get back to my stock or at least to be able to install a sense custom rom like the ARHD.
please guys help, please just give me any solution for this.
Relock flash ruu for phone and start again from begining this should sort your issue out
Sent from my HTC One X using xda app-developers app
dryan433 said:
Relock flash ruu for phone and start again from begining this should sort your issue out
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
the problem is that my RUU is "1.29.709.12" which is not exists at all, it looks like my phone is the only one world wide that has this RUU
is there anyway to flash another RUU without having "ERORR: 155"?
The RUU doesn't do anything special, it just wraps it up into a nice easy to use package. There must be quite a few threads and hundreds of posts explaining how to fix this.
Off the top of my head, quite possibly wrong.
Unlock.
Flash recovery
Flash boot.img
Fastboot erase cache
Superwipe
Flash Rom
Flash modules.
Relock
Search and you'll find.
im puzzled, why didnt u full wipe every restore?
After flashing boot image, did you do fast boot erase cache
Sent from my HTC One X using Tapatalk 2
hi i rooted my htc desire about one year ago and i installed a MUI Rom and since then i have not added another rom.
now i am trying to install the new roms cool droid and other but im having problems. i install the rom and it says it has been successful but when i reboot the htc it stays stuck at the htc logo forever. how long should it take. i know a new roms takes about 5-10 mins to start up but it shouldn't take upto an 1hr to start.
i would appreciate some help. thanks, adal316
Did you full wipe before flashing a rom? Did you flash sd-ext dependent roms without having an ext partition?
hi friend. thanks for your reply and help. much appreciated.
ive done the full wipe. but i did not do this '' flash sd-ext dependent roms without having an ext partition? ''
how would i go about do this
adal316 said:
hi friend. thanks for your reply and help. much appreciated.
ive done the full wipe. but i did not do this '' flash sd-ext dependent roms without having an ext partition? ''
how would i go about do this
Click to expand...
Click to collapse
You can partition your SD card from Recovery (depends on what type of recovery you use though)
Are you also sure you are using the right hboot?
im using clockworkMod recovery v5.0.2.0
im sorry about this but what do you mean using the right Hboot. its been a very long time since i last installed a ROM and ive forgot quite a bit so really would appreciate your help here.
Hello.
Try to tell us more information, which roms are you trying to install? Besides cool droid. Try to be more specific.
You said, you did a full wipe. That means factory reset + wiping data+wiping dalvik. Correct?
About the HBOOT thing. Try to boot into bootloader(volume down + power button), you can see the HBOOT number and version there.
Im no expert on rooting, but in the recent days ive reflashed lots of differerent roms. many roms did not boot, most likely reason was wrong rom for my phone. (i needed room for HTC Desire "Bravo")
i might be wrong, but it seemed to me that the different roms needs different recovery.
with my current setup im able to run cm but not miui. i was able to boot that one with another recovery that did not work with cyanogenmod.
i currently using CM10.1 VJ Jelly Bean 4.2.1 v4.5.
--Revolutionary-
Bravo PVT4 SHIP S-off
Hboot-6.93.1002
Radio-5.11.05.27
recovery:
CWR v5.8.0.2
hope this helps getting you a working rom.
when i go into bootloader this is what shows up
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
im trying to install sense 4.0 4.1 ROMS. yes when im doing the full wipe im wiping the cache partition and data factory reset then i am installing the new ROM. ROM get successfully installed but when htc desire reboots it stays stuck on the htc logo. please help
That happened to me when using stock hboot, but when i used cm7r2, the rom booted fine. Don't know why.
That's right, try flashing cm7r2 hboot,as abaaaabbbb63 said and I suppose it should be working fine.
Btw. My recommendation is.
Don't bother flashing 4.x.x ROMs for Desire. I don't think any of them are as good (I mean, smooth, without bugs, etc.) as the GB roms. Desire is now an "old" phone, you don't really need 4.x.x, instead of that, try flashing for example MildWild roms, (the one in my signature for example). You can get very nice performance, and a little 4.x.x look, which is probably why you're experimenting with 4.x.x ROMS
hey I had the same problem with my galaxy note then i formatted the SD .Then the problem was solved.
Ok
Sent from my Desire HD using xda app-developers app
another help
Like somebody sayed, for parandroid cm7r2 HBOOT is required.
So go to alpharev.nl download cm7r2- flash it trought Android Flasher.
Go to Recovery--full wipe--Flash ROM.
first boot need 10-15 min
htcsfragg said:
Like somebody sayed, for parandroid cm7r2 HBOOT is required.
So go to alpharev.nl download cm7r2- flash it trought Android Flasher.
Go to Recovery--full wipe--Flash ROM.
first boot need 10-15 min
Click to expand...
Click to collapse
Parandroid?
U mean paranoidandroid? If so that requires stock hboot. The rom they talking bout is cool droid. And if its the CoolDroid Revolution they talking bout then i wouldnt even bother flashing it, its bad, no offence to the dev but its slow, laggy, full of bugs. If its the old CoolDroid by coolexe then that rom is great all round.
Right
jmcclue said:
Parandroid?
U mean paranoidandroid? If so that requires stock hboot. The rom they talking bout is cool droid. And if its the CoolDroid Revolution they talking bout then i wouldnt even bother flashing it, its bad, no offence to the dev but its slow, laggy, full of bugs. If its the old CoolDroid by coolexe then that rom is great all round.
Click to expand...
Click to collapse
Yes man i didnt read well.
You are right, i will recommend you to full/wipe/ Format microSd-->Again Full/wipe--->Clear/Cache+Dalvik and then flash rom.
OFC Flash stock hboot before all this. :laugh:
At the moment it's on a bootloop with the HTC screen, although I've managed (just now) to flash CM10 which is now stuck on a loop of the CM10 Android splash screen
I'm feeling confident that this can be sorted as I can access phone through fastboot/adb and can mount the SD so all isn't lost... I'm on UK O2 HOX
Just looking for a little direction, I used to be fairly confident around the inside of my old HTC desire, but lost interest... Things are rather different with the HOX and I suspect I've maybe screwed up with some misguided bravado...
Mr Hofs has provided some excellent learning material on his responses to issues similar to mine but to no avail...
I've tried a lot of things, bootloader is unlocked, flashed boot.img and recovery.img but when I flashed x.xx.206.x - O2 UK (United Kingdom) firmware.zip with hboot 1.36 it said it failed (with no information as to why)
Just looking for pointers on where to go next!
Starting to become concerned I've made a proper mess...
mathesonewan said:
I've tried a lot of things, bootloader is unlocked, flashed boot.img and recovery.img but when I flashed x.xx.206.x - O2 UK (United Kingdom) firmware.zip with hboot 1.36 it said it failed (with no information as to why)
Click to expand...
Click to collapse
Additional to this - I've been through 10-12 pages of various fixes (searched bootloop within HOX forum) that's why the above is a little vague... They've all merged into one...
1: what hboot do you have now ?
2: what recovery are you on ?
and put the phone in the recovery in the mean time. it charges the battery there
Are you flashing cm10 or cm10.1 'cause cm10 does not support hboot 1.36.
Recovery is TWRP v2.4.1
HBoot is 1.36
and I'd read that somewhere about not supporting 1.36 and I've just checked it's 10.1 I was trying to flash
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Yep....and otherwise the way around ! because i helped somebody on team-V ...it didnt work the way TT described. but actually did work the other way around
in recovery a full wipe....
install the rom and gapps
adb reboot bootloader
and flash the boot.img followed by
fastboot erase cache
fastboot reboot
TToivanen said:
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Click to expand...
Click to collapse
Mr Hofs said:
Yep....and otherwise the way around ! because i helped somebody on team-V ...it didnt work the way TT described. but actually did work the other way around
in recovery a full wipe....
install the rom and gapps
adb reboot bootloader
and flash the boot.img followed by
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Right I'll try these out - If TTs method isn't successful is there anything I would need to be aware of inbetween these two methods? Or are both pretty much starting from scratch? (I hope you understand what I mean..?)
mathesonewan said:
Right I'll try these out - If TTs method isn't successful is there anything I would need to be aware of inbetween these two methods? Or are both pretty much starting from scratch? (I hope you understand what I mean..?)
Click to expand...
Click to collapse
TToivanen said:
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Click to expand...
Click to collapse
I've expanded on the above steps to ensure I'm completing them correctly
1. Extracted the boot.img from the firmware zip contained within the CM10.1 zip, then ran fastboot flash boot boot.img from cmd line - this completed and reported "OKAY"
2. Full wipe done using TWRP - system wipe - for good measure wiped everything else too (wasn't sure if system was a catch all for the others or not)
3. Rom Flashed using TWRP install cmd (I've assumed this is the correct way to do it...)
4. Flashed Gapps similarly
It's now past the HTC "quietly brilliant" splash (very very quiet just now...) and is stuck on the CyanogenMod splash just circling round and round...
Going to try the other method see if I have anymore luck!
OK... So haven't had any luck with either method...
When flashing the boot.img it's behaving differently to how it did before - it now triggers the phone to reboot whereas it never did before... Is that normal?
Is there any more information I can give you guys that might narrow down the issue?
Thanks in advance!
i would try a stanrd sense based rom ..... just to check its all fine, i have seen more people that didnt get it booted, why ? no clue....
did a proper wipe....factory reset,wipe caches, dalvik cache, data, system ?
then it should work !
Just downloading the stock rom just now, going to try from there... At this point in time I'll be happy to just have a working phone!
Success!
I tried going back to the stock rom but something mad happened with the recovery (i.e. it didn't work anymore) and was replaced with a graphic of a flat HOX with a sync symbol and then the sync symbol was replaced by a red cross...
So had a minor panic, realised that something wasn't right with TWRP, so flashed on CWM, then flashed the boot.img from the stock zip, and flashed the rom perfectly.
I'm tempting fate but I started this process wanting a new rom and I will finish it, but I'm glad my phone isn't bricked!
Thanks to you both for your input, your faith certainly encouraged me to not give in!
Keep up the awesome work!
Well you can always try again to install CM10.1.....again but now with cwm.
I went with viper - which has flashed successfully, but everytime I unlock the screen it comes up with a white HTC screen... haha time to start trawling the viper forum... or go for CM again!
Strange.....tho i have the idea you missed something in the wiping process ?
Funnily enough for a "low stress" option I wiped everything (CWM > advanced > wipe em all) then reflashed the boot.img from CM10.1, then flashed the rom and it's loading into CM10 but repeatedly flashes "unfortunately the process com.android.phone has stopped"
There is something funny going on if no custom roms are working no?
Wipe data/factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache,data,system
That should do it.....
ohhhhh the mounts and storage one is new to me... I'll try that now with a custom...
Meh didn't work... I'm going to reflash the stock and go to bed I think!
Hey guys,
I've currently got a HTC One X that is stuck in the bootloader. I have got Clockworks Flash Recovery 5.8.4.0 installed but haven't got any rom working. I was using Cyanogenmod until my screen started flickering and eventually it was unbearable so I tried to upgrade it. The newer version didn't support the older hboot (1.12) and therefore the update failed. I tried installing other roms from the forum but had no luck with any of them.
The steps i've been taking are basically flash the boot.img, wipe data/factory reset, install the zip, wipe the data/factory reset and dalvik cache and then reboot the phone but after all of these steps I end up stuck with a bootscreen of the rom i'm trying to install. I have followed tutorials word by word and I am still stuck on the bootloader. I'm really in a dead end here as I'm not that knowledgeable when it comes to HTC, any help would be appreciated as all I want is my phone to be working!
Not sure if it's useful but..
S-ON
HBOOT-1.12.0000
RADIO-1.1204.90.13H
and the CID is H3G_001
Thanks,
Luke
If you make a factory reset after installing the custom rom in the recovery you actually wiped it again. Only perform a full wipe before the rom. Don't wipe anything after ......
Ow and you can't install any sense based JB roms. You need to update the hboot first
..
Thanks for the fast reply,
I've looked all over the forum and they all seem to be JB with Sense of some sort? Hate to be lazy but i've tried searching and can't find anything that would be compatible, would you be able to link me a rom that should work as i've got no clue.
Thanks,
Luke
Why don't you update the hboot and flash anything you like
This is a very useful thread for you
http://forum.xda-developers.com/showthread.php?t=1927048
It has everything you need to update the hboot :thumbup:
...
Will take a look and let you know how I get off, Thank you!
..
Problem is fixed after a whole day of trying. Got there in the end with a little assistance.
Thanks for your help
Luke195
Good !
CASE CLOSED !
hi guys,
i've read about a bunch people who had and solved the problem i'm having but no luck for me. please help!
i updated from cm10.1.3 to cm10.2 via Settings>About Phone>etc. (i.e., without flashing the new boot.img like i was supposed to).
i got caught in the boot animation for over an hour and realized i didn't flash the new boot.img
i tried to manually install cm10.2 like so:
fastboot erase cache, then fastboot flash boot boot.img, then fastboot erase cache again
wiped everything (Wipe data/factory reset, Wipe Cache, Wipe Dalvik Cache, format /system and format /data)
installed the cm10.2 and gapps zips
(i tried repeating the fastboot steps here as well, and also tried "Fix Permissions")
i'm still stuck in the boot animation and don't know what to try anymore i really want to get cm10.2 working. i could use your help
thanks!
EDIT: this might be useful. i tried installing another rom (paranoid android 3.99 http://forum.xda-developers.com/showthread.php?t=2174855) and ended up getting stuck in its boot animation...
EDIT 2: this might be useful. i was able to manually install and successfully boot up cm10.1.2 following the above steps
Hboot to low ?!
Mr Hofs said:
Hboot to low ?!
Click to expand...
Click to collapse
HBOOT is 1.33. CWM is 5.8.4.0. are those too low?
Read the thread for minimum requirements, but should be ok.
Factory reset
Wipe cache partition
Wipe dalvik cache
Format cache,data,system
Then install rom + gapps. Got the correct matching gapps ?
Mr Hofs said:
Read the thread for minimum requirements, but should be ok.
Factory reset
Wipe cache partition
Wipe dalvik cache
Format cache,data,system
Then install rom + gapps. Got the correct matching gapps ?
Click to expand...
Click to collapse
i followed all of these steps without success over a dozen times already. following them, i can install android 4.2 roms (e.g., cm 10.1.3) but not 4.3 (e.g., cm10.2)... i figure there may be a clue in there somewhere...
my gapps are the 4.3 ones.
as for minimum requirements, the official cyanogenmod page (http://wiki.cyanogenmod.org/w/Endeavoru_Info) doesn't mention anything but it might be out-of-date. i found this other thread (http://forum.xda-developers.com/showthread.php?t=2450358) that mentions "datamedia" CWM as a requirement. getting a datamedia CWM for the HTC One X seemed hairy so i got the latest TWRP (2.6) and repeated the process again. still no luck
anymore suggestions?
thanks for the help btw
Maybe hboot upgrade to 1.36 or 1.39 ?
Mr Hofs said:
Maybe hboot upgrade to 1.36 or 1.39 ?
Click to expand...
Click to collapse
i've been trying to follow your latest advice but i can't seem to find the proper firmware needed to upgrade my HBOOT. i'm following your post here (http://forum.xda-developers.com/showthread.php?t=2221171) but the firmware-download post you link to doesn't provide any firmware for my cid (HTC__621) and googling is yielding confusing results (e.g., 600+MB files of dubious origins). do you know where i can get the needed firmware so i can update my HBOOT?
thanks!
Whats the outcome of
Fastboot getvar version-main
Mr Hofs said:
Whats the outcome of
Fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 3.14.751.20
Hmm looking for the firmware but can't see it that fast, at least not a working link ! You have a stock nandroid backup ?
Mr Hofs said:
Hmm looking for the firmware but can't see it that fast. You have a stock nandroid backup ?
Click to expand...
Click to collapse
unfortunately not no backups whatsoever. stupid, i know.
Hmm can't find a usable nand either. Guess you are stuck with a older CM for now or try sentinel (hearing good things about it @E) aosp rom, or a sense 5 rom
Mr Hofs said:
Hmm can't find a usable nand either. Guess you are stuck with a older CM for now or try sentinel (hearing good things about it @E) aosp rom, or a sense 5 rom
Click to expand...
Click to collapse
hmmm. that blows. is the firmware i need not released yet or is it just really hard to find? if i installed a stock rom, would that update my HBOOT? (at which point, i could try cm10.2 again).
thanks!
Well a stock rom (3.14.751) can indeed update the phone (including stock recovery) if it's put indeed. Afaik 751 is at least at 1.36 hboot now ! Will look more tonight, no time anymore now
Mr Hofs said:
Well a stock rom (3.14.751) can indeed update the phone (including stock recovery) if it's put indeed. Afaik 751 is at least at 1.36 hboot now ! Will look more tonight, no time anymore now
Click to expand...
Click to collapse
awesome! thanks! i'm a bit confused seeing as i thought i already had 3.14.751 but i'll wait for your update. thanks again for the help.
Yeah sometimes they push small updates including a hboot upgrade.
Example
3.14.401.27 = hboot 1.36
3.14.401.31 = hboot 1.39
So there could be a 3.14.751 firmware including a higher hboot.
rmanna said:
awesome! thanks! i'm a bit confused seeing as i thought i already had 3.14.751 but i'll wait for your update. thanks again for the help.
Click to expand...
Click to collapse
this is what I found for .751. OTA_ENDEAVOR_U_JB_45_S_Chunghwa_3.14.751.20-2.18.751.7_release_2928741gbid6ybg5q8r5ug.zip
Mr Hofs said:
Yeah sometimes they push small updates including a hboot upgrade.
Example
3.14.401.27 = hboot 1.36
3.14.401.31 = hboot 1.39
So there could be a 3.14.751 firmware including a higher hboot.
Click to expand...
Click to collapse
oh ok. i get it now. thanks! at this point, we're pretty far out of the realm of what i know about custom roms so i'll wait and hope you find something with my fingers crossed.
Ah thant to a possible rescue.
You can always try to flash this firmware
http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One_X/709/
Those have the same main as you have
Edit : link works
Thant said:
this is what I found for .751. OTA_ENDEAVOR_U_JB_45_S_Chunghwa_3.14.751.20-2.18.751.7_release_2928741gbid6ybg5q8r5ug.zip
Click to expand...
Click to collapse
thanks! although this is getting a little beyond me. what exactly is this file? what must i do with it and what will do? will it help me get any closer to cm10.2?