Database Info

[Q] Getting CWM installed on new ICS firmware Galaxy S2

Hi folks and especially Chainfire if he is tracking nu-bees,
Nu-bee here. Just installed Resurrection Remix Pro ICS firmware following instructions at Galaxy2Root.com. They had me install 3 files with the Remix package, GoogleApps and GoogleAppsFix. All went well. Then the instructions told me to install 10_CWM.zip so that ClockWorkMod would work. But CWM had been overwritten, so I couldn´t install something from my internal sdcard. I thought I would be clever and install one of Chainfire´s custom CF-root packages. I selected one close to the kernel number I have installed (LPJ). I flashed it over with Odin.
No joy. The phone booted, showed the opening logo and then lay there with a black screen. But CWM recovery still was active, so I wiped the system and reinstalled the files this time including 10_CWM.zip (4 files). This time I have ICS but CWM is gone again. I´d like to back up the ROM.
I´d like suggestions as to how to get CWM installed. I would be most grateful! I read the entire 450 page set of posts on Chainfire´s CF-root upgrades (whew). I´d use one of those if I was confident that I wouldn´t go back to a black screen again.....

still trying
Well, I haven´t gotten much of a response with this. With this 10 post limit for noobies, I can´t get to the developers forum where I would find the folks who grapple with these kinds of issues.
Anyway, I flashed the latest of Chainfires kernels, the LP7 version, and ended up with a black screen again. So I went into restore (and had CWM restore at least) and restored my ROM, etc. But of course, I lost CWM in the process. And had to reconfigure my phone all over again. I had used My Backup Pro and it didn´t save the connections to the Google Market, so I had to reinstall my apps all over again. Is Titanium better in this regard? My Backup Pro claims to make better backups for rooted phones, but this was pretty feeble.
So that will be my question for this forum - should I change to Titanium? Will it get all my apps, settings, and data back into my preferred configuration?
Have a great day......

I am in same boat as you are. I buy i just installed rom with Rom manager and i have Gapps fixer and remix one left and CWM ofcourse. So my problem is i don't have Ex-sd as they suggest to Install "Cwm.zip from external sd card from recovery". How to do so ?
Please help
Thanks in advance
EDIT: Never mind I sort it out Yesterday. I installed from Rom manager & Flash recovery from it and then boot up into recovery from App and then Flash Touch Recovery.

Htc One S Root SuperSU0.99 issue

Hi
Many people complained last days that they have problem with SuperSU 0.99 app.
They cant update the binary and phone reboots its self after "update failed" message
I got an HTC One S with S4 cpu last week and i got the new Jelly Bean Update 4.1.1
Then i unlocked my bootloader and installed TWRP custom recovery with One_S_All-In-One_Kit_v3.0 tool kit
After that i tryed to Root the phone with SuperSU 0.99.
Seems worked fine until i tryed to update my binary.
I get message "update failed" and my phone restarts.
I tryed to wipe and reflash the root but still same.
I even tryed to remove SUPERSU from System/App but with no luck. It keeps coming back even if i
removing it and revert everything to stock its still in SYSTEM.
Now i found this new Superuser version and flashed it and now my phone works fine and updating binary.
No more phone restart.
Even my SuperSU 0.99 is gone from system.
How TO:
Download superuser from this page http://androidsu.com/superuser/
Superuser-3.2-RC3-arm-signed.zip
Then boot into recovery
Flash Superuser-3.2-RC3-arm-signed.zip
Restart and voila the root works...
Hope i helped you guys.. Good Luck

Version 3.1.3 is reported to work better.
And doubt it really needed a new thread starting its discussed in most rom treads.

I started this thread just because of the issue SUPERSU 0.99 brings to HTC One S with Jelly Bean update.
I hope i can help someone because i didnt find any solution to my problem until i flashed superuser and it solved my problem.

