Hello.
Nice to meet your community.
I have second day my new galaxy S4.I sold my previous Iphone 4s which was jailbroked in the latest level i could,as was my 3GS before 3 years.
I decided to enter Android family and this is my first touch of serious Android phone as i am newbie here.
Searching in the internet i found that the best custom rom is OMEGA,so i entered your community to help me out.
In the subject now:
My firmware is I9505XXUBMGA.
I have download I9505_Omega_v10_XXUBMH1_md5_FF0929179DC10DB316C38969CE2AFDC0 and put in Internal memory at "Downloads" but as i see there is a different firmware XXUBMH1 from mine.
I tried to put it with VOLUME UP+HOME+POWER buttons but my CWM has not advanced settings so i pressed cache wipe and now the CWM do not open.
CWM is recovery mode as i understood,right?
What are the steps?I go to another firmware and to another CWM and then i pass OMEGA?
1st, go to developer section and read the installation instructions for Omega... You have tried to flash a custom rom with a stock recovery... NOT GONNA HAPPEN...
You need to root your phone, install a custom recovery and then flash the custom rom.
Do some reading before you brick your new toy...
Hi, welcome in the Android community !
First check the device you own, because GT-I9505 and GT-I9500 are not the same and ROM that fit the first can brick the second and vice-versa.
Then, you have to root your phone, then to install a custom recovery.
Tutorials for these two steps can be found here, Q4 and Q5 answers.
Once these two steps are successfully completed, you can then flash the OMEGA zip file in recovery mode.
ultramag69 said:
1st, go to developer section and read the installation instructions for Omega... You have tried to flash a custom rom with a stock recovery... NOT GONNA HAPPEN...
You need to root your phone, install a custom recovery and then flash the custom rom.
Do some reading before you brick your new toy...
Click to expand...
Click to collapse
XS_31 said:
Hi, welcome in the Android community !
First check the device you own, because GT-I9505 and GT-I9500 are not the same and ROM that fit the first can brick the second and vice-versa.
Then, you have to root your phone, then to install a custom recovery.
Tutorials for these two steps can be found here, Q4 and Q5 answers.
Once these two steps are successfully completed, you can then flash the OMEGA zip file in recovery mode.
Click to expand...
Click to collapse
Thank you both guys.
I am reading now to get ready.
I have done Q4 but i do not understand these informations:
Installation and usage
Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home).
Using this root increases your flash counter. You should run Triangle Away (see below) after rooting to reset the counter. Note that if you want to run custom kernels or custom recoveries, your flash counter will be set to 1 at every boot. Either configure Triangle Away to reset the counter at every boot (Play version only) or only reset the counter when you need to go into warranty.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Why isn't this just called CF-Root
The traditional CF-Root's included a custom recovery (CWM, TWRP, etc) and were meant for devices that had a single kernel/recovery combination. CF-Auto-Root doesn't include a custom recovery and is meant for devices that have kernel and recovery separate (so you can manually install any custom recovery you wish). The Auto part comes from the fact that a large part of the process is automated (though it constantly needs adjusting)
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
Click to expand...
Click to collapse
Second reply says how it is done.
I have done it successfuly,is there any other to do before Q5?
I have done both steps successfuly (as i think).
In first step i found SuperSu and in second the CWM has pasted.
Now can i root OMEGA?
I have I9505XXUBMGA.
Originally Posted by ooop View Post
There is a new update for Nordic countries with CL: 1081224
NEE
Build Date 11.07.2013
PDA - I9505XXUBMGA
CSC - I9505OXXBMG3
I9505XXUBMGA = Omega v 9?
Fast link for you (i cannot put the link because i must have 10 posts)
Click to expand...
Click to collapse
Is this link for my kernel?
Thank you for your help,by the way.
If you already rooted your phone, and install those custom recovery, then just do what indie says in his post http://forum.xda-developers.com/showpost.php?p=40778466&postcount=4
you should go fine if you really really follow those step
ar216893 said:
If you already rooted your phone, and install those custom recovery, then just do what indie says in his post http://forum.xda-developers.com/showpost.php?p=40778466&postcount=4
you should go fine if you really really follow those step
Click to expand...
Click to collapse
I have done both but i have put PhilZ CWM instead of TWRP as recommended for the omega installation.
The only thing for me is the kernel.
Is there any problem that mine is different than omegas rom kernel?
So does not mater the kernel you are been to if you are rooted?
Omega installs the rooted stock kernel so it won't matter what current kernel you're using. There's plenty of kernels available. You can only install kernels that support Samsung (TW) firmware.
Sent from my GT-I9505 using XDA Premium 4 mobile app
kotsosre said:
I have done both but i have put PhilZ CWM instead of TWRP as recommended for the omega installation.
The only thing for me is the kernel.
Is there any problem that mine is different than omegas rom kernel?
So does not mater the kernel you are been to if you are rooted?
Click to expand...
Click to collapse
Yes, like @symondo12 said, omega comes with stock kernel, so it will not be problem. For recovery, that's fine whatever recovery you use, it can install same thing, but TWRP has very user friendly view than the other.
From your post before, I think what you mean is the build number, that's like the software version. Your current version is the one same with omega v9,so if you install omega with version newer than the v9, it's like you got upgrade from your current version
Sorry for the bad english, I hope you understand what I'm saying
Yes i understand and i have done both.
It is OMEGA now
Thanks for your help.
hi
kotsosre said:
Yes i understand and i have done both.
It is OMEGA now
Thanks for your help.
Click to expand...
Click to collapse
Hi guys. Sory for the question but can you tell me where i can find galaxy s4 omega rom v 9.0 . I.ve searched all over the net and i couldnt find it. Please help.
demoskino said:
Hi guys. Sory for the question but can you tell me where i can find galaxy s4 omega rom v 9.0 . I.ve searched all over the net and i couldnt find it. Please help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=45090802&postcount=9418"
Στάλθηκε από το GT-I9505 μου χρησιμοποιώντας Tapatalk 2
hi
Tks. But this is omega v10 rom and i would like the v9 or v9.1 rom. I couldnt find anything on the omega download page or on the internet. Tx you
Related
Hello. After updating my A500 to the official ICS rom, I easily rooted my tablet succesfully by downloading a program found on this website:
http://forum.tegraowners.com/viewtopic.php?f=30&t=350
Then, I downloaded an app from the market/play store called "Acer Recovery" wich lets you flash CWM recovery (which is built in into the app). The app said it flashed the recovery succesfully. Now, when I press the "boot into recovery" button I get stuck in the Acer logo and on the top left corner it sais in red: Recovery Failed
I would like to flash custom roms. What am I doing wrong?
Many thanks...
domenicostorino said:
Hello. After updating my A500 to the official ICS rom, I easily rooted my tablet succesfully by downloading a program found on this website:
http://forum.tegraowners.com/viewtopic.php?f=30&t=350
Then, I downloaded an app from the market/play store called "Acer Recovery" wich lets you flash CWM recovery (which is built in into the app). The app said it flashed the recovery succesfully. Now, when I press the "boot into recovery" button I get stuck in the Acer logo and on the top left corner it sais in red: Recovery Failed
I would like to flash custom roms. What am I doing wrong?
Many thanks...
Click to expand...
Click to collapse
Which version of Bootloader are you running? The recovery installer app should tell you when you start it.
Also, which version of Recovery did you try to install?
Moscow Desire said:
Which version of Bootloader are you running? The recovery installer app should tell you when you start it.
Also, which version of Recovery did you try to install?
Click to expand...
Click to collapse
Thanks for helping me out.
-Bootloader Version: 0.03.12-ICS
I tried installing the two only recoveries avaliable wich are:
-ClockworkMod Recovery rev1.3.4 by thor2002ro
-Stock USA 1.141.07_COM_GEN1 recovery
After flashing any of the two I click on "Reboot into recovery", it reboots but gets stuck in Acer logo and on the top left corner says:
-Recovery verified failed
I have the same problem too and I still couldn't find a way out
Firmware Specs are same as yours
I wonder if there is a simple way out
Anyone can help ?
Thanks
Ramp
Ok, both of you need to go to this thread and read over the info.
The reason why your recovery "might have failed" is probably because you didn't delete a certain file from your rom before you flashed your CWM. That is... "recovery.from.boot.p" in the system folder.
If you don't, every time you reboot your will lose your CWM.
Anyhow, read this thread. Everything you need is there.
http://forum.xda-developers.com/showthread.php?t=1622425
And if you;re going to install some ICS Customs in the future, I advise you install a patched unlocked bootloader.
EDIT: One more important thing. Before you folks go off flashing and everything, PLEASE... Get your UID number now, and write it down in a safe place (like the box your tablet came in . If you tab gets borked up, it's the only thing that'll save it.
MD
As MD stated be sure to read that thread , once down reading it, re-read it , I would try using that method first ,it helps you learn , but if you want to go to this thread and it will be a whole lot easier :http://forum.xda-developers.com/showthread.php?t=1675939
I always tell people in here read as much as you can , read through the Android section as well!
uahuuuuuuuuuuu !
What can I say ......Afterota is AMAZING!!!!
Made my day, not my day...my month!
It works like a charm and it's really easy to handle
Thanks thanks thanks !
Ramp
Thanks, I did it as well with AfterOta, what a great tool. I am already rooted in ICS and have public recovery working. I'd like to try some custom roms. Is there any other step I have to complete before flashing a new custom rom?
Thanks again for the help
domenicostorino said:
Thanks, I did it as well with AfterOta, what a great tool. I am already rooted in ICS and have public recovery working. I'd like to try some custom roms. Is there any other step I have to complete before flashing a new custom rom?
Thanks again for the help
Click to expand...
Click to collapse
I would advise making sure you have at least Version 3 or higher of the unlocked bootloader. Version 4 is better as you can change the boot image. Also, with version 4 (and higher) you can flash any future bootloaders through CWM.
Also, make a system (nand) recovery backup before you go flashing roms. This way you have something to go back to if the flash doesn't go right.
part of the original problem you had was the recovery you tried to flash was an earlier version which doesnt match ICS , You can get the beta copy of Acer Recovery ,but you'll have to search for it , it also has updated ICS recovery listed
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
jonraymond21 said:
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
Click to expand...
Click to collapse
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
leaderbuilder said:
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
Click to expand...
Click to collapse
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
jonraymond21 said:
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
Click to expand...
Click to collapse
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
leaderbuilder said:
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
Click to expand...
Click to collapse
man thanks so much. so i definitly got super user access. I'm about to do the goo manager. since you suggested the twrp i think i'm going to try that. since i have CWM recovery installed, do u think that will create any issues if I go to install TWRP from goo manager
actually i googled and it seems that goo manager will seamlessly overwrite cwm. sorry for the questions before searching. appreciate the help. i almost didn't come on here, which would of lead me to reverting to stock, doing cwm again, then being upset that i needed twrm for most roms lmao. I owe u one. If u ever need to learn how to make bad decisions, just shoot me a pm. I got u covered.
No it will just replace it.
I actually (and many around here too) prefer TWRP 2.5.0.2.
You can download the zip for that here, boot to recovery you have now (CWM) and then install that. Or use Goo to install lates TWRP and boot to recovery and then install zip and choose the 2.5.02 you downloaded and then save to your sd card
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
jonraymond21 said:
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
Click to expand...
Click to collapse
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this Rom!
http://forum.xda-developers.com/showthread.php?t=2327692&page=43
works great!
Q&A for [CM12] [Lollerpop] JFLTEATT Nightly Kangs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [CM12] [Lollerpop] JFLTEATT Nightly Kangs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
noremac258 said:
No love for the jfltecan?
Click to expand...
Click to collapse
Yea I tried even using the jflteatt philz to trick it but the data part failed and system was success. So I didn't bother trying to boot. You can still use Antares however, it is unified.
I am wondering if I can flash Antares and then dirty flash this over to get the system part, I just don't wanna have to go through Odin to stock rigamarole.
cm-12-20141124.1217-jflteatt
Can't get it to boot on my AT&T S4. It tries, black screens, then reboots into AD recovery automatically.
I'm unlocked using T-mobile, but I don't think that should matter.
TWRP v2.7.1.0-- Using stock slot with safestrap disabled (no success on making new slots with safestrap enabled, either).
Lollerpop CM12 - AT&T Samsung Galaxy S4 (SGH-i337) - Unauthorized
Hi,
I tried replying to the CM12 Lollerpop thread but even though I have been utilizing XDA for YEARS, I am still considered a noob due to lack of posts.
Anyway, I just wanted to let the awesome developers know that I tried installing CM12 Lollerpop through TWRP, on my AT&T Samsung Galaxy S4 (SGH-i337) that I have installed ROMs on hundreds of times. For some strange reason that I cannot explain, with the Beta version of CM12 right after I power on the device after installing I see an ! and "AT&T UNAUTHORIZED SOFTWARE HAS BEEN DETECTED" and device went to a black screen after 5 -> 10 seconds. Fortunately I was still able to get back into TWRP after a reboot and home + volume up and successfully completed a restore from a 4.4.4 Beanstalk complete backup I took prior to testing CM12 installation / boot, etc.
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
jkvincent said:
I would greatly appreciate it if someone could A) explain why this is happening with CM12 and more importantly B) how to get around this annonying blocking message.
Click to expand...
Click to collapse
It sounds like you did not flash a Loki-Doki package. Search the AT&T Galaxy S4 forum and you can find it. You need to flash this after you flash your ROM (or anything else) to trick your phone into thinking you have stock software. Some ROMS have this included, which is probably why you have never had to flash this package before, but I would say that most don't. And no, even if the ROM has a Loki package included inside of it, it doesn't hurt to flash it twice so I end up flashing Loki-Doki a lot.
Sent from my GT-I9505G using XDA Free mobile app. Press "Thanks" if I helped!
Unauthorized - Loki & Safestrap
Hi,
I downloaded loki-doki.zip, wiped, installed CM12*.zip, gapps-lp*.zip and applied loki-doki.zip to find the annoying "Unauthorized..." message again. I tried installing loki by itself after a clean reboot. I tried with wiping dalvik + cache and without. Same thing.
After reading up on Loki, I ran into a bit that stated Loki is designed for 4.4.2 and for 4.4.4+ I should be using Safestrap. I downloaded the Safestrap*.apk file, installed it, granted root access and installed Recovery (says Safestrap is built off TWRP).
The first thing I noticed was the TWRP version was still 2.8.1 (I also updated TWRP prior). I went through the same process without Loki. Same "Unauthorized..." message. Tried Loki after. Same message.
I am not sure at this point but I have never had much luck installing Recoveries while being booted into Android. I have always had to install from a .zip in Recovery or use Odin. I'm not convinced Safestrap updated or even if it is the right way to go. What would be really sweet is if the Devs could wrap whatever is needed to get around the "Unauthorized...", into the CM12 installation. Maybe that is asking for too much. I need to still research Safestrap and it is getting late. I do appreciate you pointing out Loki because it got me pointed in the right direction. I kind of forgot about it with the ROMs being Lok'd.
Kind Regards,
Jason Vincent
Sr Integration & Validation Engineer
VoIP SME
For those who are on AT&T, this is how I got 11-30 to work. Worked perfectly, except the battery drain.
Install cm12 using TWRP (shouldn't matter, but I used 2.8.0.1), flash gapps if you want, flash ktoonsez aosp 5.0 kernel just updated few days ago. No loki patch needed. Good luck.
Didn't get a chance to test bluetooth, but camera seemed to work.
I am using a AT&T s4 (no safestrap)
Hi, Try installing a kernel. it work for me. Alicard or ktoonz.
Question here
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
StoneyJSG said:
I have the sgh-i337 rooted on stock firmware 4.2.2 and have installed shabbyPenguin recovery (I know it's an old recovery but it seems to work fine). I am able to flash this ROM like my bootloader is unlocked or do I need to do something else like flash the loki-doki.zip file?
Thanks in advance!
Click to expand...
Click to collapse
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
thesummoner101 said:
I'm not sure what you said in that last line. But I'm guessing you mean to ask if you can flash this or not. Simple answer, no.
Long answer: I'm not sure what your device exactly is, or what you have done with it. I'm guessing it's not an MDL or earlier device to which the loki-doki patch applies. So using that on your device could be bad idea. I'm assuming the recovery you listed is a modified version for safestrap users. In which case, you can only run touch wiz based roms or Google play edition (safestrap), which this is neither of.
Click to expand...
Click to collapse
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
StoneyJSG said:
Sorry for my typos. I was asking if I can flash this rom like I have an unlocked bootloader since I am on the MDL firmware Android 4.2.2 and can use LOKi. I have ShabbyPenguin's version of Clockwork mod recovery installed.
Click to expand...
Click to collapse
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
thesummoner101 said:
Okay, if you're on MDL, then you have a couple of options. Here's the process that has worked for me without issue. I'm also on MDL. I'm using twrp but prices should be similar. This could also be a good time to update the recovery, it's really easy.
1) download rom to external sd
2) download PA micro 5 gapps
3) download ktoonsez 5.0 att aosp 12-9 kernel
4) factory reset, wipe dalvik/cache
5) install rom
6) install kernel
7) boot then let it settle and reboot into recovery
8) install gapps
9) boot and let it settle
BTW, our bootloader isn't exactly unlocked, it's just hacked/patched/fooled to think it is. It doesn't seem any different than an unlocked one, except that it needs loki patch, patched recovery, or AT&T kernel.
Good luck.
Click to expand...
Click to collapse
Awesome! Thanks dude. Since I am partial to CWM, I was going to flash PhilZ touch recovery, but from what I have read the ShabbyPenguin recovery is supposed auto loki upon flashing. I also have the loki-doki.zip file for flashing as well just in case.
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
ahmedbatty said:
How do I even flash CM12 on my device?
My SGH-I337 has Lollipop 5.0.1 and it is rooted no custom recovery.
Please help
Click to expand...
Click to collapse
How you installed custom recovery in S4 i337 at & t?
Jordan Gonzalez said:
How you installed custom recovery in S4 i337 at & t?
Click to expand...
Click to collapse
I found out that I can't flash any custom ROM or recovery if I have the latest bootloader, so it's locked
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
I have a Note 3 N9005.
I installed the latest TWRP recovery.
No matter which rom I try to flash to the system, the same thing happens.
I see that the Aroma installer is strarting and than it just resets for no reason, no install made.
The only sulotion I have found so far is to install a 5.0 stock rom via Odin.
I want to install a custom rom 6.0.1.
Does anyone know what the hell?
Sae problem but a lil worse!!
vashthestampede! said:
I have a Note 3 N9005.
I installed the latest TWRP recovery.
No matter which rom I try to flash to the system, the same thing happens.
I see that the Aroma installer is strarting and than it just resets for no reason, no install made.
The only sulotion I have found so far is to install a 5.0 stock rom via Odin.
I want to install a custom rom 6.0.1.
Does anyone know what the hell?
Click to expand...
Click to collapse
I tried to do the same but ended up bricking my phone. So then I try to unbrick/unroot my phone by flashing the stock rom but I can't do that either cause now it says "Volume Size is too big 4620288<4718599. Need help!!!! ASAP!
Hey guys, I had the same problem at first and it freaked me out too.
Try installing the older 2.8.7.0 version for TWRP through the app, instead of the latest or any other after v3 for that matter. Apparently I've read from other forums that it's due to lack of Aroma Installer Support.
Hope this helps
Confirm the phone's model # by booting into download mode befor flashing TWRP or a stock ROM from sammobile.com.
Will try
I flashed the stock rom packege with odin.
saved my phone after brick.
so you are saying that by downgrading the TWRP recovery i can use aroma insatller based roms again?
cause i also tried to install reserection remix rom (I think this has no aroma in it), i got a massage that said that i cannot install it as well.
refuses to let me change into anything but stock rom.
rooting did not help at all.
vashthestampede! said:
so you are saying that by downgrading the TWRP recovery i can use aroma insatller based roms again?
cause i also tried to install reserection remix rom (I think this has no aroma in it), i got a massage that said that i cannot install it as well.
refuses to let me change into anything but stock rom.
rooting did not help at all.
Click to expand...
Click to collapse
To be honest I don't really know about Cyanogen Mod, however this was just my personal experience with Aroma Installer. I've tried DarkWolf_FW and Aryamod ROMs which are both S7 Edge Port ROMs, and they both use Aroma Installer.
- Also! Take the opportunity to make a Nandroid backup just in case the installation goes bad, then you can restore to where you are right now. Honestly downgrading just worked for me so please don't make me liable if anything goes to pot, at least you will have a full device backup to the exact point in your system which I have found extremely useful when trying different ROMs and Kernels.
tnks
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
vashthestampede! said:
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
Click to expand...
Click to collapse
Hey, just randomly thinking, did you reset all your System, Data and Cache and Dalvik Cache files before you tried to install the ROMs? Sorry, this might not make a difference, but I don't think I have any more advice to give (I'm kinda new to this too ).
Hope CWM recovery goes well, let me know how it goes
vashthestampede! said:
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
Click to expand...
Click to collapse
Doing a complete backup before anything is always the safest bet.
From my experience, TWRP 3+ is fine for CM and AOSP based ROMs.
TWRP 2.8.7-0 is the one you should use to flash ROMs using AROMA Installer.
If you read the OP (opening post) on any ROM forum, it will usually include installation instructions and generally states which TWRP version should be used.
Good Luck.
theawesomecw said:
To be honest I don't really know about Cyanogen Mod, however this was just my personal experience with Aroma Installer. I've tried DarkWolf_FW and Aryamod ROMs which are both S7 Edge Port ROMs, and they both use Aroma Installer.
- Also! Take the opportunity to make a Nandroid backup just in case the installation goes bad, then you can restore to where you are right now. Honestly downgrading just worked for me so please don't make me liable if anything goes to pot, at least you will have a full device backup to the exact point in your system which I have found extremely useful when trying different ROMs and Kernels.
Click to expand...
Click to collapse
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
You just need download mode to flash it.
Sent from my SM-G925F
kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
I presume when you say it doesn't turn on you mean it doesn't boot into the Android environment. Have you tried unplugging the battery and pressing the Volume Up + Home + Power Button? Yes... I was surprised you don't have to be an octopus too..
Then restore the Nandroid backup from before.
You can also flash TWRP through Odin without root, have a look at the TWRP website for more info.
re
kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
all you need is to flush new stock rom via Odin.
Search the web (like I did) to find a stock rom with 4 .tar files in it.
There should be instructions on how to install but usually all needs to be done is this:
1. load odin 3.*
2. enter the phone in download mode.
3. After you see the line 'add' in odin, load the .tar files to the correct place each (not hard they are tagged by same name)
4. Flush and pray.
5. After a successful install the phone will reboot, this will take a while so don't get streesed.
after about 10-15 min the phone will load again.
Root one more time via odin and try to install again.
vashthestampede! said:
all you need is to flush new stock rom via Odin.
Search the web (like I did) to find a stock rom with 4 .tar files in it.
Click to expand...
Click to collapse
Try Sammobile as they have a large database of firmwares for your phone and the country variants.