Cant update my note OTA - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

So the thing is i had this baseband N7000XXKK5 i rooted my note then tried first custom ics rom didnt like it restored too default GB which i backed up before flashin a custom rom then again tried another rom this time paranoid android it changed my baseband to LQ3 didnt like it revert back to again my GB backup then tried the midteam which changed my baseband to N7000XXLPT but when this time i tried to revert back to my backup it didnt change the baseband back to N7000XXKK5 n now i cant flash any custom roms as well as the OTA update
Current Details
Android version
2.3.6
Baseband
N7000XXLPT
Kernel version
[email protected] #2
Build number
GINGERBREAD.XXKKA
Help as i just wanna have the OTA update of ics n root access nothing else

Bump

You need full stock to do that, and all matching parts of a stock version. And the same csc, in plain words the same setup your phone came with.
Anything else and no ota lol
Sent from my GT-N7000 using Tapatalk 2

So just a stock gb flashed through odin would do the trick? :victory:

Yes, as long as its same csc, efs is not corrupted.
Sometimes its needed to try different roms. Had it once one version didnt ota, and earlier did.
Sent from my GT-N7000 using Tapatalk 2

Related

[Q] Stock Kernel

What is the version of the original stock kernel??
I got all messed up doing the update yesterday, it'd get to 100% several times and then say it failed, yet my kernel version had changed I believe. So I did the odin one click restore, and now its like factory new, except my kernel is still changed, odin didnt flash the original kernel I dont believe.
My current kernel version is: 2.6.29 [email protected] #2
My baseband version is: I897UCJF6
My build number is: ECLAIR
My firmware version is: 2.1-update1
Whats the version on the original stock kernel and where can I download it and how should I flash it??
Thanks!
You already have the default kernel, since u flashed the JF6 stock rom which includes the pure stock kernel.
rafyvitto

[Q] A few questions about flashing stock GB

I'm currently on a LA6 2.3.6 gingerbread, stock, non rooted, and I'm growing quite inpatient with the ICS release dates, which won't happen anytime soon for my CSC, obviously.
If I flash one of the open stock GB roms (want to change my CSC to DBT or similar), will I get the orange triangle, and will my phone get recognized by Kies in case I decide to go for a pre-rooted one? Also, will data and calls work properly with a CSC different from my phone's original one(MSR)?
I just want my Note fully functional, yet be able to use it as if it was unmodified, if possible
I am sorry for the possible stupid questions, I just couldn't find any complete explanations/answers for these!
Sent from my GT-N7000 using XDA
Backup efs if you havent already done so. See my thread regarding q backups its got a link to how to do that.
Now just flashing stock gb wont increase counters. I havent found any malfunction myself, but reading postst in this forum has tought me the outcome can be different for anyone wtf.
So I suggest make cwm backup of current rom.
Download stock dbt rom gb, flash thought pc odin. Mind you better flash pre december rom so you can root it with root only method. Mind update ics throught kies you need to be unrooted. So if root is not important, flash latest version ics dbt right away. Then change csc it will wipe data. Then you have a possible, not gauranteed ota rom.
Just dont do wipe or factory reset in ics or cwm on ics.
Make sure you have a way back for warrantee, i.e your current rom download it somewhere next to nandroid backup lol
Sent from my GT-N7000 using Tapatalk 2

OTA / KIES Update Failing...

Hi All,
Quick bit of advice, Failing on the OTA update at the moment,
I'm running;
- Android: 4.0.3
- Baseband: N7000XXLPT
- Build: IML74K.XXLQ2
Wondering if it's the fact I am running SpeedMod K3-11 which is why it's failing? Anyone else seeing this?
If so - wondering if I can reflash the stock kernel via Mobile Odin...
I have the ROM - N7000XXLQ2_N7000XXLPT_N7000CPWLP4_HOME.tar.md5 file - Is it the case that I extract the ZImage from this file to obtain the Stock ROM Kernel?
As stated here http://forum.xda-developers.com/showthread.php?t=1371007
Note: I upgraded to this current version of ICS OTA - I DID NOT flash the above file via PC Odin.
I know I could get around it by reflashing in PC Odin but I'd like to not have to go that route..
Cheers
I was facing the same problem with OTA update on my stock rooted speedmod loaded Note. I thought the custom kernel is preventing the process. So my way was to flash the whole stock rom via PC Odin. Good thing it was a non-wipe version.
And yes, the zImage you pull from the rom is the stock kernel.
Cheers,
Not sure what's up with OTA..
However think the PC KIES issue is due to the fact that once again my PC seems to have lost the drivers needed to recognise the device in Download mode..... FFS...
Conditions for kies:
Need pcode, need csc and all stock components belonging to same rom, so all stock of same rom version. No root.
Never I have read kies updated a phone if with a rom for csc a, when wanting to uodating to another csc rom, bu just changing csc.
Ota can update a rooted phone as long as components again belong to one version of stock rom. Cf kernel of that rom no, the true kernel belonging to that rom with onky root yes. Ota also succeeds without pcode, most of the time.
Another condition is intact emei, which together with pcode can be secured by flashing efs backup, but you need proper backuo then.
You can midfy pcode by hex editing certain efs files, but it most of the time to tricky to achieve. You cannot edit emei that way. So make a proper efs backup
Edit: in the end efs backup and pc odin is all you need nd a safe kernel to be able to cleanse your installation should you wish to use different version and different csc. Then again changing csc triggers reset so onky change on safe kernel
Use this knowledge wisely
Sent from my GT-N7000 using Tapatalk 2
Cheers Baz,
So in effect as I'm running a stock ROM I'd need to flash the stock kernel zimage extracted from the ROM in order to update...
Or, backup everything, flash the new stock in Odin and restore my stuff...
Or finally flash GB, wipes, OTA / KIES update...
Sent from my GT-N7000 using xda app-developers app
Yeah, the first should work
Otherwise go back indeed to gb.
Note I havent figured another variable out, on one stock rom version I wsnt able to ota, but going back version earlier I was.
Not sure what it was.
In the end, just pc oding it is faster
Sent from my GT-N7000 using Tapatalk 2
Yep seems PC ODIN is the best way, just didn't wanna have to set everything back up again..
Sent from my GT-N7000 using xda app-developers app

