Related
Introducing.... Superboot!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
APPLY THIS AT YOUR OWN RISK!
Superboot r4 - DOWNLOAD - MD5: f53825a2df09277f899b6738b3a059d5
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-mac.sh' followed by './superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x superboot-linux.sh' followed by './superboot-linux.sh'
Note: If you are using a retail device, you may need to unlock the bootloader first, using './fastboot-windows oem unlock' (or the appropriate version for your machine, included in this zip). Note that the OEM unlock sequence wipes your device, so consider doing an 'adb backup' beforehand if required!
Enjoy!
P
Awesome!!!!! Can't wait for my nexus 7 :thumbup::beer:
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
glad to see u here Paul. any plans on a cwm or are you using the one available in the other root thread? I see u porting superboot everywhere, awesome!
I'll probably just use the CWM already made, unless there's a good reason to make a new one?
P
paulobrien said:
I'll probably just use the CWM already made, unless there's a good reason to make a new one?
P
Click to expand...
Click to collapse
I just wasn't sure who even made the other n I prefer using stuff by well known devs that's all. when I get mine I'll try porting our cannibal touch recovery from the kfire with sblood86 n drew.
Sent from my Amazon Kindle Fire using xda premium
This is outstanding news. Im ready for my nexus 7 to hit my door. Believe it or not this will be my first nexus device and I cant wait. Thanks paul o brian :thumbup::beer:
Sent From A Rotary Phone
Download Counter
Does SuperBoot change the download counter from 0 to "Custom Downloads 1"?
Glenn
weltwon said:
Does SuperBoot change the download counter from 0 to "Custom Downloads 1"?
Glenn
Click to expand...
Click to collapse
There is no custom download counter on the N7 is there?
P
So does this unlock the bootloader?
Bilge656 said:
So does this unlock the bootloader?
Click to expand...
Click to collapse
paulobrien said:
Note: You need to unlock the bootloader in order to use this Superboot. Note that the OEM unlock sequence wipes your device.
Click to expand...
Click to collapse
Reading carefully before flashing helps reduce frustration. (old chinese proverb)
paulobrien said:
I'll probably just use the CWM already made, unless there's a good reason to make a new one?
P
Click to expand...
Click to collapse
Twrp is a good enough reason
Makes flashing Roms on my prime effortless.
I need a hand. Can't seem to get the USB drivers to work. I keep getting device not found
Sent from my Nexus 7 using Tapatalk 2
tried this 3 times... no joy.. no root. the ota jb update was applied before i did this..............would that screw it up??
patterone said:
tried this 3 times... no joy.. no root. the ota jb update was applied before i did this..............would that screw it up??
Click to expand...
Click to collapse
No...
P
Sent from my GT-I9300 using Tapatalk 2
patterone said:
tried this 3 times... no joy.. no root. the ota jb update was applied before i did this..............would that screw it up??
Click to expand...
Click to collapse
See if you have any luck with wugfresh that's how I got rooted
Sent from my Nexus 7 using Tapatalk 2
I was having trouble with the other two methods once inside CWM (something to do with the Windows driver), but this worked flawlessly. I can live without CWM for now.
Mogster said:
I was having trouble with the other two methods once inside CWM (something to do with the Windows driver), but this worked flawlessly. I can live without CWM for now.
Click to expand...
Click to collapse
Awesome, enjoy!
P
I've got a question I hope won't bother you to answer, Paul.
My goal with my Nexus 7 when it arrives is to be able to load up Titanium Backup Pro and restore some of my Games (App+Data). I' d like to know if I understand the process right to get to that point and still be able to receive OTA updates.
The first thing I should do when I turn on my device is boot into the bootloader and oem fastboot unlock.
Next, I should follow your instructions to chmod and install the superboot package.
When my device reboots after this, should I be able to update to 4.1.1 and retain root so I can install TBpro?
Brigaid said:
I've got a question I hope won't bother you to answer, Paul.
My goal with my Nexus 7 when it arrives is to be able to load up Titanium Backup Pro and restore some of my Games (App+Data). I' d like to know if I understand the process right to get to that point and still be able to receive OTA updates.
The first thing I should do when I turn on my device is boot into the bootloader and oem fastboot unlock.
Next, I should follow your instructions to chmod and install the superboot package.
When my device reboots after this, should I be able to update to 4.1.1 and retain root so I can install TBpro?
Click to expand...
Click to collapse
Upgrade first then unlock and root 4.1.1
Worked for me
MB860, CM7.2.0, Faux 026b1 1Ghz
Thanks, I'm happy to hear it works.
NOTE: If you upgrade to this version, then decide you WANT ROOT and DOWNGRADE to 5.0.2, DO NOT leave phone plugged in after it reboots during the flash around 80% or so. Doing this will result in a HARD BRICK! YOU HAVE BEEN WARNED!
Received official Sprint 5.1.1 OTA for LS996 Flex 2! Uploading to Google Drive right now, will post link after completion!
:highfive:
Google Drive Link: As Promised!
You must be running the original stock build of Android 5.0.1 (TOT Flash Files)
To install this file simply copy to the root directory of your SD card, then reboot into the bootloader.
If you have adb installed, run "adb reboot bootloader"
If you do not, power the device off, and hold Volume Down and Power buttons together to turn the device on. After about 5 seconds, you will see the recovery mode screen.
Now, highlight "apply update from sdcard"
Use your power button to select that option.
Select the "update.zip" from the list
Enjoy!
lyphe said:
Received official Sprint 5.1.1 OTA for LS996 Flex 2! Uploading to Google Drive right now, will post link after completion!
:highfive:
Google Drive Link: As Promised!
Click to expand...
Click to collapse
Can you upload kdz of of 5.1 i have to flash it on us995
thanks for the zip! i'm now updated to ZV6!!!! hopefully i notice some improvements!
muzammil457 said:
Can you upload kdz of of 5.1 i have to flash it on us995
Click to expand...
Click to collapse
Theres no KDZ for that model. Only TOT.
Updated. So far so good!
Thanks @lyphe very usefull topic. Anyone knows about root on 5.1.1
I just use LG flash tool? orrr is there another way to just install a .tot?
BillyxAllen said:
I just use LG flash tool? orrr is there another way to just install a .tot?
Click to expand...
Click to collapse
There are 2 methods for flashing LG Phones, tot or kdz and you must use the program.
I opened up my guide earlier: http://forum.xda-developers.com/g-flex2/general/guide-lg-g-flex-2-stock-firmware-to-t3037593
LG flashtool wants me to sign in
Also, since the file provided isn't TOT how do I install it. I got around signing in to lgflash
BillyxAllen said:
Also, since the file provided isn't TOT how do I install it. I got around signing in to lgflash
Click to expand...
Click to collapse
that's exactly what I want to know too..
Hey @BillyxAllen, if you get the answer, do let me know too.
lyphe said:
Received official Sprint 5.1.1 OTA for LS996 Flex 2! Uploading to Google Drive right now, will post link after completion!
:highfive:
Google Drive Link: As Promised!
Click to expand...
Click to collapse
how to apply this zip update?
---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------
hyelton said:
Theres no KDZ for that model. Only TOT.
Click to expand...
Click to collapse
i could not find tot too. only tot i found is for ls996. but i cant flash it on us995 beacause of DLL file. isome one told that a special dll fiile will work..
Reboot recovery and apply update by side load
INSTALL INSTRUCTIONS!!!
1. Install LG Flex 2 Drivers.
2. Download ADB version 1.0.32 or later.
3. Download update.zip and put it in the ADB folder with the ADB files.
4. Make sure USB Debugging is enabled on your phone.
5. Boot into recovery (power+vol down) and go to update from sideload (second option)
6. Open Command Prompt as Admin.
7. Cd to the ADB folder
-Example: "cd C:\Users\'Me\Desktop\ADB
8. Enter command "adb sideload update.zip"
9. Wait for it to finish and reboot!
This update is way faster than 5.0.1. It fixes all of the problems I had before! This thing flies!
justinswidebody said:
Reboot recovery and apply update by side load
Click to expand...
Click to collapse
How do you get adb to recognize the phone in recovery??
Sent from my GT-N8013 using XDA Free mobile app
shuka325 said:
How do you get adb to recognize the phone in recovery??
Sent from my GT-N8013 using XDA Free mobile app
Click to expand...
Click to collapse
Install the drivers from here - http://androiddrivers.net/lg-android-drivers/download-lg-g-flex-2-drivers-for-windows/
Also make sure USB Debugging is enabled.
happyjack96 said:
Install the drivers from here - http://androiddrivers.net/lg-android-drivers/download-lg-g-flex-2-drivers-for-windows/
Also make sure USB Debugging is enabled.
Click to expand...
Click to collapse
Will try those drivers. Thought I had already downloaded those but will try it again. ADB works for all else. Was able to reboot into recovery through adb. Thank you.
Sent from my GT-N8013 using XDA Free mobile app
Does root survive updating via this method?
uh60james said:
Does root survive updating via this method?
Click to expand...
Click to collapse
Will not allow the update if you are rooted. Have to go back to stock to flash it.
Sent from my LGLS996 using XDA Free mobile app
shuka325 said:
Will try those drivers. Thought I had already downloaded those but will try it again. ADB works for all else. Was able to reboot into recovery through adb. Thank you.
Sent from my GT-N8013 using XDA Free mobile app
Click to expand...
Click to collapse
Well, never was able to get adb to see recovery. But i was able to flash the update.zip through recovery. Took a while and thought it was stuck but afterwards i have 5.1.1.
Sent from my LGLS996 using XDA Free mobile app
Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
---------- Post added at 02:00 PM ---------- Previous post was at 01:41 PM ----------
Is this systemless root?
Darkscan said:
Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
---------- Post added at 02:00 PM ---------- Previous post was at 01:41 PM ----------
Is this systemless root?
Click to expand...
Click to collapse
Adb = Android debug bridge and is used when the phone is booted into the OS and connected to a PC
Fastboot = when the phone is booted into the bootloader and is connected to a PC
Yes it is systemless root
You can backup stock firmware with twrp RC1
Sent from my Pixel using Tapatalk
joetheshmo said:
Adb = Android debug bridge and is used when the phone is booted into the OS and connected to a PC
Fastboot = when the phone is booted into the bootloader and is connected to a PC
Yes it is systemless root
You can backup stock firmware with twrp RC1
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Why is the current version for TWRP and the previous not? Is the bootloader download mode?
Darkscan said:
Why is the current version for TWRP and the previous not? Is the bootloader download mode?
Click to expand...
Click to collapse
Current version of root for twrp and the previous not? If that's what you're asking SuperSU was developed before a working twrp was released so we had to use the boot-to-root.img
I guess bootloader mode could be considered download mode but I've never heard it called that.
Sent from my Pixel using Tapatalk
joetheshmo said:
Current version of root for twrp and the previous not? If that's what you're asking SuperSU was developed before a working twrp was released so we had to use the boot-to-root.img
I guess bootloader mode could be considered download mode but I've never heard it called that.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I come from using only Samsung devices, I'm not sure what carries over and what doesn't. The extent of my experience is loading a ROM with download mode and flashing it with recovery. Speaking of which, why does the stock recovery just say no command when I try to launch it from fastboot?
Darkscan said:
I come from using only Samsung devices, I'm not sure what carries over and what doesn't. The extent of my experience is loading a ROM with download mode and flashing it with recovery. Speaking of which, why does the stock recovery just say no command when I try to launch it from fastboot?
Click to expand...
Click to collapse
Because you have to hit power button and volume up at the same time to get the commands to show up now
Sent from my Pixel using Tapatalk
joetheshmo said:
Because you have to hit power button and volume up at the same time to get the commands to show up now
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Well that's silly.
Darkscan said:
Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
Click to expand...
Click to collapse
Why would you need to back-up the stock firmware? It is available here: https://developers.google.com/android/images
efrant said:
Why would you need to back-up the stock firmware? It is available here: https://developers.google.com/android/images
Click to expand...
Click to collapse
I suppose "where can we download the stock image" was the real question. Thanks.
Should I flash to stock first? I don't see why it would matter. All I've done is update Android and install a couple apps.
Darkscan said:
I suppose "where can we download the stock image" was the real question. Thanks.
Should I flash to stock first? I don't see why it would matter. All I've done is update Android and install a couple apps.
Click to expand...
Click to collapse
No need.
Would this be an acceptable way for me to downgrade my version? I am currently 100% stock and would like to downgrade so I can root, install TWRP, and start flashing custom ROMs.
This thread is like the twilight zone.
chadhoard said:
Would this be an acceptable way for me to downgrade my version? I am currently 100% stock and would like to downgrade so I can root, install TWRP, and start flashing custom ROMs.
Click to expand...
Click to collapse
Verizon phone? If you are on 7.1.1 you are done.
Google phone? You don't need to downgrade to do any of that.
Hi, i share my personnal experience, struggled to figure out what was wrong after flashing OB2 but it seems it's all good now.
Did this from OpenBeta2, no specific firmware required i guess as long as the tool we will use is there to erase everything.
I used the official 3.2.3.0 twrp to avoid strange encryption thing (link here)
a user reported this bug because of a custom recovery
1. Download MSMDownloadTool. The 4 files in the MEGA links seems to be requrired so download as zip the whole thing.
2. Follow the guide i quoted then check my instructions
credit to @Fivegates
Guide how to revive your op6:
First of all, you need to access to fastboot mode, if you can't , contact Oneplus support, then have a windows computer and download these file and drivers qualcomm ( https://androidfilehost.com/?fid=24052804347798730) and extract in one folder.
After you have all the file ready, plug in the phone to the computer, go in device manager and under port (COM) disinstall qualcomm one (oneplus 6) and then unplug.
Now you have to go in Windows test mode to not let him install default drivers, so:
windows key (on keyboard) + X, windows powershell (or normal prompt) administrator and write and enter: bcdedit /set testsigning on ( you will repeat the same process with "off" to stop the test mode after you will finish to do all the things).
Reboot the system and you could see in bottom right corner the test mode, now you are ready to install properly drivers.
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process (https://www.youtube.com/watch?v=PpLvmID1wdI)
Right click con US8_BULK in device manager and update drivers by system files (go to the folder's drivers you had extracted before).
Now you should see qualcomm drivers under port (COM).
You are ready to let the tool to do all the stuff, so let plugged the phone, always powered off, right click on msmdownloadtool and execute as administrator.
You should see your device and click start to begin the process; if it gives you some error (like sahara or something else), unplug, power on, power off and the plug it again, now it should be fine.
And that's it, the tool will do all the work and, at the end, you will have like a brand new phone ready to a new setup.
EDIT: if you are stucked in bootloader, you have only to power off and continue with the part: ... hold for 5 seconds vol up... (it happened in page 4)
Click to expand...
Click to collapse
lil shortcut guide (might be wrong lol check @Fivegates post if scared)
# go to Device manager, delete your op6 drivers
# enable the test mode with
Code:
bcdedit /set testsigning on
(don't forget to turn off when you're done)
# reboot your pc
# open msmdownload
# power off phone, press vol up and connect phone to pc
# upgrade mode ticked, click once on the only line you see and hit START
# wait
# unplug when it's done
3. Once process is over the phone is back stock 5.1.5 with locked bootloader
4. update to OB2 via local update in settings
Comprehensive guide to update manually
5. unlock your bootloader
6. you should be able to boot on OB2 without that red annoying popup, flash a twrp and magisk whatever
Useful Guide to Unlock Bootloader, Flash TWRP, Root and more
VISUAL GUIDE
Tell me if it works for you too, personnally i've been able to unlock bootloader, flash the latest twrp and magisk
I am living along with corrupted device no problem at all.
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Toni Moon said:
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Click to expand...
Click to collapse
Same here for me. I tried the method mentioned in the op too. It gives the same error once I update to pie. The error is still there for hydrogen and oxygen. Dp3 doesn't have that issue
Toni Moon said:
I try all.. and seems that's it's the only method that's work, with fastboot rom it's fixed if you back to Oxygen rom but when you install the beta again the error persist.
Click to expand...
Click to collapse
Yeah that "issue" is terrific :crying:
Did you try this way ?
80s Baby said:
Same here for me. I tried the method mentioned in the op too. It gives the same error once I update to pie. The error is still there for hydrogen and oxygen. Dp3 doesn't have that issue
Click to expand...
Click to collapse
you tried this and it fails ?
Neil_Armstrong_ said:
you tried this and it fails ?
Click to expand...
Click to collapse
Yes it does fail for me. It clears that warning when it's downgraded but once updated to any version of pie. The warning comes back again
80s Baby said:
Yes it does fail for me. It clears that warning when it's downgraded but once updated to any version of pie. The warning comes back again
Click to expand...
Click to collapse
Huh
Did you unlock bootloader before or after updating to Pie ? I honestly don't know what/where the wolf is
Neil_Armstrong_ said:
Huh
Did you unlock bootloader before or after updating to Pie ? I honestly don't know what/where the wolf is
Click to expand...
Click to collapse
Before..I guess right around the first update 5.1.6 or 7. That's when I bought the phone
80s Baby said:
Before..I guess right around the first update 5.1.6 or 7. That's when I bought the phone
Click to expand...
Click to collapse
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Neil_Armstrong_ said:
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Click to expand...
Click to collapse
Yes, this is the way
Neil_Armstrong_ said:
After using MSMDownload the bootloader should be locked again, you just have to stay lock and update from settings
Click to expand...
Click to collapse
Can I root my device after updating? Coz that's when the issue normally comes in as well
80s Baby said:
Can I root my device after updating? Coz that's when the issue normally comes in as well
Click to expand...
Click to collapse
Hi
I did exactly the same process as mentioned above and I have no problem with root
I first unlocked bootloader then fastbooted twrp + installer.zip
Then I flashed magisk and tons of stuff no red warning
Keep me updated
Neil_Armstrong_ said:
Hi
I did exactly the same process as mentioned above and I have no problem with root
I first unlocked bootloader then fastbooted twrp + installer.zip
Then I flashed magisk and tons of stuff no red warning
Keep me updated
Click to expand...
Click to collapse
Tried this last night it is still the same. Everything went well until I flashed magisk. That's when I got the warning this time.
Did you flash blu spark twrp?
This method works to me..
80s Baby said:
Tried this last night it is still the same. Everything went well until I flashed magisk. That's when I got the warning this time.
Click to expand...
Click to collapse
Toni Moon said:
Did you flash blu spark twrp?
This method works to me..
Click to expand...
Click to collapse
Yes, I haven't tried the official one yet..should I try that out instead?
80s Baby said:
Yes, I haven't tried the official one yet..should I try that out instead?
Click to expand...
Click to collapse
Official TWRP
I had the same error when I dirty flashed from 5.1.11 to the official 9.0. The method from OP fixed it. I'm back to 9.0 with TWRP, Magisk, and custom kernel without the annoying message.
Thanks a lot!
sasho36 said:
I had the same error when I dirty flashed from 5.1.11 to the official 9.0. The method from OP fixed it. I'm back to 9.0 with TWRP, Magisk, and custom kernel without the annoying message.
Thanks a lot!
Click to expand...
Click to collapse
can I still use the bluspark twrp or no?
R0ttenB4ndit said:
can I still use the bluspark twrp or no?
Click to expand...
Click to collapse
just read bro used official twrp 3.2.3
So I just picked up a Pixel 3 while on sale to replace my failing Nexus 5 that was literally falling apart. I managed to unlock the bootloader easily. Used a USB C to USB A cable from my Nintendo Switch used for charging the controller for unlocking the bootloader. Next step was to install TWRP and eventually Magisk.
So I followed the instructions to install TWRP from the TWRP website and grabbed the latest image and zip. Initially when I ran the command to boot the image, I would get a "too many links" error. Everything I found in relations to this said I needed a better cable. Odd but okay. I had planned to pickup a new one anyways for transferring music and pictures and such. Got it today, reboot into fastboot and now the command completes successfully with no error. Unfortunately instead of booting into TWRP temporarily as per the instructions, to then install the ZIP for TWRP, the phone boots straight into Android. I have tried the following commands. The first being from the official TWRP guide, and the second being from another guide I had found.
fastboot.exe boot twrp-3.2.3-0-blueline.img
fastboot.exe boot recovery twrp-3.2.3-0-blueline.img
Obviously both result in the same issue. Namely the phone simply reboots right into Android. I am using the latest Platform SDK tools from google, and am using the most up to date drivers for the phone. I am at a loss of what I might be missing. I do see info about boot slots A and B (My phone is B), but nothing in relation to that as far as installing TWRP is concerned. Any help would be appreciated!
What Android version is your Pixel 3 device running?
BobPony said:
What Android version is your Pixel 3 device running?
Click to expand...
Click to collapse
Android 10. Latest OTA.
Ultratails42 said:
Android 10. Latest OTA.
Click to expand...
Click to collapse
Twrp doesn't work on 10. Maybe it will some day but not now.
jd1639 said:
Twrp doesn't work on 10. Maybe it will some day but not now.
Click to expand...
Click to collapse
Yeah. I see that now. Looked it up after they asked the android version. Here's hoping they update it soon to work with 10.
Ultratails42 said:
Yeah. I see that now. Looked it up after they asked the android version. Here's hoping they update it soon to work with 10.
Click to expand...
Click to collapse
If you want, you can downgrade to Android 9 using the factory images with the flash-all script. But, it requires to have the bootloader unlocked.