Related
To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium
I didn't want to clutter up the dev thread with these questions, but I've never used any CM build on any phone.
I unzipped Bryan's CM7 build to see what was inside and noticed it didn't seem to have a launcher and didn't seem to have any market app. Ok so does that mean you have to pre install Google apps from the SDcard to be able to access the market?
In reading the instructions, it seems like Bryan's CM7 build uses the same kernel as his regular beta kernel thread but that can't be right, can it, with the discussion on the thread....
I noticed that the Google apps were all modified for CM7, so does that mean that ordinary apps won't work unless they're modified?
Can I still use the TW4 launcher on CM7? Used to it.
The business about USB storage not working in Android. I assume that means you can't put anything on the SDcard using the USB cable after Android has booted up so that you have to push everything on there with ADB, is that it, in recovery mode?
1. It does contain a launcher; Its called ADW Launcher.
2. Yes, you would need to flash the google apps. I use this one
http://goo.im/gapps/gapps-gb-20110828-signed.zip
and this one http://goo.im/gapps/gapps-gb-20110828-newtalk-signed.zip​
3. You flash the gapps-gb-20110828-signed.zip file then the gapps-gb-20110828-newtalk-signed.zip google talk with video chat support.
4. Its a different kernel. CM7 is using the MTD version. While regular stock roms use BML.
5. I believe you can use the google apps on those files on any rom. But most roms already bring them integrated.
6. Apps developed for use on the Galaxy S phones like TWLauncher et al will not work as they hook onto some samsung specific programming.
7. As mentioned in 6, you cannot use TWLauncher on cm7.
8. Yes you would have to push everything through ADB in the meantime. Pushing/puling through adb does not require rebooting to recovery though.
Can someone make a video on how to install the rom?
Just follow the written instructions on the thread and you'll be fine
Sent from my SGH-T959V using xda premium
Honestly they confuse the crap outta me. A video would dumb it down for me and im sure a few others.
IDK how the heck I made my efs backup.
But if anyhow, you manage to make some sort of a tar file with your efs files, you should be fine.
After that,
do the erase_image
and mount /efs
and cd /efs
and tar xf anybackupname.tar
you will install. That is if you get your.
Donte21 said:
Honestly they confuse the crap outta me. A video would dumb it down for me and im sure a few others.
Click to expand...
Click to collapse
My suggestion is to wait until the install procedure is easier.
In the CM7 OP, Bryan said (twice) to re-read OP after updates.
Making a video will give you proper instructions for this build, but if Bryan updates the install procedure users following the video are going to have a mixed bag of results, and possible bricks.
Sent from my SGH-T959V using Tapatalk
when I try to Heimdall the boot.img I get a warning that says Tar header contained an invalid file size.
cybok0 said:
when I try to Heimdall the boot.img I get a warning that says Tar header contained an invalid file size.
Click to expand...
Click to collapse
Are you using the heimdall command prompt? Or the heimdall program?
Sent from my SGH-T959V using xda premium
Juls317 said:
Are you using the heimdall command prompt? Or the heimdall program?
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Program, I just started reading the one click guide, I think I should of tried that first right?
---------- Post added at 09:58 AM ---------- Previous post was at 09:48 AM ----------
I will have to try this on my day off, a lot of reading and understanding to do.
cybok0 said:
Program, I just started reading the one click guide, I think I should of tried that first right?
---------- Post added at 09:58 AM ---------- Previous post was at 09:48 AM ----------
I will have to try this on my day off, a lot of reading and understanding to do.
Click to expand...
Click to collapse
You need to follow Bryan's instructions EXACTLY, a in use the heimdall command prompts
Sent from my SGH-T959V using xda premium
OK, I think I'll stick with VB, I'm not this tech savvy.
I'm going to make a video guide tonight hopefully, but of course I'm going to leave the explicit direction that noobs should not flash it
Sent from my SGH-T959V using xda premium
I have a question as well. Yes, I know that this isnt exactly high priority, but I'm wondering if later there will be a build with Wifi calling. I was trying to install it myself, but it kept force closing, and I don't wanna try anything that'll mess up my phone any worse than I have before.
Wifi calling is basically a must for me since I basically live in Smallville, KS. I get little to no service here, and without it, it usually takes forever to get anything. And yes, I've tried every modem I could, KG4 works best, since I can sometimes get one bar.
I'm trying to complain or anything, and I thank Team Acid for bringing us CM7.
Neo I'm sure at one point bryan will get that working.
Sent from my SGH-T959V using Tapatalk 2
elmejor183 said:
6. Apps developed for use on the Galaxy S phones like TWLauncher et al will not work as they hook onto some samsung specific programming.
Click to expand...
Click to collapse
So does that mean that NONE of the apps will work unless modified to run on CM7? Or are you just talking about certain Samsung issued apps? I'm in the middle of an old Tarzan novel on my e-reader program on the phone...
I have a question with the process flash boot.img with heimdall...when i open heimdall front end and put boot.img into the flash local package..i get a error the tar header contained an invalid file size..on the flash tab, it only takes pit files..also when i just use the heimdall ..a black screen happens similar like a command prompt and just exits..
how do i flash the boot.img with heimdall?
This is using fbs instructions that I am using and i am stuck on step 7. flash the latest boot.img from bryans op..
http://forum.xda-developers.com/showpost.php?p=25197350&postcount=279
Are you on windows? If so open command promt. Cd into the heimdall suite directory. Put your phone in DL mode and connect to usb. From command type "heimdall detect". Should say device detected. Then just put the boot.img in the same directory and follow the OP.
nazcalito said:
So does that mean that NONE of the apps will work unless modified to run on CM7? Or are you just talking about certain Samsung issued apps? I'm in the middle of an old Tarzan novel on my e-reader program on the phone...
Click to expand...
Click to collapse
That's just Samsung-specific stuff like TouchWiz that require Samsung's modified frameworks and extra libraries.
Just use FB's install guide instead. I was going to wait until it was installable through CWM, but this is essentially the same thing with a few extra steps.
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
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
SlickAl41 said:
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
Click to expand...
Click to collapse
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Ryanscool said:
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
Click to expand...
Click to collapse
Heimdall did it. Thanks for pointing me that direction. :highfive:
SlickAl41 said:
Heimdall did it. Thanks for pointing me that direction. :highfive:
Click to expand...
Click to collapse
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
SlickAl41 said:
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
Click to expand...
Click to collapse
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Ryan79 said:
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Click to expand...
Click to collapse
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
SlickAl41 said:
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
Click to expand...
Click to collapse
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
SlickAl41 said:
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
Click to expand...
Click to collapse
Hey Alan, sorry... been away from the forums for a couple days. But it looks like you got it figured out you are correct on the Heimdall command, the only thing different that I did is that I already had root explorer purchased... so after the SuperUser install I just ran it to move the install_recover.sh to my SD card
Glad to hear you got it working!
I am trying to Flash the Stock ROM on my Galaxy Y PRO after it is gone into a bootloop (by itself), i am using ODIN , but it got stuck on Flashin the recovery img
i tried all The USB ports of my computer and only 1 worked. Please i need help and a sure answer thx
MultipleMonomials said:
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Click to expand...
Click to collapse
How to use Heimdall when I have bl, ap, etc
Hello, just making sure I haven't missed a step or process somewhere. I have the ota stock build of jellybean 4.1.1 on my Verizon galaxy s3.
I've looked through several methods, from different websites, and it will either be for Windows only, or the international s3 or for ics.
So no CASUAL, or anything else that I saw.
Heimdall apparently does not work on the US s3's.
I even tried to root with Odin on Windows, but I had some problems with Odin (when it says it was done, apparently it wasn't done, and I could not get clockwork mod to flash)
I would try it again, but it wasn't on my pc, but a friend's, so it is a pain to schedule a time to get over there. I would much prefer to have all the tools on my person, etc. It helps me to understand the process better.
Also, I heard about cfautoroot, however, I didn't get a chance to fully investigate that method. Any thoughts?
So, am I correct?
Any way to use terminal and adb?
Please let me know if I am wrong, I would love to be!
Sent from my Nexus 7 using Tapatalk HD
funkpod said:
Hello, just making sure I haven't missed a step or process somewhere. I have the ota stock build of jellybean 4.1.1 on my Verizon galaxy s3.
I've looked through several methods, from different websites, and it will either be for Windows only, or the international s3 or for ics.
So no CASUAL, or anything else that I saw.
Heimdall apparently does not work on the US s3's.
I even tried to root with Odin on Windows, but I had some problems with Odin (when it says it was done, apparently it wasn't done, and I could not get clockwork mod to flash)
I would try it again, but it wasn't on my pc, but a friend's, so it is a pain to schedule a time to get over there. I would much prefer to have all the tools on my person, etc. It helps me to understand the process better.
Also, I heard about cfautoroot, however, I didn't get a chance to fully investigate that method. Any thoughts?
So, am I correct?
Any way to use terminal and adb?
Please let me know if I am wrong, I would love to be!
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
heimdall does actually work
this should help you: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw#Flash_alternate_bootloader_and_custom_recovery
no promises on the mac thing, i compiled that in a hacky osx vm, but i haven't heard of any problems, make sure to copy the lib
EDIT: ah crap, just realized utkanos didn't post the mac heimdall there, here's the one i compiled: http://invisiblek.org/heimdall_v1.4rc1_mac.zip
good luck, let me know if it works please
invisiblek said:
heimdall does actually work
this should help you: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw#Flash_alternate_bootloader_and_custom_recovery
no promises on the mac thing, i compiled that in a hacky osx vm, but i haven't heard of any problems, make sure to copy the lib
EDIT: ah crap, just realized utkanos didn't post the mac heimdall there, here's the one i compiled: http://invisiblek.org/heimdall_v1.4rc1_mac.zip
good luck, let me know if it works please
Click to expand...
Click to collapse
Hello, thank you! So, this is the new version of Heimdall that I read about that should fix the incompatibility in 1.3.2?
http://www.xda-developers.com/android/heimdall-the-bringer-of-illumiation-enters-a-new-age/
And you have used it, but only on emulated ios? Question...What could happen to my phone?
Sent from my Nexus 7 using Tapatalk HD
funkpod said:
Hello, thank you! So, this is the new version of Heimdall that I read about that should fix the incompatibility in 1.3.2?
http://www.xda-developers.com/android/heimdall-the-bringer-of-illumiation-enters-a-new-age/
And you have used it, but only on emulated ios? Question...What could happen to my phone?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
yes, its 1.4rc1 which supports the sgs3
first thing i'd recommend doing is:
Code:
heimdall print-pit
it's gonna print out your partition table, then reboot your phone, but at least you know you are talking to the phone properly
after that you should have no problem flashing via the rest of the instructions on the cm wiki there
hey, it did this after i double clicked the Heimdall exec file.
"
Teacher107MBP6-20-2012:~ teacher$ /Users/teacher/Desktop/heimdall_v1.4rc1_mac/heimdall ; exit;
dyld: Library not loaded: /opt/local/lib/libusb-1.0.0.dylib
Referenced from: /Users/teacher/Desktop/heimdall_v1.4rc1_mac/heimdall
Reason: no suitable image found. Did find:
/usr/local/lib/libusb-1.0.0.dylib: stat() failed with errno=13
Trace/BPT trap: 5
logout
[Process completed]
"
my phone was not connected yet. was this okay?
hey, so i plugged in my phone and double-clicked on the Heimdall file, the executable file.
the same
PHP:
Last login: Mon Jan 28 20:37:11 on ttys000
Teacher107MBP6-20-2012:~ teacher$ /Users/teacher/Desktop/heimdall_v1.4rc1_mac/heimdall ; exit;
dyld: Library not loaded: /opt/local/lib/libusb-1.0.0.dylib
Referenced from: /Users/teacher/Desktop/heimdall_v1.4rc1_mac/heimdall
Reason: no suitable image found. Did find:
/usr/local/lib/libusb-1.0.0.dylib: stat() failed with errno=13
Trace/BPT trap: 5
logout
[Process completed]
This is what happened, again. So i can't type the heimdall Print-pit command that you suggested.
any ideas about how to proceed?
Adam Outler and others are working on getting heimdall as an installer package for osx, and updating Casual we just have to wait.
Sent from my SCH-I535 using xda app-developers app
REALLY!? that's totally awesome.
that's great. any progress? like in a week, a month, 2 months, etc?
if i can't get Heimdall working on my own, which I probably can't, i'll just be patient then.
SO... i heard that Casual might work for the Galaxy sIII again?