Database Users

[Q] imei problem after rom flash

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.

[Q] N910G won't boot after TWRP restore?

Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS

MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
This http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132 :good:

One possible solution is to flash the appropriate stock rom via odin. After booting, install twrp and root your phone. After this you can restore your previously saved stock rom via twrp.

MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
Sorry no help from me but I have a similar problem. At some point mine quit booting to TWRP and I got a huge OTA update a few days ago and every time I try to boot into recovery it ends up in Stock Recovery only after going to little android saying installing updates(it fails & eventually goes to stock recovery.) I did a reset and still have 5.1.1 installed and still have the same behavior.
I have the professional version of the unified toolkit and it says if it is still booting into stock recovery select options 7, 3 which I did but it didn't fix the problem. I think what's getting me is it thinks there are still system updates to install.

"Camera Failed" After Restoring in TWRP

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

G900F Bricked after update: cm-14.1-20161219-NIGHTLY-klte.zip

Hello all.
I have a Galaxy S5 running cyanogen 13 ( cm-13.0-20161013-SNAPSHOT-ZNH5YAO21L-klte.zip ). Last night I updated it with the cyanogen tool, as usual, thinking that I was just getting a more updated version of cyanogen 13, but apparently I got it working with android 7.1.
As gapps were not working, I downloaded both 7.1 gapps, and cm-13 to try to install gapps or comeback to cm-13 if it did not work.
The problem is that I had no chance to test it. I rebooted the phone with the option "recovery reboot" and after it turned off it showed something like "no command", then it got to the first screen (recovey booting... in blue, samsung galaxy s5 white logo...) and freezed there.
I've tried every key combination and it does change nothing. I've read in another forum an user having the same issue so I advice you to not install this update. At least not from CM13. I will update when I get more details from the other users or if one of us success while trying to unbrick.

I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you

LGaljo said:
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
Click to expand...
Click to collapse
Hello!
Thank you very much, as I found the problem was the recovery I've re installed TRWP. CM14 was replacing it each time I installed it by ODIN so i had to start it just directly after flashing it (without letting the phone boot) and i've installed last CM14 klte file and 7.1 GAPPs
Now all is working , I hope it can help others with the same problem
Thank you!

Questions about bootloader and downgrading on s4, help

Okay, please bear with me as i am new to this flashing custom ROM's game.
I got a intl Galaxy s4 (gti9505) a month back. After reading a lot, i flashed TWRP, and installed a custom ROM (Lineage Optimized 14.1) It runs absurdly great, and i dont think i'll need to replace this OS. BUT if i need to downgrade for whatever reason (im sure i will soft-brick the phone soon, because im testing a lot.) I have some questions:
- Some posts says i can flash back to 5.0 and upper, because the bootloader is the same (???)
- Some posts says i cant flash back to anything below my actual OS (android 7.1) (?????)
- Some posts says i cant flash STOCK ROMS because the bootloader is different. (???????)
- Could i HARD BRICK the phone, wrongly installing stuff via TWRP? or is TWRP functional "forever?''
- I did a big ass backup of android 5.0 before, when i installed TWRP. Can i reflash back to this, at any time?
I'd like to avoid any kind of brick, so help is very much appreciated. Thank you very much for helping a fellow android fan :good:

You can always flash the latest stock ROM to the phone using Odin. There is no stock ROM beyond 5.01 as far as I know.
Yes, you can hard brick the phone by flashing files through TWRP.
How did you create the 5.0 backup?

Thank you. +1 :good:
I did the backup via twrp, i think it was nandroid or something.
One last little question. What happens if i flash, say a custom ROM that is android 6.0 on TWRP right now (Doing the correct stuff and wiping what is needed). Will it Softbrick?
if yes, could you tell me why?

neru21 said:
Thank you. +1 :good:
I did the backup via twrp, i think it was nandroid or something.
One last little question. What happens if i flash, say a custom ROM that is android 6.0 on TWRP right now (Doing the correct stuff and wiping what is needed). Will it Softbrick?
if yes, could you tell me why?
Click to expand...
Click to collapse
It should not softbrick if you are flashing a custom ROM that is designed for your phone's model #.
If it does softbrick, there are two major causes: a full wipe of the data and cache partitions is required before installing the ROM or a full wipe of the phone (system, data, cache) using recovery is required before installing the custom ROM.