Database Info

[How-To] All-In-One Guide For Asus Infinity (TF700) [25/03/2013]

** All-In-One Guide For Asus Infinity (TF700) - Rooting/Unlocking/NvFlash/Custom Recovery Install/Recover from Soft Bricks/Downgrading Firmware/Factory Restore/Various Tips &Tricks **
Warnings:
* I'm NOT responsible for any damage caused to your device by using these tutorials so use them on your OWN risk.
* Don't use the TF101&TF202 NvFlash solution/files or you will end-up with a very expensive brick.
* UPDATE [23/09/2012] AndroidRoot.mobi team released their tool to make NvFlash working on our device.If you want to unlock your bootloader and stay safe than i strongly advice to use this tool after unlocking,and before starting the "happy flashing" of custom roms and stuff,getting access to NvFlash will make your device BrickProof
* If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE
***This is a collection of guides collected from different threads on XDA Forum so credits goes to the original posters and all the people that shared precious knowledge here on XDA.Big THX to everyone.***
************************************************************************************************************************************************************************************************************************************************************************************************************
*** Rooting Your TF700 with Debugfs automated root ***
*This method works only with ICS roms
Note: Rooting will NOT void your Warranty!!!
Before you start make sure that:
* USB Debugging is activated (on your device go to Settings/Developer Options/USB debugging)
* Unknown Sources is activated ( on your device go to Settings/Security/Unknown sources )
* Make sure no other Android device is connected to your PC
* Make sure Asus Sync Tool is not running on your PC
========= Rooting procedure =========
1) Create a folder on your desktop an name it " TF700 Rooting " (you can use a different name but i will use this name in this guide)
2) Download Asus USB drivers and Debugfs automated root from here
3) Extract the downloaded files to TF700 Rooting folder
4) Power ON your device and connect it to a USB port on your PC
5) If Windows is asking for the drivers point the driver installer to the Asus USB drivers in the TF700 Rooting folder ... if not, install the ADB drivers from Windows Device Manager (if you don't know how to do it then you better stay off from rooting your device)
6) Open the TF700 Rooting folder and run RootDebugfs.bat (right click --> Run As Administrator)
7) Select option "1" and press "Enter"
8) Follow the instructions on-screen
DONE, if you did everything right your device will be rooted.
*** Rooting Method For Unlocked TF700T Devices ***
*This method can be used to root UNLOCKED devices on Jelly Bean.
************************************************************************************************************************************************************************************************************************************************************************************************************
*** Unlocking with Asus Unlock Tool ***
Warning: Unlocking WILL VOID the Warranty for ever and that's NO WAY to get back to a ORIGINAL condition/state.Also thats no reson to complain with Asus on this because the improper use of the Unlocked Bootloader could really damage your device (eg. bad kernel,bad overclocking ,flashing wrong stuff ... etc) .So read people,read and instead of flashing first and asking for help later just do the opposite,ask/read first and then flash.
Also,after UNLOCKING your bootloader you WON'T BE ABLE to receive OTA updates anymore,but you we will still be able to update your firmware manually ,using the latest Official version available on Asus site.
** Why unlocking? **
Unlocking the bootloader will give you more freedom to "play" with your device and more options to make it better.Here's why:
- Fastboot Mode will be now available (used to install recovery and more)
- You can install a custom recovery (you can install custom roms, do nandroid backups,etc)
- You can install custom roms (improved user experience)
Here's the Guide To Unlock Your Bootloaderhttp://forum.xda-developers.com/showthread.php?t=1795156
************************************************************************************************************************************************************************************************************************************************************************************************************
*** TF700 NVFlash tool ***
** What's this? **
NvFlash it's using "low level" access to your device (via APX mode) and it's the only tool that can help recover even from hardbrick but it's not provided or supported by Asus in any way,on the contrary,they are trying to do their best in order to stop us from using it,so basicaly without working NvFlash the only way you could recover your device from a hard brick would be sending the device to Asus and pay them for the repair.
But AndroidRoot.mobi team managed to get NvFlash working on our Infinity so you now have the possibility to make your device BrickProof,so a big THX to them.
Just follow the links bellow and please stick with the guide that AndroidRoot.mobi team provided,you will be just fine.
XDA original thread - [TOOL][BRICKPROOF]TF700 NVFlash release!
AndroidRoot.mobi team blog - NVFlash for Tegra3 – Transformer TF700T
Need Help with NvFlash? - Ask Here
TIPS/TROUBLESHOOT
* You are trying to flash the AndroidRoot bootloader but your device doesn't get recognized by Windows?
* Your device is recognized in Windows Device Manager but your FastBoot commands are failing?
* Your device is recognized in Windows Device Manager but you can't get Wheelie or NvFlash to work?
Most likely the above issues are the result of a missing or bad driver installation and the best way to fix is to manually uninstall the drivers from Windows Device Manager and manually install the drivers from the "Universal Naked Drivers" pack.
Also if you feel tired and it's late night ,maybe you should just get a good sleep and try NvFlash again tomorrow.
* You are trying to "bootstrap" NvFlash mode using Wheelie, but it keeps saying that "blob.bin is not found" when running "$ wheelie --blob blob.bin " command.
Just copy the "blob.bin" file from the "AndroidRoot" folder ,wich you can find on your internal storage and paste it in the same folder where Wheelie and NvFlash are located.
* When running the "$ wheelie --blob blob.bin " command on my PC with Windows7 i get an error saying " $ is not recognized as an internal or external command"
Just remove the "$" from the command,it's not used on Windows OS.
************************************************************************************************************************************************************************************************************************************************************************************************************
*** Custom Recovery Installation ***
Warning: Don't use Rom Manager to install a CWM Recovery,it will soft-brick your device!
Note: ATM there's only TWRP Touch Recovery available for Asus TF700 but works great .THX to TeamWin for their work .
UPDATE (14/09/2012) : CWM Recovery is also available now.THX to dasunsrule32
======== TWRP Recovery Installation ========
TWRP recovery works on both ICS and Jelly Bean firmware and it's an unified version for 32GB/64GB TF700T
There are two installation methods,the easy way using GooManager app and the hard way using Fastboot or ADB commands.Let's see how both ways work.
** Using GooManager **
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
** FastBoot Method **
1) Install Android SDK
2) Download TWRP Recovery blob and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Rename the downloaded file to twrp.blob and put the file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery twrp.blob
(more on fastboot http://wiki.cyanogenmod.com/wiki/Fastboot )
Here are more links/guides on how to install the recovery:
http://www.teamw.in/project/twrp2/105
http://forum.xda-developers.com/showthread.php?t=1798586
======== ClockworkMod Recovery Installation ========
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
(more on fastboot http://wiki.cyanogenmod.com/wiki/Fastboot )
************************************************************************************************************************************************************************************************************************************************************************************************************
*** Factory Restore after a softbrick/Downgrade from Jelly Bean to ICS/Clean Factory Restore ***
When You Need This?
* if you get stuck on Asus boot screen (the one with the spinning wheel)
* If you don't like JB and you want ICS back
* if you want to get back to a clean stock firmware
Note: You need to have a working recovery (stock or custom) in order to use this method.
========= Recover /Downgrade from Jelly Bean to ICS/Clean Factory Restore with stock recovery =========
1) Download the desired Asus stock firmware (based on your SKU,eg. ww 9.4.5.26 ) *** to downgrade from Jelly Bean you need the 9.4.5.30 firmware***
2) Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3) Rename the extracted archive to "EP201_768_SDUPDATE.ZIP" (without the " ") and upload it to a MicroSD card
4) Insert the MicroSD card in your tablet and use this button combination to Power ON and go to recovery --> Start the tablet by pressing Volume Down and POWER togheter for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire.
At this point the device will go in recovery and should start updating your firmware .
Note: Keep in mind that Windows doesn't show the known file extensions so most users don't have to put the .ZIP extension in the filename.
========= Recover /Downgrade from Jelly Bean to ICS/Clean Factory Restore with custom recovery =========
1) Download the desired Asus stock firmware (based on your SKU,eg. ww 9.4.5.26 ) *** to downgrade from Jelly Bean you need the 9.4.5.30 firmware***
2) Extract the .zip file somewere on your desktop
3)Rename the file to something like "recover.zip" uploade it to the root of your MicroSD card
4) Insert the MicroSD card in your tablet and use this button combination to Power ON and go to recovery --> Start the tablet by pressing Volume Down and POWER togheter for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire
5) From the recovery menu press Install and select the "recover.zip" file ...wait until the install process ends and then restart your device.
Note: Keep in mind that Windows doesn't show the known file extensions so most users don't have to put the .zip extension in the filename.
************************************************************************************************************************************************************************************************************************************************************************************************************
*** Firmware Downgrade & SKU Change ***
WARNING : Please keep in mind that this method is highly experimental on Asus TF700 but still was tested with success on TF 300 so should work on TF700 aswell, but you have to use the blobs for TF700 not the ones from the original thread. Use it on your own risk and please report here in any case.
************************************************************************************************************************************************************************************************************************************************************************************************************
*** Volume&Power Buttons combinations ***
Use this buttons for getting access to Recovery,Fastboot ,APX ,to do a Cold Boot and Wipe Data.
Note: Make sure your device is OFF before using this.
** Boot To Recovery **
Press Volume Down + Power untill you see a white text on the screen then release the buttons and press Volume UP (you have 5 seconds to do it)
Note: This works for both Stock and Custom recovery.
Note 2: On Jelly Bean you will have to press Volume UP right after the four icons (3 icons if you are still locked) will show .
** Cold Boot - FastBoot - Wipe Data Menu **
Press Volume Down + Power untill you see a white text on the screen then release the buttons.Use Volume Down to navigate and Volume Up to confirm your selection.You have 10 seconds to make your choise,or else the system will do a Cold Boot by default.
Note: FastBoot mode is available only if you unlocked the bootloader.
** Boot to APX mode **
Press Volume Up + Power for 5 seconds,the device will vibrate and your screen will be OFF.
Note: APX mode is needed if you want to use NVflash.
Note 2: Press Power button for 10 seconds to exit APX mode
************************************************************************************************************************************************************************************************************************************************************************************************************

