[RECOVERY][P4NOTELTEVZW] CWM Recovery 6.0.4.4[10/18/2013] - Galaxy Note 10.1 Original Development

This is unofficial CWM for the P4NoteLTEVZW or i925
DISCLAIMER: I take no responsibility for bad things that occur as a result to flashing this.
PreReq: You must have a "jailbroken" bootloader in order to flash this. Thanks to AdamOutler for this!
NOTE: I am only posting a Heimdall version, if there is any interest in another version I (or somone else) can make one up
[10/18/13] Heimdall - http://www.androidfilehost.com/?fid=23156208500212209
Changes:
-Updated to 6.0.4.4
-Enabled swipe gestures
[10/11/13] Heimdall - http://www.androidfilehost.com/?fid=23159073880935569
Older:
Flashable zip: http://www.androidfilehost.com/?fid=23011596498370951
Odin: http://www.androidfilehost.com/?fid=23011596498370946
Flash in PDA!
Heimdall: http://www.androidfilehost.com/?fid=23011596498370945
Heimdall Command: heimdall flash --RECOVERY recovery.img

new recovery posted 6.0.4.3

Is this the touch version?
Never mind, just flashed it and it isn't. Still, nice to have a recovery that doesn't have the touch issues that plague TWRP.

Colchiro said:
Is this the touch version?
Never mind, just flashed it and it isn't. Still, nice to have a recovery that doesn't have the touch issues that plague TWRP.
Click to expand...
Click to collapse
Just posted new recovery that has the swipe gestures

Can't format data when wiping and couldn't see the internal storage. I've tried few times.
SGN10.1_GT-N8000. Last firmware (before i tried to install your CWM) was ARHD 9.0.
In the similar thread recovery couldn't mount "extSD".

Related

Issue Flashing Roms

So for some reason, I catch an error everytime I try to flash a rom to my phone. Then I am forced to restore my backup.
I have it rooted with CWM v5.5.0.4.
i747.
Not sure what other information you guys would need to assist. Would I need to re-root it? Different version of CWM?
Are you wiping data before you flash any new roms? That could be it..
Yep, always wipe data/factory.
.... i'm pretty sure that telling us what the error message says would help, too....
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
jethro650 said:
I'll take a wag and say since your recovery is 5.5.0.4 your probably getting a status 7 error which simply means you need to update your recovery to the newest version. Check in the dev section for the cwm recovery thread.
Click to expand...
Click to collapse
Agreed, almost undoubtedly...in every recovery flashable .zip there is an update-binary file which is the actual executable that is commanded by the update-script on what operations to perform. The newer versions of this binary are incompatible with older versions of the recoveries. This effect is not necessarily one way either, an older recovery trying to flash a new .zip or vice versa can produce this error but as a general rule using the newest recoveries should minimize this problem. The only time the reverse is a problem is when there is an update to the recovery api and there hasn't been an updated update-script built into a .zip. The easiest way to check is download the appropriate rom manager for your recovery, Clockwork Rom Manger for CWM or Goomanager for TWRP.

[Q] How do I flash CWM over TWRP? Rom manager not an option

