Related
Hi,
I installed Samsung Galaxy Nexus Toolkit V9.1.0 for GSM to root my device and use Team Win Recovery Project V2.2.2.0 to install ROMs.
Currently on Official nightly build of Cyanogen Mod 10 Rom Android 4.1.2 Build JZO54K.
I want to know if I need to update anything to switch to Android 4.2 ROM or should I just download a good rom and flash it using the software?
While we are on the subject, can someone please recommend a good ROM? When will start getting Cyanogen Mod for Android 4.2?
Thanks.
You should update your recovery to the latest version (either CWM ot TWRP) to avoid nested "0" folders each time you flash a new rom.
Other than that, I didn't do anything else.
By the way, I'm using Cataclysm rom.
abulkhairi said:
Hi,
I installed Samsung Galaxy Nexus Toolkit V9.1.0 for GSM to root my device and use Team Win Recovery Project V2.2.2.0 to install ROMs.
Currently on Official nightly build of Cyanogen Mod 10 Rom Android 4.1.2 Build JZO54K.
I want to know if I need to update anything to switch to Android 4.2 ROM or should I just download a good rom and flash it using the software?
While we are on the subject, can someone please recommend a good ROM? When will start getting Cyanogen Mod for Android 4.2?
Thanks.
Click to expand...
Click to collapse
Just update your TWRP to the latest version 2.3.2.1. You can easily do that via GooManager app which you can find in the Play Store
There is no specific "good" ROM, just try then decide
Good Luck
ahmadallica said:
Just update your TWRP to the latest version 2.3.2.1. You can easily do that via GooManager app which you can find in the Play Store
There is no specific "good" ROM, just try then decide
Good Luck
Click to expand...
Click to collapse
like others have said use the latest twrp... and "best" rom is different for everyone so try them and see for yourself.. and cm10.1 is already out
ahmadallica said:
Just update your TWRP to the latest version 2.3.2.1. You can easily do that via GooManager app which you can find in the Play Store
There is no specific "good" ROM, just try then decide
Good Luck
Click to expand...
Click to collapse
Hi,
I have GooManager installed.... When I search for TWRP 2.3.2.1 I get 2.3.2.3 version shown as available as well. It's a zip and .img file as well. Am I supposed to just download and flash it? I mean the zip file would be flashed using the current TWRP right and it will auto upgrade?
Also, What I understand is that if I have 2.3.2.1 I can install 4.2 ROMs without having to root my phone using Galaxy Nexus Toolkit V10.1 because the screenshots shows 4.2 in it?
Also to find something I have to use search place on GooManager, isnt there a list of updated list of softwares available on it? I can see ROMs etc very neatly can be seen there but not patches like these.
abulkhairi said:
Hi,
I have GooManager installed.... When I search for TWRP 2.3.2.1 I get 2.3.2.3 version shown as available as well. It's a zip and .img file as well. Am I supposed to just download and flash it? I mean the zip file would be flashed using the current TWRP right and it will auto upgrade?
Also, What I understand is that if I have 2.3.2.1 I can install 4.2 ROMs without having to root my phone using Galaxy Nexus Toolkit V10.1 because the screenshots shows 4.2 in it?
Also to find something I have to use search place on GooManager, isnt there a list of updated list of softwares available on it? I can see ROMs etc very neatly can be seen there but not patches like these.
Click to expand...
Click to collapse
Please be careful with the TWRP version as 2.3.2.3 seems to be for Nexus 4 not our GNex. Follow the following steps to download and install latest TWRP for your device (2.3.2.1):
1- Run GooManager app
2- Click on the upper right 3 dots for settings
3- Click "Install OpenRecoveryScript"
4- Confirm Recovery Install --> Yes
5- Confirm download, reboot, and install --> Yes
6- A download process will start then it will be installed
7- (Optional) Reboot into recovery to ensure that TWRP is successfully installed and working.
As far as I know, you need root for GooManager app already for many functions. I never used the GNex toolkit nor have an idea which screenshots you are referring to.
I am not sure I got your last point but if you are searching for ROMs via GooManager then it is there in the first option of the app --> Browse compatible ROMs. But honestly I have never used this so can't share you any experience regarding it.
Hope this helps
RESOLVED SEE POST #6
Hey guys,
I am having trouble flashing a custom recovery (TWRP) to be specific on my brothers Note 2. I was able to easily do it with my phone but I didnt update OTA to the latest ATT software.
I have the latest samsung drivers installed too.
So in general.
1. My brother updated OTA
2. I use odin to try to flash TWRP via PDA
3. It says success but when I reboot into recovery it goes into the stock android recovery instead of the custom one
4. ??? perplexed
is your [brothers] phone rooted? (you didn't mention that in the post). if it is, the easiest way to install TWRP is to download GooManager from the Play Store and, once installed, choose Menu->Install OpenRecoveryScript.
cortez.i said:
is your [brothers] phone rooted? (you didn't mention that in the post). if it is, the easiest way to install TWRP is to download GooManager from the Play Store and, once installed, choose Menu->Install OpenRecoveryScript.
Click to expand...
Click to collapse
He is not rooted. He is stock from AT&T but he said he did an OTA update a week or two ago.
I actually tried the GooManager to install TWRP but it said it installed twrp but it goes into stock android recovery
I'm not sure if this helps or not but when I load into stock android recovery it keeps "manually loading CSC"
mc704 said:
He is not rooted. He is stock from AT&T but he said he did an OTA update a week or two ago.
I actually tried the GooManager to install TWRP but it said it installed twrp but it goes into stock android recovery
I'm not sure if this helps or not but when I load into stock android recovery it keeps "manually loading CSC"
Click to expand...
Click to collapse
so i take it [your] phone is rooted, because you have a custom recovery installed. my understanding is that the device must be rooted before you can install a custom recovery. that's why installing TWRP via GooManager didn't work.
cortez.i said:
so i take it [your] phone is rooted, because you have a custom recovery installed. my understanding is that the device must be rooted before you can install a custom recovery. that's why installing TWRP via GooManager didn't work.
Click to expand...
Click to collapse
what about ODIN doesn't it root the phone when you flash a custom recovery?
on my phone all I had to do was flash via twrp via odin and it did everything for me...
this isn't the case for my brother's phone so im a little confused
mc704 said:
what about ODIN doesn't it root the phone when you flash a custom recovery?
Click to expand...
Click to collapse
ODIN doesn't root your phone. it's the package/file that you flash with ODIN that roots your device. you didn't mention the method you used to root your phone.
mc704 said:
on my phone all I had to do was flash via twrp via odin and it did everything for me...
this isn't the case for my brother's phone so im a little confused
Click to expand...
Click to collapse
flash what via TWRP? you need to reference the methods you used to flash your device, e.g., link to post. it's difficult to help without having more info. in my case i used the CF Root method which does root your phone by using ODIN to flash a package that installs SuperSU binary and APK (app that provides root) and a Stock recovery. This took less than 30 seconds. afterwards, i added my GMail account to my device, installed GooManager from the PlayStore and then used GooManager to install TWRP. hope this is helpful.
cortez.i said:
ODIN doesn't root your phone. it's the package/file that you flash with ODIN that roots your device. you didn't mention the method you used to root your phone.
flash what via TWRP? you need to reference the methods you used to flash your device, e.g., link to post. it's difficult to help without having more info. in my case i used the CF Root method which does root your phone by using ODIN to flash a package that installs SuperSU binary and APK (app that provides root) and a Stock recovery. This took less than 30 seconds. afterwards, i added my GMail account to my device, installed GooManager from the PlayStore and then used GooManager to install TWRP. hope this is helpful.
Click to expand...
Click to collapse
I see. Sorry for not being specific
When I worked on my phone. I installed the latest samsung drivers on the main website, used Odin 3.07, flashed TWRP 2.3 by PDA, and it was rooted and the custom recovery worked awesome (I did it similar to this http://www.youtube.com/watch?v=NFHZ535L7is)
However this process does not work with my brothers note 2. Which is why im confused.... I assuming TWRP auto rooted for my phone but it didn't for my brother's phone?
I will definitely give your method a try and post back. Thanks for putting up with a newbie like me! :laugh:
mc704 said:
I see. Sorry for not being specific
When I worked on my phone. I installed the latest samsung drivers on the main website, used Odin 3.07, flashed TWRP 2.3 by PDA, and it was rooted and the custom recovery worked awesome (I did it similar to this http://www.youtube.com/watch?v=NFHZ535L7is)
However this process does not work with my brothers note 2. Which is why im confused.... I assuming TWRP auto rooted for my phone but it didn't for my brother's phone?
I will definitely give your method a try and post back. Thanks for putting up with a newbie like me! :laugh:
Click to expand...
Click to collapse
no worries... i'd hate to see you fubar your brothers phone, lol. anyway, the method used in that video appears to be created by ChainFire for the N7100, which is the international version of the Note 2. the method i referenced - also developed by ChainFire - is specific to the AT&T and Canadian versions of the Note 2. if there's one thing I've learned in my years on xda, it's to make sure that you play with stuff that's compatible with your device. several of today's devices go by the same consumer friendly name (e.g.,Galaxy S 3, Note 2) but have different internals (e.g., chips). if you flash an incompatible ROM, you could end up with a nice paperweight. hope you and your brother enjoy your phones.
cortez.i said:
no worries... i'd hate to see you fubar your brothers phone, lol. anyway, the method used in that video appears to be created by ChainFire for the N7100, which is the international version of the Note 2. the method i referenced - also developed by ChainFire - is specific to the AT&T and Canadian versions of the Note 2. if there's one thing I've learned in my years on xda, it's to make sure that you play with stuff that's compatible with your device. several of today's devices go by the same consumer friendly name (e.g.,Galaxy S 3, Note 2) but have different internals (e.g., chips). if you flash an incompatible ROM, you could end up with a nice paperweight. hope you and your brother enjoy your phones.
Click to expand...
Click to collapse
just a quick update.
I flashed CF-autoroot, TWRP, and a custom rom! Everything works great!
Thanks for the help!
Hey everyone, Im new here, just got the Nexus 7 2013 Asus.
I updated to Kit Kat right away, I tried using that root toolkit thing or whatever... it got my tablet unlocked but it would stay stuck on a message that it was trying to boot some .img file when I clicked root...
Long story short, I restored 2 times and I guess that doesnt work with Kit Kat yet... and I relocked my tablet. Anyway know how I can correctly unlock and root my new Nexus 7 on Kit Kat?
After an unlock you can manually flash the recovery IMG then just flash the super su zip for root.
Adb fastboot recoveryimage.IMG
Then the super su zip can be flashed once in a custom recovery.
If needed I can do a team viewer with you and get you all set up.
prshosting.org
ta_help said:
Hey everyone, Im new here, just got the Nexus 7 2013 Asus.
I updated to Kit Kat right away, I tried using that root toolkit thing or whatever... it got my tablet unlocked but it would stay stuck on a message that it was trying to boot some .img file when I clicked root...
Long story short, I restored 2 times and I guess that doesnt work with Kit Kat yet... and I relocked my tablet. Anyway know how I can correctly unlock and root my new Nexus 7 on Kit Kat?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2536420
Make sure you download the correct custom recovery for your device (prerequisite 3).
Sent from my Nexus 6 using Tapatalk 4
Unlocked & Rooted N7 on 4.3.1 will it stay so after update to 4.4 ?
prsterero said:
After an unlock you can manually flash the recovery IMG then just flash the super su zip for root.
Adb fastboot recoveryimage.IMG
Then the super su zip can be flashed once in a custom recovery.
If needed I can do a team viewer with you and get you all set up.
prshosting.org
Click to expand...
Click to collapse
Dear Experts,
I'm still new at this game, so bear with me please.
I have a LTE N7 on 4.3.1 (JLS361) that is unlocked & rooted.
Now I get tho OTA Update to 4.4 (KRT16S) downloaded & ready to install.
Aside from all those bad things that don't work anymore in 4.4 (eg. FLASH), what will happen ?
Will my N7 revert to a locked & unrooted device ? or will it stay unlocked & rooted ?
Or will it stay unlocked, but unrooted, and I only need to flash the SuperSU ZIP again ?
Thanks for enlightening me.
JMF
fiechterjm said:
Dear Experts,
I'm still new at this game, so bear with me please.
I have a LTE N7 on 4.3.1 (JLS361) that is unlocked & rooted.
Now I get tho OTA Update to 4.4 (KRT16S) downloaded & ready to install.
Aside from all those bad things that don't work anymore in 4.4 (eg. FLASH), what will happen ?
Will my N7 revert to a locked & unrooted device ? or will it stay unlocked & rooted ?
Or will it stay unlocked, but unrooted, and I only need to flash the SuperSU ZIP again ?
Thanks for enlightening me.
JMF
Click to expand...
Click to collapse
It will stay unlocked, but unrooted, and you only need to flash the supersu zip again.
Sent from my Nexus 6 using Tapatalk 4
xdhall said:
It will stay unlocked, but unrooted, and you only need to flash the supersu zip again.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Mine is also unlocked and rooted and want to upgrade to KK.
When you said flash, you meant I had to install TWRP first then flash SU again?
I am curious because when I first rooted my N7, I used the Nexus 7 Toolkit and did not install TWRP. Can't I just use the toolkit again to re-root?
lanwarrior said:
Mine is also unlocked and rooted and want to upgrade to KK.
When you said flash, you meant I had to install TWRP first then flash SU again?
I am curious because when I first rooted my N7, I used the Nexus 7 Toolkit and did not install TWRP. Can't I just use the toolkit again to re-root?
Click to expand...
Click to collapse
If you had a TWRP installed and downloaded the superuser binaries when you rooted initially, all you need to do is flash them again by pressing the "install" button in recovery. Based on the way he asked it, I believe that was the context of the question.
If you don't, you should install a custom recovery:
Wi-Fi only: http://techerrata.com/browse/twrp2/flo
LTE: http://techerrata.com/browse/twrp2/deb
Then download the superuser binaries to your N7:
http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
And flash them by pressing the "install" button in recovery.
Your toolkit might work, but why not just do it yourself?
Full instructions (skip unlocking the bootloader):
http://forum.xda-developers.com/showthread.php?t=2536420
Sent from my Nexus 6 using Tapatalk 4
xdhall said:
If you had a TWRP installed and downloaded the superuser binaries when you rooted initially, all you need to do is flash them again by pressing the "install" button in recovery. Based on the way he asked it, I believe that was the context of the question.
If you don't, you should install a custom recovery.
Click to expand...
Click to collapse
I assume there's no other way to re-root other than installing TWRP?
lanwarrior said:
I assume there's no other way to re-root other than installing TWRP?
Click to expand...
Click to collapse
You can install another custom recovery, e.g., clockworkmod.
Some toolkits reflash stock recovery after rooting, but that could only useful if you have something like a Samsung or HTC. Absolutely no point on a nexus device.
Sent from my Nexus 6 using Tapatalk 4
xdhall said:
You can install another custom recovery, e.g., clockworkmod.
Some toolkits reflash stock recovery after rooting, but that could only useful if you have something like a Samsung or HTC. Absolutely no point on a nexus device.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Thanks again for the help, xdhall. Sorry if I sound like a newbie, but I had the Note 8.0, I rooted and I could never get it back to stock. The original stock image for the US Note 8.0 was not available so I was stuck.
Didn't want the same thing happened with the N7, but you brought up a good point... this IS a Nexus device!
Thanks
xdhall said:
It will stay unlocked, but unrooted, and you only need to flash the supersu zip again.
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Thanks xdhall.
That makes it much easier to get back to ROOT then.
Just having to reboot in Recovery Mode and install the latest superSU.zip will be a breeze.
I'll probably wait a few weeks/months to upgrade to 4.4 though, as the comments on the 4.4 release are not that good, and I have several very important (for me) sites that still use Adobe Flash.
Anyway, I'm glad I haven't to start from scratch (backup, unlock, restore, flash recovery, flash superSU), as this is extremely time-consuming and tedious.
Again Thanks & have a nice WE.
Hey guys,
I was wondering if someone could help me a little. I just bought this tablet (2014 version) and it has MK1.
I am trying to read information on how to root it but can't figure it out. I tried to flash autoroot with odin but it errored. I didn't find mk1 autoroot anywhere so i used autorootp600.mj4.tar.md5. Is there autoroot for MK1 and i can use? Also i guess i will need to have custom recovery file for my stock OS, where do i get that?
Thank you in advance for all the help.
Edit: I finally located autoroot for mk1 and it worked. But i do have a question: why do we need to flash it with Stock Recovery after? btw i am using this tutorial : http://theunlockr.com/2013/12/17/root-samsung-galaxy-note-10-1-2014-edition/
What version do you have?
P600 (wifi only)
P601 (3g)
P605 (lte)
?
They have different chipsets and different root methods.
[e] I see you have found the correct version if you want to get OTA updates you need to flash stock recovery so your device status is not custom. But it basically doesn't matter since you can always flash updates through odin. You may choose a custom recovery that offers you a lot of cool features instead.
stamina11 said:
Hey guys,
I was wondering if someone could help me a little. I just bought this tablet (2014 version) and it has MK1.
I am trying to read information on how to root it but can't figure it out. I tried to flash autoroot with odin but it errored. I didn't find mk1 autoroot anywhere so i used autorootp600.mj4.tar.md5. Is there autoroot for MK1 and i can use? Also i guess i will need to have custom recovery file for my stock OS, where do i get that?
Thank you in advance for all the help.
Edit: I finally located autoroot for mk1 and it worked. But i do have a question: why do we need to flash it with Stock Recovery after? btw i am using this tutorial : http://theunlockr.com/2013/12/17/root-samsung-galaxy-note-10-1-2014-edition/
Click to expand...
Click to collapse
I believe...... so you can still get OTA updates and some functions like All Share Cast may not work if you don't.
The thing is, even if you have stock recovery but modify your system in other ways like uninstall alot of bloatware or use busybox your status will be custom anyway so I recommend a custom recovery for the safety of using backups etc.
Thank you guys for responding so quickly.
It's starting to make sense.
My device is Wifi only so SM-P600 (mk1). I rooted it but haven't flashed with stock recovery. Would you guys recommend i do a custom recovery or keep it stock? Where do i get stock recovery from? i can't seem to find it.
clouds5 said:
The thing is, even if you have stock recovery but modify your system in other ways like uninstall alot of bloatware or use busybox your status will be custom anyway so I recommend a custom recovery for the safety of using backups etc.
Click to expand...
Click to collapse
Yea i definitely plan on de-bloating it. So where do you get custom recovery?
http://forum.xda-developers.com/showthread.php?t=2515656
Check this thread
clouds5 said:
http://forum.xda-developers.com/showthread.php?t=2515656
Check this thread
Click to expand...
Click to collapse
Ok, that makes sense i went though it. So i see that there is ClockMod and TWRP and GooManager, do they do pretty much the same thing?
So as far as Roms go, i see that in Development section there are few ROMs available but some say they are for MJ9 or ML1, i cannot use those on my MK1 right? Do ROMs from note 10.1 (2013) work on this device? Is there a list of ROMs that would work on my device.
Sorry, guys i know these are newb questions but i just could never figure out some of this stuff.
stamina11 said:
Ok, that makes sense i went though it. So i see that there is ClockMod and TWRP and GooManager, do they do pretty much the same thing?
Click to expand...
Click to collapse
I got the same question here. Any help?
legender said:
I got the same question here. Any help?
Click to expand...
Click to collapse
Goomanager is an app use it to flash twrp recovery.
TWRP and clockmod (CWM) they are 2 different tools but have the exact same functions, just a user choice. Sometimes custom rom preferred one over the other. I like TWRP a bit better (easier).
is there a way to check if it is rooted or not?
legender said:
is there a way to check if it is rooted or not?
Click to expand...
Click to collapse
Download rootchecker in the play store
Sent from my Nexus 5 using Tapatalk
Hi all, its there any way of unlocking bootloader or bypass the lg security other than freegee as freegee is not supporting my android version. (E98810e)?
I have rooted and tried directly installing CWM. CWM works if i reboot from freegee but it will go into bootloop if i try to get into recovery using hardware key. Head too return to stock twice because of that... Can you help please?
Or is there any way of flashing custom rom without using freegee?
Sent from my LG-E988 using Tapatalk
Freegee does not unlock the bootloader. It just bypasses it. And as far as I know, Freegee is the only way to get CWM installed and boot. You can try using Rom Manager. It says Rom Manager has Loki support but when I tried it on my phone (E98010P) it wouldn't boot. You can give it a try and see what happens.
cougar214 said:
Freegee does not unlock the bootloader. It just bypasses it. And as far as I know, Freegee is the only way to get CWM installed and boot. You can try using Rom Manager. It says Rom Manager has Loki support but when I tried it on my phone (E98010P) it wouldn't boot. You can give it a try and see what happens.
Click to expand...
Click to collapse
Thanks... But will rom manager have the Capability of bypassing lg security.?
My ultimate requirement is to flash a custom kit kat rom... And as i understand i will not be able to flash custom rom without bypassing lg security...
Sent from my LG-E988 using Tapatalk
I was confused about this for the longest time. Freegee will install a lokified recovery which will bypass s-on and install roms for u
You know, that's a good question. Perhaps that is why Rom Manager won't work because it doesn't bypass the lg security? Maybe someone with more experience with this can give a better answer.
Anyone?
Akhileshjj said:
Thanks... But will rom manager have the Capability of bypassing lg security.?
My ultimate requirement is to flash a custom kit kat rom... And as i understand i will not be able to flash custom rom without bypassing lg security...
Sent from my LG-E988 using Tapatalk
Click to expand...
Click to collapse
Have there been any new news on the bootloader situation for this? Ive read conflicting reports about freegee and bootloops. Is there a tried and true way?
Can you not just use lg flashtools to flash a 10p firmware and go from there ?
Sent from my C811 4G using xda app-developers app
---------- Post added at 07:01 PM ---------- Previous post was at 07:01 PM ----------
I don't have this problem but I'm just saying ....maybe that would work for you
Sent from my C811 4G using xda app-developers app
I'm on LG E98020i. Freegee wouldn,t work for this software version. Can i flash version 98010g which happens to be supported and then root/unlock/flash CWM/Custom roms?
Well, finally I got it working! All about risk.
I simply
* flashed E98010g AT&T (4.1.2) into my current E98020i AT&T (4.4.2).
* Rooted it and unlocked the bootloader with freegee and flashing TWRP 2.3.x.x
* Performed a backup, then reflashed the newer recovery version 3.0.0 using flasify (I had to also backup my stock boot and recovery with flashify before proceeding)
* As the new recovery was installed, I simply wiped my partitions and flashed my Lollipop ROM 5.1 (ResurrectionRemix)
* My phone was brand new henceforth. So happy!
My fear was that I have to be coming from KK b4 flashing the Lollipop OS, but it didn't stop me from enjoying my "fresh" device.
Sent from my LG-E980 using XDA-Developers mobile app
dwapking said:
Well, finally I got it working! All about risk.
I simply
* flashed E98010g AT&T (4.1.2) into my current E98020i AT&T (4.4.2).
* Rooted it and unlocked the bootloader with freegee and flashing TWRP 2.3.x.x
* Performed a backup, then reflashed the newer recovery version 3.0.0 using flasify (I had to also backup my stock boot and recovery with flashify before proceeding)
* As the new recovery was installed, I simply wiped my partitions and flashed my Lollipop ROM 5.1 (ResurrectionRemix)
* My phone was brand new henceforth. So happy!
My fear was that I have to be coming from KK b4 flashing the Lollipop OS, but it didn't stop me from enjoying my "fresh" device.
Sent from my LG-E980 using XDA-Developers mobile app
Click to expand...
Click to collapse
That's similar to what I wound up doing.
On stock E98020i AT&T (4.4.2)
1. Rooted using towelroot.
2. Installed busybox
3. Installed GPRO_6.0.4.4 Recovery
4. Installed Flashify (tried FlashFire first and it ran a long terminal screen but didn't install TWRP) and flashed the oldest recovery TWRP listed on their website.
5. Verified it worked, and then flashed the latest TWRP.
Success.
I tried it the way you listed, but freegee kept either black screening or would just freeze up.
I read elsewhere that freegee is incompatible with the last AT&T KitKat release.
My only problem is that the latest CM12.1 for the e980 doesn't seem to go into deep sleep.
It used almost 20% of the battery in less than 4 hours with Wifi and bluetooth enabled.
If I can't fix it, I'll try CM11 and hope I get better results.
glocksman said:
That's similar to what I wound up doing.
On stock E98020i AT&T (4.4.2)
1. Rooted using towelroot.
2. Installed busybox
3. Installed GPRO_6.0.4.4 Recovery
4. Installed Flashify (tried FlashFire first and it ran a long terminal screen but didn't install TWRP) and flashed the oldest recovery TWRP listed on their website.
5. Verified it worked, and then flashed the latest TWRP.
Success.
I tried it the way you listed, but freegee kept either black screening or would just freeze up.
I read elsewhere that freegee is incompatible with the last AT&T KitKat release.
My only problem is that the latest CM12.1 for the e980 doesn't seem to go into deep sleep.
It used almost 20% of the battery in less than 4 hours with Wifi and bluetooth enabled.
If I can't fix it, I'll try CM11 and hope I get better results.
Click to expand...
Click to collapse
I used freegee and got the exact same results. So I went much further...brick or fix the wakelock with different basebands and kernel combos. Nexus4 radios, weird hardware issues, touch issues in a touch recovery, fun stuff. I bricked it over and over having to rgflash 4.1.2 tot. Each 'return to stock' release tot for att seems to use a different method to loki a custom recovery. idk. I've always been able to enter download mode.:fingers-crossed:
I was flashing the wrong stock firmware version and after lgflashing v10g stock firmware, I was able to update to the latest TWRP recovery using the following steps: towelroot/supersu/busybox/reboot/flashify...no wakelock in Carbon 5.1 :highfive:
@glocksmam @ssurell
The best way I found to tame battery life on the G Pro, using SlimLP :
https://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884
Also, I got myself a new battery, and I'd recommend the zero lemon ones.
Flashing steps
1. Stock JB
2. Towelroot
3. Freegee's TWRP
4. Flashify TWRP 3.0.2.0
5. SlimLP
6. Open Gapps
7. V4A Sony Beats
8. KK baseband
For the baseband I extracted it from KK to flash it when I need as it is better than JBs.
I have my G Pro running for 14 hours now and I am at 34%...I used Palabre to read some stuff on WiFi for about half an hour. Then, left the phone... Then, I spent an hour and a half reading an ebook on Moon+, screen awake all the time, reader's brightness at 40% on a dark theme.
I haven't tried slim since kat and have been interested in trying it again. I was a big 'quick settings ribbon' kind of user, disenfranchised when SlimROMs stopped offering the feature. But I've since given that dream up and swipe crazily in horizontal gestures since 5.0 But SlimROMs are fast, stable, and ya know...slim.
g0at1 said:
@glocksmam @ssurell
The best way I found to tame battery life on the G Pro, using SlimLP :
https://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884
Also, I got myself a new battery, and I'd recommend the zero lemon ones.
Flashing steps
1. Stock JB
2. Towelroot
3. Freegee's TWRP
4. Flashify TWRP 3.0.2.0
5. SlimLP
6. Open Gapps
7. V4A Sony Beats
8. KK baseband
For the baseband I extracted it from KK to flash it when I need as it is better than JBs.
I have my G Pro running for 14 hours now and I am at 34%...I used Palabre to read some stuff on WiFi for about half an hour. Then, left the phone... Then, I spent an hour and a half reading an ebook on Moon+, screen awake all the time, reader's brightness at 40% on a dark theme.
Click to expand...
Click to collapse
I found the issue.
WiFi was set to 'Always On'.
Changing it to 'Only On When Plugged In' gave me normal battery life.