Hey guys, I rooted my friends i9305t successfully using CF Autoroot and then using Mobile Odin (didn't install a custom recovery as Chainfire didn't recommend it in his CF Autoroot thread) flashed Community Rom v1.1 and it was all running fine. Was all going fine until he realised his camera wasn't working and in the Community Rom v1.1 it had specific instructions to get it working. I followed them and flashed the kernel default kernel to get the camera working. After flashing the default camera, it broke wifi and sd card and internal memory as was expected in the instructions, and this kernel got the camera working. The instructions then said to flash the aGNI purestock kernel, so I went back into mobile odin however it said device could not be recognized, I then realized by flashing this kernel I had lost root in doing so. So I used CF Autoroot and got root back however I'm still on the same kernel that broke internal memory access and wifi. I am now completely stuck, have no wifi, play store won't open but I think I have root, and got no idea what to do now. Should I flash TWRP through adb and then boot into recovery then flash the working kernel? Can I flash the kernel through ADB? Please help. Thanks
I did not tested to flash kernel via adb. I always flash the kernel on recovery. Philz recovery to be more precise.
sonyc2011 said:
I did not tested to flash kernel via adb. I always flash the kernel on recovery. Philz recovery to be more precise.
Click to expand...
Click to collapse
Ok I managed to get CWM recovery onto his phone. However after trying to flash the kernel, it won't actually update. even after booting, it still shows the kernel as the one before flashing the new kernel. Any ideas?
Try to install philz recovery. Some users had problems installing the rom whit cwm.
Edit : i am not a developer. I am the tester and the op of community rom. Post this question in the community rom forum. Maybe other users can help you.
I too had a few problems trying to flash a kernel and a couple of extra packages, but Philz touch worked great. I used Rashr to flash the recovery and (touch wood) the phone has been sweet since.
Related
Hi,
I flashed CF-Root-XW_DBT_JVI-v3.7-CWM3RFS, which worked fine and I have root access now.
But my problem - actually I dont know if its a problem - is:
I cannot boot into CWM Recovery using the 3button method.
I can successfully boot into CWM Recovery using the CWM Manager app.
The reason why I am asking:
I want to flash [ROM][ICS][4.0.3][BUILD23][BETA2.02]AOKP.
And in the instructions they are mentioning:
--COMING FROM STOCK ROMs/SAMSUNG BASED ROMS-
[..]
*WHILE FLASHING THE PHONE WILL END UP IN A BOOTLOOP, NO PROBLEM.
*SWITCH OFF BY REMOVING BATTERY.
*REBOOT INTO RECOVERY.
*REFLASH .
Click to expand...
Click to collapse
So I tried whether I can boot into CWM recovery using the 3-button method.
I saw on the CF-root thread for SGS2, that it only boots standard recovery, if there exists a samsung package (What is meant with package? firmware?).
But on the SGS thread chainfire writes:
- Booting into recovery will immediately give you CWM. The standard recovery is completely gone.
Click to expand...
Click to collapse
So I dont know if its an error, that I cannot boot into CWM with the 3button method,
or if its ok, because I still have the stock Samsung ROM running.
Thanks for your help!
Georg
I solved the problem. Maybe it helps someone.
I flashed AOKP Beta 2.02 and the SGS didnt end up in a boot loop!
It just booted into Semaphore CWM and from there I flashed AOKP again->Reboot->Finished.
During installation I had another problem: I put the AOKP zip onto the external/real SD-card. When the SGS booted into CWM after the first flash, the SD Card wasnt mounted But thanks god, the 3-button method still started the standard recovery mode, and I could reflash the original Samsung firmware using Odin.
I then re-rooted the phone and started the whole process again, but this time storing the AOKP zip on the internal SD-card
Hi, I succesfully rooted Galaxy Note and flash CWM recovery, but I have problem with all Custom ROM's. After flash from recovery still have black screen. Only Custom ROM functional is Cassies XLR. ClockworkMod Recovery has strange behavior, sometimes lag in wiping or another action. I trying another Recovery - Thor Touch Recovery and has similiar problem, wiping or flashing is not completed (abort or reboot recovery). Why are you doing?
Thank you for answer
Regards Krysoft
http://forum.xda-developers.com/showthread.php?t=1329360
follow this thread for rooting and flashing.. this would help you..
Well yours is another note fussy about the quality of the rom installed. Lol
When i made lc1 rom i did so with chainfires latest kernel. However after i tries to boot i would get tje blackscreen.
I had to switch to francos kernel before i released the rom as that did not give the blackscreen. Several reports of this in cf thread.
Not sure what rom base you rootes from and which kernel.cwm packaged you installed.
Also are all roms u tried lc1. Can you try a la6 rom and see
Sent from my GT-N7000 using xda premium
Thank you for answer, but nothing solution is worked. Only possible solution is Chainfire ICS Repack, after flash is now working every AOSP's.
Problem solved, thank you for help.
You can now lock
Regards Krysoft
Hi All,
I'm newly registered as I have problem in using HydraCoreNirvana Kernel.
I was using ZSLPN ICS Stock ROM with PhilZ-cwm6-ZSLPN-OZS-v2.7 Kernel.
A few days ago, I booted into CWM (Power + Up + Home) to flash MaxFu_HydraCoreNirana_n3_std.zip kernel.
HydraCore Kernel is working fine except that this kernel uses a lot of battery according to the
battery monitor. I keep using it for 3 days to make sure the whole system is stable after flashing a new kernel
but it is still consuming a lot of power.
Today, I boot into CWM (Power + Up + Home) to flash back the PhilZ-cwm6-ZSLPN-OZS-v2.7.zip kernel.
After flashing, I select reboot system, the "Galaxy Note N-7000" shows up and then black screen, i.e. without
the boot animation screen. I wait for a long time but still black screen. I tried to power up serveral times but same
thing happen. I then boot into CWM (Power + Up + Home), I can see PhilZ CWM so the PhilZ kernel should be flashed.
I then use this PhilZ CWM to flash Hydra kernel again and then reboot system. It can boot up.
I then try to boot into CWM to flash PhilZ kernel again, same problem. Now I flash back to MaxFU_HydraCoreNirana Kernel.
What's wrong with my procedures? Any idea? Now, I'm afraid to flash any other kernel as I am afraid I cannot flash
back to MaxFu Kernel and that will brick my phone.
Please help. Thank you so much.
I cannot post in Max_FU kernel thread as I am new here and not allowed to post there.
http://forum.xda-developers.com/showthread.php?t=2053084
Thanks.
It is happening because the latest Hydracore kernels have the new Mali drivers, which are incompatible with previous kernels. So, when you first flashed Hydracore, it also installed these new drivers; when you flash PhilZ kernel back, the new drivers are still there, so the kernel can't boot up. The solution is to install a "revert" package which will install and older Hydracore kernel (without the new Mali drivers), and also delete the installed drivers. Search the Hydracore thread for "Returning back to Hydra v5.3 std.zip". This is the file you should get and flash through CWM. After that, you can flash PhilZ kernel again.
To make it easy, download and flash returning back to hydra.zip 1st. After that you can flah philz kernel.. You can go to philz tread you kernel has been updated to v3.99
dbolivar said:
It is happening because the latest Hydracore kernels have the new Mali drivers, which are incompatible with previous kernels. So, when you first flashed Hydracore, it also installed these new drivers; when you flash PhilZ kernel back, the new drivers are still there, so the kernel can't boot up. The solution is to install a "revert" package which will install and older Hydracore kernel (without the new Mali drivers), and also delete the installed drivers. Search the Hydracore thread for "Returning back to Hydra v5.3 std.zip". This is the file you should get and flash through CWM. After that, you can flash PhilZ kernel again.
Click to expand...
Click to collapse
Thank you so much for the detailed description. I've not noticed that Mail drivers are being installed.
zai89 said:
To make it easy, download and flash returning back to hydra.zip 1st. After that you can flah philz kernel.. You can go to philz tread you kernel has been updated to v3.99
Click to expand...
Click to collapse
Hi zai89, thank you so much for your file. I flashed it and then I can flash back to PhilZ newest version.
By the way, I have used your file (v5.3 std kernel) for a while and it consumes the power normally. I still don't
understand why the HydraCoreNirvana drains huge power in my ROM (of course I am not complaining about
HydraCoreNirvana kernel, maybe my ROM problem). Since now I can flash back to PhilZ kernel, I may try
the v5.3 standard you suggested and see how good it is.
Once again, thank you very much for your time and kindly 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.
Hello there.
I have a problem with my N7000. Today I've flashed stock firmware onto my phone, everything went ok, but I have a problem now. When I'm trying to install something from recovery, I can't. I select the ROM, everything is beeing checked, etc, and when it wants to install update, a message appears: "This packgage is for 'galaxynote,n7000,N7000,GT-N7000' devices: this is a ' '." . This happens with every single rom that I am trying to install via recovery. I tried to flash stock firmware two times, two different, still same effect, tried to whipe data/cache etc, still didnt got any effect. Any solution guys?
After you flash the stock ROM, the recovery will be stock as well.. You will not be able to flash roms from here.. For that you will need to flash philz kernel.
Well actually I can install anything via recovery, so installing kernel isnt possible.
Emkarcinos said:
Well actually I can install anything via recovery, so installing kernel isnt possible.
Click to expand...
Click to collapse
You can flash Philz kernel from stock recovery..
nokiamodeln91 said:
You can flash Philz kernel from stock recovery..
Click to expand...
Click to collapse
I have exactly the same problem (and the same situation) as the OP. You cannot flash Philz kernel from stock recovery because the exact same error will pop up.
Right mate I think I got it. You will need to flash an older version of Philz kernel first, and then upgrade. Worked fine for me once I decided to install "05.05.2013 - PhilZ-cwm6 v5.00.4 with CWM 6.0.3.1 based recovery" first.