Related
Started reading the forums a few days ago, already planning on getting a gtab for x-mas. So got one at Sears today and went home confident I would know what I am doing. Well I was wrong !!
First mistake: My assumption that this will be as easy as my SGS with clockworkmod. For one, there are apparently CWM versions floating around that are known to cause issues - hence that is the one I ended up with. It installed the CMW fine and went into recovery just like I am used to. Tried to apply the ZPAD 2.2 rom and as soon as I rebooted got the 'Magic Value Mismatch' error at the top of the screen.
Mistake two: trying to fix it by finding the correct CWM called .8 which seemed to make things worse. I got a screen now right after the power and Vol + key that shows alternating black and white strips.
I had this thing only for 3 hours and I already managed to get way past my expertise on fixing this.
What can I do to get the tab to load a recovery image so I can boot?
On the internal SD card there is the folder called 'recovery' with the command file that points to the update.zip on the external sd card. I imagine that is correct. However it did not matter what ZIP file I place on the SD card. For example I renamed all the exising rom's one by one to update.zip to see if one of them would take and no luck.
I am sure someone with more experience can point me to how to get back to normal. I would appreciate some help.
Try This
I had a similar issue with mine about 30 min after I got it. Use your external SD and but the vanilla tnt update.zip and the recovery folder on it. Edit the command file in the recovery folder to say sdcard2 instead of sdcard. This worked for me , Good luck
Thaks for the info.
I created the recovery folder with the command file this time on the external SD card (preped this on the PC) and made sure the vanilla update.zip was on the root of the SD card.
I got a new error about a kernal having a critical error, but I was so frustrated that I did not write it all down.
Then I tried another rom (gtab lite 2.2) and I get the Magic Value Mismatch error again.
It seems like it does not even attempt going into recovery now, because it does not matter if I press the VOL+ and PWR key together. It has the same effect as if I press PWR alone.
I really don't want to give up just yet. If anyone else has any suggestions I am willing to try, plus this experience might help others in a similar situation down the road to recover instead of having to return the device.
I saw a post about some PC based update, but I also seen comments that that could make things even worse. Any ideas?
In the mean time I followed the NVFlash instructions and there is some success and also some loss.
The success is that I no longer get the "magic value mismatch" error. The loss is that my tablet still does not boot and now I have a Nvidia boot screen which will most likely raise a flag with Sears when I return it for an exchange.
I don't want to give up yet, but I really could use some pointers on what else to try.
Here are the instructions I followed for the NVF...
http://wiki.tegratab.com/index.php/ROMs
and
http://forum.tegratab.com/viewtopic.php?f=6&t=8
and
http://forum.xda-developers.com/showpost.php?p=9575351&postcount=26
All I get is the Nvidia logo. The tab has been on for more than 10 min and there is no change.
anosis said:
In the mean time I followed the NVFlash instructions and there is some success and also some loss.
The success is that I no longer get the "magic value mismatch" error. The loss is that my tablet still does not boot and now I have a Nvidia boot screen which will most likely raise a flag with Sears when I return it for an exchange.
I don't want to give up yet, but I really could use some pointers on what else to try.
Here are the instructions I followed for the NVF...
http://wiki.tegratab.com/index.php/ROMs
and
http://forum.tegratab.com/viewtopic.php?f=6&t=8
and
http://forum.xda-developers.com/showpost.php?p=9575351&postcount=26
All I get is the Nvidia logo. The tab has been on for more than 10 min and there is no change.
Click to expand...
Click to collapse
My nvflash won't help you, at this point. You want bekit's nvflash recovery -- http://forum.tegratab.com/viewtopic.php?f=6&t=8 I know you used mine because you have the Nvidia logo.
The difference between bekit's recovery and mine is that bekit's flashes EVERYTHING, at a low level. Mine isn't that extensive. You definitely want to try Bekit's flash before throwing in the towel.
As for SEARS, I wouldn't worry about it - they probably won't even notice. When I returned my first one, they didn't even open the box. Seriously.
roebeet said:
My nvflash won't help you, at this point. You want bekit's nvflash recovery -- http://forum.tegratab.com/viewtopic.php?f=6&t=8 I know you used mine because you have the Nvidia logo.
The difference between bekit's recovery and mine is that bekit's flashes EVERYTHING, at a low level. Mine isn't that extensive. You definitely want to try Bekit's flash before throwing in the towel.
As for SEARS, I wouldn't worry about it - they probably won't even notice. When I returned my first one, they didn't even open the box. Seriously.
Click to expand...
Click to collapse
The link you provided (I already went there before) had a link inside to download the necessary fiels but all it did is link to the main forum page. I never was able to find the correct files until this morning I believe. I found another post on these forums that had 'dropbox' links to several files that I downloaded.
So now I ended up with 1) the Tegra MSI installation file 2) the g tab image files and 3) the windows script files with the batch file. I will attempt these tonight and report back.
We are in the middle of moving - finally home owners again at last ;-). I have no internet connection at my new house yet however my SGS and tethering are my friend right now, so I can post and download at a lower rate.
Thaks for the help!!
I wonder what came of this! A feedback would be nice.
Thanks!
i would guess roebeet's suggestion worked, otherwise anosis would've been back on here.
oshea85 said:
i would guess roebeet's suggestion worked, otherwise anosis would've been back on here.
Click to expand...
Click to collapse
No PM's to me, yet. I take that as a good sign?
roebeet said:
No PM's to me, yet. I take that as a good sign?
Click to expand...
Click to collapse
I believe you deserved a big thank you instead!
Thank You!
I don't know about the other guy, but I borked the Tab tonight, and these instructions worked flawlessly. The links to the apps were stale, but the IRC channel pointed me in the right direction.
Now back to to the Tablet to find out what I need to put back on it.
Thanks again!
can you tell me where to find those links? I screwed mine up too.
professor03 said:
can you tell me where to find those links? I screwed mine up too.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=861950
Saved my bacon!
This thread was awesome! Pulled my ace out of the fire when i accidentally wiped out CWM when trying to format to install a new VeganTab. You guys rock!
Hooray!
Sorry to bump an old thread guys, but I just wanted to chime in and say this also worked for me. Someone should add this to the stickied threads...
rogersranch said:
Thank You!
I don't know about the other guy, but I borked the Tab tonight, and these instructions worked flawlessly. The links to the apps were stale, but the IRC channel pointed me in the right direction.
Now back to to the Tablet to find out what I need to put back on it.
Thanks again!
Click to expand...
Click to collapse
Hi,
I am just wondering if you can provide a more detail instruction on how this can be fixed? I am a new android user, I am not very knowledgeable. If you can provide some more information, that would be greatly appreciated!
I beleive what you are looking for is in the link posted.
http://www.slatedroid.com/topic/177...recovery-pack-cwm-standard-recovery-g-tablet/
mismatch is good
I finally did the nuclear option to get my tablet back. I was in the dummies site when panicking as well, read mismatch was to be a welcome...
Found this in my TnT site scan:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3991-user.zip
Build date is 2/12, and it's still Froyo. It looks like a lot of stuff was touched, perhaps they incorporated some recent Nvidia libs.
EDIT: They have a Flash player script in here - that's new.
EDIT2: So far, this update has competely borked my device. It's the bootloader or boot.img, so just keep that in mind. It could be that my device is all messed with all the recent flashing, but just be aware.
EDIT3: In case this is not already clear, this is a VERY dangerous update. Tread carefully - it requires stock 3588 as a baseline, including recovery.
3/28/2011 EDIT: Looks like Viewsonic pulled it (a case of the Woot! heebie-jeebies, perhaps?)
Sry to hear about your device. Hopefully you can figure it out. Bricked a phone before and took me a few weeks before I accidentally fixed it, lol.
As for the tnt update does this mean we may see another viewsonic ota update finally? Matbe they finally resolved the sluggishness issues and tntui will finally be usable
I got around the issue with using an older boot.img and bootloader. One (or both) are causing issues with my system.
They added a lockscreen - that will make some people very happy.
How did you get around this. I tried this update and it borked my device as well and I can't get past the viewsonic boot screen or load clockworkmod to boot the recovery kernel
xdadev69 said:
How did you get around this. I tried this update and it borked my device as well and I can't get past the viewsonic boot screen or load clockworkmod to boot the recovery kernel
Click to expand...
Click to collapse
I used nvflash - I dropped the old bootloader and boot.img in there and ran it with that, and it booted up.
EDIT: I couldn't get wifi working for Quadrant, but Nenamark is ~40fps. My guess is that they updated a lot of the libs so that they in up-to-date with recent Nividia changes.
EDIT2: Camera is working, including rotation. Gsensor is still off for games, but that's not a surprise.
Thank god for nvflash. I thought I seriously boned myself today installing this new UAT version. I flashed back to stock, reinstalled clockworkmod, and then was able to get back up to TNT lite 4.2.4.
While I am posting, I would like to thank all the Devs for their time and efforts making these ROMS and instructional posts. Without your efforts this tablet would seriously blow donkey balls. I actually bought the G tablet with the full intention of getting rid of the stock ROM and unleashing the full potential of the underlying hardware with the ROMS here.
Thanks again
This is not bad at all, I forgot how nice the weather dashboard looked because I was too busy cursing this thing for being sooo slow. I remember the first day I got this thing, I couldn't even stand to use it. It was so frustrating. You,gojimi and rothnic did an amazing job to get this tab where it is today. I think viewsonic even "borrowed" some of you guys work, lol.. Thanks Again for you guys work!
UPDATE: I went completely stock before this update, (no clockwork mod) this new update 3991 looks like it has a built in recovery menu. I don't remember that on older versions
what were you running prior to returning to stock?
lsu205 said:
what were you running prior to returning to stock?
Click to expand...
Click to collapse
vegaN 5.1.1
aver2one said:
This is not bad at all, I forgot how nice the weather dashboard looked because I was too busy cursing this thing for being sooo slow. I remember the first day I got this thing, I couldn't even stand to use it. It was so frustrating. You,gojimi and rothnic did an amazing job to get this tab where it is today. I think viewsonic even "borrowed" some of you guys work, lol.. Thanks Again for you guys work!
UPDATE: I went completely stock before this update, (no clockwork mod) this new update 3991 looks like it has a built in recovery menu. I don't remember that on older versions
Click to expand...
Click to collapse
I hadn't looked at their recovery - very nice. They are emulating what Notion Ink had done on their recovery.
This is going to be a nice update, once they shake out the bugs.
Here's a screenshot of the lockscreen, using the "classic" launcher:
Looks good, I like the changes.
2400 in Quadrant - and that's 3991 "stock", no changes. Normally stock is ~1900, I think.
I managed to get Wifi working by downleveling the Wifi drivers - that was needed to use the older kernel. I just don't understand why their new kernel doesn't work for me.
roebeet said:
2400 in Quadrant - and that's 3991 "stock", no changes. Normally stock is ~1900, I think.
I managed to get Wifi working by downleveling the Wifi drivers - that was needed to use the older kernel. I just don't understand why their new kernel doesn't work for me.
Click to expand...
Click to collapse
Wow looks like that next update is going to be great!
Btw I was averaging @1700 quadrant score earlier today stock before I went up to 3991
roebeet said:
2400 in Quadrant - and that's 3991 "stock", no changes. Normally stock is ~1900, I think.
I managed to get Wifi working by downleveling the Wifi drivers - that was needed to use the older kernel. I just don't understand why their new kernel doesn't work for me.
Click to expand...
Click to collapse
Looks/sounds very nice roebeet...can't wait for the push over OTA...I actually just went back to stock a few hours ago to mess with the enhancement pack with the January OTA update...it's actually fairly quick compared to the original stock...think I'll stick with it for a bit
I'm guessing that since it's a non-published update, then they may have an incomplete boot.img or possible they had to update the bootloader, who knows...could also be a "built-from-scratch" update that they are still working on, lol...doubtful but you never know
Good luck and here's hoping for an official push from Viewsonic here soon. The sooner they get this out, the sooner they can get to working on an official Viewsonic release of HC ;-) lol
Wow, that update is great! Though, sorry to hijack the thread, but I got no replies elsewhere, anyone had the "blank screen of dead" issue? I stop using my gtablet for a couple of weeks, and now that I boot it up again, the screen is white! (not even the VS birds..).
Keep pushing updates for us =)!
Thanks
pmcnano said:
Wow, that update is great! Though, sorry to hijack the thread, but I got no replies elsewhere, anyone had the "blank screen of dead" issue? I stop using my gtablet for a couple of weeks, and now that I boot it up again, the screen is white! (not even the VS birds..).
Keep pushing updates for us =)!
Thanks
Click to expand...
Click to collapse
Do you have a Backup in clockwork mod? Do you have clockwork mod?
aver2one said:
Do you have a Backup in clockwork mod? Do you have clockwork mod?
Click to expand...
Click to collapse
Yea, but again, thats not the issue. Theres nothing in the screen, not even booting to recovery, the screen is white, theres a thread about it, someone reported the same problem, I asked what happened to it, but got no reply! D:
Thanks
pmcnano said:
Yea, but again, thats not the issue. Theres nothing in the screen, not even booting to recovery, the screen is white, theres a thread about it, someone reported the same problem, I asked what happened to it, but got no reply! D:
Thanks
Click to expand...
Click to collapse
If you can't boot into recovery have you tried nvflash?
pmcnano said:
Yea, but again, thats not the issue. Theres nothing in the screen, not even booting to recovery, the screen is white, theres a thread about it, someone reported the same problem, I asked what happened to it, but got no reply! D:
Thanks
Click to expand...
Click to collapse
You may want to head over to the development forums and check out the nvflash thread by roebeet...sounds to me like you'll need it. Good luck.
Question for you roebeet...how stable is this? Just wondering if I should even attempt to install it. Let me know what you think and thanks for all the hard work.
Found this in my TnT site scan:
http://tapntap.http.internapcdn.net/...-3991-user.zip
Build date is 2/12, and it's still Froyo. It looks like a lot of stuff was touched, perhaps they incorporated some recent Nvidia libs.
EDIT: They have a Flash player script in here - that's new.
Is there an enhancement pack with this, or is it available, even ?
Great men do great things.... like our developers! Thanks guys ALL OF YUU!!!
Forgive me if I'm posting in the wrong section. Forgive me if I'm not allowed to post here yet. Just forgive me in general. I don't want to be banned or anything like that. I'm Extremely interested in android development.
I made a working port of ClockworkMod Recovery v5.0.2.8 for the Pantech Crossover. I wanted to do this before I started tinkering around with porting cm7.2. So that I would have a way to backup, restore, and flash new roms, etc... Or else when I make a noob mistake like yesterday and have a non booting phone resulting in having to flash my old boot.img with fastboot...anyways..
DANGER: DRAGONS AHEAD
FLASH AT YOUR OWN RISK
YOU HAVE BEEN WARNED
The method I used to flash the recovery was:
1)adb push recovery.img /sdcard/recovery.img
2)flash_image recovery /sdcard/recovery.img
3)repeat step 2 (for some reason it gave me a read error out of memory the first time)
Here's the link to the custom recovery:
http :// dl. dropbox .com /u/20070520/ recovery.img
I know I'm not supposed to post links yet. Remove spaces
I just hope that there are others with the Pantech Crossover that are interested in this and the possible future development of custom roms.
Also if anyone knows if there is a good way to get ahold of koush let me know, so I can give him what he needs to hopefully add this to Rom Manager. I couldn't message him on github because he doesn't have an email set up with it
And while I'm at it. Here's the method for rooting your crossover. I'm not going to provide the files since they can easily be found with a google search.
1: Find a copy of gingerbreak.apk and copy it to your sd card
2: Enable usb debugging and allow installation of non market apps
3: Install gingerbreak
4: Root device with Gingerbreak
5: You can uninstall Gingerbreak when its completed.
Sent from my rooted PantechP8000 using XDA
Thanks so much for this! I have a friend with a crossover and is always looking for my help with making it work better. I realize this is a newer thread, I was wondering how things were coming along with CM? Anything I can do to help perhaps?
crap i need a rom to fix my crossover the buttons are no longer mapped after a hard reset. please help.
Slow
Well, it's been slow goings so far. I downloaded the open source files for the p8000 and it looks like they just built the original rom from a generic build. I've been trying to get a more customized build setup but I need to do some more reading so far. One of the problems is that instead of an akmd(2) binary for orientation and compass it uses three separate modules. Plus the hci_attach is a bit different as well and so is the bluetooth. So that significantly hampers the ease of even a basic port.
As far as the gentleman with the question about a rom to fix your device. The best I can do right now is to upload a clockwork mod backup after I do a factory reset. I don't get much time to work on this between my wife and daughter.
Also, do you have adb access to your device? Surely it wouldn't be too difficult to adb push the correct keymapping files back to your phone.
You say a hard reset messed up your mappings? What problems were you experiencing prior to the reset?
Crossover
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Yup
kaylus said:
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Click to expand...
Click to collapse
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
stevotdo said:
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
Click to expand...
Click to collapse
I'm actually completely stuck at this point. I'm rooted, unlocked, different carrier, APN set correctly. I can access data and voice -- but it just hangs at "Downloading..." on the market. If I factory reset it works initially but after reboot it fails. I'm not quite sure why this occurs and if it is just this phone or a side-effect of using it on a different carrier.
Strangely Wi-fi doesn't resolve it.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
Click to expand...
Click to collapse
I'll give your recovery a run and let you know, if you manage CM7 let me know I know it's a big undertaking. Thanks for the response.
Market Error
As far as the Android Market hanging. I see a few references to it being cause by the .android_secure folder becoming corrupted on the sd card.
One temporary fix suggest moving all the installed apk's back to the phone memory and deleting the .android_secure folder. Then rebooting and moving those apps back to the sd card.
That seems like some wasted time if it doesn't happen to work. I would just turn the phone off, remove the sdcard, and restart (granted any apps that were moved to the sdcard wont work until it is reinserted.) Then I would try to download and install an app. If that works then shutdown, insert sd, and reboot.
I'm really curious if the problems with .android_secure that you and i are having aren't just more bugs in the original rom.
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Well I appreciate the support. I just hope to be able to offer a rom sometime soon. Unfortunately I won't have anymore free time till Tuesday
crimson12 said:
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Click to expand...
Click to collapse
Not an issue, life first, then android development.
Sent from my Galaxy Nexus using Tapatalk
Pantech Crossover Update
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
stevotdo said:
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
Click to expand...
Click to collapse
Oh hell yes finally. Thanks for the notice!
Sent from my Galaxy Nexus using Tapatalk
Mildly related, but have you figured out how to root the gingerbread ROM? I've tried ginger break to no avail.
Sent from my Galaxy Nexus using Tapatalk 2
anyone have a stock image of the 2.2 for android my phone came preupgraded to 2.3.6 and i would like to have it rooted over being on gingerbread since a root method hasnt been found yet for the new firmware
Bricked?
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
formattdd said:
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
Click to expand...
Click to collapse
Nevermind, bad usb cable.
formattdd said:
Nevermind, bad usb cable.
Click to expand...
Click to collapse
Glad you got it working!
Sent from my Galaxy Nexus using Tapatalk 2
Yeah now I'm having the same regrets as above. No root.
Sent from my PantechP8000 using XDA
Sooo it seems I have now bricked my beloved G2x. I have tried every recovery method on xda I can find (a few times), but still no luck.
I was trying to restore stock on my phone to catch the new OTA update, and it has failed...miserably.
Now, my phone gets to the little T-Mobile G2x splash screen and then reboots. I've tried NVflash'ing the firmware, I've tried kdz (which I absolutely cannot get to work right), I've tried sacrificing a chicken to the LG powers-that-be (okay, haven't tried that...YET), but nothing has worked.
Does anybody know of an absolute "unbrick" method?
Thanks in advance for the help!
Also, every now and then, the phone will actually make it to the initial "Touch the android to begin." screen, but my battery (which was 100% charged before this started) now says 0%, even when plugged in.
these links were in the first page of me searching "brick help"
http://forum.xda-developers.com/showthread.php?t=1611968&highlight=brick+help
http://forum.xda-developers.com/showthread.php?t=1180331&highlight=brick+help
http://forum.xda-developers.com/showthread.php?t=1619893&highlight=brick+help
I've tried those methods, and almost every other I could find. I've searched this forum for hours today before posting this, and no matter what I use, I get stuck in either a bootloop or i get a reboot after a minute of being booted. I've tried different recoveries, different ROMs, different flashing methods, and it all ends up the same way.
if you've actually tried things you might want to post exactly what you have tried what were the outcomes and so on and so on. I'm not going to assume what you have tried and assume what the process you did and where you might have messed up. I'm sure neither is anyone else. So unless you help me help you we together are not going to get anywhere.
To the best of my recollection, here's how it went down:
Started off with running Genesis v1 Beta 6.
Ran G2x batch clean up tool w/ CWM Touch
Flashed cyanogen_p999-ota.eng.feli.zip in CWM
* At this point my phone would not make it past more than 1 minute after booting. It would boot up, but after approx. 1 minute, it would reboot, no matter what I did w/ it. This happened several times
Wiped everything through CWM, flashed Genesis again (default install)
*Had same reboot issues listed above
Used NVFlash to push stock V21e firmware http://forum.xda-developers.com/showthread.php?t=1248644
*After this, My phone would not make it past the "T-Mobile G2x with Google" splash screen. You would hear the T-mobile jingle, then the screen would "get stuck" for about one minute, and then the phone would reboot and go through the LG logos to the splash screen and repeat endlessly until I performed a battery pull
Restored stock recovery using NVFlash
*Did a reboot and suddenly saw the boot animation from Genesis!? Not sure how that happened, but it never made it past the boot animation
Ran G2x batch clean up again to try to "clean" the phone, and pushed the V21e firmware again
*Same boot problem
Flashed stock recovery again, then attempted to use KDZ. KDZ will continue to force close midway through the operation, and I cannot get it to work
Pushed V21e yet again
*Now it started making it to the initial set-up "Touch the android..." dialog. I could actually make it through this part, and then the phone would reboot again
*Somewhere in the middle of this, my battery went from reading 95%(The few times it would actually boot) to reading 0%. I wiped battery stats in CWM, but it didn't fix it. "Hey, maybe my battery actually died," I thought, so it's now on the wall charger, waiting for me to try to rescue it again.
I'm going to *attempt* to install a nandroid in CWM, and pray that it fixes things, but if that does not work, I'm at a complete loss
mt3g said:
if you've actually tried things you might want to post exactly what you have tried what were the outcomes and so on and so on. I'm not going to assume what you have tried and assume what the process you did and where you might have messed up. I'm sure neither is anyone else. So unless you help me help you we together are not going to get anywhere.
Click to expand...
Click to collapse
+1
More info would be great!
If I were you, would give a shot of mansa_noob's clean up tool:
http://forum.xda-developers.com/showthread.php?t=1590523
It will reorganize your partitions. Then you just need to flash CWM recovery, then the stock ROM.
Edit:
Just saw your new post, wow that's interesting. I'm not too sure if the touch CWM has anything to do with it, how about to try the normal recovery version of the clean up tool, then maybe a different stock ROM?
Sent from my LG-P999 using xda premium
the only thing I can think of will get me flamed lol, don't use those clean up tools unless it is a last resort! I can say I've never had an issue with just flashing after going through mounts and storage (data, system,cache) and wiping the main things.
The fact that the phone can be booted and it is showing images on the screen means you are not bricked. On the other hand, I've yet to read the issues you are describing, ever. You got quite mess on your hands.
KDZ is your best bet, what do you mean it just "continues to force close"
DupleX01 said:
+1
Just saw your new post, wow that's interesting. I'm not too sure if the touch CWM has anything to do with it, how about to try the normal recovery version of the clean up tool, then maybe a different stock ROM?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Tried CWM 5.0.2.0, also. I've tried both the stock ROM and the basic cyanogen ROM (Sorry, can't remember exactly where in the cycle those fell...I've repeated several steps several times)
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
that is crazy lol, but glad something worked for you...
mt3g said:
the only thing I can think of will get me flamed lol, don't use those clean up tools unless it is a last resort! I can say I've never had an issue with just flashing after going through mounts and storage (data, system,cache) and wiping the main things.
The fact that the phone can be booted and it is showing images on the screen means you are not bricked. On the other hand, I've yet to read the issues you are describing, ever. You got quite mess on your hands.
KDZ is your best bet, what do you mean it just "continues to force close"
Click to expand...
Click to collapse
Hey buddy. I won't flame. You are absolutely right. I don't use the cleanup tool a lot either but then since my bluetooth issue is fixed I am slacking .
I am curious though why it did not work but will respond to op in a minute.
Sent from my LG-P999 using XDA
rtotheichie said:
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
Click to expand...
Click to collapse
I am afraid if my theory is correct your flash (memory) may be going. The symptoms you have described and the fix you mention would suggest a data retention problem. If it breaks again (i hope that I am wrong and it won't) you may have to stick it in the fridge again but if that happens get rid of it fast!
Sent from my LG-P999 using XDA
rtotheichie said:
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
Click to expand...
Click to collapse
Yet another proof of G2X's unbrickable fame with a happy ending.
Happy for you!
Sent from my LG-P999 using xda premium
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
dfarquhar said:
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
Click to expand...
Click to collapse
Look here for 1.3.1.
dfarquhar said:
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Click to expand...
Click to collapse
Nope, not a CWM issue. Ever since TeamAcid and I started on CM9 (and I believe the last few CM7 builds) added support for T959W. Almost everyone (thankfully! ) has kanged those device trees and also support T959W. I'm sure other T959W users will chime in to tell you that 97% of all roms here work on T959W. (GB and forward)
dfarquhar said:
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
Click to expand...
Click to collapse
Crazy mount setups shouldn't matter anymore. That was an oldschool Froyo/Early GB thing. Almost all new CWM install scripts do the right thing now.
dfarquhar said:
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
Click to expand...
Click to collapse
I like the long posts! Especially when then they contain more detail for me to help you figure out your problem with. I'm also partial to the short posts that include logs!
TwitchyEye said:
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
@TwitchyEye you're right That is the heimdall oneclick that should be used.
@dfarquhar I think using the heimdall oneclick that @getochkn made should be the right path for you. Make sure you use the right version of heimdall. Make sure you completely remove the old version (software and drivers), use zdiag to make absolutely sure!
If all else fails, post here again! (maybe with logs )
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
dfarquhar said:
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
Click to expand...
Click to collapse
Sometimes, it's just the output you see on your screen is a good enough log
bhundven said:
Sometimes, it's just the output you see on your screen is a good enough log
Click to expand...
Click to collapse
Got it working! Heimdall 1.3.1 was the key. I then turned around and flashed Slim ICS since I had it on the SD card already, and it worked. I'm debating whether to move on to Slim Bean, but maybe I need to leave well enough alone for a few days now that I have a working phone.
Thanks again,
Dave