shadowch31 said:
Version 3.1.3 is reported to work better.
And doubt it really needed a new thread starting its discussed in most rom treads.
Click to expand...
Click to collapse
I agree that this adds clutter, but I have been lightly following the threads for the JB ROMs and tried using superuser (though not the rc) without it working (still unable to update system). It's good to have this kind of solution in its own thread but general would probably be a better section.
Sent from my HTC One S Special Edition using xda app-developers app

This doesn't belong in the dev section for multiple reasons
Sent from my HTC VLE_U using xda app-developers app

Im sorry i didnt see that it was Development section. If someone can move it pls do so.

everyone uses SU...... this is very important for everyone using JB... leave it in here...
I feel it belongs here... this is where SU apps are in the development section... SO, this is where it should stay... (that is just my opinion)

I never want to start this thread like an development because im not a developer.
Reason is that i want to share my issue with anyone who is facing the same problem as i did.
Just like i said if someone think this thread doesn´t belong here then admins can move it to right section.

Updated to JB with OTA yesterday night.
Short version:
-Initially rooted with CWM recovery-> flashed MoDaCo stock recovery
-Apply OTA
-Flash CWM recovery
-Used CWM recovery to flash SuperSU 0.99 zip
-Uninstall/reinstall SuperSu from the Market
When starting SuperSU, it asks for update, if agree -> reboot.
BUT
When using root needing apps, like Titanium backup or FX file manager, they ask for root permission through SU and everything runs normally.
So SuperSU seems to work, only the front end app has some bug. I'm staying with that config waiting for an update.

Hi, same problem here on S3 cpu. Is this method works on S3 cpu as well? Thx for replying.

Hi. I think I have a problem with SuperSU (or something else??). I first started SuperSU last thursday (31.1.2013.). It ask me to update binary, I hit OK, and then it took about half hour to restart. System then recovered, and everything seem to be OK, but it's not!
When I connect my HTC One S to PC I only see files created (photos, videos) until 31.01.2013. Also, when I run Settings -> Memory com.android.settings crashes.
What to do?
I'm new to android. Plese help!

bihslk said:
Hi
Many people complained last days that they have problem with SuperSU 0.99 app.
They cant update the binary and phone reboots its self after "update failed" message
I got an HTC One S with S4 cpu last week and i got the new Jelly Bean Update 4.1.1
Then i unlocked my bootloader and installed TWRP custom recovery with One_S_All-In-One_Kit_v3.0 tool kit
After that i tryed to Root the phone with SuperSU 0.99.
Seems worked fine until i tryed to update my binary.
I get message "update failed" and my phone restarts.
I tryed to wipe and reflash the root but still same.
I even tryed to remove SUPERSU from System/App but with no luck. It keeps coming back even if i
removing it and revert everything to stock its still in SYSTEM.
Now i found this new Superuser version and flashed it and now my phone works fine and updating binary.
No more phone restart.
Even my SuperSU 0.99 is gone from system.
How TO:
Download superuser from this page http://androidsu.com/superuser/
Superuser-3.2-RC3-arm-signed.zip
Then boot into recovery
Flash Superuser-3.2-RC3-arm-signed.zip
Restart and voila the root works...
Hope i helped you guys.. Good Luck
Click to expand...
Click to collapse
I'm glad I ran across your thread. It helped me tremendously...
Da Baron

Any idea on how to get SuperSU work instead of SuperUser? I purchased SuperSU in the play store and I think it just looks better...

Moto G rooted. 4.4.2 upgrade to 4.4.3 how to?

Moto G, currently running 4.4.2 unlocked and rooted with TWRP v2.6.3.0 the firmware is tweaked to my liking with GravityBox. I am also using the Faux123 to over/under clock etc.
Very happy with the performance, features and battery life.
But I am now getting bugged by the Motorola update for 4.4.3
I did try to update and the phone got into a start, reboot loop. So I have restored to my last configuration.
It's been quite sometime since I played with configuring the above and I have gone a bit blank! Can someone please outline the steps that I have to do to complete the upgrade with minimum fuss.
As a side note. I have avoided custom ROMs so far because of all the problems that I was reading about several months ago. But perhaps enough time has elapsed for me to consider going say CM11 now? I would appreciate any comments as to me going down this route. ie. Are all bugs worked out is the Moto G fully functional, does a custom ROM truly provide worthwhile benefits?
Thanks.

