can you flash a rom from fastboot
hmm I don't see why not... you would just use
Code:
fastboot flash *rom*
Then again, you might only be able to use that with images and not zip files so it might not work. Worst that could happen is you would get an error.
Why do you want to flash from fastboot?
cant get odin to download and trying to revert back to 2.3.2 to get 2.3.3 rooted
thegod2012 said:
cant get odin to download and trying to revert back to 2.3.2 to get 2.3.3 rooted
Click to expand...
Click to collapse
Well if it doesn't work you can fastboot the recovery, restore the nandroid in development of 2.3.2, root it and do whatever else you need to. It'll suck as you'll lose your apps but it'll do the trick.
tried that doesnt catch to img it just hangs on google
edit
tried allgamers guide and when trying to get into cwm its shows the triangle ! android
odin
i use odin to go back to 2.3.1 and still my phone wont go into recovery fastboot is good/OKAY but when going to recovery it holds at google / unlock tried 5 different downloads of img for cwm and no go
Related
i tried to put custom rom on sns but i decided to just keep it stock i want to put the original recovery that it came with so i can update in the future is it possible to update even if the bootloader is unlocked?
problem:i flashed an image but couldnt use adb with my pc.
is there a image where i can just use fastboot to flash without using adb? i was using a recovery that required me to use adb to erase some kind of sh? was stuck on that. so if theres a recovery thats doesnt need to use adb? i have a recovery but i cant flash a rom.
Are you still rooted ?
It is rooted.
If you are on stock rom already, then you can do a search using root explorer or like adao file manager for install-recovery and find it and return its name to install-recovery.sh I assume this is what you changed previously ALTHOUGH if you have CWM installed then you can probably ( and easier...ly ) just find the stock image of your phone and flash it. I just did this this morning to my phone actually..
the image for i9020T can be found here http://forum.xda-developers.com/showthread.php?t=1062777&highlight=stock+i9020t
some quick searching can probably find some other images for the different models.
once you flash one of those you may have to use fastboot to lock the bootloader back up.
"fastboot oem lock" command when connected to your phones bootloader
ive flash the zip but everything is still the same ive tried to flash with cwm v2.5.1.8 i thinks somehow this version of cwm doesnt work because i cant flash anything with this i also tried to look for install recovery.sh on adao file explorer but couldnt find it. if you can help me out would be very appreciated.
Pop out the batter of your device and tell me the model number i902......
What version of clockwork do you have?
you could try to download rom manager from the marketplace and use that to flash clockwork again. once you have done that try flashing the stock img for your model phone.. flashing zips from cwm should work.... although watch your screen when you do it see if it throws any errors
Flashed the NexusBeam ICS rom and deleted the radio and bootloader img that came with the zip and now my phone wont boot at all, I was under the impression by deleting the bootloader.img it just wouldnt install the new bootloader which is what i wanted but it seemed to haved deleted mine in the process
Yup.. Deleting those files from the package would result in the bootloader and radio being wiped and replaced by nothing.. You will probably have to use Odin to flash a stock image. Hopefully someone can help you with that, as I've never used it.
This is precisely the reason I, and some others, were asking devs not to include those files in the rom package..and we were getting crap from other people about "complaining".
Sent from my Nexus S using Tapatalk
PhillyboyDROID said:
Flashed the NexusBeam ICS rom and deleted the radio and bootloader img that came with the zip and now my phone wont boot at all, I was under the impression by deleting the bootloader.img it just wouldnt install the new bootloader which is what i wanted but it seemed to haved deleted mine in the process
Click to expand...
Click to collapse
What phone do you have? to want to delete NexusBeam ICS bootloader? I have nexus s GT-I9020 & was gonna delete the radio, but thaught I would give the new ICS one a try first! (could always flash compatible radio later on!) & it works flawlessly! Then I added GlaDOS 2.4 kernel which changed the boot animation which I didn't like (simple, just deleted bootanimation.zip from system/media, then pulled original bootanimation.zip from NexusBeam zip, & replaced!)
Just dowload NexusBeam again & use cwm recovery or fastboot to reflash NexusBeam & if you want to change radio also, do it at the same time after copying your desired rado to your sd-card & wiping dalvik cache first, then if you change your stock kernel in NexusBeam to dev one, just use method I mentioned previously if you want to change your boot animation to whatever you want! Good luck!!
I cant boot into my bootloader or recovery at all....I can boot into ICS but if i try to but into my recovery from ROM manager my phone just turns off, and if i turn it off it wont turn back on until I run a unbrick program i found. Im stuck after that though, dont know how to flash bootloader without fastboot
PhillyboyDROID said:
I cant boot into my bootloader or recovery at all....I can boot into ICS but if i try to but into my recovery from ROM manager my phone just turns off, and if i turn it off it wont turn back on until I run a unbrick program i found. Im stuck after that though, dont know how to flash bootloader without fastboot
Click to expand...
Click to collapse
After you use unbrick program & get into recovery, use fastboot to flash new cwm recovery.img! (fastboot flash recovery cwm recovery.img!) Then when you're in cwm recovery, mount usb storage & put your newly downloaded NexusBeam.zip on your sd-card & install through cwm recovery!
CrackDaddy said:
After you use unbrick program & get into recovery, use fastboot to flash new cwm recovery.img! Then when you're in cwm recovery, mount usb storage & put your newly downloaded NexusBeam.zip on your sd-card & install through cwm recovery!
Click to expand...
Click to collapse
Fixed it, didnt realized i had to hold power and vol up while running the unbrick process...thanks for all your help guys
PhillyboyDROID said:
Fixed it, didnt realized i had to hold power and vol up while running the unbrick process...thanks for all your help guys
Click to expand...
Click to collapse
Glad to hear you fixed it. Don't delete the radio or bootloader files from the package again. Instead, you can just flash a different radio after flashing the rom. The updated bootloader is a keeper though.
Sent from my Nexus S using Tapatalk
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium
Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.
I rooted my phone temporarily with pie root for motorola devices:-
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623
and on some post, it was written that we could flash custom recoveries with it using rashr. I flashed TWRP using rashr but is showed an error "hab check failed for recovery failed to validate recovery image", I ignored for that time but now, I can't use my device because of it. I downloaded an ota update for 4.4.4 and pressed install now, my phone shut down and then it tried to get into recovery and again this error, I selected Normal Powerup but, it would, after one or two minutes, again shut down to install the update. I wanted to know if there is a way to stop it and can I get stock recovery from anywhere to solve it??
nitish159 said:
I rooted my phone temporarily with pie root for motorola devices:-
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623
and on some post, it was written that we could flash custom recoveries with it using rashr. I flashed TWRP using rashr but is showed an error "hab check failed for recovery failed to validate recovery image", I ignored for that time but now, I can't use my device because of it. I downloaded an ota update for 4.4.4 and pressed install now, my phone shut down and then it tried to get into recovery and again this error, I selected Normal Powerup but, it would, after one or two minutes, again shut down to install the update. I wanted to know if there is a way to stop it and can I get stock recovery from anywhere to solve it??
Click to expand...
Click to collapse
you can get the right stock image of your phone here (non-GPE):
http://sbf.droid-developers.org/phone.php?device=14
simply open the zip and look for the recovery.img file
then just put your device in bootloader mode and via
fastboot flash recovery recovery.img
you can get your stock recovery and hopefully then your 4.4.4 update will work
Then you are lucky, that your phone is still not upgraded to 4.4.4.
Just download the factory image from the location as mentionend before and restore.
Now my personal advice:
Do not upgrade to 4.4.4. There is still no Factory image out there.
I am in that situation that my Phone does not boot and i have to reflash.
It is not possible to Downgrade to older Versions for the moment. At least not a clean solution.
So actually i and some others need a solution to make a phone out of their brick.
Hope the factory image will come quick, or at least a proper solution to Downgrade.
bernida said:
you can get the right stock image of your phone here (non-GPE):
http://sbf.droid-developers.org/phone.php?device=14
simply open the zip and look for the recovery.img file
then just put your device in bootloader mode and via
fastboot flash recovery recovery.img
you can get your stock recovery and hopefully then your 4.4.4 update will work
Click to expand...
Click to collapse
I didn't see any firmware matching my system version so I found a number matching my starting numbers in system update, and downloaded a random file with those results
bernida said:
you can get the right stock image of your phone here (non-GPE):
http://sbf.droid-developers.org/phone.php?device=14
simply open the zip and look for the recovery.img file
then just put your device in bootloader mode and via
fastboot flash recovery recovery.img
you can get your stock recovery and hopefully then your 4.4.4 update will work
Click to expand...
Click to collapse
Thanks a tonne, I could upgrade to 4.4.4 and it allowed me to connect to my lg tv usinf wifi direct which further allowed me to use miracast but, the video sometimes get stuck, don't know where the problem is, phone or tv
can i fastboot flash a rom or other zip? i've run into a problem after flashing a rom that wont boot and twrp wont mount data or my internal storage so i cant flash anything else. any help would be appretiated
I dont know how to do it, but have heard you can use the sideload feature of the twrp recovery to flash a rom. Or you could try flashing the new twrp recovery if your not on the new one. The new twrp 2.8.0.3 recovery was released on 9-30-14 last I checked its not updated on xda yet but you can get it on the twrp recovery web site which its on the link below, its the newest one on the bottom of the list.
http://techerrata.com/browse/twrp2/m8_wlv
reaper420 said:
can i fastboot flash a rom or other zip? i've run into a problem after flashing a rom that wont boot and twrp wont mount data or my internal storage so i cant flash anything else. any help would be appretiated
Click to expand...
Click to collapse
worse case scenario, run the RUU, fastboot flash recovery recovery.img then install ROM in recovery.
Honestly, you might as well apply the whole RUU and get yourself back to a working stock before putting another custom ROM back on. Follow the OP in this thread: http://forum.xda-developers.com/showthread.php?t=2873144
I tried every method possible and none worked, I recently cracked my screen so I just took this as a sign and went ahead and got it replaced with insurance. Thanks for all the suggestions
did your recovery constantly reboot into a white htc screen ?
jxcorex28 said:
did your recovery constantly reboot into a white htc screen ?
Click to expand...
Click to collapse
Are you using the correct Vzw version of twrp or cwm?