Hi all. i have Samsung galaxy 4G. Phone not start just showing
______________________________
Galaxy S 4G\exlusively from T Mobile
SAMSUNG
______________________________
How this happend? My sister try to send or receive file in skype, and phone freeze. after that i never can load os.
i'm trying load new software using odin.. but nothing help.
After flashing i can hear Linda voice..
and after restart CVM message
Wiping data
Formating /data
E:format_volume: rfs format failed on /dev/block/stl10
Formating /cache...
E:format_volume: rfs format failed on /dev/block/stl10
Wipe data failed.
when i'm trying install firmware from SD
--Install /sdcard ...
E:Short write of /tmp/sideloadpackage.zip (No space left on device)
Instalation aborted.
how can i fix my phone?? das anybody help me?
Go to this thread:
http://forum.xda-developers.com/show....php?t=1358498
Select and download:
Download SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders
Let me know when you have it downloaded and I can help you proceed.
i cant open this page..
404 Page Not Found
The page you requested was not found.
http://forum.xda-developers.com/showthread.php?t=1358498
While you are waiting for the download - go ahead and do step one in that thead:
"Get the latest version of Java 1.6 from this link."
** Just so you understand - Froyo and GB have different bootloaders. If you were on Froyo and trying to flash GB without bootloaders - that is a problem. That is why - to be safe - you are downloading KJ6 WITH BOOTLOADERS so we know you will be good to go afterwards.
Make sure you refresh your browser so you can see my replies.
downloading progress 23% ....
and i really need your help
Step by step... :-( bcuz i have no idea how to fix this problem ..
nvitek said:
downloading progress 23% ....
and i realy need your help
Click to expand...
Click to collapse
Let's do it. Look at the post above yours. And take care of the Java.
nvitek said:
downloading progress 23% ....
and i really need your help
Step by step... :-( bcuz i have no idea how to fix this problem ..
Click to expand...
Click to collapse
Step by step is no problem. Using this method is fairly easy.
What is your status? I need to take my daughter to the park
can't believe, file is broken . Looks like i'm must download this file using Download manager.
23 nmin left.
Zz...
Java is up to date, battery charged.
nvitek said:
can't believe, file is broken . Looks like i'm must download this file using Download manager.
23 nmin left.
Zz...
Java is up to date, battery charged.
Click to expand...
Click to collapse
You are downloading it on your computer correct?
And downloading the link:
'Download SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders'
Correct?
ADD: I don't think you realize the thread is on page 2. Click the '2' at the bottom of your thread to see the next page. You also need to keep refreshing your browser to see new posts.
download Completed. Device connected
Operating System: Windows
Found Heimdall Version: v1.3.1
Connect your device in Download Mode to procede.
Device not connected.
SMS-KJ6 (v0.0.2d) Stock-Rom with Bootloaders UVKJ6 is ready for your device.
Ready for flash.
After Heimdall
Android recovery <3e>
...
installing update...
Succesfully installed package.
....
-- Updating filesystem...
E:failed to mount /data <Invalid argument>
E:discard_filesystem_for_rfs:Can't mount /data
--wiping cache...
formating cashe...
E:format_volume: rfs format failed on /dev/block/stl11
Chashe wipe failed.
--Apling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'.
Successfully applied multi-CSC
nvitek said:
yeap..
url correct
54% and 12 min left
Click to expand...
Click to collapse
Since you have some time to kill -
Read these two threads start to finish:
http://forum.xda-developers.com/showthread.php?t=1529348
http://forum.xda-developers.com/showthread.php?t=1515319
These are two people that did exactly what you are about to do.
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
When you are ready to get started:
USE A USB PORT YOU HAVE NOT PLUGGED YOUR PHONE INTO AT ALL AND THAT IS CONNECTED DIRECTLY TO YOUR COMPUTER (I.E. NOT A USB HUB OR ADDON PORTS)! DO NOT USE THE SAME PORT YOU TRIED TO USE ODIN WITH. DO NOT USE A PORT YOU MIGHT HAVE USED KIES MINI WITH. USE A PORT THAT YOU HAVE NEVER PLUGGED YOUR PHONE INTO DIRECTLY ON YOUR COMPUTER!
You will do this first:
- Get your phone in Download Mode
How to get into download mode:
Take your microUSB cable and plug it into the computer, but not the phone (yet).
Take out the battery from the phone.
Put the battery back into the phone.
Put the back cover back onto the phone, make sure it's snug so the battery doesn't fall out.
Hold vol + and -, keep holding them.
Plug the USB cable into the phone.
You should now be in download mode and should see a picture of a yellow triangle with Andy and a shovel in the middle.
Second:
- Run the Heimdall One-Click you downloaded using the directions in that thread:
Run: 'java -jar SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar'
Third:
- You will need to install drivers. When doing the driver install make sure you go to "options" menu and make sure "list all devices" is checked. Then from the drop down menu choose "Samsung USB Composite device" and click the "install drivers" button and let it do its thing.
It will tell you whether it was successful or not.
Fourth:
- Heimdall should show you that your phone is connected:
See attached image.
If so - Select Flash.
Fifth:
- Your phone will reboot. You will hear Linda talk to you. Wait. Let me know if you get a rainbow screen. If not it will boot into CWM Recovery. If it does - select reboot system now and you will be good to go.
- If you see the rainbow screen - Let me know and we will proceed.
OK - I assume you are sitting on page one of the thread. I can't reply to you if you don't come to the second page. Sorry.
Thx for your help.
After all steps andflashing with Heimdall my phone rebooted to CVM recovery.
after reboot phone stop in message like in my first post.
What are you doing in CWM to get that message? And do you know if you were on Gingerbread or Froyo previously. Because if you were on Froyo you were not finished with Heimdall One-Click. You would need to flash a second time - checking flash bootloaders.
1.CWM is automatically loaded after a reboot.
2.Froyo was previously.
3."You would need to flash a second time - checking flash bootloaders." - already done.
Message appears after downloading new software with using heimdall and automatical reboot
Phone still freezes on startup.
Is it possible to connect terminal to mainboard? perhaps that will help to see diagnostic messages... and will give me a chance to understand the problem.....
nvitek said:
1.CWM is automatically loaded after a reboot.
2.Froyo was previously.
3."You would need to flash a second time - checking flash bootloaders." - already done.
Message appears after downloading new software with using heimdall and automatical reboot
Phone still freezes on startup.
Is it possible to connect terminal to mainboard? perhaps that will help to see diagnostic messages... and will give me a chance to understand the problem.....
Click to expand...
Click to collapse
If you correctly flashed KJ6 Heimdall One-Click WITH Bootloaders and that did not work -
Verify that you have a Samsung S 4G SGH - T959V for me. Look under the battery for the model number.
And to be clear - after flashing it will take a bit to boot your phone as things are being done to your phone during boot up. If you pulled battery too quickly that may affect it.
Lastly - "Message appears after downloading new software with using heimdall and automatical reboot" - Where is the message appearing? In Heimdall or on phone?
if you are still having issues, you can check the "Potential Problems" section of the guide in my signature (provided that you do indeed have the right phone model)
Sent from my SGH-T959V using xda premium
Hahahaha - This kid is so proud of himself. Aww me too Juls. Keep self-promoting every where you can. You still haven't asked dsexton to link to you in his OPs.
Juls317 said:
lumin, im just trying to help the guy out as your way isnt cuttinv. sorry for caring for the community.
and you self promote too you hypocrite.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
ok
10 chars
No need to belittle members. Lets keep things nice and clean ok? Happens again, I will not be so nice. Have fun guys.
Related
Introduction: It has come to my attention that many of us windows users are still using odin for upgrading to Ginger bread and recovering from soft bricks. I have found the heimdall one click method is easier to use and more stable for flashing your phone from a computer. I am trying to make this guide as noob proof and simple as possible. Given how simple the one click method is it should not be hard (although if you are new to this device it can prove to be difficult if you don't read and understand everything).
Please be sure to format your sd card if this is the first time you are flashing ginger bread. If you have problems converting to ext4 using one of the rooted one clicks it is suggested you create a 2048 partition in cwm.
The first five steps are to help get heimdall and everything needed to use it installed on your windows computer. If you already have heimdall you can skip to steps 6&7.
Please read everything in this guide before proceeding and be sure to read everything else mentioned in this guide. proceed slowly if this is your first time. I recommend a print out, double check everything, and cross off each step as you go. Slow and methodical = smooth = fast and efficient with perfect results. Remember the best way to gain knowledge and learn to do almost anything is to READ.
If you have used the one click method and have any suggestions for this guide please feel free to comment.
Disclaimer: You are flashing your device at your own risk. No one but you can be held responsible if you make a mistake. Some one click packages contain bootloaders and flashing incorrect bootloaders may hard brick your device. Never flash a one click package that is not clearly labeled for your device by model number.
Warning: if you are on a Mac running osx 10.5 or higher there is a problem with the re partition function in heimdall. since you must flash boot loaders these packaged are designed to re partition automatically. It is recommend you use a windows or Linux parallel to flash.
On to the guide:
1: first you will need to download and unzip the lastest heimdall front end. This package can be found at http://www.glassechidna.com.au/products/heimdall/
Please read and understand everything that this website has to offer about the program before use.
2: after you have unziped the heimdall front end package open the containing folder and click on the "Read Me" text file. This file contains troubleshooting tips, driver installation, installation procedures, and instructions for flashing other heimdall supported files to your device. Oh yeah and they don't call it Read Me for nothing
3: you will also need to download and install the package labeled "Microsoft Visual C++ 2010 redistributables" and get java 1.6 do I have Java?. Simply download and run (double click) the executable files.
4: Once you have downloaded and unziped heimdall front end, installed java 1.6, and installed the C++ packages you will need to install your device drivers (this process is also explained in the read me file you should have read).
A: Place your device into download mode and plug it into your computer. How to get into download mode
B: Open the unziped heimdall folder then open the the "drivers" folder and run (double click) the "zadig" application
C: Click the "options" menu and make sure "list all devices" is checked.
D: from the drop down menu choose "Samsung USB composite device"
E: Click the "install drivers" button and let it do its thing.
Note: if you have trouble installing drivers try again. If "Samsung USB composite device" is not an option unplug your device re run zadig and take note of what options have disappeared.
5: Now it is time for you to choose your one click package. If you would like help choosing the package that is right for you please feel free to ask.The threads I am linking to are only for the Samsung Galaxy S 4G device from T-Mobile, Model# SGH-T959V. If this is not your device do not flash the one click packages I am linking to. If this is your device these are the ONLY one click packages available. Again, never flash a firmware package not clearly labeled with the exact same model number as the device you are flashing to.
Choose and download the one click package of your choice. Remember to read the OP of each thread before making your decision. If you have a question feel free to ask here.
A: kj6 one click collection
This thread contains three one click packages to choose from. All are from the official Galaxy S 4G Ginger Bread Upgrade to 2.3.6 or KJ6. Read the OP to choose the one that is right for you.
B: kf1 one click package
This was the first one click package we obtained for the Samsung Galaxy S 4G. It was from a leaked version of gingerbread 2.3.3 or KF1. I, and Most, do not recommend you use it because the boot loaders change the button mapping for recovery and download modes (this can cause problems trying to revert) ;but, I would like to give credit to the creator of the one click packager and will include his thread and work as such.
6: Now that you have installed heimdall and chosen a one click package its time to flash. Close your heimdall folders and forget about them for now. put your device in download mode and connect it to your computer How to get into download mode
A: Run (double click) your "oneclick.jar" package. Yes, they are supposed to be executable files (be patient it may take a minute to load)
B: Read the "package information" section and ensure you are flashing a one click package designed specifically for your device by model number.
C: do nothing else except click "flash"
D: wait for device to reboot
E: If you are upgrading to GB from froyo do not close your "oneclick.jar". You will need to repeat step 6 a second time with the "flash bootloaders" box checked. Please also ensure you have read the disclaimer.
7: At this point your device will be in one of these three states
A: rebooted and running as factory
B: in the stock Samsung 3E blue recovery in which case you should use the volume buttons to navigate to reboot device and use the power button to select reboot device
C: In a CWM recovery where you should use the volume buttons to navigate to reboot device and use the power button to select reboot device.
That's It! Happy flashing!
Credits
Benjamin Dobell - Creator of heimdall
Adam Outler - creator of the one click packaging system
Bhundven - For assembling the kj6 update packages for the t959v
Fbis251 - wiki links and general support
odin vs. heimdall comparison
Most of us here are used to Odin and can make it work; however, it is an unstable, proprietary, windows only, unsupported program. It often will not recognize your device or you get a better experience with v 1.7 or v 1.85 or maybe it is just picky with your computer or device. I had both the above mentioned versions installed on my desktop in case I had problems with one or the other. This, to me, is totally unacceptable. Now we have heimdall and I encourage you to make the switch. It is an ongoing project that is cross platform, supported, and open source. This means it is based on the same fundamentals as Android proving any developer the opportunity to help make it better, faster, or more user friendly. Take the one click project for example: now, with heimdall installed on your system, you can simply execute a pre programmed flash and your done with your device flashed as the developer intended. I admit it is a few clicks not just one but, it hasn't given me any problems, it tells me exactly what it's doing in a language I understand, and it is super easy. So at least give it a shot, bet you will like it
NICEEEEE!
Sent from my SGH-T959V using xda premium
Choosing the right driver
Hi there,
I don't see the Samsung USB Composite Device in the drop down box when running Zadig. What I have is below:
Samsung_Android
CDC Abstract Control Model (ACM)
Android UMS
S3C6410 Android ADB
Driver failed to install for Samsung_Android. Should I try any of the other options?
Thanks for helping a bricked noob out!
R
mandogand said:
Hi there,
I don't see the Samsung USB Composite Device in the drop down box when running Zadig. What I have is below:
Samsung_Android
CDC Abstract Control Model (ACM)
Android UMS
S3C6410 Android ADB
Driver failed to install for Samsung_Android. Should I try any of the other options?
Thanks for helping a bricked noob out!
R
Click to expand...
Click to collapse
Was your phone in download mode?
Unplug your device and re run zadig. Take note if any options disappear. If so re plug your device and try it. If not report back.
Sent from my SGH-T959V using XDA App
Sticky!
Sent from my SGH-T959V using XDA App
its honestly the far superior option and comeing from a linux based world where i dindt have to deal with odin as much Its great tried odin on windows and really its far superior and alot more stable then odin.. its worth learning tbh
Further adventures in un-bricking with Heimdall
Thanks for your quick replies!
1). I was able to get the driver installed, using the Samsung_Android. When I connect the phone it now shows up in the device manager. Picture 1 attached (libusb - Samsung Android).
2). I'm not sure what mode my phone is in. When I press the power button I get first the startup screen....Picture 2.
Then I get this screen "Android System Recovery 3e" and a range of options. The volume control is flipped i.e pressing down causes the menu to go up. (Picture 3)
There is no way to "select" any of the options. Only one of the buttons at the base of the screen seems to work: the menu button causes the text on the screen to disappear and only leaves the green android with triangle exclamation point. (Picture 4)
Heimdall does not detect that the phone is connected....Picture 5.
Any suggestions what I should try next? This is a Galaxy S 4G t959V.
Thanks so much for all your help! What an introduction to the world of Android!
M
mandogand said:
Thanks for your quick replies!
1). I was able to get the driver installed, using the Samsung_Android. When I connect the phone it now shows up in the device manager. Picture 1 attached (libusb - Samsung Android).
2). I'm not sure what mode my phone is in. When I press the power button I get first the startup screen....Picture 2.
Then I get this screen "Android System Recovery 3e" and a range of options. The volume control is flipped i.e pressing down causes the menu to go up. (Picture 3)
There is no way to "select" any of the options. Only one of the buttons at the base of the screen seems to work: the menu button causes the text on the screen to disappear and only leaves the green android with triangle exclamation point. (Picture 4)
Heimdall does not detect that the phone is connected....Picture 5.
Any suggestions what I should try next? This is a Galaxy S 4G t959V.
Thanks so much for all your help! What an introduction to the world of Android!
M
Click to expand...
Click to collapse
You are currently in recovery mode running whatever bad boot loaders you flashed. Use this method to enter download mode
1 pull out battery
2 hold Vol up Vol down at the same time
3 plug USB cable into phone and computer
4 re insert battery and continue to hold both Vol buttons until your phone displays something.
unfortunately it is possible the bad boot loaders you flashed may have messed up your button mapping. if you try the above mentioned method for download mode multiple times and only end up back in the same recovery screen please direct me to the thread you flashed the bad boot loaders from
Good luck
Sent from my SGH-T959V using XDA App
How to get into download mode
FBis251 said:
How to get into download mode
Click to expand...
Click to collapse
Thanks for that link fb. Will add this to the OP in a bit. Maybe we should edit the wiki to show pictures of download mode since we have found a couple different screens other than the one mentioned. Oh crap taking my own thread off topic
Sent from my SGH-T959V using XDA App
More Heimdall recovery....
Cool. OK followed instructions and now have a screen as below:
What next?
M
More Heimdall recovery....
Hit the up button and now get the digging android icon (Digging)...what next experts! You guys rock by the way!
Thanks!
M
Bassmanjames said:
Thanks for that link fb. Will add this to the OP in a bit. Maybe we should edit the wiki to show pictures of download mode since we have found a couple different screens other than the one mentioned. Oh crap taking my own thread off topic
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Yup, anyone can update the wiki I'm going to add guides little by little into it so we can just link new users to it. I realized after typing for the 20th time how to get into download mode that it'd be easier to just use the wiki.
mandogand said:
Cool. OK followed instructions and now have a screen as below:
What next?
M
Click to expand...
Click to collapse
Is it fine if we use your picture in the wiki? People would really appreciate it.
Now that you're in download mode you can use the one click to recover your phone.
Please feel free to use any or all of the pictures!
My utmost thanks to you guys! The "experts" at tmobile basically told me that i had a paperweight and would need a new phone!
M
mandogand said:
Please feel free to use any or all of the pictures!
My utmost thanks to you guys! The "experts" at tmobile basically told me that i had a paperweight and would need a new phone!
M
Click to expand...
Click to collapse
Well with bad boot loaders you might have.
So success?
Sent from my SGH-T959V using XDA App
Just got back. I just flashed it using the file below and put a check mark on the bootloaders.
The file I'm using is from this thread:
http://forum.xda-developers.com/showthread.php?t=1358498
pics attached. However, now the phone seems to be dead and I can't even turn it on....
I did leave the phone connected to USB and it was showing the downloading screen for the 2 hours while I was away...
What now?
Thanks,
M
mandogand said:
Just got back. I just flashed it using the file below and put a check mark on the bootloaders.
The file I'm using is from this thread:
http://forum.xda-developers.com/showthread.php?t=1358498
pics attached. However, now the phone seems to be dead and I can't even turn it on....
I did leave the phone connected to USB and it was showing the downloading screen for the 2 hours while I was away...
What now?
Thanks,
M
Click to expand...
Click to collapse
Do me a favor and pull your battery. post a pic of the device info but edit out your imei number
Sent from my SGH-T959V using XDA App
Here you go.
Serial end with a W.
Thanks,
M
My infuse when turned on goes to a screen that looks like phone ! pc with the message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So this happens even when I try and go to download mode or recovery mode. Basically as soon as I hit the power button. I'm really freaking out. It was rooted and I was doing following this link: http://forum.xda-developers.com/showthread.php?t=1613523
Then the problems started when my computer didn't recognize the phone in download mode. and then it was recognized so I started the Odin flash. Then it froze at cache.rts (I believe that's what Odin said, I can't get to it anymore)...So I uninstalled and reinstalled the drivers and did it again and it got to factoryfs.rfs before it froze there for a really long time. So I unplugged it and tried to do GTG Ultimate Unbrick...but I can't get the .zip file to open. My computer keeps telling me "Can Not Open ____ as archive". I re-downloaded it and same result. Is there anything I can do to save my phone? I'm a real idiot and this kind of stuff always happens to me no matter how much I read up on something and make sure I'm doing it right. I would really appreciate a little help though, thanks!
I actually got it downloaded and followed Rammstein874's video on youtube on how to do it and I am once again stuck on factoryfs.rfs :-(
What can I do at this point? It is still stuck at the Phone-!-PC screen when I try to go to download mode. Please help, I'm starting to get pretty worried about this...
When your screen is phone!computer, that's an alternative version of download mode. You can either use ODIN or heimdall back to stock. Just plug it in via usb, allow odin/heimdall to recognize it and start flashing.
This is correct....if you see those pic on your phone that is a form of download...i would run the one click method...
sfgiants2010 said:
Rammstein874's video on youtube
Click to expand...
Click to collapse
Can you PM me the link to Rammstein874's video? I didn't realize he still had this, and I've since updated my packages and how-to.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
jscott30 said:
Can you PM me the link to Rammstein874's video? I didn't realize he still had this, and I've since updated my packages and how-to.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Lemma know if that's the one..pm sent...
Sorry I was at work all day.
This is the video link I used: http://www.youtube.com/watch?v=y1HgcZrYR_4
I am also looking at the following one-click method posts:
- http://forum.xda-developers.com/showthread.php?t=1331381
- http://forum.xda-developers.com/showthread.php?t=1524081
* I used the above link (or tried) and it didn't seem to work either. I downloaded Heimdall Suite for Windows 64bit and then installed the drivers and plugged in my phone in download mode. But then I was unable to get it started...I used the "Stock_SGH_I997_UCLB3_Repartition-One-Click.jar" file I found on mediafire (because all of these posts link to mediaupload which is no longer working). Anyway, so I tried to run Heimdall-frontend.exe on windows and once it opened up I connected my phone (nothing turns green like the post says) and hit browse. I chose the jar file aforementioned and it said "tar header contained invalid file size."
So if someone could point me toward a more up to date thread if I'm using the wrong one and kind of explain to me how to get around the other problem I'm having with the jar file then I would be forever appreciative
Not sure what you did...not saying you did something wrong but here is what I do, below are how i perform using qkster's method...
The USB + Volume Down + Volume Up Method: Download mode (Noticeable by an Android robot digging with a shovel) is reached by taking everything out (Battery, SIM, MicroSD). plug in the USB cable to your computer and phone then putting in battery at the same time Holding the volume buttons both up and down, (Don't press the power button at all in this method).
How to INSTALL:
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: CONNECTED. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
download this file for your one click to stock...and using above directions...
once that is done and you want to put CWM mod on for flashing a custom ROM, same directions to get in to download mod...
download this file to use the one click to put CWM mod on your phone
here is the link where i took all this...
http://forum.xda-developers.com/showthread.php?t=1524081
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
sfgiants2010 said:
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
Click to expand...
Click to collapse
why are you using these other programs...idk,
I just click on the one click file it an executable design to open and run itself...you say attach the jar file...why the suite version of heimdall...?
did you download the links i provided and just use those...?
sfgiants2010 said:
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
Click to expand...
Click to collapse
Is your phone still stuck on the phone-!-pc ?
did you read the last post he had regarding the actual heimdall program suite...
not sure what he had going on...I believe he has download mode capability...
thx ''Goshujin-sama'' qkster
Yeah..that's where I wasn't sure what sf was doing.
the jar file is self executable. When you click on the jar file, there is a load up delay.
Then should be be ready.
You then hook up the phone.
I've not seen in tar header file size error.
Sf should not be trying to stick the 1-click file into heimdall front-end.
It's a single self executable jar file..the is no other dependencies...the only other situation I can think of is maybe putting the 1-click jar file onto a different PC and try running it there.
qkster said:
Yeah..that's where I wasn't sure what sf was doing.
the jar file is self executable. When you click on the jar file, there is a load up delay.
Then should be be ready.
You then hook up the phone.
I've not seen in tar header file size error.
Sf should not be trying to stick the 1-click file into heimdall front-end.
It's a single self executable jar file..the is no other dependencies...the only other situation I can think of is maybe putting the 1-click jar file onto a different PC and try running it there.
Click to expand...
Click to collapse
that's when I started to question him on these other programs...due to the one clicker is self sustained as a exe...idk...but believe he log off...i will monitor and holler at you if required thank you...
Oh man I had no idea...I was so mixed up by trying to educate myself with so many posts about using Heimdall. I thought I had to download Heimdall separately and attach the jar file or something. But okay so I ran the one-click. It failed the first time (expected) and then I checked the flash bootloaders box and hit flash again. Then it stopped at installing drivers and prompted me to install the drivers on the following prompt. So I did that and then it said installed drivers successfully and I hit close. Then nothing happens. So what do I do at this point? I'm probably being an idiot again but I really appreciate you guys trying to help me out. And I hope you realize I'm trying my best to not waste anyone's time.
The device status was a green Connected before I started by the way. At this point what I do? It seems to just break at the installing drivers part...?
It should of rebooted it self the phone...
Btw you are not wasting my time...wife is watching cup cake wars...so ....rather help you...lol
sfgiants2010 said:
Oh man I had no idea...I was so mixed up by trying to educate myself with so many posts about using Heimdall. I thought I had to download Heimdall separately and attach the jar file or something. But okay so I ran the one-click. It failed the first time (expected) and then I checked the flash bootloaders box and hit flash again. Then it stopped at installing drivers and prompted me to install the drivers on the following prompt. So I did that and then it said installed drivers successfully and I hit close. Then nothing happens. So what do I do at this point? I'm probably being an idiot again but I really appreciate you guys trying to help me out. And I hope you realize I'm trying my best to not waste anyone's time.
The device status was a green Connected before I started by the way. At this point what I do? It seems to just break at the installing drivers part...?
Click to expand...
Click to collapse
Once the connected bar is on, you click flash. It should complete it's routine. the phone reboots. you should click on the boot loader box. you disconnect. let it finish. set it back into donwload mode and flash again.
you can try different usb port or data cord or different pc
Plus you have my master...qkster here...cuz you lost me on the programs you were using...so i called in the jedia master!
As long as your screen has that Phone! Computer sign, it's not bricked yet. I recommend you to search some how to videos online so you can see the exact instructions on how to use heimdall because it's that easy. If possible maybe one of our awesome contributors can make a how to video for heimdall.
I believe he is tracking now qkster is providing....thx
So I rooted my phone for the first time via Odin. And it worked -- after that, I tried to install a custom ROM (slim bean) -- I ended up uploading the non zipped version on my SD card. And I went through all the steps to install up until "format/system" to realize that I didn't have the zipped files.
Now my phone is stuck on the Samsung Icon. I just tried to use Odin to flash the stock gingerbread again, but there it gets stuck on "Setup Connection".
Please help! Total newb at this, and clearly it failed.
---
My phone wouldn't turn off even with Odin closing, so I took out the battery -- so now my startup screen is
"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
How do I fix this?
That is kind of a secondary download mode.. odin or heimdall should detect your phone.
Make sure you have a good usb cable and maybe try switching usb ports.
Sent from my SGH-I997 using xda app-developers app
Right. To add to andros11's post, was the top left box yellow in Odin before you clicked start? Odin will acknowledge that your phone is connected immediately (the box should be yellow if you your phone is connected properly). Of course, make sure you have all of the appropriate drivers (i.e. download Kies for the Infuse).
Also, for future reference, I have a fix for situations like yours so you don't have to go back to stock. Basically, you can use adb to push the correct zip file to your sdcard. What you do is:
Download and install the Android SDK: http://developer.android.com/sdk/index.html
Make sure to install platform tools (a separate download from within SDK)
In Mac and Linux, open up Terminal. I can't remember how Windows works, sorry! Navigate to wherever the platform tools folder is. You have to do this using command line, so, cd <the/path/to/your/folder> (the easiest way is to just type cd, hit the space bar and then drag the folder to the Terminal window).
Once there, connect your phone to your computer. It can be in CWM or Download mode
Type in Terminal: adb devices
The next line - the response - should tell you if your phone is recognized. If it's blank, try again. If it's still blank, you might try disconnecting usb phone cable and reconnecting again. You might also try going into download mode.
Okay. Next type: adb push <here, just drag the zip file to your terminal window> /sdcard/
Give it time to push the file to the sd card. Repeat if necessary (if you have more than one zip)
Exit terminal, disconnect phone from computer, go back into recovery, navigate to the sdcard to flash and lo and behold! The proper zip file is there for you!
This might sound long, but it's so easy. Getting SDK set up is probably the biggest pain and it's not really that much of a pain!
You may want to give Heimdall a try rather than Odin.
Put the phone into download mode and try this:
http://forum.xda-developers.com/showthread.php?t=1331381
Thanks so much everyone. Seriously.
So, Whizzpopper -- I *think* I installed SDK, but since my phone still says, "Firmware upgrade encountered issue. Please select Recovery mode in Kies and try again." I tried connecting it to Kies -- and it says "connecting" but never connects.
And even if I try the key combo to get to Download Mode or Recovery, it never gets away from that Firmware message.
How can I just get out of that mode?
how to keep fb sync on custom rom?
Hi I am a fairly new member, I have been following different threads for a long time but have recently signed up, so if i am posting in the wrong thread I sincerely apologize. moving on...
I have been using the Aeon 1.4 rom for awhile now and have been loving it. I first downloaded the rom without the stock libs and found that it is much faster than the stock libs rom, even after manually removing most of my stock apps via sd maid pro. But it has been the only way to keep the option to share with FaceBook. and being able to add facebook in my accounts and sync are in system settings. system settings>accounts and sync>add account.
You won't be able to get out of there until you are able to flash with either odin or heimdall.
You may also try a tool called one-click unbrick (google it)
Sent from my SGH-I997 using xda app-developers app
andros11 said:
You won't be able to get out of there until you are able to flash with either odin or heimdall.
You may also try a tool called one-click unbrick (google it)
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
ONE CLICK UNBRICK HAS GOTTEN ME OUT OF THAT GODFORSAKEN FIRMWARE MESSAGE.
Thank. You. So. Much.
... Now to follow the rest of the steps to try and get it back to some sort of operating phone!
and please note that it would be best to uninstall kies- it has been a source of problems for a countless number of users.
Thank you so much for your help!
So the terminal adb push worked -- and I installed my ROM (went through all the installation wizard parts, etc.) but now at reboot, I'm still stuck at the Samsung logo.
What happened?
@andros11 -- I saw your comment on how to best get from GB to JB
http://www.android.gs/install-unoff...pdate-to-ice-cream-sandwich-4-0-3-custom-rom/
I tried to follow those instructions to install ICS first, (I was previously too eager and went straight to JB!) and still I'm stuck at the Samsung screen.
Anybody have any threads, recos to get my phone to bootup to any system?
Sorry for the newbness!
Enter download mode to Go back to stock gb and then work your way up again up to jb.
Sent from my SGH-I997 using xda app-developers app
To add to that, use qkster's link to get back to stock.
http://forum.xda-developers.com/showthread.php?p=23118134
Sent from my SGH-I997 using xda premium
Okay so I tried the Heimdall One Click Stock --
unfortunately, it stops working at the "clearing interface" stage -- says it failed. And I've changed the cables but still the same result.
You are on the right track... just that something is missing.
Be sure to get rid of kies.
Be sure you have the latest version of Java. http://www.java.com/en/
Use the link in post 13 that psal gave you - read at least posts 1 and 2 all the way through, then go through and perform each step.
The first time is a process, after that it is quick and easy. Thanks to qkster. :good:
Here is an award winning-less video of the process that you might want to watch as you may see a step in the video that you are missing. Hope this helps.
http://www.youtube.com/watch?v=sHyY7WHx4zc
Nothing in this world can take the place of persistence. Talent will not; nothing is more common than unsuccessful people with talent. Genius will not; unrewarded genius is almost a proverb. Education will not; the world is full of educated failures. Persistence and determination alone are omnipotent.
Calvin Coolidge
Hi there,
i got a 6800 with stock (but rooted) ICS running and wanted to try the ZETA 4.0 Rom from the development section - what seems to be a minor task turned into disaster ;-/
I followed the instructions from the message in the development forum:
quote:
Do a Nandroid backup!
Copy the Zeta to your SD
(optional) Wipe Data/factory reset
Wipe Dalvik Cache
Install zip from sd
Reboot
I used CWM to backup all information, (which took like 30 mins and ended in an error message)
and when i clicked on "wipe data/factory reset" in recovery things went seriously wrong ...
it seemed to take a very long time (15`+mins) and then rebooted
I am now stuck at the white/blue glowing samsung logo
I can get back into recovery, but when i try to install the "Zeta Rom V4.0.zip" file from the SD card, i just get a
E: signature verification failed in red lettering ... before that, the package is found/opened/verified
also, the cwm.zip is opening, but acting very weired (cant select with the volume keys
The weired thing to me is that I didnt even install the Zeta package when things got ugly!!! - I just did a data wipe
could some good soul pls help me out ...
thx in advance for your time
Al
Hi dude,
Did you try the download mode? (Powerbutton + vol down.) If this still works, your good.
Just get the .Pit file for your device from www.sammobile.com
Now flash this .Pit file with your pc using Odin. If you don't know how to use Odin, please find the thread for this and.read it to the letter! Whatever you do, DON'T set the function for REPARTITION.. that would be THE END dude. Beware!
I had fckd up my tab too, but the Odin solution works fine. After this you can install a new recovery even with Odin and your good M8
After that your good to go and please, of you want to go custom...try the Paranoid Android or Singha light rom . Both are top working, and with the pimp my rom addon (you will find it :good: ), you won't even think about another flash again.
Just don't panic..Good luck!
Regards,
Axelman
Sent from my GT-P6800 using xda app-developers app
Hi there, and thx for responding ...
I can get into download mode (pwr / vol-)
a few extr problems ... I lost the cable to hook up the 7.7 to a computer (3 children household, dont ask ) ... the only form to get files to the tab is pulling the SD card and manually copy files on it and put it back ...
I located 6800.pit files ... so would I just copy those 6800.pit files to the SD and install them in download mode? - could somebody confirm this?
again, thx for answering
Al
sorry, also - could you point me to the 6800.pit file on sammobile ? .... I seem to be unable to locate it ...
thx!
al128 said:
sorry, also - could you point me to the 6800.pit file on sammobile ? .... I seem to be unable to locate it ...
thx!
Click to expand...
Click to collapse
nevermind ... it seems I found it here on xda ...
http://forum.xda-developers.com/showpost.php?p=27636101&postcount=4
(could you confirm that this is the correct one ¿ ... can this be flashed directy via recovery¿
I also leant that I seemed to have superbricked my 6800 by using the "wipe data/factory reset" option in recovery, which supposedly is a bug in the firmware ...
absolutely not amused !
thx for helping
Hi,
Don't use the recovery anymore... as you said, it gave an error anyway. Get a cable and do it the only right way by using Odin.
The super brick means that also the download mode is corrupted...that's the end of the tab for sure, but you still can use the download mode so you are good.
It's your call, but in my opinion your better off with the official download mode (lucky you to still have it) then using a corrupted recovery.
For your info... I would use the Gtp6800 LQ2 .PIT file. If your tab is a 6800 offcorse .
Goodluck m8
Regards,
Axelman
Sent from my GT-P6800 using xda app-developers app
thx axelman, dont worry - I will do it right ... (well, as good as i can do it)
...getting a cable first thing tomorrow ... I cant afford to lose my tab&phone
cheers, Al
Thread moved to Q & A section, post in the relevant section next time.
al128 said:
thx axelman, dont worry - I will do it right ... (well, as good as i can do it)
...getting a cable first thing tomorrow ... I cant afford to lose my tab&phone
cheers, Al
Click to expand...
Click to collapse
He dude,
Use a download from sammobile. Get an account and download the official firmware there. It is the safest way!
I dont know were you are from, but the first ICS build was the open Austria.. P6800XXLQ1
You could use that version, or get the newer version p6800XXLQ2. But you can get any version you like..
GoodLuck
Regards,
Axelman
Axelman8 said:
He dude,
Use a download from sammobile. Get an account and download the official firmware there. It is the safest way!
I dont know were you are from, but the first ICS build was the open Austria.. P6800XXLQ1
You could use that version, or get the newer version p6800XXLQ2. But you can get any version you like..
GoodLuck
Regards,
Axelman
Click to expand...
Click to collapse
I managed to get all things running as per your advice:
I can connect and flash both the stock austrian rom and stock austrian .pit file (I even get a green "pass" in odin!) ... but I am still in a boot trap. I am pretty sure I have those corrupted blocks in the var. partitions ...
I found the following description here on xda ... but it says to TICK the "repartition" ... so I am kind of confused ...
(snip)
What Do You Need To Fix This
1. Odin and Pit get it Here ---> Odin3 v1.85.rar Pit and CWM Include in Odin.
2. Use this Stock Rom P6800XXLQ1_P6800OXALQ1_ATO. This is Open Austria Stock Rom Get it here ==>> Download and Unzip.
3. USB Connector.
3. All You Have and you a ready to Go.
4. Open Odin
5. Tab to Download Mode (( Start + Down Vol ))
6. Connect USB
7. Make Sure the port com detected.
8. Put the Pit file to PIT. Make Sure the PIT is GT-P6800 PIT for P6800XXLQ1_P6800OXALQ1_ATO.pit
9. On Files PDA Make Sure it's XXLQ1_OXALQ1_ATO.md5
10. Make Sure Tick Re-Partition, Auto Reboot and F. Reset Time
11. If you are Ready. Hit the START.
12. If you are successful Com Port box on the Blue and Green in color after the reset and show a pass.
(/snip)
I am confused ... should i tick it or untick it? ... it seems to automatically tick itself on whenever you add a .pit file - so far i UNticked the repartition option
I guess I need to go the whole "adb" route, but it seems to be way over my head ... I cant even get adb to run (a dos window opens and closes immediately) ... pretty frustrating ... there are 70 pages or so to read ... and while I do understand the whole concept, I cannot do it (operationally) ...
well, insult coming to injury ... I am also looking for a job and need my cel desperately
again, thx to all the folks looking into the matter and lending a hand!
cheers, Al
Go back to stock
al128 said:
I managed to get all things running as per your advice:
I can connect and flash both the stock austrian rom and stock austrian .pit file (I even get a green "pass" in odin!) ... but I am still in a boot trap. I am pretty sure I have those corrupted blocks in the var. partitions ...
I found the following description here on xda ... but it says to TICK the "repartition" ... so I am kind of confused ...
(snip)
What Do You Need To Fix This
1. Odin and Pit get it Here ---> Odin3 v1.85.rar Pit and CWM Include in Odin.
2. Use this Stock Rom P6800XXLQ1_P6800OXALQ1_ATO. This is Open Austria Stock Rom Get it here ==>> Download and Unzip.
3. USB Connector.
3. All You Have and you a ready to Go.
4. Open Odin
5. Tab to Download Mode (( Start + Down Vol ))
6. Connect USB
7. Make Sure the port com detected.
8. Put the Pit file to PIT. Make Sure the PIT is GT-P6800 PIT for P6800XXLQ1_P6800OXALQ1_ATO.pit
9. On Files PDA Make Sure it's XXLQ1_OXALQ1_ATO.md5
10. Make Sure Tick Re-Partition, Auto Reboot and F. Reset Time
11. If you are Ready. Hit the START.
12. If you are successful Com Port box on the Blue and Green in color after the reset and show a pass.
(/snip)
I am confused ... should i tick it or untick it? ... it seems to automatically tick itself on whenever you add a .pit file - so far i UNticked the repartition option
I guess I need to go the whole "adb" route, but it seems to be way over my head ... I cant even get adb to run (a dos window opens and closes immediately) ... pretty frustrating ... there are 70 pages or so to read ... and while I do understand the whole concept, I cannot do it (operationally) ...
well, insult coming to injury ... I am also looking for a job and need my cel desperately
again, thx to all the folks looking into the matter and lending a hand!
cheers, Al
Click to expand...
Click to collapse
Dude dd you get through? If not just go to here: http://www.sammobile.com/firmware/?page=3&model=GT-P6800&pcode=0&os=1&type=3#firmware
and download the latest file.
1. It will download as a zip file so make a new folder on your pc and extract it there.
2. Start odin and dont tick anything! leave everything as is. then select pda and choose the extracted file and press start.
3. after you do that just look fror rooting instructions.
BEWARE! DONT WIPE WITH OFFICIAL RECOVERY BECAUSE YOU'LL LOSE EVERYTHING!
dude, thats exactly what I am doing - and it works (all img transfer correctly, i get "PASS" in odin) ... but the tab still is hanging in a boot trap.
I seem to have those dreaded corrupt blocks in the internal SD ...
UPDATE!!!!
UPDATE!!!!
UPDATE!!!! - finally some light at the end of the tunnel ...
I seem to have managed to push HC 3.2 (Hong Kong version, which is where my tab came from) somewhat successfull on to the tablet... but I still get the following error messages
after a reboot, I get to the following screen:
COULD ANYBODY PLS TRANSLATE THIS !!!!!!!... and better yet, suggest what to enter ... I am stuck right there, no idea how to move on (enter doesnt do the trick, nor my google account name ...)
the good news is, other than that the tab behaves pretty normal (volume rockers really increase/decrease volume, keyboard works normal, i can get into a (chinese) shut down menu and it shuts down pretty normally (as opposed to a hard reboot)
would a hongkong 3.2 pit file help with mounting the e: drive?
any thoughts
thx, Al
Enter your password
Sorry, please retry!
word by word translation as you requested.
Sent from my GT-P6800 using xda app-developers app
bruce16878 said:
Enter your password
Sorry, please retry!
word by word translation as you requested.
Sent from my GT-P6800 using xda app-developers app
Click to expand...
Click to collapse
the /data partition is corrupted... you need to repair it for the device to be fully functional.
edan1979 said:
the /data partition is corrupted... you need to repair it for the device to be fully functional.
Click to expand...
Click to collapse
any pointers on HOW ¿¿¿¿
thx, Al
read this guide carefully http://forum.xda-developers.com/showthread.php?t=1862294
ONLY FOLLOW PART 3 to check your /data partition... starting from this point
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
edan1979 said:
read this guide carefully http://forum.xda-developers.com/showthread.php?t=1862294
ONLY FOLLOW PART 3 to check your /data partition... starting from this point
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
Click to expand...
Click to collapse
Hi there,
there def. is a problem in the /data directory ... it cannot be mounted and it cannot be formated out of cwm v5.0.2.7
below i have a snip of what I did with e2fsck ... there seem to be some problem
_____________________________
C:\Program Files\Android\android-sdk\platform-tools>adb devices
List of devices attached
46411980122B42BE recovery
C:\Program Files\Android\android-sdk\platform-tools>adb shell
~ # e2fsck -yfDC0 /dev/block/mmcblk0p10
e2fsck -yfDC0 /dev/block/mmcblk0p10
e2fsck 1.41.6 (30-May-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
10
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # e
C:\Program Files\Android\android-sdk\platform-tools>
_____________________
what is my problem with e2fsck¿
thx,
al
Step by step you will get there.
Regards,
Axelman
Axelman8 said:
Step by step you will get there.
Regards,
Axelman
Click to expand...
Click to collapse
Just to close this chapter ... and for reference to other future folks ...
I managed to get my tab working again, but it was a pita to get there ...:laugh: ... good thing - i learnt a lot in the process
finally i ran a check on the data partition (tool from the superbrick thread) ... and whilst all sectors reported "OK", there was a section where the check took some 10 times longer than normal.
I then used the .pit files provided from the superbrick thread, flashed those with odin, with the option "enable repartition", b/c thats what the .pit files does ... I was quite nervous doing so, though ... I was on the generous side with the "non usable" sectors on the data partition ... so my 7.7 now only has about 8gig of internal SD - I lost about half of it :crying:
then cleared the cache/data/davlic in cmw 6.x ... and flashed the original 3.2 rom over, which booted up - then flashed the shangha ( or so ?) Rom from the developer section a slim version of ICS 4.0.4.... and voilá ... the tab runs like a champ!
cheers,
al
If ever there was a bullet-proof "brick", I just created one. Rooted my phone. Had just changed the recovery file, but was testing and clicked "Reboot in Recovery Mode", and the file probably was copied over badly. Nevertheless, I'm stuck looking at a phone with the SAMSUMG letters and nothing else. Or if I take out and place back in the battery, with the battery image that is empty, but locks before it ever shows the green battery level.
And I can't break out of booting in recovery mode, no matter what I try.
If there is any help for this, I would very much appreciate it. Thanks.
See if you can get into download mode, vol up/down buttons, usb plugged in, connected to pc, and then put battery in (no power button). The use either Heimdall or Odin. Follow this link to get to them. Make sure you have correct drivers and follow instructions.
http://forum.xda-developers.com/showthread.php?p=25111013
Sent from my SGH-I997 using xda premium
At work, so will try that at home. Will update here. Thanks.
psal217050 said:
See if you can get into download mode, vol up/down buttons, usb plugged in, connected to pc, and then put battery in (no power button). The use either Heimdall or Odin. Follow this link to get to them. Make sure you have correct drivers and follow instructions.
http://forum.xda-developers.com/showthread.php?p=25111013
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Here's some more information and direct links to the Odin and Heimdall threads. You can disregard the first paragraph.
http://forum.xda-developers.com/showpost.php?p=39488904&postcount=17
I've been going through that and related information. The knowledge here is most appreciated, although it didn't guarantee I wouldn't make a mistake. However, my phone is back in shape, and I'm marching on with finishing all of the steps for a rooted and appreciable Infuse.
Thanks
Zen Arcade said:
Here's some more information and direct links to the Odin and Heimdall threads. You can disregard the first paragraph.
http://forum.xda-developers.com/showpost.php?p=39488904&postcount=17
Click to expand...
Click to collapse
Got my phone back, and have rooted and unlocked it. Thanks for all of the info.
Am finding a big hurdle with getting a CWM recovery installed.
Have read and put into /sdcard most of the recovery zips found here, made sure that with each attempt, that particular zip was renamed to update.zip, and still I have been unable to get past the signature error. The recovery mode results are at the bottom of this post. I followed the video that showed how to take the recovery file, rename the current to recovery.orig, put it in place, but that is how I got locked up in the first place, so have been a little bit hesitant to go there again.
Will be swamped until tomorrow evening, so will continue on with attempting to flash my way past it with Odin.
Zen Arcade said:
Here's some more information and direct links to the Odin and Heimdall threads. You can disregard the first paragraph.
http://forum.xda-developers.com/showpost.php?p=39488904&postcount=17
Click to expand...
Click to collapse
Android system recovery <3e>
Samsung Recovery Utils
- For BML -
Enter: POWER Key, Select : Vol UP / Vol Down
reboot system now
reinstall packages
delete all user data
delete cache data
format internal sd-card
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
-- Movi_check already executed!!...
-- movi_checking done!...
update media, please wait
update media, finished
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
Install default apk-files, please wait
Install default apk-files, finished
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
You run Odin and Heimdall from your PC and flash to your phone while it is in download mode (not recovery mode) via USB cable. Read the instructions on the posts I referenced from the link I provided above. You will also need the proper Samsung drivers installed on your PC (and the Java JRE for Heimdall). Read the appropriate OPs thoroughly - links are provided.
update.zip only works to flash properly signed firmware, modem and kernel packages. Most of the custom packages here are not signed and require an unsecure recovery (CWM or TWRP) to flash. Renaming will not accomplish anything.
To convert from froyo to GB or above you may need to flash bootloaders (risky). To convert back from JB (4.1, 4.2) to GB you will need to flash an Odin or Heimdall package with a a PIT file (repartitions storage). The links I provided supply options for both. At the end of that process you will have stock firmware, and depending on option selected it may be rooted and it may have a custom recovery (red CWM). From there you can explore flashing custom firmware... again, read any ROM OP completely for instructions. For JB start with Andros11's guide.
Will do, and will post an update back here.
Have read a lot here, and the contributions are very appreciated. I have been in development for 36+ years, kept my brain cells from rotting, and followed the changing technologies (my profile url should show the details). Have developed small apps for Android, more complex apps for Windows Mobile, and am hoping to update to the latest and greatest Android versions with all bells and whistles, simply as a learning exercise.
Again, thank you. Much appreciated.
WOOHOO!!!!!!
The fast-path for me was Heimdall One-Click SGH-I997Jt1134-ICS-Kernel, followed by flashing the CM9 zip.
Okay, now I'm a kid in a candy store.
Believe me, it takes some reading, but it's worth it. Seems so simple once done, but it cannot be taken for granted.
Thanks to you guys and this website. Seriously, am respectfully impressed and with genuine gratitude for the effort that is being put here.
And now I'm up to 4.2.2 from the 3/24/2013 update. Once you break through, it's quite straightforward and systematic from there. Even the mistakes were good experience. Again, thank you.
TulsaDavid said:
And now I'm up to 4.2.2 from the 3/24/2013 update. Once you break through, it's quite straightforward and systematic from there. Even the mistakes were good experience. Again, thank you.
Click to expand...
Click to collapse
pay if forward:
http://forum.xda-developers.com/showthread.php?t=2211790