Related
I am returning my nexus s back to bestbuy tomorrow. How do i go about unrooting it?
Thank you
(There isn't a Q and A section made up for the NS yet so i posted my question here)
"fastboot oem lock"
just relock the bootloader and restore to factory settings.... that's all they will check for...
jtn7040 said:
"fastboot oem lock"
just relock the bootloader and restore to factory settings.... that's all they will check for...
Click to expand...
Click to collapse
I did relock the bootloader but I still had root. I didn't factory restore yet but would that make a difference?
I just don't want to take it back up there and they find out its rooted.
Sent from my Evo using Swype and Tapatalk!
Can anyone please help with this? I'm trying to unroot this thing so that I can return it
I relocked the bootloader then did a factory reset and nothing changed..all my apps are still on the phone and the screens are still organized nor did the setup screen appear.
You need to use adb to go in the file system and delete all trace of superuser and busybox. That is the only things rooting does, places those files on your phone and changes file permissions. File permissions, they won't look for, but I've had best buy scroll through the app drawer on multiple occasions looking for superuser/rom manager.
I have attached a zip containing all the files needed for adb. Since they no longer package adb with the sdk. Just open command prompt and cd to the directory containing adb. Make sure your phone has Usb Debugging enabled, then connect your phone.
You might need to download usb drivers in order for windows to recognize the device, but probably not. Once your phone is connected, do the following.
Code:
adb devices
adb shell
su
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/bin/busybox
rm /system/bin/rootshell
reboot
You need to restore a pre-unlock backup. I'm guessing you didn't bother backing up the phone?
http://forum.xda-developers.com/showthread.php?t=875184
http://forum.xda-developers.com/showthread.php?p=9869067#post9869067
shrivelfig said:
You need to restore a pre-unlock backup. I'm guessing you didn't bother backing up the phone?
http://forum.xda-developers.com/showthread.php?t=875184
http://forum.xda-developers.com/showthread.php?p=9869067#post9869067
Click to expand...
Click to collapse
Just look at my previous post, he doesn't have to do anything else.
ryude said:
You need to use adb to go in the file system and delete all trace of superuser and busybox. That is the only things rooting does, places those files on your phone and changes file permissions. File permissions, they won't look for, but I've had best buy scroll through the app drawer on multiple occasions looking for superuser/rom manager.
Code:
su
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/bin/busybox
rm /system/bin/rootshell
reboot
Click to expand...
Click to collapse
Personally, I doubt Best Buy will even check for root. You really think they're that clever at the returns desk? Seriously.
I've never read reports of people saying Best Buy wouldn't take my phone back because it was rooted, but I never looked for them either.
How would they even check for it? You should always factory reset a phone before returning it, so you're not going to have any apps on there where they can open the app drawer and see you've got a root-required app like Root Explorer or SuperUser. They're definitely not going to attach the phone to a computer and poke around with adb.
On top of that, where on the phone's receipt does it say "no refunds on rooted devices"? It doesn't. Let the factory or the open box buyer worry about, however Best Buy disposes of the phone.
I suspect that all they'll do is check the phone for physical damage. They might turn it on to make sure it's still functional, so the fastboot oem lock is a must, just to be safe.
If I were going to return mine, and had your concern, I'd just follow @ryude's instructions; seems less likely to screw things up than messing around with fastbooting an image dump, but both are pretty safe procedures.
Please come back and let us all know exactly how the return process goes for you. What they checked, what they asked. Thanks!
shrivelfig said:
You need to restore a pre-unlock backup. I'm guessing you didn't bother backing up the phone?
http://forum.xda-developers.com/showthread.php?t=875184
http://forum.xda-developers.com/showthread.php?p=9869067#post9869067
Click to expand...
Click to collapse
How was he supposed to backup the phone before unlocking it? You need clockwork recovery to do a nandroid, don't you? ROM manager requires root to work, right?
This isn't a challenge, just curious how you backed up your phone in a manner that lets you restore a non-rooted image before unlocking and rooting.
Also, this makes me wonder how you get rid of CWM Recovery. Removing su/busybox/root doesn't do it, and fastboot oem lock doesn't. Hmmm, need to research/read up on that.
Depends if CWM is built into the kernel or not. If so, just flash stock kernel and you'd have stock recovery again.
If it's the CWM you get from Rom Manager, you can remove it by pressing "Flash to SPRecovery" at the bottom of Rom Manager.
distortedloop said:
Also, this makes me wonder how you get rid of CWM Recovery. Removing su/busybox/root doesn't do it, and fastboot oem lock doesn't. Hmmm, need to research/read up on that.
Click to expand...
Click to collapse
Reflash the stock recovery image. There's a thread for that file.
Fastboot flash recovery recovery.img
Sent from my Nexus S
ryude said:
Depends if CWM is built into the kernel or not. If so, just flash stock kernel and you'd have stock recovery again.
If it's the CWM you get from Rom Manager, you can remove it by pressing "Flash to SPRecovery" at the bottom of Rom Manager.
Click to expand...
Click to collapse
nxt said:
Reflash the stock recovery image. There's a thread for that file.
Fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Okay, thanks guys, you saved me a little searching. Not that I'm interested in doing this, but the original poster wants to remove all indications that he hacked his phone, so this is something he needs to consider.
I don't actually have a Nexus S, so the exact way to go about it I am not sure. I am just offering any help I can.
sorry...this won't be of any help...but if you can't figure out how to unroot the phone, you shouldn't be rooting it in the first place.
just saying....
good luck with the return, tho.
krumb said:
sorry...this won't be of any help...but if you can't figure out how to unroot the phone, you shouldn't be rooting it in the first place.
just saying....
good luck with the return, tho.
Click to expand...
Click to collapse
I agree, but saying that after the fact doesn't help anyone.
distortedloop said:
How was he supposed to backup the phone before unlocking it? You need clockwork recovery to do a nandroid, don't you? ROM manager requires root to work, right?
This isn't a challenge, just curious how you backed up your phone in a manner that lets you restore a non-rooted image before unlocking and rooting.
Also, this makes me wonder how you get rid of CWM Recovery. Removing su/busybox/root doesn't do it, and fastboot oem lock doesn't. Hmmm, need to research/read up on that.
Click to expand...
Click to collapse
Find a stock recovery image and
Code:
fastboot flash recovery stock-recovery.img
Voila.
distortedloop said:
How was he supposed to backup the phone before unlocking it? You need clockwork recovery to do a nandroid, don't you? ROM manager requires root to work, right?
This isn't a challenge, just curious how you backed up your phone in a manner that lets you restore a non-rooted image before unlocking and rooting.
Click to expand...
Click to collapse
I miss this step too, I was just too excited rooting.
Here's how to backup.
First you do the fastboot oem unlock, then you do the fastboot flash clockwork mod.
After that, BAM, boot into clockworkmod, and do a nandroid! That will backup your current stock Android. Save that nandroid backup.
Then you can proceed and actually finish the root.
Then when you want to restore, just boot into clockwork, restore that original nandroid and you have stock android, now just fastboot flash original recovery, then fastboot oem lock to lock the bootloader and that's it. do a wipe, and you're clean.
stock recovery.img isn't working I just tried. it's throwing an error. same for stock boot.img
one thing I love about galaxy s phones, we have the easiest recovery. Why did Google/Samsung change something that was so perfect?
jroid said:
stock recovery.img isn't working I just tried. it's throwing an error. same for stock boot.img
Click to expand...
Click to collapse
What error does it give when attempting to flash stock recovery or boot img? Was hoping to have a backup ready before I flashed my recovery.
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:
tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!
here's the screens of waht happens.
This his what happens when i try to go into recovery mode...
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!
Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.
Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.
Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2
EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?
If you haven't seen yet, from 9/6-9/7 causes bricks on some devices.
I can still get into TWRP recovery, but it's not recognizing my device in ADB, and the kernel is probably corrupted too.
How can I push a new kernel to my device and install an older rom?
When attempting to manually install the drivers, I get "The hash for the file is not present in the specified catalog file."
ThomasBags said:
If you haven't seen yet, from 9/6-9/7 causes bricks on some devices.
I can still get into TWRP recovery, but it's not recognizing my device in ADB, and the kernel is probably corrupted too.
How can I push a new kernel to my device and install an older rom?
When attempting to manually install the drivers, I get "The hash for the file is not present in the specified catalog file."
Click to expand...
Click to collapse
Try to get into recovery and do a adb sideload install in TWRP, here is the how to http://www.google.nl/url?sa=t&rct=j...=Vp_GX8CUK5C4PSCnBss8Yw&bvm=bv.51773540,d.Yms If that doesn`t work reflash the factory image in fastboot.bootloader mode.
I have the same issue... TWRP adb sideload is not working for me. Is there any way I can fastboot flash an older version of CM (i.e. 9/05)?
kino1122 said:
I have the same issue... TWRP adb sideload is not working for me. Is there any way I can fastboot flash an older version of CM (i.e. 9/05)?
Click to expand...
Click to collapse
You guys need to flash a factory image from here https://developers.google.com/android/nexus/images in fastboot.
kino1122 said:
I have the same issue... TWRP adb sideload is not working for me. Is there any way I can fastboot flash an older version of CM (i.e. 9/05)?
Click to expand...
Click to collapse
CM 9/05 isn't in a fastboot image format. Its a flashable zip so no.
Your best case is to do a ADB sideload as what gee2012 said. Always have a trusted backup or older flashable zip to work off of.
As a last resort, flash factory image but you'll have to start all over
Hey guys I found a solution.
For those unable to get ADB sideload to work, be sure to install the drivers here: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Following that you can do the TWRP sideload thing and then it'll just tell you it's starting it up. Go into your adb command and under adb devices you will see your device in sideload mode. With that, it's just a simple command of adb sideload ROM.zip and it'll install the .zip for you and you are good to go!
That happened to me too, you can try to use adb pull and install the 9/5 cm update that is not corrupted.
Guys there is a way to alert other people to not install those updates? Always is a pain in the ass to get your phone bricked
by the way, sorry for my bad english.
one day people will learn the difference between what a brick and a soft brick is. if you can get into the bootloader, the device is not bricked, it can be fixed. even if you can't get into the bootloader, sometimes it can be fixed. doing a little research/reading before rooting your device can save you lots of hassle later on, like in this situation. even just making a backup of your current set up in your recovery before flashing anything can save you hours of stress afterwards.
simms22 said:
one day people will learn the difference between what a brick and a soft brick is. if you can get into the bootloader, the device is not bricked, it can be fixed. even if you can't get into the bootloader, sometimes it can be fixed. doing a little research/reading before rooting your device can save you lots of hassle later on, like in this situation. even just making a backup of your current set up in your recovery before flashing anything can save you hours of stress afterwards.
Click to expand...
Click to collapse
I just a matter of name bro, but, anyways, you know what have gove wrong with these nightlies?
lwkkazz said:
I just a matter of name bro, but, anyways, you know what have gove wrong with these nightlies?
Click to expand...
Click to collapse
nightlies by definition are not stable, nor are meant to be. tbey are just tbe most recent upload with whatever code was added. new code will not play nice many times, especially with other stuff included. that why they build the nightlies, to test out how the newest code will behave. whats wrong with this nightly i dont know, i don't run cm. normally, after a bad nightly, flashing tge ladt nightly tgat was good would fix the non booting problem, or restoring a nandroid backup. anyways, its a good idea to keep the last good rom(or kernel) in your storage at all times, just in case of situation like this.
simms22 said:
nightlies by definition are not stable, nor are meant to be. tbey are just tbe most recent upload with whatever code was added. new code will not play nice many times, especially with other stuff included. that why they build the nightlies, to test out how the newest code will behave. whats wrong with this nightly i dont know, i don't run cm. normally, after a bad nightly, flashing tge ladt nightly tgat was good would fix the non booting problem, or restoring a nandroid backup. anyways, its a good idea to keep the last good rom(or kernel) in your storage at all times, just in case of situation like this.
Click to expand...
Click to collapse
I do that too, you know if that a way to sinalize that the last two nightlies are not bootable?
lwkkazz said:
I do that too, you know if that a way to sinalize that the last two nightlies are not bootable?
Click to expand...
Click to collapse
if they arent bootable, then whomever compiles them already probably knows. the thing to do will be to flash the last good nightly and wait for the next nightly.
kino1122 said:
Hey guys I found a solution.
For those unable to get ADB sideload to work, be sure to install the drivers here: plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Following that you can do the TWRP sideload thing and then it'll just tell you it's starting it up. Go into your adb command and under adb devices you will see your device in sideload mode. With that, it's just a simple command of adb sideload ROM.zip and it'll install the .zip for you and you are good to go!
Click to expand...
Click to collapse
Thank you!
It worked!
An update for whoever is looking for an update: I have tried 20130918 build and it's working fine.
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a backup of Recovery
Sorry for my bad English.
thanks
exebuera said:
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a back of Recovery
Sorry for my bad English.
thanks
Click to expand...
Click to collapse
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
dreamtheater17 said:
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
Click to expand...
Click to collapse
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
jason2678 said:
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
Click to expand...
Click to collapse
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Sorry I've never encountered the adb closed problem myself, but I have heard about it before. Some people have reported the following series of commands fixes it:
Code:
adb usb
adb devices
adb kill-server
adb start-server
The first two commands normally don't really do anything and its pretty obvious what the second two do, but some people have reported success doing this.
Some people have reported the closed error was fixed by updating their adb binary. If you're using the android-sdk update platform-tools, or if you're using a standalone adb consider looking for an update for it.
Good luck. That procedure to get things back to normal following using the kdz to restore sounds messy.
dreamtheater17 said:
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Click to expand...
Click to collapse
hi, i have the same problem than u, i wanna know if i can flash the US CELLULAR kdz for solve the partition issue? because i already flash the kdz test from ATT
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
mxpxboi said:
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
Click to expand...
Click to collapse
If you applied an OTA with a custom recovery installed it might soft brick your tablet, but I don't see why that would stop it from detecting and downloading the update. It is always safest to flash stock recovery, fully unroot, and undo any modifications you've made to /system before taking an OTA, but some devices are more picky than others. With what you're describing I'm afraid that even if you do unroot and flash stock recovery your tablet still won't find the OTA.
Do you have a nandroid backup of an unmodified stock ROM you could restore?
And just so you know that lollipop bootloader is not vulnerable to the bump exploit, so no custom recovery or ROMs if you get it to apply.
Whenever I type "reboot recovery" in terminal emulator, it boots straight to factory reset. I have tried this multiple times with both dd and flashify. Do you know what causes this? I'm downloading the OTA right now, I hope it doesn't wipe then too...
please help
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Devil911 said:
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Click to expand...
Click to collapse
Download the timmytim stock ROM, and extract the boot.img from it. There are probably quicker ways, but having the stock ROM on hand is a good idea.
Sent from my Amazon Fire using XDA Labs
Thank you...
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Devil911 said:
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Click to expand...
Click to collapse
The stock rooted is by timmytim ?
I forgot about deodexed, actually.
Glad you fixed boot, shame your tablet broke ?
Sent from my Amazon Fire using XDA Labs
There seems to be a lot of concerns about being able to flash roms in the future without using recovery and tripping knox. Why do we really need a recovery to do this? Sure it's easier. The recovery simply extracts and archive and runs an updater-script to add/delete/update modded files and set proper permissions etc. These are basically shell commands. Why can ADB be used on a rooted device to accomplish the same?
I have written a few mods and deodexed my fair share of roms. This can all be done through ADB by extracting the files.. deodexing/modding them and putting them back. and change a few permissions.
This works great for quick edits but to do a complete rom this way would require quite an installer script.
I can see a rom package being uploaded to the device and an installer script executed via ADB to put everything in it's place.
And do we know exactly what trips knox? (other than trying to write an image file directly to the recovery partition?) Can dd be used to write a prepared image to the system partition without blowing things up?
I'm not trying to make all this sound like it's easy...it's not! just trying to change the "We can't do anything without a recovery" mindset.
I understand a program called fireflash is in development. I'm not sure of it's intended purpose other than a Mobile Odin replacement (which it is). I hope it evolves into a complete package flashing application and we can put all this fear of tripping knox and losing potential features to rest.
I encourage responses and expect these ideas to be blown full of holes. I'm used to it.
OK, but how to nandroid/restore?
Because you need a pc otherwise to do everything. Recovery can do it all on the phone.
You have to be outside the Android OS to flash anything of significance, recovery makes the most sense since that's what it's designed to do.
gpvecchi said:
OK, but how to nandroid/restore?
Click to expand...
Click to collapse
I look for the same answer. Nandroid online works fine. To restore it , we need something like dd command.
doesn't using Flashfire eliminate the need for a custom recovery? it can flash zip files and do backups.
Yup, if phone boots...
This link might help you to understand what, and why, Knox gets tripped;
http://www.samsung.com/uk/business/solutions-services/mobile-solutions/security/samsung-knox