I appear to have a major problem with my Droid X. I was rooted, with Bootstrap installed, CW Recovery, Rom Manager - the whole nine yards. I tried to install DX2313 - Deoxed (the leaked Froyo update), using the procedure set out at this site: DROID X New Froyo Leak V23.13 | WJD Designs but I think what may be the basis of my problem was that I didn't go into recovery through bootstrap. What happened was that periodically when I power up the Droid X, it seems to go directly to CW Recovery, after the "M" startup logo. I just choose reboot and it then reboots and takes me to the desktop. This time, since I was already in CW Recovery, I just went ahead and started the process shown on that page. Which was essentially wiping cache, choosing the zip file and installing. The page says the initial installation may take longer than five minutes. I waited 15 minutes - stuck at the "M", then pulled the battery and waited a minute and put it back in. Stuck again at the "M". Waited another 5-10 minutes, pulled the battery, waited 5 minutes, put it back in and now it won't do *anything* - no "M", nothing at all.
First question: Am I totally screwed? Is there a way to recover from this. I have a nandroid backup, if I could find a way to boot to recovery.
Second question: Was the fact that I didn't access CW Recovery through bootstrap the fatal error on my part that started this whole mess? If I can recover, should I try again, the CORRECT way?
Thanks much!
-Mike
Follow-up: Just pulled the battery and put it back in, and NOW I do have the Motorola "M" logo, but it stops there - nothing beyond that.
You need to flash back to 2.1. Go to
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
reflash back to stock. Once you flash back to stock on first boot I would clear data and cache and then re-root. Then do this:
once you re-root install superuser, update superuser (Options, bottom of page).
once it updates install Bootstrap recovery, apply. Install Rom Manager, flash clockwork from inside Rom Manager.
From there I installed this 2.2 release (This backup has been more stable and better battery life with no issues compared to other releases Ive tried.)
http://alldroid.org/default.aspx?g=posts&t=806
After that I installed the new 23.13 release by P3Droid.
I will say that after a couple days of using it, I went back to my backup I made BEFORE I installed 23.13. It was just more stable on my phone. Remember, everyones phone will probably act a bit different so if these steps above don't work for you, as long as you can get in to flash back to 2.1 you will be fine, and if you are getting a M logo, then you have the ability to flash back.
Hope this helps a little at least.
Thanks for the quick response! This may sound dumb, but with my phone just sitting there on the "M" logo, how do I do anything? Is there a way to boot into recovery? I do have a backup, but right now, I can't really turn the thing on, even.
-Mike
Ultra Droid said:
Thanks for the quick response! This may sound dumb, but with my phone just sitting there on the "M" logo, how do I do anything? Is there a way to boot into recovery? I do have a backup, but right now, I can't really turn the thing on, even.
-Mike
Click to expand...
Click to collapse
Hi Mike,
Yes if you are hitting the M logo then you can hit the (I think its called the "bootstrap") to flash BACK to 2.1. You have to hold down the volume rocker, and the Camera button while turning on the phone then hold them for 10 seconds. Once you let go there will be a black screen, with white text letting you know its ready to flash.
Connect via USB and then flash the 2.1 SBF file back (DO NOT TRY THIS WITH BACKUPS OR ROMS, ONLY legit 2.1 SBF).
All the instructions are on the first link I posted (rootzwiki)
How is your GPS? Is it accurate or off just a little when it shouldn't be?
Koroz said:
Hi Mike,
Yes if you are hitting the M logo then you can hit the (I think its called the "bootstrap") to flash BACK to 2.1. You have to hold down the volume rocker, and the Camera button while turning on the phone then hold them for 10 seconds. Once you let go there will be a black screen, with white text letting you know its ready to flash.
Connect via USB and then flash the 2.1 SBF file back (DO NOT TRY THIS WITH BACKUPS OR ROMS, ONLY legit 2.1 SBF).
All the instructions are on the first link I posted (rootzwiki)
Click to expand...
Click to collapse
Not to pester you further, but OK, I've downloaded (to my PC)the SBF file from the link you provided. Did the bit about holding down the volume button, the camera button and hitting power. Got the black screen with white lettering, like you said, hooked the to the PC with USB, and at this point you say to flash the 2.1 SBF file. How? I mean, what means do I use to actually *do* this flash? Also, the SBF file is sitting on my PC, and while I'm physically connected to the PC via USB, I'm not seeing anything on the PC that indicates there's a connection.
Sorry to sound so dumb...
-Mike
Ultra Droid said:
Not to pester you further, but OK, I've downloaded (to my PC)the SBF file from the link you provided. Did the bit about holding down the volume button, the camera button and hitting power. Got the black screen with white lettering, like you said, hooked the to the PC with USB, and at this point you say to flash the 2.1 SBF file. How? I mean, what means do I use to actually *do* this flash? Also, the SBF file is sitting on my PC, and while I'm physically connected to the PC via USB, I'm not seeing anything on the PC that indicates there's a connection.
Sorry to sound so dumb...
-Mike
Click to expand...
Click to collapse
You need to download and install RSD Lite (download link can be found on the link posted above.)
Once you have installed RSD Lite you need to unzip the .sbf file to the desktop. Open up RSD and click on the (...) located on the top right of the screen. Find the sbf file and click start after you see a device connected on the bottom portion of the program. Then just sit back and wait.
Ultra Droid said:
Not to pester you further, but OK, I've downloaded (to my PC)the SBF file from the link you provided. Did the bit about holding down the volume button, the camera button and hitting power. Got the black screen with white lettering, like you said, hooked the to the PC with USB, and at this point you say to flash the 2.1 SBF file. How? I mean, what means do I use to actually *do* this flash? Also, the SBF file is sitting on my PC, and while I'm physically connected to the PC via USB, I'm not seeing anything on the PC that indicates there's a connection.
Sorry to sound so dumb...
-Mike
Click to expand...
Click to collapse
You aren't, my X was my first android phone and my first attempt at roms and flashing so I know what you are going through, I am out and about though so my responses might be a little slow.
If you follow the directions on the page they will lead you through it step by step including what files you need. mmaibl2011 has it right though, you need RSD Lite.
If you have any other questions hit up the thread and ill check it when I can. Remember what makes android great isn't the software its the community behind it. As long as we keep that community alive by helping each other only good things can happen =)
mmaibl2011 said:
You need to download and install RSD Lite (download link can be found on the link posted above.)
Once you have installed RSD Lite you need to unzip the .sbf file to the desktop. Open up RSD and click on the (...) located on the top right of the screen. Find the sbf file and click start after you see a device connected on the bottom portion of the program. Then just sit back and wait.
Click to expand...
Click to collapse
I've now got RSD Lite set up, however it doesn't "see" the sbf file. That brings up another point. The download for the sbf file produced a non-zipped, 11.1 k file of some sort, currently sitting on my desktop. No matter what I do, RSD Lite won't interact with that file. It seems excessively tiny to be an actual file, but I've tried several additional downloads from the same link, and they all turn out the same - an 11.1 K, non-zipped file. I tried doing an online search for "sbf_flash" but haven't found an alternative download site for that file.
Is there an Alternate Plan B that I can turn to?
-Mike
Ultra Droid said:
I've now got RSD Lite set up, however it doesn't "see" the sbf file. That brings up another point. The download for the sbf file produced a non-zipped, 11.1 k file of some sort, currently sitting on my desktop. No matter what I do, RSD Lite won't interact with that file. It seems excessively tiny to be an actual file, but I've tried several additional downloads from the same link, and they all turn out the same - an 11.1 K, non-zipped file. I tried doing an online search for "sbf_flash" but haven't found an alternative download site for that file.
Is there an Alternate Plan B that I can turn to?
-Mike
Click to expand...
Click to collapse
The SBF file should be over 400 megs in size here is my directory listing for the file (I run linux so it will look different then windows obv)
[email protected] /mnt/backups/Backups/Android Stuff/Roms and backups/stock-2.1 $ ls -alh
total 440M
drwxrwxrwx 1 root root 0 2010-09-10 13:37 .
drwxrwxrwx 1 root root 4.0K 2010-09-14 19:41 ..
-rwxrwxrwx 2 root root 440M 2010-08-06 04:39 VRZ_MB810_1.13.6.2_1FF_01.sbf
[email protected] /mnt/backups/Backups/Android Stuff/Roms and backups/stock-2.1 $
So something is up with the file. If you have an FTP or something I can send it to you but unfortunately my ISP blocks most incoming port traffic and I don't know of any (if you can suggest) free upload sites that will sustain a 400meg file. If ya lived in the PNW I would invite you over and I would do it for you, but Ohio is a bit out of range from Auburn WA =). I am home though, so if you need more help PM me and maybe we can jump on ventrilo or something and I can walk you through it.
Ultra Droid said:
I've now got RSD Lite set up, however it doesn't "see" the sbf file. That brings up another point. The download for the sbf file produced a non-zipped, 11.1 k file of some sort, currently sitting on my desktop. No matter what I do, RSD Lite won't interact with that file. It seems excessively tiny to be an actual file, but I've tried several additional downloads from the same link, and they all turn out the same - an 11.1 K, non-zipped file. I tried doing an online search for "sbf_flash" but haven't found an alternative download site for that file.
Is there an Alternate Plan B that I can turn to?
-Mike
Click to expand...
Click to collapse
http://www.multiupload.com/NYV7593UM3
Click on direct download from multi-upload and download The_gift. Once it is downloaded unzip it to your desktop and it should extract an SBF file as well as the drivers needed for your computer. (might not need them if you already have adb shell set up)
Would it be something you could upload to my Dropbox account? I've got one, but never used it.
It turns out that I *have* the gift, and I just extracted the whole thing. There is indeed am sbf_flash file in there, and it's size is listed at 12 KB. Is that correct?
you can find full instructions here (sbf section of the post)
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
Ultra Droid said:
It turns out that I *have* the gift, and I just extracted the whole thing. There is indeed am sbf_flash file in there, and it's size is listed at 12 KB. Is that correct?
Click to expand...
Click to collapse
It should be right around 400mb actually i believe. In any case it is NOT 12 KB.
Ultra Droid said:
It turns out that I *have* the gift, and I just extracted the whole thing. There is indeed am sbf_flash file in there, and it's size is listed at 12 KB. Is that correct?
Click to expand...
Click to collapse
Quick instruction on proper sbf...
Flash Back to Stock Android 2.1 Droid X
Also the sbf_flash(VRZ_MB810_1.13.6.2_1FF_01) file is 449 MB in total size.
mmaibl2011 said:
You need to download and install RSD Lite (download link can be found on the link posted above.)
Once you have installed RSD Lite you need to unzip the .sbf file to the desktop. Open up RSD and click on the (...) located on the top right of the screen. Find the sbf file and click start after you see a device connected on the bottom portion of the program. Then just sit back and wait.
Click to expand...
Click to collapse
After much jockeying around, I now have RSD Lite, I finally *found* the correct sbf. file (440 odd mgs), downloaded that, started RSd, did the "..." thing and it found the sbf file. Then I booted up the Droid X into bootloader, plugged in the USB cable then nothing. The phone indicates that it's attached to a USB cable (the word "USB" in the lower left hand corner of the black screen) but the PC doesn't register the presence of the phone, and neither does RSD Lite.
-Mike
I use Windows 7 64-bit
I had to run RSD Lite "As Admin" and place the .sbf file in the root of my D drive and also rename the .sbf to something simple like VRZMB810.sbf (No punctuation)
This was the only way to get RSD Lite to see my phone and for the program to start flashing the .sbf
OK, I'll try that. Thanks for the quick response, BTW!
-Mike
I tried running RSD as Administrator, I moved the sbf file to the root of Drive C - it was apparently to large for Drive D on this computer - but the program still won't recognize that the Droid X is attached.
Related
Tutorial/Walkthrough for flashing back to stock using RSD Lite (Unrooting a rooted phone by .sbf)
Tutorial Video can be found here... kind of... very close!
http://www.kimete.com/sbfrsd.html
= = =
The fine print: This information is provided without warranty. I can not be held responsible if you **** up. I simply wrote a walkthrough/tutorial. I did not produce the procedure or the steps. I just simply consolidated all the information into a single place with notes to make things easier to understand and execute. You are welcome to share this information anywhere you want. Please do credit me for writing it. Lastly, please link back to the original site if possible. I try to format the text in such a way that it is more easy to understand. Lastly, I ask that everyone who uses this pays it forward by helping others figure out their own phones. Now on to the procedure.
I am running Windows XP SP3/32bit.
= = =
Steps 1 and 2 can be skipped. You just need to download the latest version of the SBF file (currently 2.3.20). Link coming soon.
1. Download 2.3.20 SBF file for D2
You can find it here: http://www.iamthewalcs.com/Support-Files/Droid 2 2.3.2 SBF.zip
2. Extract the .zip file and put the .sbf file somewhere where you can easily find it.
3. Download RSD Lite 4.7. (RSD Lite 4.7 is not the same as RSD Lite 4.7.2)
[RSD Lite 4.9 works as well]
Reference: http://www.mydroidworld.com/forums/droid-2-how-tos/4393-how-sbf-flash-droid-2-a.html
RSD Lite 4.9 Here!
http://droid2files.com/tools/RSD Lite 4.9.zip
New: Download to RSDLite 4.7 with patch.
http://kimete.com/droid/RSDLite47patch.zip
There is a link to download RSD Lite 4.7 + patch here as well. Includes an installer (.msi) and the patch (.ini).
4. Install the program (rsdlite_4.7.msi) or RSDLite 4.9. Follow instructions until completion.
5. Next, extract the patch (pst_flash.ini) to the Motorola/RSD Lite folder. It'll ask you if you want to overwrite the file. Choose yes. (Don't think you need this for version 4.9, but don't quote me on that).
(My file path to place the file was: My Computer -> C Drive -> Program Files -> Motorola -> RSD Lite)
6. You'll need to have the Motorola Drivers. You probably already have them, but if you don't, you can get them here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
KalenXI noted that you can't use the same Motorola drivers that you used for root from the other thread. You must use these updated drivers with MotoConnect. Thank you sir!
7. Now would be a good time to back up anything on your SD card to your computer. Plug in your Droid2 to the computer via USB cable. Pull down the notification menu/blind, choose USB connection, and then choose USB Mass Storage Device. Now there should be a removable storage in your "My Computer." Go through your SD card and back up your important things. Probably the DCIM and download folder. You should also make sure that your phone is set up to "Back Up Data." Go to the system menu (the 4 squares icon/button in the lower left), choose Settings, then Privacy, then make sure the "Back up my data" and "Automatic restore" are checked.
8. You now need to put your phone in bootload mode. In order to do so, power down your phone. Slide open your keyboard, hold the "up" key (the arrow closest to the enter button), and power on your phone. You should come up with a black background and text with something along the line of d2.35 and usb okay.
9. Now you can open RSD Lite. Go to your Start Menu, Program Files, and you should see RSD Lite. In the title of the newly open window, make sure the version is 4.7.
Edit: If you opened RSDLite and your device is not showing, you might need to open it as an admin. Go to program files/motorola/rsdlite/sdl.exe, and right cllick and run as an administrator. Reference by JonandRoid. http://forum.xda-developers.com/showpost.php?p=8000565&postcount=12
10. Wait a few minutes until your device shows in the table. It should say A955, port 1, connected, etc.
11. Toward the top of the window, there is filename/blank field. To the right of it, there is "..." button. Click it. Now find your .sbf with the open window that popped up. Select "Droid2_X6_2.2...SECURE.sbf", or the latest version of your sbf, and press open. Back to the program window, press Start (right next to the "...") Your phone should now start flashing the firmware to the phone. Just let it run it's course. It's going to reboot and start up again. You'll know when it is done when the Progress field in the table of RSD Lite says complete. This may take a little bit. Maybe 5-10 minutes.
After your phone reboots and doesn't get past the boot animation (wait at least 5 or 10 minutes),
a. Turn off your phone
b. Hold down X on the keyboard
c. Turn on your phone while continuing to hold X
d. When you get the Android guy with a '!' in a triangle push the search button on the keyboard (the magnifying glass button, two keys to the left of the space bar)
e. Select both 'wipe cache' and 'wipe data' from the menu.
f. Reboot your phone
If you do steps a-f, you probably won't need to do these following steps.
12. I do not know if this will work or not, but if it does, you guys might not need to do the rest unless you truly do want to fully factory reset your phone. This step is UNCONFIRMED.
To get back onto the Verizon Wireless network, dial *22899 and press send. It should update your phone and you'll be back on the network. (Referenced from ITGuy11 at the link below.)
http://forum.xda-developers.com/showpost.php?p=7933189&postcount=12
13. Your phone still has everyone on it. You'll probably realize that you now have no 3G or phone service and are roaming. Now you need to Factory Reset your phone. Go to the system menu (the 4 squares icon/button in the lower left), choose Settings, then Privacy, the choose Factory Data Reset. Follow the instructions and agreeing to wipe your phone clean. It will ask you to confirm, and/or ask you to enter your security pin/security pattern. It'll reboot itself and run its course.
14. Your phone will eventually be put back to factory settings. You'll then be greeted by the new user/account wizard. Follow the directions. They'll ask you to program/update your phone, enter in some login info, and then your phone will be back to brand new, just like the day you walked out of the Verizon store, except with the BackUp Manager service, all your applications and contacts will be downloaded back onto the phone!
That's it! That wasn't so bad was it?!
= = =
If you found this tutorial helpful, and would like to do something for me, please donate to my PayPal. I am short on rent by $100 this month. I am a student, and moving to a new place and I need to produce first months rent, last months, and a deposit. I am not expecting to profit from this tutorial. Honestly, I am just doing this to help others. I just need some help with rent this month. All donations are appreciated, even if it is a dollar. If everyone donated even a dollar or two, I'd be set! PayPal info coming soon!
Another edit: PayPal: [email protected]
Another quick note, I'll be adding references sometime soon. It is almost 5 in the morning and I want to go to bed!
This is awesome, thank you. This tutorial and your rooting instructions (with all of the extra clarification) are very helpful. I know it's not much but I am going to try to send a few bucks your way (from one poor college student to another? ).
USB debugging should also be enabled. It's found in the Settings -> Applications -> Development.
bcs296 said:
This is awesome, thank you. This tutorial and your rooting instructions (with all of the extra clarification) are very helpful. I know it's not much but I am going to try to send a few bucks your way (from one poor college student to another? ).
Click to expand...
Click to collapse
Thank you. Any little bit is appreciated. Just need to get to the end of the week.
wsfanatic said:
USB debugging should also be enabled. It's found in the Settings -> Applications -> Development.
Click to expand...
Click to collapse
Thank you, sir. I will post that in the tutorial in a moment.
= = =
Also, according to ITGuy11, you can dial *22899 to update your phone to get it back on the Verizon network.
http://forum.xda-developers.com/showpost.php?p=7933189&postcount=12
I am a fail. Didn't read the whole tutorial. Assumed it was like the D1 sbf. Ok still have an issue though, When i get to the bootloader RSDlite and my phone do nothing, still says im missing a certain driver for the phone S Flash driver not found. Anyone know why thats happening?
LosAngeles said:
I am a fail. Didn't read the whole tutorial. Assumed it was like the D1 sbf. Ok still have an issue though, When i get to the bootloader RSDlite and my phone do nothing, still says im missing a certain driver for the phone S Flash driver not found. Anyone know why thats happening?
Click to expand...
Click to collapse
I had that same error, upgrading to the latest Motorola drivers fixed it. I'd post a link but the forums won't let me so just search for "motorola drivers" on google, go to the first link, go to "USB Drivers and PC Charging Drivers" and download the "Motorola 4.6.5 Driver with MotoConnect" drivers.
KalenXI said:
I had that same error, upgrading to the latest Motorola drivers fixed it. I'd post a link but the forums won't let me so just search for "motorola drivers" on google, go to the first link, go to "USB Drivers and PC Charging Drivers" and download the "Motorola 4.6.5 Driver with MotoConnect" drivers.
Click to expand...
Click to collapse
That makes sense. I got my drivers from when I installed Easy Tether. Driver files were on the phone. That's probably why it worked. So, solution to the problem is downloade the latest drivers!
I think a youtube video of this is possible. Would people be interested in that?
darkonion said:
I think a youtube video of this is possible. Would people be interested in that?
Click to expand...
Click to collapse
I think your instructions are comprehensive and clear here, I wouldn't do it unless you've got time to burn. my 02.cents
Thanks! What is everyone's experiences with this tutorial? I want to make sure that it makes sense and is complete. I wrote it from memory after flashing my phone.
20:56:42, September 03, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x19EC00 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
its still working afterwards, but lost root, etc. its now running 2.2.20, but I'm wary somethings messed up. should I root, install bootstrapper, and wipe, or just let it go (it still has all my apps and settings)
this is great....thank you sooo much. worked out perfect. just an fyi if you cant get rsd lite to recognize your phone on vista go to the ...motorola/rsdlite/sdl.exe and right click as administrator. wouldnt work before i did that. but everything was so smooth and great instructions, would donate but broke too..lol
kageurufu said:
20:56:42, September 03, 2010
Line: 587
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x19EC00 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
its still working afterwards, but lost root, etc. its now running 2.2.20, but I'm wary somethings messed up. should I root, install bootstrapper, and wipe, or just let it go (it still has all my apps and settings)
Click to expand...
Click to collapse
I'd just let it go. Reroot and move on with your life! If something did go wrong, reflash again.
JonandRoid said:
this is great....thank you sooo much. worked out perfect. just an fyi if you cant get rsd lite to recognize your phone on vista go to the ...motorola/rsdlite/sdl.exe and right click as administrator. wouldnt work before i did that. but everything was so smooth and great instructions, would donate but broke too..lol
Click to expand...
Click to collapse
Glad to hear it works. I'll add the note onto the tutorial.
Ughh this is frustrating.. When i get to the part where i have to select the Droid2....SBF file, the start button isn't highlighted so i cant press it. but when i choose the other SBF file, it's highlighted
knoxx said:
Ughh this is frustrating.. When i get to the part where i have to select the Droid2....SBF file, the start button isn't highlighted so i cant press it. but when i choose the other SBF file, it's highlighted
Click to expand...
Click to collapse
Do you have updated drivers? Don't quote me on this, but maybe flash one file and then flash the other?
That's what I did, I flashed the other file (successfully) and rooted. Didn't bother factory resetting or anything.
Sent from my DROID2 using XDA App
And today I was having problems, so I used the bootstrap recovery to wipe cache and data, and then sbf'd from the bootloader
Sent from my DROID2 using XDA App
How exactly do you download the device drivers? Ive tried a million times and the link given on the motorola website just keeps giving me zipped up documents. Really starting to piss me off.
joeld82 said:
How exactly do you download the device drivers? Ive tried a million times and the link given on the motorola website just keeps giving me zipped up documents. Really starting to piss me off.
Click to expand...
Click to collapse
You are moving in the right direction. Inside the zipped file, there is the install file, .msi, I believe, that you double click to install your drivers and MotoConnect.
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Follow the instructions in the alternate gtab firmware post. It worked great for me. I would suggest installing cwm so you can back up your existing firmware.
My update would force close during download on the stock firmware. I finally got it to work by minimizing the pop up that displayed the progress. For some reason the screen would crash the download.
Your files should be there but you will lose all user settings and installed apps when you do the factory reset.
This is a common issue with stock, and TnT Lite. The user data seems to be very unstable once you upgrade to different firmware.
The "easiest" thing to do is just wipe the user data. However, if there is certain data you need to keep, I would recommend the excellent Titanium Backup. The only caveat is that the device has to be rooted, to use it.
roebeet said:
The only caveat is that the device has to be rooted, to use it.
Click to expand...
Click to collapse
And Z4root does this easily. Just install and click "root".
RyuFDAC01 said:
Hey there hope this is the right place for this ... Just want to report something that has happened. I am currently unable to use the G tablet stock vanilla TnT... any clue as to why this would happen? I dont really use it anyway however should this be resolved? and would it affect the tablet in the long run if not addressed? I use Launcher pro and the tablet forces itself to that when "home" force closes. I would like to try the TnT lite however am not confident about it.
Do i need to root the device before i hold the power button and vol +? to flash the new rom ( it bugs me that this is all i have to do to put in a custom rom. it seems to easy, unless it is that easy)
Will i lose all the files, PDF's, and documents that i have on it once i flash the new rom ?
As you can see im a noob to Android. Thanks for advice and guidance in advanced and patients.
Click to expand...
Click to collapse
Tntlite is that easy I was surprised. Too since rooting my HTC hero a year and a half ago was so much more hands on
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
I thank you guys VERY VERY MUCH appreciate this
Hey guys.... first off thanks for the advice it worked great it was easy to do... flashed TnT lite and was excited.... i attempted to pull an app from freewareloversDOTcom and was stuck in downloading status for some time even with a good wifi signal... This is where all hell broke loose ....the file i wanted never downloaded.... then the pic gallery forced closed then the launcher forced closed and had to shut down now now its in bootloop....I attempted to power and vol + but nothing happened in fact got a triangle !.... what is needed now.....
LOL at the entire situation this was my fear..... please if someone with extreme patients can list or point to a noob friendly thread on what i need to do
i have a microSD card can that be used read somewhere that i may need that.....
Click to expand...
Click to collapse
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recovery\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recovery/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
Dude thank you so much for your effort in this !!!!! gonna try this as soon as i put my baby to sleep.... will let you know if this worked for me
dcom222 said:
I had a similar problem twice today (installed TnT Lite 2.02 and ran into boot loops). Here's how I recovered. Results may vary, so use at your own risk:
1. Download the vanilla restore from http://forum.tegratab.com/viewtopic.php?f=6&t=16 (this is just to get the recover\console file unless you want to manually create it).
2. Download the updated stock TnT from http://forum.xda-developers.com/showpost.php?p=9362168&postcount=35
3. Extract the "recovery" folder from gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1.
4. In the recovery folder there is a file called "command" with no extension. Open this file with a text editor (eg. notepad) and edit the line so "SDCARD" says "SDCARD2" instead. Save it and ensure you do not add any extension. It should look like this:
--update_package=SDCARD2:/update.zip
5. Rename the "update-smb_a1002-2967-user.zip" from step 2 to "update.zip".
6. Copy the entire recovery folder with the edited "command" file from step 4 and the "update.zip" from step 5 to the root of your MicroSD card. It's important that the contents on the root of your MicroSD ends up with:
/update.zip
/recover/command
7. Put the MicroSD in your gTablet.
8. Power on while holding the Volume Up button until you see a message regarding recovery.
9. You should see a graphic showing package box with a progress bar after a short time.
10. Wait until it completes and the unit will restart.
11. If all goes well, you should be back to stock TnT with the last OTA update.
If you are wondering why I just didn't use the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, it's because it didn't help me. I initially used the same general method above with the gtab_full_vanilla_system_2010_11_09.zip downloaded in step 1, but my gTablet still continued to boot loop. After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Hope this helps. Good luck.
Click to expand...
Click to collapse
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
roebeet said:
You mind if I steal these directions? It's more detailed than the one I wrote up on my TnT Lite post. I'd like to post it there (specifically the command file, as some people have issues understanding the "SDCARD2" change).
And thanks for posting your experiences to help the other users here!
Click to expand...
Click to collapse
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
dcom222 said:
Please do if they look to be correct. Hopefully we'll see confirmation that these instructions work.
I appreciate all your work on the gTablet!
Click to expand...
Click to collapse
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
RyuFDAC01 said:
Same here Roebeet thanks for your work...dcomm222 thanks again... So I tried to only install the TnTlite 2.0 from the microsd card, it read it, looked to have loaded it, and it went right into the bootloop again.... I really want TnT lite ......
so now i am going to try your method... fingers crossed
Click to expand...
Click to collapse
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
dcom222 said:
I had no luck trying to re-flash to 2.0X once I got in the boot loop - I couldn't get past it no matter what until I went back to stock. Once I was back at stock I could re-flash to 2.0X from the internal SD. I'm still trying to figure out what's getting me in the boot loop - everything seems to work great for a while.
Good luck!
Click to expand...
Click to collapse
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
RyuFDAC01 said:
GOT IT BACK!!!! geez man I was full on panic mode
have you flashed back to TnT lite back yet and how long does it last? Damn i am so tempted to go back im thinking it has something to do with what we attempted to load on the tablet ... i dont know just looking for a reason to Flash ....can this constant recovery flash do any damage to the tablet? I would like to try other Roms but dont want to mess my tablet up..
BTW i got this EUL when it rebooted especially sections 4.1 and 4.2 wtf!!! sorry about that but that is how i felt
Thanks again guys!!!!
Click to expand...
Click to collapse
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
I just flashed the TnT 2.02 again. So far it seems OK, however it did the first 2 times I did it as well. I followed all of the instructions at "forum.androidcentral.com/showthread.php?p=442691#post442691" except I substituted using roeboot's TnT. Once I did it I had everything working (flash, market, etc...). Both times the boot loop happened when I tried to install or uninstall something, and both times were after a few hours of use. I tried a third time and almost instantly got into a boot loop, but I think I got ahead of myself in that try and did some things out of order. The good thing is that I was able to recover each time.
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
The EULA shows up with a new stock firmware - and yeah 4.1 / 4.2 kinda bugged me too. I never selected "I Agree" - fark that.
As for the boot loops, it seems that we still can't pin it down - maybe it's just random, I don't know.
Hi,
I was stuck after bootlooping using Cyanmod, then flashing NVflash still didnt fix the issue, this fix did it for me. Thanks for getting me back up & running. I will give another shot at using cyanmod now that I have all the files needed to get me back.
BTW< I have a green cloth. What does that mean?
Thanks,
Rich
dcom222 said:
If I remember correctly, the stock firmware with the OTA update will prompt you to accept a license and prompt to set the time, etc....
Out of curiosity, did your tablet come with a gray or green cloth to clean the screen? The reason I ask is that I thought I had seen somewhere that this might be an indication of a difference in gTablets.
Click to expand...
Click to collapse
My tab came with a grey cloth... funny thing though I got mine on the second wave of shipments to sears... I NEVER had any issues with the time i just set it and it kept the time... I remembered that when these first came out that was a problem... i thought mine was diff because i never had any issues with time reseting itself... anyway Thanks again dude for your help hope i could play this forward to someone more noobier than me
Roebeet looking forward to your TnT lites...
dcom222 said:
After a fair amount of panicking and looking over all of the threads here, I found that gtab_full_vanilla_system_2010_11_09.zip added ClockWork Recovery so I was able to use this to copy over the update-smb_a1002-2967-user.zip to my internal SD, install it, and get my gTablet working again. When the problem happened the second time, I used the method above and it worked for me.
Click to expand...
Click to collapse
I now have clockwork recovery installed... How do i copy the update.zip from external microsd to internal microsd... mounting sd-ext gives an error..
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
Frustration levels are high with this device!!
Thanks!
a "me too" reboot problem
I was able to install TNT Lite 2.0, then 2.11. I got Clockwork Recovery installed as well.
The market would start, but if I did a search for obvious things like "Kindle", the market would give an error that it didn't exist in the market. Thinking it was the error situation described here:
http://forum.xda-developers.com/showthread.php?t=845175
I applied those instructions, and rebooted.
Upon reboot, it ended up in a continual reboot loop.
Trying to do the start with volume+power, it brings up Clockwork Recovery, and when told to wipe data/factory reset, it stays in the reboot loop. When told to apply sdcard's update.zip, it looks only at the one on the internal sdcard, which is for CWR, and goes back into the loop.
At that point I setup a microSD with the information from this post:
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
including changing the line from sdcard to sdcard2. Again it doesn't recognize that the internal sdcard2 is plugged in, and attempts to mount it with CWR (mount /sd-ext) yields the error:
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Error mounting SDEXT:!
So, unfortunately I'm at an impasse, like the previous poster. I just bought the tablet a couple of days ago, so I'm far from expert at tweaking it into working.
Any suggestions on what to do, are greatly appreciated.
PS - Bought the gtablet from Office Depot, and received a green cloth.
Boot into clockwork recovery and go to advanced and format SD, use the 2gb and 512mb I believe, then flash TNT or another rom. That fixed my boot loop.
Hi everyone,
I have a newbie question because I have read and re-read a few of the stickies here but am still confused. I used to have an elocity a-7 and to flash the rom I would simply copy a file called update to the micro sd and boot into the recovery and it would update. Seems there are a few ways to do this with the Gtab and I am very confused and I do not want to brick my device. Lack of the market is driving me crazy as are other buggy thing in the stock os.
So I have my tab connect to my pc and I can see an update file there, now if I simply delete that file and replace it with the renamed VEGAn-tnt and then run an update it should work right? Am I missing something here? Several stickies say to install clockwork first but just doing that is confusing to me and I would rather just install an update and see if it works.
Am I right about the procedure or am I missing soemthing.
Thanks for any help in advance and sorry if this question has been asked before I am just trying to get clarity before I do this.
Rob
ClockWorkMod is extremely useful and installing it is as easy (and identical actually) as flashing ROMs on the A7 (owned one for about 3 days before returning it and getting my tab )
This was the first post I followed and is a great one doing the initial setup on your gtab:
http://forum.xda-developers.com/showthread.php?t=865245
Came across this one today, just as helpful and easy to follow:
http://forum.xda-developers.com/showthread.php?t=1016695
Hope this helps
If you need clockworkmod: http://forum.xda-developers.com/showthread.php?t=1005080
See the section in PART2.
1st wifi and update with viewsonic. Updates kernel to 3588 or something. Then I downloaded the tnt lite .rar file from roebeet tnt 4.3.0 and extracted it with winzip on my desktop. It gave me 3 files: update.zip, command, recovery.. ok. Drag command file inside recovery folder on your desktop. Now you have 2 files to only worry about. Plug your USB cable into your tower or laptop. A USB message appears on screen of gtab. Yes activate USB. Go to start, computer, and gtab will be there. Double click on gtab and open up file structure. I renamed my update.zip and recovery files oldupdate.zip and oldrecovery. Then drag the 2 files on your desktop into /sdcard to replace the ones you just renamed. Deactivate USB. Turn off gtab. Press volume up button and power button. You will see a box with a green arrow filling box. When it comes up. OH MY GOD. WHAT A BEAUTIFUL. DEVICE. I have had it 2 days and I have Skype, all kinds of games, and I can't put it down. I hope this helps. Follow the other sticky post on installing roms the hard way. My is great. I hope you update. Dan
My infuse when turned on goes to a screen that looks like phone ! pc with the message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So this happens even when I try and go to download mode or recovery mode. Basically as soon as I hit the power button. I'm really freaking out. It was rooted and I was doing following this link: http://forum.xda-developers.com/showthread.php?t=1613523
Then the problems started when my computer didn't recognize the phone in download mode. and then it was recognized so I started the Odin flash. Then it froze at cache.rts (I believe that's what Odin said, I can't get to it anymore)...So I uninstalled and reinstalled the drivers and did it again and it got to factoryfs.rfs before it froze there for a really long time. So I unplugged it and tried to do GTG Ultimate Unbrick...but I can't get the .zip file to open. My computer keeps telling me "Can Not Open ____ as archive". I re-downloaded it and same result. Is there anything I can do to save my phone? I'm a real idiot and this kind of stuff always happens to me no matter how much I read up on something and make sure I'm doing it right. I would really appreciate a little help though, thanks!
I actually got it downloaded and followed Rammstein874's video on youtube on how to do it and I am once again stuck on factoryfs.rfs :-(
What can I do at this point? It is still stuck at the Phone-!-PC screen when I try to go to download mode. Please help, I'm starting to get pretty worried about this...
When your screen is phone!computer, that's an alternative version of download mode. You can either use ODIN or heimdall back to stock. Just plug it in via usb, allow odin/heimdall to recognize it and start flashing.
This is correct....if you see those pic on your phone that is a form of download...i would run the one click method...
sfgiants2010 said:
Rammstein874's video on youtube
Click to expand...
Click to collapse
Can you PM me the link to Rammstein874's video? I didn't realize he still had this, and I've since updated my packages and how-to.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
jscott30 said:
Can you PM me the link to Rammstein874's video? I didn't realize he still had this, and I've since updated my packages and how-to.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Lemma know if that's the one..pm sent...
Sorry I was at work all day.
This is the video link I used: http://www.youtube.com/watch?v=y1HgcZrYR_4
I am also looking at the following one-click method posts:
- http://forum.xda-developers.com/showthread.php?t=1331381
- http://forum.xda-developers.com/showthread.php?t=1524081
* I used the above link (or tried) and it didn't seem to work either. I downloaded Heimdall Suite for Windows 64bit and then installed the drivers and plugged in my phone in download mode. But then I was unable to get it started...I used the "Stock_SGH_I997_UCLB3_Repartition-One-Click.jar" file I found on mediafire (because all of these posts link to mediaupload which is no longer working). Anyway, so I tried to run Heimdall-frontend.exe on windows and once it opened up I connected my phone (nothing turns green like the post says) and hit browse. I chose the jar file aforementioned and it said "tar header contained invalid file size."
So if someone could point me toward a more up to date thread if I'm using the wrong one and kind of explain to me how to get around the other problem I'm having with the jar file then I would be forever appreciative
Not sure what you did...not saying you did something wrong but here is what I do, below are how i perform using qkster's method...
The USB + Volume Down + Volume Up Method: Download mode (Noticeable by an Android robot digging with a shovel) is reached by taking everything out (Battery, SIM, MicroSD). plug in the USB cable to your computer and phone then putting in battery at the same time Holding the volume buttons both up and down, (Don't press the power button at all in this method).
How to INSTALL:
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: CONNECTED. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
download this file for your one click to stock...and using above directions...
once that is done and you want to put CWM mod on for flashing a custom ROM, same directions to get in to download mod...
download this file to use the one click to put CWM mod on your phone
here is the link where i took all this...
http://forum.xda-developers.com/showthread.php?t=1524081
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
sfgiants2010 said:
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
Click to expand...
Click to collapse
why are you using these other programs...idk,
I just click on the one click file it an executable design to open and run itself...you say attach the jar file...why the suite version of heimdall...?
did you download the links i provided and just use those...?
sfgiants2010 said:
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
Click to expand...
Click to collapse
Is your phone still stuck on the phone-!-pc ?
did you read the last post he had regarding the actual heimdall program suite...
not sure what he had going on...I believe he has download mode capability...
thx ''Goshujin-sama'' qkster
Yeah..that's where I wasn't sure what sf was doing.
the jar file is self executable. When you click on the jar file, there is a load up delay.
Then should be be ready.
You then hook up the phone.
I've not seen in tar header file size error.
Sf should not be trying to stick the 1-click file into heimdall front-end.
It's a single self executable jar file..the is no other dependencies...the only other situation I can think of is maybe putting the 1-click jar file onto a different PC and try running it there.
qkster said:
Yeah..that's where I wasn't sure what sf was doing.
the jar file is self executable. When you click on the jar file, there is a load up delay.
Then should be be ready.
You then hook up the phone.
I've not seen in tar header file size error.
Sf should not be trying to stick the 1-click file into heimdall front-end.
It's a single self executable jar file..the is no other dependencies...the only other situation I can think of is maybe putting the 1-click jar file onto a different PC and try running it there.
Click to expand...
Click to collapse
that's when I started to question him on these other programs...due to the one clicker is self sustained as a exe...idk...but believe he log off...i will monitor and holler at you if required thank you...
Oh man I had no idea...I was so mixed up by trying to educate myself with so many posts about using Heimdall. I thought I had to download Heimdall separately and attach the jar file or something. But okay so I ran the one-click. It failed the first time (expected) and then I checked the flash bootloaders box and hit flash again. Then it stopped at installing drivers and prompted me to install the drivers on the following prompt. So I did that and then it said installed drivers successfully and I hit close. Then nothing happens. So what do I do at this point? I'm probably being an idiot again but I really appreciate you guys trying to help me out. And I hope you realize I'm trying my best to not waste anyone's time.
The device status was a green Connected before I started by the way. At this point what I do? It seems to just break at the installing drivers part...?
It should of rebooted it self the phone...
Btw you are not wasting my time...wife is watching cup cake wars...so ....rather help you...lol
sfgiants2010 said:
Oh man I had no idea...I was so mixed up by trying to educate myself with so many posts about using Heimdall. I thought I had to download Heimdall separately and attach the jar file or something. But okay so I ran the one-click. It failed the first time (expected) and then I checked the flash bootloaders box and hit flash again. Then it stopped at installing drivers and prompted me to install the drivers on the following prompt. So I did that and then it said installed drivers successfully and I hit close. Then nothing happens. So what do I do at this point? I'm probably being an idiot again but I really appreciate you guys trying to help me out. And I hope you realize I'm trying my best to not waste anyone's time.
The device status was a green Connected before I started by the way. At this point what I do? It seems to just break at the installing drivers part...?
Click to expand...
Click to collapse
Once the connected bar is on, you click flash. It should complete it's routine. the phone reboots. you should click on the boot loader box. you disconnect. let it finish. set it back into donwload mode and flash again.
you can try different usb port or data cord or different pc
Plus you have my master...qkster here...cuz you lost me on the programs you were using...so i called in the jedia master!
As long as your screen has that Phone! Computer sign, it's not bricked yet. I recommend you to search some how to videos online so you can see the exact instructions on how to use heimdall because it's that easy. If possible maybe one of our awesome contributors can make a how to video for heimdall.
I believe he is tracking now qkster is providing....thx
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.