Database Users

stupid reason to take back evo to get an epic?

cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.

It can be rooted you just have to work harder at it. Dont take it back you'll regret it.

Clearly you haven't done any searching in the Android Development section.
But that's OK. Go ahead and get an Epic. Enjoy your screwed-up GPS and all that, and make sure to change your password on here to something you won't remember, so we never have to see you again.

mainguy21 said:
cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829045
there you go. Just follow the directions and make sure you use the correct file locations.

real problem
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better

thats funny i just typed in the search bar root evo hboot 2.02 and the first thread was the guide on how to do it.
@op if you are going to lie about searching the forum do it somewhere else. we know when a search isnt performed.

mainguy21 said:
and ive searched everywhere
Click to expand...
Click to collapse
Sure you have, buddy... sure you have.

ohhhhhhhhhhhhhh

You have been misinformed due to stupid people making stupid and false posts such as this one:
http://forum.xda-developers.com/showpost.php?p=9578042&postcount=8

Kingmac38 said:
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I am 20 and have ADHD and search is my best friend plus I've followed many rooting guides successfully so op has no excuse

Second that my girls epic is a pain in the ass and she kinda of.wish she got my phonr instead
Sent from my PC36100 using XDA App

thanks for help even though i searched everywhere.
but since i cant root my phone im stuck in the middle of it with a red triangle can i atleast go back to my phone? like unroot or something even though i didnt get all the way to root? please thanks

Follow these revised instructions from illogos pg 121 of hboot 2.02 root guide and everything should work. I've already rooted two hboot 2.02 hw 004 and in process of doing another one now. Everything works just fine if you understand and follow the instructions. Anyways, this was a lot simpler than the old school toast part 1 and 2 root methods so acquire some knowledge so you can someday help others and not be such a newbie.

thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.

