If someone could help me I'd be very grateful.
I have cwm 6.0.3.2(0611) but was running TWRP previously. The first custom rom I installed was crdroid and today I tried to install graviton rom. I did this using TRWP. However, after installing, my SIM was not recognised and I had no IMEI and the baseband version showed 'unknown'.
I then flashed CWM and tried to re-install crdroid with the latest version but came up against the same problem. However, after installing this I also had no bootanimation. After browsing this forum for an answer, I couldn't really find anything that helped too much so I did a nandroid restore.
This worked and put me back to my stock rom.
I then tried to reflash the latest crdroid but the problems have all returned again.
Can anyone help me? I'd like to be able to flash the roms I want again but it seems that anything I'm doing is wiping the IMEI/baseband/bootanimation.
welshyoot said:
If someone could help me I'd be very grateful.
I have cwm 6.0.3.2(0611) but was running TWRP previously. The first custom rom I installed was crdroid and today I tried to install graviton rom. I did this using TRWP. However, after installing, my SIM was not recognised and I had no IMEI and the baseband version showed 'unknown'.
I then flashed CWM and tried to re-install crdroid with the latest version but came up against the same problem. However, after installing this I also had no bootanimation. After browsing this forum for an answer, I couldn't really find anything that helped too much so I did a nandroid restore.
This worked and put me back to my stock rom.
I then tried to reflash the latest crdroid but the problems have all returned again.
Can anyone help me? I'd like to be able to flash the roms I want again but it seems that anything I'm doing is wiping the IMEI/baseband/bootanimation.
Click to expand...
Click to collapse
You could try backing up your EFS partition and grabbing the Modem you had in your stable ROM. Once you flash, you could try to restore the EFS (on the rom that you have the issue on) and flash the modem if the unknown baseband/lost imei continue after that.
Cheers, I did think of something like that - I saw a few threads which suggested flashing the modem (twice?) but it seemed to me that I should be able to flash a rom without having to backup efs and restoring each time (the issue happens with every rom flash now for some reason). I saw a few similar threads but nothing with the exact same problem, and no real solutions so far.
Related
After having no issues with flashing ROM's, radios etc for over 6 months i've recently encountered a problem. When trying to update to CM7.0.3 from CM7.0.1 i had a system cannot mount error and was unable to flash any new ROM as a result. To try to fix this i formatted system and restored to a CM7 ROM and everything seemed fine. From here i can flash a ROM but when booting the new ROM it does not include gapps (even when selected to install from clockwork) and the system cannot mount error occurs again.
In short, everything seems to work fine currently but as soon as i flash a new ROM i get a system cannot mount error. The same thing happened with a CM nightly and so im thinking it is not just an isolated problem with a specific build.
Any help would be much appreciated. On a side note, on the restored ROM im currently using i have a LordMod Kernel installed, not sure if this would effect anything as when the problem was first encountered i did not.
Thanks.
Restore to a working ROM using your backups.
Boot into bootloader and then into fastboot.
Download ClockworkMod Recovery 3.0.2.8 from HERE
Unzip and run install-recovery-windows.bat. This will flash the latest recovery for you.
Now try again.
Yeh that worked perfectly, thanks alot.
I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
VegasIdaho said:
I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
Click to expand...
Click to collapse
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
v.konvict said:
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
Click to expand...
Click to collapse
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
VegasIdaho said:
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
Click to expand...
Click to collapse
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Choristav said:
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Click to expand...
Click to collapse
Thanks for your reply. After reading the response from v.konvict above, I thought that CM12 would be caf, but it isn't. I've got several more ROMs working now by using different bootstacks, but it is trial and error with some of the ROMs.
Hi,
I very much hope you can help me with this issue.
I wanted to flashTemasek's CM 12.1 v. 14.9 on a N9005 running stock Lollipop (N905XXUGBOE9_N9005DBTGBOF1). After much reading, I believed it would be best to first downgrade to stock 4.4.2 (N9005XXUENB4_N9005DBTENB1_DBT). I then flashed TWRP 2.8.7.0 hlte 4.4. Could this be the reason? I later read that for Kitkat 4.4.2 without updates I should have rather used the 4.3 version of TWRP. I did a backup of the system including efs. After that I flashed Temasek's CM 12.1 v.14.9 doing a clean install by following the steps outlined in the thread:
Clean Installation
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM.
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. WIPE DALVIK/CACHE (for good measure).
10. Reboot Device.
Flashing went fine, but the phone did not recognize the SIM card. Initially believing that this might be an issue with the ROM, I downgraded to Temasek's CM 12.1 v. 14 only to find that I was having similar issues. I then tried to restore the backup I created earlier but basically only got a black screen and a ton of notifications that apps had stopped working. I then tried to flash back stock kitkat (N9005XXUENB7_N9005DBTENB2) hoping that this would work with my version of TWRP but have had no success. Before causing any further trouble, I was hoping that some kind soul would be capable of and willing to help me with this. How can I recover my efs from the backup created with TWRP? And how can I finally restore my phone and hopefully end up with the ROM I was trying to flash? Any help is very much appreciated!
Thank you!
django e said:
Hi,
I very much hope you can help me with this issue.
I wanted to flashTemasek's CM 12.1 v. 14.9 on a N9005 running stock Lollipop (N905XXUGBOE9_N9005DBTGBOF1). After much reading, I believed it would be best to first downgrade to stock 4.4.2 (N9005XXUENB4_N9005DBTENB1_DBT). I then flashed TWRP 2.8.7.0 hlte 4.4. Could this be the reason? I later read that for Kitkat 4.4.2 without updates I should have rather used the 4.3 version of TWRP. I did a backup of the system including efs. After that I flashed Temasek's CM 12.1 v.14.9 doing a clean install by following the steps outlined in the thread:
Clean Installation
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM.
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. WIPE DALVIK/CACHE (for good measure).
10. Reboot Device.
Flashing went fine, but the phone did not recognize the SIM card. Initially believing that this might be an issue with the ROM, I downgraded to Temasek's CM 12.1 v. 14 only to find that I was having similar issues. I then tried to restore the backup I created earlier but basically only got a black screen and a ton of notifications that apps had stopped working. I then tried to flash back stock kitkat (N9005XXUENB7_N9005DBTENB2) hoping that this would work with my version of TWRP but have had no success. Before causing any further trouble, I was hoping that some kind soul would be capable of and willing to help me with this. How can I recover my efs from the backup created with TWRP? And how can I finally restore my phone and hopefully end up with the ROM I was trying to flash? Any help is very much appreciated!
Thank you!
Click to expand...
Click to collapse
Who said you need 4.4 to update to cm12.1? You need 5.0 bootloader. That's what you had.
Maybe use another version of twrp. I use 2.8.5? And it's fine.
In twrp go to back up and restore. Restore by navigating to location of your back up.
kenny1991 said:
Who said you need 4.4 to update to cm12.1? You need 5.0 bootloader. That's what you had.
Maybe use another version of twrp. I use 2.8.5? And it's fine.
In twrp go to back up and restore. Restore by navigating to location of your back up.
Click to expand...
Click to collapse
Thanks! I managed to restore the imei flashing stock lollipop. I initially downgraded because it seemed to me that all instructions were based on kitkat and not much information was available on lollipop. Just wanted to make sure I followed the instructions to the letter. Stupid me...
I tried to restore efs the way you describe it, but it didn't work out for me. Thankfully, things are back to normal now and I will flash cm12.1 directly from stock lollipop now.
Thanks for taking the time to help!
I restored a backup from a few weeks ago after trying out a marshmallow based ROM (I was on lollipop prior) and after the restore process, my old phone interface came up and it was as if I never flashed the newer rom at all as expected, however, now my camera does not work at all and I could use a hand figuring out how to resolve this issue.
Things I've tried:
- Rebooting (obviously)
- Clearing cache/dalvik from recovery
- Clearing the camera app's data and cache
When I restored my backup, I chose not to restore 'boot' and 'recovery' because while I was on the marshmallow rom, I unlocked my phone's bootloader and installed TWRP (as opposed to using SafeStrap) and I didn't want to lose it.
Samsung Galaxy S5 GM-900V
Android 5.0
Baseband: G900VVRU2BOG5
Build: OptimalRom 15-5
Marshmallow rom I referenced: Norma_Note5Port_V3.4_VZW
Any advice?
So I've formatted dalvik/cache/data/internal storage and installed the older rom (OptimalRom 15-2 ) again. Did the initial setup and the camera still didn't work. I tried reflashing a known-good kernel that's compatible with this rom and that didn't seem to help.
Can anyone point me in the right direction on how to resolve this? Something must have been flashed when I installed the Note 5 rom that wasn't when I went back to OptimalRom. I just don't know what. I'll keep searching and experimenting. Thankfully I have a real recovery menu now so softbricking isn't as big of a deal.
GoTeamScotch said:
So I've formatted dalvik/cache/data/internal storage and installed the older rom (OptimalRom 15-2 ) again. Did the initial setup and the camera still didn't work. I tried reflashing a known-good kernel that's compatible with this rom and that didn't seem to help.
Can anyone point me in the right direction on how to resolve this? Something must have been flashed when I installed the Note 5 rom that wasn't when I went back to OptimalRom. I just don't know what. I'll keep searching and experimenting. Thankfully I have a real recovery menu now so softbricking isn't as big of a deal.
Click to expand...
Click to collapse
Since you have TWRP now, try doing a complete and clean wipe. Go into recovery, Wipe, Advance Wipe and select Cache, Dalvik cache, Data and Internal and swipe. Then back out to Wipe and swipe twice on the slider and install the OptimalRom of choice. then install the PB1 firmware NO Bootloader. If you still have an issue then try with the ROM kernal and flash it which I think it'sthe OG5 Kernal No Bootloader. The reason for doing this particular wipe is to get anything that may be left over from a previous ROM. This is my preference and habit from when I started running ROM's on my S3. Beanstown103 and others had recommended doing this in TWRP and haven't had any issues or problems by doing this since. Hope this may help
Thanks al50. I will give that a shot. Sorry but I'm not familiar with "PB1 firmware". what are you referencing there?
GoTeamScotch said:
Thanks al50. I will give that a shot. Sorry but I'm not familiar with "PB1 firmware". what are you referencing there?
Click to expand...
Click to collapse
It's the version that your phone is on. Look in About Phone in settings. Anyways, that’s the Zip file you install after you install the ROM. But if you're already on PB1 then you don't have to worry about that. If you have issues with the camera then try flashing the No bootloader kernal that was made for that ROM, which I believe it was OG5 but check the OP to be for sure
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Hi
Bibi if you’re still active on xda reply to this
Help me i got same issue with you. Can provide me with ur stock rom and stock recovery? And how to do. Thanks very much.
Bibicp said:
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Click to expand...
Click to collapse
Bibicp said:
I tried to factory reset a custom ROM, got sent to TWRP then I can't reboot to system from there. Tried a clean install but to no avail. I've looked around on the internet and I think I have to reinstall stock ROM and then reinstall custom recovery and ROM, except if I were to install the stock ROM once again (with sp tools) I need my phone to be turned off, not in recovery mode. So how exactly should I proceed now?
EDIT: Managed to get rid of the TWRP bootloop by restoring from a stock nandroid I've found on the forums, coupled with flashing a stock recovery image using TWRP. Reunlocked bootloader, flashed TWRP all over again and then flashed custom ROM and Gapps. Everything running fine now.
Mods feel free to delete this post since it's solved itself, or leave it in case anyone needed help concerning the same issue, up to you.
Click to expand...
Click to collapse
can you put a link where you find the stock recovery, cos i've restore stock recovery on twrp but my device keep booting to twrp