Was trying to flash back from epf1 leaked to CI510_VZW_ED2_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.md5 but now no matter what i do i cant fix the baseband unknown error.
These are the files i've tried flashing with odin and havent had any luck.
CI510_VZW_ED2_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.md5
CI510_VZW_EG2_ALL_ONE-LTE-CP_REV03_user_CL199635.tar.md5
CI510_VZW_EP1F_ALL_ONE-LTE-CP_REV3_user_CL300919_Rooted_Debloated.tar.md5
gb_ep1f_bloated.tar.md5
tried installing these with battery on while using odin and battery off.... no luck
Have you tried PST to flash it?
mbaran said:
Have you tried PST to flash it?
Click to expand...
Click to collapse
yes, didnt work
i followed the following post
http://rootzwiki.com/showthread.php?481-LEAK-STOCK-ED2-Droid-Charge-FULL-ODIN!
Same thing is happening to me. Happened after the OTA EE4 update. Had signal just fine on ED1 before the update. Phone is wiped and bone stock right now, baseband unknown after the update, so I'm taking it to the Verizon store.
Here's something to try. (I didn't use PST since I'm only really familar with ODIN and it seemed to work for me).
1) ensure you are using ODIN 1.82. I was using ODIN 1.3 earlier and it seemed to have some issues. :-/
2) using the original ED1 tar file from here: http://forum.xda-developers.com/showthread.php?t=1087342 download and extract the .md5 file
3) Connect your phone, place in download mode and run ODIN 1.82, under "PDA"
select the .md5 file you downloaded and extracted.
4) Remove SIM card as the directions in the above link state (I dunno if required)... but put your battery back in. I think this is REQUIRED when flashing lte_modem.bin part or the files.
5) flash with ODIN and restart once completed.
This reset my phone back to ED1 completely, including writing ED1 modems, which... prior, had been stuck on the EP1F leaked versions. :-(
I suspect it will do the same for your lack of baseband, too.
shrike1978 said:
Same thing is happening to me. Happened after the OTA EE4 update. Had signal just fine on ED1 before the update. Phone is wiped and bone stock right now, baseband unknown after the update, so I'm taking it to the Verizon store.
Click to expand...
Click to collapse
thats exactly what happened to me. after i ran the ee4 update.
I used odin when the 4.0.4 official leak was posted here. I since uses the one click software restore back to 2.3.4. At first it gave an issue with the radio. On my phone while restoring it said "radio fail" but the phone seems to be working.
Now I manually updated the unrooted Sprint official 4.0. And my phone since the very first thing I said, has been randomly rebooting, I tried a different battery and it does the same thing. It's also real laggy. Any advice? Are there stock 2.3.4(7) files I can odin? I want it completely factory. Or suggest the problem? Thank you.
Bumping
Hi there. I have read quite a few tutorials on rooting my phone. I did have it rooted at one point using odin and a package for cwm. It worked great. I wanted to try out one of the 4.* ICS roms, that worked fine.. sorted that out no problem but there was no gps so I wanted to go back to my rooted 2.3.6.
Went to put it back to standard with stock firmware, that also worked fine. The problem I have now is when I attempt to root using the same files, same settings and same utilities as before, It boots up to the samsung galaxy logo, then reboots and shows the logo again and again in an infinite loop.
I have cleared the user data and cache, and the root appears to work as the recovery program installs correctly, but it will not boot the OS.
When i flashed to stock I used odin.. the 512 pit file, the stock pda, phone and csc files. and that works perfectly but not when I root it!
Any ideas??
****UPDATE
I flashed with stock 2.3.5 firmware so that I could use samsung kies to flash my phone back to 2.3.6 so that it was 100% stock and kies now says that my device does not support firmware upgrades!!!
Seems as nobody can be arsed to answer my question I have researched and answered it myself...
If anybody has the same problem of Kies saying "Your device does not support firmware upgrades" all you have to do is go into the "About phone" section of the settings.. find the baseband version of your phone.. Mine was I9000XXJVT... find the lowest version of android on samfirmwares.com , mine was 2.3.4, install it..
then kies recognizes your phone again and will upgrade it to the latest version..
Oh by the way THANKS FOR YOUR HELP lol
This particular phone for record purposes upgraded to:
PDA:JW4 / PHONE:JW4 / CSC:JW5 (CPW) which im guessing is carphone warehouse..
I tried the samfirmware.com version of the latest CPW firmware they have and kies still said it would not update the firmware
and before all you geeks get on your high horse and say why didnt u do this and why didnt you do that..
I couldn't root my firmware after installing the CPW firmware as mentioned above from samfirmwares.com.. i was in an infinite reboot loop. I could load standard firmware from samfirmwares.com and it would boot fine, but I couldn't root it from that.
My aim was to get it back to standard and go from there.
One question.. pretty obvious really... I have searched high and low and still am yet unable to find a sofrware for BACKING UP my original firmware... this would be a pretty sensible idea??? yes???
I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy
If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?
If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham
Yeah, you can still fix it. No need it to bring to samsung
Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!
So I finally took the plunge to AOSP since I have my note 2 to run stable. First thing I noticed was that the camera got a "can't connect to the camera" error. Fixed permissions, wiped multiple times, tried a couple different AOSP roms and nothing, so I looked deeper and found some file replacements for the data folders, tried that and still nothing. Wiped again flashed a stock rooted image and still nothing, so last resort was 2 different stock rooted and not-rooted images through ODIN. Successful flashes of both and still no camera.
I am stumped i thought my fail safe ODIN would work but it didn't if anyone has any suggestions I would greatly appreciate it.
p.s. my bootloder is unlocked.
::UPDATE::
Ok so after continuing the troubleshoot finally stumbled upon something. After restoring a stock ODIN of ICS from when i first got the phone I let Verizon run through and do its update and after it finished VOILA my camera's working. I honestly don't know how it happened but nothing else had worked, now i have to go through and unlock root and get a custom ROM again. hopefully this can help someone if this happens to them.