Database Develop

[Q] unlocked bootloader and installed supersu but still no root.

Hello everyone. I have been using the information from xda developers since the att tilt came out to configure my phones, a lot has changed since then. I'm now using HTC one sprint version and have unlocked bootloader and installed supersu (superuser first but saw it was not for android 4.1+ so found supersu) and root checker says my device is not rooted. I looked over all the videos on YouTube but still cannot figure out what I did wrong. Can someone please help me? This is my first attempt to root by the way. Been at it for two days now.

Babien said:
Hello everyone. I have been using the information from xda developers since the att tilt came out to configure my phones, a lot has changed since then. I'm now using HTC one sprint version and have unlocked bootloader and installed supersu (superuser first but saw it was not for android 4.1+ so found supersu) and root checker says my device is not rooted. I looked over all the videos on YouTube but still cannot figure out what I did wrong. Can someone please help me? This is my first attempt to root by the way. Been at it for two days now.
Click to expand...
Click to collapse
you have to install a custom recovery(TWRP 2.6.3.0 or CWM) THEN FLASH SUPERSU through recovery. you can't just install in though the market.a zip file not an apk or image file

Aldo101t said:
you have to install a custom recovery(TWRP 2.6.3.0 or CWM) THEN FLASH SUPERSU through recovery. you can't just install in though the market.a zip file not an apk or image file
Click to expand...
Click to collapse
Thanks for the reply! That lets me know I posted correctly. So I did install custom recovery, clockworkmod and I did the unzip from sd option. The phone updates and I reboot but still not rooted. I will try again right now and write everything down.

Babien said:
Thanks for the reply! That lets me know I posted correctly. So I did install custom recovery, clockworkmod and I did the unzip from sd option. The phone updates and I reboot but still not rooted. I will try again right now and write everything down.
Click to expand...
Click to collapse
Just tried again in clockwork recovery touch v6.0.3.3 I went to install zip, choose zip from sdcard, UPDATE-SuperSU-v1.41/ which is the folder it's in. After that phone loads saying update UPDATE-SuperSU-v1.41/ finding update package. Followed by opening update package and then installing update. It says mounting, disabling OTA survival, removing old files, creating space, extracting files, restoring files, setting permissions and ending with unmounting then done. Now my android version is 4.3 and I previously unzipped through recovery superuser no supersu but uninstalled it because superuser I had said only good for android 2.0-4.0 . My hboot is 1.55 and my phone says m7_wls pvt ship s-on rh if that helps. For some reason though Rom manager sees my device as m7spr, unsupported device in clockwork recovery option of that program. Sorry if I'm confusing you, just wanted to put everything that I can give at this time.

Babien said:
Just tried again in clockwork recovery touch v6.0.3.3 I went to install zip, choose zip from sdcard, UPDATE-SuperSU-v1.41/ which is the folder it's in. After that phone loads saying update UPDATE-SuperSU-v1.41/ finding update package. Followed by opening update package and then installing update. It says mounting, disabling OTA survival, removing old files, creating space, extracting files, restoring files, setting permissions and ending with unmounting then done. Now my android version is 4.3 and I previously unzipped through recovery superuser no supersu but uninstalled it because superuser I had said only good for android 2.0-4.0 . My hboot is 1.55 and my phone says m7_wls pvt ship s-on rh if that helps. For some reason though Rom manager sees my device as m7spr, unsupported device in clockwork recovery option of that program. Sorry if I'm confusing you, just wanted to put everything that I can give at this time.
Click to expand...
Click to collapse
you may need to update the supersu to 1.80. i think you can find it in the forums here, i can't remember where its at also you may need to install TWRP 2.6.3.0, these recoveries are touchy here lately.
might look at big daddy's FAQ forum lot of help there.

Aldo101t said:
you may need to update the supersu to 1.80. i think you can find it in the forums here, i can't remember where its at also you may need to install TWRP 2.6.3.0, these recoveries are touchy here lately.
might look at big daddy's FAQ forum lot of help there.
Click to expand...
Click to collapse
thanks again for the help. I will flash with twrp, I like clockworkmod because I had it on my rooted evo I paid someone to root for me. I'll look for it and the supersu youbare referring to. Any special information or steps I need to do to change recoveries or updating to a new supersu? Like do I need to delete or wipe cache before going into fastboot ?

