Related
I just got a message saying there is an update available. I told it not to do it. I do not want RC30 because it gets rid of root.
However, the other side of me is tempted to see if telnetd and all the other goodies are still there.
I'm also very tempted to install it to see if it removes root access. I hope someone who doesn't care about root access tests this out and reports back soon, because my curiosity is about to get the better of me.
It won't stop prompting me and I don't think I have the heart to keep saying no.
Look on your phone, and see if there is a file named "update.install" in the /cache folder. Or maybe in the /cache/recovery folder. If so, would you mind grabbing it off your phone and posting it somewhere?
Woobins said:
I'm also very tempted to install it to see if it removes root access. I hope someone who doesn't care about root access tests this out and reports back soon, because my curiosity is about to get the better of me.
It won't stop prompting me and I don't think I have the heart to keep saying no.
Click to expand...
Click to collapse
If you ever do say yes can you tell us what your software version is?
JesusFreke said:
Look on your phone, and see if there is a file named "update.install" in the /cache folder. Or maybe in the /cache/recovery folder. If so, would you mind grabbing it off your phone and posting it somewhere?
Click to expand...
Click to collapse
neoobs said:
If you ever do say yes can you tell us what your software version is?
Click to expand...
Click to collapse
The only file of interest in the /cache directory is named, signed-RC30-from-RC29-fat.1582cace.zip. From this I'm assuming it's going to update my phone to RC30. I've made the file available here in case anyone is curious.
Ah, ok. It looks like that's the same file I just posted a link to then. Thanks
boo
neoobs said:
If you ever do say yes can you tell us what your software version is?
Click to expand...
Click to collapse
It did it.
just as I get home to catch up on the "jailbreak" and start doing it I get an
error while connecting to server, "connection refused"
error while receiving from server null
So I figured I'd check (I neglect my phone when I'm at work, and no, I don't recall accepting the update)
lo and behold:
Build description: kila-user 1.0 TC4-RC30 116143
ota-rel-keys, release-keysBuild ID: TC4-RC30
Build Date: Fri Oct 31 19:00:53 PDT 2008
Build type: user
Phone type: dream
Product brand: tmobile
Build user: android-build
Build host: undroid11.corp.google.com
Linux kernel version: 2.6.25-01843-gfea26b0
[email protected] #6Mon Oct 6 14:13:36 PDT 2008Baseband version: 62.33.20.08H_1.22.12.29
RIL Impl version: HTC-RIL 1.0 (Aug 19 2008,21:32:33)
Default keyboard device: trout-keypad-v3
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
MMTest97 said:
error while connecting to server, "connection refused" error while receiving from server null
Click to expand...
Click to collapse
After starting telentd via pTerminal?
quedijo said:
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
After starting telentd via pTerminal?
Click to expand...
Click to collapse
It has more than just that fix. It patches quite a few other packages on the phone... for what purpose? I don't know.
quedijo said:
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
After starting telentd via pTerminal?
Click to expand...
Click to collapse
yes
tried pterminal and terminal emulator
netstat shows the ip
but telnet from pc fails to connect failed on port 23 and the port shown on netstat
I also tried the steps koush put up but still fail
granted I'm no linux/unix pro and I just installed cygwin a couple days after the connect bot app came out; so I may be doing something wrong
Does google check in the new change into the source tree before they push a update?
In addition to jailbreak fix there is a battery fix as well and a few others according to androidcommunity.com.
Well I finally got tired of clicking no and decided to go ahead and perform the update. After it finished, the phone rebooted and instead of booting up, the phone simply displays a '!' icon with a triangle around it and hangs. I'm not taking this as a good sign. I tried removing the battery but that didn't help.
I really hope the update didn't just brick my phone.
Woobins said:
Well I finally got tired of clicking no and decided to go ahead and perform the update. After it finished, the phone rebooted and instead of booting up, the phone simply displays a '!' icon with a triangle around it and hangs. I'm not taking this as a good sign. I tried removing the battery but that didn't help.
I really hope the update didn't just brick my phone.
Click to expand...
Click to collapse
When you're at the screen with the ! and triangle, Try pressing home+back (maybe several times). It should reboot, and hopefully boot back up normally.
JesusFreke said:
When you're at the screen with the ! and triangle, Try pressing home+back (maybe several times). It should reboot, and hopefully boot back up normally.
Click to expand...
Click to collapse
No dice. The phone reboots but still hangs at the error screen. The only thing I can think that might have caused it is that, while playing around, I set a root password and forgot to clear it before the update rebooted the phone. Who knows. I guess I'll call tmobile and see what can be done.
edit: I should mention that pressing alt-w to wipe the phone does not work either. It still returns to the error screen. I'm talking to tmobile tech support now and the original tech said that 'they were informed that a small number of users might experience this problem with the update'. I'm on hold waiting to talk to an android tech now. My advice to everyone who's played around with adding any extra files to /etc to hold off on upgrading for now. I'll report back with the results of my call with the android tech.
Now they're saying they would like to exchange the phone. Problem is the g1 isn't in their replacement program yet.
Aaaand they're out of stock so it's going to be at least 2 weeks.
I wish I'd have just kept hitting no.
Disturbing news, especially as I'm wanting to install a modified rc30. What exactly did you change?
I was playing around with trying to get dropbear to work and in the process I created some files in /etc (passwd, shadow, groups, etc). As well as creating a new regular user, I also added a password to the root account and carelessly forgot to remove it before applying the update. I'm only guessing here but I wouldn't be surprised if the new root password is what did it. The system does not have one by default and I wonder if that caused it to hang, waiting for a password to be entered while booting.
On a brighter note, I persisted and was able to get them to send me out a new phone immediatly. This has the added benefit of possibly fixing the loose-screen/creaking problem that I, like many others, am experiencing with the phone.
I'm wondering if I should try manually applying the update from the SD card while I wait for the new phone to see if that solves the problem. I probably should have tried that before calling. I'm hesitant to do that now, however, since if it does fix it, I'm not sure how tmobile would react to me returning a perfectly working phone.
Woobins said:
No dice. The phone reboots but still hangs at the error screen. The only thing I can think that might have caused it is that, while playing around, I set a root password and forgot to clear it before the update rebooted the phone. Who knows.
Click to expand...
Click to collapse
I don't get it. The update should restore whole /system folder, isn't it? /etc is actually a symlink to /system/etc, so, it should be restored too and passwd file successively removed.
Otherwise, I don't see any problem to keep the root access! Since /system is mounted without nosiud (any changes in RC30?), just keep a copy of shell with chmod 4777 somewhere there... where it wouldn't be removed by update, as it keeps passwd, and that's it.
Please, tell me where am I wrong, cause I definitely should be wrong somewhere.
PS: BTW, what was the progress with dropbear? I actually tried to make it work too, creating passwd etc, but no success...
Dimath said:
I don't get it. The update should restore whole /system folder, isn't it? /etc is actually a symlink to /system/etc, so, it should be restored too and passwd file successively removed.
Otherwise, I don't see any problem to keep the root access! Since /system is mounted without nosiud (any changes in RC30?), just keep a copy of shell with chmod 4777 somewhere there... where it wouldn't be removed by update, as it keeps passwd, and that's it.
Please, tell me where am I wrong, cause I definitely should be wrong somewhere.
PS: BTW, what was the progress with dropbear? I actually tried to make it work too, creating passwd etc, but no success...
Click to expand...
Click to collapse
Unlike the RC29 update, the RC30 update doesn't actually do a complete wipe and restore of the /system folder. It patches a number of files (which will fail if any of them have been modified), and does a recursive chmod on the entire /system directory to clear any suid bits.
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.
I have a WiFi only Xoom and it is unlocked/rooted.
I decided to use the hack on the stock browser which enables fulltime desktop mode. I downloaded the apk, renamed it to framework-res.apk and dropped in system/framework and overwrote the existing file. I dl the file from http://forum.androidcentral.com/xoom-rooting-roms-hacks/75616-full-browser.html
I've since discovered that had I read further into the thread, I would have known not to use the file on a WiFi Xoom.
The gist of my problem is I have managed to finally get the Xoom to boot to the homescreen but It's force close city. As soon as I force close one app, others come up (FC) too. The one FC that will not go away is Launcher. it will FC loop forever. The Google/Mic in the top left corner is missing but the bottom bar has the normal icons, but I can't use them because I am stuck in a FC loop. I also get stuck/locked up while rebooting using the power button and volume down and have to use the power/volume up to restart.
I'm wondering if I use the the same one click root file (with kernel) that I still have and root again if this may fix the issue?
Perhaps their may be an easier method if I am only missing the one (framework-res.apk) file I overwrote?
Any help would be most appreciated.
You wanted a new theme right?
http://forum.xda-developers.com/showthread.php?t=1015434
This theme has the framework you are looking for.
Or.. this is the original Wifi Xoom system dump. It may be in there. (I'm at work so i cant check myself)
http://forum.xda-developers.com/showthread.php?t=1011484
Just got home and read your post and do appreciate it.
I was going to begin but just discovered that my Xoom will no longer mount on my pc. Not sure what to do....
yooper said:
I have a WiFi only Xoom and it is unlocked/rooted.
I decided to use the hack on the stock browser which enables fulltime desktop mode. I downloaded the apk, renamed it to framework-res.apk and dropped in system/framework and overwrote the existing file. I dl the file from
I've since discovered that had I read further into the thread, I would have known not to use the file on a WiFi Xoom.
The gist of my problem is I have managed to finally get the Xoom to boot to the homescreen but It's force close city. As soon as I force close one app, others come up (FC) too. The one FC that will not go away is Launcher. it will FC loop forever. The Google/Mic in the top left corner is missing but the bottom bar has the normal icons, but I can't use them because I am stuck in a FC loop. I also get stuck/locked up while rebooting using the power button and volume down and have to use the power/volume up to restart.
I'm wondering if I use the the same one click root file (with kernel) that I still have and root again if this may fix the issue?
Perhaps their may be an easier method if I am only missing the one (framework-res.apk) file I overwrote?
Any help would be most appreciated.
Click to expand...
Click to collapse
I did the same thing my friend, twice in fact. Actually it was likely my post you are referencing above Second time around I still had USB debugging turned on so I didn't have to reload the images.
Do you have the original .apk backed up? If not, i'm attaching it. What I did to fix this was using the adb shell, I remounted the file system as rw and adb pushed the original .apk. You're good to go after that. Hope you have your USB Debugging still turned on
Hope this helps.
yooper said:
Just got home and read your post and do appreciate it.
I was going to begin but just discovered that my Xoom will no longer mount on my pc. Not sure what to do....
Click to expand...
Click to collapse
Are you stuck at the dual core screen? If so can you get into fastboot? You would have to flash the system and boot .img I believe. This is what I had to do when i bricked my wifi without having the USB Debugging turned on. Don't lose hope, you likely do not have a $600 paperweight on your hands.
joen1ce,
I cant thank you enough for your help and time as well as uploading the file for me. Thank you.
I do have dubugging turned on and can boot to the home screen. Actually I have gotten a bit further. I found that if I hit "ok" and force close and quickly continued to hit the time on the lower right corner, I could eventually get into the setting menu. Takes a lot of "tapping" to get it to work, but it did. I am able to get into the reset option but it simply wont work. I push the button and nothing happens. I even tried using bluetooth via my Fascinate and Xoom to see what I could do with the apk you uploaded within the xoom since I could get into the bluetooth downloads, but no worky.
Upon startup, I find that I can get into "Starting fastboot protocol support" as well as well as RSD - Fastboot and NvFlash. Although, I still cant get the Xoom to talk with the computer. I have a Mac with Windows installed and have neither will communicate with the Xoom.
I'm not overly savy with ADB and am not sure if I would know what to do with a boot.img nor where to put it let alone the commands needed to make it work with no communication between devices.
I do have SDK/ADB and the Fastboot (.exe) both on the Mac and Windows side.
I can do an exchange on the Xoom but would rather fix it myself and consider it a valuable learning experience, but I'm at my wit's end.
yooper said:
joen1ce,
I cant thank you enough for your help and time as well as uploading the file for me. Thank you.
I do have dubugging turned on and can boot to the home screen. Actually I have gotten a bit further. I found that if I hit "ok" and force close and quickly continued to hit the time on the lower right corner, I could eventually get into the setting menu. Takes a lot of "tapping" to get it to work, but it did. I am able to get into the reset option but it simply wont work. I push the button and nothing happens. I even tried using bluetooth via my Fascinate and Xoom to see what I could do with the apk you uploaded within the xoom since I could get into the bluetooth downloads, but no worky.
Upon startup, I find that I can get into "Starting fastboot protocol support" as well as well as RSD - Fastboot and NvFlash. Although, I still cant get the Xoom to talk with the computer. I have a Mac with Windows installed and have neither will communicate with the Xoom.
I'm not overly savy with ADB and am not sure if I would know what to do with a boot.img nor where to put it let alone the commands needed to make it work with no communication between devices.
I do have SDK/ADB and the Fastboot (.exe) both on the Mac and Windows side.
I can do an exchange on the Xoom but would rather fix it myself and consider it a valuable learning experience, but I'm at my wit's end.
Click to expand...
Click to collapse
Copy the apk file I uploaded to the directory where you have the adb files. Go to the command line and switch to that same directory.
Let the device reboot to the point where you get those damn force close messages.
at the command line type:
adb devices
you should see your device listed there. If so, do the following:
adb shell
mount
You should see all the mounts on your device listed. Copy the path for system you will need it for this next part. It may be exactly like mine. So next you will type in:
mount -o rw,remount /dev/block/platform/sdhci-tegra.3/by-name/system /system
the "/dev/block/platform/sdhci-tegra.3/by-name/system" above is the true path
to my /system mount. Use whatever the path yours is mounted to from the previous command.
Next hit ctrl + c to exit out of the shell and at the command line type this:
adb push framework-res.apk /system/framework/framework-res.apk
If the above was successful you should be able to reboot the device and be back in business.
You fixed it!!
joen1ce, I can't begin to thank you enough for your help Took me a couple tries as well as rebooting the Xoom for it to take but by god it worked!!!
I'm sure your post will help others out out in future too. As the WiFi Xoom becomes more popular, I'm sure this will happen again to more people looking to modify their Xoom stock browser to desktop mode.
I'm thinking their should be a sticky on bricking with possible fixes and your post should be noted for sure.
People like you really help make this site the cat's a**.
Thanks again,
Mark
yooper said:
joen1ce, I can't begin to thank you enough for your help Took me a couple tries as well as rebooting the Xoom for it to take but by god it worked!!!
I'm sure your post will help others out out in future too. As the WiFi Xoom becomes more popular, I'm sure this will happen again to more people looking to modify their Xoom stock browser to desktop mode.
I'm thinking their should be a sticky on bricking with possible fixes and your post should be noted for sure.
People like you really help make this site the cat's a**.
Thanks again,
Mark
Click to expand...
Click to collapse
No problem, glad I could help. I bricked my Xoom basically within an hour of buying it and I know how it feels, especially when trying to be moral and not return it! Had it about a week now and it's my first Android device so I'm new to these forums. But the helpfulness of the community is very impressive indeed.
Regards,
Joe
joen1ce said:
Are you stuck at the dual core screen? If so can you get into fastboot? You would have to flash the system and boot .img I believe. This is what I had to do when i bricked my wifi without having the USB Debugging turned on. Don't lose hope, you likely do not have a $600 paperweight on your hands.
Click to expand...
Click to collapse
joen1ce. Could you please help? I am stuck at the Dual Core Screen and cannot get my computer to recognize my device in adb. I am trying to return to stock 3.2.1.
After a failed OTA update, my iconia a500 stock (never rooted) bricked. Got CWM v5.0.2.3 installed through APX mode and the recovery mode starts pretty smooth when I boot with Vol DOWN + Power.
I can install every ROM (custom and stock) I could lay my hands on, ranging from 3.0.1 to 4.0.*. Also did the wipes in all imagined combinations: before installing a rom, right after installation (before first boot) and also after 1st boot attempt. Also made sure to format /data, /cache, /system and so on before every installation. Tried different SD cards and also a USB mass storage thumb drive.
The thing I just can´t explain yet, is how on every try the same thing happens, 1st boot (long one) seems to just fail and my tab gets back to that screen where you see the clock on the lower right and the pulley icon saying "Android System" on the upper left corner. After that, every boot does that and the Android initial setup screens never comes up.
Every rom I try delivers the same result, even though I get their splash logos (ephiphany, taboonay, thor) and all seems to be going OK, it always gets back to that "Android System", no error messages, nothing.
I found out that Thor rom 14.2 made the "Android System" screen touch responsive (no other did that), I can touch the clock, open the first level of settings and if I try to drill down, touching storage for an instance, it won´t load the app/menu, it gets righ back to the good old "Android System" screen.
After a custom rooted rom gets installed and I get the "Android System" screes, adb works fine and I manage to get in the tab with a shell, mount an SD card, use the ps command to see the process running and even start the bootanimation myself, so I´m assuming that android is runing OK, at least on the background. Adb also allows me to push files and install apks normally. Have some linux background myself, used the shell to browse around and checked some of the logs, nothing clear showing an error that would force my boots to terminate sooner.
Wondering if anyone experienced something like that and could point me at some direction. Am I missing something here ?? Thanks guys and great job i might add.
Still no luck ...
Hi everyone, wanted to get back and maybe share my logcat and bugreport retrieved by adb shell. If any of the more experienced members could take a look and point me to some direction, I´d really appreciate. Really i´ve tried all the methods arround here and other forums to unbrick it, it behaves and responds as if everything was OK and still fails to boot for the first time, even though, the system appears to be running ok on the backgroup the initial setup wizar never comes up and I get the "Android System" dreadfull screen.
Discovered that once in with adb shell I can run the setup wizard (calling it by prompt: am start -a android.intent.action.MAIN -n com.android.setupwizard/.SetupWizardActivity), but it only stays opened for a couple of seconds and never finishes its business, it just abends.
Not sure if this would be the proper thread to post, it would be great if someone could adivise where would be a proper place.
Thanks for your time.
Hi vortex,
Were you able to fix that? I'm having the exact same problem. :-(
I've been trying for days already.
Cheers,
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
irepressed said:
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
Click to expand...
Click to collapse
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
tobdaryl said:
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
Click to expand...
Click to collapse
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
irepressed said:
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
Click to expand...
Click to collapse
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
tobdaryl said:
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
Click to expand...
Click to collapse
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
irepressed said:
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
Click to expand...
Click to collapse
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
http://www.mediafire.com/?tk3cifzci0vw24e
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
tobdaryl said:
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
Click to expand...
Click to collapse
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Ok, I just killed my adb.exe, tried the command again and that got rid of the out of date error.
But, still stuck with the "device not found".
irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
http://www.mediafire.com/?ybplc1ws8uvskhf
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
tobdaryl said:
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
Click to expand...
Click to collapse
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
irepressed said:
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
Click to expand...
Click to collapse
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
tobdaryl said:
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
Click to expand...
Click to collapse
Yep, that's the file I was talking about.
I now need to flash and reboot, your file is at the root of an SDcard in my TF300T, I go through the Install menu and then, can't seem to view the content of my sdcard. Tried to mount it first but can't select it either, it will simply stay on "Internal Storage".
EDIT: The RCK icon is the only one right now that boots me into something. If I try the USB icon, it just stays on that screen forever.
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
http://www.mediafire.com/?hagehu5qu5ky6sf
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
tobdaryl said:
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
Click to expand...
Click to collapse
Zips trashed, kept only the one provided in your latest answer.
No cord between PC and tablet. Still unable to click on "Using external SD" or "Mount SDCard". It simply won't let me check the box or switch the bullet.
As for using this SDcard before, yes in a PC, but no, first time in my Asus. Also tried with another one just in case and same result.
As for backups and flashable zips, I kept everything from when I did my root and rom install.
I do know that I have a backup in the Restore menu of TWRP, which seems about the time I installed it. I suppose I could simply do a restore and avoid additional headaches, but my question is, what exactly will it restore? At this point, I'm mentally prepared to go back to what I had after installing Hydro 4.1, as long as I can use the tablet ASAP.
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
tobdaryl said:
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
Click to expand...
Click to collapse
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
irepressed said:
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
Click to expand...
Click to collapse
Great I'm glad you are happy. I had hoped for the outcome you expressed but this works also.
You're welcome!