Please help! C:\Documents and Settings\Tom Revell>fastboot\fastboot flash system play_modded.img
I don't know the answer to your problem, but I assume you just want Root. If that is the case, I suggest you to re-lock your bootloader and use Gingerbreak, since you don't gain any advantage of unlocking your bootloader if you just want Root
Since you already have your bootloader unlocked, you'd do better flashing Doomlord's kernel, which roots your phone by itself, instead of downloading a huge system.img. Here's the thread: http://forum.xda-developers.com/showthread.php?t=1176502
And by the way, I assume you're having issues with fastboot not being recognized as an executable, blah, blah, blah?
therevell said:
Please help! C:\Documents and Settings\Tom Revell>fastboot\fastboot flash system play_modded.img
Click to expand...
Click to collapse
This part:\Tom Revell>fastboot\ looks wrong to me, i'm at work now so can't really check.
But does it work if you go to the folder where you saved fastboot and then somewhere in the folder, as long as it is not on an icon, press shift + right mouse click > open command window here and then only type fastboot flash system play_modded.img ?
make sure play_modded.img is in the same folder as fastboot.exe
Aerox912 said:
This part:\Tom Revell>fastboot\ looks wrong to me, i'm at work now so can't really check.
But does it work if you go to the folder where you saved fastboot and then somewhere in the folder, as long as it is not on an icon, press shift + right mouse click > open command window here and then only type fastboot flash system play_modded.img ?
make sure play_modded.img is in the same folder as fastboot.exe
Click to expand...
Click to collapse
^^^^^ that...and does ginger break root ur phone without unlocking the BL?
Related
I've looked around and I can't seem to find a way to unlock the bootloader on my 2.3.6 Atrix. Most tuts are for 2.3.4. What's the best way to do it?
http://dl.dropbox.com/u/34025287/4547-fix-try2.sbf
Flash this with RSD lite - run the fastboot oem unlock commands if needed. Its as simple as that
G-Man. said:
http://dl.dropbox.com/u/34025287/4547-fix-try2.sbf
Flash this with RSD lite - run the fastboot oem unlock commands if needed. Its as simple as that
Click to expand...
Click to collapse
You just run those in ADB, right?
mugabuga said:
You just run those in ADB, right?
Click to expand...
Click to collapse
Yes that's correct. You shouldn't need to if you unlocked your bootloader before the .141 update. To re-root use this method, it will give a couple errors at a certain point, just disregard the errors and continue with the commands and reboot your Atrix when you've finished - http://www.atrixforums.com/forum/mo...ing-stock-locked-2-3-4-2-3-6-a.html#post47155
G-Man. said:
Yes that's correct. You shouldn't need to if you unlocked your bootloader before the .141 update. To re-root use this method, it will give a couple errors at a certain point, just disregard the errors and continue with the commands - http://www.atrixforums.com/forum/mo...ing-stock-locked-2-3-4-2-3-6-a.html#post47155
Click to expand...
Click to collapse
But even if I've never unlocked it, it should still work?
mugabuga said:
But even if I've never unlocked it, it should still work?
Click to expand...
Click to collapse
If you've never unlocked it, it will act like a soft brick and hang on the first reboot - this is normal. You should have a screen pop up with a list of a dozen or more options, you'll need to select 'fastboot' and then run the command in ADB - fastboot oem unlock - this will give you a unique ID # - repeat the fastboot oem unlock command with the # at the end like this - fastboot oem unlock <unique ID # here> and press enter, it will give a warning about voiding your warranty, select yes and continue. From there, it should proceed with the unlock. After wards you'll need to let it fully reboot. Then boot your Atrix BACK into fastboot again, and flash RomRacers latest recovery with ADB. You can find the thread in the Development section. Then you load your ROM of choice onto your internal SD card and boot into CWM Recovery (RomRacers) and flash the ROM - give your Atrix 10-15 mins to fully boot after you install your ROM.
G-Man. said:
If you've never unlocked it, it will act like a soft brick and hang on the first reboot - this is normal. You should have a screen pop up with a list of a dozen or more options, you'll need to select 'fastboot' and then run the command in ADB - fastboot oem unlock - this will give you a unique ID # - repeat the fastboot oem unlock command with the # at the end like this - fastboot oem unlock <unique ID # here> and press enter, it will give a warning about voiding your warranty, select yes and continue. From there, it should proceed with the unlock. After wards you'll need to let it fully reboot. Then boot your Atrix BACK into fastboot again, and flash RomRacers latest recovery with ADB. You can find the thread in the Development section. Then you load your ROM of choice onto your internal SD card and boot into CWM Recovery (RomRacers) and flash the ROM - give your Atrix 10-15 mins to fully boot after you install your ROM.
Click to expand...
Click to collapse
EDIT: Fixed the problem by pulling the batt and unpluging from the computer.
mugabuga said:
Alright. It says it worked on the phone, but my RSD Lite claims it failed with an error switching phone to BP Pass through mode (0x70BE). Its just hanging at the success screen on my phone.
Click to expand...
Click to collapse
Can you upload a pic of the screen you are seeing?
[edit] I gotta get to bed, I'll check back here tomorrow if someone else is unable to assist you tonight. Its after midnight here and I'm getting over a bad cold still. I will check back here tomorrow.
mugabuga said:
EDIT: Fixed the problem by pulling the batt and unpluging from the computer.
Click to expand...
Click to collapse
Glad to hear that Ya had me a bit concerned for a minute there...
First Of all Thanks to AndroidCentral for this!!!
I am not responsible for any bricked device
Try at your own risk!!
Now Lets go and unlock the nexus 10!! :laugh:
Requirements"
Fastboot
Android SDK
Downloads:
fastboot (windows): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-windows.zip
fastboot (mac): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
Now lets unlock!!!! :highfive:
1.Power off your Nexus 10, and reboot it into fastboot mode by holding the volume up button, volume down button and power button.
2.Plug your tablet into a full speed primary USB port on your computer. If you're using Windows, you'll see the pop-up about drivers being installed and initialized.
3.Open the terminal or command prompt on your computer, and navigate to the folder you have placed the fastboot program in. if you have already done this before you might not get any prob in doing all this stuff!!
4.At the command line, type in (without any quotes) "fastboot devices". You should get a device ID returned, which lets you know that fastboot can see your Nexus 10
5.it is really important to get the ID of the device or else you cannot go further
6.After you have got the ID just type(without qoutes) "fastboot oem unlock" in your command window.
7.Look to your tablet, where you'll have to verify the process. Remember that there's no way to undo the data loss that will happen the instant you say "Yes".
8.When the tablet reboots, you're done. You're free to install custom software, modified boot images, custom recovery.
Enjoy your unlocked nexus 10 !!!
IF you want to RE-lock your bootloader
1.All the steps are same
2.on the 6th step just change the code from "fastboot oem unlock" to "fastboot oem lock" and also flash back to STOCK images (if changed) or else it wont boot
3.This will relock your bootloader so that only authentic, signed images from Google can be flashed to the phone.
Enjoy!!!
Any idea if this sends anything to the google servers? I know when unlocking the T700 it sends the serial to ASUS to void the warranty. Not sure if this was the case with any nexus device or not (also I realize this isnt out yet). Just figured i'd ask if you had any past experience with the N7 or prior nexus device
duarian said:
Any idea if this sends anything to the google servers? I know when unlocking the T700 it sends the serial to ASUS to void the warranty. Not sure if this was the case with any nexus device or not (also I realize this isnt out yet). Just figured i'd ask if you had any past experience with the N7 or prior nexus device
Click to expand...
Click to collapse
No, it doesn't send anything to Google, that's why they give you the option to relock the bootloader .
can this be done on linux using fastboot included in sdk?
jrod091 said:
can this be done on linux using fastboot included in sdk?
Click to expand...
Click to collapse
of course man fastboot is fastboot
matt95 said:
of course man fastboot is fastboot
Click to expand...
Click to collapse
You will probably need to run fastboot as root, though.
gnustomp said:
You will probably need to run fastboot as root, though.
Click to expand...
Click to collapse
It isn't needed, if the sdk folder is in the PATH it will work normally
udimars30 said:
First Of all Thanks to AndroidCentral for this!!!
I am not responsible for any bricked device
Try at your own risk!!
Now Lets go and unlock the nexus 10!! :laugh:
Requirements"
Fastboot
Android SDK
Downloads:
fastboot (windows): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-windows.zip
fastboot (mac): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
Now lets unlock!!!! :highfive:
1.Power off your Nexus 10, and reboot it into fastboot mode by holding the volume up button, volume down button and power button.
2.Plug your tablet into a full speed primary USB port on your computer. If you're using Windows, you'll see the pop-up about drivers being installed and initialized.
3.Open the terminal or command prompt on your computer, and navigate to the folder you have placed the fastboot program in. if you have already done this before you might not get any prob in doing all this stuff!!
4.At the command line, type in (without any quotes) "fastboot devices". You should get a device ID returned, which lets you know that fastboot can see your Nexus 10
5.it is really important to get the ID of the device or else you cannot go further
6.After you have got the ID just type(without qoutes) "fastboot oem unlock" in your command window.
7.Look to your tablet, where you'll have to verify the process. Remember that there's no way to undo the data loss that will happen the instant you say "Yes".
8.When the tablet reboots, you're done. You're free to install custom software, modified boot images, custom recovery.
Enjoy your unlocked nexus 10 !!!
IF you want to RE-lock your bootloader
1.All the steps are same
2.on the 6th step just change the code from "fastboot oem unlock" to "fastboot oem lock"
3.This will relock your bootloader so that only authentic, signed images from Google can be flashed to the phone.
Enjoy!!!
Video coming soon, after i get my hands on it!
Click to expand...
Click to collapse
Thanks！I will try it!
Re-lock
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
matt95 said:
It isn't needed, if the sdk folder is in the PATH it will work normally
Click to expand...
Click to collapse
I just put it in /usr/bin with adb, I've only had my SGSII as far as android devices, Si want sure, thanks though!
Sent from my SGH-I777 using xda app-developers app
Thank you, its been so long since I rooted my last device I've forgotten most of it - do I need a new SDK and if so where do I get it?
I'm running Mac OS X 10.7.5
Apoloiges for asking but it has completely left me.
Lumsdoni said:
Thank you, its been so long since I rooted my last device I've forgotten most of it - do I need a new SDK and if so where do I get it?
I'm running Mac OS X 10.7.5
Apoloiges for asking but it has completely left me.
Click to expand...
Click to collapse
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Sdk has been updated
Sent from my SGH-I777 using xda app-developers app
alias_neo said:
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
Click to expand...
Click to collapse
yeah thanks for reminding dude
matt95 said:
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Click to expand...
Click to collapse
Apologies but is there an online guide? Iv'e got no idea what I did before when I was on my Nexus One, I reckon I might as well delete the SDK and reinstall both SDK and Eclipse sO I can root with a clean system.
---------- Post added at 02:31 PM ---------- Previous post was at 02:15 PM ----------
matt95 said:
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Click to expand...
Click to collapse
Lumsdoni said:
Apologies but is there an online guide? Iv'e got no idea what I did before when I was on my Nexus One, I reckon I might as well delete the SDK and reinstall both SDK and Eclipse sO I can root with a clean system.
Click to expand...
Click to collapse
It would appear it is a lot simpler now as you can download a sdk / eclipse bundle from here
alias_neo said:
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
Click to expand...
Click to collapse
Why do you say that? I have my Galaxy Nexus locked again with a custom ROM and kernel and it works fine. Ive never seen mention of this non-booting thing if the bootloader is locked when running something custom
I unlocked the bootloader but now the tab will not start? I starts to the X of JB and then nothing happens... Help
---------- Post added at 10:56 PM ---------- Previous post was at 10:18 PM ----------
I have the Solution :good:
If you have the same problem - Go into Stock-Recovery and make a "Factory Reset" then reboot the system.
EniGmA1987 said:
Why do you say that? I have my Galaxy Nexus locked again with a custom ROM and kernel and it works fine. Ive never seen mention of this non-booting thing if the bootloader is locked when running something custom
Click to expand...
Click to collapse
It's may be wrong, I'm basing it on my XOOM days where it wouldn't boot it you relocked with anything other than stock. If that's different now, feel free to ignore me
Sent from my GT-I9300 using Tapatalk 2
I know that when an update comes out I have to relock the bootloader, but if I unlock it after the update does it wipe the device again
Sent from my Galaxy Nexus
I have 3 questions
1. Unlocking nexus 10 means rooting it ?
2. Is unlocking or rooting tablets legal in US?
3. I ordered nexus 10 but read n
ot so good things about the limited applications are supported for 10 inch screen .. Is there any workaround to have apps look as good as iPad I mean using the entire screen ...any custom ROMs available yet
Sent from my SGH-I897
I had did a wrong boot.img flash and now fastboot is gone. I just want to verify that fastboot was actually located somewhere inside the boot.img.
Side notes..... I have a phone now that doesnt power on cuz the preloader is cooked by flashing that boot.img. If you try to charge the phone ,the battery charging icon does not show so that means I hard bricked phone.
lextacy said:
I had did a wrong boot.img flash and now fastboot is gone. I just want to verify that fastboot was actually located somewhere inside the boot.img.
Side notes..... I have a phone now that doesnt power on cuz the preloader is cooked by flashing that boot.img. If you try to charge the phone ,the battery charging icon does not show so that means I hard bricked phone.
Click to expand...
Click to collapse
Fastboot doesn't actually reside on the phone it is a communication protocol used to flash the specific partitions of the phones layout. Specifically fastboot itself is just a binary (.bin on OS X and Linux and .exe on windows) used to communicate with the fastboot protocol. Correct me if I'm wrong but what I'm guessing what you did is you meant to flash a boot.img to the boot partition and instead you flashed that to the bootloader/preloader partition erasing the bootloader. There is a flag when the bootloader is complied that allows the bootloader to have support for fastboot. Your best bet is to to try and find a factory image for your phone to try and re-flash the stock bootloader through fastboot. A second option is find a friend who has the same phone model as you and that is rooted, then dump there bootloader using terminal emulator or a similar app, transfer it to your computer and then flash it using fastboot. If you have any more questions or just want some more clarification on what I said feel free to ask more then happy to help !
shimp208 said:
Fastboot doesn't actually reside on the phone it is a communication protocol used to flash the specific partitions of the phones layout. Specifically fastboot itself is just a binary (.bin on OS X and Linux and .exe on windows) used to communicate with the fastboot protocol. Correct me if I'm wrong but what I'm guessing what you did is you meant to flash a boot.img to the boot partition and instead you flashed that to the bootloader/preloader partition erasing the bootloader. There is a flag when the bootloader is complied that allows the bootloader to have support for fastboot. Your best bet is to to try and find a factory image for your phone to try and re-flash the stock bootloader through fastboot. A second option is find a friend who has the same phone model as you and that is rooted, then dump there bootloader using terminal emulator or a similar app, transfer it to your computer and then flash it using fastboot. If you have any more questions or just want some more clarification on what I said feel free to ask more then happy to help !
Click to expand...
Click to collapse
Good info here , I did not know that fastboot was outside the android environments. The command I ran was "fastboot flash boot boot.img" if that makes sence. This was on a chinese smartphone that has a chinese only text bootloader. So no other friends will have this phone where I can grab an image from. I ordered a new phone (surprise , surprise right? ) haha , BUT I would still like to get this brick working for learning purposes and root practice.
lextacy said:
Good info here , I did not know that fastboot was outside the android environments. The command I ran was "fastboot flash boot boot.img" if that makes sence. This was on a chinese smartphone that has a chinese only text bootloader. So no other friends will have this phone where I can grab an image from. I ordered a new phone (surprise , surprise right? ) haha , BUT I would still like to get this brick working for learning purposes and root practice.
Click to expand...
Click to collapse
Glad I could help you out ! It must be a bad boot image then that you flashed, but that shouldn't prevent you from accessing the bootloader. When you get your new phone and root it you should be able to pull that stock boot image and then get your old phone working again. As always any questions let me know !
So fastboot doesn't reside in the phone?
I understand that it's a protocol, but how does the phone know to act like a server for the PC fastboot client?
Where does the phone load the protocol rules from?
Can fastboot mode run even without any partition on the phone?
If so the phone would be virtually unbrickable.
I'm just trying to understand.
JackSlaterIV said:
So fastboot doesn't reside in the phone?
I understand that it's a protocol, but how does the phone know to act like a server for the PC fastboot client?
Where does the phone load the protocol rules from?
Can fastboot mode run even without any partition on the phone?
If so the phone would be virtually unbrickable.
I'm just trying to understand.
Click to expand...
Click to collapse
Perhaps the best way to understand how fastboot works is to take a look at it's source code found here https://android.googlesource.com/platform/system/core/+/master/fastboot/fastboot_protocol.txt and the general fastboot code here https://android.googlesource.com/platform/system/core/+/master/fastboot. Let me know if you still have questions.
shimp208 said:
Perhaps the best way to understand how fastboot works is to take a look at it's source code found here https://android.googlesource.com/platform/system/core/+/master/fastboot/fastboot_protocol.txt and the general fastboot code here https://android.googlesource.com/platform/system/core/+/master/fastboot. Let me know if you still have questions.
Click to expand...
Click to collapse
Thanks, I saw but there is no answer there.
Hello ?
I'm looking to root my m4 aqua E2303 6.0.1 Bootloader unlock: yes
However I don't want any twrp stuff, last time I rooted this phone I found something on this forum, connected my phone to a pc via USB ran an exe and it got rooted it was soooo simple, and everything worked great, however after Sony released the firmware update(from 5.0.0 to 6.0.1) root dissappeared. Isn't there a similar tool for 6.0.1? I really don't want to get into all the twrp stuff and ehhh you understand, I want to keep it simple.
Thanks in advance.
Procow said:
Hello
I'm looking to root my m4 aqua E2303 6.0.1 Bootloader unlock: yes
However I don't want any twrp stuff, last time I rooted this phone I found something on this forum, connected my phone to a pc via USB ran an exe and it got rooted it was soooo simple, and everything worked great, however after Sony released the firmware update(from 5.0.0 to 6.0.1) root dissappeared. Isn't there a similar tool for 6.0.1? I really don't want to get into all the twrp stuff and ehhh you understand, I want to keep it simple.
Thanks in advance.
Click to expand...
Click to collapse
in Android 6.0.1 Without Unlock Bootloader is Impossible, but if you have Unlock Bootloader Use it,( Just Flash boot.img) : http://forum.xda-developers.com/m4-aqua/general/root-twrp-sony-xperia-m4-aqua-t3503369
And you can try KingoRoot Soft for root without Unlockbootloader
Whaaaaatt?
It just says waiting for device,
Debugging on oem on
Procow said:
It just says waiting for device,
Debugging on oem on
Click to expand...
Click to collapse
Maybe its not working.
Good luck
Yo
EHSAN™ said:
Maybe its not working.
Good luck
Click to expand...
Click to collapse
Let me explain, I'm doing the adb method, when I say fastboot flash boot boot.img it just says waiting for device
My phone doesn't react at all
I haven't manually unlocked the Bootloader it's so hard and time consuming to download all those programs.
I want only the root nothing else.
Procow said:
Let me explain, I'm doing the adb method, when I say fastboot flash boot boot.img it just says waiting for device
My phone doesn't react at all
I haven't manually unlocked the Bootloader it's so hard and time consuming to download all those programs.
I want only the root nothing else.
Click to expand...
Click to collapse
Need to unlock Bootloader for Root With ADB.
I did now
EHSAN™ said:
Maybe its not working.
Good luck
Click to expand...
Click to collapse
EHSAN™ said:
Need to unlock Bootloader for Root With ADB.
Click to expand...
Click to collapse
I did but now when I type fastboot devices
Hdjebshshd(that phone ID u know)
Then I type
Fastboot flash boot boot.img
It says something about downloading, max file size and then says FAILED
Procow said:
I did but now when I type fastboot devices
Hdjebshshd(that phone ID u know)
Then I type
Fastboot flash boot boot.img
It says something about downloading, max file size and then says FAILED
Click to expand...
Click to collapse
You must be going on Fastboot Mod Then Type this in ADB, And Read There Topic that i give you.
Well
EHSAN™ said:
You must be going on Fastboot Mod Then Type this in ADB, And Read There Topic that i give you.
Click to expand...
Click to collapse
I just open a command prompt in the adb folder and type it, it says command line is not allowed even if I try doing it in the administrator rights.
First it says max file size
,,OKAY"
Loaded(0.703seconds)
....,,boot"
Failed(command line is not allowed)
Something similar to this.
What am I doing wrong? How can I check if I actually unlocked the Bootloader(pretty sure I did)
So weird.
Procow said:
I just open a command prompt in the adb folder and type it, it says command line is not allowed even if I try doing it in the administrator rights.
First it says max file size
,,OKAY"
Loaded(0.703seconds)
....,,boot"
Failed(command line is not allowed)
Something similar to this.
What am I doing wrong? How can I check if I actually unlocked the Bootloader(pretty sure I did)
So weird.
Click to expand...
Click to collapse
*#*#7378423#*#* > Service Info > Configuration > Rooting Status:
Figured everything out, just don't know how lol
In the end I now have root ty.
Tell me how you fixed it
Hey guys, call me stupid but...
Is there a definite guide on how to download fastboot ?
Everywhere I look, the links are pointing to the android SDK but it's a 2GB download and an executable rather than a zip file.
I am confused. Can someone point me to the correct HOWTO ?
DjGeNeSiS said:
Hey guys, call me stupid but...
Is there a definite guide on how to download fastboot ?
Everywhere I look, the links are pointing to the android SDK but it's a 2GB download and an executable rather than a zip file.
I am confused. Can someone point me to the correct HOWTO ?
Click to expand...
Click to collapse
You can use this: https://mega.nz/#!RotVRSSC!j44hpB6BD_tUFsjqs2R7wH2fG3uZ_EB1cNuzBq1l3GY
raminta said:
You can use this: https://mega.nz/#!RotVRSSC!j44hpB6BD_tUFsjqs2R7wH2fG3uZ_EB1cNuzBq1l3GY
Click to expand...
Click to collapse
thank you, I downloaded Fastboot from your link and its working now.
I also had to install the Xperia dirvers from here:
https://forum.xda-developers.com/showthread.php?t=2635830&page=12
Moreover, I had to switch the USB mode to anything else rather than MTP because ADB would not recognise the device
Then I had to use this thread to make the drivers work:
https://forum.xda-developers.com/showpost.php?p=39856834&postcount=3
Then, use these commands to unlock the bootloader.
fastboot.exe devices (to make sure that your phone is properly connected)
and then:
fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which you received earlier on your email box on Step