Hi just flashed the 4.6 beta 5 the ROM is super fast and smooth. Keep up the great work.
For some reason I cannot get into the recovery. The Phone boots up and runs super fine but when I try to reboot into recovery it just goes blank. I was thinking of pushing the recovery img through the Rashr app. However it is only showing the Philz recovery img for the phone. Any idea where I can get the cwm img.
There is no recovery image for this device, it is embedded within the kernel. If the kernel on latest build doesn't have working recovery, your best bet is to either flash another compatible kernel or pull one from a different working ROM that is compatible.
@zebelchior I neglected to mention you would have to flash Philz from PC Odin first, then you can flash raw kernel or make your own zip to flash your kernel with working recovery (be careful If you don't know what your doing). Be aware that your ROM won't boot directly after flashing Philz because its for touchwizz, so ensure you have whatever you intend to flash after on your internal SD before you start this process.
That's my first reaction to flash Philz. But the device is not being recognized in Odin on my home PC. Downloaded the latest drivers but still no luck it's opening the storage etc when it is on, but the little blue light on the Com port in Odin is not showing....
I was thinking of waiting for next week's release and letting the auto update do its thing.
That's my first reaction to flash Philz. But the device is not being recognized in Odin on my home PC. Downloaded the latest drivers but still no luck it's opening the storage etc when it is on, but the little blue light on the Com port in Odin is not showing....
I was thinking of waiting for next week's release and letting the auto update do its thing.
If no luck with that, let me know. I have the universal samsung drivers saved on my PC. I remember I had a hard time finding a working download link for those.
That's my first reaction to flash Philz. But the device is not being recognized in Odin on my home PC. Downloaded the latest drivers but still no luck it's opening the storage etc when it is on, but the little blue light on the Com port in Odin is not showing....
I was thinking of waiting for next week's release and letting the auto update do its thing.
Faced the same problem. ODIN just wouldn't recognize my device. So I flashed stock and did everything again, just to share what I did:
Symptoms:
1. Can't enter recovery mode.
2. Can't flash with ODIN or apply zip update from SD card
Actions:
1. Apply "N7000DXLSE_N7000OLBLSE_N7000DXLS8_HOME.TAR.md5" (stock ROM) update to phone via ODIN
2. Wipe user data and cache, reboot.
3. Flash CWM by copying "PhilZ-cwm6-DXLSE-OLB-4.91.2-signed.zip" (download from https://www.4shared.com/zip/k2JGEiMt/PhilZ-cwm6-DXLSE-OLB-4912-sign.htm) to external SD card and "install zip"
4. After #3, reboot and kernel should be "Philz Touch 4, CWM Base 6.0.3.0"
5. Apply latest Philz CWM.
Now we can enter Recovery mode and flash anything anytime.
That's my first reaction to flash Philz. But the device is not being recognized in Odin on my home PC. Downloaded the latest drivers but still no luck it's opening the storage etc when it is on, but the little blue light on the Com port in Odin is not showing....
I was thinking of waiting for next week's release and letting the auto update do its thing.
damn, i didn't red these last posts and installed BETA5. Could anyone discribe a way an giving some links, how i could get cwm back without going to the Stock? I tried it with the Rom manager app, but that did not fix the problem.
damn, i didn't red these last posts and installed BETA5. Could anyone discribe a way an giving some links, how i could get cwm back without going to the Stock? I tried it with the Rom manager app, but that did not fix the problem.
I could not assure you, but a companion who asked him the favor for weeks for those who can not install a full Rom by ODIN pc, if I could make a kernel to get them out of this problem, the question RoGod mention this in the message, since would be a test not reach to test it, since I did not need, and users that may have proven, they came to answer if they wanted the .tar to see if it was functional at least for the rapid departure of installation problem the Rom Stock for pc:
Here you have one but you must have kitkat 4.4 cyanogen, Omni, carbon or some that is based on cyanogen, if you want to try but for the contribution that gave the ODIN FAIL, this file also serves you BONE I ask you install this kernel and if you salt the public what great recovery as a contribution but do not forget me in the credits.
RoGod said:
Aqui tienes uno pero debes de tener kitkat 4.4 cyanogen,Omni,carbon o alguna que este basada en cyanogen,si quieres probar pero para el aporte que di del ODIN FAIL,este archivo tambien te sirve OSEA te pido instala este kernel y si te sal el recovery genial lo publicas como un aporte pero no te olvides de mi en los Creditos.
If you try it and starts smoothly, and have the kernel Kit-Kat with reinstalling Rom's Kit-Kat without going through ODIN pc edos cruzados: I hope you find it useful, and if it works first, Comment, because then at least another outlet for a bad version of the Rom's Kit-Kat. But remember correctly included wipe cache partition and wipe the dalvik cache configured.
And after installation you can try to install a kernel as Bauner, I am testing it on several Rom's, and luxury v1.2 will only have a mistake v1.2.1, which is the lack of mounting internal SD and that leaves mounted USB mode, there is the problem of being unable to use it properly, hehe. I personally use the OC 1500, in Pegasus, ROW, memory 256 KB, 240 DPI, wifi 20, delayed ringing 1000, I'll incredible, giving 21269 in AnTuTu 5.2.0 on the Resurrection Remix 5.1.5.
You can flash BETA5, you just have to flash a working recovery right after. I flashed the rom and raw kernel for cm11 (which contains a functioning cwm) and everything's working fine.
edos cruzados: I hope you find it useful, and if it works first, Comment, because then at least another outlet for a bad version of the Rom's Kit-Kat. But remember correctly included wipe cache partition and wipe the dalvik cache configured.
