Develop Bugs

[ROOT](11-17-12) Root Nexus 10 with CWM and SuperSu Zip (Stress Free and Simpler)

{
"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"
}
Updated 11-17-12: Now that we have a stable CWMR image thanks to damien667 this procedure should be a lot less risky and less stressful!
This is confirmed working but due to the procedure involved is risky! The standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your tablet by following this procedure!​
You must unlock the bootloader before performing this procedure!
Credits: Kidgoo for testing and coming up with the method, thanks to damien667 for the fixed CWM images, and Chainfire for the SuperSu zip and binaries!
Before you begin make sure you read and reread the procedure and fully understand the directions.
1. Download the CWM-SuperSU-v0.98.zip
2. Download damien667's fixed CWMR 6.0.1.6 touch version of from here
3. Connect the Nexus 10 to your computer
4. Flash the CWMR image you downloaded in step 2 using fastboot
Code:
fastboot flash recovery /path/to/<recovery>.img
fastboot reboot
5. Touch "Install from SD Card" in CWMR
6. Select CWM-SuperSU-v0.98.zip that was downloaded in step 1
7. Let CWM-SuperSU-v0.98.zip install
8. Select "Reboot System"
9. Enjoy your rooted Nexus 10 !
To keep your custom recovery installed permanently and not get overwritten by the stock recovery when your reboot your tablet delete the following:
Code:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p

Reserved

works! thank you very much!

Awesome!
Now, if only we could code it so it does it all for us!
1-click and go! Im afraid ill fat finger something and have a $550 paper weight :'(
Thanks for the write up!

WannaB101 said:
Now, if only we could code it so it does it all for us!
1-click and go! Im afraid ill fat finger something and have a $550 paper weight :'(
Thanks for the write up!
Click to expand...
Click to collapse
One-Klick CWM Tounch + SuperSU would be great!!! :good::good::good:

So what am I supposed to do if ADB doesn't recognize the "sideload" command?

gravis86 said:
So what am I supposed to do if ADB doesn't recognize the "sideload" command?
Click to expand...
Click to collapse
You will need to download the latest vesion of ADB included in the Android SDK, which can be found here.

Perhaps a video?
Perhaps you could provide a video to help us along?

shimp208 said:
You will need to download the latest vesion of ADB included in the Android SDK, which can be found here.
Click to expand...
Click to collapse
Yep, my ADB was out of date... Thanks!

Got the latest version of ADB?

With regard to downloading the CWM-SuperSU file (for sideloading) do you mean that it should be downloaded on the tab itself, or downloaded into the same folder as adb and fastboot?

WannaB101 said:
Perhaps you could provide a video to help us along?
Click to expand...
Click to collapse
If my Nexus 10 had arrived yet then I would be more then happy to post a video until then you'll have to make due with the written guide I'm afraid . But if you or any one else has any questions regarding the procedure feel free to ask!

shimp208 said:
If my Nexus 10 had arrived yet then I would be more then happy to post a video until then you'll have to make due with the written guide I'm afraid . But if you or any one else has any questions regarding the procedure feel free to ask!
Click to expand...
Click to collapse
I hit ya with a question above...

joeski27 said:
With regard to downloading the CWM-SuperSU file (for sideloading) do you mean that it should be downloaded on the tab itself, or downloaded into the same folder as adb and fastboot?
Click to expand...
Click to collapse
If you download it on your tablet you'll need to then place the downloaded zip on the root of the internal storage (I.E not in a folder). Alternatively you can download it using a computer and connect your tablet to the computer and transfer it to the root of the internal storage that way.

I know this is probably a noob question but the fastboot commands (the first two, for booting from CWRT) -- should they be done in Fastboot Mode or can they be done while Nexus 10 is on and at home screen with USB debugging enabled? If you need to be in Fastboot Mode, how do you get there with Nexus 10?
Thanks!

shimp208 said:
If you download it on your tablet you'll need to then place the downloaded zip on the root of the internal storage (I.E not in a folder). Alternatively you can download it using a computer and connect your tablet to the computer and transfer it to the root of the internal storage that way.
Click to expand...
Click to collapse
Ok, the problem I have now is while I have the files on my tablet, I cannot move them to the root of the internal storage at this point...??? Suggestions??? Don't you have to be rooted in order to do this???