mainguy21 said:
thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.
Click to expand...
Click to collapse
Which instructions though? Please follow these ones by illogos-
illogos said:
1. Make sure that you downloaded and installed HTC Sync from HTC website.
2. Unzip hboot202-s_off-V8.zip to a folder in your C: drive. I used C:\hroot
3. This hroot folder should have a folder inside it called root. If you have a folder called hboot202-s_off-V8 then you need to move all the files from that subfolder to c:\hroot.
4. In Vista/7 slick on the start button and type in cmd. You will see in the program list the command prompt. Right click and open as Administrator.
5. In the command prompt type cd c:\hroot
6. On phone goto-> Setting>Applications>Debugging make sure usb debugging is on.
7. Connect the usb cable to your computer and phone. The phone should change it's screen to ask you what type of connection mode you want. Make sure that it is on charge only. Do not mount.
8. Type into the command prompt: adb push root/unrevoked-forever.zip /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
9. Type into the command prompt: adb push root/mtd-eng.img /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
10. Type into the command prompt: adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
11. Type into the command prompt: adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
12. Type into the command prompt: adb push root/flash_image /data/local/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
13. Type into the command prompt: adb push root/rageagainstthecage /data/local/tmp After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
14. Type into the command prompt:adb shell You should see a $, this means that you are "in" the phone.
15. Type into the command prompt:chmod 0755 /data/local/tmp/rageagainstthecage You should see this echoed on your screen. This is normal. You should still have $ on your cmd line.
16. Type into the command prompt: chmod 0755 /data/local/flash_image You should see this echoed on your screen. This is normal. You should still have a $ on your cmd line.
17. Type into the command prompt:./data/local/tmp/rageagainstthecage A message will pop up on the screen. It will take a few seconds, and your will be kicked "out" of the phone. The $ should now be gone.
18. Type into the command prompt: adb shell You should have a # on your command line instead of a $. # means you have temporary root in your phone. If you do not have #, then start over.
19. Type into the command prompt that has #: ./data/local/flash_image misc /sdcard/mtd-eng.img
20. Type into the command prompt that has #: sync
21. Type into the command prompt that has #: reboot bootloader
22. Your phone will be rebooting now. Eventually your phone will be at the bootloader menu. On your phone use volume up/down to highlight bootloader and press the power button once. It will start loading the PC36img.zip file.
23.After it loads, it will ask if you want to flash. Press Volume UP to say yes. It will now flash, which can take some time. You may see some red fail messages. This is normal.
24.When it is done flashing it will ask you if you want to reboot. Press Volume Down to say now to reboot.
25. Use volume up/down to highlight recovery. Press the power button once. This will try to boot into recovery mode but fail and load a screen with a red triangle. This is normal because you have not installed recovery yet.
26. Go back to your computer screen and your command prompt. You should not have a #
27. Type into the command prompt: adb push recovery /
28. Type into the command prompt: adb shell busybox --install /sbin
29. Type into the command prompt: adb shell nohup /sbin/recovery &
30. After a pause you should see a new screen on your phone. It should be green text with your recovery options.
31. Highlight backup/restore. Press the power button. Highlight backup nand and press the power button. Press the power button again to confirm the action. Your phone is now doing a nandroid backup. This will backup your wimax keys amongst other things.
32. It will take a little time to do the backup. After it is done press the power button once to return to the recovery menu.
33. Highlight enable USB-MS and press the power button.
34. On your computer, you should see a new drive in my computer or a pop up asking you for an action. Click on Explore, or open the drive in my computer, to access your phone like you would a thumb drive.
35. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip
36. On your phone, press the power button to disable USB-MS mode. You should be back at the recovery menu.
37. Highlight the option to flash image from zip. Press the power button.
38. Highlight unrevoked-forever.zip and press the power button. Press the power button again to confirm if told to do so.
39. When it completes flashing the image, select reboot from the menu.
40. When it reboots a few things could happen. If you think your phone is frozen, you are okay because that is a normal occurrence on this step.
----->Your phone gets "stuck" on a white screen with the word HTC on it for more than a minute. You need to take the back case off your phone and pull your battery out. Put the battery back in and put the back case on again. Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->You phone started up and fully booted. You need to completely power off.Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->The phone returns to the boot loader.
41. No matter which of the 3 scenarios occurred to you in the last step, you are now in the boot loader. Obviously the 3rd scenario is the best, but all are OKAY.
42. The phone should find PC36img.zip. It then loads this file and asks if you want to flash. Use volume up for yes. When it asks to reboot press volume up for yes.
43. When it is done booting, return to your computer screen and type adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip into the command prompt.
44. Type into the command prompt: adb reboot recovery
45. Highlight backup/restore in recovery and then press power. Highlight backup nand and press power. Press power again to confirm. Wait for the backup to complete.
46. Press power to return to recovery menu. Highlight reboot phone and press power.
47. Your phone is now rooted, S-OFF, and booted into stock 3.30.651.2.
-------------------------------------------------------------------------
After Root:
1. Run through setup and get to the actual phone screens.
2. Try to turn on 4G/wifi/etc and see if it all works. It may not and this does not mean disaster.
For me, I had to flash Stock RUU root 3.30.651.3 to get 4G to work. Here is what I did next:
1. Download stock RUU root 3.30.651.3(I opted for Odexed version) from http://forum.xda-developers.com/showthread.php?t=836728
2. Reboot phone into recovery by completely powering off. Hold down volume down and press power. When you get into the boot loader it will try to find PC36img.zip and fail (we renamed that file remember?) and that is normal. Use volume up/down to highlight recovery and press the power button.
3. In recovery highlight USB-MS and press power to enable.
4. Your phone should be mounted as a drive in your computer again like before. Copy the whole zip file that you downloaded for RUU 3.30.651.3 rooted odexed to your phone. Wait for it to finish the transfer.
5. On your phone press power to turn off USB-MS mode.
6. On the recovery menu highlight wipe and press power.
7. Highlight the first wipe option which is something like wipe cache/factory reset. Press power. Press power again to confirm if needed.
8. Hightlight the second wipe option which is wipe cache. Press power and then press power again if needed.
9. Highlight the third wipe option which is wipe dalvik-cache. Press power and then press power again if needed.
10. Return recovery menu.
11. Hightlight flash image from zip and press power.
12. Highlight the file that you just transfered over that is for RUU 3.30.651.3 and press power. Press power again to confirm if asked. It will start flashing the image to your phone, but you will not see progress bars. It will take a few minutes.
13. When it is complete select the option to reboot the phone.
14. The phone should fully boot up into the stock rooted 3.30.651.3 rom.
15. Now try to turn 4G/wifi/etc on and make sure it works. It did for me.
16. Assuming that everything is working fine, fully power off, boot into recovery, and do another backup. This newest backup is your holy grail backup. It is stock rooted S-OFF and 4G working backup.
Note: these last 15 steps can be used to flash any custom rom too. Just make sure that you get your "holy grail" backup first before you experiment.
Click to expand...
Click to collapse

my wife got an evo on black friday from radio shack and i rooted it with unrevoked in like 5 minutes.

I have adhd... I wonder if 4g transmissions cause an increase in autistic spectrum disorders!?!?
Sent from my PC36100 using XDA App

animal7296 said:
It can be rooted you just have to work harder at it. Dont take it back you'll regret it.
Click to expand...
Click to collapse
he wouldn't regret getting the epic, it's a cool ass phone. if you want a crisper lcd and a keyboard get the epic.

fixxxer2008 said:
If you want a cheap-ass plasticky POS, get the epic.
Click to expand...
Click to collapse
Fixed that for you.

tejasrichard said:
Fixed that for you.
Click to expand...
Click to collapse
Thank you. It seems all these Samsung phones feel like garbage. Way too flimsy. Now I have a friend with an LG Optimus S which I just rooted for her, and I have to say the build quality is very nice.

[HOWTO MAY16]UNLOCK BOOTLOADER, FLASH RECOVERY, INSTALL ROM Atrix 4G Bell/int'l + ATT