I would also like to know this as well as I am currently on 4.4.2 unrooted, but really feel feel like I want to start and get my Moto G rooted and up and running with all the goody's available on the community, but feel like I should wait for the 4.4.3 rollout before I start going through the whole bootloader unlocking, rooting etc.
So I will check back on this post, and thank you to the thread starter as this saves me starting a similar topic.

Rooted 4.4.2 over here as well. Unfortunately I've had no such luck finding a way to update to 4.4.3 while being rooted. I've been through a plethora of guides and suggestions but nothing seems to be working. I'll end up getting an error no matter what I do.
Don't mean to try and hijack your thread, but I've been trying to flash the .zip for the update with both CWM and TWRP but I get an error every time. Anyone have any ideas why? Do I need to configure root-requiring apps beforehand or something?

ugh...same here! Please someone figure this out!

@Kwala Baerr I was hoping for a quick 1,2,3 Guide! I miss posted the question in the General section, then moved it here. I subsequently find a few similar posts in this section. But your message suggests that you may have already tried them which worries me! Anyway I will have a go tomorrow and post here if I get success.
Sent from my Nexus 7 using Tapatalk

@grahamgo oh yea sorry. Well I've tried just about everything. I think I've narrowed down my problem to SoftKeyz messing up my SystemUI.apk so you might still have a chance. Let me know how it goes though!

grahamgo said:
Moto G, currently running 4.4.2 unlocked and rooted with TWRP v2.6.3.0 the firmware is tweaked to my liking with GravityBox. I am also using the Faux123 to over/under clock etc.
Very happy with the performance, features and battery life.
But I am now getting bugged by the Motorola update for 4.4.3
I did try to update and the phone got into a start, reboot loop. So I have restored to my last configuration.
It's been quite sometime since I played with configuring the above and I have gone a bit blank! Can someone please outline the steps that I have to do to complete the upgrade with minimum fuss.
As a side note. I have avoided custom ROMs so far because of all the problems that I was reading about several months ago. But perhaps enough time has elapsed for me to consider going say CM11 now? I would appreciate any comments as to me going down this route. ie. Are all bugs worked out is the Moto G fully functional, does a custom ROM truly provide worthwhile benefits?
Thanks.
Click to expand...
Click to collapse
Put on your phone Us firmware http://forum.xda-developers.com/showthread.php?t=2542219 setup the phone via wifi. Update is about 163mb. After that use Mototool to root the phone and fix the white screen http://forum.xda-developers.com/showthread.php?t=2635706
mabey you can do a beckup of sms https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore and https://play.google.com/store/apps/details?id=com.riteshsahu.CallLogBackupRestore
regards

I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!

tarotsujimoto said:
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
Click to expand...
Click to collapse
What recovery were you on?

Kwala Baerr said:
What recovery were you on?
Click to expand...
Click to collapse
Here's the thread with information on downloading & installing PhilZ Touch recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
Looks like there's a new stable release out, but I still had PhilZ Touch 6.26.6 Falcon installed.

tarotsujimoto said:
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
Click to expand...
Click to collapse
Im rooted running stock rom and using exposed installer with gravity box and a few other modules running and all I had to do to update to 4.3.3 was to use Moto Tool AIO v3.0 to revert back to stock kitkat recovery, after that I just accepted the update, installed it, and then went back to a custom recovery. I lost none of my exposed installs or settings, took maybe 10 minutes start to finish and was painless.

