Updating to Android 6.0.1 G920AUCU3CPD6 Step by Step - AT&T Samsung Galaxy S6

Root is not required to update to PD6
Edit: @rahilm is saying the zip extension is not required, I can't verify but it's quite likely true, so you can just skip adding .zip to the file name.
Edit2: Thanks to @Red5, PC2 has a patch level of March, PD6 has a patch level of May. Also all links are still up as of May 6, 2016
Edit3: If links are broken, @Zero4 has posted mirrors here
Edit4: For those with dm-verity issues, download files 2 and 3, and use Odin to flash to BOJ7, instructions are in step 2.
Hey there guys, I haven't seen a full guide yet to update to PD6, from 5.1.1 (BOJ7 or 9) so I decided to make one. Of course none of this would be possible if the people in the other thread that found all the OTAs.
There are a few Marshmallow version for the 920A right now, PC2 (with a patch level of March and build date 2 months ago) seems to be the first one that Samsung shared with AT&T, while PD6 (with a patch level of May and a build date of Apr 29) is the most recent version.
Tools required:
1. ADB, download here, install with arguments Y, N, Y
2. Odin, get a clean version from Sammobile here
3. Get this if you are on Cricket firmware(BOJ6), or not on AT&T firmware BOJ9 or BOJ7 or facing dm-verity errors. Link to BOJ7
4. Get this if you are on AT&T firmware, but not on the most recent BOJ9 Lollipop firmware: BOJ7 -> BOJ9 OTA
5. Get this to update from Lollipop to Marshmallow: BOJ9 -> PD5 OTA
6. Get this to get to the newest most recent build of Lollipop PD5 -> PD6 OTA
This was tested on a Windows 10 64 bit machine.
1. Make sure you have all your stuff backed up! These steps will wipe your phone!
2. If you are on Cricket BOJ6 or facing dm-verity issues, use Odin to flash your phone to AT&T BOJ7, this is necessary before you proceed. If you are on BOJ9, skip to step 4. Do this by downloading file 2 and file 3, plugging in your phone to your computer, turning on Odin, turn off your phone, and enter download mode by pressing volume down, home and power together for a few seconds. Then you should see Odin say that a phone has been added, and a box on the top left becoming blue colored. Now extract the files from part 3, and press the "BL, AP, CP, and CSC" buttons in order, each time there will be a popup asking you to load a file, simply load the file containing the text in the button. eg, load the BL_G920AUCU3BOJ7_CL5927475_QB6773820_REV02_user_low_ship.tar.md5 file after pressing BL. Verifying the files may cause Odin to freeze, just wait a few minutes, and Odin will unfreeze. DO NOT TOUCH anything else, once all the four files are loaded, press start, and keep your phone plugged in.
Odin:
{
"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"
}
3. Wait for BOJ7 to finish flashing, and reboot. Now, open up CMD by pressing windows and "R" on your computer together, then typing in CMD.
Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip.
Now, open up CMD, and cd to the directory that you put this file in. By typing in "cd directory", in my case this would be "cd C:\Users\MYUSERNAME\Downloads"
Once in that folder, fire up ADB by typing adb in the command console, if it installed correctly it should print out a bunch of help. Once you get to the welcome screen on your phone, you can now shut the phone down, and enter recovery mode. Do this by pressing the volume up, home and power button together. Once you enter recovery, use the volume buttons to select apply update from adb, and use the power button to confirm.
In cmd, type "adb devices", it should show a random string if your phone is connected and adb is working. Now type adb sideload SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip wait for completion, this will take a while. Once this has completed, your phone will show the AT&T logo for around half a minute, and the welcome screen will show up again.
4. Shutdown your phone, and enter recovery mode by pressing volume up, home and power button together
Open up cmd, type in "cd directory" to go the the directory where you place the download, in my case it was "cd C:\Users\MYUSERNAME\Downloads", if you did not read step 3.
Rename file 5, and add a zip extension (make sure explorer has the show file extension option checked), it should now be called SS-G920AUCU3BOJ9-to-U3CPD5-UP.zip, type in adb sideload SS-G920AUCU3BOJ9-to-U3CPD5-UP.zip, this will take roughly 15 minutes, once completed and a reboot has happened, you may now turn the phone off again
5. Similarly to step 4, side load file 6
You are now on the most recent build of Marshmallow!
CMD and ADB on windows:
Edit: screen shot of PD6:

Also make sure to go in and turn on usb debugging between the different adb updates

Any drawbacks of not waiting for OTA? Samsung Pay still works using this, knox not tripped, etc?

Your data gets wiped, that's a big no-no for a lot of people, otherwise samsung pay still works and knox isn't tripped.
Also USB debug mode isn't required, as long as you boot into recovery mode.

Wanted to mention that you don't need to cd to directory. Just press shift + right click where your Ota files are located and click on "open command window here". Saves a minute or two since your command window is already showing the crrect directory.
Sent from my SM-P600 using Tapatalk

sand_bit said:
Your data gets wiped, that's a big no-no for a lot of people, otherwise samsung pay still works and knox isn't tripped.
Also USB debug mode isn't required, as long as you boot into recovery mode.
Click to expand...
Click to collapse
Thank you. Data backup/restore isn't an issue for me, just concerned about functionality so that addresses my concern.

Thank you. It work great

Is it possible to skip step 5 if I have the "SS-G920AUCU3BOJ9-to-U3CPD6-UP" file from another thread? Or best to go OJ9 to PD5 to PD6?
Sent from my Galaxy S7 Edge.

runner77 said:
Is it possible to skip step 5 if I have the "SS-G920AUCU3BOJ9-to-U3CPD6-UP" file from another thread? Or best to go OJ9 to PD5 to PD6?
Sent from my Galaxy S7 Edge.
Click to expand...
Click to collapse
OJ9 to PD6 has failed for most people when tried... the path that works is OJ9 to PD5 then PD5 to PD6.

Dante087 said:
OJ9 to PD6 has failed for most people when tried... the path that works is OJ9 to PD5 then PD5 to PD6.
Click to expand...
Click to collapse
I was able to upgrade from OJ9 to PD6 without any issues. I only ran into the issue with the open error, which I used a different computer and it worked.

