Related
Hi,
The USB socket on my phone is not working apart from charging. I can get into download mode but do not want to risk flashing a stock rom via odin as if the USB fails mid-flash I will be in a far worse situation.
I followed the old rooting guide as I wanted to remain stock.
I've got my CPW stock rom and normal "secure" kernel (flashed back after gaining root)
I am rooted and have superuser app visible in the application list.
Is it possible to permanently unroot using a terminal editor or an apk from this position?
Should I just delete the superuser app? How can I delete busybox? Would a factory reset get rid of my root?
Really desparate so I can return my phone for repair!
Thanks
Bump. I have exactly the same problem :-(
In fact I don't even have the original rom or kernel saved and my phone won't charge
Are you trying to use warranty? Well, at last option you could try odin and going right and going wrong you should be fine. Going right you already know then answer. Going bad, since it wont boot, the tech guy from service center cannot see anything since it wont power on. He will have to fix and cannot proove that the phone was rooted.
please post here your info. I am trying to build a large DB about this issue, is it software or hardware related. There have been a lot of posts about this issue popping up.
http://forum.xda-developers.com/showthread.php?t=1188857
Kies recognised me as stock so I'm not prepared to risk flashing using a dodgy usb connection and doing software damage.
Please, does anyone know whether I can unroot just using the phone?
Sent from my GT-I9100 using XDA App
Fire up a terminal app, then:
Code:
su
busybox mount -o rw,remount /system
rm /system/xbin/su
rm /system/xbin/busybox
rm /system/app/Superuser.apk [I](this may error out with "file not found" - that it OK, only means Superuser app is installed in /data/app, perfectely fine)[/I]
Reboot to recovery and do a factory reset (wipe user data).
It's not perfect (leaves a crapload of orphaned symlinks in /system/xbin) but it's good enough IMO, I doubt they'll do a FS sweep for root remains.
I managed to break the Wifi on my tablet. I had root, accidentally replaced a file I shouldn't have, thought that wiping and flashing the .21 update would work...it didn't. It wouldn't flash because a system file had been modified.
Because I broke the wifi, I can't unlock. I basically am stuck waiting for .21 to be rooted.
Devs, are we close to root? I'm sure you're working on it and I applaud your efforts. Is this firmware super closed off? I'm not asking for an ETA, but maybe more of a status update. Just let me know there is hope
EDIT: I fixed it! I was able to pull an .apk of OTA Voodoo Rootkeep from a previous Titanium Backup file. I installed the app, and it restored root for me! Its possible that I was already still rooted, but without the ability to d/l apps I couldn't do anything about it. Anyway, I'm back with a rooted .21!
I think I had a similar issue....was using wifi tethered to phone...with modded wpa files....Couldn't OTA for .21......no computer/no router to get a wifi connection.
Went to Mickey D's for a free wifi connection....downloaded and installed .15 (for orig files) via SD card.
After that was finished, used OTA to download .21 ...if there are still issues, download it and manually install it via SD card.
Here's instructions to do it via SD card:
http://service.asus.com/TF201_fwupdate
Yeah I had to do that method when I first updated to .21. But then, after .21 I couldn't tether even though the chanelog said ad hoc wifi was supported. So I tried that method again, and broke it. Now I have no root and no wifi.
Waiting for someone to find root for .21 is killing me. lol
Any Devs want to chime in and give us an update on the .21 root process?
http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/
use this. windows didnt work for me, drivers were messed up.
i used the mac method with no drivers required. (same with linux) and it worked flawlessly. pushed CWM using this, then flashed primeval .21 firmware.
stock .21 but with root.
requires unlock
Thanks, but I can't even unlock due to no data connection
I wonder if I could do it with an USB Ethernet dongle?
We definately need some tool to recover from such positions... NVflash or anything. This way its just too risky to temper with files if you're not unlocked imho. I remember about 3-4 cases where people got issues because of trying to improve stuff by editing files like build.prop etc.
Gogo devs, Asus, nVidia... Anyone, give us some tools to be safe
Definitely. I purchased a square trade warranty so that when I unlock I am still covered. However, why should I have to?
I sincerely hope a dev can get us root one .21 at least, and maybe some kind of unlock tool that doesn't report to Asus. And of course, NVFlash
the unlock is just an APK from asus? cant download that and put on SD?
malaeus said:
the unlock is just an APK from asus? cant download that and put on SD?
Click to expand...
Click to collapse
Its simple enough to install, but the app requires a connection with Asus' servers to record the Prime's serial number and then distribute a unique unlock key.
McLiarpants said:
Its simple enough to install, but the app requires a connection with Asus' servers to record the Prime's serial number and then distribute a unique unlock key.
Click to expand...
Click to collapse
Ah was not aware of such communication. Sorry :-(
Have you tried going online with a usb ethernet dongle?
I was going to look into this option, but I was able to fix my wifi!
I pulled Titanium Backup .apk files of my old apps and installed voodoo rootkeeper. it restored root (its possible I never actually lost root, just the ability to d/l apps like root explorer because of broken wifi)! I then loaded my backup of root explorer and copied the correct wpa_supplicant file.
I then immediately unlocked and flashed Virtuous Prime .21. I purchased a square trade warranty with accidental damage protection in case I have any problems with it.
It would be nice to know if I could do that for my unrooted Prime I accidentally upgraded to .21 before rooting. My other Prime is on .21 with root.
I'm sure it is because you had root before, but maybe it's worth a try.
McLiarpants said:
I purchased a square trade warranty with accidental damage protection in case I have any problems with it.
Click to expand...
Click to collapse
Has anyone confirmed that squaretrade considers unlocking and intentionally voiding your warranty "normal use"? I too am getting disheartened waitig for .21 root method. I would love to install custom rom and never have to worry about it again if squaretrade will cover a bricked device. However, I'm afraid if I void my warranty ASUS might decide not to honor the device with warranty issues such as gps dongles, etc.
casey225 said:
Has anyone confirmed that squaretrade considers unlocking and intentionally voiding your warranty "normal use"? I too am getting disheartened waitig for .21 root method. I would love to install custom rom and never have to worry about it again if squaretrade will cover a bricked device. However, I'm afraid if I void my warranty ASUS might decide not to honor the device with warranty issues such as gps dongles, etc.
Click to expand...
Click to collapse
What I've heard from other people is that the warranty says that they don't support intentional hardware or software modifications that would also void the manufacturer's warranty. Such as unlocking or opening the unit. However, if you have the accidental warranty and you drop it after being unlocked, they will fix it or replace it.
So if you have a problem with it after unlocking, it may need an "accident" to happen before you send it into ST.
clouds5 said:
We definately need some tool to recover from such positions... NVflash or anything. This way its just too risky to temper with files if you're not unlocked imho. I remember about 3-4 cases where people got issues because of trying to improve stuff by editing files like build.prop etc.
Gogo devs, Asus, nVidia... Anyone, give us some tools to be safe
Click to expand...
Click to collapse
there is a method to recover from this, grab the full update not the patch one from asus website, put it on a microsd card, and boot recovery
McLiarpants said:
So if you have a problem with it after unlocking, it may need an "accident" to happen before you send it into ST.
Click to expand...
Click to collapse
Understood I would still have to hope that Squaretrade doesn't determine the true problem, otherwise, would be SOL on all fronts. I will try to wait it out for now, but, I think I hear Virtuous Prime calling my name as I type this message.
casey225 said:
Understood I would still have to hope that Squaretrade doesn't determine the true problem, otherwise, would be SOL on all fronts. I will try to wait it out for now, but, I think I hear Virtuous Prime calling my name as I type this message.
Click to expand...
Click to collapse
I am running VP now, but I really like AOKP. The only reason I'm running VP is because Polaris isn't working on AOKP. I know it has some bugs, but I can't work with the lag between hitting a key and the letter showing on the screen in other office apps. I also haven't been willing to pay $15-$30 for an app to see how laggy it is.
lilstevie said:
there is a method to recover from this, grab the full update not the patch one from asus website, put it on a microsd card, and boot recovery
Click to expand...
Click to collapse
The update wont install if any of the system files are modified. It would be nice if it did, but it doesn't, unfortunately.
TB Pro restore with rooted .21 (NOT UNLOCKED)
So I had a thought and I am not sure that this will work. I have a TF101 that was rooted on 9.4.2.17 then upgraded to 9.4.2.21 (without any rootkeeper installed). Still have root but decided to install Voodoo RootKeeper just in case.
I have TB Pro installed and the Dev claims that you can restore to dissimilar hardware. My thought is to restore the APP+DATA+SYSTEM backup to my TF201 that is currently running 9.4.2.21 without root.
Any thoughts on this idea?
Niles
Tried getting help before the L9 had its own section to no avail, so I'm cutting it short. Basically, I successfully rooted my L9 and everything was good for a while, ended up with the famous "insufficient storage" error, along with the "searching for up" error and after some research I resorted to factory reset. My root was removed, BUT SuperSu is stuck as a system file and I can no longer achieve root access using the method found here. I'm trying to find a way to either re-root, or at least remove all traces of the previous root so I can return/exchange it. Any idea's other than factory restore/hard reset/flashing with stock firmware??? The T-Mobile/US version is not available from LG...
Do you have CWM recovery?
John.
sdfyhpromotions said:
Tried getting help before the L9 had its own section to no avail, so I'm cutting it short. Basically, I successfully rooted my L9 and everything was good for a while, ended up with the famous "insufficient storage" error, along with the "searching for up" error and after some research I resorted to factory reset. My root was removed, BUT SuperSu is stuck as a system file and I can no longer achieve root access using the method found here. I'm trying to find a way to either re-root, or at least remove all traces of the previous root so I can return/exchange it. Any idea's other than factory restore/hard reset/flashing with stock firmware??? The T-Mobile/US version is not available from LG...
Click to expand...
Click to collapse
Hmmm. . . that's weird. I did the same thing. . well I had to hard reset and the superuser was still there but try doing a hard reset again or just try to re-root without the hard reset. I managed to re-root as well with no problems, thank goodness. Listen I would suggest that you have at least three apps when you root: 1) Link2SD 2)Titanium Backup 3)Root Explorere these three apps have saved my life dozens of times on my old phone. Now I'm backing up my stuff on the L9 with CWM and Titanium Backup AND the backup tool that's on the T-Mobile version.
Honestly truth be told the only thing you can keep trying is to root again as well as a factory reset again if that doesn't work the last option is getting a new one I have not rooted yet as for I'm worry til we get unlocked bootloader or a USA kdz file after my last situation I'm being careful
Sent from my Lg Optimus L9 P769BK using xda-premium
I'm fairly knowledgeable when it comes to the whole rooting process, and have rooted a few dozen devices of various variety and have rarely resorted to asking/needing help because I almost always seem to find a work around. Link2SD was the first program installed, other than BusyBox ad Root Explorer's but TitaniumBackup is where I started getting the "insufficient memory" error so I have no valid recovery. I've both Hard Resetted and Factory Restored who knows how many times, but can no longer get to/past the "Restore" section of the rooting process... I guess I'll just have to suck it up, and stick with just the internal memory until a ROM is developed or USA kdz file is released as previously stated. Thanks for the prompt response everybody!
PS, THIS is why you should unroot before Factory Restore/Hard Reset:
"======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (13.10.2012) v15 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
cannot stat 'stuff/busybox': No such file or directory
Pushing su binary ....
cannot stat 'stuff/su': No such file or directory
Pushing Superuser app
cannot stat 'stuff/Superuser.apk': No such file or directory
Making busybox runable ...
/system/bin/sh: chmod: not found
.
adb: unable to open file stuff/fakebackup.ab
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ..." ^^^^ It isn't joking about the "forever" :/ lol
If you return to a retail store they don't check every little detail. If you mail it back i doubt the process is any different. Techs reflash it anyway. Nobody will do forensics first and issue or deny refunds later.
guest_2011 said:
If you return to a retail store they don't check every little detail. If you mail it back i doubt the process is any different. Techs reflash it anyway. Nobody will do forensics first and issue or deny refunds later.
Click to expand...
Click to collapse
Yeah, I know... They do however instantly deny a return if they see SuperSu/SuperUser installed :/
sdfyhpromotions said:
Yeah, I know... They do however instantly deny a return if they see SuperSu/SuperUser installed :/
Click to expand...
Click to collapse
I returned one unrooted to Best Buy. Only took my dr license but didn't check the phone. Returned one nexus 4 but the unroot/lock bootloader with the toolkit didn't go well. I was so tired and upset returned as is. No problems with google. I didn't even check for SuperSu. Last year rma'ed a rooted Samsung for warranty repair. Back to stock didn't unroot or remove Su. Came back repaired and reflashed with updated fw. Had to unlock subsidy and root again. My experience.
Here's my situation. I rooted MJ7 using rootjunky via vroot and then flashed to get rid of the chinese. I then installed safestrap and created a new romslot and put Hyperdrive on my device. Then... my usb port on my device quit working. Verizon is sending me a replacement. So I read somewhere to take the MK2 update to lose root and factory reset which supposedly was going to get me back to a point where I can send it to Verizon. I did this and unfortunately the SuperSu icon is still there and the Custom padlock boot animation is still there. I never did unroot through the terminal nor uninstall safestrap. SO..... what are my options here? USB still doesn't work so I cant reroot via USB and try to gracefully unroot and uninstall SuperSu. Is there a way to root directly on the device? Thanks.
G
rolltide78 said:
Here's my situation. I rooted MJ7 using rootjunky via vroot and then flashed to get rid of the chinese. I then installed safestrap and created a new romslot and put Hyperdrive on my device. Then... my usb port on my device quit working. Verizon is sending me a replacement. So I read somewhere to take the MK2 update to lose root and factory reset which supposedly was going to get me back to a point where I can send it to Verizon. I did this and unfortunately the SuperSu icon is still there and the Custom padlock boot animation is still there. I never did unroot through the terminal nor uninstall safestrap. SO..... what are my options here? USB still doesn't work so I cant reroot via USB and try to gracefully unroot and uninstall SuperSu. Is there a way to root directly on the device? Thanks.
G
Click to expand...
Click to collapse
The saferoot method might be able to be done via terminal emulator, the install.sh seems to be all shells commands. Don't see why you couldn't modify it to run from the phone, or enter the commands manually. Someone correct me if I'm wrong...
Edit:
Nvm. It states it cannot be ran from terminal emulator.
rolltide78 said:
Here's my situation. I rooted MJ7 using rootjunky via vroot and then flashed to get rid of the chinese. I then installed safestrap and created a new romslot and put Hyperdrive on my device. Then... my usb port on my device quit working. Verizon is sending me a replacement. So I read somewhere to take the MK2 update to lose root and factory reset which supposedly was going to get me back to a point where I can send it to Verizon. I did this and unfortunately the SuperSu icon is still there and the Custom padlock boot animation is still there. I never did unroot through the terminal nor uninstall safestrap. SO..... what are my options here? USB still doesn't work so I cant reroot via USB and try to gracefully unroot and uninstall SuperSu. Is there a way to root directly on the device? Thanks.
G
Click to expand...
Click to collapse
Perhaps post this in saferoot thread in dev forum. Smart guys hangout there
safestrap enabled, Hyperdrive driven
decaturbob said:
Perhaps post this in saferoot thread in dev forum. Smart guys hangout there
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Unfortunately I haven't had 10 posts yet so it won't let me post anything there.
rolltide78 said:
Unfortunately I haven't had 10 posts yet so it won't let me post anything there.
Click to expand...
Click to collapse
Would obtaining a stock rom and flashing with Odin get me through this or will that flag the counter?
rolltide78 said:
Would obtaining a stock rom and flashing with Odin get me through this or will that flag the counter?
Click to expand...
Click to collapse
A full-wipe stock ROM will clear the custom flag. However, if you can't get USB to work, I'm not sure what you can do.
k1mu said:
A full-wipe stock ROM will clear the custom flag. However, if you can't get USB to work, I'm not sure what you can do.
Click to expand...
Click to collapse
Dang. We'll can you provide me with a link to the stock? The ones I've found lead me not too confident.
rolltide78 said:
Dang. We'll can you provide me with a link to the stock? The ones I've found lead me not too confident.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2578209
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
So this will keep Knox/etc alone? It still baffles me why we can't root without using a PC.
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
Also, one other thing to add... it does charge verrrrrryyy slowly when its powered off and connected. It loops and vibrates the charging icon with a grey spinning icon. It does charge though (about a 1/4 over a 4 hour span). So its not completely not working..whichi is odd.
rolltide78 said:
Also, one other thing to add... it does charge verrrrrryyy slowly when its powered off and connected. It loops and vibrates the charging icon with a grey spinning icon. It does charge though (about a 1/4 over a 4 hour span). So its not completely not working..whichi is odd.
Click to expand...
Click to collapse
Are you using the USB cable that came with the phone? Some other USB cables will charge, but won't transfer data. So, it may be the cable and not the USB port. Just a thought!
rolltide78 said:
So this will keep Knox/etc alone? It still baffles me why we can't root without using a PC.
Click to expand...
Click to collapse
You can root using a Mac, or a Linux system. But I don't think that's what you're asking I think what you mean is "why do you need another computer to do this?"
The reason that you need a separate computer is that the security policy on the Verizon device doesn't allow you to push a file to the phone and make it executable. i.e. you can't get it to run.
Specifically, to root you need to run the supplied "getroot" program. ADB can be used to push that to the phone and make it executable:
adb push getroot /data/local/tmp/
adb shell chmod 755 /data/local/tmp/getroot
Click to expand...
Click to collapse
So you now have a getroot program that can be executed to root the phone. The "chmod" command sets the "executable" bits so the program can run. You've got to do that to allow it to get started and root the phone.
So, let's get rid of the PC. Copy the getroot program to the external SD card. OK, so it's now on the phone.
You can't run programs from that external card, and can't set it to be executable. But the rooting scripts writes it to another place and marks it executable, so why not just do that from a terminal emulator prompt? So, it shoudl be easy - copy /mnt/extSdCard/getroot to /data/local/tmp/getroot.
Cool, that works. So now change it to be executable so you can run it:
[email protected]: / $ chmod 755 /data/local/tmp/getroot
unable to chmod /data/local/tmp/getroot: Operation not permitted
Click to expand...
Click to collapse
Oops. You can't do that. Without that, you can't run it. Game over.
I'm not using adb to force use of a separate computer to run the root. I'm doing it because the policy on the i545 doesn't allow you to push a program onto the phone and run it unless you do it via ADB.
Some phones/tablets aren't so locked down, and so may be able to use a terminal emulator to do this. I'm going to be posting info this weekend on how to do that, which may help to get rid of the PC, kind of.
Any other questions?
As far as the "Custom" status goes, this is a FAQ. Short answer:
Do you want root? OK, then you will be running a non-standard system, i.e. customized.
Do you want to avoid seeing the Custom flag? If so, either run stock, unrooted, or use the Wanam hack to fake the status.
If you don't want to be running custom software, then don't. Go stock.
Finally, "Knox" is not a thing, it's a series of protective mechanisms, some of which we can disable on rooted phones. We can't override the Knox bootloader flag ("Knox warranty void") flag, however. Apparently the Knox container software uses that to disable the ability to use a container.
k1mu said:
You can root using a Mac, or a Linux system. But I don't think that's what you're asking I think what you mean is "why do you need another computer to do this?"
The reason that you need a separate computer is that the security policy on the Verizon device doesn't allow you to push a file to the phone and make it executable. i.e. you can't get it to run.
Specifically, to root you need to run the supplied "getroot" program. ADB can be used to push that to the phone and make it executable:
So you now have a getroot program that can be executed to root the phone. The "chmod" command sets the "executable" bits so the program can run. You've got to do that to allow it to get started and root the phone.
So, let's get rid of the PC. Copy the getroot program to the external SD card. OK, so it's now on the phone.
You can't run programs from that external card, and can't set it to be executable. But the rooting scripts writes it to another place and marks it executable, so why not just do that from a terminal emulator prompt? So, it shoudl be easy - copy /mnt/extSdCard/getroot to /data/local/tmp/getroot.
Cool, that works. So now change it to be executable so you can run it:
Oops. You can't do that. Without that, you can't run it. Game over.
I'm not using adb to force use of a separate computer to run the root. I'm doing it because the policy on the i545 doesn't allow you to push a program onto the phone and run it unless you do it via ADB.
Some phones/tablets aren't so locked down, and so may be able to use a terminal emulator to do this. I'm going to be posting info this weekend on how to do that, which may help to get rid of the PC, kind of.
Any other questions?
As far as the "Custom" status goes, this is a FAQ. Short answer:
Do you want root? OK, then you will be running a non-standard system, i.e. customized.
Do you want to avoid seeing the Custom flag? If so, either run stock, unrooted, or use the Wanam hack to fake the status.
If you don't want to be running custom software, then don't. Go stock.
Finally, "Knox" is not a thing, it's a series of protective mechanisms, some of which we can disable on rooted phones. We can't override the Knox bootloader flag ("Knox warranty void") flag, however. Apparently the Knox container software uses that to disable the ability to use a container.
Click to expand...
Click to collapse
Thank you very much for the explanations. I love it! First...I've tried using multiple USB cables and no go (except for the slooowww charge using the vibrate behavior loop). Any microusb cable used to work fine. I want root but just not on this device as I'm sending it in to Verizon. If I could get rid of the custom boot animation and the SuperSu app I wouldn't be wary but I just feel awkward sending a device back with these two items still visible ont he device. I'll root and load hypervisor on the new device when it arrives. Now, I'm just trying to get it to a state to send back and am trying to figure out my options.
rolltide78 said:
Thank you very much for the explanations. I love it! First...I've tried using multiple USB cables and no go (except for the slooowww charge using the vibrate behavior loop). Any microusb cable used to work fine. I want root but just not on this device as I'm sending it in to Verizon. If I could get rid of the custom boot animation and the SuperSu app I wouldn't be wary but I just feel awkward sending a device back with these two items still visible ont he device. I'll root and load hypervisor on the new device when it arrives. Now, I'm just trying to get it to a state to send back and am trying to figure out my options.
Click to expand...
Click to collapse
Have you used the SuperSU "full unroot" setting to remove it? That'll get rid of SuperSU at the very least;
My Saferoot thread has unrooting info in post 2 - worth trying, especially before killing SuperSU.
k1mu said:
Have you used the SuperSU "full unroot" setting to remove it? That'll get rid of SuperSU at the very least;
My Saferoot thread has unrooting info in post 2 - worth trying, especially before killing SuperSU.
Click to expand...
Click to collapse
See that's just it....I took the MK2 OTA update from MJ7 thinking that is how to unroot and now I no longer have root. I get the binary not found issue when I try to launch supersu. Root checker confirms I no longer have root.
k1mu said:
You can root using a Mac, or a Linux system. But I don't think that's what you're asking I think what you mean is "why do you need another computer to do this?"
The reason that you need a separate computer is that the security policy on the Verizon device doesn't allow you to push a file to the phone and make it executable. i.e. you can't get it to run.
Specifically, to root you need to run the supplied "getroot" program. ADB can be used to push that to the phone and make it executable:
So you now have a getroot program that can be executed to root the phone. The "chmod" command sets the "executable" bits so the program can run. You've got to do that to allow it to get started and root the phone.
So, let's get rid of the PC. Copy the getroot program to the external SD card. OK, so it's now on the phone.
You can't run programs from that external card, and can't set it to be executable. But the rooting scripts writes it to another place and marks it executable, so why not just do that from a terminal emulator prompt? So, it shoudl be easy - copy /mnt/extSdCard/getroot to /data/local/tmp/getroot.
Cool, that works. So now change it to be executable so you can run it:
Oops. You can't do that. Without that, you can't run it. Game over.
I'm not using adb to force use of a separate computer to run the root. I'm doing it because the policy on the i545 doesn't allow you to push a program onto the phone and run it unless you do it via ADB.
Some phones/tablets aren't so locked down, and so may be able to use a terminal emulator to do this. I'm going to be posting info this weekend on how to do that, which may help to get rid of the PC, kind of.
Any other questions?
As far as the "Custom" status goes, this is a FAQ. Short answer:
Do you want root? OK, then you will be running a non-standard system, i.e. customized.
Do you want to avoid seeing the Custom flag? If so, either run stock, unrooted, or use the Wanam hack to fake the status.
If you don't want to be running custom software, then don't. Go stock.
Finally, "Knox" is not a thing, it's a series of protective mechanisms, some of which we can disable on rooted phones. We can't override the Knox bootloader flag ("Knox warranty void") flag, however. Apparently the Knox container software uses that to disable the ability to use a container.
Click to expand...
Click to collapse
I wish the moderators were more helpful so we could have a number of stickies in these forums. We could save so many from screwing their phones up as well as saving us a lot of time in constantly explaining the same stuff over and over again because some new comers don't want to take the necessary time to research the process. As you can tell, I'm getting a bit testy with new posters in some of my replies because its so obvious they put in so little research into what their phones are capable of taking for mods. This explains the background and how and why ADB needs to be understood as well as the ODIN process before you take the plunge. Three thumbs up to you!
rolltide78 said:
See that's just it....I took the MK2 OTA update from MJ7 thinking that is how to unroot and now I no longer have root. I get the binary not found issue when I try to launch supersu. Root checker confirms I no longer have root.
Click to expand...
Click to collapse
I apologize for my lack of experience with rooted with the Android platform. I think my downfall was relying too much on youtube videos by folks like rootjunky and galaxys4root. They are excellent at obtaining root but not so much on removing root and getting rid of the Custom screens, etc. When I tried to come here it was a bit overwhelming with all the variants, versions, and options. I thought I was doing the correct methods. I'm going to look into adb and understand more of the inter-workings now. Hopefully it won't be an issue with Verizon but I just wanted to do as much as I could to get it back to stock given the issues I have with my device and USB.
Am I completely out of luck removing the padlock custom?
rolltide78 said:
Am I completely out of luck removing the padlock custom?
Click to expand...
Click to collapse
If you can't get your device to be recognized over USB, you're kind of stuck.
Typically, you'll at least see the "Verizon Mobile" disk drive show up when you plug it in. If you see that, try running the VZW_Software_upgrade_assistant.exe that appears - that will flash stock and clear the "Custom" flag.
rolltide78 said:
I think my downfall was relying too much on youtube videos...
Click to expand...
Click to collapse
Bingo! Your modifying a $700 device based on YouTube videos. At bare minimum one should take the time to read and understand the complete process. Yes it can be very overwhelming because of all the different information contained here. Stick with reading the most popular threads in the topic you want to learn about. They are generally up to date and contain answers to most questions.
Sent from my SM-T310 using Tapatalk
OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
Solution may be here soon.
No one has the stock rom on hand yet. We are working on building a custom recovery for the phone, so please be patient.
Hopefully we can have a working recovery by this weekend, then you will have a way to still access your phone.
What files did you mess up on your phone? If i know the files, I can get someone to upload the files and then you can push the files to your phone using adb. If you haven't yet, I would recommend unlocking your bootloader via the instructions here:
http://forum.xda-developers.com/showthread.php?t=2546455
By unlocking the bootloader, you will be eligible to test the custom recovery as soon as it is available. Also, list the foiles you messed up, so that we can possibly upload them for you.
It will be a while until someone can form a stock rom update.zip for you.
Also, you can view the progress that we are making on the custom recovery.
amamartin999 said:
OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
Click to expand...
Click to collapse
You don't want to go into details but you still want someone to help you? Hahahahaha!!!
Good luck with that plan!
CtrlAltDelIrl said:
You don't want to go into details but you still want someone to help you? Hahahahaha!!!!
Click to expand...
Click to collapse
Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
Deeeno said:
Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
Click to expand...
Click to collapse
Yes and in those cases they're usually eager to share all the details required, unlike the OP.
When the proper details are supplied it's easy to help, nobody likes to mindread here.
CtrlAltDelIrl said:
When the proper details are supplied it's easy to help, nobody likes to mindread here.
Click to expand...
Click to collapse
Probably doesn't know exactly what they did to mess up.. so doesn't know how to explain it.
Merely asked for the stock application to try and fix it themselves is what I gathered.
But Whatever
Explanation.
Was using Android tweaker 2 and accidentally hit the "On Screen Navigation Keys" and then when I went to turn it off it wouldn't switch. It stayed on. Updated the T weaker app, hoping for a fix but the option disappeared and I was stuck with them. Searching the internet I found a option that allowed to disable the soft keys in the Build.prop. But when I save it and restarted the phone was stuck at the T-Mobile screen.
Also I never figured out how to do ABD it tried for a long time but it didn't work. Since I got it in October, I need to know who to send it to be repaired, since I have a warranty (But I don't really want to send it away so that's why I asked.) So, there's and explanation. I'd tell you what I edited if I could find the website.
ADB
Okay, I got ADB working. But if I unlock Bootloader, does that that void my warranty?
And basically I need a default Build.Prop. Thats the only file I edited.
Return the phone since you are under warranty, you won't be without a phone
If you are under warranty with tmobile, you should be able to get a replacement if you are on their JUMP insurance, even if it was accidental.
I would recommend first going to your tmobile store and asking them to send you a replacement(and to waive the restock fee). They will send you one by mail in a few days, then all you have to do is send the old phone back to them in the prepaid shipping package(instructions are included).
I would recommend doing this instead of unlocking your bootloader and waiting for a recovery and custom rom to come out. My belief is that unlocking your bootloader does NOT directly void your warranty, unless the company can prove that the unlocking directly bricked your phone(which it doesn't). A thread with the legality of unlocking your bootloader is found here: http://forum.xda-developers.com/showthread.php?t=2250113
Again, I recommend just bringing in your phone and saying your phone just refuses to boot anymore since an update or something of that like. You won't have to wait long. Also, the phone is $63 on ebay, if you are uneasy about going to tmobile to return it.
build.prop for Android 4.1.1
default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
Prism 2 said:
default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
Click to expand...
Click to collapse
Dont do this, you will brake it even more, every version has specific build prop.
Okay, but no.
Not on insurance....
They didn't offer it at Walmart, that I know of. The real reason I got it was that I was sick of my unlocked Pantech Link (An AT&T on T-Mobile...)
And plus, I'm just broke right now -_-
Are you sure you have Android 4.1.2? I have the latest stock T-mobile rom (just tried updating today) and I'm "up to date" with 4.1.1
How do you have 4.1.2?
That's strange. Can any other users confirm that their Prism Ii has 4.1.2?
Well...
Well.. I may be mistaken. But I can't check =/
Almost certain you have 4.1.1
Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.
I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.
To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.
If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.
Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed adb to, in order to use the adb command.
The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
streetdev22 said:
Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.
I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.
To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.
If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.
Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed asb to, in order to use the adb command.
The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
Click to expand...
Click to collapse
Pushed the Build.Prop, but still does the same thing. Lost the old one though, because I forgot to rename it.
Try Factory Reset once more
You are stuck in a bootloop? Try factory resetting once more.
If that does not work, you may be our first live install recovery image tester, and you'd just have to wait until a custom ROM was released.
Reseted... Still stuck.
Omg. They must make these phones just to make us upset when they break.
Wait until I get the unlock code from Huawei, also some other things to try
It should be any minute now, and I will see if there are other fixes. For now, unlock your bootloader according to the guide.
We will need access to recovery anyway, through recovery, we will try wiping cache/dalvik cache if available, and that may be the fix you need.
Also: I think you may need to change the permissions on the build.prop you pushed!
You would have to change the permissions to 644 according to this thread: http://forum.xda-developers.com/showthread.php?t=2152850&page=2
To do this, we would still need to use adb.
Commands in adb:
adb shell
remount rw
chmod 644 /system/build.prop
Also, are you sure that the file actually pushed successfully?