I tried booting various sense and aosp roms, but my phone won't boot past the flying 3d or any other boot animations. Can someone please help? I tried wiping everything. It worked at first but it doesn't now.
I think this belongs in the questions part of the thread.(Im sure a mod might move it) Other than that can you even do a Nandroid restore?
SilverSuperman said:
I think this belongs in the questions part of the thread.(Im sure a mod might move it) Other than that can you even do a Nandroid restore?
Click to expand...
Click to collapse
i tried that too. I think it has to do something with flashing a bad kernel
Ok in order for anyone to help you more could you please tell which hboot you have, also specify further about your problem. For example: does your phone just freeze at some point or does the bootscreen keep running and never gets past it or is it taking over the world or what?
---------- Post added at 12:08 AM ---------- Previous post was at 12:05 AM ----------
Im asking because there has been alot of views on this and ppl just pass it up because its in the wrong section. Dont take offense to this plz. Im sure u knew this due to you have been a member since Oct. 2009
SilverSuperman said:
Ok in order for anyone to help you more could you please tell which hboot you have, also specify further about your problem. For example: does your phone just freeze at some point or does the bootscreen keep running and never gets past it or is it taking over the world or what?
Click to expand...
Click to collapse
HB1.5
it keeps freezing at the flying 3d animatio.
I think you should re-post this in the questions and answers part of the thread and leave this one alone. Otherwise theres gonna be ppl that will "flame" you and say that we have a section for questions and answers. Technically of course it doesnt belong here anyways. Just re-post it over there too and for some reason ppl will be more willing to help you.
ok heres your fix
1-take the rom of your choice put in your sd card
2-then take boot.img out of your rom and recovery.img of your choice and place it in android-sdk/platform-tools
(rename recovery u have to recovery.img then place it in android-sdk/platform-tools)
3-if runing widows hold shift and right click then open with command prop
4-then reboot your phone into fastboot (make sure u have fastboot drivers installed)
5- then type this in command prop
fastboot flash boot boot.img
after its done type this
fastboot boot recovery.img
then it will take u into recovery then do all wipes and flash rom of your choice
and enjoy
hope this helps u
sac23 said:
ok heres your fix
1-take the rom of your choice put in your sd card
2-then take boot.img out of your rom and recovery.img of your choice and place it in android-sdk/platform-tools
(rename recovery u have to recovery.img then place it in android-sdk/platform-tools)
3-if runing widows hold shift and right click then open with command prop
4-then reboot your phone into fastboot (make sure u have fastboot drivers installed)
5- then type this in command prop
fastboot flash boot boot.img
after its done type this
fastboot boot recovery.img
then it will take u into recovery then do all wipes and flash rom of your choice
and enjoy
hope this helps u
Click to expand...
Click to collapse
You can take the boot.img piece out that is not needed. Once you power on phone holding power and volume down, choose fastboot, connect usb, and just do fastboot boot recovery.img this will give you full access and when you flash the rom, it will install kernel and all necessary files.
Sent from my PG86100 using XDA App
He provided the fix for the problem he's having right now. So his steps are correct. Now in the future he'd want to do the
Code:
fastboot boot recovery.img
To help with flashing in the future.
nolimit78 said:
He provided the fix for the problem he's having right now. So his steps are correct. Now in the future he'd want to do the
Code:
fastboot boot recovery.img
To help with flashing in the future.
Click to expand...
Click to collapse
I didn't think that was needed. What exactly does fastboot flash boot boot.img do?
Sent from my PG86100 using XDA App
There is a limitation with HTC's unlock, recovery does not have permission to write to the boot partition, this is where the kernel goes. What this means is that you can't flash a kernel through the normal recovery. Which also means that you can't flash a ROM that requires a custom kernel. There are two ways that I know of to work around this. One is to just flash the kernel(boot.img) from fastboot, the other, and easier way is to boot recovery from fastboot and just do everything from there.
Sent from my PG86100 using XDA App
is there a way around all of this besides fastboot? or anything i can do in recovery instead?
mariojp said:
is there a way around all of this besides fastboot? or anything i can do in recovery instead?
Click to expand...
Click to collapse
My 3D is not yet rooted, but you should be able to flash everything you need without a computer. You will need Flash Image GUI, which is found in the market, or can be downloaded via the XDA post. It's JoeyKrim's program.
Here's a stickied thread, over in the Android Dev forum
http://forum.xda-developers.com/showthread.php?t=1306248
Related
Where do I download it? I need it for the the ext4 roms which I've been just flashing through fastboot :/
Sent from my MB860 using XDA App
http://forum.xda-developers.com/showthread.php?t=1204500
Thx for the prompt reply!
Sent from my MB860 using XDA App
How exactly do i install this? If you guys dont mind me asking such a noobish question cause i can't seem to figure it out from the thread posted above =/ Step by step would be helpful?
TfzSCVang said:
How exactly do i install this? If you guys dont mind me asking such a noobish question cause i can't seem to figure it out from the thread posted above =/ Step by step would be helpful?
Click to expand...
Click to collapse
*face palm
How about the directions in his OP.
Sent from my MB860 using xda premium
Well, the thing is i dont know how to adb push, and thats what it seems like is happening, so what i did was i just put the zip file into my sd card and flashed it =/ but i dont know if that will work, since in the op, he had some commands to erase the previous recovery =/ which is why i was asking =]
---EDIT---
Well it seems to be working? I'll re-edit again should i encounter any problems? And yes, im a noob, please dont troll on it...
TfzSCVang said:
Well, the thing is i dont know how to adb push, and thats what it seems like is happening, so what i did was i just put the zip file into my sd card and flashed it =/ but i dont know if that will work, since in the op, he had some commands to erase the previous recovery =/ which is why i was asking =]
---EDIT---
Well it seems to be working? I'll re-edit again should i encounter any problems? And yes, im a noob, please dont troll on it...
Click to expand...
Click to collapse
You can flash roms through fastboot but you can't flash recovery through fastboot? What's the deal with that?
Sent from my MB860 using xda premium
Alcapone263 said:
You can flash roms through fastboot but you can't flash recovery through fastboot? What's the deal with that?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Yeah, I've been trying to find a good explanation for the difference between moto-fastboot and fastboot. What exactly is the difference between the two? Are all of the 'erase' commands just as effective between the two?
Can I just drag my fastboot.exe file into the same one my moto-fastboot and adb ones are, and use it interchangeably or will I need to copy other files as well?
Moto-fastboot and fastboot are basically the same, moto-fastboot allows for bigger file chunks(something like that)and is made for the motorola phones. Just use the same commands as you would for fastboot but use mot-fastboot instead.
Hope this helps.
bamastang said:
Moto-fastboot and fastboot are basically the same, moto-fastboot allows for bigger file chunks(something like that)and is made for the motorola phones. Just use the same commands as you would for fastboot but use mot-fastboot instead.
Hope this helps.
Click to expand...
Click to collapse
Thanks.
Out of the two I've only used moto-fastboot to install a deodexed system.img. I've done everything else through CWM. I've noticed the moto version seems to be required with certain type of flashes (i.e. recovery,system).
I had to reflash my first backup yesterday and ended up using moto-fastboot for all the erase commands. I just wanted to make sure I was using the correct program to get the cleanest recovery.
ghost_og said:
Thanks.
Out of the two I've only used moto-fastboot to install a deodexed system.img. I've done everything else through CWM. I've noticed the moto version seems to be required with certain type of flashes (i.e. recovery,system).
I had to reflash my first backup yesterday and ended up using moto-fastboot for all the erase commands. I just wanted to make sure I was using the correct program to get the cleanest recovery.
Click to expand...
Click to collapse
weird, i use normal fastboot and have yet to have a problem flashing any file; recovery and system images included.
Hi I tried to flash recovery with romracer's . I got these instructions:Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
But I can't even extract the zip file with the .img file to C because it says Error:internal error processing iso image.
I am a noobie. Could you guys give me a hand??
Thanks!
kncha said:
Hi I tried to flash recovery with romracer's . I got these instructions:Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
But I can't even extract the zip file with the .img file to C because it says Error:internal error processing iso image.
I am a noobie. Could you guys give me a hand??
Thanks!
Click to expand...
Click to collapse
This is what is did I downloaded automatic bootloader unlock from here http://forum.xda-developers.com/showthread.php?t=1182871, unzip it, you will find img file named recovery-en-goapk-0630-1029 replace it with romracer recovery you downloaded and rename the romracer recovery as recovery-en-goapk-0630-1029. Just to be safe even replace the recovery-clockwork-4.0.1.4-olympus with rom racer recovery and rename it as recovery-clockwork-4.0.1.4-olympus. Open main and select option 2 and follow the instructions.It worked for me
First of all thanks!
I did what you told me chose option #2 but when I got into the next #5 "now release vol down and press vol down until ...... it showed the exclamation sign with the lil android. Did I do something wrong?
kncha said:
First of all thanks!
I did what you told me chose option #2 but when I got into the next #5 "now release vol down and press vol down until ...... it showed the exclamation sign with the lil android. Did I do something wrong?
Click to expand...
Click to collapse
what was the error you got, just to be sure download the romracer recovery again it may be a bad download.You just have to switch off the phone switch off the phone holding volume down until you see fastboot then connect it to pc open main and select option 2. It will ask you to do the stuff i just said, press enter it will show device serial number and then again enter and it will write the recovery image and will ask for reboot, hold the volume down button until it shows fastboot disconnect the cable then keep pressing vol down till you get android recovery press vol up to select and that's it you get the recovery.
Edit: Are you rooted and have an unlocked bootloader.
Hey guys just want to ask if I can flash themes or mods for my Rom by just Reboot into recovery flash and reboot back again and done deal....
Or I have to go to my computer do the command process and then flash it
Thanx for the help
Sent from my PG86100 using XDA App
yankee minaj said:
Hey guys just want to ask if I can flash themes or mods for my Rom by just Reboot into recovery flash and reboot back again and done deal....
Or I have to go to my computer do the command process and then flash it
Thanx for the help
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
if you have hboot 1.5 then you have to flash thru cmd prompts
yankee minaj said:
Hey guys just want to ask if I can flash themes or mods for my Rom by just Reboot into recovery flash and reboot back again and done deal....
Or I have to go to my computer do the command process and then flash it
Thanx for the help
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
3vo kid said:
if you have hboot 1.5 then you have to flash thru cmd prompts
Click to expand...
Click to collapse
This is not 100% correct. If you use my application, Flash Image GUI, you're able to flash ROMs and kernels w/o ever using the command process.
Details are all below.
Although, as a word of cuation.
Using the command process to fastboot boot c:\recovery.img is the best way to fully nandroid backup and RESTORE the device.
This is important because many times there are bugs or issues in custom software users don't want bu don't know until they load it. If you want to easily be able to revert, always use proper backups.
If you have hboot 1.5, the main limitation is not being able to flash the kernel through standard recovery mode.
HTC unlocks write access to the kernel in two other modes: normal android mode and fastboot mode.
I've answered this question many times on this Q&A forum, so I'm pasting an excerpt from a previous answer. Please post back if you have questions or something isn't clear!
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes: normal Andriod mode and fastboot.
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any ROM.zip or kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
After loading the ROM .zip, Flash Image GUI will flash only the kernel and modules. Reboot into the custom recovery to flash there rest of the ROM.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery. This mode requires a computer.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues caused with Hboot 1.5 on the EVO 3D on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
Click to expand...
Click to collapse
joeykrim said:
This is not 100% correct. If you use my application, Flash Image GUI, you're able to flash ROMs and kernels w/o ever using the command process.
Details are all below.
Although, as a word of cuation.
Using the command process to fastboot boot c:\recovery.img is the best way to fully nandroid backup and RESTORE the device.
This is important because many times there are bugs or issues in custom software users don't want bu don't know until they load it. If you want to easily be able to revert, always use proper backups.
If you have hboot 1.5, the main limitation is not being able to flash the kernel through standard recovery mode.
HTC unlocks write access to the kernel in two other modes: normal android mode and fastboot mode.
I've answered this question many times on this Q&A forum, so I'm pasting an excerpt from a previous answer. Please post back if you have questions or something isn't clear!
Click to expand...
Click to collapse
You know I also heard that if your Rom has no custom kernel you can flash it in a regular recovery with out computer is that correct?
And with the explanation and all that being said....Im good to go and flash themes and Rok with your app?
Sorry if I'm askin too much you know just making sure thanks
Sent from my PG86100 using XDA App
yankee minaj said:
You know I also heard that if your Rom has no custom kernel you can flash it in a regular recovery with out computer is that correct?
And with the explanation and all that being said....Im good to go and flash themes and Rok with your app?
Sorry if I'm askin too much you know just making sure thanks
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
The only time issues occur is when the .zip file contains a kernel. The HTC unlock method blocks all writing to the kernel partition from recovery mode. This is where my app, Flash Image GUI, helps out as it allows the kernel and modules to be properly loaded so the rest of the .zip file can be loaded from the recovery!
If the .zip file does not contain a kernel, you can flash directly from recovery w/o any issues.
Hope that helps clarify!
Hello! Sorry for posting this here, Idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, I have searched the forums before to see If someone had found a solution while I was having the error!
Sorry for this, but I posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 So moderators will you please delete the above post! Thanks so much!
This has happened to me so many times, I got frustrated, then I tried this out of the blue and it seemed to work..
Some examples of ROMS that froze on boot on my HTC EVO 3D HBOOT 1.5
All Infected ROMS
MIUI
Synergy
Senseless ROM
CleanRom
and some others..
These are the steps I took to fix the issue!
1. Flash ROM and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (Power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into PC or MAC
4. Make sure you have the latest android SDK, im pretty sure you do if you have been flashing roms!
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands
PC:
Code:
fastboot flash boot boot.img
Ive done it on the PC and most of the time I have issues.. like failing of transferring over of the boot.img.. So far I don't know a way around this besides to keep trying!!
MAC:
Code:
./fastboot flash boot boot.img
Ive done it on my mac as well, and so far I have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~Bairdog35
Bairdog35 said:
Hello! Sorry for posting this here, Idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, I have searched the forums before to see If someone had found a solution while I was having the error!
Sorry for this, but I posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 So moderators will you please delete the above post! Thanks so much!
This has happened to me so many times, I got frustrated, then I tried this out of the blue and it seemed to work..
Some examples of ROMS that froze on boot on my HTC EVO 3D HBOOT 1.5
All Infected ROMS
MIUI
Synergy
Senseless ROM
CleanRom
and some others..
These are the steps I took to fix the issue!
1. Flash ROM and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (Power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into PC or MAC
4. Make sure you have the latest android SDK, im pretty sure you do if you have been flashing roms!
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands
PC:
Code:
fastboot flash boot boot.img
Ive done it on the PC and most of the time I have issues.. like failing of transferring over of the boot.img.. So far I don't know a way around this besides to keep trying!!
MAC:
Code:
./fastboot flash boot boot.img
Ive done it on my mac as well, and so far I have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~Bairdog35
Click to expand...
Click to collapse
Your problem lies in your HBOOT 1.5.... you need to flash the kernel separately, either the way you described it, or I think theres an app called FlashGUI
or just access recovery from fastboot & flash like normal.
This should be moved
Lulz. 10 char.
Sent from my PG86100 using xda premium
SketchyStunts said:
or just access recovery from fastboot & flash like normal.
This should be moved
Click to expand...
Click to collapse
This.
Maybe OP doesn't know about it so I'll guide him.
OP, we appreciate you trying to help but if you follow the steps below you should have no problem.
1. Download the Rom you want and place it on your sd card.
2. Plug your phone in to your computer and open a cmd file where 'adb' is located and type "adb reboot bootloader".
3. Your phone will now restart and boot into bootloader. Now type in "fastboot boot recovery.img". Your phone will now boot into your recovery.
(At this point, you can unplug your phone.)
4. Use the recovery as how you normally would and wipe/flash, etc.
Enjoy.
arozer said:
This.
Maybe OP doesn't know about it so I'll guide him.
OP, we appreciate you trying to help but if you follow the steps below you should have no problem.
1. Download the Rom you want and place it on your sd card.
2. Plug your phone in to your computer and open a cmd file where 'adb' is located and type "adb reboot bootloader".
3. Your phone will now restart and boot into bootloader. Now type in "fastboot boot recovery.img". Your phone will now boot into your recovery.
(At this point, you can unplug your phone.)
4. Use the recovery as how you normally would and wipe/flash, etc.
Enjoy.
Click to expand...
Click to collapse
Yes I do this, and I still have to do what I provided up above. Idk what is wrong with my phone.
Your recovery can't flash kernels. Hence the boot loop.
There is a program in the evo3d theme and apps forum for us 1.5 boot loader users to flash the kernel using an app in android then you reboot to recovery and flash rom.
The app is called flash image GUI
http://forum.xda-developers.com/showthread.php?t=1192527
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Sent from my PG86100 using xda premium
shadowmike said:
Your recovery can't flash kernels. Hence the boot loop.
There is a program in the evo3d theme and apps forum for us 1.5 boot loader users to flash the kernel using an app in android then you reboot to recovery and flash rom.
The app is called flash image GUI
http://forum.xda-developers.com/showthread.php?t=1192527
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
If you use that app and flash the boot.img from the rom and then go into recovery and flash the rom it should work
Sent from my HTC Evo 3D using XDA App
bairdog35 said:
hello! Sorry for posting this here, idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, i have searched the forums before to see if someone had found a solution while i was having the error!
Sorry for this, but i posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 so moderators will you please delete the above post! Thanks so much!
this has happened to me so many times, i got frustrated, then i tried this out of the blue and it seemed to work..
Some examples of roms that froze on boot on my htc evo 3d hboot 1.5
all infected roms
miui
synergy
senseless rom
cleanrom
and some others..
these are the steps i took to fix the issue!
1. Flash rom and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into pc or mac
4. Make sure you have the latest android sdk, im pretty sure you do if you have been flashing roms!
5. Extract the .zip file of the rom that you are using that freezes.
6. Open the folder and copy the boot.img from that rom
7. Paste that .img into the folder that has your adb and fastboot files for the android sdk!
8. In terminal navigate to that folder, and do the following commands
pc:
Code:
fastboot flash boot boot.img
ive done it on the pc and most of the time i have issues.. Like failing of transferring over of the boot.img.. So far i don't know a way around this besides to keep trying!!
mac:
Code:
./fastboot flash boot boot.img
ive done it on my mac as well, and so far i have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~bairdog35
Click to expand...
Click to collapse
this worked for me it was hanging at the htc white logo screen did this steps and the phone passed the first boot logo and it turned on fine!!!
That's due to not flashin a kernel right or you skipped a part of the wipe.
Virus has this guide for flashing the kernel on his page
The problem with using this "Flash Image GUI" is the FACT that if an individual can't boot a ROM, they obviously can't run the apk.
Individuals with HBOOT 1.5 have two choices in this situation (bootloop)...
Either
1. "adb reboot bootloader" after which you run "fastboot boot recovery.img" (recovery.img must be placed in fastboot directory), then you flash the ROM/kernel in question...
Or
2. Flash boot.img through fastboot (which is what the above "should" do in the fist place).
BTW: If you always have a problem with bootloops, you aren't loading recovery the way you should...
You can either run the commands mentioned earlier in this post, or go to
forum.xda-developers.com/showthread.pho?t=1403148
and download the batch in the second post "jthein1989_batch.zip" (you will still need to download and copy the recovery.img to the folder).
Just download twrp or clockwork and copy it as "recovery.img" to the directory that you unzipped the batch to... Then, just follow the OP of my thread...
Sent from my PG86100 using XDA App
Maybe I'm a noob,
But you mean you can't select Recorery from Hboot menu? Even if you installed twrp? I don't know much of what I'm doing only had 3d for week. but its locks up at white HTC screen all the time.
Or you could try...
Fastboot boot my kernel or ill kill you.img
Sent from my HTC EVO 3D using xda premium
jcfunk said:
Maybe I'm a noob,
But you mean you can't select Recorery from Hboot menu? Even if you installed twrp? I don't know much of what I'm doing only had 3d for week. but its locks up at white HTC screen all the time.
Click to expand...
Click to collapse
With HBOOT 1.5 you "can" start recovery without ABD, but "S-ON" will not allow you to properly flash to the BOOT partition (limitation of the HTC unlock method). Therefore, users with HBOOT 1.5 need to go to extra lengths to flash the BOOT partition.
Sent from my PG86100 using XDA App
Having HBOOT 1.5, I've ran into this very problem. I'm not sure if it's hardware or what, but my phone will not run any Sense 3.5 ROM's I've tried. The phone just won't boot! I gave up trying 3.5 ROM's. I used ABD to put a 3.0 kernel back on and restore the recovery and everything is fine again. This will probably be my last HTC phone. Hoping something better besides the S2 is coming soon.
Hi everybody.
I have been folowing the development of cm9 by Jokersax for quite some time now. Right now I am using the CM7 RC but I would like to get back to cm9 soon. Since the last update he has been adding a system.img file to flash using fastboot.
My question now is:
Do I only have to flash the system.img and that's it?
fastboot wipe everything and then flash the system.img?
What about a boot.img?
Do I have to flash that too?
I know I could use cwm instead but I would like to understand the fastboot method also...
samiam21 said:
I know I could use cwm instead but I would like to understand the fastboot method also...
Click to expand...
Click to collapse
Start here >
http://wiki.cyanogenmod.com/wiki/Fastboot
and here >
http://android-dls.com/wiki/index.php?title=Fastboot
Ok. If I only flash the system.img, I will get the cm9 rom running? I don't see anything about boot.img ...
Sent from my MB860 using Tapatalk
samiam21 said:
Ok. If I only flash the system.img, I will get the cm9 rom running? I don't see anything about boot.img ...
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
I think boot.img is about the kernel?
ri123 said:
I think boot.img is about the kernel?
Click to expand...
Click to collapse
Sure it is
http://wiki.cyanogenmod.com/wiki/Fastboot#Typical_Partition_Layout
scandiun said:
Sure it is
http://wiki.cyanogenmod.com/wiki/Fastboot#Typical_Partition_Layout
Click to expand...
Click to collapse
What about fastboot flash zip rom.zip??? Does this need a meta-inf folder?
guys i need to flash a rom cuz i cant use my phone at all.
hi,
i cant enter recovery mode, phone just reboots automatically and when it does it just stays at "why so serious" screen, i get: bootloader err command error !!!, i cant flash a rom with fastboot (i have debugging activated).
i can do nothing with my phone now.
its a htc desire btw.
i need help please.
Thanks!
Lawrence7 said:
its a htc desire btw.
i need help please.
Thanks!
Click to expand...
Click to collapse
This is the Atrix 4G forum................you are in the wrong place!
I'd hate to revive a dead thread here but.. anyone who understands fastboot willing to give me a hand with something?
My Atrix is stuck in boot loop because my battery died during a flash in TWRP. I tried going back into TWRP to recover back to my nandroid backup but TWRP just stays at the splash screen.. I've tried to ash a rom via fastboot update and no dice so far.. any assistance is very much appreciated
EDIT: Found this thread here: http://forum.xda-developers.com/showthread.php?t=1421522 should probably work so mods feel free to delete this post. If I encounter an issue I'll post there/
MewRai95 said:
I'd hate to revive a dead thread here but.. anyone who understands fastboot willing to give me a hand with something?
My Atrix is stuck in boot loop because my battery died during a flash in TWRP. I tried going back into TWRP to recover back to my nandroid backup but TWRP just stays at the splash screen.. I've tried to ash a rom via fastboot update and no dice so far.. any assistance is very much appreciated
EDIT: Found this thread here: http://forum.xda-developers.com/showthread.php?t=1421522 should probably work so mods feel free to delete this post. If I encounter an issue I'll post there/
Click to expand...
Click to collapse
You can try entering recovery mode ( before the splash screen appears ) and wipe cache , wipe dalvik and wipe data, then reboot.
I'm pretty inexperienced with rooting.. I think I may have messed my brother's phone up. I rooted his rezound and got cwm recovery working. I tried to flash a "TACHYON-1.2.zip" rom I found here and now it won't boot past the white background with green htc screen when I try to boot the phone. Please help me try to fix this! I can still boot into cwm recovery.
[EDIT] When I wipe data/factory rest it says error mounting /sdcard/.android_secure!
This was probably a mistake but I'm freaking out. I put CleanROM Standard 4.5.zip from here https://www.copy.com/s/uYOSaNCntCvx/CleanROM on another sd card and installed it after tying to wipe again. Now it boots past the htc screen and the CleanROM screen boots for a minute, then sticks..
Cap'n Jazz said:
I'm pretty inexperienced with rooting.. I think I may have messed my brother's phone up. I rooted his rezound and got cwm recovery working. I tried to flash a "TACHYON-1.2.zip" rom I found here and now it won't boot past the white background with green htc screen when I try to boot the phone. Please help me try to fix this! I can still boot into cwm recovery.
[EDIT] When I wipe data/factory rest it says error mounting /sdcard/.android_secure!
This was probably a mistake but I'm freaking out. I put CleanROM Standard 4.5.zip from here https://www.copy.com/s/uYOSaNCntCvx/CleanROM on another sd card and installed it after tying to wipe again. Now it boots past the htc screen and the CleanROM screen boots for a minute, then sticks..
Click to expand...
Click to collapse
You need to extract and flash the boot.img file from the ROM zip separately via fastboot. Extract the file and place it in an easy to access place on the drive (like same place as fastboot/adb) , then after flashing the ROM reboot into hboot and start fastboot, and use:
fastboot flash boot boot.img
Then reboot and be patient, sometimes the first boot seems to take forever.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
You need to extract and flash the boot.img file from the ROM zip separately via fastboot. Extract the file and place it in an easy to access place on the drive (like same place as fastboot/adb) , then after flashing the ROM reboot into hboot and start fastboot, and use:
fastboot flash boot boot.img
Then reboot and be patient, sometimes the first boot seems to take forever.
Click to expand...
Click to collapse
Thank you for the reply, and sorry if I ask too many questions, but how exactly do I flash the boot.img file? In CMD? There isn't a flash option in my fastboot section of the phone, just BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN.
http://img854.imageshack.us/img854/6248/ismh.png
This is how far I got in cmd if I'm headed in the right direction at all..
Cap'n Jazz said:
Thank you for the reply, and sorry if I ask too many questions, but how exactly do I flash the boot.img file? In CMD? There isn't a flash option in my fastboot section of the phone, just BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN.
This is how far I got in cmd if I'm headed in the right direction at all..
Click to expand...
Click to collapse
You start fastboot in the phone, that puts it in a mode to enter fastboot commands from a PC... You Don't do anything in the phone in fastboot, you use the fastboot command that is part of the ADB package. The same way you would have unlocked the phone on HTCdev.com to allow root or CWM to be installed.
Sent from my Nexus 4 using Tapatalk
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom.
mjones73 said:
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom.
Click to expand...
Click to collapse
Thank both of you so much! I'm sorry I had to have you completely spell it out for me, but I appreciate the help and this forum in general so much!
I hate to bring this thread back, but it's the best place to ask about my problem. I'm trying to switch from Clean Rom on an HTC Rezound to Venasaur Rom v3.2.0 because I read that it will work with a Straight Talk sim. I tried installing with ClockWork and I get the new rom's boot screen, but it won't boot past that. I don't know what I'm doing wrong. I would really appreciate it if somebody could help me out again!
Did you flash the boot.img this time? I would suggest after you get booted, trying rumrunner to go S-off... It saves sooo much time... I'm always switching between multiple ROMs because I'm s-off....
Sent from my HTC EVO 4G Running AOKP 4.2.2
Cap'n Jazz said:
I hate to bring this thread back, but it's the best place to ask about my problem. I'm trying to switch from Clean Rom on an HTC Rezound to Venasaur Rom v3.2.0 because I read that it will work with a Straight Talk sim. I tried installing with ClockWork and I get the new rom's boot screen, but it won't boot past that. I don't know what I'm doing wrong. I would really appreciate it if somebody could help me out again!
Click to expand...
Click to collapse
... you should remember one thing for sure. Because you are s-on whenever you flash any custom rom, you have to flash its corresponding boot.img file in fastboot separately otherwise you are gonna get bootloop ...
---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----------
... and yeah. you should try to get s-off as you are already been suggested above ...