ryguy2010 said:
I was able to upgrade from OJ9 to PD6 without any issues. I only ran into the issue with the open error, which I used a different computer and it worked.
Click to expand...
Click to collapse
That's good to know... I was on PC2 so I had to make the jump to PD4, then PD5 and PD6.

ryguy2010 said:
I was able to upgrade from OJ9 to PD6 without any issues. I only ran into the issue with the open error, which I used a different computer and it worked.
Click to expand...
Click to collapse
Thank you both for the replies.
Sprint guy here who sits next to a extremely frustrated AT&T S6 coworker/boss. He's been b!tching for months for the MM update. Just trying to make him happy.
Sent from my Galaxy S7 Edge.

sand_bit said:
There are a few Marshmallow version for the 920A right now, PC2 (with a patch level of May and build date 2 months ago) seems to be the first one that Samsung shared with AT&T, while PD6 (with a patch level of March and a build date of Apr 29) is the most recent version.
Click to expand...
Click to collapse
Just pointing out that you have your security dates backwards... PC2 has the March security patches, and PD6 has the May security patches.

Plz guys, why is it so complicated with G920A than all other G920xxx to upgrade to MM !!? I need an answer with hot thanks
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app

Hi, the link to the cricket one is dead.

sand_bit said:
Edit: @rahilm is saying the zip extension is not required, I can't verify but it's quite likely true, so you can just skip adding .zip to the file name.
Click to expand...
Click to collapse
Just a few minutes ago I went from BOJ9 -> PD5, then from PD5 ->PD6, both times WITHOUT adding .zip to the end. Great write up by the way, thank you for taking the time to put this together!
Tim

Any knowledge of the MM files for the ATT s6 Edge PLus? (g928A) Thanks.

Do I want PD6? How do I get there from PC2?
Should people on PC2 wait for a proper tar?

it worked with me very well, thanks a lot for making finally my G920A 6 MM. Good luck to our forum ( forum of genius)

LLStarks said:
Do I want PD6? How do I get there from PC2?
Should people on PC2 wait for a proper tar?
Click to expand...
Click to collapse
I think PD6 runs a lot smoother than PC2... also has the May security patch built in if you care about that

Related

[PROGRAM] Updated:One Click Root/UnRoot (Mac and PC)

Team,
This One-Click Root process will copy over the rooted-update.zip or unroot-update.zip file then reboot your phone. Follow the instructions in the CMD prompt that launches.​
Credits:
LeshaK at Samdroid: for the original rooted-update.zip.
gunnarhafdal : for creating the Mac GUI for my app.​
This has been tested on stock Android 2.1 Eclair only. If you rooted using another process you can use this process to unroot as long as you didnt load a rom that created links to busybox.
For the following models:
GT-I9000
Captivate SHG-I897
Vibrant SGH-959
GT-I9000M
Epic SPH-D700 (Untested but should work like other phones. Post with your results. This is harmless it will either work or it wont. It copies over 3 files to your existing build.)​
Rooting adds the following to your system and unrooting removes them:
/system/xbin/busybox (version 1.17.1)
/system/xbin/su
/system/app/Superuser.apk (version 2.3.1)
and links /system/bin/su to /system/xbin/su​
More will follow as they are released. PM me to add your Galaxy S Model.
Warning: I am not responsible for bricked phones, rooting can void your warranty....
PC Instructions:
{
"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"
}
Download the app: GalaxyS_One-Click_Root_All_Models-PC. Or down Below.
Watch the video for the full procedure on The Unlockr.
Video/Procedure Link Click Here
Requirements: Install Link: Dot Net Framework version 4
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. For Windows x86 and x64 systems make sure that the Samsung Drivers are installed. You can get them here.
3. Extract the contents of GalaxyS_Vibrant_One-Click_Root.rar to a folder.
4. Connect your phone to your PC via the USB cable and launch the file "T-Mobile Vibrant One-Click Root.exe" file.
5. Click the "One-Click Root" button. This will launch a command shell follow the instructions in the CMD window.​
Mac Instructions:
Download the app: OneClickRootMac. Or Down Below.
It requires Mac OS X 10.5 or higher.
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. Connect the phone to your computer.
3. Click one of the buttons depending on what you want to do.
4. After the phone has rebooted into recovery select "apply sdcard:update.zip" for I9000 and I9000M and choose "Reinstall Packages" for the US models using the volume keys and then press the home button for I9000 and I9000M and the power button on the right top side for US models to start the process.​
=====================================================================
Done! You are rooted.
=====================================================================
Un-Rooting Instructions:
To Un-Root follow the same instructions except click on the Un-root button. If you rooted using another process you can use this process to un-root as long as you didnt load a rom that created links to busybox. I would suggest to restore you phone back to stock ROM before even needing to unroot and if you are on stock un-root all you want otherwise what is the point of un-rooting.
=====================================================================
Getting Started with Android After Rooting:
Flash Clockwork Custom Recovery On your phone:
Follow this URL to find fill information on ROM Manager:
http://forum.xda-developers.com/showthread.php?t=734164
Install ROM Manager from Market.
Launch ROM Manager and click on Backup ROM and save you android O/S stock rooted making getting back to stock un-rooted much easier..
the simplest root just got simpler
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
junkdruggler said:
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
Click to expand...
Click to collapse
I'd say its easier to not mess up. Faster for sure, if you already have the drivers installed.
This is for our newer brethren or anyone else that want a straight forward root method. And for those having trouble entering recovery from the button presses. ADB is bundled in the rar file so you don't need Android SDK.
Another thing that will help most is when I add unroot to the app which I should have completed tomorrow.
Doon2 asked for it, so here it is.
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
s15274n said:
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
Click to expand...
Click to collapse
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
TGA_Gunnman said:
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well all most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
this
I am stoked that someone would take the time to make this program. I dont have immediate access to a PC(I use a mac) but an easy unroot program clinches the decision to root my phone. thank you for taking the time to make this much props
please do it for Mac OS.
best wishes...
Awesome application thanks!
Sent from my SGH-T959 using XDA App
Great, easy app. Works!
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
alsatea said:
please do it for Mac OS.
best wishes...
Click to expand...
Click to collapse
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
TGA_Gunnman said:
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
Click to expand...
Click to collapse
If you write it in java, then it will run any OS, right?
Relase src code. I may be able to port to unix/macosx and/or java.
I have Windows 7 installed through Bootcamp and it worked perfectly. Thanks
kelmerp said:
If you write it in java, then it will run any OS, right?
Click to expand...
Click to collapse
Ok Let me see what I can do.
Yeah release the source... Ports will follow if necessary
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
I know what you mean. I'm still used to holding down the buttons until the recovery screen pops up like on my G1. On the Vibrant, I have to remind myself to let go of the buttons as soon as the "Vibrant" screen comes up.
Yes, the overall process involved to use this program is longer, involves more steps, and, therefore, easier to screw up. Also, the fact that you have to download more than one file increases the chances of messing something up because of the possibility of corrupted files. Also, the "flash in recovery" method is OS agnostic, and technically doesn't even require a computer since you can download and rename the zip file right on your phone if you want to. Still, it's very easy to follow and would appeal to those who are new to rooting and don't feel comfortable with booting into recovery mode.
Updated the app to include unroot. Created a new update.zip file that will remove root. Also fixed the CMD shell launching minimized.
Lets see the java port. or even an APK to do so
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
Why fuss with button pushes, just enable debugging, plug in your phone, open a command prompt and type the following
Code:
adb reboot recovery
It's easier than messing with those buttons I assure you.

