I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Do you have the latest TWRP 2.4.1.0 ? (did you try reflashing your recovery?)
What android did you have before unlocking your bootloader? 4.0.3 or 4.0.4?
(and don`t panic If nothing works there is always a solution by relocking your phone and flash the ruu for your phone from here)
http://www.androidfiles.org/ruu/?dir=VilleC2
take a look here:
http://forum.xda-developers.com/showpost.php?p=37498221&postcount=309
impactor said:
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Click to expand...
Click to collapse
What's was you on before flashing a custom rom? because just a guess but I think it was 4.0.3 if that is so then try TrickDroid for S3 and get v3 which is 4.0.3 so should work.
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
impactor said:
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
Click to expand...
Click to collapse
No only v3 but if you can get an RUU thats more up to date then do that and the v4/5 should work.
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
KindleFireGuy said:
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Em what he said he did.
You cannot flash S4 roms with an S3 phone, have you made sure that the Roms you flash are specifically assigned for S3? Cuz most are S4
Thanks, guys. That was HBOOT problem. I flashed latest RUU and then I was able to use JB roms.
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
pcout64 said:
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
Click to expand...
Click to collapse
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
asdfasdfvful said:
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
Click to expand...
Click to collapse
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
pcout64 said:
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
Click to expand...
Click to collapse
Still new to xda, but check this out?
http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA
(ctrl + f and find "ruu")
My mainver is not listed, I have already seen this page
The page was last edited in November of 2012, I think it's a bit out of date
Related
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
herzbert said:
Hey Guys,
yesterday I wanted to revert my ROM from CM10 to TrickDroid 7.1. In TWRP 2.2.1 I wiped caches and did a factory reset and then flashed TD 7.1 following torxx's instructions (wipe, install ROM, flash boot.img with his boot flash script, let the ROM boot). After the reboot the phone hang. The startup sound came through but then no further action for about 7 Minutes.
Was that too little time waiting? Or is there any other issue interfering the boot process after reverting from Android 4.1.1 to 4.0.4 Sense?
If anyone can help is much appreciated. Even if I look stupid afterwords
Burkhard
Click to expand...
Click to collapse
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
el_smurfo said:
Perhaps your hboot does not allow flashing or boot.img? Have you tried the fastboot method of flashing boot.img? How about reverting to a nandroid of a sense based ROM, then flashing TD?
Click to expand...
Click to collapse
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Checked MD5?
torxx said:
Checked MD5?
Click to expand...
Click to collapse
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Same here... But fine now
herzbert said:
They correspond.
If nothing else helps I will try to install the latest RUU and then flash a ROM. But I wanna circumvent the relock and unlock procedure.
Btw: Did anybody notice that the unlock code changes after an update of HBoot? Nobody mentioned that when the new base was released.
Click to expand...
Click to collapse
Hey there,
I was having the same problems as you messioned. I flashed the boot.img through fastboot myself and some how it then worked Did not have an problems with flashing the boot.img before. But maybe its worth a try.
Of course you need to use fastboot!!
Did not try yet to flash the RUU. There was an update of CM10 yesterday. The heavy battery drain is gone with this update and there is no urgent need to go back to TrickDroid right now.
herzbert said:
Prior to CM10 I was on latest stock ROM. Before that I had custom ROMs. HBoot on my phone after the OTA update is 1.14. Flashing the boot image of CM10 was no problem.
In order to use the phone I reinstalled CM10 and it works.
The boot images were flashed within fastboot. I do not know any other way to flash a boot image.
I dont have a nandroid backup.
Click to expand...
Click to collapse
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Sent from my HTC VLE_U using Xparent SkyBlue Tapatalk 2
LikeaG2root said:
HBoot 1.14 is the problem. Anything above 1.09 needs special steps to flash unlike simply flashing with twrp as with 1.09 and below.
Alright, so, what are these special steps? Can you tell? If its not flashing the within recovery and push the boot.img via fastboot to the phone I would be very interested. My previous HBoot version was 1.13. Flashing ROMs was never a big deal. Also not going to CM9 and back to sense based ROMs.
Click to expand...
Click to collapse
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
HighRoIIer said:
I am on hboot 1.14 and it worked via fastboot. Like you mentioned yourself you reinstalled CM10 and it booted, therefore your previous flash of the boot.img didn't work. So just flash the boot.img via bootloader and fastboot and you should be good...
Click to expand...
Click to collapse
I did also flash the boot.img via fastboot. Why do you say that anyway? Is there another method to flash a boot.img?
you didn't mention wiping System as part of the full wipe--needs done
Partially solved
rugmankc said:
you didn't mention wiping System as part of the full wipe--needs done
Click to expand...
Click to collapse
Right, I did not mention it because system is wiped by TWRP during flashing the ROM. So there was no need to wipe it seperately. But maybe my mistake was not to wipe data and the new "asec" folder messed things up.
I'll never know because yesterday I did a complete wipe including the SDCard. Afterwards I was able to install TrickDroid flawlessly.
Thank you all for your efforts.
To the Guru of this forum. After my last rom flashing my device is keeping booting into recovery :crying:. Is it briked ? If so my only hope is the unbricking project ? Thanks in advance.
What recovery are you running?
Can you use the power menu within recovery to boot into bootloader?
Also, please provide as much pertinent info as possible, ie: rom you flashed, firmware, s-off or s-on, locked or unlocked. With your description it's basically like saying, "my car makes a noise all the time. what is causing it?".
Its not bricked.If u can enter recovery
Sent from my HTC sensation
Sorry you are right:
What recovery are you running? 4Ext
Can you use the power menu within recovery to boot into bootloader? yes
The device is HTC unlocked with S-On.
Rom JBMIUI v4.1 2.8.31 R2.
HBOOT 1.27.0000
firmware 3.33.401.6
I've format everything but SD. Restored the most recent back up done today before flashing. Once it reboots HTC logo comes up once, black screen, HTC logo, 4Ext is coming up saying that smartflash it is set to update the boot partition on next system start asking if this should be removed.
I've downloaded and installed again PG58IMG *different files using bootloader
I've founded a 3.33.401.6-Unsecured-Boot.img,+Root+Busybox zip file that can be installed via recovery but it did not help.
At this point I need a bit of help to look into the right direction and I'm not sure that Unbrick_Pyramid is the right way.
Thanks again.
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Hi. Manage to flash a stock 3.33.
It stopped to reboot straight into recovery.
Sits now on HTC logo now for about 10 mins. I plan to let him run for 1 hr and see what happens.
Was thinking to install CWM on the basis that could be a 4ext recovery issue, toughs?
GROGG88 said:
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Skipjacks said:
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
DiscreteTask said:
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Click to expand...
Click to collapse
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Skipjacks said:
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh
version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
Click to expand...
Click to collapse
DiscreteTask said:
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Click to expand...
Click to collapse
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Hi.
I did not use any backup only fresh ROMs: ARHD, Elegantia, but also stock ROMs I could find.
I've tried also some PG58IMG with ROM included.
Cheers.
Skipjacks said:
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Click to expand...
Click to collapse
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Hallo, after trying all option the following did work for me:
- re-lock bootloader via fastboot oem lock
- apply stock ROM founded in this list http://forum.xda-developers.com/showthread.php?t=1074559
- rebooted fine
I guess that HTC RUU had some superpower and erase and installed whatever file(s) were corrupted.
Now I'm on stock 3.6 - fw 3.33.401.106 - radio 11.76A.3504.00UU_11.24A.3504.31_M
HBOOT 1.29 - S-ON - Relocked.
Standard Recovery.
Now I'm reading how to return my device to S-OFF w/o damaging it again.
Many thanks to skipjacks & groog88 :good:
Skipjacks said:
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Wipe flash Rom flash boot IMG sit back enjoy
ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Different kernel. it is using the 2.41 RUU. So go ahead and flash the boot.img
Here's what you should do for any new ROM with a different kernel.
Wipe System
Factory Reset
Flash boot.img
Flash the ROM
flash gapps (if AOSP based)
reboot and have fun
When doing a nandroid backup, it is only necessary to backup
System
Data
Boot
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
You backed up fine, it just takes up a little more space.
You have to extract the boot.img from the ROM and put it in the same folder as fastboot.exe
open command prompt, and navigate to the folder fasboot.exe is in and do the following command
fasboot flash boot boot.img
If it gets stuck at waiting for device, reboot into your bootloader, boot into fastboot from there. and then try again.
ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
Viper is the Rom u flash it from twrp it's. azip file that's fkashable so make it easy and flash viper there and than flash the boot IMG from fastboot the command is all over the forums I thinks it fastnoot flash boot.img
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
DvineLord said:
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
Click to expand...
Click to collapse
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
ImagioX1 said:
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
Click to expand...
Click to collapse
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom.
If you want true stock 2.20 then you will have to relock your bootloader and then run the 2.20 RUU. You would only want to do this if making a warranty claim or something. If you want stock rooted, then yes, do what I said above
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok got it. I do appreciate your help. Flashing now.
downgrading only refers to the ruu not the zipped roms. so you can't run 1.85 ruu after running 2.20 ruu/ota but you can still flash a rom based on 1.85.
if you are reflashing the same rom you don't have to reflash boot.img but if you are flashing a new rom then you need to flash boot.img. 7-zip will tell you the crc32 of files so you see tell if it's a different checksum.
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
ImagioX1 said:
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
Click to expand...
Click to collapse
That's because you flashed the Voodoo mod, it's apart of the mod, theres a chinese part and a english one called "Dolby Digital" or "Dolby Surround"
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
CrossFire78 said:
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
Click to expand...
Click to collapse
Most people have good luck w/out flashing another radio.
ronnie498 said:
Most people have good luck w/out flashing another radio.
Click to expand...
Click to collapse
Hmm. Might there be a patch I'm missing out on? I just flashed one file -ViperXL 3.1.0 JB - Android File Host (692MB)
edit- Works now after another reinstall installed boot image first this time.
Hey Guys.. Just bought a HTC one x. It came rooted and flashed with CM10.. I dont want that, looking for the STOCK rom it came with or something close/debloated..
I found this.. But have no idea on how to flash.. If someone can be kind enough to help me out Id really apreaciate it!
http://forum.xda-developers.com/showthread.php?t=2029432
Also, Is there a STOCK rom like just a flashable.zip on here? Please someone help. Thanks guys hope to be able to contribute alot to the ONE x down the line.
To flash that ROM, download to your phone, or copy it from your computer to the phone's SD. In TWRP do a factory reset, wipe Dalvik and cache, flash the ROM. If you are on hboot 1.14, flash the boot.img using fastboot (you have to extract it from the ROM zip using a unzip program on your computer).
For stock rooted ROMs (flashable in TWRP just like custom ROMs) look under stock rooted in my index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Thanks for the response..
What is hboot 1.14? Is that another recovery?
Btw, how do I know what stock rooted rom is for me? I have a ATT htc one x
When i do find the stock one, do I just download to my phone, factory reset, wipe dalvik and cache and flash it? Or do i need other specials instructions..?
Sorry for all the questions, I am so used to Samsung s2 flashing, so there are a few things that i need to get used to.
Like what is a bootloader?
redpoint73 said:
To flash that ROM, download to your phone, or copy it from your computer to the phone's SD. In TWRP do a factory reset, wipe Dalvik and cache, flash the ROM. If you are on hboot 1.14, flash the boot.img using fastboot (you have to extract it from the ROM zip using a unzip program on your computer).
For stock rooted ROMs (flashable in TWRP just like custom ROMs) look under stock rooted in my index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
This will provide you with a mountain of knowledge
http://forum.xda-developers.com/showthread.php?t=2044729
[Guide][Noob Proof]How To Install Roms & Kernels it helps.
Ask back for more answers if needed.
Sent from my HTC One X using xda app-developers app
how do i get into recovery again when aroma installer stalls up?
I held down on the power button and now its boot looping..
I tried to install CLEAN ROM 5.1... I installed according to OP instructions and got to aroma, it froze at 10% so I held power button down and how do how i get into recovery now?
abesgs2 said:
how do i get into recovery again when aroma installer stalls up?
I held down on the power button and now its boot looping..
Click to expand...
Click to collapse
abesgs2 said:
I tried to install CLEAN ROM 5.1... I installed according to OP instructions and got to aroma, it froze at 10% so I held power button down and how do how i get into recovery now?
Click to expand...
Click to collapse
Tell us what you've done up until that point so far.
Sent from my HTC One X using xda app-developers app
Phone is rooted and I assume it also has bootloader.. Because when i go to reboot options previously it said reboot to bootloader..
I downloaded clean rom 5.1
Put on my SD card
went into recovery
wiped data/factoryreset
Install Clean ROM
Clean rom took me to aroma
I selected everything I wanted in Aroma
Aroma froze at 10%
I waited
Then I got inpatient and thought its frozen to I powered it down to start over
now its bootlooping
Cant get back into recovery... Just watching it flash white to HTC screen then to the colorful X...
Press and hold volume down and power button until bootloader white screen appears.
Use volume keys to navigate .Go down to recovery and click power button to select it.you should now boot into recovery.
I think you just need to be patient and wait.
If not.
Go flash the boot.img file from the cleanrom zip in fastboot
Sent from my HTC One XL using xda app-developers app
What is a fastboot?
hyun18 said:
Press and hold volume down and power button until bootloader white screen appears.
Use volume keys to navigate .Go down to recovery and click power button to select it.you should now boot into recovery.
I think you just need to be patient and wait.
If not.
Go flash the boot.img file from the cleanrom zip in fastboot
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
hyun18 said:
Press and hold volume down and power button until bootloader white screen appears.
Click to expand...
Click to collapse
You actually need to release the power button to actually get the bootloader screen to come up. But keep holding volume down rocker until the bootloader screen appears.
Alright, i got that to work! thanks alot..
I just really need some help getting back to the stock ROM. i opened your page about the stock ROM directory but cannot figure out which one best suits me.. to give some background..
The phone is currently running on CM10 rom, It is unlocked and rooted of course..
It is the ATT dual core version S4 processor..
Which stock ROM is best for me and how do I flash it if I am on CM10.?
Thanks you have been very helpful, good to know theres people like you to help.. im coming from the galaxy s2 and alot of this stuff is like french to me..
redpoint73 said:
You actually need to release the power button to actually get the bootloader screen to come up. But keep holding volume down rocker until the bootloader screen appears.
Click to expand...
Click to collapse
abesgs2 said:
Alright, i got that to work! thanks alot..
I just really need some help getting back to the stock ROM. i opened your page about the stock ROM directory but cannot figure out which one best suits me.. to give some background..
The phone is currently running on CM10 rom, It is unlocked and rooted of course..
It is the ATT dual core version S4 processor..
Which stock ROM is best for me and how do I flash it if I am on CM10.?
Thanks you have been very helpful, good to know theres people like you to help.. im coming from the galaxy s2 and alot of this stuff is like french to me..
Click to expand...
Click to collapse
All of the ROMs and mods listed on my index thread will work for your version of phone. If you want a stock experience, AT&T stock 2.20 is probably a good enough place to start as any.
Hboot (bootloader) is the white screen that comes up after you've done the volume down/power sequence. On that screen it will tell you what hboot version you are on. What version do you have?
redpoint73 said:
All of the ROMs and mods listed on my index thread will work for your version of phone. If you want a stock experience, AT&T stock 2.20 is probably a good enough place to start as any.
Hboot (bootloader) is the white screen that comes up after you've done the volume down/power sequence. On that screen it will tell you what hboot version you are on. What version do you have?
Click to expand...
Click to collapse
Ok this is what the white screen says exactly. From this can you tell me if my bootloader is unlocked or do i have to do that first?..
***Tampered***
***Unlocked***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012 14:36:28
FASTBOOT
vol up blah blah stuff..
BOOT LOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
So i guess i have hboot 1.14, does this also mean my bootloader is unlocked and if so, how would i flash that stock ROM?
Thanks man you have been a big help thus far
Yes, bootloader is unlocked, and hboot is 1.14.
Also, please confirm that your recovery is TWRP (should have a blue screen that says "Team Win" when you boot recovery. If not, come back here and tell us.
Normally, all you would have to do to flash the stock rooted ROM is:
1) Download or move the file to the phone's internal SD memory.
2) Go into hboot, then boot TWRP recovery.
3) In TWPR (NOT in hboot) go to "Wipe" and do a factory reset. You will lose any data on the phone, except the SD. So back anything up you don't want to lose before you start any of this.
4) Wipe Dalvik and cache
5) Select "Install" in TWRP and select the ROM file.
6) Wait until its done flashing and select "reboot".
Now, since you are on hboot 1.14, you have an added complication. The hboot plugged the hole by which boot.img was flashed automatically in recovery. Since you can no longer do this, you have to extract it and flash it from your computer using a tool called fastboot. In short, the steps are:
a) Setup fastboot using the guide here: http://forum.xda-developers.com/showthread.php?t=1754018
b) With the ROM file on your computer, use a unzip program to open the ROM zip file.
b) In the base directory, you should see a file called "boot.img". Unzip this file, and move it to the folder that contains fastboot.exe (that you just setup in step (a).
c) Connect your phone via USB, go into bootloader, and select fastboot mode.
d) Flash the boot.img with the command:
fastboot flash boot boot.img
e) Reboot
This is probably a bit overwhelming, as having hboot 1.14 forces you to learn how to use fastboot (which is in itself, a bit intimidating). But if you want to do any other ROM flashing, you should know how to do this, as your hboot will require it for almost all ROMs.
Alternately, you can just try to flash CleanROM again. Not sure why it stalled, it should work fine. Plus, CleanROM flashes the boot.img for you, so no need to do it separately. This would at least get you on a somewhat stock, Sense based ROM to start with. And CleanROM is quite nice. Its mostly stock, just a few added features, performance enhancements, and bloat is cleaned up.
Yes I do have twrp recovery 2.3.XX
Ok I will go through those steps and ask any questions if I get stuck..
Btw how would you suggest flashing clean rom? I tried it according to OP instructions but no dice..
what are the proper wiping procedures for it?
Thanks again you are alot of help I feel better about keeping this phone
EDIT: Just flashed clean rom again to try it out..
I flashed like this
reboot to TWRP
wipe factory reset, wipe dalvik, cache,
flash rom
go through aroma install boot.img
put all the addons i want
let it rip, then it rebooted, and started to bootloop so im now restoring a back up..
Do i need to wipe SYSTEM after i factory reset?
EDIT: Looking for the 2.20 stock rom, but the mirror is gone/download is gone.. do you know where I can find another download for it? Its not on scottsroms.com any more
Wiping SYSTEM is not needed. It just formats the portion of the memory the ROM resides, so this gets wiped when you flash the ROM, anyway.
Not sure why CleanROM is not flashing or booting. I'm on the older hboot. You may go over to the CleanROM thread, and do some reading, or ask there.
redpoint73 said:
Wiping SYSTEM is not needed. It just formats the portion of the memory the ROM resides, so this gets wiped when you flash the ROM, anyway.
Not sure why CleanROM is not flashing or booting. I'm on the older hboot. You may go over to the CleanROM thread, and do some reading, or ask there.
Click to expand...
Click to collapse
Im going to give it another go using the Hboot method, wish me luck thanks for all your help.
Ima try that light ACR rom.. i asked about earlier, i assume its going to be the same flashing procedure using the hboot.
thanks!
I believe I have given up. This whole ADB. fastboot, hboot, thing is driving me nuts. Im going to sell this phone and just get one stock unrooted. Its pretty smooth stock anyways..
Thanks for your help again.
abesgs2 said:
I believe I have given up. This whole ADB. fastboot, hboot, thing is driving me nuts. Im going to sell this phone and just get one stock unrooted. Its pretty smooth stock anyways..
Thanks for your help again.
Click to expand...
Click to collapse
Sell it and buy a new one stock unrooted? Why not just lock the bootloader and run the RUU to return to stock unrooted?
TWRP 2.4.4.0
CID 11111111 (super cid)
hboot 1.14
S-OFF
I just tried updating to Viper 3.2.6 from 2.4.0
Got S- Off, proceeded to install it.
Wiped Cache, Dalvik and System.
Install
Restart.
Stuck at logo.
Tried flashing boot.img from fastboot. still stuck
Code:
fastboot erase cache
still stuck.
Any help would be appreciated.
While writing this I'm going to attempt going back to 2.4.0 Viper but I would like guidance on making sure I can make it onto 3.2.6.
divertedmind said:
TWRP 2.4.4.0
CID 11111111 (super cid)
hboot 1.14
S-OFF
I just tried updating to Viper 3.2.6 from 2.4.0
Got S- Off, proceeded to install it.
Wiped Cache, Dalvik and System.
Install
Restart.
Stuck at logo.
Tried flashing boot.img from fastboot. still stuck
Code:
fastboot erase cache
still stuck.
Any help would be appreciated.
While writing this I'm going to attempt going back to 2.4.0 Viper but I would like guidance on making sure I can make it onto 3.2.6.
Click to expand...
Click to collapse
How long have you waited? Sometimes the first install takes a long time to load. To be sure give it maybe 10mins to load. Then if that doesn't work make sure it wasn't a bad download by comparing the md5. If that is good try a different recovery. TWRP 2.4.4.0 is know to have issues. Try an earlier version like 2.3.1 and see what happens.
ImagioX1 said:
How long have you waited? Sometimes the first install takes a long time to load. To be sure give it maybe 10mins to load. Then if that doesn't work make sure it wasn't a bad download by comparing the md5. If that is good try a different recovery. TWRP 2.4.4.0 is know to have issues. Try an earlier version like 2.3.1 and see what happens.
Click to expand...
Click to collapse
Thanks. Will check if my download went bad and will also try changing back to 2.3.1 recovery. Thanks for the heads up !
Also btw just to confirm, Does 3.2.6 have a custom load up screen like 2.4.0/2.4.1 did ?
Because I do get stuck at htc logo + red text. just covering my bases.
Yes it does.
It sounds like a bad file or bad flash. Twrp has issues with wiping. Go back to 2.3. Then do a fresh install check md5 as was said. It's also a good idea to flash the one x full wipe tool.
Sent from my HTC One X using xda app-developers app
Thanks all. Redownloaded 3.2.6. Did the hash check. Didn't realize my network was messing up my downloads so badly. I'm going to have to do some tests when I get home. ^_^
Solved.