Edited May 16 2012
Hi all,
Due to confusion and scared people I have decided to post simple instructions on how to unlock the bootloader on GB 2.3.4. I just received my Bell Atrix 4G, unlocked it for rogers and then rooted and unlocked the bootloader. I was confused by the pudding instructions, so I decided to recreate them In my own wording.
I take no responsibility for anything that happens to your phone or your heart stopping while you wait for your phone to reboot or if it is stuck on moto screen etc...
Credit for original tutorials go to the2dcour, romracer, Nottach, Faux123 and the others for all of their hard work.
Requirements:
1.Create a folder on your desktop named motounlock
2.Go here: forum.xda-developers.com/showthread.php?t=1136261
Scroll down to where it says "RSDLite/Windows Drivers/Sbf_flash"
UPDATE: Download RSDLite from here : http://www.multiupload.com/T6NOEBKKLO . If you need x64 bit Drivers use the other link. thanks AnguishedEnd!
download the first two files for windows (RSDLite 5.5 link, x64 Windows drivers)
download the third file for linux/mac
3.Scroll until you see the big word "Unlock"
where it says "Unlocker only SBFs" download the second file UNLESS you are on ATT.
4. Scroll down to the word "Root" and download 'Fastboot' for your OS
5.unzip all of the files you just downloaded into the motounlock folder on your desktop
6. open the folder, install RSDLite, and afterwards install the Drivers.
Then follow these instructions
Power Down your atrix
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD. Your device will say “Starting RSD protocol support”
Run “RSD Lite” on your computer
Press the “. . .” button next to the box labeled “Filename”
Navigate to your desktop and open the motounlock folder and select the file named intl-fix-try1.sbf ( IT WILL BE DIFFERENT IF U ARE DOING THIS FOR ATT)
Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!
Press the “Start” button. The Flash actually failed for me, wait for it to complete to 100% it may FAIL or PASS! just make sure it gets to 100% leave your phone sitting for about 10 minutes AFTER RSD SAYS FAIL/SUCCESS.
If nothing is happening after 10mins, perform a battery pull. Power the phone on while pressing vol-down. “Fastboot” Will show up on screen. DONT PLUG IT IN YET. Press volume up and let your phone sit. You will see “Starting Fastboot protocol support" LEAVE IT UNPLUGGED
press the windows key + R on your computer, type cmd and press enter
command prompt will open. type cd C:\users\YOURNAME\desktop\motounlock press 'enter'
Plug your device back into usb now
back in your command prompt window type "fastboot oem unlock" no quotes
You will now receive a warning along with a unique device ID
Type the following commands using your unique device ID (the numbers in the command prompt) in place of the ####
fastboot oem unlock ####
fastboot reboot
your moto will reboot. UNLCOKED!!!!!!!!!!!!!
Proper Recovery:
1. After your bootloader unlocked go to this link http://forum.xda-developers.com/showthread.php?t=1204500
2. Scroll down to where it says "ALL USERS" and download your favourite colour. (NOT THE ZIP VERSION) Place it in the motounlock folder that you have on your desktop.
3. Press the windows key + R on your computer, type cmd and press enter
4. A Command prompt will open. type cd C:\users\YOURNAME\desktop\motounlock press 'enter'
5. type "fastboot devices" Press Enter.
5b. type "fastboot erase recovery" Press Enter.
5c. type "fastboot flash recovery recovery-atrix5.img" Press Enter.
Wait for the command prompt to say : "writing 'recovery'... OKAY ['The amount of seconds it took here']"
5d.type "fastboot reboot"
DO NOT FORGET TO DO THIS PART: After the install of RomRacers recovery boot up your phone. Open up your favourite file browser (I used Astro file manager to do this ) and navigate to /system/etc/ and delete the file called 'install-recovery.sh'
You will be set 100% !
Installing a custom ROM (Any custom rom will work as long as it has unified kernel/Faux Kernel)
MOST ROMS WILL COME PRE-ROOTED! Just saying, to avoid confusion.
I will be using Nottach's Darkside ROM as an example, because Cyanogenmod does not have features included with original moto rom (this one is way more NOOB friendly) But this is COMMON PROCEDURE for almost every rom so be sure to follow this for whatever ROM you want to use.
1. Go here http://forum.xda-developers.com/showthread.php?t=1222108
2. Scroll down to where it says 'DOWNLOADS' and download the most current version.
3. When it is finished downloading you will have a ZIP file named something like "TheDarkSidev2.8.0-Wipe.zip"
4. Plug your phone in to your computer and transfer that file to your INTERNAL MEMORY.
5. MAKE SURE YOUR PHONE HAS DECENT CHARGE! I would say at least 50 percent. 70+ is recommended, I have done it with 40 + though.
6. Power Down your Phone.
7. Hold The POWER Button + VOL DOWN. DONT PRESS VOLUME UP WHEN YOU SEE FASTBOOT! Instead...
8. After fastboot shows up click volume down until " Android Recovery " shows up, about 7 down clicks. THEN press volume up.
9.
***FIRST TIME ROM FLASHERS ONLY!!!!!!***
WE ARE GOING TO BACKUP YOUR ORIGINAL ROM SO THAT IF YOU EVER DERP YOU WIL ALLWAYS HAVE A SOLID BACKUP
Press VOLUME DOWN and go to backup and restore. Press the POWER BUTTON
Press the POWER button on backup
Select where you want to put your backup (internal or external memory)
Backup INCLUDING WEBTOP! (if you ever think you will use it)
Wait for it to finish.
***********************************
10. Ok now that you are in android recovery you have to do a few things before flash.
a. Scroll down to "wipe data/factory reset" PRESS POWER. say yes to EVERYTHING until it goes back to the main screen.
b. scroll down to "wipe cache partition" PRESS POWER. say YES. Wait for return to main menu
c. Scroll down to"advanced", click "wipe dalvik cache" Go back to "advanced", "wipe battery stats
11. At the main menu, Scroll to "install Zip from SDcard" Press POWER.
12.scroll down to "choose zip from internal sdcard"
13. select the ZIP file that you saved to your INTERNAL memory. If you're using darkside the file name is "TheDarkSidev2.8.0-Wipe.zip"
14. Scroll down to "YES - install TheDarkSidev2.8.0-Wipe.zip" Press POWER
15. Let your phone work its magic!
16. When it is finished installing, you will be returned to the recovery main menu.
17. click "reboot system now"
18. Let it boot! This can take anywhere from 10 seconds to 5+ MINUTES! if you dont see it move from the "unlocked" screen after 10 minutes Perform a battery pull and power on again. If it hangs then all you have to do is go into recvoery click "backup and restore" and restore your original ROM. Or like me, have one of every kind of ROM on your storage in case I feel the need to change it on the go!
19. YOUR PHONE HAS BEEN SUCCESSFULLY TURNED INTO A FULLY OPEN DROID Pat yourself on the back and have a drink to your accomplishments . We on XDA knew you could do it!
Some solutions to issues:
As ar31791 said,
Anyone having issues not being able to boot into CWM recovery after flashing it (such as seeing android guy with exclamation mark):
Delete or rename /system/etc/install-recovery.sh AND /etc/install-recovery.sh I renamed mine to bkup.install-recovery.sh in case i ever wanted to use them again for some reason.
/etc/install-recovery.sh will automatically be placed in /system/etc if /system/etc/install-recovery.sh is not found on boot.
So, you must delete or rename both, THEN INSTALL CWM recovery.
rename the files using ROM Toolbox's root explorer as some file explorers will not give you the proper access levels to delete or rename the files correctly.c
Hope this helps it worked for me. I was afraid of a brick because nobody clarified the steps that were involved in RSDLite. It may be nerve racking, but it does work!! Enjoy and thanks again to the2dcour, romracer, Nottach, Faux123 and anybody else who has helped in the scene that I didnt have a chance to mention. PM me if I forgot you!

