my 1st post here .. hi all :silly:
my n7000 was flashed to ( N7000JPLSB N7000OJPLSA - United Arab Emirates ) 2 months ago and i used a phil's kernel and rooted the device .. device worked good 2 months later a system update popped in and i pressed ok .
now device stuck at boot loop at the android robot .. i removed the battery so it isnt derained .. once i put the battery back and try to charge the battery the device enters the loop again
any help well be appreciated
mustafa811 said:
my 1st post here .. hi all :silly:
my n7000 was flashed to ( N7000JPLSB N7000OJPLSA - United Arab Emirates ) 2 months ago and i used a phil's kernel and rooted the device .. device worked good 2 months later a system update popped in and i pressed ok .
now device stuck at boot loop at the android robot .. i removed the battery so it isnt derained .. once i put the battery back and try to charge the battery the device enters the loop again
any help well be appreciated
Click to expand...
Click to collapse
Weird you got an update when you were running a custom kernel. Anyways, go into recovery, plug your phone into your computer and copy other Philz kernel for... JPLSB. Flash it, reboot. Do the following wipes: data factory reset, cache, dalvik, /system /preload. Once that is done just reflash again with Odin. You will loos all of your data. This will take you to complete stock - no customs kernel. If you want root again then you will have to download Philz kernel.
XxPixX said:
Weird you got an update when you were running a custom kernel. Anyways, go into recovery, plug your phone into your computer and copy other Philz kernel for... JPLSB. Flash it, reboot. Do the following wipes: data factory reset, cache, dalvik, /system /preload. Once that is done just reflash again with Odin. You will loos all of your data. This will take you to complete stock - no customs kernel. If you want root again then you will have to download Philz kernel.
Click to expand...
Click to collapse
it is a stock rom not custom but with philz kernel for the root
Philz kernel is well custom kernel, not stock kernel.
When a stock ROM having root, normally it doesn't receive any more automatic update from Samsung.
You'd better follow hints from XxPixX.
qnt said:
Philz kernel is well custom kernel, not stock kernel.
When a stock ROM having root, normally it doesn't receive any more automatic update from Samsung.
You'd better follow hints from XxPixX.
Click to expand...
Click to collapse
it is a stock rom with stock kernel but to root the galaxy note i read that flashing or wiping might cause a brick
on a stock kernel soooooooo usually after flashing the stock rom and before rooting i flash a safe kernel
i used odin in download mode and flashed the same stock firmware and surprise the device returned to its pre-brick
state exactly with all my contacts and all apps but root and kernel gone
so i am gonna root it now after installing safe kernel
thx all
qnt said:
Philz kernel is well custom kernel, not stock kernel.
When a stock ROM having root, normally it doesn't receive any more automatic update from Samsung.
You'd better follow hints from XxPixX.
Click to expand...
Click to collapse
Stock rom on any kernel will receive updates but will not be able to install it as it needs stock recovery. Notification of new update will come.
nokiamodeln91 said:
Stock rom on any kernel will receive updates but will not be able to install it as it needs stock recovery. Notification of new update will come.
Click to expand...
Click to collapse
Thanks for that info on stock recovery need to update.
had the issue too with some custom roms i use jonrom 4.1.2 LT4 custom rom now and everything is working well
So, re-flashing the ROM is the final answer..
Be it stock or custom ROM..
Related
Hello,
I'm new at flashing but I recently bought a Samsung Galaxy Note, which already had Stock ICS on it.
Android Version: 4.0.3
Baseband: N7000XXLPT
Kernel: 3.0.15-N7000XXLPY-CL474507
Got brickbug confirmed that I am running a dangerous eMMC chip firmware. I bought this Note from eBay and I'm guessing the previous owner did a reset. It is still working and I had no trouble with it, so I guess I got lucky.
Since I would like to return to a safer kernel and install Paranoid Android I read myself into some threads but would like someone to review what I've gatherd:
Flash save kernel for ICS, for example speedmod kernel with PC Odin.
Device should reboot into ICS with new kernel.
Flash Gingerbread stock ROM for my country (germany) for example this one:
N7000XXKJ4 ------ 2.3.5 2011 october-------- N7000OXAKJ4 ------------------Germany (Debitel)
Device should restart wirh Gingerbread and an old Gingerbread kernel(?)
Root and install CWM using Dr. Ketans guide and batch file.
Follow instructions to install Paranoid Android v0.4 from CWM
I have some questions for this as well:
Speedmod kernel flashes CWM with it. Does that mean it flashes the kernel and the recovery partion, too? As I understood, the CWM works from inside the initramfs, which I thought got flashed with the kernel on the /system partion (or maybe the /boot partion) but not on the /recovery.
Does CWM disapear, when I flash another ROM?
I am pretty sure, that I am running a free (= open) Version of ICS on the phone. When I install a Stock Gingerbread ROM with a Carrier afterwards (like above the Debitel company), do I have to expect weired stuff?
I am running Win 7 64bit, and I would run Odin v1.85 with admin rights. Kies ist installed. Odin found the device, too.
Thanks in advance,
gador
Speedmod Kernel will install Kernel, CWM and Root - And is flashable via odin or mobile odin.
CWM will disappear if you flash a stock ROM via ODIN, If you flash a custom ROM through CWM you will keep CWM (may change depending on kernel from the ROM)
If you flash a branded ROM via odin, You will probably get a lot of carrier branded bloatware on the device, But if you are sim unlocked, you wont get any weird issues like network unlock codes and so on.
azzledazzle said:
Speedmod Kernel will install Kernel, CWM and Root - And is flashable via odin or mobile odin.
CWM will disappear if you flash a stock ROM via ODIN, If you flash a custom ROM through CWM you will keep CWM (may change depending on kernel from the ROM)
If you flash a branded ROM via odin, You will probably get a lot of carrier branded bloatware on the device, But if you are sim unlocked, you wont get any weird issues like network unlock codes and so on.
Click to expand...
Click to collapse
So I guess, I can go ahead and they're no fatal flaws in my procedure?
(And flashing stock ROMS overrides /recovery as well?)
Check the videos in ky sig once
Just to be safe
Erm, All ROMs are different so double check in the OP but you wont lose CWM if you switch between custom ROMs, Only a full firmware flash via ODIN will replace recovery. However there are many variations of CWM, All however do the same job
the instructions above are correct, But seem to be a more complicated way of doing it, It says to flash a safe ICS kernel, THEN flash GB ROM in ODIN ??? That makes no sense.
Anyway, What i would do is, Revert to GB via ODIN, Flash SpeedMod kernel (for GB not ICS), Load all the files on to your SD card, Boot into recovery, Do a full wipe, Along with cache and dalvik cache, Then install PA + Gapps + any other mods !
azzledazzle said:
Anyway, What i would do is, Revert to GB via ODIN, Flash SpeedMod kernel (for GB not ICS), Load all the files on to your SD card, Boot into recovery, Do a full wipe, Along with cache and dalvik cache, Then install PA + Gapps + any other mods !
Click to expand...
Click to collapse
would it then be necessary at all to install the SpeedMod kernel? I included it above to make sure, the kernel is safe, but when the Gingerbread Stock ROM overrides the kernel, do I have to flash the kernel afterwards?
I suggest you stay stock and dont do any factory reset or data wipe.
Then READ and read a LOT of the topics here.
All these suggestions of flashing this and that comes with a risk. And it does not mean that if it works for others will work the same way for you.
Sent from my GT-N7000 using xda app-developers app
Yes, thats why i thought the above steps where a bit confusing lol
Flash SpeedMod (or any other GB kernel for that matter) After flashing GB via ODIN
azzledazzle said:
Yes, thats why i thought the above steps where a bit confusing lol
Flash SpeedMod (or any other GB kernel for that matter) After flashing GB via ODIN
Click to expand...
Click to collapse
Does one need root before you are able to flash GB via PC Odin?
Sent from my GT-N7000 using Tapatalk 2
mrcarlxx said:
Does one need root before you are able to flash GB via PC Odin?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I'd say no. I mean, as I understand it, you're flashing the device in download mode. There is no need for a root user.
So, against my inner "good angel", who told me to wait for a new official firmware release, I went ahead and flashed away.
It all worked and here is what I did:
Flashed the Gingerbread Stock firmware from above with PC Odin, according to the guide in the second post of the Stock Firmware thread.
Restarted and got lots of force close issues.
Flashed the Gingerbread Kernel SpeedMod from here ("speedmod-kernel-n7000-k2-12-Odin.tar")
Rebooted, continued to have force close issues.
Rebooted into Recovery (which is now CWM, due to Kernel update)
Wiped cache, dalvik cache and did a factory reset
Rebooted into a fully working Gingerbread OS
Placed PA v0.4 and GApps onto my SD Card (from here)
Rebooted into CWM Recovery
Applied PA v0.4 from SD-Card
Applied GApps from SD-Card
Wiped Dalvik Cache, Cache and did a factory reset
Rebooted into a workind Paranoid Android OS.
Although the SpeedMod Kernel got overridden by PA, I still have CWM Recovery.
Did you root first? and did you get the yellow triangle through flashing with PC Odin?
PS
I'm still dead scared about flashing a ROM after messing up my last gnote, never ever had a problem with my desire...it's shook my confidence tbh :-(
mrcarlxx said:
Did you root first? and did you get the yellow triangle through flashing with PC Odin?
PS
I'm still dead scared about flashing a ROM after messing up my last gnote, never ever had a problem with my desire...it's shook my confidence tbh :-(
Click to expand...
Click to collapse
Well, the SpeedMod Kernel not only gave me CWM, but also root. According to PA Thread Install instructions, you would need to root your device prior to installing PA.
Yes, after flashing the SpeedMod Kernel, I got the yellow triangle, but since I bought this phone on eBay, without any bill to confirm warranty, I didn't really care about it.
I did not get a yellow triangle after flashing the official Stock ROM!
So I would hazzard to guess that this would not void warrany. (Also, in Download Mode, there was the little text saying: "Custom Binary: No" after flashing the Stock Gingerbread ROM)
So, if I were concerned about warrany, I would have a second look at Dr. Ketans guide, which describes the CWM+Root procedure without increasing the binary counter (at least I think so).
This way, you could get root and CWM after flashing to Stock Gingerbread.
I just had the problem, that Gingerbread wouldn't allow me to go into the Settings Tab to activate Debbuging, which you will need for Dr. Ketans method. (All processes were getting force closed)
If it is possible to wipe the caches and factory reset the phone with stock recovery, I think it would work. It should look like this then:
Flashed the Gingerbread Stock firmware from above with PC Odin, according to the guide in the second post of the Stock Firmware thread.
Restart to Recovery. Wipe Dalvik Cache, Cache and do a factory reset (You just flashed Gingerbread Stock, which should have given you a safer kernel)
Restart
Activate USB Debugging and untrusted sources.
Follow Dr. Ketans Guide on how to Root+ get CWM
Continue from step 8 above.
Since I consider myself a complete noob to the flashing business, someone should propably confirm, what I've just written. I wanted to be on the safe side and therefore flashed a known safe kernel again over Gingerbread, just to be sure (and to get root+CWM)
Hope that helped.
Well mine didn't :-(
I'm now cursing after my planned upgrade failed :-( I'm stuck at the yellow triangle boot screen wondering what to do
My sequence was
a) Unpack SGN, and it upgraded to ICS
b) read about all the dire warnings on ICS - and curse!
c) figure out how to flash speedmod and get root via the temp CWM - and I was pretty happy about this for a few days..
d) battery life seemed poor - so I wondered if the Abyss kernel would help
e) Went into Recovery - which appeared to be CWM (volume & on/off to navigate) and flashed the Abyss kernel and performed a wipe (assured that my SGN was safe with speedmod)
f) Now stuck at the yellow triangle boot screen - wondering what to do?
My recovery seems to be the touch screen version now - when I can get into it.
Suggestions please?
(My old nexus One wasn't this tricky!)
---------- Post added at 10:25 PM ---------- Previous post was at 10:02 PM ----------
Wll I reflashed speedmod with Odin - and at least it looks like its booting!... anxious minutes later.... well I/m back. I don't know what i did wrong - but |I don't want to repeat that in a hurry.
I'll wait for CM9 to come out with an approved kernel before messing further!
Hello all... After reading here and there and in other forums, I have a series of questions that I would really appreciate if anyone can answer based on facts...
I currently have a Galaxy Note N7000 with this settings:
Android Version: 4.0.3
Baseband Version: N7000XXLPT
Kernel Version:
3.0.15-n7000XXLPY-CL474507
[email protected] #3
SMP PREEMPT Fri May 4 04:49:06 KST 2012
Build Number: IML74K.XXLPY
I want to install the 4.1.2 leaked version (already downloaded it) BUT I have some questions:
1.- I have read in different sites that I just need to do it with ODIN, no wipe required; and in other sites I have read that after installing, a wipe is required. Which one is it?
2.- According to many sites, by wiping I am at risk of hard bricking my note because of the death bug found in ics kernels. Should I still wipe?
3.- If after testing 4.1.2 I decide to roll back to I.C.S.... Again I should do that via Odin... but again I should wipe right? At risk again of bricking?
4.- This leaked version DOES NOT accept the s-pen functions at all right? so basically my spen would just be useless...
5.- THe recovery that is installed in the phone is the basic recovery that came with the phone, I havent changed it... I have read that installing some recovery files is dangerous. Which recovery is recommended?
6.- My note is NOT rooted... Does this affect my possibility of updating with this leaked firmware?
7.- and final... Do you guys recommend that I update or should I wait for the official firmware?
Sorry for the long post, but I need advice from the best ...
Greetings from Venezuela
1. you can install that without wipes using PC odin. but its a matter of luck. if it gets stuck in a boot look then you will need to do a factory reset and for that to be safe you need to install a safe kernel Philz XXLSA (i guess thats what you downloaded)
get it from here
http://forum.xda-developers.com/showthread.php?t=1901191
can be flashed using stock recovery and external SD
2. No, Always install a safe kernel and perform wipe
3. You may have to wipe this time for a proper boot as it might enter a boot loop. Same procedure, install Philz and do a factory reset. Its better to do a nandroid backup of ICS rom if you wish to return back to ICS. this way all your settings apps and customizations will be restored.
4. Incorrect. Spen is fully functional on JB leaks TW based.
5. Philz works perfectly with JB TW roms. Recovery is not dangerous. Its what you perform on it without proper reading is dangerous
6. No, PC odin can successfully flash a JB TW rom on to a non rooted Phone. But if it enters a boot loop install Philz kernel to do a reset from recovery
7. Its a long wait and no one knows when its gonna come. so if me, i would do it and i have been on all the JB TW roms available till now.
I would say, do it, do it the right way and you will enjoy the phone.
You can root your current ICS phone using the Philz kernel PhilZ-cwm6-XXLPY-XEN-v2.7 and then do a backup from recovery to be able to revert back with no problems.
Thank you so much for your reply... will do it today
Bienvenidos
Dude, another question... When you say JB TW version... What do you mean by TW...? I downloaded the one from sammobile PDA N7000XXLSA CSC N7000OXALSA... Is this a good one?
Yes. TW is TouchWiz, samsung Roms
You rock! Thank you so much... I will start doing this right now... Hope it doesnt die on me... I'm going to flash the PhilZ file and then work through the JB update... Crossing fingers...
anything, just update the post
Quick question... First: flash PhilZ... Then Wipe and then Odin? or do I go with Odin and then Wipe Data/Cache
first flash Philz, boot into recovery do a backup, then Odin, install Philz for XXLSA then wipe
Ok problems!!!! Flashed Philz (link you gave me) and when reboots, it doesnt get past the NOTE logo... I entered Recovery to do a backup and gonna go wo download mode with ODIN to update to JB and then do wipe from Philz... I-m scared beyond my pants if that makes sense at all...
Your current ROM is XXLPY right ?, which kernel did you install ? If you installed an ICS kernel , your phone should boot anyway, but if you installed a JB kernel then it wont
Yeah my bad... I installed a JB PhilZ kernel... I did a backup and flashed via ODIN the leaked 4.1.2... It loaded fine... , now my question is... Should I still update to the JB kernel for my version of JB? or do I stay with the one I installed... another question... should I still wipe?
OK. Main thing first. Now that you have backed up your rom, and the backup contains a JB kernel and ICS rom, so in future if you choose to restore the backup, dont be surprised if the phone does not boot. Later change the kernel to ICS
Which kernel did you install, update to your version of the kernel.
If the phone is fine, dont do a wipe. You can do it when you face some issues like Force close of apps or something not working as it should
I get it... will update the Philz to the right vkernel... Everything is working beautifully... Thank you for your support and patience!
So, this is what happened. I first upgraded to the latest official JB 4.1.2 XXLSA firmware. I noticed that it still wasn't as fast as I'd like, and wanted to try a custom ROM instead. I read through the guides in here and get that I have to downgrade to a GB ROM first in order for me not to hardbrick my phone. So, I download "N7000XBKK4 ------ 2.3.6 2011 November------- N7000OXXKK5--------------------- Nordic countries" from that list over stock ROM's in the Q&A root guide here: http://forum.xda-developers.com/showthread.php?t=1424997 . I follow the flashing guide to the letter, puts my phone in download mode, runs the flash via Odin, the phone restarts, and everything goes south. Basically this happens: When I start my phone it get's to the point in the GB initial startup where I'm to touch the Android to start, but then all it does is throw messages at me about this service and that service having stopped responding, untill the phone reboots. So now I have reflashed back to the JB ROM.
So basically, what am I doing wrong, and what can I do to make a proper downgrade so I can get rooted, install CWM and get down and get it on with some custom ROM's?
Thx in advance!
Same happened with me. I flashed GB and was getting force close messages. But not a big problem. Just flash GB rom again. And after flashing just delete all user data from recovery and reboot. U wont get those messages any more.
Sent from my GT-N7000 using XDA Premium HD app
You always need to WIPE data / factory reset after downgrading from JB .. GB is safe to go ahead.. if you choose ICS then first flash a safe kernel and then do wipe
It seems to me that KK5 is non wipe, which explains why you got those messages. The rest is detailed in nokiamodeln91's message BTW, JB is still not official for our Notes. What you installed was a leak with a safe kernel (if it was Philz).
nokiamodeln91 said:
You always need to WIPE data / factory reset after downgrading from JB .. GB is safe to go ahead.. if you choose ICS then first flash a safe kernel and then do wipe
Click to expand...
Click to collapse
Stock GB kernel its safe and Stock ICS Unsafe?
Yiannis75 said:
Stock GB kernel its safe and Stock ICS Unsafe?
Click to expand...
Click to collapse
Exactly.
I had this issue too when downgrading to GB. Wipe Cache and Dalvik and you should be ok from then on.
Wow. A lot of replies in just a single day. You guys are awesome
Now you say that the KK5 is non-wipe. Are there any GB-roms which are wipe, so to speak? Or do I have to do the flash to GB, enter recovery, wipe cache partition and do wipe/factory reset, then reboot into a now working phone, set up for root with USB and so forth, root and install CWM, copy the custom ROM to my SD-card (gonna go for ParanoidAndroid) as well as Google services if I want those, and then install them via CWM/Mobile Odin?
Godofmosquitos said:
Wow. A lot of replies in just a single day. You guys are awesome
Now you say that the KK5 is non-wipe. Are there any GB-roms which are wipe, so to speak? Or do I have to do the flash to GB, enter recovery, wipe cache partition and do wipe/factory reset, then reboot into a now working phone, set up for root with USB and so forth, root and install CWM, copy the custom ROM to my SD-card (gonna go for ParanoidAndroid) as well as Google services if I want those, and then install them via CWM/Mobile Odin?
Click to expand...
Click to collapse
GB LC1 is wipe. But if you want PA (which is an excellent choice) just flash a CM10 kernel in your recovery (if your recovery is safe, like GB for example). Then follow Utacka's instructions for the installation.
But if I want CWM I should do root and install CWM there? And then flash the custom ROM from CWM?
Godofmosquitos said:
But if I want CWM I should do root and install CWM there? And then flash the custom ROM from CWM?
Click to expand...
Click to collapse
The CM10 kernel comes with its own recovery where you can flash from. If you have root issues, just flash CWM-SuperSU-v0.99.zip. In any case don't flash from stock ICS with CMW.zip: if you are on ICS and not rooted flash the relevant Philz kernel (which is safe and will give you root and CWM) then the CM10 kernel.
Edit: what ROM do you have now?
I use the 4.1.2 XXLSA ROM
Btw, anyone knows where I can download the Google Services Framework so I can install it alongside Paranoid Android? I have been led to believe it's not included as per default
Thx for all the replies!!
If you have downloaded the xxlsa rom then it's inside the rom zip file. Path system/app/GoogleServicesFramework
nokiamodeln91 said:
If you have downloaded the xxlsa rom then it's inside the rom zip file. Path system/app/GoogleServicesFramework
Click to expand...
Click to collapse
Hmmm. not that I can see. Even tried unpacking the .tar files. Can't find it :/
Edit: Ah, found it Thx for all the help
i flashed to 4.2.2 this morning but i didn't like it so i decided to go back to stock jelly bean but i can't !! kies wont connect to my phone it would just keep loading and loading and never actually open the phone itself so i tried downloading the drivers manually but then odin doesn't recognize at all i tried unitsalling kies , updating , reinstalling nothing would ever work ! but y laptop recognizes the device and i can acess the files but other then this nothing
====update=====
i tried flashing with mobile odin and now it is stuck on samsung blue logo just keeps doing the animation over and over so i connected to pc and odin recgonized and flashed the rom again but then it is stuck on a boot loop and i tried wiping cache and factory data reset but wont work
What rom did you flash. Ics or JB. Install Philz kernel and do a wipe data reboot. If still no go then wipe system data cache and preload and reboot into download mode and flash stock rom again.
Rebooting in recovery and clearing cache and dalvik cache may help..
same problem here.
Mayank Chandwani said:
Rebooting in recovery and clearing cache and dalvik cache may help..
Click to expand...
Click to collapse
It didn't here. I went back from XXLT4 (rooted) to XXLT4 (stock non-root) using ODIN, and the problem was gone. Then I flashed PhilZ 4.93.6 kernel, and the problem was back. No connection, neither USB or Wifi. I was on a rooted stock kernel before, but have no idea what the problem was.
So, as soon as I root the firmware, the connectivity is gone.
Update: it's back. I have no idea why, I'm still on XXLT4 + latest PhilZ kernel.
Next problem: Where can I edit the newly added lockscreen shortcuts? Could it be that flashing PhilZ kernel removed that feature from the settings menu? I can't find it... and I've definitely seen it before I rooted.
zazzel said:
It didn't here. I went back from XXLT4 (rooted) to XXLT4 (stock non-root) using ODIN, and the problem was gone. Then I flashed PhilZ 4.93.6 kernel, and the problem was back. No connection, neither USB or Wifi. I was on a rooted stock kernel before, but have no idea what the problem was.
So, as soon as I root the firmware, the connectivity is gone.
Update: it's back. I have no idea why, I'm still on XXLT4 + latest PhilZ kernel.
Next problem: Where can I edit the newly added lockscreen shortcuts? Could it be that flashing PhilZ kernel removed that feature from the settings menu? I can't find it... and I've definitely seen it before I rooted.
Click to expand...
Click to collapse
Why do you want to flash Philz kernel..just root your phone on the stock kernel..JB stock kernel is bug free..
Go to settings--lock screen--swipe and there you have the option to change it on stock lock screen..do you have a custom lock screen??
Mayank Chandwani said:
Why do you want to flash Philz kernel..just root your phone on the stock kernel..JB stock kernel is bug free..
Go to settings--lock screen--swipe and there you have the option to change it on stock lock screen..do you have a custom lock screen??
Click to expand...
Click to collapse
Thanks! I used PhilZ because it came with cwm, built in root and was easily available.
Do you know how to go back to stock kernel without a full install? (and keep cwm and root). Something like a XXLT4 German / DBT kernel in a ZIP zile I can flash from recovery? I simply don't know where to find that.
Mybe SCS information is missing.*#1234# and view SCS code.
My CSC information is currently "N7000OXALT4" and nothing more. I was half expecting "DBT" behind that. Could that really be the problem?
Looks like I should go for a new nandroid backup & CSC reset?
zazzel said:
Thanks! I used PhilZ because it came with cwm, built in root and was easily available.
Do you know how to go back to stock kernel without a full install? (and keep cwm and root). Something like a XXLT4 German / DBT kernel in a ZIP zile I can flash from recovery? I simply don't know where to find that.
Click to expand...
Click to collapse
The stock kernel is the zImage which is included in the stock rom, and can be flashed.
qnt said:
The stock kernel is the zImage which is included in the stock rom, and can be flashed.
Click to expand...
Click to collapse
Thanks, I figured that out in the meantime, packed zImage into another flashable ZIP and signed it. Now I can theoretically flash it using "mobile ODIN" (to keep root) or from CWM. It's still not the perfect solution since I would definitely want CWM. So currently, I keep running PhilZ and wait for a better solution for the lockscreen icon issue.
whats the issue with lock screen? sorry for asking but after reading the thread i got confused.
How to downgrade from KitKat to jelly bean 4.1.2 through recovery
You can only flash custom ROMs based on touchwiz ROMs through recovery like sweetrom or aryamod .... or use Odin to flash original Samsung firmware because you can't use recovery to flash original firmware.
Press thanks if I helped you.
Sent from my GT-N7000
kaborayyan said:
You can only flash custom ROMs based on touchwiz ROMs through recovery like sweetrom or aryamod .... or use Odin to flash original Samsung firmware because you can't use recovery to flash original firmware.
Press thanks if I helped you.
Sent from my GT-N7000
Click to expand...
Click to collapse
Or he just has to flash kernel for stock based ROMs and then flash some 4.0.x ROM.
I have Omni rom 4.4.2 and how to go back to 4.1.2 (sweet room v1.1 lta e.g or aryamod v4)
sasabo said:
I have Omni rom 4.4.2 and how to go back to 4.1.2 (sweet room v1.1 lta e.g or aryamod v4)
Click to expand...
Click to collapse
same way you flashed omni.
nokiamodeln91 said:
same way you flashed omni.
Click to expand...
Click to collapse
any tutorial?
sasabo said:
any tutorial?
Click to expand...
Click to collapse
boot recovery
wipe data and cache
install new rom
reboot
Wipe Data/Factory reset” or not?
sasabo said:
Wipe Data/Factory reset” or not?
Click to expand...
Click to collapse
Same as step 2
which cwm to flash,philz v5 or kitkat v 6?This say by sweet rom: Flash any Philz JB Kernel (after 4.35 cwm but recommend any newer than 4.89.4).
Do I need to flash an older version of CWM recovery when I switched back to JB 4.1.2?
How to revert back from Omni ROM KitKat to Stock Jellybean Rom on my N7000
Hi,
I am a noob and have installed Omni ROM KitKat 4.4.4 on my Samsung Galaxy Note N7000.
I am not able to effectively the features that were available on my note ealrier, not I am able to backup contacts from Titanium BAck Up.
I would like to revert back to the original firmware jellybean 4.1.2 . Is downgrading going to brick my mobile , can some one help me with this .
lakkuMS said:
Hi,
I am a noob and have installed Omni ROM KitKat 4.4.4 on my Samsung Galaxy Note N7000.
I am not able to effectively the features that were available on my note ealrier, not I am able to backup contacts from Titanium BAck Up.
I would like to revert back to the original firmware jellybean 4.1.2 . Is downgrading going to brick my mobile , can some one help me with this .
Click to expand...
Click to collapse
Downgrading to JB is as easy as booting into recovery, wiping data, booting into download mode and flashing the stock rom
or booting into recovery and flash a custom TW rom or restore the backup if you made any before flashing Omni.
I have a non-rooted phone upgraded with what Samsung provided (several OTA, then Kies to 4.1.2, N7000XXLTC).
I'd like to downgrade to stock 4.0.4. My steps are:
1. wipe cache & data from Recovery (would a Factory Reset do both?);
2. use Odin to flash the ROM;
3. never do any sort of wipe again.
Is that correct?
doloresanto said:
I have a non-rooted phone upgraded with what Samsung provided (several OTA, then Kies to 4.1.2, N7000XXLTC).
I'd like to downgrade to stock 4.0.4. My steps are:
1. wipe cache & data from Recovery (would a Factory Reset do both?);
2. use Odin to flash the ROM;
3. never do any sort of wipe again.
Is that correct?
Click to expand...
Click to collapse
Steps are correct... Use the recovery option to wipe data / factory reset ..instead of the settings menu.
Do I have to root my device to use PC Odin?
doloresanto said:
Do I have to root my device to use PC Odin?
Click to expand...
Click to collapse
No
nokiamodeln91 said:
Downgrading to JB is as easy as booting into recovery, wiping data, booting into download mode and flashing the stock rom
or booting into recovery and flash a custom TW rom or restore the backup if you made any before flashing Omni.
Click to expand...
Click to collapse
same thing for me,
but I have a issue here. I had made a backup of my 4.1.2 rom in cwm, and flashed a 4.4.3 omnibus rom,, after flashing omni I have twrp recovery rather cwm recovery , so I am unable to restore cwm backup
do I need to flash cwm again ,?
or any other ways
omni rom draining battery very fast, and it made a dead battery
thanks
vishvish3 said:
same thing for me,
but I have a issue here. I had made a backup of my 4.1.2 rom in cwm, and flashed a 4.4.3 omnibus rom,, after flashing omni I have twrp recovery rather cwm recovery , so I am unable to restore cwm backup
do I need to flash cwm again ,?
or any other ways
omni rom draining battery very fast, and it made a dead battery
thanks
Click to expand...
Click to collapse
Yes you will need to get CWM.. flash raw or philz kernel and then reboot recovery, wipe and restore the backup.
Let me share my own experience
Whenever i wanna go back to jellybean from kitkat :
1. Do clean wipe
2. Flashing official gingerbread rom
3. And then installing jellybean..
I dont know why but whenever flashing jellybean after do a clean wipe it never works so what i do is flashing gingerbread first hehe
Sent from my GT-N7000 using XDA Free mobile app
I'm on 4.4.4 DU Rom.. The phone got hanged after I enabled the allow mock location option. Then the phone got stuck at the Samsung Logo screen. I went to recovery and tried doing factory reset, but it failed with error as unable to mount /data. After that recovery mode is not available, but I can go in Download mode. So, i tried to install JB 4.1.2 - N7000XXLTA via Odin. But the process gets failed after 'NAND write start'!!!
Any solution???