When I restore my galaxy note with the a back up from Criskelo ICS rom, my Note loses root. How can I get it back again. I try the rooting method for a GB rom. However every time I did that the phone would not boot up and I have to flash another rom. My Note would then lose root again when I restore it with a back up from Criskelo ICS rom. Thanks for your reply.
You need to reflash CF repack LP1 with Mobil Odin, wipe data, cache and dalvik and flash again the Criskelo's ROM this way you have no issues.this way is clean instal.
Sent from my GT-N7000 using xda premium
tknguyencsu said:
When I restore my galaxy note with the a back up from Criskelo ICS rom, my Note loses root. How can I get it back again. I try the rooting method for a GB rom. However every time I did that the phone would not boot up and I have to flash another rom. My Note would then lose root again when I restore it with a back up from Criskelo ICS rom. Thanks for your reply.
Click to expand...
Click to collapse
There is a foolproof way to restore ICS Roms. Look at the stickies in Development, there's a thread created by Matius44 covering that subject.
How to root galaxy note with Criskelo ICS rom
Is that the method where you flash the Abyss 4.2 kernel then restore the backup rom? When I did this and get into the CWM, I cannot do anything since the CWM in my note do not response to any input. I had to put the Note into download mode and flash the FM kernel, then I can reinstall the Criskelo ICS rom v1.4. However when I reinstall the Criskelo ICS rom v1.4 I could not get it to work just like the first time, all the power toggles does not work. Thanks for your reply.
tknguyencsu said:
Is that the method where you flash the Abyss 4.2 kernel then restore the backup rom? When I did this and get into the CWM, I cannot do anything since the CWM in my note do not response to any input. I had to put the Note into download mode and flash the FM kernel, then I can reinstall the Criskelo ICS rom v1.4. However when I reinstall the Criskelo ICS rom v1.4 I could not get it to work just like the first time, all the power toggles does not work. Thanks for your reply.
Click to expand...
Click to collapse
As I said, the method is foolproof. Your root was gone, that's why you couldn't implement it.
Related
Hi everyone
I am new to Android. I upgraded my galaxy note GT N7000 to the official ICS German version. everything went smooth but then the battery consumption was terrible. I tried Franco kernel #3 and it didn't help so i restored the other kernel using CWM. everything is fine now but i heard about the risk of phone brick. I want to go back to GB but all the methods i reviewed involve wiping data which is the risky step that might hard brick the phone. Any suggestions? ?
Thank you and forgive my humble English
Sent from my GT-N7000 using XDA
afaik there is no way to downgrade (officially) without wiping everything :/
flash via cwm the abyss kernel, reboot in recovery through this kernel
Wipe & reflash from abyss a GB rom
I did a CMW backup before flashed to German ICS. After that find out that the ori ics is not really fast and stable, so I restore back to GB through CMW..
ckkwang said:
I did a CMW backup before flashed to German ICS. After that find out that the ori ics is not really fast and stable, so I restore back to GB through CMW..
Click to expand...
Click to collapse
unfortunately I didn't back up my GB
Spartagek said:
flash via cwm the abyss kernel, reboot in recovery through this kernel
Wipe & reflash from abyss a GB rom
Click to expand...
Click to collapse
probably I will try that. I was decided to keep the ICS till a solution for the brick comes up but this afternoon the phone screen started to go blank and display like old tv so it seems I have to go back to GB.
Another question please : Is there a risk that the phone will "auto-brick" by itself if I just keep the current ICS without making any changes or the brick happens only while installing or changing something??
Hi,
I as of yet, am not going close to any ICS build till the issue gets solved by someone.
so I am experimenting with different gb roms. i was using checkrom v6 but didnt like it, so followed steps to install darkyrom/alliancerom extreme edition. i followed the steps as I was told to install allianceota and flash the rom through there. it didnt work. so instead using cmw i flashed through recovery, it did flash but there no root.
so now, i reflashed a stock la6 rooted rom from here; http://forum.xda-developers.com/showthread.php?t=1535025
this went smoothly with no problems, so i installed allianceota as normal, this time when i try to flash the following messages come up:
Installing Multi-CSC
Can't access to '/system/CSC/KOR/system/'
Successfully applied multi CSC"
and then it gives me the option to reboot, wipe cache and a few other options, not full recovery mode.
shall i just reflash the rom through recovery, or am I doing something wrong? and does the slight error above mean I have a problem with my note?
cheers in advance.
Let me just say that almost every ICS ROM out there now has disabled the MMC_CAP_ERASE code in the kernel that activates the eMMc bug and bricks your phone. If you want stock ICS, you can use SpeedMod or Franco kernels. If you want AOKP, there is that now. If you want CM9, there's a bunch of variations plus the official CM9 nightly. If you read through the OP and stickies, you will be okay.
Are you on stock recovery still? It sounds like it from the error you are getting. Try flashing CWM recovery and installing the GB rom with that. Follow Drketan's thread in Android Development.
hmmm, so would you advise me to use ics? is it much better? i dont want to use cm9 builds as i need the spen apps and so on. i have looked into kingdroid or alba.
I'll have to think hard about this. i may give it a shot soon though..
oh and btw, I fixed the problem, yep it was to do with cwm it wasn't installed with the stock rooted rom. as for allianceota, it still didnt flash the rom, i had to flash the rom through cwm manually.
cheers anyhow.
salespalace said:
hmmm, so would you advise me to use ics? is it much better? i dont want to use cm9 builds as i need the spen apps and so on. i have looked into kingdroid or alba.
I'll have to think hard about this. i may give it a shot soon though..
oh and btw, I fixed the problem, yep it was to do with cwm it wasn't installed with the stock rooted rom. as for allianceota, it still didnt flash the rom, i had to flash the rom through cwm manually.
cheers anyhow.
Click to expand...
Click to collapse
I love ICS a lot more than GB. If you want to use stock ICS, I would just use Franco or Speedmod kernels with it and be safe. Read both of their forums and decide what you want to do.
I had the same problem with rom deodex i had flash with odin 1.85 firmware gingerbread here ; http://www.hotfile.com/dl/152168378/f76281c/N7000XXLC1_N7000OXXLB3_ATO.zip.html... then i made wipe cache and cache dalvick .
I've just flashed AlBa repack latest one on xxlq2, I did it by following the steps,
I thought i had broken my phone, because when the flashing finished and i was rebooting, at the beginning when it welcome to galaxy note n7000 and then goes to the bootup video, it restarted that several times, then after like a few minutes it loaded the homescreen and startup.
salespalace said:
I've just flashed AlBa repack latest one on xxlq2, I did it by following the steps,
I thought i had broken my phone, because when the flashing finished and i was rebooting, at the beginning when it welcome to galaxy note n7000 and then goes to the bootup video, it restarted that several times, then after like a few minutes it loaded the homescreen and startup.
Click to expand...
Click to collapse
-Flash a stock GB rom with pc odin
-Root it
-Go to cwm and wipe all (factory reset,cache and dalvik and then Install the ics rom that you like
-Reboot system and now it should work
Sent from my GT-N7000 using Tapatalk 2
Hi,
Currently I am still on GB CheckROM v5 with franco kernel 6.Never flashed any ICS ROMs before.Now I would like to finally upgrade
So before flashing ICS ROM,i would like to double comfirm the steps which i have read
1.)Boot into recovery and install GB abyss kernel 4.2
2.)Reboot recovery to abyss kernel(Can i restart phone?)
3.)Wipe data / cache / dalvik
4.)Flash ICS ROM
5.)Reboot phone
Side Qn,I have GB apps that is not updated to ICS compatibility, if i try to restore them,will it cause conflict?
Thanks!
If you're on a rooted GB, you don't need the Abyss step.
Also, when you move to ICS, using NoteCore, SpeedMod, any CM9/10 kernel are 100% safe to flash from.
ROM recommendations, CleaNote, KingDroid 7.1 and Asylum 20 (CM9-based) are my favorite.
Have a look to 'ROM Switching' on my signature.
Hi dr.ketan
I have read yr ROM switching guide.Great guide btw
I would like to clarify that the steps are for stock ICS ROMs?
cause I would like to flash from checkrom GB straight to criskelo's ICS V11.2(Post #2 says flash abyss then to criskelo ROM).I do not have to flash stock ICS ROM first correct?
Thanks!
JxXxn said:
Hi,
Currently I am still on GB CheckROM v5 with franco kernel 6.Never flashed any ICS ROMs before.Now I would like to finally upgrade
So before flashing ICS ROM,i would like to double comfirm the steps which i have read
1.)Boot into recovery and install GB abyss kernel 4.2
2.)Reboot recovery to abyss kernel(Can i restart phone?)
3.)Wipe data / cache / dalvik
4.)Flash ICS ROM
5.)Reboot phone
Side Qn,I have GB apps that is not updated to ICS compatibility, if i try to restore them,will it cause conflict?
Thanks!
Click to expand...
Click to collapse
Thats tutorial is right..
Just flashing the rom from franco kernel..
But if u're not sure with franvo kernel n want follow all the tutorial u can do it..
2.reboot recovery to abyss kernel thats mean had u flash abyss kernel u must reboot recovery..
U can do normally reboot but u will get stuck..
Don't be afraid,u can use home + volume up +power button...
Sent from my GT-N7000 using Tapatalk 2
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 will try to be as detailed as possible. I have been long time user here, but this is the first time I'm posting. I usually read the instructions and posts and that usually suffices my needs. I was on a rooted galaxy note running chasmodo's assylum rom for quite some time now. For Flashing a new rom, I used to go to recovery mode, flash abbysnote kernel (v 3.9) and install a new rom. A few days ago i tried to flash Ezaechiel XXLT6 KM edition - V2.1. I guess I should have checked md5 of the downloaded rom coz after flashing it, my phone refused to boot up. It always took me to the recovery mode screen where i tried to install abyssnote kernel and reinstall assylum. but it didn't work. So I went to dr. ketan's post and tried to flash a pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) using pc odin. Now my phone works fine but i'm on ginger bread. I tried to flash new roms using recovery mode (abbyssnote kernel method) but no new rom can be installed. Everytime I try to install a new rom i face boot loop or get stuck on the setup screen. So I follow the PC odin method to flash the same pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) to get my phone working again. I would like to go back to assylumrom because i got used to aosp jellybean so much now. Anybody who has faced a similar problem in the past, please help
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Thanks
ThaiDai said:
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Click to expand...
Click to collapse
Thanks for the quick reply thaidai. I will try the method and get back to you I used to do a clean wipe every time.
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I tried installing Cassies Xtraliterom XLC1 after the PC odin method. Got boot loop. What I'm basically saying is, after trying the PC odin method to rescue the device, I can't seem to install any other rom on it using the recovery mode route. Not even other GB roms. What am I to do??
Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I started using abyssnote kernel to install new roms after the "brick scare" of last year after which a lot of developers started recommending the method. I used to change between GB, ICS and JB roms easily using the abyssnote kernel. Don't know why it's not working anymore.