Related
Made a huge error.....didnt go through forums and read instructions before trying to Flash a German T-Mobile MDA Compact to a English ROM....
The device is completely dead....
Followed all the steps required to get it back up...It is refusing to do so though....
Used this thread:
http://forum.xda-developers.com/viewtopic.php?t=19500
One thing to note is that I am not using the AC charger, am using the USB cable to charge the phone.
Can someone please helpme...
Haven't got past the bootloader mode...
If you followed the instructions from the other thread, it should have started flashing.
Some things to check on:
1) Did you do a full d2s before you attempted the upgrade? It's always good to have something to fall back on.
2) If you can get to a bootloader screen, all is definitely not lost.
3) Sometimes, it takes 4 or 5 minutes for the "Press to flash" comes up on the screen so be patient with that.
4) Make sure you did exactly a 416 byte copy from the original rom file in to the new flash file.
5) You can only write an nb1 file from the pc AFTER it has been created from the pocket pc. If the SD card has been pc formatted, the nb1 file will write to it but the pocket pc won't recognize it and will just sit there at the bootloader screen.
HTH
I think I fired the MDA
Well I did not create the nbf file from the ppc, downloaded it from the the forum FTP. I do not have the backup of the nbf file. As I mentioned I did not read the forums before trying the update.
I just downloaded the T-Mobile ROM update and tried installing it. Obivousioly it didn't work, Game the dreaded the 112 error in the 3rd step.
Am not even getting the bootlader screen now..
Any ideas on how I can get this device up and running.?...
ok, need some clarification here. "What" are you trying to load (nbf files or nb1 files) and how are you trying to load them (SD flash or the standard USB based upgrade)?
Easy enough to check to see if your device can still get to bootload mode....hold the camera and power switches in at the same time and hit soft reset with your stylus. After letting go of those and you see either "Serial" or "USB" at the top of the screen, you should still be able to recover from this.
Tried with the nb1 files not nbf (sorry abt teh error)..
The bootloader screen was showing up ...unitll I tried the T-Mobile MDAcompact_vers11201
After the 112 error while updating...the device now refusing to get to the bootloader mode.
Have I fried the device and made it unusable....?
hey just got back the bootloader screen...
Take the SD card out, disconnect the USB and tell me what happens when you hold the power and camera buttons in at the same time, then hit the soft reset.
Also, has the unit been charged recently?
Its showing Serial v1.00...after the reset.
Its been on the USB chatge all along.....
Great. If you get Serial at the top, this can be recovered.
If you want a good T-Mobile 1.12 rom file, go here and use this one:
ftp://ftp.xda-developers.com/Uploads/Magician/tmobile-uk_wwe_ROM_1.12.00(thereapermanl).rar
Unpack it and follow all the procedures about copying the 416 bytes, rewriting the file, etc. from the other thread. I have tested this rom file and it installs ok.
Thanks for the encouraging words...
Will it work even if I do not have a backup of the original ROM on my machine?....I only have the tmobile.nb1 file which I got from the XDA forums.
Lemme try using that and editing it.
Thanks a ton for your help.
You might be a little stuck for an nb1 flash if you don't have an original flash back up but don't fear. You can go here and get this WWE1.12 file and just do a USB type upgrade:
ftp://ftp.xda-developers.com/Magician/Shipped_ROMS/WWE_11200_128_11210_ship.exe
I know this one works too. It's ROM 1.12, Radio 1.12 and Ext_ROM 1.12. When you try to run the upgrade program though, it might give you a Country ID error. If so, use the attached upgrade program instead. If this one gives you a Country ID error again, close the program and just run it again. I've been down all these roads already.
Lemme get this right this time: I will be doing the following
1. Install the ROM as you have mentioned. With the country id hack if necessary
2. Hopefully by now the device would be alive. If so will take a backup of the ROM on the SD card
3. From then on follow the instruction given in the doc.
Hope I get it righ this time else Its going to be a long night for me.
Lemme know if I have to do anything else.
Either ROM will work fine for you. It just depends on whether or not you want I-Mate stuff on it or T-Mobile stuff on it.
Doing the USB upgrade will put the I-Mate ROM on but after that, it should be working and you can then do an SD backup, follow the SD flashing procedures and get the T-Mobile ROM on.
Good Luck!
The masupgrateut is throwing up a ruu.dll error?...you seen that one before?
What sort of error? Not found?
yup...
I extracted the ROM exe and found teh file...copied it to the windows folder..and ran the no id program...no error this time round but the update is still giving a COuntry ID error...
Been looking at various posts...specially this one...
http://forum.xda-developers.com/viewtopic.php?t=14973
Thinks thats gonna help?
ok...two things.....just run it again. The no ID program sometimes does that on the first time 'round so just run it again.
Second, stick this at the end of the RUU.conf file:
[CHECKCEID_TYPE]=1
ran the program multiple times...still getting the COuntry ID error...
Are you running this program? MaUpgradeUt_noID.exe
...with the change in the RUU.conf file?
I just noticed something....did you extract all the files to a single directory and just run it from there or did you just pull a few out?
ALL the files have to be in the same directory. This is also where you need to execute the installer program.
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.
I have a My Touch 4G currently running 2.3.4 that I want to downgrade to 2.2.1 so I can root it. I am unable to get it to take the PD15IMG.zip to take once I hit the bootloader. It says its extracting fine, but the phone never reboots and if I manual reboot it, it boots up on 2.3.4.
I was using the following instructions.. cyanomod instructions and I did everything fine but get stuck with step 8.
Here is a copy of my ABD session:
Open to any suggestions.. I did some searches but no luck.
I tried to paste the URLs for the pastebin and the instructions I used but was blocked because of the stupid spam rules for newbies.. so PM me and ill send them to you.
Also as you can see I have been a member for over a year now, I just do a lot of lurker so I don't post much. I usually can find my answer searching without asking but I am stumped on this one.
This exact same thing happened to me.
The problem was that ADB wasn't pushing the entire PD15IMG file to the SD card. Every time I tried it it was missing exactly 53 bytes. (You can check this by looking at the file size of the PD15IMG on your hard drive and see if it file size matched EXACTLY on your SD card down to the single byte.)
I fixed it my using the file manager on my computer to just drag and drop the PD15IMG file onto the SD card. For some reason that transferred the entire file without problem.
I ran through the steps again and viola, 2.2.1 upon reboot.
You might also have a corrupted PD15IMG file. You can fix that by re-downloading the file, preferably from a different source just in case.
why u need downgrade 2.2.1 ?
@skipjacks - ill try that, on the 2nd attempt at it yesterday I manually copied of the file over after I downloaded it from another source, yet it still would not upgrade. I will give it a 3rd shot and report back.
@Ridofu - I am tried of having the HTC offical software crashing on me. I would like to root and then install CM7.1
Same thing..
I downloaded PD15IMG.zip manually over the HTC E:\ drive I have mounted.. did all the commands again, went to bootloader, it says it installs but then never reboots or does anything...
the image say loading, and I see a blue bar on the right top corner... then it switches to checking with a yellow/orange bar in the right top corner..
then it just goes back to the main screen and doesn't do anything..
all i see is fastboot, recover, factory reset, simlock, image crc
Id love to run the adb shell md4sum /sdcard/PD15IMG.zip but everytime I run it it comes back with md5sum: not found
Any ideas?
How I rooted my MT4G
Try this guide:
http://androidrootking.blogspot.com/2011/10/how-to-root-your-mytouch-4g-original_12.html
This is a step-by-step guide to root your MT4G. It has a link to another guide that will help you downgrade your phone.
You must downgrade FIRST, in order to root, because the root tool (gfree) DOES NOT WORK with Android 2.3, it only works with 2.1.
If you really like GingerBread, and want to keep root, go here AFTER you're rooted:
http://forum.xda-developers.com/showthread.php?t=1264704
—E!
Do you have MicroSD card reader in/for your PC?
Try to use it instead of copying the file through the phone.
@Ericm301 that is the exact method I have followed and it does not work. I have done the Push method, I have done the copy via USB cable to the E:\ drive that is mounted and neither allow me go to bootloader and load the file.
@Jack_R1 I will try getting a Micro usb adapter and copying the file over as well.
I tried taking the SD card and copying the file manually, I also tried to use the file from a 3rd source. It will not downgrade. I can post a video if you want to see it fail.
Just wanted to give a update. I did the manual downgrade 2 or 3 more times and I finally gave up on it.. then I switched to Fastboot Downgrade method and it worked perfectly the 1st time..
man what a frustration!
First, my apologies for 1) starting a new thread regarding a question that's been asked many times, and 2) making this so long. But I've tried all the possible solutions I could find, so far to no avail.
I've been running Emancipation, and decided to upgrade to Uniporn when b38 was released. No problem running the aroma installer, and no surprises after the installation when reboot hung at Samsung logo. But when I rebooted into recovery, the screen was distorted and most illegible.
I quickly found Nunhugger's instructions to Odin ICS Recovery. Not so easy on a Mac though. I tracked down the Mac port of Odin, but couldn't get it to recognize the phone. Eventually, I figured out how to install the Mac version of Heimdall, and used that to flash the zImage file extracted from the infuseICSrecovery.tar file. The Heimdall flash appeared to be successful, but it didn't fix the Recovery corruption.
I could still click through Recovery (though couldn't see what I was selecting) and was eventually able to choose to to reflash Uniporn through trial-and-error counting the number of various combinations of clicks. But got an error that the file was corrupted (don't remember exact wording of error message).
Of course I had backed everything up in recovery before trying all this, so I tried to recover from there. Uh oh, same error message. Nandroid files were corrupted, too.
Eventually, I was able to return to Emancipation after copying the file to my external card, and installing from there. Recovery was back to normal, and everything appeared to be working normally.
Confident that I hadn't bricked my phone, I tried installing Uniporn again. Again recovery was in its messed-up state. Since aroma wouldn't work at all in the corrupted recovery, I've been sticking with the non-aroma Uniporn installer. Working from my external card, I finally got it installed successfully. Yay!
Recovery is mostly usable now but still not right. Here are some things I've tried already based on answers I found in the Uniporn dev thread: 1) Flashed zImage file extracted from Nunhugger's infuseICSrecovery.tar file with Heimdall on Mac; 2) Flashed Entropy's UniKernelZip from Recovery; 3) Flashed boot.img file extracted from UnikernelZip.zip with SGS Kernel Flasher; 4) Flashed zImage file extracted from Nunhugger's infuseICSrecovery.tar file with SGS Kernel Flasher; 5) Upgraded to Uniporn b39; 6) Repeated steps 2 through 4 while running b39.
Here is a piece of information that may be relevant: While running Emancipation, I often got an error message that my sd card was unexpectedly removed. Or an error message that it was blank or in an unsupported format. Thinking that the problem was with my external sd, I would shut down, pop open the battery and sd card, clean the contacts, put everything back together and reboot. Everything would work for a while until I got one of those messages again. Thinking it may be a software issue was one of my main reasons to upgrade to Uniporn. Except that I later realized that it must be the INTERNAL sd card that was unexpectedly unmounting, since the phone wouldn't run apps from the sd card and apps are on the internal card not the external. Maybe hardware problems after all? Maybe that's why installers and nandroid restore wouldn't run from internal card?
Attached images are 1) colorful snow that flashes on the screen for a half-second or so between Samsung logo and Uniporn startup animation; 2) What recovery currently looks like. Recovery was less legible actually before flashing Entropy's kernel, and returns to less legible version after flashing infuseICSrecovery.
Does anyone have any ideas at all how to fix this? Thanks for your help!
Msg, relay done...
Sent from my SGH-I717, Black Star.
Flash GB bootloaders.... Use caution.
Sent from my SAMSUNG-SGH-I997 using xda premium
Your issue is bootloaders and I do not think more. This will get rid of the distortion on recovery, but I cannot speak for possible sd corruption or bad flash issues that happen. Lets fix the color distortion first.
Assuming you can use Odin, go here:
http://forum.xda-developers.com/showthread.php?t=1613523
and read the directions. Download this for Odin or find the one for Mac you used if that is what you are doing:
https://dl.dropbox.com/u/16149362/Odin3 v1.7.zip
then go to the FAQ in that thread and look at #1. There is a tar file for you to download and put in the pda slot. Do it and flash the file.
When all is done with SUCCESS, reboot your phone and come back and report any further issues. Recovery should be readable.
BTW, ICS recovery is to help when stuckin a bootloop from flashing and ICS rom. It fixes nothing else, including the distortion.
After struggling with this phone T959V for 3 days I finally got the ROM installed.
It seems as you read these forums you're not sure if what you're reading is accurate and how much of this still relevant to your issue.
I did everything on a 32-bit system as this seems to matter as I couldn't do this on my 64-bit Win7, but that was following the heimdall oneclick methods, but I could only go so far with that. I got all the way to the cannot mount SD Card...
Being that this is my 2nd phone to root, this is the harder of the lot (my other was HTC)
But enough about myself here's some tips if you're still having issues with this guide that helped me out which wasn't posted.
Do yourself a favor and just get a 2nd SDCard. Stop crying about the cost and just get one. I had 2 8GBs so I didn't care if anything happened.
I made sure I copied all the data over to the hard drive and then formatted the blank one and put the files back. So now if I blew this one up while in rooting mode, I didn't care, because I knew I had one sitting ready to go.
You may want to get the latest Samsung USB drivers as mine was 32-bit and after rebooting it was able to see the phone.
If you stick your phone in downloading mode, just leave it there and make sure odin can see your phone. If its not showing up then something else is wrong (usb, cable, port...etc) many times ODIN couldn't see my phone and I had to download reinstall drivers reboot etc...but my phone was still hanging in download mode, so dont sweat it...
I was able to follow the directions and was very happy I got to step 10.
You may want to get the QuickBoot.apk as this is better than going to CWM once you're in the phone.
But now enter the ROM and I get the blasted "Cannot mount sdcard".
And I cannot make a backup, which is an indication that something is not reading right.
I read through the forums and they talked about creating a partition. Since I didn't care about the SDCard info I just said create a partition thinking that it would create a separate partition on the card...nope..it will wipe everything from the card as if you formatted it. I chose the 1024 and 0 cache and away it went.
After a quick reboot, I was able to make a backup and finally load a ROM and install.
I didn't realize that it was such a big deal with the formatting, but again as they say follow all directions.
I didn't do the #12, but did hear the Linda and all is great!
I'm happy to report that my Samsung Galaxy S T959V is finally rooted and Valhalla Black Edition installed.
I figured I should contribute my headaches as someone might be going through them as well.
My follow up questions would be:
1. Do I need to flash the busybox_installer?
2. If I got a new and say larger SDCard like 32GB and just created a new partition, would it just reformat that to the phone's liking and then install a new ROM in that?
Thanks for this forum!
Andy
sqlandy said:
My follow up questions would be:
1. Do I need to flash the busybox_installer?
2. If I got a new and say larger SDCard like 32GB and just created a new partition, would it just reformat that to the phone's liking and then install a new ROM in that?
Thanks for this forum!
Andy
Click to expand...
Click to collapse
1. You don't really need the busybox installer, but it's recommended since there are a few apps and tweaks out there that need busybox. If I recall correctly, I threw in busybox into my edition of VB, but I'm not sure if Raver threw it into his.
2. Yeah you can format it directly from the phone but the repartitioning is necessary, it'll work just after a format.