So after having some issues with my phone I had US Cellular flash my phone to stock.
First issue:
Webtop does not work at all. When plugged into the dock I get a mouse cursor on the screen and the keyboard can be used to type text on the phone. The only option the phone gives is to mirror the display . Under setting it shows that my webtop version is not available. This also takes away the option the use the webtop to help root my phone.
Second issue:
I can't get root. I'm trying to use the photon-torpedo method as I did successfully last time and after pushing the .tar file all I get after running the "/bin/tar xf /data/tmp/photon-torpedo.tar" command I get told "/bin/tar: not found"
Any help would be awesome in getting my phone back to normal.
Whenever I try to run any command (including regular linux commands such as ls) all I get is permission denied. Interestingly enough, running cd without anything after gives me a "cd: HOME not set" error.
aha355 said:
So after having some issues with my phone I had US Cellular flash my phone to stock.
First issue:
Webtop does not work at all. When plugged into the dock I get a mouse cursor on the screen and the keyboard can be used to type text on the phone. The only option the phone gives is to mirror the display . Under setting it shows that my webtop version is not available. This also takes away the option the use the webtop to help root my phone.
Second issue:
I can't get root. I'm trying to use the photon-torpedo method as I did successfully last time and after pushing the .tar file all I get after running the "/bin/tar xf /data/tmp/photon-torpedo.tar" command I get told "/bin/tar: not found"
Any help would be awesome in getting my phone back to normal.
Click to expand...
Click to collapse
A factory reset should fix webtop. As for root. Go to MotoSunfire.com and try the 2.3.5 root method listed.
Sent from my SCH-R950 using XDA
Nope, same error I've been getting.
Interestingly enough, I still have the su binary on the phone. When in the shell typing 'su' gives me root prompt but any commands entered give me a "not found" error.
The superuser app pops up whenever any apps request root access but no apps actually get root access.
If this gives me to many issues I'm probably just going to pay the $35 and get a "new" phone.
A thought I have that would hurt to try is to do the 2.3.5 reflash and then retry the root. I don't care about having an unlocked bootloader because the device came locked.
well if you're already on 2.3.5 then you're locked for good anyway (unless factory shipped this way). so flashing the 2.3.5 sbf will only help fix things. i recommend it. it will fix webtop since it sounds like it's broken.
Related
Hi, I'm trying to help a fellow Atrix user after he formatted and partitioned the internal flash memory using Tenfar's CMW Recovery.
He has lost touch on the bottom part of his screen; about a 1/2" of screen space doesn't work.
Tenfar posted that he had done this too, and had resolved this by reformatting with the Stock Recovery. Another user asked in that same thread how he accomplished that, but no answer has been given yet.
This user cannot get the Recovery Menu to show up because of the lower touch screen not working.
Can the steps be run blindly without the Recovery Menu showing up?
Or, can someone help me on how to have him format the internal memory via ADB?
I've had him try the following ADB commands from both the /!\ Recovery Screen and after enabling Early USB Enumeration without luck.
Code:
adb shell
$ su
# format DATA:
Comes back with format: not found.
Can anyone help? I've seen a few others with this issue but have yet to see a full solution posted for those that aren't ADB experts.
I have this problem too! Tenfar was kind enough to try helping me but apparently I'm a retard and unfortunately can't follow his instructions. I've been spending an entire week reading hours each day and I'm embarrassed that I still can't fix it, despite him sending me almost a dozen PM's trying to do so. Very grateful but sad that I'm so dumb.
He's told me to do this:
$adb shell
$su
#busybox umount /sdcard (hit enter key)
#newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18 (hit enter key)
I'm not sure where to do this. I now think I do this while the device is in Early USB Numeration but I haven't tried it yet. The wife was getting really pissed because I spent the entire weekend trying to fix this and have been investing too much time on the computer. She's... having mad PMS so I'm leaving it for a few days lol
I tried earlier when the phone was booted up but after some research, believe it may need to be done in Early USB Numeration mode but there's only about a minute before it automatically reboots. I haven't tried this and hope that my assumption is correct. I know about 3 other people who are currently experiencing this challenge and I hope that it corrects it.
The wife is working a double shift today so I'll try after work. Can't blame her for getting upset with me. Soft bricked a few other phones but fixed them with relative ease. This has been by far the toughest. It was my birthday last week and I spent most of my day on the computer trying to fix my Atrix lol
After this, no more formatting internal SD partitions!!! Paypal is giving me grief but I plan on giving Tenfar a modest donation. He's been very supportive of my dumb ass lol
In this forum there is a very good guide on how to use adb. Can't remember where exactly it's at I just did a general search for How to use adb it may help you.
Edit I think this is the link androidsamurai.com/forum/viewforum.php?f=12
coldfusionb said:
In this forum there is a very good guide on how to use adb. Can't remember where exactly it's at I just did a general search for How to use adb it may help you.
Edit I think this is the link androidsamurai.com/forum/viewforum.php?f=12
Click to expand...
Click to collapse
Thank you!
I managed to install Ubuntu and I really like that.. tried from there too and it wasn't working. So I think it's definitely a problem with my dumb ass. If and when I get it working (I'm determined!...... and sort of stuck lol) then I'll post a guide.
Fuuuuuuuuuuck!!! Still not working!!
Yeah.. i ended up wiping with stock recovery and still a no go. Still no lower half of the screen or buttons. Sucks big time
Once ADB can be run in the recovery menu I think it should be fine.
Tenfar said he's fixed this problem but I'm no sure where he's run these commands. I feel bad after sending him a ton of PMs so I'm just waiting until he updates his Recovery app.
You could try restoring your sbf in rsd
Sent from my MB860 using XDA App
sgtmedeiros said:
You could try restoring your sbf in rsd
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
That's been mentioned and tried multiple times.
I have a simple script written with the command lines from Tenfar, but I am getting his input via PM to make sure it's correct and when exactly to run it. Hopefully he'll be able to direct me on how to get it done. Unfortunately, even if he says it looks right it's going to be completely untested. :-/
Sent via rooted Moto Atrix using Tapatalk
das8nt said:
I have a simple script written with the command lines from Tenfar, but I am getting his input via PM to make sure it's correct and when exactly to run it. Hopefully he'll be able to direct me on how to get it done. Unfortunately, even if he says it looks right it's going to be completely untested. :-/
Sent via rooted Moto Atrix using Tapatalk
Click to expand...
Click to collapse
There's still a glimmer of hope, buddy. Once we get ADB access in Recovery I think all should be well.. unless partitioning this block somehow corrupts and kills the digitizer or something.
I actually couldn't wait any longer. Ported to Bell and got a new Atrix so if things go bad I'll have an easier time swapping. When I fix this AT&T one I'll sell it to pay off my cancellation fee with Rogers. Or, if I end up sending it to Motorola I can go back with my buyer's remorse period and go back to Rogers.
Hope you've got a backup phone or something to use in the meanwhile, man. This issue drove me INSANE!!
Hope is good, but this isn't necessarily for me. That's why I can't test it; this didn't happen to my phone. I have just been trying to help those who this did happen to. I'm also sure it will continue to happen if the CWM port for our phones isn't preset to format correctly.
Glad you were able to get a working phone again, but too bad a phone had to go back under these conditions.
Well, I'll keep trying to figure it out; waiting on another reply from Tenfar. Our schedules don't mesh too well, so if there's anyone else that might have experience in formating via ADB any help would be appreciated. Thanks!
Sent via rooted Moto Atrix using Tapatalk
I have the same problem, I just wanna know if anyone found a solution to fix that?
Also, I live in Belgium (Europe), I bought the atrix in usa a month ago during my honey moon. Motorola Europe doesn't support yet the atrix, I don't know what to do!
The phone is not usable anymore, like someone said: "clicking on the soft button area registers as a click on the bottom of the screen". So, the back button don't work anymore (you have to reboot when your stuck in a menu!)
hi guys i'm currently with a reflashed stock 1.83 rom, i can use android recovery (there the bottom screen portion works) and i can run wipe data/cache.
but no matter how many times i tried when the phone finally boots up it starts with motoblur setup and i cannot pass it, all the buttons work like the bottom of the visible screen and i cannot raise up the keyboard to turn the setup off...
i read in the sbf thread that would be possible to flash or not some particular areas, so if the problems is the wrong partitioning of the /dev/block/mmcblk0p18
maybe some of them could create a sbf replacement toreflash only that partition
other side i was talking with bongd and he says he had problem with the psd.bin file that is in the mmcblk0p03...
so what is the current status of this? adb seems not to work even in early enumeration usb mode...
what if we execute the script using the update.zip function?
i can access my sdcard from windows in storage mode
if we put the script in one signed update.zip into the sd the phone should be able to execute itself?
KeRmiT80 said:
hi guys i'm currently with a reflashed stock 1.83 rom, i can use android recovery (there the bottom screen portion works) and i can run wipe data/cache.
but no matter how many times i tried when the phone finally boots up it starts with motoblur setup and i cannot pass it, all the buttons work like the bottom of the visible screen and i cannot raise up the keyboard to turn the setup off...
i read in the sbf thread that would be possible to flash or not some particular areas, so if the problems is the wrong partitioning of the /dev/block/mmcblk0p18
maybe some of them could create a sbf replacement toreflash only that partition
other side i was talking with bongd and he says he had problem with the psd.bin file that is in the mmcblk0p03...
so what is the current status of this? adb seems not to work even in early enumeration usb mode...
Click to expand...
Click to collapse
Tenfar told me it was mmcblk0p18 but it's actually mmcblk0p03 which needs to be corrected.
There's no ADB in recovery right now. Tenfar's apparently got it working but hasn't released it yet.
I also guarantee you can bypass the Motoblur setup as well. Hit these keys:
?123
ALT
ABC
e
?123
ALT
ABC
e
b
l
u
r
o
f
f
I'm positive because I've literally flashed every SBF and I've spent a lot of time troubleshooting this issue.
really i cannot open the keyboard while i'm in the blursetup screen, i keep pressing the menu button but it highlights only the emergency call and after many seconds it chance to emergency call screen...
At this time, your phone is 'bricked' since we can't get ADB access.
Sent from my MB860 using XDA Premium App
we don't have adb access but i tried and we can use the update function in the stock recovery...i tried to put a update.zip of my old milestone and the process worked till the sign verification that failed.
in the milestone that update.zip is used to run the updaterscript that launches the openrecovery by skrilax_cz, that works like the recovery of tenfar
i guess that if we have a correct update.zip for atrix and we put in it the script we need, it should be run.
unfortunately i don't have the knowledge to build the correct script and don't have access to a signed update.zip for atrix.
if we only could gain some interest of the devs i think our problem could be solved in short time...
edit: i sent 2 pm to tenfar but did not reply, maybe someone has more luck...
Ok first of all Im sticking this question in general android Q&A because there in no XDA Forum for this phone. It is a Straight Talk LG Optimus Q 55c, this is my girlfriends phone its basically an optimus p500/v with a sliding keyboard Overclocked too 800mhz. I own a virgin optimus V so I have a lot of experience with this platform but Im stumped maybe im just neglecting to see something, Im hoping "another set of eyes" will help turn on a light and get my girlfriends phone working again as she cant afford another :/!
So here is what Im dealing with. I had rooted the phone for her and installed clockwork mod recovery & fastboot. Since she got the thing its had problems freezing (probably because it stock overclocked), and occasionally pulls a random reset. She asked me If I could install another ROM on it to see if it may help make the phone more stable. I went a searching and found that the Optimus Q community is very small almost nothing and her only real choice was a port of the Area51 Rom. So Installed the rom.... A few days later she had told me her phone was mega slow now and acting up way more, so I told her I would flash back to stock.
I rebooted the phone and found to my surprise CWM and fastboot seemed to be gone... what the h*ll? Im assuming when I flashed AreaRom it installed the stock Recovery and removed fastboot, I cant figure out any reason why the stock recovery would be back on the phone. Anyways I didnt feel like flashing a new recovery at the time. Well 3 days go by and her phone crashes and gets stuck in a boot loop. So she went in to recovery and wiped it. The phone then went through the process of collecting e-mail and password, asking about backing up, then asking whether or not to turn the location services on. Once you hit next Android throws an exception and says setupwizard.apk failed to initialize or something along those line. So after that the launcher does not load only the task bar at the top. When rebooted the phone enters a boot loop againg until wiped.
So heres the deal I can use adb, but when I try to get into an adb shell the prompt says error: closed. I have been able to use adb to push and pull files that is all. I tried to push setupwizard.apk to the system/apps directory but of coures it needs to be remounted to read write and I dont have any shell access to do that. So basically adb sees the phone but the shell doesnt work, when i type adb root it reports adbd is running as root on the phone, so I guess the shell service just never loads.... I do have stock recovery but the problem with that is there is no update.zip files it will except I have tried a myraid of methods to sign an update.zip but every time I try to run the update the stock recovery says verification failed. Of course LG has no official updates for this phone using there signature that I can use.
So basically my phone works recovery works android starts but cant finish setting up and never starts the adb shell service. If anyone knows how I can push setupwizard to /system/app, get adbd to initialize, or sign a 3rd party rom and have the stock recovery use it I would be very gratefull! Maybe there is a way to get fastboot back on there or enabled or something? adb reboot-fastboot just reboots like normal. I am at the point where I going to take the phone apart to find a serial uart connection and pray I can get a shell that way!!
Ive looked into a few programs like kdz update and lgmdp but they dont seem to work with this phone and I cant get into any emergency mode, maybe Im doing it wrong this is the first ive heard of emergeny mode.
OK, I recognize I might catch some crap on this, since you guys don't know me from Adam, but it's a crappy situation. My friend passed this on to me, because he is stumped. His brother died in a car wreck on Christmas night, and found among his possessions in the car was this Venue 8320. It's set up with a pattern lock, and of course we can't get past it.Don't have access to the email, because the guy is dead. His father tossed the cell phone that might have been linked to the email, so we can't get in the email that way. So, I'm trying to figure out how to either bypass the pattern lock, or barring that, reset it so that it's at least usable.
I've loaded the Intel Android drivers on my computer, and can get an ADB shell, or access the fastboot when booted into Droidboot, but without root access I'm still pretty limited in what I can do. Is there any way in to this thing, or is my friend SOL?
Rasilon said:
OK, I recognize I might catch some crap on this, since you guys don't know me from Adam, but it's a crappy situation. My friend passed this on to me, because he is stumped. His brother died in a car wreck on Christmas night, and found among his possessions in the car was this Venue 8320. It's set up with a pattern lock, and of course we can't get past it.Don't have access to the email, because the guy is dead. His father tossed the cell phone that might have been linked to the email, so we can't get in the email that way. So, I'm trying to figure out how to either bypass the pattern lock, or barring that, reset it so that it's at least usable.
I've loaded the Intel Android drivers on my computer, and can get an ADB shell, or access the fastboot when booted into Droidboot, but without root access I'm still pretty limited in what I can do. Is there any way in to this thing, or is my friend SOL?
Click to expand...
Click to collapse
factory reset clears all lock codes but also deletes all info.
power off, then power on while holding voume down button
you should select the option called recovery, on the recovery screen you should c da droid on his back when you are there press and hold power button and voolume up button for 2 or so seconds and you should enter recovery mode
chairsz said:
factory reset clears all lock codes but also deletes all info.
power off, then power on while holding voume down button
you should select the option called recovery, on the recovery screen you should c da droid on his back when you are there press and hold power button and voolume up button for 2 or so seconds and you should enter recovery mode
Click to expand...
Click to collapse
Hmm. When I go to Recovery, all I get is a picture of an android on it's side with a repair hatch open. There does not appear to be any way to do a reset from there, at least not that I can see.
I've been trying to root it, but SuperOneClick isn't working. I tried pushing the various included files manually and executing them, but they won't execute - the error message is "not executable: magic 7F45". I tracked down x86 versions of su, busybox, etc. and they will execute, so it looks like all I need now is an x86 binary for rageagainstthecage/psneuter/zergRush. Does anybody know where I would track one down? I haven't had any luck finding one so far.
When at then android hatch picture you can press power then vol+ same time, let go and u will have more options. Good luck.
Sent from my Venue 8 3830 using xda app-developers app
Rasilon said:
Hmm. When I go to Recovery, all I get is a picture of an android on it's side with a repair hatch open. There does not appear to be any way to do a reset from there, at least not that I can see.
I've been trying to root it, but SuperOneClick isn't working. I tried pushing the various included files manually and executing them, but they won't execute - the error message is "not executable: magic 7F45". I tracked down x86 versions of su, busybox, etc. and they will execute, so it looks like all I need now is an x86 binary for rageagainstthecage/psneuter/zergRush. Does anybody know where I would track one down? I haven't had any luck finding one so far.
Click to expand...
Click to collapse
there is a working method of rooting this tab is for the 4.2.2 version ( some 4.2.2's are not really working with root but others are) and if your tabby is the 4.3 update then that method to root exists somewhat but the creator of that method isnt releasing it till he deems its ready. so just look in this forum somewhere you'll find you root method if your on 4.2.2
also to enter recovery when at the droid on his back screen press and hold the volume up and power button simultaneously
there you can wipe stuff.
chairsz said:
there is a working method of rooting this tab is for the 4.2.2 version ( some 4.2.2's are not really working with root but others are) and if your tabby is the 4.3 update then that method to root exists somewhat but the creator of that method isnt releasing it till he deems its ready. so just look in this forum somewhere you'll find you root method if your on 4.2.2
also to enter recovery when at the droid on his back screen press and hold the volume up and power button simultaneously
there you can wipe stuff.
Click to expand...
Click to collapse
Yeah, thanks. I don't think it's 4.3, because it hasn't been on a network since 12/25, although perhaps that's why I haven't been able to root it. Kernel version is 3.4.34, which I see has been reported as present in a patched 4.2.2 version that is not vulnerable to standard 4.2.2 exploits. I guess that's what I haven't been able to get in. I'll tell my friend that he can either wait for a 4.3 root exploit to be released, or wipe it clean.
Thanks for the help chairsz.
Pls help me root my zte obsidian running android 5.1 Model NO. Z820
I need help too
I also have ZTE obsidian tmobile and really want to root it i cant do much because it only comes with 4gb of space and i cant move apps to the SD card till i root Please help find a root
yeah same issue here all say that it cant after like 10-15 mins its just like nope sry
have you used this
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Yes, I tried. Its not working.
Is there any other way. I am desperate. It doesnt allow to move the Apps to SD card. There is no way. Locked in 4GB
I have a z820 in need of root as well. I've tried everything, including the link up there, and so far.....nope. Nothing. No apps to SD for me either.
Zte can't root for ****!!!!
I'm so mad because I really tried everything even a computer won't let me tried everything there to like why would the make a zte that can't even move your games or pictures or music to your SD card knowing danm well everybody gone need like we only got 4g that's nothing so what are we so posted to do delete stuff that we like.to trade for the other that we really don't need **** I'm pissed right now I know y'all are to but if anybody finds something please send me the info or con me by [email protected] thank you:good:
Needs update
This Phone really needs an update, it reboots and sucks, we can't even get into fastboot or anything to try to unlock the bootloader someone needs to make this possible because who in the hell uses only 4gb of storage, apps are so big and you can only download like 3 apps then you have to get rid of something if you want another app and its dumb so please someone..HELP US :crying:
Throwing my post up here so I can follow. Need root bad on this thing. I am using lite versions of every app. Lol
Same problem w/ ZTE obsidian..tCan't move to SD card. Anybody figure somethcing out yet?
I've gotten Kingroot to attempt to root it once and the results varied. Usually got 16% but the highest was almost 30% but I can't even get kingroot to even root it anymore.
The phone is not going into fastboot at all. I think the bootloader is locked. The phone will never be rooted.
I might of found a way, but it's untested so, proceed at your own risk, I am not responsible if your phone becomes bricked.
Enable developer mode and tick "OEM Unlocking" in the developer menu
Download SuperSU update zip from Chainfire's site and put it on your sdcard (internal won't work)
Power off your phone and hold power and volume up
Select recovery, wait for the android with the lid open to show up
Hold power and volume up for a couple seconds and let go
A menu should pop up, if not try again until it does
Select "update from sdcard"
Select the SuperSU zip
Let it flash the zip (shouldn't take long)
Choose reboot
See if SuperSU is installed and test that it works
Again, this is untested and would need a couple of people testing it to make sure it works flawlessly, so if this worked, please post that it did.
Nope. Thank you though.
picsles said:
Nope. Thank you though.
Click to expand...
Click to collapse
Any type of error happen or did it not allow it to flash at all?
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Musicmanmike said:
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Click to expand...
Click to collapse
You have to hold down power and vol up for like 2 seconds when you get to the dead android, then you'll get the recovery menu.
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Kurrelgyre said:
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Click to expand...
Click to collapse
OEM Unlocking is always on for me even after restarts but I haven't tried to flash SuperSU yet. You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
EDIT: Also every new Kingroot build allows you to attempt to root it for like 2 days and then it just can't for some reason but the thing with 18% still happens.
LUModder said:
You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
Click to expand...
Click to collapse
The logcat I am familiar with is in ADB. The only way I can find to access the phone from recovery with ADB is to select the flash from ADB option, which puts the phone in sideload mode where you can't pull data off. I was unsure if trying to load the ZIP that way would brick the phone so I haven't tried it.
I also tried using Fastboot and it doesn't recognize the phone at any time.
Is there another way to capture what is happening with the update?
I tried selecting restart in bootloader from the recovery menu with the phone connected to the PC. It stayed at the ZTE splash screen for over 10 minutes but neither fastboot nor ADB was able to communicate with it. I tried various key combinations without effect and finally ended up pulling the battery. Maybe it just froze up during boot for some reason.
I have tried every one-touch root I can find, none of them work. All the manual guides start with unlocking the bootloader - which I can't find any info on for this model. Based on the partition info, it's definitely locked: it has 27 (!) partitions including names like seccfg and oemkeystore. Is this normal for a lollipop device?
I was given to weekend to attempt to root a moto e. Did some looking in advance and saw that it was a pretty well known device and had been rooted for quite awhile. Should be: Do some reading, pick your favorite method / the one you understand the best , backup?, root, win. Have done it bunches. Rarely a glitch. This gem of a phone I am dealing with turns out to be a moto e(so far , so good) , that was purchased at wal mart( must of been really cheap, otherwise why deal with the savages at wal mart?), and is through cricket (decent enough mvno, if thats your thing), on at&t (bastards!!). Motorola is handing out bootloader unlocks to anyone with a usb cable and a pulse. At&t said they would not like their customers to have those codes. Via a chat with cricket I got a sim unlock code. No such luck for bootloader though. I worked on this yesterday and the net result so far is I think unlocking the sim dorked up the currently in use service which was through cricket in the first place. (ugh). I'm not as worried about that as It can be sorted out easily enough. The rooting thing though, I've been skunked. Tried every manner I could think of to get a custom recovery going and I got nada. I like reading. Not afarid of it in the least. If anyone can point me in the direction of what I need to do I would be ever so grateful.
bashtard said:
The rooting thing though, I've been skunked. Tried every manner I could think of to get a custom recovery going and I got nada..
Click to expand...
Click to collapse
I got my wife a Nexus for Christmas, so I've been playing with her xt1021 off and on since. It is also a Cricket, WM clearance, etc. As far as I can tell there's no current way to root the phone (or at least, when I looked around a couple weeks ago). Also, I'm pretty sure we'll not be able to bootloader unlock the phone, though something like SunShine might work eventually, and/or something like SafeStrap, if we could get a decent root.
Using KingRoot, I am able to achieve a very temporary root. These steps are vaguely repeatable but require very precise manual timing:
- Connect via USB with debugging enabled
- adb shell to the phone
- repeatedly issue 'su' on the prompt (I use 'while [ 1 ] ; do /system/bin/su ; done' )
- Run KingRoot
- DO NOT LOOK AWAY!
- While KingRoot is running, about 50% of the way through, a message will pop up to give permission to ADB. Approve.
- Kill KingRoot through the task manager, immediately.
- chown 4755 /system/bin/sh or something similar, as you will very soon lose your SUID bit on /system/bin/su.
If this does not work or you miss the prompt, you will have to reboot, clear the KingRoot application data, and then try again. If you just restart KingRoot it will continue where it left off, which will not work and will cause general instability until you reboot again.
In this state (which I can only hit about half the time I try it, even after a -lot- of practice):
- /system is mounted RW for the adb shell
- /system/bin/su has the SUID bit set for a short time
- You can copy SU to somewhere else that doesn't have root squash. This will let you retain root for the current boot - otherwise, you'll lose it after you lose the shell.
If KingRoot goes too far, or you try to do certain things in /system, the OS detects it and completely shuts down all writes to /system. Also, there's only a very short window during which /system/bin/su has the SUID bit - there must be some process that regularly checks for SUID in /system and removes it.
So far, I have not come up with a way to make any change in /system stick, nor have I found a place to keep the su binary persistently.
This is as far as I've gotten, as mentioned having to reset KingRoot every time makes things take a lot longer.
I also have a Verizon xt1528 (E 2015, also BL locked), and while I've played with it only a couple times I've seen the same kind of behavior, for what it's worth. I'll probably play with the 1528 more than the 1021, but if I hit upon a solution for either usable temp root or writing to system I'll try it on both and update.