[A511/A510] [01-07-2012] CWM Recovery - TESTING only (can cause bricks!!)

[A511/A510] [01-07-2012] CWM Recovery - TESTING only (can cause bricks!!) - Acer Iconia A700 and A510

Hi all,
Well, it looks like it works now!
Touch is also available, built through the builder of CyanogenMod (turned out I used the wrong recovery, I now used boot.img from the 1.011 ROM). Use the power button to go back one step (up one level in the menu).
For the non-touch version you can use Volume+ (one dot) and Volume- (two dots) works and use power to select an option.
** WARNINGS **
My device is hard-bricked due to the restore function not working correctly... be careful what you do!
Extra WARNING - do not use:
WIPE DATA/FACT. RESET
FORMAT PARTITIONS
BACKUP/RESTORE
FOTA
1. Avoid FOTA (software update from Acer, directly on device), see update here
2. I have not tested each function yet!
3. Step 12 below seems to have a problem. Sometimes the recovery does get corrupted and needs to be reflashed.
4. Try to not use wipe/backup/restore features - only install from zip has been tested and works
** Downloads **
EDIT FROM THE ARCHANGELULLED LINKS TO AVOID BRICKING DEVICES
** Uninstall **
Uninstall has not been tested in most cases. Please let me know whether this is sufficient and whether it works.
A510
Install the A510 Stock Recovery using the batchfile in the following download:
{
"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"
}
A510-stock-recovery.zip (4.48 MB)
A511
Try the steps in the following post:
http://forum.xda-developers.com/showpost.php?p=29101012&postcount=108
If that doesn't work (for instance because the install-recovery.sh file does not exist), try installing the files from the following post:
http://forum.xda-developers.com/showpost.php?p=29217619&postcount=111
** Credits **
Dees-Troy for the versions of the BoardConfig.mk & recovery.fstab on his github
Cyanogenmod for their CWM-recovery-build-website
Koushik Dutta for his porting CWM guide
** Install instructions **
1. Boot your device
2. If it's already unlocked, skip to step 7
3. Type following in a DOS-prompt:
Code:
adb reboot bootloader
4. Wait till device is booted and reconnected to pc (ie. drivers loaded)
5. Type following in a DOS-prompt:
Code:
fastboot oem unlock
6. Be quick (it times out) to unlock the device. Use Volume- key to highlight the unlocked lock and press the Volume+ key to activate
7. Type following in a DOS-prompt
Code:
adb reboot-bootloader
8. Wait till bootloader is loaded and reconnected to pc
9. Type following in a DOS-prompt:
Code:
fastboot flash recovery XXX.img
(replace XXX with the image file name of your choice)
Remark: step 10 to 12 can be skipped if you'll also root your device with my root-cwm-zip. That already removes the same file, so you shouldn't experience this issue
10. Reboot the device and hold to Volume- button to load the recovery
Make sure to do this - if you do not, it will automatically overwrite your recovery
11. Try to mount system. Be carefull what buttons you press. You can use power to cancel any menu and go back one menu
12. When system is mounted type the following in a DOS-prompt:
Code:
adb shell
cd /system/etc
mv install-recovery.sh install-recovery.old
13. Reboot and see whether you can still use your system. Reboot again with Volume- and see whether you can still access recovery (or use the following command)
Code:
adb reboot recovery
I will make this all much simpeler with a dos script, etc., as soon as the recovery correctly works.
** RECOVERY-A51x-tools.zip **
For quick usage I added the tools that I use to write recovery (adb, fastboot for writing the recovery to the device - batchfiles are included with each recovery download).
Next step... if you're willing... is root: http://forum.xda-developers.com/showthread.php?t=1729432
Regards,
Nika.

Great news

