I've tried 3, all just boot loop. I can Odin back to 4.1.2 and all is good. But, no 4.4 roms will take after Odin'ing MJ9.
Any thoughts?
DatacomGuy said:
I've tried 3, all just boot loop. I can Odin back to 4.1.2 and all is good. But, no 4.4 roms will take after Odin'ing MJ9.
Any thoughts?
Click to expand...
Click to collapse
I'm having the same issues. Driving me crazy!
Looks like it was a kernel issue, I installed AGNi's kernel and got them to boot. I was coming from MJ9.
http://forum.xda-developers.com/showthread.php?t=2607652
pdtp said:
Looks like it was a kernel issue, I installed AGNi's kernel and got them to boot. I was coming from MJ9.
http://forum.xda-developers.com/showthread.php?t=2607652
Click to expand...
Click to collapse
Oh, NICE...
I'm on 4.1.2 after just re-Odin'ing back to stock again since none of the ROMs would work.
So i should be able to run casual, then flash MJ9, then flash this, then flash a ROM and be good to go?
Actually.. ROM first, then kernel right?
DatacomGuy said:
Actually.. ROM first, then kernel right?
Click to expand...
Click to collapse
yeah, ROM first
Related
So I followed this guide to root my phone, since I'm on Virgin Mobile in Canada.
My only question is how the heck do I install custom ROMs or Kernels to the phone? I honestly can not figure that out.
Are there any supported by this phone? I9100-M, and I keep getting the error of:
Code:
E: signature verification failed
no matter how much I try updating via CF-ROOT.
So you've flashed your CF Root kernel via Odin? Green light, good to go?
When you boot to recovery what's the version #? Which kernel/rom are you trying to flash?
The M is the same as the "International version", it just came with Bell/Virgin firmware and an M tacked onto the end of the model #; you're in the right section.
mudferret said:
So you've flashed your CF Root kernel via Odin? Green light, good to go?
Click to expand...
Click to collapse
Indeed I have, good sir. I've got Root abilities [LOVE IT] and I can do what I please... well, minus the custom ROMs.
When you boot to recovery what's the version #? Which kernel/rom are you trying to flash?
Click to expand...
Click to collapse
Trying to flash to? Or have at the moment? At the moment, booting to recovery gives me Android System Recovery 3e. The ROM I'm trying to flash is MIUI, Drunken Clam or MIUI based off CM9 though later on, if I don't like either, I was thinking I might flash a lighter ROM if they have worse battery life then the stock ROM.
The M is the same as the "International version", it just came with Bell/Virgin firmware and an M tacked onto the end of the model #; you're in the right section.
Click to expand...
Click to collapse
Yep, everyone keeps telling me that's the case. So I figured that I'm no noob to forums, just a noob to XDA.
plauge_myr said:
At the moment, booting to recovery gives me Android System Recovery 3e...
Click to expand...
Click to collapse
That's the problem. That's the stock recovery, useless for flashing anything. I'm guessing you messed up the step to get rid of the yellow triangle and flashed a complete stock kernel back on rather than the zimage. As you've noticed you retain root, but don't have Clockwork Mod Recovery. You'll have to flash a kernel via Odin again. Good luck.
mudferret said:
That's the problem. That's the stock recovery, useless for flashing anything. I'm guessing you messed up the step to get rid of the yellow triangle and flashed a complete stock kernel back on rather than the zimage. As you've noticed you retain root, but don't have Clockwork Mod Recovery. You'll have to flash a kernel via Odin again. Good luck.
Click to expand...
Click to collapse
Well damn! That would do it! Heh, well thank you for the input and I'll try again then.
plauge_myr said:
Well damn! That would do it! Heh, well thank you for the input and I'll try again then.
Click to expand...
Click to collapse
It was only a few short months ago that I was completely confused by the process
mudferret said:
It was only a few short months ago that I was completely confused by the process
Click to expand...
Click to collapse
I'm still getting the same error even after reflashing it though, and Android System Recovery 3e is still showing up, even though I'm flashing it with the proper ROM...
I think you can try on some kernel other than CF-Root to achieve root. I had rooted my phone by flashing the speedmod kernel using odin. Then you can flash custom ROMs from the CWM recovery.
I went and installed the MIUI drunken clam since I re-rooted it and put on the insecure ROM on. I don't particularly like it, but I'm thinking either try something with a better battery life then stock (way better would be nice, I've got two batteries on the way for the phone, but no clue when they're showing up.) or simply go back to stock and start removing thing via Titanium Backup.
What would be the recommended ROM if you want the most out of your battery life? Are there anything I should watch out for on said ROM? Or what ROM would you recommend, personally? I've been looking for a good one that's nice enough for day to day, but not sickeningly sweet or something.
Going to a non-Samsung ROM can be a big jump. Especially considering that the MIUI you flashed is based on CM9 which is still "experimental", not all phone functionality has been successfully ported yet.
I'd recommend a Samsung based ROM first; which one? Not sure, I haven't been on a Samsung based ROM for a few months. I preferred lighter weight ROMs; the GingerMOD was good and is similar to an AOSP based ROM. People seem happy with Hyperdroid as well; it's not lightweight, but is a great ROM from what I've heard.
Stock to CM9/AOSP/MIUI is a big jump, and can be unforgiving at times, you have to be familiar with getting yourself out of trouble. All of the Samsung ICS leaked ROMs are also buggy as hell at the moment.
My Galaxy Player bricked since I flashed "CF-ROOT for GT-I9000"(Because I selected the wrong file)
The screen touch response is reversed and the touch button doesn't work!
Please help me what to do!!!
The problem was solved!! Thanks Samwes's help
error01671 said:
My Galaxy Player bricked since I flashed "CF-ROOT for GT-I9000"(Because I selected the wrong file)
The screen touch response is reversed and the touch button doesn't work!
Please help me what to do!!!
Click to expand...
Click to collapse
Wait...so you flashed an I9000 kernel and it still booted? Maybe I will try investigating if we could just port kernels from the galaxy s phones.
But anyway..just boot into download mode and reflash one of the custom kernels for the 4.0.
Sent using Tapatalk
klin1344 said:
Wait...so you flashed an I9000 kernel and it still booted? Maybe I will try investigating if we could just port kernels from the galaxy s phones.
But anyway..just boot into download mode and reflash one of the custom kernels for the 4.0.
Sent using Tapatalk
Click to expand...
Click to collapse
I flashed STeVEs-3.0-EU kernel but it didn't fix my problem!!
I will post video and you can see the problem on my device.
I think a dev should make a sticky to bricks. They are coming up too often now.
Also if it booted, it's not bricked.
Chris4evernoob said:
I think a dev should make a sticky to bricks. They are coming up too often now.
Also if it booted, it's not bricked.
Click to expand...
Click to collapse
But I flash any stock rom or custom rom,even any custom kernel,can't fix my device.
Why would you flash a i9000 kernel on a YP-G1 ? What kernel did you flash, we're going to need that kernel to see what happened!
pmdisawesome said:
Why would you flash a i9000 kernel on a YP-G1 ? What kernel did you flash, we're going to need that kernel to see what happened!
Click to expand...
Click to collapse
I downloaded "CF-Root-JP6-v1.2-Busybox-1.17.1.zip"from http://forum.xda-developers.com/showthread.php?t=788108
The file which I prepared for my i9000,but when I' m going to flash my YP-G1 kernel,I selected the wrong file.
get odin, stock firmware, and flash the stock firmware with odin
I have the same problem since I've flashed a kernel for the Galaxy S.
My Galaxy player has not booted.
I have flashed Steves ROM and since that I have the same problems.
I've found so far no solution.
The flash of the stock firmware did not help.
I have also tested other ROMS.
Did you're player run 2.3 or 2.2 stock, because that would make a difference. If it ran 2.2 then therea you're problem isolated.
Infact I just noticed you said touch button, so are you sure its not US?
Sent from my YP-G70
Seresta said:
get odin, stock firmware, and flash the stock firmware with odin
Click to expand...
Click to collapse
I tried,but it doesn't work.
Samwes said:
Did you're player run 2.3 or 2.2 stock, because that would make a difference. If it ran 2.2 then therea you're problem isolated.
Infact I just noticed you said touch button, so are you sure its not US?
Sent from my YP-G70
Click to expand...
Click to collapse
The touch buttons that I mean is menu button and back button,not home button.
And I will try 2.2 stock,thanks.(I already ran 2.3 stock.)
error01671 said:
The touch buttons that I mean is menu button and back button,not home button.
And I will try 2.2 stock,thanks.(I already ran 2.3 stock.)
Click to expand...
Click to collapse
Which stock rom did you try?
zaclimon said:
Which stock rom did you try?
Click to expand...
Click to collapse
2.3.6 stock rom
Samwes said:
Did you're player run 2.3 or 2.2 stock, because that would make a difference. If it ran 2.2 then therea you're problem isolated.
Infact I just noticed you said touch button, so are you sure its not US?
Sent from my YP-G70
Click to expand...
Click to collapse
I just flash 2.2.1 stock rom and it fix my device!!! Thank you very much!
Without your advice,I won't flash into 2.2!(Because 2.3 is much better!)
Can you send me the link?
Gigadroid said:
Can you send me the link?
Click to expand...
Click to collapse
Here is the 2.2.1(INTL)stock rom download link : http://dl.dropbox.com/u/60441441/G1ZSKC5-REV01-PDA-low-CL976041.tar.zip
The link is from http://forum.xda-developers.com/showthread.php?t=1531850
Thank you.
I'll try it.
EDIT: Hooray, it worked.
Yes in this case when flashing with odin 2.2.1 rom is better at resolving problems then 2.3.6.
Edited: problem solved. See my last post to the solution I found.
I don't know if it works in Odin cause I haven't tried it, but there is a link somewhere in the Skynote port ROM thread that has the modem as a zip flashable in recovery. It DOES work as I am on MJ9 on Paranoid Android 4.4.2.
Numzi said:
I don't know if it works in Odin cause I haven't tried it, but there is a link somewhere in the Skynote port ROM thread that has the modem as a zip flashable in recovery. It DOES work as I am on MJ9 on Paranoid Android 4.4.2.
Click to expand...
Click to collapse
Well from "Krowley3's" Sophisticated ROM thread, you can flash it via ODIN with this file: http://www.androidfilehost.com/?fid=23269279319198557
Thanks for letting me know its working for you on PA.
bigw34 said:
Well from "Krowley3's" Sophisticated ROM thread, you can flash it via ODIN with this file: http://www.androidfilehost.com/?fid=23269279319198557
Thanks for letting me know its working for you on PA.
Click to expand...
Click to collapse
No problem. Try flashing it then. I'm sure it should work.
Well I ended up flashing the file...the first time was through TWRP and it didnt change anything. The next time I tried through ODIN and it gave me an "unknown baseband" that a lot of people are reporting. I ended up with no data, had to flash back to stock and start all over again using vramc3.
Numzi, how did you get it working on your phone?
I'm running the new firmware with CM11. I flashed it in cwm and it works fine
tgyberg said:
I'm running the new firmware with CM11. I flashed it in cwm and it works fine
Click to expand...
Click to collapse
Maybe ill try switching over to CWM and try it. Did you notice better wifi/LTE coverage with the new firmware?
bigw34 said:
Maybe ill try switching over to CWM and try it. Did you notice better wifi/LTE coverage with the new firmware?
Click to expand...
Click to collapse
It's about the same
For anyone reading this thread and had trouble like me with the modem, try flashing this: https://dl.dropboxusercontent.com/u/48640/android/VRUEMJ9_zif.zip
I flashed it using latest twrp on slim rom/slimkat 4.4.2, and it worked perfectly.
Thanks to "zif" at this thread: http://forum.xda-developers.com/showthread.php?t=2577809&page=6
This is a recovery flashable, stock boot.img, pulled from freeza's stock rooted rom, located here. It's completely unchanged from stock, I just made it flashable. After flashing, You may, or may not have to modify your build.prop to set secure storage to "false." See freeza's thread here, for more info on this.
Use this at your own risk, I assume no responsibility.
NH7 Kernel: NH7
MD5: 610f8d02cea6f2c1641da926ae07a7c4
Very nice! Thank you sir.. :thumbup:
Sent from my SM-N900P using XDA Free mobile app
LouRock said:
Very nice! Thank you sir.. :thumbup:
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
No prob, glad it helps.
Awesome thank you so much
What would be the benefit Of this
busventinc said:
Awesome thank you so much
Click to expand...
Click to collapse
You're welcome
uknow said:
What would be the benefit Of this
Click to expand...
Click to collapse
Numerous, for example, it will allow you to return to the stock kernel, for troubleshooting purposes, if you expect an incompatibility, or issue with a custom kernel, without having to flash an entire stock rooted rom, or downloading an entire rom, just for the boot image.
By the way I want to thank you for this its a blessing we have ppl who do this for us with that said im a noob should I flash this I have the nh7 modem I flashed the nh7 stockish rom then I restored my backup for sacs moar rom
i flashed the baseband/modem and that loaded fine. i then tried to flash the kernel and get stuck in a boot loop even after i tried the file to set to false. what can i be doing wrong?
anth75 said:
i flashed the baseband/modem and that loaded fine. i then tried to flash the kernel and get stuck in a boot loop even after i tried the file to set to false. what can i be doing wrong?
Click to expand...
Click to collapse
Can you provide more info. If you were in a bootloop, how did you set the file to false? Did you flash the fix, in freeza's OP? If so, that's likely the problem. That build.prop is for a previous version.
I did flash the fix. How else can I get the new modem flashed without bootlooping? My modem/baseband is NH7. Just can get the NH7 stock kernel on without looping
anth75 said:
I did flash the fix. How else can I get the new modem flashed without bootlooping? My modem/baseband is NH7. Just can get the NH7 stock kernel on without looping
Click to expand...
Click to collapse
I'm not sure what the issue is, I haven't run into this yet. To be absolutely clear, are you flashing the wifi/secure storage fix, from freeza's thread?
Yes as I read it would fix the boot loop. I tried without it and had no luck either.
anth75 said:
Yes as I read it would fix the boot loop. I tried without it and had no luck either.
Click to expand...
Click to collapse
That's the problem. That fix is fo MJ4. Also, what rom are you on? I'm not sure if the NH7 kernel, is compatible with NC5 roms. I know for a fact, NC5 kernels, are incompatible with NH7 roms (no display).
Your best bet is to Odin the NC7 tar, if you want all NC7, or Odin NC7, and restore your TWRP backup, of your previous rom. Your baseband, will be NH7, but your kernel will be whatever was included in your previous/preferred rom.
I'm on sacs rom. My baseband/modem is currently NH7 and have no problems
Im also on sacs rom and nh7 kernel want make it past samsung screen just a heads up keep a updates back up before trying this
uknow said:
Im also on sacs rom and nh7 kernel want make it past samsung screen just a heads up keep a updates back up before trying this
Click to expand...
Click to collapse
Sacs rom is NC5 based. Use an NC5 compatible kernel.
LMMT said:
Sacs rom is NC5 based. Use an NC5 compatible kernel.
Click to expand...
Click to collapse
Yeah I was reading your post and you said you wasn't sure so I check lol but anyways do you know where a stock nc5 kernel zip is?
uknow said:
Yeah I was reading your post and you said you wasn't sure so I check lol but anyways do you know where a stock nc5 kernel zip is?
Click to expand...
Click to collapse
Yep, http://forum.xda-developers.com/showthread.php?p=51841373
leankernel: http://forum.xda-developers.com/showthread.php?p=46569112
There is also the great freeza's beastmode kernel: http://forum.xda-developers.com/showthread.php?p=47338337
Just so there no confusion, I'm using a previous thread to keep the litter at a minimum.
Is this possible? If I understand correctly, the locked bootloader prevents us from flashing a custom recovery and a custom kernal and cm11 and similar roms all run custom kernal. .is it possible to flash the rom and then boot into download mode and Odin a stock kernal or would it be incompatible with the rom? Any help would be appreciated. I really want cm11, aokp, aosp or something of the sort. The Google rom just isn't for me.
brd912 said:
What's the difference? Can they be flashed with safestrap? Out of the roms I've scanned through the only one I really like that I knew for sure could be flashed with safestrap is hyperdrive. I'm just wondering what my options are..anyone?
Click to expand...
Click to collapse
Unified builds are just builds that can be flashed on any carrier.
So they will work for our S4?
brd912 said:
So they will work for our S4?
Click to expand...
Click to collapse
Yep, you will still need an MDK bootloader for aosp/aokp.
Triscuit said:
Yep, you will still need an MDK bootloader for aosp/aokp.
Click to expand...
Click to collapse
Ahh. Thanks
Bump for the edit on the post. Figured I'd just rename the thread instead of creating a new one.