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
Related
THIS GUIDE HAS BEEN REDONE. PLEASE VISIT THIS THREAD:
http://forum.xda-developers.com/showthread.php?t=761819
Just reading through the document now, seems the first link, http://www.soft‐go.com/get/Samsung‐Kies_79632.html isn't working. Not sure if the site is just down right now or if there's a mistake.
Rad_Fishy said:
Just reading through the document now, seems the first link, http://www.soft‐go.com/get/Samsung‐Kies_79632.html isn't working. Not sure if the site is just down right now or if there's a mistake.
Click to expand...
Click to collapse
Thank you I didn't actually add that link it was from systoxity, but i will fix it.
nbs11 said:
Thank you I didn't actually add that link it was from systoxity, but i will fix it.
Click to expand...
Click to collapse
I Fixed it
A few small things:
Intel should be intel.
Under CPU Optimization:
"Samsung’s CPU is set by default the run at 1gHz."
The should be to.
Sideloading:
"(don’t forget that after you install it from the market you still have to go to your app drawer and run busybox once so it installs)."
Should this be after you download it from the market?
ClockworkMod Recovery:
"ClockworkMod written for us by a developer that goes by the name of Koush"
Missing is.
"This gent puts a ton of work into helping us captivate owners out"
Replace puts with put and Capitalize Captivate.
Changing Your Messaging Ringtone:
"well the ones that matter anyway.."
Extra period.
Other than that, excellent guide. I'll definitely be using it when my Captivate arrives.
Rad_Fishy said:
A few small things:
Intel should be intel.
Under CPU Optimization:
"Samsung’s CPU is set by default the run at 1gHz."
The should be to.
Sideloading:
"(don’t forget that after you install it from the market you still have to go to your app drawer and run busybox once so it installs)."
Should this be after you download it from the market?
ClockworkMod Recovery:
"ClockworkMod written for us by a developer that goes by the name of Koush"
Missing is.
"This gent puts a ton of work into helping us captivate owners out"
Replace puts with put and Capitalize Captivate.
Changing Your Messaging Ringtone:
"well the ones that matter anyway.."
Extra period.
Other than that, excellent guide. I'll definitely be using it when my Captivate arrives.
Click to expand...
Click to collapse
Thanks! I fixed all those errors but I'm not gonna upload the new version just yet because I will keep finding more errors so it just seems wasteful. I did not actually write most of the guide myself I just formatted it so there may be some mistakes I didn't pick up on.
i used this guide today and it delivered.
orlandoxpolice said:
i used this guide today and it delivered.
Click to expand...
Click to collapse
If there was anything you found difficult or anything you would like to change just tell me and I will add it to tonight's update.
Hi,
Thanks for publishing this. It looks very useful, similar to Energy ROM.. But I am very new to Android phones (trying this on Samsung Captivate from AT&T, bought yesterday). I am running windows 7 ultimate 64bit and I exactly followed this guide. But somehow I am still not able to see the sd card. I tried placing the update.zip at Computer\SGH-I897\Phone and shut down the phone and tried restarting the phone by holding the up/down keys as well as power button. But after selecting reinstall packages it said could not find /sdcard/update.zip.. Pls held. Again very sorry if I did some mistake..
ask_j said:
Hi,
Thanks for publishing this. It looks very useful, similar to Energy ROM.. But I am very new to Android phones (trying this on Samsung Captivate from AT&T, bought yesterday). I am running windows 7 ultimate 64bit and I exactly followed this guide. But somehow I am still not able to see the sd card. I tried placing the update.zip at Computer\SGH-I897\Phone and shut down the phone and tried restarting the phone by holding the up/down keys as well as power button. But after selecting reinstall packages it said could not find /sdcard/update.zip.. Pls held. Again very sorry if I did some mistake..
Click to expand...
Click to collapse
The SD card is simply the root directory of your phone. You do not need to open a folder, it is the highest folder you can place it in. Hope that helps
Somehow it was not able to find the sdcard root. Then I realized that you mentioned something called as Droid Explorer, I searched for it and installed it on my PC. But when I opened Droid Explorer, my device was not recognized, then I clicked on link on the explorer window, upon watching that video I enabled the USB Debugging, then I was able to see my device, then I selected connect to my device. After that I saw an explorer but it had empty root and I was not able to copy anything. There was a menu button at the top row named "Transfer to device or Copy to device" I selected that and selected update.zip file and tried to transfer. Something happened but still explorer was empty. Then from my phone Top slide down menu I selected mount USB storage and I started seeing windows explorer on my PC. Then apart from other folders I could see a folder sd in the root. Then I again put update.zip in the root.
Then followed the restart sequence, this time it found the file but exited after Signal 7. It was trying to asert something but could not find the correct model number I guess. My cell phone's model number is Samsung i897.
Please help
ask_j said:
Somehow it was not able to find the sdcard root. Then I realized that you mentioned something called as Droid Explorer, I searched for it and installed it on my PC. But when I opened Droid Explorer, my device was not recognized, then I clicked on link on the explorer window, upon watching that video I enabled the USB Debugging, then I was able to see my device, then I selected connect to my device. After that I saw an explorer but it had empty root and I was not able to copy anything. There was a menu button at the top row named "Transfer to device or Copy to device" I selected that and selected update.zip file and tried to transfer. Something happened but still explorer was empty. Then from my phone Top slide down menu I selected mount USB storage and I started seeing windows explorer on my PC. Then apart from other folders I could see a folder sd in the root. Then I again put update.zip in the root.
Then followed the restart sequence, this time it found the file but exited after Signal 7. It was trying to asert something but could not find the correct model number I guess. My cell phone's model number is Samsung i897.
Please help
Click to expand...
Click to collapse
I did not write the PC instructions, so I can not help you (I only have a Mac). But the person who did can probably help you his username is systoxity.
Because not enough errors were found to make it worthwhile to update the PDF i will wait till tomorrow to fix the minor errors.
Good source of information
Thank you for putting this together. I am going to sticky this for the time being.
For installing the latest version of busy box, you should include that before the instructions for running titanium backup...the latest version of busybox installed from the market will work with titanium backup so theres no need to have to click the "problems" button...this way you wont have to do the busybox download step twice...should also save a few megs since titanium backup wont have its own copy of busybox installed BTW nice guide
You can also just mount the phone memory using windows explorer and move the file over. I was never able to get droid explorer to transfer the file. It always said it went but then was never there.
Anyway all I did was connected just as I was going to connect to kies but then when windows asked me what I wanted to do I clicked on open file view and dropped updated.zip on my phone.
Only issue that I had with rooting was I accidentally opened the file in windows(winrar). After I moved the file over it found it and attempted to install it but then exited with an error(do not remember exact error), but had to do with mounting. Anyway I re-downloaded file and saw file size was different. After I moved the file over again everything went great. I still haven't removed bloat-ware and such but thats next on the agenda.
Also I was on windows 7 64 bit, saw some other users in other threads saying they had issues connecting the phone. Everything so far has worked great for me
Thank you very much for this handy pdf file!
Somelinks aren't working
First of all I have to say very good guide for noobs!
1. when I downloaded the update.zip folder I didn't work I guess because the name of Samsung captivate is not in the folder or something. So I just downloaded the other file from the forums.
2. Link to CPU optimization doesn't work.
3. I downloaded the droid explorer. It connected to my phone but I was unable to transfer anything. So I just tapped on the USB connected in the notification bar and mounted the phone. This allowed me to use windows explorer to transfer files. I believe one can transfer files by selecting the option of Samsung Kies under USB settings.
I got all your feedback. It will all be corrected by tomorrow night.
Cool guide however the rumor is the GPS only gets turned on when pulling up an App that uses it, so that step in the "battery saving" section might not be necessary.
Also you may want to replace Market Enabler with Market Access. It's a rehash of Market Enabler but also has a Set on Boot option that keeps it persistent versus being reset each time.
You also Might want to add a Tips/Tricks Section..
Here You can put some cool tips like the one i found out about backlight control.
(found here: http://forum.xda-developers.com/showthread.php?t=735394 )
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 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.
ROM for recovery G2X under the NVFLASH
This method necessary!
If the device is not loaded and not firmware in other ways! (If you downloaded the wrong firmware in the device)
I took the unpacked program files KDZ and added to them NVFlash and created BAT file!
Download ROM: http://www.mediafire.com/?wfokxjxi7rfoaey
Mirror: http://www.megaupload.com/?d=C5LBU3DS
Download APX driver: http://www.mediafire.com/?k559zgjlqkd5ted
Installation Instructions:
Download both files
Unpack it to the C drive to their respective folder
Remove the battery
Hold Vol Up/Down (and keep them held)
Insert the USB cable
Install APX driver from the your APX folder
For windows 7(and vista? please confirm):
Open Device Manager in Windows and you should see "APX Device" listed with an error
Right click on the APX device
Select 'Update driver software'
Select 'Let me pick...'
Select 'Have disk'
Browse to directory you extracted the APX Driver
Select the *entire* 'APX Driver' folder
Accept any warnings, including the big red alert (you may need to disable UAC)
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'
If not, uninstall the driver, reboot, rinse and repeat
Unplug everything
Hold Vol Up/Down (and keep them held)
Insert USB cable
open your ROM folder:
Run Flash.bat file and wait for the process
After the logo appears on the LG phone
Unplug USB cable
Insert the battery
enjoy!
After that, I recommend to firmware device with help programms KDZ or LG Mobile Update
I'm confused as to what this is? I'm guessing stock rom flash through nv flash? Kind of like odin for samsung phones?
Sent from my LG-P999 using XDA App
Can't wait to check this out when I get home later. Regarding the kdz file, what exactly were you able to unpack from it? I've been able to extract 2 files (a very large .wbd file and a .dll file) but I couldn't figure out how to unpack them further, specifically the .wdb file.
ILUHA_89 said:
I took the unpacked program files KDZ and added to them NVFlash and created BAT file!
Click to expand...
Click to collapse
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
Smallsmx3 said:
I'm confused as to what this is? I'm guessing stock rom flash through nv flash? Kind of like odin for samsung phones?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
jboxer said:
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
Click to expand...
Click to collapse
You described it right!
This method has helped resurrect my device!
ZeroT| Demented said:
So the point of this utility if it works is to make the g2x un f***able like even if u do u can fix?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Yes. It is almost as good as JTAG flashing the device. For Galaxy S devices using ODIN you still have to have the 'software download' mode working in the ROM and it is possible to brick a Galaxy S beyond the point of even getting this mode to be accessible leaving you the only way to fix the device through disassembling it and flashing via the JTAG pads. Using the NVFlash method you are flashing directly to the hardware through they Hynix flashing chip. I had another phone with a similar capability (I-Mobile i858 - Yuhua Touchstone device) and no matter how badly I F'd it up (I was developing custom roms for it) I had the similar low level flashing tool that could reflash the phone to stock so I could start over with a clean slate. If this method is legit, this is a big boon to the dev community for this device.
jboxer said:
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
Click to expand...
Click to collapse
After trying to firmware device with program KDZ or LG Mobile Update in folder C: \ ... \ Aplication Data \ folder appears "LGMOBILEAX" which contains the firmware files!
That's All
ILUHA_89 said:
After trying to firmware device with program KDZ in folder C: \ ... \ Aplication Data \ folder appears "LGMOBILEAX" which contains the firmware files!
That's All
Click to expand...
Click to collapse
So you got them after the LG Updater extracted the KDZ into its component files. phburks and I didn't get that far as we didn't want to connect our already updated devices to the updater. To get to the point you did where you could grab the individual files you would have had to click the start update button. Good work.
I have 7-zip on my computer but I am unable to open up the file I just downloaded. Can you put it in another format and upload to megaupload or mediafire please? I don't want to go through that Russian site again as I got an invalid download. Also, please post the baseband file as a separate download.
jboxer said:
So you got them after the LG Updater extracted the KDZ into its component files. phburks and I didn't get that far as we didn't want to connect our already updated devices to the updater. To get to the point you did where you could grab the individual files you would have had to click the start update button. Good work.
I have 7-zip on my computer but I am unable to open up the file I just downloaded. Can you put it in another format and upload to megaupload or mediafire please? I don't want to go through that Russian site again as I got an invalid download. Also, please post the baseband file as a separate download.
Click to expand...
Click to collapse
I downloaded the 7-zip file to the sdcard on my phone but I won't be home to try opening it for several hours because I'm at seaworld. Lol
Hopefully you guys can get this sorted out. Sounds promising so far.
phburks said:
I downloaded the 7-zip file to the sdcard on my phone but I won't be home to try opening it for several hours because I'm at seaworld. Lol
Hopefully you guys can get this sorted out. Sounds promising so far.
Click to expand...
Click to collapse
I won't be able to look at it until tomorrow as it is 11:31 p.m. here and time to go to bed. :-O ZZZzzzzz
How about posting a mirror???? the site will not let me download.... unless i visit a sponsor and purchase something... lol
i'll try it out and report back
........... Works like a charm
here mirror link
http://www.megaupload.com/?d=C5LBU3DS
What we really need is for someone to tell us how to create the config files for NVFlash so we can flash the baseband only. The new baseband is there and named 'P999_MDM.bin' if I am remembering correctly. No reason to flash an entire ROM when all someone wants is the updated baseband. If we can get the older baseband file also this tool could be used to revert the baseband also, if someone wanted to do that.
web_ninja said:
How about posting a mirror???? the site will not let me download.... unless i visit a sponsor and purchase something... lol
Click to expand...
Click to collapse
You don't have to buy anything. You just click on one sponsor site and it opens a new window. Thirty seconds later it will enable a download link. You need to click download two or three times if I remember correctly. I am at work now. I can mirror it in about ten hours if nobody else has done it yet. I looked at the files briefly and it looks legit.
Is this supposed to have a command interface? Or are you still typing in commands yourself?
I edited a cap!
Changed link to Mediafire
omarsalmin said:
Is this supposed to have a command interface? Or are you still typing in commands yourself?
Click to expand...
Click to collapse
Good question - that is what I am looking for rather then having to mess with the nvflash commands directly.
Update - this setup is similar to Paul's stock ROM recovery setup on modeco.com. As with his, you only have to "Run Flash.bat file and wait for the process". When I could not get off of the LGupdater screen by any other means, I ran this file from his post and it ran flawlessly - but of course I ended up with a 990's device. I tried to get back with other tools and firmware, but was never able to do it.
If this works OK, you would be able to restore your data, apps, or a nandroid and you are back in business.
I spent a week trying to restore my original (and best device as it turns out), so I am not going to fool with this right now myself. I did compare the config files from bot Paul's and this firmware and they are different - which looks real promising, as they are different.
HELP! I tried to use this and the tool failed, now I am getting ZERO response from the device. I can't even boot to APX. I'm freaking out right now!
EDIT: I managed to get the process restarted and the phone is in the process of rebooting. Hoping for the best.
EDIT 2: Phone booted up and it was all restored but for some reason the baseband was not updated :\
Did you run by using the flash.bat file? Did you hold volume up and down for the entire flash process?
Sent from my LG-P999 using Tapatalk
AimanF said:
HELP! I tried to use this and the tool failed, now I am getting ZERO response from the device. I can't even boot to APX. I'm freaking out right now!
EDIT: I managed to get the process restarted and the phone is in the process of rebooting. Hoping for the best.
EDIT 2: Phone booted up and it was all restored but for some reason the baseband was not updated :\
Click to expand...
Click to collapse
Did you have old of new baseband on before flashing? What was the state of your G2X before running this?
UPDATE: It appears that this works - but would like to 100% confirm. After all the disasters that occurred from running the LGupdater tool, this would be an important fix and should be stickied at some point. Current members know of the updater problems, but new buyers and member may not - so many may still have this problem down the road.
Therefore, I believe this is an important enough item to bring to closure and make readily available.
U saved my phone's life
THANK YOU THANK YOU
followed instructions restored completley to stock just like how i got phone out of box 2 weeks ago.
I was running eaglesblood v8 and had altered the vold.fstab file to switch mounts
from sdcard to internal and after that point i rebooted and media scanner said damaged sd card well i figured it just to be like an extension of a permission of sorts. and thought if formated it would the paths would switch no problem.
im actually kind of having a hard time rembering exactly what steps i did take to **** it up royally. but went into clockwork 5 to flash another rom from internal storage or same i cant rember now and did factory reset then all hell broke loose .
couldnt mount nothing except for system i tried formating sd card even though i dont have one probally ended up formating internal lol. formated system,
re flashed all recoverie versions including stock. i was getting so mad i called google HA by the way they got some pretty good music when u have to hold.
only thing i didnt try was to load up a rom on sd card and mount that but i really doubt it would have worked and plus i couldnt even use phone to do it lol
i need to go buy drive saved me some serious cash I would say this should be enough confirmation!!
OK I apologize ahead of time for what is probably a ridiculously easy question for most.
The ATT 1X is my first android and this is the first phone that I've rooted.
I read for hours and followed the instruction to a T. I rooted, unlocked the bootloader and installed CWM.
I can get into Recover/Boot mode or whatever you call it on phone startup, I have the Super user icon in my files, but I have no idea what to do now.
I found a ROM that I thought was worth a shot (CleanROM 2.5) but I don't know what to do. I've read and researched for hours now and everyone's problems seem to be complicated but no one talks about this.
I downloaded the ROM to my computer but I don't know what to do with the files, I can't find a .bat file or anything to initialize it and I am stuck.
I've wiped the data and done everything in the steps but I'm stuck at actually installing it. I know I'm obviously doing something wrong but I feel like I'm very close to what needs to be done.
Any help is welcome, thanks
deblas66 said:
OK I apologize ahead of time for what is probably a ridiculously easy question for most.
The ATT 1X is my first android and this is the first phone that I've rooted.
I read for hours and followed the instruction to a T. I rooted, unlocked the bootloader and installed CWM.
I can get into Recover/Boot mode or whatever you call it on phone startup, I have the Super user icon in my files, but I have no idea what to do now.
I found a ROM that I thought was worth a shot (CleanROM 2.5) but I don't know what to do. I've read and researched for hours now and everyone's problems seem to be complicated but no one talks about this.
I downloaded the ROM to my computer but I don't know what to do with the files, I can't find a .bat file or anything to initialize it and I am stuck.
I've wiped the data and done everything in the steps but I'm stuck at actually installing it. I know I'm obviously doing something wrong but I feel like I'm very close to what needs to be done.
Any help is welcome, thanks
Click to expand...
Click to collapse
I recommend you check QA thread found in a sub forum under your devices section and you review the stickied post for ROM install or Google "android install custom ROM " (remove quotes). Too much info on this already to type it all back out here. Did you watch you tube newb video you agreed to have watched when getting an xda account?
Essentially you now made it so your phone has the ability via CWM Recovery to now boot to that to install ROM zip or continue to use rooted stock ROM (how you flashed that zip for superuser is baasically same as how you flash a cwm compatible ROM zip (MOST but not all ROMs)) which with SuperUser can now run privelleged code if it is made to or requires it to run.
Sent from my SGH-T989 using Xparent Green Tapatalk 2
Thanks. I know this must seem so stupid, but I've been searching this forum, google, youtube and pretty much everything else for how to do this and I get it all and understand what's happening.
I just don't know where to put this ROM (which folder) to get it to install.
deblas66 said:
Thanks. I know this must seem so stupid, but I've been searching this forum, google, youtube and pretty much everything else for how to do this and I get it all and understand what's happening.
I just don't know where to put this ROM (which folder) to get it to install.
Click to expand...
Click to collapse
So after all that searching you never came across instructions informing you to put the zip on your phones storage?
You should probably just hold off a bit on flashing anything then. Not being mean but it sounds like you are confused by the process and end result. Step back and do some basic checklisting.
Sent from my HTC One X using Tapatalk 2
Download the rom you want and DO NOT UN ZIP IT. THEN PLACE THAT ZIP ON PHONE STORAGE AND BOOT INTO YOUR CUSTOM RECOVERY . HIT INSTALL FROM SD CARD AND MAKE SURE THE ROM YOU DOWNLOADED IS LISTED BUT DONT FLASH YET. GO BACK THE THE MAIN SCREEN OF RECOVERY. NOW MAKE A BACKUP. WHEN THAT IS DONE GO BACK TO MAIN RECOVERY SCREEN AND HIT WIPE PHONE DATA AND THEN CONFIRM. THEN GO AND HIT CLEAR CACHE OPTION. THEN GO BACK AND GO TO ADVANCED AND CLEAR DALVICK CACHE. NOW YOUR READY TO FLASH. GO TO INSTALL ZIP FROM SD AND FLASH YOUR ROM. FIRST BOOT ALWAYS TAKES LONG AFTER FLASHING A NEW ROM :thumbup:
Sent from my HTC One X using XDA
Pirateghost said:
So after all that searching you never came across instructions informing you to put the zip on your phones storage?
You should probably just hold off a bit on flashing anything then. Not being mean but it sounds like you are confused by the process and end result. Step back and do some basic checklisting.
Click to expand...
Click to collapse
Been posting on the internet for decades, don't worry about being mean. I'm here to learn. I rooted, unlocked the bootloader and installed CWM so that I could take advantage before the phone asked me to update the software to the 1.85 version.
My phone works fine now, and I did everything correctly which is what I was setting out to do. I'm in no rush to flash a ROM, but now that I'm ready I'm itching to try it out.
Driggity420 said:
Download the rom you want and DO NOT UN ZIP IT. THEN PLACE THAT ZIP ON PHONE STORAGE AND BOOT INTO YOUR CUSTOM RECOVERY . HIT INSTALL FROM SD CARD AND MAKE SURE THE ROM YOU DOWNLOADED IS LISTED BUT DONT FLASH YET. GO BACK THE THE MAIN SCREEN OF RECOVERY. NOW MAKE A BACKUP. WHEN THAT IS DONE GO BACK TO MAIN RECOVERY SCREEN AND HIT WIPE PHONE DATA AND THEN CONFIRM. THEN GO AND HIT CLEAR CACHE OPTION. THEN GO BACK AND GO TO ADVANCED AND CLEAR DALVICK CACHE. NOW YOUR READY TO FLASH. GO TO INSTALL ZIP FROM SD AND FLASH YOUR ROM. FIRST BOOT ALWAYS TAKES LONG AFTER FLASHING A NEW ROM :thumbup:
Click to expand...
Click to collapse
This is the process as I understand it and as stupid as it sounds, I'm hung up on where in phone storage to place the zip file of the rom. I don't see a storage folder, an SD folder, nothing that seems obvious and nothing that is in any of the things I've been reading or watching.
deblas66 said:
Been posting on the internet for decades, don't worry about being mean. I'm here to learn. I rooted, unlocked the bootloader and installed CWM so that I could take advantage before the phone asked me to update the software to the 1.85 version.
My phone works fine now, and I did everything correctly which is what I was setting out to do. I'm in no rush to flash a ROM, but now that I'm ready I'm itching to try it out.
This is the process as I understand it and as stupid as it sounds, I'm hung up on where in phone storage to place the zip file of the rom. I don't see a storage folder, an SD folder, nothing that seems obvious and nothing that is in any of the things I've been reading or watching.
Click to expand...
Click to collapse
Plug phone into computer. When prompted, select Disk Drive. On computer, browse to your computer, open the 'disk drive', and copy the zip there. THAT is your sdcard as seen by your phone.
Pirateghost said:
Plug phone into computer. When prompted, select Disk Drive. On computer, browse to your computer, open the 'disk drive', and copy the zip there. THAT is your sdcard as seen by your phone.
Click to expand...
Click to collapse
Seriously?
Wow I feel dumb. I was looking for a sub folder or directory specifically for storage and backup.
Thanks, I think that should be enough for me to do this tonight.
deblas66 said:
Seriously?
Wow I feel dumb. I was looking for a sub folder or directory specifically for storage and backup.
Thanks, I think that should be enough for me to do this tonight.
Click to expand...
Click to collapse
Yeah, some phones you may have to drag down notifications and tap USB mode or USB connected notification (it has standard USB icon and only appears when phone attached to computer). Then tap either USB storage mode or the button to enable USB drives. Then on computer just like a thumb drive it adds drive letter. Copy anything there that is /mnt/sdcard or /sdcard on phone. BE SURE TO EJECT DRIVES BEFORE AND TAP TO DISABLE USB ON PHONE IN THAT ORDER THEN UNPLUG FROM USB (failure to do so COULD result in data loss or corruption which you DO NOT want to happen to a ROM zip)!
Then boot in to recovery choose install zip from sdcard (not apply update from sdcard) as install from allows you to browse for any zip and install. Usually Vol up and down moves through menus and power or search button is enter. BE SURE THE ROM YOU DOWNLOAD IS SPECIFICALLY MEANT FOR YOUR DEVICE OR YOU COULD EASILY BRICK YOUR DEVICE. PLEASE REVIEW HOW TO RUN NANDROID BACKUPS AND RUN ONE BEFORE INSTALLING A DIFFERENT ROM.
I CAN NOT STRESS ENOUGH IF UNSURE DON'T PROCEED, BE SURE YOU RUN NANDROID BACKUPS AND ENSURE YOU FOLLOW INSTALL DIRECTIONS INCLUDED WITH YOUR ROM. ALSO, NEVER FORMAT EMMC (AKA INTERNAL SDCARD) IT ALMOST GUARENTEES A BRICKED DEVICE.
Sent from my SGH-T989 using Xparent Green Tapatalk 2
Wow that was easier than I thought.
Thanks for the help guys and sorry I missed such an easy step.
ROM installed.
deblas66 said:
Wow that was easier than I thought.
Thanks for the help guys and sorry I missed such an easy step.
ROM installed.
Click to expand...
Click to collapse
Is all good, and now you see why we were kinda scratching our heads wondering what was up a little . Glad we could help get you going though welcome to the world of custom ROMs. Please just be careful and always do backups and take it slow and read things 2x before even attempting once. While it can be easy to do it is also easy to accidentally brick your device (make it not work and have to be sent out for repairs).
Sent from my SGH-T989 using Xparent Green Tapatalk 2