Babien said:
thanks again for the help. I will flash with twrp, I like clockworkmod because I had it on my rooted evo I paid someone to root for me. I'll look for it and the supersu youbare referring to. Any special information or steps I need to do to change recoveries or updating to a new supersu? Like do I need to delete or wipe cache before going into fastboot ?
Click to expand...
Click to collapse
no you do not need to wipe anything, make sure your sdk tools are up to date, and flash recovery with adb.(fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img)
you should uninstall the superuser before installing a new one.

Same Problem, easy solution
I downloaded 1.80 update but TWRP told me that it was bad. Every time I downloaded the update (from my current 1.65) it didn't work. Finally, I clicked the link for the Play Store, installed SuperSU, it updated, and everything works again.

[Q] I managed to remove my os on my phone. Help please!

I want to start this off with that i really don't know anything about ROMs and flashing and stuff like that, so just hold that in mind. I am pretty sure that I have the international version of the HTC One since I live in Sweden.
Ok, so here is what happened: I rooted my phone bu using TWRP 2.6.3.3 and SuperSU 1.91. The reason i wanted to root my phone was to be able to use an app that you can only use if you have rooted your phone. When i rooted my phone and downloaded the app it said that i needed to uppdate my busybox so i downloaded a busybox installer from the appstore. When i tried to uppdate my busybox to the latest version it wouldnt work for some reason so i was going to re-root my phone with Superuser instead. However when I couldnt drag the Superuser folder into my sd card i started messing around in twerp recovery and being an idiot as i am i did a "Format data" in TWRP, when i did that obviusly everything got removed and now i don't have an os the only things i can do is booting into bootloader and TWRP otherwise my device is stuck on the HTC bootscreen. Also when i connect my phone to my computer nothing pops up so im guessing that my computer can't recognise it anymore.
I have using google but i couln't find anything. I will be monitoring this thread like a hawk so please help me.
Edit: Here is more information: I have S-on, it also says ***tampered*** and ***unlocked***
Edit2:If you need any more information for helping me please let me know and ill get it.
TL;DR: Rooted HTC One with SuperSU, Formatted data, no os, need help.

Cyanisyde said:
I want to start this off with that i really don't know anything about ROMs and flashing and stuff like that, so just hold that in mind. I am pretty sure that I have the international version of the HTC One since I live in Sweden.
Ok, so here is what happened: I rooted my phone bu using TWRP 2.6.3.3 and SuperSU 1.91. The reason i wanted to root my phone was to be able to use an app that you can only use if you have rooted your phone. When i rooted my phone and downloaded the app it said that i needed to uppdate my busybox so i downloaded a busybox installer from the appstore. When i tried to uppdate my busybox to the latest version it wouldnt work for some reason so i was going to re-root my phone with Superuser instead. However when I couldnt drag the Superuser folder into my sd card i started messing around in twerp recovery and being an idiot as i am i did a "Format data" in TWRP, when i did that obviusly everything got removed and now i don't have an os the only things i can do is booting into bootloader and TWRP otherwise my device is stuck on the HTC bootscreen. Also when i connect my phone to my computer nothing pops up so im guessing that my computer can't recognise it anymore.
I have using google but i couln't find anything. I will be monitoring this thread like a hawk so please help me.
Edit: Here is more information: I have S-on, it also says ***tampered*** and ***unlocked***
TL;DR: Rooted HTC One with SuperSU, Formatted data, no os, need help.
Click to expand...
Click to collapse
Don't panic mate, it's ok you didn't break anything.
Ok, so you can go into twrp. That's enough
All you have to do is installing a custom ROM and you will have your phone back.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=2183023 to install Android revolution HD 51 (4.4.2 android)
Since you can't access the internal SD from your computer, you will have to Sideload it. Don't worry nothing so difficult:
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2318497
So: -Download the file from the first link.
- sideload it into your TWRP
- install it from twrp
- Done!!

Uxepro said:
Don't panic mate, it's ok you didn't break anything.
Ok, so you can go into twrp. That's enough
All you have to do is installing a custom ROM and you will have your phone back.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=2183023 to install Android revolution HD 51 (4.4.2 android)
Since you can't access the internal SD from your computer, you will have to Sideload it. Don't worry nothing so difficult:
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2318497
So: -Download the file from the first link.
- sideload it into your TWRP
- install it from twrp
- Done!!
Click to expand...
Click to collapse
THANK YOU SO MUCH FOR THIS! I will be trying this right now!

