Every time I try to flash boot.img for a custom ROM using fastboot the bootloader on the device crashes (gets stuck until manual reboot).
It seems to flash fine according to terminal.
To test, I just flashed the newest CWM recovery using fastboot and that worked fine. Bootloader didn't get stuck.
The device is crashing a lot since installing 1.29 ROMs so I think boot.img isn't flashing.
any ideas?
is that after changing roms?
You need to have correct boot.img for the ROM you are using.
Also, between changing ROMs, you should delete at least(!) the cache partition (fastboot erase cache), preferably whole /data (will reset to factory!).
Simply put - I think erasing cache will solve your problem: fastboot erase cache
Did you manage to resolve this in the end? I'm getting exactly the same issues.
Naturally, after posting, I realised that I was typing fastboot boot boot.img, forgetting to add the "flash"
Actual syntax: fastboot flash boot boot.img
Related
What are the commands for flashing a rom in fastboot?
Ive tried
Code:
fastboot flash ----.zip
?
Am doing this cause JOKERDROID4.2BUZZ.zip wont flash in clockwork mod 3.2.0.0 or 4.0.0.2. It flashes in 2.5.1.7 but boot loops. I am coming from cm7 what do you think?
You can only flash a particular partition with Fastboot, like /system /data, Recovery, boot etc. AFAIK, You cant flash a Zip ROM as is the case with CWM.
You can check the list of Fastboot Commands here:
http://android-dls.com/wiki/index.php?title=Fastboot
Also, you got 2.5.1.7? Where? AFAIK Wildfire only has 2.5.0.7. Anyway, you can use Fastboot to replace your CWM 3.x or 4.x with 2.5.0.7, then try flashing Jokerdroid. Also, make sure you are performing a wipe (Factory Reset / Wipe data in Clockworkmod)
Where can i get 2.5.0.7?
Cant remember where i got 2.5.1.7 the file name was 2.5.0.7 but cwm said 2.5.1.7?
It's there under Custom Recoveries:
http://forum.xda-developers.com/showthread.php?t=1029318
jokerdroid just bootloops!?
i have wiped and wiped cache and delvik!
Try Redownloading the ROM. Or, if you search the thread, there is one version which is clocked at 648MHz. Try that. Probably the high CPU clocks are not suiting your device.
EDIT: Scratch that. Its clocked at 710, so shouldn't cause an issue.
Well after boot looping 5 or so times it rebooted cwm then rebooted system and bootlooped once but the powered up? Wierd!
if you want to flash a .zip package:
fastboot update filename.zip
if you want to flash an img. file:
depending whether you want to flash a new recovery:
fastboot flash recovery filename.img
or a new ROM:
fastboot flash system filename.img
I do however strongly recommend erasing you current recovery before flashing a new one:
fastboot erase recovery
and do a full wipe (this will erase your data, recovery and system partitions)
fastboot erase system -w
I am seeking your help to clear up some of my confusion in solving a problem with my HTC ONE X. I tried flashing a custom ROM on my HTC Android phone but all the files and partitions got messed up that every time it boots up, it is on a bootloop. I know the cause to this is due to a mixture of inconsistent (boot, recovery)partitions libraries that I have on the phone.
Therefore, I want to FULLY WIPE OF ALL the data on the phone's storage and reinstall a clean set of libraries and stock rom. However, before I wipe off all data and install the new stock rom, I want to know all the commands that I can issue to correct this problem but the problem I have is that the stock zip has a boot.img, hboot.img and recovery.img along with a set of folders (System and Meta-inf folders) and I don't know the command that I can issue to push the folders I mentioned in the right partition, "/system" partition. Moreover, I cannot boot into any recovery modes (CWM or TWRP) so everything has to be done via fastboot commands, I think.
I know I can execute the following commands if everything(all the partitions) were an .img file but for the folders I do not know how to push them onto my phones storage.
For example to push the boot content on the boot partition, I issue the following command to flash the device
fastboot erase boot
fastboot flash boot boot.img
and the following for the rest of the partitions:-
fastboot erase recovery
fastboot flash recovery recovery.img
and so on..
So what would be the solution to push those folders that are non img format related onto the right partitions? Flash it as a zip file?
Lastly, the phone is unlocked, CID: 11111111, Hboot: 1.09 and can only boot into fastboot mode for now. I also tried running the automatic RUU files via zip and exe formats but always fail due to signature or some other missing file error.
totti_09 said:
I am seeking your help to clear up some of my confusion in solving a problem with my HTC ONE X. I tried flashing a custom ROM on my HTC Android phone but all the files and partitions got messed up that every time it boots up, it is on a bootloop. I know the cause to this is due to a mixture of inconsistent (boot, recovery)partitions libraries that I have on the phone.
Therefore, I want to FULLY WIPE OF ALL the data on the phone's storage and reinstall a clean set of libraries and stock rom. However, before I wipe off all data and install the new stock rom, I want to know all the commands that I can issue to correct this problem but the problem I have is that the stock zip has a boot.img, hboot.img and recovery.img along with a set of folders (System and Meta-inf folders) and I don't know the command that I can issue to push the folders I mentioned in the right partition, "/system" partition. Moreover, I cannot boot into any recovery modes (CWM or TWRP) so everything has to be done via fastboot commands, I think.
I know I can execute the following commands if everything(all the partitions) were an .img file but for the folders I do not know how to push them onto my phones storage.
For example to push the boot content on the boot partition, I issue the following command to flash the device
fastboot erase boot
fastboot flash boot boot.img
and the following for the rest of the partitions:-
fastboot erase recovery
fastboot flash recovery recovery.img
and so on..
So what would be the solution to push those folders that are non img format related onto the right partitions? Flash it as a zip file?
Lastly, the phone is unlocked, CID: 11111111, Hboot: 1.09 and can only boot into fastboot mode for now. I also tried running the automatic RUU files via zip and exe formats but always fail due to signature or some other missing file error.
Click to expand...
Click to collapse
if you flash that recovery it will go back to stock lol you need to flash a firmware.zip...for more information please read the guides to how to flash it...all what you need to know and need to flash is stated in those guides
Hboot 1.09 that's not a endevour HTC one X ! .....what does the top of the bootloader say ?
And second.....questions do not belong in the general section !!!
And give the outcome of :
Fastboot getvar version-main
All,
I am not a noob by any means, but when I attempted to manually flash the img files via fastboot for the latest N build from the factory images coming from the last 6.0.1 build I get stuck on the Google logo. I checked the commands and re-flashed again and the same result happened ( i did flash radios and BL ) .
I even tried to format data ( i had backed everything up ) , still no go and stuck at google logo still. I could access BL and able to access TWRP.
I got frustrated and flashed the 6.0.1 images including BL and radio via fastboot and booted up just fine. I then rooted, installed flashfire and used the OTA and Android N installed just fine.
Does anyone have any idea what could be causing this. I am currently on N, but wanted to do a clean install .
Thanks in Advance
Did you flash vendor.img?
Why don't you list the exact commands you used to flash, then people can comment.
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
sfhub said:
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
Click to expand...
Click to collapse
SlimSnoopOS said:
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have tried fastboot erase userdata and fastboot format userdata and fastboot erase cache
fastboot format cache and that never worked.
I tried that factory image before and resulted in the same, however, I will at sometime attempt to do the final of 7.1.1 once it is available sometime in December 2016 and hopefully will resolve the issue.
I will stay on DP1 right now as i find the battery extremely excellent, the Visual VM is back now, and i notice some notifications are coming through better than in 7.0. (I read an article earlier today about notifications and the pixel not coming through)
Thanks in Advance for the people that did come through so far and wanted to thank you for your input on the matter and if i don't have a pixel by December I will try this out.
Hello all,
I'm a bit confused about the process of taking my current '3' ROM and changing it to the official Lenovo Rom.
I have downloaded the lenovo drivers (installed and ok) phone is in debug mode.
I have downloaded the stock rom from here: https://forum.xda-developers.com/lenovo-p2/development/7-0-lenovo-p2a42-stock-nougat-update-t3581517 and have adb / fastboot.
I know I have to use the volume rocker and powerbutton to get into the boot mode but I don't know the commands for adb or fastboot. I have changed the name of the rom to 'update'
Can someone please advise me on the commands I am meant to enter to get this onto my phone please?
Thanks in advance,
Cue
Copy all the code below, paste it to a new text file on your PC and save it as All Files instead of .txt and name it a fastboot.bat. Place the fastboot.bat in the adb/fastboot directory, also place the unpacked rom in the same path. Run it as admin. Profit.
Code:
fastboot flash partition gpt_both0.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo pause
Hi, op here.
Firstly, thank you for responding! Your instructions seem very clear. When i had a look at the contents of the ROM (in zip) i couldn't see any of the systemchunk files you mention, are they hidden deep somewhere?
Regards,
Cue.
If your phone is stock the Rom can be updated without fastboot or a PC.
All the instructions are in that thread.
Huh. Surely just boot into recovery and install the update.zip? No need to have it connected to pc.
Hello all,
Yep. I un-encrypted the sd card copied the zip onto it and booted up that way. Very easy. Now running stock directly from Lenovo which I am very happy about! It also pushed the new 78mb update as well.
Thank you for all your input.
same way i did it too theirs no need to do it through fastboot method just like the other people i did it through the built in recovery by renaming the Nougat rom to update.zip works fine and you will get another update ota straight after t obring it right up to date.
Sounds like you guys have this sorted :highfive:
Just for completeness, can somebody upload the original 3 rom? It just helps out the person who thinks they have a hardware issue and may need to return the phone to 3.
If you try and return your phone and it doesn't have the original 3 rom, your chances of a good outcome are obviously less as you have tampered with the phone etc.
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
I did the same flashed nougat and volte is working but only shows up some times not as much as I'd like is their any way to get volte to work more often. In my bedroom where the signal is weak I don't get the volte symbol at all.
philje123 said:
The warranty is with Lenovo Not three.
Doubt there'd be an issue as the bootloader will still be locked and it's an official Lenovo Firmware.
Since flashing nougat and a factory wipe my VOLTE is now working.
Click to expand...
Click to collapse
How you enabled VoLte on nougat? You are on stock rom or branded?
I'm on stock unbranded.
VOLTE settings now show up in phone menu and it just works. I had to factory reset though as initially it didn't work after flashing nougat.
Hi all,
I'm sorry to ask this question, but I'm really struggling to get my Nexus 5X to boot into stock rom. The install seems to go ok, but there was error when flashing.. See below...
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
The phone now boots to the google boot logo, then loops back to either the "Unlocked Bootloader" or the Custom OS message. (depending on the locked state of the bootloader)
I cannot get into recovery, as the phone just loops back as described above when selecting it from the bootloader option.
Can anyone advise me on how to restore the phone back to stock os. I've tried flashing version 7.1.2 8.0.0 and 8.1.0, using either the flash-all.bat or manually typing the commands. I'm 110% sure this is not to do with over heating on CPU/RAM, I have another nexus 5x that has the bootloop of death and it's bootloop is very different from what I'm seeing on this Nexus 5x.
Thanks in advance
First, the .sig errors are normal so you can ignore those. I would make sure your booloader is unlocked then manually flash the bootloader.img. Then boot back into the bootloader. Then manually flash the remainder of the partitions. Use the 8.1.0 os.
Sent from my [device_name] using XDA-Developers Legacy app
Ok here's what I've done.
1) Downloaded bullhead-opm2.171019.029.zip from Google factory images.
2) Extracted the zip to a folder and extracted image-bullhead-opm2.171019.029.zip to the same folder to get the boot.img | system.img | vendor.img and recovery.img file. (there was no userdata.img nor cache.img within the zip, so I downloaded 7.1.1 version and extracted those files too)
3) Using SDK tools ADB /Fastboot version 1.0.38, I flashed the following:-
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
fastboot flash userdata C:\bullhead\images\userdata.img
fastboot oem lock
Everything flashed without a problem, no error. However the phone still does not boot into the OS nor can I get it to boot into recovery mode.
I cannot understand what I am doing wrong. I think it has something to do with the installation of copperhead I tried. Does anyone know whether copperhead os restricts going back to stock rom due to its additional security features?
I'm stuck!!!
Thanks in advance.
pinkstink said:
Ok here's what I've done.
1) Downloaded bullhead-opm2.171019.029.zip from Google factory images.
2) Extracted the zip to a folder and extracted image-bullhead-opm2.171019.029.zip to the same folder to get the boot.img | system.img | vendor.img and recovery.img file. (there was no userdata.img nor cache.img within the zip, so I downloaded 7.1.1 version and extracted those files too)
3) Using SDK tools ADB /Fastboot version 1.0.38, I flashed the following:-
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
fastboot flash userdata C:\bullhead\images\userdata.img
fastboot oem lock
Everything flashed without a problem, no error. However the phone still does not boot into the OS nor can I get it to boot into recovery mode.
I cannot understand what I am doing wrong. I think it has something to do with the installation of copperhead I tried. Does anyone know whether copperhead os restricts going back to stock rom due to its additional security features?
I'm stuck!!!
Thanks in advance.
Click to expand...
Click to collapse
Why don't you use the "flash-all.bat" file? I'm pretty sure you're not wiping your system partition in the process you use.
i.adrian said:
Why don't you use the "flash-all.bat" file? I'm pretty sure you're not wiping your system partition in the process you use.
Click to expand...
Click to collapse
Hiya,
I have also tried using the .bat script, it leads to the same place. A phone that does not boot.
thanks in advance.
Can you boot into twrp, fastboot boot twrp.img? If you can try formatting, not wiping, the data partition. It also gives you the option to repairing some other partitions, I don't remember which ones. You could try that.
Sent from my [device_name] using XDA-Developers Legacy app