[NEW ROOTING METHOD] Trekstor Surftab Ventos 8, 9.7 and Breeze 7 - Miscellaneous Android Development

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?

Related

[ROOT + CWM 6.0.1.5 or 5.5.0.4] Lenovo IdeaPad A2107A (-H)

The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
------------------------------------------------- UPDATE 3 ---------------------------------------------------------
I think there is even easier way than the one I originally posted above.
BUT I cannot be sure that it will work with all of you - the reason is that I made so many changes to my A2107A-H that I do not know whether this method works "just because it's universal" or because my tablet was tweaked far enough.
On the other hand when you consider it reasonably it looks like it's quite simple and there is no particular reason why it shouldn't work with a stock A2107A.
So...
What you need:
1 - this package: http://www.mediafire.com/download.php?fbuzi5xjofs7vgf
2 - PC running Windows 7 would be the best (7 gave me no problems at all - takes 1 minute to do it). I made it on Windows 8 as well but there is a lot more fuss to install the proper driver.
What you do:
1 - turn on USB Debugging on your tablet
2 - connect the tablet to your PC (if it's the 1st, some default drivers will install - that's ok)
3 - tap on the notifications area in the "Connect as" change to "MTP" - this is quite important !
4 - from the downloaded package run the "Flash_tool.exe"
- click "Scatter-loading" on the right and find "MT6575_Android_scatter_emmc.txt"
- in the list in the lower part of the window you MUST have the "PRELOADER" (super important) and "RECOVERY" ticked and leading to the correct files. The PRELOADER = "preloader_lenovo75_a2_ics.bin" (in the package) and the RECOVERY is the recovery file of your choice -> there are 3 in the package - pick the one you want. You can flash them over and over so if you don't like one then try the other.
5 - click "Download" above - you will see a prompt saying that not all images were loaded - that is fine - we only want to flash the RECOVERY - so click "Yes"
6 - now the Flash tool is waiting for the tablet - press "reset" on the back - Windows will recognize a new device (and WILL NOT find the driver unless you have done it before) - no worries, you have the correct driver.
7 - open Windows "Device manager" and locate the MT65..... unrecognised device -> update / install driver -> point Windows to "USB VCOM Driver" folder from the package and pick your system. My Windows 7 found the driver on the spot but asked to confirm the install - "insecure" driver - I obviously clicked "install anyway" and so should you.
8 - once the driver is loaded the Flash tool will flash the new recovery file - you will see some colour progress bars in the program - at the end you should see a green circle.
That is it. Unplug the tablet, press reset on the back and you can now enter the recovery mode.
FUN FACT: the "reset" button on the back is not really a reset button, it's more like physical cut off button to temporarily disconnect the battery.
I have the Lenovo A2107A under Vodafone's brand Vodafone Smart Tab II 7
It has Android version 4.0.4 and compilation: A2107A_A404_010_002_120913_VODA
Imanaged to root it and install CWM using this thread. But somehow I was not able to create the CWM modded recovery.img
I used the one provided here and it worked fine.
Thanks for this.
I can't connect tablet to PC
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for you actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Window device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
Click to expand...
Click to collapse
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.
optical99 said:
csns thanks for your guide
Unfortunately I can't connect my tablet to pc in USB debbuging mode. I tried a lot of drivers from net but without success.. Pls let me know the right way to root my tablet.
Click to expand...
Click to collapse
Hi there,
Try those drivers: http://www.mediafire.com/?vx2hyv7dpwlmeyy
They come from the current Android SDK but I am running a 64 bit system and I'm not sure if those drivers will work with 32 bit systems.
Fingers crossed!
I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.
optical99 said:
I tried with yor recommend dirvers and with a lot of others and doesn't work. I have to unrecognised denices in Device Manager - A2107A-H and MTP.
I am very upset about Lenovo because their support doesn't exist.
Click to expand...
Click to collapse
I had to use the PDANET from this link.
http://forum.xda-developers.com/showthread.php?t=1982334&page=6
Should be the first post.
Sent from my Samsung Galaxy Note running JellyBeer using Xparent ICS Blue Tapatalk 2
First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance
makbro said:
First of all, a ton of thanx to csns for posting this detailed procedure along with all required scripts and tools...
I have just one question...Which Modified ROM did you install as I see you have unlocked calling feature in the video you posted???
I asked because the MOD ROM by pemergency in the other thread is for the 16 GB and creates some issues in the device...But your's is 4 GB, as is mine...
Thanx in advance
Click to expand...
Click to collapse
I'm glad you find my post useful.
As for the calling feature - it's not actually working
You see, to have the calling app (in other words "the phone" app) in the app drawer all you need to do is change one tiny value in framework-res.apk.
This value is telling the system weather the whole device is supposed to handle voice calls or not. I just tricked the system to make the Phone.apk visible but there is a lot more do be done in order to make a real call over the cellular network.
I've just had this tablet for a week and I didn't have much time to dig into this topic. Let's see what the weekend brings
Be patient, I think it's just a matter of time when someone posts a user friendly guide... Or search yourself and share what you find with the community.
Take care.
works fine
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job
optical99 said:
manwithmanypiercings
I have gained acces to tabled with PDAnet drivers...thanks a lot
csns
I followed all steps and installed CWM 6015. Very nice tutorial...I thought it's simpliest way...respect for your job
Click to expand...
Click to collapse
Glad I could help by showing the link. Glad you got everything else taken care of.
This is an awesome post! Thak you very much.
Need help at step 4
csns said:
The following post is just a TESTED collection of tools and procedures that were found over at XDA forum or elsewhere on the Internet.
I do not take any credit for all those nice scripts and manuals - I just put them together for the young community of IdeaPad A2107A owners.
Below you will find methods of getting root and Clockwork Mod Recovery v 6.0.1.5 on IdeaPad A2107A (I own the -H version with dual SIM and ca. 4 GB of internal memory).
All processes were tested by me and are working well but obviously you are responsible for your actions.
My device runs on ICS 4.0.3, compilation A2107A-H_S341 and has a couple of European languages (tablet bought in Poland).
What you need is installed ADB drivers so the PC can "talk" to you tablet. You will find a lot of guides on the net - just make sure Windows device manager shows Android Device - Android ADB Interface or something close to that.
I also advise to enable USB debugging and allow installing applications from unknown sources - all in your tablet's settings.
Once you make sure you have done the above you're good to go.
So let's go!
Download this: http://www.mediafire.com/download.php?5o7dm16d430lwal (un7zip) and read as follows:
1 - Root
The method I chose is for patient people - the device will reboot 3 times during this process.
a) connect your tablet to the PC, open "1 - 4.03root" folder and run "root.bat"
b) just after you run the .bat the device will reboot and in the command prompt you will see "Press any key to continue . . ." - WAIT until the tablet boots up completely. When you see the lockcreen THEN hit a key in the command prompt.
c) the above will happen 2 more times - always WAIT for the tablet to boot completely.
This process will install Superuser and RootExplorer so find those apps and see if the root works.
2 - Backup the whole ROM that is on your device - will be useful with making the CWM recovery.img file.
For this you will need ca. 2GB of memory so I advise at least 4GB sdcard.
I also advise to go to the settings and in the memory tab set the "Default write disk" to "SD storage" - this makes the microSD the primary "sdcard" - makes things easier with backups etc.
ALSO in the settings set the screen to stay on for at least 10 minutes - this is how long it will take to do the full ROM dump - important to keep the script alive.
To avoid any issues turn the flight mode on so no new "data" is received by the device.
Once you're done open "2 - Backup" folder from my 7zip and copy the "gscript" folder to the root of your sdcard. Now install "GScriptLite.apk" and run it (needs root access!).
In the app hit the menu button and pick "Add Script" ->"Need SU?" must be checked -> "Load file" -> select "back_mt6575_a4_v2c.sh" -> save and click the script.
As I said - wait ca 10 minutes for the scrip to finish. Now you will have a nice backup in the SD - look for "backup_v2" folder - copy it to your PC.
3 -Mobileuncle - it's in the Google Play Store but you won't find it with our tablet - supposedly incompatible. Bull*hit!
Open "3 - Mobileuncle" folder, copy the apk to your device and install. We will come back to this later.
4 - How about the CWM? Yes!
Open "4 - CWM 6015" - you will find a PDF there - read the instructions. The subfolder "michfood" contanis all the scripts you need so you don't have to download anything else.
ATTENTION - the "recovery.img" used in this process is YOUR "recovery.img" that you dumped in step 2. So find your backup from step 2 and the original "recovery.img" from your ROM.
ATTENTION - our device is MT6575 so you pick nr 1 in the command prompt.
5 - Once you have the new "recovery.img" with CWM (it is actually smaller than the original file) copy it to the root of your sdcard.
Now open the Mobileuncle Tools you installed in step 3 and hit "Recovery Update".
There, at the very top of the screen you will see your new CWM recovery file - hit it and then confirm the update. It takes a second!
Now you will be asked to boot into recovery mode - go ahead, try it
If the tablet booted in CWM then you are all set!
REMEMBER - to go into the recovery mode while the device is OFF you need to:
1 - hold the power button for ca 3 seconds
2 - let it go and in the same moment press BOTH Vol + and Vol - buttons.
REMEMBER 2 - the CWM 6.0.1.5 makes backups in a bit different way than the old CWM - read here :http://forum.xda-developers.com/showthread.php?t=1846446
It also appears that the key to modding our tablet is the MT6575 processor - a lot of tools just need to support this processor, the device itself is not so important.
All the best.
Mike.
P.S.
A little film how it looks: http://www.youtube.com/watch?v=tM3Sdwf2i4M
------------------------------------------------- UPDATE 1 ---------------------------------------------------------
For those who are running the same compilation as I am (A2107A-H_S341):
- you can download my recovery file from here: http://www.mediafire.com/download.php?um372gh6ayf6t6w
To use it you need to do:
1 - Root
(optional backup with GScriptLite.apk)
2 - flash the recovery file with Mobileuncle
Be careful and make sure you have a backup if you want to try this file with another compilation.
Cheers.
------------------------------------------------- UPDATE 2 ---------------------------------------------------------
Tested (by user: manwithmanypiercings) USB drivers are in this post: http://forum.xda-developers.com/showpost.php?p=34651039&postcount=51
Click to expand...
Click to collapse
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
Well, this happened to me once and I think the reason was that the path was too long - I guess it may have something to do with the fact that the .bat is a simple "program" and can have some problems with handling long paths.. specially with "national" character in them.
Try finding a location as close to the root of the drive as possible, and make sure you have full R/W access. Or try with a pendrive for example.
Since you made a backup of your ROM I think you are quite safe with using the recovery I uploaded - first post -> UPDATE 1.
They seem to fit all 2107A devices. If not I will tell you how to restore the original recovery from your backup.
You can also read UPDATE 3 I just made - your choice.
Thanx
Hello csns,
Thanx to your help, I have also got CWM recovery working on my device.
BTW I saw these two posts on a forum in Russian (I guess)...I used google translate and am pretty sure these two posts that I provide links for below have two modified ROMs with everything working, including phone and radio !!! The only draw back is that once you flash these ROMs you'll get Russian language, which can be changed to English from the language menu
I plan to fo it myself as well tomorrow,would let you know the outcome
http://4pda.ru/forum/index.php?showtopic=286687&st=920 (go down to the post labelled "A2107_Foxtrot_v100")
and
http://4pda.ru/forum/index.php?showtopic=286687&st=440 (go down to the post labelled "Прошивка Tasemart
MOD 1.1")
and of course you can also try the "Angeleas_Final" modified ROM also that I'll upload and provide links to tomorrow
Thanx again for all your help !!!
I also had many trouble getting the cwm bat file to work. It is very picky about its path and arguments on Win7.
I moved the michfood folder to C: and moved my own recovery.img to C:\michfood\recovery.old
cd C:\michfood
cwmr\ 6015.bat recovery.old
That worked - otherwise it wouldnt finish the cpio stuff.
Reworking that horrible script to work on linux would have probably taken less time -_-
Anyway - thanks!
Permissions problems on Windows7
Hi,
I Had the same problem.
makbro said:
Hi csns,
Sorry to bother you but when I try drag and drop my original "recovery.img" to "cwmr 6015.bat" in the "michfood" folder, I get a warning message "System cannot find the specified file "C:\users\....\recovery.img" "recovery" and the bat script exits...I have tried the following:-
1. Copy the folder and file "michfood" and my original "recovery.img" file in all possible alternate locations of my PC including desktop as shown in the pdf tutorial in "michfood" folder.
2. The permissions for both folders is "Full Control" for all users.
Click to expand...
Click to collapse
My solution:
It was required to use a directory not to deep in folder structures, so the best is as short as possible like "C:\michfood".
I had to add "Full Control" permissions for "everyone" to the "michfood"-directory and enable the "replicate permissions to subfolders"-option (I don't know the exact designation because I use it in german ... )
I had to delete an existing "Recovery" folder inside the "michfood"-directory from earlier attempts to create the new file and for this I had to take over the ownership of the "Recovery" folder before I was able to delete it.
The original Recovery.img must be in a different folder than "michfood". This can be on the desktop but for a shorter path it could be in the root directory.
I had success after copying "cwmr 6015.bat" to "go.bat" (it's shorter and does not contain any space in it) and calling it from command line from its directory( C:\>cd C:\michfood ) with: "go C:\Recovery.img" ( I had Recovery.img on C:\ ).
makbro said:
3. Files not hdden or protected.
4. Also turned off my antivirus and firewall.
No luck....Please help !!! Thanx in advance
Click to expand...
Click to collapse
I hope this helps ...
Thanx
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem
makbro said:
Thanx for the suggestions everyone, appreciate it...I got it working in the mean time on a WinXP desktop without any problem
Click to expand...
Click to collapse
HOW?
Tell me what you did...
Cristian.Ene said:
HOW?
Tell me what you did...
Click to expand...
Click to collapse
I copied the folder as "C:\michfoods" and recovery image file as "C:\recovery.img" and gave the command "cwmr6015 C:\recovery.img"...Before that, I removed the space from the file name "cwmr 6015.bat" and saved it as "cwmr6015.bat".
Hi, i rooted succesfuly my a2107a device and installed backup Gscript ...loading "back_mt6575_a4_v2c.sh and saving it , but when it comes to run...nothing...only the counter saying how many sec's till stop.Any ideeas why?

Samsung Galaxy Star Duos GT-S5282 Rooting Guide

NOTE: Click on the images to enlarge them!!!:good:
DISCLAIMER: Rooting your phone will void your warranty, and can be dangerous. You may end up with a “bricked” device if anything goes wrong. I take no responsibility if something happens to your device. If you are ever in doubt STOP! This is not something to take lightly!
While rooting is reversible, it’s not something you should ever plan to do. Use some common sense here. If you don’t understand the consequences of what you are doing, DO NOT ROOT YOUR PHONE! You have been warned.
View attachment 2312405
So you have bought the GT-S5282 and after getting bored of playing with it have decided to give the ultimate treatment to your new toy, ROOT IT!!!
Well you have come at the right place. Today I will share with you friends a ridiculously easy way to root your Samsung Galaxy Star Duos. Your droid should be running stock firmware and you need Windows OS running on your computer.
Just follow the steps mentioned below carefully:-
1. Download the version of Cydia Impactor for Windows OS from this link www.cydiaimpactor.com
2. Install your device drivers by installing Samsung Kies on your PC and then connecting your phone to your PC via data cable. The device drivers will be installed automatically after few minutes.
OR
Alternatively you may install ADB drivers from the given link adbdriver.com and after turning on USB debugging in the Developer Options of your droid and connecting it to your PC via data cable, clicking on the Install option the drivers will be installed automatically.
3. Enable USB debugging from Developer Options in your droid (if you have not enabled it previously) and connect your droid to your PC via data cable.
4. Extract the file downloaded in first step and run Impactor.
View attachment 2312448
5. The programme should be displaying the command # drop SuperSU su to /system/xbin/su as shown above. Click start and run this command in the Impactor and wait for a few seconds for the process to get completed. When the programme again displays the above command, WOW you have successfully rooted your phone!!!:highfive:
6. Last but not the least you need to install these free apps from the Play Store before you enjoy root privileges on your droid....
i. SuperSU - This is required to access Superuser privileges on your droid. https://play.google.com/store/apps/details?id=eu.chainfire.supersu
ii. BusyBox - This is required to install the BusyBox binaries on the rooted device which is needed to run some root apps. https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
NOTE: Installing the above two apps are a MUST to access ROOT features on the phone!!!
7. TADA! You are now free to enjoy your ROOTED Samsung Galaxy Star Duos and unleash the hidden power user within you...!!!
NOTE: This method only works on preupdated old firmwares. If you get "signature bugs unavailable" error, it means you are running the latest/updated version of the stock firmware which comes with the bugs patched. For you guys who get this error, you need to flash the old stock ROM released before August for your device. You can download the stock firmwares from here http://samsung-updates.com/device/?id=GT-S5282
You need to flash the stock firmware on your droid via Odin. For help regarding how to flash stock ROM via Odin, check out this thread http://forum.xda-developers.com/showthread.php?t=2482371
If I have helped you to root your GT-S5282, please press the THANKS button...:good:

How to install a Custom ROM on the Trio Stealth Pro 7c

DO THIS AT YOUR OWN RISK. YOU COULD PERMANENTLY DAMAGE YOUR DEVICE. READ ALL DIRECTIONS BEFORE ATTEMPTING.
These tablets are an LY-F1 clone. So most of the stuff that is compatible with an ly-f1 will work for you.
The model I am referring to and have personal experience with is the following: Trio Stealth Pro 7c
The Trio already comes rooted. I accidentally un-rooted mine AND I ended up with the 0.00 internal storage error. It would not let me download or install apps already on my SD card. To install a new (custom) ROM you can follow this quick guide I put together.
First...
Things you will need to Download;
CWM Recovery for the Trio Stealth Pro 7c : CWM Recovery 6.0.1.2 for Allwinner A10 LY-F1/TREQ Tablets
Custom ROM for the Trio Stealth Pro 7c : Choco Ice Cream 4.0 BETA1 for Allwinner A10 LY-F1/TREQ
32 or 64-bit Windows ADB Drivers : Windows ADB Drivers for Trio Stealth Pro 7c
ADB needs to be downloaded and installed/setup via the Android SDK found here : Android SDK Download
1.) Download CWM Recovery
2.) After your download is finished go ahead and extract the contents to the SD card. I connected to my PC and put the extracted files (there are 3 files) on both the internal storage as well as the removable micro-SD just to be safe.
3.) Download Choco Ice Cream 4.0 BETA1 Download Choco Ice Cream 4.0 BETA1
4.) After the ROM finishes downloading DO NOT extract; just copy the whole .zip file directly to the Micro-SD Card as-is.
5.) Connect your Trio to your Windows PC with a USB cable. Make sure you go to settings/Developer Options/and turn on USB Debugging. I had to open device manager and manually install the ADB Drivers for Trio Stealth Pro 7c. You can check to see if the drivers are installed by opening a command prompt on your computer. You would do this by going to start and typing CMD into the search bar. Or you can click on Run and type CMD into the box. This should open your command prompt. Enter each line one at a time, pressing enter after each line:
cd/
cd androidsdk/platform-tools (some of you may have to type just "tools' depending on which version you have)
adb devices
After hitting enter you should see your device's serial number. This shows that your device is connected and was found. If you do not see your device serial number either you don't have the correct drivers for your device or you did not enable usb debugging mode.
6.) Now we're going to start the adb shell by typing the following, again, pressing ENTER after each line of text.
cd\
cd androidsdk\platform-tools
adb shell
You should now see one of the following symbols:
# or $
Now type the following, again, pressing ENTER after each line of text
cd /mnt/sdcard
sh install-recovery.sh
sh reboot-recovery.sh
After pressing enter, you will see your tablet reboot into recovery mode. You can use the volume buttons to move up and down and use the power button to select. To get back into Recovery Mode if you reboot out of it or your tablet turns off; go ahead and turn your Trio completely off. Once it is shut down press the center of the volume button until the WHOLE thing is pushed in. Do this WHILE holding down the power button. Keep it held for a few seconds until you see the the screen come back on. Once you see it, you can let go and it will reboot into recovery mode.
7.) From Recovery mode:
MAKE A FULL BACK-UP FIRST. DON'T IGNORE THIS STEP!!! IT MIGHT JUST SAVE YOUR DEVICE ONE DAY!!! When the backup gets finished go back and then:
SELECT: INSTALL ZIP FROM SD CARD. (press the power button once to select it).
If you placed the ROM on the micro SD-card then you should select 'Choose zip from sd card' if you placed the ROM on your internal SD-card you should select: 'Choose zip from internal sd card'. Now find where you placed the ROM/download. Use the volume buttons to scroll up and down. Once you find it, select it with the power button. Scroll down until you see 'Install choco ice cream 4.0beta1_LYF1.zip'. Select this with the power button.
8.) It should now start to install. This will take maybe 3 minutes tops. Just be patient. When it's done, wipe the data and the cache. (it was one of the options listed when you first start recovery mode)
9.) SELECT: GO BACK; then choose REBOOT or REBOOT YOUR DEVICE or whatever and wait for the device to finish restarting. It takes several minutes to finish booting up; be patient; it will get done sooner or later.
10.) Your Finished
Here are some useful links for more Custom ROM's and other stuff you might need or find helpful:
XDA Thread for [ROM][Allwinner A10] Choco Ice Cream 4.0 BETA1 for LY-F1/TREQ
XDA Thread for CWM Recovery 6.0.1.2 for Allwinner A10 LY-F1/TREQ Tablets
XDA Thread for [rom] Unofficial CyanogenMod 9 for many AllWinner A10 tablets
XDA Thread for [rom] Unofficial AOKP for many AllWinner A10 tablets
XDA Thread for [ROM][PORT]CM9/CM10 for LY-F1/AlldroSpeed-UPDATED 13.09.2012
Good Luck...
will this work on Trio Stealth G4 7'' Tablet?
or at least the custom recovery and custom rom part?
im already rooted
just cant update binaries for some odd reason, some kingoroot thing, but its rooted and root works
---------- Post added at 01:14 PM ---------- Previous post was at 12:56 PM ----------
trio-stealth g4 7
How do you rooted the trio-stealth g4 7?
Tried safestrap, backup failed
I installed safestrap with your instructions. adb was not able to be downloaded for my device given the link you provided, but I had another version that I used from Android Multitools to perform the safestrap install. Only problem is now that I've installed safestrap, it boots into recovery just fine. However, that's the only thing I can boot to. I can't boot normally, and my backup using safestrap failed at /system (error was something similar to "could not mount /system!".
Any suggestions? I would like to be able to boot normally and backup fully if I can, I'm kinda worried about reflashing into the custom ROM and not being able to recover.
UPDATE:
This safestrap installation did not work for my stealth trio 7c A13. It actually prevented my device from booting, and when trying to install the choco rom, my device not only bricked but my SD card was corrupted as well. Not saying it's the ops fault at all, I know the risks when performing tasks such as these. I just want everyone to be aware.
I was able to restore my brick using the livesuite software and flashing with an image of 4.1 that I found from a different site. If anyone would like more info, ill be happy to provide it. My new rom is Google play good to go, so im happy. :thumbup:
Sent from my SCH-i605 through space and time
Brought forth to your face by the XDA Developer app
Hellstorm32 said:
UPDATE:
This safestrap installation did not work for my stealth trio 7c A13. It actually prevented my device from booting, and when trying to install the choco rom, my device not only bricked but my SD card was corrupted as well. Not saying it's the ops fault at all, I know the risks when performing tasks such as these. I just want everyone to be aware.
I was able to restore my brick using the livesuite software and flashing with an image of 4.1 that I found from a different site. If anyone would like more info, ill be happy to provide it. My new rom is Google play good to go, so im happy. :thumbup:
Sent from my SCH-i605 through space and time
Brought forth to your face by the XDA Developer app
Click to expand...
Click to collapse
I have a trio g4 7" mst-741 model will it work for me?
I don't know about a g4, I have no experience with those. Sorry
how long dose it take i put it on a trio stealth pro metal in hopes of geting good update

