Database Info

TNT keeps force closing on newest OTA update

Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.

Follow the instructions in the alternate gtab firmware post. It worked great for me. I would suggest installing cwm so you can back up your existing firmware.
My update would force close during download on the stock firmware. I finally got it to work by minimizing the pop up that displayed the progress. For some reason the screen would crash the download.
Your files should be there but you will lose all user settings and installed apps when you do the factory reset.

This is a common issue with stock, and TnT Lite. The user data seems to be very unstable once you upgrade to different firmware.
The "easiest" thing to do is just wipe the user data. However, if there is certain data you need to keep, I would recommend the excellent Titanium Backup. The only caveat is that the device has to be rooted, to use it.

roebeet said:
The only caveat is that the device has to be rooted, to use it.
Click to expand...
Click to collapse
And Z4root does this easily. Just install and click "root".

RyuFDAC01 said:
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Click to expand...
Click to collapse
Tntlite is that easy I was surprised. Too since rooting my HTC hero a year and a half ago was so much more hands on

Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
I thank you guys VERY VERY MUCH appreciate this

Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
Click to expand...
Click to collapse
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recovery\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recovery/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.

dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
Dude thank you so much for your effort in this !!!!! gonna try this as soon as i put my baby to sleep.... will let you know if this worked for me

dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!

roebeet said:
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
Click to expand...
Click to collapse
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!

dcom222 said:
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
Click to expand...
Click to collapse
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed

RyuFDAC01 said:
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
Click to expand...
Click to collapse
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!

dcom222 said:
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
Click to expand...
Click to collapse
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!

RyuFDAC01 said:
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
Click to expand...
Click to collapse
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
I just flashed the TnT 2.02 again. So far it seems OK, however it did the first 2 times I did it as well. I followed all of the instructions at "forum.androidcentral.com/showthread.php?p=442691#post442691" except I substituted using roeboot's TnT. Once I did it I had everything working (flash, market, etc...). Both times the boot loop happened when I tried to install or uninstall something, and both times were after a few hours of use. I tried a third time and almost instantly got into a boot loop, but I think I got ahead of myself in that try and did some things out of order. The good thing is that I was able to recover each time.
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.

The EULA shows up with a new stock firmware - and yeah 4.1 / 4.2 kinda bugged me too. I never selected "I Agree" - fark that.
As for the boot loops, it seems that we still can't pin it down - maybe it's just random, I don't know.

Hi,
I was stuck after bootlooping using Cyanmod, then flashing NVflash still didnt fix the issue, this fix did it for me. Thanks for getting me back up & running. I will give another shot at using cyanmod now that I have all the files needed to get me back.
BTW< I have a green cloth. What does that mean?
Thanks,
Rich

dcom222 said:
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
Click to expand...
Click to collapse
My tab came with a grey cloth... funny thing though I got mine on the second wave of shipments to sears... I NEVER had any issues with the time i just set it and it kept the time... I remembered that when these first came out that was a problem... i thought mine was diff because i never had any issues with time reseting itself... anyway Thanks again dude for your help hope i could play this forward to someone more noobier than me
Roebeet looking forward to your TnT lites...

dcom222 said:
After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Click to expand...
Click to collapse
I now have clockwork recovery installed... How do i copy the update.zip from external microsd to internal microsd... mounting sd-ext gives an error..
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
Frustration levels are high with this device!!
Thanks!

a "me too" reboot problem
I was able to install TNT Lite 2.0, then 2.11. I got Clockwork Recovery installed as well.
The market would start, but if I did a search for obvious things like "Kindle", the market would give an error that it didn't exist in the market. Thinking it was the error situation described here:
http://forum.xda-developers.com/showthread.php?t=845175
I applied those instructions, and rebooted.
Upon reboot, it ended up in a continual reboot loop.
Trying to do the start with volume+power, it brings up Clockwork Recovery, and when told to wipe data/factory reset, it stays in the reboot loop. When told to apply sdcard's update.zip, it looks only at the one on the internal sdcard, which is for CWR, and goes back into the loop.
At that point I setup a microSD with the information from this post:
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
including changing the line from sdcard to sdcard2. Again it doesn't recognize that the internal sdcard2 is plugged in, and attempts to mount it with CWR (mount /sd-ext) yields the error:
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
So, unfortunately I'm at an impasse, like the previous poster. I just bought the tablet a couple of days ago, so I'm far from expert at tweaking it into working.
Any suggestions on what to do, are greatly appreciated.
PS - Bought the gtablet from Office Depot, and received a green cloth.

Boot into clockwork recovery and go to advanced and format SD, use the 2gb and 512mb I believe, then flash TNT or another rom. That fixed my boot loop.