Tips&Tricks / Frequently Asked Questions [18/08/2012 ]
**** Tips&Tricks / Frequently Asked Questions ****
[ Q ] I've just bought my device and my battery is empty/almost empty,do i have to charge it for 8 hours before i can use the tablet?
No,you don't have to wait 8 hours before start using your tablet just plug the charger and wait until it get to 10-15% of charge then you can start using your tablet.Mostly it will need 2 - 3 hours for a complete charge and you will see a green light led when the battery is full.
[ Q ] I'm planing to let the device charge overnight,is there any risk of overcharging and battery damage?
No,there's no risk of damage for your battery because once the battery is full it will stop charging so overcharge is not possible.
[ Q ] My battery drains very fast ,is there a way to improve battery live?
IMO battery life depends very much on the way we use our device so i guess there is no real answer for this.Many users are asking about battery life and how to improve so have a look at this threads:
Asus Transformer Pad Infinity Battery Life Discussions Thread
[HOW-TO] Battery saving tips
[ Q ] Do i always have to full discharge the battery before charging again?
Usually this is not needed for ion-lithium battery but if you do it once in a while it will help for better battery calibration.
[ Q ] Keyboard Haptic feedback doesn't seem to work even if that option is active
On your tablet please go to Settings / Language&Input / Android Keyboard Settings / Advanced Settings / and make sure that "Keypress Vibration Duration setting" is set to 60ms or more.
[ Q ] The speaker is not loud enough,it's there a way to make it louder?
Many of us are using Volume + and it works very well on TF700 so you should give it a try.Also you can find more info here
[ Q ] No Audio when watching an .MKV movie with the stock player
Many .mkv movies have DTS audio and this format is not supported by the stock player so you will have to use a 3rd party video player.Try BSPlayer,it supports DTS audio and many other formats.
[ Q ] I get very low benchmark scores
Go to Settings / Developer Options and disable " Force GPU rendering " option
[ Q ] My screen constantly adjusts brightness even if auto-brightness is disabled
Yes,that is a "feature" called Dynamic Contrast but not all of us like it.Follow the directions from this post to disable but keep in mind that your device must be rooted.
[ Q ] Minimum brightness level is to low when Auto-Brightness is ON,how can i change that?
If your device is rooted you can easly change the brightness level for Auto-Brightness mode,see this post
[ Q ] I'm having issues getting my MicroSD card to work with TWRP Recovery,possibile reasons?
That could me many reasons for this kind of issue but one reason could be a bad formatted card,see here
[ Q ] I have TWRP recovery installed and i would like to use an app to Reboot to Recovery,it's that possible?
Yes it's possible but NOT recommended because the application must send a custom command so if your recovery got corrupted somehow you could end-up with a bricked device...here's more info
[ Q ] I feel like i'm ready to try some Custom Roms now,are there any available?
Yes,our great user/dev are always trying to give us the bet for our device have a look at this Index thread
[ Q ] According to my battery stats,Wi-Fi connection drain my battery a lot,is this true?
Not really,the default battery stats are not accurate so probably it's showing wrong values so don't panic and read here
[ Q ] Stock recovery doesn't recognize my MicroSD card, any idea why?
Please make sure your MicroSD card is formatted in FAT32.
[ Q ] I don't need/trust the Asus Device Tracker service and i would like to disable it,is that possible?
Yes is possible to disable that service but keep in mind that is not yet confirmed if other services will be affected (OTA update or Bootloader Unlocking) and also your device must be rooted.You will find the disabling procedure here.
[ Q ] I would like to update the device via OTA update,any recommandation before i proced with the update ?
Some users reported isues (mostly boot looping or update failure) when applying and update on systems where system applications were disabled/freezed so i recommend you to enable these apps in case you have them disabled.

