Ok, I've been reading around on the forums here, and did a ton of research in the best way to set up my gTab before I even got it. I like to think I am not a n00b, but someone correct me if I come across as one.
I was running vegan 5.1 with no issues up until yesterday. Yesterday, I got the dreaded boot loop. Looking around, it seems the most popular answer to this is to repartition. But here is my first question:
(1) in my pre-purchase research, I came across this issue a lot, and so I made sure to repartition right away. since I've partitioned the recommended way once already, does this eliminate repartitioning as a potential solution to my issue?
NVFlash seems like the next most popular solution. In researching how to do this, I came across several references to backing up your data, etc. It appears I can go into clockwork and mount my device via usb (haven't tried it yet, sorry, my bad) to do this. I didn't however find any reference to exactly what I would want to back up. I did a backup in cwm .. so my next question is:
(2) should I pull the cwm backup files? if so (and if not), which files exactly should I be looking for? just stuff in the \data folder? and would I just copy them back onto the gTab after flashing?
Again, sorry if I am coming across as a n00b, but I really have spent good amount of time searching the forums -- I am just a little confused and want to make sure I have everything right before taking either of these steps.
Thanks!
Kaz
TheKaz said:
Ok, I've been reading around on the forums here, and did a ton of research in the best way to set up my gTab before I even got it. I like to think I am not a n00b, but someone correct me if I come across as one.
I was running vegan 5.1 with no issues up until yesterday. Yesterday, I got the dreaded boot loop. Looking around, it seems the most popular answer to this is to repartition. But here is my first question:
(1) in my pre-purchase research, I came across this issue a lot, and so I made sure to repartition right away. since I've partitioned the recommended way once already, does this eliminate repartitioning as a potential solution to my issue?
NVFlash seems like the next most popular solution. In researching how to do this, I came across several references to backing up your data, etc. It appears I can go into clockwork and mount my device via usb (haven't tried it yet, sorry, my bad) to do this. I didn't however find any reference to exactly what I would want to back up. I did a backup in cwm .. so my next question is:
(2) should I pull the cwm backup files? if so (and if not), which files exactly should I be looking for? just stuff in the \data folder? and would I just copy them back onto the gTab after flashing?
Again, sorry if I am coming across as a n00b, but I really have spent good amount of time searching the forums -- I am just a little confused and want to make sure I have everything right before taking either of these steps.
Thanks!
Kaz
Click to expand...
Click to collapse
Clockwork and nvflash are 2 different thing,
for nvflash you need to power-up and hold the - of the volume, screen will show the bird then blank and it will try to load the APX usb driver on the computer. the UNIT IS MOUNTED INTO A SPECIAL TERMINAL recovery/command MODE
For clockwork you power-up and hold the + of the volume and recovery is executed, stock will simply load update.zip from the root of sdcard (internal memory), if clockwork is installed then the menu will appear and allow you to backup and restore the OS. but the UNIT IS NOT MOUNTED IN THE PC.
a full restore if the unit mean booting into recovery, restoring stock firmware following instruction from this post http://forum.xda-developers.com/showthread.php?t=861950 then installing clockwork and booting with the power-up + and restoring either your rom of choice (except for tnt lite 5.0) or your backup made previously with clockwork.
Bootloop are usually solved by wiping the partition/cache/data prior to flashing back a rom or backup.
hope this help, but there's plenty of how to already here...
...
I too had experienced "bootloop", but think I solved it through one of the threads in the dev forum. Something about formatting 2048/0 for the SD card...
Sorry I couldn't be of more help.
http://forum.xda-developers.com/showthread.php?t=865245
If your tablet bootloops…Also may be required to get market running correctly on some ROMs...
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. Then, redo steps 7-10. This erases all data on your tablet, including backups.
P00r said:
Bootloop are usually solved by wiping the partition/cache/data prior to flashing back a rom or backup.
hope this help, but there's plenty of how to already here...
Click to expand...
Click to collapse
Thanks. I am not as worried about the how-to, I can find those, I was just a little confused about what situation I am in, exactly, and which solution to use.
So, even though I've partitioned this way originally, it can still get corrupted to the point where the solution it to re-partition again..?
Related
I have a Droid Incredible Rooted using Unrevoked forever with S-Off. I have been running CM 6.0.2 for a while now and had an issue the other day with my SD card. The card died and when I put a new card in the phone got stuck in a boot loop. I tried reflashing CM 6.0.2 and gapps but I continue to get the same boot loop. I understand that you need to wipe all data but when I atempt to wipe the Dalvik Cache I get the the following message "E:Can't mount /dev/block/ (File Found)" what do I need to do to fix this. I have no phone right now and have become extremely dependent on using it for everything from GPS to MP3 player in my daily life so any help would be greatly appreciated. I have read some posts suggesting running logcat to find what error I am getting during the bootloop that is happening, but I have no idea how to do that. I think the main issue is that I cannot do a full wipe before flashing the ROM.
Please help! I don't want to chalk this up to a bricked device, but I won't be able to hold out much longer since I have to travel this weekend.
First of all, do not double post. It just clutters up the forums.
Second, you need to post this in the Droid Incredible forum or at the VERY LEAST, the Android Q&A forum. I'm not sure why people took the time to create all of the different forums around here if you guys are not even going to use them.
I'm just taking a shot in the dark here based on my experience flashing older Android phones. So do not tell me I'm wrong, AGAIN this is just an option to try:
Just boot into recovery and do a factory reset on the phone. AGAIN, I'm just going on what I CAN REMEMBER here. Use the hboot menu try a restore. Load a factory ROM onto the SD card (using your PC) and the flash it.
I don't know man, maybe I'm wrong about all of this. FACT is that I've had NUMEROUS phones that were in the same shape you are in right now and after google searching, a little common sense and READING I was able to fix the issues. There is a way to go back to your FACTORY ROM but I'm not going to waste my time doing the research for you here, it's your phone and you have access to the same information all of us do.
EDIT:
I mentioned common sense. With that being said, take a look at your own post bro.
talltubatom said:
I understand that you need to wipe all data but when I atempt to wipe the Dalvik Cache I get the the following message "E:Can't mount /dev/block/ (File Found)"
Click to expand...
Click to collapse
I assume you meant "(File NOT Found)". You are trying wipe data off of a NEW SD Card here. How do you expect it to wipe files that are not even there to start with? Make sure your battery is fully charged before doing anything with the phone also. You might think that sounds like it has nothing to do with your problem BUT it can cause boot loops on SOME devices (android and others). Reset to factory from hboot menu. SKIP THE WIPE ALL PART BECAUSE YOU HAVE A NEW SD CARD. Just get back into your phone running Android and then you can redo everything from there.
Thank you for the response.
Sorry for posting in the wrong thread, perhaps a mod could move this to a more resonable place for this question. I'm not trying to clog anythining up. If that isn't an option I'll just create a new thread over there, but like you said that would just be clutter.
First: I did not mean (File NOT Found) the error says (File Found), seems like an odd error on a Formated SD Card that is why I mentioned it.
Second: I tried going to a stock ROM and it would not flash to the device I think it was looking for the previous official ROM that was relesed for the phone and would not install since that did not exist. The one that I downloaded was when Verizon pushed FroYo for the DInc, perhaps I can find one that supports a different upgrade path.
After trying all logical steps, google searches and reading many thread regarding people who have been stuck in this situation I was not able to find anything that was helping me restore my phone, that is why i started a new thread.
Roll Tide <<<< so you won't be so upset with me
The only reason I said posting in the device specific forum or android forums would be better is because there would be more people that know how to fix it viewing your question.
I'm shooting in the dark here but have you tried flashing Clockwork again? Just putting the .zip on the new SDCARD and flashing it? I'm sorry man, I've searched and tried to come up with a good answer but I've not found THAT much. Post in the Incredible forum would probably get your problem solved. I'm not sure that there is much of a difference between deviceds when it comes to recovery but I'm sure that you will get more accurate answer over there, even in the Android section.
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...
In the main clockwork mod thread there is no mention of repartioning prior to installing a rom.
Is this necessary and why?
I came across it in another guide.
Thanks
I think it's based on the rom, so that info would be found with your rom info
I asked the same question here:
http://forum.xda-developers.com/showthread.php?t=1006012
While there was no definitive answer I think I'll partition out of an abundance of caution. It seems that many problems are solved by repartitioning and as my Grandma used to say...
..."couldn't hoit."
I can answer, to a point. We've seen that, over time, the device can get into such a state that even a data wipe or reflash does not correct problems - that's where the SD repartitioning comes in. It's kind of a last ditch effort prior to nvflashing it.
I've had to repartition my device several times - the last time I did it, it fixed the "Status 7" errors when I tried to flash new firmware. My guess is that the /sdcard was so messed up that the recovery program could not accurately read the update.zip on it, anymore.
I apologize in advance for asking what are, I’m sure, obvious questions, but I’m new at all this (started today actually).
Hardware/software state:
AT&T One X
ViperXL 3.2.7
Rooted, bootloader unlocked via this thread
Running TWRP 2.5.0.0
Flashed the boot.img that came with ViperXL, as per this post
Hboot 1.14
First, my question is how do I get the OTA update to 3.2.8? I went into settings->about and found the update, downloaded it, but when I tried to run it I just end up in TWRP. I’m guessing I need to get back to the stock recovery, is there a way to do that without erasing everything?
Second, should I be concerned with flashing radios, kernels or (I think) hboot? Will flashing any of these items erasing everything? I’m not even sure which radio I’m on, but up until today my phone has been current on AT&T.
Third, what is the "WiFi partions update"? What does this do? Ought I to have it?
I have done hours of searching, but I can’t seem to find a straight forward answer to this. If I’ve missed something and this has already been answered, a link to the post would be great and much appreciated!
Thanks for the help!!
1. The device is supposed to go to TWRP to install the update. No, nothing should be erased.
2. Sounds like you're a little too new to things to be flashing radios, kernels, and possibly even ROMs, but since you're already past that step, just tread carefully until you learn a few more things.
3. Maybe, maybe not. If you're not having any issues, don't bother. If you are have issues, try it out.
Thanks for the quick reply!
Ok, if it is supposed to go to TWRP for the update, what do I do once it’s there? All it appears to do is dump me at the TWRP home screen (options for install, backup, recover, etc..) and then does nothing.
Thanks for the advice; as long as they aren’t really necessary I’ll hold off for now on doing anything further, see if I can’t avoid breaking anything .
Well, I’m not having any WiFi issues, so I’m going to leave it like it is.
Thanks!
First I think you'll need to move the OTA zip file out of /system and onto your sd card. Use a file explorer (which has root access, I use Solid Explorer, there are also others like ES File Explorer, and Root Explorer) and navigate to /system/cache (I'm pretty sure that's where OTAs are stored once downloaded, someone correct me if I'm wrong), cut the file and navigate back to your sd card and paste it somewhere you'll remember.
Now reboot into TWRP.
Once you're in TWRP, select the wipe button, this will take you to the wipe menu. Now wipe cache, and dalvik cache. Now hit the little home button in the bottom left corner of your screen, this will take you back to the home screen.
Now you hit the install button. It will then take you to a screen which shows your sd card. Find the OTA zip file and select it. Then swipe to install. Once it has finished installing you can choose to wipe cache/dalvik again (I always do this to be safe). Then just hit the reboot system button and it should boot up into your newly updated ROM.
One thing though: you really need to do some reading, you haven't got the faintest clue about any of this obviously. You would benefit greatly from reading and actually learning about messing around with your device. Going into these kinds of things ignorantly is very dangerous, you could easily brick your phone. I'm not trying to be mean, just telling you how it is. We all gotta start somewhere, just make sure you take the right steps and get a good understanding of all this
Sent from my One XL using XDA Premium
That was what I was assuming I should do, but I was unsure if it would overwrite anything important that way. It actually seems to download the update to /sdcard/downloads (or it did that the first time I ran it). Good tip about wiping the caches though, I’ll remember that.
Turns out that I actually didn’t need to do all this after all…I deleted the OTA file and tried running it again, and low and behold it decided to work! I swear I didn’t do anything different, but I’d been messing with it for a while after I tried it the first time, maybe I changed something relevant (though I was mostly just tweaking sense to how I wanted it)
I have actually done a great deal of reading and looking around, but I’m still struggling to keep all the various version numbers and terms straight. I really appreciate the advice, and I’ll be doing more research in the future (mainly to discover what the other things that aren’t ROM’s do).
Thanks for the help all!
It wasn't showing up because turge forgot to change something. It should be showing up now.
If not just download it, flash it like normal and reboot.
No need to wipe anything
Sent from my HTC One X 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