I just installed Paranoid Android latest version; had a custom recovery that was recommended (the same as when I had used cyanogenmod previously). "LockedDualRecovery" is the file I used. I am surprised to see I am unable to root the phone with sony mobile flasher (worked before). Towelroot opens a page that has huge text and I cannot press any buttons on it.
When I try to reboot into recovery mode (to install GAPPS) I get an orange light and the "SONY" screen permanently. Holding all the buttons can shut down the phone; and it will boot into PA just fine.
I am new with the rooting/roms, and this is an impass for me. I am not sure how I can do anything without recovery, or root access.
What the hell? You installed Paranoidandroid and your looking for rooting apps?
You obviously have an unlocked bootloader so if you don't have recovery just flash a cm kernal that has recovery and flash supersu through recovery. lol.
This is a pretty basic answer, did you search?
Sent from my D6503 using Tapatalk
o0 Matt 0o said:
What the hell? You installed Paranoidandroid and your looking for rooting apps?
You obviously have an unlocked bootloader so if you don't have recovery just flash a cm kernal that has recovery and flash supersu through recovery. lol.
This is a pretty basic answer, did you search?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
yes I did quite extensive searching; my ignorance is not answered by those searches. I did not know some installations include custom recoveries. When flashing PA it says "superSU is not installed, you should root it and install SU Swipe to do so" with twrp. Didn't work like this, and the GAPPS package I had installed did not work. I reflashed and saw a 'flashable' TWRP that I installed after PA and it worked fine.
Related
So I'd been having some problems lately with my phone hanging on the Samsung screen on boot. Been running CM11 1/1/2014 nightly most recently. Decided to try using TWRP instead of CWM. That didn't seem to help my issue, so I tried installing CWM again. I used an app called Recovery Tools to download the touch version of CWM. After it said it installed, I tried to boot into recovery and got the error "Unauthorized software found. Please contact Verizon." (paraphrased a little).
Doing some research it looks like that error typically comes up when the bootloader is locked. Now, obviously I had my bootloader unlocked (well, Loki'd) because I was running CM11. Any help fixing this? I'm able to bypass the warning screen on boot if I hold down vol up + power like I'm going into download mode, but then hit vol down to cancel to boot up the phone. Once booted everything is ok, but any reboot just brings that up again. Using ROM manager to flash CWM recovery seems to work ok and it says its installed, but same issue. So does trying to flash TWRP from Goo.
If I were to run this tool that I used to root and loki before (http://forum.xda-developers.com/showthread.php?t=2301720) to install a recovery, would I be able to get everything going again? I think that somehow the recovery I installed wasn't Loki'd, although I picked the right one for my device.
Thank you in advance for any replies.
The fix I found was by pure dumb luck. I ended up trying to flash a recovery with Odin. Odin failed but reboot back into the os. I then used the twrp manager app from the playstore (mainly because goomanager wasn't downloading the recovery at the time) to flash the latest twrp recovery and all was good. Even though Odin failed at flashing the recovery I still think it helped somehow. I haven't thought much about why but I might have to now.
Sent from my SCH-I545 using Tapatalk
You could probably try using ODIN to get back to stock MDK and then Re-Root and install a recovery after.
Edit: And then flash CM11 again.
Sent from my SCH-I545 using Tapatalk
Will this one-click stock ROM work?
http://www.rwilco12.com/downloads.p... S4 (Verizon) (SCH-I545)/Stock ROMs/One-Click
or, which of the files on this page are what I would want? (about 1/3 of the way down for SCH-I545)
http://www.droidviews.com/how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models/
I was actually able to reflash TWRP w/ their app from the Play Store. Still get a lot of boot hangs on the Samsung logo though. Seemed to happen less with CWM, but now I'm too scared to try to install a different recovery. I appreciate all your help guys.
I'm trying to install [ROM][4.4.2 CM-11.0][Cyanogenmod 11.0 Unofficial][KOT49H][08/01/14].I have Unlocked bootloader with the Asus tool and i've installed rom manager and have CWM 5.8.3.4 (not touch) installed. I was looking for a specific CWM in OP's post, but didn't find any. Now, when i reboot into recovery, i see a text saying the device is unlocked, then it goes to the screen where the Android has the hood open and a red warning triangle above it. It stays like this for a couple of minutes, then i just reboots into stock JB. What am i doing wrong? BTW, don't have a dock, US pad...
EDIT: I fixed it with a fastboot installation
You fixed it? Intradesting, I had the same problem but then read here that CWM is no good, at least on the Prime, and fastboot-flashed TWRP instead.
This does work, however I cannot restore the Stock-ROM-Backup. Not sure whether this is TWRP's fault, though.
Quote from the CM11 Unofficial thread:
ebildude123 said:
You need the recovery he provided to flash this rom
http://forum.xda-developers.com/devdb/project/?id=2229#downloads
Sent from my TF300T on CM 11 (4.4.2) using Tapatalk 4
Click to expand...
Click to collapse
I think this is a modified version, but it works like a charm
I've been following instructions to install Android 4.4 KitKat on Galaxy Mega 6.3 via Cyanogenmod 11.
My device has been rooted for some time, but I have never before installed any ROMs.
I have successfully (it seems) installed Clockworkmod via Odin, yet when I boot into Custom recovery mod, there is no "backup and restore" option, and indeed I seem to be in "Android system recovery", not CWM recovery (see screenshot).
I know that I can't install Cyanogenmod without Clockworkmod on board, so I'm nervous to proceed. Can anyone please advise?
AidanBell said:
I've been following instructions to install Android 4.4 KitKat on Galaxy Mega 6.3 via Cyanogenmod 11.
My device has been rooted for some time, but I have never before installed any ROMs.
I have successfully (it seems) installed Clockworkmod via Odin, yet when I boot into Custom recovery mod, there is no "backup and restore" option, and indeed I seem to be in "Android system recovery", not CWM recovery (see screenshot).
I know that I can't install Cyanogenmod without Clockworkmod on board, so I'm nervous to proceed. Can anyone please advise?
Click to expand...
Click to collapse
That looks like the standard recovery, not clockwork mod, what model of mega do you have?
You have to reboot to recovery first after flashing custom recovery. That's because the stock ROM checks if the recovery is changed and overwrites it with the stock recovery again.
Rebooting to recovery first will solve the issue.
Sent from my GT-I9205 using Tapatalk
Thanks for responding guys.
Jzsidebott: It's a Mega 6.3, GT-I9205, in England.
Silesh.Nair: I've installed "ROM Manager" and used "Reboot into recovery", but I get to the same place as before; "Android system recovery <3e>", exactly as the screenshot in my first post.
So I used Odin again, and again apparently successfully installed "GT-I9205-recovery.tar", but still I can only get standard recovery.
Could I ask you guys if you would recommend CyanogenMod Installer?
http://beta.download.cyanogenmod.org/install
I'm a newbie at this, so if this method is considered safe I'd be happy to go down that route. Any advice? Cheers.
Don't use ROM manager. Download the cwm tar file and use Odin to flash. Remember to untick auto reboot in Odin and then reboot to recovery first. It will work for sure. Don't flash anything if you are running Knox enabled firmware else you'll screw up your phone.
Sent from my GT-I9205 using Tapatalk
Thanks. As I said I did use Odin to flash. I just installed ROM Manager afterwards to try to find out whether the Odin Flash had worked. I am a newbie at this and to be honest I have no idea what Knox enabled firmware is or whether I'm running it. I think that for safety's sake I'd best drop the whole thing and not risk bricking my phone, but thank you all for the help all the same.
Hello,
I followed this post to root and install TWRP recovery on my Sprint Samsung Note 3. The root procedures went well, showing rooted successfully.However, I installed TWRP recovery using GooManager, and also tried installig through Odin.
It shows that TWRP recovery is successfully installed, but I am not able to boot into recovery. The phone seems to try to boot into TWRP for ever.....
Later I read this post, which says that Do not try on Android 4.4.2 KitKat firmware!
IS my issue due to my rooting and installing TWRP are based on 4.4.2 (my phone is having new NC5 OTA update)? How shall I do?
Thank you very much for your helps!!!
Did you fiqure it out
Sent from my SM-G900P using XDA Free mobile app
lsdyna said:
Hello,
I followed this post to root and install TWRP recovery on my Sprint Samsung Note 3. The root procedures went well, showing rooted successfully.However, I installed TWRP recovery using GooManager, and also tried installig through Odin.
It shows that TWRP recovery is successfully installed, but I am not able to boot into recovery. The phone seems to try to boot into TWRP for ever.....
Later I read this post, which says that Do not try on Android 4.4.2 KitKat firmware!
IS my issue due to my rooting and installing TWRP are based on 4.4.2 (my phone is having new NC5 OTA update)? How shall I do?
Thank you very much for your helps!!!
Click to expand...
Click to collapse
You should be suing TWRP 2.7.0.1 and do not use goo manager.. Go to their site and click on the alternate download.. I do believe TWRP mentioned they disable the goo manage download because of issues.. Make sure you are also choosing the right phone.. I have choosing the wrong phone more than once.. Also when your done flashing in odin, and you reboot into recovery manually, make sure you wait until you see the line about recovery, before you release the 3 buttons, or you will just boot into your desktop.. Also you can use TWRP on KItKat firmware as many have done so..
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Joserin said:
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Click to expand...
Click to collapse
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
JohnSmit268 said:
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
Click to expand...
Click to collapse
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Joserin said:
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Click to expand...
Click to collapse
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
JohnSmit268 said:
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
Click to expand...
Click to collapse
I already did that.. Root Checker Basic says I do not have proper root access and the TWRP Manager tool also says I do not have root
It is really weird. I'm on i9300 official nightlies and have working root!
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Joserin said:
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Click to expand...
Click to collapse
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
kush2.0 said:
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
Click to expand...
Click to collapse
Already tried that. SU binary just doesn't update. I even downloaded the Update zip and flashed from recovery, it still asks to update the binary after reboot. There is no TWRP option to update the binary either, it directly goes to the normal method and fails everytime. Tried like 20 times probably
I'd say flash back to stock and start over. Installing siyah probably borked something.
shivadow said:
I'd say flash back to stock and start over. Installing siyah probably borked something.
Click to expand...
Click to collapse
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
Joserin said:
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
Click to expand...
Click to collapse
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
kush2.0 said:
What recovery version are you using then?? ??
Click to expand...
Click to collapse
kush2.0 said:
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
Click to expand...
Click to collapse
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Joserin said:
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Click to expand...
Click to collapse
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
kush2.0 said:
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
Click to expand...
Click to collapse
Uhm TWRP Manager doesn't work without root. Already tried that
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Joserin said:
Uhm TWRP Manager doesn't work without root. Already tried that
Click to expand...
Click to collapse
Yeah sorry you do need root access. Your probably better of doing what rp158
Said. Your twrp recovery isn't up to date enough to install a new cm13 based ROM.
rp158 said:
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Click to expand...
Click to collapse
Meh Id rather just let it be for what it is. It's my dad's phone and I just wanted him to have AdAway, he's not much of a tech-head.
Thanks people
No root access to S3 when upgraded to CM 13; affecting full access Ext SDcard
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
kevin.a69 said:
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
Click to expand...
Click to collapse
I flashed QSi9300KK on my phone (with kernel. I forget the name but it was the third option - not Agni or stock) and after that TWRP and then CM13. Everything's working fine now, even root access.
Remember do not pick the first two kernels in the installer, they didn't work correctly. Third one works like a charm.