After rooting your Moto G Osprey and flashing for example the wrong SU SuperUser zip or not in Systemless mode, a lot of People stuck into a Bootloop and can't get out.
You can get out of this Bootloop by pressing followings:
1. Hold Power Button down until your Phone turns of.
2. Right after it turns of, press and hold only the Volume Down Button.
You should now have access to the Bootloader again.
Einherjer* said:
After rooting your Moto G Osprey and flashing for example the wrong SU SuperUser zip or not in Systemless mode, a lot of People stuck into a Bootloop and can't get out.
You can get out of this Bootloop by pressing followings:
1. Hold Power Button down until your Phone turns of.
2. Right after it turns of, press and hold only the Volume Down Button.
You should now have access to the Bootloader again.
Click to expand...
Click to collapse
I was stuck in the bootloop and now by following your steps..I ended up in fastboot mode...I probably have installed wrong version of superSU zip...so now could u tell what should I do from the fastboot screen....pls help..
UtkKing said:
I was stuck in the bootloop and now by following your steps..I ended up in fastboot mode...I probably have installed wrong versions of supers zip...so now could u tell what should I do from the fastboot screen....pls help..
Click to expand...
Click to collapse
Flash SuperSU correctly... look in my signature for a link to the proper way to root any Moto G 2015 device.
UtkKing said:
I was stuck in the bootloop and now by following your steps..I ended up in fastboot mode...I probably have installed wrong version of superSU zip...so now could u tell what should I do from the fastboot screen....pls help..
Click to expand...
Click to collapse
Try to get into Recovery. I think you mean the Bootloader instead of "Fastboot Mode". From the Bootloader you should have access Into Recovery.
Einherjer* said:
Try to get into Recovery. I think you mean the Bootloader instead of "Fastboot Mode". From the Bootloader you should have access Into Recovery.
Click to expand...
Click to collapse
So from the recovery I should install SuperSU 2.78 by writing :
echo SYSTEMLESS=true>>/data/.supersu
In the terminal of TWRP as stated in the thread posted by acejavelin.
---------- Post added at 08:25 PM ---------- Previous post was at 08:04 PM ----------
acejavelin said:
Flash SuperSU correctly... look in my signature for a link to the proper way to root any Moto G 2015 device.
Click to expand...
Click to collapse
Acejavelin i followed ur thread and installed superSU 2.78 as u said in ur thread...i am now able to boot my device normally..thanx for that...
But i cannot see SuperSU in my app drawer..
Moreover when i installed Root Checker, it showed that my device is not rooted...why is it so??and what should i do now??
UtkKing said:
So from the recovery I should install SuperSU 2.78 by writing :
echo SYSTEMLESS=true>>/data/.supersu
In the terminal of TWRP as stated in the thread posted by acejavelin.
---------- Post added at 08:25 PM ---------- Previous post was at 08:04 PM ----------
Acejavelin i followed ur thread and installed superSU 2.78 as u said in ur thread...i am now able to boot my device normally..thanx for that...
But i cannot see SuperSU in my app drawer..
Moreover when i installed Root Checker, it showed that my device is not rooted...why is it so??and what should i do now??
Click to expand...
Click to collapse
No offense, but did you read the posting?
The echo command doesn't install anything and isn't magic, it creates a file called /data/.supersu that contains the parameter "SYSTEMLESS=true", then you install (flash) SuperSU normally. The installation script for SuperSU sees the file created with the echo command and performs a systemless install. If you look at the pictures attached to the first post, you will see how it should look when done properly.
If that fails (and only if it fails), which does in less than 1% of devices for some reason, find SuperSU 2.62-3 beta and flash it... It must be that EXACT version and it's in post #2 of my rooting method. Once it's up with this version update the app via play store then open the app and update the binary.
acejavelin said:
No offense, but did you read the posting?
The echo command doesn't install anything and isn't magic, it creates a file called /data/.supersu that contains the parameter "SYSTEMLESS=true", then you install (flash) SuperSU normally. The installation script for SuperSU sees the file created with the echo command and performs a systemless install. If you look at the pictures attached to the first post, you will see how it should look when done properly.
If that fails (and only if it fails), which does in less than 1% of devices for some reason, find SuperSU 2.62-3 beta and flash it... It must be that EXACT version and it's in post #2 of my rooting method. Once it's up with this version update the app via play store then open the app and update the binary.
Click to expand...
Click to collapse
Ok so should i flash SuperSU 2.62-3 BETA after creating the file /data/.supersu again with the same method??
---------- Post added at 09:41 PM ---------- Previous post was at 09:25 PM ----------
UtkKing said:
Ok so should i flash SuperSU 2.62-3 BETA after creating the file /data/.supersu again with the same method??
Click to expand...
Click to collapse
Thanx Acejavelin..i flashed the lower version of SuperSU and now it worked...my phone has been rooted and SuperSU has also appeared in the app drawer...thanx again...:good::good:
Btw should i update SuperSU from play store???is it safe to update?
UtkKing said:
Ok so should i flash SuperSU 2.62-3 BETA after creating the file /data/.supersu again with the same method??
---------- Post added at 09:41 PM ---------- Previous post was at 09:25 PM ----------
Thanx Acejavelin..i flashed the lower version of SuperSU and now it worked...my phone has been rooted and SuperSU has also appeared in the app drawer...thanx again...:good::good:
Btw should i update SuperSU from play store???is it safe to update?
Click to expand...
Click to collapse
It's safe, after updating the application, just open it and let it update the su binaries (normal way) automatically. Reboot and you are done.
BTW, you could have flashed the latest one as you have already done the Echo command. The chances of a failure are slim anyway.
Broadcasted from Zeta Reticuli
Related
I am running cwm on Verizon and I am trying to install aospa(4.4) on my phone. I have to use twrp and every time I try to install twrp, it fails and I am left with a nonworking recovery. How do I install the latest version of twrp?
Sent from my LG-VS980
oadam11 said:
I am running cwm on Verizon and I am trying to install aospa(4.4) on my phone. I have to use twrp and every time I try to install twrp, it fails and I am left with a nonworking recovery. How do I install the latest version of twrp?
Sent from my LG-VS980
Click to expand...
Click to collapse
Try flashing with the app provided below, will do either a zip or a img file. Just make sure your new Recovery file has been Loki'd.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Jimi Mack said:
Try flashing with the app provided below, will do either a zip or a img file. Just make sure your new Recovery file has been Loki'd.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
How do I make it loki'd?
Sent from my LG-VS980
oadam11 said:
How do I make it loki'd?
Sent from my LG-VS980
Click to expand...
Click to collapse
The Recovery imagine you downloaded should already be Loki'd. Verify this from the location or forum you got it from.
Yeah Help
Ok totally dont get this, first i've rooted the thing, but cant seem to get into twrp. I installed it using flashify, I reboot goto the factory reset screen, hit power 3 times and black screen. I just want to flash a rom my galaxy s2 was so EASY
timenewton said:
Ok totally dont get this, first i've rooted the thing, but cant seem to get into twrp. I installed it using flashify, I reboot goto the factory reset screen, hit power 3 times and black screen. I just want to flash a rom my galaxy s2 was so EASY
Click to expand...
Click to collapse
Make sure the recovery you flashed with flashify was a zip or img, make sure it was for your phones model, make sure its loki'd, or download Quickboot from the play store and tap recovery.
Sent from my LG-D800 using xda app-developers app
I cant get adb to work just keeps saying looking for device, I installed the LG drivers, checked debugging, goto pc connection, ethernet. The recovery I have is an img from http://forum.xda-developers.com/showthread.php?t=2449670 for verizon.
---------- Post added at 06:57 AM ---------- Previous post was at 06:13 AM ----------
Ok I got adb to work I get to ./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.3-g2vzw.img then it says cant execute: permission denied
timenewton said:
I cant get adb to work just keeps saying looking for device, I installed the LG drivers, checked debugging, goto pc connection, ethernet. The recovery I have is an img from http://forum.xda-developers.com/showthread.php?t=2449670 for verizon.
---------- Post added at 06:57 AM ---------- Previous post was at 06:13 AM ----------
Ok I got adb to work I get to ./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.3-g2vzw.img then it says cant execute: permission denied
Click to expand...
Click to collapse
Hey 2.6.3.3 is a flashable zip from twrp....from their site try flashify app from playstore too easy as click and boot to recovery
Solved
Ok 2.6.3.2 will install, so install that first then 2.6.3.3 as an image
timenewton said:
Ok 2.6.3.2 will install, so install that first then 2.6.3.3 as an image
Click to expand...
Click to collapse
If you've got 3.2 installed already, if 3.3 is a zip, you should just be able to flash it. :good:
everything went fine until i typed adb reboot recovery
followed the guides on here to flash TWRP, finally got everything flashed through adb and when i went to the final step to reboot in to recovery it said "error : device not found" .... Is this normal? should i just unplug/replug and try the reboot bootloader command again? It said the image was loki verified and flashed succesfully, but when i typed in reboot recovery it said "error: device not found" any advice/help is much appreciated
Hi, forgive me if this is a stupid question but after flashing the latest t0lte nightly I have lost root access.
How has this happened?
I've been flashing CM nightlies for weeks but fancied a change after reading up about omnirom.
Im running an international note 2 LTE using cwm, rooted with Odin.
How do I get root access back? Is it case of me having to flash via Odin again?
More than grateful for any help here!
Cheers
cbryant said:
Hi, forgive me if this is a stupid question but after flashing the latest t0lte nightly I have lost root access.
How has this happened?
I've been flashing CM nightlies for weeks but fancied a change after reading up about omnirom.
Im running an international note 2 LTE using cwm, rooted with Odin.
How do I get root access back? Is it case of me having to flash via Odin again?
More than grateful for any help here!
Cheers
Click to expand...
Click to collapse
Flash SuperSU in recovery
We haven't yet integrated SuperSU into the package itself, and fixing that has been low priority since:
1) You can't flash Omni without a custom recovery
2) If you have a custom recovery that can flash Omni, you can flash SuperSU in recovery
3) Once you've flashed SuperSU, you can go to its Settings->Custom ROM and enable the backup script
Entropy512 said:
Flash SuperSU in recovery
We haven't yet integrated SuperSU into the package itself, and fixing that has been low priority since:
1) You can't flash Omni without a custom recovery
2) If you have a custom recovery that can flash Omni, you can flash SuperSU in recovery
3) Once you've flashed SuperSU, you can go to its Settings->Custom ROM and enable the backup script
Click to expand...
Click to collapse
Ah makes sense! is the latest superSU.zip listed on XDA? I can't locate it.
Thanks for your help!!!:good:
---------- Post added at 09:57 PM ---------- Previous post was at 09:20 PM ----------
Ok, i've pulled the superSU zip from chainfire and flashed it, however it is giving me a error message.
"There is no SU binary installed and superuser cannot install it. This is a problem!"
So I am unable to run step 3
Please help :crying:
Cheers again :good:
craigbryant said:
Ah makes sense! is the latest superSU.zip listed on XDA? I can't locate it.
Thanks for your help!!!:good:
---------- Post added at 09:57 PM ---------- Previous post was at 09:20 PM ----------
Ok, i've pulled the superSU zip from chainfire and flashed it, however it is giving me a error message.
"There is no SU binary installed and superuser cannot install it. This is a problem!"
So I am unable to run step 3
Please help :crying:
Cheers again :good:
Click to expand...
Click to collapse
That's strange - 1.80 works perfectly for me.
craigbryant said:
Ah makes sense! is the latest superSU.zip listed on XDA? I can't locate it.
Thanks for your help!!!:good:
---------- Post added at 09:57 PM ---------- Previous post was at 09:20 PM ----------
Ok, i've pulled the superSU zip from chainfire and flashed it, however it is giving me a error message.
"There is no SU binary installed and superuser cannot install it. This is a problem!"
So I am unable to run step 3
Please help :crying:
Cheers again :good:
Click to expand...
Click to collapse
Yesssssss.
Ok I got there in the end, grabbed Chainfire's latest SU from his G+ page (ver1.80)
Flashed this version and it allowed me to access settings and in turn run the backup script
Thank you so much for your help, much appreciated
I came right thankyou!
Sent from my GT-I9295 using XDA Premium 4 mobile app
As discovered in the Q&A post found here: http://forum.xda-developers.com/moto-x-2014/help/root-t2886674/page2
Just like the first Moto X, users have been having success rooting by unlocking the bootloader and just flashing SuperSU with CWM. This is a test release so it may be wise just just boot to CWM to flash SuperSU instead of flash it. Use caution as always.
Bootloader Unlock Guide: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
CWM Test 8: http://d-h.st/XJr
SuperSU flashable ZIP: http://forum.xda-developers.com/showthread.php?t=1538053
I can report that this did work for me and I have achieved root.
Steps I took:
1. Unlock bootloader using Motorola's website
2. boot to bootloader, flash or boot to recovery with fastboot command (fastboot flash recovery cwm.img/fastboot boot cwm.img) *There really isn't a reason to flash this. It is very broken. Consider keeping your original recovery!*
3. boot to cwm and flash superSU zip
4. CWM will prompt to fix root, choose YES
5. Rooted!
Almost everything besides flashing a zip is broken in this CWM release, don't expect to be able to backup with it.
Vultorus said:
This hasn't been posted yet, so I'm just sharing what was found in the Q&A post found here: http://forum.xda-developers.com/moto-x-2014/help/root-t2886674/page2
Users have been having success rooting by unlocking the bootloader and just flashing SuperSU with CWM. This is a test release so it may be wise just just boot to CWM to flash SuperSU instead of flash it. Use caution as always.
Bootloader Unlock Guide: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
CWM Test 8: http://d-h.st/XJr
I can report that this did work for me and I have achieved root.
Click to expand...
Click to collapse
I appreciate you posting this, could you by any chance post a little bit more detail on how to do the flash? Is it as simple as extracting the recovery image and flashing from ADB? How do you then flash SuperSU?
km8j said:
I appreciate you posting this, could you by any chance post a little bit more detail on how to do the flash? Is it as simple as extracting the recovery image and flashing from ADB? How do you then flash SuperSU?
Click to expand...
Click to collapse
I added some basic steps to original post, use caution as this isn't the most secure way to root but it will do for now. If you need further help, you should probably wait for a safer method.
Vultorus said:
I added some basic steps to original post, use caution as this isn't the most secure way to root but it will do for now. If you need further help, you should probably wait for a safer method.
Click to expand...
Click to collapse
What are the gaps in security? When you say secure, do you mean safe as in not bricking the phone or security as in data is at risk, etc.?
Vultorus said:
I added some basic steps to original post, use caution as this isn't the most secure way to root but it will do for now. If you need further help, you should probably wait for a safer method.
Click to expand...
Click to collapse
the steps you listed are pretty much it. can't get any easier than that. exactly how it was on the previous MotoX. unlock bootloader, fastboot flash recovery .img. then just reboot to recovery and flash SuperSU zip. very straight forward.
edit: also, fix permissions shouldn't be required...
mrvirginia said:
the steps you listed are pretty much it. can't get any easier than that. exactly how it was on the previous MotoX. unlock bootloader, fastboot flash recovery .img. then just reboot to recovery and flash SuperSU zip. very straight forward.
edit: also, fix permissions shouldn't be required...
Click to expand...
Click to collapse
It was just mentioned in the original post, I guess it doesn't matter. And by not secure I mean that the CWM is a test release so I don't know what could go wrong.
Vultorus said:
It was just mentioned in the original post, I guess it doesn't matter. And by not secure I mean that the CWM is a test release so I don't know what could go wrong.
Click to expand...
Click to collapse
yeah i'm still awaiting a device so i'm not 100% sure on the persmissions. the zip should do all the work for the user, though, via the update-binary.
btw thanks for posting.
Thanks for posting this, I suggested the guys in Q&A to do that. If anybody needs help, I made the process successfully back on Q&A (when they were testing the recovery)
If anyone notices the permissions making a difference let me know, I'm curious as to why everyone was saying it had to be done..
"cannot load 'recovery': Permission denied" when trying "fastboot boot recovery cmw.img"
My bootloader is unlocked.
---------- Post added at 08:56 PM ---------- Previous post was at 08:37 PM ----------
rogeriorc said:
"cannot load 'recovery': Permission denied" when trying "fastboot boot recovery cmw.img"
My bootloader is unlocked.
Click to expand...
Click to collapse
ops, forget about it.
the command is "fastboot boot cmw.img"
And I am rooted! :laugh:
Worked for me. I'm now rooted
2/10 needs more Verizon
rogeriorc said:
"cannot load 'recovery': Permission denied" when trying "fastboot boot recovery cmw.img"
My bootloader is unlocked.
---------- Post added at 08:56 PM ---------- Previous post was at 08:37 PM ----------
ops, forget about it.
the command is "fastboot boot cmw.img"
And I am rooted! :laugh:
Click to expand...
Click to collapse
I apologize, I did not realize if you are just booting, you don't need the "recovery" part of that command. Glad it worked for you!
You mention that this version of CWM is limited to basically sideband loading and won't do backup. Do you happen to know where I can find a copy of CWM for the X 2014 that gives me shell access? I've already unlocked and rooted my phone, but busted my screen and want to back things up. I went to their rom manager page and can't find either version of the X. Would either a 6.0.5.1 or one of the Nexus ones work?
New factory image is up.
https://developer.android.com/preview/download.html
Just put dev preview 3 back on my device, now I need to give this a go, thanks!
Encryptable boot/kernel for NPD56N:
https://www.androidfilehost.com/?fid=24572369242686514
aoaleman said:
Encryptable boot/kernel for NPD56N:
https://www.androidfilehost.com/?fid=24572369242686514
Click to expand...
Click to collapse
So I flash this instead of boot?
aoaleman said:
Encryptable boot/kernel for NPD56N:
https://www.androidfilehost.com/?fid=24572369242686514
Click to expand...
Click to collapse
Does this keep us unencrypted?
Sent from my Nexus 6
-DarkKnight- said:
So I flash this instead of boot?
Click to expand...
Click to collapse
You can if you are decrypted and don't feel like being forced to being encrypted.
---------- Post added at 12:41 PM ---------- Previous post was at 12:41 PM ----------
chopt51 said:
Does this keep us unencrypted?
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes it does. It does not touch your current setup.
aoaleman said:
You can if you are decrypted and don't feel like being forced to being encrypted.
---------- Post added at 12:41 PM ---------- Previous post was at 12:41 PM ----------
Yes it does. It does not touch your current setup.
Click to expand...
Click to collapse
Thank you! I was not sure if I wanted to bite the bullet and go encrypted or wait for an unencrypted zip, but now I dont have to choose!
Also is anyone able to root it yet?
aoaleman said:
Encryptable boot/kernel for NPD56N:
https://www.androidfilehost.com/?fid=24572369242686514
Click to expand...
Click to collapse
Thank you very much indeed. Works very well, dirty flashed np4 system.img in twrp after flashing this boot.img. all good
---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------
-DarkKnight- said:
Thank you! I was not sure if I wanted to bite the bullet and go encrypted or wait for an unencrypted zip, but now I dont have to choose!
Also is anyone able to root it yet?
Click to expand...
Click to collapse
Yes, rooted with beta su 2.74
madsurgeon said:
Thank you very much indeed. Works very well, dirty flashed np4 system.img in twrp after flashing this boot.img. all good
---------- Post added at 03:28 AM ---------- Previous post was at 03:26 AM ----------
Yes, rooted with beta su 2.74
Click to expand...
Click to collapse
I flashed su 2.74, and its forcing me into "safe mode"
This was my sequence:
1. Reboot to recovery
2. Flash above linked boot.img as boot
3. Reboot recovery
4. Flash system.img
5. Reboot recovery
6. Flash su 2.74
7. Reboot system
madsurgeon said:
This was my sequence:
1. Reboot to recovery
2. Flash above linked boot.img as boot
3. Reboot recovery
4. Flash system.img
5. Reboot recovery
6. Flash su 2.74
7. Reboot system
Click to expand...
Click to collapse
Would I be able to follow that if I was coming from MM and wanted to try preview 4 or is that only for people that were running preview 3 already?
Sent from my Nexus 6 using XDA-Developers mobile app
madsurgeon said:
This was my sequence:
1. Reboot to recovery
2. Flash above linked boot.img as boot
3. Reboot recovery
4. Flash system.img
5. Reboot recovery
6. Flash su 2.74
7. Reboot system
Click to expand...
Click to collapse
Still safe mode :/
MrMiami81 said:
Would I be able to follow that if I was coming from MM and wanted to try preview 4 or is that only for people that were running preview 3 already?
Click to expand...
Click to collapse
You'd have to be on the latest bootloader and maybe radio, then you can wipe data and system and do the above, you can't dirty flash N over M
---------- Post added at 09:48 PM ---------- Previous post was at 09:45 PM ----------
-DarkKnight- said:
Still safe mode :/
Click to expand...
Click to collapse
Try this when in safe mode: power off, reboot to recovery flash su and reboot system
Alternatively(once in recovery from safe mode)
1. Flash boot.img, reboot system then go back and flash su
Or
2. Make nandroid of data, clean flash and restore from tibu/nandroid option
I'm sorry i can't help you further mate, that's the extent of my knowledge about this
madsurgeon said:
You'd have to be on the latest bootloader and maybe radio, then you can wipe data and system and do the above, you can't dirty flash N over M
---------- Post added at 09:48 PM ---------- Previous post was at 09:45 PM ----------
Try this when in safe mode: power off, reboot to recovery flash su and reboot system
Alternatively(once in recovery from safe mode)
1. Flash boot.img, reboot system then go back and flash su
Or
2. Make nandroid of data, clean flash and restore from tibu/nandroid option
I'm sorry i can't help you further mate, that's the extent of my knowledge about this
Click to expand...
Click to collapse
Does adaway and Titanium Backup work using this method on DP4?
QuickInfo said:
Does adaway and Titanium Backup work using this method on DP4?
Click to expand...
Click to collapse
i don't use adaway, i manually push a modified hosts file into system/etc, that works and
tibu seems to restore only data(even with a clean flash), so i install the apk from tibu backup folder and then restore data from tibu
flash directly from Android Developers using adb command.
However, it has been 20 minus and I am still looking at the "Google" sign. Should I try to re-flash it over or keep waiting?
PS. it took me 40 minus+ to wipe data and cache....
madsurgeon said:
i don't use adaway, i manually push a modified hosts file into system/etc, that works and
tibu seems to restore only data(even with a clean flash), so i install the apk from tibu backup folder and then restore data from tibu
Click to expand...
Click to collapse
Titanium Backup will work once you set SELinux to permissive. I did so by using the following zips:
http://forum.xda-developers.com/showpost.php?p=66371718&postcount=7
Anyone having issues with Bluetooth connectivity? I'll be listening to much over Bluetooth and the connection will drop. A few seconds later it will reconnect and continue on.
When it does this, the Bluetooth icon also disappears from the status bar.
Happens in my car (aftermarket Kenwood) and with my insignia Bluetooth speaker.
Sent from my Nexus 6 using Tapatalk
I must be doing this wrong but I get failure every time I try it
Sent from my Nexus 6 using Tapatalk
rgraville said:
Titanium Backup will work once you set SELinux to permissive. I did so by using the following zips:
http://forum.xda-developers.com/showpost.php?p=66371718&postcount=7
Click to expand...
Click to collapse
Thanks! I've been wanting to come back to N for a while now (dumped it when DP2 sucked) but the Titanium restore issue has been keeping me away. This is good news.
Wanting to root my phone. first phone ive ever rooted but I read a lot n know the dos n donts. But I cant seem to get it to work. I keep reading once you start the root with odin its supposed to have a red anroid icon on your phone. but instead it just stays at the blue downloading screen. and it always gets stuck at recovery.img I was hoping someone could help me root it, or find a guide for my phone. I would really appreciate it. My phone model is SM-G903W, Provider is Telus, its updated to Android 7.0.
Have you managed to root your device?
No sadly.
But the phone no longer has a sim card. Got a new phone. So still wanting to root it but not sure if it can be or what to do since the isn't a provider
Adversity said:
Wanting to root my phone. first phone ive ever rooted but I read a lot n know the dos n donts. But I cant seem to get it to work. I keep reading once you start the root with odin its supposed to have a red anroid icon on your phone. but instead it just stays at the blue downloading screen. and it always gets stuck at recovery.img I was hoping someone could help me root it, or find a guide for my phone. I would really appreciate it. My phone model is SM-G903W, Provider is Telus, its updated to Android 7.0.
Click to expand...
Click to collapse
Use CF-Auto-Root
Flash in odin AP section
https://download.chainfire.eu/953/C...-Auto-Root-s5neoltecan-s5neoltevl-smg903w.zip
Or
Flash a custom rom & then flash magisk
Adversity said:
But the phone no longer has a sim card. Got a new phone. So still wanting to root it but not sure if it can be or what to do since the isn't a provider
Click to expand...
Click to collapse
Ok. I've asked the forum in another thread but no one has replied. I don't understand. We can't be the only two people who own this phone, running 7.0, who want to root the device...
I think I will roolback and flash 6.0. Looks like there is a lot of support and threads showing how to root from 6.0.
---------- Post added at 03:01 PM ---------- Previous post was at 02:59 PM ----------
Adversity said:
But the phone no longer has a sim card. Got a new phone. So still wanting to root it but not sure if it can be or what to do since the isn't a provider
Click to expand...
Click to collapse
Ok. I've asked the forum in another thread but no one has replied. I don't understand. We can't be the only two people who own this phone, running 7.0, who want to root the device...
I think I will rollback and flash 6.0. Looks like there is a lot of support and threads showing how to root from 6.0.
Iamoasis said:
Ok. I've asked the forum in another thread but no one has replied. I don't understand. We can't be the only two people who own this phone, running 7.0, who want to root the device...
I think I will roolback and flash 6.0. Looks like there is a lot of support and threads showing how to root from 6.0.
---------- Post added at 03:01 PM ---------- Previous post was at 02:59 PM ----------
Ok. I've asked the forum in another thread but no one has replied. I don't understand. We can't be the only two people who own this phone, running 7.0, who want to root the device...
I think I will rollback and flash 6.0. Looks like there is a lot of support and threads showing how to root from 6.0.
Click to expand...
Click to collapse
See my above post
Also make sure you have enabled usb debugging in dev options
Also look for enable oem unlock & if you see it enable it
And also disable verify apps by adb if you see that too
TheFixItMan said:
See my above post
Also make sure you have enabled usb debugging in dev options
Also look for enable oem unlock & if you see it enable it
And also disable verify apps by adb if you see that too
Click to expand...
Click to collapse
Ok thank you. I downloaded the cf auto root from the link you provided. I enabled debugging and oem, I disabled "verify apps by USB" not adb.
I'll give it a go...
---------- Post added at 03:21 PM ---------- Previous post was at 03:14 PM ----------
Iamoasis said:
Ok thank you. I downloaded the cf auto root from the link you provided. I enabled debugging and oem, I disabled "verify apps by USB" not adb.
I'll give it a go...
Click to expand...
Click to collapse
Well I flashed it using odin. It says "pass" in odin and took a while to boot, but I think it worked. How do I verify? Download an app? And can I flash TWRP? If so, which one?
Thank you for your help
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
Iamoasis said:
Ok thank you. I downloaded the cf auto root from the link you provided. I enabled debugging and oem, I disabled "verify apps by USB" not adb.
I'll give it a go...
---------- Post added at 03:21 PM ---------- Previous post was at 03:14 PM ----------
Well I flashed it using odin. It says "pass" in odin and took a while to boot, but I think it worked. How do I verify? Download an app? And can I flash TWRP? If so, which one?
Thank you for your help
Click to expand...
Click to collapse
I see SuperSU installed so it worked. Thank you.
Do you know which TWRP I can install now?
Iamoasis said:
Ok thank you. I downloaded the cf auto root from the link you provided. I enabled debugging and oem, I disabled "verify apps by USB" not adb.
I'll give it a go...
---------- Post added at 03:21 PM ---------- Previous post was at 03:14 PM ----------
Well I flashed it using odin. It says "pass" in odin and took a while to boot, but I think it worked. How do I verify? Download an app? And can I flash TWRP? If so, which one?
Thank you for your help
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
I see SuperSU installed so it worked. Thank you.
Do you know which TWRP I can install now?
Click to expand...
Click to collapse
I'd guess it would be the following for g903w s5 neo lte
https://dl.twrp.me/s5neolte/twrp-3.2.3-0-s5neolte.img.tar.html
Put in AP section of odin
As soon as the device restarts hold power button Vol up & home button to enter recovery
If you miss the moment to enter recovery for the first time after flashing & your phone boots you will have to reflash the image until you enter twrp for the first time
TheFixItMan said:
I'd guess it would be the following for g903w s5 neo lte
https://dl.twrp.me/s5neolte/twrp-3.2.3-0-s5neolte.img.tar.html
Put in AP section of odin
As soon as the device restarts hold power button Vol up & home button to enter recovery
If you miss the moment to enter recovery for the first time after flashing & your phone boots you will have to reflash the image until you enter twrp for the first time
Click to expand...
Click to collapse
I managed to get TWRP installed. I tried to install Lineage 15.1 as per this site:
https://www.cyanogenmods.org/forums...-for-galaxy-s5-neo-android-8-1-oreo-download/
and am now stuck in a loop. It installed successfully with no errors but will stay stuck on the Lineage loading screen then revert back to recovery.
Any ideas what may be causing this? Should I install 14.1?
Iamoasis said:
I managed to get TWRP installed. I tried to install Lineage 15.1 as per this site:
https://www.cyanogenmods.org/forums...-for-galaxy-s5-neo-android-8-1-oreo-download/
and am now stuck in a loop. It installed successfully with no errors but will stay stuck on the Lineage loading screen then revert back to recovery.
Any ideas what may be causing this? Should I install 14.1?
Click to expand...
Click to collapse
Correct process for flash rom
In twrp
Goto wipe
Advanced wipe
Wipe system data cache delvik/art cache
Install
Select rom zip
Install
Select gapps zip - use mind the gapps arm for lineage os 15. 1 http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Optional install
Select root zip (use magisk)
Wipe delvik/art cache
Restart
If you didn't follow the above that's why it would bootloop
Hi, I'm wanting to root my s5 neo on 7.0 and like you, I'm also and finding it very difficult to find a guide that has a successful ending
I'm new to all this but I did notice that you tried to install lineage 15.1 for sm-g903F but your device is sm-g903w. Could that be your problem?
Have you successfully rooted your device yet?
To be honest I don't really want root, I just want to extract or atleast view all my saved wifi network passwords from the device.