Hi,
I have a Bell Galaxy S3 that has TWRP installed right now, but for some reason, only about 1/4 ROMS I try to flash on it lately, doesn't work. I would like to give CWM a try again, but I can't seem to find a way to flash it back. ROM manager doesn't give me the option and I can't find an up to date flashable TWRP or ODIN .tar file.
colhavoc said:
Hi,
I have a Bell Galaxy S3 that has TWRP installed right now, but for some reason, only about 1/4 ROMS I try to flash on it lately, doesn't work. I would like to give CWM a try again, but I can't seem to find a way to flash it back. ROM manager doesn't give me the option and I can't find an up to date flashable TWRP or ODIN .tar file.
Click to expand...
Click to collapse
i prefer non-touch. no bugs. cheers
Recovery flashable:
CWM 6.0.2.3 - http://d-h.st/8qP
CWM Touch 6.0.2.3 - http://d-h.st/qft
Odin flashable:
CWM 6.0.2.3 - https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
CWM Touch 6.0.2.3 - https://www.dropbox.com/s/uboh0ib8kwjyfrf/recovery-clockwork-touch-6.0.2.3-d2att.tar
xBeerdroiDx said:
i prefer non-touch. no bugs. cheers
Recovery flashable:
CWM 6.0.2.3 - http://d-h.st/8qP
CWM Touch 6.0.2.3 - http://d-h.st/qft
Odin flashable:
CWM 6.0.2.3 - https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
CWM Touch 6.0.2.3 - https://www.dropbox.com/s/uboh0ib8kwjyfrf/recovery-clockwork-touch-6.0.2.3-d2att.tar
Click to expand...
Click to collapse
Thankyou very much... but I have TWRP installed now... if i install CWM from recovery... what will happen to TWRP?
rao.avishek94 said:
Thankyou very much... but I have TWRP installed now... if i install CWM from recovery... what will happen to TWRP?
Click to expand...
Click to collapse
CWM will replace TWRP.
6.0.4.5 is the latest CWM and is needed to flash 4.4.2 ROMs.
audit13 said:
CWM will replace TWRP.
6.0.4.5 is the latest CWM and is needed to flash 4.4.2 ROMs.
Click to expand...
Click to collapse
Its great... Thankyou very much... am using it now:laugh:
audit13 said:
CWM will replace TWRP.
6.0.4.5 is the latest CWM and is needed to flash 4.4.2 ROMs.
Click to expand...
Click to collapse
I'm in a similar position with TWRP already installed but ROM manager gives me the option to flash CWM. If I use ROM manager will it still replace TWRP? I'm assuming it does, but I wanted to double check first.
PS I'm running an LG Optimius 4X HD, but a Google search for my question brought up this thread, which saves me starting my own.
creativeusernamea said:
I'm in a similar position with TWRP already installed but ROM manager gives me the option to flash CWM. If I use ROM manager will it still replace TWRP? I'm assuming it does, but I wanted to double check first.
PS I'm running an LG Optimius 4X HD, but a Google search for my question brought up this thread, which saves me starting my own.
Click to expand...
Click to collapse
I would not use Rom Manager. I would download a flashable zip made for your phone and flash it from TWRP. Alternatively, you could install it via adb/fastboot.
audit13 said:
I would not use Rom Manager. I would download a flashable zip made for your phone and flash it from TWRP. Alternatively, you could install it via adb/fastboot.
Click to expand...
Click to collapse
Thanks for the suggestion - is that done just by putting the zip onto the phone and using the "install" function in TWRP, just like flashing ROMs?
creativeusernamea said:
Thanks for the suggestion - is that done just by putting the zip onto the phone and using the "install" function in TWRP, just like flashing ROMs?
Click to expand...
Click to collapse
Yes. Personally, I used the latest release of Philz Touch which is based on CWM. There is a version that can be flashed via a custom recovery (TWRP or CWM) and a tar version that can be flashed in the PDA section of desktop Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
audit13 said:
Yes. Personally, I used the latest release of Philz Touch which is based on CWM. There is a version that can be flashed via a custom recovery (TWRP or CWM) and a tar version that can be flashed in the PDA section of desktop Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Click to expand...
Click to collapse
The official download off the CWM website is a .img - will that work or do I need to compress it to a .zip? Thanks for your help, especially given I don't really belong on your section of the forum!
creativeusernamea said:
The official download off the CWM website is a .img - will that work or do I need to compress it to a .zip? Thanks for your help, especially given I don't really belong on your section of the forum!
Click to expand...
Click to collapse
I believe you can flash the img via fastboot.

[Q] Recovery Install Methods (TWRP/CWM)