Uxepro said:
Don't panic mate, it's ok you didn't break anything.
Ok, so you can go into twrp. That's enough
All you have to do is installing a custom ROM and you will have your phone back.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=2183023 to install Android revolution HD 51 (4.4.2 android)
Since you can't access the internal SD from your computer, you will have to Sideload it. Don't worry nothing so difficult:
Here is the guide: http://forum.xda-developers.com/showthread.php?t=2318497
So: -Download the file from the first link.
- sideload it into your TWRP
- install it from twrp
- Done!!
Click to expand...
Click to collapse
I just have one question: Do i download the HD 31.6 or do i download HD 51.0 version of the ROM?

Cyanisyde said:
I just have one question: Do i download the HD 31.6 or do i download HD 51.0 version of the ROM?
Click to expand...
Click to collapse
51.0!

Uxepro said:
51.0!
Click to expand...
Click to collapse
Thank you once again!

Cyanisyde said:
Thank you once again!
Click to expand...
Click to collapse
You are welcome! Last raccomandations, when you flash Android rev. remember to select the wipe option in Aroma installer.
Also at the end of the installation press on "wipe davilk cache"
If you encounter bootloop do a "fastboot erase cache".
Also, remember that the first boot after flashing it takes long time (even 10 mins) and it's seems stuck on the htc logo but it's not
Good luck!

[q] xposed framework installation aborted

Hi,
I just installed the Xposed installer.
I'm trying to install the XPosed framework. Tried the classic way, but after reboot the framework is not installed; then tried with the recovery, but it says "installation aborted". The phone is rooted, of course.
Please help me

What phone do you have? What recovery? You need to have a custom recovery to flash it

GermainZ said:
What phone do you have? What recovery? You need to have a custom recovery to flash it
Click to expand...
Click to collapse
Phone: huawei g700 (4.2). I don't have any custom recovery, I think, but in the instructions for the installation of Xposed this wasn't mentioned

ouardo said:
Phone: huawei g700 (4.2). I don't have any custom recovery, I think, but in the instructions for the installation of Xposed this wasn't mentioned
Click to expand...
Click to collapse
How is your phone rooted, if not from a custom recovery? Or did you revert from the custom recovery to a stock recovery after rooting?
If you selected "Classic" install in Android, it tries to install directly via root methods. This fails if you do not have root.
If you selected recovery method, an installationfile is saved to your SD card, and that is then automatically installed when the phone reboots (into the custom recovery you installed). If no custom recovery is installed, then the recovery method is pointless as the means by which the installation takes place, is not there at all (the custom recovery).
Please download Root Checker ( https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck ) - does it verify you have root?
Kind Regards
TwinAdk

TwinAdk said:
How is your phone rooted, if not from a custom recovery? Or did you revert from the custom recovery to a stock recovery after rooting?
If you selected "Classic" install in Android, it tries to install directly via root methods. This fails if you do not have root.
If you selected recovery method, an installationfile is saved to your SD card, and that is then automatically installed when the phone reboots (into the custom recovery you installed). If no custom recovery is installed, then the recovery method is pointless as the means by which the installation takes place, is not there at all (the custom recovery).
Please download Root Checker - does it verify you have root?
Kind Regards
TwinAdk
Click to expand...
Click to collapse
I used FRAMAROOT, which is the easiest way. The root is verified. And the system recovery is there, I also tried to manually flash the zip, but it says "installation aborted". If I choose the classic mode, it reboots but with no results, as the framework is not present, even if the two voices (app process and xposedbridge) are green and active.

I have z2 with rooted, I just installed xposed, but when I am trying to update framework work it shows me this error,.

Now I tried with a custom recovery, this time it flashed the zip and everything seemed alright, but then again when rebooted, in the Xposed launcher it seems like no framework has been installed, and there is still the red error :crying:

GermainZ said:
What phone do you have? What recovery? You need to have a custom recovery to flash it
Click to expand...
Click to collapse
Done, but with no results as I said

