Related
Hi all
Background: I'm no stranger to modding devices in general but I'm not an expert in Android modding. Just a tinkerer.
I love my Nexus 10 but it's feeling a little unloved after my attempt to update it to 4.4 KitKat. Until recently I was running:
Android 4.3 (JWR66Y build)
Rooted using the Nexus Tool Kit
SuperSU
Storage encryption using the built-in cryptfs functionality
TWRP recovery
The device automatically downloaded the KOT49H (4.4.2) OTA update. I went to the XDA IRC channel on Freenode and asked in there if it'd be OK to let it install. They said yes, it'll be fine but I might need to re-root. I let it install. It soft-bricked it. All I got was the KitKat boot animation.
I went into Fastboot, wiped and flashed the KOT49H stock build to the device. I don't have root and the device is fresh as a daisy (apart from having TWRP recovery still).
What I wanted to know is why the device became bricked. Judging by the other / threads / I found in the forum there seems to be some disagreement as to the actual process and even possibility of installing the OTA delta updates.
Can someone clarify why the device became bricked and help with avoiding such issues in future? I have a freshly updated device and I'd like to know what steps I should take to avoid having to wipe the tablet each time I want an OS update.
Thank you in advance
New Years Eve
NYE was a bad time to post! Bump?
DijitalJB said:
NYE was a bad time to post! Bump?
Click to expand...
Click to collapse
OTA updates will not work if you have a custom recovery installed (TWRP). You could have pulled the OTA update zip out of cache and moved it to storage and used TWRP to "Install" it or download it yourself and install it with TWRP. It's odd that it was bricked because normally it will just fail and throw an error (has unexpected contents). I know that if it fails while installing the update with TWRP, it will tell you what file or app in the system caused the problem. An OTA update will normally only work if you have the stock recovery and nothing in the system has been modified. Basically, the update will check to see if anything has been modified that is going to be updated. A major update like from 4.3 to 4.4 everything pretty much gets updated. A minor update like from 4.4.1 to 4.4.2 not a lot got updated so you might get away with some files being modified. Also... if you flash everything in the factory image Except the userdata image you will not lose your settings and user apps. If you want to install the OTA with TWRP and have modified the system or kernel you can just flash the system.img or boot.img so that the OTA will work. Make sense?
Flashing system.img and boot.img only
wantabe said:
...if you flash everything in the factory image except the userdata image you will not lose your settings and user apps. If you want to install the OTA with TWRP and have modified the system or kernel you can just flash the system.img or boot.img so that the OTA will work....
Click to expand...
Click to collapse
Thank you wantabe. That does make sense, yes. I've found the section of the Nexus Root Toolkit that will allow me to flash the individual images, and I've dissected the build archive from Google and found where those .img files are, which is cool.
My only follow up question is: when I first boot will the system do any kind of checking/upgrading of the existing userdata to make sure it's compatible? Is this automatic? I ask because I recall the update process involving something like this when I went from 4.0 to 4.1 on my phone.
Thanks in advance
DijitalJB said:
Thank you wantabe. That does make sense, yes. I've found the section of the Nexus Root Toolkit that will allow me to flash the individual images, and I've dissected the build archive from Google and found where those .img files are, which is cool.
My only follow up question is: when I first boot will the system do any kind of checking/upgrading of the existing userdata to make sure it's compatible? Is this automatic? I ask because I recall the update process involving something like this when I went from 4.0 to 4.1 on my phone.
Thanks in advance
Click to expand...
Click to collapse
When you boot? No. When you update it will check the system not the userdata.
Hey Folks,
I am totally new to this but I want to put CM 12.1 on my SPG621. I have unlocked the bootloader so far and I was looking for hours for a step by step guide that is noob-safe.
There are many guides and tutorials that tell different things and it is very hard for me to get the essence of it.
What I understand is as follows:
- I have an unlocked bootloader (and lost my DRM Keys, good job)
- get root
- install custom recovery
- install CM 12.1
Is that the correct order? How do I do that in detail? I don't understand how to install a custom recovery without root and I don't understand how to get root.
I have downloaded Flashtool so far. I would be glad if I got any helpful advices. Thanks a lot!
These are what I did to have root and twrp:
1. Check what version you are on right now. If you are on 5.0.2, you can root it by using Kingroot 4.5 (here)
2. If not, you can download stock 5.0.2 from here and flash it via Flashtool; then you can install Kingroot 4.5 and get root
3. Turn on usb debugging and unlock the bootloader again as you have converted to stock
4. Install twrp - download from here
5. Download CM12.1 and Gapps and install via twrp here
Hope it helps!
Thanks for your quick answer.
I now obtained root access via Kingroot. I would like to install TWRP Recovery now. I downloaded it via PlayStore. I chose my device and tapped on Install Recovery.
It now asks me to confirm a partition /dev/block/platform/msm_sdcc.1/by-name/FOTAKernel else I would risk bricking the device. How can I make sure that this is the correct partition? I can't see this path in my file commander.
Cheers,
ArctiCMooN
Edit: Never mind, I didn't click on the link. I will install it with your link then and post the result here.
Mocha7 said:
These are what I did to have root and twrp:
1. Check what version you are on right now. If you are on 5.0.2, you can root it by using Kingroot 4.5 (here)
2. If not, you can download stock 5.0.2 from here and flash it via Flashtool; then you can install Kingroot 4.5 and get root
3. Turn on usb debugging and unlock the bootloader again as you have converted to stock
4. Install twrp - download from here
5. Download CM12.1 and Gapps and install via twrp here
Hope it helps!
Click to expand...
Click to collapse
I have a few problems now that I try installing the dual recovery.
Root Checker says I successfully have rooted my device. BUT: I cannot find the KingUser App anywhere.
When I try to install TWRP via this dual recovery method, it asks me if I want to use SuperSU or SuperUser method, but I don't have anyone of the, is that correct?
Did something go wrong?
ArctiCMooN said:
I have a few problems now that I try installing the dual recovery.
Root Checker says I successfully have rooted my device. BUT: I cannot find the KingUser App anywhere.
When I try to install TWRP via this dual recovery method, it asks me if I want to use SuperSU or SuperUser method, but I don't have anyone of the, is that correct?
Did something go wrong?
Click to expand...
Click to collapse
Look at this thread: http://forum.xda-developers.com/z3-tablet-compact/general/how-to-root-easy-t3115418
You'll have the answers of your questions.
It worked perfectly for me.
guizmogwai said:
Look at this thread: http://forum.xda-developers.com/z3-tablet-compact/general/how-to-root-easy-t3115418
You'll have the answers of your questions.
It worked perfectly for me.
Click to expand...
Click to collapse
Thanks a lot for the help.
I managed to get CM12.1 on my Sony Xperia Z3 Compact Tablet.
I basically did what Mocha7 told me, although I wasn't sure about KingRoot 4.5 (trustworthy or not?). I gave it a try, the first time it failed, the second time the root was successful.
I did not install SuperSU or SuperUser and directly continued with the installation of XZDualRecovery and chose SuperSU method in the Windows Command Terminal.
This worked perfectly and the tablet directly started into TWRP. From there I started the installation of CM 12.1.
After that, I did a factory reset of CM 12.1 to erase all data of the old system and reinstalled XZDualRecovery.
I downloaded the latest Gapps from CM Wiki and installed it via Recovery.
The system works fine and I am extremely happy that I got rid of Sony's Stock Android. There are some very small bugs in CM 12.1: Rebooting erases some shortcuts on the homescreen and the lowest brightness setting is still quite bright.
Thanks again for the help!
ArctiCMooN said:
Thanks a lot for the help.
I managed to get CM12.1 on my Sony Xperia Z3 Compact Tablet.
I basically did what Mocha7 told me, although I wasn't sure about KingRoot 4.5 (trustworthy or not?). I gave it a try, the first time it failed, the second time the root was successful.
I did not install SuperSU or SuperUser and directly continued with the installation of XZDualRecovery and chose SuperSU method in the Windows Command Terminal.
This worked perfectly and the tablet directly started into TWRP. From there I started the installation of CM 12.1.
After that, I did a factory reset of CM 12.1 to erase all data of the old system and reinstalled XZDualRecovery.
I downloaded the latest Gapps from CM Wiki and installed it via Recovery.
The system works fine and I am extremely happy that I got rid of Sony's Stock Android. There are some very small bugs in CM 12.1: Rebooting erases some shortcuts on the homescreen and the lowest brightness setting is still quite bright.
Thanks again for the help!
Click to expand...
Click to collapse
Sorry I was out of town for the labour day long weekend so I didn't see your replies.
So glad to hear that you nailed the CM 12.1! Enjoy!!:good::good:
Hi, Please report how is the condition of Cynogen mod 12.1, is it stable for daily use already?
wow, man! I read your post and think this is ME!! haha I just got my Z3 Tablet a few days ago and had the same struggle. I got it with 4.4.4 installed and jumped right to CM12.1. Also tried crDroid and like it actually much better^^ I got a big problem though. With these custom roms my camera would not focus! the back camera is useless. front is ok though. Have you anything like that??
Schuan said:
Hi, Please report how is the condition of Cynogen mod 12.1, is it stable for daily use already?
Click to expand...
Click to collapse
It works really well so far. No crashes or anything. very nice! :good:
Schuan said:
Hi, Please report how is the condition of Cynogen mod 12.1, is it stable for daily use already?
Click to expand...
Click to collapse
Hi, CM 12.1 is quite stable but has a few bugs.
Restarting the device deletes most of my homescreen shortcuts.
The adaptive brightness options seems a little bit buggy. It switches brightness way too fast and too often, is not smooth, so I turned that off.
Besides that, I did not experience any further bugs.
knauji said:
It works really well so far. No crashes or anything. very nice! :good:
Click to expand...
Click to collapse
Now there is a problem. I tried to update to a more recent nightly of CM 12.1. I did it via the settings menu and let everything happen.
Now I can't boot my device anymore nor can I boot into recovery. The device just tries to boot, shows the Sony symbol and then turns off and tries to boot again. So it is in a boot loop.
Can anybody help with this?
This happened to me a few times. Try to flash the recovery again and the flash the rom from there. If it works, good, if not....
It happened to last night when I tried the latest nightly. I could not do anything so I flashed the sony stock rom with flashtool. After that I could flash TWRP again. Not sure of any other way.
Yeah I had huge problems getting recovery on my device. I reinstalled stock 5.0.2, rooted it and tried to get the same dual recovery on it I used before, but it didn't work. So I downgraded to 4.4.4 and managed to get Custom Recovery on it and from there I managed to install CM 12.1 again. Now everything works fine, but my nerves need a rest now^^
glad it works. take a rest and enjoy haha
I have to wait some more or maybe even sell it because of the camera bug.... I don't like sony stock os ....
Since there seems to be no way of installing current (and future) patches from stock recovery when the device is rooted, it'd be good to know if someone has information about whether it's possible or not to develop a custom recovery. The old method using 5.02 droidboot won't work because the updates mess up the whole system if you use them. So since we have unlockable bootloaders in 5.1, could there be the possibility of compiling a permanent CWM?
since there seems no one to be working on it at the moment, i'll start a few tries myself and document the progress in this thread. Feel free to help or comment.
For now, i', stuck at unlocking the bootloader and still don't know why. "OEM unlock" was set in the developer options, rebooted to fastboot and tried "fastboot oem unlock". Results as attached. :\
I'll google a bit around and see if i can get it working....
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
He's asking about a recovery that can be installed to the recovery partition, not just tethered.
It's possible, but we'd need somebody to build one. I tried one a while back from the Zenfone 2, but it didn't want to boot.
jumpup said:
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
Click to expand...
Click to collapse
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
toxic_garden said:
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
Click to expand...
Click to collapse
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
@xBIGREDDx made some instructions on this. Let me find it.
http://forum.xda-developers.com/showpost.php?p=64391058&postcount=16
This is not straightforward, but you *can* get to tethered CWM and root your 5.1 system. I did exactly this.
jumpup said:
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
Click to expand...
Click to collapse
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
toxic_garden said:
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
Click to expand...
Click to collapse
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
jumpup said:
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
Click to expand...
Click to collapse
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
However, I have always used a multi-tiered backup system:
* Titanium Backup (FULL on Sunday, INCREMENTAL every other day)
* Online NAndroid Backup (One per week using CWM format)
Each app's backup data syncs to the home NAS and Dropbox once a week.
I thought I had the Stagefright fix already in place. That's why I wanted to compare build/version details with a device that has the fix installed.
jumpup said:
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
Click to expand...
Click to collapse
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
toxic_garden said:
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
Click to expand...
Click to collapse
D'oh. I should have remembered about the data encryption. Need more caffeine
If you need anything tested or confirmed in the field, I'd be glad to help.
Sent from my Venue 8 7840 using Tapatalk
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
jumpup said:
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
Click to expand...
Click to collapse
oops you're right. Didn't even notice.
First steps forward: it seems like it's not possible to unlock the bootloader with installed sf-patch. No matter which version of fastboot i tried, i always got "FAILED: (some text i can't remember)". After downgrading to 5.1 stock firmware, unlock was possible. So as i now at least have the possibility to boot another recovery, i'll try setting up the build env. The Recovery Builder from CWM seems to be out of order at the moment.
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
I now have the Stagefright patch installed. Used the 5.02 droidboot temporarily to engage tethered CWM and install SuperSU. Reflashed 5.10 droidboot and firmware before proceeding. All is well. As you mentioned, it makes for a mixed 5.1 boot system, but I simply cannot live without root.
Here are the new build/version details:
After taking your advice and flashing the sg droidboot, my IWFI version is in line. I'll see if any system issues occur.
Is anyone still working on the 7840? Would be nice to have TWRP or CWM
I've been poking around on my 7840 on and off for a few weeks now. I seem to have verified that, after unlocking the bootloader, you can modify the boot and recovery partitions to your heart's content. However, any time I rebuild the kernel myself, I end up back at the "Dell" screen, frozen. Any other files are free game.
Assuming that the kernel needs to be signed using some tool I haven't figured out yet, I'm going to see if I can get a version of CWM working w/ the stock kernel. I tried dumping the version from the tethered recovery onto the recovery.img, but running it results in a black screen. I'll keep poking around though.
I've been trying for days to get ubuntu touch on my Nexus 10, and nothing works. Finally posted on AskUbuntu, but it's not getting much attention. At this point I just want to know if what I am trying is even possible. Here is a copy-paste of the post:
askubuntu[dot]com/questions/796924/can-not-install-ubuntu-touch-on-nexus-10
I am having a lot of trouble installing Ubuntu onto my Nexus 10 (16gb wifi edition). I have followed the instructions here [1] and here[2]. No matter what I do it ends with the message 'this phone needs restoring from a pc or service center'. I have searched ask ubuntu and other forums and here is what I have tried to solve the problem. Installed android 4.4.4 stock, cyanogenmod 11, android 4.0 stock prior to flashing. I also formatted with
$ fastboot format cache
$ fastboot format userdata
as suggested here[3]. Nothing seems to work.
Other things to note, I am using ubuntu-device-flash on a virtual box machine running ubuntu 16.04, and it takes a long time for ubuntu-device-flash to push the last .tar.xz file to my tablet, somewhere in the range of 1 hour or more. Last night I let it run overnight because some on some forums the response to similar problems was "be patient" once you see the 'this phone needs restoring...' error. When I woke up the phone was in a boot loop and I had to re-flash stock 4.4.4.
I have successfully flashed ubuntu version 2 with the dual boot app in android, but I can't get it to update. I also have not been successful in getting the app to use the UBports server as a custom server to install the latest version, similar to this guy[4].
Anyone know what could be wrong?
Links:
1 developer.ubuntu[dot]com/en/phone/devices/installing-ubuntu-for-devices/
2 devices.ubports[dot]com/#/manta
3 askubuntu[dot]com/questions/582151/ubuntu-touch-appears-to-not-boot-on-nexus-10
4 askubuntu[dot]com/questions/795895/nexus-10-dualboot-ubports-image-with-existing-android
cool.bye said:
copy-paste of the post:
https://askubuntu.com/questions/796924/can-not-install-ubuntu-touch-on-nexus-10
Click to expand...
Click to collapse
I have successfully flashed ubuntu version 2 with the dual boot app in android, but I can't get it to update. I also have not been successful in getting the app to use the UBports server as a custom server to install the latest version, similar to this guy[4].
Anyone know what could be wrong?
Links:
1 https://developer.ubuntu.com/en/phone/devices/installing-ubuntu-for-devices/
2 https://devices.ubports.com/#/manta
3 https://askubuntu.com/questions/582151/ubuntu-touch-appears-to-not-boot-on-nexus-10
4 http://askubuntu.com/questions/795895/nexus-10-dualboot-ubports-image-with-existing-android
Click to expand...
Click to collapse
Are you sure that there is a newer version than 2?
Somewhere I picked up that ubports offer their own fork of the multirom app which uses their servers.
Edit: You could also try to only flash the recovery initially and see whether you get any further that way. So after using ubuntu-device-flash, you should have a recovery image somewhere in ~/.cache/ubuntusomethingoranother/ and in theory you should be able to flash that with fastboot.
So I recently bought myself a Nextbook Ares 11A (you can get look at it here: http://www.nextbookusa.com/productdetail.php?product_id=33
For the life of me, I can't figure out how to root it at all. Anyone have an idea how to root it. I have tried King and Kingo root, both PC versions. Vroot/iroot, framaroot apk, and some others that i kinda forgot.
One of the first things I did to this tablet was upgrading its android version to 6.0.1
I think one of the main exploits to use for this would be the firmware update
-quick note. If your having problems with this tablet rebooting by itself re download the android 6.0.1 firmware update and install it again.
Firmware update download: https://goo.gl/Cev80L
Same here. Can't root it. Awesome tablet for the price just $197 for a 11 inch tablet running Android 6.0.1 Marshmallow. Here are my specs. Hope e can find a root soon. Boring without root access. No cool apps without have root.
Netbook Ares 11A
Model# NX1611264
Running Android ver. 6.0.1 Marshmallow
Security patch level 2015-11-01
IFWI ver.
Build # V1-1.9.LMY47I.20160803.154546
Kernel-3.14.37-X86_64-L1-R517
I am so glad some of the community is interested in this.
can you post a copy of the update? ive been having a hard time gettin the update.zip to fully dl
mrspinler said:
can you post a copy of the update? ive been having a hard time gettin the update.zip to fully dl
Click to expand...
Click to collapse
no problem. ill do that when i get home from school today
GRIMMMMS said:
no problem. ill do that when i get home from school today
Click to expand...
Click to collapse
ty
also any luck actually rooting this tablet? ive tried but the device isnt recognized by the fastboot drivers.
however adb recognizes it when it is actually turned on normally wich is weird.
mrspinler said:
ty
also any luck actually rooting this tablet? ive tried but the device isnt recognized by the fastboot drivers.
however adb recognizes it when it is actually turned on normally wich is weird.
Click to expand...
Click to collapse
No I really havent had any luck wth any pc rooting software's or apk viersons. I tryed all the ones I trust. And i dont really know how to root a divise other than using the software.
mrspinler said:
ty
also any luck actually rooting this tablet? ive tried but the device isnt recognized by the fastboot drivers.
however adb recognizes it when it is actually turned on normally wich is weird.
Click to expand...
Click to collapse
here you go. the dl :https://goo.gl/Cev80L its from google drive
i installed the update and my tablet doesnt make it all the way through and is stuck on logo screen its the same model as op ..looks like i cant go back in firmware cause the older firmware says bad footer
nextbook ares 11 a
After installing the correct adb/fastboot drivers along with the intel chip usb drivers, i was able to unlock/flash boot.img and bootloader. All i need now is a working twrp_recovery image to finish rooting this tablet and remove encryption. If anyone has a working twrp recovery or knows how to make one based off the rom, then please post it. I would love to have this tablet rooted and non encrypted.
11a
i have the same tablet is there anyway you could send a copy of firmware or the stock recovery @mrspinler
look-up vampiro's work on the ares 8, he has made a twrp that will work, with a mouse connected to the ares 11, the are a few modified roms for the ares 8, including a remix os, that works great, except for touchscreen doesn't work, but touchpad, and attaching a mouse works great
nextbook ares 11 a
tim121283 said:
i have the same tablet is there anyway you could send a copy of firmware or the stock recovery @mrspinler
Click to expand...
Click to collapse
tim i am sorry but i am unable to give a stock recovery seeing as i tried to flash other recovery images. however i would be glad t post the update file but i can't post links yet. The update file is in the very first post, and you have to unzip it onto the sd card to get the tablet to notice it.
If you are familiar with rooting android then perhaps you could provide the stock recovery image so that someone with more programming knowledge can actually make a cwm or twrp recovery from it. The boot.img file is correct as well, which happens to be inside the update file. I know this because i almost bricked my tablet XD.
---------- Post added at 03:14 AM ---------- Previous post was at 03:09 AM ----------
thew-tab said:
look-up vampiro's work on the ares 8, he has made a twrp that will work, with a mouse connected to the ares 11, the are a few modified roms for the ares 8, including a remix os, that works great, except for touchscreen doesn't work, but touchpad, and attaching a mouse works great
Click to expand...
Click to collapse
Have you been able to root this tablet with the ares 8 files? If so then how did you get the recovery.img to work and what about the encryption files? I ask because the ares 8 has the same cpu but it is android 6.0.1 rom versus android 5.0/5.1.
11a
heres the deal i downloaded the update on the first page and always got stuck at like 35 percent tried to flash the recovery from the 11rootkit it didnt work tried from the ares 8 and just get an error screen ive got the tablet unlocked fully and can flash anything in fastboot but no file at all with bring it back ive tried the firmware files and there not in the right format for fastboot the tablet is bricked but can still get into fastboot but no working recovery
mrspinler said:
After installing the correct adb/fastboot drivers along with the intel chip usb drivers, i was able to unlock/flash boot.img and bootloader. All i need now is a working twrp_recovery image to finish rooting this tablet and remove encryption. If anyone has a working twrp recovery or knows how to make one based off the rom, then please post it. I would love to have this tablet rooted and non encrypted.
Click to expand...
Click to collapse
i have no idea
if you ever get it done please come back and help us get ares rooted XD
If anyone can manage getting a copy of recovery.img off your tablet, please post it. I will try and make a twrp img with it. Hopefully a dev can pick this up cause I am sort of out of my league atm.
I'm very interested in this endeavor. I have a Ares 11A as well but I'm in desperate need of a stock ROM as mine got trashed by the Marshmallow update. As a result I had to install Win 10 on the device temporarily, but i would like to get it back to the original stock ROM and try again. If that fails, then I'm going to have to build an entirely new ROM (never done this before) based on Android-x86 Marshmallow.
What's really sad is that support for this device is sorely lacking from the vendor(Efun/Yifang). They don't even post a stock ROM on their website (nextbookusa.com) for this device. However, this device is similar to some of the Chinese tablets posted on techtablets.com so I MAY be able to find a stock ROM / drivers there.
baharvey7817 said:
I'm very interested in this endeavor. I have a Ares 11A as well but I'm in desperate need of a stock ROM as mine got trashed by the Marshmallow update. As a result I had to install Win 10 on the device temporarily, but i would like to get it back to the original stock ROM and try again. If that fails, then I'm going to have to build an entirely new ROM (never done this before) based on Android-x86 Marshmallow.
What's really sad is that support for this device is sorely lacking from the vendor(Efun/Yifang). They don't even post a stock ROM on their website (nextbookusa.com) for this device. However, this device is similar to some of the Chinese tablets posted on techtablets.com so I MAY be able to find a stock ROM / drivers there.
Click to expand...
Click to collapse
I'm in the exact same situation how did you get windows to boot?
tim121283 said:
I'm in the exact same situation how did you get windows to boot?
Click to expand...
Click to collapse
Basically, I deleted the Android partitions and reallocated the space a a Windows partition. I got into the device UEFI boot manager by pressing the power + Vol down buttons, then releasing the power button when the Nextbook logo appears, then release the Vol down button. It's a little tricky to get into it but it can be done. Before you attempt to do so you have to get the device into fastboot mode (power+vol up buttons) and unlock the bootloader first. Be advised though that finding Windows 10 drivers will be VERY difficult! It's not for the faint of heart! I went to the techtablets.com website to find the drivers as they specialize in supporting Chinese-made tablets.
As I've stated earlier this is a temp solution. When all is said and done, this will become a dual-boot or multi-boot tablet
this is the only thing i can find but cant get it right http://www.nextbookusa.com/_gendownloads/NX16A11264/update.zip