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.
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!
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.
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Bumping in desperation here! Can anyone just paste in their build.prop? I'm on UVLJ1 (haven't had time to do the latest update due to root).
hmm... you should be able to go into download mode and flash the stock rom to recover the phone i think?
I think this is the answer. Flashing stock will give you what you need, it can be done through CWM (gee one's flashable zip for instance).
Wipe system/data through the format menu.
I wish I knew what a build.prop was.
installed it and rebooted my Samsung Relay and the screen went black. I pressed the power button and nothing happened.
The phone is now officially a paperweight. Also I had root privileges.
Can you help me please, I do not know what to do?:crying:
tacoman3148 said:
Hi everyone. Long-time reader, first time poster here.
Well, I've gotten myself in a bit of a jam. My Relay is rooted and has CWM 6.0.1.2 running the stock ROM per one of the awesome devs working on this phone. In a bout of zeal, I found a guide for installing Google Wallet on unsupported devices that involved editing the build.prop file to have the device identify itself as another. I dove in head first... My first mistake was not doing a CWM backup and my second mistake was that I backed up the build.prop file to the internal memory rather than the external SD card (seems pretty inaccessible there). After rebooting, the device black-screened after the Relay 4G splash and can only be brought back up by pulling the battery, though it still gets stuck at startup.
I had a look around and found these very similar threads, but they are for the S3:
http://forum.xda-developers.com/showthread.php?t=1895631
http://forum.xda-developers.com/showthread.php?t=1830191
I can also get into CWM and Odin mode, but Odin3 and adb don't see the device for some reason and CWM doesn't appear useful without a backup. From what I've gathered, the easiest way to recover from this is a flashable zip with the stock build.prop file.
Would anyone be able to make one of those or otherwise bail me out? Any help would be greatly appreciated!
Edit: If it helps any, I used ES File Explorer to do this, which apparently doesn't do permissions quite right. I'm not sure if it affects this, but I figured I'd throw it in here anyway.
Click to expand...
Click to collapse
I'm not very good at this also,but...Can you connect your phone to your computer and mount your phone from cwm and get the build.prop file that way?Or maybe do a factory reset?
I don't even have any idea how to search for this or even ask about it. I'll try!
Okay, so after having trouble with 4.2.2, I decided to flash an older rom. I had some problems with wifi logo turning white and not being able to connect to Google, so I searched for a new gapps to flash. I was having computer trouble, so I downloaded it onto my phone, it saved to the downloads folder. I also had noticed none of my other files were in there, which kinda freaked me out, but the same amount of space was being used on my internal memory (I don't have a SD card). Anyway, I went to go flash it with twrp and went to downloads and saw all my OLD files, which didn't include the new gapps download. So, I went to root explorer after rebooting and moved the gapps to my root folder, then restarted to recovery and it's not there. The only thing I can think of is when I'm in recovery, it just says sdcard, when I'm in the system, it says sdcard0.
Does anyone know what's going on and maybe something I can search for? This is weird. My files are clearly there and I just can't access them... even with full root access!
Sorry if this didn't make a lot of sense, I have no idea what's going on at all and I'm also kinda tired. Hope you can help!
------ I found the answer here: androidforums .... /verizon-galaxy-nexus-all-things-root/649940-4-2-sdcard-sdcard-0-observation.html
My tired brain finally kicked in and I searched sdcard0 and figured it out. Now, I guess I have to move stuff so I can use the old os. I'm only not deleting the post because it might helps someone. And I'm sure modifying links isn't allowed but I can't link with less than 10 posts and I wanna make sure people get the answer, so... yeah... Add com in the middle.