I'm wondering if there is a reference for recovery installation on the SGH-T989 (hercules). Specifically, I try to avoid tool kits, since they seem to be an additional layer beyond the basic (and relatively stable) technology already in place. I'm relatively familiar with ADB and ODIN, and it is not clear if Heimdall is terribly stable/compatible with our device. I love that TeamWin releases TWRP in tar file format for super easy and reliable ODIN installation. However, I'd like to have the ability to use CWM but haven't found a strong way to install the img file format they release. It would seem that, using TWRP installation directions, there is a method of using shell DD (/dev/block/mmcblk0p22), but that pushes my comfort zone and don't want to do it unless I understand it more.
Does anyone know where there is some reference to recommended install methods for CWM or TWRP?
Sorry if this is a redundant post - I welcome link references.
roperp said:
I'm wondering if there is a reference for recovery installation on the SGH-T989 (hercules). Specifically, I try to avoid tool kits, since they seem to be an additional layer beyond the basic (and relatively stable) technology already in place. I'm relatively familiar with ADB and ODIN, and it is not clear if Heimdall is terribly stable/compatible with our device. I love that TeamWin releases TWRP in tar file format for super easy and reliable ODIN installation. However, I'd like to have the ability to use CWM but haven't found a strong way to install the img file format they release. It would seem that, using TWRP installation directions, there is a method of using shell DD (/dev/block/mmcblk0p22), but that pushes my comfort zone and don't want to do it unless I understand it more.
Does anyone know where there is some reference to recommended install methods for CWM or TWRP?
Sorry if this is a redundant post - I welcome link references.
Click to expand...
Click to collapse
Just download goo manager to install twrp and ROM mananger for cwm.
Goo manager>menu botton>install open recovery script
ROM manager>flash cwm recovery>Hercules
There is also a recovery switcher apk, that allows you to go between cwm and twrp.
http://forum.xda-developers.com/showthread.php?p=38961881
[/QUOTE] There is also a recovery switcher apk, that allows you to go between cwm and twrp.
http://forum.xda-developers.com/showthread.php?p=38961881[/QUOTE]
Best option as far as I'm concerned and both recoveries are up to date!!!
Sent from my SGH-T989 using xda app-developers app

[Q] CWM Recover Fail... Help???

Ok... I'm a complete noob (saibot) when it comes to recoveries. I've been used to rooting for years but never wanted anything other than the stock rom/recovery until recently when I had to unbrick my phone after making a stupid error. Now, I want to gain acceptance into the CWM world and for some reason it isn't working.
What I've tried:
1) Downloading the recovery from the CWM official website. I downloaded the touch one.
2) Since the file was in img form (why?) I used a converter to change it into TarMD5
3) I tried flashing it with Odin 3.09
4) It showed a green "Reboot" where most have shown "Recovery" in the videos I watched before attempting.
5) And that's all it did was reboot instead of installing the custom recovery.
What did I do wrong? And why am I not as awesome as I think I am? Help! :crying:
ChampionLukeGabriel said:
Ok... I'm a complete noob (saibot) when it comes to recoveries. I've been used to rooting for years but never wanted anything other than the stock rom/recovery until recently when I had to unbrick my phone after making a stupid error. Now, I want to gain acceptance into the CWM world and for some reason it isn't working.
What I've tried:
1) Downloading the recovery from the CWM official website. I downloaded the touch one.
2) Since the file was in img form (why?) I used a converter to change it into TarMD5
3) I tried flashing it with Odin 3.09
4) It showed a green "Reboot" where most have shown "Recovery" in the videos I watched before attempting.
5) And that's all it did was reboot instead of installing the custom recovery.
What did I do wrong? And why am I not as awesome as I think I am? Help! :crying:
Click to expand...
Click to collapse
What you did wrong was using or trying to flash/use CWM recovery in the first place.
Here is the correct way to flash root and custom recovery:
Step #1
Download and Odin flash cf-autoroot: https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
Step #2
Download and Odin flash TWRP 2.7.2.0: https://dl.dropboxusercontent.com/u/45687485/TWRP_2720.tar
After doing the above you will no longer have any root or recovery issues.
For best results use Odin v1.85 which can be found here:
https://dl.dropboxusercontent.com/u/45687485/Odin85.zip
Good luck!
Thank you for your reply.... So, am I to understand that CWM will not work at all on my Note 3?
Before your reply, I tried out TWRP 2.8 and it was really laggy... Should I go and get 2.7.2 instead?
re: twrp/cwm
ChampionLukeGabriel said:
Thank you for your reply.... So, am I to understand that CWM will not work at all on my Note 3?
Before your reply, I tried out TWRP 2.8 and it was really laggy... Should I go and get 2.7.2 instead?
Click to expand...
Click to collapse
Lot's of people have been having issues with cwm recovery ever since
the NF1 official Samsung N900T firmware was released.
TWRP 2.7.2.0 works perfectly on all N900T Note 3 roms.
The download link I posted is specifically made for the
Note 3 N900T, not all versions of twrp work properly with
all phones and or all models.
Good luck!

