My phone is rooted (using the way to avoid the triangle, etc). I have tried installing TCWM and TWRP. I can install the custom recovery (Used Goomanager and dd of=/sdcard/tcwm.img if=dev/block/mmcblk0p18) and reboot and my custom recovery is there. From the recovery i will boot back into my phone then issue a command to reboot back into recovery and this time stock recovery is there. I did go through an OTA update and lost root, but have voodoo OTA rootkeeper to install it. I assume this may be related.
Also, if there was answered somewhere else, I apologize. I know the whole search first, and I tried, but unfortunately I have Hughesnet Satellite Internet that has had a download speed of 2.5KBps (half of dial up) for about two weeks and they don't know what the issue is. I've tried searching, but the webpage usually timesout. It took me a good long while to be able to get this up to post.
http://forum.xda-developers.com/showthread.php?t=1768826&page=2
Read post 84 it tells you to remove 2 lines through root explorer or another file manager.
Related
Was running along nicely on DC 3.2.3 last night. Decided oh gotta try the kernel to up the fps! It was freezing up within a couple minutes and causing a lot of fc's. No prob flash the regular DC kernel everything is fine. Decided it would be good to do Whitslack's start over method, probably should at some point, and then maybe give that custom kernel another shot and might work better. So waited until this morning to do it, looked quick and easy. Except when PCIMG ran on step 5 for recovery, got a 'pu fail'. Dl'd ROM Manager and tried to flash Clockwork..no go it said there was an error. Did get some suggestions in a few threads but nothing works. Tried the method to get recovery going via fastboot and terminal and not working. On fastboot I'm not seeing anything regarding devices(don't have the quoted instructions in front of me lost the thread). So basically I'm stuck and have no recovery so can't do anything. No fun having a phone like it's just out of the box. Also seems along the way I lost su privileges. Pretty new at all this so not sure what to do from here.
effluent said:
Was running along nicely on DC 3.2.3 last night. Decided oh gotta try the kernel to up the fps! It was freezing up within a couple minutes and causing a lot of fc's. No prob flash the regular DC kernel everything is fine. Decided it would be good to do Whitslack's start over method, probably should at some point, and then maybe give that custom kernel another shot and might work better. So waited until this morning to do it, looked quick and easy. Except when PCIMG ran on step 5 for recovery, got a 'pu fail'. Dl'd ROM Manager and tried to flash Clockwork..no go it said there was an error. Did get some suggestions in a few threads but nothing works. Tried the method to get recovery going via fastboot and terminal and not working. On fastboot I'm not seeing anything regarding devices(don't have the quoted instructions in front of me lost the thread). So basically I'm stuck and have no recovery so can't do anything. No fun having a phone like it's just out of the box. Also seems along the way I lost su privileges. Pretty new at all this so not sure what to do from here.
Click to expand...
Click to collapse
This is a common problem. Redo step 2 of Toast's method to get yourself a working recovery again. Then delete the recovery image from the PC36IMG.zip using winrar or another app that allows zip storage w/o compression. For winrar just open up the PC36IMG..zip and delete "recovery-RA...". Then flash that new PC36IMG.zip as well as the SU app.
Think someone else said since I'm updated to the new RUU via the new PCIMG I can no longer do toast's method?.. Just want to clarify before I go off doing something.
effluent said:
Think someone else said since I'm updated to the new RUU via the new PCIMG I can no longer do toast's method?.. Just want to clarify before I go off doing something.
Click to expand...
Click to collapse
Try this if you have access to fastboot.
Get the recovery.img from Toast's Part 2 Root Method. Put it in your Android SDK tools folder.
Go into fastboot (it is in the bootloader. Make sure you rename/remove PC36IMG.zip). Connect your phone to your computer by USB.
In Windows command prompt, navigate to your Android SDK tools folder. Check to make sure your phone is connected by typing:
Code:
fastboot devices
Then type in:
Code:
fastboot flash recovery recovery.img
I think some people have some odd corrupted byte or something in their recovery partition. Amon_RA mentions it. No clue why though.
No longer have su access so can't do anything.. can't adb..
You're going to need root and nand unlock to flash a recovery
Hi all.
I'll start by saying I have gotten in way over my head. I rooted my Evo with unrEVOked's one-click method, and then began to experience some problems with my 3g. Thinking I had somehow botched the rooting process, I tried to unroot using the two-step method I also found on xda (cannot post link.. further proof I am a noob ). More problems sprang up, one thing led to another, various fixes were tried (HUGE thanks to everyone in the IRC channel last night that tried to help my sorry ass..) but to no avail.
Here is where my phone is at now: booting using vol down+power shows me S-ON. Trying to flash mtd-eng.zip results in an error, so I am seemingly stuck with S-ON. Normally I would be happy about this (that's one step closer to unrooted, right?) but I notice I still have Superuser in my apps. My 3g is working again for whatever reason (no complaints here! maybe it was a Sprint-side problem in my area.. what timing!) but I'm confused as to whether my phone is rooted or not.
Ideally, I would like to go back to unrooted, since I have made it abundantly clear to myself that I am not yet prepared to embark in rooting. If anyone could guide me in the right direction, I would be very thankful.
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Jim M said:
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Click to expand...
Click to collapse
I did this, and my phone is now in RA-evo-v1.8.0 (it rebooted into recovery). Should I reboot the system now? I find it strange that it took me here in the first place.
The current PC36IMG that is flashed to the Evo is one with Amon Ra built into it.
The only RUU program that I am allowed to run (from the list that was given out in one of the unrooting evo threads) gives me the 170 error before anything happens.
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Jim M said:
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Click to expand...
Click to collapse
With a little digging and poking and reading, I found the proper RUU, ran it, and I believe I am now back to fully unrooted. Thank you very much for your help!
Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend
Throws a signature verification failed error.
Try again with the new method
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Why go to 2.3.6? It´s better than 2.3.5 customized?
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.
narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.
So I wanted to root this tablet, and I used a video online to help me do so.
I installed the USB drivers, got Odin 3, and loaded in CF_AutoRoot_Port_T700_BeansTown106.tar
It rooted my tablet and I was pretty happy about that. I then had update supersu, by getting the SU binaries.
So I came to this site and downloaded the recommended Supersu, and flashed it. It fixed that.
Well, then I wanted to get a custom ROM, so I flashed the Cyanogenmod 12, along with the component with it.
I found I didn't like it compared to my 5.0.2 Lolipop, and so I tried finding the stock ROM.
The gator download site everyone was showing refused to let me download anything, and just about all the ROMS seemed like they were from countries other than the U.S.
I searched for awhile, found nothing, then found a ROM called the Ironman Lolipop ROM, it was close enough to stock, so I flashed it.
Suddenly everything was normal, but then supersu needed binaries again, and after I flashed it again, it just stopped asking if it should grant permission, making the root useless.
Frustrated, I looked online again for ROMS, found a Canada one, decided to download, it would take two hours.
Well I'm not from Canada so I doubted it would work, and didn't want to wait two hours.
I decided to Flash back the Cyanogen.
Well unfortunately I went in and found out that I had deleted it earlier, whoops. And so my data wipe brought me back to Ironman ROM.
So, thinking that flashing to Iron Man screwed up my root I tried to re-root with Odin, the same way as the first.
It then had trouble booting, and when it did, it hung at the Samsung logo.
Now I've been stuck on this logo for about an hour, I can't turn it off. I'm assuming the only way to is to wait for it to run out of power.
I have been using TWRP this whole time.
I twice have backed up, and wiped data.
When I hit restore I saw no backups though, I'm not sure if they were for the ROM?
I don't know, I only have a year of experience.
Edit: I have an 8.1" T700 from Amazon.
pennylessz said:
So I wanted to root this tablet, and I used a video online to help me do so.
I installed the USB drivers, got Odin 3, and loaded in CF_AutoRoot_Port_T700_BeansTown106.tar
It rooted my tablet and I was pretty happy about that. I then had update supersu, by getting the SU binaries.
So I came to this site and downloaded the recommended Supersu, and flashed it. It fixed that.
Bla bla ......
Click to expand...
Click to collapse
Hi! To force reboot while in a soft brick, press and hold power+home button+ both volume buttons all at the same time.
Then when the screen goes black, quickly press the odin\download mode button combo or recovery comba if you wish.
Luckily, I have mirrored the latest firmware for the T700 to a faster hosting site. This is an UK firmware and is the latest one. It should flash fine as I have flashed different firmwares from different countries many times.
Download Firmware (fast download): https://www.androidfilehost.com/?fid=24052804347761130
Now, ironrom has problems with root sometimes. When I make roms I don't preroot them as they cause problems of binaries if you preroot them. Anyway feel free to flash the firmware with odin or load an custom ROM to your sd card and flash it.
Hope this helps!
DUHAsianSKILLZ said:
Hi! To force reboot while in a soft brick, press and hold power+home button+ both volume buttons all at the same time.
Then when the screen goes black, quickly press the odin\download mode button combo or recovery comba if you wish.
Luckily, I have mirrored the latest firmware for the T700 to a faster hosting site. This is an UK firmware and is the latest one. It should flash fine as I have flashed different firmwares from different countries many times.
Download Firmware (fast download):
Now, ironrom has problems with root sometimes. When I make roms I don't preroot them as they cause problems of binaries if you preroot them. Anyway feel free to flash the firmware with odin or load an custom ROM to your sd card and flash it.
Hope this helps!
Click to expand...
Click to collapse
Thank you for getting me out of the brick and back to stock.
However going into Supersu it says.
"There is no SU binary installed, and SuperSu cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root- consult the relevant forums for your device!"
My question is, can I properly re-root it the way I had been?
I'm assuming if it soft bricks again I can just reinstall a stock ROM again.
Also all these ROMS and backups take up a lot of space, how would I go about deleting those when I'm done?
pennylessz said:
Thank you for getting me out of the brick and back to stock.
However going into Supersu it says.
"There is no SU binary installed, and SuperSu cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root- consult the relevant forums for your device!"
My question is, can I properly re-root it the way I had been?
I'm assuming if it soft bricks again I can just reinstall a stock ROM again.
Also all these ROMS and backups take up a lot of space, how would I go about deleting those when I'm done?
Click to expand...
Click to collapse
In my files app, look for an folder called TWRP. Your backups are in there. To root simply install twrp and follow the twrp method to root. http://forum.xda-developers.com/showthread.php?p=59638836
You can delete your backups from within twrp. Just select restore, then the backup, then delete.
Long story short, I haven't done any of this stuff for a long time.
I did stuff here: .teamandroid.com/2016/03/08/update-tmobile-galaxy-note-2-t889-android-601-resurrection-remix-marshmallow-custom-rom/2/
I followed the instructions but I think where my hiccup happened was for whatever reason, CWM didn't install it's custom recovery system even though it said it had. So I'm stuck at 3e restore. However, in my stupidity and haste, I already wiped the data because I thought I was already in the CWM menu and didn't realize the 3e system would look so similar to the screen shots. Now I can't install the custom roms because they're not signatured, and I can't install a way to bypass the signature because that stuff is also not signatured. The only access I currently have to my phone is now through an ADB Sideload functionality using my PC.
Trying to at least get back to square one, or is there a way I can flash the CWM recovery system from this location?
Thanks for any help, not sure how to proceed from here (phone has no OS on it)
Nevermind, it restored the old OS
EDIT: For future reference and for those wondering what happened, the root didn't take correctly the first time so the CWM didn't flash properly. After verifying the root and updating SuperSU to kill knox, it was no problem. Flashed 100% perfect like it should have the first time. Dumb user error on my part.