Related
Hi,
First, I'd like to thank everyone (names unknown) for their time and effort in helping me root my first few cellphones. I've found many helpful posts over the years. Never had a problem.
Now, I have rooted my Sprint Galaxy S4 and installed a custom recovery MDC build. I then installed the OTA update to MF9 which knowingly destroyed root. I have tried several methods to install the custom recovery and root for MF9. When I run Root Checker, it tells me that it may take a little time because the system appears to be running slow. When I use Root Explorer, it won't let me change from r/o to r/w. To me, this means it isn't rooted.
What I am looking for is either a response explaining how to install a working custom recovery and root to my phone or a link to the best method.
Is there an Odin One-click?
I'm having difficulties following this thread:
http://forum.xda-developers.com/showthread.php?t=2277480
I don't want a custom rom just yet.
Any help would be greatly appreciated.
Jose
ps If I'm not clear in my description, please ask me what I might have meant.
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Just use cf auto root in Odin, then use Odin to flash your recovery. The thread is in one of the dev sections. Can't link it just now but it should be easy to find.
SGS4 Sent
peruvianrock said:
Hi,
First, I'd like to thank everyone (names unknown) for their time and effort in helping me root my first few cellphones. I've found many helpful posts over the years. Never had a problem.
Now, I have rooted my Sprint Galaxy S4 and installed a custom recovery MDC build. I then installed the OTA update to MF9 which knowingly destroyed root. I have tried several methods to install the custom recovery and root for MF9. When I run Root Checker, it tells me that it may take a little time because the system appears to be running slow. When I use Root Explorer, it won't let me change from r/o to r/w. To me, this means it isn't rooted.
What I am looking for is either a response explaining how to install a working custom recovery and root to my phone or a link to the best method.
Is there an Odin One-click?
I'm having difficulties following this thread:
http://forum.xda-developers.com/showthread.php?t=2277480
I don't want a custom rom just yet.
Any help would be greatly appreciated.
Jose
ps If I'm not clear in my description, please ask me what I might have meant.
Click to expand...
Click to collapse
First, I am by no means a Mod... but just as a little tip they will tell you questions belong in the question section and move it there where it will get buried. You better off posting future questions there where people often help if they can.
Ok onto your thread.
If you check out these two sections in the thread you linked they should help you. You will want to do the Custom Recovery Flash first then install Chainfire's SuperSU
CUSTOM RECOVERY FLASH
Recovery TWRP. Download this.
DL LINK http://techerrata.com/file/twrp2/jfl...0-jfltespr.tar
About TWRP http://www.teamw.in/project/twrp2
With USB cable NOT connected, turn off your device. Now boot into download mode. (Hold volume down then power...HOLD and WAIT... then volume up to accept message) Now connect USB cable.
Put the TWRP recovery .tar in the same folder on your computer that the Odin execution app is. Right click Odin.exe and click run as administrator. Flash TWRP using PDA mode with auto reboot UNCHECKED. Hit start. When you see RESET or PASS, move on.
Unplug USB cable. Next hold down VOL UP and the POWER button until the device turns off. Keep pressing VOL UP and let go of POWER. When you see the blue "recovery booting" let go of VOL UP. You will then boot into your new recovery. This should work if done correctly. Resore your Data back up if necessary and reboot. It SHOULD realize you are not Rooted and ask you if you want to Root. Select to Root (or not) and your done!
HOW TO ROOT STOCK MF9
You can either Odin flash CFAutoRoot from here:
http://forum.xda-developers.com/show....php?t=2291827
Check here for How To video:
http://forum.xda-developers.com/show....php?t=2257101
OR Custom Recovery Flash UPDATE-SuperSU-v1.41.zip from here:
http://forum.xda-developers.com/show....php?t=1538053
Flash UPDATE-SuperSU-v1.41.zip in TWRP or CWM to gain the latest and greatest Root for your S4 from Chainfire!
You should now be rooted with MF9 for the Software version, Baseband version (modem) and Build number.
I am not an expert by any means but I have been through all of this after having my new GS4 for about a week. I, however, updated to MF9 first before doing any rooting or installing any recoveries so I don't know if that would make a difference or not. I first installed Odin 1.85 then downloaded the correct CF Auto Root tar.md5 file and installed that with Odin. It took seconds and worked perfectly. After that I installed Philz Touch CWM-based recovery also with Odin and everything seems to be working like a charm. See below
CF Auto Root http://forum.xda-developers.com/showthread.php?t=1980683
PhilZ Touch http://forum.xda-developers.com/showthread.php?t=2322679
peruvianrock said:
Hi,
First, I'd like to thank everyone (names unknown) for their time and effort in helping me root my first few cellphones. I've found many helpful posts over the years. Never had a problem.
Now, I have rooted my Sprint Galaxy S4 and installed a custom recovery MDC build. I then installed the OTA update to MF9 which knowingly destroyed root. I have tried several methods to install the custom recovery and root for MF9. When I run Root Checker, it tells me that it may take a little time because the system appears to be running slow. When I use Root Explorer, it won't let me change from r/o to r/w. To me, this means it isn't rooted.
What I am looking for is either a response explaining how to install a working custom recovery and root to my phone or a link to the best method.
Is there an Odin One-click?
I'm having difficulties following this thread:
http://forum.xda-developers.com/showthread.php?t=2277480
I don't want a custom rom just yet.
Any help would be greatly appreciated.
Jose
ps If I'm not clear in my description, please ask me what I might have meant.
Click to expand...
Click to collapse
This is the easiest method to root I have ever seen.
http://forum.xda-developers.com/showthread.php?t=2257101
Thank you everyone for your help.
I am finally rooted.
I went back to an older stock rom. Then I followed the link in my original post.
Everything went smoothly.
But, Triangle Away doesn't work anymore.
I get the following message:
Could not locate hidden partition or could not detect device model. Are you running Android 4.0 or newer, and are you rooted, and is your device supported?
I uninstalled and reinstalled Triangle Away. Opened it again and got the same message.
I'll search the forums to see if there's an answer.
But once again, thank you for your help and encouragement. Just wish that I had more time to tinker with custom roms!
Additionally, I didn't lose any data throughout the whole process.
The phone is the Huawei Nexus 6P (MMB29M). No clue how this happened, but I managed to get root (working fine I can run apps that require root), but TWRP isn't on my phone. When I try to boot to recovery, it gives me the dead android symbol (dead android with front flap opened up and little red exclamation point). I can get into the boot loader just fine though, it's ONLY the recovery that is missing. Is it okay to use the TWRP app to install recovery the easy way? I have the TWRP app on my phone from the (failed) TWRP install, I guess. Or do I need to go through the whole root/recovery fastboot process again?
I don't know how I even got root without recovery, tbh. I was obviously in TWRP when I flashed superSU and busybox, but for whatever reason, it didn't stick. The only thing I can think of is that the phone took the liberty of replacing the recovery on its own when I restarted the phone (I didn't think to go back into recovery immediately, so the phone overwrote it...is that possible?)
The reason I'm asking about the TWRP app is because it has a very specific directory that it says it needs to install into and if that directory is wrong, the phone could be bricked. I've had the phone for less than a week, I'd prefer not to brick it. This is my 5th android device and I've never run into this issue before...in fact, I didn't even know it was POSSIBLE to get root without recovery. I did get a soft-brick earlier in the process, but I fixed it by re-flashing the stock android ROM (I also had to go change my pants afterward, but that's a story for another thread).
Thanks in advance for any assistance you can provide and have a nice Friday.
baronmax said:
The phone is the Huawei Nexus 6P (MMB29M). No clue how this happened, but I managed to get root (working fine I can run apps that require root), but TWRP isn't on my phone. When I try to boot to recovery, it gives me the dead android symbol (dead android with front flap opened up and little red exclamation point). I can get into the boot loader just fine though, it's ONLY the recovery that is missing. Is it okay to use the TWRP app to install recovery the easy way? I have the TWRP app on my phone from the (failed) TWRP install, I guess. Or do I need to go through the whole root/recovery fastboot process again?
I don't know how I even got root without recovery, tbh. I was obviously in TWRP when I flashed superSU and busybox, but for whatever reason, it didn't stick. The only thing I can think of is that the phone took the liberty of replacing the recovery on its own when I restarted the phone (I didn't think to go back into recovery immediately, so the phone overwrote it...is that possible?)
The reason I'm asking about the TWRP app is because it has a very specific directory that it says it needs to install into and if that directory is wrong, the phone could be bricked. I've had the phone for less than a week, I'd prefer not to brick it. This is my 5th android device and I've never run into this issue before...in fact, I didn't even know it was POSSIBLE to get root without recovery. I did get a soft-brick earlier in the process, but I fixed it by re-flashing the stock android ROM (I also had to go change my pants afterward, but that's a story for another thread).
Thanks in advance for any assistance you can provide and have a nice Friday.
Click to expand...
Click to collapse
This happened to me after the first time I installed twrp. I selected read only system after booting into twrp for the first time(they ask you if you want a read only option) and the stock rom would over write twrp with the stock recovery. Only fix for me was starting from scratch using step 11 here http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928. When you install twrp dont select the read only option and you'll be fine. Just remember not to let twrp install Su when it asks you to.
did you not read and follow the VERY detailed and specific instructions on how to do all of this, before beginning the process?
mistakes happen, and we are all here to help, but a softbrick followed by no recovery etc just seems like you tried to wing it without taking the proper time to read how to do it on your new device.
I'm sure someone will be able to give you a definite answer, but I also advise you to read @Heisenberg's guide on how to do it all on your 6P in the General section
Soulfly3 said:
did you not read and follow the VERY detailed and specific instructions on how to do all of this, before beginning the process?
mistakes happen, and we are all here to help, but a softbrick followed by no recovery etc just seems like you tried to wing it without taking the proper time to read how to do it on your new device.
I'm sure someone will be able to give you a definite answer, but I also advise you to read @Heisenberg's guide on how to do it all on your 6P in the General section
Click to expand...
Click to collapse
I read everything and my only mistake was selecting the read only option which clearly tell you that if you select read only it cant prevent the stock rom from over writing twrp with its own recovery. Mistakes happen.
can you not just install twrp again from the bootloader?
ahfu25 said:
I read everything and my only mistake was selecting the read only option which clearly tell you that if you select read only it cant prevent the stock rom from over writing twrp with its own recovery. Mistakes happen.
Click to expand...
Click to collapse
I was responding to the OP, not you.
uicnren said:
can you not just install twrp again from the bootloader?
Click to expand...
Click to collapse
Yes, but I was wondering if it was a bad idea to just let the TWRP app do it? That's what it's designed to do (that, and update TWRP). That's why I asked the question, I wasn't sure if that was a viable way to go about this or whether I just needed to re-do it from the nexus 6p "how to" that's on the site here.
Soulfly3 said:
I was responding to the OP, not you.
Click to expand...
Click to collapse
OK...have a nice day
I can't say for sure that I understand what you mean by using twrp when you don't even have it... but maybe see this post. (The bottom of that post.)
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
oh, I get what you're saying now - can you do it with the twrp app - as in an actual app. i missed that word. I think i remember Heisenburg saying that, no, you shouldn't use the app. I think it doesn't get the right twrp version. the version we need for the 6p is in beta and not available throught the app.
---------- Post added at 12:07 PM ---------- Previous post was at 11:51 AM ----------
In a previous post of mine, I quoted the explanation from TWRP of the system read-only vs read-write thing: http://forum.xda-developers.com/showpost.php?p=64707169&postcount=2143 I think you may need to mount the system read-write to get twrp to "stick". ...or you need root (according to sirxdroid)? I don't know which... I'd love to know how you get it working again!
p.s. Sorry to keep appending to my response...
Good explanations and links, I had the same issue when I decided to root. I did not choose read only during my initial flash of TWRP and could not figure out why every time I flashed TWRP, rebooted then went into recovery, I lost TWRP! After I did my due diligence and read the threads, I realized what I did wrong. I flashed back to stock, then flashed TWRP as recovery. I went into recovery via bootloader and chose read only. Then I installed the su.zip, rebooted the bootloader, then it was all good. Good luck.
I think what I did wrong is fail to wipe the caches (not sure how I missed it, but I did, originally). I'm not entirely sure why that makes any difference, but I went through the rooting process again and installed TWRP, now things are working properly. I did two things differently, wiping the cache and booting directly back into recovery after installing recovery. I saw on the TWRP website that some ROMs will overwrite the boot.img and recovery sections if you don't boot back into recovery immediately (it doesn't overwrite them after the second time, for whatever reason). I'm not sure if this is what happened or not, but it's the one thing that actually makes SOME sense to me.
It's interesting that there's an app out there which claims to install TWRP, but people shouldn't use it, that would be a mighty handy app to have if it worked properly, no more worries and very little fuss.
Why not just fastboot flash recovery........takes 10 seconds.
I've been looking online for guides after you root your phone, what to install as in recovery loaders like TWRP (I tried installing it last night, it boot looped and said "Secure Fail: Recovery", I fixed it with a guide on here), ROMS, Xposed, etc, and I can't find a total guide on what to install first, or what you need before you install this. I'm really confused. Is there a guide anyone knows that could help me? I don't make much money so I saved up for 3 months to buy this Note 3 and I don't want to hard brick it or anything. Thanks for any help you can give me.
No recovery since bootloader is locked
Sent from my SM-N900V using XDA Premium 4 mobile app
TWRP doesn't work even though there is a version that supports the VZW Note 3. I guess this must be for the DEV edition. Until 4.4.2 you could use SafeStrap which is similar to TWRP except it isn't a true recovery, it just loads before the OS and allows you to do much of the same functions as TWRP. After 4.4.4 the only option I have seen is to use FlashFire which isn't a recovery at all but an APP that runs on the OS. What FlashFire allows you to do is make and restore backups, do full wipes and flash zips such as ROMS. It works similar to SafeStrap in that once you select to do any operation that requires running outside of the OS, it reboots the phone then runs at boot before the OS loads. The drawbacks are that if you get stuck in a bootloop you have no options for fixing such as restoring backups, flashing additional zips or accessing the file system to modify files.
Hi guys, I'm tired of searching for a safe root method for my G900F, but I can't find any solution which considers my build number:
MMB29M.G900FXXU1CPEM
Although my baseband shows:
G900FXXU1CPC9
Can you guys help me to understand what I need to root my S5?
Thanks in advance for your time.
Hey Mate,
It has been so long but this should work http://forum.xda-developers.com/showthread.php?t=2696537
6Maverick6 said:
Hey Mate,
It has been so long but this should work http://forum.xda-developers.com/showthread.php?t=2696537
Click to expand...
Click to collapse
Thanks man. That thread warns about using roms which aren't exactly our model number and that seems to be my problem.
Although I have a S5 G900F (kltexx) my build ends in ...XXU1CPEM and chainfire's auto-root doesn't have it listed.
For what it's worth, sammobile lists my rom as having PDA G900FXXU1CPEM and CSC G900FTPH1CPE2
Also, chainfire's thread where we're supposed to point to new published stock roms doesn't allow me to comment, so I guess it's a dead end.
Is there anywhere where I can search?
Thanks again mate.
All the information you need is posted many times over in multiple threads here on XDA, not knowing shows you have not spent any time reading any threads at all
It is not hidden or difficult to find
*Detection* said:
All the information you need is posted many times over in multiple threads here on XDA, not knowing shows you have not spent any time reading any threads at all
It is not hidden or difficult to find
Click to expand...
Click to collapse
Thanks for your reply.
Although I also usually lecture people, in my own field of expertise, on how they shouldn't come to me with a problem without trying everything to fix it, I also try to be helpful in showing them the path that may enable them to help themselves.
Your answer does nothing for me, but thanks. I'm also aware that it shouldn't do anything for me, because of (insert jibber jabber about how these foruns are for developers and how rooting and custom roms will never be mainstream because the casual user isn't smart enough to press all the buttons in the correct sequence and developers need their time to be developing and not answering programming-illiterate people).
Anyway, if anyone else could point me, tip me, give me an innuendo in the right direction, I would be thankful. I'm not an expert, but since I've rooted my S4 (i9505) with chainfire's auto-root and loved CM12.1 and now CM13 roms, I was expecting to find a way to root my S5 (G900F) with these uncommon baseband and build numbers I've printed.
By the way: a search in xda-developers with my baseband shows 7 results, none of which concerns a rooted rom or specific method to root it. I know, because I've checked it before I bother everybody on this forum.
Thanks in advance guys.
You're welcome, and a helpful pointer to get you on your way:
I came to these forums with my G900F, and read a load of threads, after I was done reading, I knew how to root it, amazing what you can learn from an S5 forum overflowing with information about probably the most common/popular version of the S5
Hope that helps
EDIT - And ok, fair enough, I'm not a complete a$$
TWRP with ODIN > SuperSU from TWRP
*Detection* said:
You're welcome, and a helpful pointer to get you on your way:
I came to these forums with my G900F, and read a load of threads, after I was done reading, I knew how to root it, amazing what you can learn from an S5 forum overflowing with information about probably the most common/popular version of the S5
Hope that helps
EDIT - And ok, fair enough, I'm not a complete a$$
TWRP with ODIN > SuperSU from TWRP
Click to expand...
Click to collapse
Thanks man. Could you just answer me one last question? From your pointer and what I've read so far, this is what I think I understood already, could you let me know if this is by any chance a misinterpretation or am I in the correct path?
1) Since there's not an auto-root package with my baseband and build number I should resort to conventional root: installing a custom recovery, superuser and a custom rom like CM13.
2) Also, I now understand that, CF-Auto-Root would never help me to install CM13, because it just provides root access, nothing else, like CF's says.
3) Rooting with Supersu after installing a custom recovery isn't build or baseband dependent. Auto-root is, because it's basically your ROM rooted. Rooting with TWRP/SuperSu is just model dependent, so I would be fine with klte specific TWRP at https://dl.twrp.me/klte/ and a compatible SuperSu build.
My last question if you have the time, because I've searched for it and cannot find a clue: is it possible that my SIM-free G900F variant, has a locked bootloader? How can I check it?
Thanks again for your patience.
EDIT: dumb numbering.
G900F bootloader is unlocked
CF Auto root is not ROM dependant, I've been using the same version through KitKat > Lollipop, but the SuperSU included is likely fairly old, and Marshmallow requires the newer Betas 2.7x of SuperSU
Some S5s don't like CF AR and will soft brick, some do, like mine, and work fine
To root a stock ROM, you only need to flash TWRP, once you boot into TWRP which is your custom recovery, you can flash SuperSU, which is your Root
Reboot to your rooted stock ROM
CM13 is a custom ROM, which will likely already include root, if not, flash it from TWRP as normal
To flash a custom ROM you need to do so via custom recovery, TWRP is the preferred version
So basically I'd do this:
Copy SuperSU to your phone/MicroSD
Flash TWRP 3.0.2.0 (Last version that I know works fine) using ODIN 3.11.1
Boot into TWRP and flash SuperSU
Reboot into the rooted ROM
*Detection* said:
G900F bootloader is unlocked
CF Auto root is not ROM dependant, I've been using the same version through KitKat > Lollipop, but the SuperSU included is likely fairly old, and Marshmallow requires the newer Betas 2.7x of SuperSU
Some S5s don't like CF AR and will soft brick, some do, like mine, and work fine
To root a stock ROM, you only need to flash TWRP, once you boot into TWRP which is your custom recovery, you can flash SuperSU, which is your Root
Reboot to your rooted stock ROM
CM13 is a custom ROM, which will likely already include root, if not, flash it from TWRP as normal
To flash a custom ROM you need to do so via custom recovery, TWRP is the preferred version
So basically I'd do this:
Copy SuperSU to your phone/MicroSD
Flash TWRP 3.0.2.0 (Last version that I know works fine) using ODIN 3.11.1
Boot into TWRP and flash SuperSU
Reboot into the rooted ROM
Click to expand...
Click to collapse
Thank you so much man. The fact that you took the time to include the version numbers is awesome. I'll use TWRP because that's what I had in my S4 and worked really great. I believe I'll encounter small issues, but after your push I'll search for them in the forum. You're right, I was forgetting that CM13 has a built-in superuser manager. Thanks again.
The really scary part for me is the custom recovery install, because of bootloops or bricks.. but from what I've read so far I just need to be careful with checking and unchecking the right stuff in Odin and removing the battery after the green pass and before the device reboots. In some threads it's said that one should uncheck "auto-reboot", others say it should be checked, which is a bit confusing. I've seen in this thread http://forum.xda-developers.com/galaxy-s5/help/g900f-stuck-odin-mode-t3378907 that you advise to "uncheck it". Is it always the case?
Ok. This was really the last question.
Thanks again mate. You were really helpful and I'm sorry if I came across as annoying.
Works for me with it left to auto reboot, but if you end up back with stock recovery after flashing, disable auto reboot, then pull the battery
Some devices reinstall stock recovery if auto reboot is left enabled
Or to save messing about, disable auto reboot first time around, when it's finished flashing, disconnect USB and pull battery to power off, then replace battery and immediately boot into recovery and flash SuperSU
If TWRP asks if you want it to flash SuperSU/Root a second time, after you have already done it manually, say no
And with the G900F having an unlocked bootloader, don't worry too much about bricking it, worst case scenario, you have to flash a stock ROM again with ODIN, can't really brick it
*Detection* said:
Works for me with it left to auto reboot, but if you end up back with stock recovery after flashing, disable auto reboot, then pull the battery
Some devices reinstall stock recovery if auto reboot is left enabled
Or to save messing about, disable auto reboot first time around, when it's finished flashing, disconnect USB and pull battery to power off, then replace battery and immediately boot into recovery and flash SuperSU
If TWRP asks if you want it to flash SuperSU/Root a second time, after you have already done it manually, say no
And with the G900F having an unlocked bootloader, don't worry too much about bricking it, worst case scenario, you have to flash a stock ROM again with ODIN, can't really brick it
Click to expand...
Click to collapse
Hey man, just to let you know that everything went smooth like you said it would. Thanks again.
No probs, glad to hear it
lol
i was searching for a theard like this.
After 5 years i found it. I have the same baseband and build number. I have android 6.0.1.
will it still work? Im so much afraid of bricking my phone :crying:
Edit: Rooted succesfully.
Thanks a lot
As I stated in another thread, I used to do this with other phones, but it's been years and it would appear that things are now "different!" It looks like I have the Verizon locked recovery and I'm having trouble getting the phone to boot into a custom recovery. Everything I have tried so far has just been from the phone itself - I haven't plugged it into a PC. I have tried TWRP, CWM, and Safestrap. It still boots into the stock recovery. What should I do next? Was this problem fixed a long time ago?
Thanks.
With a locked bootloader, you cannot run TWRP or CWM.
I'm figuring that out. I'm in the bootloader unlocking thread now. It appears there might be an apk that works, but I have about 50 more pages to read.
If you have Verizon phone then you want that forum not this one .
That's what I got. Thanks.