Related
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
andason said:
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
Click to expand...
Click to collapse
3.18 ruu.
Sent from my One X using xda premium
jacobas92 said:
3.18 ruu.
Sent from my One X using xda premium
Click to expand...
Click to collapse
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
andason said:
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
Click to expand...
Click to collapse
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
RollTribe said:
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
Click to expand...
Click to collapse
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
andason said:
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
Click to expand...
Click to collapse
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
RollTribe said:
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
Click to expand...
Click to collapse
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Yeah, man, Wine doesn't work, I tried back when I used Mac for my Android needs. Everything is SO much easier with a windows PC
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
claudiuslu2011 said:
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
Click to expand...
Click to collapse
Yup all Roms
is there any advantage on the 3.18ruu?
Yeah, you need it to run AOSP 3.4 kernel roms
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link: http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
exad said:
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
Click to expand...
Click to collapse
Thanks again for the help.
andason said:
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link:
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
Thanks again for the help.
Click to expand...
Click to collapse
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
odd that rom would not boot with 2.14..but with 1.09 no problems?
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
There was probably some other factor causing the issue. I boot all roms with 2.14 no problem.
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
Which ROM? After s-off?
Sent from my Evita
timmaaa said:
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
Click to expand...
Click to collapse
do i need to downgrade my touch firmware?
claudiuslu2011 said:
do i need to downgrade my touch firmware?
Click to expand...
Click to collapse
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
timmaaa said:
Which ROM? After s-off?
Sent from my Evita
Click to expand...
Click to collapse
It may be I am mistaken. I thought it was baked but i was also trying a rom I was trying to port. During the time i was flashing from 1.09 to 2.14 and also seen that baked required 2.14. So with all that going on i was just trying boot.img and then the rom to ensure no errors.
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
the_ziom said:
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
Click to expand...
Click to collapse
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
benJX said:
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
Click to expand...
Click to collapse
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
the_ziom said:
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
Click to expand...
Click to collapse
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
dr3amsINdigital said:
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
Click to expand...
Click to collapse
Wise choice, yeah you are right, the bricks were when they were flashing the zips in recovery. Its actually pretty safe in RUU mode but what's the point of risking it.
benJX said:
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
Click to expand...
Click to collapse
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
HELP my device does not see any memory and i cant flash any rom hellpp
the_ziom said:
HELP my device does not see any memory and i cant flash any rom hellpp
Click to expand...
Click to collapse
What hboot are you on now? Did you run an RUU to downgrade?
rosswhite said:
What hboot are you on now? Did you run an RUU to downgrade?
Click to expand...
Click to collapse
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Which recovery did you flash? Try TWRP 2.7.0.0.
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Can you boot on stock android rom installed by the ruu ?
rosswhite said:
Which recovery did you flash? Try TWRP 2.7.0.0.
Click to expand...
Click to collapse
i already have twrp 2.7 and i flashed phillz and still nothing
benJX said:
Can you boot on stock android rom installed by the ruu ?
Click to expand...
Click to collapse
yes but i formated my memory to instal a pac man rom
the_ziom said:
yes but i formated my memory to instal a pac man rom
Click to expand...
Click to collapse
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
####
benJX said:
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
Click to expand...
Click to collapse
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
So many developers and only 2 can help me
Please I'm begging for help
the_ziom said:
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
Click to expand...
Click to collapse
Flash stock recovery : http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Then Clear Storage from bootloader and flash TWRP recovery
Today i rooted my HTC One S (S3) with moonshine, but my wifi don't turn on. I've searched how to fix, but i don't find it. I flashed twrp recovery too and i see on moonshine folder, "boot_backup.img".
What should I do to get my wifi back?
watergluis said:
Today i rooted my HTC One S (S3) with moonshine, but my wifi don't turn on. I've searched how to fix, but i don't find it. I flashed twrp recovery too and i see on moonshine folder, "boot_backup.img".
What should I do to get my wifi back?
Click to expand...
Click to collapse
You shoud try gto get a matching RUU / firmware to bring your phone back to stock. If WiFi is working fine you can flash a custom rom again
LS.xD said:
You shoud try gto get a matching RUU / firmware to bring your phone back to stock. If WiFi is working fine you can flash a custom rom again
Click to expand...
Click to collapse
I think RUU is too dangerous for me. There's another way? Can I rollback my boot with "Boot_backup" created by moonshine? If yes, how?
watergluis said:
I think RUU is too dangerous for me. There's another way? Can I rollback my boot with "Boot_backup" created by moonshine? If yes, how?
Click to expand...
Click to collapse
May you post a link to "moonshine" ?? I think its to gain S-OFF and not to root your phone.
LS.xD said:
May you post a link to "moonshine" ?? I think its to gain S-OFF and not to root your phone.
Click to expand...
Click to collapse
moonshine.io
watergluis said:
moonshine.io
Click to expand...
Click to collapse
Which firmware instalation was installed on your phone? Did you successfully gain S-OFF / unlocked bootloader / Superuser access?
Moonshine.io provives the feature to install a modified stock kernel. the boot.img backup is the original kernel. Just flash it using fastboot.
"fastboot flash boot boot.img"
LS.xD said:
Which firmware instalation was installed on your phone? Did you successfully gain S-OFF / unlocked bootloader / Superuser access?
Moonshine.io provives the feature to install a modified stock kernel. the boot.img backup is the original kernel. Just flash it using fastboot.
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Moonshine S-OFF
VILLEC2 PVT SHIP S-OFF RL
CID-HC__032
HBOOT-3.01.4444
RADIO-16.11.20.24_M
OpenDSP - V11.6.0.2235.00.0304
eMMC-boot
Yes,yes,yes.
But, if i flash, i will loss S-off?
Yesterday i install CM11. Still with same problem with wifi.
You could go back to stock and use another s-off. Rumrunner or firewater
Gesendet von meinem One S mit Tapatalk
hi guys, ill try and keep it as brief as poss.
Phone was rooted working fine, dropped the phone and cracked the screen so sent for repair. Repair shop returned it back to stock :/
Left phone stock and working fine for a couple of months, accidentally let phone fully discharge and think it damaged the battery. Bought a new battery but the phone just boot loops. Can get into Hboot but when i choose recovery it just starts boot looping again. In a panic i flashed a 3.33 firmware but made no difference. Can someone give me a step by step how to sort? thanks!!
Phone says :
-firmware- 3.33-
pyramid pvt ship s-off rl
hboot 1.27.1100
emmc-boot
Im guessing its also locked because when i do the oem lock in command prompt its saying device is locked. cheers all.
mickey909 said:
hi guys, ill try and keep it as brief as poss.
Phone was rooted working fine, dropped the phone and cracked the screen so sent for repair. Repair shop returned it back to stock :/
Left phone stock and working fine for a couple of months, accidentally let phone fully discharge and think it damaged the battery. Bought a new battery but the phone just boot loops. Can get into Hboot but when i choose recovery it just starts boot looping again. In a panic i flashed a 3.33 firmware but made no difference. Can someone give me a step by step how to sort? thanks!!
Phone says :
-firmware- 3.33-
pyramid pvt ship s-off rl
hboot 1.27.1100
emmc-boot
Im guessing its also locked because when i do the oem lock in command prompt its saying device is locked. cheers all.
Click to expand...
Click to collapse
did you try to reflash recovery to see if will work?
Mile_zdr said:
did you try to reflash recovery to see if will work?
Click to expand...
Click to collapse
If i connect fastboot-usb and use the command prompt to flash a recovery i get (error-partition doesnt exist!!)
Can i put any recovery on the sd card and somehow load it without using the recovery option?
mickey909 said:
If i connect fastboot-usb and use the command prompt to flash a recovery i get (error-partition doesnt exist!!)
Can i put any recovery on the sd card and somehow load it without using the recovery option?
Click to expand...
Click to collapse
what command do you use?
Mile_zdr said:
what command do you use?
Click to expand...
Click to collapse
fastboot flash zip recovery.zip
mickey909 said:
fastboot flash zip recovery.zip
Click to expand...
Click to collapse
why dont you try with recovery.img extract it from zip and use this command fasboot flash recovery recovery.img
Mile_zdr said:
why dont you try with recovery.img extract it from zip and use this command fasboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks mile_zdr. My Bad. Looks like it wrote ok (writing "recovery" ... OKAY) when i reboot and choose recovery option it still boot loops. :/ maybe im flashing the wrong recovery? Should any sensation recovery work?
Edit : Just flashed the sensation clockwork mod recovery successfully but still getting the boot loop when i hit recovery in the boot loader.
mickey909 said:
Thanks mile_zdr. My Bad. Looks like it wrote ok (writing "recovery" ... OKAY) when i reboot and choose recovery option it still boot loops. :/ maybe im flashing the wrong recovery? Should any sensation recovery work?
Edit : Just flashed the sensation clockwork mod recovery successfully but still getting the boot loop when i hit recovery in the boot loader.
Click to expand...
Click to collapse
i think your only option now is to flash a ruu.exe
then try again with recovery
rzr86 said:
i think your only option now is to flash a ruu.exe
then try again with recovery
Click to expand...
Click to collapse
Thanks rzr86, could you give me more info please? do i just put the ruu in the same tools folder and flash the same as the recovery?
mickey909 said:
Thanks rzr86, could you give me more info please? do i just put the ruu in the same tools folder and flash the same as the recovery?
Click to expand...
Click to collapse
no in that way
read here for more info
http://forum.xda-developers.com/showthread.php?t=1672425
rzr86 said:
no in that way
read here for more info
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Thank you so much guys, think im beggining to understand it now. I have 1 more massive favour. Im struggling to find the right ruu for my phone, can someone point me in the right direction please?
since you are on S-OFF change your cid to supercid and choose any ruu you want
also remove your imei and serial number
don't show them in public
but i noticed something else
how in the hell you have ics hboot version with gingerbread firmware?
rzr86 said:
since you are on S-OFF change your cid to supercid and choose any ruu you want
also remove your imei and serial number
don't show them in public
but i noticed something else
how in the hell you have ics hboot version with gingerbread firmware?
Click to expand...
Click to collapse
Thats a very good question rzr86 I think i have found the right ruu but i could only find one with a firmware base of 1.73 and my phone is currently 3.33. does it matter or will have to somehow downgrade my firmware to match the ruu?
mickey909 said:
Thats a very good question rzr86 I think i have found the right ruu but i could only find one with a firmware base of 1.73 and my phone is currently 3.33. does it matter or will have to somehow downgrade my firmware to match the ruu?
Click to expand...
Click to collapse
using a gingerbread ruu it will automatically downgrade your firmware too
rzr86 said:
using a gingerbread ruu it will automatically downgrade your firmware too
Click to expand...
Click to collapse
I've successfully managed flash the stock rom but i still have the boot loop. :/
mickey909 said:
I've successfully managed flash the stock rom but i still have the boot loop. :/
Click to expand...
Click to collapse
bootloop in recovery or in the rom?
rzr86 said:
bootloop in recovery or in the rom?
Click to expand...
Click to collapse
I found the stock rom for my phone, double clicked the .exe and it went through all the loading process and installed the stock ruu onto my phone but the problem i started with is still there. If i turn the phone on it just goes to the htc logo and then reboots. If i hold power + vol down then pick recovery it does the exact same boot loop. thanks for your help!! :good:
mickey909 said:
I found the stock rom for my phone, double clicked the .exe and it went through all the loading process and installed the stock ruu onto my phone but the problem i started with is still there. If i turn the phone on it just goes to the htc logo and then reboots. If i hold power + vol down then pick recovery it does the exact same boot loop. thanks for your help!! :good:
Click to expand...
Click to collapse
i think your emmc is damaged
i don't know what else to suggest mate
wait if you get better solutions
rzr86 said:
i think your emmc is damaged
i don't know what else to suggest mate
wait if you get better solutions
Click to expand...
Click to collapse
Ok, Thanks for all your help friend. Im starting to think its a hardware fault now.
As the tittle says, i cant find it anywhere and im not able to reset my phone to its original stock without it.... please pm me with a link or file..or reply to this post...thank you!!
All which is available you will find in my index thread. See the link in my signature.
old.splatterhand said:
All which is available you will find in my index thread. See the link in my signature.
Click to expand...
Click to collapse
I am aware of this site, but it only contains the RUU for Sprint and cricket.....you don't have the Boostmobile version...
RUU_K2_CL_JB_45_S_Sprint_WWE_Boost_2.06.653.6_Radi o_1.12.50.0516_10.30.42.25_NV_NV_Boost_2.20_150_re lease_333541_signed.exe
That is all, that is available.
old.splatterhand said:
RUU_K2_CL_JB_45_S_Sprint_WWE_Boost_2.06.653.6_Radi o_1.12.50.0516_10.30.42.25_NV_NV_Boost_2.20_150_re lease_333541_signed.exe
That is all, that is available.
Click to expand...
Click to collapse
I get this error when ever i try it on my boostmobile..:/
As long as you don't put any info about your phone, i can not help you.
@yoshirocks9, are you S-On? S-Off? Locked or unlocked Bootloader? OS 4.2.2, or 4.1.2, or 4.0.4?
Modding.MyMind said:
@yoshirocks9, are you S-On? S-Off? Locked or unlocked Bootloader? OS 4.2.2, or 4.1.2, or 4.0.4?
Click to expand...
Click to collapse
I am relocked and s-on
yoshirocks9 said:
I am relocked and s-on
Click to expand...
Click to collapse
If you are running 4.2.2 it won't work. Would have to be S-Off since the RUU is based on 4.1.2.
Modding.MyMind said:
If you are running 4.2.2 it won't work. Would have to be S-Off since the RUU is based on 4.1.2.
Click to expand...
Click to collapse
Once I'm s-off will the ruu work even on 4.2.2?
yoshirocks9 said:
Once I'm s-off will the ruu work even on 4.2.2?
Click to expand...
Click to collapse
Yes
Stock Recovery or not
Modding.MyMind said:
Yes
Click to expand...
Click to collapse
@Modding.MyMind I want to go back to stock JB, question? to you... I must have stock recovery before I run RUU ??????
banderz777 said:
@Modding.MyMind I want to go back to stock JB, question? to you... I must have stock recovery before I run RUU ??????
Click to expand...
Click to collapse
If S-On then yes because you will be required to relock the bootloader in order to run the RUU.
The RUU must be equivalent to your devices current OS or greater. Otherwise you will be required to S-Off your device.
Modding.MyMind said:
If S-On then yes because you will be required to relock the bootloader in order to run the RUU.
The RUU must be equivalent to your devices current OS or greater. Otherwise you will be required to S-Off your device.
Click to expand...
Click to collapse
No I am S-Off , can I run the OTA JB 422 zip also, do I just rename it to PL80IMG.zip and put it on my ext sd card and boot up ???????
banderz777 said:
No I am S-Off , can I run the OTA JB 422 zip also, do I just rename it to PL80IMG.zip and put it on my ext sd card and boot up ???????
Click to expand...
Click to collapse
No, but you can do that with the firmware.zip found inside the OTA.
If you want, run the RUU, then boot up your device so it can set itself up real quick. You should still be S-Off after running it. Now, boot to your stock recovery. When stock recovery loads up be quick to press the volume up key then the power key ans hold them both for just seconds and then release.
You may fail at the above procedure so just keep trying until you get the feel of it. If successful a recovery will show up that looks very similiar to CWM. From that screen you will be able to manually update your device back to 4.2.2 with the OTA.
Modding.MyMind said:
No, but you can do that with the firmware.zip found inside the OTA.
If you want, run the RUU, then boot up your device so it can set itself up real quick. You should still be S-Off after running it. Now, boot to your stock recovery. When stock recovery loads up be quick to press the volume up key then the power key ans hold them both for just seconds and then release.
You may fail at the above procedure so just keep trying until you get the feel of it. If successful a recovery will show up that looks very similiar to CWM. From that screen you will be able to manually update your device back to 4.2.2 with the OTA.
Click to expand...
Click to collapse
So just leave OTA name as is, don't rename it and but it on my ext sd ?
banderz777 said:
So just leave OTA name as is, don't rename it and but it on my ext sd ?
Click to expand...
Click to collapse
Yes sir.
Modding.MyMind said:
Yes sir.
Click to expand...
Click to collapse
Sweet and Thanks Modding.MyMind I have rooted a few phone ie HTC Aria, HTC Mytouch 4g, HTC Senation.... yes love my HTC's LOL
banderz777 said:
Sweet and Thanks Modding.MyMind I have rooted a few phone ie HTC Aria, HTC Mytouch 4g, HTC Senation.... yes love my HTC's LOL
Click to expand...
Click to collapse
I cannot fully remember if the stock recovery will access the external sdcard. If by some chance it does not (which would be odd lol) then just move the OTA over to your internal and go from there.