Yep, you read that right and I'm not trolling. THE ZMAX IS ROOTED!!
Discaimer and N00Bproof warning:
We have root, yes, but that doesn't mean get hasty. At the moment, there are partition images (system, boot and recovery) in my and other users' possession (free of access to all), but we don't have a working recovery at the moment and this process involves deleting the stock recovery (it will make sense later). So, if you screw up and get root-happy, there's no way to recover until we get a recovery and a custom rom, and even then you might be screwed because we don't have access to the bootloader to use fastboot. Things may change, but root-use with caution.
Also, once you root, DO NOT TAKE ETAs from T-Mo and ZTE!!!!!!! Now that we have root, we can capture the OTA and make it root-friendly. To make a long story short, the updater-script (thing that tells your recovery where and how to flash stuff) has a list of stuff it has to... well... flash. If you, for example, delete the stock ZTE Music app, and the ETA replaces the app with a new version, it's going to stop (because the script requires a REPLACEMENT and not a PLACEMENT, computers don't have the best common sense), then it will interrupt and you will likely be bricked. This shouldn't be a problem because you don't have a recovery to begin with, but I'm not taking chances here.
NOW! Let's Root. This is a long process, so don't expect to do anything for a good 10-20 minutes.
FIRST: KINGROOT
This is one of those things where your mileage may very, there have been many different ways to get KingRoot (not King"O"Root, two different apps) to work, but this one was the one that worked for me. I'll also place alternate KingRoot methods in the second post if you wanna try those. Just for the sake of knowledge, this was run on a T-Mobile ZTE ZMAX, Android 4.4.2, build 22. I don't know if it makes a difference that I factor reset my phone before doing another round of root attempts (not this one specifically, maybe a couple hours worth of attempts).
Credits to @fire3element for this method.
1) Download KingRoot APK from here (the first one with the image of the phone if you are on the desktop site).
2) Install KingRoot and run it. It will restart the phone, and it will fail (or, if you have some Android God luck, it may succeed), this is supposed to happen.
3) Clear KingRoots cache and data (in that order) and power off the phone (not reboot). Then, power it back on again.
4) Now this is where things get... well complicated for this part. You are going to need to load your RAM with a bunch of processor heavy stuff. The person that made this method used CounterSpy and Final Fantasy Type-0 in the PPSSPP v1.0.1-411 emulator, but for those of you that don't have access to that, get creative and load up. Here is what I had running (all at the same time, mind you).
Note: Force Stop Task Manager in the app settings first or it will purge to free memory automatically and this won't work.
1. Next Launcher Lite
2. Apex Launcher
3. Nova Launcher
4. Cheetah Launcher
5. CM Launcher
6. Mi Launcher
7. 25 tabs on Google Chrome (No joke)
8. Both Temple Runs
9. Fruit Ninja
10. Google Play Store
11. Google Now
12. Google Play
13. Amazon
14. Google Play Music
Mine was definitely a bit extreme but I knew all of this stuff would guarantee a good memory hogging.
5) Run all of your apps at the same time. The TL;DR for this is that apparently it's some exploit that the app uses as a buffer overflow. Now, go to settings and Force Stop KingRoot. Then Run it again. If it works, you should go from 0 to 100 real quick (no pun intended). It shouldn't progess slowly or reboot the phone to do this, but your journey does not stop here.
Click to expand...
Click to collapse
If you did it correctly, the screen from a successful root will have a green checkmark. Run RootChecker to verify root status.
SECOND: PERMA-ROOT
Now you need to permanently root the phone. This method was all @jcase, and simplified by another user. I encourage you to read JCase's original G+ post to learn something, as this guy is the master of exploits, and we are on XDA to learn.
Credits to @xtremeasure for the simplification of JCase's process.
1) Plug phone into computer...
2) Open cmd type "adb shell" (without quotes, moving forward, type all commands without quotes). This will open a terminal for the phone.
3) While in ADB Shell, type "su" to gain root shell privileges
4) Type "getprop ro.build.fingerprint"
Output for that command should be...
zte/P892T57/draconis:4.4.2/KVT49L/20140804.141306.18686:user/release-keys (the part with P892T57 may be different depending on what model ZMAX You have). If you haven't updated that number will be different, this ok, just replace the number in the next command with whatever your output is.
5) type "setprop persist.sys.k P892T57"
6) type "getprop persist.sys.k" and your output should be your build number
7) type "cd /dev/block/platform/msm_sdcc.1/by-name/" to change directories so that we can back up your recovery image (remember I said something about that?) and set the boot to our recovery partition.
8) type "dd if=recovery of=/sdcard/recovery.img" to backup the recovery image.
9) type "dd if=boot of=recovery" to set recovery as boot. Another TL;DR is that this disables the write protection set by the stock recovery, allowing you to write to the system. It will mount the /system partition upon boot.
DELETE KINGUSER NOW
10) type "reboot recovery" and restart your phone. YOU MUST RESTART WITH THIS COMMAND!!!!! It will boot straight into Android, this is good, that means you haven't screwed up anything.
11) Reopene the adb shell (using "adb shell") in your command prompt or terminal (for OSX and Linux) and type "Id". If your output is "uid=0(root) gid=0(root) context=u:r:shell:s0" then It worked...
12) Remount system as writable "mount -o rw,remount /system"
13) Manual install for supersu you can get that here: http://download.chainfire.eu/supersu
14) Type "exit" into the terminal/command and it should drop you back to your normal cmd...unzip the su zip anywhere you want in your cmd switch to that directory...
14B) I advise taking the "su" binary and "install-recovery.sh" file from the superSU folder you downloaded and putting them in the same place (on the desktop or wherever your adb.exe is if you didn't set $PATH on your computer). su can be found in the "arm" folder and install-recovery.sh can be found in the "common" folder. It is important to note that where ever your files are, you will have to type that path (if it isn't in the same directory as your adb). So, as an example, I put mine on the desktop, so I have to type "adb push ~/Desktop/su /data/local/tmp/su". If you do not know how to do that, then stop what you are doing and research it, as that's just too much to explain.
15) "adb push su /data/local/tmp/su"
16) "adb push install-recovery.sh /data/local/tmp"
17) Reenter adb shell with "adb shell"
18) Make sure system is mounted writable with "mount -o remount,rw /system"
19) Move the so files into place with these commands
"cat /data/local/tmp/su > /system/xbin/su"
"cat /data/local/tmp/su > /system/xbin/daemonsu"
"cat /data/local/tmp/install-recovery.sh > /system/etc/install-recovery.sh"
20) Give them all permissions
"chmod 755 /system/xbin/su"
"chmod 755 /system/xbin/daemonsu"
"chmod 755 /system/etc/install-recovery.sh"
21) Reboot your phone to complete install with "reboot"
22) After rebooting go into the play store and install the supersu app. It's going to tell you the su binary is out of date to fix that we need to open the adb shell on our pc again with "adb shell"
23) Reboot into recovery (you're really rebooting the system with r/w privileges) using "reboot recovery"
24) Once rebooted open the app and update your binaries one finished reboot add your done 100% perm rooted
Click to expand...
Click to collapse
Now, you are rooted! If you did everything right, you should be good. Now people are going to ask, "Is there a script for this?" The short answer is No, don't hold your breath for something immediate. There was a user that said he would be happy to make one for the second half, but the writing, testing and verification of success alone on that will take some time, as the wrong line of code can make you end up with a good old fashioned paperweight. I can verify Xposed works fine, Viper4Android works fine, and if you try to delete system apps, they will just reinstall themselves (I recommend using "System App Remover (ROOT)" on the play store, as it will actually tell you which apps are and aren't safe to install. If you have any questions, after searching of course, feel free to ask. If I can't answer, some freaking body can lol.
CREDITS:
@tech_yeet for showing us the KingRoot
@jcase for his amazing work
@xtremeasure for his method
@fire3element for his method
@the zMAX Community for staying dedicated when the going got tough, it's been a long road. Here's to custom roms and a TWRP recovery!
Please share this with others, as there is a big community of people begging for this info, let's share the love . If I forgot to credit you, let me know and I'll fix that!
ADDITIONAL INFORMATION
If you by some chance flash the TWRP Recovery Image (found in post 2), and would like to revert back to root ability (being able to write to system). Please follow the steps below:
1. cd /dev/block/platform/msm_sdcc.1/by-name
2. su
3. dd if=/sdcard/recovery.img of=recovery
4. reboot recovery
Please make sure you have the recovery in your sdcard root folder.
Alternate Root Methods and ZTE Custom ROMs/Kernels/etc
If the above first part doesn't work for you, you can find alternative root methods
Alternate Method 1 HERE
Alternate Method 2 HERE
As I see more added, I'll add them here.
CUSTOM STUFF
TWRP Image for ZTE ZMAX
Q&A/Other [UDPATED MAY 13, 2015 @ 5:45PM]
If A question is asked and you feel like it needs to be here, please tag or DM me with the Q AND THE A so that I can do so.
OTHER:
Original Discussion Thread for the ZTE ZMAX
Please see fire3element's post on what each screen in the KingRoot app means
WHAT THE SCREENS MEAN IN THE APP
That's a whole lot to swallow but I'm glad to see y'all can finally get rooted. Definitely not a method for noobs or the faint of heart but its a HUUUGE step in the right direction. Thanks to everyone responsible for this.
Hroark13 has TWRP - http://androidforums.com/threads/zte-zmax-twrp.918537/
mingolianbeef said:
Yep, you read that right and I'm not trolling. THE ZMAX IS ROOTED!!
Discaimer and N00Bproof warning:
We have root, yes, but that doesn't mean get hasty. At the moment, there are partition images (system, boot and recovery) in my and other users' possession (free of access to all), but we don't have a working recovery at the moment and this process involves deleting the stock recovery (it will make sense later). So, if you screw up and get root-happy, there's no way to recover until we get a recovery and a custom rom, and even then you might be screwed because we don't have access to the bootloader to use fastboot. Things may change, but root-use with caution.
Also, once you root, DO NOT TAKE ETAs from T-Mo and ZTE!!!!!!! Now that we have root, we can capture the OTA and make it root-friendly. To make a long story short, the updater-script (thing that tells your recovery where and how to flash stuff) has a list of stuff it has to... well... flash. If you, for example, delete the stock ZTE Music app, and the ETA replaces the app with a new version, it's going to stop (because the script requires a REPLACEMENT and not a PLACEMENT, computers don't have the best common sense), then it will interrupt and you will likely be bricked. This shouldn't be a problem because you don't have a recovery to begin with, but I'm not taking chances here.
NOW! Let's Root. This is a long process, so don't expect to do anything for a good 10-20 minutes.
FIRST: KINGROOT
This is one of those things where your mileage may very, there have been many different ways to get KingRoot (not King"O"Root, two different apps) to work, but this one was the one that worked for me. I'll also place alternate KingRoot methods in the second post if you wanna try those. Just for the sake of knowledge, this was run on a T-Mobile ZTE ZMAX, Android 4.4.2, build 22. I don't know if it makes a difference that I factor reset my phone before doing another round of root attempts (not this one specifically, maybe a couple hours worth of attempts).
Credits to @fire3element for this method.
If you did it correctly, the screen from a successful root will have a blue envelope with a checkmark. Run RootChecker to verify root status.
SECOND: PERMA-ROOT
Now you need to permanently root the phone. This method was all @jcase, and simplified by another user. I encourage you to read JCase's original G+ post to learn something, as this guy is the master of exploits, and we are on XDA to learn.
Credits to @xtremeasure for the simplification of JCase's process.
Now, you are rooted! If you did everything right, you should be good. Now people are going to ask, "Is there a script for this?" The short answer is No, don't hold your breath for something immediate. There was a user that said he would be happy to make one for the second half, but the writing, testing and verification of success alone on that will take some time, as the wrong line of code can make you end up with a good old fashioned paperweight. I can verify Xposed works fine, Viper4Android works fine, and if you try to delete system apps, they will just reinstall themselves (I recommend using "System App Remover (ROOT)" on the play store, as it will actually tell you which apps are and aren't safe to install. If you have any questions, after searching of course, feel free to ask. If I can't answer, some freaking body can lol.
CREDITS:
@tech_yeet for showing us the KingRoot
@jcase for his amazing work
@xtremeasure for his method
@fire3element for his method
@the zMAX Community for staying dedicated when the going got tough, it's been a long road. Here's to custom roms and a TWRP recovery!
Please share this with others, as there is a big community of people begging for this info, let's share the love . If I forgot to credit you, let me know and I'll fix that!
Click to expand...
Click to collapse
I have followed EVERYTHING step by step over and over again, and yet i still cant get this to work.
Basically, everything is fine up until reboot recovery.
it goes into android, but i dont start off as root, i start off as if i wasnt rooted, and i always have to do "su" to gain privledges.
afterwards, mount -o remount,rw /system/ does work but i cant write to it still for some reason.
has anyone else gotten this!? have any of you got a clue how to fix?
Here is some more info for those of you wondering what the KingRoot app is doing.
Screenshots will follow.
Text ABOVE the screenshot is for the image directly under it.
Let's begin -------------->
FIRST SCREEN WHEN YOU OPEN KINGROOT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SECOND SCREEN
- CLICK BUTTON TO BEGIN ROOT -
ROOTING IN PROGRESS...
ROOT FAILURE
[Blue Button]: SUBMIT (submits the error report to KingRoot devs)
ROOT FAILURE
ROOT FAILURE
NO DATA CONNECTION (WiFi or cellular singnal required)
[Blue Button]: ANDROID SETTINGS MENU
SUCCESSFUL ROOT
IF YOU SEE THIS MESSAGE POP UP DURING ROOTING, JUST LEAVE IT ALONE. LET THE ROOT FINISH
SUCCESSFUL ROOT
[trash can]: [...]: [...]:
SUCCESSFUL ROOT
[Blue Button]: PURIFICATION (I believe this is similar to fixing permissions)
- CLICK IT AND LET IT RUN -
^ from clicking blue button above ^
PURIFICATION PROCESS
xIP- said:
I have followed EVERYTHING step by step over and over again, and yet i still cant get this to work.
Basically, everything is fine up until reboot recovery.
it goes into android, but i dont start off as root, i start off as if i wasnt rooted, and i always have to do "su" to gain privledges.
afterwards, mount -o remount,rw /system/ does work but i cant write to it still for some reason.
has anyone else gotten this!? have any of you got a clue how to fix?
Click to expand...
Click to collapse
Should just be mount -o remount,rw /system
No extra slash
Sent from my Z970 using XDA Free mobile app
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
I would the recovery image restore commands added.. If people feel the need to recover and try again they should run these
cd /dev/block/platform/msm_sdcc.1/by-name
su
dd if=/sdcard/recovery.img of=recovery
reboot recovery
*edited to remove a potentially harmful commands per jcase's advice*
Sent from my Z970 using XDA Free mobile app
xtremeasure said:
Should just be mount -o remount,rw /system
No extra slash
Sent from my Z970 using XDA Free mobile app
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
I would the recovery image restore commands added.. If people feel the need to recover and try again they should run these
cd /dev/block/platform/msm_sdcc.1/by-name
su
dd if=boot of=boot
dd if=/sdcard/recovery.img of=recovery
reboot recovery
Sent from my Z970 using XDA Free mobile app
Click to expand...
Click to collapse
even with just one slash I still have a problem
Sent from my Z970 using XDA Free mobile app
Ok, so I am about to flash back the stock recovery from my backup and see if I can go through all these steps again to figure out what is going wrong.
I have a theory as to where and why KingUser is locking down SU in xbin. After I restore stock recovery, I will then Factory Reset and attempt to log my progress.
Stay tuned and I will try to report back later today. Hopefully with more insight on this problem.
@xIP-
Are you talking about pushing "su" , "daemonsu" , and "install-recovery.sh" files to /system ?
Keeps saying permission denied?
If that is the case, you can not. KingUser has a lock on system and is already in place as SU in /system/xbin
You will most likely need to factory reset and try again.
---------- Post added at 12:57 PM ---------- Previous post was at 12:37 PM ----------
UPDATE UPDATE!!!
Do not run the dd if=boot of=boot command
Could brick your device. As per Jcase warning. Wait for more info
fire3element said:
Ok, so I am about to flash back the stock recovery from my backup and see if I can go through all these steps again to figure out what is going wrong.
I have a theory as to where and why KingUser is locking down SU in xbin. After I restore stock recovery, I will then Factory Reset and attempt to log my progress.
Stay tuned and I will try to report back later today. Hopefully with more insight on this problem.
@xIP-
Are you talking about pushing "su" , "daemonsu" , and "install-recovery.sh" files to /system ?
Keeps saying permission denied?
If that is the case, you can not. KingUser has a lock on system and is already in place as SU in /system/xbin
You will most likely need to factory reset and try again.
---------- Post added at 12:57 PM ---------- Previous post was at 12:37 PM ----------
UPDATE UPDATE!!!
Do not run the dd if=boot of=boot command
Could brick your device. As per Jcase warning. Wait for more info
Click to expand...
Click to collapse
Remember remove kinguser after you run the dd commands but before you reboot recovery...
Sent from my Z970 using XDA Free mobile app
xtremeasure said:
Remember remove kinguser after you run the dd commands but before you reboot recovery...
Click to expand...
Click to collapse
Just so this is clear... full Root uninstall through the KingUser app, or just uninstall it through android app settings menu.
^ In case someone else has the same question ^
fire3element said:
Just so this is clear... full Root uninstall through the KingUser app, or just uninstall it through android app settings menu.
^ In case someone else has the same question ^
Click to expand...
Click to collapse
I would do a full root uninstall....
The backdoor keeps root for adb so installing the new su shouldn't be an issue
Sent from my Z970 using XDA Free mobile app
Got it. Will report back after this headache is done. *slams head on desk*
I just read the boot flash advice, I am not going to do it because I know that's a stupid idea, but if it does in fact let us flash boot.IMG, omg overclocking, custom kernels, full read write, awesome recovery, dual boot custom Roms with custom kernels here we come.
Unlocked boot.IMG
Can you Ya hoooouoo
And subscribed.
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
fire3element said:
Ok, so I am about to flash back the stock recovery from my backup and see if I can go through all these steps again to figure out what is going wrong.
I have a theory as to where and why KingUser is locking down SU in xbin. After I restore stock recovery, I will then Factory Reset and attempt to log my progress.
Stay tuned and I will try to report back later today. Hopefully with more insight on this problem.
@xIP-
Are you talking about pushing "su" , "daemonsu" , and "install-recovery.sh" files to /system ?
Keeps saying permission denied?
If that is the case, you can not. KingUser has a lock on system and is already in place as SU in /system/xbin
You will most likely need to factory reset and try again.
---------- Post added at 12:57 PM ---------- Previous post was at 12:37 PM ----------
UPDATE UPDATE!!!
Do not run the dd if=boot of=boot command
Could brick your device. As per Jcase warning. Wait for more info
Click to expand...
Click to collapse
Is there anyway to do it without a factory reset? Could I just remove kinguser? or it must be factory reset? and will I have to reroot with factory reset?
Sent from my Z970 using XDA Free mobile app
Sorry guys, kinda been running around all day, have a lot of catching up to do I see. I'll fix the thread with updated information that people have so generously contributed!
DroidisLINUX said:
I just read the boot flash advice, I am not going to do it because I know that's a stupid idea, but if it does in fact let us flash boot.IMG, omg overclocking, custom kernels, full read write, awesome recovery, dual boot custom Roms with custom kernels here we come.
Unlocked boot.IMG
Can you Ya hoooouoo
And subscribed.
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Click to expand...
Click to collapse
I know right!!! First hurdle... done... second hurdle, bootloader with no fastboot lmao...
a bit unclear on this
are we actually rebooting into recovery or its supposed to go straight back into the phone
i was never able to get into recovery
10) type "reboot recovery" and restart your phone. YOU MUST RESTART WITH THIS COMMAND!!!!! It will boot straight into Android, this is good, that means you haven't screwed up anything.
"cat /data/local/tmp/su > /system/xbin/su"
"cat /data/local/tmp/install-recovery.sh > /system/etc/install-recovery.sh"
getting permission denied when running this.
"chmod 755 /system/xbin/su"
"chmod 755 /system/etc/install-recovery.sh"
as well as operation denied or something along those lines. any help would be nice. also and running id on adb. its showing.
uid=0(root) gid=0(root) context=u:r:init:s0
rather than
uid=0(root) gid=0(root) context=u:r:shell:s0
xIP- said:
I have followed EVERYTHING step by step over and over again, and yet i still cant get this to work.
Basically, everything is fine up until reboot recovery.
it goes into android, but i dont start off as root, i start off as if i wasnt rooted, and i always have to do "su" to gain privledges.
afterwards, mount -o remount,rw /system/ does work but i cant write to it still for some reason.
has anyone else gotten this!? have any of you got a clue how to fix?
Click to expand...
Click to collapse
You have to exit adb shell to push files to /data/local/tmp, which does not require root. That was a major exploit in earlier android versions, as people would push scripts to /data/local/tmp without root, run the exploit in the directory, and it would root. That was patched of course, but that directory can be accessed without root. Once you use "reboot recovery" to reboot, then just plug your phone back up and type "adb shell" to which the phone should respond with a "#" instead of a "$". If you have the $, you are not root and need to go back. If you do, just be patient with it and make sure you are not just copying and pasting (I know this can be the root of the issue at times with command, just type it out). It should work, the second half is the easy part lol.
Related
VRoot Cleanup Tool - Easily replace VRoot with SuperSU
From your Windows PC
OK everyone, here's the deal. I did the VRoot the toher day on my phone and it worked great. The problem is that it can be tricky to get the old Chinese Superuser app and SU binaries updated to SuperSU. As a result I decided to put this tool together to help update the VRoot files to SuperSU, and get rid of the old VRoot ones. What this means is that you can now clean up the Chinese Super User app and completely install SuperSU with a single click, from your Windows PC.
How to use:
Download Root Cleanup from here: https://www.dropbox.com/s/sto74q58uq4r1bj/root_cleaner.zip
Extract it to a folder on your computer.
Open the new folder and double click the clean_root.bat file.
Follow the directions.
** You will want to make sure that USB debugging is on (which it should be from VROOT) and that VRoot is closed when you run this. **
Also note I only have one phone to test with, and it worked great on the one I have. Please let me know if you have any other issues and I will try my best to help. Also, as always, not responsible for problems . <3
Edit: I just got asked via PM if this is to be run after freezing VRoot, etc. So I wanted to add here in case anyone else wondered. With this tool you do not need to freeze VRoot, delete any files, etc. My script will literally take care of everything for you. So, run VRoot and the phone will reboot. You can immediately close VRoot on your computer and run this to completely replace VRoot with SuperSU, and remove VRoot files.
This is my first time writing something like this, but so far I have a lot of people who told me it works fine. Please let me know if you have issues and Ill do my best to help! I went ahead and created this thread at the request of some people who have had good success with this on the other thread here: http://forum.xda-developers.com/showthread.php?t=2511815&page=29
Update: V4 is up - this version makes sure that ADB is accessible. Thank you @k1mu for helping me with this!
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
fabrilas said:
I want to ask you, why do you think the process on i9505 hangs on the line "cleaning up files" and does not automatically reboot the phone? You need to manually reboot it.
For the rest it works great!
Thank you
Click to expand...
Click to collapse
My guess would be these lines:
adb shell "su -c 'rm /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm /dev/com.mgyun.shua.su.daemon'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su'"
adb shell "su -c 'rm -rf /dev/com.mgyun.shua.su.daemon'"
The issue is that I cant remember if com.mgyun.shua.su and com.mgyun.shua.su.daemon are directories or files. If you could confirm for me which they are then I will be happy to fix my tool!
Thx
Angie
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Works also with Galaxy S4 Italy Gt-i9505 :good:
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
ComputerBro2 said:
it tells me that "device not found" any clues?
never mind the first statment if i put the file in the phone the run it from my computer it goes away. but I'm now going to put word for word what it tells me. "When prompted to grant root to ADB select yes. 'adb' is not recognized as an internal or external command, operable program or batch file. Once you have granted root to ADB press any key to continue... Press any key to continue . . .
but it never askes me to grant root to it it just sits there and does nothing and if i hit continue with out allowing it, it just deletes the su and unroots the phone. any clues about what I could be doing wrong
Click to expand...
Click to collapse
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
LilTechPrincess said:
If you are getting device not found that typically means that ADB is not able to access or find the phone. I would make sure that you close the VRoot tool as it will keep the debugging bridge tied up, and give you a device not found error. After you root you need make sure VRoot is closed before running my tool.
Click to expand...
Click to collapse
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
ComputerBro2 said:
okay i just needed to update my drivers witch is odd cause i just did it yesterday hmm. Anyway now it runs fine but it wont prompt me on my phone to allow root access to adb
Click to expand...
Click to collapse
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
k1mu said:
That "adb is not recognized.. " is because the batch file is not running with it's current directory in the folder where you extracted it.
@LilTechPrincess -
adding "cd %~dp0"
at the start of the clean_root.bat will ensure that it's able to find the files that it needs since that'll CD to the drive and path where the clean_root.bat was extracted.
Click to expand...
Click to collapse
Thank you very much for the help! Im still a newb! haha Anyhow, I updated my tool with your suggestion.
LilTechPrincess said:
So did it fix your root to SuperSU?
Also, does anyone know how I can prompt root to ADB easier than this? Currently I am doing this to try and force the Superuser prompt:
adb shell "su -c 'touch /sdcard/invoke-root'"
If anyone knows how to do this better please let me know!
Click to expand...
Click to collapse
No the adb won't start on my phone
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Bfitz26 said:
Does it also say no device found?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
No it freze on this
rm failed for /sdcard/install-recovery.sh, No such file or directory
when i disconnect the pone say not found for 4 or 5 times and finish
---------- Post added at 08:49 PM ---------- Previous post was at 08:28 PM ----------
I tri 3 times
try to wipe all data.
Next try is to reinstall last firmware update whit odin or it trip my knox 0x0 to 0x1 ?
MexyHKR said:
It say to me
rm failed for /sdcard/install-recovery.sh, No such file or directory
And now ? xD
Click to expand...
Click to collapse
Thats not a big deal. Basically, I removed the /sdcard/install-recovery.sh from the script earlier and forgot to not try and delete a file that doesnt exist... Ill fix that! haha That doesnt hurt anything at all. Sowwy!
Ok now im freeze on Cleaning Up Files....
Your link is down
Tomsgt said:
Your link is down
Click to expand...
Click to collapse
The link has 2 hh's in the http
eklipz3 said:
The link has 2 hh's in the http
Click to expand...
Click to collapse
thanks did notice that
Finaly dont work on my GS4
PDA: I9505XXUEMJ7
MODEM: I9505XXUEMJ7
CSC: I9505ITVEMJ8
Try 2 times after full wipe and emergency firmware restore.
Freeze on Cleaning etc...
Now need to go sleep 1:06AM in italy
Good night and sorry for bad speak
I speak like a fish trying to speak Russian
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..
How should I go about factory resetting my rooted, HD 7" that's running a different launcher? So that it can go back to as clean as possible and be updatable and used normally without bricking/dying. I heard it's dangerous to just use the native factory reset as it can end up with bricks.
Its running on some older firmware that was rootable not long after it became possible and is running Vire Launcher instead of the typical amazon launcher. I'd like to go back to Stock somehow.
Sorry for the double post but seriously no-one knows how to go back to fully default?
Shadowshinra said:
Sorry for the double post but seriously no-one knows how to go back to fully default?
Click to expand...
Click to collapse
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
DoLooper said:
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
Click to expand...
Click to collapse
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Shadowshinra said:
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Click to expand...
Click to collapse
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Click to expand...
Click to collapse
Definitely rooted, heck you yourself helped me do it a long time ago, even Root checker says i'm still rooted, I do have JMZ tool, the OTA section is gray though, reboot didn't help, will try the adb command
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Shadowshinra said:
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Click to expand...
Click to collapse
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
DoLooper said:
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
Click to expand...
Click to collapse
You mean the popup on the kindle? Now you mention it, It hasn't been popping up since I've been attempting this, so somehow I/it semi-unrooted itself despite the rootchecker saying it's fine? Or were the changed we did responsible?
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Shadowshinra said:
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Click to expand...
Click to collapse
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
DoLooper said:
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
Click to expand...
Click to collapse
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Shadowshinra said:
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Click to expand...
Click to collapse
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
DoLooper said:
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
Click to expand...
Click to collapse
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Shadowshinra said:
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Click to expand...
Click to collapse
@bibikalka, I totally forgot @Shadowshinra would have TWRP, coming from rooted OS4. Any problem with him following your steps here to restore stock? http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267 Thanks!
Prerequisites:
Dirty Santa
ADB
HOW TO: (UPDATE COMING SOON...)
Follow DirtySanta all the way through step 3.5
Step 1: On Windows, double-click "RUNMEFIRST.bat, DO NOT CLOSE THE LOG WINDOW THAT OPENS, then double-click "Step1.bat"
On Linux,
./RUNMEFIRST.sh
Step 2: Open a Separate Terminal, then run
./Step1.sh
Step 3: Wait for shell prompt then.
run-as con
chmod 0777 /storage/emulated/0/*
This will not give you full root access!
Please comment if you're willing to help me out in getting root.
Just so everyone knows I am not taking credit for writing any of the code, none of it was me, I just was fiddling try to create root and found this worked to get root over ADB.
when does this wear off?
tommy7115 said:
when does this wear off?
Click to expand...
Click to collapse
I have not done enough to know for sure, but all the changes you made are going to reset most likely be on a reboot.
abine45 said:
Prerequisites:
Dirty Santa
ADB
HOW TO:
Follow DirtySanta all the way through step 3.5
That should give you a temporary root. I am on android 6.0, not sure if this will work on five but I don't see why it wouldn't. from there i'm going to try to make root.
Just so everyone knows I am not taking credit for writing any of the code, none of it was me, I just was fiddling try to create root and found this worked to get root over ADB.
Click to expand...
Click to collapse
Would you please write a guide for doing root step by step?THX
alexanderzhang said:
Would you please write a guide for doing root step by step?THX
Click to expand...
Click to collapse
I will either tonight or tomorrow. I'm in the process to actually getting a full root, I think i'm on to something and may be able to get this to work. This is just a temporary thing for people to try.
abine45 said:
I will either tonight or tomorrow. I'm in the process to actually getting a full root, I think i'm on to something and may be able to get this to work. This is just a temporary thing for people to try.
Click to expand...
Click to collapse
OK, My mother language isn't Eng, so I can't understand the meaning of "Follow DirtySanta all the way through step 3.5".
Is your meaning that flollow the guide from step 1 to step 3.5?
Im not getting root access, root check is not recognizing it and neither is an app like freedom
Testing it right now. @alvislee[email protected]
---------- Post added at 11:00 PM ---------- Previous post was at 10:28 PM ----------
I got a tmp root shell. Now working on installing su and changing selinux status with chainfires tools.
alvinator94 said:
Testing it right now. @alvislee[email protected]
---------- Post added at 11:00 PM ---------- Previous post was at 10:28 PM ----------
I got a tmp root shell. Now working on installing su and changing selinux status with chainfires tools.
Click to expand...
Click to collapse
How did you achieve the root shell, I can't get it working.
tommy7115 said:
How did you achieve the root shell, I can't get it working.
Click to expand...
Click to collapse
Download v20.zip
extract it
run "RUNMEFIRST.bat"
give it a second and then run STEP1.bat
wait and itll show up as a normal shell "$"
then type in "run-as con" without the quotes
then you will see "#"
alvinator94 said:
Download v20.zip
extract it
run "RUNMEFIRST.bat"
give it a second and then run STEP1.bat
wait and itll show up as a normal shell "$"
then type in "run-as con" without the quotes
then you will see "#"
Click to expand...
Click to collapse
Yeah but then the next line does nothing, by that I mean chmod 0777 /storage/emulated/0/*
Plus even if that works how do I get root?
tommy7115 said:
Yeah but then the next line does nothing, by that I mean chmod 0777 /storage/emulated/0/*
Plus even if that works how do I get root?
Click to expand...
Click to collapse
Do you see the # symbol after you type run-as con
if so then i believe you have a temporary root shell.
by the way, the line after that is just giving elevated permissions to your entire internal storage, this part of the code does not apply to us as we do not need to give more permissions to anything on our internal storage as we will not be using them unlike the other several steps on that dirty santa post.
the problem is, even though we have a sort of root shell selinux is stopping us from being able to modify any of the other files.
alvinator94 said:
Do you see the # symbol after you type run-as con
if so then i believe you have a temporary root shell.
by the way, the line after that is just giving elevated permissions to your entire internal storage, this part of the code does not apply to us as we do not need to give more permissions to anything on our internal storage as we will not be using them unlike the other several steps on that dirty santa post.
the problem is, even though we have a sort of root shell selinux is stopping us from being able to modify any of the other files.
Click to expand...
Click to collapse
Thanks for clarifying that:good:
alvinator94 said:
Do you see the # symbol after you type run-as con
if so then i believe you have a temporary root shell.
by the way, the line after that is just giving elevated permissions to your entire internal storage, this part of the code does not apply to us as we do not need to give more permissions to anything on our internal storage as we will not be using them unlike the other several steps on that dirty santa post.
the problem is, even though we have a sort of root shell selinux is stopping us from being able to modify any of the other files.
Click to expand...
Click to collapse
What are you thinking to get full root from here?
Flash a modified boot img somehow that still let's the phone boot but gives us root even with the SElinux still set to enforcing. Go reading on the dirty cow thread and get caught up
Is this an option if I wanted to change my font or do something that required root? Would it survive past a reboot?
JRM_3 said:
Is this an option if I wanted to change my font or do something that required root? Would it survive past a reboot?
Click to expand...
Click to collapse
This is still exactly what you see when reading through the post. Please follow the main ROOT thread from Albine45 (patiently wait for Albine's frequent updates on progress) and when full root is achieved, you'll know and a guide will show up to walk you through. For now, you can change system fonts in your settings menu on Android. There are a few free built in fonts and others you can purchase. Just look through your settings menu.
snapz54 said:
This is still exactly what you see when reading through the post. Please follow the main ROOT thread from Albine45 (patiently wait for Albine's frequent updates on progress) and when full root is achieved, you'll know and a guide will show up to walk you through. For now, you can change system fonts in your settings menu on Android. There are a few free built in fonts and others you can purchase. Just look through your settings menu.
Click to expand...
Click to collapse
Thank you so much. I'll definitely be watching for full root?
After I run "run-as con" package 'con' is unknown
Any solutions?
I only need to delete or rename /system/bin/logd it's giving me some troubles, battery drain and over heating.
Enviado desde mi VS990 mediante Tapatalk
windows 7 supported???
I have a soft bricked HDX 8.9 Apollo. I've scoured dozens of threads about unbricking my Apollo device and I feel fairly confident I could unbrick my device if I could just keep my device on long enough to transfer my ~600MB rom, but my device only has ADB (with root) access for about 45 seconds before it reboots, interrupting my file transfer (getting "Connection reset by peer" transfer error when the device resets).
- I can boot to recovery and fastboot modes which stops the boot loop, but I don't have ADB access in either of these modes.
- I've tried "adb -d shell stop" (which is a command I've seen used to stop a boot loop on other devices) but this does not prevent the boot loop.
Surprisingly no one in any of the threads I checked mentioned a similar problem so I guess I'll just ask here. I can give details if you want but really I just need to know if there's any way I can pause the boot loop while maintaining ADB access and I should be able to handle the rest.
Jabbernaut said:
I have a soft bricked HDX 8.9 Apollo. I've scoured dozens of threads about unbricking my Apollo device and I feel fairly confident I could unbrick my device if I could just keep my device on long enough to transfer my ~600MB firmware, but my device only has ADB (with root) access for about 45 seconds before it reboots, interrupting my file transfer (getting "Connection reset by peer" transfer error when the device resets).
- I can boot to recovery and fastboot modes which stops the boot loop, but I don't have ADB access in either of these modes.
- I've tried "adb -d shell stop" (which is a command I've seen used to stop a boot loop on other devices) but this does not prevent the boot loop.
Surprisingly no one in any of the threads I checked mentioned a similar problem so I guess I'll just ask here. I can give details if you want but really I just need to know if there's any way I can pause the boot loop while maintaining ADB access and I should be able to handle the rest.
Click to expand...
Click to collapse
No clue what you're trying to do. I'll throw this out, use the Terminal found in recovery mode.
---------- Post added at 09:30 PM ---------- Previous post was at 08:37 PM ----------
gwardsc65 said:
No clue what you're trying to do. I'll throw this out, use the Terminal found in recovery mode.
Click to expand...
Click to collapse
With all the necessary files along with the commands ready to copy and paste, you could replace recovery (if needed), aboot, and unlock the bootloader in 45 seconds or less. Boot into recovery and flash whatever you wanted to. Other options you could look into are bulk mode and 1-Click.
gwardsc65 said:
With all the necessary files along with the commands ready to copy and paste, you could replace recovery (if needed), aboot, and unlock the bootloader in 45 seconds or less. Boot into recovery and flash whatever you wanted to. Other options you could look into are bulk mode and 1-Click.
Click to expand...
Click to collapse
Absolutely agree. Forget the dated unbrick threads. Use 1-click or manually replace the bootloader and recovery. If pursuing the latter don't worry about immediately unlocking; that can be done later after device is stable.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
https://forum.xda-developers.com/kindle-fire-hdx/general/how-to-root-unlock-hdx-noobies-t3916167
Sorry for the limited info, but I can offer more clarity now that I have more time. Basically I soft-bricked an Apollo back in 2015 by accidentally flashing a rom designed for Safestrap v4 onto Safestrap 3.75. The last thing I had done before flashing the rom was I rolled back to 3.2.8 and towelrooted it. At the time I declared it a loss.
So yeah I guess I need to replace the bootloader and recovery. I don't have access to a linux or mac machine atm, so I guess I'll be doing this manually.
I was able to get my unlock file and and push twrp and aboot to /sdcard/ just fine, and it looks like I was able to get superuser in adb shell.
Code:
C:\ADB>adb shell
[email protected]:/ $ su
255|[email protected]:/ $ I have SU now right?
but when I run
Code:
255|[email protected]:/ $ dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
it returns
Code:
/dev/block/platform/msm_sdcc.1/by-name/recovery: cannot open for write: Permission denied
Do I need to change folder permissions to be able to execute this? If so, how do I do this?
EDIT: Oh I just realized I guess 255 isn't SU? Seems strange that the su command is going through without error if I don't have root access.
It looks like the one-click bootloader unlock method does not require root. Is there a way to accomplish a rootless unlock without one-click?
Jabbernaut said:
Sorry for the limited info, but I can offer more clarity now that I have more time. Basically I soft-bricked an Apollo back in 2015 by accidentally flashing a rom designed for Safestrap v4 onto Safestrap 3.75. The last thing I had done before flashing the rom was I rolled back to 3.2.8 and towelrooted it. At the time I declared it a loss.
So yeah I guess I need to replace the bootloader and recovery. I don't have access to a linux or mac machine atm, so I guess I'll be doing this manually.
I was able to get my unlock file and and push twrp and aboot to /sdcard/ just fine, and it looks like I was able to get superuser in adb shell.
Code:
C:\ADB>adb shell
[email protected]:/ $ su
255|[email protected]:/ $ I have SU now right?
but when I run
Code:
255|[email protected]:/ $ dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
it returns
Code:
/dev/block/platform/msm_sdcc.1/by-name/recovery: cannot open for write: Permission denied
Do I need to change folder permissions to be able to execute this? If so, how do I do this?
EDIT: Oh I just realized I guess 255 isn't SU? Seems strange that the su command is going through without error if I don't have root access.
It looks like the one-click bootloader unlock method does not require root. Is there a way to accomplish a rootless unlock without one-click?
Click to expand...
Click to collapse
Bulk Mode:
https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
Thanks for the tip! Unfortunately I do not have access to the filesystem via windows, I can only copy files over via ADB. So unless there's some way to gain access to the filesystem with an ADB command I'm probably sunk there
So that's it then I presume?
Jabbernaut said:
Thanks for the tip! Unfortunately I do not have access to the filesystem via windows, I can only copy files over via ADB. So unless there's some way to gain access to the filesystem with an ADB command I'm probably sunk there
So that's it then I presume?
Click to expand...
Click to collapse
Nope. There's usually a way if the HDX boots into recovery or bootloader. If recovery is twrp and not stock, it may be possible to issues the commands to replace aboot via the Terminal. It's not ideal, but may work. I think you really need to take another look at Bulk Mode. Follow the instructions very carefully or you will be out of luck. If you have any doubts, don't attempt using Bulk Mode.
gwardsc65 said:
Nope. There's usually a way if the HDX boots into recovery or bootloader. If recovery is twrp and not stock, it may be possible to issues the commands to replace aboot via the Terminal. It's not ideal, but may work. I think you really need to take another look at Bulk Mode. Follow the instructions very carefully or you will be out of luck. If you have any doubts, don't attempt using Bulk Mode.
Click to expand...
Click to collapse
I guess I should have clarified, I don't have twrp, I only have access to stock recovery. If I had twrp running I probably wouldn't be here lol.
Unless there is another thread that explains how to use this "Bulk Mode" without access to the tablet's filesystem in Windows, in the guide linked above, the very first step is to pull the diskindex from the drive as it appears in Windows. Obviously this will fail because it is not mounted, but here is the result with the tablet connected and ADB working anyway:
Code:
C:\ADB>wmic partition where index=22 get diskindex
No Instance(s) Available.
C:\ADB>wmic partition where (index=17 and numberofblocks=20480) get diskindex
No Instance(s) Available.
C:\ADB>wmic partition where (index=5 and numberofblocks=4096) get diskindex
No Instance(s) Available.
Without a diskindex reference to the tablet's drive, I can't proceed to the next step to copy twrp and aboot into the recovery folder. And as far as I can tell I don't have root anymore so I can't do it via ADB.
So I would assume I'm dead in the water here since as far as I can tell I don't have any access to the folders I need to place the files in? Unless I can like directly sideload them or something. I have virtually nothing to lose here so I'll try whatever.
Just to clarify, I definitely don't have root? What exactly does it mean if the "su" command does not throw an error but instead returns "255|[email protected]:/ $" ?
Code:
C:\ADB>adb shell
[email protected]:/ $ su
255|[email protected]:/ $ In what way did my permissions change here?
Jabbernaut said:
I guess I should have clarified, I don't have twrp, I only have access to stock recovery. If I had twrp running I probably wouldn't be here lol.
Unless there is another thread that explains how to use this "Bulk Mode" without access to the tablet's filesystem in Windows, in the guide linked above, the very first step is to pull the diskindex from the drive as it appears in Windows. Obviously this will fail because it is not mounted, but here is the result with the tablet connected and ADB working anyway:
Code:
C:\ADB>wmic partition where index=22 get diskindex
No Instance(s) Available.
C:\ADB>wmic partition where (index=17 and numberofblocks=20480) get diskindex
No Instance(s) Available.
C:\ADB>wmic partition where (index=5 and numberofblocks=4096) get diskindex
No Instance(s) Available.
Without a diskindex reference to the tablet's drive, I can't proceed to the next step to copy twrp and aboot into the recovery folder. And as far as I can tell I don't have root anymore so I can't do it via ADB.
So I would assume I'm dead in the water here since as far as I can tell I don't have any access to the folders I need to place the files in? Unless I can like directly sideload them or something. I have virtually nothing to lose here so I'll try whatever.
Just to clarify, I definitely don't have root? What exactly does it mean if the "su" command does not throw an error but instead returns "255|[email protected]:/ $" ?
Code:
C:\ADB>adb shell
[email protected]:/ $ su
255|[email protected]:/ $ In what way did my permissions change here?
Click to expand...
Click to collapse
Your best bet is to use 1-Click. 1-Click basically does the same thing as Bulk Mode, but does it automatically for you. Bulk Mode hint - bootloader.
gwardsc65 said:
Your best bet is to use 1-Click. 1-Click basically does the same thing as Bulk Mode, but does it automatically for you. Bulk Mode hint - bootloader.
Click to expand...
Click to collapse
Does 1-click not require USB access to the filesystem or root access? I guess I could install and run linux on a flash drive just to test this but it would be nice to know if the interface to the device is likely to work, I don't know anything about VirtualBox. If we're not sure I'll probably try it later.