I was so excited to flash viper on lte, i didnt install the kernel and cant get the phone to completely booy. Recovery and bootloader work fine. How can i flash the correct boot img or can I flash a stock rooted rom?
Should just be a fastboot flash boot boot.img
Sent from my EVO using Tapatalk 2
What do you mean? Viper comes with the kernel - if you're rooted and have recovery installed, you just flash the rom, and that's it.
@ Rx, what is your donation address. It worked and im going to try flashing the rom
This just happened to me over the weekend with CM10, so this is fresh in my mind. Completely power off the handset. Then, Power and Volume-Down to get into the bootloader. Connect the phone to your workstation via USB, and you will see a fastboot USB option. Then, download the ADB and Wintools ZIPs that are available here on XDA (PM me if you cannot find them via search, and I will send them directly to you).
After that, you will be able to execute the following commands to push the boot.IMG to your handset, etc.
http://wiki.cyanogenmod.com/wiki/Fastboot
Manual Nandroid restore
Make a Nandroid backup, and copy the folder off your SD card to your desktop.
cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Flash Custom Recovery.img
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
Flash Custom boot.img
You should make a Nandroid backup first, in case you need to recover your boot.img
fastboot flash boot /path/to/<boot>.img
fastboot reboot
Alternatively, if you have CWM or TWRP installed as recovery options, you can flash from there. Just make sure you are pushing the correct boot.img for the ROM you want to flash.
HTH!
~ Mike
KaoMinerva said:
@ Rx, what is your donation address. It worked and im going to try flashing the rom
Click to expand...
Click to collapse
I pmd ya
Sent from my EVO using Tapatalk 2
Related
I installed that flash image gui app, tried a new kernel, I dont like it and tried to reset my backup from the cwm recovery I use to have, but the recovery wasnt there anymore and I had to flash the twrp recovery, which i dislike, and still cant figure out how to get my cwm backup of this rom back.
Check to see if the backup files are in the CWM folder if not then not to be a Debbie Downer but you're SOL. If they are boot into system and flash the recovery using Rom Manager then restore the backup like you normally would
I've tried that... I have twrp recovery, I've tried that and when booting into recovery it just shows the white HTC screen then reboots. I do have the backup in the cwm folder but can't flash it.
Nickdroid86 said:
I installed that flash image gui app, tried a new kernel, I dont like it and tried to reset my backup from the cwm recovery I use to have, but the recovery wasnt there anymore and I had to flash the twrp recovery, which i dislike, and still cant figure out how to get my cwm backup of this rom back.
Click to expand...
Click to collapse
just reflash cwm recovery via fastboot.
How do I do that? I tried flashing it from twrp recovery but it doesn't see the file. It is in the root of my SD. It's cwm 5.0 shooter
cwm backups dont work with twrp backups and vice versa.
Load your phone into the bootloader( power button and volume down).
Then connect to computer via usb, and press power button again to enter fastboot and it should say fastboot usb.
Then in terminal/command prompt execute this command where "recovery.img" is the file name of your cwm recovery.
Code:
fastboot flash recovery recovery.img
then when thats done execute this
Code:
fastboot boot recovery.img
Do i need to rename the cwm file, or use any program on the computer? I can get into the bootloader from my phone if there's an easier way, I don't quite understand that way. Also I have hboot 1.50 if it matters
it doesn't matter the name of the recovery but u just have to use that name instead of recovery.img when u type the command. since you have 1.50 your gonna have to use flashboot to flash anything when you arent able to boot into android.
I assume u have downloaded fastboot, adb, and the google usb drivers, since u have already rooted.
You will use your command prompt on your computer to boot phone into the recovery. See in 1.50 u can't just boot up the phone, goto recovery and flash things. You have to boot into boot loader, press power button when selector is on fastboot (normally default position aka first one in the list), then connect phone via usb to computer. The Red word fastboot should now say fastboot usb.
then execute the commands. "recovery.img" replace with your cwm file name
Code:
fastboot flash recovery recovery.img
Code:
fastboot boot recovery.img
alright I think I figured it out, thanks a lot man!
and don't worry your not the only this happened to. I had this happen to me this weekend. I just got the phone 5 days ago and killed it. So i had a great weekend playing catch up to learn how to reflash on 1.50 HBOOT.
---------- Post added at 11:46 AM ---------- Previous post was at 11:42 AM ----------
also if you still get white screen after you restore with cwm, its means the stock kernel didnt carry over. just reply if that happens.
once you loose its gone why dont you try 4ext custom recovery and gui doe's cause problem's ive used it and it wiped out my boot.img right now im useing 4ext as my custom recovery and it does'nt give any problems at all give it a try
jslim38 said:
once you loose its gone why dont you try 4ext custom recovery and gui doe's cause problem's ive used it and it wiped out my boot.img right now im useing 4ext as my custom recovery and it does'nt give any problems at all give it a try
Click to expand...
Click to collapse
NO bro, the apps works very well. It gets the Job done perfectly.
Suppose you were on a certain ROM and tried flashing a custom kernel with Flash Image GUI, and stuck in bootloop/htc screen , it doesnt mean that the Flash Image GUI caused that.
Even if you tried flashing the same kernel via fastboot boot recovery.img above the same ROM.......the result will be same i.e bootloop/htc screen.
Was running cm10 did a a wipe and restored to previious rom, and it won't boot.. Just boot loops.. Anyway to get my phone working again> I can access recovery still
most likely an s-on issue, you need to flash the kernel separately in fastboot. it has to match your backup's rom base
om4 said:
most likely an s-on issue, you need to flash the kernel separately in fastboot. it has to match your backup's rom base
Click to expand...
Click to collapse
Can you go in detail for me please
You need the boot image from the Rom you made a back up of, it has to match the base at the time of the backup 1.22, 2.13 or what have you and it needs to be flashed in fastboot. To do so you need the mini SDK (adb tools) or the full sdk. Place the boot.img (kernel) into the directory and open a terminal. Navigate to the directory or open it directly in the folder (windows) by holding shift and right click and slecting open command window here. You then boot to bootloader and connect the phone in fastboot. Type devices to make sure its connected and then fastboot flash boot boot.img and reboot
Easiest way is download flashgui and then download meanrom and open up meanrom via flashgui on phone and flash the stock kernel then boot into recovery and then flash your.restore and wala!!! That's what I had to do being s on
Sent from my EVO using xda app-developers app
I used to have one but I lost it and I don't know if you have tried but its really hard to find one.
what are you looking to do
most people refer to the RUU. but PH98IMG.zip can be alot of different things
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
if your not looking to get back to stock than don't flash the zip from the link above
bunchies said:
what are you looking to do
most people refer to the RUU. but PH98IMG.zip can be alot of different things
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
if your not looking to get back to stock than don't flash the zip from the link above
Click to expand...
Click to collapse
Well basically I need the txt file in the boot img. my phone is s-on and I always have to flash the ph
are you sure your not getting that confused?
if flashing a rom.
1.Flash ROM zip in recovery
2.Take the boot.img out of the ROM zip you just flashed
3.Reboot to Fastboot and flash the boot.img through ADB with the command: Fastboot flash boot boot.img
i don't see why anyone would need to flash the boot.img from an RUU. and if you did flash a boot.img from an RUU after you installed a ROM than i dont think the ROM would work at all
just clearing that up if you don't know or new to ROMing :good:
Or just "fastboot boot recovery.zip" and flash normally, if you are S-ON and BOOT recovery via fastboot, you can flash the ROM normally and not have to manually flash the boot.img in Fastboot like you do if you flash the ROM from an installed recovery.
bunchies said:
are you sure your not getting that confused?
if flashing a rom.
1.Flash ROM zip in recovery
2.Take the boot.img out of the ROM zip you just flashed
3.Reboot to Fastboot and flash the boot.img through ADB with the command: Fastboot flash boot boot.img
i don't see why anyone would need to flash the boot.img from an RUU. and if you did flash a boot.img from an RUU after you installed a ROM than i dont think the ROM would work at all
just clearing that up if you don't know or new to ROMing :good:
Click to expand...
Click to collapse
As a mac user I tried this. With adb all set up on the mac to use terminal (the whole folder and everything was set up long ago when unlocking). I have to use the command ./fastboot instead of just fastboot with terminal. Anyway, when ./fastboot flash boot boot.img it never works. It seems like it works, but then the phone just goes into the white HTC screen and is stuck there. It never boots.
I tried to manually update my HTC One's clockwork mod recovery using the command prompt. I downloaded the new .img file directly from the clockwork mod website. I made sure that I erased cache first. I then flashed the recovery I downloaded. The command prompt did not send the recovery and it failed to find the recovery. I could not get it to flash the new version of clockwork mod. I am trying to install android 4.4 and I need the new version of clockwork. I am going to give this phone to my father and I want him to have vanilla Android on it.
I am moderate Android modder. I have rooted several phones. I cannot get this to work the way I usually do. I am missing some step. Should I or could I flash TWRP Recovery instead of Clockwork?
Thank you for all of your help. Everyone on here has always been very helpful.
Flash it in recovery
Sent from my HTC One using Tapatalk
xcrazydx said:
Flash it in recovery
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Flash a new recovery from recovery ? that's a new one on me, I remember an old UPDATE.ZIP method does that still work ?
Rom manager and root toolbox can flash a recovery I think.
the only way I have ever done it is from fastboot usb
fastboot flash recovery TWRP.img
fastboot erase cache
or
fastboot flash recovery CWMT.img
fastboot erase cache
just make sure the TWRP.img or CWMT.img are in the same directory as fastboot
clsA said:
Flash a new recovery from recovery ? that's a new one on me, I remember an old UPDATE.ZIP method does that still work ?
Rom manager and root toolbox can flash a recovery I think.
the only way I have ever done it is from fastboot usb
fastboot flash recovery TWRP.img
fastboot erase cache
or
fastboot flash recovery CWMT.img
fastboot erase cache
just make sure the TWRP.img or CWMT.img are in the same directory as fastboot
Click to expand...
Click to collapse
That's what i do on all my Samsung phones. I don't remember if I've done it on this phone yet, actually. But yes, I always flash a new recovery from recovery.
Sent from my HTC One using Tapatalk
xcrazydx said:
That's what i do on all my Samsung phones. I don't remember if I've done it on this phone yet, actually. But yes, I always flash a new recovery from recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
interesting I was able to find a recovery flashable zip of CWMT
clsA said:
interesting I was able to find a recovery flashable zip of CWMT
Click to expand...
Click to collapse
If that doesn't work and you can't delete the recovery with fastboot erase recovery.
If you are soff find the 4.1.2 ruu exe and install it over. It'll fix the partitions and nuke recovery on its way by.
Sent from my One using Tapatalk
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.