Had a working CDMA VM HTC ONE V running on slim bean. Wanted to update to newest version of Slim Bean so also decided to downgrade the HTC V to stock VM RUU ROM first to get rid of OTA update issues with custom ROMS. Anyway that wouldn't work cause the RUU wizard said the HBOOT was lower or something. Anyway, decided to forget stock VM firmware and just wanted to reflash Slim Bean but now I can't get into recovery nor will Slim Bean fully boot. I can get into fastboot and tried flashing recovery several times. I still can't enter it -- it just sticks at white HTC screen. If I just try to regular boot into the current ROM, it just sticks at boot screen. What should I try to do now? STUCK big time.
Thanks.
Finally got recovery to boot. Not sure how but I just kept trying to install and enter and it finally worked. With that could reinstall Slim Bean. All this started with the inability to downgrade from 928 (I think that's the number) radio and 1.57 HBoot. Is there anyway to do this now? I found older threads that said you're unable to downgrade from that but I don't know if that's still the case (?)
dawg1 said:
Finally got recovery to boot. Not sure how but I just kept trying to install and enter and it finally worked. With that could reinstall Slim Bean. All this started with the inability to downgrade from 928 (I think that's the number) radio and 1.57 HBoot. Is there anyway to do this now? I found older threads that said you're unable to downgrade from that but I don't know if that's still the case (?)
Click to expand...
Click to collapse
I have no idea on the CDMA one V, but for future reference if it doesn't flash, just boot the recovery straight up:
fastboot boot nameofrecoveryimghere.img
There is no known way that I am aware of to downgrade the device from the updated hboot. but there is a kernel available in the slim bean thread at the very top of the downloads area that allows the newer hboot owners to use slim bean cdma with only minor bluetooth audio issues.
Related
Hi everyone, I've come into a strange problem with my G2 and I bet someone here can help me out! I just got a refurbished G2 because my last one had display problems. I tried to root with one with gfree (05) and I ran into a couple of errors so I rebooted my phone and used the rage method. Anyway, I downloaded rom manager and flashed CWM 3.0.2.4 so I could flash that leaked gingerbread build. It wouldn't work for me, so I flashed xborders' version and it's all good. I went to flash the stock rom (to go back) and when it reboots it stays stuck on the HTC splash screen. The same thing happens with CM7, or any other rom I've tried recently. I let CM7 flash when I went to sleep, when I woke up it was still stuck on the HTC screen.
I'll explain what I do:
1. Flash superwipe g2
2. Flash the rom in recovery
I accidently deleted my froyo nandroid but I have one from xborders rom so I at least have a usable phone. Could my sd card be messed up? I've tried it on the two I have.
I had this problem with my other phone too, no matter what I tried I couldn't get CM7 to work. Now it seems like no roms are working.
After I do flash a rom, it doesn't say reboot system like I think it should? I have to hit back to go back into the recovery menu.
Ended up fixing the problem, thanks to anyone who looked at this!
Care to tell us how you fixed in case someone else comes to this thread for reference?
He probably didn't root the phone properly or the partition table has been messed up. To fix something like that just flash a stock ROM that you know works on the phone and from there you can use any root method to get SuperCID, Permanent ROOT, an unlocked HBOOT and ClockWorkMod. Then any rom designed for the G2/DZ should be flashed just fine as long as the requirements are met.
Hey guys!
I've tried to update my android 2.2 to gingerbread, both with the official update and the oxygen update, with the same result: my phone reboots, starts doing something - I get a green statusbar - and after about 1/4th of the bar it all ends up with a phone with a read exclamation mark and a red triangle.
The first time I got there, I though this was something that should happen, and left my phone around for two hours without anything happening.
I googled around and ended up doing a hard reset, which didn't change a thing.
I then tried to go into recovery mode from the boot meny, and end up with the exact same result.
So... what the hell is happening? Anyone got a clue? I would really appreciate some kind of sollution!
Its probably because you have a corrupted update file.
Try downloading it again.
If your branded to a certain carrier, then download the update for that carrier.
I've downloaded the update each time I've tried to make the update. I've tried with the oxygen ROM too, and tried loading recoverymode both from boot menu and clockworkmod. Nothing works. Amen...
So let me get this straight, you are trying to do OTA updates with a custom ROM + clockworkmod!?
It does not work like that. OTA updates are ONLY for 100% stock phones (ok, you can have Radio S-OFF, but no root). As you are using a custom ROM, why don't you just flash a Gingerbread based ROM instead of trying to mess around with OTAs, which obviously is impossible?
Uh, well, I have the standard ROM, but I did not know that it's impossible to install OTA updates when my phone's rooted. But it obviously doesn't work out
I've tried with the oxygen gingerbread release too, but same **** as I described in my original post happens. So what I've done:
- Install OTA update - failed
- Install oxygen-rom - failed
then, Hard reset +
- OTA update, without root - failed
- go into recovery mode from boot-menu - failed
hard reset + root +
- oxygen gingerbread - failed
- recovery mode from boot meny - failed
- recovery mode from ROM manager - failed
I really hoped that a hard reset would do the trick, but there you go...
Again, you cannot get any OTA because you have ClockworkMod.
Sent from my Desire HD using Tapatalk
So... How do I get any update if I can't install Oxygen either? (assuming Oxygen's ROM also qualify as OTA...)
Flash this ROM from CWM Recovery like any other ROM. Its Gingerbread with root, nothing else added.
Thanks!
But I'm still having serious problems getting into recoverymode, or even backing up my existing ROM. It seems whenever I do ANYTHING that requires my DHD to reboot, it ends up with the phone-with-red-eclamationmark-sign. No matter if I've done a hard reset either...
Holene said:
Thanks!
But I'm still having serious problems getting into recoverymode, or even backing up my existing ROM. It seems whenever I do ANYTHING that requires my DHD to reboot, it ends up with the phone-with-red-eclamationmark-sign. No matter if I've done a hard reset either...
Click to expand...
Click to collapse
The red exclamation mark is the stock recovery, so you dont have clockwork recovery. I would recommend starting from scratch installing clockwork then all should be good
Oh, nice to know But I used ROM manager to flash clockwork recovery (at least it said so).
When you say start form scratch, would that imply hard reset, root it, flash CWR and hopefully it will work?
Holene said:
Oh, nice to know But I used ROM manager to flash clockwork recovery (at least it said so).
When you say start form scratch, would that imply hard reset, root it, flash CWR and hopefully it will work?
Click to expand...
Click to collapse
Yes, you did S-off? As that would explain why clockwork didn't flash
Oh, well, uhm.
No.
Damn Thanks!
I tried all day to update my One X to 4.0.4.The phone was rooted but stock.Tried putting the stock recovery, but a red triangle appears in recovery, after that i tried locking the bootloader , but with no succes. I don't know what i'm doing wrong.Please help..
deusexisagod said:
I tried all day to update my One X to 4.0.4.The phone was rooted but stock.Tried putting the stock recovery, but a red triangle appears in recovery, after that i tried locking the bootloader , but with no succes. I don't know what i'm doing wrong.Please help..
Click to expand...
Click to collapse
Sounds a bit of a mess. If I were you I would run the RUU to get back to stock, update OTA and then re-root again.
dr9722 said:
Sounds a bit of a mess. If I were you I would run the RUU to get back to stock, update OTA and then re-root again.
Click to expand...
Click to collapse
I am having the same problem. Tried all day yesterday. Also tried installing the RUU and that failing install as well for me. I have another thread with some details of the error I get in recovery. Basically Here is the info
Get the details of install
Gets downto verifying current system...
Assert failed: apply patch check /system /app/7digital3.apk
E:error in //internal_sdcard/download/ota (file)
Status 7
Installation aborted
So was there a problem with htc servers corrupting the downloads yesterday. Just a question when I see two now with the same issue in updating.
Have the same problem with OTA update from 1.29.401.12 to 2.17.401.12 fail.
Have tryed to remove CID check as have worked with earlier OTA, that dosnt work on this.
RUU also fail with aborted installation as mention over here, but I have had error with all RUU since I got One X 6 monts ago.
Same here, i tried to change name update.zip,asserts but it doesnt work.It says "assert failed: check_cid(get prop("ro.cid"),......."
I think its because u guys remove the bloatware from the system. Ota update need the bloatware even if u r rooted
Sent from my HTC One X using xda app-developers app
Just run your stock rom, flash your stock recovery. You can enter recovery when you see the phone & red triangle just push vol up + power button. You see some errors also. No problem. It's because stock recovery can not mount your sd !
Just boot into your stock rom with stock recovery, bootloader can stay UNLOCKED.
update your phone with the software update program and it should update fine, did this myself last night. After that you can flash the custom recovery and run a custom rom again if you want.
Verstuurd van mijn HTC One X
Can't get OTA to (re)install itself on HTC One X
MarcelHofs said:
Just run your stock rom, flash your stock recovery. You can enter recovery when you see the phone & red triangle just push vol up + power button. You see some errors also. No problem. It's because stock recovery can not mount your sd !
Just boot into your stock rom with stock recovery, bootloader can stay UNLOCKED.
update your phone with the software update program and it should update fine, did this myself last night. After that you can flash the custom recovery and run a custom rom again if you want.
Verstuurd van mijn HTC One X
Click to expand...
Click to collapse
Hi, there I have an HTC One X, relocked, with RUU put back on, but it is the last OTA: OTA_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10-1.26.707.4_release_2571341oc2x91f61pch2z9
That caused the problems as FOTA. My touchscreen now randomly does not accept any inputs.
All because the FOTA was applied while loading the battery, stupid of me of course but s..t happens,right.
So all I want to do now is applying last OTA again. Read all forum updates, but no real solution.
Tried the above, put the ota on de sdcard, even renamed it to update.zip and also on card, but when in stock recovery none of the options seem to pick it up or work.
The RUU succesfully applied was:
RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
And yes it was bought in Singapore:angel:
I could unlock it again and I tried running Maximus V2.2 but the same annoying touchscreen problem.
And yes i tried the option not to go to sleep when loading on charger but didn't help either.
Who can help, or do I wait for the FOTA of Jelly Bean coming this month from HTC (or so it is stated on many websites)?
Thanks for any help in advantage!:good:
TRobdeV said:
Hi, there I have an HTC One X, relocked, with RUU put back on, but it is the last OTA: OTA_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10-1.26.707.4_release_2571341oc2x91f61pch2z9
That caused the problems as FOTA. My touchscreen now randomly does not accept any inputs.
All because the FOTA was applied while loading the battery, stupid of me of course but s..t happens,right.
So all I want to do now is applying last OTA again. Read all forum updates, but no real solution.
Tried the above, put the ota on de sdcard, even renamed it to update.zip and also on card, but when in stock recovery none of the options seem to pick it up or work.
The RUU succesfully applied was:
RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
And yes it was bought in Singapore:angel:
I could unlock it again and I tried running Maximus V2.2 but the same annoying touchscreen problem.
And yes i tried the option not to go to sleep when loading on charger but didn't help either.
Who can help, or do I wait for the FOTA of Jelly Bean coming this month from HTC (or so it is stated on many websites)?
Thanks for any help in advantage!:good:
Click to expand...
Click to collapse
hi i have a similar issue how did u manage to sought the problem of screen
Hello,
wanted to ask for help, i have HTC ONE V CDMA version Bootloader Unlocked and Rooted. S-ON
I tried installing PrimoC kernel on stock sense. I install kernel for ICS then i reboot into bootloader flash the boot.img. Phone reboots and keeps rebooting.
I install XPERIA Rom, install stock kernel through bootloader /fastboot phone wont boot up, just keeps restarting.
I install CM10 and install kernel phone boots up and shuts down. Boots up shuts down.
PACMAN ROM same issue.
The point is what am I doing wrong? I went through every phone out there on the market never had any issues. This phone is pain in my ass.
The only way for me to boot up the phone out of boot loops is flashing BOOT.img from my back i made of the stock sense. Even then my WIFI will not work.
I am looking for pointers, instructions, whatever helps i love flashing I love these ROMS on here, but i just cant seem to get the to work.
Appreciate your time and your help.
Sounds like the last OTA update, your phone might have already had it before you bought it.
http://forum.xda-developers.com/showthread.php?t=2013489&highlight=ota
Please ask all questions in Q&A. Thread moved there.
restoring back to pre ota fixed the issue. what a pain it was something so simple yet complicated.
HTC One x (protoype) bootloop after jellybean update
Hey guys, This is my first post ever on XDA so please forgive me if I sound like an idiot
I got hold of a HTC One x which was already had an unlocked bootloader, rooted and had CWM recovery installed. I was told that I have a prototype version of the one x. Anyway that is not issue. when I got the phone it was running android version 4.0.4 HTC Sense version 4.1 and I checked software update. The 3.14.401.27 OTA update was available so I proceeded with the update and after the reboot I found my phone stuck in a bootloop and the only way for me to sort it out was by restoring my nand back up from CWM. I really wanted the new Sense 5 UI and android jelly bean so I downloaded:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Radio_5.1204.162.29_release_292865_signed.exe
My CID was HTC__621 thats why I downloaded that ruu but after flashing it not was I only stuck in a bootloop but also when I entered recovery mode it was just a blank black screen with the back lights on. I even flashed different versions of CWM recovery and TWRP which gave me the same black screen so I flashed the stock recovery.img which also gave me the same black screen. I thought me maybe a different Ruu would resolve this issue so I used 'JBFWTOOL21' to change my CID to '11111111' this allowed me to flash:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
&
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
After trying both these ruu's I still found my device stuck in a bootloop. Next I downloaded 'Endeavoru_CustomRUU' this contained a 'rom.zip' which I belive was a jelly bean rom and said it would update my image version to '3.14.401.31' after flashing this ruu, my phone booted up past the 'HTC Quietly Brilliant' screen but into a black screen but I could hear the boot sound and knew it booted up but it still gave me a black screen. barre in mind this was the only rom that booted up and didn't get stuck in a bootloop but the downside was I had no picture on the screen it was literally pitch black with the backlight on when it went past the 'HTC Quietly Brilliant' boot screen. I didn't even see the one x boot animation. I could only hear the boot up sound and once it was booted up the notification LED would flash I was receiving network settings from my operator. That was about it. I booted into recovery to see wether that worked but unfortunatelly it was also still giving me a black screen. The only thing I could boot into without a problem was 'power button + volume down' which booted into bootloader in which I chose 'fastboot' to flash all these roms.
At this point I thought my device was soft bricked so I gave it to my friends father who happened to really good with his IT skills. He managed to change my device's CID from 'HTC__621' to 'HTC__001' after doing so he downloaded this ruu and flashed it:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This ruu turned out to work perfectly fine with my device. Everything functioned once again, the device was able to boot into recovery and boot normally without a hassle. I also discovered that this was the rom that I received my phone with which put me back to the start on android 4.0.4
I was really annoyed with the fact that I was stuck on ICS so I flashed the MaximusHD 21.1.0 rom and its boot.img which put me into a bootloop again. I also tried other custom roms such as Revolution and SD secxces which all put my phone in a bootloop even though I flashed their boot.img kernels. I knew that I required a hboot 1.33.0000 or above in order to flash jb roms so I used 'JBFWTOOL21' once again before flashing these custom roms to update my hboot from 1.12.0000 to 1.33.0000. so all these bootloops still occourd after doing all this and I just had to return back to ICS. barre in mind I only tried flashing JB roms as I want sense 5 so I don't know if a custom ics rom would work on my device as I havent tried it yet but I know for a full fact that none of the jb roms work on my device.
For those who are wondering here, I uploaded some pictures of my device just go to the top of the page where it says "Reason:" I put a link in it just copy and paste the link in your browser, sorry but this is the only way I can share links as I don't have 10 posts. The pictures show all the information you may want to know about my device (HTC One X PROTOTYPE).
I really hope someone can help me update to jelly bean and get sense 5 as I am frustrated from failing and being stuck in bootloops
If you read all of this I honestly appreciate it and Thank you for it, I hope you can help me!