Oh, and just to let everybody know when your bootloader is successfully unlocked it will say unlocked at the top left of your screen everytime you turn it on. just wait, this is normal.

OMG thank you so much tayshun!! I just spent 2 hours reading through that pudding post mess trying to figure out how to do this for a 2.3.4 bell atrix....
I was very nervous about trying something without clear directions in case I brick my phone. You're a lifesaver

noobler said:
OMG thank you so much tayshun!! I just spent 2 hours reading through that pudding post mess trying to figure out how to do this for a 2.3.4 bell atrix....
I was very nervous about trying something without clear directions in case I brick my phone. You're a lifesaver
Click to expand...
Click to collapse
I understand your grief hahaha. Feel free to press the thank you button at the bottom of my post. I'm trying to get a good reputation around here as I am going to school for programming and I will probably be in these dev forums daily to get help cooking Roms!

Has anybody else had success with my simplified instructions? Results?

this instructions seem simple
http://forum.xda-developers.com/showthread.php?t=1182871
what do you think?

sanriver12 said:
this instructions seem simple
http://forum.xda-developers.com/showthread.php?t=1182871
what do you think?
Click to expand...
Click to collapse
Are you sure it works on a Bell/Int'l Atrix?

Thanks heaps for the instructions Just used them to unlock a Telstra Atrix which I updated to 2.3.4 this morning! Worked a treat.
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
Maybe i spoke to soon...I just noticed it has reset to factory defaults. Not a big deal as I already backed everything up but i certainly wasn't expecting it!

What about android version 2.2.2 and system Version.4.2.11.MB860.Retail.end.FR
Build: OLYEM_ U4_2.1.1
IT'S bell phone atrix 4g unlocked and running on Rogers
In just afraid of ruining it,, I've bricked a vibrant by just updating it from Samsung utility which is weird.
Thanks
Sent from my HTC-A510a using xda premium

timfoote said:
Maybe i spoke to soon...I just noticed it has reset to factory defaults. Not a big deal as I already backed everything up but i certainly wasn't expecting it!
Click to expand...
Click to collapse
you would have expected this if you had informed yourself as you should, before performing this kind of procedure on your phone.

Worked perfectly for me. My phone wouldnt complete the flash, so I went into CMD and unlocked it.
I've been trying to do this before, and many failed attempts.
So thank you.

worked
Fantastic summary.
Worked like a charm.
Bell Atrix with retail updates.
Thanks a million!
...Damnit, still can't remove Kobo; wtf!

Super guide
Thanks for the very clear instructions. Worked first time. The one thing that always seemed ambiguous to me was the memory fix. Do we need to apply it?

xeidy said:
What about android version 2.2.2 and system Version.4.2.11.MB860.Retail.end.FR
Build: OLYEM_ U4_2.1.1
IT'S bell phone atrix 4g unlocked and running on Rogers
In just afraid of ruining it,, I've bricked a vibrant by just updating it from Samsung utility which is weird.
Thanks
Sent from my HTC-A510a using xda premium
Click to expand...
Click to collapse
I also have an unlocked bell atrix 4g on rogers. If you dont have 2.3.4 you would have to update your phone with the bell original software. It wont take away your unlock as unlocks are permanent. after you upgrade follow this guide to unlock the Bootloader and feel free to use custom roms!