[GUIDE] Root ASUS MemoPad FHD 10 Model ME302C US version 5.0.16

This post (#377 on page 38) was originally written under thread "Root Now Available For ASUS MemoPad FHD 10 Model ME302C" (http://forum.xda-developers.com/showthread.php?p=51699593) however OP has not been able to update the original post and this has caused much confusion. Its difficult to read through 40+ pages of posts with new modifications to the originally posted root procedure. I am posting the latest instructions in a new thread.
Thanks to @perpe on the German Android Hilfe forum
[Anleitung]Root, Unroot, Up-/Downgrade, Unbrick ASUS MeMO Pad FHD 10 (ab Android 4.3)
http://www.android-hilfe.de/root-custom-roms-modding-fuer-asus-memo-pad-fhd-10/528918-anleitung-root-unroot-up-downgrade-unbrick-asus-memo-pad-fhd-10-ab-android-4-3-a.html
There is also a Russian Forum 4PDA for this tablet
Прошивка Asus MeMO Pad FHD 10 (Только WW регион)
http://4pda.ru/forum/index.php?showtopic=500286
This is a thread for apps that can be frozen or removed:
[Sammelthread] Apps die man deinstallieren oder einfrieren kann
http://www.android-hilfe.de/asus-memo-pad-fhd-10-me302c-forum/482780-sammelthread-apps-die-man-deinstallieren-oder-einfrieren-kann.html
+++++++++++++++++++++++++++
This guide and below links are for USA build only (Goto Settings -> About Phone -> Build Number). WW build needs WW 5016 update and WW 5017 root update files but, indeed, uses the same procedures. DO NOT interchange USA for WW files otherwise you will BRICK. Links for WW 5017 root can be found on previous forum posts. ASUS hosts the WW 5016 update on its support page http://www.service.asus.com/#!downloads/c1wax
AS ALWAYS, BACKUP YOUR DATA! Titanium backup is a good option. Make sure backup files are copied to your PC or external storage
MAKE SURE THE BATTERY IS FULLY CHARGED!
Tools Needed:
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
For those of you who are already root and would like to update to 5016 it is recommended to download the latest 5016 update (~700mb) directly from Asus website. Please do not do an OTA update as this may fail since you are already root. Make sure that SuperSU survival mode is OFF. Place US_ME302C-V5.0.16-0-ota-user.zip in the internal Storage via Windows Explorer. Make sure it has the exact file name US_ME302C-V5.0.16-0-ota-user.zip. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. Then copy 5017 root update US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. You will then be root. Make sure you install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil as it is x86 compatible.
For those of you who are not rooted the easiest method is to accept the OTA update to 5016. (Alternatively, place US_ME302C-V5.0.16-0-ota-user.zip in the internal Storage via Windows Explorer. Make sure it has the exact file name US_ME302C-V5.0.16-0-ota-user.zip. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet). Then copy 5017 root update US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer. Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet. You will then be root. Make sure you install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil as it is x86 compatible.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
Please note avoid OTA updates after root is obtained otherwise you will loose root or maybe worse. Keep up to date with developments on this thread for rooting methods when and if Asus release new updates. @perpe recommends all future updates be installed via the internal storage method. You can also check the German FHD 10 forum for updates at the above link
+++++++++++++++++++++++++++
Step by Step Guide for root via Fastboot Method for US version 4.7.3 or below: (read above instructions first as it is much easier to update and root using alternative methods)
Please note that tablet with versions higher than 4.7.3 no longer have the ability to use the fastboot method as this has been disabled by Asus in the latest versions. Some members have suggested downgrading fastboot to 4.7.3 if you have a later version. However this is not recommended and could result in problems. Fastboot downgrade should only be a last resort and limited to advanced users:
fastboot flash fastboot fastboot.img
(fastboot.img can be found inside the 4.7.3 release on the ASUS website. You can extract fastboot.img from the ~700mb update using 7 zip. Or download USA build here: http://support.mediafire.com/download/dk487lcxqfsgau6/fastboot473.zip )
Tools Needed:
Intel Drivers - http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Asus Drivers - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME173X/ASUS_Android_USB_drivers_for_Windows.zip (download these in case Intel drivers don't work)
ADB and Fastboot tools - http://forum.xda-developers.com/showthread.php?t=2588979 (say no to drivers, just install adb)
Linux Fastboot for Intel SoC - http://www.android-hilfe.de/7373742-post8.html
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
Enable USB Debugging:
The “Developer Options” menu item on 4.2.* is hidden.
1. Goto Settings -> About Phone.
2. Goto “Build Number” at the end of the Scroll list.
3. Tap on “Build Number” repeatedly (7 times). On your third tap you should see message indicating that you only have 4 more taps to go to ‘become a developer’.
4. Continue: 4 more taps.
5. Hooray, you are now a ‘Developer’, go back to the Setting page.
6. You should see Developer Option menu item in your setting list now.
7. Open Developer Options and check USB debugging > OK
Install ADB and Fastboot from above (say no to drivers, just install adb)
Install Intel drivers
Plug in USB cable (at this point your PC will auto install several devices)
adb devices
(if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
adb reboot bootloader
Wait for tablet to reboot into bootloader. You'll see an Android with a hard hat
fastboot devices
( if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
fastboot erase cache
(Please note do not use command "fastboot erase system" - it has caused many people issues and is useless)
(Please note "fastboot erase userdata" is optional. the command is a "factory reset" and removes all user data. Sometimes after an update the tablet may be sluggish or have issues then you could try this command)
fastboot flash update US_ME302C-V5.0.16-0-ota-user.zip
If it is working your CMD window will show:
sending 'update' (******* KB)...
OKAY [49.549s]
writing 'update'...
OKAY [3.220s]
finished. total time: 52.772s
Tablet will take time to apply update.
After successful reboot place US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer
(Alternatively, reboot into bootloader and apply 5017 root update using command "fastboot flash update US_ME302C-V5.0.17-0-ota-user.zip")
Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet
You are now root. Install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
+++++++++++++++++++++++++++++++++++++++++++++++++++
Step by Step Guide for Factory Reset via Fastboot Method for US version >4.7.3:
Please note that tablet with versions higher than 4.7.3 no longer have the ability to use the fastboot method as this has been disabled by Asus in the latest versions. You’ll need to downgrade fastboot to 4.7.3 before restoring your tablet. Extract Fastboot.img from US_ME302C_V4_7_3.rar using 7 zip (~700MB download, link below) or download just Fastboot.img (~10mb, Mediafire link below) into same directory as ADB and Fastboot
Tools Needed:
Intel Drivers - http://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Asus Drivers - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME173X/ASUS_Android_USB_drivers_for_Windows.zip (download these in case Intel drivers don't work)
ADB and Fastboot tools - http://forum.xda-developers.com/showthread.php?t=2588979 (say no to drivers, just install adb)
Linux Fastboot for Intel SoC - http://www.android-hilfe.de/7373742-post8.html
USA Fastboot 473 IMG - http://support.mediafire.com/download/dk487lcxqfsgau6/fastboot473.zip
USA Asus 473 update – http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C_V4_7_3.rar
USA Asus 5016 update - http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME302C/US_ME302C-V5_0_16-0-ota-user.zip
USA 5017 root update - https://docs.google.com/file/d/0B-6nm7Jks0W5eWxSM0JoZ2FPVGc
Enable USB Debugging:
The “Developer Options” menu item on 4.2.* is hidden.
1. Goto Settings -> About Phone.
2. Goto “Build Number” at the end of the Scroll list.
3. Tap on “Build Number” repeatedly (7 times). On your third tap you should see message indicating that you only have 4 more taps to go to ‘become a developer’.
4. Continue: 4 more taps.
5. Hooray, you are now a ‘Developer’, go back to the Setting page.
6. You should see Developer Option menu item in your setting list now.
7. Open Developer Options and check USB debugging > OK
Install ADB and Fastboot from above (say no to drivers, just install adb)
Install Intel drivers
Plug in USB cable (at this point your PC will auto install several devices)
adb devices
(if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
adb reboot bootloader
Wait for tablet to reboot into bootloader. You'll see an Android with a hard hat
fastboot devices
( if you don't see a device you have a driver issue. Try the Asus drivers - Goto Device Manager. Right click on "Android" and choose "Update Driver" and do a "Manual install" and select the extracted Asus drivers. Also the tablet could be listed under "Other devices". Make sure to reboot your PC when done.)
fastboot erase cache
fastboot flash fastboot fastboot.img
be patient while update completes then reboot back to bootloader
adb reboot bootloader
fastboot devices
fastboot erase cache
fastboot erase userdata
fastboot flash update US_ME302C-V5.0.16-0-ota-user.zip
tablet will take time to apply update.
After successful reboot place US_ME302C-V5.0.17-0-ota-user.zip in the internal Storage via Windows Explorer
(Alternatively, reboot into bootloader and apply 5017 root update using command "fastboot flash update US_ME302C-V5.0.17-0-ota-user.zip")
Disconnect USB and then it will detect the update (a yellow triangle). Apply the update and it will reboot the tablet
You are now root. Install SuperSU by Chainfire from Play Store. For BusyBox use BusyBox X by Robert Nediyakalaparambil.
Optional:
1) Install AdsFree from http://adfree.bigtincan.com
2) Review the German forum (link at top) for apps that can be safely frozen or uninstalled via Titanium Backup
One little note:
fastboot flash update <name-of-the.zip> only works with the 4.2.2 fastboot. On 4.3 it only works with small zips, like the fake update.zip for root.
The easiest way to update is to place the update zip on to the internal storage and select the triangle from the notification bar to start the update process. (it's the same way like with the root zip)
cantdownload
Cant download 2nd link
Beware
Hey Guys, after I applied these "updates" and checked root (positive) I installed the Xposedframework , when I rebooted my Memo , it does not get much further then the ASUS logo and never-ending busy circle. I will attempt a factory reset, and let you all know.
Just posting this message to make sure you have your backup done as mentioned in the first post. It could be painful otherwise!
Hi
can u help me root asus zenfone 5 ?
or tell me how to make a update ota zip flashable to flashed on stock recovery..
thx for reply me...
Hi all. Thanks for the great post. This forum helps a lot who would other wise be lost.
I am a bit confused about the methods posted in the opening post. The first method explains DL the files and install from internal storage which seems simple enough. But then I scrolled down to see the second method via fastboot.
I would prefer to use the first method as it appears simple as I have said. But unsure which I should use.
Also how can I backup without root access?
Thanks for your help
Mode l# ME302C
Firmware version: 51.31
Android Version: 4.2.2
Build # US_EPAD-4.6.2-20130815
Edit: I jumped in and used the procedure described in "For those of you who are not rooted "(or the second method of the first 2). It worked. My memopad is now rooted and appears to be operating fine. Thank you to the author of this post.
help needed
Why can't I get the magic yellow triangle? Somebody please help me.
Here are my screen shots from my google+, please remove the blank space at the beginning of the address:
ht tps://plus.google.com/106139843999975472357/posts/818h3Tbagkm
ht tps://plus.google.com/106139843999975472357/posts/Z6J5iTEPswP
Asus302c said:
Why can't I get the magic yellow triangle? Somebody please help me.
Click to expand...
Click to collapse
Try plugging it into a computer or rebooting.
Would installing the latest version of the firmware get rid of the root access? V5.0.19 is the latest, from the end of May. http://usterki.hobby-elektronika.eu/biazet.html
Polarbert said:
Would installing the latest version of the firmware get rid of the root access? V5.0.19 is the latest, from the end of May.
Click to expand...
Click to collapse
Yes and you risk to get big trouble if SuperSU survival mode is active. For save updating you have to remove root first.
Gesendet von meinem ME302C mit Tapatalk
I just wanted to say:
I got the Memo Pad FHD 10: It lagged in slowness a bit in a few well known apps. Also when browsing the internet. Also the kicker for knowing I had to 'Root' was certain apps use the 'System font' for Chinese-Pinyin display. Asus-Memo Factory-font does not display accented characters well. But the standard setting do not allow adjustment to the System-font.
Your Easy instructions under: 'For those who are not rooted'... Were simple. I downloaded the two files... 5.0.16 (Although: Note I needed to rename, the 5.016, to exactly match what you said. The filename was slightly different.)
I was a little scared, even though I had already upgraded the firmware of my Tablet to 51.31, but another poster had that number as well, so I decided to boldly press-on.
Then I put the 5.017 and boom... and installed the SuperSU file as instructed... and a way I went! Thanx! Thankx! :good: I put on HiFonts and found a font that was suitable for the system. The pad is also now so much snappier!!! I hope that doesn't mean the battery is now going to drain at an alarming rate. I haven't tested that yet. :
GPS Working 5017
intrepid24 said:
This post (#377 on page 38) was origina
Click to expand...
Click to collapse
Is anyone else having an issue with the GPS on the device on 5016 rooted with the 5017 using the 'intrepid' link above. A favorite app we use: 'Copilot', does not get past "determining position". I'm speaking of when the device does not have an internet connection.
The app I speak about is designed to work without only the GPS available. But since I'm on an odd build, instead of checking with the problems on those ends. I figured, I worry first about the build itself.
I know this may be quite an old thread, but I've stupidly updated my fathers tablet to 5.0.21, and in the process lost root. Is there any trouble with following this method to get back to 5.0.17 and rooting the tablet? After updating I saw no difference, and thus no need to lose root access.
http://www.gory.pun.pl/viewforum.php?id=5
Is there an alternative to getting root? I've tried towel root and framaroot but neither of these worked.
To this day this tablet has treated me well...Is there any kitkat roms floating around the web for this tablet?
asus memo pad me302c stuck on boot screen
Hi guys! I`m new on the forum so i don`t know if this is the right place to ask... I have this Tablet stuck on boot screen and i tried every solution i found on internet but nothing seems to make it work... Can someone give me a clue about what can i do? Thank you!
I have the same problem. I have this in DroidBoot:
IFWI Version: 51.33
Serial_num: 11111111111111
Product: WW_EPAD
I've tried to flash many files, flashed earlier fastboot versions, but I'm totally stuck here
_MsG_ said:
I have the same problem. I have this in DroidBoot:
IFWI Version: 51.33
Serial_num: 11111111111111
Product: WW_EPAD
I've tried to flash many files, flashed earlier fastboot versions, but I'm totally stuck here
Click to expand...
Click to collapse
What works depends on what you were doing before this issue appeared.
If you can read German, you can check:
http://www.android-hilfe.de/thema/a...k-asus-memo-pad-fhd-10-ab-android-4-3.528918/
I'd recommend trying the RAW update.
Ok now I have the same problem with everyone having this tablet. Many of the apps have been upgraded in the world, but no longer support Android 4.3 anymore. We need at least 5.0 to work. And I can find no custom-roms. At first search I thought one was available, but then found it was not for the ME302C. The 'C' version is the intel chip. We need a wizard to create a rom.
robertkjr3d said:
Ok now I have the same problem with everyone having this tablet. Many of the apps have been upgraded in the world, but no longer support Android 4.3 anymore. We need at least 5.0 to work. And I can find no custom-roms. At first search I thought one was available, but then found it was not for the ME302C. The 'C' version is the intel chip. We need a wizard to create a rom.
Click to expand...
Click to collapse
How did you get the bootloader unlocked to be able to install a custom recovery and then a ROM to begin with? I chatted with Asus support just now and they said that for the ME302C they never made an unlock tool which I don't believe. I have an ME301T and they made the tool for it and I was able to unlock the bootloader, root and custom ROM. I was going to root my friend's ME302C but without being able to unlock the bootloader to install a custom ROM I don't see the point. Thanks in advance!
Asus ME302KL will this be the same process?

[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.

Categories

Resources