I was planning on flashing a RC CM10.2 on my device however I noticed on the cyanogen mod instructions for install it indicates I need to be on a build number I337UCUAMDB or I337UCUAMDL. I checked my device and the build number indicates 1337UCUAMF3. I was wondering what do I need to do to get my build number to match? And why doesn't it match in the first place? I'm sorry these are such nooby questions, I'm still learning....And also.....I've used TWRP recovery before however it looks like CM10.2 requires clockworkmod? Theres 2 files indicated for download on the instructions for 10.2 install (steps 1 and 2 under "Prepare and flash your recovery image") what do I do with these? Never used CWM before...
You can't flash roms or put a custom recovery on your phone. You're on mf3 firmware.
Don't try to put a recovery on, you'll mess up your phone
Related
i accidentally deleted my stock os in my nexus one. i found some stock roms but i keep getting this error every time when i try to install them
E:signature verification failed
What recovery are you currently using?
If it is stock recovery you will need to use the official google file and rename it "update.zip" and place it on the root of your SD card. Make you sure you visit the development section and read up on the procedures, as your radio version and recovery are not listed, its hard to tell from your post. If you are indeed in stock recovery...
Here is the original, official ROM http://forum.xda-developers.com/showthread.php?t=614057, make you sure you load it correctly. And of course...I am not responsible for anything that may go wrong. You will soon get the OTA update to 2.2 Froyo.
If your on a custom recovery, you should download a custom ROM. Some are based on the stock AOSP so if that's what you want you can find one like that and flash it through custom recovery after the triple wipe (factory/cache/dalvik). If that doesn't work try switching to the other custom recovery image. Aman-Ra is one, ClockWork is the other.
cheers
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
chokem said:
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
Click to expand...
Click to collapse
So, to sum up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Furies said:
So, to some up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Click to expand...
Click to collapse
OK, thanks very much. So I was indeed on the right track. I'll try your ROM recommendation as well as the modified CWM recovery.
hello,
after reading almost everything i could read on the forums about the procedure of flashing roms, i'm left with a few questions that i couldn't find answers to, or i found more then one answer.I read all the following, and more:
1. [GUIDE] All-in-One Defy Beginner's guide by Zephyrot here: http://forum.xda-developers.com/showthread.php?t=1216982
2. [JB] CM10 Android 4.1.2 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=1768702
3. [GUIDE][KitKat][CM11] Updating to 4.4 by coolshahabaz here: http://forum.xda-developers.com/showthread.php?t=2568325
4. [Kitkat][Nightlies] CM11 Android 4.4 for the Defy(+) by Quarx here: http://forum.xda-developers.com/showthread.php?t=2515036
5. http://forum.xda-developers.com/showthread.php?t=2597719
6. http://forum.xda-developers.com/showthread.php?t=2644812
7. http://forum.xda-developers.com/showpost.php?p=49558697&postcount=3
8. http://forum.xda-developers.com/showpost.php?p=49558744&postcount=4
My devicee is a Defy+ with Gingerbread 2.3.6. I found here: http://sbf.droid-developers.org/phone.php?device=28 "Android 2.3.6 Blur_Version.45.0.1610.MB526.Partner.en.IL" rom which is supposed to be my stock rom.
1. My main concern is always to keep the option to go back to stock rom. As i read here, this might be a problem with Defy+, but only if i flash SBF files, which i dont plan to. Is it correct that i will be able to flash the stock rom with RDS_lite, motorola drivers and bootloader (power up with VOL up) at any time?
questions about recovery:
2. I understand that i need TWRP 2.3.6 in order to flash new roms, and since recovery is protected in Defy, i must use 2nd_init to bypass stock recovery. Is 2nd_init include the custom recovery in it? if so, which one? and what version?
3. can i install CWM or TWRP without using 2nd_init?
4. What is rom_manager (for CWM) or goo.im (for TWRP) and do i really need them?
5. what is update_recovery.zip mentioned as part of the procedure here http://forum.xda-developers.com/showthread.php?t=2515036 does it update the custom recovery or the stock recovery? is it really needed since some of the procedures described above skip this step?
choosing a custom rom:
6. I'm looking for adnroid 4.4. what is the difference between this: http://forum.xda-developers.com/showthread.php?t=2597719 (AOSP Android 4.4 for the Defy(+)) and this http://forum.xda-developers.com/showthread.php?t=2515036 (CM11 Android 4.4 for the Defy(+))
7. If i want a as-close-as-possible to google original kitkat 4.4, which one should i use?
Thanks,
Roy.
I have some of the same questions you have... will follow this topic, hoping for some info! thx!
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
Here is where 2nd Init comes to play, this little awesome app kicks in right after the Bootloader and allows the Defy to load a different, non-Stock Android.
With this, you can also install a Custom Recovery, which runs from the Internal Memory, and is not ran from the Recovery Partition (remember: locked, not accessible) what does this means? That even screwing up your phone, deleting all your stuff, or screwing /system partition the phone can still get into Recovery, be recognized by RSD Lite in Bootloader Mode and be flashed with a Stock or modified Rom (more on this later) and it will come back to live normally.
Click to expand...
Click to collapse
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
hotdog125 said:
1. You can always go back to stock ROM using RSDLite. There is no such problem with the Defy+.
2. After rooting, install the 2ndinit app to install ClockworkMod recovery (which is now outdated). Then reboot, and flash this - http://forum.xda-developers.com/showpost.php?p=48501247&postcount=1250 in the recovery. This way you will get TWRP recovery required to flash newer ROMs such as 4.4.x ROMs.
3. The 2ndinit app installs custom recovery. This info is clearly given in Zephyrot's guide -
4. You don't need them.
5. None of the recovery updates touch the stock recovery. The stock recovery is built-in, and due to the locked bootloader, it cannot be removed or modified. For 4.4.x ROMs, it is sufficient to follow step 2. This guide explains the steps for installing KitKat - http://forum.xda-developers.com/showthread.php?t=2568325.
6. The AOSP ROM is severely outdated, I recommend you to try SlimKat or CM. AOSP is pure android (stock android you find in Nexus devices).
7. Using CM or Slimkat is sufficient. Also there is no 'Best ROM'. It depends on the user's opinion and requirement.
Click to expand...
Click to collapse
Many many thks!
Im trying to up to CM 11 from 2 months.Now Im on 10.0(4.1.2).Every try to update recovery with "update-recovery.zip" or TWRP 2.6.3.0 finished with bootloop or without custom recovery and balck screen.And them flash stock .sbf and start all from the begining.And try and try....In your guide it have link to update recovery.It have something about 30+ seconds waiting after TWRP update.So I try.
Hi All,
New to forum here and to Android *re-engineering* in general. Wife gave me a task: to remove the stock S4 OS and replace it with something better.
These are the steps I followed:
1. In Download mode, used Odin v3.10 to flash TWRP 3.02 recovery
2. Booted to Recovery Mode, it gets to TWRP recovery ROM properly.
3. Recovered to CM13 nightly builds and rebooted to System.
4. Boots to System with the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Samsung Galaxy S4
GT-I95016
After that it just stays stuck on the screen until I reboot into Download or Recovery Mode.
None of the CM13 OS downloads I used work so far. I've also tried to recover to CM11 after the initial problem, but it doesn't work. Note that there are no releases for this, only nightly builds. Tried for 2 weeks already and I think I probably need some help.
Any ideas?
zdfan said:
Hi All,
New to forum here and to Android *re-engineering* in general. Wife gave me a task: to remove the stock S4 OS and replace it with something better.
These are the steps I followed:
1. In Download mode, used Odin v3.10 to flash TWRP 3.02 recovery
2. Booted to Recovery Mode, it gets to TWRP recovery ROM properly.
3. Recovered to CM13 nightly builds and rebooted to System.
4. Boots to System with the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Samsung Galaxy S4
GT-I95016
After that it just stays stuck on the screen until I reboot into Download or Recovery Mode.
None of the CM13 OS downloads I used work so far. I've also tried to recover to CM11 after the initial problem, but it doesn't work. Note that there are no releases for this, only nightly builds. Tried for 2 weeks already and I think I probably need some help.
Any ideas?
Click to expand...
Click to collapse
The message during boot is normal if you've modified the Bootloader (in this case, by flashing the recovery).
By "recover" I assume you mean installed/flashed a ROM.
Are you flashing the right ROM for the model?
Did you wipe before flashing?
GDReaper said:
The message during boot is normal if you've modified the Bootloader (in this case, by flashing the recovery).
By "recover" I assume you mean installed/flashed a ROM.
Are you flashing the right ROM for the model?
Did you wipe before flashing?
Click to expand...
Click to collapse
Thanks for replying - ok good to know that message is normal.
1. Yes I flashed the TWRP recovery ROM.
2. In TWRP recovery mode I installed the custom ROM for cyanogenmod 13 for i9506, downloaded from the Builds in this link: __download.cyanogenmod.org/?device=ks01lte___ (copy paste the URL as I cannot post external URL yet)
3. Yes, wiped before flashing.
zdfan said:
Thanks for replying - ok good to know that message is normal.
1. Yes I flashed the TWRP recovery ROM.
2. In TWRP recovery mode I installed the custom ROM for cyanogenmod 13 for i9506, downloaded from the Builds in this link: __download.cyanogenmod.org/?device=ks01lte___ (copy paste the URL as I cannot post external URL yet)
3. Yes, wiped before flashing.
Click to expand...
Click to collapse
How much time did you wait for the phone to boot?
Have you tried other ROMs, from here on the forum?
There is a GT-I9506 section from where you can download various modified ROMs.
GDReaper said:
How much time did you wait for the phone to boot?
Have you tried other ROMs, from here on the forum?
There is a GT-I9506 section from where you can download various modified ROMs.
Click to expand...
Click to collapse
1. Waited up to 1/2 hr, same screen.
2. I've tried CM11 and CM13
3. Could you give an example?
zdfan said:
1. Waited up to 1/2 hr, same screen.
2. I've tried CM11 and CM13
3. Could you give an example?
Click to expand...
Click to collapse
I'm a GT-I9505 user, can't really recommend you anything.
There's AICP, various CM13 builds and others. Just look through the GT-I9506 section (here on the forum) until you find something promising.
Hi it is the first time I am flashing Android ROM. I have done some reading already. Before I start, I still have a few questions and also want to make sure I am doing it right.
I own the Galaxy S4 Verizon I545. It is running Samsung ROM Android 4.4.2, Baseband I545VRUFNC5. My goal is to flash a new ROM with recent Android versions, hopefully 7.1.1 (but I would settle with Marshmallow if that is more stable), it can be close to AOSP, I don't need ROMs with extra features.
In my understanding, the bootloader is locked, it will only load signed kernels and recovery. And then the kernel would load the system. In order to flash the system, it is best to flash the recovery first with TWRP. TWRP is modded with loki hack so it would load with the locked bootloader.
So here are my questions:
1. Does it matter which firmware/baseband I am currently on? For some phones (LG G2) I heard newer firmware fixed the loki hack. Should I update to the latest Samsung rom or leave it at NC5?
2. I don't see many ROM posted for the i545, which one is the most recent and reasonable stable? The Cyanogen website is down, should I try LineageOS?
3. I see different instructions for flashing TWRP. Can I flash it with just Odin? Some instruction mentioned rooting the phone first with KingRoot or other root, and then use dd. Does the phone have to be rooted? (I prefer not to if it is not necessary)
4. If after I flashed recovery, it fails to boot into TWRP, what can I do to restore everything to default?
5. The kernel will be untouched in the process right? I am only flashing recovery and system ROM, and the kernel will work fine with the new system ROM?
Here are the step and software I plan to use:
0. reset the phone to factory
1. use Odin to flash TWRP 2.8.7
2. download a ROM compatible with I545 and place it on the phone
3. flash the system using TWRP
Any feedback would be appreciated.
PS: Also I have a LG G2 D801. I would flash that phone instead if it is easier. I just want to get started and learn some things along the way.
https://forum.xda-developers.com/galaxy-s4-verizon
Oh Sorry. Didn't notice there is another forum. Should I repost there?
Yes.
1. Yes, it does matter. As you said, newer firmwares have fixed the exploits which make the phone harder to hack.
2. Any ROM should support your phone. They are generally unified.
3. In the name of anything holy, do not root with KingRoot. If you want to root, then the only way to go is CF-Auto-Root.
Rooting is sometimes necessary because recovery won't always install with Odin.
4. Flash stock ROM.
5. Kernels are specific to ROMs. So no, the kernel won't be untouched.