Related
*note this thread started out to post some general findings, and it has turned into a tutorial on fastboot, scroll through the first few posts to understand more if this first post seems confusing*
So in the past i decided to play with some sense ROMs that requires the Desire Z Hboot. last time i did this i flashed the Virtuous Team's PC10IMG.ZIP through Hboot to do this.
Of course I then had to reflash my radio and recovery and ROM of choice. Later I switched back to my G2 Hboot and again flashed radio, recovery and ROM of choice.
Well why do we have to do all these steps? For fun I decided to look around and see if i could just flash the SPL through fastboot and couldn't find an answer, so i asked a friend and got this response:
I'm not sure if you can flash the Hboot through fastboot, I don't know if anyone has tried it before.
I know the PC10IMG will work, so fastboot should as well, but can't guarantee it.
Though I would recommend removing that radio from the PC10IMG before flashing it, as it does throw up issues later on if you ever want to flash a stock PC10IMG.
Click to expand...
Click to collapse
Well it works just fine, download the DZ Hboot in the PC10IMG.ZIP format from anywhere you want (its all over XDA) and then extracted all from the .zip.
boot your phone into fastboot and open CMD into the folder the Hboot was extracted to (if you haven't edited the path for fastboot make sure fastboot.exe is in the same folder as the Hboot) in CMD type
Code:
fastboot devices
as long as you see your phone listed here proceed (displayed as the serial #)
Code:
fastboot flash hboot hboot_7230_0.82.0000_100902.nb0
You're done! Well almost...
Code:
fastboot reboot-bootloader
now your phone should say
HBOOT-0.84.2000 (PC1010000)
and you notice your radio hasn't changed
now boot into recovery, you'll noticed it is also still intact, well mostly you should see something like this:
ATTN: recovery is in safe mode
this is because the following partition
is not accessible: "system"
Please enter the wipe menu and format system!
If you changed Hboot you should choose to
format all partitions (except SD card)
Click to expand...
Click to collapse
so of course go ahead and do this
you probably wont be able to boot normally as your partitions have now changed so flash a ROM now via recovery, reboot and your golden
*Hope this helps someone... HAPPY FLASHING!
EDIT:
Well I have seen this question a lot lately (or at least similar questions) so I decided to clarify some things here and TO ADD A LINK
this will download the DZ Hboot from the cyanogen wiki (this is only the Hboot, not a shipped ROM)
You will be downloading a .zip format, so extract the image from here
the image will be named
hboot-eng.img
Click to expand...
Click to collapse
(in windows file extension may be hidden, take note that is important)
so when flashing via fastboot make sure if you use this to type
Code:
fastboot flash hboot hboot-eng.img
again you can name the image what you want so long as in your command you specify the file name
eg: i name the image dzhboot.84.img i would then enter the command
Code:
fastboot flash hboot dzhboot.84.img
also note these same steps can be used to flash the G2 Hboot found HERE:
just need to change the name of the image or what your command is
If any of the above links are down i have uploaded both Hboots to MY DROPBOX
*Know what you are doing* I have made a couple different PC10IMG.zip's to be flashed through your SPL. they contain the .19 radio, the rcdata for that, 4ext touch recovery v1.0.0.5RC6, and an engineering HBoot for either the G2 or the DZ. I do not recommend this method as manually flashing will teach you what you are doing and can help ensure there are no issues. If you are true s-off but do not have an engineering SPL then you may use one of these: POST 30 IN THIS THREAD
Click to expand...
Click to collapse
*If you have more questions feel free to ask here as i am not the best with tutorials
Good to hear that your experiment went out well without incidents.
Sent from my HTC Vision using xda premium
How Do You Use Fastboot?
I should learn to stop assuming everything... i understand that not everyone has used fastboot or adb before and therefore may not know how, but on the same note neither is rocket science and even a novice can figure this out quickly. Instead of teaching people on a case by case basis i decide to add some helpful tips here, i will attempt to be through without being too boring.
what is fastboot?
fastboot is a protocol designed to flash unsigned partitions to android phones directly into the phones flash memory. if you are familiar with adb think of it in the same way. if youre not, just understand it is a tool designed to help flash images such as recoveries, bootloaders, kernels, etc. to your android phone. for the most part you can not use fastboot unless you are rooted and have an engineering spl (hboot/bootloader) this is not a tutorial to root your phone so i will not explain this. but everything you need to know is here
how do i get fastboot?
fastboot.exe can be downloaded to your computer from googles sdk found
HERE download the proper package depending on what system you are using.
also
you will need the proper DRIVERS unless you already have them then you can skip this
ok i got it, whats next?
after you downloaded the sdk package to your pc (for the purpose of this tutorial i will assume you are running window 7 but most everything is the same in other windows os, linux, and apple) it should be downloaded to your pc to somewhere like
C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
of course put it where youd like, just know where fastboot.exe lies
although not necessary, but to make it easier i really suggest doing these steps:
left click the windows (start) button > right click on computer > choose properties > go to advanced system settings > advanced tab > environmental variables > in the first box (user variables for _____) click new > name it
adb
Click to expand...
Click to collapse
> the value is the path from earlier
C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
(yours may differ from this so double check it!) > in the second box (system variables) find a variable named
path
Click to expand...
Click to collapse
if one dosent exist make one > double click on it > at the very end of the variable value add the same line as before but with a ; in front of it. like this:
;C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
alright click ok and you are done!
why did i just do all that?
well this allows you to open a command line from anywhere on your computer without changing directories to use fastboot. pretty much we told your pc that when you type
fastboot
Click to expand...
Click to collapse
or
adb
Click to expand...
Click to collapse
into a command lined, where to find it. as you learn how useful fastboot and adb are this will help a lot.
so i still dont know what to do or how to do it!
all right lets start simple, click the windows button and in the search field type
cmd
Click to expand...
Click to collapse
you will notice a window pop up that looks suspiciously like dos. View attachment 1386065here you will see a blinking cursor after your directory, lets try this type
Code:
fastboot
a whole bunch of probably unfamiliar stuff should now pop up (for the most part this is a list of commands that can be used in fastboot) if you get something like
fastboot is not recognized as internal or external command operable program or batch file
Click to expand...
Click to collapse
then we need to troubleshoot, but for now i will assume it worked.
now try typing
Code:
fastboot devices
and nothing will happen, why? because there isnt a device attached. make sure you have android debugging turned on in your phone, plug it into your computer and boot into fastboot mode. on the g2/desireZ hold volume down while powering on, if needed choose fastboot (not all phone do this the same way so if you dont know how, ask and i can help) again try typing
Code:
fastboot devices
this time you should have a list of attached devices, this is displayed as the serial number to each. being many commands will "do" things to your phone try typing
Code:
fastboot reboot
if your phone is now back and running your existing os, congratulations! you now at least have fastboot set up and working properly. now lets try a few things out and see why this can be so helpful!
do you want a new recovery? maybe 4ext?
being this is in the vision (g2/dz) forum many have clockwork recovery but have read about 4ext recovery, only they just arent sure how to get it on their mobile.
here is a quick tutorial on how to do just this, and in my opinion the easiest and the safest way.
First
download a version of 4ext recovery for the vision HERE this will be downloaded to your computer in a .zip, i suggest to put it in a folder named 4ext recovery inside whatever folder you have all your android downloads (roms, kernels, etc)
now extract the image from the .zip you will notice it has the image and the md5sum, make sure it is
d92610abb990a78c3721d9e47e60fc13
Click to expand...
Click to collapse
if not DO NOT FLASH IT, unlike flashing a bad rom, it can be very harmful to flash bad firmware to your phone, although unlikely if flashed through fastboot, it could leave you without a working recovery or even worse, hard brick your phone. im not giving the scary warning that you see in most roms as what i am telling you is safe, im just reminding you to understand what you are doing.
i get it, im ready for 4ext!
all right, lets start by finding the folder the extracted recovery is in. hold shift > right click in that folder > choose open command window here. now you will see your command line with the directory already set to this folder. at this point, if you havent already, boot your phone into fastboot mode and have it plugged in via usb. now type
Code:
fastboot devices
so long as you see your serial # go on (if you dont fix the path in environmental variables explained in the last post or just make sure fastboot.exe is in the same folder as the recovery.img)
now lets continue, type
Code:
fastboot erase recovery
it is best to start fresh so even though you can skip this command i recommend it. lets move on:
Code:
fastboot flash recovery recovery.img
the recovery image you extracted from the .zip should have been named recovery the above command should be altered if you changed the name (notice: if using windows it may appear the image is only named recovery, that would be because windows is hiding the file extension, the true file name would then be recovery.img)
all right, if it said complete your done! seriously its that easy! now type
Code:
fastboot reboot-bootloader
from here you can boot into your new recovery and play around. if coming from clockwork to 4ext on the vision for the first time you will be wowed! this has so many more features, is far more stable, and is truly worth donating to madmaxx82 for all his hard work.
if you like this recovery and want the latest and or to donate (buying the app for 2bucks in the market is a very reasonable donation and gives you a great app too!) go HERE and you will also find tips on how to use the recovery as well as links to flash a free version of his .apk or a link to download the paid. even if you cant right now, i highly suggest doing so in the future as developers may give their hard work to us for free on xda but we should understand that just because something is free doesnt mean we shouldnt pay for it.
of course this method can be used for flashing different recoveries on different phones as well. just understand what you are doing and be sure to flash the proper recovery to the proper phone.
happy flashing!
So you need to flash a new radio...
turns out this doesnt even occur to many people as an option, that is to flash a different radio to their mobile. true, when i got my g1 this was the first time i realized this was an option, prior to that i had only dumbphones and did not even know too much how cellular phones in general worked. so to clarify i am not speaking about the fm radio in your car rather flashing the proper firmware to control your cellular radio.
Everyone keeps saying the .19 radio is the best, is that true?
well yes and no, what is true for them may not be true for you. it does appear most people using a g2 or a dz in this forum find the 12.62.60.27_26.13.04.19 radio the best in terms of reception and battery life. but it is good to know that this still has to be determined on a case by case basis. what is amazing for some may be lackluster for others.
so if you feel you need to try a new one the .19 is a good place to start, but you may need to test others and usually you will need to test it for a day or so to know how good it is in comparison. usually it is better not to estimate but rather compare using apps such as Speed Test and Network Signal Info and Battery Monitor etc. just use what works for you
So i can flash a new radio via fastboot?
Yes, and its my preferred method of doing so. its fast, easy and safe. heres how:
download the .19 radio and store it on your computer in a place you can find easy.
*checking the md5sum is a good idea before flashing a rom, and a must when flashing firmware:
6CB937DD21DC2A42DEBB66190F38370F
Click to expand...
Click to collapse
turn on debugging on your phone, put in fastboot mode and plugged into computer via usb. now open cmd in the same folder as fastboot.exe
now in cmd type:
Code:
fastboot flash radio radio.img
if you downloaded multiple radios then i suggest renaming them, in this case you may need to change radio.img to something like radio19.img or whatever you named it
now again in cmd type:
Code:
fastboot reboot-bootloader
you are now in hboot and can verify it worked, congratulations! it was that easy!
for a whole list of radios for the vision go HERE there will be two forms of each radio to download, make sure you download the images only if you want to flash through fastboot. you will also find more info about the radios there.
if you are interested in more then take look HERE FOR ICS and HERE FOR GINGERBREAD edkeys has done great work and its worth at least reading up on it. again if it aint broke dont fix it, but i will say it worked well for me.
*any questions and comments are appreciated, sometimes i go into too much detail and sometimes too little so feel free to ask and/or comment
Just a thing you might want to consider adding, I generally always 'fastboot erase recovery' before flashing a new recovery. I don't think it makes much difference, but it can't hurt.
-Nipqer
cleanleness is next to...
thanks, i do as well and just overlooked/skipped it in the tutorial
although im sure it wouldnt make much of a difference if someone just flashed a new recovery over the old, but it is always best to erase as this will lessen the chance of a bad flash due to residual effects from the previous recovery. this goes with most everything in flash memory as so many peoples problems with a newly flashed rom are simply due to them not completely wiping the phone clean.
so when flashing a rom i am a firm believer in performing
Code:
fastboot -w
prior to the flash, as it is cleaner than wiping from recovery and even cleaner than most superwipe scripts. of course not every time i flash a rom or restore a backup im next to a computer. in this situation i do recommend to wipe from recovery and then flash SuperWipeG2+ext4 from recovery prior to flashing the rom or restoring a backup. of course most of the time when people flash new roms they are at a computer, in this case i recommend these quick steps prior to the flash:
put phone in fastboot mode and attach to computer
Code:
fastboot devices
just to make sure we are ready (looking for serial # here)
Code:
fastboot erase system -w
fastboot erase boot
so fresh and so clean
Code:
fastboot reboot-bootloader
from here just reboot to recovery and flash the new rom there.
*note - you can flash a rom to your phone through fastboot but i will put that in the next tutorial*
flashing a rom with fastboot
As promised... here you go!
now of course you can flash a rom through recovery, but why not have another way? maybe your recovery partition on your phone is corrupt? maybe you just want to say "i learned something new!" whatever your reason here are the simple steps:
To start:
we need to download the rom of choice to your computer. once complete find the folder that rom is in and open cmd to that directory (quickest way just hold shift and right click within that folder > open command window here) of course make sure your phone is plugged into computer and in fastboot mode.
Lets see how quick and easy this really is...
in the command line type:
Code:
fastboot devices
see your serial number and we know all is good
now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
*its been a little while since i did this but the phone might automatically reboot after flash so no need to run the reboot command
as your phone boots into the new rom, pat yourself on the back...
can i restore a nandroid through fastboot?
of course! (why you would need to is irrelevant)
and here are the simple steps how:
well first you need to make a nandroid back up (unfortunately fastboot cant make a nandroid for you :crying: ) put it some where on your computer. personally i only keep maybe 3 or so nandroids on my phones sd card as why waste space. i do however keep almost all my nandroids on my computer separated into diffrent folders for different phones. so my path to a nandroid backup would be something like:
android/htcg2/nandroids/<nameofnandroid>
Click to expand...
Click to collapse
and the obvious stuff:
have phone plugged into pc via usb and in fastboot mode, open cmd and change directories to that folder where your nandroid is in (or again just hold shift and right click > open command window here)
once we are in:
in cmd type:
Code:
fastboot devices
all is good when serial number is displayed, now type:
Code:
fastboot erase system -w
fastboot erase boot
*this isnt 100% neccessary but im a firm believer in wiping before any flash, even a backup
Code:
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
(of course change the image names if needed)
and you did it! :good: now you are almost a pro at using fastboot!
keep playing around, you'll get the hang of it and will quickly see that this is one of the best tools in the android sdk. it makes things much faster and easier and in many cases safer than the alternatives. any questions... feel free to ask!
Happy Flashing!
*as nipqer was so kind to point out, most newer recoveries archive nandroid backups in tar format by defult. this will not work with fastboot unfortunately.
for the restoring a nandroid, you gotta make sure the backups are done in yaffs2 format don't you? fastboot doesn't work with tar's as far as I know.
Clockworkmod 3.x and lower have the yaffs2 as default, but at least 5.x (and 4ext) use tar as default, but I know 4ext has a setting so you can change it.
-Nipqer
I believe you are correct. I haven't restored a nandroid via fastboot since the g1 days but that sounds about right. looking at my g2 nandroids some are in yaffs2 and some not, ill look into it and post a better explanation.
and it looks like every nandroid i made since i flashed 4ext recovery is saving everything as tars (except the boot and recover image) when i first rooted and used clockwork 3.x ? those backups were in yaffs2. it looks like one could change the settings in the 4ext app to change from tar archives to yaffs, but if all you are doing this for is to boot a backup from fastboot that is silly :silly:
so although it still is possible, it would not be worth the effort unless you were to do it for sheer fun. or if you still have an old android device lying around and want to try it out.
also if you updated to a new recovery and your old one used yaffs2 and the new one works with tar (i think twrp uses a modified tar/ext4 image called .win?) well you cant flash those old backups in your new recovery, but you can still flash them from fastboot. and then later do a nandroid with your new recovery in the proper format. so with this i guess there still may be a reason for someone to flash a nandroid via fastboot.
thanks for the heads up nipqer! id hate to make someone think they did something wrong when they didnt!
Sent from my HTC Vision using xda premium
Some other uses...
What else can i do with fastboot?
ADB has more (but different) capabilities than fastboot, but fastboot can still be handy. Heres an example: you went through the rooting process on your Vision a while back and cant recall if you sim unlocked it or if you gained super CID. well simple, lets:
open cmd, navagate to fastboot (no other folder/files necessary here) and type:
Code:
fastboot devices
and you should see your serial number, good
Code:
fastboot getvar cid
if you are sim unlocked and (superCID) then the output should read
cid: 11111111
Click to expand...
Click to collapse
if not, and you want it, then you will have to downgrade and rerun gfree etc. or you could beg tmobile for an unlock code or you can buy one from elsewhere. any way you go about it, this will tell you if it worked.
*super CID and sim unlock are not the same thing, i am just assuming if you have super CID then you also sim unlocked. (super CID lets you flash different software and firmware to your phone that initially may be locked to a specific carrier, sim unlocked allows you to use any GSM sim card no matter the carrier. although some require specific radio bands to fully work)
And more hypotheticals?
well to get your model id you would do the same only change the command to
Code:
fastboot getvar mid
out put will be something in the lines of
mid: PC1010000
Click to expand...
Click to collapse
there are reasons to change/fake your model id, maybe for apps in the market or to tweak a kernel... im not a developer so the purposes may be many or few on this.
Get a bunch of info quick:
Code:
fastboot getvar all
this give a slue of info such as radio, bootloader, imei, cid, secure flag (on/off) and more!
Speaking of kernels...
lets say you are a developer and have worked on a new kernel for your device, a quick and easy way to test it out may be to fastboot load the kernel:
Code:
fastboot erase boot
fastboot boot kernel ramdisk
*as always replace file/image names accordingly
after testing is completed:
Code:
fastboot flash:raw boot kernel ramdisk
fastboot reboot
test it out and see how things go! good luck!
as always, if you have questions or comments feel free to leave them here!
Happy Flashing!
*im thinking about adding a simple tutorial about ADB if anyone is interested let me know
If you flash from the g2 to the dz hboot thingie and have to reformat /system does it mean time to flash a new rom? And can you reflash a ext backup back since the partition info is different?
Yeah after updating to the dzhboot you will need to reformat, this will wipe your current Rom. But most often you should have no issue taking your nanadroid made while on the g2 hboot and restoring them to you phone with the new system partitions you get with the dzhboot.
As always make a backup of current set up via recovery, follow the steps listed in the first post and then flash either a new Rom or your nandroid. Also make sure to check the md5sums.
If you need any further help feel free to ask
Happy flashing!
Sent from my Desire Z using xda premium
Umm wow that was like super easy. Thanks for the guide. Going to have to read some about the radios and see about doing that next.....
no problem, many seem to either be afraid of using adb or fastboot mostly because they dont understand it and see other options to do the things they want (recovery)
but in reality both are quite easy to get used to and it really helps with the understanding of what you are doing. so im glad this guide is helping people not just get their phone the way they like it but also help understand the process.
as for the radio its just as simple as flashing the bootloader. mind you any time you flash firmware to your phone there is potential harm (unlike with flashing roms) so its not a great idea to just flash away for no reason. but fastboot is a very safe way of flashing firmware and as long as you check md5sums your good. also make sure never to do a battery pull during a flash or if something goes wrong just dont reboot until it is fixed, knowing these few things will ensure safe flashing through fastboot and help understand why firmware shouldnt be flashed through recovery.
so if you feel you could get better reception and/or battery life with a new radio by all means go for it! i for one found the .19 radio to be the best for me along with edkeys package. it seems many feel the same but the only way to know what works for you is to try it!
Happy Flashing!
I do agree it's not that hard once you have a clue. One thing I would say you may want to be a bit clearer on (at least me and my braindead self took a while to grasp it) is that you need to be in the bootloader to use the fastboot command. I am still learning about stuff and with the crazy hours I work and with 3 kids sometimes it takes me a while to get stuff done because I want to understand it before I do it. Although with your guide once I had time to sit down and do it it was like 15 mins tops and all was done. I need to read about the radio and edkeys(whatever that is...) and see about doing it. I think I have the .15 radio and it works ok although if I understand correctly wifi calling only works with the .19 radio and who knows it may fix my mms issues when I try ics roms.....
Thanks for the suggestion, ill add that in there, I always miss some little things! Edkeys is a member here on xda who did a lot of research on radios and WiFi calling, I linked a couple of his pages in my post on flashing the radio, I definitely suggest reading up on his work as he will explain it better than I. Also note some users have issue using WiFi calling and an old sim card, if you go to a local T-Mobile outlet they'll give you a free updated sim. I think the latest is 9177? Not sure but its written on the card.
Thanks for the suggestion!
Sent from my Desire Z using xda premium
demkantor said:
Thanks for the suggestion, ill add that in there, I always miss some little things! Edkeys is a member here on xda who did a lot of research on radios and WiFi calling, I linked a couple of his pages in my post on flashing the radio, I definitely suggest reading up on his work as he will explain it better than I. Also note some users have issue using WiFi calling and an old sim card, if you go to a local T-Mobile outlet they'll give you a free updated sim. I think the latest is 9177? Not sure but its written on the card.
Thanks for the suggestion!
Sent from my Desire Z using xda premium
Click to expand...
Click to collapse
C:\Users\Pesho\Desktop\recovery>fastboot devices
SH**SRT***** fastboot
C:\Users\Pesho\Desktop\recovery>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.001s
C:\Users\Pesho\Desktop\recovery>fastboot reboot
rebooting...
finished. total time: 0.280s
C:\Users\Pesho\Desktop\recovery>
Click to expand...
Click to collapse
USB debugging is on.
I'm running Mimicry 1.5
root access is setted to apps and adb in the developer options in settings
what is your current bootloader information? can you write down the first few lines on the top of the screen?
Sent from my HTC Vision using xda premium
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?
This guide will help you unlock your bootloader, flash a factory image, and return you to a stock device. It is wriiten assuming you have a windows PC (MAC users, see post 2). This can be helpful if you need to RMA your device or if you are getting erratic behavior or messed something up.
Tools and Files You’ll Need
If you don’t have adb and fastboot installed on your PC go here for a quick install of the necessary files, thanks to @Snoop05, http://forum.xda-developers.com/showthread.php?t=2588979
For MAC users go here. http://forum.xda-developers.com/showthread.php?p=32305619
For Linux users, http://forum.xda-developers.com/showthread.php?p=10746225
For the factory image go here, https://developers.google.com/android/nexus/images You’ll download a .tgz file. Use winrar or 7-zip to extract the file to its own directory and remember where that directory is. Inside is another zip file, extract that too. You’ll need those image files if you use the long method to install the factory image. It’s also good to know where they are as they come in handy as you get more familiar with fastboot and what you can do with it.
How To Unlock the Bootloader
If you don’t have developer options enabled on your device go to settings, about device and tap on the build number 7 times.
In settings, developer options enable oem unlock
Now you get to use fastboot! Boot you device into the bootloader, vol up + power with your device shut off. Once booted into the bootloader connect it to your PC with the usb cable and open a command window on your PC. Once connected type the following command in the cmd window:
fastboot devices (Your device serial number should show up and this will ensure fastboot is working properly)
Then type:
fastboot oem unlock (This will unlock the bootloader and you’re now good to go)
NOTE, UNLOCKING THE BOOTLOADER DOES WIPE YOUR DEVICE SO BACKUP OFF YOUR DEVICE FIRST
How To Flash the Factory Image, SHORT METHOD
Open a command window on your PC in the same directory as you extracted the factory image. In that directory shift, right click in an open area and use “Open a command window here”
Boot your device into the bootloader and connect it to your PC. Then simply double click on the flash-all batch file. Note that there are batch files in there that will work for Windows as well as Linux machines
Let the batch file run and when it’s done you’ll be back to stock.
NOTE THAT FLASHING BY THIS METHOD DOES WIPE YOUR DEVICE SO MAKE SURE YOU BACKUP OFF YOUR DEVICE FIRST.
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img
Congratulations, you’ve now flashed a factory image and learned how to use fastboot!
For MAC users, proceed each fastboot command with a ./ e.g. ./fastboot flash boot boot.img
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
GedBlake said:
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks @GedBlake. I would have responded sooner but I had to get home and check my tablet. Actually both work, vol up + power and vol down + power.
Sent from my Nexus 9 using XDA Free mobile app
But.... Toolkit so easy?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639!
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought.
Edit : That ^^^^ was a hint to other members to get your guides, tutorials, info threads, FAQ... Etc... Going..... This is a Nexus section after all. :silly:
Darth said:
But.... Toolkit so easy? ?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639! ?
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought. ?
Click to expand...
Click to collapse
I'll keep an eye it and do a roll up when the need arises
Sent from my Nexus 9 using XDA Free mobile app
cant flash system.img
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
nyasha1935 said:
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
Click to expand...
Click to collapse
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
cam30era said:
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
Click to expand...
Click to collapse
Ok thanks gonna try on windows, im a noob on linux
nyasha1935 said:
Ok thanks gonna try on windows, im a noob on linux
Click to expand...
Click to collapse
You'll be sorry.....
cam30era said:
You'll be sorry.....
Click to expand...
Click to collapse
Ok back to linux, how do I update android SDK
nyasha1935 said:
Ok back to linux, how do I update android SDK
Click to expand...
Click to collapse
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Is it possible to flash a factory image using a custom recovery like TWRP?
Sent from my Nexus 9 using Tapatalk
iamroddo said:
Is it possible to flash a factory image using a custom recovery like TWRP?
Click to expand...
Click to collapse
Is it possible to extract the .img from the volantis-lmy47x-factory-3efdc8d4.tgz from https://developers.google.com/android/nexus/images and flash them individually with TWRP (with the exception of recovery.img, which I guess would over-write TWRP)? Can it this be done directly from 5.0.1 or would I need to first upgrade to 5.02?
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Leoncino said:
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Click to expand...
Click to collapse
No need top apologize. You're English if fine.
There's a lot of discussion and lack of agreement about what affects the warranty on the Nexus 9. HTC says that even unlocking the bootloader "may void the warranty".
My advice would be to do what you want to it, but make sure you understand what you are doing. Ask a lot of questions before you do something you're unsure of.
Unlock your bootloader (if you haven't already). Do not relock bootloader if something goes wrong (this does not solve anything). With an unlocked bootloader, you can recover from almost any problem.
And you can flash the Google factory images anytime you want to return to stock.
I'm sorry there's not a clear answer to your question.
cam30era said:
No need top apologize. You're English if fine.
Click to expand...
Click to collapse
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Leoncino said:
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Click to expand...
Click to collapse
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
cam30era said:
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
Click to expand...
Click to collapse
And what happens if i lock again my bootloader, will i restore the warranty?
Leoncino said:
And what happens if i lock again my bootloader, will i restore the warranty?
Click to expand...
Click to collapse
That's a good question, without a clear answer (unfortunately).
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
Theres a hardware method to boot into the bootloader, this i think you can test, just to see if you can at least get into bootloader.....nothing more
Details in the official nvidia link
http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
There's a thread here on the "questions" thread with users reporting that the timing of the hardware method can be a pain in the you know where.............might be worth looking into that thread for their experiences in booting the bootloader using the hardware method
Disclaimer:If your brave enough to risk a brick, read on
I suspect this might be the 2.1 stock/twrp issue........current twrp, or current stock dont play nice
Its a good sign that SOMETHINGS loading, rather then NOTHING booting, but dont know if theirs a solution
My analysis of the situation, of what little i know, the -w (wipe) command was expecting a stock recovery but instead got twrp, which is why your in this situation.........maybe, i stress maybe, if you could reflash stock again, you might be able to boot into android stock again and try full android again, leaving out twrp, until a twrp fix is found
Edit
Saying that, if the bootloader is, as i suspect, now using twrp to flash things, then you might be boned....... im no expert on bootloaders, stock "recoveries" and how they work, so i might be wrong on that
Reports around here say that 1.3 stock firmware is the recommended back to stock firmware, apparently, flashing any other firmware versions, bring their own issues.............
From 1.3 stock, use nvidias official OTA to upgrade from 1.3 stock, to 2.1 stock, then try 2.1 full android again...........note, i dont think you can skip firmwares i.e. you have to upgrade to 1.4, then to 2.0, then to 2.1, alot of downloading.......the OTA does'nt give you any other choice
Before doing anything that ive suggested, wait till someone with more experience to come along........i dont want to be responsible for you fully bricking your shield..........just wanna give you an idea of what i think has happened
If worse comes to worse, if you have warrenty, get a replacement
Gd luck........remember, this is an analysis of your predicament of what i THINK might of happened, and what steps, i likely might of entertained.......after looking into it more thouroughly, knowing that i could get a replacement if it went downhill.........so your mileage might vary
Edits
Crappy grammer, further musings, clarifications
Thanks.[/QUOTE]
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
I had something similar about... shield goes booting in recovery and trying delete some cache and keeps repeat and repeat
Hardware boot in fastboot / bootloader mode
Accessing Bootloader via Hardware
Unplug power from the Shield Android TV. *
Wait a few seconds.
Hold down the power button.
Plug in power
Count to three
Release the power button
You should see the bootloader screen.
If you hold it down too long or not long enough, it simply doesn’t work.
Restore Shield Android TV to Stock
P.s. Personally me I followed this instructions and kind of magically got it in bootloader mode. First done by instruction and then just gave up and pressed randomly and fastboot screen appear. Thanks God I had to done only once, if I would do again I wouldn't had patients
Good luck with this, hope you will get sorted
Here will be link about where I got instructions about hardware boot
http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
Sent from my Nokia 3310 using free xda app
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
EDIT with joy : I followed all the steps using that rom and it seems everything worked. I reconfiguring the box now. Thanks for help.
basically the procedure I intend to follow is this part (please confirm it's ok):
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
DTB file name to use for flashing for your product(see below):
P.s. maybe Since past fastboot commands failed and I only flashed system from zulu99 I could skip the 'fastboot flash boot boot.img' command so if it fails again I still can attempt the fastboot process again?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
puppinoo said:
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
Click to expand...
Click to collapse
You are on the right way with those links
P.s. You can do manual one by one entering or paste and copy those commands or (I'm doing) drag and drop file "flash-all.bat" on cmd previous opened there where you have abd/fastboot etc files and extracted RIGHT FIRMWARE (like shift and right click mouse "open command prompt here"
And after this all sit down and relax
Anyway you are on the right way.
P.s. Hope you download adb fastboot drivers somewhere from Internet !?!
Sent from my Nokia 3310 using free xda app
This is FINAL working method.
First off you must unlock bootloader, and install twrp.
instructions for unlock bootloader are in this thread
http://forum.xda-developers.com/r1-...mazon-root-t3490882/post69387472#post69387472
I made many cycles between 6.6 and 6.1 and found that this set of files was minimum needed to maintain stable device. I started with only the preloader, and that left the phone able to connect to spft but the preloader was o longer in the "trusted zone" so it would not load the second step of power on (lk). replaceing the lk with spft after that allowed to boot to the boot menu, but would not trust the next step(boot.img). But with the preloader and lk I was able to fastboot, so was able to oem unlock.. this was the first method I was going to suggest. After more trials I decided it better to foll back all the bin files that the update replaced and also the secret bin so no more need to oem unlock after the roll back.
I got so comfortable moving between preloaders and version I got careless. My carelessness allowed me to mix up secure preloader and bin files with custom non secure recovery files and without realizing it I rebooted like that. I was left in a secure environment that was panicking because the recovery was not properly signed. (a terminal soft-brick)
My point is once you roll back DO NOT go back to locked and DO NOT blame me if you forget and restore some backup that does that to you down the road.
I do recomend that you roll back though. Because with the roll back, you are almost certain not able to brick because you can always use spft to to fix things.
THIS WILL ROLL BACK BOOT LOADER AND ALLOWS SPFT .
THIS HAS ONLY BEEN RUN WITH TWRP.
But the fastboot mode can also flash preloader if prefered. Just remember you may also need to oem unlock again after. This has not and will not be tested by me.
ONCE YOU HAVE UNLOCKED BOOTLOADER AND INSTALLED TWRP, return here and download "after_bootloader_roll_back_5.tar" unpack the tar and run the .bat file. It will adb push the recovery image to you phone and then install it.
It will rewrite :
1. preloader
2. lk (little kernel)
3. boot img
4. seccfg.bin
5. frp (to make sure bootloader remains unlockable)
6. trustzone (goes into both TEE1 and TEE2
7. secro.bin
All done.
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
jhonjahegu said:
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
Click to expand...
Click to collapse
Sounds like you need to do oem unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot oem unlock"
6. If need to do oem unlock you will also need to "fastboot format userdata"
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
digihaven said:
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
Click to expand...
Click to collapse
If it is looping into twrp then you must do step 6 from above.
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
clownkitty said:
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
Click to expand...
Click to collapse
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
mrmazak said:
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
Click to expand...
Click to collapse
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
clownkitty said:
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
Click to expand...
Click to collapse
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
mrmazak said:
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
Click to expand...
Click to collapse
I didn't realize you had to load straight into recovery mode after flashing it, I got it to work now, thank you so much!
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
tuespazio said:
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
Click to expand...
Click to collapse
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
mrmazak said:
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
Click to expand...
Click to collapse
Hi, dont worry now is fixed i return to 6.1 and then flash full 6.5 firmware.
Data is now working fine .
Thanks for your Support
sorry, wrong thread
ncy1 said:
Hi guys, sorry to bother you with this
I was on 6.0 rooted and without ads, i just tried to update my phone using the v17 and settings on this thread, when i went to cellphone info on settings it said i was still on 6.0. Did i miss something or this a normal thing? Anyway, i went back to recovery mode, did a wipe and tried to flash the 7.4.2 rom but it sent me an error, now the phone won't boot and gets stuck on the blu loadscreen.
Click to expand...
Click to collapse
Don't get me wrong, I feel bad for you that your phone is in this situation, but that has nothing to do with the thread you are posting in.
This thread is for rolling back the preloader.
And all the oem and Amazon Roms are 6.0
To get help you should post in the thread you got the ROM from.
And include the error you got.
mrmazak said:
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Click to expand...
Click to collapse
I think I just want to try this method, since I want to convert it to OEM and still keep OTA updates anyway. I'm blanking though as to how I need to go about this.
I have adb installed, and I have access. I assume this requires a fastboot command, but I don't know which.
Jessooca said:
Mrmazak... does this work on a new out of the box blu r1 that came with the 6.6 August update already installed?
I'm trying to help a friend, I surprisingly can't get the bootloader unlocked, dirtycow continually failed.
He doesn't care about updates etc... just wanted to flash the no ads firmware onto a prime version blu r1 hd
Click to expand...
Click to collapse
To the best of my knowledge it was.
Last time someone told me they were having trouble, they ran the codes manually one by one instead of using the script, and it worked. Apparently they had trouble pushing the files from the batch file. I had similar trouble when I wrote the script, that is why there are 3 second pauses ,that seemed to fix it for me. I will change them to 10 seconds and see if it helps.
I will update here when I change it then you candownload again and try, or you can make the changes yourself and let the me know
OK i updated the one-click.bat . you can download it again to see if that help. Also you said dirty-cow keeps failing, please let me know the fail message and also the comments displayed during the first part of the script. the part that is pushing files.
Also I have not been able to get feedback on the one-click.sh for linux. I don't normally use linux and did not test the shell. If you are using that one maybe the fail is my poorly written .sh
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
danbcooper said:
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
Click to expand...
Click to collapse
"oem" is not supposed to be capitalized
i went back and edited that original post too.
mrmazak said:
"oem" is not supposed to be capitalized
i went back and edited that original post too.
Click to expand...
Click to collapse
Now I ran "fastboot oem unlock" and it says FAILED (remote: unknown command). Do you know why?
Never mind.. Tried again and worked! Thanks for everything!