nabicat said:
Thanks for the very clear instructions. Worked first time. The one thing that always seemed ambiguous to me was the memory fix. Do we need to apply it?
Click to expand...
Click to collapse
well after I unlocked my bootloader I installed romracers CWM and DarkSide v2.1 to my phone. No issues with ram so far. I dont know if you intend on installing customs ( I assume so because what other reason would you have to unlock the bootloader? lol) but after the install my ram readouts seemed correct

Yes, you're correct. I checked available memory and its over 800 mb, so the fix must be in there.
Cheers

Working very well with Bell Atrix.
Thanks for big help.

Wondering if this instruction works with Hong Kong's ME860 2.3.4 also?
I'd love to try this!

MrJcc said:
Wondering if this instruction works with Hong Kong's ME860 2.3.4 also?
I'd love to try this!
Click to expand...
Click to collapse
I'm not sure if it works with hong kong version. If you check the link that I posted, it leads to a thread on here called international house of pudding. in that thread at the beginning it says that " China version ??: DANGER: Brick after OTA 2.2.2" So you would definitely have to ask someone around the forums or search to see if somebody has done it successfully

It is possible to remove the unlocked during the boot?
Sent from my MB860 using XDA App

[TUTORIAL][CM11][4.4.2] CyanogenMod Tutorial for Sony Xperia Tablet Z (pollux)

I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.​3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.​3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.​f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.​4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)​5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)​8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.​12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.​15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.​
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.

Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.

Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.

alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.

I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.

for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?

Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.

Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.

BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd

No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?

kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.

mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.

Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.

I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!

tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.

Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.

[Guide] How to root N20

How to root N20 (N985F/N986B/N9860)
WARNING!
Before you root your device you must be aware that
This will void warranty.
As of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
There are many features stop working when you unlock bootloader other than S pay/Pass like Samsung Health, Secure Folder, Galaxy Watch pairing issue, Issue connecting old gear watch (S3 or earlier), Google Pay etc but some ROMs are patched for all these mentioned features, you can use custom ROM or patch it yourself for stock ROM. Still you may trouble using some bank apps and these may fixed by adding these apps to Magisk Hide
There may be some knox features there which you may not able to use but I can't list those as I never used. Just Google It
Patched featurs are working today when writing this, No idea if it may stop working next moment/tomorrow or later
Also to note, once you root, you can't go back to "pre-rooted" state completely. It is one way!
OTA won't work once you root device.
ROOT with caution.
You can unroot & Relock bootloader after flashing stock firmware, but still your warranty flag remain 0x1 and most of countries it still voids warranty. Also after unrooting & relocking bootloader, some knox features never work again.
How to Unlock Bootloader
Follow below four steps to ulock the bootloader
1.Enable Developer Option
Open the Settings app on your Galaxy device.
Choose About > Software Information.
Now tap on Build Number 7 times to enable the developer option.
You’ll get a message “You’re now a developer.”
Now Developer option has been enabled.
2: Enable OEM Unlock
Go to the Settings app again on your device.
Navigate to the Developer option.
Enable the toggle next to OEM Unlocking.
Tap YES to turn on the confirmation dialog box.
3: Boot Your device to Download Mode
While device is booted → Connect device to PC → Select to Restart → As soon as device screen turns off, Press and hold Volume Up + Volume Down simultaneously OR In case device is powered off Press and hold Volume Up + Volume Down simultaneously and connect your device to the PC via a USB Cable.
You can see the warning message on your device and release the pressed keys.
Finally, press the Volume Up key once, and you will be booted into Download Mode.
4: Unlock Bootloader
Once device booted into Download Mode, you will see option to long press Volume up to unlock bootloader,Now, press and hold the Volume Up key for a few seconds., Here, you’ll get a confirmation whether you are sure to proceed.
Use the Volume Up button to reply to the confirmation.
This will erase all the data on your device and unlock the bootloader.
Once completed, your device will automatically boot up to the OS.
Now you have successfully unlocked the bootloader
How to root
Instructions for stock non rooted ROM​
Use either samfirm.js, Frija, or Samloader to download the latest firmware zip of your device directly from Samsung servers.
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Install Magisk apk
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the AP tar file
When done, copy patched file to PC
Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.
Your device should reboot automatically once Odin finished flashing. Agree to do a factory reset if asked.
Install the Magisk app you’ve already downloaded above and launch the app. It should show a dialog asking for additional setup.
Let the app do its job and automatically reboot the device. Voila!
Upgrading the OS​Once you have rooted your Samsung device, you can no longer upgrade your Android OS through OTA. To upgrade your device’s OS, you have to manually download the new firmware zip file and go through the same AP patching process written in the previous section. The only difference here is in the Odin flashing step: do NOT use the CSC tar, but instead use the HOME_CSC tar as we are performing an upgrade, not the initial install.
Important Notes​
Never, ever try to restore either boot, recovery, or vbmeta partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.
To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always patch AP in the Magisk app and use that instead.
Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading.
PS : It is strongly recommended to make EFS backup once you root device and save to safer place like on cloud or PC
For TWRP : Read here
Credit : topjohnwu Guide part taken from Origin guide here

Happy to see you here on Note 20 Ultra Dr. Ketan my bro.