[GUIDE] [NEW] Root All L90 Varients with Latest updates [EASY]

All Credit to @thecubed. Please thanks him on his OP here
This is not my original work.I am just sharing this GUIDE for easy rooting of L90 with latest updated, those are not supported by towelroot.
I have tested this method myself and it is working perfectly for me, but it is also possible that it might not work for you for some reasons, so don't panic, just post your problem or whatever error you are facing (please attach screenshot if possible). I or other thread members will try to troubleshoot it. After resolving the problem I'll update this post, so that other members do not face such problem again
Click to expand...
Click to collapse
PLEASE, USE THIS TUTORIAL AT YOUR OWN RISK, IF SOMETHING WENT WRONG (because of your stupidity) ME OR XDA WILL NOT RESPONSIBLE FOR YOUR LOSS.
I HAVE ONLY TESTED THIS METHOD WITH MY L90 D410 AND IT MUST WORK WITH OTHER VARIENTS:fingers-crossed: . BUT STILL FOLLWO THIS GUIDE AT YOUR OWN RISK
Click to expand...
Click to collapse
First of all Install USB Drivers from following link :-
Click here to download L90 USB Drivers
After installing USB Drivers, download Rootl90.zip file attached to this post below and extract it to C Drive of your PC.
On your phone, Goto Settings -> General -> Developer options and enable USB debugging by ticking the check box.
(If you are unable to find Developer options, then go to About phone -> Common -> Software Information and continuously tap on Build amount for 5 to 6 times, it will enable developer options)
Now Connect your phone with PC in LG Software mode, open device manager and confirm ADB Device listed at the top of the list, as an image attached below:-
{
"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"
}
Now open Rootl90 folder, that you extracted to the C drive in the first step.
In this folder, press and hold shift key on the keyboard, right click on blank place and click on open command window here. The command prompt will start with c:\Rootl90>
Now type following commands one by one in the command window (simply copy, paste and hit enter) :-
Code:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
and match result as shown in following images :-
Command 1
After this phone will reboot into recovery as shown in the image below
Now Proceed to Command 2.
Command 2
Command 3
Command 4
After the last command your device will reboot, congratulations your phone is now rooted. Download and install Supersu form playstore.
reserved
Guys plz reply if worked for other than D410 Model
D410 here, after first command wait til the drivers are installed,
There is a redaction error in your comands, the correct are:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
VainxTheLurker said:
D410 here, after first command wait til the drivers are installed,
There is a redaction error in your comands, the correct are:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
Click to expand...
Click to collapse
Thanks for correction
gdjindal said:
Thanks for correction
Click to expand...
Click to collapse
Aren't these the same commands available in the purpledrake script?
Sent from my LG-D405n using XDA Free mobile app
razoract said:
Aren't these the same commands available in the purpledrake script?
Sent from my LG-D405n using XDA Free mobile app
Click to expand...
Click to collapse
yes it is from purpledrk script.
thanks!
thanks!
I've tried it on D405n and it works. Thank you.
.
LOOOL
Why should i use
Code:
adb reboot --bnr_recovery
adb push start_restore /temp/start_restore
adb push permaroot.bin /temp/start_restore
adb reboot
when i could use simple original purpledrake way. i think you took the files from purpledrake thats all ? or i am wrong ???
Does not work on t-mobile LG L90, D415 with the software version D41510e.
adb reboot --bnr_recovery reboots to a blank screen. Presumably it's still a recovery -- adb connects. But "adb push start_recovery /temp/start_recovery" does not work -- no such file or directory. Changing the destination to /tmp in both adb push commands does push files to the phone but there is no root after reboot.
Looking at the purpledrake script, I also see that the vulnerability tests looks for a process "brd" on the phone but there is no such command in the output of ps.
Any ideas?
LG L90, T-mobile D415 with SW version D41510c also does not work.... same exact issue as described above...
---------- Post added at 10:36 PM ---------- Previous post was at 10:17 PM ----------
voland66 said:
Does not work on t-mobile LG L90, D415 with the software version D41510e.
adb reboot --bnr_recovery reboots to a blank screen. Presumably it's still a recovery -- adb connects. But "adb push start_recovery /temp/start_recovery" does not work -- no such file or directory. Changing the destination to /tmp in both adb push commands does push files to the phone but there is no root after reboot.
Looking at the purpledrake script, I also see that the vulnerability tests looks for a process "brd" on the phone but there is no such command in the output of ps.
Any ideas?
Click to expand...
Click to collapse
You should use TowelRoot app, it roots the phone in like 2 seconds and no reboot is required...
Search in google for "how to root T-mobile LG D415" - first link has few instructions but leads you to the website where to download the tr.apk (if doing from phone) long click on lambda sign and select "save link" ... thank install the app and run it... 2 seconds... done...
996
cardusan said:
LG L90, T-mobile D415 with SW version D41510c also does not work.... same exact issue as described above...
---------- Post added at 10:36 PM ---------- Previous post was at 10:17 PM ----------
You should use TowelRoot app, it roots the phone in like 2 seconds and no reboot is required...
Search in google for "how to root T-mobile LG D415" - first link has few instructions but leads you to the website where to download the tr.apk (if doing from phone) long click on lambda sign and select "save link" ... thank install the app and run it... 2 seconds... done...
Click to expand...
Click to collapse
Towelroot works on the previous SW version (was it D41510c? I don't remember). But there is an update to the version 10e and towelroot does not work on it (at least it did not work yesterday, this was the first thing I tried). Unfortunately, I updated without checking forums and I might have forgotten to turn on survival mode in supersu (although i'm not sure survival mode works).
voland66 said:
Towelroot works on the previous SW version (was it D41510c? I don't remember). But there is an update to the version 10e and towelroot does not work on it (at least it did not work yesterday, this was the first thing I tried). Unfortunately, I updated without checking forums and I might have forgotten to turn on survival mode in supersu (although i'm not sure survival mode works).
Click to expand...
Click to collapse
Towelroot worked fine on my D41510c. I have not updated though, and probably won't as some say nothing really changed with the update.
I have that version and I was able to root with towelroot - it did not even request a reboot or anything... just 2 seconds of my time...
I am now running CM11 and it flies - this phone has just stepped over few models that are considered to be "faster":... not in the CM world
cardusan said:
I have that version and I was able to root with towelroot - it did not even request a reboot or anything... just 2 seconds of my time...
I am now running CM11 and it flies - this phone has just stepped over few models that are considered to be "faster":... not in the CM world
Click to expand...
Click to collapse
Which version do you have 10c or 10e? Is this T-Mobile phone? If it is 10e -- did you just use towelroot straigtforwardly? Was the phone rooted prior to 10e upgrade?
I upgraded rooted phone from 10c to 10e, possibly having forgotten to turn on survival mode in supersu, and lost root. I still have adaway's host file (so ads are blocked, now permanently since I can't go back to the standard host file), I still have supersu files in relevant directories but no root when the phone is running. And towel root says that it can't work on my phone. I was just assuming that the update has a newer kernel that fixes vulnerability exploited by towelroot. I'd love to recover root if I could.
cardusan said:
I have that version and I was able to root with towelroot - it did not even request a reboot or anything... just 2 seconds of my time...
I am now running CM11 and it flies - this phone has just stepped over few models that are considered to be "faster":... not in the CM world
Click to expand...
Click to collapse
Hello!
I would have just a short question about the root. If I make the root with this towelroot am I loosing the guarantee? I mean this procedure is open the bootloader or this is just a "smooth" root?
Thank you!!!!
fynky said:
Hello!
I would have just a short question about the root. If I make the root with this towelroot am I loosing the guarantee? I mean this procedure is open the bootloader or this is just a "smooth" root?
Thank you!!!!
Click to expand...
Click to collapse
Yes, you will lose the guarantee. I believe towelroot just roots your phone.
D1358531 said:
Yes, you will lose the guarantee. I believe towelroot just roots your phone.
Click to expand...
Click to collapse
Thank you for your quick reply.
So if it is just a simple root and in the future I will have some problem with my phone I will be able to put back the original software to the phone without any mark? Because at Samsung phones have a special trick. If you root your phone and the bootloader is open the Knox code (this is the special trick) is jump from 0 to 1 and you will not be able to replace it anymore and you will lose the guarantee forever with it.
I wouldn't like to change the software on my phone I just would like to install programs to the SD card but it is not allowed under the KitKat unless I root my phone. But I think the simple root should be enough for that isn't it?
BTW. Will I need a special program after the root is I want to install to SD card?
Thank you very much!!!!
Before I do this I would like to know if there will be a custom recovery like two? Does this work with the D415? Would I still have my T-mobile connection? I only rooted my Nexus 7 2012 with the Nexus root Toolkit.

