Flashed Resurrection Remix N [5.8.5] on my Samsung Galaxy S4 GT-i9500, and enabled root access for ADB from developer settings.
But I want total root access, so for that, I tried the way I rooted my phone when it had stock ROM, but uh oh, it didn't work. Not only that, it replaced TWRP with stock recovery.
I've searched so much and everywhere leads to Magisk root, which needs TWRP to be flashed, which needs root to be flashed. Of course, it's not that simple, but all I've tried from fastboot to Odin didn't work.
I just wanted to uninstall the bloatware and look where I am now. Could anyone help please? Thanks in advance.
Samsung devices do not recognize fastboot. Never have, and never will. You need to download the latest version of TWRP, in .tar format, from here and flash that in the AP slot in Odin. Then you'll have TWRP and can flash Magisk.
Strephon Alkhalikoi said:
Samsung devices do not recognize fastboot. Never have, and never will. You need to download the latest version of TWRP, in .tar format, from here and flash that in the AP slot in Odin. Then you'll have TWRP and can flash Magisk.
Click to expand...
Click to collapse
Hello
I asked elsewhere. I wanted to ask you too. Is it possible to temporarily install twrp? I do not intend to install custom roms.
TheSecondOne said:
Hello
I asked elsewhere. I wanted to ask you too. Is it possible to temporarily install twrp? I do not intend to install custom roms.
Click to expand...
Click to collapse
For most devices you can connect the device to your computer, open a command prompt on the computer, type "fastboot boot filename.img", and have the device temporarily run TWRP. But this doesn't work with Samsung because Samsung doesn't accept fastboot commands. On Samsung you have to install TWRP using Odin to do what you need.
Strephon Alkhalikoi said:
For most devices you can connect the device to your computer, open a command prompt on the computer, type "fastboot boot filename.img", and have the device temporarily run TWRP. But this doesn't work with Samsung because Samsung doesn't accept fastboot commands. On Samsung you have to install TWRP using Odin to do what you need.
Click to expand...
Click to collapse
I understand. I've read a lot on the subject since yesterday. Thank you for your answer. If you have knowledge, can you tell if Magisk Hide s4 works with Stock Rom?
TheSecondOne said:
I understand. I've read a lot on the subject since yesterday. Thank you for your answer. If you have knowledge, can you tell if Magisk Hide s4 works with Stock Rom?
Click to expand...
Click to collapse
I haven't been on a stock ROM in years, as the stock ROMs are so bloated on the S4 they slow the entire device down. Even debloating doesn't fully help. You'll have to try it for yourself and see if it works.
Related
I posted here this past Sunday and got a response. However, I haven't been able to find my recent post since then. Was it deleted by accident? What's up, I just don't know...
Here it is again:
So my gf has an s5 that she kept from Verizon as she switched over to T-Mobile. It has an egregious amount of bloatware on it, but everything works fine: from radio to data, from calling to you name it. Thing is, she can't download anymore apps onto it and the "apps to SD" method provided by the Verizon stock ROM only does so much justice (limitations indeed).
I took it upon myself to attempt rooting the device with no avail. An SM-900V towards a custom TMO ROM, but how?
I tried towelroot, KingMethod, Odin, etc... no luck.
Before I go even further and risk creating a paperweight in the process, could anyone give me more insight into the best and/or successful method into rooting. :good: cheers.
(and thank you to that unknown person for spitballing me an idea... I tried... but the device failed over Odin)
Install twrp for klte with Odin. Twrp will root the phone. The first time you boot into restore mode, and then Reboot system it will ask you if you would like to install Su. Just click yes, and you are rooted
ddjr said:
Install twrp for klte with Odin. Twrp will root the phone. The first time you boot into restore mode, and then Reboot system it will ask you if you would like to install Su. Just click yes, and you are rooted
Click to expand...
Click to collapse
Wait, really? There's not need to unlock anything else, or flash/load something else? I mean, I've read that you can't unlock the bootloader and shouldn't flash a bootloader or radio, but to go straight for twrp and then a new ROM afterward? Or twrp, then boot into system? or download then flash ROM via Odin?
So I have the latest Odin (or do I need an earlier one?). It detects the phone, but I'll try to go straight to TWRP tonight and see how it goes. :fingers-crossed: :fingers-crossed:
Going to use the latest TWRP from here :highfive:
I'll let you know how it goes.
Thank you for replying, btw I'll click the button :victory:
Good luck!
Hi
I am new to the OnePlus 2. When I bought it, stock 5.1.1 installed, I downloaded and installed the latest Marshmallow stock build via an OTA update. I then followed the official OnePlus video guide on unlocking the bootloader and rooting the device. I successfully unlocked the bootloader, flashed TWRP and then went on to flash SuperSU. Unfortunately, then device did not reboot - and I was soft-bricked, stuck on the boot animation. I am not sure what went wrong here.
In order to un-brick and recover my device, I downloaded the latest Marshmallow OxygenOS 3.0.2 zip from OnePlus. I was able to get this onto my device and I flashed it successfully in TWRP, and all is well.
My questions are:
1) Having flashed the latest stock, Marshmallow OxygenOS 3.0.2, will my bootloader still be unlocked?
2) Will I still have TWRP recovery, or stock recovery?
3) How can I successfully root?
Thank you in advance
I already forget what it is looks like when I change from stock to custom ROM.
But hey, here is the guide to help you:
1. use Fastboot command -> fastboot oem device-info
If "Device unlocked: ture" than your bootloader is unlocked. Normally, if you have not yet touch anything, oem is locked. But if you do unlock it, it will STAY unlock unless you use fastboot command line to change back to locked.
2. OP website only show is optional to use official recovery, so I think it is depend on you. Just go and check on it
3. For OnePlus Brand is easy. Just go and download SuperSU 2.74, place into your "sdcard", and flash it.
qingmui said:
I already forget what it is looks like when I change from stock to custom ROM.
But hey, here is the guide to help you:
1. use Fastboot command -> fastboot oem device-info
If "Device unlocked: ture" than your bootloader is unlocked. Normally, if you have not yet touch anything, oem is locked. But if you do unlock it, it will STAY unlock unless you use fastboot command line to change back to locked.
2. OP website only show is optional to use official recovery, so I think it is depend on you. Just go and check on it
3. For OnePlus Brand is easy. Just go and download SuperSU 2.74, place into your "sdcard", and flash it.
Click to expand...
Click to collapse
Hi - many thanks for the reply and information
Just to confirm, question 2: I flashed the latest stock from TWRP to recover from a soft brick. Would that process have flashed stock recovery also? Do I need to check this out by pressing Vol. down and Power buttons on boot?
Thanks again
pretty pixel said:
Hi - many thanks for the reply and information
Just to confirm, question 2: I flashed the latest stock from TWRP to recover from a soft brick. Would that process have flashed stock recovery also? Do I need to check this out by pressing Vol. down and Power buttons on boot?
Thanks again
Click to expand...
Click to collapse
TWRP will ask you, if you want to disable stock recovery flash, after you flash official firmware.
Rooting the newest stock firmware with the latest supersu from chainfire's website will turn your device into a bootloop.
Here you can find the right supersu for your firmware:
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Greetings LordHelmchen
LordHelmchen89 said:
TWRP will ask you, if you want to disable stock recovery flash, after you flash official firmware.
Rooting the newest stock firmware with the latest supersu from chainfire's website will turn your device into a bootloop.
Here you can find the right supersu for your firmware:
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Greetings LordHelmchen
Click to expand...
Click to collapse
Hello and thank you for sending me the information and links. Flashing the modified supersu worked and I am now rooted
Just a final question please...Before I received your reply I had flashed stock several times and tried different supersu versions. And ended up in bootloops as a result of this. Is this likely to have damaged my device in any way?
pretty pixel said:
Hello and thank you for sending me the information and links. Flashing the modified supersu worked and I am now rooted
Just a final question please...Before I received your reply I had flashed stock several times and tried different supersu versions. And ended up in bootloops as a result of this. Is this likely to have damaged my device in any way?
Click to expand...
Click to collapse
No, this will not damage your phone. I can not say too much about it, but the device shouldn't be damaged, it's a software-thing
PS: Hope my english is okay...and if I helped you, I would be very grateful if you click the Thanks-Button ...thank you
LordHelmchen89 said:
No, this will not damage your phone. I can not say too much about it, but the device shouldn't be damaged, it's a software-thing
PS: Hope my english is okay...and if I helped you, I would be very grateful if you click the Thanks-Button ...thank you
Click to expand...
Click to collapse
Thank you for the reassurance
Hi
Earlier today I was running 7.0.0. Stock No root with unlocked bootloader, all of a sudden random reboots. Until it no longer wanted to go past Google screen. Plugged into nexus root toolkit, tried flashing stock, downgrading to marshmallow, locking bootloader, unlocking again, multiple times and tries with no luck. The device now will only allow me to get into bootloader when I plug it to charge and immediately press power & -volume. I would appreciate it any help I can get in this.
Thanks
roelmmata said:
Hi
Earlier today I was running 7.0.0. Stock No root with unlocked bootloader, all of a sudden random reboots. Until it no longer wanted to go past Google screen. Plugged into nexus root toolkit, tried flashing stock, downgrading to marshmallow, locking bootloader, unlocking again, multiple times and tries with no luck. The device now will only allow me to get into bootloader when I plug it to charge and immediately press power & -volume. I would appreciate it any help I can get in this.
Thanks
Click to expand...
Click to collapse
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Fe Mike said:
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Click to expand...
Click to collapse
I had tried to flash twrp but had gotten an error saying I wasn't in adb recovery and never got that to work.
roelmmata said:
I had tried to flash twrp but had gotten an error saying I wasn't in adb recovery and never got that to work.
Click to expand...
Click to collapse
You mean flash to install TWRP or you were trying to install via ADB and your phone wasn't in recovery? You flash the TWRP image to install it from your bootloader via fastboot commands. You can load other files onto your phone via ADB sideload while in recovery. It is helpful to be clear on the forums so people can better help.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You mean flash to install TWRP or you were trying to install via ADB and your phone wasn't in recovery? You flash the TWRP image to install it from your bootloader via fastboot commands. You can load other files onto your phone via ADB sideload while in recovery. It is helpful to be clear on the forums so people can better help.
Click to expand...
Click to collapse
I had been trying to install twrp onto my phone through the toolkit, using the "root and install custom recovery option" but then it got the error and cancelled.
roelmmata said:
I had been trying to install twrp onto my phone through the toolkit, using the "root and install custom recovery option" but then it got the error and cancelled.
Click to expand...
Click to collapse
Again, without knowing what you have/haven't done in advance, it's hard to be of much help. To run ADB commands, you need to have USB debugging enabled on the device from settings. So, if you haven't done that, you can't do anything via ADB/fastboot and prior to that, I see you said you did have an unlocked bootloader.
Beyond those two things, which are reiterated within it, I'd strongly recommend following Heisenberg's guide at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 to do any flashing on your phone. This begins by ensuring you get a working version of the drivers installed to your machine via the Android SDK. Since your BL is unlocked, you should be able to flash TWRP via fastboot command. Also, ensure you are installing version 3.0.2-3, the latest 'unofficial' that is bug-free.
Fe Mike said:
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Click to expand...
Click to collapse
Thanks I try it out!
ultyrunner said:
Again, without knowing what you have/haven't done in advance, it's hard to be of much help. To run ADB commands, you need to have USB debugging enabled on the device from settings. So, if you haven't done that, you can't do anything via ADB/fastboot and prior to that, I see you said you did have an unlocked bootloader.
Beyond those two things, which are reiterated within it, I'd strongly recommend following Heisenberg's guide at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 to do any flashing on your phone. This begins by ensuring you get a working version of the drivers installed to your machine via the Android SDK. Since your BL is unlocked, you should be able to flash TWRP via fastboot command. Also, ensure you are installing version 3.0.2-3, the latest 'unofficial' that is bug-free.
Click to expand...
Click to collapse
Hey again
I used guide specifically to go back to stock, combined with a couple times of wiping in stock recovery I finally got the phone to boot up! However I've learned something new, the phone will only stay on if I'm plugged into charger, and as soon as it's unplugged it turns off. Any other suggestions?
I did factory reset my Moto G5 Plus, and now I am left with custom ROMs only. Where can I download the stock Motorola ROM for the Moto G5 Plus?
mstoic said:
I did factory reset my Moto G5 Plus, and now I am left with custom ROMs only. Where can I download the stock Motorola ROM for the Moto G5 Plus?
Click to expand...
Click to collapse
Check here: https://mirrors.lolinet.com/firmware/moto/potter/official/
Anyways you should always make backups in twrp :good:
tywinlannister7 said:
Check here: https://mirrors.lolinet.com/firmware/moto/potter/official/
Anyways you should always make backups in twrp :good:
Click to expand...
Click to collapse
Thanks a ton. I will surely backup everything right after installing TWRP from now on.
I'm on stock ROM NPN25.137-15, rooted with TWRP installed. Can I just upgrade it to NPN25.137-35 by downloading the zip from above link and flash it under TWRP?
anoop.ch said:
I'm on stock ROM NPN25.137-15, rooted with TWRP installed. Can I just upgrade it to NPN25.137-35 by downloading the zip from above link and flash it under TWRP?
Click to expand...
Click to collapse
I have the same questions are the linked files flashable in TWRP? My stock backup is rooted and now I can't play Pokemon GO. Just looking for the easiest way to unroot my stock rom. Thanks!
anoop.ch said:
I'm on stock ROM NPN25.137-15, rooted with TWRP installed. Can I just upgrade it to NPN25.137-35 by downloading the zip from above link and flash it under TWRP?
Click to expand...
Click to collapse
No Stock ROM can not be flashed via twrp, only the OTA zips can be flashed via stock Recovery. This is the link to the fastboot ROM.
emoney1219 said:
I have the same questions are the linked files flashable in TWRP? My stock backup is rooted and now I can't play Pokemon GO. Just looking for the easiest way to unroot my stock rom. Thanks!
Click to expand...
Click to collapse
As I mentioned above. Moreover you can flash UnSU and then root using Magisk. Magisk allows hiding root detection for Safetynet.
tywinlannister7 said:
No Stock ROM can not be flashed via twrp, only the OTA zips can be flashed via stock Recovery. This is the link to the fastboot ROM.
As I mentioned above. Moreover you can flash UnSU and then root using Magisk. Magisk allows hiding root detection for Safetynet.
Click to expand...
Click to collapse
Where would I find UnSU if you don't mind my asking?
emoney1219 said:
Where would I find UnSU if you don't mind my asking?
Click to expand...
Click to collapse
Everything is on xda. just search before posting
https://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
tywinlannister7 said:
Everything is on xda. just search before posting
https://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893
Click to expand...
Click to collapse
Never knew UnSU existed, thanks for the link. It seems to have worked, thanks.
Can't lock the bootloader
mstoic said:
Thanks a ton. I will surely backup everything right after installing TWRP from now on.
Click to expand...
Click to collapse
Hi. I am not able to lock the bootloader. As soon I enter the command
Code:
fastboot oem lock
CMD gives me the error "Still require signed boot.img"
tywinlannister7 said:
Check here: https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
Hi,
Where is the stock firmware for the EU version? Moto G5 Plus XT1685 3/32GB
tywinlannister7 said:
Check here: https://mirrors.lolinet.com/firmware/moto/potter/official/
Anyways you should always make backups in twrp :good:
Click to expand...
Click to collapse
Hi, i downloaded the zip file, but how do i install it? Can you point me to a tutorial or something?
Thank you
Hi, i followed this = https://forum.xda-developers.com/showpost.php?p=67031808&postcount=4
Got it
Thanks
pablofior said:
Hi, i downloaded the zip file, but how do i install it? Can you point me to a tutorial or something?
Thank you
Click to expand...
Click to collapse
Assuming that you have set up adb/fastboot drivers, extract all the rom files to that folder and type in the commands mentioned here :
https://pastebin.com/ZWTaWuyr
tywinlannister7 said:
Assuming that you have set up adb/fastboot drivers, extract all the rom files to that folder and type in the commands mentioned here :
https://pastebin.com/ZWTaWuyr
Click to expand...
Click to collapse
Thank you but i found here on XDA a tutorial to flash stock rom on G4 and it worked for me.
mstoic said:
Hi. I am not able to lock the bootloader. As soon I enter the command
Code:
fastboot oem lock
CMD gives me the error "Still require signed boot.img"
Click to expand...
Click to collapse
I have the same issue.
I also get these errors:
http://imgur.com/a/mRKEz
Is there a way to relock the bootloader?
tywinlannister7 said:
Assuming that you have set up adb/fastboot drivers, extract all the rom files to that folder and type in the commands mentioned here :
https://pastebin.com/ZWTaWuyr
Click to expand...
Click to collapse
I unlocked the bootlader and rooted the phone before giving it to my wife. During that whole process, fastboot had no problems recognizing the phone (obviously). Then my wife tried to update via the OTA which got her stuck in TWRP. I'd like to reflash the stock ROM, but the problem I have is I can't use fastboot to do commands line by line (as shown in the link above) since "fastboot devices" doesn't show my phone anymore. I was able to get her going on a custom ROM for now, but I'd like to put her back on the stock ROM so we won't encounter this problem again. I've reinstalled the Motorola driver several times, but no luck. ADB has no problems recognizing the phone when in recovery. One thing that happened recently was a big update to Windows 10, but I'm not sure if that is the reason for my fastboot issues.
I intend to give it a go on another computer once I get the phone again from the wife, but any advice until then would be appreciated.
Thanks. I've installed a custom ROM but im not happy with the results (specially the poor camera performace). Will this "undo" everything? I mean, stock apps, stock widgets, etc etc? (don't care if the bootloader stays unlocked and the warning moto message while booting). I know this may be a stupid question, but like Homer would say: "it's my first day"
manos78 said:
Hi,
Where is the stock firmware for the EU version? Moto G5 Plus XT1685 3/32GB
Click to expand...
Click to collapse
Did u find it?
WiteFlash said:
I intend to give it a go on another computer once I get the phone again from the wife, but any advice until then would be appreciated.
Click to expand...
Click to collapse
Just a follow up to my previous post, I tried uninstalling/reinstalling the Motorola driver and ADB on the original computer, but for some reason it still won't "see" the phone in fastboot. I was able to install ADB/Fastboot and the Motorola driver on a separate computer (also Windows 10) to get fastboot to recognize the phone so I could issue commands to reinstall the stock firmware. I noticed, though, that the following commands FAILED when I entered them:
fastboot erase customize
fastboot erase clogo
I'm not sure what those were for, but the phone seems to be working fine on the stock firmware now.
I flashed the one in the retail folder and it says ret-EU in the settings so flash that one
hello guys,
is there any custom frimeware for the galaxy grand prime sm-g532f ? i looked everywhere but can't find one.
i need one because there is no more space in my phone, the system took almost everything, 6.5go of the 8 availble, so i can't install big apps even with an sd card ! any solution ?
i was about to install a stock rom, but someone told me that it will take the same space as my current rom .
thank you.
I don't think any developer is interested in this device, it could be due to non-availability of unlocked bootloader, firmware sources, etc. I am thinking of getting rid of mine and move to another device that supports open hardware/software.
In possible solution if you managed to root it the use system app remover to get rid of Samsung bloat.
Good luck.
sga-pingo said:
I don't think any developer is interested in this device, it could be due to non-availability of unlocked bootloader, firmware sources, etc. I am thinking of getting rid of mine and move to another device that supports open hardware/software.
In possible solution if you managed to root it the use system app remover to get rid of Samsung bloat.
Good luck.
Click to expand...
Click to collapse
yes i have the same thought there will be no custom rom did you tried to install a stock rom ?
did you tried to install a stock rom ?
Click to expand...
Click to collapse
All phones when you unbox are on factory ROM (aka stock ROM). I think you are referring to rooting and installing custom recovery, I failed and phone always go into boot-loop making me to re-flash stock boot and recovery images.
sga-pingo said:
All phones when you unbox are on factory ROM (aka stock ROM). I think you are referring to rooting and installing custom recovery, I failed and phone always go into boot-loop making me to re-flash stock boot and recovery images.
Click to expand...
Click to collapse
thanks, i think i will try to root my phone, maybe it will work for me. my last hope :/
Please post your results, I am hopeless with this severely bloated device.
Update:
Managed to root using TWRP.
1. Install TWRP recovery.img using ODIN (Windows) or Heimdall (Linux) including SU. Details in this thread:
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j2-t3616589
Reboot to TWRP > format Data partition > while you are connected to PC > copy SU.zip to data and flash it.
2. Get SU.zip from here;
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
Good luck.
sga-pingo said:
Update:
Managed to root using TWRP.
1. Install TWRP recovery.img using ODIN (Windows) or Heimdall (Linux) including SU. Details in this thread:
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j2-t3616589
Reboot to TWRP > format Data partition > while you are connected to PC > copy SU.zip to data and flash it.
2. Get SU.zip from here;
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
Good luck.
Click to expand...
Click to collapse
i didn't have a lot of time these days to search for a working "rooting methode", so thank you very much.