dr.ketan said:
Here is Patched kernel to root N986B Note20 Ultra (N986B_TH3)
Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!)
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode,long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device
Installation (Flashing) custom binaries
1. Switch off the device and reboot to download mode (As said earlier) and select volume up to continue
2.Download Magisk Patched Kernel and extract on PC
Open Odin as administrator (Above downloaded Zip have included Odin)
Select Roor_N986*.tar.md5 file (you have downloaded & Extracted on PC in above instructions) for AP tab of Odin
3.From Odin option - uncheck Auto Reboot option
4.Now start flashing and wait till it finish. When you see a PASS sign on Odin, disconnect device.
Now magisk is successfully finished but yet you need to follow instructions below.
Factory reset
After disconnecting device, keep holding Vol down + Side key to exit from download mode.
Here is very important - when you see device reboot As soon as the screen turns off, immediately press Volume Up + Side Key to boot to recovery partition. continue pressing the volume up button until you see the stock recovery screen.
In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select Wipe data/factory reset to wipe the data of the device.
Select Reboot system now
The device will automatically reboot for the first time it boots. This is completely normal and done by design.After the device is booted up, do the usual initial setup. You shall see Magisk Manager in your app drawer; if not, Download Magisk Manager and manually install the APK you downloaded and continue to the next step.
Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device. (You must needed to connected to internet)
Status : Untested
Click to expand...
Click to collapse
Many thanks Ketan. i was hoping to see this
Moderators can we sticky this??

Is there, and will you or anyone work on the Hong Kong SM-9860 Root option ( which is Snapdragon )

inningsdefeat500 said:
Is there, and will you or anyone work on the Hong Kong SM-9860 Root option ( which is Snapdragon )
Click to expand...
Click to collapse
Is your device bootloader is unlocked? If yes then
Inbox me your Telegram ID for easy communication

dr.ketan said:
Is your device bootloader is unlocked? If yes then
Inbox me your Telegram ID for easy communication
Click to expand...
Click to collapse
Ketan bhai, still waiing for it but ur communication on this is makes me happy
Checking - https://www.sammobile.com/samsung/galaxy-note-20-ultra-5g/firmware/#SM-N986B
Its this version - https://www.wondamobile.com/samsung...0-lte-mobile-phone-sim-free-and-unlocked.html
So yet to come

inningsdefeat500 said:
Ketan bhai, still waiing for it but ur communication on this is makes me happy
Checking - https://www.sammobile.com/samsung/galaxy-note-20-ultra-5g/firmware/#SM-N986B
Its this version - https://www.wondamobile.com/samsung...0-lte-mobile-phone-sim-free-and-unlocked.html
So yet to come
Click to expand...
Click to collapse
Both are different in your links
First link - global exynos
Second link - Snapdragon China

dr.ketan said:
Both are different in your links
First link - global exynos
Second link - Snapdragon China
Click to expand...
Click to collapse
The first link was to show what firmwares are out already for Note 20, meaning the North American and HK Snapdragin are yet to release

Will it work on SM-N986UZKFXAA?

Androidwarrior said:
Will it work on SM-N986UZKFXAA?
Click to expand...
Click to collapse
Mostly U version is Snapdragon with unlock bootloader and not rootable. Confirm first if you have unlocked bootloader.
Also last 3 digit of firmware is weird. Which device is this? Can you post screenshot of phone info?

dr.ketan said:
Mostly U version is Snapdragon with unlock bootloader and not rootable. Confirm first if you have unlocked bootloader.
Also last 3 digit of firmware is weird. Which device is this? Can you post screenshot of phone info?
Click to expand...
Click to collapse
Yes. https://www.samsung.com/us/business...ote20-ultra-5g-512gb-unlocked-sm-n986uzkfxaa/
https://www.bestbuy.com/site/samsun...unlocked-mystic-black/6420842.p?skuId=6420842

Androidwarrior said:
Yes.
Click to expand...
Click to collapse
What I guess, here unlocked means sim unlocked NOT bootloader.

Some people might need clarification. An "unlocked" phone is not the same as a phone with an unlockable bootloader. If it's the same pattern from the past several years of Note releases. All of the snapdragon US versions won't have the ability to have their boot loaders unlocked, therefore a root. This root method most likely applies to the non-US Exynos versions. If you live in the US, and ordered your phone through Samsung or any carrier, it will be the snapdragon version. I hope I'm proven wrong.

dr.ketan said:
Here is Patched kernel to root N986B Note20 Ultra (N986B_TH3)
Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!)
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode,long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device
Installation (Flashing) custom binaries
1. Switch off the device and reboot to download mode (As said earlier) and select volume up to continue
2.Download Magisk Patched Kernel and extract on PC
Open Odin as administrator (Above downloaded Zip have included Odin)
Select Roor_N986*.tar.md5 file (you have downloaded & Extracted on PC in above instructions) for AP tab of Odin
3.From Odin option - uncheck Auto Reboot option
4.Now start flashing and wait till it finish. When you see a PASS sign on Odin, disconnect device.
Now magisk is successfully finished but yet you need to follow instructions below.
Factory reset
After disconnecting device, keep holding Vol down + Side key to exit from download mode.
Here is very important - when you see device reboot As soon as the screen turns off, immediately press Volume Up + Side Key to boot to recovery partition. continue pressing the volume up button until you see the stock recovery screen.
In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select Wipe data/factory reset to wipe the data of the device.
Select Reboot system now
The device will automatically reboot for the first time it boots. This is completely normal and done by design.After the device is booted up, do the usual initial setup. You shall see Magisk Manager in your app drawer; if not, Download Magisk Manager and manually install the APK you downloaded and continue to the next step.
Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device. (You must needed to connected to internet)
Status : Untested
Click to expand...
Click to collapse
Hi thanks for the rooting instructions. I would like to know if you or anyone has gotten the option for s pen pointer under air commands in your note advanced settings? Jimmy is promo does but every other youtube doesnt have that option so im wondering what note 20 has it and what firmware? Anyone feel free to chime in