Manual ADB/APX Driver Installation for Windows OS
Manual ADB/FastBoot/APX Driver Installation for Windows OS
1) Put your device in Fastboot or APX mode or just boot normally (but make sure ADB debugging it's set on your tablet) for ADB and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where universal naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot or ADB driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
* If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
*Also you should disable UAC if it's enabled.

this is an absolutely vital post for any tablet owner!
Well done

Very nice top job

cheltenham2004 said:
Very nice top job
Click to expand...
Click to collapse
Thank you guys for your kind words,i'm glad you like my "by users for users" guide and i really hope this will help people from damage/brick their device and also make moderators life a bit better cause i know this forum gets very messy with time and it's quiet impossible to keep track of every useful informations in here.

Well done, it will surely help many XDA members, both newbies and "oldies"
I believe you should add info about the microSD having to be formatted FAT32 to work with stock recovery.

d14b0ll0s said:
Well done, it will surely help many XDA members, both newbies and "oldies"
I believe you should add info about the microSD having to be formatted FAT32 to work with stock recovery.
Click to expand...
Click to collapse
It's in, thx for the suggestion, any help is welcome here.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Deleted, wrong post.

If you root, will you still be able to receive OTA updates?

Sreenadh said:
If you root, will you still be able to receive OTA updates?
Click to expand...
Click to collapse
Yes, afaik you can receive ota updates even if you are rooted.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Asus tf700 not rooting
First I am not a noob. Rooted many phones. First Tab. Followed instructions to the T. Device will not load drivers when in recovery. What am I doing wrong.

wizardofkoz said:
First I am not a noob. Rooted many phones. First Tab. Followed instructions to the T. Device will not load drivers when in recovery. What am I doing wrong.
Click to expand...
Click to collapse
I came across this issue once and you need to manually install the ADB drivers from Windows Device Manager. Btw why do you need ADB in recovery mode?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

When I hold down the power and volume down for 5 secs this is where I end up. With an Android on his back with a triangle with an ! in it.
---------- Post added at 09:51 AM ---------- Previous post was at 09:11 AM ----------
ADB drivers are loaded. RootDebug tool says I need to load drivers. What else?

wizardofkoz said:
When I hold down the power and volume down for 5 secs this is where I end up. With an Android on his back with a triangle with an ! in it.
---------- Post added at 09:51 AM ---------- Previous post was at 09:11 AM ----------
ADB drivers are loaded. RootDebug tool says I need to load drivers. What else?
Click to expand...
Click to collapse
I don't know why you are trying to root in recovery mode, for rooting you have to start the tablet in normal mode with adb debugging and unknown sources enabled, that's all.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Got it. The first thread I read said to hold down power and volume down button and then run rootdebug tool. Then I tried without doing that and it still did not work. Tried running the tool with administrator privileges and still did not work. Deleted drivers from the computer through the device manager and started over. Ran the tool again and it finally worked. Don't really know why it didn't work the first 10 times, but finally it loaded and ran. Now I am rooted. THanks.

So rooting the device does not void warranty but unlocking the bootloader does? I thought the main purpose of rooting phones/tablets was to install custom ROMs, like I did with my smartphone.
I'm such a noob

Pretoriano80 said:
I don't know why you are trying to root in recovery mode, for rooting you have to start the tablet in normal mode with adb debugging and unknown sources enabled, that's all.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
This is not clear from reading #6 in the OP:
6) Open the TF700 Rooting folder and run RootDebugfs.bat (right click --> Run As Administrator Start the tablet by pressing Volume Down and POWER togheter for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire.
At this point the device will go in recovery and should start updating your firmware .
Click to expand...
Click to collapse
No harm though, after a re-boot it worked like a charm. :good: Thanks guys!

esoxx said:
This is not clear from reading #6 in the OP:
No harm though, after a re-boot it worked like a charm. :good: Thanks guys!
Click to expand...
Click to collapse
Your are right that part shouldn't be there and i don't know how it got there. I already had to restore half of the content in OP because has disappeared and i still don't know how (but i have a backup of this guide on my pc so restoring was easy) that could happen.
Anyway thx for pointing that (that part is valid but for a restore with stock recovery) i will remove that part asap.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Thanks so much for the guide. I was using the LCD Density App and that thing jacked my Infinity up big time. I will never use that application again. It wanted SuperUser clearance to save the Pixel Density, then when I checked Save & Reboot, my Infinity never turned on again. It just got stuck at the ASUS screen and wouldn't turn off. If I tried to power down, it just turned back on and stuck at the first Asus Screen.
I used the following directions and was able to get back to stock firmware.
Thank god.
*** Factory Restore after a softbrick ***
When You Need This?
* if you get stuck on Asus boot screen (the one with the spinning wheel)
Note: You need to have a working recovery (stock or custom) in order to use this method.
========= Recover with stock recovery =========
1) Download the latest firmware from Asus site (based os your SKU,eg. ww 9.4.5.26)
2) Extract the .zip file somewere on your desktop (the result will be another .zip file,use it for step 3)
3) Rename the extracted archive to "EP201_768_SDUPDATE" (without the " ") and upload it to a MicroSD card
4) Insert the MicroSD card in your tablet and use this button combination to Power ON and go to recovery --> Start the tablet by pressing Volume Down and POWER togheter for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire.
At this point the device will go in recovery and should start updating your firmware .
So yeah, thanks for this guide and beware of the Pixel Density Application. I know someone from here created it, but It could not have been more clear that it messed my tablet up since I had never had a problem until I gave it SuperUser Clearance then it never turned on again.

[NEW ROOTING METHOD] Trekstor Surftab Ventos 8, 9.7 and Breeze 7

