Related
I'm having problems flashing my Desire S with ICS based roms. GB roms work fine, but any ICS rom I flash gets stuck on boot on a lit up black screen. I have tried a variety of roms, flashed both on CWM and 4EXT but the issue persists. Is there some kind of special procedure for ICS roms ?
Did you
1. Wipe all partitions except SD
2. Wipe dalvik + cache
Edit : And the procedures same for flashing ics and gb roms, unless the OP specifically tells you to do otherwise
I did all possible wipes and It's still the same. Any more ideas ?
tomkow4 said:
I did all possible wipes and It's still the same. Any more ideas ?
Click to expand...
Click to collapse
did u u unlock with HTCDEV.com ? if u did just flash the boot.img inside the rom you want if u never then either the rom takes a long time to boot or your not doing the wipe properly
give me some specs of your phone
Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.
tomkow4 said:
Ok, I'll run through my process. I did unlock my phone via HTCDEV, then rooted it via SuperOneClick (meaning I still have HBoot 2.00.0002 and S-ON), then flashed it by flashboot with CWM, now I have 4EXT. What I always did whas do a wipe data/factory reset and flashed. Now inspired by vodka69er I did that and clear dalvik, cache, format all but sd - and then flashed - still the same.
Click to expand...
Click to collapse
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.
He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something
Vodka69er said:
He's been able to flash the gb based roms , only trouble with the ics ones. That means he already knows to flash the boot img separately(unlocked with htcdev) or am I missing something
Click to expand...
Click to collapse
This. Exactly. I mean I have a MIUI GB rom so, I guess it's not about flashing a rom but trouble with ICS ones. So I figured that those must have something different about them or have a specific prerequisite. Others have flashed their D S's, so I'm kind of lost.
Can you post what you see on your bootloader
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT - 2.00.0002
Radio - 3822.10.08.04_M
eMMC - boot
Aug 22 2011, 15:22:13
@op
I know that this is covering old ground, but I've not seen an actual answer
Have you ever used 'fastboot flash boot NAME.IMG' command?
Swyped from my DesireS
http://www.androidauthority.com/desire-s-root-s-off-hboot-2-00-0002-superoneclick-74470/ - this is the guide I followed.
On a side note, I did a full wipe of everything I could and still no luck with ICS roms. I think I'll leave it alone.
You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS
ben_pyett said:
You still didn't answer the question that I asked in the above post, the guide that you have doesn't cater for separately flashing the boot , which is what you need to do. The guide only tells you gore to instal recovery and root
Which (as people have been saying) means that i suspect that your ICS installs have no kernels and therefore don't/can't boot
What ROM are you running now?
As after wiping all nothing should boot, unless CWM wipe all doesn't wipe boot?
Swyped from my DesireS
Click to expand...
Click to collapse
To answer directly - I don't remeber/don't think so. But honestly didn't care much since my roms ran. Right now I'm on MIUI.
But the remark on the kernel got me thinking - I don't really know how to approach this, should I find some kernel and flash it?
On your pc you need to open the ICS ROM zip file and take out a file called boot.img
After flashing the Rom you must then use the fastboot command from your PC, as you did when you flashed your recovery.
You must then issue the command 'fastboot flash boot boot.img'
see below for the full instructions
HappyEmu said:
If you unzip your ROM's Zip-file (the one you want to flash, you'll find a file called "boot.img". Move it into the same folder as your adb and fastboot executables (Android SDK) and flash it using fastboot.
To be a little more specific:
1. Extract boot.img from ICS rom zip file and move it in the same folder as your fastboot.exe (Android SDK) on your PC
2. Flash the ICS Rom as usual from recovery (don't forget to first perform the full wipe/format including the boot partition)
3. Boot into fastboot mode, connect your phone to your PC and flash boot.img using fastboot
Code:
fastboot flash boot $pathToYourBootIMG\boot.img
4. Reboot
Click to expand...
Click to collapse
Swyped from my DesireS
Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
eyahl said:
If you unlocked via htcdev you need to extract the boot.img from your desired ROM. After flashing the ROM you need to flash the boot.img manually via adb. You have to do this each time you flash a new ROM.
Sent by my fingers to your head.
Click to expand...
Click to collapse
*Bump*
Sent by my fingers to your head.
suku_patel_22 said:
Your GB room worked as they were running on the stock kernel
ICS won't work this way.
As Ben has mentioned you need to flash the boot.img
Click to expand...
Click to collapse
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?
tomkow4 said:
4EXT seems to flash the kernel upon installation of specific roms, but I still did it manually and ... nothing. It still goes into a coma upon boot. Maybe I'll do a video of what I'm doing when I get back from work, cause now I'm having problems with some other roms - they freeze on bootscreen. Maybe it has something to do with my phone being S-ON?
Click to expand...
Click to collapse
I suspect that you're suffering the problem on other ROMS now as you're wiping the boot partition and therefore have no kernel.
[Q] How long do you wait on boot? you must be patient as first boot can take a while (although not longer than 10minutes).
A video would be a great way of showing the problem...Try to capture everything....
Your bootloader screen....
All the partition wipes
The Rom flash
The fastboot boot.img flash
and then what happens after...
Kind of noobish on my end, but as I was making the video - and did everything according to protocol just as earlier - it worked . I flashed BlackICE 5.5. Christ. Thanks anyway for the patience guys (I assume )
I somehow have locked myself out but still have access to CWM and FASTBOOT. So, how do I use FASTBOOT to install a rom? Is it even possible? I just flashed CWM again, but still cannot get my CWM Backup copy to work.
up.
My friend has same issue, change build.prop.. no backup, no adb, only fastboot with cwm. Any ideas? Ext SD don't work in CWM\TWRP.
upd: Answer myself - Plug into usb in recovery, update driver in device manager to ADB Device, use adb
See here http://forum.xda-developers.com/showthread.php?t=1680570
What happens if clockworkmod recovery cannot read zip files???
fastboot flash zip rom.zip
prototype7 said:
fastboot flash zip rom.zip
Click to expand...
Click to collapse
Do I need a system.img file???
ri123 said:
Do I need a system.img file???
Click to expand...
Click to collapse
No, just the regular zip, you could also try reflashing the recovery (fastboot flash recovery recovery.img).
prototype7 said:
No, just the regular zip, you could also try reflashing the recovery (fastboot flash recovery recovery.img).
Click to expand...
Click to collapse
What about fastboot update command???
No
Hit the thanks button if i helped
Is this procedure compatible with the meta inf folder???
noooo!! i try "fastboot flash zip rom.zip" and it says FAILED remote partition does not exist!! what can i do now??
nooo!!! it says ( failed remote partition does not exist)
Xperia S with the same problem mine says
(remote: Partition not found)
The command you can used to flash a zipped ROM like the stock one from Asus is...
Fastboot -i 0x0b05 flash system yourrom.zip
I usually flash these using twrp recovery but I think that will do it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Maybe I just can't follow instructions or anythng, but I attempted my first ROM flash and it didn't work.
I tried the Blackbean 5 ROM, with TWRP. I found a set of instructions saying how to flash with TWRP, so I followed them, and I think I've soft-bricked my TF300T. Just stays on the Asus logo, and in top left it says "The Device is UnLocked."
I DID make a recovery in TWRP, and I attempted to flash that back with no luck.
Maybe I'm doing it wrong, so can someone help me out here?
funnel71 said:
The command you can used to flash a zipped ROM like the stock one from Asus is...
Fastboot -i 0x0b05 flash system yourrom.zip
I usually flash these using twrp recovery but I think that will do it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I tried this with the stock ROM, from their website, and it didn't help...
So I'm not sure what my problem is now.
Then again, when it comes to ROMs, I'm a noob.
EDIT: I still have TWRP, my recovery, and the Blackbean ROM .zip on the device.
TsarProdigy said:
Maybe I just can't follow instructions or anythng, but I attempted my first ROM flash and it didn't work.
I tried the Blackbean 5 ROM, with TWRP. I found a set of instructions saying how to flash with TWRP, so I followed them, and I think I've soft-bricked my TF300T. Just stays on the Asus logo, and in top left it says "The Device is UnLocked."
I DID make a recovery in TWRP, and I attempted to flash that back with no luck.
Maybe I'm doing it wrong, so can someone help me out here?
I tried this with the stock ROM, from their website, and it didn't help...
So I'm not sure what my problem is now.
Then again, when it comes to ROMs, I'm a noob.
EDIT: I still have TWRP, my recovery, and the Blackbean ROM .zip on the device.
Click to expand...
Click to collapse
Background first when stock were you JB or ICS? Blackbean OP does not specify. At the moment I'm to lazy to read through thread or flash to find the answer. If you were on stock JB you can only use JB roms, if you were on ICS you can only use JB after stock upgrade to JB.
Forget Blackbean for now and let's concentrate on getting you fully functional on stock again. If you were on ICS then download stock 9.4.3.30 and unzip once that leaves you with a zip. Place that zip on your ( /sdcard ) or external sdcard ( /Removable/MicroSD ) and flash with Twrp. If you were JB then the instructions are the same except use stock 10.4.2.13.
If you do this you will loose your recovery ( Twrp ) but you should have a functional unit.
Non stock rom install.
Be sure you use proper rom for your bootloader ( ICS or JB ). Choose one that gives you instructions as to what to wipe, etc. You can adlib after you get your feet wet. If the op gives instructions use them if not then you may or may not have a happy ending with generic instructions.:good:
If you need anything explained let me know and I'll step by step for what you don't understand.
The reply you tried to follow said "I think", you should have investigated before following. Don't get me wrong, I'm not saying that was incorrect but the poster was in doubt and you should be also.
When we say "I think" we kind of assume you are going to do some reading and be comfortable with everything before you continue.
I took a little time to look over Blackbean and as I suspected it is for the ICS bootloader not JB.
same problem
I am having the exact same problem. I did manage to install the clean rom 2.5 custom rom successfully originally, and i made a backup through CWM, but I cant install any other rom on there for some reason. Yesterday I managed to go back to stock Asus jellybean rom successfully, and then had to root it and install CWM again successfully. I have again tried again today to install that EuroSkank rom, but alas, I get stuck at the ASUS boot logo permanently and nothing happens?
What might I be doing wrong??
I am on Jellybean. Thankfully the CWM is working fine and I could also restore my cleanrom2.5 backup.
tobdaryl said:
Background first when stock were you JB or ICS? Blackbean OP does not specify. At the moment I'm to lazy to read through thread or flash to find the answer. If you were on stock JB you can only use JB roms, if you were on ICS you can only use JB after stock upgrade to JB.
Forget Blackbean for now and let's concentrate on getting you fully functional on stock again. If you were on ICS then download stock 9.4.3.30 and unzip once that leaves you with a zip. Place that zip on your ( /sdcard ) or external sdcard ( /Removable/MicroSD ) and flash with Twrp. If you were JB then the instructions are the same except use stock 10.4.2.13.
If you do this you will loose your recovery ( Twrp ) but you should have a functional unit.
Non stock rom install.
Be sure you use proper rom for your bootloader ( ICS or JB ). Choose one that gives you instructions as to what to wipe, etc. You can adlib after you get your feet wet. If the op gives instructions use them if not then you may or may not have a happy ending with generic instructions.:good:
If you need anything explained let me know and I'll step by step for what you don't understand.
The reply you tried to follow said "I think", you should have investigated before following. Don't get me wrong, I'm not saying that was incorrect but the poster was in doubt and you should be also.
When we say "I think" we kind of assume you are going to do some reading and be comfortable with everything before you continue.
I took a little time to look over Blackbean and as I suspected it is for the ICS bootloader not JB.
Click to expand...
Click to collapse
maggoty said:
I am having the exact same problem. I did manage to install the clean rom 2.5 custom rom successfully originally, and i made a backup through CWM, but I cant install any other rom on there for some reason. Yesterday I managed to go back to stock Asus jellybean rom successfully, and then had to root it and install CWM again successfully. I have again tried again today to install that EuroSkank rom, but alas, I get stuck at the ASUS boot logo permanently and nothing happens?
What might I be doing wrong??
I am on Jellybean. Thankfully the CWM is working fine and I could also restore my cleanrom2.5 backup.
Click to expand...
Click to collapse
( EuroSkank ) is also an ICS rom not JB - Clean rom 2.5 is JB. For now unless you have NVFlash you can't go back to ICS from JB and you can't run ICS rom with JB bootloader. (I'm using ICS and JB here to declare the bootloader )
Ok, Thank you very much.
tobdaryl said:
( EuroSkank ) is also an ICS rom not JB - Clean rom 2.5 is JB. For now unless you have NVFlash you can't go back to ICS from JB and you can't run ICS rom with JB bootloader. (I'm using ICS and JB here to declare the bootloader )
Click to expand...
Click to collapse
any1 with Partition not found problem, open zip and look at the folders, delete everything except folder you want (which is propably system) then write
fastboot flash system yourzip.zip
if this doesn't work for you then extract files from the folder and repack only files from the system folder and use the command above.
It doesn't work for me (dunno why) but it's something
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.
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
originalseven said:
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
Click to expand...
Click to collapse
Yes there is a sense kernel and one for non-sense roms (aosp)
Usually the dev will have a kernel link posted on their page
If you are hboot 1.14 or higher, and S-on, to be perfectly safe you should extract the boot.img for the ROM zip you are trying to flash, and flash it manually.
Also, be careful installing ROMs with GooManager (or similar apps, like ROM Manager). Not sure if it properly differentiates between the dual and quad core versions of the One X/XL.
redpoint73 said:
If you are hboot 1.14 or higher, and S-on, to be perfectly safe you should extract the boot.img for the ROM zip you are trying to flash, and flash it manually.
Also, be careful installing ROMs with GooManager (or similar apps, like ROM Manager). Not sure if it properly differentiates between the dual and quad core versions of the One X/XL.
Click to expand...
Click to collapse
Is it better to just boot into recovery (TWRP) and go that route, instead of having Goo flash it?
I checked the page where the ROM exists but I'm not seeing a link to any specific kernel. However, I downloaded to ROM again to my desktop just now, unarchived it and now see a 'boot.img" file. So this file.....this gets placed on my sd card, I boot into TWRP and flash it?
If you can point me to a how-to on this, I'd appreciate it - I hate filling boards with asinine questions.
originalseven said:
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
Click to expand...
Click to collapse
viper doesn't require you to flash the boot image, it does it for your.
For cm10 or liquidsmooth you need to, an easy way is using Flash GUI. its available on the market and xda. you don't need to hook up to a computer to flash boot image, makes things much easier and faster.
originalseven said:
Is it better to just boot into recovery (TWRP) and go that route, instead of having Goo flash it?
Click to expand...
Click to collapse
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
originalseven said:
I checked the page where the ROM exists but I'm not seeing a link to any specific kernel. However, I downloaded to ROM again to my desktop just now, unarchived it and now see a 'boot.img" file.
Click to expand...
Click to collapse
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
originalseven said:
So this file.....this gets placed on my sd card, I boot into TWRP and flash it?
Click to expand...
Click to collapse
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
redpoint73 said:
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
Click to expand...
Click to collapse
Awesome - thank you so much. Cleared that up completely.
redpoint73 said:
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
Click to expand...
Click to collapse
Ok, so I looked at this Flash Image GUI on G-Play and the OneX isn't listed as a supported device - is it simply not listed, but is actually supported? For instance, I see this in the reviews...
"I own the AT&T model of the HTC One X (the Evita with a Snapdragon 4 processor) and unfortunately I got it on the 2.20 version. This means that I need to run the "fastboot flash boot boot.img" from my computer if I want to flash a Rom or kernel. It was a pain, I just wanted to be able to download a new Rom whenever and where ever I wanted (I have a very large data cap) and flash it on the go. I can actually do that now it's worked with both AOSP and Sense based Roms, so I'm happy. Great job to the dev "
Failing that, I'll run it from terminal (im on a mac) and assume those same commands apply (but with -mac after bootloader).
originalseven said:
Ok, so I looked at this Flash Image GUI on G-Play and the OneX isn't listed as a supported device - is it simply not listed, but is actually supported? For instance, I see this in the reviews...
"I own the AT&T model of the HTC One X (the Evita with a Snapdragon 4 processor) and unfortunately I got it on the 2.20 version. This means that I need to run the "fastboot flash boot boot.img" from my computer if I want to flash a Rom or kernel. It was a pain, I just wanted to be able to download a new Rom whenever and where ever I wanted (I have a very large data cap) and flash it on the go. I can actually do that now it's worked with both AOSP and Sense based Roms, so I'm happy. Great job to the dev "
Failing that, I'll run it from terminal (im on a mac) and assume those same commands apply (but with -mac after bootloader).
Click to expand...
Click to collapse
flashimagegui is perfectly supported. got support awhile back. [APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
I have downloaded CleanRom 5.1 from a long time ago, now the link is not up for that rom. The size is 598 mb.I have flashed this rom before but now I can't get it to flash. In recovery I have wiped, dalvic,cache, system, and factory. After I choose what to flash from Aroma it goes to flash a couple of seconds then goes to the other screen to finalize, but when going to reboot, I get "no OS , do you really want to reboot".
S-OFF
unlocked
on 2.20
Tried this with HBOOT 1.09 and now on HBOOT 1.14, I would redownload but the link is gone now , and I can't figure out how to get it to flash, luckily I do have a back up that works
Downgrade your recovery to twrp 2.3 bet you are using a 2.4 version
Sent from my HTC One X using Tapatalk 2
jerrycoffman45 said:
Downgrade your recovery to twrp 2.3 bet you are using a 2.4 version
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I had 2.4 downgraded to 2.3 but having troubles now. Seems Clean Rom 5.1 is the only one I have trouble with even on TWRP 2.3
Sorry maybe someone else will know what to do I am out of ideas
Sent from my HTC One X using Tapatalk 2
leesumm said:
I had 2.4 downgraded to 2.3 but having troubles now. Seems Clean Rom 5.1 is the only one I have trouble with even on TWRP 2.3
Click to expand...
Click to collapse
Don't know if you have the MD5: C8D3304C4120F5B0AEBE75BC6B4F733C But check that. If it doesnt match, lemme know and I think I have a copy of this rom to upload for you at home assuming Dev won't mind.
Also, after downgrading from twrp 2.4 to 2.3 did you do fastboot erase cache? Regardless I would recheck checksum twrp if you have the image saved or redownload and check checksum, reflash (fastboot flash recovery "recoveryname.img" (sans "") and then do fastboot erase cache.
Lemme know.
exad said:
Don't know if you have the MD5: C8D3304C4120F5B0AEBE75BC6B4F733C But check that. If it doesnt match, lemme know and I think I have a copy of this rom to upload for you at home assuming Dev won't mind.
Also, after downgrading from twrp 2.4 to 2.3 did you do fastboot erase cache? Regardless I would recheck checksum twrp if you have the image saved or redownload and check checksum, reflash (fastboot flash recovery "recoveryname.img" (sans "") and then do fastboot erase cache.
Lemme know.
Click to expand...
Click to collapse
NO. I don't have the md5 for that rom. I downloaded it some time ago and sitting idle in the folder on the PC. I was messing around in places that I shouldn't have been and somehow things got deleted. My backup of that rom I had flashed works fine. Its when I go to flash the rom from zip that I have a problem.
I am really scratching my head now!!!
The same rom, the same zip that I have been asking about that wouldn't flash, now flashes fine and installs. I was using TWRP 2.4.1 for a long time and was having a little problems with different things and trying to flash some add ons to the rom playing with it. Reading some of the posts I read some were having problems with TWRP above 2.3 so I downgraded the recovery,thats when I couldn't flash the zip I had of Clean Rom 5.1. So, for the fun of it, I upgraded back to TWRP 2.4.1 and tried to reflash the same zip package, everything works fine now it flashed and booted. Got me scratching my head ...
leesumm said:
The same rom, the same zip that I have been asking about that wouldn't flash, now flashes fine and installs. I was using TWRP 2.4.1 for a long time and was having a little problems with different things and trying to flash some add ons to the rom playing with it. Reading some of the posts I read some were having problems with TWRP above 2.3 so I downgraded the recovery,thats when I couldn't flash the zip I had of Clean Rom 5.1. So, for the fun of it, I upgraded back to TWRP 2.4.1 and tried to reflash the same zip package, everything works fine now it flashed and booted. Got me scratching my head ...
Click to expand...
Click to collapse
Makes sense to me, sounds like you didn't do fastboot erase cache after switching recoveries. When you flash a new recovery you need to do fastboot erase cache.