Tablet wont wake up... - G Tablet General

Hi all,
I use NvFlash on my tablet, and everything seems to work. Run the batch, and the prompt says that it's a success.
Actually was able to get to the HOME screen, and a notification of updates. Clicked and downloaded okay. Now here's the problem, when the tablet shuts down, it wont come back to live again. I have to use NvFlash again to wake up the device.
Also, the "recovery" mode doesn't seem to work (Power + volume button)... So, I'm kinda stuck. While the tablet is not "bricked", I can't seem to find a way to update/flashed the ROM.
Help will be greatly appreciated.

Sounds like a bootloader issue. Have you ever partitioned your SD?

Mantara said:
Sounds like a bootloader issue. Have you ever partitioned your SD?
Click to expand...
Click to collapse
No, I don't think so. I'm new at this. Just followed the instruction here and didn't see a mention of partitioning before Nvflash...
Thanks for the quick reply...

Its just a theory. Some people have been having this issue lately and I'm wondering if the partition tables are different on the new tabs as opposed to the stock immage for nvflash recovery.
You will have to do a bit of reading but this has been solved.
Do a search in this forum and dig in. There has been a string of problems just like yours lately.
Good luck friend.

partitioned your SD CARD using your computer, than flash nvflash and just follow the rest of the steps had the same problem and this direction help me out
Sent from my PC36100 using XDA App

aalopez10 said:
partitioned your SD CARD using your computer, than flash nvflash and just follow the rest of the steps had the same problem and this direction help me out
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
After you do this i recommend that you flash clensyn's Kernel to help you wih the sleep problem version 6 is stable make sure that you read because there is a kernel for froyo and gingerbread.
i hope this helps

Hey all.
Thanks to everyone. I was getting frustrated, and decided to download the "46" version of the NvFlash instead and everything works now. I guess the version used on the tutorial doesn't like the tablet that I have. LOL.
Thank you again to everyone.
*consider this issue resolved*

Visual360,
The software used in the NVFlash thread is the correct software and has been proven
over time. I just helped a person yesterday fix a near brick which he said was caused
by loading the "46" version of bekit's files.
BTW, if you look at the innards of the "46" file you will find a .sh file (Linux shell batch file).
It isn't marked as Linux, but it is for use with Linux.
There have been a couple of discussions about what that file really was supposed to
be.
But the only Windows file I (and a lot of others) recommend is
nvflash_gtablet_2010110500.zip
In discussion that is called the bekit 1105 stock version a lot and when
you load it you come up with Stock Version 2638 -- which very
quickly get updated to 3588 by VS.
Hope this helps.
Rev
Rev

butchconner said:
Visual360,
The software used in the NVFlash thread is the correct software and has been proven
over time. I just helped a person yesterday fix a near brick which he said was caused
by loading the "46" version of bekit's files.
BTW, if you look at the innards of the "46" file you will find a .sh file (Linux shell batch file). It isn't marked as Linux, but it is for use with Linux.
There have been a couple of discussions about what that file really was supposed to
be.
But the only Windows file I (and a lot of others) recommend is
nvflash_gtablet_2010110500.zip
In discussion that is called the bekit 1105 stock version a lot and when
you load it you come up with Stock Version 2638 -- which very
quickly get updated to 3588 by VS.
Hope this helps.
Rev
Rev
Click to expand...
Click to collapse
Hi Rev,
Thanks for the comments. I know it's weird, but believe me I tried several times with the bekit 1105, and the device wont wake up after shutting it down, and the recovery button (Power + volume) is not even working.
I saw the file there (46), and didn't even downloaded it until I was just about to give up. I downloaded the file just out of frustration. I unzipped it, and copy all the files to the folder that I've created (NvFlash), and let it replace/delete whatever file that is there. I ran the batch files, and viola! The process worked, and I was able to update to 3588 or something. Clockwork recover button also works at that time.
Again, it's weird, and I'm not questioning anyone here, but it worked on my device and I'm happy running TnT right now. Everything is great for a device that cost me around $300. Everything that I care about work on this device including the market (with all my purchased apps available), Amazon apps works, so I was able to install from there too. I can even use my GPS mouse, and tether my phone to it. Heck, it took me longer to get my xoom tethered than the Gtab. LOL.
Thanks again to all.

