hello when i try to install TWRP it says it installed but when i reboot it still goes to the stocked version. any way to fix this?
fujirio said:
hello when i try to install TWRP it says it installed but when i reboot it still goes to the stocked version. any way to fix this?
Click to expand...
Click to collapse
Are you trying to reboot from goomanager into recovery using the option in goomanager? Or are you trying to go into recovery using the physical buttons after powering off?
jj14 said:
Are you trying to reboot from goomanager into recovery using the option in goomanager? Or are you trying to go into recovery using the physical buttons after powering off?
Click to expand...
Click to collapse
i did both and it just takes me to adb install update or reboot phone options
fujirio said:
i did both and it just takes me to adb install update or reboot phone options
Click to expand...
Click to collapse
How are you installing via GooManager? Are you using the "InstallOpenRecoveryScript" option in the menu?
Is literally as easy as this usually: http://galaxys4root.com/galaxy-s4-root/how-to-install-twrp-on-rooted-galaxy-s4-using-goo-manager/
CCallahan said:
How are you installing via GooManager? Are you using the "InstallOpenRecoveryScript" option in the menu?
Is literally as easy as this usually: http://galaxys4root.com/galaxy-s4-root/how-to-install-twrp-on-rooted-galaxy-s4-using-goo-manager/
Click to expand...
Click to collapse
yeah i did from the app and now i lost my root access
ok finally figured it out. I had to do a un-root method and then re-root thanks every one for the quick responses.
Related
Hi, wanted to ask why am i unable to enter clockworkmod after updating to 4.1.1 official firmware. I've already uninstall and reinstall clockworkmod a few times and the problem is still there. Will appreciate the feedback in the forum. Thanks in advance.
Did you do this:
lsherif said:
Just follow the below steps :
if you are still getting the stock recovery 3e follow these steps :
1. When flashing CWM through odin untick the "Auto Reboot" option within Odin.
2. Flash CWM.
3. When done , press power & volume up ( the one apart from power button ) until the Samsung logo appears, then leave both buttons.
4. CWM will appear.
5. Choose "Reboot System now "
6. You will get a new screen with an option mentioning something like " disable flash recovery , press it & reboot.
7. Now if you get back to pressing power & volume up you will have a permanent CWM.
Then you can install root through CWM.
Click to expand...
Click to collapse
Sent from my GT-N8010 using xda app-developers app
mauricewal said:
Did you do this:
Sent from my GT-N8010 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help. Found out the problem from your reply; forgot to unchecked auto reboot.
You dont require CWM anymore to root, you can root using exynos exploit patch apk with just a click
samir_a said:
You dont require CWM anymore to root, you can root using exynos exploit patch apk with just a click
Click to expand...
Click to collapse
Thanks for the update
Updating through the app no longer works for do I have to load it through adb?
Sent from my TouchPad using XDA Premium HD app
Install OpenRecoveryScript via GooManager.
Or get it here:
http://forum.xda-developers.com/showpost.php?p=45282861&postcount=1418
Install via TWRP then reboot recovery.
Atlasstorm said:
Updating through the app no longer works for do I have to load it through adb?
Sent from my TouchPad using XDA Premium HD app
Click to expand...
Click to collapse
If your having the same problem as i did i just downloaded http://forum.xda-developers.com/showthread.php?t=2049003 and updated it through there. when i tried goomanager it said that it updated it but when i went into twrp it was still at 2.0 something finally updated that way to 2.6.1.1 hope it helps if goomanager way doesn't work for you.
spriteboost said:
If your having the same problem as i did i just downloaded http://forum.xda-developers.com/showthread.php?t=2049003 and updated it through there. when i tried goomanager it said that it updated it but when i went into twrp it was still at 2.0 something finally updated that way to 2.6.1.1 hope it helps if goomanager way doesn't work for you.
Click to expand...
Click to collapse
thanks for the help i'll get on that when i have the time
wcn said:
Install OpenRecoveryScript via GooManager.
Or get it here:
http://forum.xda-developers.com/showpost.php?p=45282861&postcount=1418
Install via TWRP then reboot recovery.
Click to expand...
Click to collapse
thanks, flashed it and all is well
wcn said:
Install OpenRecoveryScript via GooManager.
Or get it here:
http://forum.xda-developers.com/showpost.php?p=45282861&postcount=1418
Install via TWRP then reboot recovery.
Click to expand...
Click to collapse
Did the trick.
Hi!
I'm totally new to Nexus 4. I'm on 4.3 and yesterday unlocked bootloader and rooted. Everything works.
Today I booted in fastboot just to see CWM. On exiting it warned me about possible root lost. I answered YES.
So now I lost root. I still have SuperSU but when I run it I get message that no binaries installed and SU can't install them and I need to reroot phone...
I tried to download chainfire 1.65 zip and flash it CWM - same result...
Any hints would be appreciated!
Sent from my Nexus 4 using xda app-developers app
Goldenmeadow said:
Hi!
I'm totally new to Nexus 4. I'm on 4.3 and yesterday unlocked bootloader and rooted. Everything works.
Today I booted in fastboot just to see CWM. On exiting it warned me about possible root lost. I answered YES.
So now I lost root. I still have SuperSU but when I run it I get message that no binaries installed and SU can't install them and I need to reroot phone...
I tried to download chainfire 1.65 zip and flash it CWM - same result...
Any hints would be appreciated!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try flashing TWRP.
Pipusz said:
Try flashing TWRP.
Click to expand...
Click to collapse
Ok, I'll try.
But am I accessing CWM properly? Do I have to go through fastboot?
My last phone had button combination to boot straight into recovery. I don't see such option in Nexus 4.
Thanks again!
Sent from my Nexus 4 using xda app-developers app
Goldenmeadow said:
Ok, I'll try.
But am I accessing CWM properly? Do I have to go through fastboot?
My last phone had button combination to boot straight into recovery. I don't see such option in Nexus 4.
Thanks again!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Is there an option in your current ROM to reboot into recovery? If not, power off the device, then hold down the volume up-down and the power buttons. I tend to forget these button combinations, but I think this is the one that will lead you to fastboot. From there, navigate with the volume buttons and OK something with the power button.
Pipusz said:
Is there an option in your current ROM to reboot into recovery? If not, power off the device, then hold down the volume up-down and the power buttons. I tend to forget these button combinations, but I think this is the one that will lead you to fastboot. From there, navigate with the volume buttons and OK something with the power button.
Click to expand...
Click to collapse
Thanks for reply!
Sorry I forgot to give tech details: I run stock ROM + kernel, just rooted and unlocked fastboot.
So yes, this is the way I use to access recovery: through fastboot.
Last time while exiting CWM I selected NO to last question about trying to fix root and my root is still here
Thanks for help again!
Sent from my Nexus 4 using xda app-developers app
Goldenmeadow said:
Thanks for reply!
Sorry I forgot to give tech details: I run stock ROM + kernel, just rooted and unlocked fastboot.
So yes, this is the way I use to access recovery: through fastboot.
Last time while exiting CWM I selected NO to last question about trying to fix root and my root is still here
Thanks for help again!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Glad to hear that. If it's OK, leave it that way, it won't cause any harm.
If you want to try TWRP, go to the Play Store and download the GooManager application. Grant it superuser permission, then hit the menu button at the upper-right side of the screen, right under the clock. From there, select "Install OpenRecoveryScript" and it will download and flash the latest TWRP on your device. After that, reboot to recovery to check if it's working.
I just went throught the same thing
I just unlocked my phone and flashed the latest CWM recovery and then the latest SuperSU zip; and all was fine. But whenever I was exiting from CWM recovery, it said "Possible root access loss" and if it can "fix it". Whenever I say "Yes" I lose root access; and when I select "No" the root privileges stayed. I could have lived with that but I thought screw this **** and flashed the TWRP recovery. This one doesn't say anything about losing access; all's cool.
But I still want to know what CWM was trying to do. It was trying to "fix" /system/bin/su and losing root access. Anybody?
crossjaw said:
I just unlocked my phone and flashed the latest CWM recovery and then the latest SuperSU zip; and all was fine. But whenever I was exiting from CWM recovery, it said "Possible root access loss" and if it can "fix it". Whenever I say "Yes" I lose root access; and when I select "No" the root privileges stayed. I could have lived with that but I thought screw this **** and flashed the TWRP recovery. This one doesn't say anything about losing access; all's cool.
But I still want to know what CWM was trying to do. It was trying to "fix" /system/bin/su and losing root access. Anybody?
Click to expand...
Click to collapse
cwm is most likely installing a su that isnt up to date
simms22 said:
cwm is most likely installing a su that isnt up to date
Click to expand...
Click to collapse
Oh... I've never had problems with CWM before( this wasn't actually a problem anyway). Thanks
I have a working ROM installed, a while back I tried to install multirom but it didn't work out, whenever I try to boot into recovery I get an AT&T has not authorized this software screen. Tried using goomanager and flashify but twrp will not reinstall. How do I get a good recovery back on the phone? I don't remember what I did the first time.
XxSHaDoWxSLaYeRxX said:
I have a working ROM installed, a while back I tried to install multirom but it didn't work out, whenever I try to boot into recovery I get an AT&T has not authorized this software screen. Tried using goomanager and flashify but twrp will not reinstall. How do I get a good recovery back on the phone? I don't remember what I did the first time.
Click to expand...
Click to collapse
I believe you can try running CASUAL again if those aren't working.
It says that it is not for my device and fails.
XxSHaDoWxSLaYeRxX said:
It says that it is not for my device and fails.
Click to expand...
Click to collapse
What's your bootloader version? Install terminal emulator and type getprop ro.bootloader
Sent from my SGH-I337
I just got the new T-Mobile update, but I haven't flashed it. How do I get it off the phone? I looked in /cache and /download and it's not in either. I am rooted so I have access to all the folders.
Thanks
Same here. Trying to figure out how to pull the OTA for you guys.
Have you guys tried this method? Starting from #6 on.
http://forum.xda-developers.com/showthread.php?p=56859170
https://android.googleapis.com/pack...amu-ota-LYZ28J-from-LYZ28E-superblock-fix.zip
Sweet! Thanks. Now I have to try and flash it
Downloaded and Sideloaded. Just waiting for it to finish booting.
Finished boot. Took a minute but seems to respond fine after initial startup.
biggiestuff said:
https://android.googleapis.com/pack...amu-ota-LYZ28J-from-LYZ28E-superblock-fix.zip
Click to expand...
Click to collapse
Can we flash this with TWRP? If we have the stock but rooted rom?
samomamo said:
Can we flash this with TWRP? If we have the stock but rooted rom?
Click to expand...
Click to collapse
I used wugs to flash stock rom with no wipe. Then took the OTA. You can side load it as well. Then used wugs to re-root
Sent from my Nexus 6 using Tapatalk
samomamo said:
Can we flash this with TWRP? If we have the stock but rooted rom?
Click to expand...
Click to collapse
no
simms22 said:
no
Click to expand...
Click to collapse
Thank you
The full LYZ28J image is now available for download directly from Google.
does anyone know if there's a boot.img without forcencrypt for LYZ28J?
What's the difference, please, between the file posted by @biggiestuff
https://android.googleapis.com/pack...amu-ota-LYZ28J-from-LYZ28E-superblock-fix.zip
and the one posted by @jcsww
https://dl.google.com/dl/android/aosp/shamu-lyz28j-factory-0530e1e3.tgz ?
PhilipTD said:
What's the difference, please, between the file posted by @biggiestuff
https://android.googleapis.com/pack...amu-ota-LYZ28J-from-LYZ28E-superblock-fix.zip
and the one posted by @jcsww
https://dl.google.com/dl/android/aosp/shamu-lyz28j-factory-0530e1e3.tgz ?
Click to expand...
Click to collapse
Mine is the OTA and the other is the full factory image
Sent from my Nexus 6 using Tapatalk
vivanshah said:
does anyone know if there's a boot.img without forcencrypt for LYZ28J?
Click to expand...
Click to collapse
Looks like not yet. I tried using Wug's toolkit just now and got the attached error.
vivanshah said:
does anyone know if there's a boot.img without forcencrypt for LYZ28J?
Click to expand...
Click to collapse
allen099 said:
Looks like not yet. I tried using Wug's toolkit just now and got the attached error.
Click to expand...
Click to collapse
There is now I had made one earlier today for my new N6Shamu rom which uses the LYZ28J as a base. I de-odexed it as well. While I was making the rom, I edited the kernel so it does not force encrypt. Try this flashable zip and let me know how you get on.
Stephen said:
There is now I had made one earlier today for my new N6Shamu rom which uses the LYZ28J as a base. I de-odexed it as well. While I was making the rom, I edited the kernel so it does not force encrypt. Try this flashable zip and let me know how you get on.
Click to expand...
Click to collapse
Cool! Trying it now.
*EDIT* I can simply extract the .img, rename it, and drop it into the toolkit, correct?
allen099 said:
Cool! Trying it now.
*EDIT* I can simply extract the .img, rename it, and drop it into the toolkit, correct?
Click to expand...
Click to collapse
Its a fully flashable zip, but yes you can.
lorloff said:
Downloaded and Sideloaded. Just waiting for it to finish booting.
Finished boot. Took a minute but seems to respond fine after initial startup.
Click to expand...
Click to collapse
samomamo said:
Can we flash this with TWRP? If we have the stock but rooted rom?
Click to expand...
Click to collapse
Not sure if these two posts are related and I'm probably doing something wrong trying to apply this update. I am stock rooted with the MultiROM version of TWRP 2.8.7. When I go into ADB Sideload, ADB loses the connection so I can't sideload. I just updated to Windows 10 Pro too, so I don't know if that is related either.
These are the commands I used after I connected my phone:
adb devices (works)
adb reboot recovery (works)
In TWRP - Advanced, then ADB Sideload (works)
Swipe to Start Sideload (connection lost)
Cancel (connection restored)
Any tips or help to get this installed would be greatly appreciated.
JimSmith94 said:
Not sure if these two posts are related and I'm probably doing something wrong trying to apply this update. I am stock rooted with the MultiROM version of TWRP 2.8.7. When I go into ADB Sideload, ADB loses the connection so I can't sideload. I just updated to Windows 10 Pro too, so I don't know if that is related either.
These are the commands I used after I connected my phone:
adb devices (works)
adb reboot recovery (works)
In TWRP - Advanced, then ADB Sideload (works)
Swipe to Start Sideload (connection lost)
Cancel (connection restored)
Any tips or help to get this installed would be greatly appreciated.
Click to expand...
Click to collapse
I had the same issue. I found this somewhere and it worked:
From a command prompt (administrator):
adb devices and be sure it shows your device serial number.
adb reboot recovery
Use the Power button and Volume + button to get past the green droid with the red sign.
Unplug the usb cord from the PC and then plug it back in.
In W10, go to Device Manager.
Find your phone under Other Devices with a Yellow !.
Right click on it and choose "Update Driver Software"
Choose "Browse my computer", then "Let me pick from a list."
If you see categories, select "Android Device", then select "Android ADB Interface".
The driver will install and adb sideload should proceed with the update.
What a PITA but it worked.