[Q]E988 Boot certification verify

I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
hotmatua.parulian said:
I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
Click to expand...
Click to collapse
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
ShadySquirrel said:
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
Click to expand...
Click to collapse
Thank you very much Shady.. Please be kindly to review steps that i should execute when flashing to Carbon Lollipop with regards to my current state (rooted 4.4.2. stock Kitkat):
Prerequisite:
- LG Flash Tool 2014 installed in PC
- LG United Mobile Driver (i use v3.11.3) installed in PC
- Stock firmware E98810e_00.kdz (Indonesia Jellybean) -- Jellybean stock base is required to cater modem/wakelock issue
- Stock firmware E98820c_00.kdz (Indonesia Kitkat)
- ROM Manager (for current state backup/restore)
- Freegee (to cater LG security issue after success flash)
- Towelroot (to root device after success flash)
- TWRP (for recovery tool after success flash)
- Downloaded ZeKrnl 1.7 Build 11/28 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975
- Downloaded ZeKrnl 1.6 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page4 (to cater camera issue after flashed to Carbon)
1. Flash CWM via ROM Manager
2 Execute Backup Current ROM to sd card via ROM Manager and save copy to PC
3. Backup manual for files, apks, contacts to sd card and save copy to PC
4. Copy ZeKrnl 1.7 zip & ZeKrnl 1.6 zip to sd card
5. Turn off phone, plug usb cable to phone
6. Press & hold Volume keys (Up + Down) then plug the other end of usb into PC to until download mode showned
7. Run LG Flash Tool with administrator privilege
8. Flash E98810e firmware into the device till success
(After Success Flash to Andro 4.1.2 JB):
9. Install towelroot and root the device
10. Install freegee to cater LG security issue
11. Install latest TWRP
12. Reboot into recovery mode
13. wipe system, data, cache, dalvik cache
14. flash ZeKrnl 1.7
--Camera issue
debug.composition. type=dyn --> debug.composition. type=gpu using build prop editor and/or flash ZeKrnl 1.6 kernell
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page8
--Deep Sleep issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page10
-- SD Card issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page12
-- Kernel parameter tuning sampel
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page14
Btw looks like you are the only person that still active in this thread...really appreciate it...thank you very much
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
So you are saying i just flash the rom as is without any further change?Noted shady...i will inform you the result
ShadySquirrel said:
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
Click to expand...
Click to collapse
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
hotmatua.parulian said:
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
Click to expand...
Click to collapse
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
ShadySquirrel said:
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
Click to expand...
Click to collapse
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
hotmatua.parulian said:
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
Click to expand...
Click to collapse
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
g0at1 said:
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
Click to expand...
Click to collapse
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Quiet interesting this device...salut to programmers of this device...
hotmatua.parulian said:
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Click to expand...
Click to collapse
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
hotmatua.parulian said:
Quiet interesting this device...salut to programmers of this device...
Click to expand...
Click to collapse
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
ShadySquirrel said:
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
Click to expand...
Click to collapse
:good::good::good::good: salut to you...the true programmer..never quit..yes im agree with you...i had played with nexus 1,2,3 before but never found something like this...
OK then, i will try g0at1 suggestion, hopefully it works... Like you said its only JB, root, freegee, newer twrp, backup, flash custom
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
hotmatua.parulian said:
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
Click to expand...
Click to collapse
You forgot to wipe system, data and caches.
ShadySquirrel said:
You forgot to wipe system, data and caches.
Click to expand...
Click to collapse
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
hotmatua.parulian said:
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
Click to expand...
Click to collapse
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
g0at1 said:
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
Click to expand...
Click to collapse
Finally carbon installed successfully after I repeat the step very carefully including your reminder bout wiping...
Thank you very much, I will consult any bugs I found..
Half Day 1 issue:
- Scrambled screen layout each time booting
- Camera unstable/crash, also with apps camera mx and open camera
- i think batt is draining faster than kitkat stock
- i feel internet via wifi is slower than kitkat stock
- phone call, other person cant hear my voice
Just flashed SlimLP..Gosh its so slim and smooth...thank you very much...there issue bout the camera and scrambled screen each time I reboot the system, which camera apps I should use?

Categories

Resources