Instructions for the Surftab Breeze 7:
In this case it's really easy to get the tab rooted. It already has the su binary installed Get SuperSU from market and let it do the rest.
Instructions for the Surftab Ventos 8:
Big news!
I made it to make another rooting method without the use of any 3rd party software!
It's also not important which OS you are using.
Pre-requisites:
Get a Micro SD card! (up to 8GB as it seems that more than 8GB cannot be used to activate CWM)
Instructions:
1. Get my custom clockworkmod recovery zip from this thread: http://forum.xda-developers.com/showthread.php?t=1995984
2. Unpack the zip file on the root of your micro SD card (there has to be a file named uImage_recovery now)
3. Download the attached signed_SU.zip file and put it either on your internal or external SD (do NOT unpack it)
4. Shutdown your Tab
5. Keep Volume- pressed and tap the power button (while still keeping the Volume- pressed) until you see the clockworkmod menu
6. Choose "install zip from sdcard"
7. Depending on the fact where you have the zip stored, select either the internal or external card
8. Select the zip and confirm its installation with "Yes"
9. After the script finished, hit reboot and check if you have SuperSU installed
This should be it
To do:
I'll make a new thread helping in installing the Playstore without having to root our ventos tablets.
After the tablet rebooted twice you should see SuperSU now as installed application. Now you just need a working play store apk and move it into the system partition (don't forget chmod to 644) to get the Play store running.
Instructions for the Surftab Ventos 9.7:
As I don't have anyone with a rooted 9.7 at the moment (to get a dump of the stock recovery), I can't make a working CWM to get the below signed_SU.zip flashed, sorry! Only the old rooting method listed below only works at the moment (if moborobo is in a good mood )...
As usual I don't take any responsibility for bricked devices (but I assume that the chances of bricking are nearly impossible)
If you have any questions, let me know!
Old Rooting method:
Code:
Hi,
I know, many of you don't know these tables at all. But as far as I know, these are only available in Germany at the moment.
Anyways, I think it is helpful for my German colleagues to know how to root these tablets as they don't need to search for hours and hours until finding a solution that is suitable (as I did :-/ ).
The Windows way:
Pre-requisites:
0. A Windows PC
1. Download Moborobo ([URL]http://www.moborobo.com/download/[/URL])
2. Install any Updates Moborobo needs to install
3. Download the latest release of bin4ry's universal rooting for most ICS and JB phones/tablets ([URL]http://forum.xda-developers.com/showthread.php?t=1886460[/URL])
Thanks to bin4ry by the way :)
4. Download my modded Runme.bat
Instructions:
1. Unpack the 7z Archive from point 3 into Moborobo's installation folder. The result should be that you have a new folder "stuff" and a runme.bat and runme.sh in the Moborobo folder
2. IMPORTANT: Unpack my modded runme.bat into the MoboRobo folder and delete the original batch file
3. Start Moborobo and ignore any exceptions which are thrown out (at least my Visual Studio nagged me all the time, and no, I wasn't willing to debug the application :p )
4. Connect the Tablet to the PC and wait until Moborobo says that it is connected
5. Then start the modded Runme.bat and follow the instructions (select the first option by the way, which says "Normal")
6. Watch the screen, you need to click on Restore on your tablet (without any passwords)
7. See the magic happen
The Linux way:
Here is the feedback of an owner of a Trekstor Ventos 9.7:
[QUOTE]
Hi,
[...]
I am using Linux (old Fedora 15), I used Root_with_Restore_by_Bin4ry_v15.zip without any modifications to root the device. I ran the unix shell script that is provided in the package and selected option 1 for rooting, just as you suggested. I did not really understand why you needed the mobo tool, Bin4ry's script seems to work out of the box.
After that I installed SuperUser with latest busybox, terminal app and a console version of openssh, all that also works just fine.
I did not try Google Play or any other market, I use the device without a Google account, so I actually removed the preinstalled AndroidPit market and got rid of everything that wanted to collect my personal data.
I hope some day I can post in the thread but right now I do not see anything else where I could participate to gather those annoying 10 posts.
Again, thanks for your initial walkthrough, it gave me the hints I needed.
Kind regards,
Jin
[/QUOTE]
Regards
TheSSJ

DOES the Play Store work on your device???
All other sources on the net say that the Play Store is not possible on the device...
Gesendet von meinem Nexus 7 mit Tapatalk 2

Yes,it works. but only if you root your tablet. Also it's important to move the playstore.apk into the system partition...DON'T INSTALL IT like a normal apk...
Then reboot and you're done..if you need help pm me..

Can confirm that this method is also working with the 7" Breeze. Moborobo was not able to recognize the device, but manual install of a ADB driver for the Breeze showing as non-working "Android" in the system settings device table enabled it to see it. From there rooting was indeed a "breeze" Play Store and USB devices on host working fine. Great job, thanks for sharing!

Lucas0511 said:
Can confirm that this method is also working with the 7" Breeze. Moborobo was not able to recognize the device, but manual install of a ADB driver for the Breeze showing as non-working "Android" in the system settings device table enabled it to see it. From there rooting was indeed a "breeze" Play Store and USB devices on host working fine. Great job, thanks for sharing!
Click to expand...
Click to collapse
Oh this sounds good...I was searching for a method to manually install the adb driver for our tablets...can you share how you did this? it sucks having moborobo always running for a little adb work...

I had ADB installed previously with the latest Android SDK as fastboot was acting up on my Win 8-64bit. So the devices manager in settings was already showing a not properly installed Android USB device. I changed the USB connection on the Breeze to "MTP" , and in the computer device list chose to update the driver for this USB device manually - and then chose to search computer for drivers. Under Android USB devices I chose Android ADB Interace (Google ADB driver 7.0.0.1 previously installed with the SDK) - and was able to see the device as ST70104-1413fc082 with "adb devices" from the computer. Its funny, we both speak German, trying to explain in English... . Hope it helps.

Yes,indeed funny
Thank you for your explanations..if i get adb to work too i will update my guide
Thanks again
Edit: doesn't work unfortunately but i heard that on Linux it isn't a problem to get adb running properly...

didnt work for me
hi
I just saw this post and tries doing s instructed but:
1-couldnt get into recovery mode ! I tried the volume down button but it would boot the tab into safe mode
2-tried volume up button but it goes to a black download mode screen and restarts.
3-tried the other method through Moborobo but that didnt work either , it tells me it succeeded but there is no root.
by the way I have the 8" on Jellybean
I just want a way to make more space or install aps on my SD card

Has anyone successfully rooted a Trekstore Surftab Ventos 7.0 HD with some of the above mentioned methods? I've tried both bit without success....
The reason for me wanting to root is to get Tasker running on it. It depends on some google maps framework. The 7.0 HD has playstore and maps but i suppose something is missing and I have to root to get the missing files.
If anyone has some advice I'll be very glad. Cheers
Sent from my GT-I9300 using Tapatalk

Is there a difference between the ventos 7 and the ventos 7 breeze? And are there any KitKat ROMs available?

Beginners Guide to root and flashing a custom ROM on the TF700T

Last edit: Jan 2, 2018
The information here can be found in many places on the web and several forums. But when I started flashing custom ROMs about two years ago, I got frustrated many times because I found that information to be scattered, fragmented and in many cases outdated.
I hope this guide will make it a little easier for those users who wish to unleash the potential of this tablet but have no idea where to start. This is meant to be for inexperienced users who may be flashing for the first time.
If you find information I provide here to be incorrect or outdated, please do chime in!
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames.
YOU DO THIS AT YOUR OWN RISK
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF700 involves three steps:1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery​Rooting is optional
To install a custom ROM it is not necessary to root the tablet. You do have to unlock the bootloader and install a custom recovery no matter what, but in my opinion rooting is an unnecessary step since any custom ROM you flash will be rooted anyway.
But if you want to root the TF700 on stock firmware there are three ways to go about it:
Up to firmware version 10.6.1.14.8 you could use a tool called Motochopper to root the TF700. Asus plugged the hole Motochopper exploited in the last firmware update.
For firmware version 10.6.1.14.10 there is Kingo Android Root (only works on Windows AFAIK).
And then there is Towelroot, a one-click-root exploit. It's an apk, so no PC necessary. Only Towelroot v1 works for the TF700 and it's hard to find. My dog ate the copy I had..
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Download the Asus Unlock Tool v7 from here: https://www.androidfilehost.com/?fid=817550096634776735
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
If you get an unspecified "network error" you could be in for some major headaches. Many tablet's serial number and/or the mac address of the mainboard seem to be registered incorrectly in Asus database. This problem is widely discussed on several forums, just google: "cannot unlock TF700" or similar and read the threads. Too many variables to discuss this here...
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
To determine if you need to update your bootloader read post #3
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!​
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8.+ you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
TROUBLE WITH ADB FASTBOOT DRIVERS? SALVATION IS NEAR!! (May 2017 edit)
And it is called FWUL (F-orget(?) Windows Use Linux) a great Arch Linux distro that you can boot off a USB stick or CD with simple adb fastboot all setup for you. Follow the instructions, set your boot sequence to boot from USB or SD drive first and disable Secure Boot in your BIOS Security settings. I have fought with Windows driver problems as long as I have been using Android devices and some stuff I never got to work. With this baby I was able to connect to 4 different Android devices with no problems at all. A beauty! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8/10: Inside that folder Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
If all of the above fails follow these instructions: https://www.michaelcrump.net/power-tip-for-windows-users-open-command-prompt-here/
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the Google Universal Naked Drivers. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://twrp.me/devices/asustransformerinfinityTF700T.html
Download the latest version of TWRP. Version 2.8.0 or later is ready for KitKat and Lollipop custom roms as well as backward compatible with JB ROMs.
FYI ONLY: If you for whatever reason want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Formatting data is only necessary in cases of data corruption.
Place the TWRP file into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery <name-of-file>
This will flash the recovery to the recovery partition
Example:
If the file is named TWRP_2.8.6.2_TF700_recovery.img, the fastboot command is:
Code:
fastboot -i 0x0B05 flash recovery TWRP_2.8.6.2_TF700_recovery.img
You can rename the file to something easier to type, but file name and fastboot command have to match.
So if you renamed the file to twrp.img:
Code:
fastboot -i 0x0B05 flash recovery twrp.img
If your recovery comes as a blob:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
Booting back into the (not rooted) stock rom you may get a dialog from TWRP asking you if you want to root.
You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
Touch "Backup", leave the default selection as they are and swipe the button to create a nandroid (a backup) of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: Transformer TF700 Android Development - xda-developers or check out post #2. There's a description of the most popular roms for this tablet.
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you

ROMs for the TF700
Update June 2017:
Time moves on and this tablet is till alive....
Most of the roms below are ancient by now. One dev, the legendary timduru, is still working for this tablet and currently supporting Nougatella, Android 7.1.2 for this tablet.
Skip to here if you are thinking about a current rom: https://forum.xda-developers.com/showpost.php?p=72540013&postcount=346
Click to expand...
Click to collapse
KatKiss-KatshMallow by timduru (MM on the TF700 - who would have thought?) is still under intermittent but active development and it is a beauty. Multi-window support anyone?
http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
CROMi-X is based on the latest Asus firmware (JB 4.2.1) for this tablet with many, many tweaks and improvements, but since there have been no further Asus updates, development on this rom has stopped. This rom would give you the most Asus-like experience on this tablet.
http://forum.xda-developers.com/showthread.php?t=2425383
And here is the recent incarnation of this rom: CROMi-X Resurrected: http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
@LetMeKnow still releases a new teak here and there, so keep following the thread.
Development on all of the following roms has stopped. The devs have moved on to other devices
CROMBi-KK is based on CM11 and tweaked for this tablet but a little buggy. The later LP based roms from the same team are definitely better.
http://forum.xda-developers.com/showthread.php?t=2672751
CyanogenMod is build from the ground up, CM10.x emulating JB 4.3, CM11 emulating KitKat (JB 4.4). CM was not build with a transformer (keyboard) in mind, but the dev has ironed out most of those bugs.
http://forum.xda-developers.com/showthread.php?t=1957660
ZOMBi-X: From the same team that developed CROMi-X and CROMBi-KK. Based on OMNI rom with multi-window support.
http://forum.xda-developers.com/transformer-tf700/development/rom-t2857931
ZOMBi-POP The (almost last) project from the CROMI/CROMBi/ZOMBi team. It's Omni based Lollipop for the TF700
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
A note: This rom will run with data formatted to ext4, which is the OEM default. But it benefits from /data on F2FS, the new file system developed by Samsung, more than any other rom before it. Changing the file system for /data to F2FS has become very easy since the TWRP team build support for it into their recovery. I wrote a guide for converting your data partition to F2FS here:
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
That same team took one final stab at a 6.0 rom for this tablet: http://forum.xda-developers.com/showpost.php?p=65968239&postcount=3719
But I would call this definitely an unfinished product with a doubtful future.
CM12 I don't run CM roms - try it for yourself
http://forum.xda-developers.com/transformer-tf700/development/rom-cyanogenmod-12-0-t3006624
OmniROM by lj50036 who's on the ZOMBi team
http://forum.xda-developers.com/transformer-tf700/development/rom-omnirom-tf700t-t3056438
There are quite a few more variants, check them out in the XDA Development forum and don't forget to make a nandroid before flashing anything new
AND IF YOU LIKE YOUR NEW ROM, SHOW YOUR APPRECIATION AND DONATE TO THE DEVELOPER!
Alternative methods to install TWRP
Edit February 2015
In this section I originally explained how to flash TWRP to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work sometimes (and if you have root), but I will not recommend or promote them any longer.
Why?
Because I'v read too many stories about these apps failing, even flashing to the wrong partition - you name it.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
I have spent quite a few hours helping users who got themselves into a situation where the only thing they could access on their tablet was recovery, but they did not know anything about adb/fastboot and did not set it up when the tablet was still working. To get it to work with a soft bricked tablet is much, much harder!!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.

HOW TO UPDATE YOUR BOOTLOADER
The last official Asus firmware update to JB 4.2.1 brought us to the 10.6.1.14.10 bootloader - and it will be the last one we ever get since there will not be any Asus firmware updates anymore.
If you are on an older bootloader and want to run a KK or Lollipop ROM, you should update your bootloader to this version.
Determining which bootloader you currently have
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.14.10-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.14.10 is your bootloader version
20130801 is the build date (and immaterial in most cases).
Updating your bootloader
Still on stock with stock recovery:
Just OTA update to the last Asus firmware or flash it manually.
Custom ROM with custom recovery
Either:
1. Flash Asus stock firmware in your custom recovery
Download the official Asus firmware, unzip it once, flash that second zip in TWRP or CWM.
The distinct disadvantage of this method is that you will loose your custom ROM and your custom recovery and you will have to reflash them, but it works to get you onto the latest bootloader - or the latest stock rom if you desire to return to stock​Or:
2. Flash only the bootloader in recovery
This is what I would recommend you do.
Go here for a collection of flashable bootloader/recovery packages: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
If all you need is the latest US bootloader, go to post #3.
The packages (bootloader + recovery) will replace not only your bootloader, but also your current recovery with whatever the TWRP version in the package is.To flash a KK or Lollipop ROM afterwards you need TWRP 2.8.+.
If you choose a bootloader package with an older recovery, you need to flash the latest TWRP version after you flashed the above bootloader package. In between you have to reboot (do not skip this step!)​

sbdags said:
@moderator could we sticky this please.
Brilliant post Bernd
Click to expand...
Click to collapse
Damn -you beat me to post 3! LOL
But thanks - almost everything I know about Android I learned following your lead.

berndblb said:
Damn -you beat me to post 3! LOL
But thanks - almost everything I know about Android I learned following your lead.
Click to expand...
Click to collapse
Yes after I posted I wondered if I was jumping the gun.... Maybe a mod can sort it for you? Sorry!
Mod edit: I deleted your previous post to give the third post to OP. I will copy paste it here.
@stamatis could we sticky this please.
Brilliant post Bernd :good:

sbdags said:
Yes after I posted I wondered if I was jumping the gun.... Maybe a mod can sort it for you? Sorry!
Click to expand...
Click to collapse
No problem. You "jumping the gun" is an honor to me.
Thanks

Well written and very informative post. Thread stuck.

please help
Yes i am a total noob goober.:cyclops:.I want to unlock root and flash my tf700 ..I have watched plenty of youtube vids and read how to do it, enough to where i think i am comfortable. Well I downloaded the file from asus website to unlock the M8 and it wont open on the tablet. It says file not supported. So i tried to download it on my computer and transfer it over, well my computer cant install the drivers for my tablet..urgghh.. So I saw an older article saying it would work if we downloaded the M7 file, Well that downloaded and worked I was able to open and go through the prompts, I signed away and clicked ok.. Yet another error...Which I read might happen, but I tried 20 or so times and still nothing. Am i way over my head in this, It sounds so simple to do...Any help or am i a lost cause?
Thanks

blackc3 said:
Yes i am a total noob goober.:cyclops:.I want to unlock root and flash my tf700 ..I have watched plenty of youtube vids and read how to do it, enough to where i think i am comfortable. Well I downloaded the file from asus website to unlock the M8 and it wont open on the tablet. It says file not supported.
Click to expand...
Click to collapse
I think you mean v8, v7 for the Asus Unlock tool?
You have to extract it. On the tablet you can use the app ES File Explorer from the Play Store. It downloads as a .rar file, the result has to be an apk
So i tried to download it on my computer and transfer it over, well my computer cant install the drivers for my tablet..urgghh..
Click to expand...
Click to collapse
You have to get the drivers working - no excuses
Without working drivers you cannot push a recovery to your tablet. What Windows version do you have?
Try installing the Asus PC Sync Utility, try the Google Naked Drivers, try the ones attached to this post (note: I have not tested these myself) - you will have to find the correct combination for your PC yourself.
Here are a few links that may be helpful.
http://www.addictivetips.com/window...-or-device-drivers-manually-in-windows-vista/
http://forum.xda-developers.com/showthread.php?t=2670645&page=3
So I saw an older article saying it would work if we downloaded the M7 file, Well that downloaded and worked I was able to open and go through the prompts, I signed away and clicked ok.. Yet another error...Which I read might happen, but I tried 20 or so times and still nothing. Am i way over my head in this, It sounds so simple to do...Any help or am i a lost cause?
Thanks
Click to expand...
Click to collapse
No. You just got started!
Here are a couple of different approaches if you cannot unlock:
http://www.transformerforums.com/fo...discussion/42587-my-unlocking-experience.html
http://forum.xda-developers.com/showpost.php?p=51210808&postcount=6

Thanks for the guide,
everything went smooth until this step:
fastboot -i 0x05B0 flash recovery twrp.blob
Now my cmd just hangs there (been like 10 mins), not sure if i should restart tablet or cmd? Tablet still in fastboot screen. Thanks.

What do you get with this command:
fastboot devices
Sent from my K00C using Tapatalk

berndblb said:
What do you get with this command:
fastboot devices
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
It recognizing it correctly (atleast from what I understood from the guide). If it matters, I installed twrp 2.7 instead since it indicated 2.6.3.2+
I get:
015d2bbce9141e18 fastboot
Can I safely reboot/close cmd and try again?

Yes. Ctrl C will cancel the command, you should get the command prompt back.
Strange... twrp.blob is in the same folder as your fastboot.exe, right?
Sent from my ASUS Transformer Pad TF700T using Tapatalk

Wait! There's a typo in my post!!! LOL!
And you are the first one to notice it!
Try
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
OP updated
Sent from my ASUS Transformer Pad TF700T using Tapatalk

berndblb said:
Wait! There's a typo in my post!!! LOL!
And you are the first one to notice it!
Try
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!

droijo said:
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
Click to expand...
Click to collapse
He, he, he - always wondered about that "-i 0x0B05" bit. I had this guide (including the typo) up on a different forum for months and quite a few people followed it successfully. I suspect
Code:
fastboot flash recovery twrp.blob
would work just as well.
Off to test it....
Edit: Yep - the above command just flashed TWRP 2.7 to my tablet without a hitch. So fastboot seems to totally ignore the -i 0x0B05 part (which is the Asus vendor ID).
Anybody know why every reputable website out there (e.g. TWRP, Androidroot) has it as part of the fastboot commands?
Sent from my ASUS Transformer Pad TF700T using Tapatalk

berndblb said:
He, he, he - always wondered about that "-i 0x0B05" bit. I had this guide (including the typo) up on a different forum for months and quite a few people followed it successfully. I suspect
Code:
fastboot flash recovery twrp.blob
would work just as well.
Off to test it....
Edit: Yep - the above command just flashed TWRP 2.7 to my tablet without a hitch. So fastboot seems to totally ignore the -i 0x0B05 part (which is the Asus vendor ID).
Anybody know why every reputable website out there (e.g. TWRP, Androidroot) has it as part of the fastboot commands?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
A question for @_that as I always thought you needed the ID. Maybe not?

sbdags said:
A question for @_that as I always thought you needed the ID. Maybe not?
Click to expand...
Click to collapse
Apparently there was an older fastboot version that needed it. I've not used the ID for a long time.
It doesn't matter if you use 0x0B05 or 0xb05, it's the same number.

Great tut.
Thanks for posting. Good info, very concise.
berndblb said:
I hope this guide will make it a little easier for those users who wish to unleash the potential of this tablet but have no idea where to start. This is meant to be for inexperienced users who may be flashing for the first time.
If you find information I provide here to be incorrect or outdated, please do chime in!
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here or if my instructions are dead wrong. I may be a fiend who's going for the world record in tablets bricked. Do your own research, read thrice, ask twice, flash once.
YOU DO THIS AT YOUR OWN RISK
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
Basically the process of flashing a custom ROM on the TF700 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using the custom recovery​
Rooting is optional
To install a custom ROM it is not necessary to root the tablet. You do have to unlock the bootloader and install a custom recovery no matter what, but in my opinion rooting is an unnecessary step. However - as of today, Feb 27, 2014, another path to installing a custom recovery opened up (again) and that method (using GooManager to install TWRP - see below) requires you to be rooted.
So if you want to root the TF700 on stock firmware there are two ways to go about it:
Up to firmware version 10.6.1.14.8 you could use a tool called Motochopper to root the TF700. Asus plugged the hole Motochopper exploited in the last firmware update.
For firmware version 10.6.1.14.10 there is Kingo Android Root (only works on Windows AFAIK). There was some controversy around Kingo. Late last year their threads on XDA got closed because they used the vroot method which had a sniffer component that collected information and sent it to servers in China. The developers of Kingo removed vroot and worked it out with XDA. Their threads got re-opened in December. So I believe Kingo is safe to use - but you be the judge of that....
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: ASUSTeK Computer Inc. -Support-
Select your device, choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v8 (I assume you are on JB 4.2 firmware)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you or use ES File Explorer on the tablet
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. For now I assume it goes ok.
To check if you are unlocked, boot the tablet and read the tiny script. It should say: This device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up.
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows 7/8:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
This is not confirmed to work on Win 8.1, but that may be due to the driver signature verification in Win8. Google how to turn it off.
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for the adb folder) and the corresponding drivers. Takes about 15 seconds
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Linux and iOS: Check out this site https://code.google.com/p/adb-fastboot-install/ or this [GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers
The fun begins
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
In Win XP select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
All Windows versions: In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the Google Universal Naked Drivers.
Let's assume everything is good:
On your computer go here: Techerrata Downloads - Browsing tf700t
Download the correct TWRP version for the ROM you intend to flash (see list below)
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe.
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
Booting back into the (not rooted) stock ROM you may get a dialog from TWRP asking you if you want to root.
You can accept or cancel it - doesn't matter. I assume you are going to install a custom ROM and they are rooted anyway.
Alternative methods to installing TWRP
A) The app GooManager, free in the Play Store, downloads and installs TWRP (currently version 2.6.3.1) on the TF700. But GooManager requires root AND the bootloader to be unlocked. For users who are rooted already or those who cannot get ADB and fastboot to work on their PC, rooting with Motochopper or Kingo and then using GooManger to install TWRP may be a good alternative.
B) sbdags, the developer of CROMi-X (probably the most popular ROM for this tablet) provided a tool that automates the fastboot commands necessary to install a recovery..
I personally believe it is essential to have a working fastboot connection from PC to tablet and becoming familiar with basic fastboot commands when you develop a flashing habit, but if you want to take a shortcut his tool is here: http://forum.xda-developers.com/showthread.php?t=2646279
ROM – Recovery combinations
I assume you are on the 10.6.1.14.10 bootloader
CROMi-X – TWRP 2.6.1 or later http://forum.xda-developers.com/showthread.php?t=2425383
CROMBi-KK – TWRP 2.7.0 http://forum.xda-developers.com/showthread.php?t=2672751
NOTE: Formatting data in TWRP 2.7 takes a lot longer than in previous versions (up to 90 minutes). DO NOT INTERRUPT THE PROCESS if you format /data (usually only necessary with data corruption)
CM11 – CWM 6.0.4.6+ http://forum.xda-developers.com/showthread.php?t=1926286
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet.
Touch "Backup", leave the default selection as they are and swipe the button to create a nandroid (a backup) of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Installing a custom ROM
The most popular custom ROMs for the TF700 are CROMi-X, CROMBi-KK and CyanogenMod (CM).
CROMi-X is based on the latest Asus firmware (JB 4.2.1) for this tablet with many, many tweaks and improvements.
CROMBi-KK is a mix of CM11 and CROMi-X and at this point still in beta.
CM11 is build from the ground up, emulating KitKat (JB 4.4).
There are quite a few more variants, check them out in the XDA Development forum and don't forget to make a nandroid before flashing anything new
Note: Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: Transformer TF700 Android Development - xda-developers
Note: It is recommended (mandatory if you go for CM) to do a Factory Wipe in TWRP before installing a custom ROM.
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
From here on out it's as easy as downloading the installation file of your custom ROM, booting into recovery, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you go for CROMi-X and TWRP as your recovery, make sure you check "verify zip signature" under the Install menu. sbdags signs his ROM zips - a better way to ensure file integrity than md5 sum.
For a general overview and comparison of ROMs check out Gtanner00's thread, post 2 + 3. Note that he describes roms for the TF300, but since the framework for the TF300 and TF700 is very similar there is usually an equivalent rom for the TF700 at the XDA Developers forum.
http://www.transformerforums.com/forum/showthread.php?t=41508
Do not follow or download from any of the links he provides! I only link to his thread for general information!
Any questions - please ask.
AND IF YOU LIKE THE ROM, SHOW YOUR APPRECIATION AND DONATE TO THE DEVELOPER!
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
Click to expand...
Click to collapse