For some reason when I'm not in fastboot mode, I can use adb (adb devices lists my Nexus 10), but when I'm in fastboot mode, adb no longer recognizes the device. fastboot devices does however see it when in fastboot mode.
Anybody else have this problem or know why this might be happening? Thanks!

I'm still getting the sideload error after updating the ADB
Any insight, please?

So to others who are working on this and awaiting responses from the OP, where exactly have you placed the downloaded files on your tablet? specific locations?? and if so how did you get them there? I'm totally lost at this point, LOL, hoping to get some clarification soon...

Worked ... however .. you DO have to be in FASTBOOT already (power + Vol UP + Vol DOWN) - yeah it might be obvious when you're not tired as hell - but for those wondering
The first line should be:
fastboot boot /path/to/<recovery>.img
no fastboot reboot was needed - it rebooted itself.
I had a HELL of a time finding the sideload entry in CWM (that's just my brain deadness).
You have quite a bit of time More than enough.
THANK YOU!

[ROOT / TWRP][D851 ONLY][OSX/Linux/Windows] Root/TWRP your TMO G3 with PurpleDrake!

Howdy all!
What's this? Read on, dear reader, to discover the magic that is PurpleDrake.
{
"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"
}
What is this?
This is a utility to easily root your LG G3 (specific models only). It's a fairly foolproof script that includes all the dependencies you'll need for getting your phone rooted easily.
This is the FULL version. This means that it will automatically root, and ask you if you want TWRP installed and a custom boot that doesn't trip the root checker!
Click to expand...
Click to collapse
Who made this?
This root is a collaboration between myself (IOMonster), jcase, and autoprime.
Special thanks also to beaups for some initial guidance looking at the vulnerable application.
Thanks to @Shelnutt2 for the security-disabled boot.img
Thanks to @Dees-Troy for the TWRP image!
Click to expand...
Click to collapse
Is my phone compatible?
The new LG G3 models each are slightly different with regards to rooting and unlocking.
To see a matrix of which LG G3 phones are compatible with this root, please see this Google Docs spreadsheet that we've compiled.
When you run this program, your phone will reboot and run a test to see if it's compatible. If the application succeeds, it'll let you know that it's able to permaroot you. If not, it'll fail gracefully and reboot you back to normal Android without having changed anything.
Please note that this version is currently only compatible with the T-Mobile D851 version of the LG G3. For other phones, we suggest you look for the LITE version of PurpleDrake.
Click to expand...
Click to collapse
How do I use this?
WE NOW SUPPORT WINDOWS! YAY ME
To start, for either platform you'll need to scroll down to the download section and get the file.
Ensure that your phone is in ADB mode (PTP Mode for everyone but Verizon. Verizon users need to be in "Internet"/"Ethernet" mode)
Linux Instructions (in a terminal!)
Extract the file you downloaded...
tar xvf ~/Downloads/PurpleDrake-TMO_VERSION.tar.gz
Mark the application as executable, and run it!
cd PurpleDrake-TMO
chmod +x purpledrake_linux.sh
./purpledrake_linux.sh
OSX Instructions (just a bit easier)
Extract the file you downloaded
Double-click on "purpledrake_osx"
Windows Instructions
Extract the file you downloaded
Double-click on "purpledrake_windows"
The application will guide you through all the steps you need.
You will still need to install SuperSU from the market after installing PurpleDrake. This pack does not include one.
If you choose to install the custom boot.img, your phone's root checker will not be tripped and your phone will show as UNROOTED.
After, be sure to check @autoprime's post for how to disable OTA upgrades! here : http://forum.xda-developers.com/showpost.php?p=54254111&postcount=2
Click to expand...
Click to collapse
But, what if I don't want to run your script to root?
Well then, I'd be a little hurt, but you can still do everything the script does manually.
Download the package, and extract it. Open a terminal in the main folder of the archive and run these commands:
Code:
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
That will perma-root you, however there's no protection from doing something stupid or the phone being incompatible. Please be careful!
Click to expand...
Click to collapse
Where do I get this?
WINDOWS/OSX/LINUX VERSION OUT NOW!
- Fixed Windows support
- Fixed OSX ADB issues not detecting phone first try
- Fixed race conditions leading to errors permarooting
- Added 64-bit Linux ADB
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-TMO_R03.tar.gz[/url]
Old version here... (OSX/Linux only)
Code:
[url]http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-TMO_R01.tar.gz[/url]
Please DO NOT mirror or re-upload the PurpleDrake software to your own site, or any other file host.
If you need drivers for Windows (thanks @autoprime for having these handy!):
Verizon Drivers: http://downloads.codefi.re/autoprime/LG/LG_G3/LG VZW_United_WHQL_v2.14.1.exe
Everyone Else: http://downloads.codefi.re/autoprim...leDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe
Click to expand...
Click to collapse
Help, it doesn't work!
Post here, let us know what happened and we'll try to help you. DO NOT private message us on XDA or on IRC asking for help. We will not assist privately.
Most questions if not answered here can be answered on #lg-g3 on IRC in Freenode.
Click to expand...
Click to collapse
Thanks so much! How can I show my appreciation?
Since this was a collaboration project, proceeds that are made from this root will be split between amongst us so we can purchase a Sprint test phone to root (as it's currently not rooted).
If you'd like to donate to us, click the "Donate to me" button on the left sidebar under my name, and be sure to enter a comment to let us know that you're donating towards the PurpleDrake project.
Thanks again!
Click to expand...
Click to collapse

FAQ:
Q: I'm running the Windows .bat as administrator and it's closing/not working.
A: There is no need to run the .bat as admin. Just double-click and run.
Q: I get the "Windows cannot find '.\assets\windows\bin\mintty.exe'." error.. watdo?
A: Try just double-clicking on the .bat instead of running as admin.
Also make sure the script is extracted properly first before running.
Q: I [used Flashify and] am stuck in fastboot.. how can I get out?
A: Be cautious using Flashify as it seems it's not working right.. or people are hitting the wrong buttons with it.
HERE are the stock TMO D851 partitions.
Use fastboot to flash recovery(TWRP or stock) and stock boot. This will install TWRP and fix booting into rom.
If on Windows you will need fastboot drivers. Use Google to find fastboot binaries and drivers.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
The commands to flash TWRP manually instead of using flashify is below.
Place TWRP on the root of your internal /sdcard/ using MTP, downloading it directly to phone or using ADB push.
Code:
adb push name_of_file.img /sdcard/
adb shell
su
dd if=/sdcard/name_of_file.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Disable OTA:
Open LG Hidden Menu (3845#*851#) --> WLAN Test --> OTA Setting --> OFF
*Replace "851" with your devices model number, 850, 852, 855 etc...
The first D851 update has been released (10M). Bootloader remained unlocked. It would appear future OTAs will be safe to take AS LONG AS YOUR PHONE IS NOT MODIFIED! If you have flashed TWRP or installed xposed or modified /system then you need to restore any changes made or flash stock firmware (tot/kdz) before taking OTA.
If using a non-tmobile g3 I would be hesitant about taking OTA updates. An OTA may update the boot stack to block Bump!
EFS Backup:
Code:
[FONT="Arial Narrow"][B]Backup EFS after jailbreaking your G3. EFS is split into 2 partitions modemst1 and modemst2.
img files will be on root of internal sdcard. Save the .img files somewhere else besides the sdcard... email, cloud, etc..[/B]
DO NOT FLASH OTHER PEOPLES EFS OR FLASH YOUR OWN BACKUPS ONTO ANOTHER PHONE.
THIS WILL BREAK EFS ON THE PHONE YOU ARE FLASHING TO. EFS BACKUPS ARE FOR THE PHONE THEY CAME FROM ONLY.
I have made a new thread on EFS backup and restore which can be found [URL="http://forum.xda-developers.com/lg-g3/development/efs-lg-g3-efs-backup-restore-t2907329"]HERE[/URL].
[/HIDE]
[B][SIZE="5"]Restoring Stock / Remove root flag:[/SIZE][/B]
[HIDE]
Download the tmo .tot file and use lg flash to restore it to stock. itll format everything on internal sdcard so backup anything u may need off it.
T-Mobile firmware can be found [URL="http://downloads.codefi.re/wolfgart/LG_G3/D851"]here[/URL]. Thanks to [user=608699]@wolfgart[/user] for the files and [user=1157052]@thecubed[/user] for codefire hosting.
*Step by step picture guide - [url]http://imgur.com/W83hMPE[/url]
install the drivers.
put phone into Download Mode (power off. unplug USB. pull battery. put battery back in. press/hold Volume Up then plug in USB cable.)
In Windows Device Manager set the phones serial COM port to #41. (*see picture guide for help)
Install [URL="http://downloads.codefi.re/autoprime/LG/LG_G3/Setup_LGFlashTool_1.8.6.527.zip"][B]LG Flash[/B][/URL]. In "C:\LG\LG Flash" folder delete megalock dll. Replace with .dll below.
new megalock dll - [url]http://bit.ly/1cQADXm[/url] (this site includes a "download manager.. UNCHECK THE BOX before downloading dll file.)
Run LG Flash in the "C:\LG\LG Flash" folder. Select korean factory if asked.
When LG Flash opens you will see a box to select firmware and dll.
Select [URL="http://downloads.codefi.re/autoprime/LG/LG_G3/LGUP_8974.dll"][B]LG Flash .dll[/B][/URL]
Select (.tot)
Hit OK (*see picture guide for help)
Hit yellow start button. If you get Milkyway error click ok. LG Flash will then run a crc check on the tot file. Takes a bit.
After crc check finishes unplug the phone. plug phone back in. it should now be seen in LG Flash and start flashing.
Phone will reboot when finished. You may end up on a screen with s "2"... let it sit there for a minute or two.
If stuck on "2" try unplugging the usb cable from the phone.. wait 10 seconds.. then plug the usb cable back in. now wait 30 seconds and hopefully it changes to a "3"
Once the phone says "3" you can unplug the USB.. remove the battery and plug back in.. boot back up... you are now 100% stock.
[/HIDE]
[B][SIZE="5"]PurpleDrake YouTube Videos:[/SIZE][/B]
[HIDE]
[url]https://www.youtube.com/watch?v=wJtz51KgxjM[/url]
[/HIDE]

And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855

Tectas said:
And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855
Click to expand...
Click to collapse
Hoax? What?
This pack is ONLY for the T-Mobile G3 which has an unlocked bootloader out of the box.
D855 support is NOT included in here. There will be a separate thread when we have an unlock for the bootloaders of the rest of the G3 family.

Tectas said:
And where is the bootloader unlock talked about at the bounty thread or was it just a hoax?
Gesendet von meinem LG-D855
Click to expand...
Click to collapse
There is no boot loader unlock..where ever you read this is misinformed...the T-Mobile variant ships boot loader unlocked, it is the only one so far to be shipping unlocked.

Sweet

thecubed said:
Hoax? What?
This pack is ONLY for the T-Mobile G3 which has an unlocked bootloader out of the box.
D855 support is NOT included in here. There will be a separate thread when we have an unlock for the bootloaders of the rest of the G3 family.
Click to expand...
Click to collapse
I'm aware of that and sry it wasn't meant offensive or to put this one down, autoprime, did imply at the bounty thread, that you as well managed to unlock the bootloader, at least at the beginning, that's what I'm referring to, sry that i said it the wrong way, was a bit disappointed, which for sure isn't your fault or the one of this tool, it's still great progress you made.
Gesendet von meinem LG-D855

I wish the international G3 D855 will be unlocked too
Sent from my LG-D855 using XDA Premium 4 mobile app

Great glad to see this released thank to all that is involved
LGG3 and beyond

All my family is sleep in the room with my Mac will be running asap bright and early. Thank you for your hardwork

Thecubed, autoprime, shelnutt2, jcase, and whoever else....thanks for this. Truly appreciated! Can't wait for Windows support. :Cheers:
Sent from my LG-D851 using XDA Premium 4 mobile app

Plans to support recovery for D855 in the near future?
Need to know to sell or not the G3 ?

What the hell software compatible with a mac that's a 1st whoop whoop well done guys and thanks for the hard work

Yeah great time to be a Mac owner

I have a feeling this treads about to turn in to a "when will this version be supported" topic :/
LGG3 and beyond

Success!
1. THANK YOU!
2. It didn't work the first time around, temproot worked but permaroot did not. Maybe it had to do with the fact that I was reading this forum while it was waiting for my input... I can't see how that would have made a difference but whatever. [[ Edit: It worked the second time running, I just followed the instructions immediately - no problems. /Edit ]]
3. Just a reminder for Linux users ... you have to add udev rules as described here: http://developer.android.com/tools/device.html ... and when you are done with that, also run:
$ sudo service udev restart; sudo killall -9 adb
4. My G3 would only connect to my laptop (Ubuntu 14.04) when it was in PTP mode. MTP or Charge Only did _NOT_ work... Only PTP.
5. THANK YOU AGAIN! You devs rock!
Frank.

Same as the guy above didn't work the first time but worked perfect the second! OSX here.

@ OP
http://forum.xda-developers.com/lg-g3/general/s-carrier-specific-g3-threads-t2818549

I keep getting no such file or directory, going to re download drivers and see

@thecuba not telling you what to do but maybe put this on T-Mobile thread as well http://forum.xda-developers.com/tmobile-lg-g3/development
Hope you don't take it the wrong way

Reverting back to Fire OS from CM11

Hello All!
I decided to install CM 11 a few days ago and then thought I'd like to go back to Fire OS. I followed the instructions as much as I could from the thread on here to revert back but I have ran into a problem. I could only get 4.6.1 installed but obviously, 4.6.3 is out and my phone can see it's there to download (and it does (try to) download - every time I restart my phone). When the download finishes the phone says there is an error and it can't update but then I can search for the update and so on. I have tried doing it the way Amazon suggest from my PC but to no avail.
I can only assume that this has something to do with the fact I went from 4.6.3 to CM 11 and then back to 4.6.1 and the phones still sees itself has partially being on 4.6.3?
Any help is much appreciated!
Thanks

doing it the way Amazon suggest from my PC but to no avail
Click to expand...
Click to collapse
That means you downloaded the 4.6.3 BIN image and tried sideloading it via ADB?
If not, take a look at this (scroll down to the paragraph "Recovery / Sideload Factory Images")
I think OTA update is useless at this point but using the Amazon stock recovery is very reliable, I used it many times in the beginning for testing purposes.
Just give us some details when you encounter problems, e.g. driver missing when connected to PC, etc. ... and don't forget your backup for important apps & app settings.

I tried doing this before and the CMD does not show as any devices being connected. I have it in debugging mode and plugged it in but Windows did not see it even though the phone shows as being connected. Also, just in case I tried using the command you send and it just says "* cannot read 'update.bin' *".

You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"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"
}
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":

It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one which also needed updating which I have just done and appears to now let the cmd see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now. I will post my results once the update has finished.
Also, thanks for the help with this. Your information did help and with a bit of tweaking, it appears to have worked.

Thanks for mentioning so early that you use Windows 10, that makes it so much easier for me. :laugh:
Nah, but it looks like you will be good from here on out...
Btw. by sideloading the image, it will erase "everything" on your device, so you get clean system without leftovers, just like you hoped for.

Can you add the link for the thread you used to revert back from CM11 to FireOS?

paulalva05 said:
Can you add the link for the thread you used to revert back from CM11 to FireOS?
Click to expand...
Click to collapse
The link is actually in the first reply but I have put it below anyway!
http://forum.xda-developers.com/showpost.php?p=61271723&postcount=2

Bingo Bronson said:
You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":
Click to expand...
Click to collapse
Hi, thank you for the detailed instruction. My pc can recognize and show the name of my firephone, just like what you showed in the image. But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.

iHuyou said:
But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.
Click to expand...
Click to collapse
Validate the MD5 checksum, maybe your downloaded image is corrupted...

Is the update.bin file in a different directory?

Bingo Bronson said:
Validate the MD5 checksum maybe your downloaded image is corrupted...
Click to expand...
Click to collapse
Hi, Bingo Bronson, thank you for your reply. What I downloaded from the link in your original post is a WinRAR ZIP archive. When I open it, there are multiple file and folders in there. There is a file called boot.img, should I change its name to update.bin and sideload it? But it is only 8Mb. Can you give a little more detailed instruction? Thanks

iHuyou said:
[...] is a WinRAR ZIP archive. But it is only 8Mb. Can you give a little more detailed instruction? Thanks
Click to expand...
Click to collapse
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
edit: Slight misunderstanding, luckily iHuyou found the solution by himself. :victory:
This is the direct download link from Amazon for the latest GSM unlocked version: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
An here is the direct download link from Amazon for the latest AT&T version: http://fire-phone-updates.s3.amazon...HC5/update-kindle-32.4.6.5_user_465000520.bin
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:

Bingo Bronson said:
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:
Click to expand...
Click to collapse
Thanks again, Bingo Bronson. I figured it out. The bin file has to be in the same directory as the adb file, otherwise adb cannot find the bin file therefore cannot read it. I have successfully sideloaded 4.6.5 following your post. Thank you!

Blank Screen amazon fire phone
Hello Guys i need help with my amazon fire phone, I tried to revert back from cm11 to stock rom (http://www.android.gs/downgrade-amazon-fire-phone-to-stock-fire-os-3-5/) using this site's method i got error sideloading from stock recovery then i tried it from safe strap recovery and it went successful but before sideloading update.bin from safestrap recovey i wiped and i did not know what options i selected but now my fone wont boot only black screen and when i connect it to pc it shows 3,4 partitions and says format, format... what went wrong ?

[SOLVED] Need help rooting I747M

Original Post
Hello, I am running an unlocked Bell S3 (SGH-I747M/d2can, hope this is the right forum) on 4.4.2 official Sept. 2015 update. Screenshot shows the build info.
{
"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"
}
I had a similar issue with my Skyrocket, although I was able to root it with Saferoot.
I have a MacBook on Yosemite and a Windows Vista PC (don't hurt me). Windows fails to cooperate with any drivers I install on it if they install at all. All I can get is the file transfer. JOdin3 can recognize it, but gives me libusb error -12. It just won't work. Odin..... Nope.
On my Mac, I have access to ADB and file manager. But there are no root tools for Mac.
On the S3 itself, I tried Towelroot v2, Saferoot, Framaroot, Kingo, ActiveRoot, MotoChop, that odd Chinese one, and more. They all failed.
I'd be more than happy on rooted stock, I was rocking that on my Skyrocket (pun intended) for a good 2-3 months, though I would prefer a custom ROM.
Sorry if this has been asked before.
Edit: I managed to get the drivers working by myself after reading about the registry issues.
I had an issue with a partial installation that the installer (or the computer) didn't like. Here is how I fixed it:
Manually reinstalling the Samsung USB Drivers (Windows)
First, open the file explorer (Pro tip: Hold the start button and press E) and in the address bar, type C:\Program Files\SAMSUNG\USB Drivers. If you see Uninstall.exe, right-click it, Run as Administrator, let it uninstall, and you can skip 7-10. Lucky. Otherwise...
Download 7-Zip and install it. I suggest 15.xx beta, the 9.xx is old.
Download the official universal USB driver from Samsung. Don't open it yet.
Now, find the driver ZIP file. This is most likely going to be in your Downloads folder as SAMSUNG_USB_Driver_for_Mobile_Phones.zip
Right-click on it and find 7-Zip > Open Archive...
Drag the file to your Downloads folder, and close 7-Zip.
Right-click on the EXE file with the similar name as the ZIP and do 7-Zip > Open archive...
Hit Extract and it should extract to a directory with the same name.
Open that folder and find the Uninstall.exe and Uninstall_1.exe.
If you're on a 64-bit installation, right click Uninstall_1.exe and select Run as Administrator. Otherwise, choose Uninstall.exe. (Google the way to find it if you are not sure).
Let it uninstall.
Now go back to your Downloads folder and right-click SAMSUNG_USB_Driver_for_Mobile_Phones.exe and Run as Administrator. This installation seems to take a very long time for some reason, don't panic.
Once that is done, you (hopefully) have drivers now! Plug in your phone and you should see "Installing driver software..." and it works!
Click to expand...
Click to collapse
Sent from my SGH-I747M using Tapatalk

You need to be in download mode on the phone, connect it to vista machine, launch Odin, flash twrp from Odin, boot into twrp, flash supersu from twrp, and you will have a rooted stock rom.

audit13 said:
You need to be in download mode on the phone, connect it to vista machine, launch Odin, flash twrp from Odin, boot into twrp, flash supersu from twrp, and you will have a rooted stock rom.
Click to expand...
Click to collapse
No, I can't get Odin to recognize my S3 (or my Skyrocket) in download mode. I tried.
Thanks, though.
Sent from my SGH-I747M using Tapatalk

Does it show up as an unknown device?

audit13 said:
Does it show up as an unknown device?
Click to expand...
Click to collapse
I get nothing. It doesn't see it.
Drivers are not working right or something. I installed Samsung drivers but, even still, each time I plug in my phone it asks to install drivers.
Sent from my SGH-I747M using Tapatalk

Tried different USB cables and USB ports? Doesn't even show up as a device in OS X?

audit13 said:
Tried different USB cables and USB ports? Doesn't even show up as a device in OS X?
Click to expand...
Click to collapse
Yes, yes.
OS X has ADB access and file access, but JOdin3 won't recognize the thing, and when I start it I get a message saying that heimdall-mac.dmg has no mountable filesystems or something.
Sent from my SGH-I747M using Tapatalk

What about running win7 in VMware? Or getting access to a win7 machine to try it out?

audit13 said:
What about running win7 in VMware? Or getting access to a win7 machine to try it out?
Click to expand...
Click to collapse
Can't afford a Win7 disk. But I may be able to try a friend's computer.
Sent from my SGH-I747M using Tapatalk

I ran into the same issue last night trying to root mine.
Win 7 would not install the correct drivers for my S3, I installed kies 3 just for the heck of it, and after that it picked up the correct driver for the S3. After that Odin picked it up right away after plugging it back in and I was able to flash TWRP on it. I installed Kies 1 first. Then Kies 3.
Give it a try, see if it works for you, I spent all day yesterday trying to get TWRP on it.
Good Luck!

Rooting I747m
I know it's answered, but here we go.
1. Flash TWRP.
2. Flash CF Auto-Root.
3. Flash TWRP again.
Done.

The i747m can be rooted by:
1) flashing cfautoroot without TWRP;
2) flashing TWRP, flashing supersu from TWRP; or
3) flashing TWRP, flashing custom rooted ROM from TWRP.

How To Guide Simple Guide How To Root

Alright so a lot of people seem to have issues with rooting their device and creating a lot of spam on this forum because they don't know how to read.
This guide is for Windows PCs and will be for the people who don't want to read complicated guides.
What you Need:
A Device that has an unlocked Bootloader
The Factory Image of the ROM you are using or updating to Download Here
The Latest STABLE Magisk Download Here, if you are opting for a Beta/Canary then have fun.
7-zip or similar file extractor
ADB and Fastboot, I use Minimal ADB and Fastboot but this Script Here will download the latest version and add it to your PATH.
Way to Transfer Files to Phone (USB Cable?)
Steps:
Update to the Latest ROM. This can be done via Sideloading (personal preference) or OTA
Confirm you are on the same version as the factory image. Current is SP2A.220305.013 aka March 2022 Update
Extract the Zip File to a Folder. Current filename is raven-sp2a.220305.013.a3-factory-87b3bf0a.zip
Go in to the folder and extract the Image ZIP into a Folder. Current Name is image-raven-sp21.220305.003.zip
Find the Boot.img and transfer it to your device.
Install the Magisk Manager APK on the Device
Open Magisk and press Install.
Select "Select and Patch a File" and select the Boot.img you transferred to your device.
Magisk will patch the file and place the new .img file in your downloads. The filename will look like "magisk_patched-24300_abcde.img".
Transfer the patched file from your Downloads folder to your PC.
Reboot your phone to Fastboot mode Youtube Tutorial
Locate the patched .img file and press SHIFT+RightClick, click the option "Copy as Path"
On your PC open Command Prompt. If you dont know how to do this, you shouldn't be rooting your device.
In command prompt type "fastboot flash boot" and then paste the location of your patched .img file.
The whole command should look like "fastboot flash boot "C:\Users\Admin\Downloads\magisk_patched-24300_abcde.img"
Reboot the phone with the command "fastboot reboot"
Once the device is booted up, go to Magisk and see if you are rooted.
If there is enough demand, I can provide photos to help.
If I messed up along the way, let me know and I can change the guide.

Saved

{
"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"
}
I can't find my Downlaods folder. Idk what that is.

Gytole said:
View attachment 5574243
I can't find my Downlaods folder. Idk what that is.
Click to expand...
Click to collapse
Fixed lol

vassosman said:
Alright so a lot of people seem to have issues with rooting their device and creating a lot of spam on this forum because they don't know how to read.
This guide is for Windows PCs and will be for the people who don't want to read complicated guides.
What you Need:
A Device that has an unlocked Bootloader
The Factory Image of the ROM you are using or updating to Download Here
The Latest STABLE Magisk Download Here, if you are opting for a Beta/Canary then have fun.
7-zip or similar file extractor
ADB and Fastboot, I use Minimal ADB and Fastboot but this Script Here will download the latest version and add it to your PATH.
Way to Transfer Files to Phone (USB Cable?)
Steps:
Update to the Latest ROM. This can be done via Sideloading (personal preference) or OTA
Confirm you are on the same version as the factory image. Current is SP2A.220305.013 aka March 2022 Update
Extract the Zip File to a Folder. Current filename is raven-sp2a.220305.013.a3-factory-87b3bf0a.zip
Go in to the folder and extract the Image ZIP into a Folder. Current Name is image-raven-sp21.220305.003.zip
Find the Boot.img and transfer it to your device.
Install the Magisk Manager APK on the Device
Open Magisk and press Install.
Select "Select and Patch a File" and select the Boot.img you transferred to your device.
Magisk will patch the file and place the new .img file in your downloads. The filename will look like "magisk_patched-24300_abcde.img".
Transfer the patched file from your Downloads folder to your PC.
Reboot your phone to Fastboot mode Youtube Tutorial
Locate the patched .img file and press SHIFT+RightClick, click the option "Copy as Path"
On your PC open Command Prompt. If you dont know how to do this, you shouldn't be rooting your device.
In command prompt type "fastboot flash boot" and then paste the location of your patched .img file.
The whole command should look like "fastboot flash boot "C:\Users\Admin\Downloads\magisk_patched-24300_abcde.img"
Reboot the phone with the command "adb reboot"
Once the device is booted up, go to Magisk and see if you are rooted.
If there is enough demand, I can provide photos to help.
If I messed up along the way, let me know and I can change the guide.
Click to expand...
Click to collapse
It should be fastboot reboot

fil3s said:
It should be fastboot reboot
Click to expand...
Click to collapse
Good call, I was writing this on the fly and wasn't actually doing it as I was writing the guide.

fil3s said:
It should be fastboot reboot
Click to expand...
Click to collapse
Rather than saying they don't know how to read", it might be that they don't understand the "meta-language" of any given discussion or explanation!

EdBurger l said:
Rather than saying they don't know how to read", it might be that they don't understand the "meta-language" of any given discussion or explanation!
Click to expand...
Click to collapse
Goodo bruh.

vassosman said:
Saved
Click to expand...
Click to collapse
Do you really think this guide is too hard to follow? It's thoughtful that you typed out the steps but is it really less confusing or difficult?
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com

Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.

.

dmarden said:
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
Click to expand...
Click to collapse
They are not required to change if you plan on running Magisk 24.3. I did not change anything when I updated my P6P (bought in Feb) and rooted it.

dmarden said:
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
Click to expand...
Click to collapse
not needed anymore with latest magisk

That's great news, I've been missing it.

I am going to do this on S3B1.220218.006 (QPR3 Beta 1.1). Fingers crossed!

Worked perfectly, the only thing I might add is a link to the Google USB Drivers (since they must've updated). I had them installed originally (to have unlocked my device in the first place) but needed to update them.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Thanks a ton! I would've never noticed that the wipe step was no longer needed.

I recognize I am replying a lot, haha... sorry about that.
Presumably the update method for this should work exactly like past Pixel devices, yeah?
For me, this method was as follows:
1. Download the full image and edit the script to remove the "-w"
2. Install the modified image
3. Boot up once
4. Then basically follow the original procedure from this thread again
I know on OnePlus devices I was always able to uninstall Magisk root via the Magisk app, take the OTA, then reinstall Magist root via the Magisk app before rebooting, but that never seemed to work on Pixel devices (at least for me).

Just to share...
I decided to give the Magisk restore images, OTA, install again before reboot method a try and it worked perfectly going from QPR 1.1 to 2.

Thank you for this post. I would like to root my phone. I am a noob and it’s a little intimidating. If you would add pictures, I for one, would really appreciate that. Thanks again!