Database Info

[Q] Boot loop, can boot to twrp/fastboot, but cant flash any roms.

Okay so heres the deal. Bought a new evita from a dealer. Dont remember/have what the stock software was, but it was booting with an att rom and all the bloatware. I downloaded the all in one eztoolkit and unlocked the bootloader successfully. Heres my problem, I can get into fastboot and twrp, but all of my flashes fail regardless of what rom I flash. I tried cm 10.2, 10.4, and 11 beta and they all failed. Then I tried to revert using both att ruus I could find, including the 2.20 and 3.18 updates directly from att. Both of them reboot to the ruu loader and appear to be working, but fail citing the incorrect software version. I assume its because I manually changed the recovery and flashed boot.img files from each of the roms I tried to flash, but I am not certain. Heres is the getvar information:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 0.19as.32.09.11_
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.20.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT24DW304126
(bootloader) imei: 359691042468010
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3897mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Can this be solved by flashing the correct rom, and if so can you direct me to it? Otherwise, how can I fix this?
Thank you.

edit: flashed cm 10.0.0 and related gapps after manually flashing the boot.img and I got it to boot.
Going to try to s-off so I can be done with all this garbage.
edit: Got it booting, got s-off. Still on 10.0.0 with root and s-off. Not sure where to go from here unless anyone can give me further direction. I'd prefer to have the latest cyanogen etc, but I am ok with this if I cant go any further.
Thanks all !

Where are you downloading your ROMs? You mentioned earlier that you flashed cm10.4 but there is no such ROM for this device. You need to be careful about where you get your ROMs, flashing a ROM that isn't intended for this device can easily result in a brick.
Your ROM flashes were failing because your firmware is too old, it does state pretty clearly in the install instructions on the cm threads that you need to update your firmware via the 3.18 RUU. So you need to download the 3.18 RUU and run that which will update your firmware. Here's a very useful thread which details how to run an RUU.
After you've done that you'll need to flash TWRP again. If you want to flash the latest cm, which is cm11, you need to install the modified version of TWRP 2.6.3.0 recovery which can be found in our Original Android Development section. Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter TWRP and flash your ROM + gapps. Because you're new here I'd suggest you click the Everything Evita link in my signature and bookmark it, it contains links to basically everything for our phone. You should also click the other links in my signature and read those threads, you'll find them very helpful. Here's a few important links for you too:
One XL Main Page
http://forum.xda-developers.com/forumdisplay.php?f=1538
One XL Q&A
http://forum.xda-developers.com/forumdisplay.php?f=1572
One XL Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1726
Make sure you only ever download ROMs from the development sections I've linked there, many people make the mistake of wandering into the HTC One X forum and flashing those ROMs, many of those people bricked their phone. That might seem confusing but you don't have the HTC One X (Endeavoru), you have the HTC One XL / at&t One X (Evita). If you have any further questions just ask either here or in my q&a thread (link in my signature).
Sent from my Evita

Cyanogenmod11 ruu

I made install cm11 a bit easier for yall.
https://drive.google.com/file/d/0B0x...it?usp=sharing
download this file.
extract rom.zip and put into same folder as fastboot
reboot phone into fastboot
then run command fastboot oem rebootRUU
when in ruu mode run command- fastboot flash zip rom.zip
note you must be s-off and using supercid.
it might say flush immediately blah blah just run fastboot flash zip rom.zip again and wait til it finishes
next fastboot reboot-bootloader
and then boot into recovery
press the wipe button and choose "format data" enter "yes" when prompted
then reboot recovery and choose "wipe" this time press "advanced wipe" only check "cache" when its done go back and now only check "dalvik-cache"
once thats complete reboot system and wallaa cm11
these are just the bootloader variables hboot is also modded for red text, and will also not show "tampered" or "security warning" etc.. also when you do fastboot oem lock it will say locked not relocked.
I tested it on my mini so it does work.
version: 0.5
version-bootloader: 2.21.0000
version-baseband: 1.24.40e.00.26
version-cpld: None
version-microp: None
version-main: Cyanogenmod11
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid:
product: m4_ul
platform: HBOOT-8930
modelid: PO5822000
cidnum: 11111111
battery-status: good
battery-voltage: 4319mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
thanks to h8rift for the hard work on cm11
and to jmz for an official twrp recovery
also attached is stocksplash.zip..to apply use fastboot oem rebootRUU then fastboot flash zip stocksplash.zip then fastboot reboot..done.

