Develop Bugs

[Solved] Boot loop on every ROM

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 !

I formatted my htc one x

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?

[Q] Need help my phone gone all glichy

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 !

[Q] HBOOT CID problem

Hi guys,
let me fill you in on my situation.
I live in The Netherlands, last year i got my one x.
My service provider is vodafone, current HBOOT version is 1.12 and my CID is VODAP102
At the moment i''m running slim bean 3.1.0 official (android 4.1.2)
I would like to upgrade to a JB ROM but i cant because my HBOOT version is to low.
I followed the instructions from the link below (short version: lock phone, fastboot oem RUU, etc..)
But after locking the phone it wont boot into RUU and it wont flash the new HBOOT version.
I checked and i downloaded the correct HBOOT for my CID.
I followed the steps in the video to the letter but always fails when trying to reboot into RUU and after that to flash the new HBOOT.
https://www.youtube.com/watch?v=fkD3CeSecb8
My best guess would be that the CID that my phone returns to me is not the CID my phone realy has.
Because when i look up the CID it is assosiated with either vodafone UK or vodafone germany not vodafone NL.
Can u help me ?

If you have a backup of stock ICS rom, restore this and lock your phone.
Take the upgrade by OTA and re-unlock your phone with the first code by htc.
p.s. SlimBean works on 1.2x hboot?

Guich said:
If you have a backup of stock ICS rom, restore this and lock your phone.
Take the upgrade by OTA and re-unlock your phone with the first code by htc.
p.s. SlimBean works on 1.2x hboot?
Click to expand...
Click to collapse
i dont have the stock backup anymore.

I searched a backup of ics or the ruu for Jelly, but i don't found nothing.
I hope that someone can post the backup or RUU.

Get the main version
Fastboot getvar version-main

Mr Hofs said:
Get the main version
Fastboot getvar version-main
Click to expand...
Click to collapse
Thanks for your response.
version-main: 2.17.161.4
and my radio is 2.1204.137D1.21
HBOOT: 1.12.000

The same number as this one
http://bugsylawson.com/index.php/fi...-radio-21204137d121-release-280390-signedexe/
Should work. Otherwise we get a nandroid backup
Try the ruu first
Relock the bootloader
Fastboot oem lock
Then run the ruu with admin rights
Right click the ruu and select :
Uitvoeren als administrator (of zoiets)

Mr Hofs said:
The same number as this one
http://bugsylawson.com/index.php/fi...-radio-21204137d121-release-280390-signedexe/
Should work. Otherwise we get a nandroid backup
Try the ruu first
Relock the bootloader
Fastboot oem lock
Then run the ruu with admin rights
Right click the ruu and select :
Uitvoeren als administrator (of zoiets)
Click to expand...
Click to collapse
Thnx, for the quick reply.
to clarify, with "relock the bootloader" you mean Fastboot oem lock right ?
and what is the file linked above, it is over 600 mb bit it isn't an rom ?

dutch_guy90 said:
Thnx, for the quick reply.
to clarify, with "relock the bootloader" you mean Fastboot oem lock right ?
and what is the file linked above, it is over 600 mb bit it isn't an rom ?
Click to expand...
Click to collapse
Correct, its fastboot oem lock
The file is a ruu, it should flash back the stock rom,kernel and recovery back to the phone via a setup menu on the pc. It reads the phone and flashes all for you

Mr Hofs said:
Correct, its fastboot oem lock
The file is a ruu, it should flash back the stock rom,kernel and recovery back to the phone via a setup menu on the pc. It reads the phone and flashes all for you
Click to expand...
Click to collapse
cool il give it a try
do i need to do a nandroid backup ? or just backup sdcard

dutch_guy90 said:
cool il give it a try
do i need to do a nandroid backup ? or just backup sdcard
Click to expand...
Click to collapse
Backups are always good, can't have to many of them

Mr Hofs said:
Backups are always good, can't have to many of them
Click to expand...
Click to collapse
after i have instalt the RUU and whent through the whole proces what should i do ?

Reboot

Mr Hofs said:
Reboot
Click to expand...
Click to collapse
ok that worked, what shoudl i do now ?

Search for updates

Mr Hofs said:
Search for updates
Click to expand...
Click to collapse
sorry for the late response, i have been away for a few days.
Thanks for your help it worked perfectly, i'm on Hboot 1.36 now

[Q] Lag when flashing any JB ROM

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