Related
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Thanks, this worked for me. However, it does not re-lock the bootloader. You can tell by when the Google logo is on the screen while booting up, if there is an unlocked lock on the bottom then it is unlocked. To fix this, type in:
flashboot oem lock
Click to expand...
Click to collapse
After that you should be good to go again and be stock.
Why not use the 4.0.2 image? Makes more sense to use the latest version:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Zzim said:
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Click to expand...
Click to collapse
If you've got the SDK installed put the fastboot files in the sdk\tools or sdk\platform folder where adb is located. The adbwinapi.dll should be located in there.
Or just copy adbwinapi.dll into the same folder where you have the "restore kit" files downloaded from the OP.
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
error
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
djeddieone said:
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
Click to expand...
Click to collapse
cerotes have galaxy nexuses? hrm
mikedfromaz said:
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
Click to expand...
Click to collapse
Winzip.. unzip it twice...
Sent from my Galaxy Nexus using XDA App
edit: got it thanks
Thank you for the script..i know it will come in handy one day or another!
Sent from my Galaxy Nexus using xda premium
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
bigeric828 said:
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
Click to expand...
Click to collapse
It was zipped with WinRAR as a standard zip file. Should be able to be opened on just about anything... Have you tried redownloading?
oops already posted this but i put it in the wrong thread but here it is again sorry.
does anyone know how i can get this working? whenever i run it i just get an error: device not found
waiting for bootloader...
flashing bootloader...
error cannot load "bootloader-toro-primek10.img"
<waiting fo device>
anyone suggestion? ive tried reinstalling the drivers and its still not working
any help is appreciated thanks
so.....how do we run the script? with fastboot? with what commmands? it's late, i'm tired and i just want to start from scratch on my GNex...had Wallet running, then loaded BB, lost Wallet, now wallet won't run on ANY rom i have, even rebuilt to 4.0.2, but need to get back to 4.0.1...i posted a question in the Q&A section if there was an ODIN of 4.0.1 lying around somewhere....hopefully i'll get some help either way...
thanks.
EDIT...got it, double click the bat file...the original post did not say that.....thanks for the last post for mentioning it
|Jason8| said:
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Click to expand...
Click to collapse
Having seen the Nexus S sticky for factory firmware etc., I think its time we see this or another post evolve into the same sort of thing including full restores for 4.0.1, 4.0.2 and the eventual 4.0.3(lte) radio's etc.,
Here's a modified script that will allow you to choose between 4.0.1 and 4.0.2. (as long as you have either image or both) It also has the option to re-lock the bootloader.
I'll also update it when the official 4.0.3 images are released.
I don't take no credit for what was already done, I just modified it
{
"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"
}
Instructions:
=========
1- Extract folder with contents of this package.
2- You will need the Google Factory image for the version you want to restore, or both if you want.
3- Extract the image files to the same folder in step one. Image files should not be in a seperate folder!
So you should have, in one folder, the above files contained in this package plus:
image-mysid-xxxxxx.zip (xxxxxx= pertains to what version)
radio-tor-i515.xxxx.img
radio-cdma-tor-i515.xxxx.img
flash-all.sh
bootloader-tor-primexxxx.img
4- Dbl click on GNexRestore.bat and follow the prompts.
Optionally, if you do have the Android SDK installed, just copy the image files and GNexRestore.bat to the platform-tools folder.
fastboot.exe will also be needed, if you don't have it already, just copy the one in this package to the same location.
Then run GNexRestore.bat
when you extraxt the factory image i get one file and the icon looks like a blank piece of paper. is that how it is suppose to be
When you extract the image, you should see a folder with the files you need.
e.g. this is from 4.0.2
{
"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!
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 ?
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.
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!