It seems that I can't flash update.zip anymore (1.011 ROM or FOTA)
I desperately need a stock recovery.img because my system is not working anymore (I've installed this Recovery, and then tried to apply the FOTA update: when it reboot to recovery the flash seems to have had some errors. On system reboot the tablet is stuck on Acer logo). I can't flash the 1.011 ROM anymore

simoneser said:
It seems that I can't flash update.zip anymore (1.011 ROM or FOTA)
I desperately need a stock recovery.img because my system is not working anymore (I've installed this Recovery, and then tried to apply the FOTA update: when it reboot to recovery the flash seems to have had some errors. On system reboot the tablet is stuck on Acer logo). I can't flash the 1.011 ROM anymore
Click to expand...
Click to collapse
See attached recovery for A510. I'm quite sure it works for A511 too.
Did you try to enter recovery using "adb reboot recovery" or by power off, power on with Volume- and wait for recovery? And did you put the 1.011 ROM (update.zip) into the external sdcard?
Flash recovery with:
1. Reboot into bootloader with:
Code:
adb reboot bootloader
2. Enter the next command from the folder with the recovery.img:
Code:
fastboot flash recovery recovery.img
By the way, I've managed to get into bootloader mode by using Volume- and switch the rotation lock back and forward at the same time...not sure whether there's another way (other than booting the device and rebooting into bootloader with the adb command).
Regards,
Nika.

simoneser said:
It seems that I can't flash update.zip anymore (1.011 ROM or FOTA)
I desperately need a stock recovery.img because my system is not working anymore (I've installed this Recovery, and then tried to apply the FOTA update: when it reboot to recovery the flash seems to have had some errors. On system reboot the tablet is stuck on Acer logo). I can't flash the 1.011 ROM anymore
Click to expand...
Click to collapse
Maybe some more details from your side are good as well.
1. Why did you install the 1.011 update.zip using the recovery? See also next question
2. Did you try install update.zip (put in external sdcard and name it update.zip!) using the regular recovery? In my case it always first tries to do update.zip and then goes into the recovery
3. Make sure the update.zip is correct on the external sdcard. Maybe copy it back and unzip to see whether it's not corrupt
Yesterday I also tried installing another zip that I created myself (to see whether I can get root somehow) and running the zip works fine, so it definitely works!
Regards,
Nika.

OP changed. It works now. It's not touch recovery, but using Volume+ and Volume- works and use power to select an option.
** WARNINGS **
1. I have not tested each function yet!
2. Step 12 below seems to have a problem. Sometimes the recovery does get corrupted and needs to be reflashed.
Believe it or not, my first version of the recovery was very close. I just had some problems due to invalid BoardConfig.mk entries which I had used from the Dees-Troy recovery source. I have now used the ones that were generated automatically when using the CWM-recovery-build-website (which generated the touch recovery but seems to have the before mentioned issues)...

nikagl said:
Maybe some more details from your side are good as well.
1. Why did you install the 1.011 update.zip using the recovery? See also next question
2. Did you try install update.zip (put in external sdcard and name it update.zip!) using the regular recovery? In my case it always first tries to do update.zip and then goes into the recovery
3. Make sure the update.zip is correct on the external sdcard. Maybe copy it back and unzip to see whether it's not corrupt
Yesterday I also tried installing another zip that I created myself (to see whether I can get root somehow) and running the zip works fine, so it definitely works!
Regards,
Nika.
Click to expand...
Click to collapse
1. I've installed the 1.011 update.zip (via stock recovery) yesterday and all went fine. Then today I saw your recovery and I flashed it. Then I saw the FOTA alert, I've pressed "Update", but when it went to flash it I saw an Android with a red triangle, and on restart the tablet is stuck on Acer logo.
2. Yes, but it goes straightly to your recovery. And if I flash 1.011 update.zip with your recovery I see only an Android robot, it seems that it can't flash it for some strange reasons. And I can't see the bottom part of the recovery, it's zoomed so I can't know what's happening.
3. It's the same .zip that yesterday worked, so it's not corrupted
Now the situation got worse..I tried some other things (other recoveries for A510 like Thor's or TWRP) but didn't get to solve. Now I think that the battery is dead, and I'm charging the tablet from 1 hour (but it's not booting anymore: nothing happens when I press power button, the screen doesn't turn on...I hope it's not definitely dead ) so I can't try the above method

simoneser said:
1. I've installed the 1.011 update.zip (via stock recovery) yesterday and all went fine. Then today I saw your recovery and I flashed it. Then I saw the FOTA alert, I've pressed "Update", but when it went to flash it I saw an Android with a red triangle, and on restart the tablet is stuck on Acer logo.
2. Yes, but it goes straightly to your recovery. And if I flash 1.011 update.zip with your recovery I see only an Android robot, it seems that it can't flash it for some strange reasons. And I can't see the bottom part of the recovery, it's zoomed so I can't know what's happening.
3. It's the same .zip that yesterday worked, so it's not corrupted
Now the situation got worse..I tried some other things (other recoveries for A510 like Thor's or TWRP) but didn't get to solve. Now I think that the battery is dead, and I'm charging the tablet from 1 hour (but it's not booting anymore: nothing happens when I press power button, the screen doesn't turn on...I hope it's not definitely dead ) so I can't try the above method
Click to expand...
Click to collapse
When you only installed the recovery as recovery you should be ok. Bricks only happen when you flash a new boot record... I've also tried TWRP's but didn't have any issues so far, other than that they didn't work.
Remember the tablet doesn't charge when USB connected (unless using the charger). In my case that's one of the reasons I had to stop yesterday
When it runs again (hopefully) try my new recovery. Get into bootloader mode with the Volume-, Poweron, screenrotation lock method and flash it with "fastboot flash recovery recovery.img". If it's locked again (which happens after flashing roms, it will then complain when you try to install the recovery) run "fastboot oem unlock", reboot with "fastboot reboot" and try again to flash the recovery.
Good luck and keep me (us) posted
Regards,
Nika.

The tab is completely dead
I've charged 100% (white LED), but the screen won't turn on.
I only noticed that if I connect the tab to pc via USB there is a new device called "APX" in "Other devices".
Checked some A500 threads and it seems APX mode is to flash bootloaders
But nothing for A510\1...so it's dead

simoneser said:
The tab is completely dead
I've charged 100% (white LED), but the screen won't turn on.
only noticed that if I connect the tab to pc via USB there is a new device called "APX" in "Other devices".
Checked some A500 threads and it seems APX mode is to flash bootloaders
But nothing for A510\1...so it's dead
Click to expand...
Click to collapse
That's horrible also for others because it will make the choice to install this a little harder... although I honestly have not had any of your trouble, and I don't really understand what happened either
But.. definitely check on google. I have seen many successful recovery from APX-mode.
Good luck and keep us posted.
Regards,
Nika.

For others, still willing to play around with the device, here's a solution to get root:
http://forum.xda-developers.com/showthread.php?t=1729432

great job
any idea if it can fit in a510?

BENETNATH said:
great job
any idea if it can fit in a510?
Click to expand...
Click to collapse
root or cwm? I guess I can build CWM for A510 too, but you have TWRP and CWM already don't you (on other forums...)?

we have root but no working recovery..
Twrp first not allow the swipe to unlock
cwn release from EB launch but only backup works, not restore.
Any help would be appreciated

BENETNATH said:
we have root but no working recovery..
Twrp first not allow the swipe to unlock
cwn release from EB launch but only backup works, not restore.
Any help would be appreciated
Click to expand...
Click to collapse
Ok... will build it as soon as I can (takes some time to setup the env). I haven't tested restore btw, need to backup some more stuff (with titanium backup) to make sure I don't loose anything
Also, make sure you have a large enough external sdcard when making backups. Remember the internal sdcard is huge and backups can cause the external to be full
One more thing, also good to know, you can always backup using DD commands:
Code:
dd if=mountpoint of=/sdcard/filename.img
And here's a list of the mountpoints in the A510/A511:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS /dev/block/mmcblk0p1 /recovery
/dev/block/platform/sdhci-tegra.3/by-name/LNX /dev/block/mmcblk0p2 /boot
/dev/block/platform/sdhci-tegra.3/by-name/APP /dev/block/mmcblk0p3 /system
/dev/block/platform/sdhci-tegra.3/by-name/CAC /dev/block/mmcblk0p4 /cache
/dev/block/platform/sdhci-tegra.3/by-name/MSC /dev/block/mmcblk0p5 /misc
/dev/block/platform/sdhci-tegra.3/by-name/FLX /dev/block/mmcblk0p6 /system/vendor /flexrom /flex
/dev/block/platform/sdhci-tegra.3/by-name/AKB /dev/block/mmcblk0p7 ?
/dev/block/platform/sdhci-tegra.3/by-name/USP /dev/block/mmcblk0p8 /aboot (bootloader.blob)
/dev/block/platform/sdhci-tegra.3/by-name/DE2 /dev/block/mmcblk0p9 ?
/dev/block/platform/sdhci-tegra.3/by-name/UDA /dev/block/mmcblk0p10 /data
So you can use these commands:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/LNX of=/mnt/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/APP of=/mnt/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/CAC of=/mnt/sdcard/cache.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/MSC of=/mnt/sdcard/misc.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/FLX of=/mnt/sdcard/flexrom.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/AKB of=/mnt/sdcard/AKB.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/USP of=/mnt/sdcard/bootloader.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/DE2 of=/mnt/sdcard/DE2.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/UDA of=/mnt/sdcard/data.img

Well... I tried making a backup in my CWM and it says "Error while making a backup image of /data". Not sure yet why... will first make some dd backups, titanium backups, wipe device and will then start testing from scratch...

BENETNATH said:
we have root but no working recovery..
Twrp first not allow the swipe to unlock
cwn release from EB launch but only backup works, not restore.
Any help would be appreciated
Click to expand...
Click to collapse
Sorry for spamming, please provide a boot.img of your device/rom-version so I can use that kernel for building the recovery.

Touch is now also available, built through the builder of CyanogenMod (turned out I used the wrong recovery, I now used boot.img from the 1.011 ROM). Use the power button to go back one step (up one level in the menu).
See first post

Problem with CWM
Great work. Only problem what I have is that my device is not recognized when entering CWM. In the device manager is just an unknown device. I have installed the drivers from the Acer support. Do I need somehting else, too?

Well, my A511 is stuck at "writing recovery".
Bootloader vICS-MR1-89805f0(UnlockMode) :
sending recovery 5268kb ...
OKAY 2,063s
writing recovery ...
FAILED status malformed 0 bytes
finished. total time 503.062s
Well its still booting without problems in unlocked bootloader, but i cant flash. It just stuck there even if i try it again and again.
A511 & NV Fastboot Driver are both recognized by my system, but can it cause an error that i run windows in a VB? Need to enable USB-Debugging to run adb.
I never had problems with my Arc before using fastboot in a VB.
EDIT: Same for the touch-CWM. It just stuck at writing recovery.
adb v1.0.29

Related

[RECOVERY][UPDATE] Unofficial port of ClockworkMod Recovery for folio100 - BETA

This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
boot part is not backup when using Backup / Restore.
Update 1 : Cache is mounted at start
Installation instructions :
Download : update.zip
- Copy the update.zip to a sdcard
- Follow the same procedure as explain in this post for the FolioMod
- Don't need to wipe.
- After reboot, enter recovery again to see the change
Click to expand...
Click to collapse
Usage :
- ( VOL + ) and ( VOL - ) key to highlight the menu
- ( HOME ) key to select
Click to expand...
Click to collapse
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel

wolfx said:
This is a port of the ClockworkMod Recovery V3.0.0.5 for Folio100.
Almost everything is functional except some minors issues.
Known issues :
partitions do not mount automatically at startup
boot part is not backup when using Backup / Restore.
Installation instructions :
Usage :
THANKS to:
Koush : the original creator of ClockworkMod
Dexter_nlb : for the great work he makes with the FolioMod
All the peoples who help me on cyanogenmod irc channel
Click to expand...
Click to collapse
this will be so great, good joob and keep em comming. Next stop Gingerbread

Installed it just aminute ago worked great. I played around a bit, i formated system, data, cache and dalvik cache. I also tryed format boot but that was a no go. In the first clockwork 3 releases there was also this problem with boot. i cant remember if it was the same error, but its fixed now so that it works correct. I also flashed FolioMod from clockwork iwth out any problems. Really nice work

Great Job!! Now we just need some AOSP/CM7 love

Can I use it with stock rom too? Tnx

Great work thanks alot for taking the time to do this

girello71 said:
Can I use it with stock rom too? Tnx
Click to expand...
Click to collapse
I don't try backup / restore (nandroid) with stock rom maybe it work, but when i try to flash stock rom it skip the different part and don't write anything.
However, what could be interesting if backup / restore work is to make a backup of a fresh install stock rom with the last update include.

boqonx said:
Great Job!! Now we just need some AOSP/CM7 love
Click to expand...
Click to collapse
I currently work on the CM7, but be patient, it's more complicated than for recovery.

Of course dude, take your time and slowly churn that tasty gingerbread dough

wolfx said:
I currently work on the CM7, but be patient, it's more complicated than for recovery.
Click to expand...
Click to collapse
Finaly, one more rom builder. We need some options to choose from. Wish you the best of luck. And if you dont mind, maybe from time to time post progress on your work. If you need some beta testing, im there

Back to square 0
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..

Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
If you delete the update.zip for clockwork recovery you will have normal recovery. When installing clocwork you pu the zzip to root of exterenal sd card boot to recovery do system update, device reboots, now you have to do the system update again, your now in clockwork recovery

Butchi said:
Hi,
Based on the positive response i started to install the ClockworkMod recovery. As i got the error message that there was no space on the device i did a factory reset (i have 1.3c). Now the installation of the ClockworkMod looked ok. But after i rebooted the device nothing happened (blank screen). Only the initial screen shows (with pressing the on/off-vol+ buttons) after this just a blank screen. Also if i press within the 3 sec the on/off and vol+ the screen goes blank. So i guess i have now a bricked folio and i will start to read up how to unbrick.
BTW i do not know if i did something wrong or there is/was some particularities with my configuartion or that the clockworkmod still needs some work..
Click to expand...
Click to collapse
Not sure you bricked it, you can use the fastboot method to flash the recovery again, then you can use the recovery to flash a full rom.

Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)

boqonx said:
Btw, where do we have fastboot access? I thought what we have is the tegra bootloader which is quite risky to enter? (heard of the story of ppl getting stuck in the bootloader with no way to get out)
Click to expand...
Click to collapse
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot

wolfx said:
you can access fastboot by pressing POWER x 3 ( attention : 3 times only not 4) then VOL UP when the folio start. I use it everyday to flash recovery.img or boot.img with no problems.
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
for recovery:
Code:
./fastboot flash recovery recovery.img
for boot:
Code:
./fastboot flash linux boot.img
you can use the -w option to wipe data and cache
for reboot :
Code:
./fastboot reboot
Click to expand...
Click to collapse
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?

wolfx said:
Usage :
place the recovery.img or boot.img in the same directory as fastboot then from a shell navigate to your fastboot directory and us the following command :
Click to expand...
Click to collapse
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.

nickwarn said:
So if we flash recovery.img thru fastboot we should be able to boot in to clockwork recovery via rom manager?
Click to expand...
Click to collapse
Rom manager don't work with this recovery for now, official support must be added by Koush in rom manager before. I will commit the source to him when recovery is finalized.
Butchi said:
Thanks for all the responses but i go step by step (hopefully "unbricking" my folio).
I was able to get to the display of the line "Starting Fastboot USB download protocol, please execute 'fastboot' command" (by pressing 3times the power button).
I connected the folio with USB to my PC (Win7) but the needed driver could not be found in the PC.
So i have a couple questions.
-Is the PC-driver part of the SDK? or how can i get the driver?
-I guess that with the PC i can copy via USB the recovery image to the fastboot directory. Is this correct? How else can i get the recovery image to the fastboot directory?
-Is the recovery image the "Folio stock image for full restore to stock rom" Dexters thread
Hope i can get some more help with restoring my system.
Click to expand...
Click to collapse
For driver :
- Download the android SDK here
- Edit "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Add the following after [Google.NTx86] (or [Google.NTamd64] if 64 bits windows)
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
- start your folio in fastboot mode and plug in. Win will not find the right driver to use
- Force driver installation : click update driver -> have disk -> point to "<your-android-sdk-folder>/usb_driver/android_winusb.inf"
- Choose bootloader driver
After this you normally can use fastboot place in : <your-android-sdk-folder>/tools
For the recovery.img you can use the one include in the update.zip or one from FolioMod.
Hope it can help you

I am still not there...
Again thanks for all the help and support
OK I installed the SDK (and the JRE as it was also a requirement). But i did not find the USB driver so far (which is strange because i had connected the folio with the PC earlier).
While doing all that i discovered that somehow the ClockworkMod Recovery was installed correct. I could get the expanded ClockworkMod menu. (Using the power button and simulteaneous the Vol+ button within the 3 sec. And whatever i selected update or recovery, i got to the ClockworkMod menu.) This looked promissing.
So i put an update.zip on the sdcard (dextermod 1.3b).
In the menu i selected 'apply sdcard:update.zip'. After this i got the screen (white text) Confirm install? THIS CAN NOT BE UNDONE and (yellow text) 7 lines with '-No', one line with '-Yes - install /sdcard/update.zip' and 3 more lines with '-No'.
After selecting the 'Yes' line i got the following messages:
--Install from sdcard...
Finding update package...
Opening update package...
Installing update...
Installation aborted
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Strange enough, even after the update was aborted, the system started again after i selected to reboot in the ClockworkMod menu. Wow. Who knows what happened may explain this. But nice for me the system works again (till the next time).

Looking very nice. Just flashed it and made a backup

N00b tutorial: Flashing EOS3 to MZ604 Xoom (Wifi)

Hi all.
A few days ago I entered the Xoom forum asking about how to modify an "unaltered" Spanish/European Xoom (Wifi Only, MZ604) running stock Android Honeycomb (3.2) and flash a custom ROM with Android 4.1.1 (JellyBean), so that I don't have to wait Motorola to release the updates (still in Honeycomb in Europe, while in US they're enjoying JB), and to enjoy the extras that custom ROMs offer (root, overclocking, etc).
Xda users "wesamothman" and "Cubanluke88" answered quickly to my question and this allowed me to unlock my Xoom bootloader, install TWRP Recovery and flash EOS3 ROM (JellyBean for Xoom from TEAM EOS). The results are awesome; the change from Honeycomb to Jellybean, plus the totally stable overclocking at 1.2 and even 1.4 Ghz is worth the fact that you void the Xoom warranty by doing this procedure. It's like having a brand new tablet.
As I found some problems/mistakes in the procedure I was given, I've created a new "Guide for Noobs" (based on wesamothman's) so that anybody can reproduce the same steps and convert an European Xoom (Wifi Model, MZ604) into a modern EOS3-powered Xoom.
NOTE: I initially wrote this tutorial using the EOS-RECOVERY-6.IMG as the CWM Recovery software to install in the Recovery Partition. The recommended recovery software now is TWRP so I've updated the tutorial replacing the download links and filename.img to flash. The procedure remains the same, although I really tested and executed it with eos-recovery-6, not with TWRP. Anyway, it is supposed to be flashed and work the same way than I initially described it.
NOTE THAT THIS PROCEDURE IS FOR EOS3 - (EOS NIGHTLY <= v155).
EOS4 (nightly >= v156) requires a slightly different procedure!!!
Please, remember that by unlocking the bootloader (and flashing non official software) you're voiding the device warranty and that I'm not responsible of any damage that your device can suffer. I'm just explaining how I did the unlocking+flashing to convert my SLOW XOOM in a fully working JellyBean system. Remember also that this procedure is for WIFI ONLY Xooms. 3g xooms need a different rom/procedure.
So, sumarizing, that's what we are going to do:
a.- Unlock the "bootloader" of the Motorola Xoom so that we can "install" custom software in both the "recovery" and the "data" partitions. Please notice that by unlocking the bootloader you void the device warranty.
b.- Flash TWRP software into the recovery partition, (I was flashing EOS-Recovery-v6 software initially but now is deprecated and TWRP must be used) so that we can launch this software pressing a combination of keys during power-on. This software will allow us to make full backup/restore of the device memory, and to install any ROM (EOS2, EOS3, cyanogenmod, EDGE, etc) in the system. Thanks to this recovery we are safe against problems in the O.S. (even if we break it), because we can always recover from backup or flash a new ROM (including the "stock" ROM, I mean, the ROM shipped oficially with the device) and solve the situation.
c.- Once recovery is installed, do a NANDROID backup of the NAND of our device, to have a copy of the "stock" system.
d.- From Recovery, flash the desired ROM (EOS3 in my case) and the Google Apps applications (they can't be included inside the ROM for legal reasons, so they are flashed separately) to the "data" particion.
e.- Restart and enjoy our new system (you can also made another NANDROID backup to save this "working point" for the future).
Steps a). and b). need a working computer with Linux, Windows or Mac. After doing b).- you can do everything from the Xoom itself and you don't need the computer anymore. After doing b)., you'll be able to download ROM images directly under your Xoom in the uSD card and reflash any new ROM directly rebooting the tablet into recovery-mode.
Steps a) and b) can be done from Linux, Windows and Mac. Although I have Linux in my laptop, I found that almost all the tutorials in Internet explain the procedure under Windows so I installed temporary a Windows system to do the "PC dependant" steps, because I didn't want to experiment with the "risky" actions in both steps.
So, let's start with the "PC dependant" actions, which includes steps a). and b).
I'll try to update the thread with screenshots in the future, as I didn't take photos/screenshots of the procedure, I'll check images.google.com to find something that fits the text, and add the later to the tutorial if they are really needed.
PART 1 .- HOW TO INSTALL TWRP RECOVERY:
Here we are going to unlock our Xoom and install a custom recovery software into the recovery partition. The recovery software is launched when you start your Xoom in recovery mode, and this is achieved by pushing Power, VolUP and VolDown key combinations when you power-on the tablet (we'll see how later).
So we'll replace the original "recovery" software by a custom one that allows us to flash NON OFFICIAL software to the data partition.
To do that, first we have to download all the required software in the Xoom enternal uSD card and prepare our PC system to recognize and work with the Xoom. We have to download:
Get the Motorola USB drivers for your system: http://developer.motorola.com/docstools/USB_Drivers/ . This step is only needed under Windows, so that the Windows System recognizes the Xoom and the Android SDK binaries (adb and fastboot) can send data to the tablet. Check that you're downloading the right drivers (32 or 64 bits) for your 32 or 64 bits System, and install them. If the Android SDK in your Linux system can recognize the Xoom, you're ready to use Linux also to do the following steps.
Download and Install in your PC the lastest JavaSE JDK from Oracle's website: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
Download and install the Android SDK for your system: http://developer.android.com/sdk/index.html .
Download the EOS v155 ROM and GoogleAPPS for that version. My final choose was EOS3 ROM Wingray (Jellybean for Xoom), and installed v155 from the nightly compilations (which is the latest nightly in Android 4.1, being v156+ Android 4.2). "Nightly" means that as the software is still not "final version" (it's still in development) a new version is released almost everyday, correcting bugs or adding new features. I personally didn't found any bug in v155 but you can check the EOS3 thread in XDA to check that the latest version has no bugs reported by people in that thread.
ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ (as of date September-2012 - I recommend v141 )
GAPPS: Latest: http://teameos.org/gapps/wingray (I used http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120802-eos-signed.zip for v155).
EOS3 THREAD: http://forum.xda-developers.com/showthread.php?t=1764751
And the most important, download TWRP the "recovery software" that will allow you to work without the need of the PC (I was using Team Eos Recovery 6 initially, but now is deprecated and TWRP must be used):
Team Win Recovery Project 2.x, (TWRP): http://forum.xda-developers.com/showthread.php?t=1782235
You should download the IMG file (example: R.A.H.v3_TWRPv2.5.0.img). Check that the size of the downloaded file matches the size that is shown in the above link. This is the most important file because it will allow to install the recovery system and it's CRITICAL that the file is not corrupted..
Steps:
a.- Install in your PC the Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
This will download and install the packages needed so that we can access the Xoom from the PC for "flashing" data purposes; mainly "adb" and "fastboot". Adb allows us to work with the xoom started in the Android System, and fastboot allows us to work with the xoom started in fastboot mode, which is the mode we'll use to "flash" the recovery software.
b.- Enable USB debugging in the XOOM (in settings, development), so that we can use adb with the tablet.
c.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
d.- Plug the Xoom to your PC.
e.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices". You should see that the system identifies your Xoom with a long numbers+letters string. If you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device, so that the system can bind the right USB drivers we installed to that concrete device.
After a While, Windows will fix it and re-executing "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
Now, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup. Fastboot mode is a special bootmode in the xoom that allows the PC to send data to the Xoom and "write" to Recovery and Data partitions. You can also enter that mode starting the Xoom with "Power+Volume Up" pressed simultaneously.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
{
"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"
}
(Photo: fastboot mode, taken from google images)
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because Windows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot".
Issue the following command to unlock the Xoom (you'll void the warranty). If you don't unlock the xoom, data and recovery partitions will be "read only" and you can't send the "new software" to them.
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option. The device will ask you twice if you are sure that you want to unlock the device and void the warranty, and then it will make a "factory reset" of the O.S. .
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc. Enable again "USB debugging" and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the recovery file (the name may vary, with something like R.A.H.v3_TWRPv2.5.0.img) to the android-sdk/platform-tools/ folder with name "recovery.img" and execute:
Code:
fastboot flash recovery recovery.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery recovery.img
sending 'recovery' (XXXXX KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
Now disconnect the USB cable and enter recovery mode with:
- When the Motorola logo appears, tap Volume Down (not press, tap) repeteadly until "Android Recovery" is displayed in the screen.
- In this moment, pressing Volume Up will send you to Recovery Mode.
- If you press by mistake again Volume Down, you'll enter DRS mode. You can leave it with VolUP+VolDown+Power and try again (Xoom is powered off).
And you'll start the TWRP Recovery recovery system. If you see the standard Android recovery system instead of TWRP recovery, you can repeat the above "fastboot flash recovery recovery.img". You don't have to unlock the bootloader again, just flash the recovery software and reboot again in recovery mode with "fastboot reboot" and "adb reboot recovery".
(Photo: my Xoom in EOS6 recovery mode, TWRP is different, with better controls and more features )
You can start recovery mode also manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE TWRP RECOVERY
How to enter in recovery mode:
A.- Manually:
- Turn Xoom off.
- Press Power to turn Xoom on.
- When the Motorola logo appears, tap Volume Down (not press, tap) repeteadly until "Android Recovery" is displayed in the screen.
- In this moment, pressing Volume Up will send you to Recovery Mode.
- If you press by mistake again Volume Down, you'll enter DRS mode. You can leave it with VolUP+VolDown+Power and try again (Xoom is powered off).
b.- From "adb" in a PC system with Android running on the tablet connected to that PC:
Executing "adb reboot recovery"
c.- With a custom ROM, selecting "reboot" will ask you if you want a normal reboot or a recovery-reboot.
How to use recovery mode:
Use the Volume Up and Volume Down keys to move between options and Power button to select an Option:
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
Available options for a basic CWM / recovery are:
Reboot system now -> exit Recovery mode.
install zip from sdcard -> allows to install ZIPs to data partitions such as ROMs.
wipe data/factory reset -> delete all the contents in the data partition (needed before flashing a ROM)
wipe cache partition -> delete cache partition.
backup and restore -> allows doing "nandroid" backups and restore of our system (FULL MEMORY BACKUPS).
mounts and storage -> allows to mount aditional media to save/read data.
advanced -> extra options.
(Photo: Nandroid backup)
NOTE: TWRP is newer than the OLD EOS-recovery-6, the above capture and options may differ.
PART 3 .- HOW TO INSTALL EOS3 ROM:
Now we've installed recovery, so we don't need the PC anymore. We can enter in recovery mode at any moment and do backup/restores, flash new roms, flash updates, etc.
To install EOS3 ROM (or any other "full install" -not update- ROM, do):
Start the Xoom in recovery mode.
Backup/restore -> backup the current system to our external SD.
Wipe data/factory reset -> remove partition contents
Wipe cache -> delete the cache
Advanced -> Wipe Dalvik Cache
Advanced -> Wipe Battery Stats
Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
Reboot
Install gmail, youtube, etc from Market (not included anymore in gapps).
Enjoy your new rom!
PART 4 .- HOW TO UPDATE EOS3 ROM or install a new different ROM:
Start the Xoom in recovery mode.
Backup/restore -> backup the current system to our external SD.
Wipe data/factory reset -> remove partition contents
Wipe cache -> delete the cache
Advanced -> Wipe Dalvik Cache
Advanced -> Wipe Battery Stats
Install ZIP from SDCARD -> /sources/ -> the new rom .zip file.
Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
Reboot
Enjoy your new rom!
I hope this can help people to unlock their xooms.
Thanks to "wesamothman" and "Cubanluke88" for the initial support given and specially to EOS Team and the people that created ClockWorkMod for sharing their time, work and knowledge with us. They've converted my "slow xoom" in a very powerfull and fully functional tablet.

Couldn't expect less from you. Super great guide...
Sent from my MZ601 using Tapatalk 2

Post reserved for updates in case the initial post gets too large...

I wish all new Android users would do the level of research the OP did prior to making his initial question thread. We guided you a bit but if I remember right, your first post showed quite well that you had done your homework. If more people committed themselves to understanding what they're doing prior to doing it, I'd imagine there'd be a lot less "bricks" in the android world. Great work dude and nice job entering the forums with a bang.
Sent from my Xoom using Tapatalk 2

Thanks for your words...
In this thread I've tried not only to give a procedure (the forums and lots of websites are full of procedures) but also explain the concepts themselves (oem unlock, adb, fastboot, recovery mode, gapps, etc).
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime".
Thanks.
--
Sent from my Xoom with EOS3 ROM using Tapatalk 2

Updated with some pictures

Updated with links to v141...

eos 6 recovery.img not available
the recovery image file is not available in the link..could you update the link. Thank You !
Great tutorial

kakrikakri said:
the recovery image file is not available in the link..could you update the link. Thank You !
Great tutorial
Click to expand...
Click to collapse
Hi.
According to this URL, EOS6 RECOVERY.IMG has been deprecated:
http://forum.xda-developers.com/showthread.php?t=1604014
Now you can use Team Win Recovery Project 2.2, (TWRP):
http://forum.xda-developers.com/showthread.php?t=1782235
Flashing is almost similar to EOS6 recovery method described above, just check the last link.

NoP_Compiler said:
Hi.
According to this URL, EOS6 RECOVERY.IMG has been deprecated:
http://forum.xda-developers.com/showthread.php?t=1604014
Now you can use Team Win Recovery Project 2.2, (TWRP):
http://forum.xda-developers.com/showthread.php?t=1782235
Flashing is almost similar to EOS6 recovery method described above, just check the last link.
Click to expand...
Click to collapse
wow that was a quick reply.. THANKS (Y)

kakrikakri said:
wow that was a quick reply.. THANKS (Y)
Click to expand...
Click to collapse
Anyway, I have the eos-recovery-r6.img.zip file in my desktop, I can send you via email if you want to use it instead of TWRP (but you should not, as Team Eos recommends their new recovery system).
I'm going myself to update to TWRP this evening (they have a .zip file that you can flash from an existing recovery like my current "EOS6 recovery").

Same method for stock ics?
Sorry I am a bit paranoid..but will this same unlocking bootloader and flashing recovery method work for stock ics on my xoom?
Thanks !

Help !!! In a lot of trouble
I flashed the twrp recovery and then it rebooted..everything was perfect till that point
then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.
I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.
Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)
please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?
HELP !!!!

kakrikakri said:
I flashed the twrp recovery and then it rebooted..everything was perfect till that point
then i rebooted into recovery..and when i selected to install zip from usb drive..it said mount to sdcard failed (at this point the roms were downloaded in my internal storage) and it does not detect any zip files.
I tried putting the zip files on a proper micro sdcard and then rebooted into recovery..but still no luck.. it just says it failed to mount sdcard.
Special note:- and btw.. when i reboot into recovery and after pressing the vol up button there is a droid icon on my screen, but no 'recovery' menu shows up.. then i pressed volup+power button, this action popped up the list of menus of the recovery screen... (do u think this might be a problem?)
please help me i am panicking here..is there anyway i can flash a different recovery..like the eos recovery or the cmw?
HELP !!!!
Click to expand...
Click to collapse
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard

wesamothman said:
Twrp recovery doesnt mount external sdcard by default, you need to mount it first thru recovery. Just go to mounts and check the box to mount external sdcard
Click to expand...
Click to collapse
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?

kakrikakri said:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
Click to expand...
Click to collapse
First time ROM flashing is longer than normal booting, like 5 min ,
If you got stuck in boot loop, reboot into recovery using the power and sound keys combination and clear cache and dalvik and reboot again

kakrikakri said:
I am sorry i panicked.. I think its working fine now..i flashed a wrong recovery it seems.
May i ask ! if we are installing the eos 3 rom for the first time, does it take very long to boot the very first time?
because i my xoom is booting up after installing, and the eos logo is on display for more than 10-15 mins.. is it supposed to take this long?
Click to expand...
Click to collapse
Did you finally succeded "booting" EOS3?

NoP_Compiler said:
Did you finally succeded "booting" EOS3?
Click to expand...
Click to collapse
Yes it did and it works perfectly
Thank you NoP_Compiler and wesamothman
Sent from my Xoom using xda app-developers app

Just to say thanks for 1 of the best tutorials I have ever found,from stock ICS to eos 3 wingray nightly 151 in less than 20 mins. Only prob I had was android SDK wouldn't find x64 java on win had to install 32bit version on top but only hiccup

dead android in step 2
Hi,
Thanks for the great tutorial.
I got thru Step 1, using the image "openrecovery-twrp-2.3.1.0-wingray.img"
In Step 2, when I enter in recovery mode, I get a screen with a "dead droid" image.
Any idea about what I might be missing?
thanks!

[RECOVERY][NABIJR 4GB] TWRP 2.4.4.0, 2.6.1.0 testing

TWRP recovery for the Nabi JR. (NABIJR-NV5A)

{
"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"
}


At this point this recovery is still considered in testing. The normal disclaimers apply. 2 forum members have tested as working. After flashing to recovery partition sometimes the device would hang and need power button reset and then device works normally.
This is for Nabi JR 4GB
Nabi2 is HERE
NabiXD is HERE
NabiJR 16GB is HERE
Updates
Auto Installer for 2.6.0.0 in NabiLabGUI http://forum.xda-developers.com/showthread.php?p=44258583#post44258583
Initial
-Latest TWRP 2.4.4.0
For more information on TWRP and change log see the TeamWin Website
Download
There are 2 downloads provided. The first is an installer for those less comfortable with the command line, it can install TWRP, and restore the stock recovery if you are updating or returning Nabi to stock. The second are for people that just want TWRP 2.4.4.0 and can do a manual install.
Auto Installer
Recovery Installer for Nabi(Recovery installer for TWRP 2.4.4.0 and STOCK recovery) Use install method 1
Current recovery.img
TWRP 2.4.4.0 for Nabi(Only TWRP 2.4.4.0, manual install) Use install method 2 or 3
Installation
Start with Nabi booted to android, ADB debugging enabled, windows adb and fastboot drivers installed. (PDAnet drivers are popular)
-Method 1 (Recommended install , guided installer)
-Download "Recovery Installer for Nabi" from above
-Extract TWRPupdaterjr.zip
-Run RecoveryUpdater.bat
Code:
Select option 1 for a Nabi on v1.0.3 and follow directions
Select option 2 to return your Nabi to stock recovery after restoring stock ROM
-Method 2 (manual temporary install, will keep your current recovery)
-Download "TWRP 2.4.4.0 for Nabi"
-Extract recovery.img from TWRPrecoveryjr.zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot boot recovery.img
-Method 3 (manual permanent install, will overwrite your current recovery)
-Download "TWRP 2.4.4.0 for Nabi"
-Extract recovery.img from TWRPrecoveryjr.zip to your adb directory
-From a command prompt in your adb directory
Code:
adb reboot-bootloader
fastboot flash recovery recovery.img
Other
Device source https://github.com/aicjofs/android_device_fuhu_junior
TWRP source https://github.com/TeamWin/Team-Win-Recovery-Project/
Credits
TeamWin team for TWRP.
Dees_Troy for build tutorials.
Eric Karz and his hours of testing.

just think, now you don't have to do a factory reset any time you have a problem with JR. thank you aicjofs for contributing such useful items to help make the nabi family experience so much better .

TWRP 2.5.0.0 for NabiJR
What's new in TWRP 2.5.0.0
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
Nabi specific: Theme change required for 2.5.0.0
Download

This is awesome, thank you so much for this.

Just flashed gapps using this recovery on the Nabi Jr with ICS. Fantastic. Thank you. Now it's not a useless POS anymore.

are there any stock roms or anything i can do if i wiped the original rom that comes from the factory

juanfernandez77 said:
are there any stock roms or anything i can do if i wiped the original rom that comes from the factory
Click to expand...
Click to collapse
I replied to you in the Root for Nabijr thread. I don't have a NabiJr or I would. I know Eric should have a backup, someone needs to make a stock system image.

I've been attempting to flash the recovery, but my Nabi Jr keeps getting stuck on a screen that says, "Checking for RCK.. press key <volume up> in 1 sec to enter RCK" It has options to continue, reboot-bootloader, reboot, or power off. I have tried manually installing using the adb command lines and I've tried the automatic installer. Both get stuck on this screen. Any idea what's going on?

Anybody able to help?

is it the 4 or 16 GB tablet ?

My kid broke the 4GB Tegra 2 ICS Nabi Jr, and I got the 16GB Tegra 3 JB Nabi Jr as a replacement.
Any idea if it will work on that model?
Edit: I can't even test because this Nabi variant shows this screen after reboot-bootloader: http://i.imgur.com/I1rRMgI.jpg, and fastboot is saying waiting for device. Not sure how to proceed.

aicjofs would be able to say better
but I wouldn't use the the one built for 4 gig on the 16 gig version
4 gig is ics and 16 is jelly bean - using it could result in a foobard tablet
Send aicjofs a PM and see if he has time to look in to a recovery for 16 gig version of the nabi jr

Archon810 said:
My kid broke the 4GB Tegra 2 ICS Nabi Jr, and I got the 16GB Tegra 3 JB Nabi Jr as a replacement.
Any idea if it will work on that model?
Edit: I can't even test because this Nabi variant shows this screen after reboot-bootloader: http://i.imgur.com/I1rRMgI.jpg, and fastboot is saying waiting for device. Not sure how to proceed.
Click to expand...
Click to collapse
No way this particular recovery will work. It is Tegra2 based, and the new tablet is Tegra3 based. If anything you could try the Nabi2, or NabiXD recovery they are at least Tegra3, although if it works at all the screen will be completely off because of resolution differences. Be aware that you could damage using those recoveries, although I don't think it will and it just wont boot....anyway... for whatever that is worth... I'm just telling you. Based on what Fuhu did for XD(jelly bean) I'm not sure the Bin4ry root script will work. You can read about that adventure here http://forum.xda-developers.com/showthread.php?t=2207499
As for the fastboot thing. Make sure it is showing the fastboot/bootloader driver in device manager, the menu is definitely different what is that saying above the menu?

I did try Bin4ry, but I don't think it worked. There was an odd message in the process, and even though the script said it was done, I am not sure it was.
As for the custom recovery, I'm willing to work with you or whoever is interested, to test and get it working for the new Jr. For starters, it'd be great to know how to dump the current recovery. The next step is to figure out why I can't fastboot, and then try other recoveries from XD or custom if someone is testing with me.
The bootloader message says something about RCK - not sure what it means.

Archon810 said:
I did try Bin4ry, but I don't think it worked. There was an odd message in the process, and even though the script said it was done, I am not sure it was.
As for the custom recovery, I'm willing to work with you or whoever is interested, to test and get it working for the new Jr. For starters, it'd be great to know how to dump the current recovery. The next step is to figure out why I can't fastboot, and then try other recoveries from XD or custom if someone is testing with me.
The bootloader message says something about RCK - not sure what it means.
Click to expand...
Click to collapse
What did script say something about "cannot mount are you root"?
I'm not sure why fastboot isn't there. Do you get a different menu if you manually boot with Power and vol+ key. Maybe this new bootloader wants a key input within a few seconds of boot to enter recovery or fastboot?
I'm guessing RCK is recovery kernel.
One way or another you need to get fastboot, as you said, to try a custom recovery. So it's best to concentrate on that.

I don't remember what the script said, but it wasn't that. In fact, it could have worked for all I know, because it thought it did, but there was a "not found" message halfway through the process about something. I can repeat if this is needed.
This is the menu that comes up with adb reboot-bootloader, or by holding Vol-Up and Power. Same menu.
Do you want to connect on gTalk to try to debug this further?

Archon810 said:
I don't remember what the script said, but it wasn't that. In fact, it could have worked for all I know, because it thought it did, but there was a "not found" message halfway through the process about something. I can repeat if this is needed.
This is the menu that comes up with adb reboot-bootloader, or by holding Vol-Up and Power. Same menu.
Do you want to connect on gTalk to try to debug this further?
Click to expand...
Click to collapse
I'm mobile right now. Watching my kiddoz playing at park. I can try Gtalk later today.
So I'm looking at the image and 2 things come to mind. The USB icon
1) it's in fastboot now which is why icon is there. Open device manager as you have it plugged in and then power it up and see if there is any activity. Yellow exclamation, bootloader/fastboot driver showing up. Anything to show there is life on tablet side
2) can you use the volume keys to go down and "select" the USB icon. Or is it a touch icon, doesn't look like it but worth a shot.

OK, I'll pm you my gTalk.
The USB icon is not selectable. It just cycles back to Continue after Poweroff.
This shows up in the device manager when it's hooked up, including when it's in this bootloader mode: http://i.imgur.com/SVMzw8v.png. The Unknown Device isn't related as it's there when the Nabi Jr is unplugged too - I think it's a fingerprint reader, I'm not even sure what it is.

Archon810 said:
OK, I'll pm you my gTalk.
The USB icon is not selectable. It just cycles back to Continue after Poweroff.
This shows up in the device manager when it's hooked up, including when it's in this bootloader mode: http://i.imgur.com/SVMzw8v.png. The Unknown Device isn't related as it's there when the Nabi Jr is unplugged too - I think it's a fingerprint reader, I'm not even sure what it is.
Click to expand...
Click to collapse
Strange that its showing the ADB interface, instead of bootloader one in that task manager screenshot. I'm not thinking of many avenues here less some button pressing sequence we don't know. I tried a quick google search the other day and didn't come up with anything enlightening. You don't actually need fastboot/TWRP to root it but it would make it easier, plus I almost consider it a necessity for the backup purpose alone. It might be wise to post this is a general section and see if anyone else has seen a similar bootloader screen.

Ok here is the story on the 16GB Nabijr.
Fastboot commands need to be issued with "fastboot -i 0x0489"
The bootloader is locked on this Nabi. There is good news and bad news. Good news it can be unlocked. The bad news is that it wipes the Nabi to do so.
I was able to gain temp root in adb with motochopper. With this I was able to dd the recovery partition and extract the kernel. I was only interested in temp root, so I don't know if the program can be used as is for permanent root, or if you need to copy su and superuser.apk yourself. You can root with TWRP anyway. With this I was able to build a TWRP for the 16GB junior. Unfortunately the touch screen was very buggy. Hard to get presses to take and especially to swipe. I'm not sure if its just mine or they are all like this. This devices looks quickly thrown together. It's version 1.0, not 1.0.2, or 1.2.3, just 1.0, the build.prop looks like they never even touched it. Maybe it can be fixed with software update(touchscreen firmware update), no kernel source so that route won't work, maybe I don't have the module bound right in TWRP. I'm not sure the recovery is entirely usable with this bad of touch response but let's see what other devices are like.
If you wish to use TWRP for Nabi Jr 16GB this would be the instructions. USE AT OWN RISK!
1) Enter fastboot mode
With the Nabi powered off press and hold power and volume down.
2) Unlock the bootloader. This will erase everything on the device.
Code:
fastboot -i 0x0489 oem unlock
after issuing the above look at the Nabi screen and use volume keys to OK the unlock.
3) Enter fastboot mode (as described above)
4) Test and/or flash TWRP to your device.
Extract the TWRP download and place recovery.img in the same folder as your fastboot.exe
Run the command to test out TWRP
Code:
fastboot -i 0x0489 boot recovery.img
or this command to make it permanent
Code:
fastboot -i 0x0489 flash recovery recovery.img
5) To boot TWRP from power off. Press and hold power and vol up(different then fastboot and vol down)
6) MAKE A BACKUP! If it's like mine the swiping will be hard to start the backup, but just do it. The Nabijr should be in an unmolested(unrooted) condition with your personal info erased if you followed this. I can guarantee one of your fellow Nabi JR owners will at some point needs this so help them and help yourself. Now put a copy of that backup on your computer.
7) When TWRP exits it will ask if you want to root the device. It is hard to swipe on mine, but you can do this instead of the motochopper. We had some trouble with the Gapps for 4.1.2 on XD, will be interesting to see if it works here.
TWRP 2.6 for Nabi JR 16GB
To get your recovery back to stock if you flash TWRP:
Stock Recovery for Nabi JR 16GB
device tree source: https://github.com/aicjofs/android_device_fuhu_juniorb
TWRP source: https://github.com/TeamWin/Team-Win-Recovery-Project/
If it works for everyone I will try and build an auto installer type script at some point, but no promises, I barely had free time to figure this out.

