Today i flashed CM 11 with CWM and after rebooting the baseband and IMEI were gone. I tried to flash the baseband but nothing happened. I then tried to flash the stock rom touchwiz through ODIN and it failed. Now the phone reboots asking to connect to KIES and do a recovery which i can't perform.
Any clues about?
Thank you in advance,
Davide
you have back up of your phone..?
can you boot into recovery..?
which stock rom you tried to flash , 4.3..? 4.4
http://forum.xda-developers.com/showthread.php?t=2758855 See this might help you
caravaggio971 said:
Today i flashed CM 11 with CWM and after rebooting the baseband and IMEI were gone. I tried to flash the baseband but nothing happened. I then tried to flash the stock rom touchwiz through ODIN and it failed. Now the phone reboots asking to connect to KIES and do a recovery which i can't perform.
Any clues about?
Thank you in advance,
Davide
Click to expand...
Click to collapse
tnt4ever said:
you have back up of your phone..?
can you boot into recovery..?
which stock rom you tried to flash , 4.3..? 4.4
http://forum.xda-developers.com/showthread.php?t=2758855 See this might help you
Click to expand...
Click to collapse
Thanks for the prompt reply. The Rom I flashed is the 4.4.2 snapshot.
In the meantime i flashed this pit file from this link
http://forum.xda-developers.com/showthread.php?t=2137008
and now the CYM is back and working but still no baseband.
Is there any way i can reinstall the stock rom ? is the partition a problem?
I dont have a backup of the EFS folder (I made it once but i cant find it)
EDIT: CWM is installed and working
is your IMEI Same..?
i assume there are several reasons, it can be a simple fix by installing a stock 4.4 KK which will eliminate the problem you are facing, iin past week, i done alot of experiences on my bricked note 2, specially the failed PIT flashed, i tried couple of them but at the end the only thing turned the phone in right direction was stock KITKAT
you can find that in the the post i posted earlier.
i am 100% sure you will get your phone back to life.
also remember to when you are done flashing go to stock recovery and wipe data and cache. It is needed after re-partiton to form the partitions correctly
edit: best keep a nand of your current rom as well
4.4.2
https://mega.co.nz/#!2QRmCbyb!YkWs927BfvYxqL-vJiQHXkshqG3UtqHm4XIDbgLsEK0
best of luck
caravaggio971 said:
Thanks for the prompt reply. The Rom I flashed is the 4.4.2 snapshot.
In the meantime i flashed this pit file from this link
http://forum.xda-developers.com/showthread.php?t=2137008
and now the CYM is back and working but still no baseband.
Is there any way i can reinstall the stock rom ? is the partition a problem?
I dont have a backup of the EFS folder (I made it once but i cant find it)
EDIT: CWM is installed and working
Click to expand...
Click to collapse
tnt4ever said:
is your IMEI Same..?
i assume there are several reasons, it can be a simple fix by installing a stock 4.4 KK which will eliminate the problem you are facing, iin past week, i done alot of experiences on my bricked note 2, specially the failed PIT flashed, i tried couple of them but at the end the only thing turned the phone in right direction was stock KITKAT
you can find that in the the post i posted earlier.
i am 100% sure you will get your phone back to life.
also remember to when you are done flashing go to stock recovery and wipe data and cache. It is needed after re-partiton to form the partitions correctly
edit: best keep a nand of your current rom as well
4.4.2
https://mega.co.nz/#!2QRmCbyb!YkWs927BfvYxqL-vJiQHXkshqG3UtqHm4XIDbgLsEK0
best of luck
Click to expand...
Click to collapse
Exactly. Flashing the official stock rom based on kitkat 4.4.2 (which has been released few days ago I believe) solved the problem. I'll try to flash CM tomorrow (tonight get.cm is not reachable and can't download the android app).
Thank you!
Hello
very happy to see your problem is fixed
enjoy your galaxy note 2
this community is very helpful for every one my friend
caravaggio971 said:
Exactly. Flashing the official stock rom based on kitkat 4.4.2 (which has been released few days ago I believe) solved the problem. I'll try to flash CM tomorrow (tonight get.cm is not reachable and can't download the android app).
Thank you!
Click to expand...
Click to collapse
Just wanted to ask you something. I installed the Nordic version of the latest Android update which is at the moment the only one available and I have the impression that the voice quality is not that good. I was wondering if this may depend on the baseband version installed on this one. I'm from Italy and kitkat 4.4 is still not available in my country. Flashing a different baseband may change the situation? If so, Is there a baseband more compatible with this touchwiz version and the Italian telco providers?
Thank you again,
Davide
Sent from my GT-N7105 using XDA Free mobile app
Related
Recent stability update is not allowing the flashers to downgrade or limited to only roms with particular modems as it is causing to corrupt the IMEI.
Though our clever developers have found many solutions it has become a hindrance to many of flashoholics like me.
What do you think? Can there be a permanent solution to this? and most important why Sammys have done this. I do not think this is some kind of bug. It is done on purpose,like preventing people from frequenting flashing?
what do you say?
I agree with you, efs problem and partition table corrupt are such problems which make people to think before flashing
Sent from my GT-N7100 using Tapatalk 2
I am not flashing any rom for the moment.
Do asop roms suffer from efs problem?
After an update my IMEI has changed from what is under battery cover to something like 004999xxxxxxxxx after which I can't make phone calls any more , after checking I've discovered that the EFS file doesn't contain the IMEI anymore, when happened this my phone was not rooted so obviously I have no backup.I've flashed back the original ROM many times but it's still the same.
Do you think there is a way to find a solution to this?
Please give detailed description of what happened like which was previous rom and which rom you are now on and trying to flash....
Sent from my GT-N7100 using Tapatalk 2
It was on stock xxDMB5 wanted to try the latest Nordic Nee downloaded it from sammobile and flashed with Odin PC.everything went well .however didn't like it so reverted back to the stock DMB5 only than is that I've noticed that my IMEI had changed and can't make any calls. Now I am on the latest xxxDMC3.
hagba said:
It was on stock xxDMB5 wanted to try the latest Nordic Nee downloaded it from sammobile and flashed with Odin PC.everything went well .however didn't like it so reverted back to the stock DMB5 only than is that I've noticed that my IMEI had changed and can't make any calls. Now I am on the latest xxxDMC3.
Click to expand...
Click to collapse
You should read this
http://forum.xda-developers.com/showthread.php?p=43037578
[N7100 All in 1]Stock ROM +How to Root+Reset counter+MobileOdin+Xposed
Sent from my GT-N7100 using Tapatalk 2
hagba said:
It was on stock xxDMB5 wanted to try the latest Nordic Nee downloaded it from sammobile and flashed with Odin PC.everything went well .however didn't like it so reverted back to the stock DMB5 only than is that I've noticed that my IMEI had changed and can't make any calls. Now I am on the latest xxxDMC3.
Click to expand...
Click to collapse
Latest update is not allowing the downgrade of modems, so please reflash the nordic rom so that atleast you will have your IMEI back. I was on ARHD 17.0 , tried Omega rom which is DME6 and reverted to ARHD 17.0. In the process I lost IMEI. So I reflashed Omega and I had my IMEI
NOw ARHD 18.0 is also DME6 and I can flash it but not below that
Ok will try it.
Just one question please,do I need CWM installed on my rooted phone to flash a modem?
hagba said:
Just one question please,do I need CWM installed on my rooted phone to flash a modem?
Click to expand...
Click to collapse
No, you can flash modem through pc odin or mobile odin only the modem file should be tar file
Sent from my GT-N7100 using Tapatalk 2
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
*Note* If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone. The Stock ROM contains the Bootloader which should never be downgraded. Fyi: the Bootloader is not the Baseband, the Baseband is just what Modem you're using.
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
bullet2binary said:
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
spongdangly said:
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
Click to expand...
Click to collapse
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
bullet2binary said:
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
exodus454 said:
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
Click to expand...
Click to collapse
I'm glad to hear that this seems to be the proper fix. That's odd that you were having trouble with 4.2 ROMs, but then again I'd been running 4.2 ROMs on my phone since they first started rolling out. It's kind of annoying that everyone's S3 seems to be slightly different then the next.
Yeah this was a weird one all right. Just glad this post had a solution
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
glad i found this otherwise my first noob post would have truly been a noob move. Thanks wouldn't have guessed that fix for a few days at least.
verified it works. but it did require some weird time dealing with a bootloop issue on stock recoveries. had to find a .tar version of CWM to flash via odin for the final result.
Still Stuck at Splash Screen after trying to upgrade to 4.3
Background:
I had been running task's rom since 4.1.x. Upgraded to 4.2 with not problems and I kept the rom current. Tried to upgrade to 4.3 and that is where the problems started. It appeared to work, saw that Google was updating a number of apps but then then I kept getting error messages regarding various about various processes stopping unexpectedly. Rebooted the phone and it came up with Task's kernel splash screen where it remains frozen.
I can get into TWRP (v2.3.3.1) recovery and into Download mode.
I have tried wiping Cache and Dalvik Cache
I have wiped System
I have done a Factory Reset
I have Formatted Data
I have used Odin twice to get back to stock (I747UCDLK3) and both times it says "passed."
When I try to reboot it, however, it comes back to Task's Kernel splash screen (I do not see the Samsung screen)
Any help or suggestions would be great.
UPDATED: Found an older update from April and was able to restore it. Still wondering why 4.3 wouldn't take.
This Works
I was skeptical, but this actually works! Now running Task's 4.3 on my bell i747m without any problems!
Thanks for the tip OP :good:
spongdangly said:
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
I hope I posted this in the right section but apologies if it's not.
Click to expand...
Click to collapse
If this works you're a life saver! I've been posting around 4.3 threads about this for weeks and no one came up with a decent answer....
Tried reflashing stock with root but didn't work... i'll try your way, see if that works
Gonna try this tonight!!!
Thanks!
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Solved
Thanks, also works for i727 skyrocket
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Kastro1784 said:
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Click to expand...
Click to collapse
spongdangly said:
1. Use Odin to flash the latest stock ROM
Click to expand...
Click to collapse
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
spongdangly said:
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
Click to expand...
Click to collapse
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Kastro1784 said:
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Click to expand...
Click to collapse
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
spongdangly said:
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
Click to expand...
Click to collapse
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
shortydoggg said:
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
Click to expand...
Click to collapse
I'm sorry that I'm unable to help. As I had mentioned I have a Canadian Rogers phone (since I'm in Canada) so I don't know what's going on with the AT&T Stock 4.3 ROMs other then the fact that lots of people are having problems.
If you never flashed or did an OTA update to 4.3 then I'd suggest flashing the Stock 4.1.2 ROM. That or try what Ozark_8125 did since it saves you a couple steps (just make sure that LK3 isn't an older ROM than the one you were on).
If you're unsure what bootloader is currently on your phone and your phone is rooted I'd highly recommend downloading one of the many Root Check apps from the Play Store to verify which bootloader you're currently on.
*Note* I don't know which bootloader is for the 4.1.2 AT&T ROM nor do I know which bootloader came with the 4.3 ROMs. I'm sure a simple search would answer that for you.
Ozark_8125 said:
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Click to expand...
Click to collapse
Samsung fixed my phone free thanks for the help
Sent from my SAMSUNG-SGH-I747 using Tapatalk
ok so as you all know ive been having this problem with my note 2 eversince i flashed a mk4 rom and updated prl firmware version i guess it updated my baseband and all sorts of things i flashed the odin wifi fix and it made mk4 wifi work and everything was glee.. well i wanted aosp 4.4.2 back because it was simply gorgious i guess i had a thing for it. well i went to flash it after wiping factory data reset and after it flashed i let it run for over 30 minuts and it never made it past the cyanogenmod boot screen so i assumed it was a bootloop or bad download. my answer to this is i believe its the baseband or prl version not letting me run this. because before i ran mk4 and did all the updates i could always revert back to 4.4.2 without a problem now all the sudden i cant even load any aosp 4.4 rom. i can load all of 4.2.2 4.1.2 all those aosp roms but not the newest rom which is frusterating. if anyone has a fix or a recamended solution please help me because i have done just about every factory reset availible such as billiards back to stock and some other one. both not helping.
below here is the data i have recorded from my phone
PRL 2011
Baseband L900VPAMC2
PRL and baseband should both be irrelevant. Your problem is most likely a corrupt download. Have you checked hash sums?
Skripka said:
PRL and baseband should both be irrelevant. Your problem is most likely a corrupt download. Have you checked hash sums?
Click to expand...
Click to collapse
i have redowloaded roms 2x and still no luck i reset the phone back to stock 5 times and still no luck it still bootloops makes me wonna sell the phone and be done with samsung.i should of never did the 4.3 rom because it gave me nothing but problems. i downloaded another aosp rom to my internal sd to see if my sd card was currupt and it did the same Bootloop. i have no clue what it could be. ive used CMW and tWrp and both did the same
How many times you've downloaded is completely irrelevant. You've either verified the md5 hash and thereby confirmed your downloads are good or you have not. I presume you have yet to do so.
Before any other steps can be advised you have to do that 1st basic step.
The download is good
im not sure what to do about this stupid problem but its aggrivating me to no end. ive done just about everysingle thing there is to make this work but it fails
zachdees said:
The download is good
im not sure what to do about this stupid problem but its aggrivating me to no end. ive done just about everysingle thing there is to make this work but it fails
Click to expand...
Click to collapse
One question...your baseband says MC2, did you unroot at any point following the MK4-upgrade (and wifi "fix") back to MC2? I have a theory, if you have not unrooted to MC2 firmware, and that is just because you didn't update radios...you might not like it...
The MK4 radio works fine IME with 4.4 ROMs FWIW.
i chose the oldest return to stock from billiards. i wanted to see if that fixes anything and it doesnt do squat. i just wonna figure out a resolution to this mess. my current baseband and prl and firmware version are
About device_______
Software version
L900VPALJC
Hardware version
L900.09
Baseband version
L900VPALJC
PRL IS STILL 2011
Device status custom
i did everysingle return to stock possible today and when i flash with either twrp philz recover cmw i still get bootloop. it doesnt load any further than the Samsung logo,
this leads me to belive that i have no clue
zachdees said:
i chose the oldest return to stock from billiards. i wanted to see if that fixes anything and it doesnt do squat. i just wonna figure out a resolution to this mess. my current baseband and prl and firmware version are
About device_______
Software version
L900VPALJC
Hardware version
L900.09
Baseband version
L900VPALJC
PRL IS STILL 2011
Device status custom
i did everysingle return to stock possible today and when i flash with either twrp philz recover cmw i still get bootloop. it doesnt load any further than the Samsung logo,
this leads me to belive that i have no clue
Click to expand...
Click to collapse
Crap...you just shot down my working theory.
In flashing 4.4 builds, you're using complete wipes? What GApps package are you using? ParanoidAndroid 4.4 Apps?
im doing a complete wipe and flashing the rom first to see if it even boots. and no go.
This doesnt make sense at all and makes me revert back to the baseband theory. i think somthing with the version of my phone has somthing to do with it.
the wifi patch wasnt the problem the recovery isnt the problem the only think i can think of is my phone is corrupt and wont flash 4.4.2 roms which aggrivates me. i want to get to the bottum of this
literally any aosp 4.4.2 rom bootloops.
the only one that booted up fine was omni rom and it didnt even have mobile data or signal seemed like it was for att or a gsm company because it had no support for my phone.
if i could just get ahold of a 4.4.2 kernal such as carbons trinity kernal or pretty much any 4.4.2 flashable kernal i think i could fix it as it seems that might also be the case
Did you try wiping your internal memory? I had a similar problem once, that was the solution.
Sent from my SPH-L900 using Tapatalk
zachdees said:
literally any aosp 4.4.2 rom bootloops.
the only one that booted up fine was omni rom and it didnt even have mobile data or signal seemed like it was for att or a gsm company because it had no support for my phone.
if i could just get ahold of a 4.4.2 kernal such as carbons trinity kernal or pretty much any 4.4.2 flashable kernal i think i could fix it as it seems that might also be the case
Click to expand...
Click to collapse
The 2.05b kernel of Plasma works fine with Omni. I've been using Omni builds for the last full month on my L900. Baseband is MK4 and PRL here is 2006.
No radios working sounds like you were using TWRP and not CWM or PhilZ recovery to a T. Maybe the latest TWRP has fixed its compatibility problems with 4.4+, but last I tried using TWRP to flash any 4,4 build-all it got me was no wifi/cell service. Be sure to use the recommended Paranoid Android GApps package for 4.4 with Omni.
Could you provide me with a link to the kernel that will work with cyanogen mod omni doesn't have data or mobile service
I have the philz
I don't flash any Google apps until i see that the rom is working which I've had no success. The weird thing with omni is that it doesn't even support sprint it only supports gsm
zachdees said:
Could you provide me with a link to the kernel that will work with cyanogen mod omni doesn't have data or mobile service
I have the philz
Click to expand...
Click to collapse
Plasma 2.05b0 can be found here, select the version appropriate to your device:
http://forum.xda-developers.com/showpost.php?p=48991763&postcount=866&nocache=1&z=8858325940594172
zachdees said:
I don't flash any Google apps until i see that the rom is working which I've had no success. The weird thing with omni is that it doesn't even support sprint it only supports gsm
Click to expand...
Click to collapse
Something has to be bizarre with your handset. Seriously, there's no other way to describe it. OmniROM for L900 is NOT GSM only, something in your flashing got altered in the middle of all your flashing. See my screencaps below if you don't believe me.
My only theory is that that "wifi fix" scrambled something in your radio for AOSP 4.4 ROMs....and that whatever it is isn't purged by a normal flash of a new/old baseband. It can't be the PRL as that is irrelevant and if you had a bad PRL it wouldn't work even under stock ROMs, and the baseband shouldn't matter but as you can see below I'm on baseband MK4 and I work fine.
let me revert back to stock one more time and do the 4.3 update and get the latest baseband version and ill report back to you after rooting and trying the omnirom or cm ok? i dont have a clue what the hell is going on as of now but its boggling my mind
OK so I'm on the latest baseband I flashed cm and no go kept sticking at the cm logo animation nothing else
I flash the kernel and it does the exact same. Fwi I'm using clockwork mod recovery
ok so i managed to get omni running without a problem the only issue is Root privilages. it doesnt have root. ive installes super su but it doesnt go into recovery and flash the binaries which doesnt make sense. ill try one more rom before i flash back to mk4 smoothest for a while. wish i could get this sorted out
zachdees said:
ok so i managed to get omni running without a problem the only issue is Root privilages. it doesnt have root. ive installes super su but it doesnt go into recovery and flash the binaries which doesnt make sense. ill try one more rom before i flash back to mk4 smoothest for a while. wish i could get this sorted out
Click to expand...
Click to collapse
Just flash supersu installable zip from recovery
i dont have the flashable zip
didnt see anything on the omni post either.
my question is why did this rom run without a flaw but when cm or pa flashes it has issues
Hey there,
recently, I pulled a really noob move - I flashed an i-9505 kernel (stock, plus recovery) on an i-9195 phone.
I had just flashed both phones a few days apart from each other and obviously,
something with the folders on my PC (or in my head^^) went wrong...
So, in short I have a phone right now, which wouldnt start and could not be flashed either by Odin
or via recovery. I have flashed serranoltexx recovery, Odin says "Pass", but I couldnt start it,
the screen says something about Image size being too large and shows "Secure Fail:Kernel".
Download mode does work, though.
Does anybody have a stock kernel for the 9195 variant? Since I couldnt flash via recovery,
I would prefer a tar.md5 file.
Or are there any other solutions to my problem?
AtzeOnAcid said:
Hey there,
recently, I pulled a really noob move - I flashed an i-9505 kernel (stock, plus recovery) on an i-9195 phone.
I had just flashed both phones a few days apart from each other and obviously,
something with the folders on my PC (or in my head^^) went wrong...
So, in short I have a phone right now, which wouldnt start and could not be flashed either by Odin
or via recovery. I have flashed serranoltexx recovery, Odin says "Pass", but I couldnt start it,
the screen says something about Image size being too large and shows "Secure Fail:Kernel".
Download mode does work, though.
Does anybody have a stock kernel for the 9195 variant? Since I couldnt flash via recovery,
I would prefer a tar.md5 file.
Or are there any other solutions to my problem?
Click to expand...
Click to collapse
What version of rom u have now ?
KitKat or JB ?
If Kitkat try this and see
If not just try to flash a full firmware from sammobile.
From error u got, Knox is active and tripped on your phone
And u also need a new recovery U can flash Phillz touch
Both files u can flash with Odin
SilviuMik said:
What version of rom u have now ?
KitKat or JB ?
If Kitkat try this and see
If not just try to flash a full firmware from sammobile.
From error u got, Knox is active and tripped on your phone
And u also need a new recovery U can flash Phillz touch
Both files u can flash with Odin
Click to expand...
Click to collapse
Thanks for the quick reply.
I will have a look into it this evening and report then...
So, I flashed the kernel and recovery and had no success so far.
Odin shows pass, though.
I was originally on 4.2.2 but decided then to flash some CM -
I am not sure anymore if it was 11, since I acted mostly in time pressure and out of desparation -
which worked quite fine. Since my friend, who wants to buy the phone, didnt want any modifications,
I tried to get back to stock.
After some different (and quite frankly useless) attempts, I read something about being on
KitKat and never going to return to lower versions. Too late for me...Could this be a problem?
So, no success with the KitKat kernel, is there the necessity to try a stock firmware?
I have tried so many before...
AtzeOnAcid said:
So, I flashed the kernel and recovery and had no success so far.
Odin shows pass, though.
I was originally on 4.2.2 but decided then to flash some CM -
I am not sure anymore if it was 11, since I acted mostly in time pressure and out of desparation -
which worked quite fine. Since my friend, who wants to buy the phone, didnt want any modifications,
I tried to get back to stock.
After some different (and quite frankly useless) attempts, I read something about being on
KitKat and never going to return to lower versions. Too late for me...Could this be a problem?
So, no success with the KitKat kernel, is there the necessity to try a stock firmware?
I have tried so many before...
Click to expand...
Click to collapse
I think your only bet is to try a stock kitkat rom unmodified ...
SilviuMik said:
I think your only bet is to try a stock kitkat rom unmodified ...
Click to expand...
Click to collapse
Will do...
Thank you so much man, it worked!
Phone is back to stock now, so my friend gotta deal with having an unrooted phone with KitKat
Thanks again and have a nice one!
New galaxy user, here its a s3 for ATT 4.4.2 i747CUCFNE4. I have rooted using the Cf Auto-Root method.
Along the lines of trying to flash a new task manager apk, (for I had to factory reset my phone because the original task manager was missing) I came across a thread that had s5 apps (settings apk) and tried flashing this apk(don't laugh I know.) Then I couldn't get my phone to boot through the standard setup wizard. So I tried booting into recovery and factory resetting my phone clearing cache, dalvik, and partition.
My biggest problem arose when I chose to format system from ghe recovery.
I know all this can be fixed with odin but I can't find a 4.4.2 os link, I have read I can't simply downgrade my os. A link to a 4.4.2 stock rom thread would be greatly appreciated. I also have the Ktoonsez kernel installed if that makes any difference.
AT&T never released a full 4.4.2 ROM. AT&T released 4.3 and 4.4.2 via OTA updates only.
Since you are on the NE4 bootloader, do not flash anything that will attempt to downgrade the bootloader or the modem. A mismatched modem/bootloader combination may cause other problems.
Have a look here: http://forum.xda-developers.com/showthread.php?t=2789917
Ok I just reviewed your link in your response but just to be clear I'm starting where it says step 3: stock deodex and root and finishing the walkthrough from there?
And also will this reset me to my factory kernel?? Either or it doesnt matter to me I'm still trying to find one that I find suitable.
And I appreciate the speedy response you've been a huge help.
If you just want to get your phone up and running, I would flash Philz and then CM11. Confirm the bootloader and modem then decide if a stock ROM would be best.
I am always paranoid when it comes to flashing bootloaders on the s3 so I prefer to know exactly whan my phone is running.
I have never used the thread I linked because I no longer have an s3 i747m. Infact, I haven't had my s3 for several months.
Ok and my last question is you can flash Philz and CWM 11 through odin?
Nevermind I see it now greatly appreciated
I hope it all goes well. With CM11, you will also need to flash Gapps via CWM as CM11 does not include certain apps such as the Play store.
Now odin wont recoginize or open any of my rom files. Li see the rom im trying to flash by name but when i click open it only opens the next folder instead of initiating the flash. I really just need someone who has a 4.4.2 stock rom in md5 format.(edited or not.)
As a last effort if i get no answer im going to try to downgrade to another os and reupdate to 4.4.2 right after. Ive been searching for days now all i see are guides from how to upgrade to a different os . If it does include 4.4.2 they only posted the update and not the entire rom.
And when i do find someone posting a full rom for 4.4.2 its either not for 747i or its not a md5 file so someone plz help me.
glyph2 said:
Now odin wont recoginize or open any of my rom files. Li see the rom im trying to flash by name but when i click open it only opens the next folder instead of initiating the flash. I really just need someone who has a 4.4.2 stock rom in md5 format.(edited or not.)
As a last effort if i get no answer im going to try to downgrade to another os and reupdate to 4.4.2 right after. Ive been searching for days now all i see are guides from how to upgrade to a different os . If it does include 4.4.2 they only posted the update and not the entire rom.
And when i do find someone posting a full rom for 4.4.2 its either not for 747i or its not a md5 file so someone plz help me.
Click to expand...
Click to collapse
DO NOT downgrade to a bootloader older than your NE4 -- doing so will cause a hard brick.
You did mean i747 instead of 747i, didn't you?
Odin is designed to not flash any stock rom that would install a bootloader than the one on your phone. this is to save you from hard bricking your phone. Since you are on 4.4.2, any stock rom in a .tar.md5 format has an older bootloader than your NE4. As far as I know, the only stock NE4 rom on the forums is in a .zip format for flashing from recovery, it was posted by enewman17. (The thread audit13 linked.) If you tried to flash an older bootloader and baseband package through recovery you will probably hardbrick the phone.
Otherwise, there are roms based on TW in the forums: S3Rx, TMS3KK, Likewise, and others. Some use the stock kernel, others give you an option from their Aroma install. The iBubbler's kernel in a couple of these roms is reported to be excellent.
I'm guessing you pulled your S5 apk from either the S3Rx or Likewise thread.
I appreciate everyones feedback and guideance. Yeah I meant i747. It gets pretty easy to misread something when all you've been doing was researching roms and guides. And now its back to researching and finding one of the roms you mentioned. Much appreciated everyone I hope u all have a blessed day..
i know this a zip , but maybe could find help in the thread.
http://forum.xda-developers.com/showthread.php?t=2788357
good luck.
"all I can really do, is stay out of my own way and let the will of heaven be done"