Related

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] Step by Step?

Hey guys!
Noob here who has flashed other phones in the past, but never anything Android based. Is there a step by step guide anywhere for the Mesmerize? Something generic and simple to follow from post root to a fully flashed phone?
Thanks for any input.
Tyler
Well our moderator is nowhere to be seen.. we should have a step by step sticked.. but we don't.
1) Root your phone. Search the forums to figure out how to do that.
2) Install RomManager and the ClockworkMod Recovery. There's a thread for that as well.
3) Download and install the ROM of your choice. Roms are located in the Dev Forums.
The details can be found in the Mesmerize General and the Mesmerize Development Forums. Search is your friend.
tyler.raven said:
Hey guys!
Noob here who has flashed other phones in the past, but never anything Android based. Is there a step by step guide anywhere for the Mesmerize? Something generic and simple to follow from post root to a fully flashed phone?
Thanks for any input.
Tyler
Click to expand...
Click to collapse
When I began this process about 2 weeks ago, I was at the same experience level as you Tyler. This is what worked easiest for me for my US Cellular Mesmerize.
(I'm just going to elaborate a bit on what Dcow posted, hopefully he doesn't mind .
Also keep in mind there are many variations to each step, this is what worked for me the easiest as a newb, hoping it does for you too.
And last but not least. There is always the disclaimer that attempting any of this can and will make your phone dysfunctional and or possibly bricked beyond repair (but most likely just dysfunctional which is a pain in the arse to deal with) if you do not follow steps completely (and of a trustworthy source such as xda).
So take your time, read each step that these people have taken the time to carefully write up, and you'll be just fine. Be patient as things don't always move fast and you never want to freak out as you may screw things up bad, when it's actually just taking longer than you would expect. There is alot going on behind the scenes so just give it time, trust me!
1) Root your phone. - Basically all this means is gaining the ability to give programs/apps and yourself SuperUser access (equivalent of being admin in windows) and also the ability to flash roms via recovery, detailed below.
The easiest way to root is to acquire the z4root.apk.
Download Here
After download, put z4root.apk on your SD card root directory
Then make sure in Settings->Applications that the "Unknown sources" box is checked.
If you don't have a file manager, download a free one from the market, using the file manager navigate to the z4root.apk and select to install it.
Reboot your phone
After it boots, open the z4root app and press root. At this point it is going to hang, give it 2 minutes and pull the battery. Count to 10, put it back in and turn it on. - This is normal, trust me.
After it reboots open z4root again and run it, this time it will run no problems and phone will reboot.
Once you are rooted (you will see the superuser icon in your apps, it will show apps you've given that permission to eventually) you will need to make sure you have a file manager that can request root permissions (read/write) before you will be able to complete the next step. Search the market for "root file manager" and pick one to download and install.
Also at this step I would download and install RomManager and TerminalEmulator as you will need these later.
2) Install RomManager and the ClockworkMod Recovery. These will basically just give you the ability to boot into recovery where you can more easily flash kernel's/rom's and anything else you wish to push to your phone.
I was able to install the Clockwork Mod Recovery very easily just by simply using the root file manager app I downloaded with these instructions.
Download the two zip files located in the first post here
Place both files on your SD card root
Using the root file explorer app, move the Redbend_ua file from the SD card to /system/xbin/
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that.
Now open the TerminalEmulator
NOTE:The spaces below are actual spaces and the bml8 is a lowercase "L" not a "1" there is also a space after cd, after redbend_ua, after restore, and after recovery.bin
TYPE THIS ALL EXACTLY AS SHOWN BETWEEN THE QUOTES
at the command line ($) type "su" (then hit enter)
Type "cd /system/xbin" (then hit enter, which changes directory)
Type "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" (then hit enter, It will now scroll a bunch of text and reboot.)
After phone boots, open RomManager
Click on Flash ClockworkMod Recovery
Select the Samsung Fascinate your phone will still be the mesmerize
At this point you're all stock and ready for new kernel/rom.
3) Install Voodoo lagfix kernel and new 5.0 sound
If you want speed and good battery life (and high standard marks) +unlocking the headphone amp and eq controls (it makes even the samsung headset sound killer) go here and follow those steps for using your now functional recovery mode to flash the new Voodoo 5.0 kernel.
Note: There are a few ways of getting into this recovery mode, the best way if all else fails is to hold phone from the back with left hand (thumb on volume button, in the middle holding both down and pointer on power button) hold these down until the mesmerize logo pops up then slide your thumb down a bit to volume down only (if you slip don't worry it might blink but it'll still go to recovery)
Note: If you are more code/computer oriented there is a method using a program called ADB, which I'm not familiar with and seemed more complicated than what I went with. Search for that on the forum if you wish to do the above process that way instead.
4) Download and install the ROM of your choice.
Just pick one from this list Here, read through the first post of each before you decide, some are plug and play some take a few steps first.
Credit goes to all of the OP's and many others included in my sig, these people are awesome show them some love!
Thanks for the nice stepbystep. I wonder if pming the mod would help get it stickied? He still hasn't replied to my last pm though..
dcow90 said:
Thanks for the nice stepbystep. I wonder if pming the mod would help get it stickied? He still hasn't replied to my last pm though..
Click to expand...
Click to collapse
Agreed this should be a sticky! Thanks for the AWESOME write up bdemartino!
dcow90 said:
Thanks for the nice stepbystep. I wonder if pming the mod would help get it stickied? He still hasn't replied to my last pm though..
Click to expand...
Click to collapse
Did you PM me? I don't recall ever getting one from you. If I did, I apologise! I always try to be proactive in my forums
I check in on all my forums many times per day (even at work ) so if I miss something, please feel free to PM me anytime and I'll try to help where I can
I'll get in touch with bdemartino regarding getting a guide together that I can sticky
In the meantime Ill move this to general.
I few days ago I found an explanation here on how to do this:
http://www.howardforums.com/showthread.php/1694111-Installing-Clockwork-and-Voodoo-onto-the-Samsung-Mesmerize
(The same explanation bdemartino gave here today)
1. I used the files from there. How do I tell if I am running voodoo5?
2. If its not the same, I've read that I can install voodoo5 over another voodoo, correct?
3. Is anyone having trouble with 3g, vibrate, etc...on the mez? I saw in the voodoo5 thread that a few people were having trouble with these things. I couldn't tell if they were fascinate, mesmerize or captivate.
Sent from my voodooized Mesmerize using XDA App
gr4ybu5h said:
I few days ago I found an explanation here on how to do this:
http://www.howardforums.com/showthr...ockwork-and-Voodoo-onto-the-Samsung-Mesmerize
(The same explanation bdemartino gave here today)
1. I used the files from there. How do I tell if I am running voodoo5?
2. If its not the same, I've read that I can install voodoo5 over another voodoo, correct?
3. Is anyone having trouble with 3g, vibrate, etc...on the mez? I saw in the voodoo5 thread that a few people were having trouble with these things. I couldn't tell if they were fascinate, mesmerize or captivate.
Sent from my voodooized Mesmerize using XDA App
Click to expand...
Click to collapse
That is the old Voodoo kernel, you will need to go to the link I listed in my post for Voodoo 5, and yes you can simply disable lagfix and flash the new one over the old.
And no problems on the write up, I spent a good amount of time digging up the links and stuff but I'll spend a little more time polishing it and will post it in another thread for Scotsman to stickie.
And to answer your last question, no I'm having no problems with any functions of my phone after upgrading to voodoo 5.
Thanks for the write up and nice job on it too. It seems, sometimes when people try and tell others how to do something, they don't break it down enough. But you did and made it easy for us noobs. Thanks again.
My clockwork ( or voodoo, not sure) didn't come with a "disable lag-fix" button. I just have to create an empty file called "disable_lagfix". I'm just unclear where to put it. I saw it somewhere before I just have to find it
Sent from my SCH-I500 using XDA App
gr4ybu5h said:
Thanks for the write up and nice job on it too. It seems, sometimes when people try and tell others how to do something, they don't break it down enough. But you did and made it easy for us noobs. Thanks again.
My clockwork ( or voodoo, not sure) didn't come with a "disable lag-fix" button. I just have to create an empty file called "disable_lagfix". I'm just unclear where to put it. I saw it somewhere before I just have to find it
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
There isn't a button, per se. When you go in to recovery, there is a disable lagfix option under voodoo. You can put the file, disable_lagfix, in the voodoo folder on your sdcard to do the same thing.
He does write up a good how-to, though, doesn't he.
Haha thanks guys, and you're welcome!
I think the reason you don't usually see this much detail from others is because they are more developmentally enabled and therefore "forget" to break down the little steps that are second nature to them but foreign language to a non-developer.
Thanks. I found it. and disabled it aready. now i just download the file in the write-up and boot into recovery, install zip from sd card and select my file correct?
I always wipe dalvik cache (in advance settings within Recover) before flashing anything.
So it's;
Disable Lagfix
Reboot (you'll hear the chick reversing the process)
Clear Dalvik
Install voodoo 5.0 from zip
reboot
re-enable lagfix and reboot one last time.
Then you'll need to download the voodoo controller app from the market to control the amp gain and set a few other eq settings.
Man you guys are fast. Thanks for the quick replies. WOW
Ive done all that except re-enable lag-fix. Noone ever mentions that step. Do I just remove the "disable_lagfix" file from the voodoo file and reboot?
I just enable/disable it through the voodoo menu in recovery, much easier than pushing files around. In your case i think you should be able to delete the file and reboot, but if not you may just need to go into voodoo and enable it that way (after removing the disable file)
I guess if I edit a post and dont finish it, the post gets deleted. Oh well, I asked how to reenalbe lag fix but i figured it out. Like I said I had to put the disable lag_fix file in the voodoo folder. I just had to remove it from that folder.
Is there a way to tell (besides the quickness and the extended battery life) how do i tell if its voodoo5? just out of curiousity
Just a guess here but possibly under About Phone the kernel version might? Mine is listed as 2.6.29
I would also think that when trying to use the Voodoo app it would fail if you didn't have the kernel so that would be a sign too, if that's what you're looking for.
Well thanks alot. Thats what mine was listed as also. And the voodoo app did work, so I guess I've got it. And I think thats all for now.
Now I think I might wait to see the awesome developers come up with for 2.2. I dont mind the stock 2.1 for now. I just dont want to keep flashing ROM's, if they might be close to getting a version of 2.2 going. I can wait....I think.
Thanks Again
gr4ybu5h said:
Well thanks alot. Thats what mine was listed as also. And the voodoo app did work, so I guess I've got it. And I think thats all for now.
Now I think I might wait to see the awesome developers come up with for 2.2. I dont mind the stock 2.1 for now. I just dont want to keep flashing ROM's, if they might be close to getting a version of 2.2 going. I can wait....I think.
Thanks Again
Click to expand...
Click to collapse
2.2 is so close, you should be able to smell it. I've had it's froyo-ey goodness all over my phone and even with the issues we're still having, I flash it back every night when I get home to play with it.
phidelt82 said:
I've had it's froyo-ey goodness all over my phone
Click to expand...
Click to collapse
That's what she said....

Viewsonic GTab Unbrick and Update package

Hey guys. Since this is the place I found every ounce of help that I needed to effectively unbrick and install the best Android version I have seen to date, I thought I would share my results as well as pass forward the work I did to help save some other poor guy a little bit of time. What I have here is a .zip containing NVFlash with a modified batch script to flash ClockworkMod into the GTablet. You just need to install the correct drivers on your PC, and when you boot you tablet, hold down the - (minus) key along with the power button. Not the + (plus) key, but yes the minus key. This will put it into a seperate boot mode that you can then use to run the NVFlash.bat batch script. I have the script set to install "image9" which is actually CWM, just renamed per the script. This will install CWM into a currently bricked, frozen, melted or melting Gtab. Once you get to this point, you probably know how to boot into the CWM recovery kernel (Power and +). Next you will find the boot images for both VEGan Ginger and Gtab Honeycomb next to the NVFlash stuff. First install VEGan, then lather, rinse repeat with Honeycomb. Make sure you follow the other instructions found in this site for completing this process, just like I did. Even I had this process fail over and over again until it finally worked, so if you start boot looping just do it all again. it makes no sense, but it eventually works. Just keep repeating and looking over the other forums here and IT WILL WORK. The trick here is, just get CWM installed. Once you are there, you're golden. Make sure that you rename the .zip files containing the images and all that in them as update.zip before you move them to your tablet, and then remove the old one out before you stick the next one in. If anyone has any questions, just message me. I am happy to help
UPDATE: I wasn't able to upload the main zip file to this site, but probably because it's almost half a gig. So I sent it to MegaUpload, so you can pull it from there.
UPDATE UPDATE: Apparently since this is my first thread posting, I can't post outside links.. LOL. Ok, so I guess if you message me, I can send you the download link. Well hey, at least I tried. Thanks again to everyone that posted the information that I needed. Hopefully I can be of help to someone else.
I did attach the windows drivers that you will need however, so please feel free to grab those below.
jamtab said:
Hey guys. Since this is the place I found every ounce of help that I needed to effectively unbrick and install the best Android version I have seen to date, I thought I would share my results as well as pass forward the work I did to help save some other poor guy a little bit of time. What I have here is a .zip containing NVFlash with a modified batch script to flash ClockworkMod into the GTablet. You just need to install the correct drivers on your PC, and when you boot you tablet, hold down the - (minus) key along with the power button. Not the + (plus) key, but yes the minus key. This will put it into a seperate boot mode that you can then use to run the NVFlash.bat batch script. I have the script set to install "image9" which is actually CWM, just renamed per the script. This will install CWM into a currently bricked, frozen, melted or melting Gtab. Once you get to this point, you probably know how to boot into the CWM recovery kernel (Power and +). Next you will find the boot images for both VEGan Ginger and Gtab Honeycomb next to the NVFlash stuff. First install VEGan, then lather, rinse repeat with Honeycomb. Make sure you follow the other instructions found in this site for completing this process, just like I did. Even I had this process fail over and over again until it finally worked, so if you start boot looping just do it all again. it makes no sense, but it eventually works. Just keep repeating and looking over the other forums here and IT WILL WORK. The trick here is, just get CWM installed. Once you are there, you're golden. Make sure that you rename the .zip files containing the images and all that in them as update.zip before you move them to your tablet, and then remove the old one out before you stick the next one in. If anyone has any questions, just message me. I am happy to help
UPDATE: I wasn't able to upload the main zip file to this site, but probably because it's almost half a gig. So I sent it to MegaUpload, so you can pull it from there.
UPDATE UPDATE: Apparently since this is my first thread posting, I can't post outside links.. LOL. Ok, so I guess if you message me, I can send you the download link. Well hey, at least I tried. Thanks again to everyone that posted the information that I needed. Hopefully I can be of help to someone else.
I did attach the windows drivers that you will need however, so please feel free to grab those below.
Click to expand...
Click to collapse
Jamtab,
I am in the same situation you described regarding your GTab! Could you email me a way to download the unbrick and update package? I have wrestled with this over the weekend and after trying 1000 different forum posts suggestions, your experience is identical to my problem and as such, your solution would most likely work for me...
Thanks, Mike
Dr. Michael L. McCrimmon
[email protected]

[Q] At the end of my rope.

Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
TwistedPoet said:
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
Click to expand...
Click to collapse
Ok, Can you boot to Odin mode (dowload mode)?
TwistedPoet said:
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
Click to expand...
Click to collapse
I doubt you'll bore us here, after all we dwell in the minutiae and tiniest of details for fun. Hmm, from what I see you have a bootloader hard brick since you tried using EZ Unlock. TW 4.3 prevents downgrading the rom to pre-4.3, flashing an unlocked bootloader, and installing a custom recovery using 4.1.2 methods. Your best option will be to try the steps detailed in this bootloader/hardbrick thread by SpyroDazee.
buhohitr said:
Ok, Can you boot to Odin mode (dowload mode)?
Click to expand...
Click to collapse
No. Once I used EZ Unlock, I was bricked.
SlimSnoopOS said:
I doubt you'll bore us here, after all we dwell in the minutiae and tiniest of details for fun. Hmm, from what I see you have a bootloader hard brick since you tried using EZ Unlock. TW 4.3 prevents downgrading the rom to pre-4.3, flashing an unlocked bootloader, and installing a custom recovery using 4.1.2 methods. Your best option will be to try the steps detailed in this bootloader/hardbrick thread by SpyroDazee.
Click to expand...
Click to collapse
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img. http://angelfirenetworks.servegame.com/XDA/S3 Debrick IMG_s/
And then I can seem to make that run either.
I also have bricked S3 different circumstances but still hard bricked. Nothing I've tried here on xda or anywhere else has worked. I'm going to try this http://www.ebay.com/itm/281217379767?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649 . It is probably the cheapest and easiest way.
TwistedPoet said:
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img. http://angelfirenetworks.servegame.com/XDA/S3 Debrick IMG_s/
And then I can seem to make that run either.
Click to expand...
Click to collapse
It usually takes a few tries to get it to work, but if you really can't then you can always send it in for a jtag repair.
Mobile tech videos will do it, and there's someone on eBay who will do it for $30. Not too expensive.
Sent from my SCH-I535 using Tapatalk 2
TwistedPoet said:
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img.
And then I can seem to make that run either.
Click to expand...
Click to collapse
So I just downloaded the debrick.zip and Win32 program from my link onto my laptop. I saved the unzipped debrick folder onto my desktop and found the debrick.bin once I switched the "Files of type" to "." then I just wrote the debrick.bin to a 512 mb sdcard with no problems. I'm not going any further cuz I have no need for this though. Are you saying that Win32 doesn't find the bin file at all?
Edit: I just ran it again and it worked a second time. My backup laptop is a 2006ish (maybe older) with a very outdated version of Windows and my sdcard has been unused since 2008. I don't know what else to tell you but it worked surprisingly well for me.
SlimSnoopOS said:
So I just downloaded the debrick.zip and Win32 program from my link onto my laptop. I saved the unzipped debrick folder onto my desktop and found the debrick.bin once I switched the "Files of type" to "." then I just wrote the debrick.bin to a 512 mb sdcard with no problems. I'm not going any further cuz I have no need for this though. Are you saying that Win32 doesn't find the bin file at all?
Edit: I just ran it again and it worked a second time. My backup laptop is a 2006ish (maybe older) with a very outdated version of Windows and my sdcard has been unused since 2008. I don't know what else to tell you but it worked surprisingly well for me.
Click to expand...
Click to collapse
The Win32 program finds the debrick.bin file when I switch to "." as well. But when I click WRITE, I get an error message and the file doesnt't write to the sd card. I'm using a HP Windows 7 Pro (2009) and I have a 32gb, class 10 sd card. I will run it again to double check.
Follow Up: I figured out what I was doing wrong. I was attempting to pull the "bin" file through Win32 and should have been pulling the "zip" file instead. I was able to write the debrick.zip file onto my SD card but wasn't (on first attempt) able to load my phone. Are there any other steps I may have misunderstood or overlooked?
TwistedPoet said:
The Win32 program finds the debrick.bin file when I switch to "." as well. But when I click WRITE, I get an error message and the file doesnt't write to the sd card. I'm using a HP Windows 7 Pro (2009) and I have a 32gb, class 10 sd card. I will run it again to double check.
Click to expand...
Click to collapse
Have you tried formatting the sdcard and running the program again? Set it to Fat32. I'm thinking it may be the sdcard and not the program itself but I'm not certain.
SlimSnoopOS said:
Have you tried formatting the sdcard and running the program again? Set it to Fat32. I'm thinking it may be the sdcard and not the program itself but I'm not certain.
Click to expand...
Click to collapse
VICTORY!!!!!!! - I made several mistakes in getting to this point but i have successfully retrieved my phone from it's previous HardBrick status. The steps it took me to get to this point were, make sure the sd card is formatted (FAT32) and empty, unzip the debrick.zip file, run the Win32 program, select the unzipped debrick.bin file and upload it to the F drive, then click Write. So, more or less, exactly what the instructions told me to do. Sometimes, it's the simple things that we're most often missing or not understanding.
THANK YOU to everyone and especially SlimSnoopOS for talking me through it and SpyroDazee for making such a comprehensive guide to work with. (although, it's simplicity was too complex for me. ).
TwistedPoet said:
VICTORY!!!!!!! - I made several mistakes in getting to this point but i have successfully retrieved my phone from it's previous HardBrick status. The steps it took me to get to this point were, make sure the sd card is formatted (FAT32) and empty, unzip the debrick.zip file, run the Win32 program, select the unzipped debrick.bin file and upload it to the F drive, then click Write. So, more or less, exactly what the instructions told me to do. Sometimes, it's the simple things that we're most often missing or not understanding.
THANK YOU to everyone and especially SlimSnoopOS for talking me through it and SpyroDazee for making such a comprehensive guide to work with. (although, it's simplicity was too complex for me. ).
Click to expand...
Click to collapse
Haha I love the enthusiasm my friend! Great way to start the weekend! All it took was another perspective, it's all good. You are most definitely welcome.
Edit: and while I'm here, if you have any inquiries about TW 4.3 or want to read up on some info then here's our TW 4.3 discussion thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Haha I love the enthusiasm my friend! Great way to start the weekend! All it took was another perspective, it's all good. You are most definitely welcome.
Edit: and while I'm here, if you have any inquiries about TW 4.3 or want to read up on some info then here's our TW 4.3 discussion thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I'm not turning away knowledge. I'm still very new to this and obviously have a hard time following directions. I was looking at the next steps on that guide and am all ready confused enough to not do anything yet.
What is your phone doing after you inserted your sdcard and what size card and class were they. If you got it to go into download mode or some call it Odin mode by pressing volume down, home button and power button then your off to a great start to bringing your phone back from the dead. If only it worked for mine
Where did you get the debrick.zip file? Every time I download the file it comes as debrick.img not a .zip
Always_Jonezen said:
What is your phone doing after you inserted your sdcard and what size card and class were they. If you got it to go into download mode or some call it Odin mode by pressing volume down, home button and power button then your off to a great start to bringing your phone back from the dead. If only it worked for mine
Where did you get the debrick.zip file? Every time I download the file it comes as debrick.img not a .zip
Click to expand...
Click to collapse
Edit: My SD Card is a 32gb class 10. Once I got Win32 to extract the file properly, I put the SD card back into the phone, put the battery in, and plugged phone into computer. Pushed the power button and the phone came back on.
When you go to download that file with Win32, change the file type to "." - then you'll be able to select the debrick.zip
All files were obtained here - http://forum.xda-developers.com/showthread.php?t=2581166
I hope that helps.
TwistedPoet;49543890. Edit: My SD Card is a 32gb class 10. Once I got Win32 to extract the file properly said:
http://forum.xda-developers.com/showthread.php?t=2581166[/url]
I hope that helps.
Click to expand...
Click to collapse
Thanks I hope it works too. Am I supposed to change the file type of the debrick.img to debrick. and or change the file type in win32
Always_Jonezen said:
Thanks I hope it works too. Am I supposed to change the file type of the debrick.img to debrick. and or change the file type in win32
Click to expand...
Click to collapse
They did exactly what I posted, which was: unzip the debrick.zip, open Win32 and change the file type to ".", find the unzipped debrick folder and select the debrick.bin, and write to the sdcard.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
They did exactly what I posted, which was: unzip the debrick.zip, open Win32 and change the file type to ".", find the unzipped debrick folder and select the debrick.bin, and write to the sdcard.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
As stated earlier when I download the debrick file it downloads as debrick.img not a zip file am I missing something
Always_Jonezen said:
As stated earlier when I download the debrick file it downloads as debrick.img not a zip file am I missing something
Click to expand...
Click to collapse
Did you brick BEFORE 4.3? I hovered over this link in SpyroDazee's post: "Debrick if you bricked before 4.3 OTA" and that's the only one that would download as an IMG. Press "Debrick if you took the 4.3 OTA" and it will download as a zip.
Or change the browser that you're using. I downloaded it using Chrome on my MBP.
Sent from my SCH-I535 using Tapatalk 4
I did brick on 4.1.2 and I am using chrome as my default browser

[Q] All links down, need T839UVKJ2 SK4G stock rom

so after looking for 3-4 hours i'm convinced that almost all the links for files related to the SK4G are expired/down/DL limit reached. i had to wipe my HDD and can't find my backup anywhere!?!? if anyone has the stock firmwares (any and all) could you pretty pretty please send them to me? i'm stuck in a buggy version of glorious overdose and just need my phone to work right again. respond for e-mail or just post ***NEW*** link in this thread.
P.S. so when the mods say "wrong thread" or "duplicate" i looked i searched and found nothing newer than 2013 so i started a fresh one......... that and i just signed up and it keep telling me "NO" in what seemed like the correct forum.
P.S.S i'm assuming there's legal reasons but whats up with a file repository on or at least paired with XDA to hold all the files posted here. shooting in the dark but maybe Kimdotcom will provide a mega account to serve as a repo?!?!?!?
I have the One-Click KG2 ODIN Java app that may be able to restore your SK to t839-Sidekick4G-UVKG2. Here's the README:
If you brick your phone, well you're lucky because it can't get any easier to fix. This is pretty much a one-click version of ODIN that is OPERABLE AND EXECUTABLE on ANY operating system that has Java installed. Self-explanatory, but if you don't have Java installed yet, you probably should go get it installed now.
(Credits go to Ayoteddy for the following post) :
To get into download mode (if you can't) pull the battery out of your phone, the USB cord (if connected), the SIM card, and the SDCard. Now...in a position where your one hand is able to access the Trackball and - volume key, hold them both at the same time and with your other free hand, insert the battery, after a second or two, you should see an Android on screen with a logo saying DOWNLOADING..you're ready to advance.
After you install Java, double-click the .jar file in this folder.
Hit "flash" and if all is well, it'll work without any hassles and you'll be back to the stock ROM like the day you got your Sidekick (factory reset).
If it says driver was not found, a window will popup with an administrative prompt if you are running Windows 7, allow it to run.
On the new Zadig window, go to Options>List all devices.
You should now see SAMSUNG COMPOSITE DRIVER, make sure the box to the immediate right says WinUSB and then hit the install button.
You should be on stock after performing these steps...if not and YOUR MODEM fails to upload, check "Flash Bootloaders" and the modem should flash just fine and you'll be back on stock ROM soon enough.
Thanks to AdamOutler for Heimdall!
His thread is here if you want to thank him properly!
http://forum.xda-developers.com/showthread.php?t=1350060
I also have Odin3+v1.61 with sk4g pit. Let me know if you want me to upload these.
marathonjon said:
I have the One-Click KG2 ODIN Java app that may be able to restore your SK to t839-Sidekick4G-UVKG2. Here's the README:
I also have Odin3+v1.61 with sk4g pit. Let me know if you want me to upload these.
Click to expand...
Click to collapse
Please re-upload these to sammobile.com, samsung-firmware.org, MEGA, Android File Host, or similar where the files can live on longer.
Sorry, I got rid of my SK a couple years ago and all the files that went with it.
marathonjon said:
Sorry, I got rid of my SK a couple years ago and all the files that went with it.
Click to expand...
Click to collapse
Is there anyone out there that still has this? Please re-upload.

Categories

Resources