sandy.parulekar said:
I have z2 with rooted, I just installed xposed, but when I am trying to update framework work it shows me this error,.
Click to expand...
Click to collapse
Don't crosspost!
ouardo said:
Now I tried with a custom recovery, this time it flashed the zip and everything seemed alright, but then again when rebooted, in the Xposed launcher it seems like no framework has been installed, and there is still the red error :crying:
Click to expand...
Click to collapse
Which "red error" are you referring to? If it's just the red text on the welcome screen, but the version number is green, check the log section if there is any error message there. You might have run into the issue "ClassCastException" that is mentioned in the FAQ.

ouardo said:
I used FRAMAROOT, which is the easiest way. The root is verified. And the system recovery is there, I also tried to manually flash the zip, but it says "installation aborted". If I choose the classic mode, it reboots but with no results, as the framework is not present, even if the two voices (app process and xposedbridge) are green and active.
Click to expand...
Click to collapse
There is an old and a new way to install things in a recovery, and xposed uses the new way cannot remember the names or the difference), but your recovery must support it. What recovery did you flash, and what error do you get?

GermainZ said:
What phone do you have? What recovery? You need to have a custom recovery to flash it
Click to expand...
Click to collapse
rovo89 said:
Don't crosspost!
Which "red error" are you referring to? If it's just the red text on the welcome screen, but the version number is green, check the log section if there is any error message there. You might have run into the issue "ClassCastException" that is mentioned in the FAQ.
Click to expand...
Click to collapse
Yes, that's the error. So there's no way to get it working? In the settings I can't see any option to disable the resources API, as suggested in the FAQ.

Gesendet von meinem GT-N7000 mit Tapatalk

I have micromax canvas play q355.....custom recovery is not available for my device...........is there any other way to install xposed framework?

[ROOT][RECOVERY][Xposed] worked/confirmed Blu Vivo XL. No need unlock bootloader.

First I want to thanks emowing for his finding the brother of this Blu Vivo XL, it is Gionee Elife S Plus.
Whole thing: https://blog.hovatek.com/how-to-root-gionee-elife-s-plus/
Step1: Install Vcom Driver manually. This intend to use for the SP Flash tool to work.
https://forum.hovatek.com/thread-440.html
Step2: Run SP Flash tool to install CWM recovery.
*** When read from scatter file, choose RECOVERY ONLY.
https://forum.hovatek.com/thread-159.html
Step3: please do backup to excard (sdcard1) before install superSU.zip
Step4: root, by installing superSU using CWM.
*** Xposed:
Download the latest version of Xposed for sdk22 and arm64 from here.
As of this writing it is xposed-v80-sdk22-arm64.zip.
Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install framework xposed-v80-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Initial boot would take longer than normal, plus rebooted like five times during the "Android is starting" (orange color on white background) step but finally finished.
Once your phone boots up install app XposedInstaller_3.0_alpha4.apk
Now you are ready for your favorite modules.

quyvinh said:
First I want to thanks emowing for his finding the brother of this Blu Vivo XL, it is Gionee Elife S Plus.
Whole thing: https://blog.hovatek.com/how-to-root-gionee-elife-s-plus/
Step1: Install Vcom Driver manually. This intend to use for the SP Flash tool to work.
https://forum.hovatek.com/thread-440.html
Step2: Run SP Flash tool to install CWM recovery.
https://forum.hovatek.com/thread-159.html
Step3: please do backup to excard (sdcard1) before install superSU.zip
Step4: root, by installing superSU using CWM.
*** Xposed:
Download the latest version of Xposed for sdk22 and arm64 from here. As of this writing it is xposed-v79-sdk22-arm64.zip. Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install xposed-v79-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Initial boot would take longer than normal, plus rebooted like five times during the "Android is starting" (orange color on white background) step but finally finished.
Once your phone boots up install XposedInstaller_3.0_alpha4.apk
Click to expand...
Click to collapse
I gave Xposed a try yesterday so that I could use Amplify. I started getting reboots when I started setting up Amplify. Did basically everything you said in this post. I think it had something to do with the 3.0 installer. Not sure though.
Sent from my VIVO XL using Tapatalk

