Develop Bugs

[Q] Strange root problem, please help

Okay it's been a few months since this has happened so I'll try to remember as best as I can; I had rooted my Nexus using WugFresh's kit, everything went fine. It was rooted for about 6 months and eventually got stuck in a boot loop (no clue how this happened, I hadn't installed any kernals, roms, even apps in months). I tried like 4 or 5 different methods to fix the issue; I finally was able to get the phone working again using ODIN mode, it completely restored it to stock (as far as I'm aware).
So I tried to re-root the phone; no luck, using ANY method I've been able to find. The main problem is I can't seem to get into TWRP, every time I try to it simply gives me the dead android with the red exclamation point. I'm not an advanced user by any means, but I'm not totally clueless and I can follow directions. If anyone has any advice for me on this I'd GREATLY appreciate it, I have an excellent 4G signal where I live and the only other internet option is AT&T basic DSL so I'd really like to be able to use my wifi hotspot again. Thanks in advance for your time, I appreciate anyone who takes the time to try to help.

1) android on its back is stock recovery.
2) follow this: http://forum.xda-developers.com/showthread.php?t=1529058
it works 100% of the time if you read and take your time.

it sounds like you have root but cant flash a recovery, let me know if im wrong but if this is the case I would just download goo manager from the market and go into settings and flash a custom recovery and that should fix your recovery problem but sometimes you have to download the recovery twice ive noticed that in the past, let me know if this works for you or you could go through the longer process above but your fix may be very simple

Thanks for the info, I will try this either tonight or tomorrow and get back to you; I certainly hope it works!

jaymazz13 said:
it sounds like you have root but cant flash a recovery, let me know if im wrong but if this is the case I would just download goo manager from the market and go into settings and flash a custom recovery and that should fix your recovery problem but sometimes you have to download the recovery twice ive noticed that in the past, let me know if this works for you or you could go through the longer process above but your fix may be very simple
Click to expand...
Click to collapse
I thought that too, but I tried installing super user and a couple of other root-only apps and it said that my device wasn't rooted. =P

Zepius said:
1) android on its back is stock recovery.
2) follow this: http://forum.xda-developers.com/showthread.php?t=1529058
it works 100% of the time if you read and take your time.
Click to expand...
Click to collapse
This is driving me insane. I'm trying this method; I followed the directions step by step, but my phone is showing that it is unlocked already (when I entered the fastboot oem unlock command in CP it returned FAILED: Invalid Command, but it is showing as unlocked in bootloader.
Now for the weird part; I rebooted to bootloader and tried fastboot flash recovery recovery-clockwork-6.0.2.3-toroplus.img and it returned immediately FAILED: Invalid Argument. I decided to start the process over, and now I can't reboot from CP, it's saying error: device not found.
I really want to just smash this f*%&ing thing into several hundred thousand pieces right about now, so I'm going to take a break for the moment. Are there different types of bootloaders, or is it possible the my bootloader is just corrupted or something?

There are different bootloaders, but the fastboot commands should work just the same. You're on Windows i'm assuming? You could also look at efrant's guide, http://forum.xda-developers.com/showthread.php?t=1626895, as well as his 101 in the general section stickies. It does not make sense that the device would become not found, and I would try reflashing the bootloader. Don't smash the phone!

Have you tried this method?
http://forum.xda-developers.com/showthread.php?t=1400871

lockehart12 said:
Now for the weird part; I rebooted to bootloader and tried fastboot flash recovery recovery-clockwork-6.0.2.3-toroplus.img and it returned immediately FAILED: Invalid Argument. I decided to start the process over, and now I can't reboot from CP, it's saying error: device not found.
Click to expand...
Click to collapse
your drivers are not installed correctly.

unable to reroot Sprint Galaxy S3 with a failed root.

I have an S3 from sprint. it has a faild root at this point (TrevE). My guess is that an update locked up my root.. I am tring to flash back to stock so I can reroot but SU blocks everything i do. I have tried to reroot but CW wont come up, just android recovery. Everything I have found on removeing SU requires you to be rooted first.... I even tried Root Browser and Uninstall master but SU just denies permission.... All i want to do is start from scratch. Please help...

