Related
http://code.google.com/android/nexus/images.html#yakju
https://groups.google.com/forum/?fromgroups#!topic/android-building/b50nY_onbP4
^Thanks.
This can be flashed via CWM recovery ?
(after a 'fastboot oem lock/unlock' ?)
No. They are fastboot images. If you're not sure what these are and how to use them then I would not mess with them.
^ gotcha
can someone please put up a tutorial/guide to do this.
I really want to try this.
The shell script gives you the exact fastboot commands to run if you want to do it manually. And it will restore your phone to a true factory state with 4.0.4.
if i will use the factory img the baseband version in bootloader will be change? i see now i9020xxkl1 but my nexus is i9023?
I was wondering the same .. In the zip it says :require board=herring
require version-bootloader=I9020XXJK1|I9020XXKA3|I9020XXKI1|I9020XXKL1
require version-baseband=I9020XXJK8|I9020XXKB1|I9020XXKD1|I9020XXKF1|I9020XXKI1|I9020UCKB2|I9020UCKD1|I9020UCKF1|I9020UCKJ1|I9020KRKB3|M200KRKC1
So it should be okay , because when I reboot into the bootloader of my phone it says :
Bootloader version: I9020XXKL1
Baseband version : I9020XXKI1
My phone actually is a I9023 so I gues the images are okay to flash on a I9023
Just noticed that the full ROM version for Nexus S is 4.0.4 IMM76D. Wouldn't be better to flash this complete rom instead of the partial patch OTA which is clearly giving troubles?
HELPPPPP
can someone please put up a tutorial/guide to do this.
I really want to try this.
i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307
goldy_rocky said:
can someone please put up a tutorial/guide to do this.
I really want to try this.
Click to expand...
Click to collapse
(No time to write a full tutorial right now but...) I'd say...
Pls wait for someone experimented to confirm what I say because I couldn't try it to confirm it works right now... And also try it at your own risk...
If your bootloader is not unlocked, follow PART 1 & PART 2 of this tutorial. (you will loose data)
(Note that ADB is not in tools folder anymore but in /platform-tools so that's where the part2 cmd as to be runned from)
Then if windows (I guess you would know what to do if on Linux) use 7zip to extract (2 times) all files from the archive.
Then copy the files to the /platform-tools folder.
The open a command prompt in that folder (shift+right click>open a command prompt here).
Then use the commands provided in the .sh script to flash all files (you can read it easily with Notepad++ for instance) one by one...
Note I don't think you can run the "sleep 5" cmd manually but you can of course wait 5' manually .
Code:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-soju-imm76d.zip
I'm not really sure if bootloader will be locked at this time but my guess is no so just reboot the bootloader ("fastboot reboot-bootloader" or shut down the device then "Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button" and look for the "LOCK STATE - LOCKED" or "LOCK STATE - UNLOCKED").
If "LOCK STATE - UNLOCKED" you may want to lock the bootloader again, just follow part2 again and replace "fastboot oem unlock" by "fastboot oem lock"
EDIT :
ale.landra91 said:
i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307
Click to expand...
Click to collapse
You just made me feel so useless ...
First of all, the credits goes to "a2b". I am only put his work here via a link.
Secondly, PLEASE KEEEP IN YOUR MIND THAT NEITHER ME OR "a2b" IS RESPONSABLE FOR ANY LOSS OF YOURS IF YOUR PHONE GET BRICKED.
The thrid, I have tried the method on my Nexus i9023. It works perfectly for me. BUT, I cannot gurentee it works for everyone.
Okay, I just flashed the factory img according to a2b's tutorial for Galaxy Nexus. But for me I just needed to change the names for few files. If you cannot figure out what to change, I suggest you follow albundy2010's advice on post #3
Good luck!
http://androidtobe.blogspot.com/2011/12/galaxy-nexus-installing-ics-402-from.html
Seems most are not familiar with doing this so here are some things you should know.
Doing this will wipe EVERYTHING off your phone. Yes, everything including /sdcard.
Do not be a fool and flash these images to the 4g.
I am not certain about this and if you it and your phone gets messed up do not blame me.
The 9020a should be able to run this factory image. Check to see what version of the bootloader you have. If it matches one of the bootloaders in the .sh script you should be fine. I would NOT flash the bootloader included in this factory image myself. Since I do not know for sure if they are the same for both GSM models. If you follow the guide minus the parts where you flash the bootloader and the radio image I believe it will work.
Again if you try this and it breaks your phone that is on you. I am not responsible for it. I do not have a 9020a to test this on and verify it. I am fairly certain it will work perfectly. If anybody tries it let me/us know the outcome.
is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?
mindwalkr said:
is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?
Click to expand...
Click to collapse
No
Sent from my Nexus S using XDA App
I used the flash-all.sh script from the factory image file and it didn't wipe the sdcard. Backed it up beforehand anyway just in case. Recovery was broken on reboot. Flashed CWM recovery and all good. i9023.
I have a new rooted and unlocked Nexus 7. I flashed a kernel and can't get past the nexus boot screen. My battery is about dead. What do I need to do! I have the tookkit, but I can't get it to do anything! Please help! My battery is almost gone!
Infuser86 said:
I have a new rooted and unlocked Nexus 7. I flashed a kernel and can't get past the nexus boot screen. My battery is about dead. What do I need to do! I have the tookkit, but I can't get it to do anything! Please help! My battery is almost gone!
Click to expand...
Click to collapse
And I don't have any backup ROMS or kernels to flash...
Infuser86 said:
And I don't have any backup ROMS or kernels to flash...
Click to expand...
Click to collapse
Battery just died. I could not turn it off. Everytime I tried to, it booted right back up. I was in recovery, but as I said, I have no roms or kernels to flash. I tried to mount the device, but was unsuccessful. I clicked mount system and nothing showed up on computer. Couldn't click mount sd card.
Someone please help me.
Always make a back up... we'll starting now
Let it charge, try again to get the proper kernel and flash in recovery. If it won't let you mount SD to transfer, extract the boot.img from the ROM you were using and flash via fastboot.
fastboot flash boot boot.img
fastboot reboot
See what happens
Sent from my Nexus 7 using xda premium
Can you please explain how to do that? I am new to the Nexus. I can get into Fastboot and then recovery. But how would I flash via flashboot. I do not see that option.
Edit
I do suggest reading up a bit on android or you are bound to find yourself in these situations. Also try and stay away from toolkits, you would already know what to do if you weren't using them
Download rom of choice to computer
Extract the boot.img from the .zip
After you charge nexus a bit, plug into computer and boot into bootloader
Open command/terminal on computer in the same location the boot.img is and type
fastboot devices
If you get 'waiting for device' you need to download the proper drivers, and or need to change directories to where fastboot.exe is located on PC, or just make sure you download everything from the platform-tools in the sdk and I recommend changing the path in environmental variables to include adb/fastboot
If you see your serial number proceed
fastboot flash boot boot.img
fastboot reboot
this should replace the kernel causing your boot loop with and all is well
Sent from my Nexus 7 using xda premium
demkantor said:
I do suggest reading up a bit on android or you are bound to find yourself in these situations. Also try and stay away from toolkits, you would already know what to do if you weren't using them
Download rom of choice to computer
Extract the boot.img from the .zip
After you charge nexus a bit, plug into computer and boot into bootloader
Open command/terminal on computer in the same location the boot.img is and type
fastboot devices
If you get 'waiting for device' you need to download the proper drivers, and or need to change directories to where fastboot.exe is located on PC, or just make sure you download everything from the platform-tools in the sdk and I recommend changing the path in environmental variables to include adb/fastboot
If you see your serial number proceed
fastboot flash boot boot.img
fastboot reboot
this should replace the kernel causing your boot loop with and all is well
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Learned that the hard way! So if I download the ParanoidAndroid ROM, just extract it and get the IMG file?
Infuser86 said:
Learned that the hard way! So if I download the ParanoidAndroid ROM, just extract it and get the IMG file?
Click to expand...
Click to collapse
Took the img from the ROM and fastbooted it and it wrote, but tablet won't load past Google screen...
So the only thing you did to cause it to get stuck originally was flash a kernel? If that was it and then Fashing the right kernel doesn't work and recovery won't let you Mount to put a ROM on SD, I would flash one of the official full ROM updates through fastboot.
There are a bunch of them posted here just grab one and flash it and she what happens
Sent from my Nexus 7 using xda premium
This Optimized Guide is for NvFlash Flatline only! That is for stock Android Versions: 10.6.1.15.3 - 10.6.1.27.5.
According to this post and this post, it works with the tf300tg as well. Bootloader: 10.6.2.11
Original Thread: http://forum.xda-developers.com/showthread.php?t=2455922
Why install NvFlash?
rayman said:
The AndroidRoot.Mobi Team is proud to present Flatline: Nvflash for TF300T Jellybean!
This release allows generating nvflash blobs for your specific device, making your device unbrickable as long as you have a copy of the blobs.
As a brand new feature, it will also enable wifi and upload a copy of the blob to androidroot's server. Later, a solution will be released to retrieve the blobs from the server if you ever loose them.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Credit goes to the AndroidRoot.Mobi team:
Bumble-Bee (Apache14), IEF, kmdm, lilstevie & RaYmAn.
Click to expand...
Click to collapse
You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
Guide:
1) Download files
NvFlash for windows.
and the TF300 image, which is a custom recovery for the purpose of flashing the AndroidRoot Bootloader.
Place image in ADB folder, and rename it to: flatline_device.img
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power and vol down button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery flatline_device.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6) Reboot into recovery which should be CWM at this point. Go Advanced -> Wheelie. Accept the warning.
step 1) Flash AndroidRoot BL
The device will shut down, reboot into Android. Then reboot back into recovery.
step 2) Once back in recovery select go to Advanced ->:”Generate wheelie blobs” Be patient here too.
They can be found in the device at /data/media/AndroidRoot" or /tmp/AndroidRoot
You can use ADB to get them:
Code:
adb pull /data/media/AndroidRoot
or
Code:
adb pull /tmp/AndroidRoot
Alternatively, you can use a root file explorer such as ES File Manager. Be sure to copy all of the files out of the directory. Make sure you have root access before you try to search for the files.
Keep this file safe in multiple places.
7)The next section (Accessing NVFlash) is for creating more essential backups with NVFlash.
step 1) Hold down the volume up key while rebooting and the tablet is plugged in via USB. (This may take a few tries to get into APX mode). If you are successful, the screen will be blank and the device name on the computer will be something along the lines of "NVIDIA APX"
step 2) Take the NvFlash tools zip and extract them to a folder. Shift right click in that folder and select "Open Command window here".
step 3) Copy the blob.bin from the Step # 7 above into the NvFlash folder.
step 4) run the command:
Code:
wheelie --blob blob.bin
8) Next we run some commands to get even more backup files. These should all be run from the same command window in the previous step.
Code:
nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Code:
nvflash --resume --read 14 factory-config.img
Code:
nvflash --resume --read 7 unlock-token.img
These files will be stored in C:\User\AppData\Local\VirtualStore (on the computer)
If they are not there, run a search on your computer for
Code:
*img
9.) Flash any other recovery you want, including TWRP. Be sure it is the correct version for your bootloader.
10.) Store ALL of the img files AND the blob.bin AND all other files in the folder in multiple safe places (email, dropbox, HDD, flash drive, SD card, tape backup, or your favorite plant etc.)
11.) Enjoy the peace of mind that you can now restore your device if you brick it
Hit that thanks button if I helped and also thanks to @bucket81 and of course AndroidRoot.mobi devs @rayman
Recovery
For recovery from a brick when you have already made your NvFlash backups, look here:
As @ebildude123 pointed out, first try
Code:
nvflash -r --download 5 twrp.blob
where the output should be:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
ebildude123 said:
Then the device proceeded to reboot into android
Click to expand...
Click to collapse
If that does not work, try using the method here:
http://forum.xda-developers.com/showthread.php?t=2590450
Thanks to @lj50036 and @bucket81
Hello guys! This nvflash does it work in the Memopad 301T or only TF300T? Both tab works for Tegra 3.
nadorf said:
Hello guys! This nvflash does it work in the Memopad 301T or only TF300T? Both tab works for Tegra 3.
Click to expand...
Click to collapse
If you can flash a Tf300t version of CWM recovery to your ME301 then it could work. I dont have a 301, so i cant test it but i dont think it will because this is bootloader specific and the me301 does not have the same bootloader.
Does this work with TF300TG\L?
spider623 said:
Does this work with TF300TG\L?
Click to expand...
Click to collapse
Im not sure if you can flash a tf300t recovery on a TG or L. If you can, then it should work fine, but if you have to use a separate recovery, then this may not be compatible. You could try modding a tf300tg CWM with the NVflash scripts though, but dont expect any support.
cmendonc2 said:
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
adb devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery flatline_device.img -i 0x0b05
Blue bar on device will fill. Be patient.
Click to expand...
Click to collapse
Think you mean fastboot devices not adb devices
cmendonc2 said:
Im not sure if you can flash a tf300t recovery on a TG or L. If you can, then it should work fine, but if you have to use a separate recovery, then this may not be compatible. You could try modding a tf300tg CWM with the NVflash scripts though, but dont expect any support.
Click to expand...
Click to collapse
It is for twrp but no idea for cwm
Sent from my Nexus 4 using Tapatalk
spider623 said:
It is for twrp but no idea for cwm
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
You could use WinRar to extract the NvFlash scripts from the tf300t image version but i dont really know how you would implement those then,
cmendonc2 said:
You could use WinRar to extract the NvFlash scripts from the tf300t image version but i dont really know how you would implement those then,
Click to expand...
Click to collapse
No need, they are the same, only difference is one file that you can put in any rom before flashing to her the radio to work, same for the TL
Sent from my Nexus 4 using Tapatalk
Just wondering, if I made the blobs for preJB, then upgraded to JB (so now I'm on JB bootloader), should I bother using Flatline? or will my preJB blobs be ok (and make me unbrickable)?
cravinRiboflavin said:
Just wondering, if I made the blobs for preJB, then upgraded to JB (so now I'm on JB bootloader), should I bother using Flatline? or will my preJB blobs be ok (and make me unbrickable)?
Click to expand...
Click to collapse
Well, when you restore, you restore back to ICS bootloader so you will have to reflash the stock JB zips first. I don't think its worth the hassle if you already have them.
Hey guys, I want to get some custom ROM to my TFT300. But first I want install this NvFlash Flatline, if anything goes wrong.
But now I´m looking that my android version is already 10.6.1.27.5.-20130902.
But you say in the first post that the Flatline is only for 10.6.1.15.3 - 10.6.1.27.1.
So is it a problem or it should be working anyway?
Thanks a lot
BrakeZ said:
Hey guys, I want to get some custom ROM to my TFT300. But first I want install this NvFlash Flatline, if anything goes wrong.
But now I´m looking that my android version is already 10.6.1.27.5.-20130902.
But you say in the first post that the Flatline is only for 10.6.1.15.3 - 10.6.1.27.1.
So is it a problem or it should be working anyway?
Thanks a lot
Click to expand...
Click to collapse
Since it is also the latest 4.2 bootloader, it should work fine.
cmendonc2 said:
Since it is also the latest 4.2 bootloader, it should work fine.
Click to expand...
Click to collapse
I had 10.6.1.27.5 on my device before i upgraded it to CM11 with Grimlock kernel. I did it with the tool for idiots in a hurry so i did not remember to do this but one guy at Q & A section said this should be easy to do even i have CM11. I am kind of new with these tablets and android so i dont know very much but does that work exactly same way even i have CM11 that i would have Stock rom with 10.6.1.27.5 or is the bootloader changed in the CM11? I have Scanno TWRP. As i said i am very confused about these names and dont know very much but little guidance would be a great help.
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Matatusku said:
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Click to expand...
Click to collapse
Installing CM does not change your bootloader, so if you were running the latest Asus firmware before, you should be fine.
To make sure, you can check the bootloader version on the top-left of the bootloader screen.
Sent from my TF300T using Tapatalk
Matatusku said:
I had 10.6.1.27.5 on my device before i upgraded it to CM11 with Grimlock kernel. I did it with the tool for idiots in a hurry so i did not remember to do this but one guy at Q & A section said this should be easy to do even i have CM11. I am kind of new with these tablets and android so i dont know very much but does that work exactly same way even i have CM11 that i would have Stock rom with 10.6.1.27.5 or is the bootloader changed in the CM11? I have Scanno TWRP. As i said i am very confused about these names and dont know very much but little guidance would be a great help.
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Click to expand...
Click to collapse
No, the bootloader does not change when you flash ROMs. So, you still have the 10.6.1.27.5 bootloader installed on your tablet. When you run the guide, the TWRP you have by scanno will be overwritten and you will have to flash it again at the end once you have made the backups.
cmendonc2 said:
No, the bootloader does not change when you flash ROMs. So, you still have the 10.6.1.27.5 bootloader installed on your tablet. When you run the guide, the TWRP you have by scanno will be overwritten and you will have to flash it again at the end once you have made the backups.
Click to expand...
Click to collapse
Would this method work for 10.6.1.14.10? Because I see that this is the latest one and I can't get above that version at this time. Not even on the official site. (TF700T)
aminpro715 said:
Would this method work for 10.6.1.14.10? Because I see that this is the latest one and I can't get above that version at this time. Not even on the official site. (TF700T)
Click to expand...
Click to collapse
Well I'm not experienced with tf700t bootloaders, but it says that it is compatible with bootloader version 10.6.1.14.4. That may be the same as 10.6.1.14.10 but you will have to check in the tf700 forum.
Does not work for me in step 4!
hello
I have followed your tutorial on my Asus TF300T Android 4.2.1 build 10.6.1.27.5.
I installed ADB Fastboot, placed flatline_device.img file in the ADB folder.
When I get to step 4 the fastboot devices command displays the serial number of my tablet but the command to flash the image file does nothing !...
My question is: Should the tablet be rooted for this manipulation? or it could be something else?
Thank you for your help
Hi, I am a happy owner of the HP Slate 7 Extreme which is basically the same device as you guys are using.I am still on the 4.2 Jelly bean since HP are not pushing over the air updates with our devices.I want to use the script from the development forum "[Script] [Utility] Nvidia Tegra Note 7 Kitkat Unlock BL, Restore, Recovery, & Root", I want to know if anyone has tried to use it with the Slate Extreme or if it simply should work on the Jelly Bean aswell. Thanks guys.
still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
mofared said:
still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
Click to expand...
Click to collapse
What about the 4.3+ ?
crazyhacker202 said:
What about the 4.3+ ?
Click to expand...
Click to collapse
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later
mofared said:
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later
Click to expand...
Click to collapse
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
There was an individual who has received the 4.4.2 update from HP on his Slate Extreme over at the HP forums. I believe he stated he received 20 units donated directly from HP and was wondering why only 1 of them received the update. I believe the reason stated is that he most likely received a non-retail unit by accident. Not sure if he ever dumped the ROM or even knows how. I don't know either otherwise I'd try to contact him to get him to do so.
Re-write recovery partition?
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2
Belmichel said:
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2
Click to expand...
Click to collapse
See my HP Slate 7 Extreme Root post: http://forum.xda-developers.com/showthread.php?t=2850893
What am I supposed to open updater-script with?
---------- Post added at 03:47 AM ---------- Previous post was at 03:31 AM ----------
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
---------- Post added at 04:25 AM ---------- Previous post was at 03:47 AM ----------
I downloaded a script editor and deleted the first three lines of updater script but it still fails to flash.
Finally success!
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I have the 4450 extreme and one the things that was a little different- is that I had put the update zip on the sd card prior and it did the update on its own... WEIRD but acceptable! rooted and on 4.4.2- thanks man!
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot (previously this): This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk (Previously this): The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip (previously this): A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt (previously this): A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
It Worked! But...
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
I was able to unlock my bootloader using the above method and it worked. My s7e rebooted and everything was working normally. I loaded the bootloader again to go in and do a cache wipe and my 3 year old bumped into me as I was holding down the volume+ and power buttons. Now I'm stuck in ADX mode (black screen but recognized by my pc, have tried connecting to charger, volume+ and power, volume - and power, nothing works) . I've read that Advent has released adx files for the Vega Note 7 and you can use Tegra Note 7 Super Tools to restore the Nvidia Note 7. I'm wondering if I can use the update.zip file and the nvflash files from Nvidia to restore my tablet from ADX mode.
Any suggestions?
Mike-S, Thanks for the in depth how-to. I tried to sell my Extreme 4450 and the guy that I sold it to said when he received it was in boot loop. I got it back and it is indeed the one I sent him, however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling. I almost seems like the recovery was wiped... I can get to uploading from SD and have tried using your info to accomplish with no success. Any suggestions? I hate to smash it or try and sell if I can fix it.
Thank you in advance for anyone's help
som1special2 said:
however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling.
Click to expand...
Click to collapse
Damn, I'm sorry to say that I'm unsure if i'll be able to help much or at all. All i can suggest is look and see if there is any pre-boot subsystem that connects to your pc via usb, similar to the mediatek "preboot mt65xx" which can sort of provide a last gasp chance of recovery.
help with ROM
Hi there,
Need desperate help. I followed the instructions here but ended up with no OS in the s7e. I kept on trying to install a signed ROM via ADB, it reaches 100% senidng but always failed inside TWRP. Not succesful even with CWM. I even tried installing from SD card but no success. Please help, thank you.
Anyone still around here?
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ
MGrad92 said:
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ
Click to expand...
Click to collapse
Get your device drivers right (try androidsdk if it's still not getting recognised) and fastboot the stock system images (fastboot is not root dependent). By the way why were you trying those weird rooting methods ??? Just flash supersu from cwm/twrp and be done with it.
Thanks ... I'll try androidsdk. I actually am a root n00b and so I was trying to figure out the simplest way to go. I guess I guessed wrong! But of course before I can get that working I need the right drivers ... So I'll try that first. I was thinking the drivers were OK since my PC recognized the S7E when Android loaded (before it crashed to the white screen).
Couldn't get androidsdk to work
Hello again... I never could get androidsdk to work. My computer never recognized the tablet to be able to fastboot. *sigh* As much as I hate to give up, I don't know what else to do.... I might try another PC?
Looking for update.zip for S7E
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
Hey Mike, you wouldn't still happen to have that signed update.zip since you've don't have it on Dropbox anymore?
The aim of this thread is to make an easy guide to flashing stock firmware. Owners of previous nexus devices already know all this stuff, this thread is aimed at making the process as simple as possible for new users. This will work regardless of what modifications you've done to your device. Remember to backup all your important data and do this with the knowledge that all flashing activity carries some risk.
Download
Factory image here
(for windows users) Minimal adb & fastboot
(for mac users) adb & fastboot for mac
Follow the instructions to install adb on your computer.
Prepare your tablet
Enable developer options in settings > about tablet and tapping build number 7 times
Open developer options and enable usb debugging. (If you haven't unlocked your bootloader yet, tick enable oem unlock)
Extract images
Place the downloaded factory image inside your adb folder and extract with 7zip.
A new folder will be there called something like volantis-lrx21. Open and extract "image-xxxxx-zip" to your adb folder. We are interested in these files:
bootloader-flounder-xxxxxx.img
boot.img
recovery.img
cache.img
system.img
vendor.img
Place these files directly into your adb folder.
# I recommend renaming the 'bootloader-flounder-xxxxxx.img' to just 'bootloader.img' to make it easier to type.
Now that everythings set up, we can start flashing
Plug in your device. Open the adb folder, hold shift and right click and select open command window here
(if your having driver issues try using Pdanet)
Run these commands one at a time
Code:
adb devices
adb reboot bootloader
if you haven't unlocked the bootloader yet run
Code:
fastboot oem unlock
and follow the instructions using the volume keys to scroll through the menu. This procedure will wipe all data.
Run the following commands one at a time
Code:
fastboot flash bootloader bootloader-flounder-xxxxxxx.img
[B] [I](replace 'bootloader-flounder-xxxxx.img' with full name of bootloader image[/I])[/B]
fastboot reboot-bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
(OPTIONAL) At this stage you can relock the bootloader if you want by running the command
Code:
fastboot oem lock
finally reboot the device by running
Code:
fastboot reboot
Thats it. Enjoy your tablet in factory condition
Great. Is it possible to make a batch file to run all the commands at once?
albsat said:
Great. Is it possible to make a batch file to run all the commands at once?
Click to expand...
Click to collapse
There is already a flash all batch script that comes with the firmware files but I've noticed that some people have problems with it so I decided not to include it. It should work fine most of the time.
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Cool, thanks for the information.
Thanks for creating this! Will come in handy. Saving this for later
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
scotty1223 said:
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Click to expand...
Click to collapse
I indeed tried this as a last chance hoping it would bypass bootloader lock protection. It didn't work since I think the factory image is not signed by HTC as RUU are . It also lead to a fastboot crash. Now sending my nexus 9 for RMA
Sent from my HTC One using XDA Free mobile app
remedya said:
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
Click to expand...
Click to collapse
Same here. The manual flash method worked very well. Here's hoping that Google doesn't muck 5.1
cant flash stock rom
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
Art Vanderlay said:
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
Click to expand...
Click to collapse
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
cam30era said:
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
Click to expand...
Click to collapse
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
doitright said:
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
Click to expand...
Click to collapse
I agree.
I also used Linux but I executed the commands individually rather than using the script. It worked.
remedya said:
I also used Linux but I executed the commands individually rather than using the script. It worked.
Click to expand...
Click to collapse
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
nyasha1935 said:
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
Click to expand...
Click to collapse
Update your Android SDK.
These instructions also worked with 5.1.1
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
maxtcee said:
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
Click to expand...
Click to collapse
Are you writing the full name and file path for the bootloader img?