Related
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.
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
baareem said:
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
Click to expand...
Click to collapse
what color is your cwm screen?
this may be a simpler way of gettin cwm:
http://forum.xda-developers.com/showthread.php?t=1220090
specifically, the CWM instructions set.
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
baareem said:
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
Click to expand...
Click to collapse
if you still have root, download from market
sgs kernel flasher and the flash the gingerbread kernel to give you RED recovery and flash the rom of your choice after a factory reset and usual wipes
Cool... i'm now running CM7 !
Here is what i missed for anyone who would have the same problem in the future (you can find the download links here: http://forum.xda-developers.com/showthread.php?t=1220090 ):
CWM Installation Instructions:
1) You must be rooted.
2) If you have a /Voodoo folder on your internal SD card, delete it and reboot.
3) If you're already running a custom ROM with Voodoo lagfix FULLY enabled, you can skip to step 7.
4) Download CWM-community-kernel-v8.zip if you're on Froyo or CWM-infused-v2.0.1-kernel.zip if you're on Gingerbread and place it on your internal SD card.
5) Install SGS Kernel Flasher from the Market.
6) Open SGS Kernel Flasher, select choose kernel, select the file you downloaded, and select flash kernel. Your phone will reboot and begin to enable Voodoo lagfix. Let it do that and boot all the way up. It will take a while (5-10 minutes) because it's converting all partitions to ext4.
7) Download update-infused-v2.X.X-full.zip and place it on your internal SD card.
8) Power off your phone.
9) With the phone powered off, hold both volume keys and the power button for about 10 seconds and then release. This should boot you into RED CWM.
10) Select "install zip from sdcard" and select update-infused-v2.X.X-full.zip.
11) Once that finishes, select "wipe data/factory reset".
12) Select "reboot system now".
13) Do NOT restore system data with Titanium Backup. Do NOT restore ALL apps with data. If you absolutely must restore something with Titanium Backup, only restore MISSING apps with data.
Click to expand...
Click to collapse
Now just another question: i noticed different errors when running the market and other old built-in apps... I just need to reinstall gapps right?
yeah, that is why it's stickeyed.
you just had to read/search them.
market wise, there's a market fix
or you can also factory reset and wipe cache and dalvik in cwm
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread (NOT) SOLVED.
--------
(Edited after realizing gapps still don't show up as installation didn't really worked)
baareem said:
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread SOLVED.
Click to expand...
Click to collapse
np. take it easy, bro.
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
E: Can't open /emmc/gapps-gb-xxxxxxx-signed.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
baareem said:
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
Click to expand...
Click to collapse
what version of ROM were you running when you tried this?
Stock FRoyo?
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
baareem said:
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
Click to expand...
Click to collapse
I haven't played with CM7, it's not an infuse based rom.
I recall some installation issues with it.
I remember an unsuccess reboot intially and pull battery thing..not sure.
If you're looking to install another rom, odin back to stock and start over.
check out my sig line for some useful links
Abstact: my GS4G is bootlooping between the Samsung and T-Mobile splash screens after following this tutorial on removing 'gremlins' and flashing icbinb 2.3.7 for absolutely no discernible reason.
First off, I'd like to apologize for having made this thread in this area vs posting about this in the proper thread. It looks like somewhere along the lines, morons forced the staff to enact a rule about not being able to post to dev forums with less than ten posts, effectively ruining things for those of us who have made accounts but never post because we're usually able to fix our problems by reading around etc prior to having to post about it.
Either way, I decided to do my tri-yearly phone wipe and try to update today thinking there may have been some new developments for the GS4G since I last looked. Having flashed Samsung's (leaked? grey area official?) GB rom it unrooted my phone and I needed to fix that. Luckily I ran across a supposed 1-click root and general phone junk clean up tool; as listed above. After running that I was given CwM voodoo lagfix 3.0.2.8x. I made a back up of the freshly formatted phone and proceeded to flash icbinb 2.3.7.
Right after it started to bootloop at which point I began looking around the thread for any advice. Obviously, people were saying to wipe everything but to my knowledge I'd done so prior yet even after wiping the cache, dalvick cache, and fixing permissions I was still left with a bootloop of the Samsung and T-Mobile splash screens. Formatting /cache, /data, /system, and /sdcard only caused further problems (big surprise!). There hit a point at which CmW was giving me all kinds of errors claiming it couldn't find certain directories every time I gave it a command (I'd elaborate on exactly what the errors were but I was focused on trying other methods and it's been a few hours since I've seen the exact messages). After becoming completely inoperable (to the point of the icbinb 2.3.7 claiming it didn't know what phone I had; a problem stemming from formatting /system or so the thread made it seem) I was forced to run the Odin 1-click process again just to be able to do much of anything.
There was one point at which the phone booted to a home screen yet it immediately started yelling at me about the USB not being assigned (IIRC?) every time I went to do much of anything and literally the entire settings screen consisted of sliding bars (like volume or brightness controls) which had no effect from what I could tell.
After that I attempted four more installations of icbinb 2.3.7 (with many forcing me to run Odin to revert back to some functional state) trying different ways of wiping the cache etc before and after, etc with no luck.
At no point were there problems with anything I attempted to do with my phone untill I flashed icbinb 2.3.7 so I am completely baffled. It's even more frustrating that icbinb is said to be the most stable ROM for the GS4G and virtually nobody has complained of bootlooping or any real problems with flashing it.
Again, I'm sorry for posting this here but there isn't another place I feel it would be allowed but if there's a better place by all means please move it.
Thank you to anyone who is able to help me.
Download ICBINB again. Make sure that you compare the filesize of your downloaded file to the one on the download page:
https://sourceforge.net/projects/teamacid/files/roms/icbinb/
Try following my GB starter pack guide from step 6
Do not download the fb_kc1... File since you won't need it.
http://forum.xda-developers.com/showthread.php?t=1223765
Install ICBINB again. Post back here if you need more help.
I'm on my fifth ICBINB download and they've all been 120mb (122,462kb) instead of 125.4mb
I've never seen anything like this before what are people paying sourceforge for ugh
thanks for the quick reply though and I'm gonna keep downloading till I get it right (unless you feel like mirroring it to some place that allows for full downloads)
should I assume "11) Flash the GB rom you put on your sd card" means flash ICBINB
yeah I tried ten times and it's been the same file size every time. I even tried changing the file name and save location but that didn't matter. this is pretty infuriating.
Asemic said:
I'm on my fifth ICBINB download and they've all been 120mb (122,462kb) instead of 125.4mb
I've never seen anything like this before what are people paying sourceforge for ugh
thanks for the quick reply though and I'm gonna keep downloading till I get it right (unless you feel like mirroring it to some place that allows for full downloads)
should I assume "11) Flash the GB rom you put on your sd card" means flash ICBINB
yeah I tried ten times and it's been the same file size every time. I even tried changing the file name and save location but that didn't matter. this is pretty infuriating.
Click to expand...
Click to collapse
Download winMD5Sum
http://www.nullriver.com/downloads/Install-winMd5Sum.exe
It'll let you verify that the file you downloaded is exactly the same as the one that's hosted on sf. I'm about to run the md5sum checker on the file to verify it's the same.
EDIT
Once you have downloaded and installed the program on your computer, right click on the icbinb zip file, select Send To > winmd5sum
It'll have a box called compare, paste this in there:
Code:
428563f929b64fda7f10cda3ff31764a
If your download is good it'll say "MD5 Check Sums are the same" after you click compare.
Asemic said:
I'm on my fifth ICBINB download and they've all been 120mb (122,462kb) instead of 125.4mb
I've never seen anything like this before what are people paying sourceforge for ugh
thanks for the quick reply though and I'm gonna keep downloading till I get it right (unless you feel like mirroring it to some place that allows for full downloads)
should I assume "11) Flash the GB rom you put on your sd card" means flash ICBINB
yeah I tried ten times and it's been the same file size every time. I even tried changing the file name and save location but that didn't matter. this is pretty infuriating.
Click to expand...
Click to collapse
I had this problem with ICBNB today switching from Val-Black i decided to try thomas gremlin remover and ended up bootlooped then tried Fb's Starter pack and after flashing the rom said it got installed but it was a mix of both of them so did GB Starter pack again but before flashing ICBNB i flashed bhunds latest rc1.1 kernel rebooted back into recovery adn then flashed with manually formatting /system /data and /cache with no problems
Try that it worked good for me hopefully for you too ive tried it twice in a row right now
do a custom install theres a issue with the standard (first choice installer) that doesnt actually wipe the system partition....
RaverX3X said:
do a custom install theres a issue with the standard (first choice installer) that doesnt actually wipe the system partition....
Click to expand...
Click to collapse
+1
i told dsex day it came out about the issue, glad i got it right
also Raver I formatted the /system /data and /cache manually on Val-Black and dsp is working flawlessly for me now thanks for everything!
yeah I think I may have actually gotten it! I managed to get /system wiped after fighting with "format_volume failed to unmount "/system"" for a bit
after doing a quick install it booted and gave me the proper (or at least new to me) boot animation and I'm letting it sit for a bit at the android touch screen.
it seems like this may be solved but I'm gonna give it a little bit just to be sure.
thanks so much everyone, I mean that from the bottom of my heart
looks like things are working very well. again sorry for having to post about it here.
sanQ~
Good to hear everything is cool now....the rom is awesome
Thank's aren't asked for but aappreciated
@Asemic: If this issue is resolved can you please add [SOLVED] to the title of this thread. Thanks!
Okay, have found a lot of threads similar to this, but with key differences that are making the answers not-terribly-helpful in my particular circumstances. Not a comment on the answers, but enough that I feel the need to ask my question specifically.
I am trying to gain more control over my MyTouch 4g Slide (aka Doubleshot), obviously on T-Mobile.
It is running Android 2.3.4, and has hboot 1.45.0013. I have wiped it a few times in the process of fuxing with it, so right now I'm not worried about losing anything other than basic function (i.e., bricking it is still bad).
I have tried the zergrush exploit (it's been closed),
have managed to unlock the bootloader using the HTC unlock tool,
and have managed to flash the appropriate Clockworkmod recovery and get the blue menu to come up.
My overall goal isn't to do any major overhauls- I want to be able to allow some apps to turn my GPS on and off, clean out some bloatware, and put some new ringtones into the same folder as the stock ones. My understanding is that temporary root access is enough to do these things- go in and clean up, change some permissions on apps, then go back to being a normal user, just like with a well-managed Linux computer.
I just can't seem to get the next step to work.
My understanding is that I now somehow use Clockworkmod to install Superuser from the .zip archive. The options I get in the recovery screen are:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
install zip from sdcard
backup and restore
mounts and storage
advanced
power off
My impression is that I should be using "install zip from sdcard" to install Superuser, but when I select that, the menu just disappears, and I am left looking at the logo, with no further options. I have seen it implied that there should be choices about which zip to install- those never come up.
What am I missing? My google-fu is failing me in trying to find instructions or guides for this particular combination of limitations and progress.
EDIT TO ADD: Ah- found part of my problem... the recovery menu uses the camera button, not the power button. Still somewhat at a loss to see what's next. Installing from the SD card fails. Info in a second post.
Got the menu working, but now failing to install Superuser. I get the following output:
Mounting SYSTEM...
Deleting SYSTEM:bin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E:Error in /sdcard/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted.
Now what?
I am seeing in other places that HBOOT 1.45.0013 can't be rooted. I've been trying for about 9 hours to do this. . .no luck, even with a variety of methods.
bummer.
I'm in the same boat as the both of you. Spent the last two hours and enough tabs in my browser that my music player was skipping when switching between them, and my machine is nothing to be scoffed at!
There just doesn't seem to be enough clear information about how to root this device, and with only 7 pages of development threads, it's gonna be hard to be told to search!
In recovery you use the trackpad to navigate, and select....also, why not just flash a pre rooted stock rom? Follow the directions in this thread, it will work with any rom, not just ICS roms. I used the instructions in this thread to install Bulletproof on my Bf's phone which was an insurance replacement, so it had the same hboot that you guys have, and S-on. It worked flawlessly, I am not sure why so many people are having such a hard time, because it worked the first time perfectly for me.
http://forum.xda-developers.com/showthread.php?t=1508556
Edit: Which recovery are you using?
Woot! Oops...
Well, I managed to root my phone... and then borked it through my own overexuberance. :headdesk: Oh well, I can fix it. Important part:
I finally found out what "Status 0" means- the zip you are trying to install wasn't signed properly. I re-downloaded, no luck. But there is an option to turn off signature checking in CWM, and that worked, after some fiddling- Superuser installed and worked fine. Not sure if re-downloading ended up being relevant or not.
So, you can root this version without flashing a new ROM.
That said, I think I probably did enough weirdness to mine that I will go for a new stock ROM, so much thanks to yellowjacket for posting that thread link. Removed HTC Sense, then somehow borked Go Launcher Ex, so my phone doesn't have a home screen and I can't get to the app I used to move stuff to fix it. Of course I never found a set of instructions for making a Nandroid backup until after I messed things up... Oh, well, time to go looking for the stock ROM.
Thanks all!
If anyone has a Nandroid backup or copy of the dead-standard out-of-the-box ROM for this phone, please let me know. All I am finding is modified versions. Can't find the base that they were made from, and even the most basic version says it requires S-OFF to install. :headdesk:
Do you specifically need a nandroid backup, or would a flashable ZIP do? Pointers to the latter are available.
Flashable zip would actually be preferable, and pointers would be very much appreciated. I know they have to be out there somewhere, I'm just not finding the right search terms to locate them among all the modified versions.
Look at this post in the developer reference thread: http://forum.xda-developers.com/showpost.php?p=17384145&postcount=7
(There's lots of stuff listed there, but look for the 400 MB+ images.)
NOTE: Some ZIP tools get confused by these signed ZIPs, so they might seem corrupt. Check the MD5s to see that you got a good download. 7Zip seems to deal with them OK if you want to look inside.
I have personally flashed the 1.28 and 1.55 ZIPs without incident, but I did check the MD5s.
Well, I was not able to restore the ROMS from the links wjcarpenter linked- everything worked fine, as far as I can tell, but the phone said the "updates" were older than what was originally installed, so the installation was aborted. Not sure how to fix/handle that.
For the moment, I have one of the cleaned-up ROMs that is very similar to stock, but I would really rather it not be obvious that I rooted the phone the second you start it up (the one I found has changed the startup animations), so I will keep looking.
If it's going to be obvious that I changed the ROM, I guess I might as well start looking for the best custom ROM... any suggestions as to which is the most stable?
Firefairy said:
Well, I managed to root my phone... and then borked it through my own overexuberance. :headdesk: Oh well, I can fix it. Important part:
I finally found out what "Status 0" means- the zip you are trying to install wasn't signed properly. I re-downloaded, no luck. But there is an option to turn off signature checking in CWM, and that worked, after some fiddling- Superuser installed and worked fine. Not sure if re-downloading ended up being relevant or not.
So, you can root this version without flashing a new ROM.
That said, I think I probably did enough weirdness to mine that I will go for a new stock ROM, so much thanks to yellowjacket for posting that thread link. Removed HTC Sense, then somehow borked Go Launcher Ex, so my phone doesn't have a home screen and I can't get to the app I used to move stuff to fix it. Of course I never found a set of instructions for making a Nandroid backup until after I messed things up... Oh, well, time to go looking for the stock ROM.
Thanks all!
Click to expand...
Click to collapse
Just think of it as a big learning experience! The first time I rooted a phone, I messed it up so much I had to keep flashing back to stock and rerooting at least 3 or 4 times. Thankfully I had a phone that was virtually unbrickable. It was a good learning experience though, and I now feel comfortable rooting and flashing on several different devices.
Firefairy said:
Got the menu working, but now failing to install Superuser. I get the following output:
Mounting SYSTEM...
Deleting SYSTEM:bin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E:Error in /sdcard/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted.
Now what?
Click to expand...
Click to collapse
download from androidsu and either save it directly to the ROOT of your sdcard, or copy and paste to the root of your sd card. i always get that same error when i install superuser from a folder in my sd card.
My phone is rooted (With Super One Click) and when tap the "boot into recovery" option in Rom Manager it just send me to the stock recovery (with Blue text and what not). I have flashed Rom Manager with my Sidekick 4g before I tried to boot into recover. Please, someone help me. The answer is probably right in my face, but my noobish eyes just cant see it. :crying:
Please don't bash me this is my first post. I made sure there wasnt any post like this before i started a new tread.
Don't use ROM Manager with Sidekick 4G as CWM doesn't work the same way. When you reboot you always go into Samsung recovery from where you gotta reinstall packages to 'fake flash' the CWM recovery. If it says permission denied, the recovery file wasn't pushed to /system properly. You gotta reinstall every single time .. till of course you install a custom ROM. I think most come with voodoo CWM which replaces stock recovery, allowing you to go into CWM directly when you go to Recovery.
Firstly you need root, which I'm assuming you already have. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using other similar apps that give you R/W (read and write) access. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery.
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
Edit: Looks like the links on Krylon's page aren't working .. if someone can give an alternative it would be great!
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Those guided really helped me out I spent ages reading up different things so when I finally went and did it, I didn't face any problems!
Important notes:
1. Root, obviously I personally didn't use the latest edition of SuperOneClick (at the time) on the website, but the file the dev posted on his XDA Thread.
2. Don't use ROM Manager or any other 'one click' kind of recovery for this phone. You need to download a custom recovery file and update file (links above, thanks Krylon) and go into CWM Recovery through the official Samsung Recovery through reinstalling the custom update file. This is the only way to access Orange CWM. Most custom ROMs come with the Red Voodoo CWM which is permanent in the sense that when you go into recovery, you should go into CWM (Red), instead of having to go through Samsung.
3. Orange CWM (and some say Red CWM as well) has some mounting issues. Always remember to check your mounts such that System, Data (well just to be safe, all of the items in the list) always say UNMOUNT. Basically when its mounted, means CWM has access to the partition. It says UNMOUNT because it is MOUNTED. I know thats a bit confusing, but think of it like this - there is a light switch that says ON so when you press it, turns the lights on but then the writing changes to OFF because you need to push the switch to turn it off. Erm .. hope that helps?! Lol.
4. Basically if your partitions are showing up as MOUNT, means you need to MOUNT them. Otherwise whatever changes you did won't apply! Instead of getting confused like I did, just make sure the screen says UNMOUNT SYSTEM and so forth for the rest of the items on the list.
5. Before installing a custom ROM, I always wiped x 3, before and after. Means after checking mounts, wipe data / dalvik, etc. 3 times. So for me, after checking mounts I would go to wipe date - yes - done 1; wipe data - yes - done 2; wipe data - yes - done 3. Followed by wipe dalvik and whatever else you want to wipe. Then I'd check mounts again (they usually get unmounted after a wipe .. well for me they always have anyway) before installing the ROM. Oh, sometimes I installed the ROM twice. Then I'd check mounts, wipe x 3, check mounts again before finally rebooting and letting it stand still for around 20 minutes or so. I don't really know if there is a logic or if doing it so many times makes a difference but I know some other people have done this and (other than wasting time) it doesn't really do any harm (someone correct me if I'm wrong) so why the hell not? I think the basic reasoning behind double / triple wiping and installing is to make sure that the changes are properly written as sometimes the system still retains old data.
6. Some people have SD card partitioning issues apparent. I can't remember why everyone went around partitioning in the first place (it must have been for some important reason, completely slipped my mind right now .. I personally did it to link my apps / data to SD card and save internal memory / space) but I personally used Gparted to partition my card on a computer (rather than CWM on the phone as I've heard people have issues with this) and never had a problem.
But I think thats it. I know there is a lot of information but its really worth having a look at the guide and other posts on that thread as that and the ROM thread (I personally use GOV 3.2) really had me prepare for any possible issue beforehand so I started off in a position where I could avoid them.
WTF_IsA_Android said:
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
can someone update the sidekick 4g stuff everything is either dead or does not lead anywhere to download any of the required files, thanks.