Hi!
I followed all the steps in this link:
http://forum.xda-developers.com/gal...rom-cyanogenmod-12-1-galaxy-e5-e500h-t3255586
on how to intall CM 12.1 to my Samsung E500H but after installing the ROM and gapps, after reboot I'm having a "Set Warranty Bit: Kernel" error and stuck in boot loop. I restored back my Nandroid backup and it's working again.
Is there any workaround for me to make CM 12.1 to work without the error? Device is rooted and still in stock 4.4.4.
Any help would be appreciated.
Thanks! :good:
fsociety.dat said:
Hi!
I followed all the steps in this link:
http://forum.xda-developers.com/gal...rom-cyanogenmod-12-1-galaxy-e5-e500h-t3255586
on how to intall CM 12.1 to my Samsung E500H but after installing the ROM and gapps, after reboot I'm having a "Set Warranty Bit: Kernel" error and stuck in boot loop. I restored back my Nandroid backup and it's working again.
Is there any workaround for me to make CM 12.1 to work without the error? Device is rooted and still in stock 4.4.4.
Any help would be appreciated.
Thanks! :good:
Click to expand...
Click to collapse
maybe you have to be on lollipop to flash cm12.1 roms. I am not sure but it is mentioned int the requirement that you have to have Lollipop bootloader and modem. Ask the OP
nepalbiraj said:
maybe you have to be on lollipop to flash cm12.1 roms. I am not sure but it is mentioned int the requirement that you have to have Lollipop bootloader and modem. Ask the OP
Click to expand...
Click to collapse
Thanks! That might be the issue. Kinda new here.
fsociety.dat said:
Thanks! That might be the issue. Kinda new here.
Click to expand...
Click to collapse
Its alright
fsociety.dat said:
I followed all the steps in this link:
http://forum.xda-developers.com/gal...rom-cyanogenmod-12-1-galaxy-e5-e500h-t3255586
Is there any workaround for me to make CM 12.1 to work without the error? Device is rooted and still in stock 4.4.4.
Click to expand...
Click to collapse
You did NOT follow the first step itself!!!. The dev clearly mentioned that you need to be on STOCK 5.1.1 before installing this rom.
Your phone was running 4.4.4 before you flashed cm12.1. So the obvious workaround is to flash stock 5.1.1 completely. [ link to stock 5.1.1: http://www.sammobile.com/firmwares/database/SM-E500H/ ]
Warning: Dev said cm12.1 's radio is broken, which means you will not be able to make phone calls. Proceed at your own risk.
Related
Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA
vish9 said:
Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA
Click to expand...
Click to collapse
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
joebob296 said:
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?
Click to expand...
Click to collapse
Exactly, AOSP ROMs are booting up fine but not the Stock based ones.. I am not flashing any kernels, just the ROM, so I'm assuming it will run on either the stock kernel or the kernel included in the ROM zip?
Have you been successful in installing such ROMs? Am I missing something in the wiping part? Only been doing the factory reset in TWRP before installing any ROM.
Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk
rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Oh, I hadn't thought about anything being wrong with the recovery.. Always assumed it gets the work done
How do I find previous versions of TWRP compatible with D800?
joebob296 said:
Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yes I am on 10o.. Does it have issues with installing other Stock ROMs? If yes, I'll try to follow the thread on using LGFlash tools, I've never done that before. Hopefully its not much difficult to follow the instructions.
That is one of the easiest guides to follow. Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
joebob296 said:
That is one of the easiest guides to follow. Me sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Thanks.. I'll try to do it tonight and post my results here.
joebob296 said:
Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I'm stuck in the process! Can't change the com port number to 41. The guide is pretty easy to understand. But when I put my phone is download mode and try to change the com port number, it says I don't have the write privileges for this device's setting. I've tried it on both Win 7 and Win 8 laptops, with LG mobility drivers installed.
Is there something in the phone settings I need to enable so that I get the write privileges to change com port number?
Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk
SOLVED!
joebob296 said:
Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yay!!! Finally did it!
Issue 1: If faced with write privileges for com port (tried successfully in Win 8)
Solution: After going in to com port properties, click "change settings" and there is the option to change com port number.
Issue 2: Once the port number was changed to 41, rest of the instructions are easy to follow on this thread http://forum.xda-developers.com/showthread.php?t=2633150
Once on D80010d, I rooted with ioroot22, and installed recovery using FreeGee. Just installed Rayglobe 3.2 minutes ago, and it finally booted up!!!
So, the bottomline is that go back to D80010d if you wanna play with Stock based ROMs! I flashed with TWRP 2.6.3.3, so the fault is not with the recovery. That much I can confirm
Thanks for the suggestions guys. Thread solved I guess.
Great. Glad to hear it.
Sent from my LG-D801 using Tapatalk
rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Thanks for the input. Before I flashed back to D80010d today, I installed older versions of Philz and TWRP but neither helped. So downgrading was sort of a compulsion, in my case at least.
and the moral of the story is, unless you are getting an android version upgrade in the update, do not take the update.
Hi Guys,
As you can see, I am new to this site. My phone is S4 19505. Yesterday, I tried to root my phone and that was a succes. Problem began when I want to install kernel for longer battery life. I have installed kernel from http://forum.xda-developers.com/showthread.php?t=2297379 and I have chosen Touchwiz KitKat 4.4 version. After I flashed this kernel my s4 is not starting. It just stuck at first screen "where we get first white letters samsung galaxy s4".
I have no idea what to do now.
Can anyone please help me?
Advance thanks.
safi_k19 said:
Hi Guys,
As you can see, I am new to this site. My phone is S4 19505. Yesterday, I tried to root my phone and that was a succes. Problem began when I want to install kernel for longer battery life. I have installed kernel from http://forum.xda-developers.com/showthread.php?t=2297379 and I have chosen Touchwiz KitKat 4.4 version. After I flashed this kernel my s4 is not starting. It just stuck at first screen "where we get first white letters samsung galaxy s4".
I have no idea what to do now.
Can anyone please help me?
Advance thanks.
Click to expand...
Click to collapse
Did you follow the instruction of the OP, wipe cache and wipe dalvik after installing it?
Interface23 said:
Did you follow the instruction of the OP, wipe cache and wipe dalvik after installing it?
Click to expand...
Click to collapse
Yes, I did everything as there said.
safi_k19 said:
Yes, I did everything as there said.
Click to expand...
Click to collapse
Are you using cmw or twrp? I believe your stock rom is 4.4 kitkat
Interface23 said:
Are you using cmw or twrp? I believe your stock rom is 4.4 kitkat
Click to expand...
Click to collapse
twrp. I dont know what you mean by stock rom because this is my first time I did. My device is running 4.4.2. and I chose for kernel 4.4 version of tw.
I think that you have to re-flash a new rom. Then, you have to retry installing root and the kernel.
msmlz said:
I think that you have to re-flash a new rom. Then, you have to retry installing root and the kernel.
Click to expand...
Click to collapse
I agree with msmlz, if you have nandroid restore it or download the firmware in sammobile and reflash it and before flashing the custom kernel again, read the thread, see if someone face bootloop like you. Hope someone with experience on it could help you, I never install custom kernel, just update the last stock kernel on my rooted stock rom.
My friend's got a s3 neo and all he wants is cm 12 on his phone. I rooted using towelroot but I can't get into recovery and even if I install any custom recovery the phone boots into download mode saying "Could not do normal boot" bla bla and Qualcomm secure boot enabled and write secured something like that. I think that some qualcomm security is not letting the recovery written in system. AND then when I boot the phone back on and start flashify it says the current installed recovery: Stock recovery.
Help me here guys. I just wanna get into recovery somehow and wipe and get on with lollipop
Was it on 4.4 before updating to cm 12 ?
Rox said:
Was it on 4.4 before updating to cm 12 ?
Click to expand...
Click to collapse
Nope. It's never updated to 4.4 it's on 4.3
Are you sure you have installed the 4.3 custom recovery? The 4.4.4 version cannot work on 4.3. Make sure you followed this guide not the 4.4.4.
Barbarian-King said:
Are you sure you have installed the 4.3 custom recovery? The 4.4.4 version cannot work on 4.3. Make sure you followed this guide not the 4.4.4.
Click to expand...
Click to collapse
Thanks man, was flashing 4.4 recoveries all along...
Are there any other lollipop rom than CM12 ?
@Rox @Barbarian-King Guys I DM'ed you both the same thing. Sorry if I'm annoying you but it's kinda urgent and I'm a nexus 5 user. So I installed the cm12 with TWRP for 4.3. and then after installing it boots into the same "could not do normal boot" download mode screen. Thing is He's kinda jerk and wants it back quicly and I know I can flash stock 4.4.4 but my internet is kinda slow. I have Cm11 and CM12 downloaded but no luck with both
Really need help from both of you
Read requirements before installing ROM. You must be on stock 4.4 firmware
Rox said:
Read requirements before installing ROM. You must be on stock 4.4 firmware
Click to expand...
Click to collapse
Oh! I'm really soryy, so there is no workaraound now ?
I must be on 4.4 ? is there any other rom that doesn't require that
No. Flash stock 4.4 ROM firmware with Odin
Rox said:
No. Flash stock 4.4 ROM firmware with Odin
Click to expand...
Click to collapse
Well, Thanks and :'(
Thanks for the time man, So I install 4.4 and then lollipop
Rox said:
Read requirements before installing ROM. You must be on stock 4.4 firmware
Click to expand...
Click to collapse
I searched but it doesn't say anywhere that you should be on 4.4 either on cm11 or 12 thread...
Anyway you're the developer you obviously know more Mention it I think you should
Q&A for [UPDATE][OTA][ERROR][SOLVED] cm12 5.0.2
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 [UPDATE][OTA][ERROR][SOLVED] cm12 5.0.2. 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!
How to Fix error while installing 122 mB BUGFIX update
If u r getting Error while installing 122MB bugfix update.Then Follow these steps. You Dnt Need to Download Whole Rom.
1. Ensure U r On Stock 5.0.1.
2. Ensure u have Stock Recovery and Stock Kernel + UNROOTED YUREKA
3. If Ur Phone is Rooted, Flash Stock Image First
4. then Enter Stock Recovery
5. Apply Update from INternal SD Card and Flash 122 MB update through Stock Recovery
Incremental ota update problem
I got incremental ota update today but when i press install update ... my phone boot into update mode but after half process my phone directly boot in to stock Cyanogen recovery ...so i unroot my phone now also my phone boot in to recovery and not update ... please help me i have rooted via temporary method (stock recovery)
please help me ...
Anybody has stock recovery.img file for yureka 5.0.1?
I have rooted my phone and flashed TWRP recovery. Am I able to install the OTA update(My phone is showing the OTA update)? If not then what should I do to install the OTA update? Plzz help.
nissan skyline said:
I got incremental ota update today but when i press install update ... my phone boot into update mode but after half process my phone directly boot in to stock Cyanogen recovery ...so i unroot my phone now also my phone boot in to recovery and not update ... please help me i have rooted via temporary method (stock recovery)
please help me ...
Click to expand...
Click to collapse
I also faced this problem . please help
Downgrading from 5.1.1 to official 5.0.2
Hello,
I am currently running on unofficial pac man 5.1.1 ROM. Want to downgrade to the latest official ROM. Can i use your method to do this? If not, can you please guide. Thanks in advance.
mohdehjaz said:
Hello,
I am currently running on unofficial pac man 5.1.1 ROM. Want to downgrade to the latest official ROM. Can i use your method to do this? If not, can you please guide. Thanks in advance.
Click to expand...
Click to collapse
do clean wipe and flash this rom. it will work..
Ok bro, thanks for your response. Will try it
ashish_zarekar said:
do clean wipe and flash this rom. it will work..
Click to expand...
Click to collapse
Bro,
Had some doubts before i flash:
1) You mentioned do clean wipe and flash that ROM. Do i need to install stock recovery and stock kernel before that? I have custom recovery (CWM) installed right now.
2) After installing your this ROM will my phone be official, unrooted? Will i be able to get the official OTA updates in the future?
Please let me know.
mohdehjaz said:
Bro,
Had some doubts before i flash:
1) You mentioned do clean wipe and flash that ROM. Do i need to install stock recovery and stock kernel before that? I have custom recovery (CWM) installed right now.
2) After installing your this ROM will my phone be official, unrooted? Will i be able to get the official OTA updates in the future?
Please let me know.
Click to expand...
Click to collapse
oh yes sorry i have forgot that this one is official. i am really sorry for that. ohk now i have not tried this. i have solution for soft brick. so when ever i want to revert back to stock i use soft brick method. download fast boot stock images and follow procedure. you will be on stock.
Link for fastboot rom
Link for tool and guide
:fingers-crossed: :highfive:
ashish_zarekar said:
oh yes sorry i have forgot that this one is official. i am really sorry for that. ohk now i have not tried this. i have solution for soft brick. so when ever i want to revert back to stock i use soft brick method. download fast boot stock images and follow procedure. you will be on stock.
Link for fastboot rom
Link for tool and guide
:fingers-crossed: :highfive:
Click to expand...
Click to collapse
HI,
I have not done anything, means my phone is not soft bricked. its still running on the custom 5.1.1 rom with cwm custom recovery. Any other procedure to be applied now???
mohdehjaz said:
HI,
I have not done anything, means my phone is not soft bricked. its still running on the custom 5.1.1 rom with cwm custom recovery. Any other procedure to be applied now???
Click to expand...
Click to collapse
i know your mobile has not soft bricked yet.
but you can follow that procedure. it is safe. you will successfully boot in stock lollipop.
just download stuff from above link and extract it in single folder. you can see guide in above link also
ashish_zarekar said:
i know your mobile has not soft bricked yet.
but you can follow that procedure. it is safe. you will successfully boot in stock lollipop.
just download stuff from above link and extract it in single folder. you can see guide in above link also
Click to expand...
Click to collapse
Done and running official 5.0.2 now. Hope will be getting future official updates from now on. Thanks a ton bro. :good::good::good:
I flashed the the 122 mb update and got the error, but it was fine when I flashed the OTA LP again and flashed the incremental right after it.
But unfortunately (or fortunately ) my Mac address was lost had to flash a custom kernel to make it work. Was it the same for you?
And I don't see much difference with the phone, the battery lasts around 8-9 hours on games (heating is still on).
I do like to know if there's any difference for you guys
Sent from my AO5510 using XDA Free mobile app
Hey guys, I'll keep it short. I was rooted, installed TWRP, running Simple Rom and was just feeling to flash erobot. Flashed it doing full wipes and then rebooted, cool. Got to the samsung logo and within a second back to the note 4 screen. Okay I said, maybe the file I downloaded was corrupted or I installed it wrong. Did it over again, this time trying a few variations in the aroma installer (not installing xposed) thought maybe that was the problem. Bam same issue.
No worries I still had the old simple rom on the sd card. Went back with the same install and what do you know, that rom is now in a bootloop as well. Tried flashing through odin but I always get a nand write failed to start or something like that. Tried 3 different usb ports and same issue.
Am I missing something? Any advice would be greatly appreciated.
So you are using the Exynos model? Last I checked there is this OJ5 bootloader which can't be downgraded from!
ithehappy said:
So you are using the Exynos model? Last I checked there is this OJ5 bootloader which can't be downgraded from!
Click to expand...
Click to collapse
Yes I'm on the exynos model. So what did I do wrong, I went from lollipop to a lollipop rom. I didn't go back to KK or anything. What do I have to do?
guys help me im having bootloop because i was trying to install the su suser .in my note 4 Note 4 N910C lolipop in tw recovery still boot loop? because i want to root it .send me a maasage thank you
Anyone?
Did you flash a kernel for your variant after flashing the ROM?
No but that is my next move today, had a feeling it might be the problem, I'll try it and report back.
Oj5 bl doesn't let the flash of older rom even lp 5.1.1 older then oj5 but erobot 12 and 13.4 are newest then oj5 so it must be something else like the supersu v2.65 have issues with some costum kernels try to flash v 2.45
radium56ad said:
Oj5 bl doesn't let the flash of older rom even lp 5.1.1 older then oj5 but erobot 12 and 13.4 are newest then oj5 so it must be something else like the supersu v2.65 have issues with some costum kernels try to flash v 2.45
Click to expand...
Click to collapse
Will try that, thanks. On a side note, flashed custom kernel after flashing the ROM and nothing same bootloop.
try this! http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132
migsguerra said:
guys help me im having bootloop because i was trying to install the su suser .in my note 4 Note 4 N910C lolipop in tw recovery still boot loop? because i want to root it .send me a maasage thank you
Click to expand...
Click to collapse
Had the same problem, solved it by flashing cf auto root using ODIN.
can't you just flash the previous rom again??
Enter your recovery and flash your "old" rom