droijo said:
I tried that too initially seeing it in the cromi kk rom. However it didn't do anything either when I cancelled the first one that hanged.
But funny, I rebooted and tried again using your guide 0x05b0 and it worked. So I'm not sure what happened there. I used a lower case "b" this second time.. lol
Just downloading cromi kk now, thanks!
Click to expand...
Click to collapse
Same thing happened to me. Fastboot recovery command did not return after over 10 minutes. I did Ctrl-C. Ran the command again and got the invalid argument error. Tried a couple times with same result. Unplugged and replugged USB cable (to same USB port). Ran the command again and it worked. When it worked, it took 11 seconds to flash recovery.
Also probably worth noting in the guide is that the Asus boot unlocker requires Google sign-in. If you have 2-step verification setup on your Google account, you need to use a one-time app password to sign-in.
Code:
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
^C
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
C:\adb>fastboot devices
015d2c05683c0a50 fastboot
C:\adb>fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
sending 'recovery' (6930 KB)...
OKAY [ 2.704s]
writing 'recovery'...
OKAY [ 8.026s]
finished. total time: 10.731s

[SOLVED] Nexus 5 stuck in boot loop animation (Lollipop) , partially working with 4.4

I have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .

stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad

Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.

killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck

Or just read the stickies.

I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers

Thank you so much for this! You saved my phone!

volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?

Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..

volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?

{
"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"
}
External, like on this picture.

Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue

volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks

Just the button. You can DIY, it's easy.

worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5

incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:

eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T

ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.

help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you

Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.

[GUIDE] Proscan PLT9650G (RockChip RK3126) Tablet, Root, TWRP, etc

*** Use at your own risk these instructions worked for me on MY tablets that is no guarantee they will work for you ***
This is for the ProScan PLT9650G(K-1G-8G) tablet. It has the RockChip RK3126 chipset. The one I am working with was purchased in Canada at the Atlantic Superstore. I will just briefly outline what I needed and had to do to root and install a TWRP recovery on the tablet. See the attachment for the recovery image. I will explain how to get the programs and general steps to make a full backup of the tablet before ever rooting the device. It is a little difficult, and not necessary, but like any backup can be helpful to have around.
Specifications:
The ProScan tablet has:
- Android Lollipop 5.1.1;
- Quad-core Processor, 1.2Mhz;
- 1 GB of DDR3 Memory;
- 8GB Flash Storage;
- 800x480 Screen Resolution.
Backup Overview:
1) Install USB drivers;
2) Put tablet in bootloader mode;
3) Read the different partitions.
Tools Needed:
1) Rockchip Driver Assistant v4.3;
2) Android Tool v2.3.
Detailed Instructions:
This tablet is a newer version and requires at least version 4.3 of the Rockchip Driver Assistant. The older versions (4.1) won't recognize the USB product id (310D) in bootloader mode.
Download the drivers unrar and run DriverInstall.exe. Select uninstall to clean any old drivers and then select install to install the newer ones. I've done this under Windows 7/8.1/10. Since I've done it so often and so many times with different driver version, I can't remember if the bootloader drivers require you install them with the driver signing turned off or not. The problem becomes that the bootloader drivers (under Windows 8+) will fail the driver signing authentication and won't install. The ADB and MTP drivers are signed and will install correctly, but when you boot the tablet in bootloader mode the device will be unrecognized by Windows. If you end up with this problem follow these instructions and then install the drivers.
After testing on a new machine under Windows 10 the drivers install fine. There is no need to boot with driver signing verification turned off.
To put the tablet in bootloader mode follow thes instructions:
1) Unplug tablet (both power and usb);
2) Turnoff tablet;
3) Press and hold the esc and power buttons at the same time;
4) Hold until the stock recovery menu comes up;
5) Press the esc button to go down to the menu item saying bootloader;
6) Press the power button to execute that menu item.
The screen will go blank. Plug the tablet into the computer and it will be recognized as a device type "Class for rockusb devices" in the Windows Device Manager.
Download the Android Tool from the link provided. The link gives a detailed description of how to backup all the partitions. I have included my parameters.txt file that I created. From the standpoint of undoing the root operation described below I believe only the recovery and system partition needs to be saved. But saving all the partitions never hurts. After you have followed the information in the link and saved the partitions you can move on to rooting the device.
One serious warning I have NOT been able to write anything to the device using the Android Tool. It always give me an error and won't even try. The backups we create can be used from within the tablet to restore it later if needed.
Custom Recovery Overview:
1) Root device;
2) Download the image file on the tablet;
3) Flash the recovery partition with the image file.
Tools Needed:
1) KingRoot;
2) Terminal Application;
Root Device:
The device rooted using KingRoot. Startup the tablet and go through the setup process. Download the apk from the link provided. The version used in testing was 4.6.2. You will need to allow "Unknown sources". The app will eventually give a button just try to root. This will eventually work and the tablet will be rooted.
Extract the img file from within the zip file below onto the internal drive. Make sure you put it in the Download directory. If you are doing this from the tablet it should go there if you move it over using the computer make sure you put it in that directory or change the command below to the proper directory.
Install a terminal emulator. Anyone will do, the one I chose is linked above. Open the emulator and type:
Code:
su
at the prompt. KingRoot should prompt you asking if you want to grant root privilege to the command prompt. Then type the command:
Code:
dd if=/sdcard/Download/TWRP_800x480_Unified.img of=/dev/block/rknand_recovery bs=4096
. That's it if you type:
Code:
reboot recovery
the tablet will reboot and TWRP should start up.
Notes:
If you saved the original system partition you can install it using TWRP and effectively unroot the device but keep the TWRP recovery. With the recovery image you can install it over the TWRP and return the tablet to its stock state. I'm giving these tablets to my kids and I wanted a way to return them to the state I bought them plus after I've personalized them for each of my kids I can make a backup in case they do something that messes them up.
This will also work for the PLT1065G but you need to use different recovery/parameters. The kernel is different (looks like a different touchscreen).

