Hi,
I update my Galaxy note 10.1 8010 with the firmware XXBLK9 German Jelly Bean rom last night with Odin, all went well and it's successfully installed on my device but the problem I have is that my Note will no longer connect to Kies.
All I get is the screen 'connecting device' and it doesn't move on from there?
If anyone could please help me with this I'd be very grateful as I'm worried that I will no longer be able to receive official updates.
Thanks,
Burnage
Total removal of Kies including registry entries .
Followed by install of latest Kies ..
If you go down the Kies route its the German updates you get '
Alternative join XDA Developers and flash stock roms custom roms .
jje
Related
Hi,
I flashed my phone to the latest ICS firmware at the time, which was lp6 i think. I want to downgrade it to another official one, like the unbranded UK version so when it is released in UK I can upgrade it using kies.
I tried many firmwares but only 1 was had the ability to be upgraded via kies according to the firmware listo on sammobile.com, I tried it but Kies states Your Device Does Not Support Updating Via Kies.
So just to test, I downloaded the latest o2 ICS firmware, I still get the same message.
Anyone know what I can do so kies recognises it?
All help will be appreciated, and thanks.
maybe trying to download last original gingerbread rom with 4 files and try to update from kies
hamadazh said:
maybe trying to download last original gingerbread rom with 4 files and try to update from kies
Click to expand...
Click to collapse
Do you know which one it is? I can't seem to figure out which one it is.
if you know odin you can use a rom to flash back to gingerbread like 2.3.5 official frimware : )
I have a verizon samsung s3 thats rooted and unlocked. For severel weeks i have been prompted to upgrade my device but every time i try it starts then stops about a quarter way thru and shows a dead android guy laying on his back. My phone restarts just fine with the old software still installed. I have looked for the officail jelly bean 4.1.1 rom so i can install it. But cant find it. Only can find custom. Can anyone point me to a official rom download or tell me how i can get my phone to just do it thru the update on my phone. Why is my phone having problems updating anyway. Im guessing it because of it being rooted or unlocked. Thank you for the help!!!! MY PHONE INFO!!!!! SCH-I535 ANDROID VERSION 4.0.4
There is no official Jelly Bean ROM yet. The update it just a different modem and some security updates. I would just flash a custom recovery and install a JB ROM.
I am here from Sweden and I couldn't wait for Kies to upgrade my phone to Jelly bean with Kies, so I upgraded my phone to Jelly bean with Odin OTA which is released for Poland and its working perfectly, but now the problem is that if i connect my phone to KIES on my laptop so it gives me a message that "Your device does not support software upgrading via Kies". So please let me know if there is any solution so that I can still connect my phone with KIES software. thanks
Moved to General Q&A.
I had the same problem! Here in Brazil the update didn't come either, so I updated by Odin. I believe the only way to use kies again is going back to the original firmware(you can get it in sammobile if you need, by the way). I'm not entirely sure it's the only solution, though.
Hi All,
Hoping for some advice
Ages ago I installed some custom roms on my UK N8010 - I now want to pass the tablet onto a non technical family member and want OTA updates to work
I did a restore before and in download mode it showed Binary as official and system status as official but OTA was not working
I've used Odin to flash the BTU N8010XXUCMG1 stock rom on there from samsung-updates.com
All seemed fine, though now there is no OTA update to test.. when I hold Power+Volume to get into download mode it is still showing "Odin Mode" at the top
Can anyone advise how I can be sure that OTA will work?
Thanks in advance!!
connect the note to Kies on pc , and check on Kies for updates, if it says u r modified then OTA will not work, if it says u r on latest firmware , then u r good (I think )
Thanks - It did that before but still failed when upgrading on the device itself
I did some more digging and managed to find an older firmware on sammobile.com, flashed that and it's updating ok it seems
Hi
I've flashed firmwares before on Galaxy mini, Galaxy grand prime and Note 10.1 GT-N8000
So I'm a little oriented with the flashing process and even the rooting process of my devices
I've used Sammobile many months ago to get the 4.4.2 firmware that was non-official, and it worked fine for many months & I have rooted my note a couple of months ago and it was working fine, but the problem was that the charging time usually exceeded 8 hours
and that was too long as I was starting to use my note longer than usual lately
So I tried 2 days ago to downgrade to an official 4.1.2 ROM but The process Failed and I got that message:
"Firmware upgrade encountered an issue
Please select recovery mode in Kies & try again"
I tried recovery mode, but I haven't backed up my firmware on Kies before, so it didn't work for me as Kies didn't find any backed-up firmwares on my laptop
I tried firmware upgrade & initializing.. I entered my model and S/N, but I got a message that this model doesn't support initializing!
I've windows 10, and I've tried Odin 3.07, 3.09, 3.10, 3.11
I removed my external memory card, stopped the antivirus, changed the USB port and tried flashing many other firmware versions, some are 4.1.2 and the others are 4.4.2, some are official and others aren't, including the non-official version that I think I've used before
But all my trials failed to get my note working again! and I'm always stuck with this message and can't even turn my note off!
Please, can anyone help me in this problem?
IT FINALLY WORKED
I tried flashing for the zillion time.. it worked with the non official ROM
and when it opened I found all my apps there! without the rooting app
and that was In no time, so it's not due to backup
Now I want to flash an official one, or downgrade to the official 4.1.2, what can I do to avoid facing the same problem again?