Related
Hi guys, new to the Android rooting community and just wanted some help figuring out what's what.
Today I bought a Samsung Galaxy S4, unlocked, I9505. It's on Android 5.0.1 (I believe that's lollipop?). Now I just wondered now that I have rooted it, what do I do now? I've rooted and done nothing else other than check my root permission which I have. I wanted to install a clean, stock Google Play Edition rom and then remove the bloatware from it and use that as my phone. How am I doing that? Do I need to have rooted a specific Android version to install roms? I was reading around about a custom recovery, do I already have that installed from root or is that another thing that I need? :crying:
Any help would be appreciated as I am super new to this having come from iPhone jailbreaking.
Thanks!
You need a custom recovery to install just about any custom rom. Custom recoveries don't from rooting, you have to flash it manually. I recommend TWRP. Just google twrp s4. They also have an installation guide. After you flashed TWRP you can flash one of the GPE roms from the forum. There are 2. One is untouched and the other has slight modifications.
GDReaper said:
You need a custom recovery to install just about any custom rom. Custom recoveries don't from rooting, you have to flash it manually. I recommend TWRP. Just google twrp s4. They also have an installation guide. After you flashed TWRP you can flash one of the GPE roms from the forum. There are 2. One is untouched and the other has slight modifications.
Click to expand...
Click to collapse
Thanks for the reply, at this moment I just need all the info I can get before I do anything! Is TWRP the best? I'm sure "which is the best recovery" is asked a lot, so I'll have a look around. Do they do different things or are the premise of them generally the same? And that's fantastic about GPE, so I won't need to upgrade any higher than 5.0.1?
Dannilad said:
Thanks for the reply, at this moment I just need all the info I can get before I do anything! Is TWRP the best? I'm sure "which is the best recovery" is asked a lot, so I'll have a look around. Do they do different things or are the premise of them generally the same? And that's fantastic about GPE, so I won't need to upgrade any higher than 5.0.1?
Click to expand...
Click to collapse
Just tried installing the JFLTE-GPE latest version using TWRP and it's not worked, I'm stuck in TWRP :/ Any help?
Did you perform a full wipe of the system, data, and cache before flashing gpe?
audit13 said:
Did you perform a full wipe of the system, data, and cache before flashing gpe?
Click to expand...
Click to collapse
Hey, I just looked around and one video I watched did not specify that I needed to wipe System. Just tried wiping System, darvik cache, cache and data so I'll see what happens and let you know if it's worked fingers crossed
EDIT: No, it hasn't worked, I've been kicked straight back into TWRP screen again Any ideas?
Dannilad said:
Hey, I just looked around and one video I watched did not specify that I needed to wipe System. Just tried wiping System, darvik cache, cache and data so I'll see what happens and let you know if it's worked fingers crossed
EDIT: No, it hasn't worked, I've been kicked straight back into TWRP screen again Any ideas?
Click to expand...
Click to collapse
bump
Normally you have to wipe data, cache, dalvik cache and system before flashing a rom. This can either be done manually or as a factory reset from within the recovery. I don't see any reason why it wouldn't boot. Try another kernel. Or you might want to try the AOSP rom by JDC team. It's basically the same as GPE, but without any of the google apps. But those can be flashed. You need to download a gapps package. The most popular seems to be from open gapps. Choose ARM, the android version of the rom and then the type of package. Pico is the smallest and will give you only the google play store.
---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------
And don't change recoveries. The others are outdated. TWRP is the only one up-to-date. You might also try another version of TWRP. The newest is 2.8.7.2 I think.
My N10 with stock 5.1 previously had root with TWRP 2.8.6, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.
Then I flashed back to TWRP 2.8.6, but the problem remains!
How to fix the problem? Thanks!
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
nitin.chobhe said:
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
Click to expand...
Click to collapse
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
mj56gt said:
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
Click to expand...
Click to collapse
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
nitin.chobhe said:
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
Click to expand...
Click to collapse
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
mj56gt said:
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
Click to expand...
Click to collapse
With nandroid, you are good to go.
Should be possible :fingers-crossed:
nitin.chobhe said:
With nandroid, you are good to go.
Should be possible :fingers-crossed:
Click to expand...
Click to collapse
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
mj56gt said:
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
Click to expand...
Click to collapse
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
mj56gt said:
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
Click to expand...
Click to collapse
May be there isn't enough space to flash them.
Happy that is working now
Sent from my Nexus 4 using XDA Free mobile app
I tried installing Lineage 14.1 last night, and cannot get past recovery screen now. Not sure what else to do, as I've formatted data and cache both to ext4, and have updated back to TWRP 3.0.3. Any help would be greatly appreciated.
I can still get adb and fastboot to recognize the phone, so that seems to be a good thing. But every time I reboot, I just see the ZTE logo, and then it boots into TWRP.
Format system as ext4 and make sure to be on twrp 3.0.3-1
Just to be sure, but did you flash the Nougat bootstack that was in the release topic?
Twiggy000b said:
Format system as ext4 and make sure to be on twrp 3.0.3-1
Click to expand...
Click to collapse
Thank you. Will I need to completely reinstall the rom and gapps again after updating TWRP? I'll have to get to a computer again and give it a shot.
P.S. Would have quoted your post in the Lineage forum, but lost my old account information and couldn't post under Development. So, out of curiousuty, how much trouble did you have with this?
xtermmin said:
Just to be sure, but did you flash the Nougat bootstack that was in the release topic?
Click to expand...
Click to collapse
I did. But am scared that I may have panicked and reinstalled it again. Hoping that won't cause any more trouble for me. Have had to revert to a backup iPhone, and am hating it. Lol.
Updating TWRP worked.
Setting the ROM up now, just had to get back to a computer and try updating recovery. Thanks for the help.
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit
Custom roms for MM modem works better.
I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..
OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?
dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..
Okay, please bear with me as i am new to this flashing custom ROM's game.
I got a intl Galaxy s4 (gti9505) a month back. After reading a lot, i flashed TWRP, and installed a custom ROM (Lineage Optimized 14.1) It runs absurdly great, and i dont think i'll need to replace this OS. BUT if i need to downgrade for whatever reason (im sure i will soft-brick the phone soon, because im testing a lot.) I have some questions:
- Some posts says i can flash back to 5.0 and upper, because the bootloader is the same (???)
- Some posts says i cant flash back to anything below my actual OS (android 7.1) (?????)
- Some posts says i cant flash STOCK ROMS because the bootloader is different. (???????)
- Could i HARD BRICK the phone, wrongly installing stuff via TWRP? or is TWRP functional "forever?''
- I did a big ass backup of android 5.0 before, when i installed TWRP. Can i reflash back to this, at any time?
I'd like to avoid any kind of brick, so help is very much appreciated. Thank you very much for helping a fellow android fan :good:
You can always flash the latest stock ROM to the phone using Odin. There is no stock ROM beyond 5.01 as far as I know.
Yes, you can hard brick the phone by flashing files through TWRP.
How did you create the 5.0 backup?
Thank you. +1 :good:
I did the backup via twrp, i think it was nandroid or something.
One last little question. What happens if i flash, say a custom ROM that is android 6.0 on TWRP right now (Doing the correct stuff and wiping what is needed). Will it Softbrick?
if yes, could you tell me why?
neru21 said:
Thank you. +1 :good:
I did the backup via twrp, i think it was nandroid or something.
One last little question. What happens if i flash, say a custom ROM that is android 6.0 on TWRP right now (Doing the correct stuff and wiping what is needed). Will it Softbrick?
if yes, could you tell me why?
Click to expand...
Click to collapse
It should not softbrick if you are flashing a custom ROM that is designed for your phone's model #.
If it does softbrick, there are two major causes: a full wipe of the data and cache partitions is required before installing the ROM or a full wipe of the phone (system, data, cache) using recovery is required before installing the custom ROM.