Related
hmm I've been searching around a bit bit I couldn't find anything about fastboot for galaxy S (epic 4G).
Please let me know if its out there
Thanks
You mean the thing HTC has in their new Sense builds?
Frankly I don't understand if its only for HTC or a generic tool
but basically I wanted to use
$ fastboot flash boot boot.img
$ fastboot flash system system.img
Click to expand...
Click to collapse
fastboot commands which seems to be available for HTC devices.
My concern is if we have something similar for Galaxy S devices and specifically epic 4g
Thanks
Fastboot is an executable in your android tools platform whatever folder...it should be in same folder as adb. You push .img files from your computer to the phone by fastboot.
Fastboot is the same throughout android regardless of phone (for most part I reckon
Its the best and cleanest way to erase and flash your partitions.
Look in the stickies.
Yes I've known about fastboot terminal utility
However I read people referring to fastboot boot loader separately than recovery mode (CWM3) in phone itself.
I didn't try just going with it, as I wanted to confirm if I'm thinking something wrong here
Thanks
you are on the right track.
To make things worse -- fastboot is also a feature in Sense development settings -- it literally means "fast-boot" as in it boots faster than normal. People get confused over that as well.
everything go ok?
So it is safe to assume that Galaxy S doesn't have anything similar to fastboot?
I don't think so.
Sent From My Evo Killer!
Sorry I'm bit confused now
Can you please elaborate a bit more or even just a link with explanation would be good
If your talking about the speed the device boots up..we already have that from day one..takes me 15 seconds to boot...an Evo for example without HTC's fast boot takes like 2 minutes I hear :/
Thats good,
however I wanted a way to flash img files to my epic before making flashable zip and for that purpose I need support (on phone) from fastboot PC utility.
http://wiki.cyanogenmod.com/index.php?title=Fastboot
http://forum.xda-developers.com/showthread.php?t=532719
http://forum.xda-developers.com/showthread.php?t=517874
In that order...there are no better tutorials. Read away.
bier
First of all I have a 16gb n7 currently on 4.2.1 JOP40D. It's unlock/rooted on STOCK rom.
First off I have tried installing the OTA update and would get an error everytime.
Then I tried installing CWM and manually pushing the update nakasi update and it still threw an error:
Verifying current system..
assert failed: apply_patch_check ("/system/build.prop", 38f7593c2ff2fa85a147 etc...)
E: Error in /sdcard/0/6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
(status 7)
Installation abborted.
So from googling/searching that I have figured that there is something not "stock" about my build.prop. I had edited it to get rid of the NAV bar but after re-editing it back to stock, it would still throw the same error.
So first I tried reflashing 4.2.1 ... threw the same error
Now I'm trying to get the build prop out of the JOP40D update but when I look in the files it is called "build.prop.p" ... I'm not sure what that last .p is about? Also when opening it there are just about 2 lines of chinese characters... Soooo this is where I'm stuck... I need to know how to extract a proper build prop from 4.2.1 or I need someone to post a stock 4.2.1 build prop.. thanks..
edit: before people suggest I have tried redownloading both the JOP40D and JPQ39 files
edit2: I am on a mac so flashing to stock from fastboot / abd isn't really an option
The checksum performed requires the file to be exactly identical to the original.
No extra spaces, identical line termination schemes et cetera - identical byte-for-byte. That means including characters you can not see in an editor.
You can certainly copy the original to a folder side-by with your hand-edited version and run any checksum on the both of them to see if you got it right, but it is probably easier to just copy the original into place.
Simply put, the only reason that check continues to fail is because the file you have there is NOT identical to the original.
good luck
canadianrider said:
edit2: I am on a mac so flashing to stock from fastboot / abd isn't really an option
Click to expand...
Click to collapse
since when does fastboot or adb not work on a mac????
http://developer.android.com/sdk/index.html
hint: they have the package for mac...download it and follow the directions to run fastboot/adb commands...its easier than you think
canadianrider said:
Now I'm trying to get the build prop out of the JOP40D update but when I look in the files it is called "build.prop.p" ... I'm not sure what that last .p is about?
Click to expand...
Click to collapse
That is a *patch* file. It is used to perform binary patching of the original file - it is neither the original nor the replacement for the original.
You need to dig the original build.prop out of the 4.2.1 factory distro, or your own nandroid backups ( you do make backups, right?) The 4.2.1 distros are no longer online from Google, but oldblue910 has your butt covered with his randomphantasmagoria (sp?) site. Check for the link in the OTA post by oldblue910 over in the dev forum.
http://www.randomphantasmagoria.com <--- choose nakasi or nakasig links on rhs of page as appropriate
the easiest option would be to fastboot
system.img
and
boot.img
from the 4.2.2 images google provides...
bftb0 said:
That is a *patch* file. It is used to perform binary patching of the original file - it is neither the original nor the replacement for the original.
You need to dig the original build.prop out of the 4.2.1 factory distro, or your own nandroid backups ( you do make backups, right?) The 4.2.1 distros are no longer online from Google, but oldblue910 has your butt covered with his randomphantasmagoria (sp?) site. Check for the link in the OTA post by oldblue910 over in the dev forum.
http://www.randomphantasmagoria.com <--- choose nakasi or nakasig links on rhs of page as appropriate
Click to expand...
Click to collapse
Thank you! That's what I was looking for.
I did make a backup .... many moons ago.. then the hard drive on my windows pc died. And there went my backups..
Pirateghost said:
since when does fastboot or adb not work on a mac????
http://developer.android.com/sdk/index.html
hint: they have the package for mac...download it and follow the directions to run fastboot/adb commands...its easier than you think
Click to expand...
Click to collapse
Yeah I looked that up after I posted this.. Now to figure out how to use ADB and Fastboot.
Pirateghost said:
the easiest option would be to fastboot
system.img
and
boot.img
from the 4.2.2 images google provides...
Click to expand...
Click to collapse
Not sure how to do that... I've been looking at the thread for putting the n7 back to stock with adb/fastboot .. haven't looked too closely yet (just sat down) but I don't want to relock the bootloader so im not sure if that applies to me. Is there a thread on how to flash firmware with ADB?
Cheers
canadianrider said:
Thank you! That's what I was looking for.
I did make a backup .... many moons ago.. then the hard drive on my windows pc died. And there went my backups..
Yeah I looked that up after I posted this.. Now to figure out how to use ADB and Fastboot.
Not sure how to do that... I've been looking at the thread for putting the n7 back to stock with adb/fastboot .. haven't looked too closely yet (just sat down) but I don't want to relock the bootloader so im not sure if that applies to me. Is there a thread on how to flash firmware with ADB?
Cheers
Click to expand...
Click to collapse
running adb and fastboot commands DO NOT require you to relock the bootloader
its simple. once you have your fastboot executables set up on your computer its literally as simple as putting the device in fastboot mode, and running:
fastboot flash system nameofsystem.img
fastboot flash boot nameofboot.img
Pirateghost said:
running adb and fastboot commands DO NOT require you to relock the bootloader
its simple. once you have your fastboot executables set up on your computer its literally as simple as putting the device in fastboot mode, and running:
fastboot flash system nameofsystem.img
fastboot flash boot nameofboot.img
Click to expand...
Click to collapse
No no I know it does not require you to relock the bootloader.. I just assumed the method used in the one thread I was talking about would relock the bootloader.. I'm just talking out of my ass here though.. I'll start reading on how to use fastboot soon.
If anyone has any good idiot proof guides I'd appreciate it.
follow GOOGLE's directions for setting up fastboot and adb.
it is literally 2 commands
fastboot flash system nameofsystemimgfile.img
fastboot flash boot nameofbootimgfile.img
while the device is in fastboot mode....its not complicated. download the files you need and get started. in the amount of time you have waited on a reply, you could have already had it done. you dont have to learn every command, you just need to 'install' fastboot and adb and put the files in the proper place.
https://developers.google.com/android/nexus/images
http://bit.ly/158k5Wr
ah hah! after a bit of reading and fumbling around with fastboot I did it! thanks for all the help guys. my blood pressure can go down now..
canadianrider said:
ah hah! after a bit of reading and fumbling around with fastboot I did it! thanks for all the help guys. my blood pressure can go down now..
Click to expand...
Click to collapse
see? it wasnt really that complicated.
Pirateghost said:
see? it wasnt really that complicated.
Click to expand...
Click to collapse
no it wasn't... but it was a little more complicated because there's no "this is how you flash on a mac" thread ... I just had to compile different parts from different threads.
canadianrider said:
no it wasn't... but it was a little more complicated because there's no "this is how you flash on a mac" thread ... I just had to compile different parts from different threads.
Click to expand...
Click to collapse
i provided a lmgtfy link, that had many threads listed on setting it up on a mac.
all nexus devices are the same in respect to fastboot/adb
any thread you find for n7, galaxy nexus, nexus4....pretty much universal
Ok, now just came across another issue.. I'm on 4.2.2 and all is well, but now I want to root.
And now adb is saying that my device is offline? I've tried restarting the device. Checking and unchecking USB debugging. Unplugging and plugging it back in but nothing? ... I've read on windows machines it might be a driver issue but with mac's we don't have to install drivers.
ADB worked perfectly fine before the update...
Has anyone made a version of the 4.2.2 update that can be installed even for those of us with modified system/app files? The only way I could get the last two updates was to hunt down this specific version of the update files.
canadianrider said:
Ok, now just came across another issue.. I'm on 4.2.2 and all is well, but now I want to root.
And now adb is saying that my device is offline? I've tried restarting the device. Checking and unchecking USB debugging. Unplugging and plugging it back in but nothing? ... I've read on windows machines it might be a driver issue but with mac's we don't have to install drivers.
ADB worked perfectly fine before the update...
Click to expand...
Click to collapse
What version of adb are you using? (command: "adb version")
With 4.2.2 you should see a pop-up on the tablet asking you to accept the device (PC/Mac) with the RSA fingerprint yadda-yadda-yadda... If you don't hit the accept/OK button within 2-3 seconds, adb will report the device offline ... even if you eventually press the OK/accept message in the popup on the tablet.
Try restarting the adb server on the Mac and be ready to press the button on the popup (make sure screen on tab is unlocked)
Code:
adb kill-server
adb devices
gavingt said:
Has anyone made a version of the 4.2.2 update that can be installed even for those of us with modified system/app files? The only way I could get the last two updates was to hunt down this specific version of the update files.
Click to expand...
Click to collapse
Pirate posted a link of the full 4.2.2 ROM that can be installed with fastboot.
bftb0 said:
What version of adb are you using? (command: "adb version")
With 4.2.2 you should see a pop-up on the tablet asking you to accept the device (PC/Mac) with the RSA fingerprint yadda-yadda-yadda... If you don't hit the accept/OK button within 2-3 seconds, adb will report the device offline ... even if you eventually press the OK/accept message in the popup on the tablet.
Try restarting the adb server on the Mac and be ready to press the button on the popup (make sure screen on tab is unlocked)
Code:
adb kill-server
adb devices
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.29
No pop up on the tablet
Ah nevermind.. I'm just reading on the ADB website that you need version 1.0.31 or higher with 4.2.2 .... thanks for the heads up!
So, I lurked a couple different sites for android for a while. I just like to read the whats happening and such with tech, and I always read about root and how rooting pretty much makes a phone/tablet a whole different device, so today I rooted it (my Nexus 7)...
Well, I can't remember exactly what I did, because I have been searching every place on the internet to figure out exactly what I did and how to fix it.
Oh and I rooted it by manually doing it (with cmd and such)
When I try and get into recovery I get a android green dude laying down on his back with a red triangle with a ! in the middle that says "no command" below it. I have wiped and cleared cache. I have read a bit about this from searching the internet, but I have yet to find a way that works. I was thinking about trying to undo everything then reroot it, but I really no idea what to do. I did root it correctly (I believe), but I may have tried to update the recovery (maybe) and that may have done it. But like I said I can't remember what I did since it has been so long and I have read so much other stuff.
I can provide anymore info for anyone who wants to try and help.
Oh, I forgot to mention that I read that putting a new recovery on would probably take care of it, but when I try I get a message saying "installation aborted". How or why, I do not know.
Sorry, for rambling and the not too hot spelling and grammar. Been a while since I have posted on any forum.
I just keep forgetting things. I can still turn it on and do somethings. Things like the home softbutton/key (not sure what they are called) doesn't work, the notification bar only scrolls down on the one side, and no notifications show up there, I still have root according to the root checker app I used, so yeah.
Thanks.
The android dude lying on his back is the stock recovery.
Put your tablet in bootloader mode and
Code:
fastboot flash recovery name-of-your-custom-recovery-image-file.img
and proceed from there.
If you don't know what the above means you need to do some more reading - perhaps the fastboot/return to stock sticky thread.
PS: you should define what exactly you mean by "manually" as there are now two different rooting paths... my answer above presumes you rooted by unlocking the bootloader via fastboot. Up until recently, that was the most common method.
bftb0 said:
The android dude lying on his back is the stock recovery.
Put your tablet in bootloader mode and
Code:
fastboot flash recovery name-of-your-custom-recovery-image-file.img
and proceed from there.
If you don't know what the above means you need to do some more reading - perhaps the fastboot/return to stock sticky thread.
PS: you should define what exactly you mean by "manually" as there are now two different rooting paths... my answer above presumes you rooted by unlocking the bootloader via fastboot. Up until recently, that was the most common method.
Click to expand...
Click to collapse
OK.
I did that and I was able to get into clockwork, but I am still stuck with a non working home key and a notification bar that isn't working right. I think I would like to just go back to stock until I figure this out better, I thought I knew enough to root, but I guess I don't.
I did it that way (bootloader via fastboot). I just see people doing toolkits and stuff and I wanted to say I didn't use them, so people knew.
Thank you for the help.
Also, what sticky are you talking about? I'm not sure where it (the sticky) is located. If you could direct me to it or post a link, that would be awesome. I think I am going to hold off on the root. Just once I can get this back to stock.
Once again, thanks.
OK, I found the guide I used to help me along with rooting and I was going over it to redo the root, but during step 9 of it I got a problem.
C:\adt-bundle\sdk\platform-tools>fastboot flash recovery-clockwork-touch-6.0.3.1
-grouper.img
unknown partition 'recovery-clockwork-touch-6.0.3.1-grouper.img'
error: cannot determine image filename for 'recovery-clockwork-touch-6.0.3.1-gro
uper.img'
C:\adt-bundle\sdk\platform-tools>
I am actually getting 2 errors it appears:
C:\adt-bundle\sdk\platform-tools>fastboot flash recovery recovery-clockwork-6.0.
3.1-grouper
error: cannot load 'recovery-clockwork-6.0.3.1-grouper': No error
C:\adt-bundle\sdk\platform-tools>fastboot flash recovery recovery-clockwork-6.0.
3.1-grouper.img
error: cannot load 'recovery-clockwork-6.0.3.1-grouper.img': No error
C:\adt-bundle\sdk\platform-tools>
I can't post a link until I get 10 posts, so once I get 10, I will post it.
I found the guide to get back to stock, so I think I will try that.
[GUIDE] Flashing a Factory Image with fastboot / return to stock Is what I found and I will try.
During the erase userdata part, it seems it has gotten stuck.
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-4.18.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jdq39.zip
So, I stopped the stalled cmd and I started another to try and get the userdata erased.
So, I skipped the step to erase userdata and went on to the next one and I got this:
C:\adt-bundle\sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.
18.img
error: cannot load 'bootloader-grouper-4.18.img': No error
C:\adt-bundle\sdk\platform-tools>
I cannot seem to find a way around this error I have gotten a bunch of times.
All taken care of, someone over at Androidcentral helped me out.
So, thanks for the bit of help and this thread is done.
Welldang said:
All taken care of, someone over at Androidcentral helped me out.
So, thanks for the bit of help and this thread is done.
Click to expand...
Click to collapse
I would reccomend if you get any future issues use wugfresh nexus root toolkit.. I have used this many times to revert back to stock / full wipe or re root etc. Glad you sorted it dude. I hate it when something goes wrong but then learnng new stuff to do is always fun
I stepped out (it's the weekend!) so I just saw your posts now.
Congrats on getting it fixed.
The trouble you had with fastboot was that you did not use the correct number of arguments; the correct format is:
fastboot flash partition_name source_file
and you forgot to give the partition_name ("recovery")
In the future, I would recommend that you strictly avoid flashing the bootloader (not the "boot" partition, but the "bootloader" partition) unless it is absolutely, positively necessary. It is simply too dangerous - a mistake made here will cause a hard brick of your device.
cheers
Samsung/Google Nexus 10 Help Thread!
mantaray
Welcome to the Nexus 10 help thread! You can ask all questions here without the need of background knowledge. This thread is dedicated to solve users problems, so if you don't want to start a new thread for your question, ask it here. Members ready to help will be monitoring this thread and provide answers as soon as possible. For a list of supporters, see here:
Current List of Supporters@demkantor - All Things Nexus - adb & fastboot expert!
@lj50036 - GitHub Expert and All Around Android Guy!
@rirozizo - Battery Guru and Android Know It All!
@XxLordxX - The Unbricker!
Click to expand...
Click to collapse
Supporters: If you want to be put on or off the list, just send me a PM!
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @ like above. Also, if you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible for posting there, you may post here. And Please Read The 2nd & 3rd Post Of This Thread Before Posting! Thank you!
ROM developers: Please read this. Consider if you want to have a ROM specific help thread or not, if not, most likely questions about your ROM will be asked here if the users aren't eligible for posting in development section.
To all of you: Remember the Rules and the Forum Etiquette
Knowledge is Power!
This section is not meant to offend but rather inform XDA members, please read, understand and abide by what is said in this post... you will never be called a n00b if you do!
First Read This:
~~~~This alone will save you - thanks Tony Stark~~~~
How to post your problem or question
This isn't really complicated but the more you know the more likely you can find your own answer.
But we are here to help! So the more information you give us, the better/faster we may help you!
Step One
Have you searched for the answer to your problem/question?
If not do this first, both the search button in the XDA forums and Google work wonders.
At least attempt to show you did a little research before you scream help or this ROM is garbage, Not searching or just simply complaining will get you ignored EVEN IF YOU WRITE IN ALL CAPS
All questions belong in Q&A Forum All General Phone discussion in General NEVER post random problems in Developers section
Step Two
So you have searched for your answer and can't find it, that's okay, it happens to all of us. But before you create a new thread seek out a similar one (in the proper forum for you device) and ask there - or here.
You may think a new thread is better but in truth people look at the old ones just as much, and keeping all similar questions in one thread helps to elevate congestion and makes the next guys search a ton easier.
Step Three
Know what to post. This means explain your problem as best you can (dont write a book, just not "help my phone is possessed by demons" this is not helpful)
So this means explain all about your phone, boot into your bootloader and write down all from that screen within your post. Are you rooted? Explain where your troubles began and what you have tried to do to fix it.
Give details as much as possible, this often will include a logcat. Which there are many ways to get, learn how to before you have a problem.
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg ; adb logcat -b system -b radio -b events -b main
Code:
cat /proc/last_kmsg
Also read THIS or maybe try THIS
Use pastebin or codewraps around your logcat ( # sign from above)
Obviously every problem and question will require different information, but the more you give the better chance someone can help you.
Step Four
Wait for your answer, do not post the same question in ten threads, one will do. While you are waiting keep searching for your own answer.
When someone gives you help say thank you (with the thanks button preferably - don't make a post that just says thanks... nope, never)
Even if you don't like the answer be grateful someone took time from their day to try and help, If you think it's bad advice maybe reiterate your question and politely ask for a clearer or better explanation to the solution.
Once you have an answer
Edit first post to add the fix. If there was no fix maybe explain why there is no fix in first post.
This will help others searching for a similar problem later. Make sure your helper was thanked as well.
*Remember ROMs, Kernels, etc, may be posted in the developer section, basic questions shouldn't be in those threads. If you must add something, like a bug report, be sure to add a logcat or you man not be helped.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Again, please understand that no one here is paid, we are here to learn and we help for fun. so please be respectful...
Quick Tips!
Okay, so if you look through the Q&A thread here the number one issue that keeps popping up is "Help Bootloop!" and "Help I Think it's Bricked!"
So here is a quick guide that will most often fix these issue (90% of the time anyway)
First things first.... Drivers
Now many of you have these installed, so if you can connect your device to PC through USB and are able to communicate with adb and fastboot just skip this.
If however you can not, then you need to download appropriate drivers for Windows.
You can get these through the Adroid SDK if you already have this
Or direct from the OEM following the link HERE
Or some say having the Naked Drivers works best, so try HERE or HERE or HERE
If you need help installing these then see the next chunk on adb/fastboot or feel free to ask here as well!
*Linux users just need the android rules set up, see fastboot link for how to...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So after drivers are up... Fastboot!
Well here is many's big fear, but fear not as the terminal is not that scary!
For an in depth explanation on how to use fastboot, I highly suggest reading through THIS
It will have all you need to know and if there are any further question please feel free to ask here or in the fastboot thread.
If you have any issues running fastboot (or adb) commands, please copy and paste all input/output from terminal/cmd here so one of your helpers can assist better.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You can connect to PC and you know the commands.. but what to flash?
For the most part we want to use the stock firmware found here (some OTAs HERE for another use)
Download the latest for mantaray (currently 4.4.2-(KOT49H)
Now check MD5sum or sha1 for a match (Linux use terminal, windows use THIS)
If all is good lets extract the contents (I prefer 7zip but whatever)
So if all of your prep work is a success then when you type
Code:
fastboot devices
Into a terminal/CMD you will see your serial number
If not be sure you are in bootloader mode (power on while holding volume +)
Also have a high quality USB cable if not the one that came with your device
*Still have issue, ask in this thread!
If you have a locked bootloader it may be wise to
Code:
fastboot oem unlock
Then follow the below info, if you don't want to unlock your tablet just run the flash-all.bat to get similar results
And now you have a bunch of images, lets erase and flash so we will be oh so clean!
*have everything backed up first! this will erase your tablet!
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
now after we cleaned things up, lets flash back to stock!
Code:
fastboot flash bootloader nameofbootloader.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
(Everything should be named accordingly except for bootloader, so change this command)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Congrats! You can reboot to a functioning tablet!
Some quick notes:
If you want a custom recovery, fell free to instead flash latest TWRP or CWM or whatever.
You do not need to use stock recovery for the above to work, but you will need your custom recovery in a .img
Similarly if you want a custom ROM instead of stock you can do this, but only if your dev supplies you with the system.img, if not just boot to recovery, make a nandroid, wipe all, flash custom ROM and gapps through adb sideload.
If you still have a bootloop or a "brick" then ask us here and someone will be glad to give you personal assistance.
Or for real time help you can see if anyone is at ##Manta_Help_IRC on freenode
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Anything I missed feel free to ask in this thread!
Happy Flashing!
Tech Specs and More!
Want To Know More About Your Tablet
GENERAL INFO
GSM ARENA
Factory Images "mantaray" for Nexus 10
AOSP
Click to expand...
Click to collapse
Quick Linux/Unix Rooting Guide
First of all, you need to have Fastboot and ADB. To do as such open your command line and type:
Code:
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/fastboot
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/adb
Now that you have both files, you need to setup them to be able to use. As you're an Unix user you'll probably get what I'll do here, you can do it slightly different, but this way was the easiest IMO, also it makes the procedure for next times using adb and fastboot easier. Type the following:
Code:
sudo mv fastboot /usr/bin/fastboot
sudo mv adb /usr/bin/adb
sudo chmod 755 /usr/bin/fastboot
sudo chmod 755 /usr/bin/adb
Now that you have adb and fastboot set up it's time to start the real thing. First of all, make sure to backup your device, as everything will be lost in this procedure! First you need to unlock your device bootloader (if it is already unlocked, skip this part). Please, go to settings, "About Device" and click multiple times "Build Number", a new tab will appear in settings, called "Developer Options", go there and enable USB Debugging. Now plug your Nexus 10 on your PC and type this to check if your device was recognized:
Code:
adb devices
If something came up it was successfully recognized and you can follow up :victory:, but it nothing appeared you may need to check this:
http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
When you get your device recognized do the following:
Code:
adb reboot bootloader
Wait for the device to reboot, when it turns on again, you'll type the following:
Code:
sudo fastboot oem unlock
Now follow the instructions on your tablet screen. As soon as your bootloader is unlocked the device will reboot, so you'll now download the recovery and the Superuser.
Get the TWRP from here (download the .img file): http://www.teamw.in/project/twrp2/128
Get the SuperSU from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
Click to expand...
Click to collapse
Copy SuperSU to your device internal memory (that's probably empty now) and rename the .img file of TWRP to recovery.img. Now enable USB debugging again (it's explained above lol) and replug the tablet on your PC. Time for typing again! (Please, open the terminal in the folder where the recovery.img is located).
Code:
adb reboot bootloader
Wait for it to reboot, and then type:
Code:
sudo fastboot boot recovery.img
(If you want to install the recovery permanently in the device, type 'sudo fastboot flash recovery recovery.img' before issuing the command above).
Now you probably see a screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click in Install and select the SuperSU zip that you copied to your tablet internal memory earlier. When the flash is complete, reboot the tablet and congratulations! You're rooted :victory:.
Hope this helps anyone who may need it!
Click to expand...
Click to collapse
Quick Linux/Unix Restoring to Stock Guide
So you've decided that you don't want root anymore or you did something and want to restore to stock? That's not a hard thing to do! Just follow these steps and you'll be fine.
First you need to have adb and Fastboot ready. To do as such open your command line and type:
Code:
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/fastboot
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/adb
Now that you have both files, you need to setup them to be able to use. As you're an Unix user you'll probably get what I'll do here, you can do it slightly different, but this way was the easiest IMO, also it makes the procedure for next times using adb and fastboot easier. Type the following:
Code:
sudo mv fastboot /usr/bin/fastboot
sudo mv adb /usr/bin/adb
sudo chmod 755 /usr/bin/fastboot
sudo chmod 755 /usr/bin/adb
Now that you have adb and fastboot set up it's time to start the real thing. First of all, make sure to backup your device, as everything will be lost in this procedure! First you need to unlock your device bootloader (if it is already unlocked, skip this part). Please, go to settings, "About Device" and click multiple times "Build Number", a new tab will appear in settings, called "Developer Options", go there and enable USB Debugging. Now plug your Nexus 10 on your PC and type this to check if your device was recognized:
Code:
adb devices
If something came up it was successfully recognized and you can follow up :victory:, but it nothing appeared you may need to check this:
http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
When you get your device recognized do the following:
Code:
adb reboot bootloader
Wait for the device to reboot, when it turns on again, you'll type the following:
Code:
sudo fastboot oem unlock
Now you'll follow the instructions on screen. When your device is unlocked, you'll have to download the stock firmware you want from one of those links:
Android 4.2.2. - https://dl.google.com/dl/android/aosp/mantaray-jdq39-factory-d79f489e.tgz
Android 4.3 - https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Android 4.4 - https://dl.google.com/dl/android/aosp/mantaray-krt16s-factory-94413961.tgz
Android 4.4.2 - https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz[/CODE]
Click to expand...
Click to collapse
Now that you're done with your download, you'll extract the .tgz package the way you prefer. Now, open a command line in the folder where the extracted files are and (with your device plugged on fastboot mode) just type:
Code:
chmod 755 flash-all.sh
sudo ./flash-all.sh
The procedure will now begin. It can take some time to finish. When it ends, it's recommended that you lock back your booloader, which is as easy as unlock. Type (tablet plugged in fastboot):
Code:
sudo fastboot oem lock
Hope this helps!
Click to expand...
Click to collapse
~Lord
XxLordxX said:
If you want I can do the Linux walkthrough and script . I'll be more than glad to assist in this.
~Lord
"This Story Ends Where It Began"
Sent from my monstrous Xperia Z1
Click to expand...
Click to collapse
Yes a Linux walk-through is what I was going to do... I can also do a windows one it will just take me a bit longer... Thx lj
i want in! "all-round-android-guy"
Sent from my Nexus 4
Nexus 10
I've followed the instructions, unlocked the bootloader all the commands executed with "okay" but then on reboot the tablet is exactly like it's been from the get go, still showing user info and still showing all downloaded apps and updates, nothing works correctly. Thought maybe was a half installed update or virus. Nothing I've tried resets this to Factory. It's the Gtp 8110
kerriganinks said:
I've followed the instructions, unlocked the bootloader all the commands executed with "okay" but then on reboot the tablet is exactly like it's been from the get go, still showing user info and still showing all downloaded apps and updates, nothing works correctly. Thought maybe was a half installed update or virus. Nothing I've tried resets this to Factory. It's the Gtp 8110
Click to expand...
Click to collapse
What is your PC's OS.....:good:
OS
lj50036 said:
What is your PC's OS.....:good:
Click to expand...
Click to collapse
Windows 7 64 bit. on several machines. I tried 3 diff systems same results, even tried the hated toolkits, but the bootloader locks on any reboot at all. Negating any changes, the fastboot at least didn't reboot so it said all commands were completed, but nothing actually changed. I'm having issues reading those verifications on the page to post, is there a way around that. I got the phone number to call this in to Samsung for service, something has it locked and I've wasted way too much of my life toward trying to work on someone else's tablet. I've used the flash method on several phones and tablets in the past, so not a complete novice, just know it's not giving the same results as for others because something's wrong with the tablet.
This indeed is a strange issue, it seems others have had the same challenge
http://forum.xda-developers.com/showthread.php?t=2638227
Can you try the fastboot method of restoring stock again and this time copy and paste all input/output here
Also can you write down all info on bootloader screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
Nexus 10 Boot behavior
Hello forum gurus!
I have a question regarding the boot behavior of the Nexus 10 that you'll probably know something about.
I need to have the device boot straight to the android desktop after it's been plugged in while in an off state. Usually, most devices boot into a battery-charging screen when you apply power while they're off, then they top up the battery and go to sleep, waiting for you to press the power button.
I'm hoping there is a way to alter this behavior and get the device to boot into android's desktop straight up. I've seen this setting being changed between different ROMs and I'd like to hear your opinion how to get the change done.
This is for a project of mine, the way I see it, i'll be using a few of these tablets for an installation.
Thank you for your feedback in advance!
Best,
Stef
Hi wheezardth
Unfortunately I can't answer your question directly as I have never attempted this. The boot sequence is controlled by the bootloader but I have often seen android devices with a custom recovery boot directly to recovery when being off and then plugging in. So this would mean that the bootloader must look to the kernel (which a recovery is a kernel) for some direction at this point.
It more than likely is possible to alter either the kernel partition or possibly the recovery to do exactly what you are after but how you implement this I can't say off hand. But I will say it is unwise to attempt to alter the bootloader itself so look to kernel ninjas for help on this one.
I'll talk with some people who may have an answer on this and get back to you and if you know any (they don't have to own a n10) ask them and see if they may have an answer
Best of luck and I'll let you know what I find
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks a lot, also for the quick response.
I'll wait for your reply, so we don't end up pestering the same people twice for the same thing.
BR,W
demkantor said:
Hi wheezardth
Unfortunately I can't answer your question directly as I have never attempted this. The boot sequence is controlled by the bootloader but I have often seen android devices with a custom recovery boot directly to recovery when being off and then plugging in. So this would mean that the bootloader must look to the kernel (which a recovery is a kernel) for some direction at this point.
It more than likely is possible to alter either the kernel partition or possibly the recovery to do exactly what you are after but how you implement this I can't say off hand. But I will say it is unwise to attempt to alter the bootloader itself so look to kernel ninjas for help on this one.
I'll talk with some people who may have an answer on this and get back to you and if you know any (they don't have to own a n10) ask them and see if they may have an answer
Best of luck and I'll let you know what I find
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please Help
Main issue: Unable to write to internal storage
Symptoms: Cannot write to external storage,
Google Play FC
Opening Gallery shows "no external storage available"
Opening camera shows "insert an SD card before using the camera"
Trying to open internal sd from ES file explorer storage/emulator/0 not found.
I installed Omni Rom. Then i changed to other roms which were already in the storage.I noticed I could not write to internal storage but i could read.I tried 3 roms then i switched to stock 4.4.2 and locked my bootloader. I heard installing a custom kernel may help so I tried flashing one but didnt help. I can install APK's through ADB but not otherwise.I cannot download anything also.
Currently im in stock 4.4.2 rooted bootloader unlocked.
My problem is different as i can install apk's that means the emmc is not corrupted? (Not sure)
Storage shows: 26.75 GB available Total : 27.30
Please help me
unitnerd said:
Main issue: Unable to write to internal storage
Symptoms: Cannot write to external storage,
Google Play FC
Opening Gallery shows "no external storage available"
Opening camera shows "insert an SD card before using the camera"
Trying to open internal sd from ES file explorer storage/emulator/0 not found.
I installed Omni Rom. Then i changed to other roms which were already in the storage.I noticed I could not write to internal storage but i could read.I tried 3 roms then i switched to stock 4.4.2 and locked my bootloader. I heard installing a custom kernel may help so I tried flashing one but didnt help. I can install APK's through ADB but not otherwise.I cannot download anything also.
Currently im in stock 4.4.2 rooted bootloader unlocked.
My problem is different as i can install apk's that means the emmc is not corrupted? (Not sure)
Storage shows: 26.75 GB available Total : 27.30
Please help me
Click to expand...
Click to collapse
Hi,
Did you try formatting your storage? I know that relocking the bootloader will format, but maybe you need to reformat with a PC or something... Make sure you didn't select a bad partition .
Sorry, but this issue is a little weird... And I can't help you too much, I'll think a little more, but hope this helps a little.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1
XxLordxX said:
Hi,
Did you try formatting your storage? I know that relocking the bootloader will format, but maybe you need to reformat with a PC or something... Make sure you didn't select a bad partition .
Sorry, but this issue is a little weird... And I can't help you too much, I'll think a little more, but hope this helps a little.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1
Click to expand...
Click to collapse
How do i reformat with pc?
hi, i am very new to android (i still use a flip phone)
i have unlocked my nexus 10 (4.4.2), and have stopped there.
after the final steps in post #3
>fastboot erase system -w
>fastboot erase boot
>fastboot erase recovery
>fastboot flash bootloader nameofbootloader.img
>fastboot flash system system.img
>fastboot flash userdata userdata.img
>fastboot flash cache cache.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>Congrats! You can reboot to a functioning tablet!
after the reboot, would the device be rooted?
thanks in advance.
Not if using the factory image, you would still need to boot into recovery and flash superuser, then it would be rooted. Or boot to recovery and flash one of the many custom ROMs, all of which are prerooted
Really the only thing you need to do is unlock the bootloader, flash a custom recovery, then either flash a custom ROM or su
Sent from my Nexus 4 using XDA Premium 4 mobile app
thanks for the reply,
it looks like a 'catch 22' , but im sure its just that, i am seriously confused.
after reading several links, that link, to yet another linked guide.
i thought that i would use team win recovery project but it requires root. so thats a no go.
i checked a few others but same situation, require root to use.
could you/someone recomend a stable recovery or whatever i need.
...my head hurts, ill revisit this tomorrow.
Ok, so I figured I'd start a thread for a little community think tank.
If you have any ideas, direction, insight, experience, or anything else constructive, throw it in and maybe one of us can come up with something to crack this bootloader. Root might be nice, but to do anything worth a damn, an open bootloader is needed.
So I'll get this thread rolling...
Something I thought of...some devices need special programming cables.
How comical would it be if Amazon is selling the product needed to send the special command to the device to unlock it?
amazon.com/Factory-Fastboot-Cable-N2A-Motorola/dp/B0099E59SG
I'm going to pick one up and see what I can do with it.
Also something to throw out, anyone aware of how to gather the HW identifier for fastboot devices? Some devices also need to manually have the HW identifier passed via fastboot -i
kenmoini said:
Ok, so I figured I'd start a thread for a little community think tank.
If you have any ideas, direction, insight, experience, or anything else constructive, throw it in and maybe one of us can come up with something to crack this bootloader. Root might be nice, but to do anything worth a damn, an open bootloader is needed.
So I'll get this thread rolling...
Something I thought of...some devices need special programming cables.
How comical would it be if Amazon is selling the product needed to send the special command to the device to unlock it?
amazon.com/Factory-Fastboot-Cable-N2A-Motorola/dp/B0099E59SG
I'm going to pick one up and see what I can do with it.
Also something to throw out, anyone aware of how to gather the HW identifier for fastboot devices? Some devices also need to manually have the HW identifier passed via fastboot -i
Click to expand...
Click to collapse
That cable will not cut it. I have a few N2A fastboot cables, so don't wast your money. The identifier is out there somewhere, don't remember where I found it, but fastboot -i xxxxxxxx will not do it either. Not trying to shoot down the post, but most of the obvious stuff has been tried. It is very likely that a key must be sent before fastboot will go online via usb, but I haven't found anything that works pouring thru the source or bl/misc dumps & hex views.
GSLEON3 said:
That cable will not cut it. I have a few N2A fastboot cables, so don't wast your money. The identifier is out there somewhere, don't remember where I found it, but fastboot -i xxxxxxxx will not do it either. Not trying to shoot down the post, but most of the obvious stuff has been tried. It is very likely that a key must be sent before fastboot will go online via usb, but I haven't found anything that works pouring thru the source or bl/misc dumps & hex views.[/QUOTE
I'm no device but will this help?
if stay at fastboot you should send command ” fastboot -i 0×1949 oem idme bootmode 4000″ under fastboot command line. if it can not fix, you should reflash the system.img to the kindle fire hd.
Click to expand...
Click to collapse
Tomen8r said:
GSLEON3 said:
That cable will not cut it. I have a few N2A fastboot cables, so don't wast your money. The identifier is out there somewhere, don't remember where I found it, but fastboot -i xxxxxxxx will not do it either. Not trying to shoot down the post, but most of the obvious stuff has been tried. It is very likely that a key must be sent before fastboot will go online via usb, but I haven't found anything that works pouring thru the source or bl/misc dumps & hex views.[/QUOTE
I'm no device but will this help?
if stay at fastboot you should send command ” fastboot -i 0×1949 oem idme bootmode 4000″ under fastboot command line. if it can not fix, you should reflash the system.img to the kindle fire hd.
Click to expand...
Click to collapse
No. That is for the older model, using TI & uboot.
Click to expand...
Click to collapse
How about flashing an alternative bootloader like U-boot?
Patrick4 said:
How about flashing an alternative bootloader like U-boot?
Click to expand...
Click to collapse
We are not at the point where we can overwrite the bootloader yet. The kernel prevents the system from touching the bootloader.
JordanRulz said:
We are not at the point where we can overwrite the bootloader yet. The kernel prevents the system from touching the bootloader.
Click to expand...
Click to collapse
The kernel can not really prevent access to the bootloader. The bootloader & kernel are independent of each other. In fact, the bootloader is online before the kernel and even without a kernel, you can still access the bootloader. In fact, I have learned that at this time, no kernel can allow or bar access to the bootloader. That applies to Linux, not just Android.
Even beyond that, many functions on all devices are being moved onto parts of the chip that the kernel cannot access period. They are moving many functions & features into the trusted zone, beyond the kernels reach.
At any rate, none of that changes the fact that you have to have an unlocked bootloader to change the bootloader, or at the very least, an exploit that makes the bootloader think it is unlocked, or that temporarily unlocks it.
Would it help if I offered my HDX 8.9, with the advantage that I have a RIFF box so I could eventually restore the whole thing if needed?
I haven't been able to it teardown, I am afraid I might break something when trying it, but according to iFixit's mini teardown: ifixit.org/blog/5564/kindle-fire-hdx-8-9-mini-teardown/
It doesn't have screws to open the lid, but I can see some screws holes on the pictures and it was too stuck at the top part (right where the HDX 7 has the pink screws).
So:
- If any of you did tear it down without visible scratches or dents and can point me in the right direction I will be willing to try it (have some jtag adapters which I think should work with the socket on the Kindle).
- Is it worth it for any devs to try with my Kindle and available tools?
Thanks!
Would it be possible to pull the bootloader of the device and analyze it in hex or disassemble it ?
All Stormed out?
Guess this brainstorm dissipated? I am researching because of a Saturn that somehow lost the boot.img file. I may have to relinquish it to the brick pile.