[GUIDE][BOOTLOADER,TWRP, ROOT]Lenovo TAB3 8/TB3-850F

This guide, for the Lenovo Tab 3 8" (TB3-850F), has 3 purposes:
1. Unlocking your bootloader;
2. Installing TWRP custom recovery;
3. Attaining superuser privileges (root) of the stock OS.
NOTE:
I can attest & confirm that this method has worked 100% on at least 7 devices of my own. Please read and re-read the instructions carefully before proceeding. If you follow this tutorial exactly as delineated, you should have no adverse issues in unlocking your bootloader, flashing custom recovery, or achieving systemless root of the stock Android OS.
MENTIONS & THANKS:
Based on XDA Senior Member @Hemphiz's groundbreaking root and custom recovery for this device, I am now revising this thread wth improved step-by-step instructions based on members' feedback and experiences. Thanks @Hemphiz for your research, assimilation of necessary files, and for breaking ground on this tablet. Thanks also for your granting me ownership of the thread. Your contributions are greatly appreciated by many. Thanks to the great @Chainfire for his flashable systemless rooting script. Thanks to @jemmini for compiling TWRP for this tablet. Finally, thanks to the many members who have tested this guide and provided much needed input & user experience.
DISCLAIMER: As always, please be reminded of the risk involved with flashing a custom recovery and/or attempting to attain superuser privileges of your Android OS. I will not be held responsible for devices bricked or otherwise rendered inoperable as a result of this thread. You assume full responsibility for any good or bad which may result from proceeding any further. However, with that having been said, I will provide any and all support possible. Read and follow the foregoing steps thoroughly and carefully prior to proceeding. NOTE: THIS GUIDE IS INTENDED ONLY FOR THE LENOVO TAB 3 8"/TB3-850F.
REQUIREMENTS:
1. Minimal ADB & Fastboot v1.4 (or newer) Windows Installer;
2. Windows PC or laptop (Mac may be used; however this guide is intended for Windows 7 and newer operating systems);
3. Official Lenovo USB Device Driver v1.1.21;
4. TWRP v3.0.1 for the TB3-850F;
5. ADB Driver Installer for Windows;
6. SuperSU v2.82-SR5 flashable zip.
(All files, drivers & utilities for this process are available in the below download link)
DOWNLOAD LINK: https://drive.google.com/folderview?id=1l-YN5aXmjDF3O1bHxFHVIxLKuvd847Q9
INSTRUCTIONS:
1. First and foremost, unlocking the bootloader is necessary. Also, this step is a good place to make some requisite preparations. Power on your Tab 3 and select SETTINGS once booted up. Go to ABOUT DEVICE, find BUILD NUMBER, and tap it 7 or 8 times until DEVELOPER OPTIONS is enabled. In DEVELOPER OPTIONS, tick OEM UNLOCKING and USB DEBUGGING. On your PC, install the Minimal ADB & Fastboot utilities, the ADB Driver Installer, and the Lenovo USB Driver Installer. Connect your Tab 3 to your PC with the supplied (or quality equivalent) OEM charging/syncing cable. Open a command window in your ADB/Fastboot directory, by holding SHIFT and right clicking in the desired path. In the command window, type: adb devices & press RETURN. If your device is connected properly, the command window will display a string of numbers/letters, which represent your device's serial number. If your serial number does not appear in the window, try changing USB ports, change syncing cables, or try reinstalling the ADB Drivers. Once properly connected, type adb reboot bootloader & press RETURN. Your tablet should boot into Fastboot Mode, which will be displayed in white bold letters on your device's display once complete. Once in Fastboot Mode, type fastboot oem unlock & press RETURN. Your device will prompt you to press Volume Up to proceed with unlocking the bootloader, or Volume Down to cancel the process. WARNING: UNLOCKING THE BOOTLOADER AUTOMATICALLY INITIATES A FACTORY DATA RESET. YOU WILL LOSE ANY UNSAVED VIDEOS, MUSIC, PERSONAL FILES, ETC.
2. Now that your bootloader is unlocked, you are ready to flash TWRP. Download the twrp.img file from my link and save it to your PC in the ADB/Fastboot path/directory. Also, save a copy of the file on your device's internal storage or external micro SD card. Since your device underwent a factory data reset, you will again need to enable DEVELOPER OPTIONS & tick OEM UNLOCKING & USB DEBUGGING as you did in Step 1. When you have done this, again open a command window, ensure a proper connecion, & type adb reboot bootloader & press RETURN. Once in Fastboot Mode, type fastboot boot twrp.img & RETURN. EXTREMELY IMPORTANT NOTE: this device's boot image is secured with dm-verity. Leave the /system partition as read-only when prompted by TWRP. Mounting /system as read/write at this point will result in a boot loop. Flashing SuperSU, as outlined in Step 3, will patch dm-verity and fix this.
From the TWRP main menu, select INSTALL, select the image file option in the bottom right of the screen, navigate to the location where you saved twrp.img in device storage or external storage, and commence the installation. Be certain and correctly choose "recovery" when prompted by TWRP. Now select REBOOT, then RECOVERY. Your TWRP custom recovery should now be successfully installed on your device's /recovery partition.
3. Now, it is time to root this tablet. Download & save a copy of the SuperSU v2.82-SR5 zip file to the tablet's internal or external storage. In TWRP main menu, select INSTALL & navigate to the saved SuperSU zip. Commence with installation. Systemless root mode will unpack, modify, repack and flash the patched boot image. Once done, reboot system. Your Android OS should now have full systemless root, and the /system partition may now safely mount as read/write.
TROUBLESHOOTING:
In the event your device becomes stuck in a bootloop, or is otherwise failing to boot into the OS, the following is a link to my stock firmware images thread for this device. NOTE: the following link will be beneficial only if your device successfully boots into Recovery/Fastboot mode. This link provides stock partition images of /boot, /recovery, /logo & /system. Typically, flashing the stock boot & system images will get you up & running again, and will restore the Android OS to stock condition.
https://forum.xda-developers.com/an...o-tab-3-8-tb3-850f-android-6-0-t3593043/page5
In the unfortunate event that you encounter a brick (your device fails to boot into the OS or Recovery Mode), please visit @r&xp's thread on unbricking your device & restoring it to factory stock condition. Members using his thread be sure to thank @r&xp. His collection of necessary files & comprehensive instructions has saved many, many bricked tablets. https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727