tarotsujimoto said:
Here's the thread with information on downloading & installing PhilZ Touch recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
Looks like there's a new stable release out, but I still had PhilZ Touch 6.26.6 Falcon installed.
Click to expand...
Click to collapse
I have just wasted a lot of time...... I tried Philz Touch 6.43.8, no go, then an earlier version, still no go. Then I found a thread saying that there were bugs in later versions, they recommended the use of 6.26.6
I tried it and it works great. However I wasted almost 2 hours finding this out.

castuis said:
Im rooted running stock rom and using exposed installer with gravity box and a few other modules running and all I had to do to update to 4.3.3 was to use Moto Tool AIO v3.0 to revert back to stock kitkat recovery, after that I just accepted the update, installed it, and then went back to a custom recovery. I lost none of my exposed installs or settings, took maybe 10 minutes start to finish and was painless.
Click to expand...
Click to collapse
I appreciate @tarotsujimoto post and I see the logic of this approach. But I too was thinking that it might be less troublesome (but maybe take longer) to go back to factory, update it to 4.4.3 and then re-install Xposed and apps + data, etc using Titanium.
@castuis I am intrigued by your mention of using a custom recovery. Could you please expand on what you backed up and if possible more details on how you did it etc.
I have wasted too much time today getting a working Philz Touch going, (maybe I should have stayed with TWRP!). But I do like the look of Philz 6.26.6 now its working. But will have to put my 4.4.3 update attempt off for a day or so.
Thanks!

Since none of the methods mentioned works for me, I have tried to extract the system.img from the original ROM archive. But how do I mount that system.img_sparsechunk files on Linux? They can not be converted by simg2img or unyaffs either ...

I had no success with any of the "short cut" methods either. I was hoping that @castuis promise of a 10 minute method would come true, but he hasn't been back to expand on his method. I myself reverted the phone to factory, let it upgrade. Then re-rooted, installed xposed and then let Google play reinstall my apps. It's definitely not a quick method. But at least it gave me a clean install. Significant frustration, caused by using Philz touch, but switched to TWRP. Finally did a system backup with Titanium. I thought that was it. Now it looks like there will be a 4.4.4 soon. I'm thinking to ignore it and wait for the next upgrade. @nodh I would wait for 4.4.4 !
Sent from my Nexus 7 using Tapatalk

I've solved my upgrade problem: I've flashed the 176.44.1 (retail Germany, 4.4.3) stock ROM, as described here. Altough I didn't flash the recovery (to restore root with the ClockWorkMod recovey) and didn't erase userdata. Now I've got the upgrade, with all my settings preserved and even rooted again.

Unable to restore/mount/flash in TWRP and unable to achieve dl mode in LG Flashtool

