It looks like it's not a very successful guide. Better not use it I guess.
How to get from the Android to Ubuntu on the Meizu 5 Pro.
Here is a little guide of how I installed/returned to Ubuntu after installing Android on my Meizu 5 Pro Ubuntu edition.
My desktop pc is running Ubuntu, so these commands are for the Ubuntu terminal. But should be very similar on Windows, probably.
First, install ADB and Fastboot on your pc :
Code:
sudo apt-get update
sudo apt-get install fastboot adb
Connect the Meizu phone to your pc with a usb cable. Then power up the Meizu 5 Pro with both the power button and volume down.
Type:
Code:
sudo fastboot devices
If all went well you’ll see a screen with an number/letter combination with the text fastboot behind it, and the Meizu logo.
Now download TWRP_3.0_m86.img from http://xep.8800.org/pro5/.
With the next command you are going to flash TWRP custom recovery to your phone.
Code:
sudo fastboot flash recovery TWRP_3.0_m86.img
This should be done pretty fast. Power off your phone, and restart it with volume up and power button both pressed.
If all went well you’ll see a screen like this:
Your recovery is set. . You’ll see the Team Win Recovery Project if correct.
Do a full wipe:
- go to settings and select "use rm -f instead to formatting"
- Got to wipe -> advanced wipe and select all except the last/bottom one, and swipe to wipe.
Now check to see if ADB devices works correctly
Code:
sudo adb devices
List of devices attached
0123456789ABCDEF device
If not restart adb by typing adb kill-server, and the restart adb with the sudo adb devices command.
Download the Canonical recovery-turbo, recovery.img, form:
https://wiki.ubuntu.com/Touch/Devices
And install ubuntu device flash program :
Code:
sudo apt-get update
sudo apt-get install ubuntu-device-flash
Now here comes the harder part. Open 2 terminals, you’ll see later why.
Now go back to the recovery on your phone. Go to Mount, and mount the system partion. And be sure it looks like this:
With three checkmarks.
Now type, BUT DO NOT PRESS ENTER, in the first terminal window:
Code:
sudo fastboot flash recovery recovery.img
And leave it there for later.
Then in the second terminal window, you are gonna use the ubuntu device flash program with this command:
Code:
sudo ubuntu-device-flash touch --channel=ubuntu-touch/stable/meizu.en --device turbo
If everything is alright, this command will first download files, than start pushing them to your phone, and will end with this message:
Code:
Rebooting into recovery to flash
You will have to be quite quick because you’ll need to intercept this. When you see this message you will need to press volume down + power button at once, so you can go to the fastboot screen.
Now you will have to use the second terminal to use this command:
Code:
sudo fastboot flash recovery recovery.img
When done you need to manually turn the phone into recovery mode by pressing volume up + power button. It is really important that you reach the recovery mode. If you reach the normal boot mode you will have to run the ubuntu device command from the beginning. You will not see the recovery screen if you reach the recovery mode. The screen turns black and will be like this for a little bit of time.
The screen wil go black, that’s normal. Wait a 5-10 minutes, and if everything is alright you’ll see a FlymeOS recovery. That is normal and good. Now power the phone off and on again, and if everything happened like it did on my phone, Ubuntu starts.
Now you can enjoy Ubuntu on your phone. You should have a white Meizu Powered by Ubuntu screen and an orange Ubuntu recovery logo, but sometimes it doesn't come in the first install. From my experience you will need to run the command one more time from a different channel, and this will be fixed aswell.
You can also use the Release candidate proposed channel, the software is newer.
Code:
sudo ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/meizu.en
I will also try to make a TWRP backup image, maybe that will be easier for people with Windows PC's. But I haven't tested that yet.
Thanks to all the people on XDA and the people who made the TWRP recovery. I hope I can give something back to the community with this guide.
If you have any questions. Please ask.
Thanks to all bro, i hope to flash it with recovery soon bc i have Windows
I tried but it doesn't seem possible. I get errors when restoring the back-up.
It's this working with Linux mint?
When I after I flash the recovery and then reboot I just get
Code:
Update failed, contact support.
Repeated in several languages. What am I doing wrong? :crying:
I had no luck getting this method to work.
askubuntu [dot] com/questions/767323/how-to-install-ubuntu-on-meizu-pro-5-that-was-originally-with-android
The above link worked first time and can be done on any OS
I hope it does work for other people, but at least we have an other method now as well.
I don't know if this works with Linux Mint. You might try the other method, it's os independent.
Pleytos said:
I hope it does work for other people, but at least we have an other method now as well.
I don't know if this works with Linux Mint. You might try the other method, it's os independent.
Click to expand...
Click to collapse
As far as I understood the guide on askubuntu didn't ensure ota update. In your experience you were able to download package update running the Ubuntu release?
I don't know, it always downloads the latest release with the ubuntu-device-flash command, and OTA update's don't come that often. So I have no experience yet.
Pleytos said:
I don't know, it always downloads the latest release with the ubuntu-device-flash command, and OTA update's don't come that often. So I have no experience yet.
Click to expand...
Click to collapse
can you let me know how to installing Android on my Meizu 5 Pro Ubuntu edition ?
I was looking at this:
https://developer.ubuntu.com/en/phone/devices/installing-ubuntu-for-devices/
and the procedure is slightly different from your guide.
Have you ever tried with this?
It looks that is should works on the PRO5 but I'm unsure to have understood when and how I have to flash the turbo recovery.
Yes that's what I tried first, but it didn't work for me. Do you mean my guide or their guide for flashing turbo recovery?
I mean their guide; as far as I understood the "turbo" recovery should be flashed onto the device from the channel.
Anyway I will try and let you know.
I didn't work for me. After doing what is in the guide and then updating to a newer release release candidate channel I got the Ubuntu logo recovery. But I could only get Ubuntu to install in the first place like the way I did it in the guide.
I just tested it and OTA updates work!
dbech said:
When I after I flash the recovery and then reboot I just get
Code:
Update failed, contact support.
Repeated in several languages. What am I doing wrong? :crying:
Click to expand...
Click to collapse
It's the same for me here Actually I think that the screen you mentioned is an error message from the Ubuntu recovery indeed the font used is the Ubuntu style one.
In my case I followed the instructions 5 times and eventually I learned to be fast enough to get the message and fastboot flash the turbo recovery but the further steps are not going as expected.
When I press the power+vol up combo, seems that the system reboot with a white meizu logo on a black screen and after that what happen is:
1. It's reboot with flyme
2. There is this error message on with screen
For both of above its possible to reboot the system and you will have a running flyme with the Ubuntu recovery.
I don't know if this is important but at the end of my couple of hours doing this :cyclops: all my music and pictures were still there while I was supposed to loose everything somehow during the process.
After manually stopping the phone from entering recovery and the go to fastboot -> flash recovery -> reboot recovery, I get a black screen for a couple of minutes and end up with a flymeOS recovery screen. Power off and on again and then I see Meizu on a black screen for a while and then Ubuntu loading screen.
Does that clarify anything?
@mickjmickj
If you still see your own files after trying for a while, that's not right. Do a full wipe:
- Go to recovery.
- Go to settings and select "use rm -f instead to formatting"
- Got to wipe -> advanced wipe and select all except the last/bottom one, and swipe to wipe.
Then try again. It should work. I'll try to make a youtube movie of my process this weekend, maybe I haven't explained it good enough.
When you say "reboot recovery" how did you do exactly?
Starting from the device ended to receive the files I press and hold power+vol down still the device is in fastboot mode, then I flash the recovery; starting from this I press and hold power+ vol up waiting the time to see what happen.
Maybe tonight I will try again after a full wipe as you suggest.
Reboot to recovery -> Holding power + vol up. Might not work the first time. But just keep holding the buttons till it does. Till you think you will enter recovery. You will need to boot directly to recovery, if you make one normal boot before you enter recovery, installation will fail in my experience.
I made a TWRP back up file for you to try: https://drive.google.com/open?id=0B5XS8BitdbnhQjN0N25Ed01ieWs
Maybe that works?
Related
Fuhu Nabi General information
1. Introduction
It was only recently that the Nabi2 got it's own forum. This device has been out a couple of years so the information you may be looking for is spread all over XDA. The largest single chunk of information resides in the Nabi 2 Root and Gapps Install by jmz, the problem is that thread is now 265 plus pages and mostly impossible to search. What I find more troubling is that the methods in which we go about root, modding etc evolve over time and newer users are using methods and tools that are now obsolete and can create more issues then they solve. Also while the moderators have done a wonderful job, not every Nabi thread is here in this section of the forum so I wanted to link to those that are pertinent.
While this is a Nabi2 forum I personally find it a better use of this corner of XDA to discuss all Nabi products, and this information post will discuss them all. Nabi JR, Nabi 2 Original, Disney and Nick, Nabi XD, Nabi2S, Nabi Dreamtab(Intel and Nvidia) , Nabi BigTab 20" and 24".
Most of the discussion will be catering to Microsoft Windows users as it is the most common usage scenario. It also will be light on discussion of the Intel version of the Dreamtab as it quite different.
Also look at the wiki. Information is very dated but there is some useful stuff, be careful with what you are flashing as the wiki is more informational then current methods. I would recommend asking before using any of the scripts or programs. http://forum.xda-developers.com/wiki/Fuhu_nabi_2
2.Basics
With the exception of the Nabi Dreamtab by Intel (DMTAB-IN08A), all the Fuhu Nabi products are built on Nvidia Tegra2, Tegra3, or Tegra 4. Therefore most methods of modding, recovery, etc are similar with a few device specific difference. The main utility we use is a custom recovery called TWRP, if you have come from other devices you might have used CWM, Odin, and countless other utilities, TWRP will be accomplishing the tasks on the Nabi devices. All the Nabi's already have a "stock" recovery on the device. It is useful for taking OTA(updates) and factory resetting but it's limitations end there, and this is where the TWRP custom recovery will come in to play.
There are 4 modes of operation for Nabi's
Each mode offers different usage scenarios and you should familiar with what they look like and which one you are in.
-Android
-Recovery -
-Bootloader/Fastboot
-Forced recovery/nvflash/APX
Windows are driver can be a pain but necessary before you can do anything else
No matter which method you choose or need to use the Windows drivers must be installed on your computer before you can do anything, without getting that setup nothing else is going to matter.
Most mods, rooting, and recovering devices and are done by one of 2 methods.
-Tool/Script - This is usually done by a GUI/Command prompt tool where the user clicks a few buttons and the magic happens in the background
-Manually - This is getting the hands dirty method, typing command lines, moving and unzipping files and is unfortunately common as there aren't many of the tools/scripts mentioned above.
3. The 4 Operational Modes
1. Android Usage: ADB and File Transfer.
-The normal operational mode for the device, and why you bought the tablet. ADB is NOT enabled by default, you will need to turn it on to perform any ADB operations. To enable ADB on the device:
-Login to parent mode
-Open Settings and see if "Developer Options" is listed if not
------Go to "About tablet".
------Click on Builder Number 10 or so times.
------Eventually you will see developer options are enabled.
-Open Developer Options and turn them on in top right corner
-Check the box USB debugging
-When using ADB on newer software builds when you execute a command the first time you will need to authorize on the tablet the first time, you can prevent this pop up by checking the box to always trust your computer.
2. Bootloader Usage: Fastboot. Booting to recovery. Booting to nvflash. Installing TWRP or stock recoveries.
Allows selection of other 3 modes, and utilizing fastboot commands.
How to enter bootloader/fastboot mode:
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line: adb reboot-bootloader
3. Recovery Usage: ADB, File Transfer, Installing Mods and Root, Recovering backups, Recovering Device.
There are 2 different versions of recovery. "Stock" and "TWRP". Stock is what comes with your device, and can be identified by the "dead android" picture when it boots up. Stock recovery is rather limited so if you see the "dead android" know you have stock recovery on the device. The 2nd possible recovery is TWRP, and the one used for most things you will be doing. It should say Team Win Recovery Project, or TWRP when it boots up.
How to enter recovery mode:
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen.
-Use the vol + and - keys to select recovery kernel. (one key will highlight the selection and the other key will "select" what's highlighted)
Device powered on:
-Use ADB and execute from the command line: adb reboot recovery
4. Forced Recovery Usage: Last resort for recovering dead tablet, heavy duty modding.
Rarely used. Can modify tablet, and prevent bricks. Only useful on Nabi2 Original, Disney, and Nick.
How to enter forced recovery mode:
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen.
-Use the vol + and - keys to select forced recovery. (one key will highlight the selection and the other key will "select" what's highlighted)
-screen will be completely blank, you will also need a windows APX driver to communicate with device.
4. Drivers
The windows drivers are problematic. There can be conflicts with other drivers, or just not found for the Nabi, or 64bit driver signature enforcement. As previously mentioned to utilize almost any operation for modding/rooting etc. you must have the drivers installed. None of the manual methods or auto tools are going to work if you don't get this accomplished.
It most cases you will only need 2 drivers. ADB interface and Fastboot/Bootloader Interface. The 3rd will only be needed on the rare chance you need to use the APX interface. What is important to understand is your computer will only see the interface that is used depending on the "Operational Mode" the tablet is in. For example if you are in Android or Recovery your computer will see ADB interface but NOT the fastboot interface. If you are in the bootloader interface(and have selected fastboot protocol) you will see the fastboot interface and NOT the ADB interface. So to install both drivers, you will have to boot to Android or Recovery and install one driver and then the bootloader to install the other. The order in which you do this will depend on which operational modes are available to you depending on the health of the tablet. (The same would apply if you need to use Forced recovery, you will need to be in that mode to install the 3rd driver APX interface, again this is rare)
Device Manger is the best way to see what is happening. With your tablet plugged in to the computer open device manager and look for either yellow ! or ? or something under the tree for "Android Device". If you are seeing the yellow ! or ? for your device then likely the drivers are not installed.
There are a few drivers and methods that seem to work best for most users. One of the bigger issues is 64bit driver signature enforcement. Windows Vista,7,8, and 10 do not like to install drivers that aren't digitally signed. There are 3 drivers that I am going to recommend. 2 are digitally signed drivers and there other is not.
PDAnet: I really don't like recommending this but it seems to work in most scenarios. Remember your tablet will have to enter both modes to install both drivers and remember that ADB will not show up by default in Android unless you enable it(see the operational mode section above)
http://pdanet.co/a/
NabiLab drivers: These are digitally self signed by me. That will require rootCA to be installed. This could create a security risk if someone was to steal my signing key. If that worries you don't use them or uninstall the drivers and certificate when you are done.
http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Universal naked:
If you aren't technically savvy I would use these as last resort. It will require you to disable "windows driver signature enforcement"(google it because it depends on windows version). Extract the zip package. Enter device manager and find your device, and manually update driver by pointing to the folder you extracted the zip.
http://forum.xda-developers.com/showthread.php?t=2263822
5. Tools and Automated scripts.
There aren't a lot of current tools available. They have mostly aged beyond their usefulness. The reasons are quite a few.
1. As the Nabi's upgrades the Android software from Ice Cream Sandwich to Jellybean to KitKat, the bootloader also changes. This changes how TWRP is able to see the internal storage and usually it can't. An Ice Cream Sandwich bootloader needs to use a TWRP for that version. For example the original Nabi2 has 3 different TWRP versions for the 3 different bootloaders. A lot of the older tools were made with a TWRP that no longer will work with your device. This will show up as TWRP "unable to mount" errors, and therefore the tool/script will fail for that reason.
2. Gapps. Originally many Nabi devices didn't have a Google Play store option. A lot of the tools still work on that premise, but most Nabi's have Google Play now. Google Apps also change with the Android version. So the tools can make mods based on that old information will cause problems.
3. Super user. A lot of older tools with "root" scripts don't have a current super user(root) binary and daemon. Newer Android version need a more up to date Super User install. With this situation you won't cause as many problems but will not good root with the script like you expect.
I will try to keep the list somewhat up to date
4. Mods. Like above, the mods that change your screen and/or add functionality, are heavily dependent on your android version, and will usually make your tablet un bootable if using an incompatible one.
Taking that in to account it's important to realize using old tools will cause you more issues then using no tools at all. I will try to keep the list some what up to date but in general there aren't many still usable tools.
The only tool that is even somewhat current is NabiLabGUI 2015, it can deal with quite a few of the Nabi products, and is at least very good at troubleshooting and has a command line setup that you can use to follow other users command line suggestions.
Get it here. http://nabtabhacks.com/nabilabgui2015/publish.htm
Here is the thread for the OLD version of the program. http://forum.xda-developers.com/showthread.php?t=2391449
Remember none of these are going to work if you haven't set up the drivers
Nabi2 Original/Disney/Nick
Old software not to use: jmzroot package, Ubuntu install from scratch, original NabiLab(non GUI version), and most others.
Really just stick with NabiLab2015 if you need a automated solution.
NabiXD
The XD hasn't changed much so this probably still will work http://forum.xda-developers.com/showthread.php?t=2207499
Nabi JR
For the Tegra2 4GB NABI-NV5A(couple years old) NabiLab2015 can do some functions or this tool http://forum.xda-developers.com/showthread.php?t=2200119
For the Tegra3 16GB NABI-NV5B(also a couple years old) NabiLab2015 can do some functions.
For the newest NabiJR SNBJR-MT5C - Not much, no TWRP even available yet.
Nabi DreamTab Nvidia Edition
Latest installer http://forum.xda-developers.com/showpost.php?p=63151136&postcount=46
Nabi BigTabs
None
Nabi 2S(newer Nabi 2 tablet)
None
If the tools aren't working your are going to need to do it by hand. See next section.
6. Setting up to do it by hand
Remember none of this is going to work if you haven't set up the drivers. Putting it all together now, also recall that you must be in the right "Operational Mode" to use either fastboot or to use ADB.
First of all I should mention that NabiLabGUI2015 has an option to work from the command line and has a lot of this already setup but to start from scratch:
When you setup the drivers earlier you got a driver for ADB and a driver for fastboot. Now to then talk to those interfaces you will need software to do that. Specifically an ADB.exe and fastboot.exe.
-Download and install this package(pay attention to where you install this as you will likely need to put files in there later): http://forum.xda-developers.com/showthread.php?t=2317790
-From your start menu select "Minimal ADB and Fastboot" this should open a command prompt where you can type commands
-If you didn't pay attention or forgot where you installed the files, at the command prompt that opens type "explorer ." The period is important, explorer <space bar> and a period. So type what is between the quotes.
Now you can drop and drag, unzip, etc the files you need in to that folder. You are done with manual setup.
For nvflash setup(Only for Nabi2 Orig, Nick, Disney NOT 2S, this step won't normally ever be required, and is only here for completeness)
-Download the nvflash.zip attached to this post.
-Make a new folder in the same folder as above and call it nvflash
-Extract the contents of the nvflash.zip in to the nvflash folder
-At the command prompt type "cd nvflash" to change in to the folder and use nvflash
THIS IS STILL A WORK IN PROGRESS
7. Getting TWRP on the device
The most common form of using TWRP is to install to the recovery partition of your device. Remember on certain devices(Nabi2 for example) the version of TWRP you use has to match the bootloader on the device, and the bootloader "type" will almost always correlate to the version of Android you are/were using. So if your Android ROM is Kitkat, the bootloader will be KitKat and you should use the KitKat TWRP. There are various tools linked above in the tools and scripts section that can install TWRP automatically depending on device or you can also use "dd" from Android to install it. In this section the manual method of installing will be highlighted.
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
On some device the bootloader is "locked", without unlocking the bootloader TWRP cannot be loaded. Unlocking the bootloader will erase ALL personal data on the device. If you see a message like this when trying to load TWRP:
downloading 'recovery.img'...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.003s
You will need to unlock the bootloader with following command
Code:
fastboot oem unlock
OR
Code:
fastboot -i 0x0489 oem unlock
8. TWRP List and Downloads
Latest TWRP Recovery for all Nabi devices, download links, and discussion threads.
*Updated as of 04/19/2018*
Also see my AFH account https://androidfilehost.com/?w=files&flid=41986
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
Code:
[U][B]Nabi2 Disney and Nick (NABI-NV7A-D or NABI-NV7A-N)[/B][/U]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
Code:
[U][B]Nabi2S (SNB02-NV7A)[/B][/U]
KitKat TWRP 2.7.1[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3148865&d=1423018617"] Download[/URL]
Code:
[B][U]Nabi JR A (Tegra2 4GB, NV5A)[/U][/B]
TWRP 2.6.3[URL="https://androidfilehost.com/user/?w=settings-dev-files&flid=44896"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2200119"] Link[/URL]
Code:
[B][U]Nabi JR B (Tegra3 16 NV5B)[/U][/B]
TWRP 2.6.3[URL="https://androidfilehost.com/user/?w=settings-dev-files&flid=44897"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2391468"] Link[/URL]
Code:
[B][U]Nabi JR New (SNBJR-MT5C)[/U][/B]
None - Work in progess
Code:
[B][U]Nabi XD (NV10A)[/U][/B]
TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3171414&d=1424242604"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2207459"] Link[/URL]
Code:
[B][U]Nabi Dreamtab Nvidia NV08B[/U][/B]
TWRP 3.0.0[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3692992&d=1458705735"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917"] Link[/URL]
Code:
[B][U]Nabi Dreamtab Intel IN08A[/U][/B]
Tethered CWM recovery see here: [URL="http://forum.xda-developers.com/showpost.php?p=57825022&postcount=25"]Link[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917"] Link[/URL]
EDIT 11/5/2019 Might be a recovery download mirror Download
Discussion Thread Link[/CODE]
Code:
[B][U]Nabi BigTab NV24A[/U][/B]
No TWRP - Working in progress, the TWRP for the NV20A 20" BigTab can bring up ADB
Discussion Thread [URL="https://forum.xda-developers.com/nabi-2/general/nabi-nabi-se-discussion-thread-t3770816"] Link[/URL]
Code:
[B][U]Nabi SE[/U][/B]
TWRP 3.0.2 [URL="https://github.com/huckleberrypie/device_Mattel_NabiSE/releases"] Downlaod[/URL]
Discussion Thread [URL="https://forum.xda-developers.com/nabi-2/general/nabi-nabi-se-discussion-thread-t3770816"] Link[/URL]
9. Recovering Bricked Devices
In this section we will go over recovery from non booting devices. I would classify non booting as one of three situations.
1) Tablet is being used normally and one day it has crashed or when restarted sits at the bootamination(spinning Nabi logo, Dreamworks characters)
If you haven't been doing anything but using the tablet normally then the most likely culprit is that some file is corrupt on the data partition. While there are ways to replace just that file if you suspect which one it is the simple solution is to try and wipe the data partition and start fresh. There are two ways to accomplish this:
a) Use the stock recovery if you haven't installed TWRP or haven't unlocked the bootloader. Boot the stock recovery using "recovery" in Section 3 above. Press both vol+ and vol - and the same time and you should get a menu where you can select to factory reset. This wipes ALL data from the tablet. When complete try to boot the tablet.
b) Use TWRP recovery from section 7 above. TWRP will give you some flexibility in that you can back up the data partition before you wipe it(in case the issue wasn't actually the data partition you can restore the data back), and TWRP will not delete "internal storage" if you do a factory reset.
-Boot TWRP
-<optional> Backup data partition to EXTERNAL sdcard(be safe and back up to external card not internal)
-<optional> While connected to computer backup the remaining files on the "internal sd" with windows explorer(Device should show up as an MTP device on later TWRP versions)
-Select Wipe tab and factory reset
2) You have installed a mod, installed a root application that has made a system modification, installed a zip file, or were just playing around swiping and wiping things in TWRP. Sometimes this will appear the same as above with a bootloop and boot animation that goes on forever.
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Backup tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
10. ROM List and Downloads
Also see my AFH account https://androidfilehost.com/?w=files&flid=41986
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
KitKat 3.0.13 ROM[URL="https://www.androidfilehost.com/?fid=24052804347843199"] Download[/URL]
ROM Mirror [URL="http://www.nabtabhacks.com/downloads/3013stock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087011778"] Download[/URL]
Code:
[U][B]Nabi2 Disney(NABI-NV7A-D)[/B][/U]
KitKat 3.0.4 ROM[URL="https://www.androidfilehost.com/?fid=24052804347843201"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/304D.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087011793"] Download[/URL]
Code:
[U][B]Nabi2 Nick (NABI-NV7A-N)[/B][/U]
KitKat 3.0.5 ROM[URL="https://www.androidfilehost.com/?fid=24052804347843202"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/305N.zip"] Download[/URL]
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
Code:
[U][B]Nabi2S (SNB02-NV7A)[/B][/U]
KitKat 2.0.141107[URL="https://www.androidfilehost.com/?fid=24052804347850076"] Download[/URL]
Mirror[URL="http://www.nabtabhacks.com/downloads/2_0_141107stock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087011808"] Download[/URL]
Code:
[B][U]Nabi JR A (Tegra2 4GB, NV5A)[/U][/B]
Latest Stock ROM[URL="https://www.androidfilehost.com/?fid=24052804347850083"] Download[/URL]
Mirror [URL="http://www.nabtabhacks.com/downloads/njr1stBACKUP.rar"] Download[/URL]
Bootloader: None
Code:
[B][U]Nabi JR B (Tegra3 16 NV5B)[/U][/B]
Latest Stock ROM[URL="https://www.androidfilehost.com/?fid=24052804347850077"] Download[/URL]
Mirror [URL="http://www.nabtabhacks.com/downloads/JRB.zip"] Download[/URL]
Bootloader: None
Code:
[B][U]Nabi JR New (SNBJR-MT5C)[/U][/B]
None - Work in progess
Code:
[B][U]Nabi XD (NV10A)[/U][/B]
EDIT 11/5/2019 ROM Mirror[URL="https://androidfilehost.com/?fid=24269982087013990"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2207459"] Link[/URL]
Bootloader: None
Code:
[B][U]Nabi Dreamtab Nvidia NV08B[/U][/B]
1312 ROM[URL="https://www.androidfilehost.com/?fid=24269982087013911"] Download[/URL]
ROM mirror [URL="http://www.nabtabhacks.com/downloads/1312stock.zip"] Download[/URL]
Bootloader[URL="https://www.androidfilehost.com/?fid=24269982087013988"] Download[/URL]
Code:
[B][U]Nabi Dreamtab Intel IN08A[/U][/B]
EDIT 11/5/2019 from some files I found.
Maybe a ROM backup [URL="https://www.androidfilehost.com/?fid=24533100289589801"] Download [/URL]
[STRIKE]Tethered CWM recovery see here: [URL="http://forum.xda-developers.com/showpost.php?p=57825022&postcount=25"]Link[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917"] Link[/URL]
Code:
[B][U]Nabi BigTab NV20A[/U][/B]
TWRP 2.8.1 [URL="https://www.dropbox.com/s/p1gh6oo34sgbwri/recovery.img?dl=0"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/android/help/24-tab-hd-powered-nabi-rooting-t2932197"] Link[/URL]
Code:
[B][U]Nabi BigTab NV24A[/U][/B]
No TWRP - Working in progress, the TWRP for the NV20A 20" BigTab can bring up ADB
Discussion Thread [URL="http://forum.xda-developers.com/android/help/24-tab-hd-powered-nabi-rooting-t2932197"] Link[/URL]
[/STRIKE]
One last post for misc and other
nabi dream tab
hello I have a nabi dream tab that dead and wont boot i follow thw instruction in the forums and re install the stock rom
and boot loader. everything was successful but the tablet still wont boot up its stuck on powered by android
any advice please
Suck4 said:
hello I have a nabi dream tab that dead and wont boot i follow thw instruction in the forums and re install the stock rom
and boot loader. everything was successful but the tablet still wont boot up its stuck on powered by android
any advice please
Click to expand...
Click to collapse
Which ROM did you reinstall? What version 1.3.7, 1.3.12? Have you tried doing a tablet wipe/factory reset?(obviously you will lose everything on the tablet)
Nabi dream tab
aicjofs said:
Which ROM did you reinstall? What version 1.3.7, 1.3.12? Have you tried doing a tablet wipe/factory reset?(obviously you will lose everything on the tablet)
Click to expand...
Click to collapse
I tried both the 1.3.7 and 1.1.12 with boot loader 137 and still no success..
Before I did all that reading and trying I first tried the factory reset but the tablet still didnt boot so i went on to use the twrp tool and follow the instruction here in the forums but still no luck..
I also did some further research and from what i understand it appears that the firmware is what i need to flash so i open up the tablet and try to use the board id and processor type to find it but no luck.. (not sure if i needed to do that but since the twrp didnt work i tried another method) its the dream tab NVO8B..
t
All very nice, but will there ever be tips for doing this stuff on Linux? We do not run MSWin in our household. Granted, it will probably be a few months before I once again try rooting/flashing the Nabi2S, so there's time for the Linux methods to come out if they ever do.
Suck4 said:
I tried both the 1.3.7 and 1.1.12 with boot loader 137 and still no success..
Before I did all that reading and trying I first tried the factory reset but the tablet still didnt boot so i went on to use the twrp tool and follow the instruction here in the forums but still no luck..
I also did some further research and from what i understand it appears that the firmware is what i need to flash so i open up the tablet and try to use the board id and processor type to find it but no luck.. (not sure if i needed to do that but since the twrp didnt work i tried another method) its the dream tab NVO8B..
t
Click to expand...
Click to collapse
I'd be interested if it helped to format system and data in TWRP before the restore next time.
jelabarre59 said:
All very nice, but will there ever be tips for doing this stuff on Linux? We do not run MSWin in our household. Granted, it will probably be a few months before I once again try rooting/flashing the Nabi2S, so there's time for the Linux methods to come out if they ever do.
Click to expand...
Click to collapse
Most of the time the commandine stuff is still the same when it comes to fastboot or adb. A lot of the scripts are easy to modify for linux.
Android keeps restoring all apps
I've got the NabiLab 2015gui, wiped and restored the Nabi2 to 3.0.13, installed twrp through it. I've flashed to the MinimalNabiWipe.zip, and rebooted and it goes right back to please wait while android updates 117 apps. I also can't get it to accept the changes recommended at trendblog.net/fix-kitkat-sd-card-write-restriction/ (which I had found while reading through 50+ of the most recent pages in the Nabi 2 Root and Gapps Install thread, it throws a generic error that it couldn't save. Any ideas?
damfn said:
I've flashed to the MinimalNabiWipe.zip, and rebooted and it goes right back to please wait while android updates 117 apps.
Click to expand...
Click to collapse
I would check to see if you have .odex files that are orphaned. If minimalnabiwipe.zip deleted the .apk and leaves behind the associated .odex file what you describee will happen.
damfn said:
I also can't get it to accept the changes recommended at trendblog.net/fix-kitkat-sd-card-write-restriction/ (which I had found while reading through 50+ of the most recent pages in the Nabi 2 Root and Gapps Install thread, it throws a generic error that it couldn't save. Any ideas?
Click to expand...
Click to collapse
Make sure /system is mounted read AND write?
aicjofs said:
I would check to see if you have .odex files that are orphaned. If minimalnabiwipe.zip deleted the .apk and leaves behind the associated .odex file what you describee will happen.
Click to expand...
Click to collapse
Can you point me in the direction of the .odex file locations? As I did a look around all the folders I could find in twrp and couldn't find .odex.
aicjofs said:
Make sure /system is mounted read AND write?
Click to expand...
Click to collapse
You are correct, I ended up removing "es file manager" and installing "total commander file manager" as it would do it for me.
hi all
I appreciate the awesome write up to help get this done.
I am having trouble, though. I am going thru nabilabgui. I get as far as rebooting below and then nothing happens when I hit a key. It appears that the nabi also freezes on reboot. Not sure what is going on. I tried going thru the manual method and seem to be confused.
Anyway, I would be happy to provide more details to help with this. Any help is appreciated, thank you.
******** Install Recovery and Root for JB and KK ********
Make sure device is connected and detected. Press any key.
Press any key to continue . . .
# Rebooting device
# If stuck here drivers are not installed
< waiting for device >
sending 'recovery' (8176 KB)...
OKAY [ 2.115s]
writing 'recovery'...
Press any key to continue . . .
OKAY [ 1.571s]
finished. total time: 3.686s
Press any key to continue . . .
# If writing recovery OKAY is stated above
# Press VOL - button on device until bootloader is selected
# Push VOL + to select.
# Press VOL - button on device until recovery kernel is selected
# Push VOL + to select.
# Press enter when you see TWRP has booted
Press any key to continue . . .
Press any key to continue . . .
# Pushing root to your device
# Ignore external SD card error if you have none installed
# This will take a few minutes. Wait.
mount: mounting /external_sdcard on vfat failed: No such file or directory
5580 KB/s (4017098 bytes in 0.703s)
0 KB/s (25 bytes in 1.000s)
# Rebooting recovery to flash gapps and root rom.
# Please wait until backup and install has been completed
# Once it has completed hit enter
Press any key to continue . . .
aeneas3 said:
hi all
I appreciate the awesome write up to help get this done.
I am having trouble, though. I am going thru nabilabgui. I get as far as rebooting below and then nothing happens when I hit a key. It appears that the nabi also freezes on reboot. Not sure what is going on. I tried going thru the manual method and seem to be confused.
Anyway, I would be happy to provide more details to help with this. Any help is appreciated, thank you.
******** Install Recovery and Root for JB and KK ********
Make sure device is connected and detected. Press any key.
Press any key to continue . . .
# Rebooting device
# If stuck here drivers are not installed
< waiting for device >
sending 'recovery' (8176 KB)...
OKAY [ 2.115s]
writing 'recovery'...
Press any key to continue . . .
OKAY [ 1.571s]
finished. total time: 3.686s
Press any key to continue . . .
# If writing recovery OKAY is stated above
# Press VOL - button on device until bootloader is selected
# Push VOL + to select.
# Press VOL - button on device until recovery kernel is selected
# Push VOL + to select.
# Press enter when you see TWRP has booted
Press any key to continue . . .
Press any key to continue . . .
# Pushing root to your device
# Ignore external SD card error if you have none installed
# This will take a few minutes. Wait.
mount: mounting /external_sdcard on vfat failed: No such file or directory
5580 KB/s (4017098 bytes in 0.703s)
0 KB/s (25 bytes in 1.000s)
# Rebooting recovery to flash gapps and root rom.
# Please wait until backup and install has been completed
# Once it has completed hit enter
Press any key to continue . . .
Click to expand...
Click to collapse
You don't mention what device you have? I'm guessing Nabi2 of some sort, which particular model? Judging by the log it seemed to have written recovery, at which point is it hanging? The way I had to write it as windows app and emulating a command window(so if I ever stopped updating the GUI program someone could edit the batch files on the backend to do what they needed) I couldn't find a good way to end the script very gracefully(I'm not very strong at that language), but it looks like it finished normally.
aicjofs said:
You don't mention what device you have? I'm guessing Nabi2 of some sort, which particular model? Judging by the log it seemed to have written recovery, at which point is it hanging? The way I had to write it as windows app and emulating a command window(so if I ever stopped updating the GUI program someone could edit the batch files on the backend to do what they needed) I couldn't find a good way to end the script very gracefully(I'm not very strong at that language), but it looks like it finished normally.
Click to expand...
Click to collapse
sorry, nabi 2. thanks! so the next step would be flashing a rom?
It hangs at the end of the text there.
"# Rebooting recovery to flash gapps and root rom.
# Please wait until backup and install has been completed
# Once it has completed hit enter
Press any key to continue . . .'
Thank you. And the program is awesome, no need for apologies about how it ends!
i try restore to stock my nabi XD
i try flash nabi XD with rom stock, 15stock.zip in twrp and faild and to restore as backup, It is restored only well and stays in the logo.
help
my whatsapp +18097191879:crying::crying::crying::crying:
sergioagilp said:
i try flash nabi XD with rom stock, 15stock.zip in twrp and faild and to restore as backup, It is restored only well and stays in the logo.
help
my whatsapp +18097191879:crying::crying::crying::crying:
Click to expand...
Click to collapse
Are you trying to flash("install") the zip or extract the zip(system.win, etc) and restore? I'm not sure which part is failing for you. Which TWRP version?
Did you also do a factory reset after the flash?
Any one have scatter file I'm in twrp but it cannot mount any thing it says internal disc as zero I need to format it but cannot as Windows does not see it so if I use a scatter file try and flash it so flash tools
Any chance there will support for the Nabi Jr (new) soon? I made mistake of buying 2 from Amazon on t assumption that they were completely "hackable".
LOG IN Issue: It's Nabi 2 Demo Device I guess
Dear XDA friends,
This is Zeeshan from Pakistan. Few days back I purchased a used*Nabi 2 from*the local market here in Pakistan. The salesman gave this password to enter*into*the mommy/daddy mode "zxcv6789" which was working perfectly fine.
Then I thought of creating my own nabi account to enhance my daughter's Nabi experience. I registered through my own email ID,*which have*been working fine . However lately I decided to factory reset the Nabi 2 to improve its speed and performance, here is where I have been stuck from last so many days.
After the hard factory reset the tablet did not ask for setting up my Nabi account but it automatically logged in to the nabi mode and now when I try to login into to the mommy mode it says your password is incorrect, when I click on the forgot password link it says "An email has been sent to you. Please allow a few minutes for* delivery. ([email protected])" which seems to be nabi's own email ID and I am in a doubt that this device could be a store demo unit however when I purchased and before the factory reset it was working like a normal one, no demo nothing.
How can I fix this issue to login to Nabi 2 using my own registered email ID.
Following are the details of my Nabi2 device:
About this nabi
Account: [email protected]
Model No: NABI2NV7A-D
Android Version: 4.0.4
Build Number: IMM76L
Product Version: 1.9.23
Many thanks in advance.
Looking forward to any help.
Hi. New to this device. Just to check has anyone successfully root this device on the Marshmallow 6.0?
I did read around for a solution but only saw the lollipop-root-method.
Thanks in advance!
Sent from my ASUS_T00N using Tapatalk
Still no solution found. Anyone?
Sent from my SM-G900FD using Tapatalk
I can't figure out root on 6.0.1 either. I just upgraded from rooted 5.0.1 to 6.0.1 using TWRP on WW version of firmware with Padfone S. I immediately flashed SuperSU from TWRP after flashing the update, but the update still broke root. Tried both Kingroot APK and Kingoroot APK + PC without success.
Thanks for that update martingriffis! At least we know that didn't work.
Anyone else has any other solution?
Sent from my ASUS_T00N using Tapatalk
https://forum.xda-developers.com/showpost.php?p=69715735&postcount=2
Nice! Will try that out.
Sent from my ASUS_T00N using Tapatalk
Systemless root?
Enviado desde mi Moto G (4) mediante Tapatalk
The binarie not update
Enviado desde mi ASUS_T00N mediante Tapatalk
itsme1st said:
https://forum.xda-developers.com/showpost.php?p=69715735&postcount=2
Click to expand...
Click to collapse
I recently tried doing this. To no avail. DLs not working. Been trying to push twrp can't too.
Anyone successfully done this recently? Care to share the dls here?
Sent from my ASUS_T00N using Tapatalk
My problem ist - i can`t get the TWRP 2.8.7.8. - the HP seems to be shut down. So I cannot try it. And I need urgent root, cause I have a Synology Server save Clod also on the Asus. Anyone an Idea?
Is here anybody who has coincidentally the TWRP 2.8.7.8. still on his PC and cand send it per mail??
Asus Padfone S Marshmallow Rooted *Working*
If you like me 'get the device and direct update to latest MM', then you need to do something like this.
First you need the device and a computer.
Next is get all files from here https://forum.xda-developers.com/showpost.php?p=62352276&postcount=2 and skip the old supersu and use the new version here https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
After that enter the device into fastboot mode (Turn on while hold vol up and it will vibrate once and stuck at Asus logo)
Connect the usb to computer, open adb (extract fastboot and adb.rar to new folder, inside it right-click on empty place while holding [Shift] on keyboard, and see for 'Open command window here')
Write first 'fastboot devices' (without quote) to check if the computer detect your device with '(font+number) fastboot' in cmd.
If is working, then you can go to the next step. If not maybe need to get some adb driver to make it working.
Next is extract twrp_2.8.7.0.rar into the adb folder, make sure it is .img file.
At cmd, write 'fastboot flash recovery twrp_2.8.7.0.img' and press enter. If you see some line like this 'remote: can't flash unsigned image' is actually working.
After that write 'fastboot reboot' and press vol down so the device will immediately enter the recovery mode. If working the device will enter TWRP perfectly (opening sometime it will say something about 'read-only', just press 'Back' to get the actual TWRP menu) but if the device just straight boot normally, you need to do the flash recovery back because it failed.
At TWRP menu choose mount, and put some CrowLock_RC3.zip and SuperSU-v2.79-201612051815.zip from your computer to your device folder.
Press back at TWRP and flash the CrowLock_RC3.zip to unlock bootloader first (if you do not see this file, just press 'storage...' at top and choose the actual storage). After done you need to reboot the device and enter fastboot mode again (If you want to make sure your device still working, can just reboot it normally but do back fastboot mode again after that)
Next is flash the old recovery asus_t00n_twrp_2_7_1_1.img. Same step as before. After your reboot the device and enter recovery mode, your screen device will go to black. Actually is working, you just need to press power on once or twice to make the TWRP screen visible.
Next is flash the SuperSU-v2.79-201612051815.zip just like how you flash the CrowLock_RC3.zip before. You can wipe dalvik/cache after that or maybe not, then reboot. Your device will bootloop once and after that you can enjoy your device with root working.
To make sure your device have rooted, use Root Checker. For the first time, supersu will make a long time to prompt it but after that it should working normally like the previous day you use.
Has to be SuperSu 2.79, any higher won't work.
After finished instal twrp 2.7.1.1 and sucess i try to sigin twrp again and My screen change black and i press power once or twice but keep black no change
Can you help me..thx
If your have linux, you can install android-tools, then use fastboot from there.
HEZAiKU said:
At TWRP menu choose mount, and put some CrowLock_RC3.zip and SuperSU-v2.79-201612051815.zip from your computer to your device folder.
Click to expand...
Click to collapse
You can also got to /data/media/0 to access to your Downloads directory.
HEZAiKU said:
Press back at TWRP and flash the CrowLock_RC3.zip
Click to expand...
Click to collapse
The button is not named "flash" but "install".
HEZAiKU said:
Next is flash the old recovery asus_t00n_twrp_2_7_1_1.img. Same step as before. After your reboot the device and enter recovery mode, your screen device will go to black. Actually is working, you just need to press power on once or twice to make the TWRP screen visible.
Click to expand...
Click to collapse
Oops, I forgot that step ...
@wric01 is it true then? Thou when im download the SuperSU.zip that time its still the latest so i thought any latest version should be working.
@Paidi86 just make sure you follow the tutorial correctly.
@xdej well, cuz for smartphone android device, im actually too prefer with 'flash' instead 'install', well for me its still the same meaning.
I got root with my personnal open-source files:
Code:
# /system/bin/id
uid=0(root) gid=0(root) groups=0(root), context=u:r:init:s0
How I got there:
(1) install Termux from Google Play
(2) in /data/data/com.termux/files/home, put "CrowLock_RC3.zip" and "SuperSU-v2.79-201612051815.zip".
(3) Install version v19 (will be uploaded soon) of https://sourceforge.net/p/gentooandroid/wiki/InstallingInstructions/ using EPREFIX=/data/data/com.termux/usrex.spartacuside/gentoo_armv6l and PLACE_LD=/data/data/com.symli/n/3 following all instructions (that took me half a day, this installs Gentoo on your phone; if you want I can make an easier way). Don't add any package with emerge, this is not needed at this point.
(4) Download twrp_2.8.7.0.rar from https://mega.nz/#!GwRRBBjT!8ms39GK62...aKA816Cg4lsQr0
checksums with sha1sum:
8dc6b577d04fbd05ff31d3dedca7cf51d7bfef22 twrp_2.8.7.0.img
1d784bde5339054ed27ff38fb17e1368f95d6dcb twrp_2.8.7.0.rar
(5) Connect it to a computer, then power Off the phone, keep "vol up" button pressed before it switches off.
(6) If you did not connect it to a computer, press "power" button
(7) the phone powers on, vibrate a bit, you can release the buttons "power" and "vol up".
(8) you now need another computer. If it is a linux computer, install package android-tools , then run, as root: fastboot flash recovery twrp_2.8.7.0.img ; if it is a windows computer, issue the equivalent instruction with fastboot.exe downloaded from https://forum.xda-developers.com/showpost.php?p=62352276&postcount=2 (checksums with sha1sum:
e01c22dc34e915bca88de2c73966b807b2b39f26 fastboot.exe
eb9ce15bebcfb63a5cb4c24913aba76c8d319287 fastboot_and_adb.rar) ; whether you have a mac or no, also download fastboot from https://wiki.lineageos.org/adb_fastboot_guide.html You can ignore the erro "remote: can't flash unsigned image' is actually working": it nevertheless did works.
(9) keep "vol down" pressed on the phone.
(10) on linux, execute: fastboot reboot ; on windows, fastboot.exe reboot I guess
(11) after it vibrates, you can now release "vol down". select "enter recovery mode", then validate with the power button. The phone boots twrp, which is a sort of equivalent of init=/bin/sh on linux.
(12) in twrp, select "keep read-only", then use "install", then select "/data/data/com.termux/files/home/CrowLock_RC3.zip", validate, then repeat steps (5) to (11).
(13) in twrp, select "keep read-only", then use "install", then select "/data/data/com.termux/files/home/SuperSU-v2.79-201612051815.zip", validate, then repeat steps (5) to (11) (if you skips entirely step (13), the phone will not be able to boot).
(14) in twrp, select "advanced", then "terminal command", then select directory /data/data/com.termux/usrex.spartacuside/gentoo_armv6l/usr/local/bin as working directory
(15) execute: mount /system
(16) execute: mv /system/bin/app_process32 /system/bin/app_process.wrapped (you will first need to use backspace to remove characters of previous command, "mount /system")
(17) execute: cp app_process_wrapper /system/bin/app_process32
(18) execute: chgrp shell /system/bin/app_process32
(19) execute: umount /system
(20) use back button three times, and select reboot, then select system.
(21) it should boot normally. It did on my asus padfone S and on my asus padfone S+ (the only padfone with 3GB of RAM).
(22) open tmux, inside it, execute:
Code:
ssh -p 64000 [email protected]
(23) you will be asked the root password that you used at step (2)
if you want to add packages, remember to use
Code:
ssh -p 64000 [email protected]
before using Gentoo's installer:
Code:
PORTAGE_BINHOST=http://sourceforge.net/projects/gentooandroid/files/packages/packages emerge --autounmask-write -GKv firefox
xdej said:
I got root without unlocking, with my personnal open-source method:
Code:
# /system/bin/id
uid=0(root) gid=0(root) groups=0(root), context=u:r:init:s0
How I got there:
(1) install Termux from Google Play
(2) Install version v19 (will be uploaded soon) of gentooandroid.sf.net
Click to expand...
Click to collapse
You can replace step (2) with any other provider of sshd binary:
(2bis) ignore step (2),
(2ter) put any binary you want to be executed with selinux context u:r:init:s0 at /data/data/com.termux/usrex.spartacuside/gentoo_armv6l/usr/local/bin/sshd_root
(2quater) download app_process_wrapper binary
/data/data/com.termux/usrex.spartacuside/gentoo_armv6l/usr/local/bin/app_process_wrapper from the attachment in this message
Then proceed from step (3) onwards.
This may work for other phones supported by twrp, I did nothing asus-specific.
No need to install old recovery. just fastboot your device (power on and vol up) and then do `.fastboot boot asus_t00n_twrp_2_7_1_1.img` it'll boot the old recovery.
Make sure to put supersu in device memory, not sdcard.
The method you give is much simple then the rest. Just want to know if the custom recovery mode is able to enter without unlocked bootloader?
Hey there,
i was wondering if anyone got an idea how to get root access / TWRP working on a Doogee T6 Pro ?
I don't really find anything online that seems to be working and of course most one-click root tools dont work for China phones.
Anyone got any idea ? The official forums look empty as well.
It looks good
Applesoap said:
Hey there,
i was wondering if anyone got an idea how to get root access / TWRP working on a Doogee T6 Pro ?
I don't really find anything online that seems to be working and of course most one-click root tools dont work for China phones.
Anyone got any idea ? The official forums look empty as well.
Click to expand...
Click to collapse
Some useful tips for rooting MAZE Alpha, perhaps will help you : MAZE Alpha root
Use the method I to patch your boot.img with Magisk-v14 and flash the result image, it must works
Here is the HowTo, have done it 3 times yet:
First, get the correct TWRP Version for Doogee T6Pro ( i dont remember where i got it, i can upload it somewhere if someone have a good location) and the SuperSu Zip.
Then, activate the Developer Options in the Device Settings and Activate the OEM Unlock and USB Debugging in there.
The next Step is to Boot the Device in Fastboot mode. you can either do it by USB with the Terminal Command: "adb reboot bootloader" or you can turn the device of and then reboot it by pressing the Volume Up Button and the Power Button simultanously (quite difficult, didnt Work every Time). You will get to a menue with 3 options: Boot to Recovery, Fastboot and Normal. Switch through these Options with the Volume Up Button and Select it with the Volume Down. Go To the Fastboot Option and Select it.
In Fastboot Mode, plug in the device to an computer and type the terminal command "fastboot oem unlock" (in windows, you have to install the fastboot tools. i dont remember that i had to install them in ubuntu... im not sure). this will wipe the whole data of the device. its important to reboot the device afterwards normaly. otherwise it could happen that you get stuck in an bootloop later ( happend twice to me ) this normal system boot will last much longer then normal, so get a coffee or tea
the next step is do get to fastboot mode again and then send from your computer the command: "fastboot flash recovery twrp-recovery-filename.img". this will flash the recovery.img on the recovery partition.
than go to the bootloadermenue and this time you dont choose fastboot but the recovery option. this will start TWRP
while TWRP is running, you can copy the SuperSU zip to the device with Nautilus or in windows systems with windows explorer. then select "Install" in TWRP and select the SuperSU.zip.
After the installation, reboot to normal system and you are ready with rooting!
if something goes wrong, it can happen that booting to normal system will get you stuck in an bootloop. the last time i could repair the system by booting into recovery (TWRP) and select the Wipe menue and there the Format option. the other time i downloaded the original system from Doogee and flashed all partitions. im not sure if that was necessary.... but who knows :fingers-crossed:
Never had a problem running @phhusson GSI when running Android 8.0 bootloader. After I upgraded to Huawei 9.0, I can no longer load a system image, using the guide, it just bootloops every time.
Followed the official instructions from here:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Perform a factory reset on your device.
Reboot to your device’s stock recovery using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot recovery. Once here, use the volume keys to navigate and the power button to select the factory reset option.
Once your device has been factory reset, reboot to your device’s bootloader using either a button combination when booting or issuing the following ADB command when booted in Android: adb reboot bootloader
With your device connected to your PC, open up a command prompt or terminal window in the same directory where you downloaded your GSI of choice.
Enter the following command: fastboot erase system
Enter a command in the following format: fastboot -u flash system name_of_system.img (NOTE: -u is an invalid option, I think it supposed to be --unbuffered)
Allow the image to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering fastboot reboot.
I also tried the comment in the troubleshooting section:
As a last resort, you can try a full format of the data partition (WARNING: THIS WIPES EVERYTHING) by entering fastboot -w from a command prompt/terminal window while in the bootloader. I have had to do this on my Huawei device before it could work.
Nobody?
It seems Huawei have got Android 8 GSI certification, and then flipped a switch to stop it working post release, which is rather naughty.
I guess nobody cares that Huawei took this away from you.
Well, same problem here, but Openkirin ROMS still work as they use their "unopen-sourced" magic to make their ROMS run on EMUI 9 devices and Tablets.
as mentioned here https://forum.xda-developers.com/showpost.php?p=79811581&postcount=45 and here https://forum.xda-developers.com/showpost.php?p=79987022&postcount=48 there are some GSI Builds which boots on mediapad M5 SHT-AL09 with vendor 9.
I didn't test every GSI build, phhusson got me only to erecovery, and i wanted a build with gapps, so these two i can confirm to work.
I don't really trust openkirin. We don't know who they are (Internet forum accounts don't count) , and it's closed source. It could contain literally anything.
I will stick with stock I think.
Chr1stOnABike said:
I don't really trust openkirin. We don't know who they are (Internet forum accounts don't count) , and it's closed source. It could contain literally anything.
I will stick with stock I think.
Click to expand...
Click to collapse
Yes, me either
I tried to root my phone using this guide, followed it down to the word and yet my phone's stuck in a bootloop. It keeps restarting to the Poco start screen.
Ive got the stock recovery, and for some odd reason fastboot commands work only in the "FASTBOOTD" screen and not the the "FASTBOOT" screen which you get from "adb reboot bootloader" command.
I try to shut it down and it boots up back again in the same screen and is stuck there.
Im clueless and I really dont know what to do. Some help would be greatly appreciated.
edit: I tried to use the stock recovery and wipe data. No progress.
I tried to connect the phone with the MIAssistant but the app doesnt recognise the device.
I tried using the MiFlash tool to flash the stock rom, it goes on infinitely. Im currently trying to use the SP Flash tool and MediaTek Bypass tool but I havnt got any progress yet.
I promise I'm never buying MediaTek devices ever again.
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
aricooperdavis said:
Careful with the Flash and Bypass tools, they can cause problems.
What can you achieve with the hardware buttons on the phone? Can you get it into recovery?
Fastbootd working but fastboot not sounds like a USB drivers problem - there are some driver options here.
Click to expand...
Click to collapse
It was a driver issue, thanks for the link.
What I did to get out of the bootloop:
1. Download the latest Miui rom for your version, make sure it's the recovery version and not the fastboot one.
2. Press ALL the buttons, Vol+ Vol- and Power button to shut it down for a few seconds (assuming you can't switch it off as it keeps powering back up again).
3. After it's switched off, quickly press the power and vol- button until you see the FASTBOOT screen.
4. Connect with PC, make sure you have the proper drivers and have connected with the right USB port.
5. Download OrangeFox custom recovery. It is a unofficial custom recovery, so its stability is questionable. But it does the job here.
6. Copy the OrangeFox zip and the Miui rom file to your phone's SD card or any external storage which your phone can access.
7. In your PC, extract the OrangeFox zip folder in your platform-tools folder. (The folder where you run your cmd fastboot/adb commands)
8. Open up cmd, and enter the command:
fastboot flash boot recovery.img
9. Your phone should boot up to the OrangeFox recovery. If not switch the phone off (Step 2) and press power + vol+ button for booting up to the recovery.
10. Locate your OrangeFox zip installer file in the recovery and flash it.
11. Reboot to the recovery again.
12. Locate the Miui rom and flash that. Before swiping to flash the rom, there is a check box which says something like "flash OrangeFox once the rom has been flashed". If you want to keep OrangeFox as your recovery then check it, or else leave it unchecked. Flashing roms remove custom recoveries.
13. Your phone must reboot to miui.
NOTE: You can use fastboot commands to flash the rom but I'm not very familiar with fastboot commands (I actually forgot most of them). Hence I use the recovery method.
warhead1721972 said:
It was a driver issue, thanks for the link. Should I delete this post? It isnt much big of an issue imo.
Click to expand...
Click to collapse
Great, glad you got it sorted! No, leave it up, you never know someone might stumble across it and find it useful