I rooted my z3c with Kingroot. Now trying to install TWRP from TWRP Manager app.
After download it says "Ensure the partition listed below ...." and says "/dev/block/platform/msm_sdcc.1/by-name/FOTAKernal"
Is that correct? Don't wanna brick...
Yes its correct, however i am not 100% sure kingroot works well with TWRP.
nzzane said:
Yes its correct, however i am not 100% sure kingroot works well with TWRP.
Click to expand...
Click to collapse
Well, TWRP flashed "successfully" but rebooting to recovery just caused a normal reboot.... with the whole "android optimizing" all apps thing...
I cannot seem to get into recovery.
d0g said:
Well, TWRP flashed "successfully" but rebooting to recovery just caused a normal reboot.... with the whole "android optimizing" all apps thing...
I cannot seem to get into recovery.
Click to expand...
Click to collapse
Yep happened to me, I believe kingroot does not allow full access to recovery, possibly.
nzzane said:
Yep happened to me, I believe kingroot does not allow full access to recovery, possibly.
Click to expand...
Click to collapse
So, what did you do? I'm on a Mac and haven't found a rooting guide.
d0g said:
So, what did you do? I'm on a Mac and haven't found a rooting guide.
Click to expand...
Click to collapse
I actually just gave up with that, used flashtool to get to firmware 23.0A.2.93 and used giefroot to root, and install TWRP from that.
Kingroot does root, but isn't the best, I would suggest you use giefroot if possible.
Related
Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.
twrp works, but SU binary still wont flash :/
edit - the combination of this APK and TWRP gave me all I need for root + rebooting and keeping root
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Steel01 said:
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Click to expand...
Click to collapse
So you were successful in getting TWRP installed, SuperSU installed and removing KingRoot clean - leaving only SuperSU on the system, surviving a reboot?
Ink Rampant Wolf said:
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
Click to expand...
Click to collapse
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
You might wanna include the instructions as shown here,
http://forum.xda-developers.com/xpe...how-to-root-lollipop-xperia-tablet-z-t3115107
It basically tells you how to install SuperSU and remove the entire KingRoot library after that. It worked on my Z and on my SHIELD as well.
This was essentially what I did:
http://greenrobotgamer.com/shieldzone/root-shield-portable-lollipop-5-1/
Mine seems to be working just fine, after obtaining root and installing SuperSU. I didn't bother with installing TWRP, I just hotboot the recovery. I'm rebooting my SHIELD as we speak, see if there's any issue
EDIT: Scractch that, it's not booting. How do I flash the latest image back in?
JCESAR2 said:
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
Click to expand...
Click to collapse
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Ink Rampant Wolf said:
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
JCESAR2 said:
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
Click to expand...
Click to collapse
You need to unlock your bootloader first.
ok long story short: since i had the shield drivers installed and tha adb drivers installed i did the oem unlock and after a confirmation screen on the shield i did it, then i immediately flashed the twrp image from the same command line. now the shield is stuck in nvidia android boot logo. any suggestions? thanks
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
JCESAR2 said:
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
Click to expand...
Click to collapse
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Ink Rampant Wolf said:
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
Guess I'll have to flash the old firmware then, it's been sitting there forever.
341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
JCESAR2 said:
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
Click to expand...
Click to collapse
I just re-flashed the system using RAM, should be fine now. I'll just have wait for the OTA all over again. UGH.
I wish someone could provide a KitKat version tho.
EDIT: Annnd battery's at 15% so the system won't let me OTA yet.
SuperSU will work fine with my latest TWRP builds posted here. The older 2.8.5.0 builds will not work, neither will any build in the linked thread before yesterday. I used SuperSU 2.49 Beta and it worked as expected.
Side Note: The older builds will have the problem where boot will just hang. That seems to be because the older builds didn't have selinux policies built in, so some things never get set up right and the boot panics.
I have tried via Flashify but cannot get it to work. I'm used to doing everything via TWRP but I know it is not an option at this time.
Any thoughts? How to install Xposed without TWRP? Currently on rooted ZV6.
happy_5 said:
I have tried via Flashify but cannot get it to work. I'm used to doing everything via TWRP but I know it is not an option at this time.
Any thoughts? How to install Xposed without TWRP? Currently on rooted ZV6.
Click to expand...
Click to collapse
Flashify only works if you have a custom recovery. AFAIK you can't flash the framework without it
Flashfire works without recovery.
LaughingCarrot said:
Flashfire works without recovery.
Click to expand...
Click to collapse
How can you flash a zip without recovery.
Wj287 said:
How can you flash a zip without recovery.
Click to expand...
Click to collapse
That's the exact reason Flashfire was made.
Got it working!
I was able to get it done via Flashfire. A bit difficult to find the app initially, but WORKS like a CHARM! Rooted with Xposed, fully working and tweaked to the gills.
I don't know if it is against the rules to post the Flashfire link.
happy_5 said:
I have tried via Flashify but cannot get it to work. I'm used to doing everything via TWRP but I know it is not an option at this time.
Any thoughts? How to install Xposed without TWRP? Currently on rooted ZV6.
Click to expand...
Click to collapse
Follow the instructions on this thread:
http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593
In addition you can download v79 instead of v74 as the instructions suggest and it will work fine.
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Rentom said:
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Click to expand...
Click to collapse
flash any custom kernel to get rid of that message
simms22 said:
flash any custom kernel to get rid of that message
Click to expand...
Click to collapse
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Rentom said:
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Click to expand...
Click to collapse
because google put it there, it is new.
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah I let twrp root it when it asked when I did it two months ago. Was that a bad thing? I thought I read that it was if you were rooting 6.0.1, but I was rooting 6.0 so I decided to see what would happen, and it went smoothly.
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I see. Makes sense. Alright, thanks. I already did flash it back to stock to update to 6.0.1, so I'm not sure why you told me to flash it back to stock and then install su 2.67.
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Mongo23ny said:
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Click to expand...
Click to collapse
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
simms22 said:
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
Click to expand...
Click to collapse
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Mongo23ny said:
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Click to expand...
Click to collapse
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Tried flashing twrp a couple of times, went back to stock recovery and then twrp. No luck. Also, phone will not boot with custom recovery only with stock. Not sure if I tried 3.0.0.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0?
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
no, do not keep system read only, ever.
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
Thanks for all your help, did a clean install, fastboot flashed 6.01. I had gotten that corrupt phone message when I rebooted again but I took some security update and that got rid of the message. I flashed twrp 3.0.0.0 and SuperSU 2.67 and got root back. No worries, thx again.
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
If you are using the systemless root method then yes, you do want to keep system read only.
alryder said:
If you are using the systemless root method then yes, you do want to keep system read only.
Click to expand...
Click to collapse
I kept it in read only, installed SuperSU 2.67 in twrp.
Is there any way to root without TWRP? I'll be doing this for a family member, and want to keep it as stock as possible. I just want root to remove some stock apps they don't need, then probably unroot. Is there any way to do so? Otherwise I was thinking of flashing TWRP, rooting, then flashing back the stock recovery.
Purplezigar said:
Is there any way to root without TWRP? I'll be doing this for a family member, and want to keep it as stock as possible. I just want root to remove some stock apps they don't need, then probably unroot. Is there any way to do so? Otherwise I was thinking of flashing TWRP, rooting, then flashing back the stock recovery.
Click to expand...
Click to collapse
You can boot into twrp.
Use "fastboot boot twrp-recovery-file location"
Then you can just use the root shell from twrp to make changes, no need to flash SuperSU if you want the ROM unrooted.
mrmazak said:
You can boot into twrp.
Use "fastboot boot twrp-recovery-file location"
Then you can just use the root shell from twrp to make changes, no need to flash SuperSU if you want the ROM unrooted.
Click to expand...
Click to collapse
I'm not quite sure what you're saying, but it sounds like you're saying that I can boot into the TWRP image while I'm connected with fastboot, without actually installing TWRP?
Purplezigar said:
I'm not quite sure what you're saying, but it sounds like you're saying that I can boot into the TWRP image while I'm connected with fastboot, without actually installing TWRP?
Click to expand...
Click to collapse
That's right. You can just boot twrp instead of flashing it.
And when twrp is booted you can connect to phone with adb, you will have a shell with root privileges.
mrmazak said:
That's right. You can just boot twrp instead of flashing it.
And when twrp is booted you can connect to phone with adb, you will have a shell with root privileges.
Click to expand...
Click to collapse
Cool! So then I can just remove system installed apps that I don't want (e.g. Google Play Movies and Books)?
Purplezigar said:
Cool! So then I can just remove system installed apps that I don't want (e.g. Google Play Movies and Books)?
Click to expand...
Click to collapse
You could also read this thread as see if the twrp packages there are what you want to do.
They can all be run from the booted twrp.
https://forum.xda-developers.com/r1-hd/how-to/guide-ad-removal-debloat-block-ota-easy-t3429555
mrmazak said:
You could also read this thread as see if the twrp packages there are what you want to do.
They can all be run from the booted twrp.
https://forum.xda-developers.com/r1-hd/how-to/guide-ad-removal-debloat-block-ota-easy-t3429555
Click to expand...
Click to collapse
Awesome, thanks!
Yes, I was aware this could happen. Yes I read the warning thread. This is MY fault. I got to step 12 on this tutorial: https://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
and now I can't get into recovery/ and its bootlooping. What do I do? Computer makes a noise when it boot loops so its being recognized. Phone was running marshmallow.
Fixed, nevermind.
Anyone who is concerned about this and it should be everyone. Rashr app will backup in an flashable .IMG file both Kernel and stock recovery so long as you've rooted and have an app to manage the sun requests, ie Superuser King root, etc.
Suggested that before you flash TWRP use it for emergencies or for updating. Skirts having to use the flash tool frp (sp?) Vcom and windows 7
WiddleyScudds said:
Fixed, nevermind.
Click to expand...
Click to collapse
How did you fix it? I'm having the same loop problem.
Surmoka said:
How did you fix it? I'm having the same loop problem.
Click to expand...
Click to collapse
Sorry, don't use this phone anymore. Best of luck