Hello.
I currently have SlimBean 3.0.0 installed, and I'm trying to get Sense back. I've tried countless ROMs, but on every single one of them, I get boot loop and then I have to install Slim again.
Yes, I do all the wipes, including dalvik cache, but nothing seems to help.
Thanks in advance.
Have you flashed the boot.img of each rom?
Re: Boot loop on every ROM
And what is your hboot number ?
Yes, I've always flashed the boot.img that comes with each one.
Now that you mentioned hboot, that might be an issue. It's 0.94.000, I've tried to search, but I can't find any instructions on how to upgrade it.
Re: Boot loop on every ROM
Yeah the old hboot is the issue
Get the main version, lets get back to stock and update the phone with official ota ! I bet there is a matching ruu for you with that old hboot
Do
Fastboot getvar version-main
Post the result please
Mr Hofs said:
Yeah the old hboot is the issue
Get the main version, lets get back to stock and update the phone with official ota ! I bet there is a matching ruu for you with that old hboot
Do
Fastboot getvar version-main
Post the result please
Click to expand...
Click to collapse
Here:
version-main: 1.28.401.9
Re: Boot loop on every ROM
Oke download this file
http://androidfiles.org/ruu/securek...Radio_2.1204.135.20_release_274900_signed.exe
Charge the battery before you do this :
Put the phone in the bootloader and relock the bootloader
Fastboot oem lock
After that you keep the phone in the bootloader and execute the ruu.exe from the pc with admin rights (right click the ruu.exe)
This will flash the phone to original android 4.0.4. When the ruu flashed with succes you boot the phone and update the phone with the original OtA to JB
Alright, I'll do that when the phone is charged. Many thanks.
Now this is just horrible... I got it to 4.1, but now I can't select it to charge only when connected, so I can't root it.
Re: Boot loop on every ROM
Just set usb debugging enabled and you're good to go.
TToivanen said:
Just set usb debugging enabled and you're good to go.
Click to expand...
Click to collapse
I was able to flash the recovery via fastboot. Next I'll try to install JB Remix ROM.
EDIT: The issue has been solved.
Glad it worked ! :thumbup:
CASE CLOSED !
Related
I'm going to update my htc one x to jelly bean from ICS, using custom ROM (ARHD), it was noted that I need a firmware package, and now that I found the package for my CID because took sometime before I found it, is it really required to flash it? TIA
For JB roms you need a JB hboot those are the 1.31 and higher up. Except for the aosp JB roms, those run also on the lower ics hboots.
So if you are on a lower hboot then 1.31 then yes you need to upgrade the hboot
Now I think everything's messed up and I badly need help here, so stupid with I did.
At one moment, my phone is stuck at One tm screen, after I flash the boot.img and installed the custom ROM. I tried to restore my phone using CWM but it still stucked. It was too late before I realized how to flash the firmware package that I need to rename what I downloaded to firmware.zip. I tried flashing the firmware without knowing that I have to relocked my phone before I flash it. Now I relocked my phone and I'm stucked with hboot and I can't do anything at the moment.
With it relocked. In fastboot do
fastboot oem rebootRUU (note the capitals)
Your phone will then reboot into a black screen with the HTC logo.
Then do fastboot flash zip firmware.zip
Once completed fastboot reboot-bootloader
It will reboot into bootloader
Then unlock and flash recovery again.
Flash boot image and reinstall ROM and you should be good to go
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
With it relocked. In fastboot do
fastboot oem rebootRUU (note the capitals)
Your phone will then reboot into a black screen with the HTC logo.
Then do fastboot flash zip firmware.zipOnce completed fastboot reboot-bootloader
It will reboot into bootloader
Then unlock and flash recovery again.
Flash boot image and reinstall ROM and you should be good to go
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Cannot load "firmware.zip" always shows up. My CID is HTC_044, and as far as I know I downloaded the correct firmware package for my phone according to ARHD forum. Thanks in advance.
Did you have the firmware.zip in your fastboot folder?
Yes. And I downloaded it 3 times just to make sure it is the right firmware.
Oh and sometimes you need to flash it 3 or 4 times to succeed. I had to do the command 3 times when I flashed my firmware.
So try it multiple times in a row.
Sent from my One X
Sorry but I tried several times and "error: cannot load 'firmware.zip' all the time. What could be the problem?
During at work. I thought if is it possible just to return to stock ROM? But I just can't find the proper RUU yet.
cid: htc_044
version-main: 1.29.707.11
I'm currently charging my phone using the batch file I found here in xda. I saw a lot of posts regarding flashing the current version of CWM so you can charge your battery, I think my CWM is in version 5.8.1.0, and as far as I know you have to unlock your hboot before you can flash recovery, so it's impossible for me to flash 5.8.4.0? Am I correct here or I can just proceed to the other steps?
I can check tonight if i have your RUU !
Mr Hofs said:
I can check tonight if i have your RUU !
Click to expand...
Click to collapse
Thank you Mr Hofs! And, should my battery level is 30% or higher before I can flash the RUU?
Yes ! If you can't get enough power with the batt script you can flash the latest cwm recovery and charge the battery in there to 100% if you want to.
Unlock the bootloader first if it is still locked
Mr Hofs said:
Yes ! If you can't get enough power with the batt script you can flash the latest cwm recovery and charge the battery in there to 100% if you want to.
Unlock the bootloader first if it is still locked
Click to expand...
Click to collapse
I was done in re-unlocking my bootloader, but then I still can't flash cwm recovery because it says low battery, then I tried to use the batt script again and of course it cannot work since I just re-unlocked my bootloader.
I never tried it with a unlocked bootloader, have you tried it ?
Yes, I tried it and it doesn't work.
What I did for the past hours, I tried to restore my phone again using cwm recovery, still nothing changed, still stucked at htc one logo, then I turned it off trying to charge it using the main charger and it does have light in its LED, left it for a while and now it doesn't turn on.
Try it with phone connected to the pc, it seems to make a difference sometimes....and if you are capable again to run the bat script then leave it for 2.hours or so !
Now it's working. The first time I used the batt script, I thought it could charge more than 3681mV but It didn't work as it didn't get higher than 3681mV. I HOPE it's enough just to flash the cwm recovery. Thanks Mr Hofs, will update asap.
Please my htc one x is s-on , HBOOT 0.96 and unlocked i got a virus on my htc so i formatted my sd and now i am stuck on the white screen.
i need to know step by step what to do as i followed many guides and failed to fix it.
Thank you
Unlocked as in running a custom rom, or still on the stock rom ? Please give some more info
So what recovery ?
Stock or custom rom ?
What rom where you using if it is custom ?
Also curious about the virus you had?
webpatrick said:
Also curious about the virus you had?
Click to expand...
Click to collapse
+1 on that, and how it affected the phone in any way !
Mr Hofs said:
Unlocked as in running a custom rom, or still on the stock rom ? Please give some more info
So what recovery ? i am using TWRB recovery
Stock or custom rom ? i was on custom ROM but know everything gone as the Phone is formatted
What rom where you using if it is custom ?
Click to expand...
Click to collapse
I cant Remember
Your help is highly appreciated
Oke then do this fastboot command , we get you a ruu to get back to stock and then you can also update to jellybean
Fastboot getvar version-main
Mr Hofs said:
Oke then do this fastboot command , we get you a ruu to get back to stock and then you can also update to jellybean
Fastboot getvar version-main
Click to expand...
Click to collapse
I did the command then restart the phone but nothing happened
I know it did do nothing ! I need the number that came out
Mr Hofs said:
I know it did do nothing ! I need the number that came out [/QU
ohhhh sorry i am new to this .
the version no is 1.29.415.11
and really much thanks for your help and quick reply
Click to expand...
Click to collapse
Download this file
http://androidfiles.org/ruu/securek...Radio_2.1204.135.20_release_275980_signed.exe
First how is the battery ? Charge it in the recovery if needed. You need at least 30% of power for this !!
1: put the phone in the bootloader and lock the bootloader
Fastboot oem lock
Keep the phone in the bootloader and execute the ruu with admin rights (right click the ruu.exe and select it)
This will flash the phone to stock android 4.0.4 sense 4.1. After this all you go into the settings and check for manual updates, update it to JB !
Thank you it's worked now how to update to jelly bean
Check in the phone
Settings - about - softwareupdates and do manual searching now !
I did the same stupid thing with my HTC One (v. 1.29.651.7) I cant find an RUU to restore. Any suggestions?
Hi all,
I m still a noob to android and I was trying to flash viperx jellybean rom on my htc one x international tegra 3 version. But after the flashing I noticed that my IMEI and baseband have been erased. The stupid thing I did was not to take a backup before proceeding. So now my phone cant connect to the network.
Can you please let me know if there is a way to fix this phone?
Reflash the rom and in aroma choise: "venom kernel".
After or before, you have to flash the boot.img that you can found in zip rom...
Guich said:
Reflash the rom and in aroma choise: "venom kernel".
After or before, you have to flash the boot.img that you can found in zip rom...
Click to expand...
Click to collapse
Just to confirm reflash the viperx jellybean rom, after after reflashing in aroma choose venom kernal
after that flash the boot.img ?
thanks much for help.
Now, you have wifi signal and network signal?
If no, this is the problem.
So:
1) Extract boot.img from zip folder and put it (boot.img) into your fastboot folder
2) Make an erase cache: "fastboot erase cache"
3) Flash the boot.img: "fastboot flash boot boot.img"
4) Make another erase cache: "fastboot erase cache"
5) Reboot into recovery
6) Flash the rom with a full wipe and at kernel voice, choise Venom kernel
You can resolve with this procedure
Thanks. I have wifi signal but no cell phone signal since my IMEI is erased. Its unable to connect to network.
I will give it a try right now.
thanks.
Unfortunately this didnt work for me. It still doesnt show the IMEI and baseband info on my phone. Both are unknown.
My kernal version is 3.1.10 if that matters.
Please help.
Which version of rom you've flashed?
And what's you hboot?
i think that one way to retrieve it back is with a ruu, going back to full stock ! can you give the out come of :
fastboot getvar version-main
Mr Hofs said:
i think that one way to retrieve it back is with a ruu, going back to full stock ! can you give the out come of :
fastboot getvar version-main
Click to expand...
Click to collapse
I had the same issue...
And I resolved with a reflash of rom, its' strange that for him didn't work...
Mr Hofs said:
i think that one way to retrieve it back is with a ruu, going back to full stock ! can you give the out come of :
fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 3.14.401.31
Also could you please point me on how to go back to stock ? Can I go to ICS or should I go to JB stock?
well if this does not work....i have no other option....this will bring the phone back to factory state
download this file
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_302015_signed.exe
steps :
1: charge the battery full
2: backup all content you need to keep
3: boot the phone in the bootloader and relock the bootloader
fastboot oem lock (the bootloader reboots with a warning in the bootloader, thats fine. keep the phone there)
4: execute the RUU on the pc with admin rights (right mousebutton -> select : run as administrator)
5: sit back and follow the steps on screen. it takes about 7-10 minutes and your phone is back to factory settings
6: hopefully it works
Guich said:
Which version of rom you've flashed?
And what's you hboot?
Click to expand...
Click to collapse
I flashed venom 3.3.7
hboot is 1.39
my cid is htc__001 is that matters
R: [Q] HTC one x corrupted my IMEI and baseband
spacemango80 said:
I flashed venom 3.3.7
hboot is 1.39
my cid is htc__001 is that matters
Click to expand...
Click to collapse
We have only the cid different, but for me worked my steps
Try with the steps by Mr Hofs
Sent from HOX
thats all good....but the IMEI thing is not ......i say try the above and report back !
Just a question on this process:
Dont I have to flash the boot.img and recovery.img too?
Nope.....all is done by the ruu
Mr Hofs said:
Nope.....all is done by the ruu
Click to expand...
Click to collapse
I belive there is something wrong with my windows box (may be a driver issue)
After I run the RUU it goes as far as "waiting for rebooting the bootloader.."
then it gives up saying the phone is not connected.
Is there any way to run this from MAC?
Mr Hofs said:
Nope.....all is done by the ruu
Click to expand...
Click to collapse
Everything went through fine with RUU and now am back to stock.
However the problem persists. IMEI is still not there and baseband is still unknown. This is really killing me.
Any help is highly appreciated
thanks
Then i can't give you the answer....
R: [Q] HTC one x corrupted my IMEI and baseband
spacemango80 said:
Everything went through fine with RUU and now am back to stock.
However the problem persists. IMEI is still not there and baseband is still unknown. This is really killing me.
Any help is highly appreciated
thanks
Click to expand...
Click to collapse
Before the first flash of viper, did you have unlocked your phone or this was unlocked?
And, this problem appears after the flash of Viper Rom??
Sent from HOX
I've tried to update my phone HBOOT from 1.28 to 1.39 and I've used JBFWflasher to do it so I can try using Viper ROM. To cut a long story short I've tried several methods and resorted to flashing it with back to stock but now if looks like it has Viper on it. The phone has gone to being very slow and glichy and I'm stuck with what should I do? .
Can I flash it back to stock again?
What are the steps you have been taken ?
You need to flash the boot.img from the viper rom.zip with fastboot, then make a FULL wipe in the recovery .... not the sdcard ofcourse.
Then install the viper x rom zip.....
Your hboot is updated successfully ?
Give some (or all) info of the steps you did. Including what recovery you are using. Its easier to give proper help
isptim elizabeth
Mr Hofs said:
What are the steps you have been taken ?
You need to flash the boot.img from the viper rom.zip with fastboot, then make a FULL wipe in the recovery .... not the sdcard ofcourse.
Then install the viper x rom zip.....
Your hboot is updated successfully ?
Give some (or all) info of the steps you did. Including what recovery you are using. Its easier to give proper help
Click to expand...
Click to collapse
I've tried Android Revolution HD 20.1 the last few hours still not any better. I've flashed the boot img using jbfwtool21 and then flashed the rom and did a full wipe. Does it have anything to do with the hboot? How do I check?
Check your hboot number in the bootloader. Its number is in there. And what recovery are you on ???
Mr Hofs said:
Check your hboot number in the bootloader. Its number is in there. And what recovery are you on ???
Click to expand...
Click to collapse
hboot is 1.39.0000 recovery is twrp
All should be oke then. Did you try another rom....or maybe its a bad download.
Phone still appears to be acting up even after flashing with another rom. Is there anyway to flash back to stock?
Can you do
Fastboot getvar version-main
Sorry how do i do this? I'm a bit of a noob:laugh:
Ah think I got it, its 3.14.401.31
Oke download this file
http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/
Then relock the bootloader
Fastboot oem lock
Then run the ruu with administrator rights....it will flash the phone back to full stock
Or try flashing the rom without the jbfwflasher and just use cmd
A
Viper 3.5.4 xm296
Thank you Mr Hofs followed your instructions and I'm so releived that its now fixed and that I don't have an expensive paperweight
Thank you soooo much!!!
:laugh::good:
Very good mate !
CASE CLOSED !
Hi guys, finally got a HOX. I've rooted, flashed a new recovery and bootloader unlocked it. When ever I flash a JB ROM (4.1.x or 4.2.x) I have issues with major lags to the point where everything seems to operate at 3fps and it's unusable. Anyone know why this is so?
Weird, can you give some more detailed info ?
What rom
What kernel
What recovery (type & version number)
Steps you perform before flashing and installing ?
Mr Hofs said:
Weird, can you give some more detailed info ?
What rom
What kernel
What recovery (type & version number)
Steps you perform before flashing and installing ?
Click to expand...
Click to collapse
When I bought the phone it had stock 4.1.1 firmware and had the major lag issues and then I flashed Android Revolution ROM v9.9 I think on 4.0.4 and it smoothed out.
I tried CM10.1 and flashed the boot.img in fastboot and then rebooting into recovery (Lastest CWM) to do wipes and then flashing CM10.1. The phone proceeds to boot but lags immensely from that point on.
Okey, but what recovery are you using ? So i can give steps to install properly, not saying you didn't but to be safe.
Then we can try CM10.1 again or another sense rom just to test.
After that we can try different governer settings or different kernels.
Mr Hofs said:
Okey, but what recovery are you using ? So i can give steps to install properly, not saying you didn't but to be safe.
Then we can try CM10.1 again or another sense rom just to test.
After that we can try different governer settings or different kernels.
Click to expand...
Click to collapse
I'm using ClockWorkMod Recovery v5.8.4.0 I think. My usual method is
1. Boot into bootloader
2. fastboot flash boot boot.img (flash boot image for CM10.1)
3. Boot into recovery
4. Wipe all partitions
5. Install CM10.1 and Gapps.
6. Reboot into OS.
After flashing boot.img use fastboot erase cache . Dont know if this help but this step is missing
Maybe after flashing rom first reboot ,after that ,reboot and then flash gapps.
Sent from my HTC One X using xda app-developers app
Fastboot erase cache is very good, always good to do that but always flash gapps before reboot
Steps looks fine, i give a detailed one so you can compare
Flash boot.img
Fasboot erase cache
In recovery :
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache,system,data
Then install of the the rom.
Is this on all roms (did you try a sense based one) ?
Can you post the outcome of :
Fastboot getvar version-main
It even lagged the same way with the stock ROM and the phone still being 'virgin'? Aka no root, flashing, unlock etc.
In that case I would suspect a hardware failure, such as the memory.
Mr Hofs said:
Fastboot erase cache is very good, always good to do that but always flash gapps before reboot
Is this on all roms (did you try a sense based one) ?
Can you post the outcome of :
Fastboot getvar version-main
Click to expand...
Click to collapse
3.14.401.31 is the outcome of fastboot getvar version-main.
It is weird because on stock HTC 4.1.1 ROM it's laggy as hell and any other 4.1.x or 4.2.x ROM is just laggy as hell. I flash back to Android Revolution v9.9 on 4.0.4 and it's smooth as normal.
Alright lets try this :
Relock the bootloader :
Fastboot oem lock
Then run this ruu with admin rights by right clicking the ruu and select that option
http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/
Then you get it back to stock including of flashing the firmware
Mr Hofs said:
Alright lets try this :
Relock the bootloader :
Fastboot oem lock
Then run this ruu with admin rights by right clicking the ruu and select that option
http://bugsylawson.com/files/file/1...-r-radio-5120416229-release-302015-signedexe/
Then you get it back to stock including of flashing the firmware
Click to expand...
Click to collapse
Just done this and booted into Stock 4.1.1. It's a LOT smoother than it was before, still not quite buttery smooth but hey it's usable. Would it now be a good idea to get rooted and Custom Recovery?
I suggest you let this stock rom settle for a couple of hours or a day.....check if its getting better.
But yes if you wish you can custom rom it again
Mr Hofs said:
I suggest you let this stock rom settle for a couple of hours or a day.....check if its getting better.
But yes if you wish you can custom rom it again
Click to expand...
Click to collapse
I flashed back to CM10.1 and it still is incredibly laggy. I have no clue why it's doing this.
Can you download trickster from the playstore and set the governer to performance, see if that makes a difference ?!
Mr Hofs said:
Can you download trickster from the playstore and set the governer to performance, see if that makes a difference ?!
Click to expand...
Click to collapse
Just tried it. No changes to report. Still slow as hell. Clock speeds look normal as well.
Then im afraid i cant help you any further
Hoooold on a second.
Please provide me the following information: CID and HBOOT version.
To get your CID, download CID Getter from the Play Store. Your CID will be displayed in the top area of the app.
To obtain your HBOOT version, simply reboot to the bootloader and check the version there.
Zulake said:
Hoooold on a second.
Please provide me the following information: CID and HBOOT version.
To get your CID, download CID Getter from the Play Store. Your CID will be displayed in the top area of the app.
To obtain your HBOOT version, simply reboot to the bootloader and check the version there.
Click to expand...
Click to collapse
Well his main number is 3.14.401.31 that's a wwe cid with hboot 1.39
Already gave this on page 1, plus he ran the ruu with succes already .....
Mr Hofs said:
Well his main number is 3.14.401.31 that's a wwe cid with hboot 1.39
Already gave this on page 1, plus he ran the ruu with succes already .....
Click to expand...
Click to collapse
True, it's just that it was unclear to me whether he got on that ROM by OTA or by custom ROM. In the second case the HBOOT could be a too low version.
True, but the fastboot getvar version-main always tells the true main version (and can be automatically be linked to the hboot) of the phone and not the running software