what does it means? and why Kies don't let me update via kies?

I heard 4.1.2 official Samsung update is rolling out.
I connected my N7000 to the computer and opened KIES after a long time i didn;t opened Kies. It said that a firmware is available, and also said a new version of KIES is available.
I thought I should update Kies first, so I did.
After Kies updated I connected the G Note again, and this time Kies said:
"Your device's current firmware version is not supported to update firmware via Kies"
Current firmware version: PDA:LPY/PHONE:LPT/CSC:LPY(KOR)
my device information is:
4.0.3
N7000XXLPT
kernel version: 3.0.15-N7000XXLPY-CL474507
Build: IML74K.XXLPY
Does anyone can tell me why KIES doesn't let update firmware via KIES?
I bought my phone few month ago from somebody and he said that the phone can get official updates.
Is the phone info and firmware/build etc. is an official firmware?
I don't want to put non official ROM or 4.1.2.
Thanks for any help!
Probably because you have a non-stock kernel. Flash the stock kernel that goes with your stock rom and try again.
It's because you probably have a German rom and the csc is set to Korea. Dial *#272*IMEI# and choose DBT.
Doing this will wipe your phone. So make sure you are on a safe kernel and backup your important data.
nokiamodeln91 said:
It's because you probably have a German rom and the csc is set to Korea. Dial *#272*IMEI# and choose DBT.
Doing this will wipe your phone. So make sure you are on a safe kernel and backup your important data.
Click to expand...
Click to collapse
How do I find the device IMEI?
and what do you mean by " make sure you are on a safe kernel"?
thanks again!
all the data is backed....
You are on ICS stock. But i dont know what kernel you are on and what info about the kernel you have mentioned, seems to be stock. Stock ICS kernels are not safe to do a reset.. so to be safe you need to install a safe kernel ... I would recommend flashing Philz kernel LRT zip from stock recovery..
IMEI is either by daialing *#06# or its in about device > status section

[Q] problem reverting back to stock from x-bean 3.0

hi guys
last year, i installed x-bean 3.0 on my i9000. i'll not bore you with the details, but i have a need to revert back to a stock rom. i've downloaded a couple of stock roms from sammobile and used odin v1.85 to restore them to the phone and wiped data/factory reset, but now the phone is in a boot loop at the samsung splash screen
not sure if i have to do something with the bootloader or the kernel? any ideas?
thanks
model number: gt-i9000
android version: 4.1.2
baseband version: i9000xxjvt
kernel version: 3.0.45-semaphore_jb_2.3.0
build number: x-bean 3.0
Hey,
Did you flash in dbsdata.rfs.tar? Going from unofficial to stock requires this file as well... Flash it in via Odin and it should stop the bootloops.
Sent from my GT-I9000
Soryuu said:
Hey,
Did you flash in dbsdata.rfs.tar? Going from unofficial to stock requires this file as well... Flash it in via Odin and it should stop the bootloops.
Sent from my GT-I9000
Click to expand...
Click to collapse
I have been meaning to ask... WTF is this sh*t? I have gone back to stock numerous times, but I have never heard of this file. Is it a specific requirement for some of the custom roms?
snapper.fishes said:
I have been meaning to ask... WTF is this sh*t? I have gone back to stock numerous times, but I have never heard of this file. Is it a specific requirement for some of the custom roms?
Click to expand...
Click to collapse
Its because the data partitions and so on (I think) in custom roms like CM, AOKP etc. are different from the stock roms. The data partitions from the unofficial roms are incompatible with the stock roms and so you get bootloops. dbsdata.rfs fixes that problems by fixing those partitions. Or something like that.
Sent from my GT-I9000

Categories

Resources