Thanks for this. Got one for $50 at Loblaws today. Will attempt rooting.
Got it for my 6 yr old
Edit: Fixed boot issue

protectivedad said:
*** Use at your own risk these instructions worked for me on MY tablets that is no guarantee they will work for you ***
This is for the ProScan PLT9650G(K-1G-8G) tablet. It has the RockChip RK3126 chipset. The one I am working with was purchased in Canada at the Atlantic Superstore. I will just briefly outline what I needed and had to do to root and install a TWRP recovery on the tablet. See the attachment for the recovery image. I will explain how to get the programs and general steps to make a full backup of the tablet before ever rooting the device. It is a little difficult, and not necessary, but like any backup can be helpful to have around.
Specifications:
The ProScan tablet has:
- Android Lollipop 5.1.1;
- Quad-core Processor, 1.2Mhz;
- 1 GB of DDR3 Memory;
- 8GB Flash Storage;
- 800x480 Screen Resolution.
Backup Overview:
1) Install USB drivers;
2) Put tablet in bootloader mode;
3) Read the different partitions.
Tools Needed:
1) Rockchip Driver Assistant v4.3;
2) Android Tool v2.3.
Detailed Instructions:
This tablet is a newer version and requires at least version 4.3 of the Rockchip Driver Assistant. The older versions (4.1) won't recognize the USB product id (310D) in bootloader mode.
Download the drivers unrar and run DriverInstall.exe. Select uninstall to clean any old drivers and then select install to install the newer ones. I've done this under Windows 7/8.1/10. Since I've done it so often and so many times with different driver version, I can't remember if the bootloader drivers require you install them with the driver signing turned off or not. The problem becomes that the bootloader drivers (under Windows 8+) will fail the driver signing authentication and won't install. The ADB and MTP drivers are signed and will install correctly, but when you boot the tablet in bootloader mode the device will be unrecognized by Windows. If you end up with this problem follow these instructions and then install the drivers.
After testing on a new machine under Windows 10 the drivers install fine. There is no need to boot with driver signing verification turned off.
To put the tablet in bootloader mode follow thes instructions:
1) Unplug tablet (both power and usb);
2) Turnoff tablet;
3) Press and hold the esc and power buttons at the same time;
4) Hold until the stock recovery menu comes up;
5) Press the esc button to go down to the menu item saying bootloader;
6) Press the power button to execute that menu item.
The screen will go blank. Plug the tablet into the computer and it will be recognized as a device type "Class for rockusb devices" in the Windows Device Manager.
Download the Android Tool from the link provided. The link gives a detailed description of how to backup all the partitions. I have included my parameters.txt file that I created. From the standpoint of undoing the root operation described below I believe only the recovery and system partition needs to be saved. But saving all the partitions never hurts. After you have followed the information in the link and saved the partitions you can move on to rooting the device.
One serious warning I have NOT been able to write anything to the device using the Android Tool. It always give me an error and won't even try. The backups we create can be used from within the tablet to restore it later if needed.
Custom Recovery Overview:
1) Root device;
2) Download the image file on the tablet;
3) Flash the recovery partition with the image file.
Tools Needed:
1) KingRoot;
2) Terminal Application;
Root Device:
The device rooted using KingRoot. Startup the tablet and go through the setup process. Download the apk from the link provided. The version used in testing was 4.6.2. You will need to allow "Unknown sources". The app will eventually give a button just try to root. This will eventually work and the tablet will be rooted.
Extract the img file from within the zip file below onto the internal drive. Make sure you put it in the Download directory. If you are doing this from the tablet it should go there if you move it over using the computer make sure you put it in that directory or change the command below to the proper directory.
Install a terminal emulator. Anyone will do, the one I chose is linked above. Open the emulator and type:
Code:
su
at the prompt. KingRoot should prompt you asking if you want to grant root privilege to the command prompt. Then type the command:
Code:
dd if=/sdcard/Download/TWRP_800x480_Unified.img of=/dev/block/rknand_recovery bs=4096
. That's it if you type:
Code:
reboot recovery
the tablet will reboot and TWRP should start up.
Notes:
If you saved the original system partition you can install it using TWRP and effectively unroot the device but keep the TWRP recovery. With the recovery image you can install it over the TWRP and return the tablet to its stock state. I'm giving these tablets to my kids and I wanted a way to return them to the state I bought them plus after I've personalized them for each of my kids I can make a backup in case they do something that messes them up.
Click to expand...
Click to collapse
It seems the boot issue is still there. Do you ever get this? It will get stuck at the PROSCAN logo display.

