Related
[ update ]
It's not bcuz "can't access terminal as root"
It's bcuz every time when Updated the device via OTA, the third part recovery was replaced by the Official recovery, and the device was unrooted again. So EVERY TIME finished OTA Update, the first thing to do is to root it again.
my friend told me that i have to re-root my ics-ed device. i am giving a try
Sent from my Nexus S using XDA App
feinux said:
see the screenshot here
http://picplz.com/user/shellehs/pic/kx7b3/
and here shows my ns is rooted
http://picplz.com/user/shellehs/pic/kx7fk/
but root explorer can grant root permission as usual
http://picplz.com/user/shellehs/pic/kx7hw/
thanx for any help!
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
try android terminal emulator from the market, works well here https://market.android.com/details?id=jackpal.androidterm&hl=en
and/or update your superuser app.
---------- Post added at 09:49 PM ---------- Previous post was at 09:48 PM ----------
feinux said:
my friend told me that i have to re-root my ics-ed device. i am giving a try
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
do not listen to your friend, do not "reroot" your android. that will just be a waste of time.
---------- Post added at 09:53 PM ---------- Previous post was at 09:49 PM ----------
feinux said:
my friend told me that i have to re-root my ics-ed device. i am giving a try
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
here, flash this in your recovery http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
its the updated superuser app
thax. i just
fastboot flash recovery Super*.zip
but it does not work.
do i wrong something?
Sent from my Nexus S using XDA App
feinux said:
thax. i just
fastboot flash recovery Super*.zip
but it does not work.
do i wrong something?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
put it in your sd storage, boot into recovery, find the file and flash it, boot up. you do have a custom recovery installed, like clockworkmod or twrp recovery?
Tried installing/updating busybox?
i forget... looks there is no custom recovery since i ota upgrade to ics. get to install one.
Sent from my Nexus S using XDA App
Thanks very much. all done.
and one more [Q]
I used flashboot to flash the Super*.zip into recovery, just like I mentioned my reply.
Can I delete it? or just when I flash twpr recovery img, than the recovery partition all be override?
feinux said:
Thanks very much. all done.
and one more [Q]
I used flashboot to flash the Super*.zip into recovery, just like I mentioned my reply.
Can I delete it? or just when I flash twpr recovery img, than the recovery partition all be override?
Click to expand...
Click to collapse
id keep it in your storage just in case you need it again. most the recent roms have the superuser updated already, so you probably wont need it again if youre flashing roms. but you never know.
thanks.
I rooted my phone successfully and then I installed TWRP and it rebooted the phone and I got this message which now I have to use kies to go back to stock.
"System software not authorized by ATT has been found on your phone"
Sounds like you didn't install the Loki twrp
Sent from my A500 using Tapatalk HD
StolenVW said:
Sounds like you didn't install the Loki twrp
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
I downloaded goo manager and installed it from there. Could you please link me to the right one?
I haven't used goo manager but I have herd they have a Loki version of twrp in goo manager you have to make sure its for the att s4
Sent from my A500 using Tapatalk HD
If I use this method, will it work?
http://forum.xda-developers.com/showthread.php?t=2297900
Capt said:
I rooted my phone successfully and then I installed TWRP and it rebooted the phone and I got this message which now I have to use kies to go back to stock.
"System software not authorized by ATT has been found on your phone"
Click to expand...
Click to collapse
You are not flashing the correct kernel, I have seen that error, many times. Just boot to recovery, and flash a different kernel.
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
Capt said:
If I use this method, will it work?
http://forum.xda-developers.com/showthread.php?t=2297900
Click to expand...
Click to collapse
yes, but what ever rom you are flashing, most likely will included their kernel, flash the att compatible kernels, it will work.
Use Tibu to freeze "knox".
Twrp does not auto loki. you have to either flash a loki kernel or flash loki doki after flashing the rom and then reboot.
Loki doki can be found here: http://tau.shadowchild.nl/attn1/?p=483
He did not try to install a rom.....he got that after installing twrp
Sent from my A500 using Tapatalk HD
I keep having the same error. I used the latest "Lokifyed 3way Tool" as well as AdamOutler's "Casual Root and Recovery". Everything works fine until I try to install a ROM (tried various ROMs, Infamous/Revolt). After a successful ROM install, I reboot and get this error. I have the latest Samsung USB drivers installed, flashed back to stock, did a factory reset, cleared cache/dalvik, rerooted, frozen anything with "knox" in it, reinstalled both recoveries (on separate tries of course), and tried installing the loki-doki patch and lokied kernals before and after the ROM successfully installs, to which they both fail and abort install. I feel I have tried everything but any suggestions would be appreciated.
Methods I used to root and install lokied recovery:
bhp090808's "[TOOL](OneClick)Updated 6-1-13 ATT ROOT RECOVERY ODIN LOKIFYED"
http://forum.xda-developers.com/showthread.php?t=2297033
^used the CWM OUDHS 1.0.3.5 recovery^
AdamOutler's "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13"
http://forum.xda-developers.com/showthread.php?t=2297900
Kernal and loki patch I used (both fail when trying to install):
[KERNEL][ATT][AOSP/TW][6/3/2013] KT-SGS4 - MDM - LOKI'd - KTweaker
http://forum.xda-developers.com/showthread.php?t=2292341
http://tau.shadowchild.nl/attn1/?p=483
adr1aN said:
I keep having the same error. I used the latest "Lokifyed 3way Tool" as well as AdamOutler's "Casual Root and Recovery". Everything works fine until I try to install a ROM (tried various ROMs, Infamous/Revolt). After a successful ROM install, I reboot and get this error. I have the latest Samsung USB drivers installed, flashed back to stock, did a factory reset, cleared cache/dalvik, rerooted, frozen anything with "knox" in it, reinstalled both recoveries (on separate tries of course), and tried installing the loki-doki patch and lokied kernals before and after the ROM successfully installs, to which they both fail and abort install. I feel I have tried everything but any suggestions would be appreciated.
Methods I used to root and install lokied recovery:
bhp090808's "[TOOL](OneClick)Updated 6-1-13 ATT ROOT RECOVERY ODIN LOKIFYED"
http://forum.xda-developers.com/showthread.php?t=2297033
^used the CWM OUDHS 1.0.3.5 recovery^
AdamOutler's "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13"
http://forum.xda-developers.com/showthread.php?t=2297900
Kernal and loki patch I used (both fail when trying to install):
[KERNEL][ATT][AOSP/TW][6/3/2013] KT-SGS4 - MDM - LOKI'd - KTweaker
http://forum.xda-developers.com/showthread.php?t=2292341
http://tau.shadowchild.nl/attn1/?p=483
Click to expand...
Click to collapse
Use the recovery I am linking to flash whatever it is. It will auto-loki for you. Loki is required to bypass the bootloader authentication.
http://forum.xda-developers.com/showthread.php?t=2291956
CamFlawless said:
Use the recovery I am linking to flash whatever it is. It will auto-loki for you. Loki is required to bypass the bootloader authentication.
http://forum.xda-developers.com/showthread.php?t=2291956
Click to expand...
Click to collapse
This recovery is included in the 3way tool I used and it is the recovery I choose to use when going through the root/recovery process.
I have the same error "System software not authorized by at&t has been found on your phone" but when I press vol up and power it says rebooting to recovery but just boots back to that error. Anyway to fix this? TIA
irus said:
I have the same error "System software not authorized by at&t has been found on your phone" but when I press vol up and power it says rebooting to recovery but just boots back to that error. Anyway to fix this? TIA
Click to expand...
Click to collapse
What did you flash and how did you flash it? And do you have the i337 or what?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
What did you flash and how did you flash it? And do you have the i337 or what?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
sorry for not giving more detail. I have the sgh-i337 at&t version. Like I said I pressed the volume up with power and did not release until it said rebooting into recovery in the upper left of the display.
irus said:
sorry for not giving more detail. I have the sgh-i337 at&t version. Like I said I pressed the volume up with power and did not release until it said rebooting into recovery in the upper left of the display.
Click to expand...
Click to collapse
Are you on stock, or did you flash a rom? And of so how did you flash it
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 05:38 PM ---------- Previous post was at 05:36 PM ----------
Have you read this whole thread? Because the other guy didn't flash the correct kernel. You probably didn't either
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I was on stock. I rooted, then installed cwm recovery the installed v1.3 of Google play stock. I did not install the loki patch because it says its auto Loki patch. So not sure what I did wrong :-\ thanks for helping with this
jd1639 said:
Are you on stock, or did you flash a rom? And of so how did you flash it
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 05:38 PM ---------- Previous post was at 05:36 PM ----------
Have you read this whole thread? Because the other guy didn't flash the correct kernel. You probably didn't either
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
irus said:
I was on stock. I rooted, then installed cwm recovery the installed v1.3 of Google play stock. I did not install the loki patch because it says its auto Loki patch. So not sure what I did wrong :-\ thanks for helping with this
Click to expand...
Click to collapse
You didn't read the whole op for v1.3 because it says to Loki patch. Do that and you'll be fine.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
My problem is I can't get back into recovery. I press volume up and power and it says rebooting into recovery but the I just get the same error. Is there something else I need to do?
jd1639 said:
You didn't read the whole op for v1.3 because it says to Loki patch. Do that and you'll be fine.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
irus said:
My problem is I can't get back into recovery. I press volume up and power and it says rebooting into recovery but the I just get the same error. Is there something else I need to do?
Click to expand...
Click to collapse
You need to go into download mode and get a stock rom that is rooted through odin. I can't really explain through text how to use odin, so just use google and YouTube to your advantage.
sent from that HUGE Phone
I did research for this for a couple of hours but didn't find anything too helpful besides flashing back to stock. I also saw I could install the TWRP img file by the command line but that makes me a little nervous for the brick warnings posted.
I have the Goldeneye rom on my phone and I had TWRP 2.5.0.2 and everything was working great. I also updated the Modem to the MF3 one. I flashed TWRP up to 2.6 and loki-doki and everything seemed to go OK until I rebooted the phone.
I rebooted the phone and got the error of System software not authorized by ATT has been found on your phone and the SECURE FAIL: KERNEL message at the top.
I am now unable to boot into recovery with the buttons or using the reboot menu from the Goldeneye rom. Every time I try to reboot it goes to the error message above.
Now I am able to have the phone boot up fully if I go into download mode and then press the volume down key to cancel/restart the phone and then it will boot up with out issue. Any time I reboot though with out going into download mode I get the secure kernel error.
Is there a way to recover the device without going through ODIN and reflashing it back to stock? Also, my baseband shows MF3 now since I flashed the modem, is that going to cause any issues?
Any advice would be appreciated. Thanks
Can you try reinstalling the twrp recovery through goomanager when you get it to boot.. Then retrying to get into recovery?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
bump
Sent from my SAMSUNG-SGH-I337 using xda premium
rcklss1 said:
Can you try reinstalling the twrp recovery through goomanager when you get it to boot.. Then retrying to get into recovery?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I go to install OpenRecoveyScript in goomanager and it tells me that no recoveries were found for my device
lyrad12 said:
bump
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Why are you bumping this--
---------- Post added at 11:52 PM ---------- Previous post was at 11:47 PM ----------
dibe said:
I go to install OpenRecoveyScript in goomanager and it tells me that no recoveries were found for my device
Click to expand...
Click to collapse
Why not Odin
I haven't looked for awhile, but if you example of command to put recovery on phone by adb, try it. If you have the command line from a dev thread then just copy/paste the line. No chance of typing error. Still double check all. And any bu's you can do prior, do them and put copy on pc. Know you can't nandroid, but maybe MyBackUp Pro.
I was hoping there was something I could do to retain the setup on the phone how it is.
I'll push the twrp file using the command line and if that doesn't work I will flash with odin
dibe said:
I was hoping there was something I could do to retain the setup on the phone how it is.
I'll push the twrp file using the command line and if that doesn't work I will flash with odin
Click to expand...
Click to collapse
Good Luck--:good:
dibe said:
I was hoping there was something I could do to retain the setup on the phone how it is.
I'll push the twrp file using the command line and if that doesn't work I will flash with odin
Click to expand...
Click to collapse
Lol, odin is much easier.
Sent from my HTC One X using xda premium
rugmankc said:
Good Luck--:good:
Click to expand...
Click to collapse
Thanks.
I installed the TWRP 2.5.0.2 img file using Android Terminal Emulator and the command line. Everything is working fine now with the phone and I didn't have to reflash or lose any data.
Thanks for everyone's help.
convict_moody said:
Lol, odin is much easier.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Odin is last resort for me since you lose everything--
---------- Post added at 02:47 AM ---------- Previous post was at 02:46 AM ----------
dibe said:
Thanks.
I installed the TWRP 2.5.0.2 img file using Android Terminal Emulator and the command line. Everything is working fine now with the phone and I didn't have to reflash or lose any data.
Thanks for everyone's help.
Click to expand...
Click to collapse
Glad you got it--:good:
rugmankc said:
Odin is last resort for me since you lose everything--
I would have to fully agree with you there. I am very glad installing the img worked.
Click to expand...
Click to collapse
I flashed a kit kat ROM earlier to play around on, and when I was rebooting I accidentally hit the wrong button in cwm to not reflash recovery. Now I don't have recovery anymore, and I don't have access to a computer so I can flash the PA version of Kit Kat. ROM manager will not flash recovery for me. Is there anything I can do to get recovery without a computer?
Sent from my AOSP on Mako using xda app-developers app
EggosEvo said:
I flashed a kit kat ROM earlier to play around on, and when I was rebooting I accidentally hit the wrong button in cwm to not reflash recovery. Now I don't have recovery anymore, and I don't have access to a computer so I can flash the PA version of Kit Kat. ROM manager will not flash recovery for me. Is there anything I can do to get recovery without a computer?
Sent from my AOSP on Mako using xda app-developers app
Click to expand...
Click to collapse
you can flash the twrp recovery via the goo manager app.
Do you think flashing recovery through adb would work getting recovery?
Sent from my AOSP on Mako using xda app-developers app
well, if you have access to a computer use fastboot. you can probably flash via adb as well.
I wont have access to a computer for a few hours but I'm thinking that's my best bet, as I don't have root
Sent from my AOSP on Mako using xda app-developers app
EggosEvo said:
I wont have access to a computer for a few hours but I'm thinking that's my best bet, as I don't have root
Sent from my AOSP on Mako using xda app-developers app
Click to expand...
Click to collapse
you don't need root to fastboot either, you just need to boot into the bootloader. of course, and have the drivers installed in the computer. same for adb.
simms22 said:
you don't need root to fastboot either, you just need to boot into the bootloader. of course, and have the drivers installed in the computer. same for adb.
Click to expand...
Click to collapse
From the looks of it, my computer wont recognize fastboot commands in either OSX or Windows. I've installed the necessary files on both OS's and still nothing.
Well I was able to "flash" it, but it didn't actually flash. Still the dead android with the red triangle.
EDIT: I can get to the menu by pressing power+volume up. is there anything I can do there to help?
Did you try flashing a recovery from Recovery Tools aplication?
You will find it in Play store.
Sent from my NookColor using Tapatalk 4
I was in the same situation you were.
Do these things:
1. Install the drivers for ur N4.i used Wug's toolkit ONLY TO INSTALL THE DRIVERS.
2. Next set up your fastboot.
3. Download the the latest CWM recovery (i think it was 6.0.4.3 touch).
4. "fastboot flash recovery recovery.img"
5. Voila! U got your recovery back.
6. (optional) Download the SuperSU 1.65 version and flash it via recovery.
Hit the thanks if i helped!
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 12:48 PM ---------- Previous post was at 12:47 PM ----------
RASTAVIPER said:
Did you try flashing a recovery from Recovery Tools aplication?
You will find it in Play store.
Sent from my NookColor using Tapatalk 4
Click to expand...
Click to collapse
He doesn't have root for that...
Sent from my Nexus 4 using XDA Premium 4 mobile app
I've tried that. When after I flash in fastboot and hit start in the bootloader, it starts into android and not into recovery. Should I click recovery instead of start?
Sent from my AOSP on Mako using xda app-developers app
Same Problem!
EggosEvo said:
I flashed a kit kat ROM earlier to play around on, and when I was rebooting I accidentally hit the wrong button in cwm to not reflash recovery. Now I don't have recovery anymore, and I don't have access to a computer so I can flash the PA version of Kit Kat. ROM manager will not flash recovery for me. Is there anything I can do to get recovery without a computer?
Sent from my AOSP on Mako using xda app-developers app
Click to expand...
Click to collapse
I not can access the recovery. i try now wit nexus 4 toolkit and wugfresh!
EggosEvo said:
I've tried that. When after I flash in fastboot and hit start in the bootloader, it starts into android and not into recovery. Should I click recovery instead of start?
Sent from my AOSP on Mako using xda app-developers app
Click to expand...
Click to collapse
Well one would assume clicking on recovery would send the phone into recovery, instead of start. PS. When you see the Android with red icon, you are looking at the stock recovery itself, so no, you do have (stock) recovery on your phone.
I tried that, and it worked. However, the only thing I can flash is my backup. Attempting to flash a different rom, like the 4.4 PA doesn't flash it, just leaves that same 4.4 rom.
Sent from my Nexus 4 using xda app-developers app
I admit I am new to the G2. On my GS3 all that was needed was factory reset (I formatted /system to be sure) when I was changing ROMs. I keep getting errors when I try to flash a CM11 ROM on my D801 (tmo). I specified CM11 because I was able to get a stock-based ROM working without much trouble. I have gotten into the habit of taking a backup before doing anything so I'm not gonna lose anything. I'm using TWRP which I've gotten pretty comfortable with on my GS3. I'm pretty sure there's something I'm missing.. Can anyone help?
Possible corrupt or incomplete download? You could try a different build of CM11... I assume you made sure the build was compatible with your variant because you already specified it is a D802. I occasionally had failed flashes on TWRP 2.6.3.3 but I upgraded to 2.6.3.4 and a lot of them worked... It could be a number of things...
Cyanogenmod thread recommends you use CMW recovery when flashing Cyanogenmod because TWRP gives off too many problems.
Sent from my LG-D800 using XDA Premium 4 mobile app
I thought the same thing, even though I've only had it happen one time before. I checked the md5 hash and the codes matched from the website, my HDD and on my phone so that wasn't it. And yes I made sure it was for the D801. I guess it's time to try a different recovery =/ changing recovery is always a pain too
I have a stupid question..can I use D802 (AT&T variant) CWM on my D801 (T-Mobile)? Or do I have to use my computer to flash via adb again?
Medlock87 said:
I have a stupid question..can I use D802 (AT&T variant) CWM on my D801 (T-Mobile)? Or do I have to use my computer to flash via adb again?
Click to expand...
Click to collapse
The AT&T phone model is d800 not d802. Why don't you just flash the recovery right from your phone? Download the flashable .zip file go into your recovery and select the zip to flash, then reboot recovery and the new recovery should pop up? Skip all that adb nonsense I've never done that. I would only do the adb to flash a recovery when I'm in an emergency and can't get into anything.
Sent from my LG-D800 using XDA Premium 4 mobile app
---------- Post added at 03:46 AM ---------- Previous post was at 03:44 AM ----------
I would use the correct CMW version for your set phone because idk if it'll mess up your phone completely or if it'll be fine.
Sent from my LG-D800 using XDA Premium 4 mobile app
xxxrichievxxx said:
The AT&T phone model is d800 not d802. Why don't you just flash the recovery right from your phone? Download the flashable .zip file go into your recovery and select the zip to flash, then reboot recovery and the new recovery should pop up? Skip all that adb nonsense I've never done that. I would only do the adb to flash a recovery when I'm in an emergency and can't get into anything.
Sent from my LG-D800 using XDA Premium 4 mobile app
---------- Post added at 03:46 AM ---------- Previous post was at 03:44 AM ----------
I would use the correct CMW version for your set phone because idk if it'll mess up your phone completely or if it'll be fine.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got it figured out. I was able to find a flashable zip (for some reason they were nearly impossible to find for my old phone) flashed CWM and CM11 is up and running without any further issue! :victory:
Medlock87 said:
I got it figured out. I was able to find a flashable zip (for some reason they were nearly impossible to find for my old phone) flashed CWM and CM11 is up and running without any further issue! :victory:
Click to expand...
Click to collapse
Cool! If you have any other questions, let us know!