Related
I have a fastboot oem unlock'ed Nexus S I9020T. I am interested in the methods I can use to restore stock GRI40 (e.g. android.clients.google.com/packages/ota/google_crespo/f182cf141e6a.signed-soju-ota-102588.f182cf14.zip). I am running stock recovery although I have a copy of
Clockwork Recovery 3.0.2.4 on hand. I don't care about any data on the device -- in fact, I would probably prefer to nuke it all.
One way I have successfully done this already (thanks to instructions on the forum) is to copy the soju ROM to the /sdcard root, boot into recovery and 'apply update from /sdcard'.
Are there other ways I could do this? I can imagine there is using fastboot flash or fastboot flashall might work... and there are probably more that I'm too n00b to imagine.
Thanks!
PS: as a forum newcomer, I'm posting this dev-centric question in this forum per the instructions in this thread. Please let me know if this is the wrong place.
PPS: Managed to post with a crap title, and can't edit that. Sorry!
"fastboot flash" is not for ROMs.. its using for flashing radios/bootloader etc.
Recovery is what you need to flash ROMs.
Updating radios and bootloaders can also be in done in recovery but in a flashable .zip format.
Fastboot flash is for .img(s)
Just use Recovery.. I don't know why you would want to flash it with something else. Alternatively, you can use Odin but I wouldn't recommend it since there isn't any need to. It's a last resort.
Thanks! As a followup, does does flashing a ROM from recovery also flash the radio, boot image, bootloader, recovery (so, for example, will flashing stock GRI40 overwrite clockwork recovery if installed)?
Inside the GRI40 zip, I see boot.img, bootloader.img, and radio.img, so I'm guessing yes, at least partially. Does bootloader.img include a stock recovery?
Thanks again.
A few questions as this is all new to me.
Do all ROMS require you to flash a new kernal?
Do you flash a kernal the same way as you flash a radio? (PD98IMG File and Hboot?)
I appreciate the input...
ROMS should and typically will come with the recommended kernel, however, some kernels do work that aren't the packaged one. Always be careful when flashing a new one (backup, backup, backup!) because sometime they don't always get along with the ROM you have running.
Also, most of them should be flashable .zips that can be ran through CWM.
At least in my experience with various kernels
Hope this helped!
Kernels are included with every rom I have ever tried, and if you want to use a different kernel than the one in the rom, you have to make sure that is compatible. A good rule of thumb is if it a sense based rom (custom user interface that comes stock on the inspire) you have to use a sense based kernel. If it is a ASOP rom (Android Open Source Project, like Cyanogenmod 7, or MUIU) you must use a ASOP kernel. They will specify in the OP. And I have never heard of flashing them through HBOOT, or FASTBOOT. In my experience it is always through CWM recovery, and you flash them just as you would a rom, theme, or anything else. Move the .zip file to the root of your SD, choose install zip from sd card, scroll down to choose zip from sdcard, then choose the file. When it is done hit back and then reboot. Easy Peezy.
Tmullins23 said:
A few questions as this is all new to me.
Do all ROMS require you to flash a new kernal?
Do you flash a kernal the same way as you flash a radio? (PD98IMG File and Hboot?)
I appreciate the input...
Click to expand...
Click to collapse
Read.
Reread.
Search.
Research.
Try.
Retry.
Then ask.
kernal == kernel
Most users will flash kernels through clockwork like a rom. I flash them through fastboot, you can fastboot flash zimage(or boot), or fastboot boot zimage , which lets you boot the kernel before actually writing it, fastboot flashing requires eng s-off, which you probably don't have or need
I am finding that the 10.56 radio would be best for my carrier and would like to switch to it. What is the safest way to get there? Would that be to flash a RUU, updating the ROM as well? I would like to get rid of the InsertCoin ROM and try a different one anyway as I am having another issue with it. I want to keep clockwork, the factory unlocked state and root. This phone was an Asian factory unlocked phone supplied to me by a seller with InsertCoin already on it. I want an English RUU with a stable well tested ROM and preferably with Sense 3.5 although that is not an absolute requirement. Any recommendations?
Any suggestions?
Although I don't know much of the sensation's build, my experience with android in general tells me that the safest way to flash a radio is through fastboot.... But you could do it through flashable zips too... Just check the md5 some dozens of times...
Sent from my HTC Sensation XE with Beats Audio using XDA App
dexter93 said:
Although I don't know much of the sensation's build, my experience with android in general tells me that the safest way to flash a radio is through fastboot.... But you could do it through flashable zips too... Just check the md5 some dozens of times...
Click to expand...
Click to collapse
Any suggestions from someone with experience on the Sensation?
Thanks
Bump, please?
Download the radio zip and DO NOT extract it then put it in the root of your sdcard which the same place of where the rom zips go. Then boot into boot loader by holding the down volume button and power button till it boots and then select update by upper volume button.
After the rom boots fully delete the radio.zip and then boot into recovery again then flash the ril.zip in recovery and that's it
blahbl4hblah said:
Download the radio zip and DO NOT extract it then put it in the root of your sdcard which the same place of where the rom zips go. Then boot into boot loader by holding the down volume button and power button till it boots and then select update by upper volume button.
After the rom boots fully delete the radio.zip and then boot into recovery again then flash the ril.zip in recovery and that's it
Click to expand...
Click to collapse
I see on the Radios thread at http://forum.xda-developers.com/showthread.php?t=1178143 a different installation procedure using ADB. Which method should I use?
tk_xda said:
I see on the Radios thread at http://forum.xda-developers.com/showthread.php?t=1178143 a different installation procedure using ADB. Which method should I use?
Click to expand...
Click to collapse
Depends on you as I've used this method and never fails
if you have s-off and unlock bootloader then you should be able to do fastboot commands(adb way) and i always do fastboot way
best thing to do is get adb setup on your computer
once thats done download your radio
and put your phone in fastboot(go into bootloader)
fastboot flash radio (drag radio.img in cmd window)
hit enter and it will give you message sending and writing .
from there you can download 3.5 rom( suggestion Leedroids) put on sdcard go back into recovery and do a nandroid, then do superwipe then flash rom
make sure you get the large MMSfix zip too after you flash leedroid rom flash the MMSfix then reboot let rom boot, then go back to recovery and match ril, every rom has a different RIL
after reboot into recovery
mount the system in recovery flash the RIL then unmount system and reboot
and you should be on new english rom with match radio
Hello everyone,
Excuse my noviceness here but I have a few questions. Im NOT new to flashing roms on Android but NEW to flashing roms on HTC Devices. I came fresh off a Galaxy S2 where things were more simple.
I have a STOCK Rooted HTC ONE S (TMO USA VERSION) and want to install TrickDroid. In the install instructions it asks to install Stock HTC kernel for Android 4.0.4 (BOOT FLASH SCRIPT).
Do I have to do this since I am running the stock rom (never changed or touched kernel) with TWRP recovery? Can I skip this step? See below the section in BOLD UNDERLINED... Must I follow these steps at this point or skip them?
Instructions:
Download ROM
Download tweak package
Copy ROM and tweak package to your sdcard
Fullwipe (data and cache)
Flash the ROM
Reboot into bootloader
Go into fastboot mode
Flash the stock boot.img from the ROM with fastboot, TWRP does not help!! (You can also use the Boot_Flash_Script I deliver you which runs every command for you)
Fastboot erase cache if you do not use the Boot_Flash_Script
Let the ROM boot
Flash the tweak package
Enjoy
And for those who are wondering if i did read through the threads and tips... I have, I spent several hours looking for an answer before i had to resort to asking!
Thanks to whoever can answer and educate me as to why I must or must not have to flash the boot image.
you can try without them first and if it doesn't work, rewipe and flash the boot.img from the trickdroid rom (just extract the .zip file on your computer and there it will be)
Can I push it with root explorer or with TWRP once i get the boot.img?
jgentry151 said:
And for those who are wondering if i did read through the threads and tips... I have, I spent several hours looking for an answer before i had to resort to asking!
Thanks to whoever can answer and educate me as to why I must or must not have to flash the boot image.
Click to expand...
Click to collapse
It's just the way HTCDev unlock the bootloader, it doesn't allow for certain partition to be flash. Boot is one of them so you'll need to flash the boot.img separately.
TWRP work for some but not others to flash the boot.img.
Just like HidaKureku said, just flash using TWRP if it boot up fine. If it doesn't just bootback into fastboot and flash boot.img
Thanks for the valuable info.... I risked it and was rewarded. i was able to install the rom and the tweaks without touching the boot.img...
Now for future refrence...
How can I Flash the stock boot.img from the ROM with fastboot? Do i just pull the boot.img and go into bootloader and do it from there?
Funny thing is that on my phone not only I can flash the boot.img with TWRP, I noticed that I don't even have to flash it at all! When I installed the ROM using TWRP it automatically installed the boot.img.
jgentry151 said:
Thanks for the valuable info.... I risked it and was rewarded. i was able to install the rom and the tweaks without touching the boot.img...
Now for future refrence...
How can I Flash the stock boot.img from the ROM with fastboot? Do i just pull the boot.img and go into bootloader and do it from there?
Click to expand...
Click to collapse
Just copy the boot.img to your fastboot.exe folder
CD to that folder in Command Window
Type: fastboot flash boot boot.img
I don't remember if "fastboot erase cache" is recommended after you flash the boot.img
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!