noob here,
I am very new to android, I have a Galaxy S4 SCH-i545, About a month ago I rooted the phone and flashed Hyperdrive 7 on it, it worked great, then when version 8 came out, upgraded. Now I cant turn off the phone or restart it because it stay in the custom boot screen, One thing I noticed is that the baseband (I545VRUAMDK) and build (JDQ39.I545VRUAME7) are different, is this normal? thanks
Yes, this is normal. The rom you're on is an ME7 base, but your firmware (modem) is still your stock MDK modem. This shouldn't cause you a bootloop.
thanks
Erievon said:
Yes, this is normal. The rom you're on is an ME7 base, but your firmware (modem) is still your stock MDK modem. This shouldn't cause you a bootloop.
Click to expand...
Click to collapse
Any idea whats causing the bootloop? thanks
Related
I've spent the last 2 days trying to fix my mistake. I have the GS2 ATT version, and I didn't realise there was a difference between that and the GTI9100 S2.
I wanted to give some tips I learned on how to recover your phone if you make this mistake.
First, here are some posts you'll want to look at:
http://forum.xda-developers.com/showthread.php?t=1286432 - Stock firwmware
http://forum.xda-developers.com/showthread.php?t=1285823 - Clockworkmod for the ATT
http://forum.xda-developers.com/showthread.php?t=1286192 - Cyanogenmod for our phones.
Using Odin and the stock firmware, you can recover your phone to a 95% working state. Once I got my stock firmware on there, I found that while making calls my phone made no sound, and the mic didn't work. The mic did work when I wasn't making calls though.
I reflashed the modem.bin file found on the stock firmware, not sure if its required but that is what I did first. Then, I unpacked the rooted stock firmware, and flashed JUST THE zImage file. After doing this, I rebooted, and my calls were working again.
After that, I installed the correct version of Clockworkmod, and then CM7 nightly. Now everything seems to be running great on my phone.
Hope this helps someone out there,
-Orbital
Good job thanx man.
Sent from my SAMSUNG-SGH-I777 using XDA App
Been awhile since I messed w/ android. I forgot about the different models myself until I realized I was spending half my day in the wrong section
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Alucardis666 said:
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Click to expand...
Click to collapse
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Alucardis666 said:
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Click to expand...
Click to collapse
Those are NOT for our version of the GS2, International only. Our version is here in the development forum.
Sent from my SGH-I777 using xda premium
Yes, it will return a status error 7 which means it's unmatched. Ask me how I know. I flashed international roms last night and used this fix to get me good again.
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
connexion2005 said:
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
Click to expand...
Click to collapse
The simple thing would be to change out the sec_touchkey.kl with rootexplorer and take the sec_touchkey from system/usr/keylayout should fix the i9100 rom to work with the i777. Seeing as how this worked for the Captivate *i897* for jvr, jvs, and jvt darkyrom releases and I would assume that it would work.
daraj said:
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
Click to expand...
Click to collapse
Personally I would think that you had a bad flash? Did you flash through Odin or CWM? From what I have been reading the gb bootloaders between the i777 and i9100 are different and I can see if you used a custom i9100 rom flashing via cwm could cause that. Since I am not too sure on the sgs2 if the differences between the euro models versus the carrier locked, the Kernel will not fix the button mapping, I learned this with the captivate when I switched over to using DarkyRom jvr and jvs builds since they were the most stable of GB for the i897 captivate. Plus if you are going to run a i9100 rom, I am sure the modem will not work with the att kernel. Especially if the situation with the cappy is any indication that att kernel needs att modem and i9000 kernel needs i9000 modem. I will be able to know more as soon as I get my i777 tomorrow.
HTH,
Charlie
Does anyone know how to remove the i9100 splash screen?
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
spbluffmaster said:
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
Click to expand...
Click to collapse
wipe data/factory reset
tried that three times... didnt help..
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
DiscipleDOC said:
Does anyone know how to remove the i9100 splash screen?
Click to expand...
Click to collapse
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1311975
re: get rid of i9100 boot logo
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
Use a download mode jig or flash entropy 512's stock TAR kernel with Odin from the link below.
http://forum.xda-developers.com/show....php?t=1286432
Good luck!
highaltitude said:
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
Click to expand...
Click to collapse
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Entropy512 said:
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Click to expand...
Click to collapse
i messed up and flashed an i9100 rom and am having the call prob u described. can i just flash the modem or stock rooted kernel and be back to 100%? if so do i use odin and do i need to check the box for repartition or anything like that? thx in advance!!!
Which modem version is for the gingerbread for att? I noticed Im still running on UCLC or whatever 5. which is the same as ICS. Could this be causing me any service issues that ive been having? what version comes stock? cause I odin flashed back to stock att and its still stuck on version 5
hyelton said:
Which modem version is for the gingerbread for att? I noticed Im still running on UCLC or whatever 5. which is the same as ICS. Could this be causing me any service issues that ive been having? what version comes stock? cause I odin flashed back to stock att and its still stuck on version 5
Click to expand...
Click to collapse
1717UCLA1 is what you want. Should be available in the Modems thread in Development. Flash that in CWM and you're good to go.
Here it is: http://downloadandroidrom.com/file/GalaxyNote/modems/ATTNOTEUCLARADIO.zip
Yea I got it flashed Thanks!
Would running UCLA5 on GB cause any issues?
I am running stock 4.3 from here.
Before that I was trying out stock 4.4.2 from here.
4.3 seems to be running well but I still have the ND7 radio. I know this shouldn't necessarily be a problem, but I would like to try the MJ9 radio and see if my battery life improves.
To downgrade the radio from ND7 to MJ9, is it simply a matter of flashing VRUEMJ9_radio.zip in recovery?
Or are there any other additional steps I should take, such as "format /modem" or something similiar in Philz?
I would appreciate any input on this.
Rootabaga, I can't help you with your situation however am having an issue with my signal being intermittent,especially when I set up a hot spot. Could someone tell me what's a better radio to use than MJ9 or is there a better means to fix this issue...?
Can anyone shed some light on this?
Thanks
Rootabaga said:
I am running stock 4.3 from here.
Before that I was trying out stock 4.4.2 from here.
4.3 seems to be running well but I still have the ND7 radio. I know this shouldn't necessarily be a problem, but I would like to try the MJ9 radio and see if my battery life improves.
To downgrade the radio from ND7 to MJ9, is it simply a matter of flashing VRUEMJ9_radio.zip in recovery?
Or are there any other additional steps I should take, such as "format /modem" or something similiar in Philz?
I would appreciate any input on this.
Click to expand...
Click to collapse
Yes just flash the zip in twrp or CWM. FYI your battery life isn't going to get better by doing this.
DreamFX said:
Yes just flash the zip in twrp or CWM. FYI your battery life is going to get better by doing this.
Click to expand...
Click to collapse
In my experience, only way to go from ND7 baseband to MJ9 baseband is to flash the MJ9 firmware( rooted/unlocked) using ODIN. Trying flash the MJ9 baseband zip in recovery did not work for me.
DreamFX said:
Yes just flash the zip in twrp or CWM. FYI your battery life isn't going to get better by doing this.
Click to expand...
Click to collapse
Thanks for replying. You're probably right about the battery life. Maybe it was wishful thinking on my part. Now that I've had ND7 for a few weeks, battery life seems to be more like it used to be.
netma2k said:
In my experience, only way to go from ND7 baseband to MJ9 baseband is to flash the MJ9 firmware( rooted/unlocked) using ODIN. Trying flash the MJ9 baseband zip in recovery did not work for me.
Click to expand...
Click to collapse
Thanks. I already flashed the MJ9 firmware when I first went from 4.1.2 to 4.4.2. Are you saying I would need to flash the firmware again?
The main reason I now want to try it is because browsing the net on any browser over WIFI has gotten almost impossible with ND7. 4G is fine. I'm not sure if it is because of ND7 but I thought it might be worth a try.
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
II hace recently purchased a Samsung Galaxy S4 i9500 and I am now having sone issues.
I have installed Cyanogenmod, and now my mobile data, calls and texts no longer work.
How do I completely reset my phone to what it was out of the box?
Many thanks to anyone who can help!
lachlanmcnicol said:
II hace recently purchased a Samsung Galaxy S4 i9500 and I am now having sone issues.
I have installed Cyanogenmod, and now my mobile data, calls and texts no longer work.
How do I completely reset my phone to what it was out of the box?
Many thanks to anyone who can help!
Click to expand...
Click to collapse
Sounds like you might not have flashed the right rom or you need to use a specific modem version with it. Is your baseband version still showing in Settings / About Phone? You should have made a nandroid backup 1st, and then you would already have your way back to normal. Other than that, flash a stock based rom or use Odin and the official firmware to get back to stock. Don't let this minor set back scare you off from CM, but use it as an incentive to read a bit more about how to safely flash the rom.
es0tericcha0s said:
Sounds like you might not have flashed the right rom or you need to use a specific modem version with it. Is your baseband version still showing in Settings / About Phone? You should have made a nandroid backup 1st, and then you would already have your way back to normal. Other than that, flash a stock based rom or use Odin and the official firmware to get back to stock. Don't let this minor set back scare you off from CM, but use it as an incentive to read a bit more about how to safely flash the rom.
Click to expand...
Click to collapse
Somehow everything started working again a few days ago...