I have a rooted and bloatware removed Captivate. I tried the OTA update to JH7 and of course it failed. I've tried un-rooting, and doing it again, and of course it failed, just like everyone else. I've tried multiple times, and it fails each time. But here is the weird part, and I've seen a couple other people say this too. When I look at my phone settings, it says that I have JH7 installed. So here's my question, do I, or don't I, have this damn update? How can I verify it? Also, I tried running Mini-Kies, and updating manually, but I get that silly "Unregistered firmware version error". God damn I can't wait for Froyo! But I really don't want the stupid beta that is causing all kinds of issues.
Teejeaux said:
I have a rooted and bloatware removed Captivate. I tried the OTA update to JH7 and of course it failed. I've tried un-rooting, and doing it again, and of course it failed, just like everyone else. I've tried multiple times, and it fails each time. But here is the weird part, and I've seen a couple other people say this too. When I look at my phone settings, it says that I have JH7 installed. So here's my question, do I, or don't I, have this damn update? How can I verify it? Also, I tried running Mini-Kies, and updating manually, but I get that silly "Unregistered firmware version error". God damn I can't wait for Froyo! But I really don't want the stupid beta that is causing all kinds of issues.
Click to expand...
Click to collapse
I had a similar issue. My solution was to unroot, use Odin to back to "stock," and update my PC (.net 4, and x86 drivers) to use Kies mini to get JH7. Unfortunately, that means wiping every app you currently have, but ...
Related
I have a Galaxy S 4G Rooted and Unlocked. I tried to install a special lock screen tweak, and all of the sudden upon booting, the Android System imemdiately force closes. The screen stays totally black after the T-Mobile splash screen and Galaxy S logo come up.
I've erased all my data, but what i really need to do is flash the phone (i think...)
What should i do?
Thanks.
danstheman7 said:
I have a Galaxy S 4G Rooted and Unlocked. I tried to install a special lock screen tweak, and all of the sudden upon booting, the Android System imemdiately force closes. The screen stays totally black after the T-Mobile splash screen and Galaxy S logo come up.
I've erased all my data, but what i really need to do is flash the phone (i think...)
What should i do?
Thanks.
Click to expand...
Click to collapse
If your phone appears to be bricked what you may have to do is flash your phone with one of the three or four Stock Roms that can be found on the DEV site. Check here to see how to use ODEN. For flashing Roms ODEN is the process that is being used on the SGS4G until CWM is working. There may be another way to fix your issue, but if you can get into download mode ODEN should work to get you back to working order. Just make sure you don’t check Partition when using ODEN.
danstheman7 said:
What should i do?
Thanks.
Click to expand...
Click to collapse
You are in luck!!! Check Here http://forum.xda-developers.com/showthread.php?t=1061093
Samsung just released an update using Kies Mini. It's just bug fixes, but it addresses your blank screen. Kies Mini Updates your system Over The Air (OTA). read up on it before you do it. It can be done with the data connection from your phone, but you may want to have a WiFi backup to download the ROM. You don't want it to get interupted during the download process.
nwpro3 said:
You are in luck!!! Check Here http://forum.xda-developers.com/showthread.php?t=1061093
Samsung just released an update using Kies Mini. It's just bug fixes, but it addresses your blank screen. Kies Mini Updates your system Over The Air (OTA). read up on it before you do it. It can be done with the data connection from your phone, but you may want to have a WiFi backup to download the ROM. You don't want it to get interupted during the download process.
Click to expand...
Click to collapse
I ended up using ODEN like you said, and installed 2.2.1 FROYO KC1.
Phone works fine now, thank you
Oh, and I tried clicking "Software Update" and it says "No Firmware"....
Maybe because i'm unlocked on AT&T?
danstheman7 said:
I ended up using ODEN like you said, and installed 2.2.1 FROYO KC1.
Phone works fine now, thank you
Oh, and I tried clicking "Software Update" and it says "No Firmware"....
Maybe because i'm unlocked on AT&T?
Click to expand...
Click to collapse
I don't think Kies recognizes the KC1 firmware since it was never an official release. Hopefully someone will get a firmware dump so that Whitehawk can give us a Deodexed version soon.
danstheman7 said:
I ended up using ODEN like you said, and installed 2.2.1 FROYO KC1.
Phone works fine now, thank you
Oh, and I tried clicking "Software Update" and it says "No Firmware"....
Maybe because i'm unlocked on AT&T?
Click to expand...
Click to collapse
Good to hear you got your phone back up and working. Whether you use KC1 or the new KD1 that was just released won’t make all that much difference. When you clicked on Update Software it is looking for the Over The Air Update firmware. That update is selectively distributed to phones from TMO as the bandwidth allows. Your phone hasn’t received the OTA update yet. That is why you got the No Firmware message. The other way you can download the KD1 firmware is by using Keis Mini software from Samsung. I did that update last night and now have the KD1 Firmware. If you are on AT&T you would have to get the OTA update from them if you are on that network. That is if they decide to send it out.
Ah, great.
Well either way I removed the bloatware apps on my phone with TitaniumBackup, so no OTA for me anyway, correct?
danstheman7 said:
Ah, great.
Well either way I removed the bloatware apps on my phone with TitaniumBackup, so no OTA for me anyway, correct?
Click to expand...
Click to collapse
Tmo is in the process of scheduling OTA updates. If you are on ATT, the update will have to come from them if they are sending them out. You can also use the Kies Mini application to get the KD1 update from Samsung Here Check the OP. There is also a Deodexed version On the Dev page. http://forum.xda-developers.com/showthread.php?t=1063696. Note: The Deodexed version needs to be flashed using ODEN or Heimdall.
Yeah just follow the steps in this guide http://forum.xda-developers.com/showthread.php?t=1001759
to flash the deodexed rom in the post above me.
Did my daily Kies backup of my outlook data. When I ran Kies it told me that there was an update, that's nothing new, so I allowed the update.
Once I re-ran Kies, instead of listing the current ROM and my ROM on the first page, it said in BOLD letters that "YOUR DEVICE DOES NOT SUPPORT SOFTWARE UPDATE VIA KIES".
Was it trying to do an update to something, or was it just telling me that since I'm non-stock, rooted and CWM, that it can't do an update.
Harry
Yeah, that was your one shot at getting the ICS update and now you have to wait until Summer to get it again.
ok j/k
I can't help w/kies questions but a top will not hurt.
Very funny.
I got the same Kies update. With mini Kies, that was sometimes associated with a phone update. My phone is stock but after the Kies update, no phone update was available. You didn't miss anything.
jimhlt said:
I got the same Kies update. With mini Kies, that was sometimes associated with a phone update. My phone is stock but after the Kies update, no phone update was available. You didn't miss anything.
Click to expand...
Click to collapse
Thanks for checking that. Totally appreciate it.
I updated my girlfriend's phone from stock GB to stock ICS using ODIN but she has now lost carrier billing. Any advice?
(unfortunately, i couldn't figure out how to get kies to see the device, so I used odin. almost bricked it though; it failed twice then passed the third :\)
EDIT:
I don't have root on it yet b/c I want her to be able to update ICS regularly using AT&T OTA updates and presume replacing the recovery would break that. Also, I tried wiping the play store data/cache amongst a couple other basic things like that and it didn't fix it.
Make sure your device usb drivers are right and up to date? Kies can be a pain on Windows xp or at least was for me. I have the T-mobile vers. of your phone but its almost the same.
Shanayo said:
I updated my girlfriend's phone from stock GB to stock ICS using ODIN but she has now lost carrier billing. Any advice?
(unfortunately, i couldn't figure out how to get kies to see the device, so I used odin. almost bricked it though; it failed twice then passed the third :\)
EDIT:
I don't have root on it yet b/c I want her to be able to update ICS regularly using AT&T OTA updates and presume replacing the recovery would break that. Also, I tried wiping the play store data/cache amongst a couple other basic things like that and it didn't fix it.
Click to expand...
Click to collapse
I'm having the exact same problem, under very similar circumstances...
Okay I've got myself into quite the predicament. Here is what happened. First of all I have been enjoying the benefits of having root access on my Indulge. When I heard there was an official Gingerbread update for this phone I decided to give it a go and install it using Kies Mini. It installed fine and everything worked great! There was but one problem...I could not root it. I searched forever for a solution, but could not find one. After awhile I decided to give up. I decided to downgrade back to 2.2.1 Froyo using this method. That was a very bad mistake. All this method does is overwrite the /system partition. Yes I am now running Froyo, however, the Gingerbread updated more than just the /system partition. In the About Phone it says my Firmware version is 2.2.1, but it says my Baseband version is EL06 when it should be EE05. I wouldn't have a problem with any of this if it weren't for the CONSTANT reboots. I am able to use my phone for ten minutes max before it reboots again...In fact it just did it again. Now I have tried to reinstall the Gingerbread upgrade, but Kies Mini says "Unregistered Device" in the "Firmware Version" and I am unable to receive the upgrade. I am guessing this is because it cannot detect which Firmware my phone has. I have also tried doing a factory reset many times with no luck. I have lost all hope. Will somebody please help me? I don't care if I end up with Froyo or Gingerbread, root or no root, I just want my phone to work!
HI,
I've updated the Verizon version of the Galaxy Note Pro 12.2 and I really don't like it. There's too many instability issues that I haven't seen before! I rely heavily on the S-Note and it keeps crashing on me after a few minutes when it is opened up. I can write for a bit but then it just stops working and brings me back to the home screen. The other problem is the SD Card. I never had an issue with it before, but I am now! Sometimes it goes missing when I go into a file manager looking for a document. And it occasionally freezes up!
Oh, and the best part? I like the fact that Samsung has added the "Galaxy Apps" in this Lollipop version like it is on my Galaxy Note 4 (SM-N910F), BUT IT'S ALL IN DUTCH LANGUAGE!!!
And this is suppose to be an American model with the preference language set US English?? Go figure...
I never had this problem before with KitKat 4.4.2, and I want it back!
Now I've tried using ODIN 3.10.7, 3.07, and 3.09, but I can't get it to connect. It keeps saying "added!! removed!!" when I try to use Home-Volume Down-Power" to reboot in Odin mode.
So does anyone have any suggestions on how I can downgrade?
Did you use the OTA 5.1.1 version that was pushed out by Verizon? I took it last week and this beast is way more stable, no crashes, the SD Card works properly (I have a 128GB card) and no language problems. Try resetting your tablet and getting the OTA (again).
tdetroit said:
Did you use the OTA 5.1.1 version that was pushed out by Verizon? I took it last week and this beast is way more stable, no crashes, the SD Card works properly (I have a 128GB card) and no language problems. Try resetting your tablet and getting the OTA (again).
Click to expand...
Click to collapse
No, I didn't get it by OTA. I did it through KIES. I'm an American ex-pat living in the UK for the past few years and I had this shipped to me from family back in Florida. It doesn't seem that the OTA would work at all and the only way I could get the update is through KIES.
As for resetting, that's what I was trying to do. When I do a "factory" reset, it puts 5.1.1. back on again plus the Verizon repair app is not giving me any joy since it's doing the same and placing lollipop 5.1.1, which is why I'm going through ODIN mode to place the original ROM back onto it that I've downloaded from SamMobile's website. However, as I mentioned, Odin on all versions are giving me "ADDED!! REMOVED!!".
What I really find so strange is that the Verizon Update/Repair app will re-flash with no problem; but when trying to use Odin, it won't connect. Can someone give me a clue on what's going on with that??
It would also mentioned I'm using Odin on Windows 7 64 bit and I've used separate computers so that the drivers for KIES and Verizon Update App doesn't clash, yet I'm still getting the same messages from Odin.
OR am I missing something else??
By the way, Sammy's Galaxy Apps is still in Dutch!!
sjbrother said:
No, I didn't get it by OTA. I did it through KIES. I'm an American ex-pat living in the UK for the past few years and I had this shipped to me from family back in Florida. It doesn't seem that the OTA would work at all and the only way I could get the update is through KIES.
As for resetting, that's what I was trying to do. When I do a "factory" reset, it puts 5.1.1. back on again plus the Verizon repair app is not giving me any joy since it's doing the same and placing lollipop 5.1.1, which is why I'm going through ODIN mode to place the original ROM back onto it that I've downloaded from SamMobile's website. However, as I mentioned, Odin on all versions are giving me "ADDED!! REMOVED!!".
What I really find so strange is that the Verizon Update/Repair app will re-flash with no problem; but when trying to use Odin, it won't connect. Can someone give me a clue on what's going on with that??
It would also mentioned I'm using Odin on Windows 7 64 bit and I've used separate computers so that the drivers for KIES and Verizon Update App doesn't clash, yet I'm still getting the same messages from Odin.
OR am I missing something else??
By the way, Sammy's Galaxy Apps is still in Dutch!!
Click to expand...
Click to collapse
Did you ever get this figured out? I, myself, am having a terrible time with the lollipop upgrade on my 905V. I've tried to ODIN back to 4.2.2 with no luck. ODIN fails every time I try to push one of the older versions to the tablet.
I am like you where I had to use ODIN to upgrade to 5.1.1. I was rooted and I had done a few other things which required me to factory reset a couple times after using ODIN to install an original factory package.
It is possible we are S.O.L. There is simply no DEV support for a device few people have, I don't expect much.
My only shot to try next is to see if putting one of the older versions in a specific folder will give me an option in Kies to revert back.
There is always a chance someone will come along with the answer we need.
Lollipop haywire
I to have the Verizon Note Pro and recently did the update to lollipop and is having a horrible experience... The system seems to be unstable all my apps are crashing a lot... Ive tried to revert back to 4.2.2 using Odin as well but no luck. Ive factory reset numerous times... Ive even reinstalled lollipop several times, with no luck. If any one has any insight on what this problem is or have anyway of going about fixing the crashing, please let me know...
Has this ever been figured out? When I first got my NP 12.2 on verizon I rooted it, but then I OTA updated it, like a dummy, to 5.1.1. I want to flash back down to 4.4 or whatever version it WAS so I can root 4.4 then update to a 5.1.1 or 6.0.1 rooted rom. * Any help would be appreciated.
In the same boat
Any help on this? I would really like to downgrade my NP12.2 to Kitkat to root it.
I pretty much a novice to Android, but have 20+ years with PC and MAC. This doesn't seem like it should be that big of a deal. Thanks for any help!