Related
Hi all, all credits go to xordis for the instructions, cyanogen and Amon_RA for their discussion/findings/contributions in this thread: http://forum.xda-developers.com/showthread.php?t=547896
I just created a separate thread as I realised that the file posted by xordis could be used on various other ROMs (probably except HTC-based ones) to get a flashing trackball on an incoming call. Here are the exact instructions by xordis:
xordis said:
Here is the fix for the trackball flashing.
Grab this file
http://members.iinet.net.au/~xordis/files/lights.msm7k.so
adb remount
adb push lights.msm7k.so /system/lib/hw/
adb shell reboot
Worked for me. would like to know if it works for others.
Cyanogen will hopefully include this in the next release if it works.
Click to expand...
Click to collapse
Also, according to Amon_RA there should be 2 versions of lights.msm7k.so as of now, one for 32A (MD5: FBFC8129630F7C517C7999521B015C20), and one for 32B (MD5: E94DDAD629894B0CB01138A58B2CC031). The one posted by xordis has a MD5 value of E94DDAD629894B0CB01138A58B2CC031, but I have tested it on Amon_RA's ROM and it works.
On the other hand, I have also tried pushing lights.msm7k.so from a 32A ROM (MD5: FBFC8129630F7C517C7999521B015C20), and it does not work. My guess is that it is specially compiled for the HTC framework.
Hope it helps some of you. Once again, all credits go to the respective people! Thanks for all the hard work!
Thanks to all who worked on this, this works great
Does anyone know how we could change the color of the trackball? Just out of curiosity.
Breakthecycle2 said:
Does anyone know how we could change the color of the trackball? Just out of curiosity.
Click to expand...
Click to collapse
I was wondering that earlier. I don't think anyone has tackled it.
I know some devices have the ability to show all colors, but by default they just don't.. so it depends if that trackball led can do it, then its just a matter of someone cracking it open and seeing if they can or not.. but i have no idea.
What does this do?
My Trackball already flashes, when receaving a SMS or phonecall?
does this change the pattern of flashing?
zzup said:
What does this do?
My Trackball already flashes, when receaving a SMS or phonecall?
does this change the pattern of flashing?
Click to expand...
Click to collapse
It's for the people who flashed their MT3G with custom rom that does not support trackball blinking. Mine worked after pushing this thanks
briggs81 said:
I was wondering that earlier. I don't think anyone has tackled it.
I know some devices have the ability to show all colors, but by default they just don't.. so it depends if that trackball led can do it, then its just a matter of someone cracking it open and seeing if they can or not.. but i have no idea.
Click to expand...
Click to collapse
Thanks man. Nucks fan, huh?
Got it for 3.9.11.
Breakthecycle2 said:
Thanks man. Nucks fan, huh?
Click to expand...
Click to collapse
;-) ......
were do i put the file at sorry for the dum ? dose it go on the sd
It's explained in the first post of this thread.
tato22 said:
were do i put the file at sorry for the dum ? dose it go on the sd
Click to expand...
Click to collapse
You got to set up the android SDK first (search in xda for it), then make use of adb. Follow the instructions on the first page to continue .
hi all... how do I fastboot this? Is it replacing adb for fastboot? I'd setup and have working the fastboot method instead the adb... Than ks for your help...
Just connect your phone in normal mode and run the adb commands..
Does this enable persistent flashing while there are new notifications, like the flashing ring on the Touch Diamond for example?
I don't find a single flash useful in any way unless I sit and watch for the moment a new message arrives!
MikLSP: It flashes when there's a new email. However, it does not flash when there's a missed call or new sms for me . No idea why..
it worked ...... but there a slight problem..... if a call is misssed. previously ( before rooting ) the track ball used to blink again and again....but after falshing and uploading that trackball falshing update ...... its just blinking for one time....and then its not blinking.....! any ideas......?
pintspin said:
it worked after pushing the attached file to phone ...... but there a slight problem..... if a call is misssed. previously ( before rooting ) the track ball used to blink again and again....but after pushing that trackball update ...... its just blinking for one time....and then its not blinking.....! any ideas......?
Click to expand...
Click to collapse
can any one give me an idea.... about this problem.....!
I have tried moving this file to the stated directory then rebooted, but all it does is get rid of all my LEDs. HTC magic 32b CM6 Froyo
I tried this on my 32A with FroyoRedux 1.5 and it caused reboots, plus it blinked non stop...
Hi all,
Rumor has it I picked up a DEFY last week. Most people in the community know me for my work on the cliq/backflip/cliqxt. It's been quite some time since I posted any mods/work here on XDA so here we go. First I'd like to say thanks to Koush & Tenfar for the work they've done. They laid the ground work. I simply needed/wanted to improve on it more. I wanted to include the latest 2.5.1.x version since it has some bug fixes/new features also. So here you go. This recovery includes the latest 2.5.1.8 ClockworkMod Recovery, fixed fix_permssions script, and updated adb that allows root access when using adb shell. All your backups, downloads will reside in the clockworkmod directory on your sdcard just like a standard clockworkmod recovery. If you haven't noticed the fix_permissions script don't run properly via the recovery on the DroidX/Droid2/Defy. I simply fixed the script so it does work properly. Thanks again to both Koush & Tenfar. I'm looking into resolving the problem when you have USB debugging enabled you can't boot into recovery mode properly. This release still has that issue, just FYI. If you choose to use this version over Tenfar's, you'll need to un-install his version, install this one, & choose the option to install recovery once. After that, it's works the same way. Take care.
UPDATE: I've uploaded a new version to my 4shared as well as included it here. This new version simply adds a power off option to the menu & was a quick attempt to try to resolve the USB debugging option. I'll give it another try when I have time, until then, I hope you like having the option to power off your Defy from the recovery menu. I've also provided a link to the original version. Take care.
Steve, kb7sqi
Edit: Due to requests, I'm re-adding the link for this updated version. While I do have plans to come back to #android soon, until then, this will be unsupported by me till then. I'm glad it's been useful to others. Take care.
Latest Version:
Older version:
http://goo.gl/NtsTV
Steve
Great work! Will try it out asap.
installed seems to be working fine btw whats key test?
S1dew1nder said:
installed seems to be working fine btw whats key test?
Click to expand...
Click to collapse
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
kb7sqi said:
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
Click to expand...
Click to collapse
thanks for the answer dude, just did a back up with it all went well only diff was it made a new folder btw it will restore older back ups right?
kb7sqi said:
It's does exactly what it sounds like. It simply returns the "key" value when you touch keys/buttons on your phone. It's handy if you're wanting to update a recovery to use certain keys if your phone has them. Perfect example, on the cliqxt the phone has a touch pad. So in the version I created for it, instead of needing to use the volume up/down, you could also use the touchpad for up/down/select as well. Take care.
Steve
Click to expand...
Click to collapse
How can I can quit key test?
Power+VolUp results in a black screen.
pull the bat?
S1dew1nder said:
pull the bat?
Click to expand...
Click to collapse
that's what i did. but would've been nice to have long press (power button) to quit instead of battery-pull.
Ah, well, wouldn't need to use it twice anyway.
I'm gonna try restoring an older img, report back in a few.
S1dew1nder said:
thanks for the answer dude, just did a back up with it all went well only diff was it made a new folder btw it will restore older back ups right?
Click to expand...
Click to collapse
Yeah, you should be able to restore other nandroid backups.
racca said:
How can I can quit key test?
Power+VolUp results in a black screen.
Click to expand...
Click to collapse
You guys do know you don't have to pull the battery out right? You can hold down volume down button & hit the power button to turn the phone off while in the recovery. When you power the phone on, it'll boot up like normal. Take care.
Steve
Restore doesn't work. "can't find directory"
I will switch back to the old version
Andy
morphin said:
Restore doesn't work. "can't find directory"
I will switch back to the old version
Andy
Click to expand...
Click to collapse
try renaming the goapkrev folder on your sdcard to clockworkmod it should be able to find the directory then
S1dew1nder said:
try renaming the goapkrev folder on your sdcard to clockworkmod it should be able to find the directory then
Click to expand...
Click to collapse
You took the words right out of my mouth. I was just getting ready to type that. lol Thanks!
Steve
kb7sqi said:
You guys do know you don't have to pull the battery out right? You can hold down volume down button & hit the power button to turn the phone off while in the recovery. When you power the phone on, it'll boot up like normal. Take care.
Steve
Click to expand...
Click to collapse
ahhhhhh, i tried power+volup
thanks for the refreshment, and again for the great work!
now if only we can be rid of the annoying "debugging" bug.
racca said:
ahhhhhh, i tried power+volup
thanks for the refreshment, and again for the great work!
now if only we can be rid of the annoying "debugging" bug.
Click to expand...
Click to collapse
Thanks. I'm working on it. I got a little tired of rebooting my defy over 100 times yesterday when I was working on this. lol After I get my version done for the Motorola Charm, I'll get back to working on that.
Steve
kb7sqi said:
You took the words right out of my mouth. I was just getting ready to type that. lol Thanks!
Steve
Click to expand...
Click to collapse
lol np bud, btw is there any way to rename backup folders with out having a md5 miss match error?
S1dew1nder said:
lol np bud, btw is there any way to rename backup folders with out having a md5 miss match error?
Click to expand...
Click to collapse
i have no such problem ever. renaming always works and no such info is stored in the md5 file
do you think it could of happened because i edited the file name via my computer while my phone was in usb mass storage mode?
kb7sqi said:
Thanks. I'm working on it. I got a little tired of rebooting my defy over 100 times yesterday when I was working on this. lol After I get my version done for the Motorola Charm, I'll get back to working on that.
Steve
Click to expand...
Click to collapse
no pressure then, it's fine as it is.
i just need to remember, like really hard, to turn it off.
i wish i didn't make the same mistake not turning it off over and over again
S1dew1nder said:
do you think it could of happened because i edited the file name via my computer while my phone was in usb mass storage mode?
Click to expand...
Click to collapse
It's a good chance that could've caused it. I've had some wierd stuff happen doing things like that when in usb mass storage mode.
Well here is something that I hope is the start of some hardcore hacking.
This is an ODIN that I created of stock-rooted ED1 for the DROID Charge. In the course of making this, I bricked my charge (first attempt failed in ODIN) and then created a working ODIN that un-bricked it. I then upgraded to ED2 (I confirmed that I lost root as well) so I could test if this will downgrade back to ED1 and it worked and I have root again!
Instructions for ODIN (for those who are unfamiliar with it):
1. Open ODIN.
2. Put the phone into download mode. Do this by powering off your phone, pulling out the battery, and then holding volume down while connecting it to your pc. A giant yellow triangle should be on the phone's screen and it should say 'Downloading...' ODIN should say 'Added!!' and one of the boxes will be yellow and say '0:[COM#]'
3. Click the button labeled 'PDA' and locate the file you are wanting to flash. For emphasis: YOU MUST USE THE PDA BUTTON!
4. Click start. Do not disconnect the phone while it is flashing, it can cause some serious damage.
5. Wait.
6. When finished, unplug the phone, put the battery back in and power up the phone.
Every time I've flashed this, the phone booted straight into recovery. Just select reboot (press home) and it boots up normally. It should probably be recommended to wipe data and cache afterwards, but I didn't and all of my data stayed in tact.
Multiple people have reported that this works. Use at your own risk. I am not responsible for anything that happens to your phone if this doesn't work.
Thanks to imnuts for the HOW-TO thread on creating ODIN builds.
Download here.
Download ODIN here.
to my redbull habit if you feel the need.
I feel dumb for asking, but what are you using to flash this to the phone? I've never used anything other than simple one click root programs, so if you could give a little more detail I'd be happy to try it out.
Download Odin here: http://goo.gl/52aY1
Download Drivers here: http://goo.gl/Tbcca
Download stockrootedED1-20110517.tar.md5 http://goo.gl/kD3Ld
1. Open Odin3 v1.30
2. Remove battery,Hold Vol down. Connect USB to computer and phone then press power. It should take you to a yellow android.
3. Click PDA Button
4. choose stockrootedED1-20110517.tar.md5
5. Click on the Start button
6. Don't Touch and allow the phone to reboot
7. If its taking a while to start DONT PANIC, its perfectly normal
Thanks for the guide, but it doesn't do anything for me, seems like Odin doesn't even know my phone is there. When I plug it in I get the Verizon media manager link to pop up though.
I edited my first post with a link to ODIN and instructions. I guess I'm a little slow with the typing because you beat me to it medjam, but you left out the step of putting the phone into download mode.
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
that's awesome...I gonna try this right now....If i brick my phone I will just swap it out a vzw..They are tarded and can't tell the difference any ways. Will report back once I finish.
Zeek215 said:
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
Click to expand...
Click to collapse
Once rooted go into your build.prop file and every thing that says ED1 change it to ED2...that should quit the nagging to update. Then restart your phone
Credit goes to Jt3 for that info as he posted it in the Charge forum at android central.
Zeek215 said:
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
Click to expand...
Click to collapse
AWESOME!!! So glad to help!
Very nice!
I know that this will kick start the development of this device now that everybody can haz root.
so just to be clear here, this will bring you back from ED2 down to ED1. Does this method require you to have already rooted while you were on ED1 and then upgraded to ED2 and lost it or will this work for everyone?
Thanks in advance
streetlightman said:
so just to be clear here, this will bring you back from ED2 down to ED1. Does this method require you to have already rooted while you were on ED1 and then upgraded to ED2 and lost it or will this work for everyone?
Thanks in advance
Click to expand...
Click to collapse
Should work for everyone. My Charge that I just ran it on was never rooted before.
das7771 said:
that's awesome...I gonna try this right now....If i brick my phone I will just swap it out a vzw..They are tarded and can't tell the difference any ways. Will report back once I finish.
Click to expand...
Click to collapse
They certainly can tell. Don't send back a phone because you broke it. That makes ALL of us look like assholes and promotes the disturbing trend of locking bootloaders. Be an adult.
Sent from my SCH-I500 using XDA App
jt1134 said:
They certainly can tell. Don't send back a phone because you broke it. That makes ALL of us look like assholes and promotes the disturbing trend of locking bootloaders. Be an adult.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
OH OK...Well let me make change my statemet to be more adult like. If i brick my phone I will just go buy another full price so I don't seem like an asshole. I hope this pleases you Sir....
Hey guys. First off, I'm psyched to see this come out.
When I try to do it, I get a driver installation failure telling me that the serial driver was not found and then ODIN never seems to see the phone. This is on W7.
Any help?
teddykgb715 said:
Hey guys. First off, I'm psyched to see this come out.
When I try to do it, I get a driver installation failure telling me that the serial driver was not found and then ODIN never seems to see the phone. This is on W7.
Any help?
Click to expand...
Click to collapse
Did you install the drivers that came with the phone?
wynalazca said:
Did you install the drivers that came with the phone?
Click to expand...
Click to collapse
I thought so, I can connect to USB storage, etc. I'll check it out.
Well this worked perfectly only thing that was different from your instructions was that my com ID was '0[COM12] instead of '0:[COM7]...So no one freak out if yours if different it's just what is being used by your comp. Much thanks to the OP for this..You need to set up a donation link so I can donate for this outstanding work.
teddykgb715 said:
I thought so, I can connect to USB storage, etc. I'll check it out.
Click to expand...
Click to collapse
I think the issue is that my damn work laptop is locked down pretty tight so it won't let all the drivers install. Unlike many here, I'm actually not an IT professional so I can't circumvent it. I'll just have to try it at home tonight.
das7771 said:
Well this worked perfectly only thing that was different from your instructions was that my com ID was '0[COM12] instead of '0:[COM7]...So no one freak out if yours if different it's just what is being used by your comp. Much thanks to the OP for this..You need to set up a donation link so I can donate for this outstanding work.
Click to expand...
Click to collapse
You're welcome! I'm very glad to help get this development stuff going. Also, there should be a donate button in the OP.
So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.
gmermel said:
So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.
Click to expand...
Click to collapse
You should be alright... Can you try this for me? Holding the power button and volume down at the same time.. You should see your bootloader menu whih has 3 icons... Please let me know if you can get there..:fingers-crossed:
gmermel said:
So I sell my Infinity on ebay tonight. Went to wipe my data via TWRP and managed to delete my OS. The device shows the ASUS bootup screen but goes nowhere.
I'm a near illiterate in terms of understanding root level work on the tablet, and my other handicap is that I am a Mac user which means that I am not familiar with some of the "lingo" people use when describing connections to their Windows OS (things like ADB, bootloader, that sort of stuff).
Can someone help me with a step by step fix, using basic language?
i was hoping to ship tomorrow. OTOH, if I've bricked the thing, give me the bad news and I'll refund the money.
Click to expand...
Click to collapse
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post
berndblb said:
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post
Click to expand...
Click to collapse
Wow. 2 minutes and I'm getting help already.
I'm in TWRP. Where do I get the stock rom? I presume I'll download it my computer, but how do I tell the tablet to load it from there?
berndblb said:
No - you're probably ok.
Just boot up with Power and Volume Down, hold both buttons until you feel the tablet vibrate twice. Let go when you see the tiny script and you'll see the bootloader menu with three icons and RCK flashing. Push Volume up and you should boot into TWRP.
From here you can just re-flash the rom you wiped or the stock rom (although flashing the stock firmware would wipe out TWRP). You need to have the zip of your chosen rom on your internal storage already (but maybe you wiped it???) or on your microSD.
Ask if I was not clear enough.
Edit: LMK beat me to it - again... LOL
Sorry mate, didn't see your post
Click to expand...
Click to collapse
It is not a problem... I think that my device is running the ET so it is a little faster...:silly: Just kidding...
It would be better that you can help him/her.. I am a little busy testing new stuffs.. Thanks for the helps and talk more with you later...
LetMeKnow said:
It is not a problem... I think that my device is running the ET so it is a little faster...:silly: Just kidding...
It would be better that you can help him/her.. I am a little busy testing new stuffs.. Thanks for the helps and talk more with you later...
Click to expand...
Click to collapse
A LITTLE busy testing new stuff??? Haha! Are you doing anything but...?
---------- Post added at 10:48 PM ---------- Previous post was at 10:38 PM ----------
gmermel said:
Wow. 2 minutes and I'm getting help already.
I'm in TWRP. Where do I get the stock rom? I presume I'll download it my computer, but how do I tell the tablet to load it from there?
Click to expand...
Click to collapse
You don't. You have to copy the rom or firmware to your microSD.
Insert the card, boot into TWRP as described earlier.
Choose 'Install" and then navigate to your microSD and the zip you parked there.
Select it, swipe to flash it.
Now: I cringe, when someone on a perfectly fine and unlocked TF700 wants to flash back the Asus firmware. Ouch!
But I understand you only want to sell it and the buyer may not know how much better this tablet is on a custom ROM like CROMi-X. Sigh!
So, if you insist on flashing the latest firmware, go to the Asus support website, the download section, enter Transformer in the search box, select the TF700 and look for the 10.6.1.14.10 firmware. Make sure you select the one for your SKU, meaning US if you're on this continent (and I assume you are since you're awake at this time ), or WW or where ever you are.
Download the firmware and and on your computer, extract that zip file once - the result being another zip file.
It's that once extracted zip you want to copy to your SD, insert in your tab and flash in TWRP.
Ask if I left anything out.
Thanks. You're right, I'm in the US. But I am going to sleep. Will get on this in the AM.
You are correct to cringe. I rooted/C-romix'd a few months ago because I was frustrated by the constant lag on the tab. Figured if I bricked it, well, I wasn't happy with it anyway. I cringed when I went and did it because I knew I was taking a risk what with my capabilities. I've moved on to the Nexus 7 and just love it. Not just the performance. The small platform is just right....
Thanks for the rapid replies and the sophisticated yet understandable directions. Mostly, thanks for not calling me a knucklebrain even though I deserve it.
gmermel said:
Thanks. You're right, I'm in the US. But I am going to sleep. Will get on this in the AM.
You are correct to cringe. I rooted/C-romix'd a few months ago because I was frustrated by the constant lag on the tab. Figured if I bricked it, well, I wasn't happy with it anyway. I cringed when I went and did it because I knew I was taking a risk what with my capabilities. I've moved on to the Nexus 7 and just love it. Not just the performance. The small platform is just right....
Thanks for the rapid replies and the sophisticated yet understandable directions. Mostly, thanks for not calling me a knucklebrain even though I deserve it.
Click to expand...
Click to collapse
Not that long ago, I was exactly where you are now....:silly:
berndblb said:
Not that long ago, I was exactly where you are now....:silly:
Click to expand...
Click to collapse
Problem #1: When I opened the ROM.zip, I didn't get another zip, I got a folder with no zips in it (a blob.exe, several other .exe). When I moved that over to the SD and chose to install it TWRP returned a "failure" notification.
I'd like to get the stock ROM on for the buyer. What should I do
Problem #2: I still have CROM-X on the external card. It is installing, but which kernel should I use?
I'm going to use sbdags stock, and if you think that's a mistake I'll reflash.
gmermel said:
Problem #1: When I opened the ROM.zip, I didn't get another zip, I got a folder with no zips in it (a blob.exe, several other .exe). When I moved that over to the SD and chose to install it TWRP returned a "failure" notification.
I'd like to get the stock ROM on for the buyer. What should I do
Problem #2: I still have CROM-X on the external card. It is installing, but which kernel should I use?
I'm going to use sbdags stock, and if you think that's a mistake I'll reflash.
Click to expand...
Click to collapse
If you get the blob file you extracted once too often. The firmware is a zip inside a zip. You extract the downloaded file ONCE.
Stock kernel is fine.
Sent from my DROID4 using Tapatalk
I knew this day would come, I've traded PC trouble shooting for tablet troubleshooting. My son's tf300 gets to the screen where circles/dots go round and round and never gets any further. I am trying to learn everything I can and try everything I can before doing the wipe and starting over...as he has pictures and videos he'd like to save, and of course the all important saved game/app data...LOL. Anyway I'm new to tablets relatively speaking, but I've tried the volume down, and power button for doing a cold boot, same result. I've tried going to the recovery option just to see what that was about, and all I get is a flash of a screen saying something like updating android version or something like that and then the dead android with the usual red triangle and eventually the device will restart itself. I should that to him and told him he killed the android which gave me a puzzled look and then a smile...Anyway, you can't turn off the device nohow noway, except letting the battery drain completely.
I've been reading a little and learning about roots, backups, recoveries, etc... trying to come up with a plan of attack but feel like I'm spinning my wheels. Any advice here? and Can I access via PC to USB to device and just pull off his pics and videos to copy back over to the device after a wipe?
Problem started...I think when he ran the power dead completely and then had to restart...nor sure though... memories of a child are sketchy at best.
Feedback
chromegsx said:
I knew this day would come, I've traded PC trouble shooting for tablet troubleshooting. My son's tf300 gets to the screen where circles/dots go round and round and never gets any further. I am trying to learn everything I can and try everything I can before doing the wipe and starting over...as he has pictures and videos he'd like to save, and of course the all important saved game/app data...LOL. Anyway I'm new to tablets relatively speaking, but I've tried the volume down, and power button for doing a cold boot, same result. I've tried going to the recovery option just to see what that was about, and all I get is a flash of a screen saying something like updating android version or something like that and then the dead android with the usual red triangle and eventually the device will restart itself. I should that to him and told him he killed the android which gave me a puzzled look and then a smile...Anyway, you can't turn off the device nohow noway, except letting the battery drain completely.
I've been reading a little and learning about roots, backups, recoveries, etc... trying to come up with a plan of attack but feel like I'm spinning my wheels. Any advice here? and Can I access via PC to USB to device and just pull off his pics and videos to copy back over to the device after a wipe?
Problem started...I think when he ran the power dead completely and then had to restart...nor sure though... memories of a child are sketchy at best.
Click to expand...
Click to collapse
I have a solution, but your not going to like it, all data will be lost....:crying:
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700 and TF300: EP201_768_SDUPDATE.zip
B. For the TF101: E101_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Let me know if you need any help along the way.... Thx as always lj
lj50036 said:
I have a solution, but your not going to like it, all data will be lost....:crying:
...
Let me know if you need any help along the way.... Thx as always lj
Click to expand...
Click to collapse
So the RCK thing doesn't do anything unless you have SD card in to do something that's on the card?
And there's no way to access what's on the device without getting it booted all the way?
Sounds like your saving me and my son from updating from his original Android version after a wipe...Thanks
SKU
chromegsx said:
So the RCK thing doesn't do anything unless you have SD card in to do something that's on the card?
And there's no way to access what's on the device without getting it booted all the way?
Sounds like your saving me and my son from updating from his original Android version after a wipe...Thanks
Click to expand...
Click to collapse
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
lj50036 said:
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
Click to expand...
Click to collapse
Hey congrats on Recognized Contributor!
Happy
cmendonc2 said:
Hey congrats on Recognized Contributor!
Click to expand...
Click to collapse
I am happy about it.. Still so much to learn... Im not trying to let it go to my head...LOL:silly:
lj50036 said:
... NEVER select the WIPE DATA.. Bad things will happen...
Click to expand...
Click to collapse
As far as I know it's related only to custom recovery and if You have stock one it should work. Or I'm wrong?
Data Wipe
Graiden05 said:
As far as I know it's related only to custom recovery and if You have stock one it should work. Or I'm wrong?
Click to expand...
Click to collapse
Yes that is correct. I just like to move people away from even thinking its an option, as I have had people with stock everything and the Wipe Data
icon has even given them trouble, its just not worth touching....LOL...Thx as always lj
lj50036 said:
Yes that is correct. I just like to move people away from even thinking its an option, as I have had people with stock everything and the Wipe Data
icon has even given them trouble, its just not worth touching....LOL...Thx as always lj
Click to expand...
Click to collapse
Yep when I first got my tablet i was so scared about going into that menu because I learned that it was only 3-4 clicks away from a brick.
lj50036 said:
Yes the tablet having a locked bootloader... You can only flash signed zip files...From the SDcard
When your on that screen with the RCK.. NEVER select the WIPE DATA.. Bad things will happen...
Also when your in the RCK screen.. That is called the bootloader screen....So you know if some one refers to it by its name.....
Also that is were you can find your SKU on the bootloader screen upper left in white letters... WW, US, TW ............... Make sure you get the right SKU from asus for your 300....
Click to expand...
Click to collapse
Out of curiousity...Isn't doing these steps more or less just upgrading the firmware? Like getting an update from ASUS? If so, why will it lose all the data?
I haven't mustered up the courage yet to do this yet... actually it's more like getting the time to do it.
Feedback
chromegsx said:
Out of curiousity...Isn't doing these steps more or less just upgrading the firmware? Like getting an update from ASUS? If so, why will it lose all the data?
I haven't mustered up the courage yet to do this yet... actually it's more like getting the time to do it.
Click to expand...
Click to collapse
Yes, that is correct..but its not a ota.... So the process will wipe all data....Thx always lj
You could try using ADB to try and pull your files. I faced a similar problem and was able to pull some of my files:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
UndisputedGuy said:
You could try using ADB to try and pull your files. I faced a similar problem and was able to pull some of my files:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
chromegsx said:
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
Click to expand...
Click to collapse
Try installing the universal naked drivers.
cmendonc2 said:
Try installing the universal naked drivers.
Click to expand...
Click to collapse
Same result. Still nothing in Device manager.
chromegsx said:
Read your link. I have adb downloaded and cannot get it to list my device. I cannot see my device in device manager like you though.
Click to expand...
Click to collapse
Apologies, I'm very rusty with this stuff now. If flashing a .blob file doesn't wipe data (I can't remember whether it does or not), perhaps you could try doing that if you're able to get into recovery?
Call me, Beep me, If you wanna reach me.
UndisputedGuy said:
Apologies, I'm very rusty with this stuff now. If flashing a .blob file doesn't wipe data (I can't remember whether it does or not), perhaps you could try doing that if you're able to get into recovery?
Call me, Beep me, If you wanna reach me.
Click to expand...
Click to collapse
I just gave in and did the flash procedure. Looked like it went well, now I'm watching the circles for round again for the last 10 minutes.
chromegsx said:
I just gave in and did the flash procedure. Looked like it went well, now I'm watching the circles for round again for the last 10 minutes.
Click to expand...
Click to collapse
Just wanted to follow up on this...lj50036 is top noctch helper here. going above and beyond does not even come close to explaining what he has tried to do for me. Ultimately it was after we hit a brick wall, that I suggested flashing back to an earlier version that finally worked. I'm not convinced flashing to the latest version (like I first tried) would not work, as I didn't personally create/rename the SD card to do the flash. but re-flashing the original firmware got the tablet to boot finally. Of course all was lost other than what had been automatically backed up via google servers. Pictures/videos back to exactly one year from when the pad stopped booting were recovered. Everything before a year was gone. No game data or installs were saved. I thought maybe it had to do with a space issue, but after re-installing every app my son had before and about 1GB worth of pics/videos restored, there is still 16GB left, I doubt game/user data would have consumed that much...so I still have no idea what might have cause the pad to stop booting. Other than it was trying to do something important when he ran the battery dead. So at this point I'm having my son clean out unwanted apps, and we are going to unlock and root after a proper backup is done. Thank you to all that have had input on my dilemma. I've learned a ton.