Related
Hi everyone,
I'm new to "rooting" android devices, although I have jailbroken all my iPhones and "rooted" my palm pre.
As a newbie, it seems the "root toolkit" is the best way to do this? Is this Windows only, or is there a Mac version?
anything else I should read up on / know before rooting? I basically want to root, initially at least, to get sixaxis support and stickmount working.
Thank you all for your help in advance.
First of all, this is the wrong section. You should post inquiries in the q/a section.
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Sent from my Nexus 7
Take a peek at the nexus root toolkit thread in this forum...quick and easy.
Sent from my Nexus 7 using xda app-developers app
The tool kit is windows only, correct?
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
I would agree with:
evonc said:
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Click to expand...
Click to collapse
Then you know what is happening, and how it works... so if you run into troubles later, you know what to do.
Hard to brick this device.
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
Click to expand...
Click to collapse
For practice, and maybe the one-click solution is not flexible enough for your means. It's usually dependent on the developer to update it, so do check if it has any limitations.
Also, the ones I've seen are Windows only.
Foxman2k said:
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
As long as you don't mess up the bootloader, it should be possible to reflash stuff via recovery or fastboot. Bear in mind there have been exceptions (though that came about because of a serious kernel bug, rather than due to user error) so this can't be a guarantee.
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
spdecoste said:
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
Click to expand...
Click to collapse
Another recommendation for WUGS rootkit - literally very easy foolproof step by step menus/instructions - only prob I had were the drivers - just manually pointing to driver directory sorted this out.
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
This seems to rely on Windows. Any Mac tools available?
Foxman2k said:
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
Click to expand...
Click to collapse
Unlocking the bootloader allows you to mess with the bootloaders progression at startup, which gives you the ability to install a custom recovery and gives us the method to gain root access. The bootloader can be unlocked by many different methods - some manual and some "one-click". I'd suggest doing it the manual way first, so you understand the process, and are able to fix it manually if anything goes wrong.
To my understanding, it's locked so that people who don't know what they're doing can't mess the device up. It's a safety procedure basically.
To relock the bootloader, you just type (I only know how to do this in windows - Linux and Mac work as well al beit differently)
Code:
fastboot oem lock
and you're all set.
Foxman2k said:
This seems to rely on Windows. Any Mac tools available?
Click to expand...
Click to collapse
The Android SDK and ADB tools are equally available on Linux and Mac. You won't have to do the "Adding to Path" thing. All of the ADB commands will be the same, though.
I didn't know anything about rooting at all too, despite having an android phone for more than 2 years.
I went with the one-click root process.
Download this file, plug your Nexus 7, follow the instructions- which means typing Y, N, Y etc
Done in 5 minutes. There's a youtube video on it too. Go check it out.
I still dont know much about the process.. except I'm unlocked and rooted =)
I have a few naive questions
Do I have to do the OEM unlock to root the device? I would prefer not to wipe it.
Assuming I don't hard brick the device, can I go back to stock for warranty work?
Does rooting the device mean I can't get OTA updates from Google? For now I just want to run the stock kernel/rom and get updates. I just want root to run titanium and certain other apps that require root.
I've seen a thread that suggest that the play store (market) doesn't work on rooted devices. Is that true?
New FlashTool Updated To Full Supported Xperia Z1 With (FlashTool Driver 1.1)
Available Download Now
http://www.flashtool.net/ (Official Site)
Mirror Link: (Dev-Host)
http://d-h.st/Xrv
anyone succesfully root the xperia z1 with flashtool?. Cheers.
No, it's not supported.
Follow the routing goes in the development section
Sent from my C6903 using xda premium
No Mac release of 0.9.13 yet
Rekoil said:
No Mac release of 0.9.13 yet
Click to expand...
Click to collapse
How about now?
Troll
You can't report a negative...
Sent from my C6903 using xda premium
While flashing a stock firmware over another stock firmware, do we have to exclude anything from the package.????
I saw an option to exclude TA as well. So if i don't exclude it, will i lose my original DRM keys??
crk1995 said:
While flashing a stock firmware over another stock firmware, do we have to exclude anything from the package.????
I saw an option to exclude TA as well. So if i don't exclude it, will i lose my original DRM keys??
Click to expand...
Click to collapse
you can only lose your TA partition if you unlock your bootloader, flashing a firmware ftf file does not touch that. please search and read the available threads on how to flash a firmware file and what you can and cannot check, the only things that people sometimes uncheck is wipe data, cache etc
sofir786 said:
you can only lose your TA partition if you unlock your bootloader, flashing a firmware ftf file does not touch that. please search and read the available threads on how to flash a firmware file and what you can and cannot check, the only things that people sometimes uncheck is wipe data, cache etc
Click to expand...
Click to collapse
Actually I'm new to Sony Xperia line. So i m a bit scared about all this TA thing.
I have watched some videos but none has an option to exclude ta but mine has. I m still not convinced. Can you confirm that you have done it with your phone and did you have an option to exclude TA in your flashtool software...
Thanks in advance. Sorry to bother you.
crk1995 said:
Actually I'm new to Sony Xperia line. So i m a bit scared about all this TA thing.
I have watched some videos but none has an option to exclude ta but mine has. I m still not convinced. Can you confirm that you have done it with your phone and did you have an option to exclude TA in your flashtool software...
Thanks in advance. Sorry to bother you.
Click to expand...
Click to collapse
Just use a tool (or my guide if you're not a Windows user) to backup your TA partition and you won't have to worry about a thing (except losing the backup ).
Rekoil said:
Just use a tool (or my guide if you're not a Windows user) to backup your TA partition and you won't have to worry about a thing (except losing the backup ).
Click to expand...
Click to collapse
Actually the problem is that i m updated to the latest firmware which cannot be rooted at the moment. So i want to first revert back to previous firmware and then root and backup.
And in the guide i didnt find the option for exclude TA in the screenshot.
crk1995 said:
Actually I'm new to Sony Xperia line. So i m a bit scared about all this TA thing.
I have watched some videos but none has an option to exclude ta but mine has. I m still not convinced. Can you confirm that you have done it with your phone and did you have an option to exclude TA in your flashtool software...
Thanks in advance. Sorry to bother you.
Click to expand...
Click to collapse
When ive flashed ftf files, i have never checked anything in the exclude section of the flash tool, leave that as it is.
There are 2 versions of flashtool, one is an official from Sony, this tool does not have the option and can only be used with a unlocked bootloader. The flashtool that can be found here in the forum can be used wether you have unlocked or not, it was originally designed back when the Sony Ericsson Xperia X10 came out.
So to conclude
1. Make sure you have the latest version of flashtool installed.
2. Download your preferred firmware.
3. Open flashtool and click the lightning icon at top left.
4. make sure bootmode selected is Flashmode.
5. Select your firmware file when prompted.
6. Flashtool will now process the file (give it a minute or 2 to do this)
7. It will now prompt for you to connect phone in flash mode.
8. make sure your phone is turned off, in order to connect in flash mode while holding volume down
connect the usb, keep everything held down until the flash starts.
9. Follow onscreen instructions, it will take around 5 minutes for this to flash, flashtool will tell you went to
disconnect and reboot.
crk1995 said:
Actually the problem is that i m updated to the latest firmware which cannot be rooted at the moment. So i want to first revert back to previous firmware and then root and backup.
And in the guide i didnt find the option for exclude TA in the screenshot.
Click to expand...
Click to collapse
Or just wait for a root exploit to show up for the latest version. I mean unless you're planning to flash CyanogenMod or something now then why worry about it?
sofir786 said:
When ive flashed ftf files, i have never checked anything in the exclude section of the flash tool, leave that as it is.
There are 2 versions of flashtool, one is an official from Sony, this tool does not have the option and can only be used with a unlocked bootloader. The flashtool that can be found here in the forum can be used wether you have unlocked or not, it was originally designed back when the Sony Ericsson Xperia X10 came out.
So to conclude
1. Make sure you have the latest version of flashtool installed.
2. Download your preferred firmware.
3. Open flashtool and click the lightning icon at top left.
4. make sure bootmode selected is Flashmode.
5. Select your firmware file when prompted.
6. Flashtool will now process the file (give it a minute or 2 to do this)
7. It will now prompt for you to connect phone in flash mode.
8. make sure your phone is turned off, in order to connect in flash mode while holding volume down
connect the usb, keep everything held down until the flash starts.
9. Follow onscreen instructions, it will take around 5 minutes for this to flash, flashtool will tell you went to
disconnect and reboot.
Click to expand...
Click to collapse
CORRECTION:
sony's official flash tool is for locked bootloader and not unlocked bootloader.
And the Sony's official flashtool require some login details. i went through a new user option. But i didnt receive a confirmation email.
I m giving flashtool a try now. Lets see what happens. God save me...:laugh:
crk1995 said:
CORRECTION:
sony's official flash tool is for locked bootloader and not unlocked bootloader.
And the Sony's official flashtool require some login details. i went through a new user option. But i didnt receive a confirmation email.
I m giving flashtool a try now. Lets see what happens. God save me...:laugh:
Click to expand...
Click to collapse
You missed something, you're supposed to edit the configuration file so that the program will allow use without a login. But it only works for unlocked bootloaders.
Follow the instructions in the link below and you'll get it running:
http://developer.sonymobile.com/services/flash-tool/how-to-download-and-install-the-flash-tool/
crk1995 said:
CORRECTION:
sony's official flash tool is for locked bootloader and not unlocked bootloader.
And the Sony's official flashtool require some login details. i went through a new user option. But i didnt receive a confirmation email.
I m giving flashtool a try now. Lets see what happens. God save me...:laugh:
Click to expand...
Click to collapse
Sony's flashtool only works if you have a unlocked bootloader, go ahead try and use it if you dont believe me, the software will actaully tell you, but hey go ahead.
---------- Post added at 08:58 AM ---------- Previous post was at 08:54 AM ----------
crk1995 said:
CORRECTION:
sony's official flash tool is for locked bootloader and not unlocked bootloader.
And the Sony's official flashtool require some login details. i went through a new user option. But i didnt receive a confirmation email.
I m giving flashtool a try now. Lets see what happens. God save me...:laugh:
Click to expand...
Click to collapse
http://developer.sonymobile.com/services/flash-tool/
Read that if you don't believe me, read the first paragraph!
i quote "Flash tool for Xperia™ devices
Here you can learn more about the flash tool for Xperia™ devices, which is a desktop application that you can use to flash Sony software on your unlocked Xperia™ device. This is useful if you’ve for example flashed a custom ROM on your device, and want to go change to a standard Sony software. This flash tool can only be used by Xperia™ devices having an unlocked boot loader. Please note that your phone still stays unlocked, and that the warranty may still be voided."
sofir786 said:
Sony's flashtool only works if you have a unlocked bootloader, go ahead try and use it if you dont believe me, the software will actaully tell you, but hey go ahead.
---------- Post added at 08:58 AM ---------- Previous post was at 08:54 AM ----------
http://developer.sonymobile.com/services/flash-tool/
Read that if you don't believe me, read the first paragraph!
i quote "Flash tool for Xperia™ devices
Here you can learn more about the flash tool for Xperia™ devices, which is a desktop application that you can use to flash Sony software on your unlocked Xperia™ device. This is useful if you’ve for example flashed a custom ROM on your device, and want to go change to a standard Sony software. This flash tool can only be used by Xperia™ devices having an unlocked boot loader. Please note that your phone still stays unlocked, and that the warranty may still be voided."
Click to expand...
Click to collapse
OHHH!! Thank You for correcting me...
I m damn scared right now...to flash even a stock rom on new device.. This was not the case with samsung. They didnt have this bootloader thing earlier, dont know about current gen samsung phones.
crk1995 said:
OHHH!! Thank You for correcting me...
I m damn scared right now...to flash even a stock rom on new device.. This was not the case with samsung. They didnt have this bootloader thing earlier, dont know about current gen samsung phones.
Click to expand...
Click to collapse
Do not touch the bootloader at the moment, there is a reason why people are not unlocking their bootloader as doing this breaks camera functionality. Don't be scared, it is quite a simple procedure.
Flashing with flash tool will NOT break your phone and you can airways force a repair with pccompanion.
Just try it, it's perfectly safe
Sent from my C6903 using xda premium
crk1995 said:
OHHH!! Thank You for correcting me...
I m damn scared right now...to flash even a stock rom on new device.. This was not the case with samsung. They didnt have this bootloader thing earlier, dont know about current gen samsung phones.
Click to expand...
Click to collapse
New Samsungs are worse, you can't restore them to a state where Samsung can't detect that you've been running custom software on it.
sofir786 said:
Do not touch the bootloader at the moment, there is a reason why people are not unlocking their bootloader as doing this breaks camera functionality. Don't be scared, it is quite a simple procedure.
Click to expand...
Click to collapse
Unless you have a TA backup in which case you can do whatever you want.
I'm too much of a ***** to confirm the following theory, but I wouldn't be completely surprised if someone who flashed the wrong TA-backup was able to start the phone in fastboot mode, unlock the bootloader again (perhaps with the unlock token matching the new TA), and flash his own TA from CyanogenMod or something. (Do not quote me on this please, not taking responsibility for someone breaking their phone trying this.)
Restoring a ta that did not come from your phone will result in a hard brick, nobody should try it EVER
Sent from my C6903 using xda premium
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.
Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea
Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.
akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.
THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.
Since we are using engboot, write protection seems to be off, so it appears you can use dd to write to normally write protected partitions such as the bootloaders (ex: "dd if=/sdcard/aboot of=/dev/block/sdd10"). In my testing I was successfully "dd" a backed up aboot (secondary bootloader) partition and also write to the modem partition and have it stick (which means write protection should be off akaik). If you were to "dd" the Chinese bootloaders, you might be able to flash and re-partition onto the Chinese firmware and then use the CROM service to unlock the bootloader from there. I personally don't know too much about this type of stuff and haven't tried to actually "dd" the Chinese bootloader, but for those more knowledgeable, could this potentially work?
Partitions likely needed are:
- rpm (Resource and Power Manager / Primary Bootloader) located at /dev/block/sdd1 (/dev/block/bootdevice/by-name/rpm)
- aboot (AP Bootloader / Secondary Bootloader) located at /dev/block/sdd10 (/dev/block/bootdevice/by-name/aboot)
- xbl (Extended Bootloader) located at /dev/block/sdb1 (/dev/block/bootdevice/by-name/xbl)
- ? located at /dev/block/sdc1
Modifying the bootloader is dangerous and could permanently brick your device. I take no responsibility if you try this and it breaks your device.
Edit 5: Additional Details
qwewqa said:
Since we are using engboot, write protection seems to be off, so it appears you can use dd to write to normally protected partitions (ex: "dd if=/sdcard/aboot of=/dev/block/sdd10"). In my testing I was successfully dd a backed up aboot (secondary bootloader) partition and also write zeros to the modem partition and have it stick (which means write protection should be off). If you were to dd a Chinese bl/ap, you might be able to flash/re-partition onto the Chinese firmware and then use the CROM service to unlock the bootloader from there. I personally don't know too much about and haven't tried to actually dd the Chinese bootloader, but for those more knowledgeable, would this work?
Edit: Modem partition sticks after reboot.
Click to expand...
Click to collapse
@Binary100100 you probably know somebody that knows little bit more about this, tell them to check it out
Magnifik81 said:
@Binary100100 you probably know somebody that knows little bit more about this, tell them to check it out
Click to expand...
Click to collapse
Nope. Don't know anyone specific.
Wish I had the $175 for my insurance deductible, I'd give it a try. All in all, it should work. The hardware is the same.
thescorpion420 said:
Wish I had the $175 for my insurance deductible, I'd give it a try. All in all, it should work. The hardware is the same.
Click to expand...
Click to collapse
Well, if it WORKS, I'm sure the bounty on unlocking the bootloader is a lot higher than $175! ?
DOMF said:
Well, if it WORKS, I'm sure the bounty on unlocking the bootloader is a lot higher than $175!
Click to expand...
Click to collapse
Lets start a thread . . . I am willing to contribute $25.00 :good: into a pool with others here at XDA to the developer who can produce an unlocked bootloader that is rooted with a decent rom that works great and better than stock, something that will fix all of the untold bugs and address the known issues.
Anyone else?
serendipityguy said:
Lets start a thread . . . I am willing to contribute $25.00 :good: into a pool with others here at XDA to the developer who can produce an unlocked bootloader that is rooted with a decent rom that works great and better than stock, something that will fix all of the untold bugs and address the known issues.
Anyone else?
Click to expand...
Click to collapse
$25? Hell think about how much we spend on the phone itself and bill every month.. I'd easily pledge $100 for an unlocked bootloader with twrp support.
That's the 1 thing I don't understand.. this is the most highly sought after phone right now with 0 developer support. I understand the limitations with the locked bootloader but other phones have overcome the same through the works of various motivated individuals. There is no one even interested in trying it seems on ANY carrier forum. Instead we have countless threads with people more interested in getting the nougat update early which will hardly provide anything useful compared to an unlocked bootloader with working root.
serendipityguy said:
Lets start a thread . . . I am willing to contribute $25.00 :good: into a pool with others here at XDA to the developer who can produce an unlocked bootloader that is rooted with a decent rom that works great and better than stock, something that will fix all of the untold bugs and address the known issues.
Anyone else?
Click to expand...
Click to collapse
"Start?" It was started ages ago and it thousands of dollars. https://forum.xda-developers.com/tmobile-s7-edge/how-to/bounty-unlocked-bootloader-s7edge-t3339857
bdvince said:
$25? Hell think about how much we spend on the phone itself and bill every month.. I'd easily pledge $100 for an unlocked bootloader with twrp support.
That's the 1 thing I don't understand.. this is the most highly sought after phone right now with 0 developer support. I understand the limitations with the locked bootloader but other phones have overcome the same through the works of various motivated individuals. There is no one even interested in trying it seems on ANY carrier forum. Instead we have countless threads with people more interested in getting the nougat update early which will hardly provide anything useful compared to an unlocked bootloader with working root.
Click to expand...
Click to collapse
Root right now is just too impractical for most people. I'm still rooted, but for most people it isn't worth the hassle and trade-offs, for many it's worse than stock. I think most people who are really into root probably switched devices. Switching to android N could actually prevent bootloader unlock in this way, unless root for N comes out. That is if this unlock method could actually work, hard to say without anyone experienced in bootloaders and write protection though.
I'd like to find someone with a sm-g9350 to DD a dump of sdd10.
thescorpion420 said:
I'd like to find someone with a sm-g9350 to DD a dump of sdd10.
Click to expand...
Click to collapse
Sdd1 is the primary bootloader, probably also necessary.
Came to the realization that the Chinese bootloader is v2 where all US models are v4. I'd imagine the Chinese nougat update will make it v4, so we wait to try.
Don't want to a be downer or anything but I'm pretty sure you can't just replace the bootloader, even if write protection is off on the Eng kernel. Even if you did replace it you'll have probably bricked your phone.
Sent from my SM-G935T using Tapatalk
dogredwing1 said:
Don't want to a be downer or anything but I'm pretty sure you can't just replace the bootloader, even if write protection is off on the Eng kernel. Even if you did replace it you'll have probably bricked your phone.
Click to expand...
Click to collapse
The thinking is that since the devices are virtually the same hardware wise, there is a chance the bootloader could be replaced. I do agree that there is a good chance of hard bricking though. I haven't done any testing other than apparently successfully dding a backed up version of the same bootloader.
If I wasn't on nougat I would try it if someone posted instructions and devs confirmed the directions are correct..
Sent from my SM-G935T using Tapatalk
I was actually playing with the bootloader, and found this thread when I went to post. I'm going to be pulling fastboot commands also to see if I can find anything interesting. I'm tired of not being able to use a custom kernel
My device is on nougat. Bit I can easily downgrade and test if someone has a rock solid idea. I don't mind bricking as the device has a cracked screen and I have my s6 edge plus to use until the s8 drops...
Sent from my SM-G935T using Tapatalk
Count me in as well!
I have a theory that we can open the BL file in WinRAR and extract the rpm.mbn file from G9350 odin file,
and flash to our device. But I cannot determine which one is for aboot. I have not tested this yet.
aaron007 said:
Count me in as well!
I have a theory that we can open the BL file in WinRAR and extract the rpm.mbn file from G9350 odin file,
and flash to our device. But I cannot determine which one is for aboot. I have not tested this yet.
Click to expand...
Click to collapse
What I know is:
RPM = Resource and Power Manager = Primary Bootloader
ABoot = AP Bootloader = Secondary Bootloader
I believe the boot process is "RPM > ABoot > boot.img (Main OS)", so both the rpm and aboot file would be needed. Also I think the partition layout in the Chinese version is slightly different, so a flash and repartition would be needed after replacing bootloader to actually root. I don't know what the chances success are though, the devices are virtually the same hardware wise, and the Chinese rom with the U.S. bootloader works according to the Verizon fourm, but there is a chance there are other differences what might prevent this from working.
Flippy125 said:
I was actually playing with the bootloader, and found this thread when I went to post. I'm going to be pulling fastboot commands also to see if I can find anything interesting. I'm tired of not being able to use a custom kernel
Click to expand...
Click to collapse
Isn't fastboot disabled on the s7. Also, were your results the same?
qwewqa said:
What I know is:
Isn't fastboot disabled on the s7. Also, were your results the same?
Click to expand...
Click to collapse
Yes, found that out when I started playing with it more. I'm currently reading sdd10 line by line. I did find an entry "Device is unlocked! Skipping verification...". I'm starting to think we need to look into recovery-side exploits. I'm too scared to try and mess with the bootloader too much.
EDIT: If we can find a way to get fastboot working, possibly piggybacking off of Odin, I found a command written in the aboot code 'fastboot oem unlock-go'
EDIT2: Using that command requires some sort of key. May be a dead end.
EDIT3: I'd be willing to test modifying the recovery image to see if it triggers the bootloader's hash checking. If anything, this could lead to writing a custom boot image that would open TWRP.
Is it possible to unlock the bootloader without the unlock code coming from Huawei itself?
I want to unlock the bootloader. Many pages on the web (and on this forum as well) say I need to get the unlock code from huawei, but... it seems that huawei is not collaborative any more: Honor/Huawei’s bootloader unlock page disappears with no explanation
Can I work it out without the code?
Actually, what I really want to do is...
Actually, what I really want to do is...: install a different firmware.
I'm a real noob in the world of modding & custom rom.
As far as I understand, unlocking bootloader is required in order to install a different ROM: is it right? or can I install it somehow even with bootloader locked? Also, can I root the P8 without unlocking the bootloader?
My P8 is on the latest firmware I recently received OTR from Huawei: GRA-L09C02B405. The phone is starting to have some problems: hight battery drenage, UI freezing and rebooting from time to time.
I'd like to install a previous version of Huawei official firmware, or different a custom ROM (I read about some of them in this forum: any suggestion?). But as far a I understand, unlocking bootloader is required, and it seems that without the code from Huawei I'm blocked
Ik zit met de zelfde vraag, ook mijn P8 kan ik niet unlocken website van Huawei met deze optie is verdwenen.
I have the same question, also my P8 I can't unlock Huawei's website with this option is gone.
You now have to contact Huawei and request it, providing IMEI, SN, Product Code, Model, and reason why you wish to unlock it.
Here is a link to contact the UK (most people say this is more successful than others) :- https://consumer.huawei.com/uk/contact-us/
Thanks @Sparkrite, I will try that way.
Can you help me also with my second post in this thread? I mean, do I have to unlock the bootloader in order to flash a custom rom and / or to root the phone?
ModNoob33 said:
Thanks @Sparkrite, I will try that way.
Can you help me also with my second post in this thread? I mean, do I have to unlock the bootloader in order to flash a custom rom and / or to root the phone?
Click to expand...
Click to collapse
For both, yes, you need to unlock your phone. For rooting, you have to flash a new boot.img, and for a custom ROM you have to flash the system.img too.
Without the unlocked bootloader you are unable to flash the images /partitions
ModNoob33 said:
Thanks @Sparkrite, I will try that way.
Can you help me also with my second post in this thread? I mean, do I have to unlock the bootloader in order to flash a custom rom and / or to root the phone?
Click to expand...
Click to collapse
For both NO, however it tends to be a bit easier if the bootloader is unlocked. Some third party rooting apps may or may not work, depending on what version OS you have installed, without changing the recovery partition.
However it is usually easier to root by flashing with TWRP etc. which necessitates an unlocked bootloader to allow you to flash the said recovery.img and then flashing SU.zip for example.
The same goes for flashing a system.img ( does not need an unlocked bootloader ) eg. use fastboot mode and an ADB shell or even DLOAD if it has the correct signatures. The caveat is that most if not all custom ROMs use a proprietary boot.img so an unlocked BL will be required in this case.
Hope that clears it up for you.
Sparkrite said:
For both NO, however it tends to be a bit easier if the bootloader is unlocked. Some third party rooting apps may or may not work, depending on what version OS you have installed, without changing the recovery partition.
However it is usually easier to root by flashing with TWRP etc. which necessitates an unlocked bootloader to allow you to flash the said recovery.img and then flashing SU.zip for example.
The same goes for flashing a system.img ( does not need an unlocked bootloader ) eg. use fastboot mode and an ADB shell or even DLOAD if it has the correct signatures. The caveat is that most if not all custom ROMs use a proprietary boot.img so an unlocked BL will be required in this case.
Hope that clears it up for you.
Click to expand...
Click to collapse
Isn't it? Oh, damn, all time I thought it necessary to do this. Sorry
Sparkrite said:
For both NO, however it tends to be a bit easier if the bootloader is unlocked. Some third party rooting apps may or may not work, depending on what version OS you have installed, without changing the recovery partition.
However it is usually easier to root by flashing with TWRP etc. which necessitates an unlocked bootloader to allow you to flash the said recovery.img and then flashing SU.zip for example.
The same goes for flashing a system.img ( does not need an unlocked bootloader ) eg. use fastboot mode and an ADB shell or even DLOAD if it has the correct signatures. The caveat is that most if not all custom ROMs use a proprietary boot.img so an unlocked BL will be required in this case.
Hope that clears it up for you.
Click to expand...
Click to collapse
I asked Huawei for the code, now I'm waiting for reply.
So, if I understand correctly, even without unlocking bootloader I should be able to flash a previous version of an official firmware, ain't it? I can consider that option if I don't get the code from Huawei
Thanks a lot, you are being really helpful
Bootloader unlocking is not needed for upgrading official firmware, unfortunately, normally it is a completely different matter when trying to downgrade .
Sparkrite said:
Bootloader unlocking is not needed for upgrading official firmware, unfortunately, normally it is a completely different matter when trying to downgrade .
Click to expand...
Click to collapse
So, it seems that I really need Huawei help to do something more or less useful for me. They made something such a "unhackable" phone which can be hacked only with their support. And more or less every other vendor I assume.
Quite weird I think.
AFAIK Huawei are/were the only vendors that made it so easy to unlock the BL, esp. when their code generator was online.
Have you heard back from them yet, some people report getting the code within 12 hours ?
Sparkrite said:
AFAIK Huawei are/were the only vendors that made it so easy to unlock the BL, esp. when their code generator was online.
Have you heard back from them yet, some people report getting the code within 12 hours ?
Click to expand...
Click to collapse
I got a first mail the day after I wrote, with them asking to add the reason for the code request.
This morning I answered them them that I wanted to play with root rights & custom rom, and that I was aware of the risks implied.
now (6 hours later) they sent me the code.
Quite a good support I'd say
ModNoob33 said:
I got a first mail the day after I wrote, with them asking to add the reason for the code request.
Click to expand...
Click to collapse
Yes indeed, the reason why, as I said in my first post, wonder why they're interested ?
Sparkrite said:
You now have to contact Huawei and request it, providing IMEI, SN, Product Code, Model, and reason why you wish to unlock it.
Click to expand...
Click to collapse
Any way you have it now, I assume it worked OK.
The product id in a custom firmware is the same as de original firmware?
i use this method to see product id *#*#1357946#*#* but in a custom firmware,because i lost the code but only want to save it,try the unlock page but i dont get code only errors.
Cientista2018 said:
The product id in a custom firmware is the same as de original firmware?
i use this method to see product id *#*#1357946#*#* but in a custom firmware,because i lost the code but only want to save it,try the unlock page but i dont get code only errors.
Click to expand...
Click to collapse
Try here for your product code :- www.imei24.com
well they dont give anymore codes for bootloader... my huawei p8 lite RIP
djokagg said:
well they dont give anymore codes for bootloader... my huawei p8 lite RIP
Click to expand...
Click to collapse
u sure there's absolutely no way?
AcidCat said:
u sure there's absolutely no way?
Click to expand...
Click to collapse
i'm struggling with the same issue. UK support doesn't want to give me the unlock code even if my P8Max is blocked on all google related stuff. I can't even get Google services
after the last OTA update ( DAV-703LC233B226 ) installed anymore. But still they persist that I should send back the unit ...
You can unlock your bootloaders by using DC Unlocker.