Related
Hello guys,
i got a problem. So i want to flash a boot.im gfile in the bootloader with flash-boot-windows.bat.
The problem is that i can see the statusbar in the phone, and see that the cmd tries to push the boot.im to the phone ... but nothings happen -.-
Any Idea ? Im affraid if i have crashed the boot poartition-.-
But the phoen is further working until now
Regards,
Snot
Check out fipsibs tutorial and learn to do it "properly" with fastboot (which is what the script you're using does anyway) and it'll be easier to see what's going on. Plus after you set it up once you're not depending on someone to make scripts fot you and can also use ADB and other fastboot commands http://forum.xda-developers.com/showthread.php?t=1752270
[Tutorial] How to flash a new boot.img via Fastboot
i know the tutorial .... its hanging here:
C:\Users\User\One_S_All-In-One_Kit_v1.1\Data>fastboot flash boot boot.img
sending 'boot' (6202 KB)...
And nothing is happen now. I see the green statusbar in the right corner ... but it dont fills up
hello in
http://forum.xda-developers.com/showthread.php?t=1658158
you can find stock boot.img with self flash under the
LeeDrOiD One Supreme V2.0.0 boot.img (Self flash)
there you have it, small letters. Try this
How do you mean you can see the status bar on the phone? It should be started in bootloader mode then select fastboot. I guess you did this or fastboot should give you an error... Do you get your serial number from "fastboot devices"? If so fastboot is OK, then I'd check md5sum of the boot.img. You're not trying to flash boot image for S4 device to an S3 right?
yeah i could see my device with fastboot devices. Its there ...
I can see a green status bar at flashing the rom, in the right upon corner at the telefon screen.
But the status does nothing there until i disconnect the cable after 10 or more minutes ...
I try to flash the MoDaCo.one for the HTC One S Rom ... my CPu has 1512 mhz what means i have a S4 right ?
I got no failure ... only a freeze in the progressbar ... it seems that the fastbook is unable to put the file to the mobile ... ?!
I was have the same problem for me work LeeDroid self flash but if i good remember i first flash it stock recovery via One_V_All-In-One_Kit_v1.0 it
must be the 1.0 version
Hmmm where i can get the stock HTC recovery ?
Is there a connection between the recovery and the bootloader ?
In this version 1.0 there you have stock recovery, about connection with bootloader i dont know its just works for me
Sent from my HTC One S using xda app-developers app
I think i got the problem ... the bootloader is s-on ...
but i already can install custom roms so i dont know whats happen -.-
Cant unlock it with the Unlock_code.bin ...
I have s-on too, unlocked bootloader and root. Do you try this program 1.0 version ?? i was trying everything my phone was dead only recovery was working but sdcard was unmaount and this helps
krewett said:
I have s-on too, unlocked bootloader and root. Do you try this program 1.0 version ?? i was trying everything my phone was dead only recovery was working but sdcard was unmaount and this helps
Click to expand...
Click to collapse
Yea your right ! My bootloader is unlocked too i see now ...
What you mean with programm 1.0 version exactly ?!
One_S_All-In-One_Kit version 1.0 i have it if you wont it in my case this green line on the corner was stoping before end, and then stops i was waiting one time 20 min and nothing after that i was traying everything and this program One_S_All-In-One_Kit version 1.0 hi push this stock recovery , i was see that this green line go to the end and magic 100%, i was have stock recovery and after this i try flash boot.img and works on first time before i was trying flash my boot maybe 30 times
There is no way to S-off the One S yet and being S-on won't prevent you from fastboot flashing a boot image. The recovery is a separate basic OS loaded from its own partition instead of your regular ROM, this happens after the bootloader mode so this has nothing to do with fastboot. What is the boot.img for, which ROM? Did you check the md5sum? Also you could try the earlier version of the all in one kit I guess, or redownload the one you got if you don't want to install the Android SDK.
Ok the solution was simply to use another pc ... Even the fastboot founds my One S i cant put the boot img to it.
With my notebook i works instantlly ... no idea but it works now
for me it helped to change the USB port I connected the device. The thing is it should be connected to a primary USB, not a HUB!
umm i got problem with my phone, my htc go into bootloop mode after i install Revelation rom jb 1.0.0 , it goes to htc logo sreen, then black screen, then back to htc logo screen again
i do format all partition except sdcard but no luck, then i tried to restore my previous rom, it went to bootloop too ,
what should i doo ?
everytime i went into 4ext recovery , there always appear a popup says that "there are pending update to your boot partition, do you want to remove smartflash ?" <-- i dont know what is smartflash, all i do know is my phone is in hboot 1.27 , rooted,s-off, and unlocked
and everytime after i installed any room, it says "backup of your boot partition has failed, please report this bug "
Try entering fastboot via terminal and flash boot.img manually type
fastboot flash boot boot.img
and see how it goes...
regards
_phoenix_-- said:
Try entering fastboot via terminal and flash boot.img manually type
fastboot flash boot boot.img
and see how it goes...
regards
Click to expand...
Click to collapse
umm could you explain a step by step method how i did this, kinda forget how to do this, i've "s-off"-ed , and unlocked my phone about one year ago
Assuming you have a working adb setup installed on your pc (if not follow http://forum.xda-developers.com/showthread.php?t=1152148)
1. connect your phone to pc
2. extract the boot.img of your roms .zip file and place it in your platform-tools folder (or where fastboot is located on your system)
3. type "fastboot reboot-bootloader" (on your phone it should read "fastboot usb")
4. type "fastboot flash boot boot.img"
5. when finished type "fastboot reboot"
and you are ready to go.
Remember since you are s-off, there is no need to have smartflash enabled, so disable it in your recovery...
regards
_phoenix_-- said:
Assuming you have a working adb setup installed on your pc (if not follow http://forum.xda-developers.com/showthread.php?t=1152148)
1. connect your phone to pc
2. extract the boot.img of your roms .zip file and place it in your platform-tools folder (or where fastboot is located on your system)
3. type "fastboot reboot-bootloader" (on your phone it should read "fastboot usb")
4. type "fastboot flash boot boot.img"
5. when finished type "fastboot reboot"
and you are ready to go.
Remember since you are s-off, there is no need to have smartflash enabled, so disable it in your recovery...
regards
Click to expand...
Click to collapse
could i just put the boot.img i extracted from the rom i want to flash into my sdcard and let it load in bootloader ?
sweethurt said:
could i just put the boot.img i extracted from the rom i want to flash into my sdcard and let it load in bootloader ?
Click to expand...
Click to collapse
no
put it in your adb and fastboot folder in your pc as suggested above
it works like charm, i just have to flash the boot.img from pc, even though i have to borrow my friends pc since mine on win8, anyway thank you for the information, really really help ! !
i almost got frustated since i cant do restore from backup and the flashing always stuck at <waiting for devices> in my win8 pc,
oh, one more question, if i want to flash another rom, should i just do wipe-install ( normal method ) or i still have to flash its boot.img alone from pc ? :fingers-crossed::fingers-crossed:
sweethurt said:
it works like charm, i just have to flash the boot.img from pc, even though i have to borrow my friends pc since mine on win8, anyway thank you for the information, really really help ! !
i almost got frustated since i cant do restore from backup and the flashing always stuck at <waiting for devices> in my win8 pc,
oh, one more question, if i want to flash another rom, should i just do wipe-install ( normal method ) or i still have to flash its boot.img alone from pc ? :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Just follow the normal procedure
But if you have again the same message about bending to the boot partition has failed then you will have to use the boot.img of the rom again
Sent from my HTC Sensation Z710e using xda premium
rzr86 said:
Just follow the normal procedure
But if you have again the same message about bending to the boot partition has failed then you will have to use the boot.img of the rom again
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Wanna ask something again, everytime i went into recovery to install a rom and kernel, it went to boot twice until phone went into boot animation screen. Is it normal ?
All i know is that it would only happened if i i'm on s-on, i'm s-off, and everytime i try to disable smartflash on recovery, it went enabled again
Sent from my Sensation using Tapatalk 4
sweethurt said:
Wanna ask something again, everytime i went into recovery to install a rom and kernel, it went to boot twice until phone went into boot animation screen. Is it normal ?
All i know is that it would only happened if i i'm on s-on, i'm s-off, and everytime i try to disable smartflash on recovery, it went enabled again
Sent from my Sensation using Tapatalk 4
Click to expand...
Click to collapse
smartflash from recovery always stays disabled
check from the 4ext updater if you have enabled permantly the smartflash
Hello, I had a MIUI ROM and I flashed a new version , doing the wipes and flashing it, but after the reboot, I see the HTC logo and nathing else, only the black screen.
In my bootloader appears "unlocked", saga pvt ship s-on rl, hboot 2.00.0002.
I tried to flash others ROMs and it happens the same, black screen after the HTC logo.
Thank you.
Did u flash the boot.img after flashing the roms? Since ur s-on u need to flash a rom then boot straight into bootloader and flash the boot.img then reboot. The boot img is inside the rom zip.
jmcclue said:
Did u flash the boot.img after flashing the roms? Since ur s-on u need to flash a rom then boot straight into bootloader and flash the boot.img then reboot. The boot img is inside the rom zip.
Click to expand...
Click to collapse
Can you tell me how to do it? I read something about that but I don't know how to do it.
I had the same problem today but the flash fixed it.
Estrada88 said:
Can you tell me how to do it? I read something about that but I don't know how to do it.
Click to expand...
Click to collapse
The Linux / ubuntu method
I had the same problem and followed the advice of the previous post this is how I did it:
1. First I made sure the fastboot programme was in my home directory
2. Then using a compression program I extracted the boot.img file from the "cm-11-20141214-UNOFFICIAL-saga.zip" rom. I also extracted it to my home directory (same directory as the fastboot program)
3. After installing the Rom and Gapps on my phone via TeamWin Recovery I immediately rebooted into the bootloader. and selected fastboot
4.I connected the phone via usb cable to my laptop.
5.On my laptop I opened a terminal for commandline
6. I entered the following command:
"sudo /home/simon/fastboot flash boot boot.img"
After the flash was successful I rebooted and CM11 is now working. I suppose the windows meathod follows similar principles.
Or use fastboot adb on windows.
Sent from my HTC Desire S using XDA Free mobile app
I'm totally unable to make it works. I have the "waiting for device" message, I'm reading tutorials but nothing works.
Estrada88 said:
I'm totally unable to make it works. I have the "waiting for device" message, I'm reading tutorials but nothing works.
Click to expand...
Click to collapse
U using windows? If so use this tool to setup drivers
http://forum.xda-developers.com/showthread.php?t=2588979
I got it! thank you very much
after using command fast boot flash recovery boot.img my phn got stuck in blue light...command prompt shows' waiting for device'..how long it will take to flash twrp or am i got stuck!!!pls help me
XDA Visitor said:
after using command fast boot flash recovery boot.img my phn got stuck in blue light...command prompt shows' waiting for device'..how long it will take to flash twrp or am i got stuck!!!pls help me
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Does not sound like anything ill was done, as it did not connect. This could be a cause of one of three things:
Phone is not in the bootloader
Even if in the bootloader, fastboot mode is not activated
PC drivers for fastboot may not be appropriate (or maybe even an outdated fastboot program)
To help you further, can I get the make, model and carrier (if bought through said carrier) of your phone?
Many thanks.
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!