Related
Good Afternoon
The other day I was having an issue with my Nexus 7 so I inadvertently went into TWRP on my device and wiped everything including the OS so when it starts up I just get the Google screen with the unlocked padlock on it.
I have tried several things so far
I have downloaded Nexus root Toolkit 1.7.3 and several stock images, I choose the option to flash stock + Unroot but it doesn't seem to do anything I just get the following screen as per attached screenshot, from looking around it looks like it should run something before I get that screen but nothing happens.
I really don't know where to go from here I have tried so many different things but just don't seem to be getting anywhere, any help would be soooooooo much appreciated, I can’t even send it back as I have unlocked it and I believe that voids the warranty.
I have managed to get into the TWRP section by choosing the custom recovery in the advanced section menu but when it loads up it asks me for a password on my Nexus and the password I had it keeps on saying password failed.
Is there anything I can do, I have literally spent hours searching around and I cant seem to get anything to work, as I say I have inadvertently wiped everything!!!!!!:crying:
davechampion said:
Good Afternoon
The other day I was having an issue with my Nexus 7 so I inadvertently went into TWRP on my device and wiped everything including the OS so when it starts up I just get the Google screen with the unlocked padlock on it.
I have tried several things so far
I have downloaded Nexus root Toolkit 1.7.3 and several stock images, I choose the option to flash stock + Unroot but it doesn't seem to do anything I just get the following screen as per attached screenshot, from looking around it looks like it should run something before I get that screen but nothing happens.
I really don't know where to go from here I have tried so many different things but just don't seem to be getting anywhere, any help would be soooooooo much appreciated, I can’t even send it back as I have unlocked it and I believe that voids the warranty.
I have managed to get into the TWRP section by choosing the custom recovery in the advanced section menu but when it loads up it asks me for a password on my Nexus and the password I had it keeps on saying password failed.
Is there anything I can do, I have literally spent hours searching around and I cant seem to get anything to work, as I say I have inadvertently wiped everything!!!!!!:crying:
Click to expand...
Click to collapse
Try reflashing TWRP first, then reply if you still have the password problem. We can work from there. Remember, you have a N7 - nexus devices are practically unbrickable (if you know what I mean)
Nexus 7 2013
Thanks for that will give it a try later.
I have also come across the website below
forums.androidcentral.com/google-nexus-7-2012-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.
It gives a guide on how to reinstall the stock software, the only thing that I can see they have that I dont are a few files and I dont know where you get them from.
the files in the guide are
Bootloader-Grouper 3.34
Flash-all.sh
Flash-Base.sh
The image file I am fine with as I downloaded that from the site below.
developers.google.com/android/nexus/images
sorry I dont have enough privaleges to include link have to paste it manually
Nexus 7 2013
Also in regards to you last comment about TWRP
could you give step by step instructions on how to reinstall it, I am just paranoid that I may do something wrong again, I cant activate usb debugging so would need to do it via the bootlader and Command prompt ideally.
Nexus 7 2013 Re flash TWRP
Not to worry about steps I have managed to find some that will do the job
theunlockr.com/2013/03/25/how-to-install-twrp-recovery-on-the-asus-nexus-7/
davechampion said:
Thanks for that will give it a try later.
I have also come across the website below
forums.androidcentral.com/google-nexus-7-2012-rooting-roms-hacks/191477-guide-nexus-7-factory-image-restore.
It gives a guide on how to reinstall the stock software, the only thing that I can see they have that I dont are a few files and I dont know where you get them from.
the files in the guide are
Bootloader-Grouper 3.34
Flash-all.sh
Flash-Base.sh
The image file I am fine with as I downloaded that from the site below.
developers.google.com/android/nexus/images
sorry I dont have enough privaleges to include link have to paste it manually
Click to expand...
Click to collapse
Have you used 7z to unpack the files? Google puts all the files within an archive which is within another archive. In case you aren't able to successfully follow your guide, let me know and I will post steps. And btw, using CMD is actually quite easy once you get used to it... You just need to put in the effort! :good:
[GUIDE] How to install/reinstall/flash stock Nexus 7 Image from Google
I just saw your other thread mate! Seems like you're really worried about your device. And so I thought I'll give you step by step instructions;
1) Install, then open and navigate 7-zip to the location where you have the factory image file downloaded from google with the ".tgz" extension.
2) Unpack the .tgz file by selecting it and clicking extract (with the big blue negative sign).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Now, navigate to the extracted folder, you will see another file with the extension ".tar"
4) Repeat step 2 for the ".tar" file.
5) Now open this folder using windows. You should see the following files in your directory;
6) From here, you can either follow the instructions on the webpage you have or follow these instruction (using CMD and fastboot);
* Remember, after doing this you will not have any files/setting left on your N7.
1) Boot your N7 into bootloader.
2) Open cmd.exe and enter the following commands;
3) cd "put here without quatation marks, the directory of where the .img files are" (the last pic above)
4) fastboot devices (note: after entering this command your device should be displayed below)
5) fastboot erase boot
6) fastboot erase system
7) fastboot erase recovery
Perform steps 8 & 9 only if you have the 3G version of the N7:
8) fastboot erase radio
9) fastboot flash radio "put here without the quotation marks, the FULL name of a file that will look similar to this: radio-razor-m9615a-cefwmazm-2.0.1700.84.img"
10) fastboot update -w image-razor-jss15q.zip
11) fastboot reboot
Remember, because you have freshly flashed your N7, it will take little longer than usual to boot up.
Thank You!!!!!!!!!!
Thank you so much you are a LEGEND - I am all up and running again, just a quick question I re flashed the standard stock file which was listed as JSS15J (it wasn’t on the official factory image website) but my Nexus root toolkit seems to be playing ball after a re install, can I flash a later version over what I have without causing issues as I assume they have bug fixes.
I am unable to do an OTA update as I am in an unlocked state.
I have seen online that you can use the following code in CMD to flash newer factory images without wiping data, Is this correct?
here is the code they suggest to use
Code:
fastboot update <Filename>.zip
I suppose you could back up all data first and then re flash.
Again a massive thank you for all you help:victory:
[GUIDE] Reinstall/Update Android without loosing your Userdata (media Directory)
davechampion said:
Thank you so much you are a LEGEND - I am all up and running again, just a quick question I re flashed the standard stock file which was listed as JSS15J (it wasn’t on the official factory image website) but my Nexus root toolkit seems to be playing ball after a re install, can I flash a later version over what I have without causing issues as I assume they have bug fixes.
I am unable to do an OTA update as I am in an unlocked state.
I have seen online that you can use the following code in CMD to flash newer factory images without wiping data, Is this correct?
here is the code they suggest to use
Code:
fastboot update <Filename>.zip
I suppose you could back up all data first and then re flash.
Again a massive thank you for all you help:victory:
Click to expand...
Click to collapse
I'm glad to be of assistance. If you want to update your rom without loosing your data, I recommend you follow these steps (however, there is a catch: read the second last paragraph);
1) Boot into TWRP and wipe everything except "Internal Storage".
Reboot into bootloader and erase the following using CMD:
2) fastboot erase system
3) fastboot erase boot
4) Now unpack the <filename>.zip file. You will find that there are a multitude of <filename>.img files in there.
Flash two of the files named system.img and boot.img (this contains the Kernel) using CMD (remember CMD must be open in the folder containing these files):
2) fastboot flash system system.img
3) fastboot flash boot boot.img
And the other file (again is if you have the mobile version of the N7), is to flash the radio as given in my previous instructions (remember to erase radio first before flashing it).
When you're done, you will have updated your N7 without losing your data (i.e. the files you see when you plug your N7 to the computer). However, following this method, you will not retain any Apps or settings (remember: Backing up apps and restoring them to a different ROM is a BAD idea). I have to say also that given you cannot use OTA, I am not aware of any other method that will keep your apps and settings untouched. I may be wrong, and if I am please do let me know. :good:
Finally as a personal note, I wouldn't flash anything to a Nexus but the latest stock files provided from Google until they stop providing updates to that particular device.
..
..
[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+2]Moto X Pure[/SIZE]
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Please note: this method is only valid for Lollipop, do not use this method on Marshmallow. You can find a systemless root method for Marshmallow here, big thanks to @ivcarlos!
Download SuperSU to your phone.
Boot into TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]7. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
Donate To Me
This will be very helpful to many thanks for taking the time to put this together!
Sent from my XT1575 using Tapatalk
Thank you so much for taking the time on the guide. There will be many who will use it in the years to come! I'm just about at the verge of needing to root so I can get some insight into my battery life woes
This is much appreciated. All I did on my LG G2 was root as I did not see any roms that interested me since the bootloader is locked. I haven't used TWRP in a couple of years, so all this will help me clear the old cobwebs in my head.
Thank you so much for this! Exactly the kind of information I need. Can I trouble you to maybe add one more section to your guide: What to do when there's an OTA update from the manufacturer (Motorola)? I have concerns like:
- Would being rooted prevent OTA updates? (Assuming stock ROM).
- Would I need to "unroot" the phone to get the update? If so, how to unroot the the phone?
- Is the process to root the phone again after the the update the same, or could it possibly change?
- Would I need to wait until root is confirmed for the new version before attempting to re-root?
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
elitemeat said:
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Click to expand...
Click to collapse
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Oops
emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
Thanks for your suggestions.
1. This info has been added.
2. This section is in the same place in all of my guides, I see no problem (and have had no problems) with its location. Anyone following a guide should read it first before attempting it anyway.
3. I've added inductions to download the zip directly to the phone, less mess.
emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
This is already covered here:
http://forum.xda-developers.com/moto-x-style/help/root-to-updates-t3200588
Oaklands said:
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Click to expand...
Click to collapse
If you're on Windows, I highly recommend this one, I've been using it for ages: http://code.kliu.org/hashcheck/
I flashed SU and it didn't give me root, any suggestions?
mxpxboi said:
I flashed SU and it didn't give me root, any suggestions?
Click to expand...
Click to collapse
Have you enabled root for apps (and adb if you wish) in Developer Options?
Heisenberg said:
Have you enabled root for apps (and adb if you wish) in Developer Options?
Click to expand...
Click to collapse
I don't see root for apps in Developer Options.
mxpxboi said:
I don't see root for apps in Developer Options.
Click to expand...
Click to collapse
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Heisenberg said:
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Click to expand...
Click to collapse
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
mxpxboi said:
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
Click to expand...
Click to collapse
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Heisenberg said:
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Click to expand...
Click to collapse
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
mxpxboi said:
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
Click to expand...
Click to collapse
Cool, I've updated the link. There's a thread discussing how to remove that boot screen in the q&a or general section. Not sure about your Titanium problem, if you have root access it should work.
UPDATE: Please read the updated information at the bottom of this post, on my new recommendation to use the easier method, SuperSU systemless, to patch your original boot.img. This is in my quick start guide at the end of it, also. You still need to read my info on getting setup, also.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have started this thread as a place to post a working root solution for this tablet.
https://www.walmart.com/ip/Nextbook...-System/122137749?variantFieldId=actual_color
This is a great Android tablet for the price. It features an updated Intel Cherry Trail quad core 1.92 GHz processor, 1gb RAM, 16gb internal storage. and Android 6.0.1 Marshmallow.
UPDATE: There is a newer version of the tablet with a manufacturing sticker date of September, 2017. Despite retaining the 8A model number, it has a slower, ARM processor and Android Nougat 7.1.1. Although it is quite snappy, It shows much slower benchmarks in AnTuTu and has a much smaller battery, about half the size. Also the boxes are about 2/3 the thickness of the older, 6.0.1 tablets.
The chances of rooting it are very slim. My solution will not work for it. Fastboot mode appears to be disabled on this and one other Nougat tablet that I own. I am returning the one I tested.
UPDATE: I now have root, a custom TWRP recovery and modified boot images for the Android 6.0.1 version of this device.
I would like to thank @vampirefo for his TWRP and original boot images, for without his work, this would not be possible.
PLEASE DO NOT CONTACT HIM ABOUT THIS HE WILL NOT PROVIDE ANY SUPPORT FOR IT, THAT WILL BE PROVIDED BY ME AND OTHER GENEROUS FORUM MEMBERS.
I strongly recommend, though that you donate to him, in his signature, for all of his hard work on this, even if it is a small amount. I asked him twice about this and he never responded, so please donate to him.
His original boot.imgs are modified to remove encryption and make the kernel permissive.
I unpacked them and removed dm_verity to remove the failed verification message, on boot then repacked them.
FILES ARE UP ON ANDROID FILE HOST
https://www.androidfilehost.com/?w=files&flid=197521
Choose the version of the tablet that you own. Go to settings, about tablet and scroll to the bottom and look at the first few numbers of the build number. For example: V1.2.0.
Do not use this on the 1.0.8 version of the tablet or you will loose sound, wifi and maybe bluetooth. If you have this version of the tablet and can provide me a twrp, backed up, original boot.img, I can modify it to work with your tablet. You can temp boot twrp, to do this (see below). As of yet no one has provided one to me for the 1.0.8 tablet version.
UPDATE 10/24/2017: I now have a I now have a 1.0.8 modified boot.img up on android file host:
https://www.androidfilehost.com/?fid=962021903579487577
Here is a twrp backup of the 1.2.0 rom, with userdata deleted to start fresh. It will boot to the Android setup screen. If you have any major, unexplained problems, I recommend starting fresh with this. It works great on either tablet version: 1.1.1 and 1.2.0.
https://www.androidfilehost.com/?fid=673368273298970542
UPDATE 12/15/2017: I have uploaded a pre-rooted TWRP backup of my original V1.1.1 tablet
https://www.androidfilehost.com/?w=files&flid=235141
TO PREPARE YOUR DEVICE:
UPDATED 12/3/2017: I now have found a Version 2.1.5 of the tablet and have uploaded an unrooted, TWRP backed up version of it. It also contains the original recovery so do not check that box when flashing it in TWRP unless you intend to replace TWRP with the stock recovery
https://www.androidfilehost.com/?fid=673791459329065002
This will be long and thorough, because I see so many people who have trouble with this because they don't have their computer setup properly from the get go.
This will help you get ready to be successful in applying this.
First and foremost, unlocking your bootloader will delete all userdata on the tablet so you need a good backup of important files. If you backup to an external sd card, I strongly recommend also copying the files to an external source such as your computer. You can do that through mtp or remove the card and place it in an sd card adapter and insert it into an sd card reader. I did not do this, even though I knew better and my sd card was corrupted in the process, so I lost the original twrp backup of the virgin, untouched system partition.
Secondly, if you are on windows you need the proper drivers for adb and fastboot installed on your system. Proper drivers are the number one issue I see with windows users. For this Intel device get them here:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Here are the steps to install adb and Intel drivers, in the proper order:
The best way to to set up adb and fastboot in windows is to install it system wide. Here is an installer to do this that works well:
https://forum.xda-developers.com/showthread.php?t=2588979
Install process for 15 sec adb:
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot
3. Press Y/Yes to install ADB system-wide
4. Press N/No to skip installing Drivers
5. 15 seconds passed - finished!
6. Now install the Intel drivers listed above and here, again:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Third, enable developer options by going to settings, about tablet, and tap on the build number seven times to enable it.
Then go to developer options and make sure usb debugging is enabled. watch on the tablet screen for a popup dialog the approve usb debugging. check the box to always allow for this computer and hit ok.
Now, with the proper drivers installed, adb and fastboot properly installed, You need to test that it is functioning properly. This is done with the tablet booted into Android. If you used the adb I recommended, go to my computer, C drive and open the newly created adb folder. Left click in an open area of the folder to select it. then shift right click to open a contextual menu, then select: open a command prompt here. Once the command window is open, type:
Code:
adb devices
and hit enter:
you should see the device serial number listed. I am now doing this from linux, so it may differ,slightly:
adb devices
List of devices attached
YFGV1216059870 device
Sometimes you get starting daemon on port... and you have to type it again to see the device listed. If you don't see this, then your drivers or adb/fastboot aren't properly installed.
If you see your device, then type:
Code:
adb reboot bootloader
and hit enter. your device should now reboot to bootloader mode. once in bootloader mode, type:
Code:
fastboot devices
enter and you device should once again be listed.
the next step, is to unlock your bootloader. Warning: ALL OF YOUR USERDATA WILL BE DELETED, HENCE THE BACKUP CREATED EARLIER. YOU HAVE BEEN WARNED!
It has come to my attention that this is not clear: after unlocking the bootloader, all userdata will be deleted, like doing a factory reset.
Go into developer options and select OEM unlocking. This does not unlock your bootloader, it only enables the ability to do it from a fastboot prompt.
Now jump to the Quick Start guide for updated instructions:
Older, system mode method hidden, please use the instructions in the Quick Start Guide
Now, while still booted into bootloader mode, type:
Code:
fastboot flashing unlock
and hit enter to unlock your bootloader. All data will be deleted and the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader. Now type
Code:
fastboot reboot
t, to reboot the tablet and you should reboot to the android setup screen, You can set it up again if you want, but you will be deleting userdata later when you flash the modified boot.img, so keep this in mind.
So you may want to wait to unlock until I release twrp and the boot.img, so you can continue using the tablet.
UPDATE: The files are now live.
To summarize, the above steps are to prepare you for the next exciting adventure to come and to realize the full potential that a rooted device offers..................
To be continued.
THE FILES ARE NOW ON ANDROID FILE HOST. DOWNLOAD HERE:
https://www.androidfilehost.com/?w=files&flid=197521
Boot or flash TWRP Recovery and flash boot.img
These instructions are for Windows, for Linux you must type sudo before fastboot commands
Instructions: first make sure you read the instructions above to be sure you have the proper drivers and adb and fastboot are installed and tested before proceeding. Unlock your bootloader per above instructions. WARNING! DANGER WILL ROBINSON! THIS PROCEDURE WILL DELETE ALL USERDATA ON YOUR TABLET SO BE SURE YOU HAVE A BACKUP OF ANY IMPORTANT DATA.
First, unzip the files to a directory. I usually do it in C:\adb, and leave the SR2-SuperSU-v2.82-SYSTEMMODE.zip, zipped.
Now, left click in that folder in an empty spot, or where ever you unzipped it and select it. Now right click and choose open a command prompt here from the contextual menu. once the command window is open type
Code:
adb devices
, hit enter, to confirm your device is listed. Now type
Code:
adb reboot bootloader
and it should reboot to bootloader mode.
I recommend booting into twrp temp first so you can backup your original boot, recovery and system.
now:
Code:
fastboot boot Ares8A_recovery_twrp.img
enter and it should reboot to twrp temp. Don't choose read only after it boots. Once in twrp choose backup and hit select storage and choose micro sdcard. now swipe to backup. You can later install twrp permanently if you want to. To flash permanently:
From bootloader mode:
Code:
fastboot flash recovery Ares8A_recovery_twrp.img
UPDATE: See the the end of my updated quick start guide for updated info on a simpler method to patch your original boot.img with either systemless SuperSU or Magisk. I no longer recommend flashing my patched boot.imgs, but instructions are still provided here for historical reference and for the few who still want SuperSu in the unofficial, system mode.
I have hidden the older method here, but is still here for those who still want system mode SuperSU:
Now
Code:
fastboot flash boot Ares8A_111_boot.img
enter, for the 1.1.1 version, or
Code:
fastboot flash boot Ares8A_120_boot.img
enter, for the 1.2.0 version, to flash the appropriate boot.img
For the newer 2.1.5 version of the table:
Code:
fastboot flash boot unsigned-new.img
hit the enter key, to flash.
Next, again in bootloader mode issue:
Code:
fastboot format userdata
enter, and wait for a successful message in the command window and on the tablet. it will take a little while.
Next
Code:
fastboot format cache
enter, wait. Now
Code:
fastboot reboot
hit enter, and the tablet should reboot to the android setup screen where you can set it up. It will take some extra time to reboot, so be patient. You may see the boot animation for awhile. This will be booted unencrypted now without root. I recommend doing a backup again in twrp before rooting.
There has been some misunderstanding about the above. Your data is encrypted and will not be accessible it twrp, hence, the backup before you do anything with this tablet.
You must wipe the userdata, so a new, clean data partition can be created that is unencrypted. A factory reset is not enough. You will have problems if you don't format userdata in the above step to created a decrypted data partition.
Flashing SuperSu for root
For the v1.1.1 and v1.2.0 tablets:
Make sure you have the SR1-SuperSU-v2.82-SYSTEMMODE.zip on your ext sd card.
For the newer 2.1.5 you need a systemless version of SuperSU:
SuperSU-v2.82-201705271822.zip Get it at:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip Copy it to your external SD card.
When flashed, this systemless version will also patch your boot image for sytemless mode.
Furthermore, to install SR1-SuperSU-v2.82-SYSTEMMODE.zip, or SuperSU-v2.82-201705271822.zip, either boot twrp temp again, from bootloader mode issue:
Code:
fastboot boot Ares8A_recovery_twrp.img
, or if you already have it installed permanently and you are booted normally, issue
Code:
adb reboot recovery
enter to boot to it.
Next hit the install button in twrp and choose SR1-SuperSU-v2.82-SYSTEMMODE.zip or SuperSU-v2.82-201705271822.zip and swipe to confirm flash. after it is complete, go back to the main menu and choose reboot system. I choose not to install the twrp app before reboot.
Once rebooted, open the supersu app, making sure the following are selected in settings enable superuser, default access prompt or grant, enable su during boot, trust system user and enable pro, then go back and enable full content in logging. Next download a root check app to confirm root.
congratulations you should now be rooted! Now download a desired app that requires root and test to confirm you have no problems with root.
If you want an app that makes it easy to reboot in the various modes, I recommend Simple Reboot by Francisco Franco. It works great with this device and android version.
I was using Easy Reboot [ROOT] by Simone Luconi with my older, ares 8 with 5.1.1 and it had worked well.
Apparently it is not compatible with this device or rom. when I rebooted to recovery with it, I was not able to mount my external sd card and the card was corrupted on reboot. That is why I don't have a virgin, unrooted, copy of my system image now.
Good luck!
Here is a quick start guide for the already initiated:
https://forum.xda-developers.com/showpost.php?p=72970060&postcount=82
Here is a link to my post for some apps I personally find useful:
https://forum.xda-developers.com/showpost.php?p=72995672&postcount=112
Please report successes and problems on this thread, not to @vampirefo.
Thanks
@vampirefo has a solution, but has not released it. I'm not sure if it needs more work or testing before release? He has been quiet in this regard. It is my hope that he will reply with more relevant information about this.
I and maybe others, would be willing to give a donation, if that would help.
Thanks
Bootloader unlocking
WARNING! UNLOCKING THE BOOTLOADER WILL DELETE ALL OF YOUR DATA!
DON'T DO THE UNLOCKING UNTIL WE CAN REMOVE ENCRYPTION AND HAVE TWRP FOR BACKUP. YOU HAVE BEEN WARNED!
You can enable the ability for the bootloader to be unlocked with a setting in the developer options. Like I stated, it enables the ability to unlock it, but does not unlock it. On must use the command in adb, through a computer. make sure usb debugging is enabled in the developer options. In a command prompt issue adb devices to make sure your device is showing up. There will be a prompt on your tablet to allow this. Confirm this.
Now with the tablet off, boot into fastboot by hold the volume key down button and the power button at the same time. Also, you can type: adb reboot bootloader then hit enter to get into bootloader or fastboot mode.
Once in fastboot mode, open a command prompt in windows and type fastboot devices to confirm your device is still showing up. If my memory serves me correctly there will also be a security confirmation on the tablet, to approve.
To unlock the bootloader type: fastboot flashing unlock. All data will be deleted and (I believe,) the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader.
I HAVE NOT TESTED THIS, AS I DON'T WANT TO DELETE DATA, UNTIL WE HAVE TWRP TO BACKUP AND ROOT.
6/7/2017 UPDATE: I HAVE UPDATED THE UNLOCK COMMAND. I HAVE UNLOCKED MY BOOTLOADER. AS I THOUGHT, ALL USER DATA IS DELETED (FACTORY RESET). I USED THE FIRST:
"fastboot flashing unlock" Unlocks the device. Allows flashing any
partition except bootloader-related
partitions
"flashing unlock_critical" Enables flashing bootloader-relate partitions.
all fastboot commands are listed by just typing fastboot, while booted into bootloader mode. My tablet is still running great with my bootloader unlocked. One more tiny step toward gaining root, however, there is still a long way to go.
Please post any additional info if I have something wrong, or left out any important steps.
Thanks
Geenify: How to grant permissions required by some features on non-root device?
I am currently using Greenify on my non-rooted device and it is working very well.
By using adb, one can grant it additional permission so it performs almost as well on an unrooted device. Here is a link for this:
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
I copied and pasted each command, one at a time, in the command prompt then hit enter, to enable each one.
In Greenify settings, I also have aggressive doze enabled, Automated hibernation enabled, Wakeup Tracker enabled and Quick action Notification enabled.
How to boot into stock recovery mode
To boot to the stock recovery through adb:
adb reboot recovery
You will see "no command" on the tablet.
Hold the power button and volume up for about 4sec then release the volume up, where you should go to the stock recovery screen.
You can also get to it without a computer. With the tablet shut down, hold the volume down power button until it boots to bootloader or fastboot mode.
Use the volume up or down button to toggle through the options: normal boot, restart bootloader, recovery mode, reboot, power off and ftm mode. Choose recovery and use the volume up and power button as before.
In addition you can get to the efi bootmanager by holding the volume up, power button when the device has been shutdown first.
adb security confirmation
Unlike my Nextbook Ares 8 with 5.1.1, with this newer tablet which has 6.0.1, I have to reaffirm the security prompt on the device each time, despite checking the box: "Always allow from this computer".
Maybe this is because of the tightened security in Android Marshmallow? I'm not sure.
If there is a way around this each time, please let me know
Thanks
UPDATE: After I unlocked the bootloader and the tablet was factory reset, I no longer have to re-approve each time after checking the box: "Always allow from this computer"
Would love to see some break throughs with this device aswell. Cheers to any one working in it.
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Giftlift said:
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Click to expand...
Click to collapse
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
martyfender said:
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
Click to expand...
Click to collapse
:good::good:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
I found this kernel building guide for arm and mediatek devices. would this be similar for Intel using the right repositories?
https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057
Thanks
Click to expand...
Click to collapse
martyfender said:
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
Thanks
Click to expand...
Click to collapse
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
vampirefo said:
martyfender said:
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
martyfender said:
vampirefo said:
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
No ideal, try it and see.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
cjhudson101 said:
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
Click to expand...
Click to collapse
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
vampirefo said:
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
cjhudson101 said:
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
Click to expand...
Click to collapse
You didn't misread, I rooted my son's, he doesn't live near me, he is in college. He is using my laptop that I used, so all my source files are with him.
I need tablet to start over, I already know what to do but without tablet, I can't do it.
Sent from my Life Max using Tapatalk
Check your zip in the link, lets get vamp an 8a!
I just got one of these for $35, but now the closest walmart with it in stock is an hour away. Ill totaly send you one if I drive that way for any reason. Check your zip on brickseek ..... anyone?
slickdeals.net/f/10189248-nextbook-ares-8a-16gb-tablet-android-6-ymmv-35-bm?src=SiteSearchV2_SearchBarV2Algo1
it came with 6.0.1 on it
Hello mates! What a heck of a problem rooting this fancy brick, right? Not anymore ! The guides available in here are very confusing and lack of simple information. I'm just trying to help.
Special thanks goes to sumec100 who made me into the first steps of this process.
Rooting the Brick
*What will you need in a first moment:
- SDK MANAGER AND PLATAFORM TOOLS ONLY https://developer.android.com/studio/index.html#downloads *end of the page, 132mb archive* (Plataform-tools is attached in case you can't find it)
- SuperSU: https://mega.nz/#!t2wGDbhL!H07JxlbmLH2tFQD7Frx2BKlJp0AyDthXkbEj6sw4z08 (this one worked out) (Leave it in your SD Card before start the process)
- TWRP ported by Jemmini from 4pda and translated to English by TuksOID. : https://drive.google.com/open?id=1Uwkl_2vqHfXkbLGmF-gKbs63UxVKmw_T
- ADB Driver Installer: http://adbdriver.com/downloads/
- ARMOR 2 Latest Drivers: https://drive.google.com/folderview?id=0B8NC4kBpjQhYdDNhdzdUdTRsRFE&usp=sharing
0) Go into your Ulefone Armor 2.
Settings >About phone > Tap ''build number'' 8 times until you see ''now you are a developer''.
Developer options> OEM unlocking (yes) >USB Debugging (Yes)
After all drivers are installed in Driver_Auto_Installer you downloaded from ulefone.com keep ADB Driver Installer open and plug in your phone on your PC. It will auto detects your MediaTek device. Just click ''Install'' wait until it finishes and close it. Now you are properly connected to your phone.
1) Open ''cmd.exe'' as an administrator.
Type: cd (path you unziped plataform-tools inside SDK tools folder) kind of looking like this: ''X:YOUR PATH\tools\platform-tools''
Put the recovery image you downloaded (I suggest you to rename it as ''recovery'') in ''plataform-tools''
2) Back to the cmd in the way you leaved it do it:
adb reboot bootloader Press Enter. The phone will reboot in fastboot mode. (I suppose you did not shut it down, please don't)
fastboot flashing unlock Press Enter. The phone will prompt you. Read the content of the text if you want. To keep going press ''Volume Up'' DO NOT INTERRUPT THIS PROCESS
fastboot flash recovery recovery.img Press Enter. Now the TWRP will be flashed. Note that I used ''recovery'' as file name.
After the successful flash:
fastboot boot recovery.img Press Enter. TWRP will now start.
3) Unplug your phone.
Your TWRP will show a ''Enter Code'' prompt since your device stills encrypted. Press ''Cancel''
Drag the bar to allow modifications;
Press ''Wipe'' in the main menu;
Drag the bar to do a Factory Reset (THIS IS NOT OPTIONAL);
Press ''Install'';
Select the SuperSU file you downloaded in the above. (I hope you copied it in your SDCard. If you did not, You can plug your phone in your PC, mount your Storage via TWRP, copy the zip file and keep going);
Drag the bar to flash SuperSU zip file (DO NOT select any parameters)
Press ''Wipe Dalvik/Cache''
Press ''Reboot System''
Wait for it.
If you had a successful boot, now your device is rooted. Cheers !
Did your device don't boot in 15 minutes? I'm quite sure you messed up but keep calm, don't panic!
Unbricking the brick
*What will you need:
SPFlashtool: https://spflashtools.com/windows/sp-flash-tool-v5-1728
Latest Ulefone Armor 2 ROM: https://drive.google.com/open?id=0B8NC4kBpjQhYdEJTdTdpazVGQjg
The software is quite of auto-explained. Please, Do not use the Ulefone's SPFlashtool, use the one I provided. (I DID NOT CREATE IT)
Shut off your phone
In SPFlashtool set the ''scatter-loading file'' inside the ROM zip, Click ''choose'' and locate it.
Keep it ''Download Only''
Click ''Download'', SPFlashtool will be waiting for your device. (REMEMBER YOU NEED THE DRIVERS I QUOTED ABOVE FOR ALL PROCESSES)
Plug your phone.
Wait until SPFlashtool say it is finished.
[*]After that your phone is brand new. If you want to try again just go up and follow all steps again (Correcting mistakes, of course)
Known Issues
-Latest Magisk is not working with our Stock ROM. It bootloops.
-Latest Nougat Xposed Module Bootloops our phone too.
Any doubts or corrections please, say it !
TheReal V said:
*What will you need in a first moment:
- SDK MANAGER AND PLATAFORM TOOLS ONLY
Click to expand...
Click to collapse
The download doesn't contain the platform tools anymore. They have been moved into an extra download:
developer.android.com/studio/releases/platform-tools
Funny thing: I can't quote links because of new account oO
Have you tried the new ROM that came out last month on needrom?
TheReal V;76285584[FONT="Arial Black" said:
*What will you need in a first moment:[/FONT]
- SDK MANAGER AND PLATAFORM TOOLS ONLY https://developer.android.com/studio/index.html#downloads *end of the page, 132mb archive* (Plataform-tools is attached in case you can't find it)
Click to expand...
Click to collapse
Hi,
Thank you for your work
but I could not find the platform tools 132mb archive in the link you provided.
The only download link close to 132mb is the 149mb I found.
Is this the file you were referring to?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you
enzovic said:
Have you tried the new ROM that came out last month on needrom?
Click to expand...
Click to collapse
No, I did not. I'm not messing with this system anymore (not enough time ) since I made my last format and root I decided to not try anything else since he is my daily driver and I need it workin 24/7
kaibird said:
Hi,
Thank you for your work
but I could not find the platform tools 132mb archive in the link you provided.
The only download link close to 132mb is the 149mb I found.
Is this the file you were referring to?
View attachment 4550585
Thank you
Click to expand...
Click to collapse
That's right ! Inside this zip and inside sdk tools folder it should be a plataform-tools folder. If not, tell me !
Daugl said:
The download doesn't contain the platform tools anymore. They have been moved into an extra download:
developer.android.com/studio/releases/platform-tools
Funny thing: I can't quote links because of new account oO
Click to expand...
Click to collapse
You can go ahead and download it. I guess my attach was erased
kaibird said:
Hi,
Thank you for your work
but I could not find the platform tools 132mb archive in the link you provided.
The only download link close to 132mb is the 149mb I found.
Is this the file you were referring to?
View attachment 4550585
Thank you
Click to expand...
Click to collapse
Quick Remember ! Plataform-tools is a tiny folder (15~30mb) The huge one is the sdk tools !!
Hey, everybody ! Plataform-tools is attached again ! You guys can download it again !
hey guys... sorry to comment in the old thread but I followed the guide and... my phone is booting always in the recovery I really don't know what I have to do now lol
Hi,
I have flashed successful the latest Ulefone Armor 2 Firmware from their site h**p://ulefone.com/download/armor2.html
Then I did all the necessary steps to root the phone. But when I first time start the SuperSU app, get a popup message "SuperSU needs to update"
and hit "OK". After a while get this failure:
"SU Update unsuccessful"
Regards...
After install SuperSu and press "Reboot System", my phone keeps booting into TWRP.
Can someone help me?
rafaelsenna said:
After install SuperSu and press "Reboot System", my phone keeps booting into TWRP.
Can someone help me?
Click to expand...
Click to collapse
Fixed. I restored my original ROM using this this tutorial: https://forum.xda-developers.com/showpost.php?p=74294320&postcount=31
Now, Super SU is installed but is asking for update.
Hi all,
I managed to root my Armor 2 but after that I cannot install Netflix from Play Store. It says that device is not compatible.
Does anyone know if the app is restricted to rooted devices?
Thanks in advance
flashed the wrong recovery now stuck ( I used "one click" program )
phone constantly restarts and gives the following error
"
orange
state your device has been unlocked and can't be trusted your device
will boot in 5 seconds
"
the following video is someone else who has the same problem as me
( I didn't have a camera, so I used another video)
I can't do "fastboot and recovery" in any way. Always gives me this error
https://www.youtube.com/watch?v=LJRqMPtKKX4
The best way to root armor 2
1) copy boot-verified.img from firmware folder to internal
2) install magisk
3) download any update in magisk
4) press install and select "select and patch a file"
5)select boot-verified. Img
6)after operation comlate copy magisk-patch. Img file in download folder to pc
7)flash it with sp flash tool
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any thoughts please?
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
akhilarora666 said:
type "Oneplus 7 Downgrade Firmware".
Click to expand...
Click to collapse
Thank you for your encouraging message.
That article you mentioned says this:
copy the Rollback package to the phone’s internal storage.
Go to device Settings > System > System Updates > Tap on top right icon > Local upgrade > Select the installation zip package > upgrade > System upgrade completed to 100%.
Click to expand...
Click to collapse
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
akhilarora666 said:
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
Click to expand...
Click to collapse
That's not possible when you have no os anymore...
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
Just stay on xda-developers, no need for suspicious off site downloads.
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Or the unbrick tools: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
In my case, I was stuck too. So i did "fastboot boot recovery.img" tried both android Q and android pie revocery. (version 70 and 65) (editied versions by mauronofrio) one of them worked. I got into the recovery. then installed the android Q stock firmware zip file. Thing is, i dont know why, but once you are on android Q, your phone stops supporting android PIE. Since you were on android Q once, you have to go back there. only then follow the external website i linked.
Like the other guy said, you can stick to XDA and try the unbrick tools. but for me they didnt work. So i followed that website. then everything was fine. Ofcourse its fishy. but once you are back on pie, you can reinstall any pie rom you want.
strongst said:
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Click to expand...
Click to collapse
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
who ah way said:
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
Click to expand...
Click to collapse
Your screenshot is the fastboot screen. Stated with: fastboot
If your device is not recognized, maybe you should check your adb drivers etc.
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
Same situation happened to me but due to wipe in twrp vendor image
who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
You used a nandroid backup which is what resulted in the brick. Nandroid backups do not backup firmware
Anyway try
fastboot --set-active=a
Then reboot and see if it boots
Or try
fastboot --set-active=b
If that doesn't work download twrp and flash it to the boot partition
fastboot flash boot whatever
Reboot and you should have twrp
Which twrp to flash? The one for Q firmware. It's obvious
---------- Post added at 22:31 ---------- Previous post was at 22:25 ----------
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
I do not know how you formatted cache on a device that doesn't have a cache partition