[Q] Bootlooping icbinb 2.3.7 - Samsung Galaxy S (4G Model)

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!

Related

[MOD][RECOVERY] Firerat's Custom MTD Partitions (resize Data,System and Cache)

If you dont understand what this Modification is doing, why it needs to be done, or what possible benefits come from it, then...
PLEASE DO NOT TRY THIS MOD.
***Even tho it is impossible to brick your phone when flashing this i still highly recommend you UNDERSTAND what you are attempting to do before you do it. If someone explains you are freeing up internal memory from other places not using it and you still have to ask what the benefit is, then you obvisouly dont fully understand the mod and your phone and should turn away now.***
Thank You.
Click to expand...
Click to collapse
Now onto the mod: Heres a quick description of what this mod is doing. Pretend your phone is a pizza cut into 3 even pieces. Each piece is memory for /cache, /system, /data. Your aneroxic sister "aka cache" doesnt eat a lot so most of her slice will always be left, your fat obese brother "/data" always eats his whole slice and is left wanting more. You are healthy "/system" and only eat what you need and never less never more.
What this mod is doing is taking that original pizza and RECUTTING the slices to better fit whos eating them, so since your aneroxic sister barely eats and your obese brother is always hungry it takes all the extra pizza "aka memory" from your sister and gives it to your brother. As for you "aka /system" you only eat exactly what you need "aka the size of the rom and files it install" so it resizes your own slice to exactly the number it needs to install the rom and its gapps/files and leaves you with just a little wiggle room.
That being said, i tried this on my buddies CDMA Hero that i rooted for him and it worked like a charm. he went from something around 170mb internal storage to around 350+mb internal storage while on CM6 - Froyo 2.2.
***One thing i noticed when using a hero CDMA is that adb is crucial. one of the steps after flashing the recovery file is to reboot back into recovery and i noticed it was impossible to do it the right way without plugging your phone in and using ADB***
Original Files and Instructions: Firerats Original G1/MT3G thread found here - http://forum.xda-developers.com/showthread.php?t=717874
After you read thru firerats original instructions just know that itll be slightly different on your hero!
1. Click on the link i posted above and download these files: FR-recovery-v1.5.3-CustomMTD_S.zip and FR-boot-v1.5.3-CustomMTD_S.zip
2. Put both those files onto your SDCard.
3. While in your SDCard, make a .txt file named "mtdpartmap.txt"
4. Open your new mtdpartmap.txt file and...
- If you are using CM6 then type
Code:
mtd 102 2
- If you are using a larger Sense Rom like Fresh or ZenHero then type
Code:
mtd 182 4
5. Once all 3 files are saved on the root of your SDCard, reboot your phone into recovery
6. Format/Wipe your system and cache.
7. Flash the file: FR-recovery-v1.5.3-CustomMTD_S.zip
8. Once the file is done flashing, itll prompt you to wipe cache, system, and dalvik again.
9. Once its wiped, plug ur phone in and pull up command to adb reboot recovery (if you try to reboot into recovery any other way itll mess up the partitions and ull get cache memory.log errors and that will mean the mod didnt work correctly) by using this
Code:
adb shell
reboot recovery
10. if you did step 9 correctly, then youll get back to your recovery menu and itll say "formatting cache..." at the bottom of your screen but your recovery menu is instantly able to be used and you dont have to wait. ***On the newest version i think it no longer says this and your just got to go***
11. Flash CM6 if you used 102 for /system or Flash your larger Sense Rom if you used 182 for /system
12. Optionally, flash any kernal you may be choosing to use
13. Flash the file: FR-boot-v1.5.3-CustomMTD_S.zip
14. Click the top option on your recovery menu to reboot your system.
15. Once your system is fully booted you can go into menu > settings > sd card and internal storage , and check all the new added internal memory you have.
FYI : anytime you flash a new rom after this mod, or flash a new kernal to a currently flashed rom, you will ONLY NEED TO FLASH THE SECONDARY FIRERAT BOOT file named "FR-boot-v1.5.3-CustomMTD_S.zip".
so say after this mod you want to try a new kernal, you flash the kernal, flash boot, and reboot the system.
or say you want to flash a new cm6 nightly update, you flash the new rom/update, flash boot, reboot.
or say u want a new nightly and a new kernal, you flash the nightly, flash the kernal, flash the boot, reboot.
its very simple, if anything u flash overwrites current kernal specifications, u need to flash the boot file to make sure it knows how to set itself up. this goes for nandroid back ups aswell.
Fine Tweaking/Trouble Shooting: To get the most space you possibly can do go into adb or terminal and type
Code:
df -h
and it'll tell you what % you are using on your system. if you are at 60% then you can go ahead and decrease your /system value in your mtdpartmap.txt to about 2mb over the value it says you are using. so if your rom uses 115mb of /system you can change your mtd to "mtd 117 2".
So if you are getting an error while trying to flash a rom after doing this modification you most likely dont have enough /system space and will want to up your value to something more then enough like "mtd 200 4" then run the above code and re-scale down back to 2mb over what the current rom is using.
Enjoy CDMA users!!!
Not sure if Ill try this personally, but thank you.
tailsthecat3 said:
Not sure if Ill try this personally, but thank you.
Click to expand...
Click to collapse
Trust me, well worth it. At first i thought it was amazing gains on the g1 and mytouch, but after being the first person in the world to try it on the Sprint Hero CDMA the benefits blow all passed expectations out of the water.
It nearly doubled my buddies internal memory.
i remember on his stock rom with a handful of his favorite apps he was at around 40mb internal memory. after i rooted his phone and flashed FRESH HERO onto his phone with apps2sd he had around 150, now with this mod-cm6-apps2sd hes got over 300.
my win7 drivers are goofy and sometimes won't do adb when its in recovery mode. if you screw up the restart part - ie: can't get into adb to reboot by typing the command and those messages appear - is the device bricked or anything? Is it a one-time? Recoverable? etc...
thank you for the info. i was down to bout 20 mbs free and now well over 100. kept running into problems until i changed the cache size to a little bigger. i had a spare hero to experiment with so alls good.
Skeptical...idk why. I don't wanna risk bricking yet another Hero I guess.
SammyM00782 said:
Skeptical...idk why. I don't wanna risk bricking yet another Hero I guess.
Click to expand...
Click to collapse
Can you please enlighten us as to how you bricked your Hero?
I've been thinking about trying this. I hate having 80+ mb free in system that I can't use. Would love to just add it to /data
This won't brick your hero. The only way you can brick it is by flashing the wrong bootloader or radio. This does none of these.
Hey has anyone tried this on a different rom..
oldjackbob said:
Can you please enlighten us as to how you bricked your Hero?
Click to expand...
Click to collapse
Well.....first time was an accident. First time rooting, first time messing with a phone. I just kinda jumped right into it because when I found XDA it was pretty exciting. I always support the small guy coming from small businesses my whole life. Anyway, second time was probably due to incorrectly flashing a rom or something but regardless, I went to reboot and the phone was totally unresponsive afterwards. I trust you guys though, especially the devs. So do you think it's worth a shot?
I just did it, running cm6, and it took away that extra 80mb in system, took away all that unused space in cache, and moved it all to data. I went from 20mb free (still using apps2sd mind you) to almost 200! and so far, no issues, market works fine, everything works. Just one little note: I took somethings out of /system/app before flashing both in the rom and the gapps, things I don't use, like calculator (prefer realcalc), voice search, maps, quicksearch(all updated and installed elsewhere), and I only have 3mb free in system, so you may want to see about the customizing given in firerat's thread to increase system to say 100mb (it's 90 by default)
im trying to do this mod but every time i flash the recovery all i get the htc logo and it stays there.. i am using cm6.. any help please
You don't flash a new recovery, this patches your current one. Flash the one labeled recovery like any rom.zip in the recovery, wipe everything, flash your rom or restore, then flash the boot zip as an update.
Sent from my HERO200 using XDA App
danaff37 said:
You don't flash a new recovery, this patches your current one. Flash the one labeled recovery like any rom.zip in the recovery, wipe everything, flash your rom or restore, then flash the boot zip as an update.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
i also was stuck on the white htc screen...
can you explan which file to us.
i couldnt get this to work with clockwork recovery, so changed my recovery first to darchs 1.7.0. you have to make the custom file first and put it on your sd card. i had to have at least 10mb of cache memory specified or i got stuck on the white htc screen.
have to read firerats thread for that.
danaff37 said:
I just did it, running cm6, and it took away that extra 80mb in system, took away all that unused space in cache, and moved it all to data. I went from 20mb free (still using apps2sd mind you) to almost 200! and so far, no issues, market works fine, everything works. Just one little note: I took somethings out of /system/app before flashing both in the rom and the gapps, things I don't use, like calculator (prefer realcalc), voice search, maps, quicksearch(all updated and installed elsewhere), and I only have 3mb free in system, so you may want to see about the customizing given in firerat's thread to increase system to say 100mb (it's 90 by default)
Click to expand...
Click to collapse
Hell yea, glad to see people flashing this mod correctly and enjoying the results!
if you end up customizing your partitions to diff sizes let all the guys know what values they should set and/or how to set them up themselves.
I dont get to use my buddies CDMA Hero a lot so i dont know how smoothly everything has been working over the past 2 days but i havent gotten any complaints or calls to fix bugs so i assume its all working very well with firerats default values but i dont know for sure.
so far ive seen these suggestions
1. up cache to 3mb
2. up system to 100mb
@danaff37, did you set your own values or are you using defaults still?
can you us this on cyanogenmod? its 2.2.... i have tryed every way and all it gets me is the white htc screen and never does on from there... please help
i checked before i flashed to see what all i was using. i had quick system info installed already so was easy for me to see. i was already using 130mb for system, prob because of dalvic-cache, so i upped it to 150mb for future use. default setting for cache was no go, changed it to 10 mb and all is fine.
I'm using default still, but downloading the latest nightly and noticed it's about 5mb bigger than before, so I'm going to go ahead and change it to 100mb when I flash it later (after I make my mods). Anybody using it should keep in mind that most rom files, the bulk of the space it takes up is in system, so be sure to partition accordingly (including gapps on aosp roms)
I left the cache at the default, try to go to /cache afterwards and it symlinks straight to /data/cache, so I don't understand how leaving it bigger would solve anything, but I've seen stranger things occur with these damn phones. lol

TNT keeps force closing on newest OTA update

Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Follow the instructions in the alternate gtab firmware post. It worked great for me. I would suggest installing cwm so you can back up your existing firmware.
My update would force close during download on the stock firmware. I finally got it to work by minimizing the pop up that displayed the progress. For some reason the screen would crash the download.
Your files should be there but you will lose all user settings and installed apps when you do the factory reset.
This is a common issue with stock, and TnT Lite. The user data seems to be very unstable once you upgrade to different firmware.
The "easiest" thing to do is just wipe the user data. However, if there is certain data you need to keep, I would recommend the excellent Titanium Backup. The only caveat is that the device has to be rooted, to use it.
roebeet said:
The only caveat is that the device has to be rooted, to use it.
Click to expand...
Click to collapse
And Z4root does this easily. Just install and click "root".
RyuFDAC01 said:
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Click to expand...
Click to collapse
Tntlite is that easy I was surprised. Too since rooting my HTC hero a year and a half ago was so much more hands on
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
I thank you guys VERY VERY MUCH appreciate this
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
Click to expand...
Click to collapse
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recovery\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recovery/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
Dude thank you so much for your effort in this !!!!! gonna try this as soon as i put my baby to sleep.... will let you know if this worked for me
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
roebeet said:
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
Click to expand...
Click to collapse
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
dcom222 said:
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
Click to expand...
Click to collapse
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
RyuFDAC01 said:
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
Click to expand...
Click to collapse
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
dcom222 said:
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
Click to expand...
Click to collapse
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
RyuFDAC01 said:
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
Click to expand...
Click to collapse
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
I just flashed the TnT 2.02 again. So far it seems OK, however it did the first 2 times I did it as well. I followed all of the instructions at "forum.androidcentral.com/showthread.php?p=442691#post442691" except I substituted using roeboot's TnT. Once I did it I had everything working (flash, market, etc...). Both times the boot loop happened when I tried to install or uninstall something, and both times were after a few hours of use. I tried a third time and almost instantly got into a boot loop, but I think I got ahead of myself in that try and did some things out of order. The good thing is that I was able to recover each time.
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
The EULA shows up with a new stock firmware - and yeah 4.1 / 4.2 kinda bugged me too. I never selected "I Agree" - fark that.
As for the boot loops, it seems that we still can't pin it down - maybe it's just random, I don't know.
Hi,
I was stuck after bootlooping using Cyanmod, then flashing NVflash still didnt fix the issue, this fix did it for me. Thanks for getting me back up & running. I will give another shot at using cyanmod now that I have all the files needed to get me back.
BTW< I have a green cloth. What does that mean?
Thanks,
Rich
dcom222 said:
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
Click to expand...
Click to collapse
My tab came with a grey cloth... funny thing though I got mine on the second wave of shipments to sears... I NEVER had any issues with the time i just set it and it kept the time... I remembered that when these first came out that was a problem... i thought mine was diff because i never had any issues with time reseting itself... anyway Thanks again dude for your help hope i could play this forward to someone more noobier than me
Roebeet looking forward to your TnT lites...
dcom222 said:
After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Click to expand...
Click to collapse
I now have clockwork recovery installed... How do i copy the update.zip from external microsd to internal microsd... mounting sd-ext gives an error..
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
Frustration levels are high with this device!!
Thanks!
a "me too" reboot problem
I was able to install TNT Lite 2.0, then 2.11. I got Clockwork Recovery installed as well.
The market would start, but if I did a search for obvious things like "Kindle", the market would give an error that it didn't exist in the market. Thinking it was the error situation described here:
http://forum.xda-developers.com/showthread.php?t=845175
I applied those instructions, and rebooted.
Upon reboot, it ended up in a continual reboot loop.
Trying to do the start with volume+power, it brings up Clockwork Recovery, and when told to wipe data/factory reset, it stays in the reboot loop. When told to apply sdcard's update.zip, it looks only at the one on the internal sdcard, which is for CWR, and goes back into the loop.
At that point I setup a microSD with the information from this post:
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
including changing the line from sdcard to sdcard2. Again it doesn't recognize that the internal sdcard2 is plugged in, and attempts to mount it with CWR (mount /sd-ext) yields the error:
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
So, unfortunately I'm at an impasse, like the previous poster. I just bought the tablet a couple of days ago, so I'm far from expert at tweaking it into working.
Any suggestions on what to do, are greatly appreciated.
PS - Bought the gtablet from Office Depot, and received a green cloth.
Boot into clockwork recovery and go to advanced and format SD, use the 2gb and 512mb I believe, then flash TNT or another rom. That fixed my boot loop.

[Q] Trying to Root: hboot 1.45.0013, Unlocked Bootloader, S-ON

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.

[ODIN+CWM] GB Ext4 Starter Pack (Nov 24) THANKS!

After struggling with this phone T959V for 3 days I finally got the ROM installed.
It seems as you read these forums you're not sure if what you're reading is accurate and how much of this still relevant to your issue.
I did everything on a 32-bit system as this seems to matter as I couldn't do this on my 64-bit Win7, but that was following the heimdall oneclick methods, but I could only go so far with that. I got all the way to the cannot mount SD Card...
Being that this is my 2nd phone to root, this is the harder of the lot (my other was HTC)
But enough about myself here's some tips if you're still having issues with this guide that helped me out which wasn't posted.
Do yourself a favor and just get a 2nd SDCard. Stop crying about the cost and just get one. I had 2 8GBs so I didn't care if anything happened.
I made sure I copied all the data over to the hard drive and then formatted the blank one and put the files back. So now if I blew this one up while in rooting mode, I didn't care, because I knew I had one sitting ready to go.
You may want to get the latest Samsung USB drivers as mine was 32-bit and after rebooting it was able to see the phone.
If you stick your phone in downloading mode, just leave it there and make sure odin can see your phone. If its not showing up then something else is wrong (usb, cable, port...etc) many times ODIN couldn't see my phone and I had to download reinstall drivers reboot etc...but my phone was still hanging in download mode, so dont sweat it...
I was able to follow the directions and was very happy I got to step 10.
You may want to get the QuickBoot.apk as this is better than going to CWM once you're in the phone.
But now enter the ROM and I get the blasted "Cannot mount sdcard".
And I cannot make a backup, which is an indication that something is not reading right.
I read through the forums and they talked about creating a partition. Since I didn't care about the SDCard info I just said create a partition thinking that it would create a separate partition on the card...nope..it will wipe everything from the card as if you formatted it. I chose the 1024 and 0 cache and away it went.
After a quick reboot, I was able to make a backup and finally load a ROM and install.
I didn't realize that it was such a big deal with the formatting, but again as they say follow all directions.
I didn't do the #12, but did hear the Linda and all is great!
I'm happy to report that my Samsung Galaxy S T959V is finally rooted and Valhalla Black Edition installed.
I figured I should contribute my headaches as someone might be going through them as well.
My follow up questions would be:
1. Do I need to flash the busybox_installer?
2. If I got a new and say larger SDCard like 32GB and just created a new partition, would it just reformat that to the phone's liking and then install a new ROM in that?
Thanks for this forum!
Andy
sqlandy said:
My follow up questions would be:
1. Do I need to flash the busybox_installer?
2. If I got a new and say larger SDCard like 32GB and just created a new partition, would it just reformat that to the phone's liking and then install a new ROM in that?
Thanks for this forum!
Andy
Click to expand...
Click to collapse
1. You don't really need the busybox installer, but it's recommended since there are a few apps and tweaks out there that need busybox. If I recall correctly, I threw in busybox into my edition of VB, but I'm not sure if Raver threw it into his.
2. Yeah you can format it directly from the phone but the repartitioning is necessary, it'll work just after a format.

[Q] Cant Install Rom? Me or File

Ive already flashed my phone acouple of times over the past couple years. But I tried downloading GloriousOverDose V5. At my current location the internet connection is horribly slow.
I have red voodoo so I know its not a mounting issue
Wipe Data
Wipe Cache
Install zip from SD, selecting file
starting unpacking
Installation Aborted: Bad
Im guessing the Download got messed up because of connection speed? Or am I just missing something here?
Thanks
there are issues with it but it shouldnt abort installation out right, i would assume a bad download and would check the md5sum
If you need im sure i or another can post a mirror, i like dev-host for the only limitation is speed but they never take down link and well theyre free!
but yeah GOV5 is a work in progress right now and you may need to flash ROM, then flash the package again, this time skipping ROM and doing the rest... not fun and it does appear to be a mount issue but im in the middle of too many projjects right now to finish fixing it... maybe the weekend...
no worries
No Worries Mate, Aint in no rush. Having some phone issues so i thought I would swap to something more updated. I'll just try something else for a couple days then come back and try again.
Thanks again
Found the Fault
i tried a new download and tada, didnt notice before but the download never "finished" the zip was still spereated into a zip.part file and never combined... *sigh* second download was a success, installed with no issues... But with the aroma installer i find myself wiping it every 10 minutes to look at all the options lol.
Is aroma only available on a fresh boot? or is there a backdoor to add/delete without reflashing the rom?
work in progress
Love the concept of this. Cant wait to see when up and running perfectly. Is there issues with aroma installer? I select the programs i want but none seem to make them to the phone? lol or is it me again?
Don't use the download from first post, use the one on the second or so page I posted.
There is an issue right now, first flash ROM and nothing else, then exit aroma but no need to reboot. After this choose flash zip again, say no to flashing ROM and here choose what you want to install. There is an issue with the mounts that is connected partly to how aroma works and partly to how the recovery for this phone works,
I'm working on this and may in the end have to build a whole new recovery.
Sent from my Nexus 7 using xda premium

Categories

Resources