Related
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
I bought the Motorola Bravo which is similar to the Flipside and an app on the market called Z4ROOT was able to root the phone. It works on many phones not just the Bravo. Give that try and see if it works.
z4root does work for permanent root i have tried and can confirm
jediskywalker said:
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
Click to expand...
Click to collapse
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Got my Flipside rooted and non market apps allowed
I followed the instructions given at modmymobile dot com forum. Look up "fully unlock 3rd party apps backflip" It allowed me to root my phone and install non market apps. I tried and tried to follow the instructions given here, but i guess they weren't idiot proof. It is for the backflip, but it worked perfectly for my Flipside. I couldn't post the link here.
Someone found some typos in my scripts. I have updated them so they are accurate. Should make things run better.
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
ishiiisbooyah said:
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
Click to expand...
Click to collapse
Lets say you installed your SDK in the default folder, you would need to type
Code:
cd c:\"Program Files"
cd Android
cd appinventor-extras
Now, I put mine in c:\SDK, so all I type is
Code:
cd c:\SDK
you either must add the SDK to your PATH, or find the directory that you installed it to, and then try running adb from there. If adb.exe isn't in the folder, you aren't in the right folder.
jonsjava said:
Rooting a Motorola Flipside
[/url]
Click to expand...
Click to collapse
hi
i m new in unlocking field
can i unlock this handset "flipside" by motorola came from usa at&T
if yes then plz explain
thanks in advance
RZ4root does not appear on the marketplace and when I click the link above it starts to download, then says the content is not supported on my phone.
Model num MB508 Motorola Flipside running Android 2.1 update 1.
You need to push it to the phone from a computer using adb to install z4root, now that it has been removed from the market.
Sent from my Liberty using Tapatalk
adb.exe not in the zip file
jonsjava said:
Rooting a Motorola Flipside
grab the ADB SDK files
android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
(...snipped...)
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Click to expand...
Click to collapse
adb.exe is not present in the SDK that you linked. Are you sure that is the SDK we need to root the Flipside?
You have to install it manually. It comes with the platform-tools.
how do i install adb.exe from platform-tools
lol, i may ask stupid questions but this one wasnt me, i shouldnt leave my laptop lying around haha
jonsjava said:
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Click to expand...
Click to collapse
Notice:
For anyone having trouble rooting the Motorola Flipside with these instructions, after much trial and error I managed to get my girlfriend's rooted. I'll provide the method I took.
Note: The easiest way to do this is to have downloaded and extracted "android-sdk_r08-windows" directly to your (C: ) drive. Not under programs or another system folder.
Once you have it extracted to (C: ), copy and paste z4root.1.3.0.apk into the "android-sdk_r08-windows" folder. ADB.exe will most likely not be in here. What you have to do now is click on SDK Manager within the SDK folder. A Black Command window will pop-up, ignore it. A secondary window will pop-up prompting you to install the packages I went ahead and installed all of them (better if you don't know which to install).
Now that they've all been installed, a command line will state that ADB has to be restarted. Let it restart and it should say completed.
Now -- here's where everything was messing up. When you click open the SDK-R08 folder, you should have the z4root.apk file right there amongst a list of folders. Go to the "platform-tools" folder and in there you should see the ADB.exe file. Ignore that for now. While in platform-tools press Ctrl+A so that everything is highlighted. Right click and select Cut, back out to the main directory of the SDK R08 folder and select Paste so that the ADB.exe, .dll, and all the other files from within platform-tools is out and listed alongside the z4root.apk.
Next - Follow all of the instructions up to "Plug in your phone, and have it set to "Charge only" Like JonsJava said, open up command prompt (type in CMD in the "search programs and files bar"). If you extracted the "android-sdk-r08-windows" file directly to the (C: ) drive, all you have to type in is...
(Note: Before I go into that, it'll be easiest to rename the file "SDK" instead of the whole "android-sdk, etc, name... I'll complete the instructions assuming you renamed it to SDK. Continued below... all you have to type in is...
cd C:\SDK
(The next line below will look like this)
c:\SDK>
Here, type in... adb install z4root.1.3.0.apk
Total should look like... c:\SDK>adb install z4root.1.3.0.apk
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Last note:
Uploaded with ImageShack.us
This is what the main directory of the SDK folder should look like before you enter anything in the command line.
I don't seem to be able to get this...
I'm using x64 windows 7, I have a Flipside MB508 on 2.1, and I can't get this to work.
I followed all the instructions, updated all the platform-tools stuff, and now my problem lies with the driver, I believe.
I installed those Motorola drivers that were linked, with my phone unplugged, successfully..
copied the apk to C:\SDK...
found adb.exe in the platform-tools folder..
...and this happened..
C:\SDK\tools>cd C:\SDK
C:\SDK>cd platform-tools
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
error: device not found
C:\SDK\platform-tools>_
"error: device not found" every time i try this
USB debugging is on, phone is plugged in set to charge only..
Windows even sees it, the taskbar eject icon says 'Eject MB508"
please please help me get adb to see my phone.. I really want to be able to root this thing!!
EDIT: I noticed the Motorola drivers are 32bit.. I'm going to try 32 bit windows 7 instead of 64 bit and see if I get more successful results
EDIT 2: Bazinga!! Installed Win7 32 bit on my other HDD, booted up, followed the steps again, worked flawlessly! Thanks a lot for the easy instructions, got z4root installed, and my phone worked with permanent root
ErebusRaze said:
Notice:
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Click to expand...
Click to collapse
You wrote in here that once rooted, thebphone would no longer have low memory issues...i rooted my wife's phone, was able to sideload applications (but for some strange reason I am now unable to, as adb command prompt states 'device not found')- but she still gets low memory issues at least 2-3 times a week...
I should just hold up a sign...
LINK2SD
Its in the market
Sent from my MB508 using XDA App
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
thehotrod11 said:
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
Click to expand...
Click to collapse
Link2sd makes installing to sd card possible on 2.1...
Sent from my MB508 using XDA App
I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
First of all thanks to all amazing people on this forum ( thecubed,777jon,Dees_Troy, chainfire, supernoman, crashfocus, etc)
This is not my work . It is a compilation of what it worked for me from the work made by others. It is directly toward newbie users.
Instructions
1- Make sure you install LG G3 drivers in your computer( you can get them attached on this thread). Connect phone to the PC using USB cable. Make sure the phone is recognized when you plug it in with the usb cable
Also phone shall be connected as Media device (MTP), if it is in Charge Phone change it to MTP.
Scroll down this post. You will find the correct usb drivers attached. Install them in your pc.
2- Enable Developer options in your phone on Setting > General> About phone > Software information > and click seven times Build number until it enables it
3- Enable USB debugging on your LG G3 from your phones Settings > Developer options > tick ‘USB debugging’ check box. A window should pop up in your phone display to allow USB debugging. Select Allways Allow from This Computer and hit OK.
It will also be convenient to Enable installation of apps from Unknown Sources: Open phone’s Settings » select Security » Tick the “Unknown sources” check box (under Device administration section)
4- Download and unzip
- Pupledrake-Lite at http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-Lite_R03.tar.gz Thanks to Codefi.re
- Download and unzip the attached ADB LOCAL READY with TWRP recovery.img
Thanks to @Dees_Troy & TeamWin - for TWRP Touch recovery
ATTACHMENT IS HERE- JUST CLICK HERE
5- Download -Latest SuperSu at http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip Thanks to Chainfire
6- Transfer UPDATE-SuperSU-v2.40.zip to the internal sdcard
7- Open Purpledrake-Lite and Run purpledrake_windows.bat. It should detect your devices if it is not, you need to check if the drivers were installed properly and unplug-plug back your phone.
Hit Enter as instructed on the computer screen until it gains temporary root.
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD.
Hit Ctrl+C to exit to use adb.
This process takes a few seconds and The phone start on download mode and it will stay on it.
8- Open ADB LOCAL READY folder you downloaded and hit Start Here.bat
Type "adb devices" to ensure that your phone is connected and it accept adb commands . On list of devices attached it should show LGD851........
Unplug it and plug it back if it is not .
NOTE: SOME PEEPS HAVE REPORTED PROBLEM WITH ADB NOT WORKING PROPERLY ON USB 3.0 PORTS. PLEASE USE USB 2.0 PORTS
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds
Note: you may need to push it a few times if you do not find the recovery file on the /temp folder when you do step 12.
Some members stated that they need to push it ..5 times.
rubbamade tip
" This does work. If after you do the "adb push....", Hit the up key on your keyboard. What you just typed " adb push...." will appear again. Hit enter. It will "push" again. Hit up again. Hit enter. Do this at least 5 times. Now proceed with next step "adb shell"..... Should work now"
For some reason others user needed to push it more than 5 times, i assume that it is due to the file size of the image and your operating system and pc settings(i used win7). It is recommended to verify if it was pushed on step 12.
10- Type "adb shell" and it should go to shell command $
11- Then type "/temp/fakesu". This will put you in a superuser shell on your device. It should show su command line # .
12- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
14- Type type "reboot recovery" It should boot onto TWRP Touch recovery. it could take a few but it should
15- Once in TWRP, select install,go to the SD card directory, select UPDATE-SuperSU-v2.40.zip and install it. Reboot the phone once complete. Do not panic, it should take a while to cook and update applications, but it will, be patient.
16- Your device is rooted and with TWRP custom recovery. IF you do not see SuperSu in your application drawer, do not panic, just install it from the Play Store.
17- Now you are ready to install custom Roms, any application that requires root, or enjoy root features.
Quick References
How to Boot into TWRP(Recovery Mode)
1.Turn off your phone
2.Now, press and hold Power and Volume down buttons at the same time.
3.When the LG logo appears, release the keys.
4.Immediately press Power and Volume Down buttons again until the Hard Reset menu will be displayed.
5.Press volume down to Select "YES" on reset data. Do not panic, it will not . Select "yes" again . It will boot into TWRP recovery mode.
If you do not like hardware method you can use Quickboot or TWRP Manager applications from the Play store
How to Boot LG G3 Download Mode
-Disconnect your phone from PC.
-Power off your G3 and wait 4-5 seconds after lights go off.
-Hold the Volume Up button on phone, and while holding it, connect the phone to PC using a USB cable
If you get the "Windows cannot find '.\assets\windows\bin\mintty.exe'." error..on purpledrake temproot step 7.
Try just double-clicking on the .bat instead of running as admin.
Also make sure the script is extracted properly first before running
Disclaimer: It worked for me, but I am not responsible for any damages to your phone.
Your experience is very interesting vcurbel!
I was under the impression there was no way to root untouched stock 10R.
It would appear you have found a way! :good: Thanks for your contribution.
I am curious if anyone else has replicated this?
thank you so much had a little trouble but successfully rooted my device
Where was this guide yesterday?
Last week I just thought rooting build R was impossible as of yet, got fed up, and 5 minutes ago ran the LG Update tool to revert my phone back to stock/ Build C and root that way.
vcurbel said:
I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
Click to expand...
Click to collapse
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!
NO GO
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
AT THIS POINT I AM GETTING "NOT FOUND". DID THE STEPS ABOVE SEVERAL TIMES.
I saw 8xxxkb data pushed after 'push'
==========================================================================================
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9716 KB/s (11245568 bytes in 1.130s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
#
=========================================================================================
sharkoparko said:
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
/temp/fakesu: Is: not found
#
=========================================================================================
Click to expand...
Click to collapse
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13
vcurbel said:
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13
Click to expand...
Click to collapse
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
===================================================================================
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... Found device!
Your phone is a [ LG-D851 ] on [ TMO ] running SW version [ V10r ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .... Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
Temproot worked, all done here. Moving on...
Alright, now that you're temprooted, you can press CTRL-C here and get
a temproot prompt through 'adb shell /temp/fakesu' if you're so inclined...
However, if you'd like to permaroot, let's continue.
Press [enter] to continue...
===============================================================================================
DO I NEED TO RE-ROOT?
sharkoparko said:
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....
DO I NEED TO RE-ROOT?
Click to expand...
Click to collapse
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
vcurbel said:
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).
sharkoparko said:
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).
Click to expand...
Click to collapse
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app
Just got home with a Craigslist buy.
rooted in 15min thanks vcurbel !
now to find CM12 for this baby
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app
all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
vcurbel said:
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator
tomez206 said:
all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator
Click to expand...
Click to collapse
It seems your windows os is missing the default mintty.exe terminal...
Google it and you will find a solution to manually install it.
Or use other pc
Sent from my LG-D851 using XDA Free mobile app
tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
If I recall if the PD batch file/script is closing on you or giving you trouble, then you can run the script manually.
See link below to thecubed PD lite thread and read the 5th grey portion down of the OP, it is titled:
"But, what if I don't want to run your script to root?"
If you must use command line because the PD batch file/script is closing immediately just be sure to STOP after gaining temporary root!
From OP step 7:
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD. [/FONT]
lagvoid said:
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!
Click to expand...
Click to collapse
Hello,
I am also having the same issue. I tried the above steps a couple times and am not sure if I am doing something wrong (more than likely I am). What did you mean by repush recovery?
Try step 9 again
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds
vcurbel said:
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9682 KB/s (11245568 bytes in 1.134s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
# dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
/temp/recovery.img: cannot open for read: No such file or directory
#
--------------------------------------------------------------------------------
Yes, The phone is recognized and the file as you see was pushed (see script above). I think there is some issue with this method, as other people are reporting problems following the procedure in post #1??!! I guess it work for some and it does not for others.
Noob again. So I am rooted and I'm currently on build NDE63X on my Verizon 128 gb XL. If i understood the instructions correctly, I have to go back to stock before I can put TWRP on the phone. I know I get the factory images here.
https://developers.google.com/android/images
Do I get the NDE63P image for the phone since that was what was on the phone before I sideloaded the OTA for my current version which is NDE63X or do I just need to download the full image for NDE63X?
Can someone also list the steps needed to accomplish getting phone back to stock? I read Google's instructions and I was a little confused. I understand that I will lose root but should be able to root after installing TWRP since it looks like Chainfire updated the root method for those using TWRP.
Thanks.
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it. ?
Sent from my Pixel XL
Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
Thank you. Gonna attempt it this weekend.
Deleted
Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Veid71 said:
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Click to expand...
Click to collapse
https://developers.google.com/android/images
Sent from my Pixel XL
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
chipslate said:
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
Click to expand...
Click to collapse
if you are executing the commands, you are in fastboot, not adb.
try fastboot devices
if it doesnt return anything, your computer is not seeing the device.
you will need the computer to see the device in fastboot before you can proceed.
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
first thing to try is to go into fastboot, then unplug the cable, and then plug it back in.
if it is still not recognized, then its either an outdated adb/fastboot issue, or a driver issue (if you are using windows, if not there may be other possibilities).
chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
When it finds your phone does it say unauthorized or authorized?
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
chipslate said:
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
Click to expand...
Click to collapse
What happens now when you attempt the next command?
Edit: So after running adb devices, you should be running adb reboot bootloader command next I believe.
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Also, I have the phone in MTP File Transfer mode and USB Debugging enabled.
chipslate said:
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Click to expand...
Click to collapse
You should now use the flash-all command but this is going wipe all of your data.
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
chipslate said:
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
Click to expand...
Click to collapse
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
magestic1995 said:
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
Click to expand...
Click to collapse
It finally worked!!! Thanks again for your help and going back and forth. I finally installed Android Studio and it inserted the ADB drivers at the top of Device manager. Worked like a charm then. Finally, Android 7.1.1 and unlocked bootloader... Bring it on, world!
Congrats! I've only used Android Studio for all this stuff since Im a developer. Congrats on getting it all figured out!
i have been trying to take my pixel xl back to stock but the flash-all.bat script hangs on the part where it should flash the system img zip. it says the file size is to large
(Note before you begin: If you have a SHIELD TV 2017, you will need a quality Male-to-Male USB Type A cable to connect your SHIELD TV to a PC. If you have a SHIELD TV 2015 or a SHIELD TV Pro, you may be able to just use a regular micro USB cable, because those two models have a micro USB port)
A. Download these files to your PC:
Download the Android SDK Platform-Tools
Download the Official NVIDIA SHIELD family Windows USB Drivers
Download the Magisk Manager APK (This is the latest version as of the time of writing)
Download the ***CORRECT*** NVIDIA SHIELD Experience Upgrade v7.2 Image for your model
(You will need to register for a Developer Account if you don't already have one. Flashing the wrong image will BRICK your device)
B. Setting up Android SDK Platform-Tools on your PC:
On your PC, extract the Android SDK Platform-Tools somewhere where you can find them
Add the platform-tools folder to PATH in the Windows System Environment Variables (Instructions HERE or HERE)
C. Installing the Official NVIDIA SHIELD family Windows USB Drivers on your PC:
On your SHIELD TV, enable developer options and debugging (Instructions HERE)
Using a Male-to-Male USB Type-A Cable, connect the USB port further away from the HDMI port on your SHIELD TV to your PC
On your PC, extract the Official NVIDIA SHIELD family Windows USB Drivers somewhere where you can find them
Open Device Manager and find the new device
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
adb devices
On your SHIELD TV, a prompt will pop up asking you to allow ADB access from your computer. Check the box to remember your selection and then Grant Access
On your PC, the Command Prompt should show the serial number of your SHIELD TV
(You may have to run the 'adb devices' command again since it may have timed out the first time waiting on you to authorize the ADB connection on the SHIELD TV)
Boot the SHIELD TV into bootloader/fastboot mode by typing the command:
Code:
adb reboot bootloader
(Alternatively, you can enter bootloader/fastboot mode by following the instructions HERE)
On your PC, open the Device Manager again and find the new device (it will probably have an error with a yellow triangle)
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one NOT relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
fastboot devices
The Command Prompt should show the serial number of your SHIELD TV
D. Unlocking the bootloader on your SHIELD TV (CAUTION: THIS WILL WIPE YOUR DATA AND FACTORY RESET YOUR SHIELD TV)
Plug the NVIDIA SHIELD TV Game Controller or a USB Keyboard into the USB port closest to the HDMI port on your SHIELD TV
In bootloader/fastboot mode on your SHIELD TV, select "Unlock Bootloader", read the message and confirm
(Use the Y and X buttons to scroll UP and DOWN, and the A button to CONFIRM selection, if your button presses aren't doing anything you need to reboot the SHIELD TV into bootloader/fastboot mode with the Controller or Keyboard already plugged in)
On your PC, open a Command Prompt and reboot your SHIELD TV to the OS by typing:
Code:
fastboot reboot
This process only needs to be done once per device and you will not have to unlock the bootloader again for subsequent updates
(From now on while your bootloader is unlocked, your SHIELD TV will display a warning message when it first boots saying that the system cannot check for corruption. This is perfectly normal and the boot process will resume automatically after a few seconds. There is no need to relock your bootloader unless you are selling the device or something. NEVER lock the bootloader if you have anything other than 100% stock full RECOVERY Image installed. Never even try it.)
E. Installing Magisk Manager on your SHIELD TV and Patching your boot.img
On your PC, extract the NVIDIA SHIELD Experience Upgrade v7.2 Image that you downloaded to somewhere where you can find it
Find the boot.img file in the folder that you extracted it to
Open a Command Prompt and type:
Code:
adb push boot.img /storage/emulated/0/Download/
Install Magisk Manager by typing 'adb install [path-to-magiskmanagerapk]' example:
Code:
adb install C:\MagiskManager-v6.1.0.apk
On your SHIELD TV, open Magisk Manager [Settings > Device > Apps > Magisk Manager > Open]
(The Magisk Manager App Interface is not designed to be operated with an Android TV Remote so I suggest you install the NVIDIA SHIELD TV app on your phone. Once paired with your SHIELD TV, the app has an option to let you use a virtual mouse to navigate and interact with your SHIELD TV. Alternatively, you can plug a USB Mouse into the USB port closest to the HDMI port on your SHIELD TV)
If Magisk Manager automatically pops up and asks you if you would like to Install Magisk, select Cancel
Make sure the "Preserve AVB 2.0/dm-verity" option is checked, and then select "Install"
Select "Patch Boot Image File"
Using the Virtual Mouse on the NVIDIA SHIELD TV remote app on your phone, or a USB Mouse, navigate to the "Download" folder on your internal storage and select the boot.img file that you copied over then click Open
Magisk Manager will take a few moments to patch the boot.img (pay attention to the message in the console about the path to the patched_boot.img - It should be "/storage/emulated/0/Download/patched_boot.img"
On your PC, in the Command Prompt type:
Code:
adb pull /storage/emulated/0/Download/patched_boot.img
F. Installing Magisk rooted SHIELD Experience Upgrade v7.2 on your SHIELD TV:
On your PC, navigate to the folder where you extracted the NVIDIA SHIELD Experience Upgrade v7.2 Image
Find the boot.img and rename it to boot.img.bak
Rename the patched_boot.img to boot.img
Open a Command Prompt and type:
Code:
adb reboot bootloader
Once the SHIELD TV is in bootloader/fastboot mode, type:
Code:
flash-all.bat
(It will take a few minutes for the flashing process to finish and then the SHIELD TV will automatically reboot to the OS)
Optional Stuff and Additional Information:
Disable Auto-Upgrades by going to [Settings > Device > About > System upgrade > Auto-upgrade]
Enable Full OTA's instead of Partial/Differential by going to [Settings > Preferences > Developer options > Provide full system upgrades]
(It is the very last option at the bottom and this is very important when using a rooted device and modifications to the System partition are likely)
If you want to upgrade to a new OTA update with root without waiting on NVIDIA to post the Developer/Recovery images, the downloaded OTA file is in
Code:
/data/data/com.nvidia.ota/app_download
(You will need a root file explorer to be able to access this directory)
You can extract the boot.img from the OTA zip and patch it using the same method described in step E.5 through E.10
You can then install the OTA the normal way [Settings > Device > About > System upgrade > Check for upgrade]
(Make sure you have copied the OTA zip or extracted the boot.img to somewhere on your Internal Storage like "/storage/emulated/0/Download" BEFORE you install the OTA because the system will delete the file in "/data/data/com.nvidia.ota/app_download" when it installs the update and you will be unable to get it after that)
Copy the patched_boot.img that you made with Magisk to your PC
Reboot to bootloader/fastboot mode with:
Code:
adb reboot bootloader
Manually flash just the Magisk Patched boot:
Code:
fastboot flash boot patched_boot.img
Manually reboot back to the OS with:
Code:
fastboot reboot
Hey mate, just curious if you have full root access, eg, can you uninstall system apps or delete their folders in system/apps, only asking as I also thought I had gained full root access with patching the boot.img with Kantjers version of Magisk, but when I try to uninstall a system app or try and delete their respective folders, even though it appears in Magisk that I have full root access, when I try to uninstall or delete a system app folder, I actually don't have full root access.
whiteak said:
Hey mate, just curious if you have full root access, eg, can you uninstall system apps or delete their folders in system/apps, only asking as I also thought I had gained full root access with patching the boot.img with Kantjers version of Magisk, but when I try to uninstall a system app or try and delete their respective folders, even though it appears in Magisk that I have full root access, when I try to uninstall or delete a system app folder, I actually don't have full root access.
Click to expand...
Click to collapse
I don't modify the system partition if I can avoid it. I just disable System Apps if I want them gone; however, I am fully confident that I could delete anything in /system if I wanted to. Is /system mounted as +rw? Not all Root File Managers are created equal. I recommend Root Explorer. It is not the most modern and feature rich file manager, but when it comes to Root File Managers specifically, I haven't found any other that can compare.
Thanks for the reply, not a big deal, was just curious if you actually did have full root access as it appears I do as well until I actually need it to do something like delete a system app etc. I may try flashing your patched boot.img and see if I get the same results as my patched boot.img, may just come down to the fact that I'm using Kantjers version of Magisk etc, wouldn't think it would be any different, but never know I guess until I try. Thanks again.
whiteak said:
Thanks for the reply, not a big deal, was just curious if you actually did have full root access as it appears I do as well until I actually need it to do something like delete a system app etc. I may try flashing your patched boot.img and see if I get the same results as my patched boot.img, may just come down to the fact that I'm using Kantjers version of Magisk etc, wouldn't think it would be any different, but never know I guess until I try. Thanks again.
Click to expand...
Click to collapse
I would test it for you if I had a system.img for v7.2.1 that I could reflash real quick. I just don't feel like flashing v7.2.0 then updating to v7.2.1 again to restore an unmodified system partition.
ACiDxCHRiST said:
A. Download these files to your PC:
Download the Android SDK Platform-Tools HERE
Download the Official NVIDIA SHIELD family Windows USB Drivers HERE
Download Magisk Manager APK (Link to latest version at time of writing is HERE)
Download the ***CORRECT*** NVIDIA SHIELD Experience Upgrade v7.2 Image for your model HERE
(Flashing the wrong boot.img will BRICK your device You will need to register for a Developer Account if you don't already have one)
B. Setting up Android SDK Platform-Tools on your PC:
On your PC, extract the Android SDK Platform-Tools somewhere where you can find them
Add the platform-tools folder to PATH in the Windows System Environment Variables (Instructions HERE)
C. Installing the Official NVIDIA SHIELD family Windows USB Drivers on your PC:
On your SHIELD TV, enable developer options and debugging (Instructions HERE)
Using a Male Type-A to Male Type-A USB Cable, connect the USB port further away from the HDMI port on your SHIELD TV to your PC
On your PC, extract the Official NVIDIA SHIELD family Windows USB Drivers somewhere where you can find them
Open Device Manager and find the new device
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
adb devices
On your SHIELD TV, a prompt will pop up asking you to allow ADB access from your computer. Check the box to remember your selection and then Grant Access
On your PC, the Command Prompt should show the serial number of your SHIELD TV
(You may have to run the 'adb devices' command again since it may have timed out the first time waiting on you to authorize the ADB connection on the SHIELD TV)
Boot the SHIELD TV into bootloader/fastboot mode by typing the command:
Code:
adb reboot bootloader
(Alternatively, you can enter bootloader/fastboot mode by following the instructions HERE)
On your PC, open the Device Manager again and find the new device (it will probably have an error with a yellow triangle)
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one NOT relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
fastboot devices
The Command Prompt should show the serial number of your SHIELD TV
D. Unlocking the bootloader on your SHIELD TV (WARNING: THIS WILL WIPE YOUR DATA AND FACTORY RESET YOUR SHIELD TV)
Plug the NVIDIA SHIELD TV Game Controller or a USB Keyboard into the USB port closest to the HDMI port on your SHIELD TV
In bootloader/fastboot mode on your SHIELD TV, select "Unlock Bootloader", read the message and confirm
(Use the Y and X buttons to scroll UP and DOWN, and the A button to confirm selection, if your button presses aren't doing anything you need to reboot the SHIELD TV into bootloader/fastboot mode with the Controller or Keyboard already plugged in)
On your PC, open a Command Prompt and reboot your SHIELD TV to the OS by typing:
Code:
fastboot reboot
E. Installing Magisk Manager on your SHIELD TV and Patching your boot.img
On your PC, extract the NVIDIA SHIELD Experience Upgrade v7.2 Image that you downloaded to somewhere where you can find it
Find the boot.img file in the folder that you extracted it to
Open a Command Prompt and type:
Code:
adb push boot.img /storage/emulated/0/Download/
Install Magisk Manager by typing 'adb install [path-to-Magisk-Manager-APK]' example:
Code:
adb install C:\MagiskManager-v6.1.0.apk
On your SHIELD TV, open Magisk Manager [Settings > Device > Apps > Magisk Manager > Open]
(The Magisk Manager App Interface is not designed to be operated with an Android TV Remote so I suggest you install the NVIDIA SHIELD TV app on your phone. Once paired with your SHIELD TV, the app has an option to let you use a virtual mouse to navigate and interact with apps on your SHIELD TV. Alternatively, you can plug in a USB Mouse into the USB port closest to the HDMI port on your SHIELD TV)
If Magisk Manager automatically pops up and asks you if you would like to Install Magisk, select Cancel
Make sure the "Preserve AVB 2.0/dm-verity" option is checked, and then select "Install"
Select "Patch Boot Image File"
Using the Virtual Mouse on the NVIDIA SHIELD TV remote app on your phone, or a USB Mouse, navigate to the "Download" folder on your internal storage and select the boot.img file that you copied over then click Open
Magisk Manager will take a few moments to patch the boot.img (pay attention to the message in the console about the path to the patched_boot.img - It should be "/storage/emulated/0/Download/patched_boot.img"
On your PC, in the Command Prompt type:
Code:
adb pull /storage/emulated/0/Download/patched_boot.img
F. Installing Magisk rooted SHIELD Experience Upgrade v7.2 on your SHIELD TV:
On your PC, navigate to the folder where you extracted the NVIDIA SHIELD Experience Upgrade v7.2 Image
Find the boot.img and rename it to boot.img.bak
Rename the patched_boot.img to boot.img
Open a Command Prompt and type:
Code:
adb reboot bootloader
Once the SHIELD TV is in bootloader/fastboot mode, type:
Code:
flash-all.bat
(It will take a few minutes for the flashing process to finish and then the SHIELD TV will automatically reboot to the OS)
Optional Stuff and Additional Information:
Disable Auto-Upgrades by going to [Settings > Device > About > System upgrade > Auto-upgrade]
Enable Full OTA's instead of Partial/Differential by going to [Settings > Preferences > Developer options > Provide full system upgrades]
(It is the very last option at the bottom and this is very important when using a rooted device and modifications to the System partition are likely)
If you want to upgrade to a new OTA update with root without waiting on NVIDIA to post the Developer/Recovery images, the downloaded OTA file is in
Code:
/data/data/com.nvidia.ota/app_download
(You will need a root file explorer to be able to access this directory)
You can extract the boot.img from the OTA zip and patch it using the same method described in step E.5 through E.10
You can then install the OTA the normal way [Settings > Device > About > System upgrade > Check for upgrade]
(Make sure you have copied the OTA zip or extracted the boot.img to somewhere on your Internal Storage like "/storage/emulated/0/Download" before you install the OTA because the system will delete the file in "/data/data/com.nvidia.ota/app_download" when it installs the update and you will be unable to get it after that)
Copy the patched_boot.img that you made with Magisk to your PC
Reboot to bootloader/fastboot mode with:
Code:
adb reboot bootloader
Manually flash just the Magisk Patched boot:
Code:
fastboot flash boot patched_boot.img
Manually reboot back to the OS with:
Code:
fastboot reboot
Click to expand...
Click to collapse
Thankyou ever so much for putting this together but after following exactly what you said in this guide this is what i get:
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 10.295s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.641s
< waiting for any device >
sconnyuk said:
Thankyou ever so much for putting this together but after following exactly what you said in this guide this is what i get:
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 10.295s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.641s
< waiting for any device >
Click to expand...
Click to collapse
Do you have a 2015 or a 2017 SHIELD TV? Assuming you didn't edit that directory name, it should be nv-recovery-image-shield-atv-2017-7.2.0
If you have a 2017 and did manage to flash that image without an error, it would have bricked your SHIELD TV.
Do you still have Minimal ADB installed? I kind of feel like your fastboot.exe is outdated. I feel like your Minimal ADB install is registered to PATH and whenever a command calls fastboot, it is running the outdated fastboot in your Minimal ADB install.
ACiDxCHRiST said:
Do you have a 2015 or a 2017 SHIELD TV? Assuming you didn't edit that directory name, it should be nv-recovery-image-shield-atv-2017-7.2.0
If you have a 2017 and did manage to flash that image without an error, it would have bricked your SHIELD TV.
Do you still have Minimal ADB installed? I kind of feel like your fastboot.exe is outdated. I feel like your Minimal ADB install is registered to PATH and whenever a command calls fastboot, it is running the outdated fastboot in your Minimal ADB install.
Click to expand...
Click to collapse
I have 2017 Shield TV 16gb, which is on stock 7.2.1
I am using platform tools you suggested previously.
im quite sure im downloading the correct version, yes i do rename certain folders when i extract (just like i did with platform-tools to platform tools etc.
Im wondering if because im using standard usb 2.0 a to a cable is problem ? , aswell as both my laptop and desktop computers are older usb 2.0 models?
Both cables i have are usb 2.0 a to a but never had problems using with other devices including amazon fire tv 2 4k box when i had to recover it. Also i can adb push/pull/install no problems.
I have tried selecting unlock bootloader again just to triple check its unloacked and it reports bootloader is already un locked.
Im running out of ideas to be honest, quite the nightmare im having.
sconnyuk said:
I have 2017 Shield TV 16gb, which is on stock 7.2.1
I am using platform tools you suggested previously.
im quite sure im downloading the correct version, yes i do rename certain folders when i extract (just like i did with platform-tools to platform tools etc.
Im wondering if because im using standard usb 2.0 a to a cable is problem ? , aswell as both my laptop and desktop computers are older usb 2.0 models?
Both cables i have are usb 2.0 a to a but never had problems using with other devices including amazon fire tv 2 4k box when i had to recover it.
I have tried selecting unlock bootloader again just to triple check its unloacked and it reports bootloader is already un locked.
Im running out of ideas to be honest, quite the nightmare im having.
Click to expand...
Click to collapse
I don't see USB 2.0 being an issue. You could try locking then unlocking your bootloader again.
Also try running with an elevated Command Prompt with admin rights.
ACiDxCHRiST said:
I don't see USB 2.0 being an issue. You could try locking then unlocking your bootloader again.
Also try running with an elevated Command Prompt with admin rights.
Click to expand...
Click to collapse
Yes i always use admin rights with CMD.
I will try re locking and unlocking again later today. (i cant see how nobody else has had issues like mine)
Thanks, il report back.
---------- Post added at 09:00 AM ---------- Previous post was at 08:36 AM ----------
Just tried re locking my bootloader then unlocking again and get same output:
Just for your info the download im using is 'nv-recovery-image-shield-atv-2017-7.2.0.zip' like i said i had a few downloaded alreadyh so just renamed it.
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 6.297s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.853s
< waiting for any device >
sconnyuk said:
Just tried re locking my bootloader then unlocking again and get same output:
Just for your info the download im using is 'nv-recovery-image-shield-atv-2017-7.2.0.zip' like i said i had a few downloaded alreadyh so just renamed it.
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 6.297s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.853s
< waiting for any device >
Click to expand...
Click to collapse
I googled your error and I found a post that said changing cables fixed the problem. So that is at least one piece of information that points towards your hardware setup being the issue. I don't know what else to tell you.
ACiDxCHRiST said:
I googled your error and I found a post that said changing cables fixed the problem. So that is at least one piece of information that points towards your hardware setup being the issue. I don't know what else to tell you.
Click to expand...
Click to collapse
Yes even though I've got 2 here I'm going to try another, now if my local computer shop is open today I'll grab one to try.
As soon as I get a cable I'll report back and let you know, at the very least this might help someone with any issues that turn out to be similar to mine.
I was even thinking of trying to get twrp on or even boot to it to flash the boot.img but it's a no go on 7.2.1 and more so it's a no go because nothing will flash through fastboot for me at the moment.
I'll be in touch. ?
sconnyuk said:
Yes even though I've got 2 here I'm going to try another, now if my local computer shop is open today I'll grab one to try.
As soon as I get a cable I'll report back and let you know, at the very least this might help someone with any issues that turn out to be similar to mine.
I was even thinking of trying to get twrp on or even boot to it to flash the boot.img but it's a no go on 7.2.1 and more so it's a no go because nothing will flash through fastboot for me at the moment.
I'll be in touch.
Click to expand...
Click to collapse
Here is the cable that I use: https://www.amazon.com/Cable-Matters-2-Pack-Male-Black/dp/B00HSS9IDW
Finally, i decided to butcher 2 good thick usb cables and bodge a new a to a cable together and it flashed first time
Thanks for all your help.
Cannot understand how i have had issues with 2 different cables but now we know this device must be picky.
sconnyuk said:
Finally, i decided to butcher 2 good thick usb cables and bodge a new a to a cable together and it flashed first time
Thanks for all your help.
Cannot understand how i have had issues with 2 different cables but now we know this device must be picky.
Click to expand...
Click to collapse
Awesome
ACiDxCHRiST said:
Awesome
Click to expand...
Click to collapse
So from a virgin 7.2.1 we can after all flash a modded boot ??.
Just have to wait for a TWRP that is working on 7.2.1 now.
Thanks again for your help, I'd probably of given up after all that untill you mentioned the lead.
I did have a sneaky feeling myself but wasn't gunna try a new one till after Christmas.
sconnyuk said:
So from a virgin 7.2.1 we can after all flash a modded boot .
Just have to wait for a TWRP that is working on 7.2.1 now.
Thanks again for your help, I'd probably of given up after all that untill you mentioned the lead.
I did have a sneaky feeling myself but wasn't gunna try a new one till after Christmas.
Click to expand...
Click to collapse
What do you need TWRP for?
Thank you ACiDxCHRiST, for creating a new guide. It takes a considerable amount of time to first find a solution that is repeatable, document everything, test it, etc... :good: well done.
I have a question for you if I may. I've been trying to understand what Magisk actually patches. I've read through their web site and other than rooting it doesn't go into to many details about what else it patches or modifies. Do you have any additional information about this?
Once you've installed the patched_boot.img, and you first boot your Nvidia Shield TV are you required to first connect to the internet, then sign-in to Google Play and assuming the existing Nvidia Experience software is not already updated to the latest release, does it begin to download the and force you to install the latest update?
ACiDxCHRiST said:
What do you need TWRP for?
Click to expand...
Click to collapse
Just for backups, I'd like to get my system all setup exactly like I want it and then create a backup.
Also if any magisk/xposed modules make my box not boot to restore also ??
nadia p. said:
Thank you ACiDxCHRiST, for creating a new guide. It takes a considerable amount of time to first find a solution that is repeatable, document everything, test it, etc... :good: well done.
I have a question for you if I may. I've been trying to understand what Magisk actually patches. I've read through their web site and other than rooting it doesn't go into to many details about what else it patches or modifies. Do you have any additional information about this?
Once you've installed the patched_boot.img, and you first boot your Nvidia Shield TV are you required to first connect to the internet, then sign-in to Google Play and assuming the existing Nvidia Experience software is not already updated to the latest release, does it begin to download the and force you to install the latest update?
Click to expand...
Click to collapse
The SHIELD TV will only force you to update when you are going through the Initial Setup after a data wipe. If you follow the guide exactly as written and your bootloader is not unlocked yet, you will be forced to update to v7.2.1 after unlocking the bootloader. But since there aren't any more data wipes and the last step is to flash the v7.2.0 image that we modified, you will end up on v7.2.0 without being forced to do the Initial Setup again. In fact, you could likely use the same steps in the guide to install other versions.
As for what Magisk patches, it modifies the bootloader to trick the OS into thinking that the SU binary is in the system partition without actually modifying the system partition.
sconnyuk said:
Just for backups, I'd like to get my system all setup exactly like I want it and then create a backup.
Also if any magisk/xposed modules make my box not boot to restore also
Click to expand...
Click to collapse
Roger that, makes sense.
first off, huge shout out to @JengaMasterG for TWRP for these devices. Without him, this super simple method wouldn't be possible.
What You'll Need
- Android 11 most recent update
- TWRP: TWRP for Surface Duo (credits to @JengaMasterG )
- Unlocked Bootloader
- ADB/Fastboot: ADB/Fastboot Install (what i use)
- Magisk
video
YT Tutorial
Bootloader Unlock
1.) Enable Developer Options via tapping Build Number over and over in the About Device part of settings
2.) Enable USB Debugging and OEM Unlock
3.) Plug device into the computer, and type the following command in cmd.exe, hit enter
Code:
adb devices
4.) You may get a pop up on screen requesting permission, always allow it
5.) Type the following and hit enter
Code:
adb reboot bootloader
6.) Once in the bootloader, your device might not be recognized right away and will need the driver manually installed via Device manager (see video for that)
7.) Once device is recognized, type the following command
Code:
fastboot flashing unlock
8.) Allow the unlocking of the Bootloader on device screen. this will erase everything
9.) Allow the device to fully boot up, enable USB Debugging again and continue the tutorial!
Instructions
1.) Rename Magisk-vxx.x.apk to Magisk.zip
2.) Enable USB Debugging
3.) Type the following to make sure your computer sees the device (in cmd.exe)
Code:
adb devices
4.) You may get a pop up on your device's screen asking for adb permission, check the always allow and hit ok
5.) Type the follow command to reboot to bootloader (in cmd.exe)
Code:
adb reboot bootloader
6.) Once you're in the booloader and its unlocked, download the TWRP image from above
7.) Use the following fastboot command to boot into TWRP
Code:
fastboot boot twrp.img
8.) Once TWRP boots, keep your device plugged in via usb and type the following command into cmd.exe and hit enter
Code:
adb shell twrp sideload
9.) Once in sideload, you can type the following with magisk.zip and root your device!
Code:
adb sideload magisk.zip
10.) Use the following command to reboot and you're done!
Code:
adb reboot
congrats! you're rooted!
LETS GOOOO!! HEROOO!! Super easy and working on the latest December 2022 update! Felt way safer as well, not so much concern over twrp as we only booted into it, and then I just used the standard magisk and it worked excellent without worrying about all types of patches and versions aside from the latest twrp for android 12 from @JengaMasterG!
Thank you! I think the renaming the magisk file from apk to zip was probably what I was doing wrong trying to follow the other methods, on top of driver errors, that were solved by uninstalling all the drivers for the duo on my surface pro, which revealed a native 'Surface Fastboot' driver. Combine that with the 15 second ADB and it's .bat ready to go command line interface, idk... it wen't so smooth and worked perfectly.
Now I can try to see if I can improve my experience with some go to methods.. I really want to enable immersive mode and hopefully increase overall volume, if possible (many devices this can be done with engineeringmode, idk yet but hopefully it does have one and hopefully I can also calibrate the gyroscope)... obviously adblock without vpn is on the menu.... can utilize the full autoruns app to stop apps from starting up at boot like in windows... and then get into some other customizations.
cqqx2 said:
LETS GOOOO!! HEROOO!! Super easy and working on the latest December 2022 update! Felt way safer as well, not so much concern over twrp as we only booted into it, and then I just used the standard magisk and it worked excellent without worrying about all types of patches and versions aside from the latest twrp for android 12 from @JengaMasterG!
Thank you! I think the renaming the magisk file from apk to zip was probably what I was doing wrong trying to follow the other methods, on top of driver errors, that were solved by uninstalling all the drivers for the duo on my surface pro, which revealed a native 'Surface Fastboot' driver. Combine that with the 15 second ADB and it's .bat ready to go command line interface, idk... it wen't so smooth and worked perfectly.
Now I can try to see if I can improve my experience with some go to methods.. I really want to enable immersive mode and hopefully increase overall volume, if possible (many devices this can be done with engineeringmode, idk yet but hopefully it does have one and hopefully I can also calibrate the gyroscope)... obviously adblock without vpn is on the menu.... can utilize the full autoruns app to stop apps from starting up at boot like in windows... and then get into some other customizations.
Click to expand...
Click to collapse
Hello! I'm rooted, but I can only read and can't write. I am Android version 122022.821.13 of Att.
So I can't delete the apk inside the system directory
linlin2az said:
Hello! I'm rooted, but I can only read and can't write. I am Android version 122022.821.13 of Att.
So I can't delete the apk inside the system directory
Click to expand...
Click to collapse
Newer Android versions, especially stock ROM, generally doesn't let you write to the system partition. Only ROMs can do that, unless you can find a way to change the partition permissions. Root alone will not allow it, no matter what you do. I used to know of a TWRP script to fix that and make the system writable, but it doesn't work on andorid 11/12/13 anyway