How would one go about flashing a kernel?
I tried looking at Xboarder's kernel guide, but it looks like the thread got deleted and I couldn't find a Kernel Flashing guide.
I tried flashing Faux's new kernel via 4ext and got the following:
E:error in /internal_sdcard/ruby-faux123-kernel-v002.zip
(status 7)
Installation aborted.
Tried doing it via Hasoon's toolkit. I downloaded the zip file, placed it in data/kernel and renamed it Boot.IMG
flashed and got the following:
C:\Users\Evan\AppData\Local\Temp\Rar$EXa0.438\data>fastboot flash boot Ker
nels/boot.img
< waiting for device >
sending 'boot' (12353 KB)... OKAY [ 2.643s]
writing 'boot'... FAILED (remote: image error! (BootMagic checkfail)) finished.
total time: 2.959s
C:\Users\Evan\AppData\Local\Temp\Rar$EXa0.438\data>fastboot reboot
rebooting...
finished. total time: 0.169s
What am I doing wrong?
I'm S-off, with an unlocked bootloader and rooted running Speedrom 6.0.
broker32 said:
How would one go about flashing a kernel?
I tried looking at Xboarder's kernel guide, but it looks like the thread got deleted and I couldn't find a Kernel Flashing guide.
I tried flashing Faux's new kernel via 4ext and got the following:
E:error in /internal_sdcard/ruby-faux123-kernel-v002.zip
(status 7)
Installation aborted.
Tried doing it via Hasoon's toolkit. I downloaded the zip file, placed it in data/kernel and renamed it Boot.IMG
flashed and got the following:
C:\Users\Evan\AppData\Local\Temp\Rar$EXa0.438\data>fastboot flash boot Ker
nels/boot.img
< waiting for device >
sending 'boot' (12353 KB)... OKAY [ 2.643s]
writing 'boot'... FAILED (remote: image error! (BootMagic checkfail)) finished.
total time: 2.959s
C:\Users\Evan\AppData\Local\Temp\Rar$EXa0.438\data>fastboot reboot
rebooting...
finished. total time: 0.169s
What am I doing wrong?
I'm S-off, with an unlocked bootloader and rooted running Speedrom 6.0.
Click to expand...
Click to collapse
The lines highlighted in red is probably what's wrong. You're running the batch file INSIDE the archive. Unzip/decompress it and then run it (in the uncompressed folder)
Keylogger_0 said:
The lines highlighted in red is probably what's wrong. You're running the batch file INSIDE the archive. Unzip/decompress it and then run it (in the uncompressed folder)
Click to expand...
Click to collapse
Oh, I see. How would I go about doing that?
I tried running it through the Easy Kernel Flasher. Extracted the Easy Kernel flasher to a folder in my desktop. Extracted the Faux's kernel files, put them in a folder, placed the folder in "Kernel here", renamed it boot.IMG. Clicked the flash.bat and got this.
C:\Users\Evan\Desktop\Easy Kernel Flasher>adb reboot bootloader
C:\Users\Evan\Desktop\Easy Kernel Flasher>fastboot flash boot Kernel-Here/
boot.img
< waiting for device >
sending 'boot' (12353 KB)... OKAY [ 2.630s]
writing 'boot'... FAILED (remote: image error! (BootMagic check
broker32 said:
Oh, I see. How would I go about doing that?
I tried running it through the Easy Kernel Flasher. Extracted the Easy Kernel flasher to a folder in my desktop. Extracted the Faux's kernel files, put them in a folder, placed the folder in "Kernel here", renamed it boot.IMG. Clicked the flash.bat and got this.
C:\Users\Evan\Desktop\Easy Kernel Flasher>adb reboot bootloader
C:\Users\Evan\Desktop\Easy Kernel Flasher>fastboot flash boot Kernel-Here/
boot.img
< waiting for device >
sending 'boot' (12353 KB)... OKAY [ 2.630s]
writing 'boot'... FAILED (remote: image error! (BootMagic check
Click to expand...
Click to collapse
Is there a file named just "boot" in the faux kernel zip file?
Put your phone in bootloader first then run the command again.
you should have no problem installing the zip through 4ext, could be a bad download? have you tried downloading again? and same error? I don't think any of the ICS kernels have a boot.img attached in the zip
Be careful flashing the kernel.
soundping said:
Be careful flashing the kernel.
Click to expand...
Click to collapse
"Location: Southern Indiana"
"Attached Thumbnail: Kentucky Fried Chicken"
Now it all makes sense.
Sounds like a bad download.. 4ext should flash it fine. Try looking up status 7.. or update 4ext to latest version. But definitely download it again, using a different browser, or connection, something.. but everything I've seen says it is a bad download.
Another thing you can check is to be sure you downloaded the ICS kernel and not the GB one.
Turns out that the 4.ext version I had wasn't the latest. Made the update and flash was successful!
Thank you guys!
will flashing the kernel delete my data? should i backup first??
blindskater39 said:
will flashing the kernel delete my data? should i backup first??
Click to expand...
Click to collapse
No and yes. Always have a good backup as it will backup kernel and everything. Make sure you're using 4ext, anything else probably wont work properly. Make sure you know what you're doing and you will be fine, check the bible in my signature if you aren't sure of anything.
Sent from my Nexus 7 using xda app-developers app
Flashing different kernels
Is there some step I need to take before flashing different kernels? I ask because I was using stock and couldn't connect to Ford sync via Bluetooth, so I thought I'd try Faux123. Unfortunately using Faux123 my Plantronics BT headset wouldn't automatically connect any longer so I thought I'd go back to stock. Now, my WiFi won't connect at all. Searching brought up all kinds of threads on how to flash a kernel, but I didn't see anything that said that I needed to do something else before flashing a kernel. I flashed the stock kernel from the one posted in the 5th post of NRG's ROM thread. Any suggestions?
Related
Hi!
I tried to update using the pkg file from http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak and got an error message.
failed getprod("ro.product.foto.model") == "Boss... and then rebooted.
Anyone have an idea?
thanks
Young
Hi,
have you flash the Recovery.img for the Dell 2.2.2/345 Rom ???
http://forum.xda-developers.com/showthread.php?t=1000455 <-
Greetings
UKSheep
No, I have not. I will do that first later today then the upgrade.
Thanks
No problem
Use the 2.2.2/345 Recovery and it works
MfG
UKSheep
moving from 340 to 351
I didn't try for 345 but I was trying to upgrade 351 today got the following error.
"assert failed: !less_than_int(xxxxxxxxx,getprop("ro.build.date.utc")"
I think I used correct recovery from MRF..
.:: Dell Streak - Multi Recovery Flasher ::.
Connect yout Streak in "fastboot_mode"
[8] flash Dell-Recovery 2.2.2/351
Select:8
sending 'recovery' (3434 KB)... OKAY [ 0.328s]
writing 'recovery'... OKAY [ 2.094s]
finished. total time: 2.422s
rebooting...
finished. total time: 0.000s
Please let me know what I am doing wrong.
thanks,
Dont let the device reboot after flashing the necessary recovery .
Reboot will overwrite the recovery unless you do the following
You can also prevent the overwrite of the recovery by renaming the file install-recovery.sh to something else. It's in /system/etc. I just added.bak to the file name.
Hence the easy option is to pull battery .
THen go to recovery and flash 351
I have renamed install-recovery.sh and reinstalled the recovey but flashing still not working with the same error.
I have successfully unlocked my bootloader using the htcdev.com way. Then I tried to flash FlyHigh ROMv1.2, unfortunately my Wi-Fi is unable to turn on. I get Error everytime I try to turn on my wi-fi. Then I tried to flash radio.img using the fastboot command: "fastboot flash radio radio.img" but it gives me an error message.
Code:
sending 'radio' (256000 KB)...
OKAY [ 4.161s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.082s
I was able to flash boot, recovery, the only thing that failed was radio.
Help me please.
EDIT: I got HC working, so nevermind.
Questions like this should go into General section or in the respective ROM thread. You mention FlyHigh, which already has a radio (20.3504.3 0.089BU_3809.07.04.12_M).
I would recommend to fullwipe your device with recovery twice and then re-flash FlyHigh via Recovery.
Sorry about the wrong section.
I fullwiped twice and flashed the FlyHigh ROM again but it doesn't work. I still cannot turn on my Wi-Fi, is it something wrong with the radio or something else?
is it possible for anyone to post a rogers nandroid back up
i flashed osimod rom buh when i tried flashing the RUU downloaded from http://forum.xda-developers.com/showthread.php?t=1287553
and i keep getting stuck on the error described below, i also tried using the exe and locking the bootloader
C:\android-sdk-windows>fastboot flash zip update.zip
sending 'zip' (456867 KB)...
OKAY [ 39.978s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 40.170s
with bootloader locked and updating updating through .exe i get error on line 8 -Fail-Pu
get partition update fail
Oi vey.
That's not how you update your device. When you get an update.zip for a custom ROM, such as the ones you'll find here on XDA, you need to flash it via ClockworkMod Recovery.
In the Jetstream - Android Development forum you'll find instructions on how to root your device and install the custom recovery image. Once that's done, you'll boot your device into recovery mode, and install your update.zip from there.
I have no idea what "fastboot flash zip" even does. You may have completely screwed your device. That being said, head here: http://forum.xda-developers.com/showthread.php?t=1418084 and follow the instructions to install ClockworkMod Recovery.
I'm not sure just how well that'll work for you. Good luck, sir!
i m able to flash the rom buh it wont boot up when connected to pc it shows the tablet is running but the screen will remain black,
finally able to fix it i went to cwm mounts and storage formatted the system, date and everything tht had format on it and somehow it fixed it, do u have any suggestion on how to flash the stock rom?
http://forum.xda-developers.com/showthread.php?t=1287553
That thread points to a collection of all the RUU's available for download. I haven't had any luck flashing my own, so good luck!
I tried that didn't wrk
I was running the latest TRON ROM from Neo with no issues for several days. Tonight, I went to use the camera and it FC'd. It kept doing it so I tried rebooting. It flashed the white screen with the green HTC logo and thats it, it won't go any farther.
I can get to recovery by pulling the battery and using the hard buttons, but recovery is not able to mount the internal or external memory. I cant backup, restore, flash a zip, or do anything really. How could this have happened? Am I bricked?
HELP!
If the phone does anything at all, it is not bricked. (The state it's in is sometimes called a soft brick, though). I believe there are two things you can do: either get an RUU (PH98IMG.zip) onto your SD with a computer (and an SD card reader EDIT: Or the Incredible you mentioned in the ROM thread), then boot up to hboot and let it flash, or try flashing a kernel (boot.img), ROM, or RUU using adb/fastboot.
If you have questions about the first of these processes, I may be able to answer them, but I probably won't be too helpful about the latter since I haven't flashed anything with adb/fastboot in quite a while.
HERE is the latest RUU, by the way.
Thanks, I'll try this out tomorrow.
s-on? Can you boot into the bootloader? Try reflashing the kernel via fastboot.
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
trud9340 said:
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
Click to expand...
Click to collapse
Did you re-unlock after running the RUU?
trud9340 said:
So I was able to get the latest RUU and flash it using Hboot. The phone booted up into stock. Great news!
However, I am now trying to get custom recovery installed again, but when I try to flash amon ra using "fastboot flash recovery recovery.img" I get the following error:
sending 'recovery' (7074 KB)..
OKAY [ 1.503s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.831s
Click to expand...
Click to collapse
download this zip and place it on the root of your sd card. it will flash Amon RA through hboot. no need for fastboot commands.
http://androidfilehost.com/?fid=9390248398092764223
mjones73 said:
Did you re-unlock after running the RUU?
Click to expand...
Click to collapse
Just realized that, after doing some research...DOH!
Unlocked and good to go. Thanks!
After fumbling with install twrp in order to change over to CM13 from stock, I somehow managed to install the original recovery wrong as well as completely boning the OS. Because of this, on boot, all that shows is the honor screen continuously. Of course the obvious answer to this is to reinstall twrp and restore one of my recovery files. Unfortunately trying to flash twrp through fastboot results in an "FAILED (data transfer failure (Unknown error))". Any suggestions? I can't access the phones internal storage nor the SD card either when I plug it into my PC.
Only one solution, flash a stock firmware using a PC.
PalakMi said:
Only one solution, flash a stock firmware using a PC.
Click to expand...
Click to collapse
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Dueter1um said:
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
Click to expand...
Click to collapse
I don't think only fastboot is enough, but take a look at the link provided by JT-on
JT-on said:
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Click to expand...
Click to collapse
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Dueter1um said:
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Click to expand...
Click to collapse
Happy for you, next time be careful
I got this same error, had to use different USB cable and different USB port.