Hello ,
since two days i am trying to install a custom rom on my htc desire x. I repeated every single step several times to make sure everything still is fine.
(unlook, flash boot, flash recovery / tried twmp and cwm, etc..)
The only rom which works for me ist the cM10-2-20138004-unofficial. But with restrictions. WLAN doesn't work, media manager isn't starting. Cant hear the partner when calls are incoming.
I tried mySense, Half_Sense, myOnedx, but after finishing installation the device hangs on startup. I waited hours and minutes but nothing happened.
I tried several RUU´s but can't find the right ones for me, or i got the 155 error message.
There is no OS installed on the device. How can i get the device up an running? I would be really happy if somebody can give me a hint whats going wrong.
Thx in advance
Dont worry all ****s can be fixed.Wha is ur hboot ? Or simply before to try to install custom rom U was with ICS rom or JB ?.You have to use the right recovery.Look what rom you want to flash, if you on ics hboot u cant just flash jb room (Some roms already have this funcion)
Ps:
After flasing the rom go in boothloader and flash boot.img And away do full wipe
What you need to make sure when installing a ROM: Install a suitable kernel. When installing a Sense ROM, install a Sense custom kernel or the stock kernel. Installing CM isn't advisable, because it's not ready for daily use yet. Also, make sure you use the right recovery for right hboot.
Good Morning,
thx for reply. I want to install the myOnedx_RC4.0 FX. I extracted the boot.img from zip. Installed the rom, wiped, reboot and installed the boot.img.
But that failed. Again, the cyanogen start up occurs for hours and hours. The device doesnt start.
Also tried the same wir the mySENSEdx5_RC4
I evem tried to install the nexuskernelv3.img
I am on hboot 1.25.002
Anyone an idea what wrong with my installation?
Thx
Again: Which custom recovery are you using? Please post a link to the thread here, so we can see what you've installed. Also, as first time user, you should check this and this.
Sorry i forgot. I am using TWRP 2.6.3.0 as custom recovery
Ok, strange, as this one works for me without problems. However, try the 2.5.0.0 version for JB and see if it goes without problems then. Also be sure to wipe system, dalvik cache, cache and data partition before installing a new ROM.
Same with version 2.5.0.0. I tried clockworkmod recovery, but as soon as i try to wip i got the error messages:
cant mount cache/recovery
cant open cache/revocery
So how can i get back to a stock rom? I tried the way described in here: http://forum.xda-developers.com/showthread.php?p=41327224
, but restore failed.
Any other ideas?
If you want to get back to stock, you need to know your CID first. After that, check this thread: http://forum.xda-developers.com/showthread.php?t=2324815
As you have JB hboot, you need to restore a JB backup. In the thread I linked you to are backups of several CIDs. If yours isn't there, you won't be able to return to stock.
Ok thanks. So it is not in there. I got the cid VODAP102.
Does that mean my device is gone? Or can i even try other workarounds?
Thanks
So i installed odexed rom and this one works fine. Do not know why all the other roms not working to me.
Maybe anyone an idea.
Otherwise thanks for your support.
Lastmenstanding said:
Does that mean my device is gone? Or can i even try other workarounds?
Thanks
Click to expand...
Click to collapse
Your hboot : 1.25.0002
Recovery to flash - JB recovery download from here : http://d-h.st/VjM
fastboot flash recovery command : fastboot flash recovery recovery.img
For a test ROM to flash, flash this stock ROM : http://forum.xda-developers.com/showthread.php?t=2239511
also make sure to fastboot flash boot boot.img
(boot.img is attached on OP)
Once everything run, it is up to you to try any other ROM and any other boot.img
Lastmenstanding said:
So i installed odexed rom and this one works fine. Do not know why all the other roms not working to me.
Maybe anyone an idea.
Otherwise thanks for your support.
Click to expand...
Click to collapse
It's either you flash ROM with wrong recovery type or wrong boot.img type or ROM which is not supported on your hboot.
Simple rules:
1) Recovery must be a recovery for JB.
2) Correct boot.img for correct ROM
ICS ROM that support hboot 1.25.0002
Recovery : JB recovery is a must
Boot.img : ICS boot.img is a must
JB ROM which should run fine on hboot 1.25.0002
Recovery : JB recovery is a must
Boot.img : JB boot.img is a must
ICS ROM that does not support hboot 1.25.002 - you need to manually change the mountpoint in updater-script, then
Recovery : JB recovery is a must
Boot.img : ICS boot.img is a must
Yeah, that was the problem, I see now... Have been blind a bit... The ROMs OP has installed on his phone are all ICS ROMs which need changing of updater-script mountpoints. That's why they won't work. @Lastmenstanding: Try any JB ROM available in Android Development section, should work without problems. The ROMs you tried were ICS ROMs especially written for ICS hboot, that's why they didn't work on your phone.
dansou901 said:
Yeah, that was the problem, I see now... Have been blind a bit... The ROMs OP has installed on his phone are all ICS ROMs which need changing of updater-script mountpoints. That's why they won't work. @Lastmenstanding: Try any JB ROM available in Android Development section, should work without problems. The ROMs you tried were ICS ROMs especially written for ICS hboot, that's why they didn't work on your phone.
Click to expand...
Click to collapse
OP mentioned about installing my ICS ROMs. Both ICS ROMs work on JB hboot without a need to edit the updater-script. My guess is he either use wrong recovery (ICS recovery is wrong) or wrong boot.img (JB boot.img is wrong) as it should be JB Recovery and ICS boot.img
..do not know how to use the thank meter, but..
Thank you guys for your excellent support.
Lastmenstanding said:
..do not know how to use the thank meter, but..
Thank you guys for your excellent support.
Click to expand...
Click to collapse
Just thank them at the bottom of their posts...
There is a thanks button at the bottom of every post.
Related
So heres the deal, i tried to flash miui and it doesnt work at all, i am the dummy who didnt do a nandroid back up, and now im stuck, evo 3d hboot 1.5, twrp 2.0,try to push adb, but its says device not found. i can boot into hboot and twrp but i cant get a rom to load so.. someone please help
hmm
ok so i figured out if i load into twrp and then do adb commands they work. installed new rom but it gets stuck at boot animation, any help would be great.
baloocifer said:
ok so i figured out if i load into twrp and then do adb commands they work. installed new rom but it gets stuck at boot animation, any help would be great.
Click to expand...
Click to collapse
Did you wiped everything before the flash ?
Sent From My RED 3Dimension
yeah i did wipe everything, and i did get roms to load, but everyrom that i try now gets to the actual rom and keeps giving me errors, like htc.bg process force close
did you follow the instructions on how to flash miui to a phone with hboot 1.5 or did you just do it blindly thinking it will work? if you didnt follow the instructions your kernel did not flash
plus you can always mount your sd-card in recovery to transfer a different ROM, zip, ect.......
I have tried a lot of different things. i have loaded into twrp pushed roms then fastboot load recovery then installing with twrp and i seem to get the same results with every different rom.
baloocifer said:
I have tried a lot of different things. i have loaded into twrp pushed roms then fastboot load recovery then installing with twrp and i seem to get the same results with every different rom.
Click to expand...
Click to collapse
What radios are you on software? You should stick with a rom that is built off the latest updates. I have been waiting on a rom to drop built off the latest software update. Are you on the latest software? If you try running old roms built off 2.3.3 and your kernel and radios are the latest you will have issues no matter what you do.
i think i may have been trying flash it all wrong i dont really know what i did right this time but i got it loaded so making a nandroid back up right now thanks for all your guys help
I rooted my rezound and flashed a rom with no problems. Today I tried flashing a different rom and I have been unable to start my phone since. I can get into recovery, wipe, flash etc.. but nothing I've tried has gotten my phone to boot. I've tried Awesome Recovery Tool-> Touchscreen based PH98IMG Creator for MainVer which isn't helping and I don't know what else to do. The last message I saw in hboot was something about the main version is older. Can someone please help me get my phone to boot please
This worked well for me:
http://forum.xda-developers.com/showthread.php?t=1467099
k9tim said:
This worked well for me:
http://forum.xda-developers.com/showthread.php?t=1467099
Click to expand...
Click to collapse
Thanks but that wouldn't work via recovery but I did manage to get my problem fixed!! I managed to "fastboot flash boot boot.img" then boot into recovery and flash the rom and thank god it worked!!
sungal said:
I rooted my rezound and flashed a rom with no problems. Today I tried flashing a different rom and I have been unable to start my phone since. I can get into recovery, wipe, flash etc.. but nothing I've tried has gotten my phone to boot. I've tried Awesome Recovery Tool-> Touchscreen based PH98IMG Creator for MainVer which isn't helping and I don't know what else to do. The last message I saw in hboot was something about the main version is older. Can someone please help me get my phone to boot please
Click to expand...
Click to collapse
the problem u were having has to do with kernels.
when u first tried flashing a different rom, were u going to ics from gb or gb from ics?
gb roms and ics roms have different kernel.
"fastboot flash boot boot.img" then boot into recovery
and flash the rom was the right call.
just wanted to let u know this.
Ok so I've been struggling with this for MONTHS. I flashed Hatka 2.x (Android 4.2) a while back, and ever since then I have not been able to install any other rom besides Hatka 2.x.:crying:
Android: 4.2
Rom: Hatka 2.x
Kernel: 3.4.10-g4d47dce [email protected] #1 SMP PREEMPT
HTC Sense: 4+
I have tried flashing several roms from just about anything 4.2.2 - 4.3 and now 4.4.x. I'm not sure If maybe I need a new kernel, boot image or what but I feel like I have tried everything. When I flash a rom I wipe data/cache/dalvik cache (of course), Flash the rom, flash gApps, flash cache/dalvik and more times than not my phone will never get past the HTC logo. Sometimes more lately with 4.4 roms my phone will boot loop only showing the HTC logo for a minute or two then restart. I root and flash several different types of phones for my friends all the time, and never have any of these issues that I've faced with my own phone.
I recently thought about trying to un-root, re-lock, and flash back to stock, then re-root and un-lock again but I'm not sure if that will even help.
Things I've tried:
Several roms
Moded kernel
Stock kernel
Multiple CWM versions
Multiple TWRP versions
Fastboot flash
Adb flash
Adb Sideload
Roms I am currently trying to flash:
AOKP unofficial (4.4.2)
BeanStalk (4.4.2)
CM-11 Nightly (4.4.2)
OSE Official (4.4.2)
My secondary HDD with all of the kernels, roms, and anything else I have tried recently failed so I don't have the specific version numbers for any of the attempts listed above.
If someone could give me any advice on this I would be eternally greatful. The Android/xda community has always been so helpful with many others in times of need, so now after spending months of research and trial & error I am reaching out to anyone here at xda that may be able to give me some advice/assistance.
Links to other threads/tools are greatly appreciated also! :good:
Thank you in advance.
-EDIT-
SOLVED
I took thay10's advice and flashed RUU. Since I got an error flashing RUU 3.04 I found RUU 1.15 here and flashed that successfully.
After that I verified my cid using this method.
When that turned out ok I continued to the HTCDev page to unlock my bootloader.
Once the bootloader was unlocked I used Facepalm S-Off method to achieve S-Off. (Using only the modified boot.img and DNA-rescue.img [links in thread]).
After all that was finished and I now had my bootloader unlocked and S-Off, I chose the recovery of my choice and flashed it using fastboot.
FINALLY, I was able to load the recovery and wipe everything (system,data,cache,sdcard) and flash a 4.4.2 rom of my choice!
Everything works perfectly now, I'm so relieved! Thank you again thay10 for your help. Hopefully this can help someone else out as well.
anyone?
Okay first thing. Looks like your doing a dirty flash and going from rom to rom may cause problems and clutter.
What I would advise is you to do a clean flash which involves you wiping. cache,data,system,sdcard.
But ONLY do this after you backup files you need, and make sure you have fastboot and adb installed and is working properly on your computer.
Edit: Are you still soff and bootloader unlocked?
thayl0 said:
Okay first thing. Looks like your doing a dirty flash and going from rom to rom may cause problems and clutter.
What I would advise is you to do a clean flash which involves you wiping. cache,data,system,sdcard.
But ONLY do this after you backup files you need, and make sure you have fastboot and adb installed and is working properly on your computer.
Edit: Are you still soff and bootloader unlocked?
Click to expand...
Click to collapse
Thank you for the advice. Yes I am S-off and my bootloader is unlocked. I noticed that the version of cwm I had installed was not wiping the system folder so I flashed 'Philz Touch 6' cwm and used that to do a full wipe including system,data,cache,sdcard and then used adb sideload to flash a couple roms. Each rom I flashed after a full wipe still won't boot. I continue to loop through the htc logo.
ADB and fastboot are both working properly, and htc drivers are fully up to date.
Roms I am currently trying to flash are:
AOKP unofficial (4.4.2)
BeanStalk (4.4.2)
CM-11 Nightly (4.4.2)
OSE Official (4.4.2)
stevenschemers said:
Thank you for the advice. Yes I am S-off and my bootloader is unlocked. I noticed that the version of cwm I had installed was not wiping the system folder so I flashed 'Philz Touch 6' cwm and used that to do a full wipe including system,data,cache,sdcard and then used adb sideload to flash a couple roms. Each rom I flashed after a full wipe still won't boot. I continue to loop through the htc logo.
ADB and fastboot are both working properly, and htc drivers are fully up to date.
Click to expand...
Click to collapse
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
thayl0 said:
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
Click to expand...
Click to collapse
No problem. I was using TWRP for the longest time but I read a few different places that people were having issues flashing cm-11 on some versions of TWRP and to explorer versions of CWM that worked.
I have RUU downloaded but I have not ran it yet. What exactly will RUU do?
-EDIT- Also when would I run RUU? Would I have to restore my nandroid backup first or can it read my phone while in recovery through adb?
-EDIT- I went ahead and flashed RUU 3.04 while in the bootloader. It says it's sending to my phone right now so I will update shortly with a result.
thayl0 said:
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
Click to expand...
Click to collapse
I flashed the latest TWRP and when I sideload the rom I get the error saying "Error executing updater binary in zip '/data/'
This is the issue I was reading about when people were saying they couldn't flash cm-11 with TWRP. I've even tried installing cm-10.2 roms and had the same issue.
thayl0 said:
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
Click to expand...
Click to collapse
The RUU 3.04 flash finished and I got "ERROR 158; Image error. The rom update utility cannot update your android phone. Please get the correct rom update utility and try again."
Any idea what would cause that?
RUU was downloaded from HERE.
stevenschemers said:
No problem. I was using TWRP for the longest time but I read a few different places that people were having issues flashing cm-11 on some versions of TWRP and to explorer versions of CWM that worked.
I have RUU downloaded but I have not ran it yet. What exactly will RUU do?
-EDIT- Also when would I run RUU? Would I have to restore my nandroid backup first or can it read my phone while in recovery through adb?
-EDIT- I went ahead and flashed RUU 3.04 while in the bootloader. It says it's sending to my phone right now so I will update shortly with a result.
Click to expand...
Click to collapse
TWRP last time I checked didn't support CM thats why people switched to CWM
What are you trying to do to your phone? Most people only run RUU to get to stock.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
stevenschemers said:
The RUU 3.04 flash finished and I got "ERROR 158; Image error. The rom update utility cannot update your android phone. Please get the correct rom update utility and try again."
Any idea what would cause that?
RUU was downloaded from HERE.
Click to expand...
Click to collapse
I'm guessing you ran the exe. I was refering to the one thats a zip file and you flash it
hello friends wanted to know if I could help with a rom I put my htc Rezound which was its official rom 4.0.3 with locked bootloader unlock with which HTCDev because my wifi and bluetooth problems and change the boot.img and the cell was bricked me in htc screen and there is no step more, then install android systen recovery and install the rom you liquidsmooth and kenel funky but the Rezound stays in the animation of the rom and there does not pass I wonder if someone could help me I'm s-on bootloader unlock if any rom that works well with me these try installing an exe ruu but I think the 115 Error error loading the image. Thanks I hope to fix my htc.
What recovery did you use? Did you ever flash the boot.img after flashing the ROM? Also, you can't run a RUU without really being S-OFF. If you want some good ROMs, try out Chucktr's CM 11, bunchies Liquid smooth 3.2, or some other newer ROMs. Any should do. But after flashing them in recovery. You have to flash the boot.img manually in fastboot. Or else you will be stuck on boot logo forever. If you want to get back to stock, we can do that after you get booted.
Sent from my HTC One M8 Running Paranoid Android. S-OFF.
pball52998 said:
What recovery did you use? Did you ever flash the boot.img after flashing the ROM? Also, you can't run a RUU without really being S-OFF. If you want some good ROMs, try out Chucktr's CM 11, bunchies Liquid smooth 3.2, or some other newer ROMs. Any should do. But after flashing them in recovery. You have to flash the boot.img manually in fastboot. Or else you will be stuck on boot logo forever. If you want to get back to stock, we can do that after you get booted.
Sent from my HTC One M8 Running Paranoid Android. S-OFF.
Click to expand...
Click to collapse
Cm11 install the rom,gapps and your boot.img with this rom in the list of downloads to make the wipes and install everything and install the boot.img from fastboot and start tefono becomes trapped in the circle of blue animation like liquidsmooth know what would be the problem
DrakoVains said:
Cm11 install the rom,gapps and your boot.img with this rom in the list of downloads to make the wipes and install everything and install the boot.img from fastboot and start tefono becomes trapped in the circle of blue animation like liquidsmooth know what would be the problem
Click to expand...
Click to collapse
Always ALWAYS extract boot.img from rom zip and use it.
Snuzzo said:
Always ALWAYS extract boot.img from rom zip and use it.
Click to expand...
Click to collapse
Push the boot rom but still I stay in the blue circle with the name of CyanogenMod in an infinite animation that does not happen there is a splash screen, try changing the put recovery v2.7.1.0 and good while trying to clean I get the factory reset: factory reset failed, then all is well wipe cache, data, system.davilk install the rom fine but when installing i get GASPP failed, will try to update the recovery to see if that's, if you think you know where is my mistake I could say? thank you
thanks and could solve my problem this way: install the TWRP recovery-2.7.0.1-OpenRecovery-vigor.img is that I could run to perfection only thing I did not wanted to install gapps.4.4.4 then me DOWNLOAD the gapps4.4.4 (standard) cache.davilk wipe, data, system. all well factory reset then install the rom cm-11-20140605-UNOFFICIAL-standart vigor.zip and gapps, clear cache went back to bootloader and install the boot.img reincie and ready. thanks!!!:victory:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..