Rooting HP Slate 7. Updated March 16 2014 - Miscellaneous Android Development

Updated to March 16th 2014.
General Warning, read before doing anything to your tablet:
Whenever you try to do anything to your system ALWAYS back up everything since there is always the chance that something might go wrong.
If something goes wrong you have to download and install the boot images from HP support, HP Slate 7 2800 restore image and HP Slate 7 4600 restore image, the install instructions are in the same page in "How to install".
Some users have had problems with the alternative rooting method using Bin4ry's tool, since it is some I will asume it is something someone is not doing correctly, because other users with the same slate model have been able to root, if it is your case where you can't actually root post here I'll try to help you in any way I can.
To end this sort of disclaimer, my Slate 7 is the model 4600 so I'm not actually able to try the method with other slate models, anyhow other users have had no problem but as always this could be your case and I'm not responsible in any way if you brick your device.
Cydia's Impactor tool has been updated and it's working with all versions of the roms (Confirmed by users).
Bin4ry's rooting tool has been updated, chances are it's more friendly user and won't throw any errors, up to you to try it out.
Just as a side note, the screenshots below are just for reference, they are not the same drivers/devices, they are only meant for you to know where to click.
Step 1: Download Tool Package (this is an old package, the drivers in the package works but you NEED TO ALSO DOWNLOAD Cydia's Impactor (Link to home page in case you are interested in reading a bit) and Googles ADB Drivers with a little modification in the ini file so it installs the driver for our HP Slate 7 tablet). If your Slate 7 model is 2800, you have to also download Moborobo that will find and install the drivers for you. I've received messages from users who have had both good luck and no luck installing the drivers, this must be dependant on your operative system and administrative rights, I did all this steps on a Windows 8 64bits machine with administrative privileges.
Download latest Cydia's impactor tool from the link above. The one in the package won't help you if you are trying to root v9 and above.
Step 2: Unzip the package anywhere you like, meanwhile go to your tablet and set it to USB Debugging.
{
"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"
}
YOU MUST SET IT ON USB DEBUGGING MODE, else nothing that you try will work.
Step 3 OPTIONAL: Just in case if your computer doesnt realize there is a device connected you need to copy the file in "\.android\adb_usb.ini" over to your user path "%USERPROFILE%\.android\" and reboot the computer (Just in case it wont recognize a device as connected).
Step 4: Now open the computers Device Manager and you will see something similar to this picture
Step 5: Right click the HP Device and choose to update driver, search for drivers in the computer (2nd option), then "let me pick from a list of device" as follows:
Step 6: Next click in "have disk" and navigate to where you unpacked the file downloaded earlier and choose the ini file.
Pictures for reference only.
Step 7:All you have left is open Cydia's Impactor tool, you will see a small window with a default command on screen which is the following:
Code:
# drop SuperSU su to /system/xbin/su
Just click Start next to it aaaaand you are done!
(PS: If this worked you are done, skip Step 7B. If you were unable to root your device try Step 7B)
Step 7B (ONLY IF Cydia's tool did not work): Warning: I've received messages from some users that this exploit has left them on bootloops, this method is tested on the 4600 model, if you have another and it works please do post your results, if you have problems all you have to do is download your model ROM from HP support and boot it through your microSD card to restore factory settings, also check in Bin4ry's thread for information if it is your case, if you find another method please do let us know . DO THIS ONLY IF STEP 7 FAILED, you will have to download the following rooting tool from Bin4ry's XDA thread, execute "RunMe.bat" and use method 1 and follow the on-screen instructions (This method will reboot your tablet 3 times if I remember correctly, after 2 reboots it will be stuck in a black screen for a couple of minutes (or more, it took me around 10 minutes) this is as it pushes the files for superuser, don't panic).
You can check your build version as it's shown in the following picture.
Just open an app like Titanium Backup which needs root to see if it worked.
This method is simple plus you don't have to download anything chinese or unnecesary software into your computer, the tutorial is really long because I tried to be as detailed as posible but in the end you shouldnt take more than 5 minutes (The downloads might take a bit longer though for the SDK), I would take screenshots of the process but my computer runs on a Spanish version of Windows (The same reason why you might see things with different names I was just trying to guess the device manager label part).
If you have any question feel free to ask (of course... as long as it hasn't been asked again and again in the thread ) and if it worked for you a thanks would be awesome so more users will try
PS: My Slate 7 model is the 4600 but it should work with others slates and for that matters, with any tablet as long as the adb driver is recognized.
PS2: If you could upload the package into a new mirror that might help more people.
PS3: Updated to March 16th 2014.
PS4: I just realized the screenshots facilitated by another user have been deleted, will try to find new ones.
PS5: If this helped you, please do thank, this way more users will benefit from it.

Universal Root
Ok people, I've used pretty much the same method to unlock 2 different tablets, if you see my other guide with rooting MSI Windpad 71 it's almost the same thing.
Once you get ADB running all you have to do is run Cydia's impactor and you are good to go.
If this helped anyone please tell your experience and with which devices you have tried this.

It's working guys!
It works perfectly, even better.
Also does anybody know how to make GT Racing Academy work on it?

My HP its Slate7 2800 your thread its for 4600 its diferent i think? I cant install the driver from device manger.

mastertempo said:
My HP its Slate7 2800 your thread its for 4600 its diferent i think? I cant install the driver from device manger.
Click to expand...
Click to collapse
Please do reply to the questions I asked you earlier, if you don't give out information I don't know what you are not doing right.

Dont wory man,i root my slate 7. How? I told you now. First i intall this: https://www.dropbox.com/s/0jg872o2armnntt/ADBDrivers.exe and strart it and install drivers. Then i run cydia impactor and everyting its done for few seconds. But i have one question now: is the cydia its universal for all android deviceses?

mastertempo said:
Dont wory man,i root my slate 7. How? I told you now. First i intall this: https://www.dropbox.com/s/0jg872o2armnntt/ADBDrivers.exe and strart it and install drivers. Then i run cydia impactor and everyting its done for few seconds. But i have one question now: is the cydia its universal for all android deviceses?
Click to expand...
Click to collapse
Yes, Cydia's main goal is to be a universal rooting tool.
I will check on the drivers you found, it could shorten the guide.
For everyone else I know it looks like a lot of steps, but it's really download software, modify a couple of ini files, install driver and run Cydia Will check on the drivers MasterTempo installed maybe I can make a package for a single small download.

Ok guide updated to v2.0 with single package download.
As long as the computer recognizes the ADB drivers for the phone/tablet Cydia's Impactor tool should root any device.

Worked on my slate. Thank you very much for your help
Sent from my GT-I9100 using XDA Premium 4 mobile app

what about unroot?
hi still i didnt root but i want to know how to unroot it : as my HP Slate is very new

OTA update
kibaruk said:
Ok guide updated to v2.0 with single package download.
As long as the computer recognizes the ADB drivers for the phone/tablet Cydia's Impactor tool should root any device.
Click to expand...
Click to collapse
My tablet is asking to update, if I do the OTA will I lose root?

wasim9283 said:
hi still i didnt root but i want to know how to unroot it : as my HP Slate is very new
Click to expand...
Click to collapse
No idea here mate sorry.
dalethefarmer said:
My tablet is asking to update, if I do the OTA will I lose root?
Click to expand...
Click to collapse
Nope, I've updated mine and it's still rooted.

kibaruk said:
No idea here mate sorry.
Nope, I've updated mine and it's still rooted.
Click to expand...
Click to collapse
I just updated mine and lost root...

dalethefarmer said:
I just updated mine and lost root...
Click to expand...
Click to collapse
Really?? That's odd... well you could always just re-run Cydia and go ahead with the push of files again and voila rooted again.

kibaruk said:
Really?? That's odd... well you could always just re-run Cydia and go ahead with the push of files again and voila rooted again.
Click to expand...
Click to collapse
Doesn't work. When I run Impactor I get an error: Signature bugs unavailable.
I tried updating impactor and I have the latest version.
I can factory reset and root again, but how do I stop the OTA update prompts from popping up?

dalethefarmer said:
Doesn't work. When I run Impactor I get an error: Signature bugs unavailable.
I tried updating impactor and I have the latest version.
I can factory reset and root again, but how do I stop the OTA update prompts from popping up?
Click to expand...
Click to collapse
Ok it seems the latest OTA which was a big one over 250mb changed something, I lost root access too, will have to see how to get this one rooted.
If anyone could confirm before trying to update to big OTA their versions? Mine is after OTA Android Version 4.1.1 compilation numbre v1.05.10_user.

It seems that for version 1.05.10 they have fixed the master key vulnerability of android.
"If you are having problems using Cydia Impactor (it crashes, doesn't work on your device, or simply doesn't make any sense) please join #android on irc.saurik.com and ask a question.
The Android "Master Key" vulnerability was found by Bluebox Security. For more information on how this bug works, I have done an overly-detailed article on the exploit technique.
If that bug is not available, Impactor will instead attempt to use a different signature verification bug. For more information on how that bug works, I have done another article on the new exploit.
It is possible that your device has been patched against both bugs; Impactor will inform you of this. If you'd like to check before spending time working with Impactor, you can try either the Bluebox Security Scanner or the alternative SRT AppScanner (which I have found to provide fewer false positives than Bluebox's tool).
Some devices are also patched against the second stage now used to get root; devices that are patched will show "link failed file exists". (This second stage was made possible due to help from @giantpune.)".

dalethefarmer said:
Doesn't work. When I run Impactor I get an error: Signature bugs unavailable.
I tried updating impactor and I have the latest version.
I can factory reset and root again, but how do I stop the OTA update prompts from popping up?
Click to expand...
Click to collapse
Ok I found a working root for latest 1.05.10 patch you can download here.
Once you download the tool you have to run the "RunMe.bat" file and follow the instructions, the method that worked was method 1 "New Standard-Root", it seems to also come with an unroot option for those who have asked for it, havent tried it though.
PS: Be careful when "press a key to continue now" because you can make it a double tap and miss a step, it won't brick the device but you will take longer.

Guide updated for latest OTA pushed 1.05.10_user that won't accept Cydia's vulnerability. It seems that the alternative rooting tool has the option to unroot for all of those who have asked for it, I havent tried it yet though.

mastertempo said:
My HP its Slate7 2800 your thread its for 4600 its diferent i think? I cant install the driver from device manger.
Click to expand...
Click to collapse
I've found out other HP Slate 7 2800 users are having problems with the drivers I put in the package, they have found Moroboro useful for that matter

Related

[HOW TO] Root Nextbook8 Premium (and install market app) [UPDATED 1-17-12]

PLEASE BE ADVISED: THE AUTHOR OF THIS POST NO LONGER PROVIDES SUPPORT FOR THIS THREAD. HOWEVER YOU ARE MORE THAN WELCOMED TO CONTINUE USING THE FILES AND METHODS AT YOUR OWN DISCRETION. GOOD LUCK!!
INTRO: For all those searching the internet trying to find answers as to how to gain root on your Nextbook8 Premium and also gain access to the wonderful android market from which we were greatly deprived (as is the case with many low-priced tablets these days), the wait is over thanks to a certain someone who goes by the name of DEVMONKEY. Of course I take absolutely NO CREDIT for this and only took the liberty to re-write it thus adding a little more detail to the process. Enjoy!!!
DISCLAIMER​***I HAVE NOT TESTED THIS PARTICULAR ROM WITH MY N8 WHEN I HAD IT BUT AS THE PROCEDURE TO FLASH IS STILL THE SAME ALL SHOULD GO WELL. HOWEVER, I AM NOT RESPONSIBLE FOR WHAT MAY OR MAY NOT HAPPEN IF YOU USE THIS AND DAMAGE YOUR DEVICE. PLEASE FOLLOW ALL STEPS CAREFULLY***​
[HOW TO] Root and install Market on your Nextbook8 Premium​
UPDATE: This is post has been updated with a new rom to replace old one. Method of flashing is still the same so no worries. All those who want to upgrade to this rom from the one I previously posted in this guide when I first wrote it can just repeat the steps over again with the new rom package.​
This rom is based on Samhain's release: SamDroid v1.13
Modifications (mostly GUI / cosmetic tweaks):
1.) cifs.ko / slow-work.ko / nls_utf8.ko are in /system/lib/modules and can be loaded using Mount Manager app from the market. This will let you mount CIFS/SMB shares to the device.
2.) Honeycomb-like launcher and updated GUI icons. (you can change it to any Launcher you want)
A couple of things to note once you have installed the rom:
- It starts up in Italian, so open Android settings "Impostazioni" and go to the "Lingua e tastiera" setting, and change the "Seleziona lingua" to your preffered language.
- I've put a few wallpapers in /system/media that you can set full screen by going into Live Wallpapers and using the "Multipicture Live Wallpaper" set them to the screen.
- There are a few things (widgets) on the homescreen that don't work after initial boot, just remove them and add back whatever you want to the homescreen.
- Sleep of death issues seem to be fixed, and the camera works (Camera app works, but Skype and Fring don't work yet...).
- You can also grab Adobe Flash 11 from the market and it'll work correctly.
- This release boots MUCH faster, and is even more responsive than before.
- There is a cell standby issue that drains the battery more in theory so if you feel like that is happening with you just delete the Phone.apk and TelephonyProvider.apk from /system/app. You can use ADB or you can use Root Explorer to do so. You will likely have to force a reboot because you'll start getting repetitive force closes once you do so, but it won't hurt anything. Once you reboot, all is well.
VERY IMPORTANT: After installing custom roms that also flash a custom recovery your N8 may reboot into the custom recovery. If this happens hit reboot system and only reboot system.
​Download new rom from HERE and extract (using winRAR preferably) to your desktop or anywhere you choose. Location doesn't really matter for this guide to work.
NOTE: If you have anything you care about (like apps, notes etc.) on your N8 make sure you back it up now.
Step 1: Turn your N8 off.
Step 2: Press both Volume buttons down and plug the USB cord into the N8.
NOTE: On your screen you should see a bubble pop up in the lower-right corner saying "Installing drivers". Most likely it will say it can't find the drivers. This is normal. Continue following the steps to install the missing drivers.
Step 3: Open the Device manager by typing mmc devmgmt.msc into your "Run" box on XP or search box in start menu on Windows 7 and hitting enter (you can also find Device Manager in your Control Panel options in Windows 7).
Step 4: With your N8 still in an off state and plugged in via USB you should see a yellow exclamation symbol somewhere next to "Unknown Device" in the list of devices in the Device Manager. Right click on it and select "Update driver software".
Step 5: Now it will prompt you to choose how you want to search for it. Select "Browse my computer for driver software" and it will bring up a window for you to navigate manually to the driver location which is in the "drivers" sub-folder in the NEXTBOOK8ROOT folder. Select which ever system you have (32bit or 64bit) and then hit "OK". You might go thru one or two prompts before it actually installs. Just "OK" everything and you should be fine.
Step 6: Once the drivers are installed you are ready to flash. Go into the root of the NEXTBOOK8ROOT folder and select RK29update.exe (right-click for Win7 users and Run as Admin).
Step 7: Now you should be at the interface of the program and at the bottom in bold words it should say "FOUND RKAndroid rock usb" (if it doesn't then it mean the drivers probably weren't installed correctly). This part is VERY IMPORTANT!! Make sure all of the boxes on the left are checked (should look like the pic below). The one at top is the one usually missing a check and would need to be checked by you.
{
"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"
}
Step 8: Once all boxes on the left are checked you are going to click on "EraseIDB" at the bottom and let it complete. Once that finishes click on "Run" and you will see a series of commands running in the right window pane (see pics below). Give it some time as it will probably take a few minutes. When it's done it should look like the second pic below.
Once the process is finished your NEXTBOOK should reboot into the recovery and reflash the OS. Congratulations!!! You now have an affordable rooted tablet with access to the Android Market!!
OTHER ROMS YOU CAN FLASH INSTEAD OF THE ONE IN THE ABOVE GUIDE:
Pisteone - [SDK 2.1] EXT4 Bluetooth 3G Root [Basic FW 1.0.21] ICS Style - LINK
Fintadroid - [FULL ROOT & EXT4] [BT & 3G] [FW.1.0.21 PRESTIGE] - LINK
ALL ROMS FOR NEXTBOOK8 - LINK (Be very careful and read before you flash)
Thanks! worked great.
I signed up, so i can say thank you. this worked perfectly.. i was skeptical and scared i'd ruin this tablet, as i got it as a gift, and was obviously disappointed to see no market on it, but this worked. thank you.
How about Nextbook Premium 7?
Thank you!
This worked great, I was able to get the android market installed and working.
Android version?
What version of Android does this install?
Cheers, Greg.
It's work, your are wonderful,thank you Sunnyboy167
Great job! Good to have root and Market working. But anyone else get FC when opening Camera app?
Perfect! I have rooted many Android devices and this is one of the easiest ones. Just read the directions carefully and you'll do fine.
Hopefully someone will release an ICS update for this device soon..after using my Galaxy Nexus, Gingerbread seems so...obsolete.
I'm glad you enjoyed this info just as much as i did
To everyone YOU ARE WELCOME but please....the best way to thank me is by hitting the thank button at the bottom right of my post. Thanks!
@xxProphecyxx - here is a link for the nextbook7 http://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/ I don't see any root method listed on the site but im sure there is one out there if you want to root it too. Or you can even take a chance if youre brave and use a one click root based on the android version you have.
@ghi07 - All this method does is re-install the OS (which is Gingerbread to answer your question) with market and superuser.
@dalerious - I'm sorry but I don't have a Nextbook anymore but if I did I would definitely try my best to help you. Try doing the entire process over and see if that works. Good luck!
THANK YOU!!!!
I was about to throw this tablet out the window!!! Followed the instructions and it works perfectly!!!! Thanks SO SO much!!!
Thanks to you I had a very Merry Christmas haha thank button has been pushed repeatedly!
Hi Sunnyboy,
Just want to say a big thank you for the detail post. I was about to give up on on this tablet when I came across your post.
Chris
help help!!!
hi sunny boy,
i just got my nextbook8 yesterday... come across this website and trying to root my nextbook last night at home...
I encounter this problem...when i plug in my nextbook into the PC USB ..it turn on from the off mode. and the pc started to scan the driver and it actually install successfully. I am running on win7. after that i cant install the driver required.. can anyone help me out here cos i try to run exe. file. it cant root my nextbook... i am helpless now...
I am also having problem with the camera. I'll have this error:
The application Camera (process com.android.camera) has stopped unexpectedly. Please try again.
HELP HELP HELP...not able to on the device after updated the driver....PC shows device found after plug in USB, which shows the device is working but just cannot on it.. a total IT dummy and not sure what's going on..someone said the ROM is damaged which cause this.....any way to recover the tablet..i just bought it for less than a week. HELP HELP HELP!!!!!! (tried reset but still no response)
Sunnyboy167 said:
To everyone YOU ARE WELCOME but please....the best way to thank me is by hitting the thank button at the bottom right of my post. Thanks!
@xxProphecyxx - here is a link for the nextbook7 http://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/ I don't see any root method listed on the site but im sure there is one out there if you want to root it too. Or you can even take a chance if youre brave and use a one click root based on the android version you have.
@ghi07 - All this method does is re-install the OS (which is Gingerbread to answer your question) with market and superuser.
@dalerious - I'm sorry but I don't have a Nextbook anymore but if I did I would definitely try my best to help you. Try doing the entire process over and see if that works. Good luck!
Click to expand...
Click to collapse
I have already been to this website and successfully added the market to my Next7. I do want to root it and flash a custom ROM, but I have not found anything useful. Thanks though.
Rooted fine, thx a mil. Installed GOLAUNCHER EX and the icons were too big. Dl'd LCD resolution from market and decreased res from 160 to 140. To apply changes app reboots tablet. When it came back up, nextbook stuck on launch screen and I can't even turn it off!! This was my gf's xmas present from her parents!!! Any suggestions??
eybarra2 said:
Rooted fine, thx a mil. Installed GOLAUNCHER EX and the icons were too big. Dl'd LCD resolution from market and decreased res from 160 to 140. To apply changes app reboots tablet. When it came back up, nextbook stuck on launch screen and I can't even turn it off!! This was my gf's xmas present from her parents!!! Any suggestions??
Click to expand...
Click to collapse
u can reboot the device by using a paperclip and press in the reset button.
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Thanks for the detailed guide Sunnyboy167~ Anyway devmonkey just release a newer mod which works better than the previous. Do check it out
hi all,
I rooted my new nextbook8 ...and it works just nice...
just need some help on whether possible to use my iphone as a modem for my nextbook? as i realized it cant detect my wifi network from my iphone. While my colleague 's motorola zoom works fine with my iphone...any solution on this?
Caduser from singapore...

[TOOL][NABIXD] NabiRootXD Root, Gapps, Recovery

NabiRootXD v2​
{
"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"
}
This is a tool for rooting, installing Gapps(Play Store, etc), and adding custom TWRP recovery on Nabi XD. It's written as a windows command line batch file, and is based off NabiLab I made for Nabi2.
It was an adventure to say the least. I include some of the hurdles for those that want to duplicate the root process or just to place my thoughts "on paper" because of the 100's of posts I read from those that posted detailed information and allowed me to gain useful insight in how I could adapt things for the XD, and explain in one swoop to the many PM's I have received about "when will we see root on the XD" why it took so freaking long. Those that just want the program can continue to the Overview section.
What started as an interesting avenue was TWRP using the Nabi2 kernel was booting the NabiXD to TWRP without video. I thought it possible to dd the recovery, or boot kernel. Unfortunately it was unable to recognize internal storage as a block device and that ended that. Like a few devices on Android 4.1.1 and above the standard once click program using Bin4ry's ADB restore exploit doesn't work. It doesn't work for a couple of reasons, when restoring fakebackup.ab in locks up writing the first file, and even if it did work placing ro.kernel.qemu=1 in local.prop doesn't work because Jelly Bean doesn't parse any property files to set the ownership of adb daemon. Searching the file system I found su2 in the xbin directory. This was promising as it is the su program but renamed, also unfortunate was its permissions had no setuid bit set and while it was executable it would not change uid to 0. I then foolishly went down the path of nvflash(forced recovery). I attempted a few different avenues here to try and possibly get the SBK to unlock nvflash, that proved uneventful, especially without root access. I tried extracting what "could" be the key from the Nabi2 it hope it was reused. That lead no where, it would be awesome to have access to it for many other reasons but it turned out to be an exercise in learning but ultimately a waste of time. Then on to other Android exploits... Tried Samba, debugfs, and vfat exploit. All of those are either patched or I'm not skilled enough. I finally returned to looking at the ADB restore exploit.
The "tabletS" exploitation showed promise as it takes the avenue of installing /dev/sh vs ro.kernel. A side effect of the failed ADB restore bug was leaving a directory with full permissions. Bads3ctor had an interesting fakebackup.ab that was more reliable at making a directory or file that you simlinked have full permissions. Now you can step through the tabletS script more effectively where you couldn't before by manually setting permissions for files/directories you need by doing the restore for each file and directory you need. The script installs VPNfaker and backs up the /data/app directory, then creates a new app directory. This however will cause the NabiXD to rerun the initial kidsmode setup and breaks everything. You can dance around that by not rebooting, and VPN faker will still give you a Term app with system uid. From there you can't symlink the sysfs links properly to data/property but that can be worked around by moving and then removing files. Finally you can makedev /dev/sh and run su from /data/local/tmp. The end result is that the exploits and bugs found by others are adequate when strung together in the right order on the NabiXD just not the one click solutions provided on the forums, they needed some modifications and done by hand to figure out for the NabiXD
Here is a nice publication I found in my searches that is more layman terms for older root methods. http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf
Overview
Video Overview of NabiRootXD - a video tutorial of the use of NabiRootXD.
-Root the Nabi XD
-Install Gapps(Play Store, etc)
-Make a stock backup of unrooted device
-Install stock, or TWRP recovery
-NabiLab patching system to install updates to this program
Version 2
-Fixed scripting error causing early exit
-Added 7z for patching system
Download
Read the installation section below to determine which version you want.
File names:
NabiRootXD.zip 96MB (Version 2)
Download
Download Mirror
Installation
NEW INSTALLS
1) Download NabiRootXD
NabiRootXD.zip 96MB
2) Extract the zip files to a location of your choosing. Run the NabiRootXD.bat file.
Prerequisites
1) Script is for Windows
2) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
3) ADB and Fastboot driver. Most popular are the PDAnet drivers. You can get them here: PDAnet drivers
Usage
Obviously using this script on your NabiXD voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Root, Gapps, Recovery​
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps. This is Jelly Bean Gapps dated 10/11/2012 without Google Search. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
MENU 2 - Install Recoveries​
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.2.3
Installs TWRP 2.4.4.0. This is the latest at this time. It has a screen timeout, if the screen goes black touch the screen to wake the screen, it's not locked up.
Menu Option 2 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 3 - Patch NabiLab​
Menu Option 1 - Install Patch
For any updates to NabiRootXD this is where you can automatically load them. Basically you will download NabiPatchXD.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Credits - If you see these guys buy them a beer.
jzmtaylor - Original Nabi2 script that this is based off of.
Bin4ry, Bads3ctor, HEXcube, drjbliss - all the bugs/exploits needed to accomplish root
Dees_Troy - TWRP build tutorial
Eric Karz - TWRP Theming and rooting assistance
TeamWin - They are the guys that make TWRP possible
Weeee more Easter goodies haha.
thanks aicjofs
Sir can i use this tool for installing Gapps for unrooted Galaxy Tab 7.0+ (wifi)? bcoz i updated my tablet for Honeycomb to Ice creamsandwich (China Firmware), everything is fine except that i cant open google playstore...
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
srgsng25 said:
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
Click to expand...
Click to collapse
The gapps removes the problem in system/app/quicksearchbox.apk you can rename it toquicksearchbox.bak
only other way I can think of is some how playstore added it to data/app
rename com.google.android.googlequicksearchbox.apk to com.google.android.googlequicksearchbox.bak
hth
ps: thank the op he spent hours and hours to make this happen = sacrificed his free time
Thanks for the feedback.
Perhaps we should have used the 7/26/2012 gapps? http://goo.im/gapps/gapps-jb-20120726-signed.zip 10/11/2012 is suppose to be 4.1.1 backward compatible, but perhaps there are some bugs with it on XD. Flash over the top of the current one. It will leave behind /system/app/thinkfree.apk, /system/app/microbes.apk and /system/lib/libmicrobes_jni.so, which you could remove manually. Wipe caches.
How about GPS stuff? Is that working?
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Eric Karz said:
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Click to expand...
Click to collapse
Do we know that the GPS works at all?
aicjofs said:
Do we know that the GPS works at all?
Click to expand...
Click to collapse
with gapps installed it doesn't seem to work .
maybe we are going to need a edited gapps ?
I'm just going to remove Google Search for now. That is highly annoying, I was messing around with ways to fix it, and got it to open in apps when you press the settings button, I was previously only getting it when pressing back button.. I updated the downloads. Until we figure out the fix, it's just too troublesome.
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
srgsng25 said:
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
Click to expand...
Click to collapse
I don't know if there is a hidden proxy. I'm not sure of your question. You could try going to settings-wifi. Long press the name of the network and a pop up will come up. Modify network, show advanced options. There is the proxy and DNS, for DNS you have to be static. I think there is 4.4.4.4 in there by default, plus what your router gives out.
If you are talking about something more underground I think you could use a getprop in adb shell or term.apk. I know I have seen stuff in there for DNS, something like dhcp.wlan0.dns there is stuff in there about "change" too. Should be able to set if you "su" and do a setprop. That would only be good until reboot, but could help you trouble shoot. I think it's set here /system/etc/dhcpcd/dhcpcd-hooks/20-dns.conf, maybe not in Jellybean. Anyway those are places to look if it's more then in settings that you are looking for.
ok it seems that this might be a work around to the quick search problem
edit the buildprop and change
ro.sf.lcd_density=160
to
ro.sf.lcd_density=145
I tried 149,150,59 and 120
120 does seem to fix it also but the screen makes every thing look smaller and some may not like that .(I do)
also I had to install BusyBox in order to get a few things to work including
build prop Editor by Nathan Campos (this tool seems to be a good test app to see if you have proper permissions)
note that the swipe screen will be a bit smaller under 160
maybe some one can use this info to edit quick search box we wouldn't have to change anything?
i am trying to get this tablet to use my network opendns settings and web filters
Can someone direct me to where I can get a Vista MTP driver for the Navi XD? I installed PdaNet as instructed but the tool wont connect, and I have a yellow exclamation mark by MTP Device. Can't seem to find anything else online.
EDIT: After rebooting a few times, then disabling my firewall, the tool connected. Thanks for the awesome tool.
Looks like an OTA was released for the Nabi XD today that bumbs the Nabi XD up to version 1.3.5. I tried doing the stock recovery option but the NabiRootXD app just closes out after selecting it. I looked into the NabiRootXD.bat file and I noticed on line 483 that it says to "GOTO Install_4" which doesn't seem to exist. I believe it should actually say "GOTO Install_2".
After making this change I was able to restore to the stock recovery to perform the OTA.
Now once I tried to install the OTA it appeared to atart the installs and then fails with the dead android symbol about a third of the way through. No idea what the problem is now so I'll just wait for others to try this and see what their results are.
yup getting the dead droid
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
OTA procedure
srgsng25 said:
yup getting the dead droid [
BOOT into TWRP and perform and system restore to pre-root image
reboot
download and install the OTA
reapply root and gapps
Click to expand...
Click to collapse
aicjofs said:
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
Click to expand...
Click to collapse
Thanks for the update aicjofs! I'll test this out shortly and let you know how everything goes.

[HOWTO][ROOT] POV Protab 3XXL: upgrading, rooting & saving battery guide

{
"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"
}
So I recently bought a Protab 3XXL from vendor Point of View, and I noticed there wasn't much information to find on the internet for this tablet. So I had to figure out by myself how to get things done, and as an android beginner, that wasn't very easy. That's why I wanna create this guide for all you people who bought the same tablet and want to do the following things with it:
1. Upgrade to new firmware release
2. Root the tablet so you can uninstall bloatware and install some advanced apps
3. Save battery, make the tablet go faster and smoother.
This guide will probably work on other RK3066 devices as well. I'm in no way responsible if you brick your device by not following every exact step!
1. Upgrade the tablet to new firmware release
When I initially bought the tablet, the firmware that was installed was buggy as hell, so the first thing I did was install the new updated firmware from the Point of View download site. This made my tablet go a bit faster and save a bit more battery life. The manual on the site though doesn't give a great explanation on how to install new firmware. Here's how to do it easily:
Beware: upgrading your tablet will result in loosing all your data! Make sure you took backups before continuing! Also, make sure you got over 50% of battery life so the tablet doesn't die in the middle of the upgrading process.
Go to http://ow.ly/lSuza and download the latest firmware release (get the one with the latest date in the filename, do not install v1.1 as wifi doesn't work on that one, don't know why) and extract it.
For upgrading your tablet to a new release, you need your tablet to boot into flash mode. This is done by switching off your tablet, wait a few seconds, press the VOLUME UP button and (while still pressing that button) connecting your tablet to your pc. Windows will tell you it failed to install the drivers as none were found, that's because you have to manually point windows where to find the drivers. To install the drivers, follow the steps written in the manual (page 2-6) found on the same site as the firmware update.
Open up rkbatchtool.exe which is in the extracted folder from step 1. If all went well, you should see a green rectangle which means your tablet is correctly connected in flash mode. If this rectangle is pink or no color at all, connect your tablet again holding the volume up button.
Once you got the green light on rkbatchtool.exe, you're good to go and you can follow the steps written in the manual!
I tested this procedure on Windows 7, but I guess it should be about the same on any other Windows version. Just use the appropriate drivers as described in the manual That should be about it, if you have any further questions, feel free to ask!
2. Rooting the tablet
Rooting the tablet is even easier than upgrading it! Here's how to do it:
Go to www.moborobo.com. Download and install moborobo as this app will automatically search for the right drivers (other ones than the ones used to upgrade the device) when you connnect your tablet to your pc.
Make sure you got USB debugging enabled on your tablet (settings -> developers options -> usb debugging)
Open up Moborobo, connect your tablet the normal way (so without pushing the volume button) and let moborobo do the rest. If Moborobo doesn't do anything when connecting the device, click on 'refresh devices'. Installing the drivers may take a long time so be patiently (it took about 15 minutes on my laptop).
When the correct drivers are installed, download the tool to root your device from here: http://ow.ly/lSZtT
Don't worry, it's malware free and safe
Extract the zip and fire up SuperOneClick.exe.
Click on 'root'. Everytime a dialog comes up, press 'yes' or 'ok' a few times untill it says your device is rooted.
Disconnect your tablet and check if superuser is installed, that's it
3. Some battery advice
All Android tablets last about a day and have to be plugged in by the evening, and the Protab is no exception for that! These are some tips to make your battery last longer (most tips are for rooted devices, so make sure you root your tablet first!)
Greenify is a great app to save some battery. Watch what it does and how to use it over here: http://www.youtube.com/watch?v=fW81YJME69U. This saved my battery a lot!Download it in the playstore!
Android tablets still have some leftovers from their sibling phones, and that's causing TONS of battery drain. To get rid of the phone functions and a better explanation head over to this guide (very easy to follow): http://ow.ly/lT0ZV
There are a bunch of better home screen launchers out there which are less battery-consuming than the stock android launcher (which the Protab has). My advice is Smart Launcher (or the pro version). This launcher is really smooth, fast and has a clean minimalistic look! Get it at the Playstore: http://ow.ly/lT1yX
Rom Toolbox by jrummy is a great app to execute some root tasks like uninstalling bloatware (software installed by Point of View like their useless keyboard). Head over to the Playstore to download it! Beware of what you're uninstalling, if you uninstall core android apps, it could mess up your system! If this happened, flash your device again as explained in the beginning of this thread.
I use my tablet a lot for reading pdf-files for school. As most pdf-readers have a white background, this drains a lot of battery (the lighter the colors on your screen, the more battery it drains). Moon Reader has an option to read pdf's in night mode (turns the background dark and the words white). This saves a lot of battery and is way easier to read! Head over to the playstore to download it.
As I already said in my previous tip: white colors drain a lot of battery. Therefore, use a dark wallpaper on your home screen!
Always use the lightest apps possible for a task. For example: Chrome browser for Android is a very heavy app which can be perfectly substituted by Boat Browser Mini (a lightweight browser that works blazingly fast). Try and google 'lightweight ........... for android' to see what the best alternatives for a heavy app are!
If someone has other tips for conserving some battery life, be sure to write it in the comments, I'll include it in this list!
If anyone has a better way of solving things or has anything to add to this guide, feel free to let me know
some custom rom fot this tablet POV Protab 3XXL?
costyprj said:
some custom rom fot this tablet POV Protab 3XXL?
Click to expand...
Click to collapse
Searched everywhere, but couldn't find any specifically for this tablet. I found a site which stocks many custom roms for the same chip this tablet has (Rockchip RK3066), didn't test any though so I really don't know if they would work:
Code:
http://www.rockchipfirmware.com/firmware-downloads
If there would be enough demand, I could try and make one myself
Hello,
my mother owns a ProTab 3 XXL. Since yesterday the tablet is not starting any more. I tried the reset button and several combinations with the front buttons.
i also checked the voltages:
- charger: 5,2V
- battery when charger disconnected: 4,3V
- battery when charger connected: 4,3V
is there something wrong? How can i fix the tablet?
thank you very much,
machinE
Hi,
I need backup/dump for protab 3 xxl, v1.1 (I think any v1.x will do). It has cwm installed already, but user did not backup official rom before changing roms, so now its bootlooping, and no way to flash anything on it. I think last resort is restoring official rom dump. Or maybe some other ROMs if someone can provide dump of it. If size is problem, PM me, I can provide way to upload big files. Thanks in advance!!
johhnycash said:
Hi,
I need backup/dump for protab 3 xxl, v1.1 (I think any v1.x will do). It has cwm installed already, but user did not backup official rom before changing roms, so now its bootlooping, and no way to flash anything on it. I think last resort is restoring official rom dump. Or maybe some other ROMs if someone can provide dump of it. If size is problem, PM me, I can provide way to upload big files. Thanks in advance!!
Click to expand...
Click to collapse
Just after install CWM, I'll make backup and post it here.
Korny(CzE) said:
Just after install CWM, I'll make backup and post it here.
Click to expand...
Click to collapse
Thanks a million, you are life saver!!! :good:
I have v1.0 did you try this?
Korny(CzE) said:
I have v1.0 did you try this?
Click to expand...
Click to collapse
I have, it does not work since flash tool needs working tablet. This one cant even boot. Only cwm works...
johhnycash said:
I have, it does not work since flash tool needs working tablet. This one cant even boot. Only cwm works...
Click to expand...
Click to collapse
It's not quite as easy as I expected. So far I failed to flash CWM. Update are fail. What steps are you / user you used?
Korny(CzE) said:
It's not quite as easy as I expected. So far I failed to flash CWM. Update are fail. What steps are you / user you used?
Click to expand...
Click to collapse
Friend doesnt remember, but I believe he used rkflashtool. Here are listed all possible ways to do it : http://androtab.info/clockworkmod/rockchip/install/
Good luck :good:
Ok, finally I was flashed it via root shell. Its backing up right now. After finish, i will upload it somehwere and post link here.
There is.
Korny(CzE) said:
There is.
Click to expand...
Click to collapse
Thank you very much. Downloaded already but have trouble entering cwm. What is correct procedure to enter cwm? Releasing power button and pressing and holding volume up and down when point of view logo appears? I tried almost every combination of keys and no way to enter it. Could be cwm got deleted when I tried to install some rk3066 rom for archos tablet. I dont believe it, but that would be logical explanation as to why I cannot enter it.
Last hope will be trying maskrom mode, by shorting nand chip and hoping it shows up in rkflash tool.
I am not using button combo, coz I have app for reboot to recovery. I will try it.
Odesláno z mého GT-I9505 pomocí Tapatalk

Xiaomi QIN 1s Hacking Thread

Xiaomi QIN 1S Hacking Mega-Thread!
{
"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 decided to go ahead and buy a Xiaomi QIN 1s feature phone. Unlike other feature phones, it runs a version of Android. Since there doesn't seem to be any threads here on XDA, I thought I'd start one.
SPECS
I finally found a guide/tool over on 4pda that will let you install apks. I have translated the tool to English and have it attached. The original post of the tool is here
If you don't want to download the tool (which also helps with ADB) here are the steps to obtain root:
-- Install the driver on your PC
-- Dial: *#*#83781#*#* To Open the Engineering Menu
-- Find the section "Debug & Log" and enable "Allow Debug"
-- Open the Settings app
-- Find "about phone"
-- Click "Build number" multiple times until you see "You are now a Developer!"
-- Go to "Developer options" and then turn on USB Debugging
-- Connect your phone to your computer (MTP)
-- Using ADB, push the apk to the device
-- ???
-- Profit
You can use this method to install any applications, not just root the phone. Remember, however, we only have 256mb of RAM and a total of 512mb of storage. Definitely not for gaming and you will definitely want an SD Card. I can confirm QQ and WeChat work fine when installed.
Let's get this rooted!
Big shoutout to Frolkin who helped me get the original tool and gaguga for making the tool!
Reserved
NICE! Thank you so much for posting that code. I have been searching for this code but couldn't find anything until yesterday.
So far I've sideloaded spotify lite and it doesn't work that well. Get stuck on the playlist view and can't scroll further down beyond the top banner.
Google Maps Go doesn't work without chrome and I can't install chrome because there isn't enough space.
Since mocor5 is on kitkat 4.4.4, would the hack to allow system to write to SD Card work to enable additional space for app installation?
foureight84 said:
NICE! Thank you so much for posting that code. I have been searching for this code but couldn't find anything until yesterday.
So far I've sideloaded spotify lite and it doesn't work that well. Get stuck on the playlist view and can't scroll further down beyond the top banner.
Google Maps Go doesn't work without chrome and I can't install chrome because there isn't enough space.
Since mocor5 is on kitkat 4.4.4, would the hack to allow system to write to SD Card work to enable additional space for app installation?
Click to expand...
Click to collapse
It should. I don't see why not. It might be worth it to just root the Qin and install apks directly to the sd card. The spotify issue is most likely because the app doesn't support the dpad.
Qiangong2 said:
It should. I don't see why not. It might be worth it to just root the Qin and install apks directly to the sd card. The spotify issue is most likely because the app doesn't support the dpad.
Click to expand...
Click to collapse
Yep the spotify issue is 100% because of that. The mouse pointer works but on certain views like the playlist, the scroll doesn't register. I wish the next version would add a a touch feature. Even if it's the same screen size, I think that would be a perfect device.
I have been looking for a replacement and get away from bulky and constantly connected smartphones without losing some of the nicer features like streaming music and using maps when I get lost. The hotspot feature makes this phone much more compelling to use too.
ROOT/ ROM download
Qiangong2 said:
Xiaomi QIN 1S Hacking Mega-Thread!
I decided to go ahead and buy a Xiaomi QIN 1s feature phone. Unlike other feature phones, it runs a version of Android. Since there doesn't seem to be any threads here on XDA, I thought I'd start one.
SPECS
After seeing vague rumors of it being possible to root the QIN 1s, I finally found a guide/tool over on 4pda. I have translated the tool to English and have it attached. The original post of the tool is here
If you don't want to download the tool (which also helps with ADB) here are the steps to obtain root:
-- Install the driver on your PC
-- Dial: *#*#83781#*#* To Open the Engineering Menu
-- Find the section "Debug & Log" and enable "Allow Debug"
-- Open the Settings app
-- Find "about phone"
-- Click "Build number" multiple times until you see "You are now a Developer!"
-- Go to "Developer options" and then turn on USB Debugging
-- Connect your phone to your computer (MTP)
-- Using ADB, push either iroot or kingroot apk to your device
-- ???
-- Profit
You can use this method to install any applications, not just root the phone. Remember, however, we only have 256mb of RAM and a total of 512mb of storage. Definitely not for gaming and you will definitely want an SD Card. I can confirm QQ and WeChat work fine when installed.
Let's see how far we can crack this phone open!
Big shoutout to Frolkin who helped me get the original tool and gaguga for making the tool!
Click to expand...
Click to collapse
Hi This app doesn't work to root that Xiaomi and do you know how to download ROM without ROOT?
danio40 said:
Hi This app doesn't work to root that Xiaomi and do you know how to download ROM without ROOT?
Click to expand...
Click to collapse
I don't know how to download an unrooted rom, sorry. Also, I put in the post that you need to load either Kingroot or iroot. However, I have uploaded iroot to the post. please check.
EDIT: hmm... I guess you're right. My new 1s comes in about two weeks, and then I'll be able to test it more extensively. It's possible that it may give you temp root after running it and you can manually install supersu from there
foureight84 said:
Yep the spotify issue is 100% because of that. The mouse pointer works but on certain views like the playlist, the scroll doesn't register. I wish the next version would add a a touch feature. Even if it's the same screen size, I think that would be a perfect device.
I have been looking for a replacement and get away from bulky and constantly connected smartphones without losing some of the nicer features like streaming music and using maps when I get lost. The hotspot feature makes this phone much more compelling to use too.
Click to expand...
Click to collapse
Yeah! that's what interested me in it. I don't necessarily need a touch screen, but a 5mp camera on the back would be nice for the few times I do take photos.
Qiangong2 said:
I don't know how to download an unrooted rom, sorry. Also, I put in the post that you need to load either Kingroot or iroot. However, I have uploaded iroot to the post. please check.
EDIT: hmm... I guess you're right. My new 1s comes in about two weeks, and then I'll be able to test it more extensively. It's possible that it may give you temp root after running it and you can manually install supersu from there
Click to expand...
Click to collapse
I'm trying both Iroot and kingroot nothing still unrooted.
Also I tried to use a box miracle SPD to download but no luck it stuck on loading FDL and freeze.
danio40 said:
I'm trying both Iroot and kingroot nothing still unrooted.
Also I tried to use a box miracle SPD to download but no luck it stuck on loading FDL and freeze.
Click to expand...
Click to collapse
I've updated the thread with the fact that we have not gotten root yet. I left the tool there because it can help people install apks.
Time to find a root method
danio40 said:
I'm trying both Iroot and kingroot nothing still unrooted.
Also I tried to use a box miracle SPD to download but no luck it stuck on loading FDL and freeze.
Click to expand...
Click to collapse
Have you tried using a PC-based root solution such as shuame pc or kingo pc?
Qiangong2 said:
I've updated the thread with the fact that we have not gotten root yet. I left the tool there because it can help people install apks.
Time to find a root method
Click to expand...
Click to collapse
yes I'm stuck with it. I want to download a ROM in a PAC file. I think that bootloader is locked when I looked via xiaomi adb tool.
danio40 said:
yes I'm stuck with it. I want to download a ROM in a PAC file. I think that bootloader is locked when I looked via xiaomi adb tool.
Click to expand...
Click to collapse
On 4pda they claim it isn't locked.
If you do:
adb reboot bootloader
fastboot oem get-var
fastboot oem unlock
Supposedly it unlocks the device
Qiangong2 said:
On 4pda they claim it isn't locked.
If you do:
adb reboot bootloader
fastboot oem get-var
fastboot oem unlock
Supposedly it unlocks the device
Click to expand...
Click to collapse
In fastboot mode when typed fastboot oem get-var <waiting for any device>
Doesn't do anyrhing
danio40 said:
In fastboot mode when typed fastboot oem get-var <waiting for any device>
Doesn't do anyrhing
Click to expand...
Click to collapse
What does fastboot devices show? Do you have all the drivers installed? Does it show up in the upgrade tool?
Qiangong2 said:
What does fastboot devices show? Do you have all the drivers installed? Does it show up in the upgrade tool?
Click to expand...
Click to collapse
I'm trying now kingoRoot PC version. I useed xiaomi ADB to see if the bootloader is locked. It shows that is locked. I have got debugging ON. There is a big issue with a space on that phone. kingroot installed only and it comes up as no memory. Maybe that is the case why is not rooting so I'm trying now after RESET the phone to use PC version - maybe will work.
After that i'm going to bed sorry but we can play tomorrow anytime
---------- Post added at 03:53 AM ---------- Previous post was at 03:46 AM ----------
danio40 said:
I'm trying now kingoRoot PC version. I useed xiaomi ADB to see if the bootloader is locked. It shows that is locked. I have got debugging ON. There is a big issue with a space on that phone. kingroot installed only and it comes up as no memory. Maybe that is the case why is not rooting so I'm trying now after RESET the phone to use PC version - maybe will work.
After that i'm going to bed sorry but we can play tomorrow anytime
Click to expand...
Click to collapse
Also yes all drivers I think I have got installed. When it is fastboot mode it is just says that 2 words nothing else. No menu. I dont have upgrade tool.
danio40 said:
I'm trying now kingoRoot PC version. I useed xiaomi ADB to see if the bootloader is locked. It shows that is locked. I have got debugging ON. There is a big issue with a space on that phone. kingroot installed only and it comes up as no memory. Maybe that is the case why is not rooting so I'm trying now after RESET the phone to use PC version - maybe will work.
After that i'm going to bed sorry but we can play tomorrow anytime
---------- Post added at 03:53 AM ---------- Previous post was at 03:46 AM ----------
Also yes all drivers I think I have got installed. When it is fastboot mode it is just says that 2 words nothing else. No menu. I dont have upgrade tool.
Click to expand...
Click to collapse
Okay, keep me updated
Qiangong2 said:
Okay, keep me updated
Click to expand...
Click to collapse
KINGOROOT - root failed
danio40 said:
KINGOROOT - root failed
Click to expand...
Click to collapse
Shoot. Next step I guess, is see if it shows up when in fastboot mode.
On linux use lsusb
On windows open device manager
Do you see the Qin?
Qiangong2 said:
Shoot. Next step I guess, is see if it shows up when in fastboot mode.
On linux use lsusb
On windows open device manager
Do you see the Qin?
Click to expand...
Click to collapse
On windows manager Yes but only if you choose MTP then it shows as QIN 1s, Standard file manager.

Twrp 3.3.1. UmiDIGI Power 4G

TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​
New twrp 331-test 1 for this device is builded!
Now need period of tests...
http://www.mediafire.com/file/cnqw8d2qkjqtp6k/Twrp_331_test1_Umi_Power.rar/file
reserved 1
Reserved 2
TWRP Not Working for Me
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
I confirm the first part of this, same issue here... i'd like to flash a twrp for gsi purposes, but for now no luck
SeekerofLight.iz said:
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Root UMIDIGI Power with Magisk
mr A V said:
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Click to expand...
Click to collapse
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
Step 0 - Download the Attached Zip File Below
Google Drive Mirror
Mediafire Mirror
MEGA Mirror
Step 1 - Drivers
Install the MediaTek drivers by running "DriverInstaller.exe". These are the drivers that worked for me. But if you have issues with them in Step 5, Google "Mediatek MT65xx USB VCOM Drivers" (or some variation of that) and try some others you can find.
-----------------------------------
Step 2 - Install ADB Interface
Install the Android SDK (ADB Interface). To do this drop the platform-tools folder (from the Step 2 folder) into your C:\ directory. Press the windows start button and search for "Environment Variables" and click on "Edit environment variables" from the results. Under SYSTEM VARIABLES on the bottom (not User variables above it) click on the "Path" variable, and click edit. In the new window that appears, hit "Browse..." and click on the "platform-tools" folder that you placed in your C:\ directory.
All this does is allows you to easily input adb commands into command prompt with no issues. This will be used to verify that the device is appearing properly and issue commands in case of emergency.
{
"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"
}
-----------------------------------
Step 3 - Install Magisk
Copy the Magisk.apk to your phone and install it.
(This is where you can then copy the boot.img to your device and patch it via the Magisk app to create the "magisk_patched_boot.img" file, however I have included the already patched file in Step 6 for the UMIDIGI Power so you don't need to.)
Also, this is the Magisk v19.3 Beta, but you can install another version.
-----------------------------------
Step 4 - OEM Unlocking/USB Debugging Mode
On your phone, go to Settings >> System >> Developer Options. (If you haven't activated Developer Options yet, do that by going to About Phone >> Build number, and tap it a bunch of times, but I'm sure you already know this lol)
In Developer Options, turn on "OEM Unlocking" to unlock the bootloader, and USB Debugging.
-----------------------------------
Step 5 - Verify That Your Phone is Detected with ADB
Connect your phone to your PC. Make sure you click "Allow USB debugging" on your phone. Then open up Command Prompt. (Protip: Type "color a" and press Enter if you want to feel like a REAL HACKERMAN.) Now, type in "adb devices" and verify that your phone is detected by your computer. If it's detected, then that's perfect you can move on to Step 6. If not, then uh... you may have to try and find some other MediaTek drivers mentioned in Step 1.
-----------------------------------
Step 6 - Set up SP Flash Tool
Open up SP Flash Tool on your computer by running "flash_tool.exe" in the SP Flash Tool Folder. (If at any time it shows a "Processing" window for some reason, just close and reopen the program if it doesn't go away on its own.)
On the first line choose "MTK_AllInOne_DA.bin". And the third line "Authentication File" can be left blank.
On the second line where it shows "Scatter-loading File", hit "choose" and find the "MT6765_Android_scatter.txt" file in the Step 6 folder. It'll load up and show a bunch of green/white rows in the space below.
Now this looked intimidating to me at first, but it's actually quite simple. As far as I understand (and I could be wrong but), the scatter file just tells the program where to place certain files, like a map for the program to follow. The scatter file I provided is for the UMIDIGI Power. The only thing we'll worry about for now is the boot.img file (but in the future, this is where you could also install a TWRP recovery once we get one that is confirmed to work.)
So in the white/green list, scroll down to where it says "boot" in the "Name" column, and click on the blank area in the "Location" column. It will bring up a window where you can browse to the "magisk_patched_boot.img" that I provided.
-----------------------------------
Step 7 - The Big Huzzah (Rooting)
Power off your phone and make sure it's UNPLUGGED. On SP Flash Tool, click "Download". This prepares the program to begin flashing your phone as soon as it is connected. Grab your phone with one hand, and with your other hand plug in the USB cable (if you only have one hand, use your mouth I guess). Your screen should not turn on at all throughout this process, but if it's successful, you should see that the program begins to flash your device after a second or two. Now just wait until it reaches 100% and says "Download Ok" with a green checkmark. And you're pretty much done!
You can then boot up your phone and check the Magisk app, as well as download a root checker from the Play Store to confirm that your phone has root access! Have fun!
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
mr A V said:
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
Click to expand...
Click to collapse
No problem! Unfortunately I don't see many custom ROMs coming to this phone, considering it's not a very popular device. I'd guess our best bet is to hope that the UMIDIGI F1 gets some support, and that anything on there can hopefully be ported over to this phone, but even that device isn't very popular either. For me though, that's not a huge issue because I'm actually quite satisfied with the stock firmware it has on board. It's basically stock Android Pie, and I've been able to add all the extra goodies I want into the phone through Magisk Manager and EdXposed with very minor issues. Most notably Viper4Android to fix the slightly tinny speakers and pump up the overall headphone experience too, and Gravity Box for some extra minor software customization.
Overall, I'd say the biggest downside to this device is the limited camera capabilities, and its somewhat limited performance for heavier tasks like 3D games / game streaming. But other than that, this feels like a very premium device. :good:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
mr A V said:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
Click to expand...
Click to collapse
I definitely consider myself to be a major noob with the more advanced Android development stuff. I only know enough to find my way around the internet and flash compatible software, haha. I've never looked into creating ports myself, but it's certainly something I think might be worth learning, especially with the limited device support on these phones.
And yeah, in terms of performance I don't expect much out of a phone at this price point, but for all the essentials - music, 1080p YouTube, web browsing, and mid to light gaming, it's surprisingly great considering the price. I haven't had any issues with the memory as of yet, so I wouldn't be too concerned, although you're definitely right in that they probably source some pretty cheap parts for these kind of phones.
SeekerofLight.iz said:
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
"stubbed guide"
Click to expand...
Click to collapse
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------
ghost45 said:
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​
Click to expand...
Click to collapse
Can i ask you a guide on how were you able to boot it? i'm only getting a bootloop after flashing that from SPFlash
I will build one other version of recovery soon...
mg95tux said:
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
Click to expand...
Click to collapse
Glad to hear it worked for you!
Still nothing. Unfortunately I haven't had any luck with booting into TWRP since I last tried it. Hoping ghost45 will be able to help us out with that when he gets the chance.
Bootloop - Secureboot
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Andre_Filho said:
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Click to expand...
Click to collapse
remember to allow oem unlock from developer settings in stock rom, otherwise it will fail!
SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Andre_Filho said:
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Click to expand...
Click to collapse
The trick to getting Viper4Android to work is to make sure you have SELinux set to "PERMISSIVE" rather than "ENFORCING" on your phone. Here's a handy little app designed to automatically set it to permissive on boot!
https://forum.xda-developers.com/devdb/project/?id=1561#downloads
And for BusyBox, I was having issues too at first because I think with systemless root, BusyBox can only be installed in /sbin, which gets wiped after each boot. So I searched for "BusyBox" in the Magisk app and found a module called "BusyBox for Android NDK" which has worked perfectly for me.
One thing to note...
Sometimes SELinux doesn't always get changed automatically everytime you boot up. It's pretty consistent, but every once in awhile you may need to manually set it to permissive mode again if things don't seem to be working. But it's literally just pressing a single button, so not a big deal.
The other thing is with Viper itself- At times when I launch the app, the driver status says "abnormal" even after I've toggled SELinux to permissive. If you go into settings and toggle "compatibility mode" or "attach audio effects" on and then off that seems to refresh the driver status. Not sure why, but it works.
Let me know if you have any issues.
TWRP for UMIDIGI POWER
I ask for help in creating TWRP for UMIDIGI POWER firmaware ROM v1.5
Please make for this model TWRP
I am very grateful to you - I unlocked the phone and got the rights Root rights.
It remains only to create a TWRP for UMIDIGI POWER
At this forum, competent specialists and for other models everything is already done.
Maybe there is a website where you can make an order to create a TWRP?
Unfortunately, I do not know English and I do not know how to apply.
I would be very grateful and ready to test your work.

Categories

Resources