Friko said:
It seems the boot issue is still there. Do you ever get this? It will get stuck at the PROSCAN logo display.
Click to expand...
Click to collapse
I have had it stuck. It was when I was testing things. I can't remember what I did. I do know one time I left it for a day and I noticed the ProScan logo had a flashing cursor in it.

protectivedad said:
I have had it stuck. It was when I was testing things. I can't remember what I did. I do know one time I left it for a day and I noticed the ProScan logo had a flashing cursor in it.
Click to expand...
Click to collapse
I've been fiddling with it and it seems to be completely random. So I guess it's something we'll have to live with.
I bought it for my 6 year old who's dying to play Pokemon Go. The app runs okay on it. It's just the 'GPS' (or lack of a proper GPS chip) that's a bit slow/inaccurate

Hello I to bought this tablet in Canada I successfully rooted it but is there a reason why no other cameras can be downloaded or Music players or Instagram.

Is thee any chance to unbrick this tablet?
I have one stuck in the boot logo, hard reset wont solve, is there any flash file?

Hellooooo !!
anybody here ?
---------- Post added at 12:30 PM ---------- Previous post was at 12:26 PM ----------
ANYONE TEIED THIS FIRMWARE?
https://mega.nz/#!TVFX0CiZ!6CaGOSGZM47PQAd9KZDuKcPJaXsCL3n3JJQBtXPRHJo

is there any tool capable of flashing this tablet?
I have tried all known by me and all report a sudden error as sson as you try to write anything.
like OP said.
I have one stuck at boot logo, I have 2 firmwares ready to flash.

yurais said:
is there any tool capable of flashing this tablet?
I have tried all known by me and all report a sudden error as sson as you try to write anything.
like OP said.
I have one stuck at boot logo, I have 2 firmwares ready to flash.
Click to expand...
Click to collapse
There is a way to create an SDCARD and it will run from the SDCARD. I've forgotten how . I'm looking at one of my kids cracked ones right now. The touchscreen is cracked so I'm looking at build Ubuntu for it. I'll post when I figure out the SDCARD again.

Reset tablet to factory
I was able to use the factory irmware to reset the tablet from a computer. It will over write any custom recovery, etc. I have been unable to recreate a custom image any changes make the image fail. I found the software I used to create a bootable SDCARD but I can't get it to work keeps failing on creating the MBR. The software was the Rockchip SD Firmware Tool and there is an option to create SD Boot. So far I can only find v1.43 anyone have v1.45?

Let me know here as soon as you just remember anything related to this.
I got another tab like this, screen cracked and I could read off its firmware, so I now have a working firmware waiting to be written...
Enviado desde mi SM-N920T mediante Tapatalk

Thanks so much for this guide. I picked one of these up for $6 when HHGREGG was closing.

Proscan PLT7650G
Good day is there a guide and firmware for a Proscan PLT7650G

Technician
protectivedad said:
I was able to use the factory irmware[/URL] to reset the tablet from a computer. It will over write any custom recovery, etc. I have been unable to recreate a custom image any changes make the image fail. I found the software I used to create a bootable SDCARD but I can't get it to work keeps failing on creating the MBR. The software was the Rockchip SD Firmware Tool and there is an option to create SD Boot. So far I can only find v1.43 anyone have v1.45?
Click to expand...
Click to collapse
How did you flash the image? what software did you use,
Thanks.

it's not possible to change the rom or custom image of the tablet to another operating system like ubuntu or linux. It has allow OEM bootloader unlocked in the settings in developer section greyed out and it doesn't allow oem bootloader unlocking 'enabled'. You cannot enable it.
What you are doing is just resetting the factory image. or rom. you can just push the reset button with pin after charging the tablet for 3 hours.
These tablets are not 'cheap' to make and google, cell phone companies subsidize these 'cheap' tablets. so you have to use and pay them when you subscribe to their cell phone 'service' or google advertisements when you use their 'service'.
Lots of vaporware being pushed saying they can unlock something for $40 or downloading tools etc. wasted of time as it's impossible to unlock oem BOOTLOADER if the manufacture has locked it, you cannot install another operating system in the tablet, or smart phone. so don't waste your time.
Only some phones allow oem unlocking bootloader and those are the higher end phones costing $400-$600 for a tablet that are not 'subsidized' by google or you cell phone company as with 'cheap' phone or tablet.

the firmware is not available for download at the manufacture website that should raise alarms about the firmware. I've factory reset the device and now it's having reboot issues, either the firmware is defective or corrupt bootloader etc. The manufacture proscan seems to be selling the devices yet no technical support or even a direct download from the manufacture, downloading firmware from thirdparty servers is security risk. it seems like today lots bogus websites and no technical support from manufacturers in tech devices they sell. and people have to sites like XDA for 'free' technical support. Even Microsoft which makes billions in profits fail to provide proper technical support for some reason. and have to rely on 'free' technical support for bugs and issues with their software and hardware and lots vaporware apps etc.. bogus apps. that don't work.
Rooting gives the user the ability to install and change OEM software. from what i gather so don't waste your time, to root a device, allows the user to delete operating system files. if the manufacture doesn't allow changing the oem software there is nothing you can do. about so don't waste time trying root it or try to install ubuntu or linux on the tablet or smartphone if it's oem LOCKED. bootloader. you cannot unlock it. it's much harder to unlock oem software.

the method to 'restore' factory image or known as 'flashing the rom'
there is no reason to flash the rom etc.
1. just hold the power button and esc button at the same time
2. release the power button wait 2 seconds
and then release the esc button
you should now be in boot up mode.
this unit doesn't allow you to be in bootloader mode. so you CANNOT install another firmware or install linux etc. other than the proscan firmware.
3. press esc to select restore the factory settings
4. press the power button to select
this the easiest way to restore stuck in browser or need to flash the rom
again if the rom is 'corrupt' which is not likely
if that is the case
the option to "apply update from external storage" doesn't seem to work as you cannot mount to flash the rom and reinstall the .img file from the .zip file

"apply update from external storage"
where you saved your .zip doesn't work
the apply updated from ADB works you need a usb computer hooked up to you computer and terminal command to ADB to your table to rinstall the .imge file

update ,this no longer seems to work in installing the .zip file method to install the firmware.
lot of software and hardware that have no technical support or documentation and the stuff just doesn't seem to work and high security risk with no updates from manufacture as it cost them money to resolve issues. selling disposable technology tablets. that is not meant to last. basically toys. for kids.