Hello
I can not install the 3 scented recovery.
https://forum.xda-developers.com/galaxy-j5/development/3-customs-recoverys-galaxy-j5-2015-t3560266
Odin normally installs the recovery, but when it starts the cell phone a message "updating the system" appears and initiates the original recovery of the android
I have the j500m android 6.0.1 and original rom and original kernel
I'm trying to install this rom https://forum.xda-developers.com/galaxy-j5/development/rom-port-6-0-1-perforlite-speed-v2-0-t3560999
Can anybody help me ?
hiperxxx said:
Hello
I can not install the 3 scented recovery.
https://forum.xda-developers.com/galaxy-j5/development/3-customs-recoverys-galaxy-j5-2015-t3560266
Odin normally installs the recovery, but when it starts the cell phone a message "updating the system" appears and initiates the original recovery of the android
I have the j500m android 6.0.1 and original rom and original kernel
I'm trying to install this rom https://forum.xda-developers.com/galaxy-j5/development/rom-port-6-0-1-perforlite-speed-v2-0-t3560999
Can anybody help me ?
Click to expand...
Click to collapse
You must check off auto reboot option of Odin when flashing, after that turn off phone, Power on and when twrp begin swipe to allow changes and you're done...hope this help. :good:
Sent from my Samsung Galaxy J5 using XDA Labs
You need to disable auto reboot option in Odin than reflash TWRP and insert the baterry
Related
my phone is Samsung Galaxy Grand Prime SM-G530FZ
Version: KTU84P.G530FZXXU1AOA9
method for this firmware
omus64 said:
my phone is Samsung Galaxy Grand Prime SM-G530FZ
Version: KTU84P.G530FZXXU1AOA9
method for this firmware
Click to expand...
Click to collapse
http://autoroot.chainfire.eu/ download the respective file for your device and flash it with odin
I rooted my sm-g530fz with cf_auto_root method (SM-G530F) and when i reboot it i have Android system recovery screen
Everytime I restart the device, I have to select "System Reboot" :crying:
omus64 said:
I rooted my sm-g530fz with cf_auto_root method (SM-G530F) and when i reboot it i have Android system recovery screen
Everytime I restart the device, I have to select "System Reboot" :crying:
Click to expand...
Click to collapse
I have the same phone SM-G530fz and firmware KTU84P.G530FZXXU1AOA9. And i have a question for you, is what you say the only problem you have?. Does phone boot and work once you flash cf_auto_root method (SM-G530F)¿
You select start system in recovery and works all¿
Works fine:
http://forum.xda-developers.com/gra...share-galaxy-grand-prime-sm-g530h-f0-t3057571
:good::good::good::good::good::good::good::good:
Stuck in recovery mode
Hi, I've rooted the device with success using this tutorial: http://trueandroid.com/root-samsung-galaxy-grand-prime-sm-g530f-easy-guide/
...the problem I have: whenever I reboot, the device goes into recovery mode and I have to select reboot to start the phone.
I've already removed the phone battery; wiped cache partition and did a wipe data/factory reset but the problem remains.
This is my phone model: Samsung SM-G530FZ, Build ID: KTU84P.G530FZXXU1AOA6
How can I solve this?
You can use Samsung KIES to restore the phone back to it's original ROM. Anyway, anyone solved the "stucked on recovery" problem?
Thanks.
weee
replying to myself: to solve the stucked on recovery, install the new recovery provided in: http://forum.xda-developers.com/gra...share-galaxy-grand-prime-sm-g530h-f0-t3057571
xjpmauricio said:
You can use Samsung KIES to restore the phone back to it's original ROM. Anyway, anyone solved the "stucked on recovery" problem?
Thanks.
Click to expand...
Click to collapse
work perfectly........:good::good::good:THANX
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
I tried on my 530fz and it works! Yeah!!!
xjpmauricio said:
replying to myself: to solve the stucked on recovery, install the new recovery provided in: http://forum.xda-developers.com/gra...share-galaxy-grand-prime-sm-g530h-f0-t3057571
Click to expand...
Click to collapse
It doesnt solved my problem. I still have opened recovery after reboot/restart phone. I disabled KNOX with Kingroot and it still appears. Any solutions?
530H and problems after second reboot
530H running 4.4.4. Downloaded the 530 H file from autoroot.chainfire. eu. Installed with Odin per instructions after wiping the phone of all user data in recovery. Rebooted first time into recovery and from there into normal operation. Installed Rootchecker Basic and this said I was rooted. Installed a number of other tools I run on phones and tablets. After the next reboot, AFWAll+ would not start. Also using NOBloat and Root Browser to try to clean up some of the bloatware and nothing is working. Re checked RootChecker Basic and it says the phone is no longer rooted. WHAT?
Other than Kingroot any alternatives around. Mohan did not work.
Expat
SM-G530FZ Root
Just finished rooting a SM-G530FZ using KingRoot, then i unlocked the phone using Z3x BOX, now everything is OK
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
dork997 said:
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
Click to expand...
Click to collapse
Akalsemann said:
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Try that
Akalsemann said:
Try that
Click to expand...
Click to collapse
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
vinura kithmal said:
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
Click to expand...
Click to collapse
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
dork997 said:
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Click to expand...
Click to collapse
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
dork997 said:
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
Click to expand...
Click to collapse
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Swimguy14 said:
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
vinura kithmal said:
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Click to expand...
Click to collapse
I followed instructions given earlier to install philz recovery, i opened it by booting into it immediately i selected format for new rom install. after that i am stuck on samsung logo i think the old rom is now deleted. Now i am downloading fresh 5.0.2 UK from sammobile i will download it and try to root it normally with flashing CF ROOT via odin. if it does not work then i will do what u guys said. I dont know if TWRP will work by the same method (booting immediately into recovery) but philz recovery did. And i will also try flashing a prerooted Rom. What i dont understand is that why is this happening in the first place? i had an alpha before i could enter into TWRP normally i rooted it with CF AUTO root normally...no errors or anything why is this happening on my S5? the last owner must have done something weird with it ...i am trying to figure out why is this happening in the first place. Appreciate ur feedback.
I also dont know why this is happening
and yeah
i had all the galaxy S series upto S5 and this the only device that is not rooting with CF-auto root
the latest updates from samsung may have done something i dnt knw
and eralier mentioned method worked 100% for me and i did root my device like that
And last owner may b or may not done anything with it because my device is a brand new and still i had that issue
Hi,
I tried to install CWM on my rooted Note 3 N9005 with the latest 5.0 updates and the default recovery kept overwriting the custom. So I followed the advice on an article to delete the files [/system/recovery-from-boot.p] [/system/etc/install-recovery.sh] an this made my phone to fall in a loop, booting and trying to find these files then rebooting and so on...
I then had no choice but to load the stock ROM via ODIN which fixed the loop.
Is there anyway to install a custom recovery on a Note 3 running 5.0 - I want to do this in order to continue and install a custom ROM.
Thanks in advance for the answers!!
Don't use cwm as it has not been updated for a long time. Download the latest tar version of twrp for your phone.
Open Odin, uncheck everything except f.reset time, flash twrp, when you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait about 5 seconds, replace battery, use button combination to boot into recovery.
Thank you!!
What did the trick was that I quickly removed the battery and went to recovery mode. Even with "Auto Reboot" deselected the phone rebooted so if I left it it would have overwritten again the custom recovery.
Just a quick note to help others... anyone trying to flash Darklord or Phronesis ROM... USE TWRP v.2.8.0 and not the latest. The latest version for some reason won't install the ROMs.
thanx this wad so heapful .
:fingers-crossed::good:
abod7070 said:
:fingers-crossed::good:
Click to expand...
Click to collapse
Could be a year out of date and in some respects it is .
KEY is roms with AROMA installer will not work above 2.8 TWRP .
Hi Guys
I believe you guys on here will be able to help. Let me first tell you about my device and what I want to do and then what I did and what problems I encountered.
Device: Samsung Note 4 International Model SM-N910H (Exynos CPU)
OS: 6.0.1
Build Number: MMB29K.N910HXXU2DPE2
I only want to root my device and install Custom Recovery like CWM. I don't want to install a Custom ROM!
So I downloaded CF-Auto-Root-tre3g-tre3gxx-smn910h.tar.md5 and used Odin 3.12 to flash tar file to phone. After that phone rebooted and got stuck into the "Samsung Galaxy Note 4" Screen displaying in red letters on top left Corner "Recovery is not seandroid enforcing"
So I downloaded CWM Recovery v6.0.3.6.tar and flashed with Odin again, this time the phone rebooted back into my Working Phone OS and all seems fine. SO I wanted to test if CWM is installed? Powered phone down and booted into recovery & then got the same "Recovery is not seandroid enforcing" message on screen, so rebooted phone normally and it goes back into the OS. Also SuperU is not installed and phone is not rooted
So how do I solve this issue getting a Custom Recovery on my Phone Since I don't have any Recovery Mode option when booting into recovery. Your help, effort and time will be appreciated
Try again your steps and using odin both times make sure reboot is not ticked. After the flash pull the battery. There is a remark about that somewhere.
I had the same problem with my n9100 and at the end flashed custom rom to solve this. But my phone is slightly different to yours.
Thanks a mil, however I did manage to fix the issue and still wanted to resolve this post. I downloaded SuperU Beta 2.74 and different version of CWM. Installed CWM 6.0.5.1 (1113).tar with Odin 3.10.7 and it worked installing CWM Recovery. Then installed the SuperU 2.74 with CWM and everything works great. Phone now rooted and CWM installed :good::victory::victory:
******** Resolved ************
wilcovh said:
Try again your steps and using odin both times make sure reboot is not ticked. After the flash pull the battery. There is a remark about that somewhere.
I had the same problem with my n9100 and at the end flashed custom rom to solve this. But my phone is slightly different to yours.
Click to expand...
Click to collapse
I have the n9100 as well with the hong kong rom. I'm having the same problem while trying to root with cf-autoroot. I really want to root the phone while keeping the stock rom.
Is there any way to do so??
I've tried every way possible to install TWRP on Sm-N910S via odin or flashify just get stuck on boot logo upon booting. Anybody successfully flash twrp and boot please advice me how thanks
irul.monster said:
I've tried every way possible to install TWRP on Sm-N910S via odin or flashify just get stuck on boot logo upon booting. Anybody successfully flash twrp and boot please advice me how thanks
Click to expand...
Click to collapse
I have the same phone. It took me a long time to get a twrp file that worked. Also I am using a custom rom called Nemisis Refined with the Prime kernel and I love my phone. There is a different kernel you can you use too but I haven't tried it yet its called Spacelemon.
Root: http://www.theandroidsoul.com/root-galaxy-note-4-sm-n910s-using-cf-auto-root/
Recovery: Follow either of these links for TWRP:
https://forum.xda-developers.com/note-4/development/twrp-2-8-1-2-recovery-note-4-sm-n910c-t2977933
http://rootmygalaxy.net/twrp-recovery-for-galaxy-note-4-marshmallow/
ROM: https://forum.xda-developers.com/note-4/development/rom-nemesis-refined-v3-5-n7port-t3587637
when i install complety twrp n its reboot then its just reboot only it didn't show twrp recovery my android verson is 6 and mobile verson is sm-n910s korean
suraj260 said:
when i install complety twrp n its reboot then its just reboot only it didn't show twrp recovery my android verson is 6 and mobile verson is sm-n910s korean
Click to expand...
Click to collapse
find it here: https://forum.xda-developers.com/note-4/development/recovery-twrp-3-2-3-0-touch-recovery-t3836759
sm-n910s is trelteskt
thanks for the info , it helped me a lot ,
one note i need to mention , for those of you trying to flash it using odin , un-tick the auto reboot option in odin , because this will cause the phone to reboot normally , and this will remove the custom recovery ,
you just need to reboot is manually after flashing it, just remove the battery , then boot immediatelly to recovery mode by pressing power + home + volume up
if you do it correctly , custom recovery will install it self permanently on your phone ,