What is your software version?
Mine is TB3-850F_160412
i have a pending 51MB update ,do i complete all updates or ignore them and root?
Also whats the procedure to unroot if i want to get the updates later?

viv_jen said:
What is your software version?
Mine is TB3-850F_160412
i have a pending 51MB update ,do i complete all updates or ignore them and root?
Also whats the procedure to unroot if i want to get the updates later?
Click to expand...
Click to collapse
Look for build number. It's usally best to determine things. I'm on TB3-850F_S100030_161209_ROW
I took the latest OTA before flashing twrp else ota will fail due to the recovery being modified. For unroot there's an option in Superssu to unroot. I would personally create a full backup via twrp before rooting, so you can revert to it if you wish

this bricked my tablet

nox13666 said:
this bricked my tablet
Click to expand...
Click to collapse
Well you must've done something wrong. It's pretty much fool proof

Hemphiz said:
Well you must've done something wrong. It's pretty much fool proof
Click to expand...
Click to collapse
Great thread. OP's instructions & downloads work flawlessly. Thank you @Hemphiz

Thanks for the guide

Thanks for the guide!
Everything works but when I reboot into recovery I just get the dead android with no command under him..
I tried two times with same result Fastboot reports twrp flashes ok
Any ideas?
Thanks

Xecsc said:
Thanks for the guide!
Everything works but when I reboot into recovery I just get the dead android with no command under him..
I tried two times with same result Fastboot reports twrp flashes ok
Any ideas?
Thanks
Click to expand...
Click to collapse
Not to hijack the OP's thread but here are my thoughts. The dead Android indicates that TWRP did not successfully flash to your /recovery partition. Sounds like stock recovery is still installed. First, place a copy of twrp.img on your device's internal storage or on an external micro SD. Try this: instead of typing the command "fastboot flash recovery twrp.img", type " fastboot boot twrp.img" (assuming your twrp file is named twrp.img. If it isn't, rename it twrp.img for simplicity purposes). This command will temporarily boot your device into TWRP recovery. From the main menu on TWRP, select INSTALL. In the bottom right of the screen, select the option for "img" files. Navigate to where you stored "twrp.img" and select it. Install it to "RECOVERY" when prompted. Once it flashes, select REBOOT then select RECOVERY. Your device should now successfully boot into TWRP recovery.

MotoJunkie01 said:
Not to hijack the OP's thread but here are my thoughts. The dead Android indicates that TWRP did not successfully flash to your /recovery partition. Sounds like stock recovery is still installed. First, place a copy of twrp.img on your device's internal storage or on an external micro SD. Try this: instead of typing the command "fastboot flash recovery twrp.img", type " fastboot boot twrp.img" (assuming your twrp file is named twrp.img. If it isn't, rename it twrp.img for simplicity purposes). This command will temporarily boot your device into TWRP recovery. From the main menu on TWRP, select INSTALL. In the bottom right of the screen, select the option for "img" files. Navigate to where you stored "twrp.img" and select it. Install it to "RECOVERY" when prompted. Once it flashes, select REBOOT then select RECOVERY. Your device should now successfully boot into TWRP recovery.
Click to expand...
Click to collapse
I was running into the same issue after flashing twrp.img via fastboot, it kept coming up with no command when booting into recovery. Followed MotoJunkies advice and booted into twrp.img instead of flashing and installed it that way, now my device is rooted. Thank you Hemphiz and MotoJunkie.

MotoJunkie01 said:
Not to hijack the OP's thread but here are my thoughts. The dead Android indicates that TWRP did not successfully flash to your /recovery partition. Sounds like stock recovery is still installed. First, place a copy of twrp.img on your device's internal storage or on an external micro SD. Try this: instead of typing the command "fastboot flash recovery twrp.img", type " fastboot boot twrp.img" (assuming your twrp file is named twrp.img. If it isn't, rename it twrp.img for simplicity purposes). This command will temporarily boot your device into TWRP recovery. From the main menu on TWRP, select INSTALL. In the bottom right of the screen, select the option for "img" files. Navigate to where you stored "twrp.img" and select it. Install it to "RECOVERY" when prompted. Once it flashes, select REBOOT then select RECOVERY. Your device should now successfully boot into TWRP recovery.
Click to expand...
Click to collapse
Thanks worked perfect!

this did not work for me. now my tablet is in boot loop. keeps going to team win. trying to trying to mount storage and then back to the regular boot. over and over.

figgenhoffer said:
this did not work for me. now my tablet is in boot loop. keeps going to team win. trying to trying to mount storage and then back to the regular boot. over and over.
Click to expand...
Click to collapse
Hmmm. Did you execute "fastboot oem unlock" first to unlock your bootloader? It sounds as though you are saying TWRP installed correct? When you try to boot into the OS, you are getting reverted back to TWRP?

i did that. i had teamwin recovery. then installed the superuser.zip and it keeps looping

figgenhoffer said:
i did that. i had teamwin recovery. then installed the superuser.zip and it keeps looping
Click to expand...
Click to collapse
I see. The superuser zip is likely the culprit. Which one did you use? Did you use the one in the link? Here is a link for the stock boot.img for this device. Install it in fastboot mode by typing "fastboot flash boot boot.img". Try booting after flashing the stock boot image and also try reinstalling the boot script.https://drive.google.com/file/d/0B7-zQU1VihD3ZGZBRzU1Nm1PYjA/view?usp=drivesdk
Note: you will need to rename the downloaded file to " boot.img"

Thanks for the guide. Tried to do this on the Lenovo TAB3 10 Business, but no success
I can connect using the tools and enter into fast boot
When I flash, it seems successful, but after shutdown, start with power, volume buttons, I don't see the TWRP, but instead a kind of test app
When i use the other method to boot into the twrp, the Lenovo, boots normal, not into TWRP
Any ideas?

smouge said:
Thanks for the guide. Tried to do this on the Lenovo TAB3 10 Business, but no success
I can connect using the tools and enter into fast boot
When I flash, it seems successful, but after shutdown, start with power, volume buttons, I don't see the TWRP, but instead a kind of test app
When i use the other method to boot into the twrp, the Lenovo, boots normal, not into TWRP
Any ideas?
Click to expand...
Click to collapse
When you initially connect your Tab3 to PC and open a command window, did you execute both recognition tests? "adb devices" and "fastboot devices"? I am just curious as to whether your device is being recognized by both the fastboot and the adb platforms. Please try this and let me know.

This i what I with Lenovo Tab3 10 business
>adb devices
List of devices attached
8HSKCMT4PJIZ9HDZ device
>adb reboot bootloader
>fastboot devices
8HSKCMT4PJIZ9HDZ fastboot
At this moment, on the Lenovo Android you only see a smaal line at the bottom: =>FASTBOOT mode...
The fastboot does nt deisplay errors, but after the following command, the tablet just boots in the normal Android. On the Android device I also saw quickly the message "USB transferring OK" before booting
>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.192s]
booting...
OKAY [ 0.073s]
finished. total time: 1.269s
---------- Post added at 09:20 AM ---------- Previous post was at 09:03 AM ----------
On the Lenovo TAB3 10 Business I can also do the following:
Holding Vol up + Power when off and then releasing power when you see the Lenovo logo will bring up the following menu:
Select Boot Mode:
[VOLUME_UP to select. VOLUME_DOWN is OK.]
[Recovery Mode]
[Fastboot Mode]
[Normal Boot] <<==
With the recovery mode I see the following:
Android Recovery
Lenovo/LenovoTB3-X70L/TB3-X70L
6.0/MRA58K/TB3-X70L_S000020_170209_ROW
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Backup user data
Restore user data
Root integrity check
Mount /system
View recovery logs
Power off

smouge said:
This i what I with Lenovo Tab3 10 business
>adb devices
List of devices attached
8HSKCMT4PJIZ9HDZ device
>adb reboot bootloader
>fastboot devices
8HSKCMT4PJIZ9HDZ fastboot
At this moment, on the Lenovo Android you only see a smaal line at the bottom: =>FASTBOOT mode...
The fastboot does nt deisplay errors, but after the following command, the tablet just boots in the normal Android. On the Android device I also saw quickly the message "USB transferring OK" before booting
>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.192s]
booting...
OKAY [ 0.073s]
finished. total time: 1.269s
---------- Post added at 09:20 AM ---------- Previous post was at 09:03 AM ----------
On the Lenovo TAB3 10 Business I can also do the following:
Holding Vol up + Power when off and then releasing power when you see the Lenovo logo will bring up the following menu:
Select Boot Mode:
[VOLUME_UP to select. VOLUME_DOWN is OK.]
[Recovery Mode]
[Fastboot Mode]
[Normal Boot] <<==
With the recovery mode I see the following:
Android Recovery
Lenovo/LenovoTB3-X70L/TB3-X70L
6.0/MRA58K/TB3-X70L_S000020_170209_ROW
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Backup user data
Restore user data
Root integrity check
Mount /system
View recovery logs
Power off
Click to expand...
Click to collapse
Chances are the twrp isn't compatible with your device. Although the hardware all looks the same. Problem is my knowledge with Android development isn't that great. I simply read in my spare time. The twrp I found for this device on a previous xda thread, but it was more of a Q&A so I made this guide to simplify things for people. I do know that the original twrp was made here http://4pda.ru/forum/index.php?showforum=583

Worked great for me thanks. Had a few problems off at first but managed to get it done. First boot did take a little while but after that all is great

Oukitel K6000 Plus Twrp, Root

Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
Updates: ( All files from 4pda.ru )
Twrp Flashable zip Update to rom Version V9: https://yadi.sk/d/z8dbqfOM3Jk6w3
Twrp Flashable zip Update to rom Version V18 ( supersu integrated ) : https://yadi.sk/d/jlNSmqYN3L4xHK
I Flashed it over V9 without Wiping and it works for me lika a charm
Flashable Viper4Android : https://drive.google.com/file/d/0B5u-Eac1xV2CYUxqRmxFVkltNms/view?usp=sharing
If you dont need root you can flash V18 with SPflashtool:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
At this time there is no working twrp for V18
Custom Rom Doogee Shot (FreemeOS) : https://yadi.sk/d/YklP0V7b3LBFfV
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!
SPFlashtool FT V23:https://drive.google.com/file/d/0B1kz3pYtoOExemc0VkJtdXZRMVU/view
SPFlashtool FT V18:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
I also tried Magisk systemless on V9 and for me it works ( Working modules : Viper4android,dolby atmos,) but on V18 i cant install the new Magisk Framework and get bootloop
If Someone had Problems with SPFlashtool this is how i did it:
Install Spflashtool to C:
Copy flash file to C:
start spflashtool as Admin
select scatter file
{
"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"
}
BTW Sorry for my bad English XD

@Cheese-ass
Greetings and welcome to xda. All posts on xda must be in English, I have translated this one for you but please use google translate for all future post's
Regards
Sawdoctor
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted

There is a way to connect a lan usb adapter?

fantastic work like a charm, but used recovery download from the german one and worked rooted oukitel k6000 plus yea

i follow every step ( iread many times before i do it)
But Phone dosent boot anymore
I got only this Message on Display :
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
But Nothing happend
When i try to flash stock rom with splash tool i got da brom error with 60002
Its bricked???

Worked fine. I had to download files from other websites, but this procedure was good.
After reboot, su was working fine in /system. I wanted to reset the device completely, and typed "fastboot oem unlock"; I thought it would wipe data. Now, phone only boots on TWRP, and it seems like the /data partition is broken. TWRP can mount /system, but not /data. Either the device node is missig, or the partition is not formated properly.
Code:
# cat /etc/fstab
/dev/block/mmcblk0p6 /nvdata ext4 rw 0 0
/dev/block/mmcblk0p8 /protect_f ext4 rw 0 0
/dev/block/mmcblk0p9 /protect_s ext4 rw 0 0
/dev/block/mmcblk0p26 /system ext4 rw 0 0
/dev/block/mmcblk0p27 /cache ext4 rw 0 0
/dev/block/dm-0 /data ext4 rw 0 0
/external_sd auto rw 0 0
/usbotg auto rw 0 0
Losetup-a gives nothing.
I tried all possible commands (adb reboot to everything), and press volume up or down ... always get back in TWRP. Can not even reach the factory menu (the one where there are tests).
After reformating /data i can reboot to bootloader (fastboot), but still not /system.
Stock ROM was looking fine; I would like to be able to keep it. I would like to avoid flashing to an other ROM.

In short, I have TWRP and flashboot, but /system launches TWRP.
I don't know how to get a working system. SPFlashTool does not seem to work with TWRP installed. TWRP does not like OUKITEL_K6000_Plus_V6.0_20170519.rar. I can't find any ZIP ROM for TWRP. And when I try individual .img files from the RAR, TWRP can install them, but it does notproduce a working phone.
I fear something could be wrong with the partition table, or at least /data. /system contains many files and this looks good.
---------- Post added at 01:30 PM ---------- Previous post was at 12:40 PM ----------
How I fixed it:
fastboot flash boot /tmp/OUKITEL_K6000_Plus_V6.0_20170519/recovery-verified.img (EDIT: this MUST be wrong, should be fastboot flash recovery /tmp/OUKITEL_K6000_Plus_V6.0_20170519/recovery-verified.img or fastboot flash boot /tmp/OUKITEL_K6000_Plus_V6.0_20170519/boot-verified.img )
then, perform again https://fvknl.pro/k6000-plus-v6-0-upgrade/
and now I have a working phone.

* Can't apply Android updates because of TWRP+SuperSU ?
Now that my phone works, and is rooted (i use the stock ROM version 6), may 19th, the system is telling me there are system updates to do. I have downloaded them (200MB), but after reboot, update fails, for obvious reasons: the update is designed to be installed by the stock recovery firmware; and that partition is overwritten by TWRP.
I was given a tip to work around this (wherer the img file is taken from the .rar archive of the stock ROM):
# fastboot boot /tmp/recovery-verified.img
and it worked: fastboot uploaded the recovery image to the phone, ran it, and that recovery firmware started to apply the update.
Started ... but failed before half of it ... PROBABLY because /system was HEAVILY modified while I asked TWRP to install UPDATE-SuperSU-v2.82-20170528234214.zip (read the installation log of SuperSU ... it alters many things).
How can I apply my android updates without erasing the whole phone each time I want to apply them ?
A: how to get the installation log, to see the failure point, and fix it manually
or
B: install the update manually without running the recovery, but extract the update file, and manually copy the new files at due place, one by one
or
C: how to undo installation of SuperSU, so that /system is in a state where the update can be applied.
I want to do this without erasing /data, or /system. I had this issue on my previous phone; since december 2014 I could not apply any Android update; so my phone is stuck to Android 4 from december 2014. There have been many changes and updates during 2015 and I could not apply them. After installing su, i had been able to perform two Android updates; updates broke after installing Xposed. I do not want my new K6000 to have the same issue; I want to find a way to apply updates. And I would like to keep the stock flavour because there are many features I would like to use (don't want to install misc ROMs).

Xposed for oukitel 6000plus root
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio

no xposed for k6000 plus
patpix75 said:
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
Click to expand...
Click to collapse
sorry latest xposed is for sdk 25 and the latest firmware for this device is android 7.0 (Sdk 24)

patpix75 said:
Hi I have an oukitel 6000plus root. I can not find the way to install xposed. You have succeeded in installing it successfully? Send me my email address app and zip to use. Thanks Fabio
Click to expand...
Click to collapse
I have tried many random things; I forgot the details of it. The versions are not a problem; there are links around to download old installers. Even if latest Xposed is for Android 25, archives will let you download v24.
It also depends when you rooted your phone, and which updates you did on your ROM before rooting. Depends if you are using ROM v6, v9, or v18 ...
Also, even if Xposed is installed, it's not working properly; in particular, I wanted Xposed to NotifyClean, and this plugin could not be installed on the Xposed I have (download goes fine, but plugin complains I need reboot to activate it). So, in short, Xposed is useless for me for now. Some other plugins have installed correctly (Taskbar).
The Xposed I have NOW is version 87 by PurifyOS. ATM, Android API 24.
But I said I tried many random things, so, maybe having tried to installed other variations of Xposed by other people was important to have this one installed. I remember that at some point, trying to install this one (purify) failed, and then, worked later ... forgot why.

Error
When you try to upload a TWRP, a message pops up:
"error: cannot load 'recovery-twrp31jemini.img'"
Bootloader should be unlocked. I see a buzz when switching on "yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds"
Phone has a ROM v18
Application procedure on W10.
Does anyone find any solution?

You don't need to burn TWRP in FLASH to be able to use it. You just need to load and run it, this way:
fastboot boot recovery_TWRP-3.1.0.img
This way, if you have backup your whole phone, or downloaded and extracted a ROM, you can boot a stock recovery image:
fastboot boot /tmp/recovery-verified.img
According to your name jemini ... I thjink you have downlaoded the wrong TWRP. Boot and flash may fail if you grabbed a file for an other phone.
This should be ROM independant.
Since I rarely use TWRP, I now keep the stock recovery, and run TWRP from fastboot only when I need it; this way, stock recovery is available for Android updates.
Do you have links to ROM v18, so that I can download and install it directly, instead of having to burn v6, then update to v9 and v18 via update process ? I have issues with updates, and would like to flash directly using v18; but could not find a download link.

I got the phone today and unlocked it for root and everything.
After
Code:
fastboot oem unlock
the following showed up:
Code:
...
(bootloader) Start unlock flow
OKAY [ 14.791s]
finished. total time: 14.792s
Problem is now:
Orange state
Your device has been unlocked and can't be trust
Your device will boot in 5 seconds.
But it's not booting, just stuck at this screen.
Any help very much appreciated!
EDIT:
I was on V23 ROM which came per OTA.
EDIT-2:
I was able to flash it back to V23 with flashtool, but no root. Bootloader seems to be unlocked, the message still appears.

rom
"Custom Rom Doogee Shot (FreemeOS) :
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!""""
What do you say that this rom picks up on the oukitel k6000 plus ??

I need someone to help me my k6000 plus did not call any more after this procedure.
when I install the rom stock by flash sp this error appears
https://drive.google.com/file/d/0ByEkRDgYmbWtOXdpbngtcGJxQk0/view?usp=sharing

What do you want to do?
Flash the Stock ROM back with flashtool?
You should switch to "Download Only" and not "Firmware Upgrade".
Also the Download Agent was different when I flashed it, it was DA_PL.bin.

cojo11 said:
i follow every step ( iread many times before i do it)
But Phone dosent boot anymore
I got only this Message on Display :
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
But Nothing happend
When i try to flash stock rom with splash tool i got da brom error with 60002
Its bricked???
Click to expand...
Click to collapse
SIVAKUMAR: yes my mobile also same problem ...boot loop please help me oukitel k6000 plus MT6750T
------------- Orange State----------------
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds:crying:
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
sivakumarindia said:
SIVAKUMAR: yes my mobile also same problem ...MT6750T
------------- Orange State----------------
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds:crying:
Click to expand...
Click to collapse
SIVAKUMAR: I THINK THIS ROM DIFFERENT MT6750 AND MT6750T:crying:
---------- Post added at 11:19 AM ---------- Previous post was at 11:14 AM ----------
rolex0815 said:
i got the phone today and unlocked it for root and everything.
After
Code:
fastboot oem unlock
the following showed up:
Code:
...
(bootloader) start unlock flow
okay [ 14.791s]
finished. Total time: 14.792s
problem is now:
orange state
your device has been unlocked and can't be trust
your device will boot in 5 seconds.
but it's not booting, just stuck at this screen.
Any help very much appreciated!
Edit:
I was on v23 rom which came per ota.
Edit-2:
I was able to flash it back to v23 with flashtool, but no root. Bootloader seems to be unlocked, the message still appears.
Click to expand...
Click to collapse
sivakumar: My mobile also same condition boot loop

I got the same and this help me :
For this case, leave SP tool setting as normal. Before connect USB to device:
1. Press and hold vol +
2. Connect USB to device and hold vol + button.
3. Just release the button until you see the download process start working.
with this solution i have Flaht the v6 rom

Boot loop try this Back to STOCK ROM
Cheese-ass said:
Execution of this manual at your own risk !!!!
TWRP Install (Custom recovery to install the root files)
1. Install on pc adb and Fastboot driver
2. Install minimal adb and fastboot: https://forum.xda-developers.com/sho....php?t=2317790
3. On the smartphone in the settings, press the Developer mode (Settings-Over the phone-press 8 times on the build number)
4. Under Settings-Developer Options, allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
5. Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
6. Starts at Pc Minimal adb and Fastboot. In the command window "adb reboot bootloader" enter and press Enter (restart the smartphone into the bootloader)
7. WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty !!!! In the command window, type "fastboot oem unlock" and press Enter (turns the boot loader on). The smartphone sits back and restarts. Repeat steps 3 to 6 after restarting
8 Download the Twrp images: https://mega.nz/#!siZhjIKa!OSfglS4Q8...PgKY9vaxthuilo copies the recovery-twrp31jemini.img file to the installation folder of minimal adb and fastboot
9. In the command window, type "fastboot flash recovery recovery-twrp31jemini.img" and press Enter. After successful flashen enter "fastboot reboot" in the command window, press Enter and press the Lauter key on the smartphone (Bring the smartphone to the boot menu)
10. 3 options appear on the smartphone: Recovery, Fastboot, Normal with the Lauter key you navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)
11. The recovery is set to Russian, so press the 3ten button from the top (Settings) on the right side, then click on the language icon in the upper right corner and select your preferred language.
Smartphone Roots:
1. Download the root files: https://mega.nz/#!wyQVSbwL!m2arVJbjA...4Nn8LVhDb_AB9Q
2. copy the .zip file to your smartphone, press Install in the recovery, select the copied .zip file and confirm the installation. After flashing the smartphone restart and voila ... your device is rooted
Updates: ( All files from 4pda.ru )
Twrp Flashable zip Update to rom Version V9: https://yadi.sk/d/z8dbqfOM3Jk6w3
Twrp Flashable zip Update to rom Version V18 ( supersu integrated ) : https://yadi.sk/d/jlNSmqYN3L4xHK
I Flashed it over V9 without Wiping and it works for me lika a charm
Flashable Viper4Android : https://drive.google.com/file/d/0B5u-Eac1xV2CYUxqRmxFVkltNms/view?usp=sharing
If you dont need root you can flash V18 with SPflashtool:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
At this time there is no working twrp for V18
Custom Rom Doogee Shot (FreemeOS) : https://yadi.sk/d/YklP0V7b3LBFfV
Flash with TWRP at your own risk because i doesnt tried it at my own because V18 runs really smoooth
Expect some Bugs!!!
SPFlashtool FT V23:https://drive.google.com/file/d/0B1kz3pYtoOExemc0VkJtdXZRMVU/view
SPFlashtool FT V18:https://drive.google.com/file/d/0B1kz3pYtoOExSFZ5WGJraFNUYUE/view
I also tried Magisk systemless on V9 and for me it works ( Working modules : Viper4android,dolby atmos,) but on V18 i cant install the new Magisk Framework and get bootloop
If Someone had Problems with SPFlashtool this is how i did it:
Install Spflashtool to C:
Copy flash file to C:
start spflashtool as Admin
select scatter file
BTW Sorry for my bad English XD
Click to expand...
Click to collapse
SIVAKUMAR INDIA: BOOT LOOP TRY THIS BACK TO STOCK ROM OUKITEL K6000 PLUS MT6750T
----------------------------ERROR BOOT LOOP -------------------------------------------
Orange State
yor device has been unlocked and cant ve trust
your device will reboot in 5 seconds
---------------------------TRY THIS STEPS RECOVERED STOCK ROM--------------------------
step1: Vcom+SPD+and+adb+driver+Installer+Windows+8_10
INSTALL DRIVERS
step2; SP_MDT_v3.1732 (DOWNLOAD )
EXTRACT AND RUN SP-MDT FLASH ,
SCAN ---------CONNECT MOBILE------FLASH SUCCEED----
step3: OUKITEL_K6000_Plus_V23_20170726
THIS LINK AVAILABLE OLD VERSION SP_MDT ONELY SEARCH AND DOWNLOAD NEW VERSION SP_MDT_v3.1732
LINKS: https://www.oukitel.com/latest-software-rom-for-all-oukitel-devices-48.html

Database Info

welcome