ItGuyJax8430 said:
I gave Xposed a try yesterday so that I could use Amplify. I started getting reboots when I started setting up Amplify. Did basically everything you said in this post. I think it had something to do with the 3.0 installer. Not sure though.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
1. Make sure you have correct file of framework install in recovery.
2. Restart into android, then install xposed app
3. install amplify module.
Mine is running well. Tested and work with: Lucky Patcher, Greenify w/experiment.
However, not working: GravityBox.
*** Not all module is working for Android 5.1 ***
Sorry, my knowledge is limited, as I am still learning. 'Just want to share what I have. Thanks.

quyvinh said:
1. Make sure you have correct file of framework install in recovery.
2. Restart into android, then install xposed app
3. install amplify module.
Mine is running well. Tested and work with: Lucky Patcher, Greenify w/experiment.
However, not working: GravityBox.
*** Not all module is working for Android 5.1 ***
Sorry, my knowledge is limited, as I am still learning. 'Just want to share what I have. Thanks.
Click to expand...
Click to collapse
I used v80, maybe that was the issue. I'll give v79 a go and see if that fixes it.
Sent from my VIVO XL using Tapatalk

ItGuyJax8430 said:
I used v80, maybe that was the issue. I'll give v79 a go and see if that fixes it.
Sent from my VIVO XL using Tapatalk
Click to expand...
Click to collapse
make sure it is sdk22 arm64

quyvinh said:
make sure it is sdk22 arm64
Click to expand...
Click to collapse
Just installed, I'll keep you posted if I get reboots. I have Amplify installed as well with the default wakelock recommendations.
Sent from my VIVO XL using Tapatalk

Is Gionee Elife S Plus recovery fully working on Blu Vivo XL? need any modification on MT6753_Android_scatter.txt?
Saw a few people bricked Vivo XL, a little scared.

min1968 said:
Is Gionee Elife S Plus recovery fully working on Blu Vivo XL? need any modification on MT6753_Android_scatter.txt?
Saw a few people bricked Vivo XL, a little scared.
Click to expand...
Click to collapse
Please do not modify anything. To make it easy, Blu Vivo XL is the same Gionee Elife S Plus.
Tested. Worked. No need unlock bootloader.

In this linek: https://forum.hovatek.com/thread-159.html
it shows example selected checkboxs of recovery and android. Should we only select "recovery"?
quyvinh said:
Please do not modify anything. To make it easy, Blu Vivo XL is the same Gionee Elife S Plus.
Tested. Worked. No need unlock bootloader.
Click to expand...
Click to collapse

Recovery ONLY