Here's to hoping someone can help me out. My phone details before I messed up: LG G3 D850, rooted, TWRP 3.0, running Fulmics 5.2 for about 1 1/2 weeks
I noticed that I was not seeing the LTE indicator on my phone. I checked the HUB and saw the BootD850-30012016 data patch and figured that I just needed to install. So I flashed it and my phone wouldn't start. I was able to boot into recovery, so I figured I would do a clean install of the ROM so I did a full wipe, accidentally wiping EVERYTHING except for my external SD.
Result was that I can access TWRP but am unable to flash any of my backups or zips from my external SD, or OTG. I can see the files, but don't have the option to "swipe". I also am unable to 'mount' or 'install'.
At this point, I noticed that AT&T has finally released the OTA for Marshmallow, so I figured I would just use LG FlashTool and totally un-root and give the update a try. (BTW, I have used the flash tool many times with no problems/issues on both my phone and my son's D855).
Unfortunately, I am getting the dreaded "unable to change to download mode" after 15 seconds. I have uninstalled and re-installed Flash Tool, the LG Drivers and all files and used every port on both of my computers (Windows 10 btw) but can't get past the download error.
So...after many hours of digging, I took a leap of faith and was able to sideload Fulmics 5.1 successfully and install the 5.2 update from the HUB. I made backup of the ROM but TWRP still won't allow me to "swipe" and install/restore. I reinstalled TWRP using Flashify and it installed version 2.8 but still no go on flashing from recovery.
I realize that I'm lucky to have been able to figure out how to get the phone back using the sideload function in TWRP, but I really do want to go back to stock and it bugs me that I am unable to use my backups.
Sorry for the novel, but I wanted to be sure to include everything I did....if anyone can help me out I would be much obliged. My 11 year old is anxiously waiting on me to figure this out before she gets this phone (I'm moving up to the HTC 10 in a couple of weeks!). She still thinks I'm 'SuperMommy' so if I can fix this I get to keep my swagger!

I was also running fulmics 5.1 and updated to 5.2 in my phone but now i was having pretty good laggs and i finally realised that the update provided by the phone was corruped so i went on the official site and downloaded the same 5.2 OTAs from there and flashed it into TWRP recovery to finally get the latest version 5.3..know that is it always advisable to flash zip file when in recovery mode using TWRP recovery...The big mistake was cleaning also the internal memory of your phone.this caused the malfunction of twrp.

The issue is that most often i have seen cases of lagg in those updating to fulmics 5.2 from the Hub .sometimes in twrp recovery the update files will not successfully wipe and then reboot system with 5.2 installed but with many lagg the file downloaded there may be corrupted and not give you permission to swipe..if you really like fulmics and still update to the latest..Try this it may help you solve your problem:1 reinstall the fulmics 5.1 go to xdadevelopers.com/fulmics follow the link given by xpirit to www.fulmics.com and download the OTA 5.2(file size maybe 46 mb).. 2.reboot your phone now in twrp recovery it should now be able swipe and install..(if not then install Twrp 3.0 and try) 3-search the files in your internal memory or wherever you have downloaded it and flash it ..4.reboot system.That should be done!! In case you want to come back to stock and cant install from Twrp then the problem is with Twrp just download the latest version that goes with your phone.

Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.

dcli23 said:
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
Click to expand...
Click to collapse
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk

SofaSpud said:
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Hey there....you can access the Hub after you flash the Fulmics ROM. It's where you can get your tweaks, downloads, mods, etc. You'll find it in your app drawer.

BLU PURE XL - STOCK ROM or Assistance with Download Error

I own a BLU Pure XL, installed the custom CM12 rom to try out and I forgot to backup. I noticed someone uploaded the Stock Rom for 5.1 but for some reason It won't let me download anything from the play store showing it as paused all the time. I have cleared data for all the download apps,play store, and play store services within the apps section and installed a GAPP zip get the same result. The same error occurs with the OTA update saying cannot connect even with access to the internet and the ability to search the app store.
So if anyone has a stock 6.01 version and could upload it I would greatly appropriate it

I have the same problem. Unable to download anything from the play store. Still searching for a solution. Please let me know if you resolve this issue and I will do the same

I'm going through it ,too, thought about flashing Gionee ROM

Bought New Phone
I am not to much of a fan of the phone anyways so bought a BB Priv. If anyone finds a solution please post so I can have a backup phone

OK, I had to utilize the Gionee scatter file and stock ROM in order to get the phone partitioned correctly,
I then took the BLU Scatter file and Stock ROM , boot, and recovery and flashed it afterward. Then did a factory reset. Took updates then rooted, again. You are left with the Gionee splash screen... But that's an easy fix.
Appears that the versions of TWRP posted DO NOT partition the phone correctly and writes a TWRP partition that screws everything up.
I will post links or you can find them yourself in the meantime. They are all on xda mainly on the thread about rooting... Odd thing is. Phone seems to run better than before... I would have left the Gionee ROM up and running if it wasn't 4G only... I'll post links later.

Its been well documented to use the TWRP 2.8 not the 3,0 as it has issues partitioning. there is a whole thread about unbricking where we went into EXTENSIVE depth on this