[Q] TF boots, flashes locked screen for a second and shuts down! :(

Hello friends, Please note that i tried installing ClockworkMod 3.1.0.1 but it refused to setup for some reason, even though i did everything right i.e. holding down the down vol key and power button etc but like others i only get the green android with the exclamation mark in the middle, so i do not have a backup unfortunately ;(
Anyway the story starts here:
Please be patient with me though as i am new to all this but learning fast.
Got a new Asus transformer TF101 (with keyboard) for only 5 days with
Device serial: B70KAS3?????
Build number: HMJ37.WW_epad-8.4.4.11-20110711
Android version: 3.1
Didnt know about Razorclaw ability to root B70 :-(
Anyway on going online on the TF101 for the first time, I immediately got a message saying there was a new os update available, the TF101 auto downloaded it and i then immediately updated it, thinking that the new update was best for me :-(
After the update, i then had -
Build number: HTK75.WW_epad-8.6.5.21-20111216
Android version: 3.2.1
Razorclaw doesnt work on my TF101 however i was able to use use the WW_epad-user-8.6.6.19.zip update on it and then was able to root using Razorclaw.
After that everything worked fine until i used 'Rom Manager' to create a script that was to change my hostname to my preferred one instead of the usual 'android_????????????', i then set it to do so on boot within 'Rom Manager'.
I then used 'Rom Manager' 'reboot' script to reboot the TF and now it boots then flashes locked screen for a second and shuts down and the same thing happens when i power it up again
If i am lucky and quick, i can put in the password and see the desktop just before it shuts down.
I have a feeling it the script i created and set to execute on boot is what is causing the shutdown.
Is there anyway to fix this?
It not a low battery issue, already checked that.
Was thinking along the lines of a key combination to prevent scripts running on boot time.
Dont really want to wipe the TF, as it already taken me 5 days to get it setup how i want it and now this!

It sounds like you have a stock recovery and a buggered up system.
You might be able to recover with adb, but you'll have to know what to stop/kill before it reboots. If it's enable, adb will be active well before you see the lock screen. There might also be some tools in the android sdk, perhaps ddms.
What exactly is in this rom manager script? Perhaps it is passing a reboot via one of the partitions. You would need to clear the command to stop the reboots or just kill the process that is rebooting.
That's all I gots. Good luck!

gee one said:
It sounds like you have a stock recovery and a buggered up system.
You might be able to recover with adb, but you'll have to know what to stop/kill before it reboots. If it's enable, adb will be active well before you see the lock screen. There might also be some tools in the android sdk, perhaps ddms.
What exactly is in this rom manager script? Perhaps it is passing a reboot via one of the partitions. You would need to clear the command to stop the reboots or just kill the process that is rebooting.
That's all I gots. Good luck!
Click to expand...
Click to collapse
thanx for responding mate...appreciated.
the script is just a simple script with just one line with tr3ble being the new hostname, its exactly as below:
setprop net.hostname tr3ble
I'll have a tinker with adb but what how do i search for processes to stop/kill using adb as im not that clued up with linux commands

I'm not a pro either, but I think "ps" will show you the process and "kill <pid>" will kill them. There might be a better way and I haven't tested this, so if you end up in a worse situation than then one you are in, it's all on you.
I don't think that changing the hostname will cause a reboot. I think the "reboot" command from rom manager is somehow stuck. I think it passes a reboot command via one of the partitions so that it can "find" it when it restarts. You would just have to clear the command. I think it's somewhere in the /cache directory, but that is just a guess.

gee one said:
I'm not a pro either, but I think "ps" will show you the process and "kill <pid>" will kill them. There might be a better way and I haven't tested this, so if you end up in a worse situation than then one you are in, it's all on you.
I don't think that changing the hostname will cause a reboot. I think the "reboot" command from rom manager is somehow stuck. I think it passes a reboot command via one of the partitions so that it can "find" it when it restarts. You would just have to clear the command. I think it's somewhere in the /cache directory, but that is just a guess.
Click to expand...
Click to collapse
Wow...you are definitely pointing me in the some direction though, in the begining i didnt have a clue what to do and where to look but now i have a few things to try...i'll see how things go with adb and report back.
Thank you for your time and patience mate

Update:
I tried everything i could but just didnt seem to have much time to do much using adb so i bit the bullet and did a data wipe, but to my joy, after the data wipe the TF was still rooted and my adhoc hack was still in place. If only took me bout an hour to then reinstall all my apps, which was more or less easy as i had them all in one folder on my microSD.
So all in all, the data wipe which cured the shutdown after restart wasnt sooo bad afterall.
Thank for your help mate!
....Happy New year!

b00b said:
Update:
I tried everything i could but just didnt seem to have much time to do much using adb so i bit the bullet and did a data wipe, but to my joy, after the data wipe the TF was still rooted and my adhoc hack was still in place. If only took me bout an hour to then reinstall all my apps, which was more or less easy as i had them all in one folder on my microSD.
So all in all, the data wipe which cured the shutdown after restart wasnt sooo bad afterall.
Thank for your help mate!
....Happy New year!
Click to expand...
Click to collapse
Did the same exact procedure when the same thing happened to my TF earlier this month.... Good to know that i wasn't the only one that faced this situation.
Sent from my Transformer TF101 using xda premium

[Tutorial] Proscan PLT-7035-PL Root and install GAPPS

Rooting and installing Google Play on the Proscan PLT7035-PL ** UPDATED **
*** Disclaimer ***
I am not responsible for bricked tablets, voided warranties, crashed computers and/or global thermonuclear war! This is what worked for me if you are unsure of anything in the following steps STOP NOW! There is no factory rom released for this tablet. If you brick it your possibly stuck until if and when they release an update!
These instructions assume you are competent to do the folling: get files on and off of your device using the mass storage driver, able to edit and understand changes to inf files, use command prompt, edit system user files and have enough patence to read all of the steps without skipping any. There are a few gotcha's that if are skipped will leave you pulling your hair out. Also these instructions are written for Windows. If your using Linux you shouldn't need my help anyways ..​
Click to expand...
Click to collapse
This tutorial may also work on other Chinese generic tablets. You would only need get the hardware vendor and product ID's from the device info for step 2. For the purpose of this post I wont be getting into that but the information is out there.. GOOGLE IS YOUR FRIEND
Introduction
Its likely if you are reading you have recently visited Big Lots and scored a $69 7" tablet. Only to get home and find virtually NO information on rooting it or installing Google Play or GAPPs. I know I was in that boat but after a few hours of messing around I got it. I am writing this to hopefully help the hundreds of others I see out there asking for help on this.
Step 1 Download Stuff (Things to round up before you even think about starting)
Root with Restore by Bin4ry v15 - http://forum.xda-developers.com/showthread.php?t=1886460 .** UPDATE ** I attached the version I used to this post
ADB Drivers - You have several options here, milage may very.** UPDATE ** I attached USB drivers to this post. I had to seperate the 64 and 32 bit drivers to get the files under the 8 mb limit for uploads
install android SDK http://dl.google.com/android/android-sdk_r21-windows.zip and follow instructions to get the google usb drivers. Search XDA there are several guides, I couldn't find the one I used as of writing this article but there are many out there.
Search google and find a zip with just the ADB drivers.
Download Super One Click Root and use the drivers in the tools directory of the zip. http://forum.xda-developers.com/showthread.php?t=803682
Root Explorer - quick way to move and remount file systems rw with ease. I used v2.13.1. Google around and find an APK to install, just be careful there is another completely differnent package out there called "rooted explorer" it may work but I have not tried it. ** UPDATE ** I attached the version I used to this post
Google Apps for ICS - gapps-ics-20120429-signed.zip is what I used from http://goo.im/gapps/gapps-ics-20120429-signed.zip ** Update ** I replaced the URL with a direct download link from goo.im enjoy!
**NOTE** SUPER ONE CLICK ROOT WILL NOT ROOT YOUR TABLET SO DON'T BOTHER TRYING!
Step 2 install and configure your ADB USB Drivers (Let the fun begin)
Extract your zip file containing the ADB USB drivers or Install the Android SDK and follow instructions on how to use the SDK manager to download the lastest drivers from google.
Once downloaded edit the inf file (usually named android_winusb.inf)
Add the following under the [Google.NTx86] heading and again under the [Google.NTamd64] heading: (one is for 32bit systems and the other is for 64 bit Systems)
Code:
;ProScan plt-7035
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&REV_0222&MI_01
After saving and exiting. Turn on USB Debugging on your tablet. It is under Settings => Developer Options and is the first option at the top make sure it has a check in the checkbox. Exit the developer screen by pressing back or the home key and plug in your tablet to a usb port on your computer using a micro-USB cable.
Device detection should at this point detect a few devices but at least 1 will fail without drivers. Possibly more on XP systems..
Under Device Manager => Other Devices you should have a device called "PLT7035-PL" use the usb drivers modifed above to install the ADB USB Drivers.
*** Important Note ***
At this point even with the ADB Driver installed ADB will not see the tablet. We have to create or edit the file c:\users\whatever your username is\.android\adb_usb.ini
If you have already run ADB at any time on your system the file and directory should already exist. If not you will need to create the directory and the file.
on a single line simply add this to a blank line in the file and save and exit:
0x2207
This tells ADB to look for that vendor code. (if you allready have ADB on your computer 'adb devices' should now show your tablet.
** UPDATE ** This is still necessary even if using the drivers attached to this post!​
Click to expand...
Click to collapse
Step 3 Root your Tablet!
*** Warning ***
I almost bricked my tablet on this step due to an error with a faulty PlayStore I had tried to install just using the APK. It kept the tablet from rebooting properly during the root process! I recommend erasing all user data before continuing YOU HAVE BEEN WARNED!
Click to expand...
Click to collapse
Extract Root with Restore by Bin4ry v15 to the directory of your choosing.
From explorer on your pc double click the RunMe.bat and select option one.
This particular root uses the system restore function to gain root access. If everything goes right you should get a prompt on the table to restore an image.
Click to expand...
Click to collapse
Press restore ON THE TABLET without entering a password or changing anything else and after a minute or two (maybe more) it should reboot.. Do some more stuff then reboot one more time and you should now have a rooted tablet.
Step 4 Copy root explorer and gapps-ics-20120429-signed.zip to the internal storage of the tablet.
Make sure the tablet is plugged into your computer and turn On USB Storage.
Copy rootexplorer.apk and gapps-ics-20120429-signed.zip to the Downloads folder via windows explorer and the removeable drive from the tablet.
Step 5 Install root explorer
ON THE TABLET: to applications => explorer => Internal memory => Download => rootexplorer.apk
This should bring up the apk installer and ask for permission to install rootexplorer. Follow the prompts until rootexplorer is installed.
Open root explorer. The first time you open it if everything is right you should get a prompt from SU to allow root access, hit grant. After that you might get a message that you need to close and reopen root explorer again, this is completely normal.
Step 6 Remount File Systems r/w
Once root explorer is open and has root access you should be in the root directory of the device.At the top you should see a message that says "Mounted as r/o" and a button to the right of it that says "mount as r/w".
Click to expand...
Click to collapse
Click the button to mount / as rw.
The message at the top should change to "mounted as r/w" and the button should change to "mount as r/o"
Click to expand...
Click to collapse
Scroll to the system folder and open it.
At the top you should see a message that says "Mounted as r/o" and a button to the right of it that says "mount as r/w".
Click to expand...
Click to collapse
Click the button to mount /system as rw.
The message at the top should change to "mounted as r/w" and the button should change to "mount as r/o"
Click to expand...
Click to collapse
Now click on the ../ Parent Folder icon on the top to go back to the root directory,
Step 7 Extract GAPPS
Scroll to and tap sdcard
Scroll to and tap Download
You should see the google apps file we copied earlier.
Click to expand...
Click to collapse
tap and hold on gapps-ics-20120429-signed.zip until the menu comes up and select "extract all" this will extract the zip file to /sdcard/extracted/gapps-ics-20120429-signed/
Step 8 Copy Google APPS to /system
Scroll to and TAP .. Parent folder at the top to go back a directory to /sdcard/
Scroll to and TAP extracted
Scroll to and TAP gapps-ics-20120429-signed
You should see 5 items, install-optional.sh, META-INF, optional, system and the ../ Parent Folder link.
Click to expand...
Click to collapse
*** WARNING *** Do not click on the install-optional.sh bad things might happen!
Click to expand...
Click to collapse
TAP and hold on the system folder until the menu comes up and select copy.
This will place a paste button on the bottom of the screen be careful not to hit it yet or you will have problems.
Click to expand...
Click to collapse
TAP ../ Parent Folder until the directory at the top says / (you should have to go back 2 or 3 folders)
You should now see a bunch of folders in the root directory as well as the tablets system folder. There should NOT be a ".. Parent folder" visible.
Click to expand...
Click to collapse
Now hit the paste button on the bottom left. You should get a warning massage saying "system already exist. Do you want to overwrite it?" hit yes
The file copy takes 1 to 2 minutes when it is done all that is left is to remount the / and /system folders r/o and reboot the tablet
Click to expand...
Click to collapse
Step 9 Remount file systems r/o
At the top you should see a message that says "Mounted as r/w" and a button to the right of it that says "mount as r/o".
Click to expand...
Click to collapse
Click the button to mount / as ro.
The message at the top should change to "mounted as r/o" and the button should change to "mount as r/w"
Click to expand...
Click to collapse
Scroll to and TAP system
At the top you should see a message that says "Mounted as r/w" and a button to the right of it that says "mount as r/o".
Click to expand...
Click to collapse
Click the button to mount /system as ro.
click the back icon on the bottom left until you have exited root explorer.
Press the power button on the top of the tablet and turn it off and back on.
If everything went right you should now have a fully functioning rooted tablet with Google Playstore...
Click to expand...
Click to collapse
WASN'T THAT FUN!!?!?!

Ive tried this several times. It hasn't worked yet. Maybe I am doing it wrong, not sure. Ill keep trying but I am losing hope.
I am trying with a Proscan PLT7035-PL

worked ... Many thanks to amjtech ...
Here's how to do it:
Install Android SDK, then install Android SDK Tools, Android SDK Platform-Tools, Google USB Driver (download from google)
Install PdaNet for Android on PC.
Attach Proscan pad, check Settings->Developer options->USB debugging to on
XP install adb driver - if unsuccessful, need modify registry
regedit under HKLM/SYSTEM Permissions -> Advance, check replace permission entries on all child
(http://www.tomshardware.com/forum/252428-45-installation-failed-access-denied)
Install USBDeview, run to see usb device attached, get device ID of PROSCAN pad (0x2207)
Add device ID to file adb_usb.ini in c:\docume~1\<user>\.android, also add google's id:
0x2207
0x18d1
(http://forum.xda-developers.com/showthread.php?t=1479311)
(http://androidforums.com/kindle-fir...k-how-get-adb-running-root-superoneclick.html)
Now device will show running
Install ICS Root Unlocker 1.0, run ... got rooted.
Download Root Explorer (2.21.1).apk, Google Play Store (3.8.16).apk, and gapps-ics-20120429-signed.zip from 4shared
http://www.4shared.com/folder/k86VyEKK/_online.html
follow the rest of the instruction (http://forum.xda-developers.com/showthread.php?t=1993013)
... reboot proscan ... voila !!!

Help me!! please!!
I pushed the reset button then right now it's stay at recovery mode ever and I don't what firmware name it's using.. Someone help me find the link to download firmware and teach me how to restore it!! thanks very, very much!!

Factory ROM
tnan0906 said:
I pushed the reset button then right now it's stay at recovery mode ever and I don't what firmware name it's using.. Someone help me find the link to download firmware and teach me how to restore it!! thanks very, very much!!
Click to expand...
Click to collapse
Unfortunately as stated above there is no factory rom available for these tablets yet... I am looking into using rkflash or rkflashtool to download my rom prerooted so I have a backup and also can post a rooted rom for everyone. Most likely later this week I should have some time to figure out the rkflashtool and get it dumped.
I will post it here once it is done.
I'm going to say this now. I have a very busy schedule so I cannot guarantee when I will get this accomplished.
Also if this works for you please hit the thanks button.

Stuck
Humphrey1989 said:
Ive tried this several times. It hasn't worked yet. Maybe I am doing it wrong, not sure. Ill keep trying but I am losing hope.
I am trying with a Proscan PLT7035-PL
Click to expand...
Click to collapse
How far are you getting? Were you able to get root?

Rom Backup
amjtech said:
Unfortunately as stated above there is no factory rom available for these tablets yet... I am looking into using rkflash or rkflashtool to download my rom prerooted so I have a backup and also can post a rooted rom for everyone. Most likely later this week I should have some time to figure out the rkflashtool and get it dumped.
I will post it here once it is done.
I'm going to say this now. I have a very busy schedule so I cannot guarantee when I will get this accomplished.
Also if this works for you please hit the thanks button.
Click to expand...
Click to collapse
Thanks thanks thanks!! Please upload your backup from you for me! I think it will work because same products!! please as soon as possible!! Thanks you, thanks you very very much!!!

Confused as heck !!
OK, I am confused as heck here. I have the SDK installed. I have the USB Drivers installed. The PC sees the phone just fine, I can browse the internal storage and the external sd card with no problem. Windows XP Device Manager shows Android Phone, and under that the Android Composite ADB Interface.
PDANet works with the phone, no problem. However, adb devices never shows the device, and the Root program cannot find it either. At this point, I'm stumped. Any ideas what I need to do? I have put the android_usb.ini file in c:\Documents and Settings\myusername\Android with the necessary hex codes for the device and for Google. I'm going nuts here!
I know ADB is installed properly, because I can plug my phone into the PC and run adb devices, and it's detected just fine. It's just this tablet it can't find.
FIX: Not as obvious as it might have been, but here is the solution to my problem. I used the Search function to find the adb_usb.inf file - umm... it's in .android, not android. Once I added those ids, everything was fine.

No Market?
Achieved root, copied over the system folder from the zip, but no market. Did I miss something?

What about Recovery?
Just wondering if there is a recovery option as yet? That would be so helpful!
---------- Post added at 08:13 AM ---------- Previous post was at 07:28 AM ----------
spycom773469 said:
Achieved root, copied over the system folder from the zip, but no market. Did I miss something?
Click to expand...
Click to collapse
Yeah, this happened to me too. And for some reason, when you go to the \system folder and look in apps there is another apps folder in there. I think there is something really odd going on with root manager possibly. I don't know what the deal is, but none of the Google Apps are running.
I've tried several older 4.0.x versions of GAPPS, and I will be danged if I can get any of them to work. I'm rooted OK, but that's all that worked thus far.

Good instructions! But failure... and then success
The instructions were great above! The pointer to the version of google play was bad, but I found this link http://forum.xda-developers.com/showthread.php?t=1934441 and after using Root explorer to do the appropriate permissions at / and /system, and on the renamed file, it works!
---------- Post added at 06:17 AM ---------- Previous post was at 06:06 AM ----------
Now that I got Google Play to work...
I am having an odd problem however - the installation of apps stalls at 0% for about 30 seconds, and then continues. And as the percentage is updated, I see app screens cycling. And little google play shopping bags start to stack up in my "task tray" area of the tablet.
Does anybody else have that problem? It's very annoying! It seems like the downloaded apps not only install but open, eating up precious memory.
Speaking of which, how is the flash memory used? (4 GB), and not having apps take up the 500 MB that's available?

jmasters said:
Speaking of which, how is the flash memory used? (4 GB), and not having apps take up the 500 MB that's available?
Click to expand...
Click to collapse
It is 4GB shared. I haven't tried looking at the partition table.
There is only 2GB usable, it's on the TF card, I moved the apps there.
Not sure how to access the SD card to put apps there.
netizenmt said:
Yeah, this happened to me too. And for some reason, when you go to the \system folder and look in apps there is another apps folder in there. I think there is something really odd going on with root manager possibly. I don't know what the deal is, but none of the Google Apps are running.
I've tried several older 4.0.x versions of GAPPS, and I will be danged if I can get any of them to work. I'm rooted OK, but that's all that worked thus far.
Click to expand...
Click to collapse
My GAPPS are working fine. I thought about killing that /system/system folder and manually placing the files via adb.
Try checking the permissions too, I think they need to be 644 or better.
I've put the Tablet away for now, I will tinker again later probably.
Sent from my DIRTY Jelly Bean EVO 3D

How to move apps internally to TF card?
spycom773469 said:
It is 4GB shared. I haven't tried looking at the partition table.
There is only 2GB usable, it's on the TF card, I moved the apps there.
Not sure how to access the SD card to put apps there.
How do you move your apps there? I'm aware of the app called something like app2SD, but the TF card isn't an SD card.
Click to expand...
Click to collapse

jmasters said:
spycom773469 said:
How do you move your apps there? I'm aware of the app called something like app2SD, but the TF card isn't an SD card.
Click to expand...
Click to collapse
If you go to the Apps tab under the system settings you will see a button that says "Move to TF Card"
Sent from my DIRTY Jelly Bean EVO 3D
Click to expand...
Click to collapse

netizenmt said:
Just wondering if there is a recovery option as yet? That would be so helpful!
---------- Post added at 08:13 AM ---------- Previous post was at 07:28 AM ----------
Yeah, this happened to me too. And for some reason, when you go to the \system folder and look in apps there is another apps folder in there. I think there is something really odd going on with root manager possibly. I don't know what the deal is, but none of the Google Apps are running.
I've tried several older 4.0.x versions of GAPPS, and I will be danged if I can get any of them to work. I'm rooted OK, but that's all that worked thus far.
Click to expand...
Click to collapse
You have to extract the zip file, remount the file systems as rw and copy the /system folder from the zip into the / of the device so that all the files goto their proper places... if you have /system/system it was not copied correctly...
as far as those not getting ADB to reconize the tablet.. a) make sure you have usb debugging turned on and b) you put the hardware id in the adb_usb.ini file.. See the ** important note ** in Step 2!

Unzipping Files
I have read and followed your directions to download the files, but, my unit keeps saying it can not open any zip files.
Do you have any idea why it may say this or how to get around this problem so I can continue as instructed?

unzip on your computer and transfer over, or use root explorer
bluetxsteel said:
I have read and followed your directions to download the files, but, my unit keeps saying it can not open any zip files.
Do you have any idea why it may say this or how to get around this problem so I can continue as instructed?
Click to expand...
Click to collapse
You can unzip them on your computer and then transfer them over, or use root explorer on your tablet. You'll have to hold your finger on the .zip file for a few seconds and then the unzip option pops up.

Well, everyone be careful! When my Google Play would not install properly, I tried to clean the tablet up, ie, put it back to its original condition. Somehow, I managed to cause something to crash, and from then on, the tablet won't boot past the Android startup screen, although I can adb into it and it is still rooted, etc. What I've got now is a project tablet - HOW TO UNBRICK THE BRICK.

my bricked too
netizenmt said:
Well, everyone be careful! When my Google Play would not install properly, I tried to clean the tablet up, ie, put it back to its original condition. Somehow, I managed to cause something to crash, and from then on, the tablet won't boot past the Android startup screen, although I can adb into it and it is still rooted, etc. What I've got now is a project tablet - HOW TO UNBRICK THE BRICK.
Click to expand...
Click to collapse
I hope you do so or some body find a way to unbrick this thing as for me i still have 26 days to return mine.i got to the part where I was about to paste the system I hit yes then everything locked up. I noticed before I hit yes it said do you want to merge and copy the files over not do you want to overwrite it but I still hit yes bad idea. can anybody tell me why I said merge and copy. well this is the second one I have bricks follow the steps perfect got all the way to the end and this is what happens so I took the first 1 back guess I'm going to take a second back also and try again until i figure out what I'm doing wrong.has anybody maked a rkimage or a .zip. update that will work to re cover this thing. I would be willing to try it out for you because I can.

netizenmt said:
Well, everyone be careful! When my Google Play would not install properly, I tried to clean the tablet up, ie, put it back to its original condition. Somehow, I managed to cause something to crash, and from then on, the tablet won't boot past the Android startup screen, although I can adb into it and it is still rooted, etc. What I've got now is a project tablet - HOW TO UNBRICK THE BRICK.
Click to expand...
Click to collapse
try doing an ADB shell
then the following commands
su
wipe data
this will reset the user partition. I had something similar happen on mine.. BTW 'wipe all' will definitly brick your tablet so be carefull
If you still cannot get it I was almost in a car accident yesterday and my tablet went flying and broke the screen... If you confident with a soldering iron I now have a plt-7035 mainboard prerooted and playstore installed for sale for $25 including shipping.. it would involve soldering 6 wire and the wifi antenna if your up to it pm me,, I know its good as I was able to ADB into it and run su and wipe data to reset it..
-Andrew

[Q] Can't Get CWM Install To Stick

I recently acquired a Photon Q LTE after being an Epic 4G user for years. I've flashed and rooted and beat that Epic 4G to bits over the years, but I can't seem to get CWM installed on this device for the life of me.
I've verified I've unlocked the bootloader and followed the directions in shabby's thread (http://forum.xda-developers.com/showthread.php?t=1856480) and on a couple other sites (http://www.andromods.com/basic-how-...r-user-install-cwm-recovery-photon-q-lte.html and http://www.androidegis.com/how-to/root-and-install-clockworkmod-recovery-on-motorola-photon-q-4g/), but it never seems like CWM wants to stick. Fastboot sends the file fine and says it writes it, but whenever I try to boot into recovery, I get the old school factory recovery with the Red Triangle and the Android System Recovery (3e) header, which is the factory bootloader (right?). Obviously SU isn't going to load in there.
My wife was playing with my new phone before I had a chance to do so (it was a gift), and I think she ran the latest OTA updates before I had a chance to even touch it. Looks like I'm running SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4, so I don't know if this has been tested with that or if I'll need to revert to a lower version, root, and then upgrade.
Any help would be greatly appreciated.
Thanks!

sometimes stock ROMs have a file in the system folder called recovery-from-boot, which reinstalls stock recovery on boot. if you have flashed SU, try looking in /system, and if that file is there, you can rename it to recovery-from-boot-bak, and that should disable it.

yogi2010 said:
sometimes stock ROMs have a file in the system folder called recovery-from-boot, which reinstalls stock recovery on boot. if you have flashed SU, try looking in /system, and if that file is there, you can rename it to recovery-from-boot-bak, and that should disable it.
Click to expand...
Click to collapse
I haven't been able to get SU installed as I can't get CWM installed. Is there another way to push SU to the phone without CWM?
Running terminal emulator, I can see there's a recovery-from-boot.p file /system, which is probably my issue. So basically, I need to get SU on there somehow to kill it, unless there's a way to kill that file with desktop adb or something.

orty said:
I haven't been able to get SU installed as I can't get CWM installed. Is there another way to push SU to the phone without CWM?
Running terminal emulator, I can see there's a recovery-from-boot.p file /system, which is probably my issue. So basically, I need to get SU on there somehow to kill it, unless there's a way to kill that file with desktop adb or something.
Click to expand...
Click to collapse
ok, i see. damn that's odd, because i haven't seen anyone run into this. i'm trying to think if there
is a way to boot straight into recovery from the bootloader, without booting up the system. i don't think you will be able to modify the file in /system without SU.
---------- Post added at 09:15 PM ---------- Previous post was at 09:11 PM ----------
come to think of it, i think there is a rootkit somewhere here that will install SU without flashing recovery. can't find it atm tho... but i believe it is said to still work on your software version..
actually if i remember correctly, i think it might be Dan Rosenberg's Motofail2Go exploit:
http://forum.xda-developers.com/showthread.php?t=1940594
the other thing you might try is flashing TWRP recovery instead of CWM. i am not sure but maybe TWRP automatically disables the recovery-from-boot file. i used TWRP and i see my file is already renamed and i never consciously did that!

I'll try to get a few minutes tonight and give that a whirl. Will report back as soon as I can.
Thanks!

orty said:
I'll try to get a few minutes tonight and give that a whirl. Will report back as soon as I can.
Thanks!
Click to expand...
Click to collapse
i just posted at the same time as you, so if you didn't see it, perhaps TWRP recovery is worth trying too!

Motofail2go got SU installed, which allowed me to rename that file. Then was able to follow the procedure to install CWM just fine.
Thanks much for the help!

Great, glad you got it working!

Did CWM not stick on my Photon Q ?
What is the key sequence to boot into CWM on a motorola photon Q ? I did an motorola upgrade before I tried any of this so my version nmbers are the same as orty.
SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4
Here's how it went. - The bootloader unlock seemed to work fine. Things were a little hairy with the CMW install. I am doing this on ubuntu and much like orty I had to make the best guess from various posts. Since I'm not sure of the key sequence to boot for CWM - you can bet I was not holding any buttons when the thing rebooted after downloading CWM. I looked around for a while before I found anything about the key sequence and now if I try a boot holding power & volume up I get an dead android with an red triangle ! in his tummy. I gather this means failure. I did however manage to install Superuser from ChainsDD. Does having Superuser installed mean anything about whether I have CWM installed or not? I am confused! From this post I gather I should try the CMW install again and hold the buttons when it reboots? What do you see to indicate you are in CWM? Some sort of menu?
If I knew how I would try and use the installed SU to look in /system to see if there are any of the mentioned files.
Can somebody give me some clues on next steps I can try at home tonight. Much appreciated!!

penguinpal said:
What is the key sequence to boot into CWM on a motorola photon Q ? I did an motorola upgrade before I tried any of this so my version nmbers are the same as orty.
SW Version 77.8.10.XT897.Sprint.en.US and Android Version 4.0.4
Here's how it went. - The bootloader unlock seemed to work fine. Things were a little hairy with the CMW install. I am doing this on ubuntu and much like orty I had to make the best guess from various posts. Since I'm not sure of the key sequence to boot for CWM - you can bet I was not holding any buttons when the thing rebooted after downloading CWM. I looked around for a while before I found anything about the key sequence and now if I try a boot holding power & volume up I get an dead android with an red triangle ! in his tummy. I gather this means failure. I did however manage to install Superuser from ChainsDD. Does having Superuser installed mean anything about whether I have CWM installed or not? I am confused! From this post I gather I should try the CMW install again and hold the buttons when it reboots? What do you see to indicate you are in CWM? Some sort of menu?
If I knew how I would try and use the installed SU to look in /system to see if there are any of the mentioned files.
Can somebody give me some clues on next steps I can try at home tonight. Much appreciated!!
Click to expand...
Click to collapse
Yeah, sounds like you got into recovery properly by holding volume up while powering on. But it also sounds like your CWM might have gotten overwritten. If you did get SU installed, you can use a file program like Root Explorer or ES File Explorer to look for recovery-from-boot.p in your /system directory, and rename it to recovery-from-boot.bak. then reflash CWM.

smorealt rorer
Ok so a little program to browse for files. I'll load that because I'll blow it away when I redo CWM anyway.
---------- Post added at 11:01 AM ---------- Previous post was at 10:48 AM ----------
Yip there is it - recovery-from-boot.p in /system - so just so I understand - If I rename it now -does this mean it will not be drop-dead necessary to boot straight into CWM after I download CWM onto the phone and it reboots - because the phone won't be setup to undo the CMW anymore.
Also - am I correct that you can make backups using CWM?

penguinpal said:
Ok so a little program to browse for files. I'll load that because I'll blow it away when I redo CWM anyway.
---------- Post added at 11:01 AM ---------- Previous post was at 10:48 AM ----------
Yip there is it - recovery-from-boot.p in /system - so just so I understand - If I rename it now -does this mean it will not be drop-dead necessary to boot straight into CWM after I download CWM onto the phone and it reboots - because the phone won't be setup to undo the CMW anymore.
Also - am I correct that you can make backups using CWM?
Click to expand...
Click to collapse
Yep, correct on both counts you'll see the option 'backup and restore' in CWM.

Well no go on the rename - recovery-from-boot.p cannot be renamed because the file system is read-only.
I installed Total Commander and when I try and remount / as r/w with it I get re-mount error su called failed. Seems my su is not the real thing.
Will it work if I install CWM and boot straight from the download into the CWM - can I rename the file from there somehow?

If you can get adb access in CWM, there should be a command to rename that file, i'm not sure if it would be from adb shell or not... perhaps Google it or someone else will chime in here. You would probably need to flash SU first, then try adb and type su first and see if you get # prompt.
Otherwise you can go thru the full cycle- flash CWM, boot straight into recovery, flash SU, reboot and rename the recovery file, reflash CWM. Using adb in CWM would be the more elegant way, haha.

I am OK with full cycle - just explain this to me --> boot straight into recovery, flash SU,
I think I know how to boot straight into recovery -> but how do I flash SU from there?
Do I have to get the su.zip onto the phone before I boot into recovery? How do I do that?
Which reminds me of another question the http://forum.xda-developers.com/showthread.php?t=2017748 thread says
Bugs:
Usb mass storage isnt working,
Is this still true? Does this mean if you install CWM you can't mount your phone as mass storage in anyway ?

Yeah, load the SU zip onto your phone before going into CWM, since usb storage might not mount. Easiest way might be just to DL the zip on the phone by going to the thread on the phone, then navigate to your downloads folder in CWM to flash it. Otherwise if you have a more recent version of Ubuntu, you might be able to access device storage thru usb to transfer the zip... or else you can do that in Windows(or Mac maybe?).
Edit: flashing CWM won't break usb storage in general, it just doesn't seem to mount in CWM.

Great - so I downloaded the SU.zip from my phone and it is in /sdcard/Download for later. So I assume loading CWM does not erase what is in the download folder ?
And thanks for explaining that CWM just break usb mount in CWM not generally.
Much Much appreciated.

CWM shouldn't erase whats in the download folder. If it does, there's an issue there.
And why not just use MotoFail2Go to push in SU and then use RomManager from the appstore to flash CWM from the OS itself, because that fixes the rewrite issue as well and is a much simpler process?
CMNDR

since I am using ubuntu the word "windows" in the link did not draw me in .... am I missing something?
http://vulnfactory.org/public/motofail2go_windows.zip

penguinpal said:
since I am using ubuntu the word "windows" in the link did not draw me in .... am I missing something?
http://vulnfactory.org/public/motofail2go_windows.zip
Click to expand...
Click to collapse
i always keep a Windows installation around, just for certain programs. but, by doing this the manual way, at least you get to see what is being done, instead of programs doing it for you

TWRP backups

So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:

mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.

exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.

mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.

mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.

robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!

mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?

mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.

TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??

mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.

I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks

What version of twrp ?
I only use rc1, never seen this.

Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.

pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.

Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks

pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?

Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.

pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.

Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.

pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.