christivson said:
I have an S3 from sprint. it has a faild root at this point (TrevE). My guess is that an update locked up my root.. I am tring to flash back to stock so I can reroot but SU blocks everything i do. I have tried to reroot but CW wont come up, just android recovery. Everything I have found on removeing SU requires you to be rooted first.... I even tried Root Browser and Uninstall master but SU just denies permission.... All i want to do is start from scratch. Please help...
Click to expand...
Click to collapse
Do you are able to get to download mode?

kevinrus123 said:
Do you are able to get to download mode?
Click to expand...
Click to collapse
The problem was that i watched too many videos and went through too many how to guids. I kept working at it and finaly got it to work. i finaly found a video that told me not to let it reboot after odin was done. I turned "off" the auto reboot on Odin, which is the exact oposite of what every other video said to do, and manualy shut it down and put it straight into Recovery Mode. All of the videos I had seen said to leave Auto Reboot on so i had been doing that. after it would reboot I would shut it back down and try to go to recvery mode but got the android recvery insted of CWRecovery. I guess the reboot after Odin was enough to through it all out of wac. Manually shutting it down after Odin and then going into recovery right away got it. Unfortunatly thats the problem when there are 5,000 answers to the same question. Thanks

christivson said:
The problem was that i watched too many videos and went through too many how to guids. I kept working at it and finaly got it to work. i finaly found a video that told me not to let it reboot after odin was done. I turned "off" the auto reboot on Odin, which is the exact oposite of what every other video said to do, and manualy shut it down and put it straight into Recovery Mode. All of the videos I had seen said to leave Auto Reboot on so i had been doing that. after it would reboot I would shut it back down and try to go to recvery mode but got the android recvery insted of CWRecovery. I guess the reboot after Odin was enough to through it all out of wac. Manually shutting it down after Odin and then going into recovery right away got it. Unfortunatly thats the problem when there are 5,000 answers to the same question. Thanks
Click to expand...
Click to collapse
You may have watched some videos from before the last two official stock updates that were released several months ago - I don't recall which one, but one of those updates added a function that reinstalls the stock recovery every time the phone boots up. And since the custom recovery is the only way to flash a custom rom that doesn't revert your recovery to stock, you have to do that while the custom recovery is still installed, which means before the stock rom ever gets a chance to boot
In other words, nothing was thrown out of whack - it was all operating the way it was designed to, by developers who don't want us to be able to mess with their programming - we sure showed them, though, lol
Sent from my SPH-L710 using xda app-developers app

[Q] Attempted Factory Reset now locked out!