If you have rooted the Note 20 ultra 5g (Germany), can i start it normally or do you have to hold a key combination?

Conan179 said:
If you have rooted the Note 20 ultra 5g (Germany), can i start it normally or do you have to hold a key combination?
Click to expand...
Click to collapse
If you root with Method mentioned in OP, you should able to boot with root without using combo keys

I coming from the note 9.
If it's rooted, how do I update it?
(Switch from csc to talk (Vodafone DE to DBT) I know that has nothing to do with this topic )

Conan179 said:
I coming from the note 9.
If it's rooted, how do I update it?
(Switch from csc to talk (Vodafone DE to DBT) I know that has nothing to do with this topic )
Click to expand...
Click to collapse
Plz post your question to appropriate forum

ok a new topic, "how do i update a rooted note 20 ultra 5g" Ok I'll do it as soon as I have mine.

no one has the S pen pointer option?
Also have any of you signed up for beta 3.0 android 11 for the s20? Im guessing you guys have early access because the note 20 isnt even out yet.

Shield TV 2019 (non-Pro, tube) ROM Flashing

So I hadn't tried to flash a ROM on my "tube" Shield TV 2019 until the Experience 9 ROMs just leaked. I didn't realize it didn't have a USB port. I have been flashing ROMs on Android phones for over a decade, so I'm good there but what about Fastboot access via network TCP/IP or UDP? I was able to ADB to the Shield with "ADB connect [IP address]" but Fastboot doesn't see the unit at the same IP and I've looked on my router's device list and don't see anything. I have the latest 1.4.3 ADB/Fastboot tools.
So no access to flashing using the SD card slot, ethernet, or network?
THANKS!

KeepingItCuttingEdge said:
So I hadn't tried to flash a ROM on my "tube" Shield TV 2019 until the Experience 9 ROMs just leaked. I didn't realize it didn't have a USB port. I have been flashing ROMs on Android phones for over a decade, so I'm good there but what about Fastboot access via network TCP/IP or UDP? I was able to ADB to the Shield with "ADB connect [IP address]" but Fastboot doesn't see the unit at the same IP and I've looked on my router's device list and don't see anything. I have the latest 1.4.3 ADB/Fastboot tools.
So no access to flashing using the SD card slot, ethernet, or network?
THANKS!
Click to expand...
Click to collapse
I'm sorry, this is slightly off topic, but consider it a bump. haha. A quick question. Do you have a link for the experience rom? I would love to look at it, or do you know what OS they are rolling?

Hello,
trying to do the same but fastboot mode is as far as I get as well. Any ideas on how to flash the image on the tube?
@jenneh
Here you go . The OS is Android 11

KeepingItCuttingEdge said:
So I hadn't tried to flash a ROM on my "tube" Shield TV 2019 until the Experience 9 ROMs just leaked. I didn't realize it didn't have a USB port. I have been flashing ROMs on Android phones for over a decade, so I'm good there but what about Fastboot access via network TCP/IP or UDP? I was able to ADB to the Shield with "ADB connect [IP address]" but Fastboot doesn't see the unit at the same IP and I've looked on my router's device list and don't see anything. I have the latest 1.4.3 ADB/Fastboot tools.
So no access to flashing using the SD card slot, ethernet, or network?
THANKS!
Click to expand...
Click to collapse
Well I figured it out. First copy the downloaded image to the external sd card of the tube. Then:
When you reboot to fastboot using wifi ADB, then first unlock the bootloader.
Then choose "Boot recovery kernel" from the menu. The power button is located above the HDMI port on the tube.
When the dead android image appears, press the power button for 3 seconds and then release.
You should see the recovery menu. If you still see the dead android, then repeat the process by holding the power button pressed for 3-4-5-6 seconds. It can be tricky.
Once in the menu, choose the sd card.
Choose the file.
The process will start. and it should complete after a couple of minutes.
You are then done.
I did some extra steps:
I performed a factory reset and cleared cache from the recovery menu, although this happens automatically when you unlock the bootloader.
I then got back to the fastboot menu and locked the bootloader again. Otherwise you get a warning every time you boot the device.
Be ware that locking/unlocking the bootloader, erases the data of the user partition and the device needs to be setup as from a factory reset. This is by design.
Here is a link with all the images.
Cheers

