Related
Hi,
I got a GTablet for Christmas today and I seem to have had some bad luck with it...
When I first got the tablet, it wouldn't keep any of my settings (not the wifi connection, not the development settings, nothing).
I thought I could get around this by flashing a different image (I am a novice user, though I do have a very modded N1 -- except it's still stock, sort of).
So... I did not have a MicroSD card at all (it's Christmas, all the places are closed until Monday, and I did not anticipate any problems). Still, I was able to flash the image of TNT Lite...Sort of. I had no problems upon booting, with the familiar N1 X boot animation.
I could add things to the stock Android launcher included with TNT Lite, but not remove them (as soon as I sled the icon I wanted to remove over to the 'trashcan', it force-closed the launcher, but my icon was removed nonetheless).
I did have a slightly working Market (I had the half-star issue). I did not have Titanium Backup installed, so I attempted to restore a working Market by force-closing and clearing the data of the 'Google Services Framework' and 'Market' services... Didn't work, like I thought, so I then tried to sideload Titanium Backup.
There is where my big, big problem came up. As soon as I tried to load TB onto my GTablet, I had tons of Force-Closes (and the tablet sort-of half rebooted). So, I got them to go away and tried again. Same thing.
So, I gave up and vowed to try again tomorrow. Except, I might not be able to tomorrow... As soon as I turned the tablet off, all was A-Okay for the most part... Later, I thought I'd try a little earlier than tomorrow, so when I turned it on.... I didn't get any farther than the GTablet logo before I realized I was in an infinite boot loop.
Now, I'm stuck with a boot-looping GTablet and a not working Christmas present! Help, please.
EDIT @ 3:44AM (Dec 29, 2010)- [FIXED]
FIXED!
When you get an sdcard you can do a fresh install from the external sdcard.
Yeah, I know that.
I don't know if I'll be able to rescue it or not (like I said, I'm new to this, and I was under the impression that [Power]+[Volume-UP] meant 'load recovery mode' which would look like the one I use on my Nexus One).
Do you think I should try (if I can get out of the infini-boot) flashing to TNT Lite (the latest, I think 3.1.0.1 or something similar)?
I'm wary of flashing to that one again, since it seems to have some serious problems with my particular tablet (I searched and there were no similar problems to mine that I could find).
I don't know if I'll be able to sideload Titanium Backup, are there any alternatives to that in getting a working Market (I tried anything else I could think of, but nothing was ever able to sideload onto my Tablet, ever)?
Have you installed Clockworkmod recovery?
Read the main threads (tnt lite, vegan, installing gapps) and I believe you will find someone has had the same problems you have
Hi there! I got the MicroSD card today.
So, I was looking through the guide I had previously used (http://forum.xda-developers.com/showthread.php?t=842004) and now I'm going to try to install ClockWork Mod recovery .8 (the one they said works best here).
I will update this (or maybe make a new message if you don't mind, if I can't edit my posts) if I can successfully get it working.
EDIT @ 12:47AM (Dec 29, 2010)- [Downloading the recovery mod file]
I downloaded the 'gtab-cwm-v08.zip' file to my MicroSD card, and extracted the 'update.zip' and 'recovery' folders inside (I imagine that is correct).
Then, took it out of the computer and loaded it onto my GTablet. I turned it on and did the recovery combination with [Power]/[Volume-UP].
It gave the screen that said it was loading the image and then another screen (black with 'ANDROID' and some other text on the screen).
For just a second, an error-type screen flashed on the screen (big warning icon, not sure how to describe it, but there was no text nor a loading bar).
Then, it rebooted (and then again and again, so it's not fixed yet).
Not sure what I did wrong... <
EDIT @ 1:43AM (Same Day)- [Installing recovery/Fixing boot loop]
Successfully installed Clockwork Mod Recovery .8 after downloading a 'command' file from my ROM's .rar (I modified the file so that it'll say <load-info>sdcard2<load-info> instead of <load-info>sdcard<load-info>).
Repartitioned to 2048 and 0 for the memory settings.
EDIT @ 1:55AM (Same Day) [Boot loop fixed, now just trying to figure out what to do next]
Repartitioning to 2048 and 0 in the memory fixed the boot loop. Yes!
Now, I don't know exactly what to do next... This one is still in progress right now.
Sounds like you did it right. Where you got the Clockwork file may make a difference though. There are 2 of them out there. One is from a thread that has it setup to load from an external sdcard. The other from the internal. Quick way to see what you have is to open the command file inside the recovery folder and see if it says sdcard, or sdcard2. You want it to point at whatever method you are using to load it. Sdcard for internal, sdcard2 for an external card.
If you haven't tried it already, look at this.
After that just load the rom you want.
Beware though, you may have a strange model that won't work with that, some have been floating around..... Read the full thread too
This may also be useful to you: http://forum.xda-developers.com/showthread.php?t=842000
Now, I see why it did not work... Mine had no 'command' file AT ALL (in the 'recovery' folder)!
So, how can I make one?
By the way... To address your initial issue of being in a boot loop. Get clockwork installed. Once installed go to advanced, partition sdcard. Use 2048, and 0 for the swap. That will get rid of the boot loop.
XANAVirus said:
Now, I see why it did not work... Mine had no 'command' file AT ALL (in the 'recovery' folder)!
So, how can I make one?
Click to expand...
Click to collapse
You can find one in most any of the roms. The earlier TnT roms had them, others too...
They are all the same except for the sdcard, or sdcard2 thing I talked about so don't worry about finding a specific one.
So, when I install Clockwork, do I need to leave that MicroSD in there to run it everytime (not sure where it puts the files/etc)?
XANAVirus said:
So, when I install Clockwork, do I need to leave that MicroSD in there to run it everytime (not sure where it puts the files/etc)?
Click to expand...
Click to collapse
Nope. Once it is installed you don't need the sdcard anymore. Be sure to read my post a couple above this about fixing your boot loop.
Okay, as you wrote in the first page to reformat to 2048 and 0 (in that order), I just did that (as wrote in my edit )
What should I do next?
XANAVirus said:
Okay, as you wrote in the first page to reformat to 2048 and 0 (in that order), I just did that (as wrote in my edit )
What should I do next?
Click to expand...
Click to collapse
Reboot and see where you are... It should go back to where you were before you got the boot loop. The stuff on your internal sdcard will be gone though. So I hope there wasn't anything important there.
BTW, you can hit the back button on the side of your screen to go backwards in the clockwork menus.
Nothing important. I haven't even installed anything new or changed any new settings on my current ROM (that TNT-Lite).
I'm rebooting it right now as I type this.
EDIT @ 1:58AM (Same Day)-
Your steps fixed my boot looping problem. Thanks!
Now, I don't know what next to do. I don't have Titanium Backup installed (couldn't sideload it, I kept having problems).
I don't know if the Market is fixed yet.
Did it boot?
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
Yes, thanks!
Awesome! Now I would boot back into clockwork and make a backup. You can rename them from a file manager too so they make sense..
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
I don't ever use titanium to do the market fix. I just use it to backup apps.
Sent from my VEGAn-TAB-v1.0.0b4 using Tapatalk
Okay, I made the backup like you asked. So, now should I try to fix the Market?
Is there anything else that needs tweaking?
Let's begin
1st download all the necessary files:
Motorola 5.4.0 Driver with MotoHelper http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
stock UK XT720 sbf and RSD Lite 4.9 from http://forum.xda-developers.com/showthread.php?t=953863
SuperOneClickv2.1.1 ftom http://forum.xda-developers.com/showthread.php?t=887416
OI File Manager or from Android Market
Open Recovery for XT720 from http://forum.xda-developers.com/showthread.php?t=1242259
CM6 RC3 from http://forum.xda-developers.com/showthread.php?t=1197655
Then proceed to install the windows drivers for XT720,
once that is done flash your XT720 back to factory stock,
to go into ROM flashing mode Hold Power + Volume Down + Camera buttons all at once, be patient, it will take a while and a couple of reboot.
When the phone is finally done booting up, go into Settings > Applications, and check the boxes for USB debugging + Stay awake,
now you can run SuperOneClickv2.1.1 to root your XT720, for step by step rooting instructions follow this guide http://forum.xda-developers.com/showthread.php?t=887416
Next you will want to install a File Manager to your XT720, the stock XT720 doesn't include any file manager,
open a command line (in windows run CMD),
switch to the directory ..\SuperOneClickv2.1.1-ShortFuse\ADB\
run the command line adb.exe install FileManager-1.1.6.apk
The next step is best done using a microSD card reader, then you can drag & drop all the files for your XT720 directly to the SD card from Windows Explorer
- OpenRecovery.apk,
- the unzipped files from OpenRecovery-XT720-01 folder,
- update-cm-6.3.0-RC3-MilestoneXT720-signed.zip,
- gapps-hdpi-20101114-signed.zip
Using the OI File Manager install OpenRecovery.apk (it should be at the root of your SDcard),
run Open Recovery from XT720 stock launcher's app drawer,
select Install Recovery System (allow super user),
then follow the instructions to install OpenRecovery-XT720-01 from http://forum.xda-developers.com/showthread.php?t=1242259
Once you are done proceed to install update-cm-6.3.0-RC3-MilestoneXT720-signed.zip, and gapps-hdpi-20101114-signed.zip using OpenRecovery-XT720 (for details follow http://forum.xda-developers.com/showthread.php?t=1197655),
select clear cache, dalvik, and factory reset
choose the reboot option from OpenRecovery-XT720 menu,
the first boot of CM6 will take a very long time,
when you see the launcher, let it finish loading, then reboot the phone again via power button > reboot,
after this last reboot, the phone is finally ready for normal usage.
Enjoy!
You can get the Dexter's OpenRecovery.apk here
you can use universal androot to root your phone alternatively. its super easy. just drag it onto your sd card (or download directly from your phone), install the apk, and click root. heres a link. http://www.4shared.com/file/HvHnis8C/Universal_Androot_v161.html
I actually did this to a friends xt720 yesterday and I needed to fix the APN settings, he wasn't getting data.
WARNING, about BusyBox newer than v1.17.1 and Link2SD
So i found out the hard way there's an odd bug with BusyBox 1.18.x or newer it conflicts with Link2SD, it wont mount and causes Link2SD to throw this message
Code:
Mount script error
Mount script cannot be created
mount: mounting /dev/block/vold/179:2 on /data/sdext2
failed: no such device
reverting BusyBox back to 1.17.1 fixed the problem
Help on Boot Loop
Followed all instructions here to update to the the cm 6.3.0 RC3. Everything appeared to go as stated, but after reboot i seem to be stuck in a vicious boot loop. I get the cyanogen mod droid logo but it seems to pop up every 10 seconds or so without the phone ever starting up. Any help would be greatly appreciated. It's cute as a paperweight, but not much good as a phone.
Disregard....after rebooting for nearly nine hours....the phone finally started up and appears to be working....Thanxxxx
I too now am unable to access data....i am not skilled enough to work with the APN settings. Could you please help me out on what i need to do to get my data working again...no internet access sux....
AllGamer said:
Next you will want to install a File Manager to your XT720, the stock XT720 doesn't include any file manager,
Click to expand...
Click to collapse
Awesome Instructions bud, much needed for the first timers. Just thought I would add that stock 2.1 always came with quickoffice for me and that's what I normally use at first to install Open Recovery but always end up needing a better File Manager anyway. So either way, I hate to be a stickler just might be one less step lol. Good job AllGamer dude!
Ps.. I should have just said good job dude your way is better lol.
hitech1 said:
I too now am unable to access data....i am not skilled enough to work with the APN settings. Could you please help me out on what i need to do to get my data working again...no internet access sux....
Click to expand...
Click to collapse
Install APN manager from the market and find your carrier there.
You could always just input them manually, doesn't require any skill bud, you just have to google the correct APN configuration details.
nice App
JiroPrinz8 said:
Install APN manager from the market and find your carrier there.
Click to expand...
Click to collapse
https://market.android.com/details?id=ale.android.apnmanager&feature=search_result
this is an Excellent recommendation.
I didn't even know such APP existed
it's so easy to enter APN data... pick and choose, done!
Don't think you should be flashing ROMS if you're hesistant about manually entering an APN, my 2 cents lol.
I would still rather recommend singapore rom, with the tv out and everything. Don't know of any cons with this atm.
Hi,
i installed cm6 rc 3 as described above. And it runs very smooth and stable.
Although i have one big problem: If i insert my sd-card (3gb fat + 1 gb ext4, with app folder on ext partition) in my phone, app2sd works as it should and the phone boots as usual. But when the phone shuts off the display and goes into sleep mode, i am no more able to wake it up again. When I push the power button only the leds switch on. I have to pull the battery and restart the phone.
If sdcard is not inserted, everthing works great. with no problems since three days now.
But i would like to have my sdcard back...
Perhaps some can help me.
Leotronick said:
Hi,
i installed cm6 rc 3 as described above. And it runs very smooth and stable.
Although i have one big problem: If i insert my sd-card (3gb fat + 1 gb ext4, with app folder on ext partition) in my phone, app2sd works as it should and the phone boots as usual. But when the phone shuts off the display and goes into sleep mode, i am no more able to wake it up again. When I push the power button only the leds switch on. I have to pull the battery and restart the phone.
If sdcard is not inserted, everthing works great. with no problems since three days now.
But i would like to have my sdcard back...
Perhaps some can help me.
Click to expand...
Click to collapse
I'm not certain but I think this means that Android thinks your battery has more charge than the hardware does. I would first try to redo battery calibration (there are threads in the XT720 general section about how to do this) if you can convince yourself that your battery is actually full. It can be a little tricky.
Leotronick said:
Hi,
i installed cm6 rc 3 as described above. And it runs very smooth and stable.
Although i have one big problem: If i insert my sd-card (3gb fat + 1 gb ext4, with app folder on ext partition) in my phone, app2sd works as it should and the phone boots as usual. But when the phone shuts off the display and goes into sleep mode, i am no more able to wake it up again. When I push the power button only the leds switch on. I have to pull the battery and restart the phone.
If sdcard is not inserted, everthing works great. with no problems since three days now.
But i would like to have my sdcard back...
Perhaps some can help me.
Click to expand...
Click to collapse
might be your vsel being too low. it happened to me too, and i made the vsel a little higher and it didnt happen anymore.
Hi, I have a noob question...
Can I install this recovery image (CM6) directly from stock Videotron SBF?
I do have install open Recovery based on Androidiani. Can I flash this Rom (CM6) with that recovery or I need something diffrent?
Thanks for your help!
speedmax said:
Hi, I have a noob question...
Can I install this recovery image (CM6) directly from stock Videotron SBF?
I do have install open Recovery based on Androidiani. Can I flash this Rom (CM6) with that recovery or I need something diffrent?
Thanks for your help!
Click to expand...
Click to collapse
if you are already on stock, then yes you can flash CM6
but make sure you are rooted first
and use the Open Recovery XT720 listed in the OP topic
AllGamer said:
if you are already on stock, then yes you can flash CM6
but make sure you are rooted first
and use the Open Recovery XT720 listed in the OP topic
Click to expand...
Click to collapse
Thanks, I Will proceed tomorow.
Regards,
Sent from my MB860 using xda premium
Just installed! Working nice...
Camera and camcorder are working, it was a bug with stock Rom.
Is there a Overcloking kernel for XT720 CM6 rom?
Or is there a way to overclock it with the current one?
Regards et thanks for your help!
speedmax said:
Just installed! Working nice...
Camera and camcorder are working, it was a bug with stock Rom.
Is there a Overcloking kernel for XT720 CM6 rom?
Or is there a way to overclock it with the current one?
Regards et thanks for your help!
Click to expand...
Click to collapse
yes, just download the milestone OC utility from Android market
HI Guys
so here is the thing , everything was working fine, until i flashed ICS the stock rom with CWM, right after flashing my pc was unable to recognize my Transformer as a USB device.
Every time i connect it my transformer freezes for a few seconds and then nothing happens, and on my computer screen it doesn't even recognize a new USB drive.
I tried to connect it to two different computers and the same thing happens which means the problem is with my transformer
Afterwards i Flashed Revolver rom but i still have the same issue
Any one had the same problem? any possible fix for this problem
Edit: Charging Works fine
Thanks
Update: Strangely when i tried to connect the USB when i am on the recovery menu the computer was able to recognize my transformer, ADB was installed but not the MTP so the problem is not a cable or computer problem something much be wrong
I used ViprerMod to root my transformer and i am using Rogue CWM
Thanks
Just flash this update on top of your ROM
http://forum.xda-developers.com/showthread.php?p=19093950
Slight hi-jack but I have a question about this.
I updated OTA from scratch (meaning a full and complete wipe). I plugged my tablet into my PC and it downloaded all the drivers. Great!.
I have my Titanium backup folder on the Internal (for some unknown reason why I did that) and I want to put it on my External. I plug the tablet into my PC and the media device icon pulls up. I click on it and both drives pull up and I can open them. Now I want to take my Titanium folder from the internal and put it on the external with just drag and drop. So I drag and drop, only when I click on the folder in the external (tried it to a temp folder on my PC desktop too) it shows as empty. I have USB debugging on and MTP is checked. I have also been able to transfer pix, .zips and other misc files over while inside the tablet with Root Explorer, it is just that the Titanium folder will not cross over for some reason.
Ideas? I did the OTA so not sure that flashable bootloader.zip will work. I am just missing something and I can't figure out what it is. I know they did away with Mass Storage mode with HC and not ICS. How can I get it over there?
Woodrube said:
Ideas? I did the OTA so not sure that flashable bootloader.zip will work. I am just missing something and I can't figure out what it is. I know they did away with Mass Storage mode with HC and not ICS. How can I get it over there?
Click to expand...
Click to collapse
Back then I use to use Root Explorer and copy the whole folder over to external sd card. Now TB have the option to backup directly to external sd card.
Ya, but my dumba$$ pulled a copy of my TB from my phone with all my backups (PowerAmp, Jango Music, At-Bat,...) and installed it on the external when I first got the tablet and then copied it over to the internal (because I didn't know there was such a threat of losing internal on this tablet) once I got a new external I wanted to move it back.
I know that in TB you can set the backup destination to wherever you want it to be, but this is an existing backup folder that I am wanting to move. Wonder if I can put it in my dropbox (900mb- but can be trimmed down for some apps that I know don't work and general cleaning house) and pick it back up to my PC and then transfer it over to external?
Edit:: I used Root Explorer to try and copy it over and let it run all night and when I woke up it was still cycling the icon in the center of the screen, 6hrs later.
baseballfanz said:
Just flash this update on top of your ROM
http://forum.xda-developers.com/showthread.php?t=1514658
Click to expand...
Click to collapse
Thank you very much for your advise , But Doesn't that mean that i will go back to stock rom and i won't be able to use the benifits of the revolver rom?
One other thing i should mention is that i already tried flashing this stock rom once before i flashed revolver rom and i had the exact same problem
i mean first flashed ICS CWM flashable >> USB not recognized
Then i tried with the ICS revolver rom >> Same thing USB not recognized by the computer
All what happens is that my Transformer freezes for a few seconds and nothing shows up on my computer
It sucks not being able to connect your device to the computer i mean it is kind of a deal breaker
Any ideas?
Bogda2 said:
Thank you very much for your advise , But Doesn't that mean that i will go back to stock rom and i won't be able to use the benifits of the revolver rom?
One other thing i should mention is that i already tried flashing this stock rom once before i flashed revolver rom and i had the exact same problem
i mean first flashed ICS CWM flashable >> USB not recognized
Then i tried with the ICS revolver rom >> Same thing USB not recognized by the computer
All what happens is that my Transformer freezes for a few seconds and nothing shows up on my computer
It sucks not being able to connect your device to the computer i mean it is kind of a deal breaker
Any ideas?
Click to expand...
Click to collapse
I apologize, didn't see the part that you're on Revolver.
Did you wipe going from one ROM to the next?
baseballfanz said:
Just flash this update on top of your ROM
http://forum.xda-developers.com/showthread.php?t=1514658
Click to expand...
Click to collapse
hi. i can't use MTP on my transformer too. I flashed the CWM flashable ICS ROM (Option B)that was in your link about two days ago. was just wondering if there's a new version and if I flash from that, it'll work?
yuhenyo said:
hi. i can't use MTP on my transformer too. I flashed the CWM flashable ICS ROM (Option B)that was in your link about two days ago. was just wondering if there's a new version and if I flash from that, it'll work?
Click to expand...
Click to collapse
Flash the upgrade link he linked to above for your version. Should clear it up.
Solved:
After Updating to the Latest revolver Rom 1.3.1
Everything Went Back to normal , USB is recognized by the computer
I think this update solved the Issue
According to Gnufabio's Latest Changelog:
Added bootloader to solve usb problems for some people
Dont really know what the Bootloader is but Probably this is what was missing
baseballfanz Thank you very much it is not the first time you've helped me
Cheers
jasonwuzthere said:
Flash the upgrade link he linked to above for your version. Should clear it up.
Click to expand...
Click to collapse
by update, do you mean option A? or is it still the option B?
yuhenyo said:
by update, do you mean option A? or is it still the option B?
Click to expand...
Click to collapse
Just go here and flash the correct update ROM for you're region
http://forum.xda-developers.com/showthread.php?p=19093950
After flashing ICS thru OTA, not able to sunc with Asus, PC recognizes the device, but not able to change from MTP
Any ideia ?
Asus Sync reinstaled, with XP
Mistake.....
Have a ASUS TF101, running Android Revolution HD 3.5.1 with Raymanfx kernel 2.6.39.4ASUS (appeared to be updated after flashing ROM)
Installed a ROM (Team EOS) on the weekend, everything went fine until I was installing GAPPS as I used clockwork-mod app to boot into recovery then I got a CWM loop which I managed to correct with some terminal work (as per other XDA post) - then ran a restore and got back to 'normal' but with limited connectivity and accessibility as per below.
The problem is:
*can't read SD card - every time I access storage from setting it crashes
*WIFI and Bluetooth won't turn - wifi just states 'turning on' and bluetooth appears to be working but does not connect to devices
*Can't connect TF101 to PC, does not initiate connection and/or no changes in Device Manager even after scanning for changes
*Every time I connect the docking station it beeps and screen goes blank.
The above issues means I cannot load any external programs but can only use the data I currently have on SD Card which are:
*cwm_recovery-5504_roach-tf101
*Energy ROM
*Andriod Revolution HD ROM
*Rayman ROM v6
Troubleshooting so far:
I have used terminal window to fix the CWM looping issue
Tried to use terminal window to get SD Card to mount - did not work
Tried to connect TF101 to PC to use other tools and transfer data - did not work
Tried loading another ROM - able to load ROM but same connectivity issues
Loaded restore from CWM - worked but same connectivity issues
Can't seem to get anything working that would allow me to connect, any assistance would be greatly appreciated, thanks.
Kind regards,
Kenny 'rethink' Oldenskov
UPDATE - loaded the Energy ROM, this has somehow enabled the storage and dock
BUT no connectivity through USB, WIFI or Bluetooth
Rethink said:
UPDATE - loaded the Energy ROM, this has somehow enabled the storage and dock
BUT no connectivity through USB, WIFI or Bluetooth
Click to expand...
Click to collapse
Do not use ROM manager... use twrp or rogue recovery which recognises external recovery, now do a clean and fresh install
Sent from my Transformer using xda app-developers app
Thanks to udupa82 - with lots of wiping and loading/reloading of ROM's I'm now back to a fully functioning TF101 again-->NO MORE CWM ROM Manager
Rethink said:
Thanks to udupa82 - with lots of wiping and loading/reloading of ROM's I'm now back to a fully functioning TF101 again-->NO MORE CWM ROM Manager
Click to expand...
Click to collapse
What did actually do and use..... I'm at the same point and can't get any wifi amd have all the same issues as above...
jalfonso119 said:
What did actually do and use..... I'm at the same point and can't get any wifi amd have all the same issues as above...
Click to expand...
Click to collapse
To install TWRP go to Google Play and install GooManager. Open it and select the 'three dot' option at the top right, then select 'Install OpenRecoveryScript'. As long as you have root access it'll install, reboot, and give you TWRP as your recovery option. I had to do this twice to get out of CWM, but it worked just fine.
I managed to get out of the cwm loop as well with some terminal commands... I then use blue tooth w pdanet from my gs3 to get Internet on the tf101 and got goo manager to re flash TWRP and it worked... After that I wiped and restored an old nandroid and bam tablet is good with wifi amd I'm having issue with it connecting to computer w usb tho..... Wondering if u had smae issue as well..... Here's a link to another thread I started to try and get a fix
http://forum.xda-developers.com/showthread.php?t=2076120
Sent from my SPH-L710 using xda app-developers app
jalfonso119 said:
I managed to get out of the cwm loop as well with some terminal commands... I then use blue tooth w pdanet from my gs3 to get Internet on the tf101 and got goo manager to re flash TWRP and it worked... After that I wiped and restored an old nandroid and bam tablet is good with wifi amd I'm having issue with it connecting to computer w usb tho..... Wondering if u had smae issue as well..... Here's a link to another thread I started to try and get a fix
http://forum.xda-developers.com/showthread.php?t=2076120
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
i hd this problem, unfortunately there is no twrp for my xperia mini pro, what did i do? .
I found that it was sd card related. I tried a new sd card and flashed a new kernel and rom using it and it worked.
Really would appreciate if twrp supported mango too.
So I've had a bit of bad luck mixed with poor timing. Here's the run down.
I have an Asus Transformer TF101 which was running the stock rom.
I rooted my Tablet a few weeks back without any problem. Things were great. Then, I tried to upgrade to Jelly Bean from ICS using Team EOS (I followed these 2 threads mainly, http://www.transformerforums.com/fo...ficial-faq-teameos-4-android-4-2-x-tf101.html & http://forum.xda-developers.com/showthread.php?t=2063406)
I put the ROM and all the files needed onto my micro SD card.
I booted into TWRP and followed the instructions. Things seemed to have gone great. When I rebooted, I saw the new splash Logo upon bootup and awaited it to do it's thing. It never did. I let it run for an hour and it never made it into the OS.
I rebooted, went back into TWRP with plans to redo the procedure, only now the microSD card slot is not being picked up. I tried multiple micro SDs of different sizes (1GB-32GB), I've tried inserting before boot up, inserting after bootup, inserting after bootup and then rebooting the device. No luck.
I bought a USB adapter that plugs in where the power plug goes, hoping I could run the files off a USB flash drive. or a micro SD card within a USB flash drive. No luck.
I am running Teamwin's TWRP 2.3.2.3
My backup from nandroid happens to be on my microSD card too. So I can't use it to recover the old OS either.
TL;DR: Micro-SD card stopped working after a failed attempt to flash an OS. OS and backups are on the microSD card. PC recognizes the device but won't let my access the hard drive.
Does anyone have any suggestions on what to try?
Thanks!
Well, the USB is not set up to be mounted in recovery. Keep in mind, the microSD is mounted at /sdc/ in TWRP.
You can always use ADB and push a file to the internal (/sdcard/) so you can flash if your microSD slot is dead.
Let me find a post on how to do this.
EDIT: Here is what to do if you need to use ADB:
Plug tablet to PC via USB
It should install new hardware and show 1 devices, an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://db.tt/b9dQ6xzp
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite ROM. If applicable, save any other files needed (GAPPs or kernel)
Save this at c:\adb\ROM.zip. Other files save accordingly like Kernel.zip and GAPPs.zip.
Next, run the following commands
Code:
adb push ROM.zip /sdcard/
Once this competes, you will need to repeat for any other files to flash like GAPPs or Kernel.
After these files have been transfered, you can install a file from the internal (/sdcard/) directory.
frederuco said:
Well, the USB is not set up to be mounted in recovery. Keep in mind, the microSD is mounted at /sdc/ in TWRP.
You can always use ADB and push a file to the internal (/sdcard/) so you can flash if your microSD slot is dead.
Let me find a post on how to do this.
EDIT: Here is what to do if you need to use ADB:
Plug tablet to PC via USB
It should install new hardware and show 1 devices, an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://db.tt/b9dQ6xzp
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite ROM. If applicable, save any other files needed (GAPPs or kernel)
Save this at c:\adb\ROM.zip. Other files save accordingly like Kernel.zip and GAPPs.zip.
Next, run the following commands
Code:
adb push ROM.blob /sdcard/
Once this competes, you will need to repeat for any other files to flash like GAPPs or Kernel.
After these files have been transfered, you can install a file from the internal (/sdcard/) directory.
Click to expand...
Click to collapse
Thanks so much frederuco! I will be trying this later today and will update this post as soon as I do.
I just wanted to say good luck, and we are all counting on you.
Almost there!
frederuco said:
I just wanted to say good luck, and we are all counting on you.
Click to expand...
Click to collapse
The update! I followed your instructions, while on the cmd prompt, I got no confirmation that the files were moved, but they appear to be on the device now. When I go to reinstall through TWRP, the flashing fails. I am going to do some digging around the forum to see what solutions there may be, but if you (or anyone reading) has an idea, do tell.
I will be sure to update this thread if I fix it, including the solution I found.
Try downloading the ROMs again.
Also, note that I edited my reply as I had said ROM.blob and it should be ROM.zip.
frederuco said:
Try downloading the ROMs again.
Also, note that I edited my reply as I had said ROM.blob and it should be ROM.zip.
Click to expand...
Click to collapse
I think I'm in good shape. I tried to edit my post from earlier, but I had to wait a few minutes before it would let me.
I realized the file didn't finish transferring to the tablet. Moments after my last post, I got a confirmation from cmd prompt that the first file finished. The second one just finished, and the third is still transferring I suspect. That would totally explain the failure.
db1984 said:
I think I'm in good shape. I tried to edit my post from earlier, but I had to wait a few minutes before it would let me.
I realized the file didn't finish transferring to the tablet. Moments after my last post, I got a confirmation from cmd prompt that the first file finished. The second one just finished, and the third is still transferring I suspect. That would totally explain the failure.
Click to expand...
Click to collapse
Yes, that would do it!
frederuco said:
Yes, that would do it!
Click to expand...
Click to collapse
Alright, so I got past the logo, Android upgraded all the Apps and is now "Starting apps" .. it's been here for about 10 minutes. I think I can take it from here.
The ADB push was the solution.
Waited another 15 minutes. Nothing happened (stayed at Starting apps)
Restarted device. Booted up as it should and I am now all set. Thanks again!
Now that you're using EOS can you use the microSD slot? I know moving from stock to EOS fixed my card slot issues not to mention that I'm loving the Jellybean goodness
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
bsoplinger said:
Now that you're using EOS can you use the microSD slot? I know moving from stock to EOS fixed my card slot issues not to mention that I'm loving the Jellybean goodness
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
I'm fairly certain the slot itself is broken. Haven't been able to get it to read things yet.
I'm still having some minor issues with the setup, but I know I've seen fixes to these problems when browsing this forum. Google Search/Google Now crashes 3-4 seconds after opening it. The system also reboots "randomly" (really, just when it's idle for more than 10 minutes), I also had to go into TWRP last night to get the system to power down. Long pressing power and selecting Power Off simply rebooted it.
But compared to where I was 24 hours ago (and had been stuck there for 1+ week, I really didn't want to burden people with my problem since I'm a lurker here), I really can't complain and have full confidence that I'll be able to get the kinks worked out.
At least I have an adapter for the power port, so I can plug USB sticks (or USB-microSD adapters) into the tablet still.
db1984 said:
I'm fairly certain the slot itself is broken. Haven't been able to get it to read things yet.
I'm still having some minor issues with the setup, but I know I've seen fixes to these problems when browsing this forum. Google Search/Google Now crashes 3-4 seconds after opening it. The system also reboots "randomly" (really, just when it's idle for more than 10 minutes), I also had to go into TWRP last night to get the system to power down. Long pressing power and selecting Power Off simply rebooted it.
But compared to where I was 24 hours ago (and had been stuck there for 1+ week, I really didn't want to burden people with my problem since I'm a lurker here), I really can't complain and have full confidence that I'll be able to get the kinks worked out.
At least I have an adapter for the power port, so I can plug USB sticks (or USB-microSD adapters) into the tablet still.
Click to expand...
Click to collapse
The workaround for Google Now crashing is to disable Hotword Detection in Settings - Language & Input - Voice Search (or something like that). Search the EOS thread for "Hotword" and you will find the location.
Do you have a SD in the dock? This can cause SOD and RR's.
Hmm, I guess I have never tried powering down on EOS, but I am pretty sure it works. I just put my tablet to sleep and never turn it off. I find my tablet (even undocked) will lose more power when it is off than when it is sleeping.
frederuco said:
The workaround for Google Now crashing is to disable Hotword Detection in Settings - Language & Input - Voice Search (or something like that). Search the EOS thread for "Hotword" and you will find the location.
Do you have a SD in the dock? This can cause SOD and RR's.
Hmm, I guess I have never tried powering down on EOS, but I am pretty sure it works. I just put my tablet to sleep and never turn it off. I find my tablet (even undocked) will lose more power when it is off than when it is sleeping.
Click to expand...
Click to collapse
Nope, nothing was in the dock. I actually didn't have the keyboard dock plugged in during the "crisis"- I did try getting TWRP to read a card from it once, that was about it.
I read somewhere else, that once you let the battery die on it's own, and recharge, the "never powers off" issue goes away for many people (haven't seen one specifically relating to EOS on TF101, but the other symptoms were spot on)
I'll be checking out the Google Now tweak in a bit.
I'd been running a custom kernel on my Transformer since about a week or two after I bought it at a Black Friday sale simply because it would keep running on the stock ICS ROM. Changed to KAT kernel when I moved to EOS. You might want to consider a custom kernel if you have a Transformer that suffers from the reboot issue like mine did.
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
db1984 said:
-snip-
Click to expand...
Click to collapse
You may want to try doing a full format in TWRP, and using the superwipe full scripe from the ARHD thread, then formatting again, wipe cache and dalvik, push the latest EOS, KATkernel and Gapps to the device, wipe dalvik cache and cache, flash EOS, wipe dalvik cache and cache, boot into the ROM, boot back into twrp, wipe cache and dalvik, flash Gapps, wipe cache and dalvik, boot into the ROM, boot back into TWRP, wipe cache and dalvik, flash KATkernel, wipe cache and dalvik, cold-boot into the ROM.
That should set you up with the most stable your tf is going to get, it seems erroneous and like a ton of work, but I strongly believe in doing this whenever I flash a new rom setup, I've gotten to doing it in about 10 minutes now.
Just an update.
EOS's random reboots were getting pretty bad. Happened a few times while I was working on a few docs (thankfully Evernote had autosaved)
I also noticed when the screen would go off, it would eventually turn back on and attempt to reboot, getting stuck at the Asus loading splash (pre EOS logo). I ended up re-flashing with my newly gained leet adb skills (thanks frederuco ) and went with Cyanogenmod 10. I've only had 1 random reboot since and Google Now seems to work 90% of the time.
I'm sure there are some more things I can do to fine-tune it, still getting a hang of everything.
Thanks again for everyone who's helped.