Related
I hope there is a way for me to fix this. I am a noob but, I have been successful flashing things a few times in the past (and not so lucky a few times). This time I had flashed my Infuse back to stock 2.2 Froyo UCKD5 after having Zues w/ Aries HellFire running for a couple weeks. I decided to try another ROM because I was bored. Then I screwed something up thinking I knew more than I do. As I was trying to clean things up in my files to get ready to do a back-up,something happened and about half of my apps,factory and 3rd party had no files or ?? They didn't show any MB in cache / data,in TIBU or App Mgr, only "computing...", and obviously things didn't work right. So I hit the phone's Factory Reset,went into Odin3 thinking I would try doing something I never tried before,stupid me, and installed through the PDA button, zimage root tar file, success, saw the Fugu fish and then reset Odin, turned off/ on. Pulled battery from phone, usb jig to download mode, because three button method wasn't working. I thought it had something to do with the residual kernel or bootloader from Zeus. The kernel that was running is 2.6.32.9 and I don't know what that is. Any way I thought I would install KF1 .tar Odin3 installed it but it got stuck on the Samsung power-up screen,black background white Samsung letters. I usb jigged into download mode , thinking maybe I had the wrong drivers possibly and did the Heimdall Zadig driver install, nothing changed. So, I thought that I better just reflash to stock using GTG's Ultimate Unbrick, used the UCKD5 tar and it passed. Then I unplugged the phone when it shut off to reboot, it booted into blue recovery and I hit reboot and it came right back into blue recovery. I am able to get into download mode or into the ever looping blue recovery<3e>,but nothing else. No programs,Odin, Kies, Heimdall,GTG's, recognize the phone,the laptop does and says the device may not work correctly..., but I did notice what the fails were in the recovery boot-up. So I snapped pics with my Captivate and uploaded them and I will paste them here (I think XDA lets idiots like me paste in this area?). they are readable, but if I need to type everything out I can, but not until someone asks so as to keep this already lengthy story a bit shorter. Thanks in advance,KK13/khkaiser13. sent in using my Rooted Captivate on APEX12 through XDAPremium View attachment 899419
View attachment 899420
Did you try clicking flash in Heimdall, sometimes it looks like it doesn't see the phone, but you click flash and it works. Also, have you tried clearing user data and cache? (I know you said you had factory reset at one point but now that you are stuck might be worth a try.) Looks like a boot loader issue, not sure why Heimdall doesn't see the phone, I've had good luck in the past with it.
I'm tempted to tell you to format the internal sd and try heimdall again, but maybe someone with more experience would have a better idea.
khkaiser13 said:
I hope there is a way for me to fix this. I am a noob but, I have been successful flashing things a few times in the past (and not so lucky a few times). This time I had flashed my Infuse back to stock 2.2 Froyo UCKD5 after having Zues w/ Aries HellFire running for a couple weeks. I decided to try another ROM because I was bored. Then I screwed something up thinking I knew more than I do. As I was trying to clean things up in my files to get ready to do a back-up,something happened and about half of my apps,factory and 3rd party had no files or ?? They didn't show any MB in cache / data,in TIBU or App Mgr, only "computing...", and obviously things didn't work right. So I hit the phone's Factory Reset,went into Odin3 thinking I would try doing something I never tried before,stupid me, and installed through the PDA button, zimage root tar file, success, saw the Fugu fish and then reset Odin, turned off/ on. Pulled battery from phone, usb jig to download mode, because three button method wasn't working. I thought it had something to do with the residual kernel or bootloader from Zeus. The kernel that was running is 2.6.32.9 and I don't know what that is. Any way I thought I would install KF1 .tar Odin3 installed it but it got stuck on the Samsung power-up screen,black background white Samsung letters. I usb jigged into download mode , thinking maybe I had the wrong drivers possibly and did the Heimdall Zadig driver install, nothing changed. So, I thought that I better just reflash to stock using GTG's Ultimate Unbrick, used the UCKD5 tar and it passed. Then I unplugged the phone when it shut off to reboot, it booted into blue recovery and I hit reboot and it came right back into blue recovery. I am able to get into download mode or into the ever looping blue recovery<3e>,but nothing else. No programs,Odin, Kies, Heimdall,GTG's, recognize the phone,the laptop does and says the device may not work correctly..., but I did notice what the fails were in the recovery boot-up. So I snapped pics with my Captivate and uploaded them and I will paste them here (I think XDA lets idiots like me paste in this area?). they are readable, but if I need to type everything out I can, but not until someone asks so as to keep this already lengthy story a bit shorter. Thanks in advance,KK13/khkaiser13. sent in using my Rooted Captivate on APEX12 through XDAPremium View attachment 899419
View attachment 899420
Click to expand...
Click to collapse
Before you go any further,
Read my how to..click on the first link on my sigs.
Read through several times.
There is a BIG difference b/t download mode and recovery.
Thanks, I did clear Data/Cache. I also did format the sd as a last resort but, it didn't help. I don't know if you looked at the screenshots I posted but, it says Checksum Fail and Movinand Checksum Fail. I dont know what either of those are but, willing to bet if someone knows it might be repairable. Thanks Again, to both, enochpc and qkster for the helpful info which I did not know before. khkaiser13/ kk13
khkaiser13 said:
Thanks, I did clear Data/Cache. I also did format the sd as a last resort but, it didn't help. I don't know if you looked at the screenshots I posted but, it says Checksum Fail and Movinand Checksum Fail. I dont know what either of those are but, willing to bet if someone knows it might be repairable. Thanks Again, to both, enochpc and qkster for the helpful info which I did not know before. khkaiser13/ kk13
Click to expand...
Click to collapse
Put your phone in download mode. Odin or heimdall back to stock and start over.
Don't worry about anything else as long as you can get into dl mode
Hey, thanks for responding. I know the difference b/t recov. and dload. I am stuck in recovery<3e> blue, it just returns the recovery screen no matter if I press reboot, clear cache, or clear data, or try install zip. But if I usb jig it, it goes into download mode. Thats it. What I have and don't know what or how to fix is during the reboot attempt (you can read it if you click on my screenshots) it says Checksum Fail, Movinand Fail, and lfs undone. I'm gonna try to find out more about those files ( I guess thats what those would be ???) Thanks Bro.
khkaiser13 said:
Hey, thanks for responding. I know the difference b/t recov. and dload. I am stuck in recovery<3e> blue, it just returns the recovery screen no matter if I press reboot, clear cache, or clear data, or try install zip. But if I usb jig it, it goes into download mode. Thats it. What I have and don't know what or how to fix is during the reboot attempt (you can read it if you click on my screenshots) it says Checksum Fail, Movinand Fail, and lfs undone. I'm gonna try to find out more about those files ( I guess thats what those would be ???) Thanks Bro.
Click to expand...
Click to collapse
You borked something in the ROM. That's why it won't boot. Files mismatch and don't add up. That's why you're in blue recovery.
You've to get into dl mode and flash a stock ROM img. Then start over.
qkster said:
You borked something in the ROM. That's why it won't boot. Files mismatch and don't add up. That's why you're in blue recovery.
You've to get into dl mode and flash a stock ROM img. Then start over.
Click to expand...
Click to collapse
Just to add this to what qkster said! I know you said you know the difference but be sure to have proper drivers installed I personally used GTG’s Ultimate Unbrick with 100% success. If there is any doubt about bad drivers I would also suggest reinstalling them there is a very easy to use Utility called usbdeview that lets you uninstall drivers and start fresh.
Let's see, where shall I begin?
Got my phone back from my girlfriend since she bought the Nexus 4. Battery was extremely swollen and because of that, the phone basically didn't work. Constantly restarting, couldn't use data, etc... Bought a new battery and decided that I would get a nice fresh ROM installed to get this thing running nice again. It has been on Valhalla for about a year now, and I tried to jump straight to the ICS milestone ROM that I saw in Development. Unfortunately, I didn't know of the new CWM that I was supposed to have, which results in a nice little brick. Frozen at the Boot screen. I was able to get it back into download mode with the volume buttons+cable method and luckily Odin recognized it. I installed a really old KD1 Rom that I had which appears to be all the way back to Froyo.
Now that you are up to speed, the phone boots up fine and seems to be working, but nothing in CWM works at all. Everything fails to mount, which means I can't flash any zips to get off this ROM. To top that off, Odin stopped recognizing it in download mode after I installed that other ROM.
It's been too long since I have been on this phone, and within a couple hours of messing with it again, I can see that I have obviously fallen behind on the development. Any suggestions as to what I should do next? My goal is the get it up to the newest ROMs and see how well it runs. I have the Basic with a twist kernel and ICS milestone ROM ready to go, but no way to flash them.
Thank you to anyone who took the time to read this.
Follow this to the tee
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Don't forget to flash bootloader's since you got into Froyo!
Unless you need to, don't flash back to Froyo. Always flash back to stock Gingerbread.
Once you do that flash a another one-click package to get a CWM recovery.
th3controller said:
Follow this to the tee
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Don't forget to flash bootloader's since you got into Froyo!
Unless you need to, don't flash back to Froyo. Always flash back to stock Gingerbread.
Once you do that flash a another one-click package to get a CWM recovery.
Click to expand...
Click to collapse
I didn't even realize it was a Froyo rom, to be honest. I would go and search for a Gingerbread Rom, but the "All roms/rooting/FAQS....." sticky in the development section has been updated in such a long time. I decided to take my chances on that one instead of looking through tons of threads. Froyo was the only one I had for Odin at the moment unfortunately, and Odin was all that I could use.
Thank you so much for the help! This phone should be up and running again in no time!
Don't forget to delete drivers! Odin and Heimdall don't play too well together!
th3controller said:
Don't forget to delete drivers! Odin and Heimdall don't play too well together!
Click to expand...
Click to collapse
Just the Samsung Drivers? I'll try to find them all.
Well, looks like the guide isn't going to work very well for me. I got all the way up to installing drivers with zadig. Heimdall opened automatically like I installed it before ( I may have, it has been forever), but zadig never did. I had to trick it into opening. Once it did open, my phone never shows up in the list of devices as a Samsung device. It only shows up as "Unknown device" and there are no drivers for it to install.
With the phone plugged in download mode, go into device manager delete all USB drivers, reboot pc. Next time you plug in the phone windows should prompt you to install drivers, don't. Use zadig.
TwitchyEye said:
With the phone plugged in download mode, go into device manager delete all USB drivers, reboot pc. Next time you plug in the phone windows should prompt you to install drivers, don't. Use zadig.
Click to expand...
Click to collapse
Finally got around to working on my phone again. Unfortunately, I am unable to follow the guide how I was supposed to. Fortunately, on the other hand, it appears that I successfully got it to flash gingerbread.
Here were my steps to get it work if you want a laugh. My computer didn't like the procedure that the guide had.
1. Update Java, download file, place file into C drive, etc... Everything up to this point worked fine.
2. Open command prompt and execute command. (This is where it all went crazy)
3. Command says false. (instead of opening Zadig, my computer immediately opened Heimdall. So how do I install drivers?)
4. Went to Heimdall help menu and selected install, which froze heimdall completely. Upon Heimdall crashing, Zadig opens.
5. Open Zadig. All drivers are uninstalled, but my device can't be found in the list. (Right after here is where to told me to reboot.)
6. Reboot. Windows keeps automatically installing drivers and I can't do anything about it, so I just uninstall them and try again.
7. Same process. Command prompt, heimdall opens early, crash heimdall, open Zadig, SUCCESSFULLY install drivers.
8. Command prompt again, because that is my only way of getting heimdall open
9. Heimdall finds device, try to flash, but it fails.
10. Unplug phone, and plug in again. Heimdall finds it again.
11. Try to flash again, and success.
It was kind of a nightmare getting it to work, but it looks like it will fix it finally. Thanks for the help everyone!
Double-flashing with Heimdall seems fairly standard. When that happens, sometimes you don't actually have to unplug the phone again, just repeat the same flash-command and it should work the second time. If that doesn't work, reboot the phone, it should go to panic-download mode where it doesn't boot to launcher anymore, just shows the yellow exclamation mark screen, and there the flash should work.
Both my SGS4G and my wife's have done this since we first got them. Sometimes.
Samsung Galaxy s 4g T959V-Gingerbread. Rooted it with SuperOneClick... Didnt have CWM. when I tried to install Black Ice and ICNINB. Tried doing with Rom Manager. Then read that doesn't work with this phone. Was able to flash AltonX KJ6 kernal through SGS kernel flasher in order or get CWM on the phone. That worked. But when I went to flash the zip files for the roms again. They still didn't work. I thought I was following the directions. Get into download mode> create a backup> wipe data> make sure the mounts were right> then flash the zip file. Well the first time I did i,t it kinda went through. Although I didn't have RED CWM or Linda. Wanted to get Voodoo and LagFix. So I decided to flash again. When it came time to reboot.. it got stuck in a loop between two different Samsung screens.One with a big swoopy S the other just the normalt-mobile samsung screen before it boots up. Going from one to the other never really rebooting. So again I decided to get into download mode again and then flash a recovery backup file. And NOW it just hangs on the Samsung T-Moblie screen. I've tried battery pulls also tried using a JIG. Screen pops up but just freezes there.
Any suggestions??
pistol865 said:
Samsung Galaxy s 4g T959V-Gingerbread. Rooted it with SuperOneClick... Didnt have CWM. when I tried to install Black Ice and ICNINB. Tried doing with Rom Manager. Then read that doesn't work with this phone. Was able to flash AltonX KJ6 kernal through SGS kernel flasher in order or get CWM on the phone. That worked. But when I went to flash the zip files for the roms again. They still didn't work. I thought I was following the directions. Get into download mode> create a backup> wipe data> make sure the mounts were right> then flash the zip file. Well the first time I did i,t it kinda went through. Although I didn't have RED CWM or Linda. Wanted to get Voodoo and LagFix. So I decided to flash again. When it came time to reboot.. it got stuck in a loop between two different Samsung screens.One with a big swoopy S the other just the normalt-mobile samsung screen before it boots up. Going from one to the other never really rebooting. So again I decided to get into download mode again and then flash a recovery backup file. And NOW it just hangs on the Samsung T-Moblie screen. I've tried battery pulls also tried using a JIG. Screen pops up but just freezes there.
Any suggestions??
Click to expand...
Click to collapse
you don't want voodoo lagfix. unreliable, imho.
Try eollie's stock + root in the second post my oneclick thread. It's a stock rom and blastoff v2.5.
Run the oneclick the first time to flash just the kernel and rom.
Click flash bootloaders.
reboot phone to download mode again
flash again, this time with bootloaders.
After that, you should be golden.
Don't forget to read the directions in the OP.
bhundven said:
you don't want voodoo lagfix. unreliable, imho.
Try eollie's stock + root in the second post my oneclick thread. It's a stock rom and blastoff v2.5.
Run the oneclick the first time to flash just the kernel and rom.
Click flash bootloaders.
reboot phone to download mode again
flash again, this time with bootloaders.
After that, you should be golden.
Don't forget to read the directions in the OP.
Click to expand...
Click to collapse
Thank you so much for getting back to me. A couple of questions if I may?
1) if I'm able to get the samsung screen, does that mean I'm able to get into Download mode? It just seems to hang on that samsung T-Mobile screen.
2) The link to dropbox that I'm supposed too click on, seems to be broken... Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel)- https://dl.dropboxusercontent.com/u/10373328/Stock KJ6 + root-One-Click.jar -
Here's what comes up: Error (404)
We can't find the page you're looking for. Check out our Help Center and forums for help, or head back to home.
3) Assuming that I'm able to get to download mode, I just want to check to make sure that I'm reading your directions correctly.
- when I run OneClick the 1st time, it will automatically apply just the kernel and rom.
- Then I'm supposed to reboot? Or flash the bootloaders?
- After that I'm supposed to reboot phone to download mode again.
- Flash Bootloaders again??
I'm sure I'm messing up the directions or rather misreading them.
Sorry for that. Kinda NOOB when it comes to HEIDENALL
pistol865 said:
Thank you so much for getting back to me. A couple of questions if I may?
Click to expand...
Click to collapse
Well, seeming it is the Q&A forum
pistol865 said:
1) if I'm able to get the samsung screen, does that mean I'm able to get into Download mode? It just seems to hang on that samsung T-Mobile screen.
Click to expand...
Click to collapse
Yes. Sometimes even if the phone seems to turn on and go to a black screen, you might still be able to get to download mode.
Seriously, this phone is like a tank... unless you flash gt-i9000 or vibrant roms. Then you will brick your phone.
pistol865 said:
2) The link to dropbox that I'm supposed too click on, seems to be broken... Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel)- https://dl.dropboxusercontent.com/u/10373328/Stock KJ6 + root-One-Click.jar -
Here's what comes up: Error (404)
We can't find the page you're looking for. Check out our Help Center and forums for help, or head back to home.
Click to expand...
Click to collapse
Dang, I'm uploading a new link to this. Give it 20 minutes. and go back and try the link again.
pistol865 said:
3) Assuming that I'm able to get to download mode, I just want to check to make sure that I'm reading your directions correctly.
- when I run OneClick the 1st time, it will automatically apply just the kernel and rom.
- Then I'm supposed to reboot? Or flash the bootloaders?
- After that I'm supposed to reboot phone to download mode again.
- Flash Bootloaders again??
I'm sure I'm messing up the directions or rather misreading them.
Sorry for that. Kinda NOOB when it comes to HEIDENALL
Click to expand...
Click to collapse
Put your phone into download mode, either by holding vol+ and vol- and plugging in the usb from your computer (keep holding vol+ and vol- till you see download mode) or use a jig.
Once your in download mode. Flash the first time. Yes, it will only flash the kernel and rom. The phone will automatically reboot after the flash.
Wait a little bit after the phone reboots, you'll see a little local update happen and reboot the phone again. Then pull the battery and put the phone back into download mode.
Then check the "flash bootloaders" checkbox. flash the oneclick again this time with bootloaders.
After this, you can go anywhere from this rom, except back to froyo. I'm still working on a simple oneclick method for going back to froyo.
bhundven said:
Well, seeming it is the Q&A forum
Yes. Sometimes even if the phone seems to turn on and go to a black screen, you might still be able to get to download mode.
Seriously, this phone is like a tank... unless you flash gt-i9000 or vibrant roms. Then you will brick your phone.
Dang, I'm uploading a new link to this. Give it 20 minutes. and go back and try the link again.
Put your phone into download mode, either by holding vol+ and vol- and plugging in the usb from your computer (keep holding vol+ and vol- till you see download mode) or use a jig.
Once your in download mode. Flash the first time. Yes, it will only flash the kernel and rom. The phone will automatically reboot after the flash.
Wait a little bit after the phone reboots, you'll see a little local update happen and reboot the phone again. Then pull the battery and put the phone back into download mode.
Then check the "flash bootloaders" checkbox. flash the oneclick again this time with bootloaders.
After this, you can go anywhere from this rom, except back to froyo. I'm still working on a simple oneclick method for going back to froyo.
Click to expand...
Click to collapse
Once again, many thanks for your time and patience
.Just wondering if you fixed that link yet?
I keep clicking on: Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel) , it takes me to this page: https://dl.dropboxusercontent.com/u/10373328/Stock KJ6 + root-One-Click.jar, but I'm still getting the message: Error (404)
We can't find the page you're looking for. Check out our Help Center and forums for help, or head back to home.
That link is Underneath the link: eollie: AntonX's BwaT + Stock Rom... on the page: http://forum.xda-developers.com/showthread.php?t=1358498 .
Again, pardon my detailed reply, but I just want to be sure that I'm clicking on the correct link.
pistol865 said:
Once again, many thanks for your time and patience
.Just wondering if you fixed that link yet?
I keep clicking on: Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel) , it takes me to this page: https://dl.dropboxusercontent.com/u/10373328/Stock KJ6 + root-One-Click.jar, but I'm still getting the message: Error (404)
We can't find the page you're looking for. Check out our Help Center and forums for help, or head back to home.
That link is Underneath the link: eollie: AntonX's BwaT + Stock Rom... on the page: http://forum.xda-developers.com/showthread.php?t=1358498 .
Again, pardon my detailed reply, but I just want to be sure that I'm clicking on the correct link.
Click to expand...
Click to collapse
Yea man. I updated the second post in the onclick thread. Here is the timestamp from the post: "24th July 2013 12:39 PM"
You need to clear the cache on your browser and reload that page. The link is here.
bhundven said:
Yea man. I updated the second post in the onclick thread. Here is the timestamp from the post: "24th July 2013 12:39 PM"
You need to clear the cache on your browser and reload that page. The link is here.
Click to expand...
Click to collapse
Ran into a new problem now...
It's me again... Sorry if I'm being a pain..
So I downloaded the link.. I have it on my desktop...I put my phone into download mode..(Yellow Triangle> Do not unplug).. I clicked on your OneClick... it loads but then tells me to connect my device... It keeps telling me I'm disconnected..
When I plug my phone into my compt via USB.. it now tells me that my device is unrecognized.
Now what did I do wrong?
I was hoping I was close to a resolution... another roadblock.
Can I fix it?
Once again, thank you for any and all the help and advice you have given me.
There is s thread called fresh out of the box now what. It will help you immensely. Sounds like you need to uninstall all samsung and android drivers and reinstall them. In that thread there is a application for your computer called usbview that can remove them (I probably misspelled that apps name). The thread is by lumin30.
limeaide said:
There is s thread called fresh out of the box now what. It will help you immensely. Sounds like you need to uninstall all samsung and android drivers and reinstall them. In that thread there is a application for your computer called usbview that can remove them (I probably misspelled that apps name). The thread is by lumin30.
Click to expand...
Click to collapse
I already installed usbDview.. ran as admisistrator... removed anything that said samsung or android.. plugged in my samsung phone and Still is not recognized. Also downloaded Zadig.. to install the drivers to the phone.. but it doesn't recognize the phone.
Anything else that I'm missing? Can I download something online so that when i plug in via USB it will recognize my phone?
You have tried different usb ports too? Other than that maybe a different computer. I know bhundven says dont use front usb ports too.
limeaide said:
You have tried different usb ports too? Other than that maybe a different computer. I know bhundven says dont use front usb ports too.
Click to expand...
Click to collapse
Tried different usb ports as well as a different computer.. When I hoked up to a different computer, at first it said it was installing the drivers.. then it stopped and said USB device Unrecognized.
Is it a matter of drivers? Can I get them offline? and then plug in my phone?
limeaide said:
You have tried different usb ports too? Other than that maybe a different computer. I know bhundven says dont use front usb ports too.
Click to expand...
Click to collapse
Computer pop up says: usb device has malfunctioned and windows does not recognize it.
limeaide said:
You have tried different usb ports too? Other than that maybe a different computer. I know bhundven says dont use front usb ports too.
Click to expand...
Click to collapse
I just went to the samsung website and downloaded the drivers from there.. Still having the same problem... usb device has malfunctioned and windows does not recognize it.
IIRC when you plug the phone in you need to stop it from installing the samsung drivers. Then use zadig to install them like illustrated in lumin30s guide.
Be sure to use a rear usb port if on a desktop. Dont change ports if things start to work. If you have to use a different port I suggest using usbdeview to remove drivers each time. It seems like overkill but it might work.
limeaide said:
IIRC when you plug the phone in you need to stop it from installing the samsung drivers. Then use zadig to install them like illustrated in lumin30s guide.
Be sure to use a rear usb port if on a desktop. Dont change ports if things start to work. If you have to use a different port I suggest using usbdeview to remove drivers each time. It seems like overkill but it might work.
Click to expand...
Click to collapse
ALMOST THERE.. I think..lol
I think I successfully ran the program.. phone turns on now.. Yayyy...
New Problem:
The screen now says:NO SIM CARD IN PHONE
AFTER YOU INSERT THE CARD, PLEASE REBOOT
EMERGENCY CALLS CAN BE USED
The SIM card is already installed... the phone is not recognizing it now.
What now??
limeaide said:
IIRC when you plug the phone in you need to stop it from installing the samsung drivers. Then use zadig to install them like illustrated in lumin30s guide.
Be sure to use a rear usb port if on a desktop. Dont change ports if things start to work. If you have to use a different port I suggest using usbdeview to remove drivers each time. It seems like overkill but it might work.
Click to expand...
Click to collapse
One more thing, I installed Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel)... That should mean the phone is rooted.. correct? although I don't see SUPERUSER in my apps list.. Also does this have CWM installed? Can I flash a custom rom moving forward?? If so which one do you consider the best? I originally was having trouble because I was running into low internal memory and couldn't download many apps. That's why I wanted to flash BLACK ICE originally.. I thought that would fix my problem..
This phone suffers from low internal memory. However you can move almost all apps to your sdcard from within the rom. If the things that do not work on the JB roms are ok with you I hear good things about those.
As for the sim card..Im not sure. The one click you used doesnt have SU included because it is a stock rom with custom rooted kernel. You would have to install it from the Play store. But I reccomend flashing a different rom anyway. Again the JB roms seem to be pretty awesome so that is a option.
limeaide said:
This phone suffers from low internal memory. However you can move almost all apps to your sdcard from within the rom. If the things that do not work on the JB roms are ok with you I hear good things about those.
As for the sim card..Im not sure. The one click you used doesnt have SU included because it is a stock rom with custom rooted kernel. You would have to install it from the Play store. But I reccomend flashing a different rom anyway. Again the JB roms seem to be pretty awesome so that is a option.
Click to expand...
Click to collapse
Did I do something wrong because I didn't pull the sim card when I flashed: Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel). Also does Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel) come with CWM Red?
pistol865 said:
Did I do something wrong because I didn't pull the sim card when I flashed: Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel). Also does Stock_KJ6_+_root-One-Click.jar (this has the blastoff v2 kernel) come with CWM Red?
Click to expand...
Click to collapse
reboot to cwm (recovery). wipe cache partition. advanced -> wipe dalvik cache. advanced -> fix permissions. reboot phone. Let it sit for a few minutes before doing anything (I'd say 10-15 minutes).
Oh weird. did that oneclick come with blastoff v2 and not 2.5?
Hmm, then do this. download blastoff v2.5, put that on your sdcard and install it from red cwm.
Then do what I said above. You should be back to blue after rebooting to recovery after flashing that kernel.
EDIT: if you really want red cwm (voodoo lagfix), I really don't know why you'd want that, but checkout my older subtly modified stock kernel.
bhundven said:
reboot to cwm (recovery). wipe cache partition. advanced -> wipe dalvik cache. advanced -> fix permissions. reboot phone. Let it sit for a few minutes before doing anything (I'd say 10-15 minutes).
Oh weird. did that oneclick come with blastoff v2 and not 2.5?
Hmm, then do this. download blastoff v2.5, put that on your sdcard and install it from red cwm.
Then do what I said above. You should be back to blue after rebooting to recovery after flashing that kernel.
EDIT: if you really want red cwm (voodoo lagfix), I really don't know why you'd want that, but checkout my older subtly modified stock kernel.
Click to expand...
Click to collapse
No..no.. I'll definitely take your word for it.. I'll stick with the blue. I just thought that with the lagfix, it would fix my problem with internal memory.
My problem now is my SIM card.. The phone reboots and I get : NO SIM CARD IN PHONE
AFTER YOU INSERT THE CARD, PLEASE REBOOT
EMERGENCY CALLS CAN BE USED]
I did as you said:
reboot to cwm (recovery). wipe cache partition. advanced -> wipe dalvik cache. advanced -> fix permissions. reboot phone. Let it sit for a few minutes before doing anything (I'd say 10-15 minutes).
Should I still install: download blastoff v2.5?
Thank you again for ALL your help.. You guys saved my phone..
I got my GNP 12.2 (SM-P900) a few weeks ago and just tried to root it using Odin and download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
However it paused at cache.img and after 10 minutes or so it just failed.
I've tried it a few times, but same thing, and on start up all I get is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I tried Kies 3 and Kies 2.6 but they both say my device is not supported, even if I try to go into Tools and do it it says the model name is incorrect and doesn't even give me an option to enter the serial number :-\
I looked around for a stock ROM but the closest I could find was the P901 and P905 (But I am the P900)
I don't really know what to do, so any advice would be much appreciated :angel:
Actually got Kies working, was just entering the model # wrong
This could probably be deleted / etc, not really sure how to do that
jns20 said:
Actually got Kies working, was just entering the model # wrong
This could probably be deleted / etc, not really sure how to do that
Click to expand...
Click to collapse
bump?
I'm having the same exact issue. I can get it into download mode. I've tried Kies several times and it keeps failing. Originally, I was using odin 3.07 to auto root on the sm-p900. During the process, the screen got this weird rainbow pixelated look, and odin told me the process has failed. It is now stuck on the error message "Firmware update has encountered an issue..."
Now I'm not really sure what to do. I've tried to reboot from download mode, and that sends me right back to the error message.
Any ideas?
ChampagneFerret said:
bump?
I'm having the same exact issue. I can get it into download mode. I've tried Kies several times and it keeps failing. Originally, I was using odin 3.07 to auto root on the sm-p900. During the process, the screen got this weird rainbow pixelated look, and odin told me the process has failed. It is now stuck on the error message "Firmware update has encountered an issue..."
Now I'm not really sure what to do. I've tried to reboot from download mode, and that sends me right back to the error message.
Any ideas?
Click to expand...
Click to collapse
IIRC you need to reflash recovery and you should be able to boot up again.
muzzy996 said:
IIRC you need to reflash recovery and you should be able to boot up again.
Click to expand...
Click to collapse
I'm sorry if I sound stupid but how do I reflash the recovery? I keep searching for a recovery ROM but I can't find anything, so I must be misunderstanding something here.
ChampagneFerret said:
I'm sorry if I sound stupid but how do I reflash the recovery? I keep searching for a recovery ROM but I can't find anything, so I must be misunderstanding something here.
Click to expand...
Click to collapse
TWRP 2.7.0.0 is available now! http://forum.xda-developers.com/showthread.php?t=2706982 :good:
icem237 said:
TWRP 2.7.0.0 is available now! http://forum.xda-developers.com/showthread.php?t=2706982 :good:
Click to expand...
Click to collapse
Thank you very much. In case anyone else is wondering. I ended up asking the problem with Samsung kies, using the upgrade feature rather than emergency recovery. Wiped all my data but u have my tablet back.
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
ChampagneFerret said:
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
Click to expand...
Click to collapse
Did you use Odin 3.0.7 or 3.0.9? 3.0.7 is included with CF and MUST be used even though 3.0.9 is the latest. If odin was already installed on your PC and you used 3.0.9 bad things are going to happen.
ChampagneFerret said:
Thank you very much. In case anyone else is wondering. I ended up asking the problem with Samsung kies, using the upgrade feature rather than emergency recovery. Wiped all my data but u have my tablet back.
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
Click to expand...
Click to collapse
I myself have tried odin 3.07 and .09 and mine just hangs when cache is being written to. A full green bar but will not move pass the cache portion of the install.
icem237 said:
I myself have tried odin 3.07 and .09 and mine just hangs when cache is being written to. A full green bar but will not move pass the cache portion of the install.
Click to expand...
Click to collapse
I tried both as well, and that's exactly what happened to me. During the process, my screen went all screwy and that's when it told me the process had failed.
I had some of the problems mentioned above. My attempt to flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 failed using Odin3-v3.07.exe.
It tries for several minutes and then says failed.
I then used Kies (not Kies 3) to reflash the tablet to factory settings. Here its important to know that Kies will never "connect" you have to ignore that and go to tools and "firmware upgrade and initialization". Google "Firmware upgrade encountered an issue” – Got This Error While", the first result on "droidviews" is the guide i used to fix this.
I then went into the settings and enabled "USB Debugging". Something i had forgotten before. I tried to flash the root file again, but it still failed.
Given that i was able to reflash the firmware with kies, i would say my USB port / cable / drivers must all be good.
What else should i try?
Flash Stock Recovery
davschm said:
I had some of the problems mentioned above. My attempt to flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 failed using Odin3-v3.07.exe.
It tries for several minutes and then says failed.
I then used Kies (not Kies 3) to reflash the tablet to factory settings. Here its important to know that Kies will never "connect" you have to ignore that and go to tools and "firmware upgrade and initialization". Google "Firmware upgrade encountered an issue” – Got This Error While", the first result on "droidviews" is the guide i used to fix this.
I then went into the settings and enabled "USB Debugging". Something i had forgotten before. I tried to flash the root file again, but it still failed.
Given that i was able to reflash the firmware with kies, i would say my USB port / cable / drivers must all be good.
What else should i try?
Click to expand...
Click to collapse
For those getting stuck or failing root, Make sure your usb drivers are updated in Kies 3 then flash stock recovery in Odin 3.07. Don't get mixed up with stock firmware (over 1GB) and stock recover (only around 20MB).
Stock recovery is here:
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
Thread is here:
http://forum.xda-developers.com/showthread.php?p=50492301&nocache=1
Russbad said:
For those getting stuck or failing root, Make sure your usb drivers are updated in Kies 3 then flash stock recovery in Odin 3.07. Don't get mixed up with stock firmware (over 1GB) and stock recover (only around 20MB).
Stock recovery is here:
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
Thread is here:
http://forum.xda-developers.com/showthread.php?p=50492301&nocache=1
Click to expand...
Click to collapse
Question, what is the purpose of the Stock recovery and CWM recovery?
Also, after trying three times, i was able to get the flash to work. After each failier i used Kies (not kies 3) to flash back to factory. Would these recoveries have helped? Maybe i wouldn't have lost data?
davschm said:
Question, what is the purpose of the Stock recovery and CWM recovery?
Also, after trying three times, i was able to get the flash to work. After each failier i used Kies (not kies 3) to flash back to factory. Would these recoveries have helped? Maybe i wouldn't have lost data?
Click to expand...
Click to collapse
Stock recovery is what your device originally comes with. CWM recovery is a modified version of that and it allows you more functionality.
When I messed up my update and root, my device would not boot up at all. I flashed the stock recovery and that enabled me to successfully root. No data was lost, no factory reset was needed and all my apps and settings were unchanged.
Don't mean to bump this thread, but I'm having the same issue. Odin 3.07 hangs up when it gets to cache.img, and it's non-responsive. I don't care about rooting it, I just want a stock firmware back. I've tried the files that Russbad posted, same issue. Running Note Pro 12. SM-P900 on 4.4.2.
bioncorp said:
Don't mean to bump this thread, but I'm having the same issue. Odin 3.07 hangs up when it gets to cache.img, and it's non-responsive. I don't care about rooting it, I just want a stock firmware back. I've tried the files that Russbad posted, same issue. Running Note Pro 12. SM-P900 on 4.4.2.
Click to expand...
Click to collapse
Try this: With your device unplugged from your PC, open Kies 3, go to tools tab and uninstall the drivers. Then plug your device in and reinstall drivers.
I don't know if it makes a difference but if you get your device to boot up, enable developer options and check USB debugging.
Also make sure you are using the cables that came with your Tablet.
Then flash stock recovery and flash stock firmware.
If it still fails, check that your downloaded firmware and recovery are not corrupted, download them again.
Also try these procedures using different USB ports.
Good luck!
Russbad said:
Try this: With your device unplugged from your PC, open Kies 3, go to tools tab and uninstall the drivers. Then plug your device in and reinstall drivers.
I don't know if it makes a difference but if you get your device to boot up, enable developer options and check USB debugging.
Also make sure you are using the cables that came with your Tablet.
Then flash stock recovery and flash stock firmware.
If it still fails, check that your downloaded firmware and recovery are not corrupted, download them again.
Also try these procedures using different USB ports.
Good luck!
Click to expand...
Click to collapse
I found the issue, it should work with everyone with it. Some people don't have the .md5 extension enabled in their archive viewer, so by simply removing the .md5 (left with CF_XXXX.tar), and flashing that it works 100% fine.
bioncorp said:
I found the issue, it should work with everyone with it. Some people don't have the .md5 extension enabled in their archive viewer, so by simply removing the .md5 (left with CF_XXXX.tar), and flashing that it works 100% fine.
Click to expand...
Click to collapse
I finally got mine rooted by simply trying over and over. I re-downloaded the CF flash tool and used 7zip to extract it several times, and used a different usb port at least once. Not that I really thought there was a problem with my extraction or the download or my USB port. But from what i have seen posted, you just have to try it 3 or 4 (maybe even 10) times until you get lucky and it works.
I did at one point try to recover my Note 12.2 with the "recovery.img" instead of flashing it with a full factory re-image (which causes data loss) but that didn't work for me ether. But I later had good luck with using Odin 3.09 to flash TWRP. So at least I now have a good custom recovery and backup tool.
okay everyone, I'm going to try these methods and report on what happened. Thank you for being so helpful. :cyclops:
ChampagneFerret said:
okay everyone, I'm going to try these methods and report on what happened. Thank you for being so helpful. :cyclops:
Click to expand...
Click to collapse
FINALLY! :laugh: I got it to root!
I ended up using a different computer in the end and used Kies 2.6 for the drivers. I tried this a total of maybe 8 or 9 times, and it worked on the second attempt on the second attempt.
For the record, I left "md5" in the file when rooting, and that's when it worked.
My Phone sprint S3 is rooted with a stock4.1.2 rom. I was going to put my phone in recovery to do a backup because I wanted to flash ND8 then a new Kit Kat rom. The phone wouldn't boot to recovery. I read something about using Kies if this happens. I updated Kies and connected the phone to it. Now it boots to the "Samsung" on the screen and goes to small windows with "unfortunately the process.com.android.phone has stopped" when I hit OK it says ".process.acore has stopped". It goes in to some more windows sometimes. can I fix this or am I screwed. I just wnat to go back to my rooted 4.1.2 stock rom for now and then figure out where to go from there. If the only thing to do is flash the phone with ND8 with Oden so be it, I'm not sure how at this point to do that.
congaman59 said:
My Phone sprint S3 is rooted with a stock4.1.2 rom. I was going to put my phone in recovery to do a backup because I wanted to flash ND8 then a new Kit Kat rom. The phone wouldn't boot to recovery. I read something about using Kies if this happens. I updated Kies and connected the phone to it. Now it boots to the "Samsung" on the screen and goes to small windows with "unfortunately the process.com.android.phone has stopped" when I hit OK it says ".process.acore has stopped". It goes in to some more windows sometimes. can I fix this or am I screwed. I just wnat to go back to my rooted 4.1.2 stock rom for now and then figure out where to go from there. If the only thing to do is flash the phone with ND8 with Oden so be it, I'm not sure how at this point to do that.
Click to expand...
Click to collapse
see this
Newest odin
flash- said:
see this
Click to expand...
Click to collapse
says to flash the bootloader in the "PDA" section. The newest odin doesn't have a "PDA" section. Have an idea what I should do about that?
congaman59 said:
says to flash the bootloader in the "PDA" section. The newest odin doesn't have a "PDA" section. Have an idea what I should do about that?
Click to expand...
Click to collapse
install the version they work on it in the guide ..look for it ...you shall find it somewhere
having driver problem
Oden3 ver3.09 to do what you said. I still can't get the usb driver to work with my computer and phone. It is a SPH-L710 on sprint.
Okay got the driver but getting FAIL
I got the driver to work after I got the phone in to download mode. However every time I try to flash the VRALEC bootchain I get a fail. I have the phone in download mode.
got first bootloader to run. But
I got the driver to work after I got the phone in to download mode. I think I got the first bootloader to run even though it failed every time I tried to flash it. I however can't get the second one to even show up in Odin!