Related
First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL. (There's another link in the forum to do this, I can't find it at the moment)
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Galaxy S i9000 as your phone.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!
If you can't seem to get ROM Manager off the market, you can get it from my homepage:
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Just installed! Working great!
Installed with ROM manager. Works like a charm! Thanx alot Koush!
works fine
works like a charm
Installed, everything working without problems.
To install roms with clockwork we need roms in *.zip format? Where to get them?
Sent from my GT-I9000 using Tapatalk
Just got my phone
will try it after charging ]
YOU ARE THE MAN
thank you and thanks all Xda devs and members
hmm ... I know this might sound stupid but, acually GSG is my first android phone, though I know how to flash roms with odin and how to apply update.zip and all that but what is the difference between this and ClockworkMod Recovery ?? and does it use the same components as odin ? (I mean CODE, CSC, MODEM and Pit) ?
Stickied. Closing the other one. Not sure why you would start a new thread instead of modifying the old one though...
Thanks Koush your the man. Coming from a htc magic I hate this odin bull
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
EDIT: After rebooting my phone and trying to open ROM Manager again, I have some sort of "Recovery Failure" screen with 3 options:
- Recovery mode is broken.
- ROM Manager doesn't reboot.
- Other.
?
Arkymedes said:
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
Click to expand...
Click to collapse
Do you already have an update.zip on your internal sdcard? If yes, rename it, and then should boot just fine!
kalpik said:
Do you already have an update.zip on your internal sdcard? If yes, rename it, and then should boot just fine!
Click to expand...
Click to collapse
Ahhh... I guess I'm not very used to this "Internal SD Card" thing... there was the update.zip I used to root the phone there and I only checked my regular External SD.
Everything is fine now, sorry for bothering.
Arkymedes said:
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
EDIT: After rebooting my phone and trying to open ROM Manager again, I have some sort of "Recovery Failure" screen with 3 options:
- Recovery mode is broken.
- ROM Manager doesn't reboot.
- Other.
?
Click to expand...
Click to collapse
I had the same issue. Must have been the update.zip, but I didnt remove it, just pressed the other option, went into manual recovery mode, rebooted went into rom manager and backed up my files. Worked a charm
Does this mean there will be no more work on a permanent recovery solution?
I have the Korean version M110S - and it does not have the standard recovery (it is crippled - no apply:update.zip). Is there and abd command to "apply update.zip" ?
May I ask if this work for me using mimocan ext4 fix on the backup/restore?
This may sound stupid, but I'm kinda new to Android modding (SGS is my first droid, moving here from WiMo on SE-X1) and.... What is Clockwork?
So if I ever needed to send this phone in for warranty purposes, I could just flash the backup of my stock ROM in and I should be good to go?
does this method works for captivate and vibrant???
edit: just install/ captivate and vibrant option available.
Rithina said:
May I ask if this work for me using mimocan ext4 fix on the backup/restore?
Click to expand...
Click to collapse
Worked for me with mimocan ext4 fix
Hi all! I recently switched to TWRP recovery since everyone says its better, So I installed it through the Goo manager app. I was then wondering, "what's gonna happen to my CWM recovery?" Whenever I hit reboot to recovery on my power menu options, it takes me to TWRP, which is what i want, but should I take away CWM recovery just to be safe? or is it already gone?
AND I still have a couple of nandroid backups with CWM, so is there anyway to restore them via TWRP?
Thanks! :laugh:
Nabeel10 said:
Hi all! I recently switched to TWRP recovery since everyone says its better, So I installed it through the Goo manager app. I was then wondering, "what's gonna happen to my CWM recovery?" Whenever I hit reboot to recovery on my power menu options, it takes me to TWRP, which is what i want, but should I take away CWM recovery just to be safe? or is it already gone?
AND I still have a couple of nandroid backups with CWM, so is there anyway to restore them via TWRP?
Thanks! :laugh:
Click to expand...
Click to collapse
There is only one recovery on the phone at any given time, and its installed to some block on the phone which is automatically loaded by the phone by the hardware keys "UP VOL+HOME+POW." So yes, CWM is gone entirely (already) since TWRP was installed. As for the restoring CMW backups with TWRP, I have no idea (since I installed TWRP the day I got my phone).
A suggestion though is to download both the rommanager app and the goomanager app and switch between the two recoveries whenever to restore without doubting whether or not it will work. (you can also do this with busybox + the two images you can find here: "h t t p ://te amw. i n/p roje ct/twr p2/1 06" and "ht t p:/ /w ww. cl ockw ork mod. co m/ ro mm an ag er" no spaces (xda doesnt allow me to post links below 10 posts). the twrp page also has the command for installing either of the two recoveries, yes they both work the same, both .img)
I installed the KK ROM wit the TOT method and then rooted the phone and installed the CWM recovery as an apk. Now when I go into SU, it says I am not rooted. I tried 2 methods to root but unsuccessful. It boots into CWM recovery and then nothing. Do I need to reinstall the OS with the TOT method again? Any ideas?
HD2FORNICK said:
I installed the KK ROM wit the TOT method and then rooted the phone and installed the CWM recovery as an apk. Now when I go into SU, it says I am not rooted. I tried 2 methods to root but unsuccessful. It boots into CWM recovery and then nothing. Do I need to reinstall the OS with the TOT method again? Any ideas?
Click to expand...
Click to collapse
This method works perfectly: http://forum.xda-developers.com/showpost.php?p=51480568&postcount=1
After root, use this to get the correct recovery: http://forum.xda-developers.com/showpost.php?p=52945705&postcount=1
Once the phone boots into the UI, use Freegee to install the latest recovery.
jdk2 said:
This method works perfectly: http://forum.xda-developers.com/showpost.php?p=51480568&postcount=1
After root, use this to get the correct recovery: http://forum.xda-developers.com/showpost.php?p=52945705&postcount=1
Once the phone boots into the UI, use Freegee to install the latest recovery.
Click to expand...
Click to collapse
Tries and doesn't work. It goes back to my CWM recovery and does nothing. Thanks.
HD2FORNICK said:
Tries and doesn't work. It goes back to my CWM recovery and does nothing. Thanks.
Click to expand...
Click to collapse
flash the hacked twrp. that gets me out of cwm bootloop.
Same problem here phone was rooted and then installed CWM and for some reason lost root. Its not a CWM bootloop.
When the root step requires "Apply Update from ADB" I cannot because CWM doesn't have that option.
mk3 said:
Same problem here phone was rooted and then installed CWM and for some reason lost root. Its not a CWM bootloop.
When the root step requires "Apply Update from ADB" I cannot because CWM doesn't have that option.
Click to expand...
Click to collapse
I got bad news bro. I had to re TOT the phone and start from scratch. There is a CWM 6.0.4.4 floating around causing this issue. The phone loses root but it constantly boots into CWM when trying to root.
ROOT achieved, now need recovery!
OK, so I had to re TOT and get the phone back to factory state with 4.4. Then I was able to root successfully and now I am wondering how and which recovery to use. Could someone please post a link to Philz recovery and can I flash it with the same root toll with ADB sideload? THanks.
Ok I figured out how to get root back on my phone! Yay!
Run the same F240 root tool as usual, it will reboot phone into CWM recovery but you can't choose "apply update from ADB" so instead pick INSTALL ZIP, then choose INSTALL ZIP FROM SIDELOAD. Press any key on computer to load root files then at next step in CWM choose GO BACK, then choose REBOOT SYSTEM NOW. At next step in CWM will ask "Rom may flash stock recovery on boot. F1 This can not be undone." here I choose NO. Phone will reboot and root is restored. I think before I was scared and chose YES on this step and that's what lost my root.
Root Check Basic and SuperSU both show I am rooted and back to okay.
:good:
mk3 said:
Ok I figured out how to get root back on my phone! Yay!
Run the same F240 root tool as usual, it will reboot phone into CWM recovery but you can't choose "apply update from ADB" so instead pick INSTALL ZIP, then choose INSTALL ZIP FROM SIDELOAD. Press any key on computer to load root files then at next step in CWM choose GO BACK, then choose REBOOT SYSTEM NOW. At next step in CWM will ask "Rom may flash stock recovery on boot. F1 This can not be undone." here I choose NO. Phone will reboot and root is restored. I think before I was scared and chose YES on this step and that's what lost my root.
Root Check Basic and SuperSU both show I am rooted and back to okay.
:good:
Click to expand...
Click to collapse
Ok so i need a custom recovery such one did you use. I need one that can read the external card.
HD2FORNICK said:
Ok so i need a custom recovery such one did you use. I need one that can read the external card.
Click to expand...
Click to collapse
I used that CWM 6.0.4.4 recovery to install a custom recovery only. Once it flashes the recovery, reboot the phone. Answer No to the disclaimer in recovery and let the phone boot into kitkat. Then I used Freegee to install it's latest version of CWM. Ignore the warning if you get one in Freegee. It will install the newer recovery.
jdk2 said:
I used that CWM 6.0.4.4 recovery to install a custom recovery only. Once it flashes the recovery, reboot the phone. Answer No to the disclaimer in recovery and let the phone boot into kitkat. Then I used Freegee to install it's latest version of CWM. Ignore the warning if you get one in Freegee. It will install the newer recovery.
Click to expand...
Click to collapse
The last time I did that and installed the CWM 6.0.4.4 I lost root and freegee couldn't install another recovery but I'll give it a shot again.
HD2FORNICK said:
The last time I did that and installed the CWM 6.0.4.4 I lost root and freegee couldn't install another recovery but I'll give it a shot again.
Click to expand...
Click to collapse
You'll loose root if you answer "Yes" to the disclaimer CWM throws when you try to reboot. Just answer "No" and you won't loose root.
jdk2 said:
You'll loose root if you answer "Yes" to the disclaimer CWM throws when you try to reboot. Just answer "No" and you won't loose root.
Click to expand...
Click to collapse
Thanks bro. Worked!
jdk2 said:
I used that CWM 6.0.4.4 recovery to install a custom recovery only. Once it flashes the recovery, reboot the phone. Answer No to the disclaimer in recovery and let the phone boot into kitkat. Then I used Freegee to install it's latest version of CWM. Ignore the warning if you get one in Freegee. It will install the newer recovery.
Click to expand...
Click to collapse
Can you please share the custom recovery that you flashed from 6.0.4.4 ?
Sent from my LG-E988 using Tapatalk
Akhileshjj said:
Can you please share the custom recovery that you flashed from 6.0.4.4 ?
Sent from my LG-E988 using Tapatalk
Click to expand...
Click to collapse
It was CWM 6.0.4.7 and included with Freegee.
jdk2 said:
It was CWM 6.0.4.7 and included with Freegee.
Click to expand...
Click to collapse
Can you be bit more specific on how did you download the 6.0.4.7 from freegee. As i see only install option available only in freegee but not download so that it can be installed from 6.0.4.4..
Sent from my LG-E988 using Tapatalk
Akhileshjj said:
Can you be bit more specific on how did you download the 6.0.4.7 from freegee. As i see only install option available only in freegee but not download so that it can be installed from 6.0.4.4..
Sent from my LG-E988 using Tapatalk
Click to expand...
Click to collapse
When I opened Freegee, it presented the option to install 6.0.4.7. It wasn't a stand alone version but part of Freegee.
mk3 said:
Ok I figured out how to get root back on my phone! Yay!
Run the same F240 root tool as usual, it will reboot phone into CWM recovery but you can't choose "apply update from ADB" so instead pick INSTALL ZIP, then choose INSTALL ZIP FROM SIDELOAD. Press any key on computer to load root files then at next step in CWM choose GO BACK, then choose REBOOT SYSTEM NOW. At next step in CWM will ask "Rom may flash stock recovery on boot. F1 This can not be undone." here I choose NO. Phone will reboot and root is restored. I think before I was scared and chose YES on this step and that's what lost my root.
Root Check Basic and SuperSU both show I am rooted and back to okay.
:good:
Click to expand...
Click to collapse
Thanks its works
hey, im new to Android, after moving on from my Iphone 4 to my the new M9, i start wondering.
i got my phone unlock booter threw the devHTC,
got it S-ff with the great app (that i forgot the name) which i payed for it.
installed SuperSu update to give roots privilages, and also BusyBox Free.
thoese are my problems:
1. installed SB game hacker, and its says after i gave it root privilages that i dont gave it, or i dont have root acces.
the thing is that with GameKiller i do get root access...
2. trying to apply patch with the Lucky Patcher sometimes i get root unstable window error that asked me to update my
SuperSu even thew its update to last vesrion.
3. again with Lucky patcher (which does get root privilages for sometimes) - i try to install threw the toolBox -> patch to android -> Signature Verificcation Status Always True , and after it reboot i go back to it and it says its not patched. like the patch failed.
i tryed to clear the core.jar and the service.jar but it doesn't help, it doesn't patch it.
4. i got the new System Update 1.36.709.3 and when i press Install now, it enter the teemmod (the developer mode which i can wipe, install and everything) and does nothing. after reboot to system it ask me again if i want to install, and again go to this dev mode (which is needed for installing supersu to the system).
5. same as befor, apps like clean master doesn't get superuser privilages and cannot disable auto start apps even thew superSu do allow it. also, CPU manager in Battery Life app always get off after a while, or after a reboot.
i hope i could get help cuz im really lost in finding a way to fix all of this.
Please help?
Hello,
You need to fix your root situation.
- Open supersu, and do a complete uninstall.
- Download the latest super su flashable from chainfires website (Google it)
- flash it in recovery mode
- boot and install supersu free from play store
- report back here
Also, if you flashed a custom recovery you cannot OTA update the stock Android, that update requires stock recovery to install.
TwinAdk said:
Hello,
You need to fix your root situation.
- Open supersu, and do a complete uninstall.
- Download the latest super su flashable from chainfires website (Google it)
- flash it in recovery mode
- boot and install supersu free from play store
- report back here
Also, if you flashed a custom recovery you cannot OTA update the stock Android, that update requires stock recovery to install.
Click to expand...
Click to collapse
OK, by flash u mean to go to recovery mode and install the su u told me right?
waltobc6 said:
OK, by flash u mean to go to recovery mode and install the su u told me right?
Click to expand...
Click to collapse
Basic terminology:
- Recovery / recovery mode: Instead of booting into the Android OS, you can boot into the "recovery OS" (located on a partition of the phone storage, just like the android OS is located on its own partition). The OS used for the recovery partition can be either stock or custom - popular custom choices are TWRP (TeamWin Recovery Project) or CWM (Clockwork Mod) - TWRP is the best choice for the M9 - http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
- To flash something: To install something (always a zip-file, never apk files) while the phone is in recovery mode
TL;DR: Yes. :good:
Kind Regards
TwinAdk
TwinAdk said:
Hello,
You need to fix your root situation.
- Open supersu, and do a complete uninstall.
- Download the latest super su flashable from chainfires website (Google it)
- flash it in recovery mode
- boot and install supersu free from play store
- report back here
Also, if you flashed a custom recovery you cannot OTA update the stock Android, that update requires stock recovery to install.
Click to expand...
Click to collapse
TwinAdk said:
Basic terminology:
- Recovery / recovery mode: Instead of booting into the Android OS, you can boot into the "recovery OS" (located on a partition of the phone storage, just like the android OS is located on its own partition). The OS used for the recovery partition can be either stock or custom - popular custom choices are TWRP (TeamWin Recovery Project) or CWM (Clockwork Mod) - TWRP is the best choice for the M9 - http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
- To flash something: To install something (always a zip-file, never apk files) while the phone is in recovery mode
TL;DR: Yes. :good:
Kind Regards
TwinAdk
Click to expand...
Click to collapse
Okay I got 3 options - reinstall which is not what I need
And 2 more which are cleanup for switching userroot app
And a full cleanup for preparing uproot.
Which one should I pick.
Also I used last time Supersu 2.49, and now from the site is gave me I downloaded 2.46
I understand 2.49 is beta - so which one to pick?
2.49. Place it on the SD card of the phone before unroot. Choose complete unroot in the su app.
TwinAdk said:
2.49. Place it on the SD card of the phone before unroot. Choose complete unroot in the su app.
Click to expand...
Click to collapse
Not having SD - and install it from the internal storage of the phone can **** it up?
I press. Uninstall and it get stuck on it. I let it run for more then 40 min
And it didn't finish
Complete unroot just got the phone stuck?? If so, please walk me through the life of your phone from unboxing, eg what have you done with the device in terms of unlocking it, flashing stuff etc. Also, what carrier and soff status...
TwinAdk said:
Complete unroot just got the phone stuck?? If so, please walk me through the life of your phone from unboxing, eg what have you done with the device in terms of unlocking it, flashing stuff etc. Also, what carrier and soff status...
Click to expand...
Click to collapse
I mean got stuck on the please wait- I was able to switch app.
Also after trying few time to uninstall it - it worked.
I flashed the super 2.49 opened google store and unlocked the app.
The CPU manager in doctor battery still turn off after a while.
Also auto start app disable in clean master still says it don't have room access even
I have it again.
And I tried to install in lucky patcher the signal true - and after long "please wait"
And a auto robot it says it not patched.
What to do ?
Do you see a prompt to allow root access to the apps asking for it?
Can you post a screenshot of the Super su app with allowed and disallowed applications listed?
Are you on stock ROM with custom recovery?
TwinAdk said:
Do you see a prompt to allow root access to the apps asking for it?
Can you post a screenshot of the Super su app with allowed and disallowed applications listed?
Are you on stock ROM with custom recovery?
Click to expand...
Click to collapse
I do get the approve window, also it shows the permission granted
In the super all allowed listed.
I didn't change any stock rom. I'm on the default of HTC m9 system.
And I'm still-off, and unlocked
That is really wired... Either we are missing something obvious, or your system is really messed up..
TwinAdk said:
That is really wired... Either we are missing something obvious, or your system is really messed up..
Click to expand...
Click to collapse
How can I do a full reset, cuz factor reset still leave the Supersu broke
Look in the forum for it
TwinAdk said:
Look in the forum for it
Click to expand...
Click to collapse
Please oh: I'm into it for like week without any good sucsses
Guide , help please?
Find your device/carrier RUU and start over, if you went through all the steps to get s off, you should have made a back up that you could start over with in recovery. If not search for for the RUU or original system file in the m9 forum For your SPECIFIC device.
---------- Post added at 07:52 AM ---------- Previous post was at 07:45 AM ----------
waltobc6 said:
How can I do a full reset, cuz factor reset still leave the Supersu broke
Click to expand...
Click to collapse
Try entering ##786# on your dialer key paid
I bought my phone in Bolivia, and at the box it had Chinese so I think it's a new movie9 from Asia. How can I check my SPECIFIC so I can download what's needed
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?