m33ts4k0z said:
Well I figured it out. First copy the downloaded image to the external sd card of the tube. Then:
When you reboot to fastboot using wifi ADB, then first unlock the bootloader.
Then choose "Boot recovery kernel" from the menu. The power button is located above the HDMI port on the tube.
When the dead android image appears, press the power button for 3 seconds and then release.
You should see the recovery menu. If you still see the dead android, then repeat the process by holding the power button pressed for 3-4-5-6 seconds. It can be tricky.
Once in the menu, choose the sd card.
Choose the file.
The process will start. and it should complete after a couple of minutes.
You are then done.
I did some extra steps:
I performed a factory reset and cleared cache from the recovery menu, although this happens automatically when you unlock the bootloader.
I then got back to the fastboot menu and locked the bootloader again. Otherwise you get a warning every time you boot the device.
Be ware that locking/unlocking the bootloader, erases the data of the user partition and the device needs to be setup as from a factory reset. This is by design.
Here is a link with all the images.
Cheers
Click to expand...
Click to collapse
First of all, THANK YOU for this share~ ~! secondly, would you happen to have any idea why my usb ports have stopped working all of a sudden. I swear I didn't step on the shield this time. Lol

m33ts4k0z said:
he menu, choose the sd card.
Choose the file.
The process will start. and it should complete after a couple of minutes.
You are then done.
I did some extra steps:
Click to expand...
Click to collapse
m33ts4k0z said:
Hello,
trying to do the same but fastboot mode is as far as I get as well. Any ideas on how to flash the image on the tube?
@jenneh
Here you go . The OS is Android 11
Click to expand...
Click to collapse
false alarm Sir!!! I plugged my mouse in where the usbc cord usually goes, and i have access back! i was about to go return this sield to bestbuy for the 5th time for another hahaha

I want to go back from Android 11 to Android 9. It is possible to download a ROM for Shield 2019 Non Pro 8GB ATV 8.2.3? THX

There are links to the recovery firmware 8.2.3 but I can't get past the agree button that shows when klicking on the link..
It could be my old laptop.. but here's the link..
Gameworks Download Center
Get the latest Gameworks software for your game development work.
developer.nvidia.com
Sinse the update most of my aps are gone or not usable..
I can not fint the shield on my network.. and there is no installable apk showing up in any file manager.
I wil do my best to get back to android 9.

Tried to go back using the 8.2.3 recovery img.. but no luck.
I get an error saying cant flash over newer firmware.

Ugg... I didn't see this post that you can't downgrade until I tried it myself and also got the error.
Anybody have any possible work around ideas?

The same here:
The method I used is the one below according to nvidia's instructions:
Hardware Method:
- Disconnect power cable
- Connect power cable to SHIELD and hold down the remote locator button
- Release the keys once you see the fastboot menu on the screen (it's
red in color)
- If the standard boot process starts, disconnect the power cable and
repeat
the process
*******************************************************************************
FASTBOOT MENU NAVIGATION
*****
Once in fastboot mode (it's red in color), navigate the menus using the
remote locator button on the device.
Short press to navigate and long press for ~2s to select.
*******************************************************************************
FLASHING THE DEVICE
*****
To flash the recovery image to your SHIELD from fastboot, download the
image package.
- Download the image package. Copy the same downloaded zip file with
name
'nv-recovery-image-shield-atv-2019_.zip' to a uSD card that is FAT32
formatted
(where corresponds to the image version of the update being
installed).
Insert uSD card into the uSD card slot on the device
- in fastboot mode select Factory Data reset (opp in Recovery menu
scegli wipe data/factory reset)
- Enter recovery kernel by selecting the option "Boot recovery kernel"
from fastboot menu
- Once the device boots into recovery kernel, you will see a "No
command" image on the
screen
- Long press the remote locator button for ~2s and release button.
Recovery menu should show up (it's blue and green).
If not, please try to long press the button again
- On the recovery menu, select the option "apply update from SD card"
(navigate using short
press of remote locator button and long press ~4s to select and
release button)
- From the SD card contents, select the image package
- At anytime if the display goes back to the "No command" picture, press
the button for ~2s and release button
to go back to the previous screen
- Once the image is selected, the update process should start
Unfortunately the process interrupts with "newer build ....error status
7". I deleted the first two rows of UPDATE-SCRIPT, repacked in ZIP and
reflashed but in vain!! the error was:"Signature failure"
I also use SIGNAPK to sign the new ZIP, but in vain....
Any help?

Does anybody found solution to force downgrade (2019 nonPRO of course)?

Hello, I have a device that at this moment, after a failed update, ended up blocking..Now I turn it on, I feel that the nvidia heats up, but I don't have a signal on the television or anything, I've tried to do a reset but I haven't been successful because I am unable to enter to the fastboot screen... Does anyone who has gone through the same problem have any tips? Any help would be nice...Thanks

kuki68ster said:
Hello, I have a device that at this moment, after a failed update, ended up blocking..Now I turn it on, I feel that the nvidia heats up, but I don't have a signal on the television or anything, I've tried to do a reset but I haven't been successful because I am unable to enter to the fastboot screen... Does anyone who has gone through the same problem have any tips? Any help would be nice...Thanks
Click to expand...
Click to collapse
This is exactly what's happening to me. For some reason the network stopped working. I tried to see what happens if I factory reset. After the factory reset the device no longer displays anything. It does turn on and I can turn the tv and receiver on and off with the shield remote. I can enter the bootloader though.
Is this a coincidence or did the latest update screw something up?