says recovry installed, but safe system not active on mine (s5 active/870a)
if I can't use safestrap in 4.4.4 or 5.0, what do i use to nandroid?
If it says safe system not active it just means you aren't using a virtual slot, if you can boot in to it its working.
Sent from my SAMSUNG-SM-G900A using Tapatalk
if you can boot in to it its working.
Click to expand...
Click to collapse
I can't boot into it/recovery when i try to reboot, there's a cyan loading circle/symbol but then it boots normally (not into recovery)
stillsober said:
I can't boot into it/recovery when i try to reboot, there's a cyan loading circle/symbol but then it boots normally (not into recovery)
Click to expand...
Click to collapse
You need to downgrade the kernel to use it if you're on lollipop, there's an app that does that for you and then a flashable zip to go back to the L kernel once everything is said and done.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Related
We all know this is Koush's Work But Just Figured I Would Post It Up Here in case anyone needs it............
Thank you. Is there anyway to flash through Rom Manager
Sent from my Nexus S using Tapatalk
Zehlek said:
Thank you. Is there anyway to flash through Rom Manager
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
yea it should b the first option in the menu
aam6906 said:
yea it should b the first option in the menu
Click to expand...
Click to collapse
I flashed it, but now I am unable to boot into recovery. It takes me to the bootloader instead.
The only way I can get back into recovery is to flash and older version of CWM. Is anyone else having this issue?
Same problem here, with i9020.
i've a german nexus s (.23) it works very well!
RickROM said:
I flashed it, but now I am unable to boot into recovery. It takes me to the bootloader instead.
The only way I can get back into recovery is to flash and older version of CWM. Is anyone else having this issue?
Click to expand...
Click to collapse
I had that problem and I just flashed it a second time in rom manager and it works
Sent from my Nexus S using Tapatalk
Zehlek said:
I had that problem and I just flashed it a second time in rom manager and it works
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I flashed it multiple times in ROM Manager, and I could never get it to work. I will try again later.
Fix permissions then reboot, I had the same issue and that fixed it
Sent from my Nexus S using XDA Premium App
Im having the same issue can't boot into recovery now
Where can we find the changelog?
Darrien13 said:
Im having the same issue can't boot into recovery now
Click to expand...
Click to collapse
I have the same proble. I have to flash back to CWM 3.0.0.0 to able to go to recovery mode. I'm not sure whether it's becuase I rooted my wiht this methode "Root & custom recovery WITHOUT oem unlock & wipe ".
Any suggestion? Or just stay with CMW 3.0.0.0?
You can try this one. In the same forum. http://forum.xda-developers.com/showthread.php?t=988686
yup it killed my recovery mode too. reverting back!
brrip said:
yup it killed my recovery mode too. reverting back!
Click to expand...
Click to collapse
It also killed my recovery.
This killed my recovery too. I did as Suprakarma suggested and all is well.
From within RomManager, run the fix permissions script.
(This had a problem on my device, it appears it doesn't like the BusyBox that Titanium Backup installed, so I had to install a new copy from the market).
Once that script's finished, reboot, then reinstall recovery from Rom Manager. Boot into recovery.
Hope that helps.
nop working i fix permition and flash recovery and stell same no working
Sent from my Nexus S using XDA Premium App
Just out of curiousity, can anyone confirm if this recovery works on the i9023 or i9020a?
Sent from my Nexus S using Tapatalk
I am back on 3.0.0.5 after trying to fix permissions. I will try again later.
we can always use an extra mirror
some times Koush website goes down for long period of times
I get my MB886,yesterday. The first thing I do is change the moto recovery to the touchrecovry.Then I enter into the recovery,formating system cache and data, then I do a dual wipe.After this,I flash the BatakangROM_AtrixHD_1.10.zip,and it's successfully installed. But when restarting the system,it stays in the red moto screen.In the end, I flash the rooted JB ROM. But I want to flash a clean third part ROM.Who can tell me how to deal with it? is there something to do with the BatakangROM_AtrixHD_1.10.zip to fit my MB886?
This is the Recovery for MB886
I download it from gfan。com
flash with fastboot,unlocked bootloader is needed
help me to solve the problem,please!
Batakang most likely needs to be installed with Safestrap recovery.
http://forum.xda-developers.com/showthread.php?t=1995220
coolloser said:
Batakang most likely needs to be installed with Safestrap recovery.
http://forum.xda-developers.com/showthread.php?t=1995220
Click to expand...
Click to collapse
Yup.
Sent from my Galaxy Nexus using Tapatalk 2
I just got an OTA.
http://android.clients.google.com/p...signed-nakasi-KRT16S-from-KRT16O.3aad414b.zip
Changelog: https://funkyandroid.com/aosp-KRT16O-KRT16S.html
My initial analysis.. It's tiny, 1.5 megs large. It's adding the recovery-from-boot.p stuff back, something I think disappeared in like 4.3 or so, so this will wipe out custom recovery when booted. Just remove the file from /system and re-flash recovery.
Bunch of files are patched, including build.prop for build info but it's still 4.4. No kernel change.
You'll have to re-root, as usual. This, with the recovery wipe, means you'll be using fastboot to flash recovery, re-flash supersu, etc.
AdAway is saying it can't remount /system. I didn't have this problem previously, so something might have changed here. I can do it manually in adb but AdAway keeps failing to do it itself.
Any idea what it does?
Sent from my Nexus 7 using Tapatalk 4
I just got the exact same thing! It looks like a patch to the original 4.4 OTA.
Sent from my Nexus 7 using xda app-developers app
Analyzing, although I'm not the best at this. Looks like it's enabling the recovery-from-boot.p again, something that seemed to disappear in like 4.3. Will over-write custom recovery, so we'll have to delete the file from /system and re-flash CWM/TWRP.
It's patching a large number of other files, but I couldn't guess what it's doing. I'm sure someone else could.
It flashed fast enough on my system, I'll update if it changed to 4.4.1 or anything like that.
I've flashed the update KRT16S and recovery not wiped. Twrp still there and working.
Sent from my Nexus 7 using Tapatalk HD
My recovery is gone after that little update. I even tried reflashing it using fastboot and it was not installed after a reboot again so something is writing over TWRP on a reboot for me.
Evo_Shift said:
My recovery is gone after that little update. I even tried reflashing it using fastboot and it was not installed after a reboot again so something is writing over TWRP on a reboot for me.
Click to expand...
Click to collapse
Read the op
I also got the OTA update today. It blasted away TWRP and SU. Simple process to reload both.
BTW... the KRT16O update files no longer appear for download on the Nexus Factory Image page on Google, replaced with KRT16S.
ADAway has no problem for me. adaway 2.3 with superSU1.69. Both recovery image and supersu need to reinstall again.
I flashed stock recovery and unrooted just to be safe, then used ADB sideload to apply the update. All went well. I'm letting it sit for a while before flashing TWRP and installing SuperSU.......
Sent from my rooted GSM Galaxy Nexus
CatThief said:
I flashed stock recovery and unrooted just to be safe, then used ADB sideload to apply the update. All went well. I'm letting it sit for a while before flashing TWRP and installing SuperSU.......
Sent from my rooted GSM Galaxy Nexus
Click to expand...
Click to collapse
I did the same thing but I'm getting an error while installing the update, error 7 I think. Any ideas?
The exact same thing happened to me when I tried to install the JWR66Y-to-KRT16O. I got lucky this time. Whew!
You could try downloading the full factory image from Google, extract the image files, and use fastboot flash. I would do that with boot.img and system.img
If that fails, you probably have something inside the system files that isn't stock.
Sent from my Nexus 7 using xda app-developers app
dumdum2 said:
I've flashed the update KRT16S and recovery not wiped. Twrp still there and working.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Hmm, mine won't reboot now. Just goes back into twrp. Argh!
Sent from my SCH-I535 using Tapatalk
I let the OTA update on its own. I lost root and TWRP, but only took a few minutes to reroot and push TWRP back on. All is well.
Sent from my Nexus 7 using XDA Premium 4 mobile app
just lou said:
I let the OTA update on its own. I lost root and TWRP, but only took a few minutes to reroot and push TWRP back on. All is well.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So you flashed the update.zip via TWRP?
qualitymove13 said:
So you flashed the update.zip via TWRP?
Click to expand...
Click to collapse
The update flashed itself in TWRP. I took the OTA.
Sent from my Nexus 7 using XDA Premium 4 mobile app
just lou said:
The update flashed itself in TWRP. I took the OTA.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Strange, when I hit the update button it reboots into TWRP and sits there.
qualitymove13 said:
Strange, when I hit the update button it reboots into TWRP and sits there.
Click to expand...
Click to collapse
Same here. Here goes three hours of reconfiguration.:crying:
I got ota update thru TWRP(ver 2.6.3.1). No problem except recovery will be replaced.
As usual have update process ongoing automaticly in TWRP, no need to do anything.
autorage said:
Same here. Here goes three hours of reconfiguration.:crying:
Click to expand...
Click to collapse
What version of TWRP are you guys running?
Sent from my Nexus 7 using XDA Premium 4 mobile app
I just installed the rooted stock lollipop on my S5. I installed safestrap following the instructions, the app shows it as installed but when I press the "boot to recovery" it just restarts. I don't get the splash screen or anything else. Any ideas? I tried reinstalling it already.
Titek1985 said:
I just installed the rooted stock lollipop on my S5. I installed safestrap following the instructions, the app shows it as installed but when I press the "boot to recovery" it just restarts. I don't get the splash screen or anything else. Any ideas? I tried reinstalling it already.
Click to expand...
Click to collapse
Safestrap does not work with Lollipop! Only FlashFire. Or use this guide,
http://forum.xda-developers.com/showthread.php?p=60224956
Sent from my SAMSUNG-SM-G900A
I have flashfire as well, so can I flash the same roms using flashfire as I would with safestrap?
Titek1985 said:
I have flashfire as well, so can I flash the same roms using flashfire as I would with safestrap?
Click to expand...
Click to collapse
At this point flashing with FF is still experimental. Here is a good place to start:
http://forum.xda-developers.com/showthread.php?p=60070460
Sent from my SAMSUNG-SM-G900A
Hello all,
So I just installed the latest Xposed framework on my rooted note 4 (the stable one not the experimental) and am having trouble installing it. It keeps giving me an error shown below in an attachment. Either Xposed is "Not (yet) compatible with Android SDK Ver. 22 or not compatible with my armeabi-v7a processor.
Any help is appreciated. Other forums have had the same problem except with Marshmallow and I am on 5.1 lollipop
Screenshot link:
https://onedrive.live.com/redir?res...55&authkey=!AMHNWfNScXZPVuw&ithint=folder,png
http://www17.zippyshare.com/v/LDWrcUd7/file.html
http://www17.zippyshare.com/v/daEGu98p/file.html
Flash the .zip in recovery, reboot and then sideboard install alpha apk afterward. This is what we must use to get xposed to work on 5.1.1 TW.
Sent from my SM-N910T using Tapatalk
d12unk13astard said:
http://www17.zippyshare.com/v/LDWrcUd7/file.html
http://www17.zippyshare.com/v/daEGu98p/file.html
Flash the .zip in recovery, reboot and then sideboard install alpha apk afterward. This is what we must use to get xposed to work on 5.1.1 TW.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. Can i do this through ODIN since I dont have TWRP or CWM installed on my phone? If so do I flash under pda with a .tar file or will the zip work?
Thanks!
You would need to Odin the twrp or cwm recovery first, than flash the .zip thru either recovery.
Sent from my SM-N910T using Tapatalk
d12unk13astard said:
You would need to Odin the twrp or cwm recovery first, than flash the .zip thru either recovery.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Thanks so much. I bricked my device a few times trying to fix it but it worked. For anyone else who has the same problem, just use Rashr to flash it and it will automatically go into recovery in TWRP and do it for you. I also made sure to clear cache and dalvic before doing so. Thanks again d12unk13astard!
Glad you got it to work, I can't live without xposed lol
Sent from my SM-N910T using Tapatalk