Hi there,
When i'm going to flash FLAUW B7 kernel i'm getting an error.
1. put the boot.img in the fastboot folder.
2. use the command: fastboot boot boot.img succesfull
3. use the command: fastboot erase cache is getting up with a FAILED error. Just failed. No code.
After that the phone hangs and needs to be reset.
Any suggestions?
MDLefevere said:
Hi there,
When i'm going to flash FLAUW B7 kernel i'm getting an error.
1. put the boot.img in the fastboot folder.
2. use the command: fastboot boot boot.img succesfull
3. use the command: fastboot erase cache is getting up with a FAILED error. Just failed. No code.
After that the phone hangs and needs to be reset.
Any suggestions?
Click to expand...
Click to collapse
Try flashing the boot.img first, then flasing the .zip in recovery and erase cache afterwards.
Tried to erase cache but same problem.
I cannot flash the zip file with recovery because I didn't copy it on my sdcard.
Any other thoughts?
Thanks.
Mount the sdcard as a diskdrive in recovery and copy the file !
Related
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
Hello,
Id appreciate any help with my problem:
After wishing to upgrade to JB from ARHD 9 (ICS), I flashed the correct Hboot and upgraded CWM to 5.8.4.0. However, when trying to flash the ARHD ROM, im getting a "failed installation" message after selecting the zip on the SD card. I thought it might be the boot.img i was using (from the download section), so used the one from the ROM zip instead. No luck. I erase the cache etc very time I can.
Any ideas to what might be the problem?
Thanks in advance
so you have a hboot 1.3* and you flashed the boot.img with fastboot command
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
then entered recovery and did a FULL wipe (also dalvik cache under the advanced tab)
then trying to install the rom.zip ?
install failed, redownload the rom, might be corrupted !
Mr Hofs said:
so you have a hboot 1.3* and you flashed the boot.img with fastboot command
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
then entered recovery and did a FULL wipe (also dalvik cache under the advanced tab)
then trying to install the rom.zip ?
install failed, redownload the rom, might be corrupted !
Click to expand...
Click to collapse
exactly - all steps followed. currently downloading it again...
Hi,
I got a HTC One X (JB, ARHD 19.2)
I'd like to use the XM-Kernel (http://forum.xda-developers.com/show....php?t=2136731)
but I don't understand the 4th instruction here given in the kernel thread.
"1.Install modules from recovery (Install the zip)
2.Wipe dalvik cache.
3.Erase fastboot cache
4.Flash kernel image with fastboot"
Flash kernel image with fastboot ?
Do I have to unzip the kernel on my computer, use the " new_boot.img " file inside the folder ?
So... The question is : Where's the kernel image ??
the boot.img could be in the .zip file. open it and check it......i dont know if its need to be repacked for the rom you are using by the way....
Open the xmkernel zip and extract 'boot.img' or 'senseboot.img' to your fastboot folder. Copy the intact zip to your sdcard and flash in cwm after flashing kernel. Xmister advises that no repacking is required, but I used the online service anyway.
Thanks for this post, answered my queston. One more thing:
Is there a specific fastboot command for flashing kernal image like there is for, say, boot.img
i.e. fastboot flash boot boot.img?
iang265 said:
Thanks for this post, answered my queston. One more thing:
Is there a specific fastboot command for flashing kernal image like there is for, say, boot.img
i.e. fastboot flash boot boot.img?
Click to expand...
Click to collapse
Yes its
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
And as additional info, if you ever made a nandroid backup with twrp recovery you get a boot.emmc.win file (its the boot.img)
Fastboot erase cache
Fastboot flash boot boot.emmc.win
Fastboot erase cache
Mr Hofs said:
Yes its
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
And as additional info, if you ever made a nandroid backup with twrp recovery you get a boot.emmc.win file (its the boot.img)
Fastboot erase cache
Fastboot flash boot boot.emmc.win
Fastboot erase cache
Click to expand...
Click to collapse
Thank you, it's worked a treat. :good:
as title says ive tried loads of stuff and seem to have hit a brick wall.
tried to root phone and thats when it went wrong
system info is
3.14.206.27 version
s on
boot is hboot 1.36.0000
boot loader unlocked
tried recovery from and it comes up with errors it wont flash files over can mount sd card and stuff like that
last night when i was tired i had formated all the storage in the phone got clockworkmod recovery 5.8.3.1 on it
wont recover the O2_001 3.14 Stock JB comes up with errors tried through adb and get an error about a buffer stack.
im running windows 7 any help would be great or if some one near nottinginham i can take the phone too and ither buy drinks or cash to sort it
First flash cwm 5.8.4.0
http://db.tt/Krlm4dPs
Put the file in the fastboot folder and rename it to recovery.img
Put the phone in the bootloader and open a command prompt inside the fastboot folder. Point in the folder, hold shift and right click the mouse - select open command window here
Then type
Fastboot erase cache
Fastboot flash recovery recovery.img
Fastboot erase cache
Then download a rom of your choice, open the rom.zip and copy the boot.img file to the fastboot folder.
Flash that too
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and mount the sdcard as a mass storage device and copy the rom.zip to it.
Then make a full wipe....
factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache,data,system
Then install the rom.zip
Mr Hofs said:
First flash cwm 5.8.4.0
Put the file in the fastboot folder and rename it to recovery.img
Put the phone in the bootloader and open a command prompt inside the fastboot folder. Point in the folder, hold shift and right click the mouse - select open command window here
Then type
Fastboot erase cache
Fastboot flash recovery recovery.img
Fastboot erase cache
Then download a rom of your choice, open the rom.zip and copy the boot.img file to the fastboot folder.
Flash that too
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and mount the sdcard as a mass storage device and copy the rom.zip to it.
Then make a full wipe....
factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache,data,system
Then install the rom.zip
Click to expand...
Click to collapse
thank you so much i got viper on the phone then copyd the o2 nandroid backup to the phone and it recoverd ok
Good !
CASE CLOSED !
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:
xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.
hardest soft-bricked ever seen!!!
anybody haven't idea?
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---