I figured I'd post this since there seems to be a bunch of people STILL having problems getting to EP1Q Gingerbread and Gummy.
I made a post about this in another thread but it seems not enough people have seen it.
Below you will find the steps and links to get you to EP1Q from absolutely any ROM or Kernel or Voodoo or Non-voodoo, Gingerbread or Froyo.
--------------------------------------------------------------------------------------------------------------
1. Turn off phone, remove battery, open Odin, plug in phone via USB and put in download mode. Put battery BACK in.
2. Check Re-Partition, UN-check Auto Reboot and F. Reset Time.
3. Load the PIT file below. Also load the ED1 file below in PDA.
4. Hit Start
5. Wait til it is fully finished. When it is done, unplug the phone and remove the battery.
6. Put battery back in and start up the phone. It may or may not boot into Recovery.
7. If it boots into recovery then hit Reboot. It should now boot into ED1.
8. First exit out of Odin and re-open it. Then Repeat STEP 1.
9. Load EP1Q into PDA in Odin. Hit Start.
10. Be patient and wait, when it is finished doing everything, you may or may not see red error lines, don't worry. Go to the next step.
11. Repeat Step 1 and load "New_CWM_Recovery.tar" into the PDA slot. Hit Start. It should reboot itself into Recovery, hit reboot.
12. It should now load into EP1Q.
You may stop here if you don't want Gummy.
--------------------------------------------------------------------------------------------------------------
13. Repeat Step 1.
14. Load Gummy EP1Q into the PDA slot in Odin. Hit Start.
15. It should reboot into Recovery when finished, hit Reboot.
16. You are now on a fully fresh copy of Gummy EP1Q!
--------------------------------------------------------------------------------------------------------------
Links:
ED1 - http://www.multiupload.com/LNTF3IKJ21
PIT - http://www.mediafire.com/?kk62yxpp8b8x918
CWM - http://www.multiupload.com/D7ELKNADJD
EP1Q - http://www.multiupload.com/0EKVFHOFJ9 - REAL WORKING FAST DOWNLOAD LINK, uploaded by myself.
Gummy - http://bit.ly/n0G8J9
Links are from imnuts, Kejar31, and P3Droid. They have done all of the dev work, this is just a How-To created by me.
Thank Jeebus. The noobs just say the same thing over and over.
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
Thank Jeebus. The noobs just say the same thing over and over.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
You're welcome. Let me know if you need any more help.
Why ED1or ED2 though, I keep seeing people say to use that instead of EE4... Anyways I've gone back and forth from EE4 to EP1H and EP1Q then back about a dozen times (to test, load different roms, or try and duplicate problems to troubleshoot) in the last few days without a single problem so I don't know what people are doing wrong. I'll always help when I can though
Nice write-up too btw
blazing through on my VZ Droid Charge 4G
Syn Ack said:
You're welcome. Let me know if you need any more help.
Click to expand...
Click to collapse
1) have you had any luck with EP1Q Special from TBH? 2) Do you notice any connectivity issues with 4G on EP1Q stock?
anoninja118 said:
Why ED1or ED2 though, I keep seeing people say to use that instead of EE4... Anyways I've gone back and forth from EE4 to EP1H and EP1Q then back about a dozen times (to test, load different roms, or try and duplicate problems to troubleshoot) in the last few days without a single problem so I don't know what people are doing wrong. I'll always help when I can though
Nice write-up too btw
blazing through on my VZ Droid Charge 4G
Click to expand...
Click to collapse
It just seems that the ED1 All in One file seems to be a 100% surefire way to get to EP1Q from anywhere. I came from a Voodoo Froyo and used this exact method to get to EP1Q Gummy. It seems that most people that are having problems are the ones with Voodoo Froyo.
j0kerm4n said:
1) have you had any luck with EP1Q Special from TBH? 2) Do you notice any connectivity issues with 4G on EP1Q stock?
Click to expand...
Click to collapse
Personally I haven't tried anything with the EP1Q special. All I know is flashing EP1Q Gummy over stock EP1Q is amazing. Stock EP1Q is pretty buggy compared to Gummy. Connectivity is better for 4G on EP1Q. Wifi is very good too.
j0kerm4n said:
1) have you had any luck with EP1Q Special from TBH? 2) Do you notice any connectivity issues with 4G on EP1Q stock?
Click to expand...
Click to collapse
the signal is greatly improved in terms of radio connectivity... 4G/3G/1X hand-off is pretty much non existent for me, I get 4G in 4G areas and 3G/1X in spotty areas. Not so much of that constant switching just when its sitting on my desk
blazing through on my VZ Droid Charge 4G
Syn Ack said:
It just seems that the ED1 All in One file seems to be a 100% surefire way to get to EP1Q from anywhere. I came from a Voodoo Froyo and used this exact method to get to EP1Q Gummy. It seems that most people that are having problems are the ones with Voodoo Froyo.
Click to expand...
Click to collapse
Alot of people are forgetting to deactivate voodoo lag and reverting back to rfs.... This is causing boot loops.
Sent from my SCH-I510 using XDA Premium App
danalo1979 said:
Alot of people are forgetting to deactivate voodoo lag and reverting back to rfs.... This is causing boot loops.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yeah exactly. This completely fixes everything.
danalo1979 said:
Alot of people are forgetting to deactivate voodoo lag and reverting back to rfs.... This is causing boot loops.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
When flashing in Odin, if a file is included to perform a data wipe, you don't need to deactivate voodoo as it will auto-format the partitions correctly.
imnuts said:
When flashing in Odin, if a file is included to perform a data wipe, you don't need to deactivate voodoo as it will auto-format the partitions correctly.
Click to expand...
Click to collapse
Which is extremely helpful in situations like these
Otherwise it can cause a nightmare to casual flashers.
Anyone else having trouble with the stock EP1Q Odin file? I downloaded it from three separate links on the main download page, and when I start Odin every time I get this result:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CI510_VZW_EP1Q_ALL_ONE-LTE-CP_REV3_user_CL397514.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
I followed the instructions step-by-step up to this point, and the Odin of stock ED1 worked fine.
Thoughts?
tsgeek said:
Anyone else having trouble with the stock EP1Q Odin file? I downloaded it from three separate links on the main download page, and when I start Odin every time I get this result:
I followed the instructions step-by-step up to this point, and the Odin of stock ED1 worked fine.
Thoughts?
Click to expand...
Click to collapse
I went to p3's mydroidworld post and downloaded it from the second link. Did this yesterday midday and it had no problems with md5 hash, Although it bootlooped for me so I just odin'd gummy 1.9RC1 and all was well.
Sent from my Droid Charge running GummyCharged 1.9RC1
GoBlue13 said:
I went to p3's mydroidworld post and downloaded it from the second link. Did this yesterday midday and it had no problems with md5 hash, Although it bootlooped for me so I just odin'd gummy 1.9RC1 and all was well.
Click to expand...
Click to collapse
I'll try that one. Of course it was the one I skipped when choosing them randomly
Of course it was. I hate when that happens. Good luck!
Sent from my Droid Charge running GummyCharged 1.9RC1
OK, I did end up going to P3Droid's post on Droid World here to get the EP1Q stock download. I chose the Mirror 1 Download from there. Using that file with Odin did work. I got sent into a boot loop, but really didn't care because I was going to Odin GummyCharged EP1Q anyway. From that point, I picked up from Step 12 in this thread's OP.
Worked just fine. I'm now the happy owner of a GummyCharged EP1Q Charge,
I flashed ED1 with the pit, rebooted, and flashed driectly to gummy GBE from there. Worked fine without flashing the EP1Q leak first.
tsgeek said:
I'll try that one. Of course it was the one I skipped when choosing them randomly
Click to expand...
Click to collapse
I went over there. They talked about removing the .md5 extension and the file working. I did that and it appears to be working.
Removing the md5 extension is not a smart idea, even if it worked for you. That's an easy way to brick your phone. The md5 hash is how you know everything is there. If you odin a corrupt md5 file, it will just fail. If you odin a corrupt tar file, more than likely you're bricked.
Related
I have been attempting to flash the ROM on my Charge all day with mixed results. After much frustration, I have finally been able to flash a few ROMs, and everything works great except I have no phone signal and my phone says "Unknown Baseband." in both slots. Earlier, it said it in only one of the slots. I have attempted Altered Beast, Stock, Stock Rooted, Deodoxed, all to no avail. Is there any way to flash just the modem or radio code?
did you actually read the directions, or just willy nilly flash from AB to stock and so on and so forth?
because they aren't all compatible with each other to do that
I was initially following the directions in this thread: http://forum.xda-developers.com/showthread.php?t=1122657
I went through all these directions, and after a reboot at the end, that's when it developed the problem initially.
There are only two known radios for the phone, and none of the roms flash a new radio, so even if the OP screwed up flashing his rom it shouldn't impact basebands, unless he didn't check PDA.
OP - What all did you actually try to flash? Are you sure you checked PDA in Odin, and not Modem each time?
I made certain I checked PDA each time.
Earlier yesterday afternoon, I was initially following this guide: [http://www.theandroidsoul.com/how-t...and-clockworkmod-recovery-installation-guide/]until I realized it was old and didn't work w/ EE4. I had to flash my ROM back to ED1 Stock rooted in order for it to work. After that, I began following the guide in the earlier post. When my radios stopped working after that, I began flashing just about any ROM I could get my hands on, just to see if I get could get my radios back, including the aforementioned Stock, Stock rooted, Deodexed, Altered Beast, Debloated, etc. I eventually had to so the CWM repair ROM [http://forum.xda-developers.com/showthread.php?t=1111486] and flashed to Altered Beast and then to Stock ED2 after that, which is where I think I'm sitting right now.
distortedloop said:
There are only two known radios for the phone, and none of the roms flash a new radio, so even if the OP screwed up flashing his rom it shouldn't impact basebands, unless he didn't check PDA.
OP - What all did you actually try to flash? Are you sure you checked PDA in Odin, and not Modem each time?
Click to expand...
Click to collapse
There are several people experiencing an unknown baseband, most of the time its from attempting to use cwm prior to v3 to flash a recovery, then fixing the soft brick and now we have a "unknown baseband"
This happened to me as well. Any way to fix?
Anyone try flashing the official EE4 update.zip with stock recovery? Since that is the only file we have that has modem parts, maybe it can recover your basebands.
hoppermi said:
Anyone try flashing the official EE4 update.zip with stock recovery? Since that is the only file we have that has modem parts, maybe it can recover your basebands.
Click to expand...
Click to collapse
Do you know where I can locate that .zip? I am in the same boat and would be willing to try.
My experience with unknown baseband and ee4 update is that it wouldn't update to ee4 because it couldn't find an ltemodem to patch. I don't think the update is just going to insert the baseband because it can't find the original.
I'm back on my Incredible in the meantime. Can't believe how small it is!
Sent from my ADR6300 using Tapatalk
jaylikesdroid said:
Do you know where I can locate that .zip? I am in the same boat and would be willing to try.
Click to expand...
Click to collapse
Its posted in development. If it were me I would odin to ed1 and try and apply that zip in stock recovery. Either it will work or it won't. Don't cost nuthin.
Sent from my SCH-I510 using Tapatalk
hoppermi said:
I would odin to ed1 and try and apply that zip in stock recovery.
Click to expand...
Click to collapse
In the process of doing this, I bricked my phone even more. When I try to reboot the phone, it says:
++++++++++++++++++++++++++++
-- bootmode=7 from cmdline...
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
-- Movi_check already executed!!...
-- movi_checking done!...
#MANUAL MODE #
++++++++++++++++++++++++++++
Then it boots into recovery. Obviously, this is a good example of why not to root your device unless you have a REALLY good understanding of what you're doing.
I would install ED1 via odin and let it update OTA.
http://forum.xda-developers.com/showthread.php?t=1085190
other useful threads that helped me a lot
http://forum.xda-developers.com/showthread.php?t=1107797
http://forum.xda-developers.com/showthread.php?t=1122657
chiahead52 said:
I would install ED1 via odin and let it update OTA.
http://forum.xda-developers.com/showthread.php?t=1085190
Click to expand...
Click to collapse
That's what I've been trying to do, but unfortunately, it's not working. Odin is saying it's successfully installed, but when I try to reboot within recovery, it loops me back to the same place within recovery and gives me the message I posted above.
chiahead52 said:
I would install ED1 via odin and let it update OTA.
http://forum.xda-developers.com/showthread.php?t=1085190
other useful threads that helped me a lot
http://forum.xda-developers.com/showthread.php?t=1107797
http://forum.xda-developers.com/showthread.php?t=1122657
Click to expand...
Click to collapse
I think at this point I have tried every available package in the dev section. Unfortunately, though the all get me a "working" phone I still have the unkown baseband and thus am unable to find a wireless signal. This prohibits me from get and OTA when at ed1.
hoppermi said:
Anyone try flashing the official EE4 update.zip with stock recovery? Since that is the only file we have that has modem parts, maybe it can recover your basebands.
Click to expand...
Click to collapse
Thanks for the suggestion. Tried it. No luck.
Well just now a FULL ODIN ED2 package was posted at rootzwiki http://rootzwiki.com/showthread.php?481-LEAK-STOCK-ED2-Droid-Charge-FULL-ODIN!&p=5957#post5957
If anyone wants to try this to see if it is legit. I figured it would be one of you who is stuck. This "should" fix your problems and put you on stock ED2. And it would be a safety net for everyone else. It nearly impossible to brick your phone if there is a full odin.
Good luck.
hoppermi said:
Well just now a FULL ODIN ED2 package was posted at rootzwiki http://rootzwiki.com/showthread.php?481-LEAK-STOCK-ED2-Droid-Charge-FULL-ODIN!&p=5957#post5957
If anyone wants to try this to see if it is legit. I figured it would be one of you who is stuck. This "should" fix your problems and put you on stock ED2. And it would be a safety net for everyone else. It nearly impossible to brick your phone if there is a full odin.
Good luck.
Click to expand...
Click to collapse
Trying it right now!!! Wish me luck!
hoppermi said:
Well just now a FULL ODIN ED2 package was posted at rootzwiki http://rootzwiki.com/showthread.php?481-LEAK-STOCK-ED2-Droid-Charge-FULL-ODIN!&p=5957#post5957
If anyone wants to try this to see if it is legit. I figured it would be one of you who is stuck. This "should" fix your problems and put you on stock ED2. And it would be a safety net for everyone else. It nearly impossible to brick your phone if there is a full odin.
Good luck.
Click to expand...
Click to collapse
Giving it a try. Will report back.
UPDATE:
It didn't work. Got an error message in Odin that says MD5 hash value invalid
So I was on Gummy 1.8.1 and I chose to flash the Full ODIN package to 1.9.1...
The flashing failed in ODIN (Dnt know why, everybody said you can flash without a data wipe/reset)
Now it displays a phone and computer icon with a exclamation point in the middle, Everything else I try to flash fails, What is the safest way to get my phone working again?
http://forum.xda-developers.com/showthread.php?t=1111486
I just tried that guide and Im still unable to flash any of those files...... Everything simply fails in ODIN, its heartbreaking......
Is there something Im severely overlooking? Should ODIN be the only program open when Im flashing? Redownload all the files? Im just tired of waiting only to see the red fail box -__-
Take the battery out and put it into download mode. Then start Odin flashing. As soon as it verifies the MD5 pop your battery back in.
Sent from my Droid Charge running GummyFroyo 1.9.1
The only thing we can really recommend is that you follow that guide to the T. There's not much else you can do aside from a) using a rear USB port if you're on a desktop and b) make sure you're using the stock cable your phone came with
kvswim said:
Take the battery out and put it into download mode. Then start Odin flashing. As soon as it verifies the MD5 pop your battery back in.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
I always put the battery in after Odin recognizes the phone.
hazard209 said:
I always put the battery in after Odin recognizes the phone.
Click to expand...
Click to collapse
Me too...sounds silly trying to time it like that imo...
Sent from my SCH-I510 using XDA Premium App
Don't mean to bump but Thanks Everyone. My phone is back and working fine. In the first guide, someone else posted a link to another thread with an alternate mode of flashing. Worked like a charm and booted right back to stock EE1.
Right now Im enjoying Gummy 1.9.1, thanks again guys
http://rootzwiki.com/showthread.php?t=3163
this thread is now null and void lol. for anyone that wants it, kejar released his own updated Cwm version of gummycharged. follow the link above for his ext4 lagfix instructions.
Does this work? Anyone try?
works, nice write up too
blazing through on my VZ Droid Charge 4G
awesome thanx for figuring it before i had to try a thousand combonations...
This is awesome!
How long should it stay at Samsung after doing all of the steps? I did all of the steps. Samsung flashed several times. Now its just staying at Samsung. Been this way for a couple of minutes.
sdcard issues
ok, first of all I did this and everything worked fine.
Upon first reboot, I think it went 4 or 5 times through the samsung bootloop and then loaded the rom (i wasn't watching it fastidiously).
Upon loading the rom and loading my apps from titanium backup, I finally hit the issue of not being able to move apps to the sd card; it just comes up with "failed to move application". I've rebooted just to make sure things weren't off from first boot. It's still not letting me move any apps to sd (even if allowed in the os).
Any ideas on what to try next?
I'm still at Samsung logo. Don't think its going to load the Rom. Not sure what I'm doing wrong. Following the steps. This is the second time I've tried this.
NM, figured it all out.
Going to give it a shot shortly.
This failed to work 3 times. Going back to RFS Gummy.
did anyone else lose ROOT access after booting up?
I used Imnuts' EP1Q hacked kernel flashable via CWM.
I went to TB and it said I didn't have root access. Flashed superuser.zip and still no go.
evercleardoc said:
did anyone else lose ROOT access after booting up?
I used Imnuts' EP1Q hacked kernel flashable via CWM.
I went to TB and it said I didn't have root access. Flashed superuser.zip and still no go.
Click to expand...
Click to collapse
From what I have read over at Rootzwiki, that seems to be a problem exclusive to Imnuts' hacked kernel (possibly, he posted that he is looking into it as some users used his kernel and didn't have this problem). This process uses another kernel.
I was waiting for more users to give reports back, but I might just give this one a go.
PeterGunz said:
From what I have read over at Rootzwiki, that seems to be a problem exclusive to Imnuts' hacked kernel (possibly, he posted that he is looking into it as some users used his kernel and didn't have this problem). This process uses another kernel.
I was waiting for more users to give reports back, but I might just give this one a go.
Click to expand...
Click to collapse
I tested his hacked kernel and yes we ran into this issue, however flashing superuser in CWM fixed it for me... doesn't seem to work for other people so idk
blazing through on my VZ Droid Charge 4G
Hrmm. Well for the people it isn't working for, try following the guide here to at least get a good copy of EP1Q on there and working first. Then follow my process.
Sucks that the imnuts kernel isn't working right yet. I would love to have the EP1Q kernel working on this, would be much more ideal.
It breaks root for me too. Come one imnuts, i know you know what is causing it, you are a smart cookie. Put out an updated zip already lol...
skydeaner said:
Hrmm. Well for the people it isn't working for, try following the guide here to at least get a good copy of EP1Q on there and working first. Then follow my process.
Sucks that the imnuts kernel isn't working right yet. I would love to have the EP1Q kernel working on this, would be much more ideal.
It breaks root for me too. Come one imnuts, i know you know what is causing it, you are a smart cookie. Put out an updated zip already lol...
Click to expand...
Click to collapse
I've downloaded the file twice, but I keep getting MD5 hash value invalid on the Odin step for the Nameless recovery. That's as far as I could get in the steps. I tried downloading it from multiple places but no dice.
PeterGunz said:
I've downloaded the file twice, but I keep getting MD5 hash value invalid on the Odin step for the Nameless recovery. That's as far as I could get in the steps. I tried downloading it from multiple places but no dice.
Click to expand...
Click to collapse
what did you need? the nameless v2 kernel? I can upload my copy for you if I have it
anoninja118 said:
what did you need? the nameless v2 kernel? I can upload my copy for you if I have it
Click to expand...
Click to collapse
I need the Nameless recovery file for Odin from the step after flashing the GC rom in Odin.
Sent from my SCH-I510 using XDA App
I executed this method using Imnuts kernel and kept root (Thankfully). However I looked at the post to confirm EXT4, and my Terminal Emulator doesn't match the one posted at all. Right now, it's just showing data and dbdata on EXT4, the rest is still on RFS. Is this normal for GB? I can post the exact coding if needed.
PeterGunz said:
I need the Nameless recovery file for Odin from the step after flashing the GC rom in Odin.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
you mean CWM? the one for step 3?
anoninja118 said:
you mean CWM? the one for step 3?
Click to expand...
Click to collapse
Yes that's the one. If you have the correct file that would be great.
Sent from my SCH-I510 using XDA App
I flashed the 0817_charge_recovery.tar.md5. I didnt see that it worked and then went back into download, thru Odin, tried to flish cwm_Recovery4008.tar. Got a fail and now when i try to turn on it just shows an icon of a phone with a yellow triangle exclamation point between that and a computer icon. it still goes into download mode with volume down and usb connection but it wont flash the default VZW rom back.
Suggestions?
Battery in or out?
battery in = (phone) ... ! ... (cpu)
battery out = can still go into download mode
Did you come from another rom? I think if you want to flash back to stock from another rom via odin you need to also flash the pit file. At least thats what I had to do.
Sent from my SCH-I510 using XDA App
No i had reverted back to the stock (pentafive ee4 full factor tar).
Have you tried everything from imnuts Fix your Phone thread?
http://forum.xda-developers.com/showthread.php?t=1111486
Ya i got a fail for that as well on Odin. Also tried the Samsung PST and it said error download there as well
DRO1DZ1LLA said:
Ya i got a fail for that as well on Odin. Also tried the Samsung PST and it said error download there as well
Click to expand...
Click to collapse
Are you keeping the battery out during the entire process? You're using the PIT too with the Re-partition box checked (unchecked Auto Restart and F. Time)?
I left the battery in cause in step 4b he says to but anyways it worked. the first time i tried i was using the ed2 file cause for some reason the ed1 link wasnt loading. then i realized i had that file already from somewhere else and used that and it went through
DRO1DZ1LLA said:
I left the battery in cause in step 4b he says to but anyways it worked. the first time i tried i was using the ed2 file cause for some reason the ed1 link wasnt loading. then i realized i had that file already from somewhere else and used that and it went through
Click to expand...
Click to collapse
Nice, bro! Glad to hear you're back up!
thanks for all the help tho! so should i not try to re-root/rom/kernel this ***** or what?
DRO1DZ1LLA said:
thanks for all the help tho! so should i not try to re-root/rom/kernel this ***** or what?
Click to expand...
Click to collapse
Right now, your best bet is to apply whatever system updates there are. If your phone doesn't get you up to EE4 on its own, then you should follow imnuts' instructions here: http://rootzwiki.com/topic/10202-how-to-prepare-for-the-gb-ota/
At some point today, someone will be able to confirm whether the update.zip (leaked) is truly 100% identical to the update.zip that Verizon is pushing out for EP4. If it is, then we'll be safe update to EP4 ahead of the OTA, root, restore any backups, and apply working EP4 themes. I'm anxiously awaiting the ability to depoop my phone--rolled back to stock EE4 last night and have hated my phone ever since!
Haha same. I returned initially for the same reason and then was so sick of it i pushed ahead and messed it up. Still haven't gotten the update tho
Happened to me once. Used stock ee4 odin with the charge .Pit file imnuts posted and it brought me back to stock
Sent from my SCH-I510 using Tapatalk
Hi folks...
I am trying to help a friend that owns this phone. I recently rooted it for him and all was well until one day he said that the phone died and when he rebooted the phone would force close EVERYTHING, rendering the phone unusable. Here's what I have done thus far:
via odin... i have tried everything in the "how to fix your phone" post all with the same result of the phone booting to setup force closing everything.
so i got the idea to try and get cwm installed and try a custom rom (tweaked v2.2). Initially, after I installed it, the phone bootlooped. So i found the post with the stock fp1 kernel (which is the kernel with the rom if i'm not mistaken) and flashed it. The phone booted... still forces closing everything.
I am stuck now... Not bricked by any means, but this force close issue is going to be the bain of my existence:crying:. If anyone has experienced this and managed to get the phone working normally again, please help.
I am pretty good with everything on samsung phones except ADB... if the fix involves that just make the instructions idiot proof...
THANKS A LOT FOR THE HELP IN ADVANCE!!!
Pit.
Sent from my SCH-I510 using xda premium
kvswim said:
Pit.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Is there a different PIT file other than the one found via the "how to fix your phone" post? If not, tried that already, but thanks for the reply.
Go to imnuts.org
Every file for Odin is there
SENT FROM THE DOG POUND
Flash this and the pit. http://forum.xda-developers.com/showthread.php?t=1380430
If it's still FC city I would use SamsungPST to flash that along with the pit. It may take a few tries because your NAND is likely corrupted.
Sent from my SCH-I510 using xda premium
Thanks folks. the only thing here i haven't done is the samsung pst thing. I downloaded what i hope is the right version of it. do i go about using it the same way i would use odin?
EDIT: Figured it out... lets hope for the best and thanks guys
QUESTION...should i be checking the repartition, efs clear, of boot update boxes when using the pst program, or do i just keep trying to flash and re-flash until the problem goes away?
onyx1898 said:
Thanks folks. the only thing here i haven't done is the samsung pst thing. I downloaded what i hope is the right version of it. do i go about using it the same way i would use odin?
EDIT: Figured it out... lets hope for the best and thanks guys
QUESTION...should i be checking the repartition, efs clear, of boot update boxes when using the pst program, or do i just keep trying to flash and re-flash until the problem goes away?
Click to expand...
Click to collapse
If you are flashing with the pit Re-Partition, Auto Reboot, F. Reset Time and PDA should be the only things checked. If you are not flashing with the pit then Re-Partition should be unchecked
Thanks Paul, i was using the samsungPST program, so i will give the repartition option a try within that program.
Maybe you are using the wrong version of odin. 1.83 or 1.85 are the only versions you should be using
been using 1.85, will try 1.83...
When using PST check only the PIT. EFS Clear and Boot Update will break the phone even more.
Sent from my SCH-I510 using xda premium
kvswim said:
When using PST check only the PIT. EFS Clear and Boot Update will break the phone even more.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Thanks, glad i didn't mess with those...
Sent from my GT-P5113 using xda app-developers app
wrong forum... ignore
I still haven't gotten this darn thing working... at this point i can say i have tried everything... any other input?
currently have tweaked v3 w/ clockwork mod installed, still FC everything...
as always, thanks in advance
onyx1898 said:
I still haven't gotten this darn thing working... at this point i can say i have tried everything... any other input?
currently have tweaked v3 w/ clockwork mod installed, still FC everything...
as always, thanks in advance
Click to expand...
Click to collapse
what kernel are you running?
Whatever kernel that comes with the stock rom, that is unless it stays with whatever was last flashed kernel wise. If that's the case, it's stock fp1
Sent from a phone that is better than sliced bread...
Reading through this I haven't seen any mention of taking the OTA updates. After flashing EP4D with Pit did you allow the 2 over the air updates from Verizon? This needs to be done before flashing Tweaked. Then when you flash Tweaked I suggest using the Odin version "Tweaked with CWM". That worked out perfectly for me.
Update: Also did you check the MD5 Checksum of the EP4 file you downloaded. That's pretty much mandatory since bad downloads do sometimes happen.
stueycaster said:
Reading through this I haven't seen any mention of taking the OTA updates. After flashing EP4D with Pit did you allow the 2 over the air updates from Verizon? This needs to be done before flashing Tweaked. Then when you flash Tweaked I suggest using the Odin version "Tweaked with CWM". That worked out perfectly for me.
Update: Also did you check the MD5 Checksum of the EP4 file you downloaded. That's pretty much mandatory since bad downloads do sometimes happen.
Click to expand...
Click to collapse
I will double check all of these things... only problem, the phone is force closing setup right after odin, rendering it completely unusable. i will double check the md5 to make sure things are good and will get back to this...
onyx1898 said:
Whatever kernel that comes with the stock rom, that is unless it stays with whatever was last flashed kernel wise. If that's the case, it's stock fp1
Sent from a phone that is better than sliced bread...
Click to expand...
Click to collapse
you should be on FP5 with this ROM. what does your phone settings show?
onyx1898 said:
I will double check all of these things... only problem, the phone is force closing setup right after odin, rendering it completely unusable. i will double check the md5 to make sure things are good and will get back to this...
Click to expand...
Click to collapse
You don't need to use recovery at all. Odin EP4 then take the two OTA updates then odin Tweaked 3.0 w/ CWM. It's in the OP. I did setup Google Backup on EP4 before I took the OTA's. I never use VZW Backup.
Sent from my SCH-I510 running Tweaked 3.0 using Tapatalk 2