quyvinh said:
Recovery ONLY
Click to expand...
Click to collapse
I flashed CWM recovery, enter it flashed supersu, and reboot, now it stopped at white screen with back "BLU Android" text.
Tried enter CWM recovery again, wipe data or cache, but always stay at "wipe cache...." screen. Have to remove battery to enter CWM recovery again...
What should I do now?
Can anybody upload CWM backup-ed ROM so I can restore?
---------- Post added at 03:46 PM ---------- Previous post was at 03:02 PM ----------
I wonder if this CWM recovery has something wrong. I tried to backup to builtin ROM, it says cannot backup; then I tried to back to MicroSD, after about 10 min it still says cannot backup, and also, my MicroSD cannot be recognized by any device (my PC, camera, and This phone itself anymore.

*** You are in soft brick now. As long as you can get into recovery, you are OK. Please find out how to change to TWRP, and flash the backup rom from this post. http://forum.xda-developers.com/vivo-xl/how-to/rom-warning-please-read-unlock-t3313857***
It sad to hear you are in problem. Did you do the step#3? Do nand backup before flashing superSU?
If you did, then you should have your own a ROM back up.
Moreover, I do not know how could you end up in this situation. Any one have the same problem? I need to gather all popular problem into one place and try to figure out the safeway.
I feel bad if more people have problem with this method. Honesty, I succeeded with this method. Then come here and share with all of you. Please do at your own risk. If I see more problem then I will turn my thread down.
min1968 said:
I flashed CWM recovery, enter it flashed supersu, and reboot, now it stopped at white screen with back "BLU Android" text.
Tried enter CWM recovery again, wipe data or cache, but always stay at "wipe cache...." screen. Have to remove battery to enter CWM recovery again...
What should I do now?
Can anybody upload CWM backup-ed ROM so I can restore?
---------- Post added at 03:46 PM ---------- Previous post was at 03:02 PM ----------
I wonder if this CWM recovery has something wrong. I tried to backup to builtin ROM, it says cannot backup; then I tried to back to MicroSD, after about 10 min it still says cannot backup, and also, my MicroSD cannot be recognized by any device (my PC, camera, and This phone itself anymore.
Click to expand...
Click to collapse

I have tWRP Recovery now.
There are 4 files in ROM backup folder, I merged two win.000 and win,001 files into one file as .win, how to deal with another win000.md5?
Putting 2 files(boot.emmc.win and merged system.ext4.win) in new SD card and restored, now always boot to tWPR recovery, cannot see "Blu Android " screen... and idea?
Thanks.
quyvinh said:
*** You are in soft brick now. As long as you can get into recovery, you are OK. Please find out how to change to TWRP, and flash the backup rom from this post. http://forum.xda-developers.com/vivo-xl/how-to/rom-warning-please-read-unlock-t3313857***
It sad to hear you are in problem. Did you do the step#3? Do nand backup before flashing superSU?
If you did, then you should have your own a ROM back up.
Moreover, I do not know how could you end up in this situation. Any one have the same problem? I need to gather all popular problem into one place and try to figure out the safeway.
I feel bad if more people have problem with this method. Honesty, I succeeded with this method. Then come here and share with all of you. Please do at your own risk. If I see more problem then I will turn my thread down.
Click to expand...
Click to collapse

can you redo with out merged?

Finally got my phone up.
I used tWRP restored without merge files, but still always boot to recovery. Then I flashed back to original recovery ; powered on, it went to factory recovery, from there I selected boot, it boot clean.
quyvinh said:
can you redo with out merged?
Click to expand...
Click to collapse

I am glad to know your phone is good now. Thanks for sharing.

I challenged again, now I get my Vivo XL rooted.
Basically I re-do OP's steps, except:
1, Use TWRP recovery image instead of CWM
(from this thread: http://forum.xda-developers.com/vivo-xl/how-to/rom-warning-please-read-unlock-t3313857)
2, after flashing recovery, enter TWRP to clear data.
No need unlock boot loader.
And I found it's actually had to really brick this phone, since you can easily switch recovery (TWRP, CWM and original), and fact is, original recovery + stock rom restore is always working.

This could work for the Blu Vivo 5? (Most of the specs are the same)

I can't for the life of me get any of my 3 computers (2 are Windows 10, one is Windows 7, all 3 are 64-bit) to recognize the phone using the VCOM drivers. I installed them as I believe I'm supposed to, prior to connecting it to the computer:
1.) Open Device Manager
2.) Right-click PC name
3.) Select "Add legacy hardware"
4.) Manually install drivers (I used /MediaTek USB VCOM drivers/USB VCOM Driver/Win7/usb2ser_Win764.inf)
5.) Select "MediaTek PreLoader USB VCOM Port" (it's been assigned to COM 8)
I get a notice that it's been installed correctly, but may not work (I assume because it's legacy / not verified) and it shows up in my list, but it has a yellow exclamation point. When plugging in the phone, it comes up as either MTP (also with a yellow exclamation point) or under Android Devices (or similar)...which one depends on the computer. And yes, I've tried restarting the computer before plugging it in.
In any case, I can almost always use ADB to get into the phone, but when running MTK Droid Tool Kit, it's never recognized. And when I run ADB using the Kit's included install, it never starts the ADB server (even after running kill-server / start-server / list devices).
Thoughts? The fact that y'all haven't had trouble makes me think I'm missing something obvious. Not sure what it is, though. Wrong driver?

I was finally able to install custom recovery (I used TWRP instead of CWM) and get the phone rooted using SuperSU, but the included instructions weren't clear enough for me. I'm not new to rooting and flashing, but I am new to Mediatek and maybe that's the problem. Or maybe it's just a reading comprehension fail on my part. Anyway, I uninstalled everything via USB Deview, restarted, installed VCOM drivers manually, restarted, removed battery and plugged phone in. Waited a few moments before running the SP Flash Tool.
One thing I didn't pick up on that this tutorial (http://www.guruswizard.com/2016/01/root-gionee-elife-s-plus-and-install-cwm-recovery.html) made clear was the location of the scatter file. I thought I was supposed to generate it myself. I replaced the CWM "recovery.img" with the TWRP one (kept the same name) so that when I loaded the scatter file, it would use TWRP instead of CWM.
I figure we're stuck with the stock ROM for now? Anyone aware of CM development for the Vivo XL or Elife S Plus?