Thx for the ROM, I can confirm it works.
Is it possible to post the original boot splash screen(in splash.img form) for stock restore? I can't find it anywhere.
Thx in advance.

Sorry, but what is this exactly?

Its basically just custom recovery hboot and ROM all in a flashable zip.
Sent from my One Mini using Tapatalk

Work with Hboot 2.22.0000!?
cmvienneau said:
Its basically just custom recovery hboot and ROM all in a flashable zip.
Sent from my One Mini using Tapatalk
Click to expand...
Click to collapse
Execute me. i'm new in HTC One mini and i'm poor in English.
this RUU worked with Hboot 2.22?
i have one is Hboot 2.22 S-ON if i apply this ROM it worked?
and another one is Hboot 2.19 S-OFF 4.2.2 rooted if i Update OAT can i keep ROOT after Updated?
Thanks.

Unbrand and update 3UK S4 on 1.06 hboot

Hello, I could use a little help, as I cannot flash recovery on branded 3-Mobile UK phone (S4 processor).
I have unlocked the bootloader via htcdev.
More phone info via fastboot getvar all :
Code:
version: 0.5
version-bootloader: 1.06.0000
version-baseband: 0.15.31501S.19_2
version-cpld: None
version-microp: None
version-main: 1.53.771.4
serialno: HT242W411761
imei: ***
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: H3G__001
battery-status: good
battery-voltage: 4018mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 802fa374
hbootpreupdate: 11
gencheckpt: 0
CID is H3G__001 and HBOOT is 1.06.0000
I have tried flashing both CWM and TWRP from fastboot, but though it seems everything goes well, when I reboot to recovery, it gives me the generic HTC recovery screen (the one with the little bar on the top right of the screen) and reboots after a while to the branded ROM. I think it reflashes the branded recovery automatically, because the bar is proceeding and then reboots the phone.
I cannot root or change CID without custom recovery.
Do I need to flash a boot.img (and which one)?
Thank you in advance!
*UPDATE*
OK, I managed to install an older version of TWRP (2.6.3.0).
What must I do to update hboot and install newer ROMS?

Candlemass said:
Hello, I could use a little help, as I cannot flash recovery on branded 3-Mobile UK phone (S4 processor).
I have unlocked the bootloader via htcdev.
More phone info via fastboot getvar all :
Code:
version: 0.5
version-bootloader: 1.06.0000
version-baseband: 0.15.31501S.19_2
version-cpld: None
version-microp: None
version-main: 1.53.771.4
serialno: HT242W411761
imei: ***
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: H3G__001
battery-status: good
battery-voltage: 4018mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 802fa374
hbootpreupdate: 11
gencheckpt: 0
CID is H3G__001 and HBOOT is 1.06.0000
I have tried flashing both CWM and TWRP from fastboot, but though it seems everything goes well, when I reboot to recovery, it gives me the generic HTC recovery screen (the one with the little bar on the top right of the screen) and reboots after a while to the branded ROM. I think it reflashes the branded recovery automatically, because the bar is proceeding and then reboots the phone.
I cannot root or change CID without custom recovery.
Do I need to flash a boot.img (and which one)?
Thank you in advance!
*UPDATE*
OK, I managed to install an older version of TWRP (2.6.3.0).
What must I do to update hboot and install newer ROMS?
Click to expand...
Click to collapse
your phone's security is on. I would recommend do the following:
1) S-off ur phone
2) change CID to supercid
3) Run any new RUU
4) Re-flash TWRP
5) Enjoy