So this may be a stupid question (but it's my first post so go figure) but I've read a few forum posts and I still can't seem to find a resolution.
I'm using a Rogers SGH i3170 with Android 4.3. I used the cf auto root file to root my phone with ODIN and otherwise did not modify the original software I manually installed the SuperSu apk to get around KNOX.
I was going to sell the phone so I went into the backup & reset option to clear out all my information. the phone seemed to clear itself just fine but now it won't go back the 'samsung' boot screen.
It'll show the device name, do the boot animation and otherwise just sits there.
The battery is at 80-90%
My main issue is that I would flash the stock ROM but it also won't go into recovery mode. It just reboots without actually going there.
Did I just brick my phone?
**I'm fairly new to rooting, I've rooted my S4 and Nexus 5 and was able to reset them without issue through the menus without using CWM or TWRP. I'm familiar enough with the processes just need some direction I guess!

Try this: Vol down& power& home. That'll put you into download mode so you can use Odin to return to stock...
You can also try THIS
If that doesn't help then goHERE for more INFO:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk

LENT0N said:
So this may be a stupid question (but it's my first post so go figure) but I've read a few forum posts and I still can't seem to find a resolution.
I'm using a Rogers SGH i3170 with Android 4.3. I used the cf auto root file to root my phone with ODIN and otherwise did not modify the original software I manually installed the SuperSu apk to get around KNOX.
I was going to sell the phone so I went into the backup & reset option to clear out all my information. the phone seemed to clear itself just fine but now it won't go back the 'samsung' boot screen.
It'll show the device name, do the boot animation and otherwise just sits there.
The battery is at 80-90%
My main issue is that I would flash the stock ROM but it also won't go into recovery mode. It just reboots without actually going there.
Did I just brick my phone?
**I'm fairly new to rooting, I've rooted my S4 and Nexus 5 and was able to reset them without issue through the menus without using CWM or TWRP. I'm familiar enough with the processes just need some direction I guess!
Click to expand...
Click to collapse
My guess would be depending on what options you chose for wiping your data you probably wiped the root folder.
in which case there is nothing to boot to.
I have done that before in error and its a pain.
If you still have a recovery great you just need to flash a ROM.
Otherwise you might have to ODIN a recovery back on and then flash. Which is what I had to do.

Rooting 910V - Non Dev Model

Instead of flooding the bootloader thread, I humbly ask for anyone's help in getting my N4 rooted so that I can unlock the bootloader.
1. I am able to use Kingroot to obtain temp root
2A. I open Root Checker and N4 reboots
OR
2B. Root checker OK then I get to ADB and enter a push command, the N4 reboots
This is where I am stuck.

Bootloader
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.

coledeb said:
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=66371097&postcount=237
I had the same bootloop problem and following those directions fixed it for me. I had to use Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip as my kernel. Later versions didn't work (wrong phone version?).

coledeb said:
I have my boot loader unlocked and twrp flashed successfully using king root. I used version 4.8.5 to do it. Basically it's kind of a hit or miss of how long the temp root stays until the phone either freezes or reboots (in my experience). I have attempted this process multiple times and it doesn't seem to hurt the device if the device freezes while I am executing adb commands.
The process that I did was hook up the Note 4 to my pc, then verify in adb that the phone was showing up. I then followed the adb command "adb push samsung_unlock_n4-2 /data/local/tmp/" as it doesn't require root to copy the file to the phone. Then I used king root to temp root the phone and followed the rest of the steps immediately. The boot loader is unlocked and I was able to flash twrp with Odin afterwards without having any issues. It seems time is the key because you don't know how long king root will let you keep the root.
Where I'm stuck is obtaining perm root after unlocking the boot loader and flashing twrp. I thought I would be able to just grab the latest version of SuperSU and flash through twrp but every time I tried this it caused a boot loop after the Verizon logo. (I went through a couple of flashing the stock 5.1.1 image from Samsung and retrying). Now I've made a backup in twrp so if anything goes wrong I can return to the unlocked/custom recovery state that I have gotten it to. I just am not sure how to obtain the perm root after the unlock and custom recovery.
On the topic of king root again, there were a couple of instances where it froze either before trying the adb commands or during (even failing to root sometimes). I just restarted the phone, or pulled the battery when that happened and tried the process again. It always worked eventually.
Click to expand...
Click to collapse
Why don't you guys flash a ROM that is rooted instead of flashing SU?
Edit:
But if whatever you guys are doing works eventually, keep doing that.

thanks for everyone's help - I finally got DEV mode to stick!

No Command after Recovery Flash

Hey all. Its been almost 3 years since Ive rooted a phone, and Ive only used odin once. But I needed to root my Samsung Tab 3 to ue the hotspot feature at my wedding. I found this set of instructions after lots of googling, but I may have missed something.
http://techbeasts.com/install-cwmtwrp-recovery-and-root-sprint-galaxy-tab-3-sm-t217s-how-to/
I have the s217s from sprint. I flashed the recovery as it asked, but after it rebooted, I only got to use recovery once, tried to flash SU, and it didnt work. Rebooted, now I get No Command, with # MANUAL MODE # in the lower left corner, and can only boot out of recovery. It seems there is no real recovery. Odin wont see it unless its booted into android.
SO I guess my issues is two fold: How do I get TWRP or CW recovery installed on this thing now, and what is the best way to root this tablet at this point?

Bump. I know it's an older tablet but I'm just not finding anything for this issues specifically for this tablet. I can't get it into download mode to reflash twrp
Sent from my SM-N920P using Tapatalk