Hi. I have accidentally installed this baseband on my Sky Vega 820: "IM-A810K_ICS_Baseband FW212.zip".
Afterwards, when I installed CM10 jellybean ROM update via CWM recovery it installed correctly but did not load. The CM10 screen appears and the wheel rotates but then a blue screen appears showing "MDM Error" and the phone reboots automatically. This keeps on happening again and again and the ROM never loads.
I think the Kernel of my device is changed
I want to move back and install the original baseband for my device but I am unable to find it...
Please help.
you can restore the rom of other user of 820L through CWM..
sorry for my bad english..
hassaan1309 said:
Hi. I have accidentally installed this baseband on my Sky Vega 820: "IM-A810K_ICS_Baseband FW212.zip".
Afterwards, when I installed CM10 jellybean ROM update via CWM recovery it installed correctly but did not load. The CM10 screen appears and the wheel rotates but then a blue screen appears showing "MDM Error" and the phone reboots automatically. This keeps on happening again and again and the ROM never loads.
I think the Kernel of my device is changed
I want to move back and install the original baseband for my device but I am unable to find it...
Please help.
Click to expand...
Click to collapse
Baseband is generally a "radio" type update, and not a ROM. What you did it seems, is install an ICS component, the tried installing a JB ROM.
Quick question. When you installed CM, did you do all your wipes and formats as generally required? If not, you need to go back into CWM, do your wipes, then install CM again.
Otherwise, I would suggest you try installing a stock factory rom for your device. This should take care of things.
Your baseband has been changed
I think your baseband has been changed. The easiest way to be back original version is install a stock rom .BINX your phone will be back to stock rom . Let try
Related
Hi Everyone! just a rookie here in need of a bit of advice.
I'm a Galaxy S II I9100 owner and have my phone rooted and all setup with custom roms and been comfortable with flashing for some time now. My ROM of choice recently was Vanilla Rootbox and have to say the ROM has been fantastic with very few bugs to report. Last night i recieved the OTA update via Goo Manager for Vanilla Rootbox 3.4. I downloaded the full update over wifi and flashed with all wipes no worries. Next step was to flash the latest GAPPS and i figured there would be nothing wrong with flashing the GAPPS zip i had on my sd card that i had downloaded the last time i was notified of a GAPPS update via Goo manager as well. After flashing, wiping everything and rebooting again. My phone then booted up to a series of dialog boxes indicating that many google processes had stopped functioning. apps.google.com etc etc. A similar error has been reported in the Vanilla Rootbox thread by another user but i wasnt able to report this bug their either because my post count is too low to post in a development forum. So after seeing this error i rebooted into recovery to flash my last backup but CWM recovery came back with an error messaging stating it couldnt mount either ext or int sdcard. i did a factory reset which made no difference to the problem whatsoever. I then downloaded ODIN and the latest stock ICS Rom and flashed it via ODIN with no reported errors. My phone now boots through the optus boot animation and is stuck at the Galaxy S 2 screen with the flashing red and yellow animation over the S. If i turn off the phone with the power button, the phone turns off and immediately starts again and gets stuck at the flashing s screen. I've taken the battery sim and ext sd card out and put it all back in only for the problem to persist.
If anyone could help me there's a donation and my thanks in it!
Much appreciated
Nick
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
gastonw said:
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
Click to expand...
Click to collapse
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
darkstar117 said:
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
Click to expand...
Click to collapse
wow wow, leave pit files alone for now, they are nasty.
What stock ROM did you flash? 4.0.4 or 4.0.3?
You can factory reset via recovery mode.
Try installing kies anyway, it can't never hurt. Just make sure all applications are closed before you re-flash.
here's jb leak, might help:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
darkstar117 said:
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
Click to expand...
Click to collapse
Tell me your:
Model
Firmware
Country
Carrier
Always mention this
try flashing jb leak (ROM, modem & kernel package).
Hi, I just flashed UK Retail firmware from here ( http://forum.xda-developers.com/showthread.php?t=2231289 ) and I wanna go back to nonEIFGS Retail. How can i do that ? When I'm trying to flash an old firmware RSD fails and the phone remains in Fastboot.
It's impossible due to locked bootloader.
If there is no way back, can someone leave a tutorial on how to flash CM10.1 ? And if I flash CM10.1 it would be the only ROM in my phone or I need to keep the Stock too ?
PS: Forgive me but on my old phone things were simplier.
First of all - is your phone rooted? I assume it's not. So the first thing to do if you want CM 10.1 is rooting your phone. Then you should install boot menu manager or safe strap recovery. And with one of these tools you'll be able to flash cm or any other rom. It depends on you whether you want to keep your stock rom or just back it up and delete it.
Yes, my phone is rooted and I tried with BMM but when I booted with the custom rom nothing happend and the red let turned on.
tomitzam3 said:
Yes, my phone is rooted and I tried with BMM but when I booted with the custom rom nothing happend and the red let turned on.
Click to expand...
Click to collapse
You have to install BMM from google play...
Try booting with BPTools.
I have previously installed custom ROMs before and have successfully been running wanamlite for several months, however, i tried to install CM11 today.
I installed CM10.2 first to get CWM 6.0.4 and then continued to flash CM11. It was successfully installed and booted fine but apps kept crashing such as the playstore. I decided to go back to my wanamlite backup so went back, cleared the caches and went to restore to find that it couldnt find any files. Now when i try to reboot i get the Cyanogen mod cymbol then it loads the background but with a message that reads "the process com.android.phone has stopped" and i cant do anything from there. It will still boot into recovery and download yet this happens everytime i try to boot the phone into the normal mode.
So what did I do wrong? Whats the extent of my problem? & does any bright soul know if and how i can fix it?
Thankyou everyone
Jakeymd said:
I have previously installed custom ROMs before and have successfully been running wanamlite for several months, however, i tried to install CM11 today.
I installed CM10.2 first to get CWM 6.0.4 and then continued to flash CM11. It was successfully installed and booted fine but apps kept crashing such as the playstore. I decided to go back to my wanamlite backup so went back, cleared the caches and went to restore to find that it couldnt find any files. Now when i try to reboot i get the Cyanogen mod cymbol then it loads the background but with a message that reads "the process com.android.phone has stopped" and i cant do anything from there. It will still boot into recovery and download yet this happens everytime i try to boot the phone into the normal mode.
So what did I do wrong? Whats the extent of my problem? & does any bright soul know if and how i can fix it?
Thankyou everyone
Click to expand...
Click to collapse
With what recovery did you perform the backup? Maybe flashing that recovery will let you restore your backup.
All sorted now. I flashed the stock rom through odin and started again with the jeboo kernel and took extra care when flashing everything and now it's all working. KitKat-ed.
Missing some of the aspects of touchwiz a bit and i got a lower score on antutu than with wanamlite but i'll stick with it for a big, if only for the bragging rights when i get back to work on Monday.
At first, hello to all of you
I had CWM 5 on my Galaxy I9300, and I installed 4.3.1 CM custom rom, and downloaded gapps for 4.3, but google play crashed everytime. Then I flashed CWM via odin, and i installed v 6.0.4.5 but with this version I couldnt " wipe dalvik cache" so I flashed v 6.0.4.6 but it wont open in recovery, then I flashed another one, and when I turned the device on, the touch screen was not responding, it booted regulary, then I tried 4.1.2 CM custom rom, but the problem is the same. I have no carrier, where to find stock rom, or what to do?, here are some photos I wont do anything on my own, to avoid more demage. Thanks for help
Zlajaaa said:
At first, hello to all of you
I had CWM 5 on my Galaxy I9300, and I installed 4.3.1 CM custom rom, and downloaded gapps for 4.3, but google play crashed everytime. Then I flashed CWM via odin, and i installed v 6.0.4.5 but with this version I couldnt " wipe dalvik cache" so I flashed v 6.0.4.6 but it wont open in recovery, then I flashed another one, and when I turned the device on, the touch screen was not responding, it booted regulary, then I tried 4.1.2 CM custom rom, but the problem is the same. I have no carrier, where to find stock rom, or what to do?, here are some photos I wont do anything on my own, to avoid more demage. Thanks for help
Click to expand...
Click to collapse
Whats the exact file name of the recovery you flashed or a link to it?
Zlajaaa said:
I flashed v 6.0.4.6 but it wont open in recovery, then I flashed another one
Click to expand...
Click to collapse
You blew the digitiser by flashing a recovery from another s3 model, there is no fix apart from replacing the screen assembly.
Jes, the digitiser is blown. Can i replace just him, cuz the display is working?
No, they are glued together.
When I updated Cyanogenmod to CM13 my recovery stopped working (I turned on "update recovery with system"). I didn't can apply ANY updates from SD card and from PHONE STORAGE too.
To fix it I tried to update CM to 13 from 10-02-2016 to 13-02-2016. But... It didnt ANYTHING happened! It was only black screen. But now I can't turn on my phone! Recovery mode is not turning on too! I have only not working phone with not working recovery when it will turn on too!
I need my phone tomorrow, please, HELP ME! What can I do?!
Recovery: CM13 recovery.
It is not bootloop, I have:
BLACK SCREEN
After Samsung logo.
It is very important, does somebody know what to do?
I have new news:
After turning on I have samsung logo and for about one second Updating System message! Without loading bar . After it of course black screen!
I didn't do any backups of my phone, but I can wipe all data, but I NEED WORKING PHONE!
@tom790
Try flashing this kernel I attached with odin. Next try rebooting to recovery. If you get a working TWRP recovery, then flash the rom you want to use as normal. Please read this guide if you want to use CM13 and avoid common issues.
Same problem here after trying to update to the newest nightly (also with "update recovery with system" on in developer settings) I assume that this function isn't working correctly. The only alternative is as mentioned above - flash kernel+recovery with Odin and make changes afterwards.
I have same problem. I tried to install this kernel above with ODIN but no luck, after sucessful flash logo and black screen. Any other advice or tips? Is there any chance to recover some data from internal card?
And exactly the same issue here. Will try the workaround from the first answer by noppy22.
OK, succeeded. I used ODIN with the kernel tar file from noppy22, put the S2 into download mode (that was still possible, recovery mode couldn't be accessed), flashed the kernel. Phone rebooted automatically into recovery and started (continued?!) with the installation of CM 13.0. And here I realize the issue. The OTA was the nightly of CM 13.0 which I inadvertently chose to be flashed over the running CM 12.1. Bad idea!
Caveats: I see the yellow triangle now which didn't show up before. No problem for me - it's more than 4.5 years old. And there is still the error that "Google play service was terminated" which showed before I triggered the OTA update of CM 12.1.