bilal_liberty said:
your phone's security is on. I would recommend do the following:
1) S-off ur phone
2) change CID to supercid
3) Run any new RUU
4) Re-flash TWRP
5) Enjoy
Click to expand...
Click to collapse
Thank you for your answer and congrats on your ROM (it is the one I'm running right now ).
I managed to solve the issues yesterday, but the information was so scattered around, it took me half a day (along with the sloooow downloads).
For anyone interested, the procedure was like this :
1) Unlock bootloader via htcdev.com and identifier token
2) Flash TWRP 2.6.3.0
3) Root
4) SuperCID
5) S-OFF
6) Change CID to HTC__001
7) Update HBOOT to 2.15 via firmware flash
8) Run newest RUU
9) Flash newest radio
10) Re-flash TWRP
11) Flash Custom ROM
Step 8 can be skipped, but I wanted to see if it ran the stock ROM ok.
In more detail, with links and files :
Initially the phone was branded on 3UK with CID H3G__001, HBOOT 1.06 and MID PJ4010000.
Code:
version: 0.5
version-bootloader: 1.06.0000
version-baseband: 0.15.31501S.19_2
version-cpld: None
version-microp: None
version-main: 1.53.771.4
serialno: HT242W411761
imei: ***
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: H3G__001
battery-status: good
battery-voltage: 4018mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 802fa374
hbootpreupdate: 11
gencheckpt: 0
The safest way to update my HBOOT to 2.15 or 2.16 was via a latest official RUU from here http://www.androidruu.com/?developer=Ville . But the latest RUU matching my CID was a bit old (RUU_Ville_U_H3G_UK_1.78.771.5_Radio_0.16.31501S.19_2_10.23.31501S.10L_release_258982_signed) and I didn't know which HBOOT it contained, so I decided to update using the latest European RUU (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4). In order to do this, I would have to chance CID to something corresponding (i.e. HTC__001 or HTC__N34 for my region - ELL).
(1)
I began with the thread [Tutorial]Root, Unlock, Recovery and flashing a Custom ROM, but got stuck on the recovery flashing, that's when I started this thread. I flashed the latest TWRP (2.7.0.0) and latest CWM (6.0.4.8) but they didn't work.
The recovery boot acted as described in the OP (gave me the generic HTC recovery screen) and tried multiple times. Then I remembered reading something like that the newest recoveries work differently to support newest hboot, so I tried the previous version (TWRP 2.6.3.0 from http://techerrata.com/browse/twrp2/ville ) and it worked.
(2-3)
TWRP also offered to root the ROM by installing supersu automatically, so I didn't have to flash it myself. After the reboot to system, I installed supersu from market, updated su binary and the root access was complete. The rooting was necessary so that we can change the CID to SuperCID.
(4)
SuperCID can be set following this guide [UNLOCK] AT&T Bootloader Unlock Through HTC-Dev. I changed H3G__001 to 11111111 with HxD (needs care not to change more that those 8 bytes and check that the size remains the same - mine was 1024B).
(5)
Next stop is S-OFF via Facepalm with the help of this thread [S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA. It worked right away, following exactly the procedure as described.
(6)
I changed CID to HTC__001 , not leaving SuperCID on, because there were reports of bricks when flashing OTA updates. Just wanted to be on the safe side.
Easy from fastboot with S-OFF :
Code:
fastboot oem writecid HTC__001
(7-8)
The next step was to flash the latest RUU (RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4), in order to update my HBOOT to 2.15. But this came to a halt, as the RUU didn't proceed, giving me error 159. More info and solution on this matter can be found in the thread RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release.
In short, the problem is that the ROM.zip inside the RUU is encrypted and we either had to decrypt it using ruuveal via linux, or to use the already decrypted by hasoon2000 zip ( http://forum.xda-developers.com/showpost.php?p=40925380&postcount=79 ).
As I also mentioned in that said thread ( http://forum.xda-developers.com/showpost.php?p=52852710&postcount=123 ), if you update the HBOOT manually, by flashing corresponding firmware, the RUU flashing proceeds without any issues.
So, I followed the thread [GUIDE][TOOL]FUU/FirmwareHTC One S and flashed the Official Unbranded 2.15 Firmware (Sense) zip via fastboot. The result was an updated HBOOT to 2.15 and the ability to flash the official RUU. With S-OFF there is no need to relock the bootloader.
(9-10-11)
After that, I simply reflashed TWRP and the custom ROM Liberty-S4-V7a. I skipped the manual radio flash, because Liberty ROM had the option to flash it from AROMA installer automatically. For other ROMs, it is a simple flash via fastboot.
Simple, hah

[Q] unable to flash ruu via .exe or fastboot

ive been trying to resolve this for two days in an attempt to avoid having to post this thread
sooo here we go-
the phone is k2plc_cl. in a haste/ not caring/ thinking i could maybe get the data working fashion, i flashed viper to my oneSV.
unable to get any signal, i tried relocking my bootloader, and flashing the latest ruu.exe- it sat on sending everytime
so i unlocked my bootloader and tried flashing via fastboot.
recovery and boot flash, radio gives me the remote not allowed like the bootloaders locked.
im not 100% sure on what to do right now actually...
i have the OTA_K2PLC_CL_JB_45_S_Cricket_US_2.04.1050.2-1.03.1050.7_release_321361523g7wih6zk058h5.zip
this needs flashed through stock recovery or fastboot?
fastboot gives me data too long, so i think recovery
but
i flash recovery img. in fastboot, it says OK, and reboots and hangs on the white htc screen
c:\android\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.12.00.1029
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: k2_plc_cl
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8012000
(bootloader) cidnum: CRICK001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3763mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
any help will be GREATLY appreciated!:good:

Remove your imei & serial, not needed in public.
You need to downgrade hboot first, if you wanna flash the Ruu.
As you are S-off, i would give the last firmware.zip a try. Maybe this solves the issue.
http://fotadl.htc.com/OTA_K2PLC_CL_....04.1050.5_release_343402dpsh8ror12wwdww2.zip
Download the OTA, inside you'll find a firmware.zip. Extract it from the OTA file and rename it to PL80IMG.zip.
Copy to external sdcard, boot into bootloader, wait for scanning the files and confirm to flash with vol+ button. Wait until its finished, can take some minutes.
Reboot and see if your problem is gone.
Some sidenotes: Make a backup before in recovery. And after flashing the firmware you will have stock recovery, so in case you will need TWRP, flash it with fastboot.

old.splatterhand said:
Remove your imei & serial, not needed in public.
You need to downgrade hboot first, if you wanna flash the Ruu.
As you are S-off, i would give the last firmware.zip a try. Maybe this solves the issue.
http://fotadl.htc.com/OTA_K2PLC_CL_....04.1050.5_release_343402dpsh8ror12wwdww2.zip
Download the OTA, inside you'll find a firmware.zip. Extract it from the OTA file and rename it to PL80IMG.zip.
Copy to external sdcard, boot into bootloader, wait for scanning the files and confirm to flash with vol+ button. Wait until its finished, can take some minutes.
Reboot and see if your problem is gone.
Some sidenotes: Make a backup before in recovery. And after flashing the firmware you will have stock recovery, so in case you will need TWRP, flash it with fastboot.
Click to expand...
Click to collapse
flashing the pl80img brought the phone back on, but its still on the viper rom.
so, im going to downgrade hboot, and try to flash the ruu.
thanks for the advice too!
update- i got it back to normal! thanks
i downgraded by renaming the firmware zip to pl80img, put it on my sdcard, and let the bootloader take it from there.
then i installed cwm and flashed the zip that you made from the cricket backup.
geez ive been stuck on this for 2 days hahaha

ok this phone is confusing me sooo freaking bad
so i see that you need to make sure your bootloader is equal(?) or lower than that of which your updating to..
im at 4.1.2, hboot 1.01.000, and software version 2.04.1050.3 trying to update to 2.04.1050.5
and it fails with an 'error in zip file'
i have stock recovery, unrooted, unlocked and s-off.
ive read i do not need to relock to update right?
im trying to just update to 4.2.2 right on the phone but im def at a road block haha

I thought you want to run the RUU to get back stock?

old.splatterhand said:
I thought you want to run the RUU to get back stock?
Click to expand...
Click to collapse
Yes after finally getting the ruu to work! I had to relock, flash newest firmware zip from your list, unlock, download and flash ota then ruu worked. in between I was trying to just flash the ota zip and recovery would abort no matter what
But
Man Im happy to be back on 422 hahaha
And thanks a lot for being there to help everyone out btw :good:
This process finally makes sense to me haha :cyclops:

[Q] lot's of problems

Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.

theconverter said:
Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.
Click to expand...
Click to collapse
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now

rzr86 said:
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now
Click to expand...
Click to collapse
Hi,Yep tried that one still getting signed error.
Thanks for looking

You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **

lot's of problems
Gatosbil said:
You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **
Click to expand...
Click to collapse
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s

theconverter said:
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s
Click to expand...
Click to collapse
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command

rzr86 said:
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
extract the recovery.img and flash it via fastboot command
Click to expand...
Click to collapse
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts

theconverter said:
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts
Click to expand...
Click to collapse
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked

rzr86 said:
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked
Click to expand...
Click to collapse
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?

theconverter said:
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?
Click to expand...
Click to collapse
i really don't know mate

rzr86 said:
i really don't know mate
Click to expand...
Click to collapse
Hi, just a update ive fixed my phone, :laugh: done so by making a gold card following the tut's on this fourm installed 4ext via the card booted into recovery cleared dalvik cache ect and now boot's without any loop's.
Looking forward to flashing cyanogenmod and maybe going s-off
Many thanks for all your help and suggestions ill hit the thanks button for you.
Just need to mark as " solved " not sure how ( mod's ? )