Trouble with installing xposed (galaxy s4)

I have a Samsung Galaxy S4 (verizon SCH-I545) running android 5.0.1
I have already rooted my device using KingRoot
I have been trying to flash the xposed zip file for several days now and I'm not having any luck. I've tried a few different tools to flash but they all kick me to bootloader but fail to flash the zip. I get the following error when bootloader is verifying the update package:
Code:
E:footer is wrong
E:signature verification failed
I've tried putting the zip file on my device and on SD to see if that might help, but still no dice. Does anyone have suggestions or know what I'm doing wrong? I'm using the most recent zip from XDA (xposed-v86-sdk21-arm.zip updated 08-Jul-2016 15:25... I've also tried arter97's package and dkcldark's package as well as Magisk v1)

Deleted

Anyone have any suggestions?

Bump
Someone has to have some sort of suggestions I could try... would flashing a custom rom on do anything or is this related to the KNOX security stuff?

Are you using twrp? if so, did you turn off zip verification and md5 verification?

Nergal di Cuthah said:
Are you using twrp? if so, did you turn off zip verification and md5 verification?
Click to expand...
Click to collapse
i am using twrp manager 9.0 (from the play store) but i didn't see a place/option to disable the verification. is there a different app i should be using or am i overlooking something obvious?
edit: I've also tried CWM and i get the same errors

lordofbeond said:
i am using twrp manager 9.0 (from the play store) but i didn't see a place/option to disable the verification. is there a different app i should be using or am i overlooking something obvious?
edit: I've also tried CWM and i get the same errors
Click to expand...
Click to collapse
Not in manager in actual twrp

Nergal di Cuthah said:
Not in manager in actual twrp
Click to expand...
Click to collapse
I wasn't aware of the install twrp step which answers most of the questions I have about this.
I tried it and softbricked my device. Did a little more research and it looks like the kernel I have won't allow me to install TWRP. I'm trying to use verizion's recovery tool to downgrade/repair the device and I'll see if I can get this device rolled back and TWRP installed.
Thank you for the info, this gives me a launching point at least. I'll check back here if/when I get TWRP installed and I try to disable the validation.

This thread is probably your answer
lordofbeond said:
I wasn't aware of the install twrp step which answers most of the questions I have about this.
I tried it and softbricked my device. Did a little more research and it looks like the kernel I have won't allow me to install TWRP. I'm trying to use verizion's recovery tool to downgrade/repair the device and I'll see if I can get this device rolled back and TWRP installed.
Thank you for the info, this gives me a launching point at least. I'll check back here if/when I get TWRP installed and I try to disable the validation.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-framework-install-galaxy-s4-sch-t3425615

lordofbeond said:
I have a Samsung Galaxy S4 (verizon SCH-I545) running android 5.0.1
I have already rooted my device using KingRoot
I have been trying to flash the xposed zip file for several days now and I'm not having any luck. I've tried a few different tools to flash but they all kick me to bootloader but fail to flash the zip. I get the following error when bootloader is verifying the update package:
I've tried putting the zip file on my device and on SD to see if that might help, but still no dice. Does anyone have suggestions or know what I'm doing wrong? I'm using the most recent zip from XDA (xposed-v86-sdk21-arm.zip updated 08-Jul-2016 15:25... I've also tried arter97's package and dkcldark's package as well as Magisk v1)
Click to expand...
Click to collapse
Hola. i just did this on vz GS4 i545:
use FlashFire for everything. make sure you have a titanium backup of your apps and data for after you flash new ROM. here are the steps:
1. Flash Fire Zip or OTA stock of1 deodexed ROM from here: http://forum.xda-developers.com/gal...1-keeproot-t3182544/post62413212#post62413212
it will spend 10 to 15 minutes on the red Verizon splash screen.
2. reload from titanium at this point.
3. install xposed 3.0alpha4.apk from the xposed forum page.
4. flashfire zip or ota Arter97's xposed v65 sdk21 arm arter97 V5 krait.zip
this last step took about 35 minutes to upgrade all 260 plus apps i have.
make sure you have the proper uninstaller loaded too just in case. i put mine on the ext sd card in case i needed to load it from recovery. though that might not work because of the unsigned issue.