Root Gear 2 Neo

It seems as tho there hasnt ever been a sticky made for rooting the Gear 2 Neo, so here ya go(lets hope they make it a sticky).
youre going to need Odin and the tar.md5 file you flash in Odin to get this accomplished. No worries tho, its quite easy to do and the tar linked below works with every version attempted so far, and I've personally flashed all of the versions available on Sammobile.com.
WARNING!!! Do this at your own risk! If you mess it up, its on you, not me!!
download these 2 files
Odin 3.10
Gear 2 Neo tar.md5
the next best thing is to do is to create a folder on your desktop, name it whatever you like, and put those 2 files in it.
next, open Odin by right clicking and open as administrator.
there are some settings that can be changed in Odin, but leave them as they are for this.
click on the "AP" button in Odin and navigate to the folder on your desktop that has the tar.md5 file in it and double click on it to select it.
Go to your gear 2 neo and go to the gear icon. Scroll to the bottom and touch the icon with a lower case "i" in a circle, then check the box that says "USB Debugging"
connect a usb to micro usb cable to your computer and connect the charging dock to the watch, but do not connect the micro usb end of the cable to the cradle.... yet
press and hold the button on the Gear 2 Neo. It will present a menu asking if you want to reboot etc etc, but just keep pressing it. Itll eventually (about 8, or so, seconds later) turn the screen off for a second and then say "rebooting" At this point its critical that you rapidly press the button 5 times. No more, no less. It will then bring you to a screen that gives 4 options. Single press the button to navigate thru the choices and long press to select. The option you want is "Download"
Once the watch is in download mode, connect the micro usb to the cradle. Your computer will likely install some drivers and when its done, the top left box of Odin should show "Com:#" (the pound sign will be a random number of a com port your computer selected)
Next press the start button is Odin.
There will be a dialogue box on the bottom left of Odin that says what its doing and a progress bar that shows on the watch and Odin itself. This process should take around 70 to 90 seconds.
Once complete, the watch should reboot and you should now have root access.
The following posts will be reserved for instructions on how to add custom ringtones. The only supported file type for ringtones and message notifications is .OGG. Ill also include some notif tones im currently using myself because i think theyre HILARIOUS!!!
putting custom ringtones and notification sounds on the neo with stock firmware is done via SDB. Very similar to ADB, you use command prompt to push the tones to specific folders within the file structure of the watches internal storage.
Ok, so to add notification tones, you need to SDB into the filesystem of the watch
fist thing youll need is the SDK itself found here
Follow the install instructions on the page linked above and open a command prompt session, then navigate to the folder that the SDK is located in.
Next, youll need some tones. The notif tones need to be in .ogg format (there are many free tools online available to convert files from mp3 to ogg.) Word of warning here, dont make the notifs too long as the watch has a very limited amnt of space reserved for notif tones, and if you put too much in there, it could corrupt the existing tones. Here are a couple nice-n-short tones of Brak (from Space Ghost) saying woah, hey and dont touch me.
The one i use is Wilford Brimley saying diabeetuhs. (I need to say that diabetes isnt even slightly funny, but the way he says it is)
next thing after either creating your own files or downloading mine is to put them into the same folder that the SDK is located in (its just easier this way) and type the following commands
PHP:
sdb root on
then
PHP:
sdb push YOUR_RINGTONE.ogg /opt/share/settings/Alerts/
(but replace the YOUR_NOTIFICATION.ogg with the actual name of the file you want to inject to your watch)
id also like to stress the importance of not guessing at the commands, as in doing so, you can corrupt the existing tones and theyll not be recoverable on the device. To me, thats ok because the stock ones are lame anyways, but be forewarned
ringtones are basically the same process as above, but you push the files to a different location. Here is the code
PHP:
sdb push YOUR_RINGTONE.ogg /opt/share/settings/Ringtones/
as above, make sure to replace the "YOUR_RINGTONE.ogg" with the actual file name
reserved 3
reserved 4 (just in case i have MOAR fun stuff to add )
Have a question. The stock ringtones and notifications. Can those be removed? I would have asked elsewhere, but i believe you and I are the only ones in this ghost town of a forum. Thanks man.
Sent from my SM-N920P using Tapatalk
Thanks for the tutorial. My Gear 2 Neo was having issues with bluetooth, so I installed this new ROM with root and now it connects again.
fsunoles101 said:
Have a question. The stock ringtones and notifications. Can those be removed? I would have asked elsewhere, but i believe you and I are the only ones in this ghost town of a forum. Thanks man.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
yes you can. the command is something like "sdb rm /opt/share/settings/Ringtones/YOUR_RINGTONE.ogg"
and if that doesnt work try "sdb shell rm /opt/share/settings/Ringtones/YOUR_RINGTONE.ogg"
and to see whats in the folder "sdb LS /opt/share/settings/Ringtones/"
similarly, you might need to add a shell command to LS to see the contents of the folder you seek.
Also also, make sure to "sdb devices" and "SDB root on" before doing any of that stuff with usb debugging checked
youdoofus said:
yes you can. the command is something like "sdb rm /opt/share/settings/Ringtones/YOUR_RINGTONE.ogg"
and to see whats in the folder "sdb LS /opt/share/settings/Ringtones/"
Click to expand...
Click to collapse
Awesome. I will give it a try this evening. Thanks.
Sent from my SM-N920P using Tapatalk
fsunoles101 said:
Awesome. I will give it a try this evening. Thanks.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
not a problem. lemme know if you have any problems with it. ive removed most of my stock ringtones and alerts because i think theyre kinda dumb lol i just have space ghost, wilford brimley and some mario sounds on mine
Novakingwai said:
Thanks for the tutorial. My Gear 2 Neo was having issues with bluetooth, so I installed this new ROM with root and now it connects again.
Click to expand...
Click to collapse
No problem man. This section of the forum is a ghost town! Glad i could help
I know you said it takes 70-90 seconds for the rom to copy over, but mines been sitting here for almost an hour and it only moves a tiny bit every 10-15 minutes.
{
"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"
}
Is it normal?
Not even slightly. Might want to try a different cable, USB port or computer.
Sent from my SM-G900P using XDA Free mobile app
uh oh!
so i found my gear 2 in a drawer the other day and decided to play with it. After flashing this thru odin it doesnt boot up. Everything in Odin showed it was good. How do i fix this now?
Can it even get to download mode?
Also, is it the gear 2 or gear 2 neo? The firmware posted was for the neo only
Yes I can get into download and it is the neo as well.
If you can get to download mode, then its likely a bad download. Try a fresh download and reflash in Odin. If that doesn't work, I'll grab the link from sammobile.com and try the flash from that download link
jwwolfe77 said:
Yes I can get into download and it is the neo as well.
Click to expand...
Click to collapse
Try downloading the firmware from here if the fresh download doesn't work.
http://www.sammobile.com/firmwares/download/46122/R381XXU0BOA2_R381OXA0BOA2_XJP/
If you can get to download mode in Samsung devices, you're not in trouble 99% of the time
youdoofus said:
Try downloading the firmware from here if the fresh download doesn't work.
http://www.sammobile.com/firmwares/download/46122/R381XXU0BOA2_R381OXA0BOA2_XJP/
If you can get to download mode in Samsung devices, you're not in trouble 99% of the time
Click to expand...
Click to collapse
youdoofus said:
If you can get to download mode, then its likely a bad download. Try a fresh download and reflash in Odin. If that doesn't work, I'll grab the link from sammobile.com and try the flash from that download link[/QUOTE
Ok. tried both and still nothing. It kinda does a boot loop a couple times and then the green just stayed black.
---------- Post added at 02:22 AM ---------- Previous post was at 01:50 AM ----------
so just to try, i flashed the android wear and that is working good. Id just rather have the tizenmod 3.0.
---------- Post added at 02:43 AM ---------- Previous post was at 02:22 AM ----------
HAHA!!!! i got it working.....the hard way. I flashed android wear, then the tizenmod full restore file and it worked after that. Everything is good. Thank you for all of your help.
Click to expand...
Click to collapse

Flashing 6.0.1 with Encryption Enabled?

Hey guys!
FIRST - A HUGE thanks to everybody that has done the legwork and research finding the MM files and also those that have uploaded them for download!
SECOND - I have the 925A that I've been running on Cricket. Since Cricket does not officially support the Edge, I've been having to periodically flash the past updates or I've used Odin. Because I am running a Cricket SIM, I cannot do OTA updates.
However, I just recently enabled encryption on my device. Will this affect me trying to do further updates by flashing? Do I need to disable encryption? (I thought I read in the past that this is not possible.) I obviously don't want to brick my phone.
Also, I am currently on OI2 and I've seen that it seems PD6 needs to update from OJ9. All of the posts I've seen say to OTA to OJ9 before flashing. Since I can't OTA I would have to flash OJ9 first. I can't find the file for OJ9 to download. Any help finding it would be appreciated.
Listen, I again want to say thanks to everybody who contributes here. I have been a lurker here for quite some time since I first bought my Nexus 5 and the amount I have learned has been invaluable. I wish I knew enough to contribute in some way. Just know that everybody's work does not go unappreciated!
EDIT - I realize now this probably should have been posted in Q&A, Help & Troubleshooting. Can a Mod move this if it is necessary?
Instructions on how to get 6.01 on G925A
1. YOU MUST HAVE OJ9 update on your phone.
2. Check "about devices" under baseband version.
3. Download all files from this link
https://drive.google.com/open?id=0B04l-XMi07VKdkY0ZExzeEVHcFk
4. Open adb fastboot (MAKE SURE YOUR PHONE IS CONNECTED TO YOUR PC)
5. Put this file (SS-G925AUCU3BOJ9-to-U3CPD6-UP) in your main PC directory C:\ and change the name
SS-G925AUCU3BOJ9-to-U3CPD6-UP to OTA and place a copy of OTA in your phone main directory.
6. Shutdown phone.
7. Restart phone by holding down the POWER, HOME, and UP button at the same time. DONT release until you get an UPDATE LOGO on your phone.
8. Go to your computer in the adb fastboot and type adb devices
9. Then type adb sideload DO NOT HIT ENTER YET!!
10. Go to your main directory on your computer where you put the OTA file and drag it on the
adb fastboot after adb sideload and hit ENTER.
11. This process will take 1hr so be patient and let the phone reboot.
12. Once the phone reboot, you will have 6.01!!!!!
gmccowan1 said:
1. YOU MUST HAVE OJ9 update on your phone.
2. Check "about devices" under baseband version.
3. Download all files from this link
https://drive.google.com/open?id=0B04l-XMi07VKdkY0ZExzeEVHcFk
4. Open adb fastboot (MAKE SURE YOUR PHONE IS CONNECTED TO YOUR PC)
5. Put this file (SS-G925AUCU3BOJ9-to-U3CPD6-UP) in your main PC directory C:\ and change the name
SS-G925AUCU3BOJ9-to-U3CPD6-UP to OTA and place a copy of OTA in your phone main directory.
6. Shutdown phone.
7. Restart phone by holding down the POWER, HOME, and UP button at the same time. DONT release until you get an UPDATE LOGO on your phone.
8. Go to your computer in the adb fastboot and type adb devices
9. Then type adb sideload DO NOT HIT ENTER YET!!
10. Go to your main directory on your computer where you put the OTA file and drag it on the
adb fastboot after adb sideload and hit ENTER.
11. This process will take 1hr so be patient and let the phone reboot.
12. Once the phone reboot, you will have 6.01!!!!!
Click to expand...
Click to collapse
Thanks, Can you please explain step 5, because I have no idea how to do that.
moodyy25 said:
Thanks, Can you please explain step 5, because I have no idea how to do that.
Click to expand...
Click to collapse
when you downloaded the files, one of them was the SS-G925AUCU3BOJ9-to-U3CPD6-UP. Rename this file to OTA and put OTA file on your computer directory C:\ (so the adb fastboot application can find it).
gmccowan1 said:
when you downloaded the files, one of them was the SS-G925AUCU3BOJ9-to-U3CPD6-UP. Rename this file to OTA and put OTA file on your computer directory C:\ (so the adb fastboot application can find it).
Click to expand...
Click to collapse
He can just drag it from the download location without renaming. It works.
Sent from my SAMSUNG-SM-G925A using Tapatalk
Perfect
steelcity1 said:
Hey guys!
FIRST - A HUGE thanks to everybody that has done the legwork and research finding the MM files and also those that have uploaded them for download!
SECOND - I have the 925A that I've been running on Cricket. Since Cricket does not officially support the Edge, I've been having to periodically flash the past updates or I've used Odin. Because I am running a Cricket SIM, I cannot do OTA updates.
However, I just recently enabled encryption on my device. Will this affect me trying to do further updates by flashing? Do I need to disable encryption? (I thought I read in the past that this is not possible.) I obviously don't want to brick my phone.
Also, I am currently on OI2 and I've seen that it seems PD6 needs to update from OJ9. All of the posts I've seen say to OTA to OJ9 before flashing. Since I can't OTA I would have to flash OJ9 first. I can't find the file for OJ9 to download. Any help finding it would be appreciated.
Listen, I again want to say thanks to everybody who contributes here. I have been a lurker here for quite some time since I first bought my Nexus 5 and the amount I have learned has been invaluable. I wish I knew enough to contribute in some way. Just know that everybody's work does not go unappreciated!
EDIT - I realize now this probably should have been posted in Q&A, Help & Troubleshooting. Can a Mod move this if it is necessary?
Click to expand...
Click to collapse
Thank you very much, works wonders on my S6 EDGE G925 AT & T
Everything went perfect me.
Thank you.
Thanks, but unfortunately I am on OJ7, and I tried to update OTA telling me I am up to date, I don't know how to use odin and I need to instal marshmallow im my device. Any help ?
My baseband version is G925AUCU1AOCE so I dont have OJ9. Can you please tell me how I can update to OJ9 first?
When I check for update, it says my device has the latest firmware (which is obviously wrong).

Bootlooping with Android 12 beta preview

TL;DR- I'm trying to get back to Android 11 but I only have access to the fastboot menu since my phone is bootlooping. I'm fairly certain I hadn't enabled USB debugging when the phone was fully functional so I'm not sure if I can use ADB to do so. I also don't have the bootloader unlocked
I downloaded the 12 beta preview last week to try the new features, some UI bugs understandably but was mostly fine. A couple days ago while the screen was off and I just had the phone in my hand it randomly activated SOS mode so after a brief panic and cancelation of the 911 call I opted out of the beta immediately. The next morning after using my phone a bit I picked it up and noticed it was rebooting and was a little warm, and it's been bootlooping since then. I still remember the Andoid 12 UI being active so I'm pretty sure it hadn't reverted to the "new" 11 firmware yet.
I'm trying to revert back to 11 using the ADB on my PC, but I realized that I'm pretty sure I hadn't enabled USB debugging when my phone was still functional, so I'm not sure how to bypass that if I can at all. The web firmware flasher tool does detect my phone, but can't properly connect and I assume it's because the USB debugging isn't enabled.
Before I tried using the ADB I had attempted to perform a factory reset to fix the bootloop and the log messages said it was successfully done, but that didn't get it out of the loop.
@jet flyer
I didn't see the word "locked" or "recovery" anywhere in your post. If you are bootloader unlocked, you use fastboot to flash a full image. If you are BL locked, that should have been in your TL;DR. If you are BL locked, you can still flash a full OTA without having usb debug enabled. You just need to have the latest fastboot/adb binaries installed. Download the rescue OTA, put it in your adb folder and then from recovery mode, use the update via adb option. You do NOT need usb debug enabled to do this. You do however need a working Recovery mode. If you are BL locked and cannot access recovery that is the end of the road.
Sorry for the delayed response wanted a day off so I had enough time to properly deal with this. No it's not unlocked, edited OP to indicate that.
I only downloaded adb last week so that should be the most recent, are the fastboot binaries included in that install or is that something separate?
Using this video for help on how to run adb
I get the device connected sound on my PC when I select install from ADB on the recovery menu and I have ADB running at the C:\adb folder location. when I do the adb devices command I get this
'adb' is not recognized as an internal or external command,
operable program or batch file.
using the powershell I got the long list of text that's mentioned in the video after typing \adb but I still get a similar, but different, error when doing the devices command trying to confirm it's connected
Since this is probably just an error on my part not doing the right commands or something I'm hopping on the xda discord, I'll post here if I get it figured out
Download platform tools from here https://developer.android.com/studio/releases/platform-tools. Unzip it and then put the file that you want to side load in the same folder. I prefer PowerShell. Type adb sideload "file name.zip. That might not work if USB debugging isn't checked. If it doesn't try this.
Transfer the download OTA file to your device’s internal or external storage. Don’t put it inside any folder as the system won’t be able to find it.
Next up, boot your device to recovery.
From recovery, navigate to the Apply Update from SD Card option using Volume Keys. Press the Power key to confirm your selection.
Similarly, use the Volume keys to highlight the OTA.zip file and the Power key to install it. Once the process finishes, you could then use the Reboot system now option to boot your device back to OS
ok finally got something to run on my phone but got an error, here's the file paths and what I typed just in case
{
"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"
}
And here's what the phone says, sorry about the marginal focus my backup pixel 2XL is doing it's best with the reflective screen. The relevant messages start right after the purple of the IR focusing laser reflection
one of the first errors is E: footer is wrong
and Error 21: signature verification failed
I recall hearing on one of those videos or guides I read that something has to be digitally signed, but this is a direct download from the Android website, wouldn't be already be signed?
jet flyer said:
ok finally got something to run on my phone but got an error, here's the file paths and what I typed just in case
View attachment 5333167
And here's what the phone says, sorry about the marginal focus my backup pixel 2XL is doing it's best with the reflective screen. The relevant messages start right after the purple of the IR focusing laser reflection
View attachment 5333175
one of the first errors is E: footer is wrong
and Error 21: signature verification failed
I recall hearing on one of those videos or guides I read that something has to be digitally signed, but this is a direct download from the Android website, wouldn't be already be signed?
Click to expand...
Click to collapse
Sorry for the delayed response, but If you use "reply" to a post the user will get an email notification and so respond more quickly. I normally check this board once a week. Yes, there is one zip file from Google that contains all the binaries you need for adb/fastboot. Yes the image coming from Google is signed. They even include the file hash so you can verify the file is a mirror image and un-corrupted. I'm going to continue down the adb method because it is fool proof and you may not be able to "push" the file to your device and use the sdcard method.
I'm not sure you have added your adb folder to your PC's path statement and this could be causing an issue. If you add this folder to the path, you can call up adb from any folder. However if you have the ota image in the same adb folder, and you navigate to that same folder before typing commands it will still work. I'm not seeing any of your inputs on your photo, so I can't check that. You can easily copy/paste text from the command window so we can clearly see what you are typing and the response back. What response are you getting to "adb devices" and "adb version" ? Until you get back your phone's serial number as a response, you are not connected properly. You can PM me for more assistance or use the reply button on this note. Best of luck.
v12xke said:
Sorry for the delayed response, but If you use "reply" to a post the user will get an email notification and so respond more quickly. I normally check this board once a week. Yes, there is one zip file from Google that contains all the binaries you need for adb/fastboot. Yes the image coming from Google is signed. They even include the file hash so you can verify the file is a mirror image and un-corrupted. I'm going to continue down the adb method because it is fool proof and you may not be able to "push" the file to your device and use the sdcard method.
I'm not sure you have added your adb folder to your PC's path statement and this could be causing an issue. If you add this folder to the path, you can call up adb from any folder. However if you have the ota image in the same adb folder, and you navigate to that same folder before typing commands it will still work. I'm not seeing any of your inputs on your photo, so I can't check that. You can easily copy/paste text from the command window so we can clearly see what you are typing and the response back. What response are you getting to "adb devices" and "adb version" ? Until you get back your phone's serial number as a response, you are not connected properly. You can PM me for more assistance or use the reply button on this note. Best of luck.
Click to expand...
Click to collapse
Ah sorry, still getting used to the specifics of this forum. Thanks for checking though.
I do get the serial number back as a response to verify I'm properly connected, I just didn't do it in that specific instance to avoid posting that online. And yes I did add it to the path(as far as I understand, that's just a convenience thing though?) but I'm still running it from the ADB folder just to be sure.
I'll go ahead and type here what commands I did and what the phone log says, since it's not in focus in the picture.
on adb I typed .\adb sideload coral-[specific file version].zip
adb response: Total xfer: 0.00x
on my phone which was on the load from adb screen it said this:
Now send the package you wan to apply
to the device with "adb sideload <filename> . . .
Supported API: 3
Finding update package. . .
Verifying update package. . .
E:footer is wrong
Update package verification took 0.5 s (result 1).
E:Signiture verification failed
Error: 21
Install from ADB completed with status 2.
Installation aborted.
Then it tried one more time automatically with the exact same text except taking 0.6 seconds but still failing and the same error messages. Should I just download the latest package (now the June update) and try again, or did I do something wrong? The file explorer window is where I opened the powershell from and where the file was extracted to. What does error 21 mean?
jet flyer said:
Ah sorry, still getting used to the specifics of this forum. Thanks for checking though.
I do get the serial number back as a response to verify I'm properly connected, I just didn't do it in that specific instance to avoid posting that online. And yes I did add it to the path(as far as I understand, that's just a convenience thing though?) but I'm still running it from the ADB folder just to be sure.
I'll go ahead and type here what commands I did and what the phone log says, since it's not in focus in the picture.
on adb I typed .\adb sideload coral-[specific file version].zip
adb response: Total xfer: 0.00x
on my phone which was on the load from adb screen it said this:
Now send the package you wan to apply
to the device with "adb sideload <filename> . . .
Supported API: 3
Finding update package. . .
Verifying update package. . .
E:footer is wrong
Update package verification took 0.5 s (result 1).
E:Signiture verification failed
Error: 21
Install from ADB completed with status 2.
Installation aborted.
Then it tried one more time automatically with the exact same text except taking 0.6 seconds but still failing and the same error messages. Should I just download the latest package (now the June update) and try again, or did I do something wrong? The file explorer window is where I opened the powershell from and where the file was extracted to. What does error 21 mean?
Click to expand...
Click to collapse
Sorry, I don't know what error 21 means. Trying the latest image is not going to hurt at this point. Make sure you post the complete file name of the image you are trying to flash. I think there may be bootloader version mismatch that is causing the errors. Verify and post your bootloader version (fastboot menu) and OS version (recovery menu). Have you tried doing a factory reset from recovery and retrying? At this point I would keep searching "rescue ota" for tips and hints. Pasting your screen would be best, rather than retyping. Best of luck!
v12xke said:
@jet flyer
I didn't see the word "locked" or "recovery" anywhere in your post. If you are bootloader unlocked, you use fastboot to flash a full image. If you are BL locked, that should have been in your TL;DR. If you are BL locked, you can still flash a full OTA without having usb debug enabled. You just need to have the latest fastboot/adb binaries installed. Download the rescue OTA, put it in your adb folder and then from recovery mode, use the update via adb option. You do NOT need usb debug enabled to do this. You do however need a working Recovery mode. If you are BL locked and cannot access recovery that is the end of the road.
Click to expand...
Click to collapse
So I read up and Error 21 is because the bootloader is locked. I have the latest bianaries installed like you mentioned, is there something else I was missing in my process?
jet flyer said:
So I read up and Error 21 is because the bootloader is locked. I have the latest bianaries installed like you mentioned, is there something else I was missing in my process?
Click to expand...
Click to collapse
Because your bootloader is locked, you cannot flash a full image . You have to flash an OTA instead.
Secondly, the OTA you choose has to match your current bootloader version or it won't work.
Read the instructions again for flashing a rescue OTA via recovery.
1. Have you accessed the phone's recovery menu and used the update via adb option?
2. What is your current bootloader version? (recovery menu)
3. What is the full name of the file you are attempting to flash? (OTA)
https://developers.google.com/android/ota
v12xke said:
Because your bootloader is locked, you cannot flash a full image . You have to flash an OTA instead.
Secondly, the OTA you choose has to match your current bootloader version or it won't work.
Read the instructions again for flashing a rescue OTA via recovery.
1. Have you accessed the phone's recovery menu and used the update via adb option?
2. What is your current bootloader version? (recovery menu)
3. What is the full name of the file you are attempting to flash? (OTA)
https://developers.google.com/android/ota
Click to expand...
Click to collapse
ohh, I never noticed that tab at the top that says OTA, I get it now that those are needed for non-unlocked bootloaders. I see all the different versions, what does my bootloader version have to do with one of those? I only see the dates pertaining to the monthly updates, how do I know which one is for my bootloader version? I found the section specific to the Pixel 4XL
That worked!!! Thanks for the help, kinda annoyed it was as simple as that tab at the top left of the page saying OTA updated, but glad to have my phone back after 6 weeks. My Pixel 2XL did it's best but a lot of the apps I use for my action camera or drone stuff didn't even work with it haha
jet flyer said:
That worked!!! Thanks for the help, kinda annoyed it was as simple as that tab at the top left of the page saying OTA updated, but glad to have my phone back after 6 weeks. My Pixel 2XL did it's best but a lot of the apps I use for my action camera or drone stuff didn't even work with it haha
Click to expand...
Click to collapse
Happy to hear you are back up and running! Cheers.

Categories

Resources