Related
Every time I try to flash a different modem, IE XXKG3, XXKG2, XXKG1, XXKF2, XXKF1; it tells me PHONE: Unknown in *#1234# XXKE4 and lesser seem to work just fine. I have had this issue on stock 2.3.3, and now with the latest lightningrom3.2(XXKG2) it is the same. Can anyone help me fix this, or offer insight into what the deal is?
Bump.
Sent from my GT-I9100 using XDA App
Bump looks as you are only one with the problem .
Wrong flash wrong whatever totally wipe phone and start again only suggestion.
Phones get confused with multiple flashes with bits left behind is my experience .
jje
I have wiped and re-flashed 5 times minimum. Some of those with PIT. I guess ill give it another shot, I don't mind setting everything up again(and again...).
I re-flashed another 5 times. Still not working, I will just go back to my working setup and live with it. Unless anyone else can help.
I re-flashed another 5 times.
As i posted multiple flashes f*** phone .
Connect in mass storage mode format phone through windows .
Recovery mode mounts and settings format data sytem sd card .
Recovery wipe dalvik cache wipe cache factory reset .
Blank phone via Odin install stock firmware not 2.3.4 .
jje
So you are saying, to mount in windows, format my usb storage, then perform a factory reset on the phone? Reflash the stock firmware.
Then I can flash the KG3?
Formatted the usb storage partition VIA windows, with CWM wiped data, wiped cache, wiped davlik, formatted everything else.
Re-flashing stock.
I am doing the format then I will wipe everything again. Then install LightningROM 4.1 Is this as you meant?
After all that still did not work.
I meant wipe and install a stock rom with a later modem than KE4 NOT A CUSTOM ROM .
Have you actually flashed a modem by itself .
Does your custom rom actually contain a modem .
jje
Ok, I will try that tonight, an XXKF2 rom. I have tried to flash modems by themselves, the way I get the modem to be XXKE4 while using lightning rom(XXKG3) is by flashing only a modem. Yes the LR4.1 Contains the KG3 modem.
So, I had KF2 recognized, and I saw service for about 5 seconds, then it went away didnt come back, so I am trying other ROMS. At least it was recognized. Thanks
Now I have it recognizing KG3, but not recognizing my sim, with KF2, it got my phone number and such, then disconnected never connecting again
So with the official higher than KE4 modems, they are now recognized, but no network. Is there anything more I can do?
Hello,
HELP Please!!!
I just unlocked, rooted with cwm and SAUROM, added modem t989 with cwm.
With CWM install, I saved all data and then erased all data before installing Saurom. After installation of Saurom, I restored the data, then I added the modem.
sim card installed, reboot. Phone turns on, but not apps open and phone keeps looking, nothing works.
What should I do now?
Thanks,
I would try to flash again. Wipe everything first in cwm. And dont restore ur apps, redownload them from the play store. If u still have probs flash back to stock wit Odin. Theres threads in the dev section on this.
Sent from my SGH-I717D using XDA
Where do I find the file to bring it back to stock with Odin?
No need to go back to stock
Do this:
Recovery
clear data, d cache, and cache
Flash Rom
Reboot
Clear d cache, cache
Flash modem
Make sure its the correct modem
Sent from my SAMSUNG-SGH-I717 using xda premium
I tried redoing these and it still does not work
were do I find the file t bring it back to factory?
I am using SAUROM v7
Ok, Reflashed the rom using ICS. It works, but the phone is not reading the sim card and there is no network.
How do I fix this?
Hello,
Recently, I was having problems with my cache partition being corrupt as I could not install apps from the play store. To fix this, I flashed stock rom S5830i_XXLI1_ODDLI1_DDLI1. After flashing via odin, I got stuck in a bootloop and had to flash cyanogenmod RC 3 with the CM kernel after which the phone started working. Since then I have lost my IMEI number. I tried flashing S5830i_XXMC1_ODDLK1_DDMC1 but my phone is again stuck in bootloop? I think the kernel is the reason why I lost my IMEI, so I dont want to flash it again. Is there anyway I can get my phone to working conditions?
I have tried the Hex workshop method which hasn't yet worked for me.
In CM 7 Rom,IMEI bug is not solve. Search in xda you will get the information about how to restore IMEI or see CM7.2 Rom's thread and comments.
Sent from my GT-S5830i using xda app-developers app
vibhavp said:
Hello,
Recently, I was having problems with my cache partition being corrupt as I could not install apps from the play store. To fix this, I flashed stock rom S5830i_XXLI1_ODDLI1_DDLI1. After flashing via odin, I got stuck in a bootloop and had to flash cyanogenmod RC 3 with the CM kernel after which the phone started working. Since then I have lost my IMEI number. I tried flashing S5830i_XXMC1_ODDLK1_DDMC1 but my phone is again stuck in bootloop? I think the kernel is the reason why I lost my IMEI, so I dont want to flash it again. Is there anyway I can get my phone to working conditions?
I have tried the Hex workshop method which hasn't yet worked for me.
Click to expand...
Click to collapse
Flash a stock Rom again and boot into stock recovery(power+home+volume up).Now wipe data/factory reset, wipe cache and Reboot.
Sent from my GT-S5830i using xda app-developers app
andy.acei said:
Flash a stock Rom again and boot into stock recovery(power+home+volume up).Now wipe data/factory reset, wipe cache and Reboot.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
Had to do this twice to get back to stock with my IMEI. Thanks!
I searched the internet and threads on XDA for this problem but couldn't really find one!
The problem is- My Galaxy S3 (GT-I9300) doesn't boot any AOSP/AOKP/CM ROMs! It's just the bootanimation and DONE! For hours and hours the bootanimation only! But I can flash any Sammy 4.3 / 4.4 ROMs! They boot! They work properly!
I used to change to AOSP to Sammy and vice versa so many times with no issues. One day I downloaded the UltimaAOSP Valhalla ROM and flashed it. This was the first time my S3 didn't boot. I flashed custom Kernels like boeffla on it but all in vain. It was stuck on the bootanimation. I flashed NeatROM AOSP on top of it, which worked properly. Then it was with the fusion sp ROM that it didn't boot again. Again I flashed NeatROM AOSP on top of it (it's my favorite ROM), which I used just to copy some other ROM from my PC to my phone.
Now, I'm on my Stock ROM which came with my phone since so long! I'm shocked to see now NO AOSP ROMs are booting! I've used C-ROM, NeatROM, Resurrection Remix and SOKP Milestone. I have the ROMs' ZIP files and also a Nandroid Backup which I made when I changed to other ROMs. Not the ZIP files neither the Nandroid Backups are helping! ZIP files get flashed succesfully (I wipe the data & cache & dalvik-cache every time) and the Nandroid Backups get restored successfully! But always the phone gets stuck on the bootanimation!
I always moved to AOSP from Sammy (never Sammy to Sammy) but this time I gave it a shot.
Result : All the Samsung ROMs are flashing, working properly, even the Nandroid restores boot. I flashed my newly downloaded FlashingDroid Sammy 4.4 ROM which also works.
BUT I CAN'T GET THE AOSP ROMs onto my phone!
My thought (it could be wrong) : Is it to do something with the data in a partition other than system, data, and cache? Some partition which has stored files needed to boot Sammy ROMs and is preventing AOSP ROMs to start?
HELP!
:crying:
MORE UPDATED INFO ON POST #6
::ROBLEM SOLVED:::
Wipe system, data, cache and preload partitions manually in mounts and storage in CWM Recovery.
DONE! AOSP Working!
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
boomboomer said:
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
Click to expand...
Click to collapse
Have lots of data on my internal memory! Still I deleted lots of unwanted files. Any other way to wipe the hidden preload partition other than using Philz Recovery? I remember I flashed Philz after which I couldn't restore any of my Nandroid Backups backed up with CWM Recovery..
Sent from my GT-I9300 using XDA Premium 4 mobile app
In cwm mounts and storage wipe preload
Press thanx if i helped you in anyway...
Update - Got More Info
Update : Just noticed that when it's the bootanimation on the screen after flashing an AOSP ROM, pressing any of the buttons on the phone vibrates the phone vigorously 2 times.. why??
Also, I want to ask about the connection between a kernel and a bootanimation without starting a new thread 'cause I think it's the solution to my problem here.. The data which I probably suspect that prevents AOSP ROMs from booting is some different bootanimation file? I mean when I'm on a Sammy ROM, I started to flash different bootanimations after flashing some CWM Custom Bootanimation ZIP file. The bootanimation changes on all Kernels on Sammy ROMs -except 1 that is the boeffla kernel. The strange thing is that the first custom bootanimation I had flashed (after flashing Boeffla's Sammy Kernel) when I switched to Sammy from my last AOSP was the hTC One Bootanimation which worked fine (the bootanimation successfully changed). After that, it never changed. My phone always booted up showing the hTC One Bootanimation no matter how many times I flashed another bootanimation ZIP or the CWM ZIPs which enable/disable Custom bootanimations. But! When I changed to any other kernel (the stock that came with the ROM/GoogyMax 2/AGNi), the bootanimation was the last one flashed by me before changing the kernel. I could change the bootanimations successfuly every time after that. Now, I flashed Android Revolution HD ROM and was on Stock Kernel. As soon as I changed to boeffla kernel (without flashing any other ZIP), the bootanimation changed! (automatically!) And it was again the same old hTC One Bootanimation.
Can someone please tell me WHERE is this bootanimation data and the data that prevents AOSP ROMs to boot is stored? Certainly not in the data or system or cache partition...
Update 2 : Just figured out where the automatic htc bootanimation magic happened. The hTC bootanimation.zip file was found in data/local . However, I always knew the bootanimation directory as system/media.. So now, is it safe for me to delete all files in data/local 'cause it seems it is the problem for AOSP ROMs?
Sent from my GT-I9300 using XDA Premium 4 mobile app
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
jimbobpro87 said:
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
Click to expand...
Click to collapse
I'm not trying to go back to Jelly Bean! I'm flashing AOSP based ROMs of KitKat 4.4.2 which don't boot!
SOLVED!
Yayy!
I guess I got a solution!
Wiped system, data, cache and preload partitions manually in mounts and storage in my CWM Recovery.
DONE! AOSP Working!
:victory:
THANKS TO ALL WHO HELPED! :angel:
Thank you for your post.
I am having the same problem, phone not booting past boot animations using aosp ROMs. Haven't tried Sammy ROM to test the theory yet but will try soon.
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
alaska_ryder said:
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
Click to expand...
Click to collapse
Strange- it happened that day but not now. Even I get an error formatting preload. But! I guess the problem is the system partition! There IS an option to format /system in mounts and storage option on the first screen.
Sent from my GT-I9300 using XDA Premium 4 mobile app
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Eden532 said:
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Click to expand...
Click to collapse
Have you flashed the rom then factory reset?
Beamed in by telepathy.
shivadow said:
Have you flashed the rom then factory reset?
Beamed in by telepathy.
Click to expand...
Click to collapse
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Eden532 said:
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Click to expand...
Click to collapse
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
MigoMujahid said:
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
Click to expand...
Click to collapse
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Eden532 said:
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Click to expand...
Click to collapse
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
MigoMujahid said:
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
Click to expand...
Click to collapse
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
shivadow said:
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
Click to expand...
Click to collapse
I did flash the custom rom twice but still no good.
(And also i checked the IMEI via a custom Sammy rom)
Eden532 said:
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
Click to expand...
Click to collapse
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
MigoMujahid said:
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
Click to expand...
Click to collapse
Thank you so much for sending the link, Its really difficult to download from sammobile.com . Ill check it right away and report. Thanks.
before this happened I'm on SLX v24 and TWRP 2.7.1, everything normal and no error. Then I want to try the MIUI v7 5.10.8. I follow the instructions in xda, I flashed newest TWRP 2.8.7 rev1 (inside the zip there's update-binary-f2fs), reboot again to TWRP and flashed MIUI, and reboot to MIUI, then I noticed that there's no baseband and IMEI, then I restore IMEI from my backup with mobileuncle, reboot it, and still unknown. I try to change modem, reboot it, and still unknown. I cant edit the cds radio. I already tried deleted the nvram folder, reboot it and still unknown. Then I tried to flashed it to stock rom with flashtool hoping it restored to normal, but still the baseband and IMEI unknown.
can anyone help me??
ludhpraditto said:
before this happened I'm on SLX v24 and TWRP 2.7.1, everything normal and no error. Then I want to try the MIUI v7 5.10.8. I follow the instructions in xda, I flashed newest TWRP 2.8.7 rev1 (inside the zip there's update-binary-f2fs), reboot again to TWRP and flashed MIUI, and reboot to MIUI, then I noticed that there's no baseband and IMEI, then I restore IMEI from my backup with mobileuncle, reboot it, and still unknown. I try to change modem, reboot it, and still unknown. I cant edit the cds radio. I already tried deleted the nvram folder, reboot it and still unknown. Then I tried to flashed it to stock rom with flashtool hoping it restored to normal, but still the baseband and IMEI unknown.
can anyone help me??
Click to expand...
Click to collapse
Hi. Try this, but no garanties, because you could corrupted the NVRAM:
1. Download this recovery openrecovery-twrp-2.8.4.0rev2-p780row.zip from here; NOT OPTIONAL, ONLY THAT RECOVERY.
2. put it on the sd card .
3. Reboot in recovery and flash openrecovery-twrp-2.8.4.0rev2-p780row.zip.
4. reboot in recovery again.
5. do a full wipe except sd card
6. Reboot in system and tell me if your imei is back.