Related
[Q][ME176CX] Any new news about unlocking bootloader and installing CWM Recovery?
I'm wondering if there are any new news/hacks/exploits/methods to unlock the bootloader on the ASUS Memo Pad 7 (ME176CX) to install ClockworkMod or any other Recovery Menu on it.
I really really need a working Recovery Menu installed, so I can undo critical system changes (eg: Xposed) if the device ends up bootlooping...
EDIT: I googled days long to find a solution, before opening this thread here
GhettoGirl said:
I'm wondering if there are any new news/hacks/exploits/methods to unlock the bootloader on the ASUS Memo Pad 7 (ME176CX) to install ClockworkMod or any other Recovery Menu on it.
I really really need a working Recovery Menu installed, so I can undo critical system changes (eg: Xposed) if the device ends up bootlooping...
EDIT: I googled days long to find a solution, before opening this thread here
Click to expand...
Click to collapse
Hi,
do you know of the "temporary cwm" or "temporary recovery method" here? How did you root your device?
And: To get out of a bootloop caused by one of the XPosed-Modules you only need a working adb connection.
Before installing XPosed, check, whether you can connect to your tablet via adb. If yes and you get into a bootloop,
simply open a adb shell and you will be able to edit the filesystem.
And maybe what is tried in this thread
http://forum.xda-developers.com/memo-pad-7/help/asus-memopad-7-me176cx-getting-linux-t3164705
may lead to a way to boot other things than Android on this wonderful tablet - that is may be twpr and cwm are
in reach.
HTH!
Best regards,
tuxic
thanks for the replay
tuxic001 said:
How did you root your device?
Click to expand...
Click to collapse
i've rooted my device with ROOT ZenFone, worked like a charm at the first try
tuxic001 said:
do you know of the "temporary cwm" or "temporary recovery method" here?
Click to expand...
Click to collapse
i've heard of that temporary recovery method, but i prefer a permanent one which can be accessed with POWER+HOLD VOL-. what are exactly the differences between a temporary and a permanent one, do you need to install this every time you need it? or how i can understand this.
tuxic001 said:
check, whether you can connect to your tablet via adb. If yes and you get into a bootloop,
simply open a adb shell and you will be able to edit the filesystem
Click to expand...
Click to collapse
what i understand about bootloops is, that the device does a full restart after unable to start android, which would disconnect the adb shell. or did i got somethig wrong here?
tuxic001 said:
And maybe what is tried in this thread
http://forum.xda-developers.com/memo-pad-7/help/asus-memopad-7-me176cx-getting-linux-t3164705
Click to expand...
Click to collapse
i know about this, but it's not finished yet. the power button for example cannot be used to confirm for example, which would be useless on-the-go. (how has a keyboard all the time :silly: )
http://forum.xda-developers.com/memo-pad-7/help/how-to-dual-boot-me176cx-part-1-t3183437
sorry for all the questions, but i got this device 2 days ago and i don't know anything whats going on under to hood - and no: i'm not a android/linux noob - i just won't full brick my device
and also, what about a nandroid backup over adb, is there a legit way to archive this?
thanks in advance
EDIT: i tried the temporary recovery, but i'm unable to do any kind of backup. maybe the paths are all incorrect (?)
anyway, i took the risk of a bootloop and installed the xposed framework and succeed
i also found out that i can try to "stop" android before it bootloops again -> adb -d shell stop and do a manually restore over the command line
GhettoGirl said:
thanks for the replay
i've rooted my device with ROOT ZenFone, worked like a charm at the first try
i've heard of that temporary recovery method, but i prefer a permanent one which can be accessed with POWER+HOLD VOL-. what are exactly the differences between a temporary and a permanent one, do you need to install this every time you need it? or how i can understand this.
what i understand about bootloops is, that the device does a full restart after unable to start android, which would disconnect the adb shell. or did i got somethig wrong here?
i know about this, but it's not finished yet. the power button for example cannot be used to confirm for example, which would be useless on-the-go. (how has a keyboard all the time :silly: )
http://forum.xda-developers.com/memo-pad-7/help/how-to-dual-boot-me176cx-part-1-t3183437
sorry for all the questions, but i got this device 2 days ago and i don't know anything whats going on under to hood - and no: i'm not a android/linux noob - i just won't full brick my device
and also, what about a nandroid backup over adb, is there a legit way to archive this?
thanks in advance
EDIT: i tried the temporary recovery, but i'm unable to do any kind of backup. maybe the paths are all incorrect (?)
anyway, i took the risk of a bootloop and installed the xposed framework and succeed
i also found out that i can try to "stop" android before it bootloops again -> adb -d shell stop and do a manually restore over the command line
Click to expand...
Click to collapse
Hi GhettoGirl,
(first of all: I am no native English speaker...so some things may sound wrong either technically or otherwise.
But they are not intended to do so.... )
I started with my ME176CX not long ago and I am still a newbie when it comes Android (haveing some experience in Linux though). Mis012 and cyandro helped me a
LOT to get more understanding and to root my tablet.
I rootet my ME176CX with the temporary cwm/twpr recovery method, which does other wonderful things possible too.
You will find links to its description here (a BIG thank you to cyandro and Mis012) and it is the thread from which I learned
so much:
http://forum.xda-developers.com/memo-pad-7/help/asus-memopad-7-me176cx-1e041a-otg-t3156922
(The title of the thread becomes a little misleading in the meanwhile...)
The base problem (currently) with this tablet is: The bootloader is locked.
This means:
If you power on the tablet roughly the following steps happens:
1) The CPU gets power, erases its own internal RAM and registeres, does some other initializing
and finally executes a super mini mini program, which is often in its own ROM.
2) This little program call UEFI (its kinda "BIOS replacement" -- think of the BIOS screen of PCs when pressing F2/ESC/DEL while booting)
3) The UEFI looks into its configuration and calls the bootloader.
4) Finally boots the Android Linux kernel BUT only a kernel which is cryptographically "signed" by ASUS. Thats why it is called "locked".
By the way: You can get into UEFI, if you attach a powered OTG hub and an USB keyboard to the tablet, power it up and hammering "F2" while
it boots. Be careful! For the first: Dont change anything!
A permanent TWPR/CWM is possible, if the bootloader would boot TWPR/CWM as a kind of "kernle replacement". But since both are not
signed by ASUS...sigh.
The temporary CWM/TWPR method (and now some not-so-sure-knowledge follows) tricks the bootloader (called "fastboot") in thinking, that some
factory maintenance has to be done (like partitioning the EMMC internal flash) and therefore allows to insert a not signed boot image temporarly
into the system and boot that instead of the kernel: And if these "recovery images" are not recovery images as such but say TWPR or cwm, the
system boots into those.
And it feels and act identical (until now I did not find a difference) to a permanent TWPR/CWM recovery ... but it only can be initiated with the help of
a seconde computer (or another Android smartphone/tablet with is rooted and has a Terminal Emulator and adb/fastboot installed.
Bootloops: You are completly right here, GhettoGirl...as long the power is there, it boot loops and boot loops and....
But you already found your way into the system: COOL!
WIth the same temporary twpr/cwm method you can start TWPR and do an Nandroid backup (whole system backup) and put that onto
the external SDcard.
BUT! ATTENTION! I dont know, whether the kind of EMMc flash is important in this process, and I dont know, wheter TWPR currently don't supports
the ME176CX. The locked bootloader may the reason or an incompatible/currently not supported EMMc flash. I did a Nandroid backup but I dont test
to restore it!
I dont understand, why it does not work for you: Of what size are your SDcard?
Another way, which may be better in this moment is to backup all user data with Titanium Backup to the external SDcard. If anything fails: Reflash the last
Lollipop ROM (not the upgrade...the whole thing) with the temporary TWPR/CWM method and then install Titanium backup again and restore all user data.
This way was also NOT tested by me.
May be someone can comment on this? Mis012? Cyandro?
What Mis012, cyandro and me are trying to to do is to insert an UEFI bootmanager in the boot sequence BEFORE the locked bootloader. With this bootmanager
it should be possible to select either another Linux kernel (another non-locked bootloader) to boot a free and open Linux distro of your choice or even things
like Windows...or TWPR/CWM or Cyanogenmod (if one will be available...)
Since this is a work in progress with some real problems to clearify, this is currently not finished.
And: Only questions will lead to answer. Therefore: ASK!
And I have also a question: Do you use Linux or Windows with your PC?
HTH!
Best regards,
tuxic
thanks for the useful info ?
and i'm a pure linux user, i literally don,t know anything about windows
my current distro is opensuse x86_64
GhettoGirl said:
thanks for the useful info
and i'm a pure linux user, i literally don,t know anything about windows
my current distro is opensuse x86_64
Click to expand...
Click to collapse
...me too. The only windows here are those made of glass...
Have fun!
tuxic
Please excuse me if this is a simple process, but I cannot seem to locate a thread on how to flash to -44, as I am slowly in the process of trying to root my Turbo.
Currently living off of FoxFi USB tethering, but finally would like to obtain root access since it is available as I miss having wifi tethering!
I'd like to add, that the process of rooting this phone is a bit more advanced than what I have done over the years. I'm used to plugging the phone in the PC, installing a software on the PC, then "one click" root and reboot.
Any insight or recommendations is greatly appreciated! Tethering is my main reason for root, but I'd still like the versatility of having root access.
Thanks XDA!
coconutt said:
Please excuse me if this is a simple process, but I cannot seem to locate a thread on how to flash to -44, as I am slowly in the process of trying to root my Turbo.
Currently living off of FoxFi USB tethering, but finally would like to obtain root access since it is available as I miss having wifi tethering!
I'd like to add, that the process of rooting this phone is a bit more advanced than what I have done over the years. I'm used to plugging the phone in the PC, installing a software on the PC, then "one click" root and reboot.
Any insight or recommendations is greatly appreciated! Tethering is my main reason for root, but I'd still like the versatility of having root access.
Thanks XDA!
Click to expand...
Click to collapse
THIS METHOD WILL VOID YOUR WARRANTY. But if you're on xda, chances are you knew that. It's also irreversible.
If you're not unlocked and not rooted, take the OTA that is available to get you to -44. 44 is the most recent version available, so there is no risk of updating too far.
Once you're on 44, download the Kingroot apk and install it. http://www.kingroot.net/
Then download this version of Sunshine and install it. http://forum.xda-developers.com/showpost.php?p=64027688&postcount=4064
Once both are installed, open Kingroot and follow the instructions to try and get temporary root. It doesn't always work, and sometimes you have to try multiple times. If it fails, uninstall Kingroot, reboot the phone and try again. Wiping cache in the recovery menu sometimes helps too.
After Kingroot says it is successful, run Sunshine and follow the prompts. Sunshine costs $25, so if you're not cool with that, don't try this method. If Sunshine succeeds, your phone will reboot and instead of the Motorola M that you usually see at boot, you'll see a bootloader unlocked warning message. If Sunshine fails, uninstall Kingroot, reboot, reinstall and try again.
Once your bootloader is unlocked, you need to get a custom recovery installed (TWRP), which you can get here http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308. The easiest way to flash that in my opinion is with Fastboot. The easiest way to install Fastboot is by installing this: http://forum.xda-developers.com/showthread.php?t=231779. You'll also need to make sure you have the appropriate drivers so that your PC will recognize your phone. This will ensure that: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Put the TWRP .img file that you downloaded into the folder that you installed Minimal ADB and Fastboot to, boot your phone in bootloader mode, plug it in to the computer, start Minimal ADB and Fastboot, and type the following command:
fastboot flash recovery <name of TWRP .img file>
Once you have that, the sky is the limit. If you only want to add permanent root to your phone, download this: http://forum.xda-developers.com/showthread.php?t=1538053, put it somewhere on your phone, boot into recovery mode (which will now be TWRP instead of the stock recovery), select install, navigate to the .zip file and flash it. That's it. If you want to try cyanogenmod or any other custom rom, see their respective xda threads for details.
Oh, and as for enabling tethering for free, which is only necessary if you have an unlimited data plan (if not, it's free already, just use Verizon's app to do it), find any root browser, search for a file called build.prop, open it with the browser's text editor and add this line to the end of it:
net.tethering.noprovisioning=true
Remember to save when you're done.
---------- Post added 7th December 2015 at 12:00 AM ---------- Previous post was 6th December 2015 at 11:45 PM ----------
If you need more help, this guy might explain better than I did: http://forum.xda-developers.com/droid-turbo/general/videos-tutorials-root-restoring-droid-t3076456
http://forum.xda-developers.com/showthread.php?t=2317790
Link for minimal adb and fastboot, I think this is the right one?
TheSt33v said:
THIS METHOD WILL VOID YOUR WARRANTY. But if you're on xda, chances are you knew that. It's also irreversible.
If you're not unlocked and not rooted, take the OTA that is available to get you to -44. 44 is the most recent version available, so there is no risk of updating too far.
Once you're on 44, download the Kingroot apk and install it.
Oh, and as for enabling tethering for free, which is only necessary if you have an unlimited data plan (if not, it's free already, just use Verizon's app to do it), find any root browser, search for a file called build.prop, open it with the browser's text editor and add this line to the end of it:
net.tethering.noprovisioning=true
Remember to save when you're done.
Click to expand...
Click to collapse
Sorry for the late reply as I'm having the free time to fidget with the phone.
To my understanding about taking the OTA that is available to me is not the Marshmallow update? I have a screenshot of the OTA when it pops up each night, but not sure if I'm allowed to img code it on here. But it displays "New version: 23.21.44.en.US"... I'd just like for you to confirm that this is the -44 update before I advance, thanks a bunch!
Also, I tried the buildprop edit on my current -39 version and it won't let me save the file. I take it this can be done after rooting though.
coconutt said:
Sorry for the late reply as I'm having the free time to fidget with the phone.
To my understanding about taking the OTA that is available to me is not the Marshmallow update? I have a screenshot of the OTA when it pops up each night, but not sure if I'm allowed to img code it on here. But it displays "New version: 23.21.44.en.US"... I'd just like for you to confirm that this is the -44 update before I advance, thanks a bunch!
Also, I tried the buildprop edit on my current -39 version and it won't let me save the file. I take it this can be done after rooting though.
Click to expand...
Click to collapse
Yep. That's it. The marshmallow update isn't out yet, so it cannot be the marshmallow update. Build.prop is located on the system partition, which is write-protected on a stock Turbo. Once you unlock with Sunshine (just rooting with Kingroot isn't good enough), you will be able to edit it. Also, Sunshine no longer needs Kingroot. Simply download the latest version here http://theroot.ninja/download.html and use it to unlock once you're on -44.
TheSt33v said:
Yep. That's it. The marshmallow update isn't out yet, so it cannot be the marshmallow update. Build.prop is located on the system partition, which is write-protected on a stock Turbo. Once you unlock with Sunshine (just rooting with Kingroot isn't good enough), you will be able to edit it. Also, Sunshine no longer needs Kingroot. Simply download the latest version here therootdotninja/download and use it to unlock once you're on -44.
Click to expand...
Click to collapse
Well that was easy! Bootloader unlocked!! Thanks.
Now on to the rooting process. Currently getting my Moto drivers updated on the PC, and I've also downloaded the TWRP file onto the PC as well. As for Fastboot, the link you've provided takes me to a 2005 thread! I'm sure I can find a link to Fastboot to download, but I wanna make sure I get the one I need, if that makes any sense? (Don't mind me being paranoid)
TheSt33v said:
Put the TWRP .img file that you downloaded into the folder that you installed Minimal ADB and Fastboot to, boot your phone in bootloader mode, plug it in to the computer, start Minimal ADB and Fastboot, and type the following command:
fastboot flash recovery <name of TWRP .img file>
Click to expand...
Click to collapse
For an update, I got everything I needed downloaded. I am stuck at this point though, as I can't get passed this point when I input the above command!
EDIT:
I skipped the recovery flash, and went ahead with just the build prop edit for tethering after installing King Root. Rebooted it and still have root, and tethering works. Thanks a bunch!!
coconutt said:
For an update, I got everything I needed downloaded. I am stuck at this point though, as I can't get passed this point when I input the above command!
EDIT:
I skipped the recovery flash, and went ahead with just the build prop edit for tethering after installing King Root. Rebooted it and still have root, and tethering works. Thanks a bunch!!
Click to expand...
Click to collapse
If you want twrp flashify works well.
Hello all. First time posting on the forum. I've looked up on how to root the Moto x 2nd gen, but most I find is for the xt1095. I've read some information on how to unlock the bootloader for the xt1097 (I'm on AT&T). But it all just seems so confusing. I can't seem to find a source that has all the information I need all in one. I've found info from different sources but I don't wanna mess anything up by miss connecting the dots. If anyone has had success or knowledge on how to root this type of phone, I'd be very grateful! Thank you!
USA1791 said:
Hello all. First time posting on the forum. I've looked up on how to root the Moto x 2nd gen, but most I find is for the xt1095. I've read some information on how to unlock the bootloader for the xt1097 (I'm on AT&T). But it all just seems so confusing. I can't seem to find a source that has all the information I need all in one. I've found info from different sources but I don't wanna mess anything up by miss connecting the dots. If anyone has had success or knowledge on how to root this type of phone, I'd be very grateful! Thank you!
Click to expand...
Click to collapse
Hey, welcome to our forum.
You can use Kingroot (a one click root app) to root your at&t xt1097.
Then, if you want to unlock the bootloader, you can do it ONLY with sunshine app (an app that unlocks the bootloader, simple either), but in order to use sunshine app you need to pay for license or something like that, about 20-25$.
Sunshine works only if you have root, so you have to use kingroot.
Kingroot will not always work, but it should. Use it until it works, many reported it took them more than once.
That happens because you don't have offical bootloader unlock.
Have fun
OrenGazala said:
Hey, welcome to our forum.
You can use Kingroot (a one click root app) to root your at&t xt1097.
Then, if you want to unlock the bootloader, you can do it ONLY with sunshine app (an app that unlocks the bootloader, simple either), but in order to use sunshine app you need to pay for license or something like that, about 20-25$.
Sunshine works only if you have root, so you have to use kingroot.
Kingroot will not always work, but it should. Use it until it works, many reported it took them more than once.
That happens because you don't have offical bootloader unlock.
Have fun
Click to expand...
Click to collapse
Hey thank you for the information!! On the kingroot it said my phone was rooted, but then once I tried to do sunshine app, it said my phone was not rooted so I couldn't do that. Any idea why that is? Also, is kingroot and sunshine app the only thing I have to do? Or is after the bootloader unlocked there's other steps I must take to root the phone?
Was finally able to get kingroot to work and sunshine to unlock the bootloader after I did a factory reset. Now I'm confused as whats next. I read something about twrp and flashing logo?
I'm not trying to unlock the bootloader, only root the phone. KingRoot says "root successful," I download supersu, and it says my root binary (or something) isn't installed. However, SuperSu isn't able to install the binary for me.
An even worse problem: after KingRoot says "root successful" I check RootChecker, and it tells me I am NOT rooted. Also, every time I reboot, KingRoot claims I am not rooted. This makes me think that KingRoot incorrectly thinks it's rooted my phone. Because no other app seems to think I'm rooted, and when I reboot not even KingRoot thinks I'm rooted.
Finally, many of the KingRoot tutorials (as well as the app itself) say that KingRoot will likely reboot your phone a few times before it roots, and that after it roots it your phone will reboot. However, KingRoot has never rebooted my phone ONCE. This also adds evidence to my hypothesis that KingRoot incorrectly thinks it's rooting me. When I run KingRoot, it tells me not to be afraid if my phone reboots; well I am afraid because my phone is NOT rebooting.
Vegerot said:
I'm not trying to unlock the bootloader, only root the phone. KingRoot says "root successful," I download supersu, and it says my root binary (or something) isn't installed. However, SuperSu isn't able to install the binary for me.
An even worse problem: after KingRoot says "root successful" I check RootChecker, and it tells me I am NOT rooted. Also, every time I reboot, KingRoot claims I am not rooted. This makes me think that KingRoot incorrectly thinks it's rooted my phone. Because no other app seems to think I'm rooted, and when I reboot not even KingRoot thinks I'm rooted.
Finally, many of the KingRoot tutorials (as well as the app itself) say that KingRoot will likely reboot your phone a few times before it roots, and that after it roots it your phone will reboot. However, KingRoot has never rebooted my phone ONCE. This also adds evidence to my hypothesis that KingRoot incorrectly thinks it's rooting me. When I run KingRoot, it tells me not to be afraid if my phone reboots; well I am afraid because my phone is NOT rebooting.
Click to expand...
Click to collapse
Vegerot,
KingRoot accomplishes what's called a temp root (temporary root). After you reboot your phone, the temp root files will be deleted and you will not have root anymore. Also, installing a SuperSu binary will not work with a temp root. If you want to perm root your phone (permanent root), you will need to use KingRoot to root your phone (may take a couple of tries) and then you will need to use Sunshine to unlock your bootloader. After it is unlocked, you can flash a custom recovery and install the SuperSu binary.
Secondly, I've had that problem before. I would recommend using the PC version first, (which is in Chinese, but is easy to figure out) which will attempt the root, and if that doesn't work, use the phone version right after using the computer one. As I mentioned before, KingRoot is a temporary root that goes away after a reboot.
Lastly, usually reboots are not a measure of success. When I rooted, I did not reboot that often, so you should not be worried. If you think that something is not working, again, use the PC version; it seems to have a better success rate.
Contact me if you need any help.
R55770 said:
Vegerot,
KingRoot accomplishes what's called a temp root (temporary root). After you reboot your phone, the temp root files will be deleted and you will not have root anymore. Also, installing a SuperSu binary will not work with a temp root. If you want to perm root your phone (permanent root), you will need to use KingRoot to root your phone (may take a couple of tries) and then you will need to use Sunshine to unlock your bootloader. After it is unlocked, you can flash a custom recovery and install the SuperSu binary.
Secondly, I've had that problem before. I would recommend using the PC version first, (which is in Chinese, but is easy to figure out) which will attempt the root, and if that doesn't work, use the phone version right after using the computer one. As I mentioned before, KingRoot is a temporary root that goes away after a reboot.
Lastly, usually reboots are not a measure of success. When I rooted, I did not reboot that often, so you should not be worried. If you think that something is not working, again, use the PC version; it seems to have a better success rate.
Contact me if you need any help.
Click to expand...
Click to collapse
Thank you! Is it possible to use the TempRoot to remove bloatware?
Vegerot said:
Thank you! Is it possible to use the TempRoot to remove bloatware?
Click to expand...
Click to collapse
Yep. In the KingRoot app, after you have successfully rooted, you can uninstall the bloat apps.
---------- Post added at 07:47 PM ---------- Previous post was at 07:44 PM ----------
USA1791 said:
Was finally able to get kingroot to work and sunshine to unlock the bootloader after I did a factory reset. Now I'm confused as whats next. I read something about twrp and flashing logo?
Click to expand...
Click to collapse
After I unlocked my bootloader, I first flashed TWRP through the bootloader. I then did a full backup and installed a ROM. Flashing a LOGO is optional as it only changes the logos before the actual boot animation.
Contact me if you need any help with flashing or anything else.
After unlocking the bootloader, I'm having trouble installing Marshmallow. I tried following this tutorial but it hasn't helped either. This is my problem with that tutorial:
"When I run "fastboot flash system..." I'm stuck on "waiting for devices." Also, "fastboot devices" returns nothing. However, adb devices returns my phone.
Also, instead of system.img, the download link you provided gave me boot.img (along with a META-INF and system folder).
When entering TWRP, why must we go through that bootloader interface? I just do "adb reboot recovery" and that also opens TWRP.
Since fastboot isn't working, is there a way to do it through the TWRP GUI? Such as copying the file to my phone and then doing something with that?
Something strange happened. I decided to download the Marshmallow .zip on my phone, then booted into recovery and went to Install, and selected that file. I thought I would get an error (I'm trying to flash my phone from a file stored on my phone (therefor deleting itself)), but I didn't. I rebooted and all my apps were still there from before and my background, but the settings app says I'm running Android 6.0. What exactly happened?
There are some unexpected things happening though. For examples, I cannot swipe down with 2 fingers to access my quick settings In addition, the home button will not take me back to my app launcher (I have to tap the multitasking button THEN tap the home button to return to the launcher). When I look at my notifications, it still says "AT&T" at the bottom. Is that supposed to happen? This doesn't feel right and I would like to use the method you recommended in the article, but for now this is the only thing that will work.
"
????
Kingroot not works on my moto x 2nd gen xt1097 at&t ... How it works??
Como ser root
Ver contraseñas
As most of you know already from my other postings, I have a Verizon Xperia Z4V.
I have the dreaded bootloader unlock allowed = no at the moment (even though I have a Sony Dev. fastboot unlock code from their web tool)so am looking for a method to root the phone so I can extract the cdma radio and uhd screen drivers and use various other kernel sources to compile new ROM's
I have fastboot, and adb access.
So far, NOTHING has worked. Flashtool has come closest with the service menu exploit, however I cannot re-create what it did the first time.
The device is using 5.0.2 with kernel version : 3.10.49-perf-g301bca8-01952-g67d95bb / Platform : 64bits / Build number : 28.0.E.0.570
I know the device is NOT directly supported by any scripts, but it seems to me something should work from a similar device. After all, the only differences are the cdma radio and the screen resolution.
Any ideas?
Rick
BlackIce
https://www.xda-developers.com/root/
Choose your poison
That page is very useful. But as I mentioned the Z4V isn't listed at all.
Rick
BlackIce
Aha! Even though I am not abig fan of KingRoot, I managed to get version 5.3.0 to root the Z4V. Sort Of.
Sort Of? Well, I have Flashtool running on my PC and all drivers working. KingRoot runs and achieves root. Flashtool then recognizes root and pushes files and deactivates RIC. Then I get a crash or reboot on the phone, when it returns, root is gone.
Any ideas how to get it done?
RIck
BlackIce000
If i can get root for 15 seconds is there anyway i can flash a recovery or defeat RIC so I can keep it and begin to work on this phone??
Thanks,
Rick
blackice000 said:
If i can get root for 15 seconds is there anyway i can flash a recovery or defeat RIC so I can keep it and begin to work on this phone??
Thanks,
Rick
Click to expand...
Click to collapse
15 or 30 seconds is a bit short in time ...
Prophylaxis is key first (not breaking anything): create a backup of the kernel image/partition
https://android.stackexchange.com/q...img-and-recovery-img-from-sony-xperia-e4-dual (that example is with a MediaTek chipset so mostly different still a good starting point though)
you need to find out which partitions contain what data and create a dump / dd image as a backup of boot.img
https://github.com/lygstate/lygstat...10-Extract-boot.img-from-an-android-device.md
https://stackoverflow.com/questions/26967862/how-to-make-an-image-of-android-partition-to-your-pc
blackice000 said:
As most of you know already from my other postings, I have a Verizon Xperia Z4V.
I have the dreaded bootloader unlock allowed = no at the moment (even though I have a Sony Dev. fastboot unlock code from their web tool)so am looking for a method to root the phone so I can extract the cdma radio and uhd screen drivers and use various other kernel sources to compile new ROM's
I have fastboot, and adb access.
So far, NOTHING has worked. Flashtool has come closest with the service menu exploit, however I cannot re-create what it did the first time.
The device is using 5.0.2 with kernel version : 3.10.49-perf-g301bca8-01952-g67d95bb / Platform : 64bits / Build number : 28.0.E.0.570
I know the device is NOT directly supported by any scripts, but it seems to me something should work from a similar device. After all, the only differences are the cdma radio and the screen resolution.
Any ideas?
Rick
BlackIce
Click to expand...
Click to collapse
Just a small thing you may forgot, USB debugging mode to be on (for non carrier specific Z4) and you can use Flashtool for unlocking bootloader.
Before unlocking bootloader, take backup of DRM keys and important data.
New info. I can get root with Kingroot...I can manipulate using Flashtool. RIC is deactivated...after a short while phone reboots.
Any ideas?!! I'd really like to be able to use this phone.
Flashtool LOGFILE Attached
Rick
Hi all,
I am trying to relock the bootloader on 3T, with no success. I want to do it because of too many apps nagging me or not working with unlocked bootloader
here's what I did to unlock in the past and relock:
unlocking:
- enable dev options, enable oem unlocking & usb debugging
- flashed TWRP & fastboot oem unlock from command line (don't remember which I did first)
- got my phone wiped which was an an unexpected surprise!
- bootloader unlocked, the fist of those lovely warning screens telling me so
- tried to root without success, so no custom ROMs for me
- lived with it like this for a while, too many apps telling me they won't work, decided to relock
- got latest stock ROM, flashed it via TWRP, wiped, tried to fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- flashed just the 3t recovery img, wiped, fastboot oem lock ==> success reported by CLI, BUT device still unlocked
- tried the qualcomm unbrick tool after installing the recommended drivers, can't have it see my device maybe because it's not bricked or maybe some other reason, I don't know. it doesn't show up in the app. Will uninstall and reactivate driver signature checks soon unless someone explains me how to make the bloody phone show up ...
So at this moment I have a many times-wiped phone with latest 9.0.4 stock ROM whose bootloader won't lock back. I am quite at a loss. I haven't tried any magisk or similat, SuperSU at the time told me I am not rooted.
I am tearing out the few hairs I have left. Any help for this poor family man so that he may not be allowed to walk in darkness? (quote from Uninvited). Thanks
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
pitrus- said:
Why don't you use Magisk hide to hide root/unlock status to those apps instead of loosing root/adaway and more?
Click to expand...
Click to collapse
I have never investigated Magisk, I think I installed it at the tima but there was some problem with it so I uninstalled it and didn't think much more about it. The problem is, my phone is not rooted (even though I tried it failed, I unlocked the bootloader to root it in the first place but was not successful), only OEM unblocked. So, so to say, I'm stuck in the worst of the possible worlds except for a bricked device. unlocked with no apparent way to relock it, and not rooted.
I feel like my phone is in some strange state where the normal procedures do not work. If I could at least figure out what's wrong with the rooting, I could go the full way AND then, in case use Magisk. but at the moment I feel like there is a need to put the phone in a known definite state whichever it is and work from there. I'd be happy to revert to stock and locked and then redo everything when needed in the future.
How could I troubleshoot further or get to such a "known state"? many thanks
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
pitrus- said:
The thing you did wrong was using the outdated SuperSU method of rooting which is not supported anymore. You should just flash the latest Magisk zip of their github page and then you will have root with the possibility of hiding it for bank apps and others.
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
MassiB said:
Thanks pitrus, I'll have a look at it tomorrow and will update with what happened
Click to expand...
Click to collapse
Hi, update. I installed Magisk but, seeing that it had a way to put the phone in EDL mode, instead of going full root I decided to go the other way around and try to make my phone as stock as possible and reserve the experiments to an unit other than my primary. So I used the Qualcomm "unbrick" tool, and was able to flash the OxygenOS version that came with it - a rather old Android 6 whose networking (wifi, mobile...) wasn't working. But an adb sideload of the latest version after having put the phone in recovery mode allowed me to restore the networking and to update to the last supported version.
Magisk made the difference in getting me out of the spot. Thanks for bringing it to my attention!