Database Info

[Q] Samsung Tab 2 10.1 GT-P5113 CM10.2 to CM10.2 Update

I need a real and very specific answer here please that is for my specific device only. I will tag this post properly.
My Device: Samsung Galaxy Tab 2 10.1 WiFi, GT-P5113. Screenshots attached.
I need advice on getting my Tablet updated from CyanogenMod 10.1 to 10.2. Yes there are lots of entries here about this issue, but they are flooded with all sorts of different devices, 60 or more pages, little of it is for my specific device. I have ClockworkMod Rom Manager installed, tried to update manually to the cm-10.2-20131207-NIGHTLY-p5100.zip and gapps-jb-20130813-signed.zip. Booting to recovery gives me the option to flash a zip file, I choose the cm-10.2 zip. This is not like Safe Strap where I can also choose the gapps. When I tried to flash the zip, I get a system 7 error, no update.
In Settings/About Device is the update section, and the same cd10.2 update is available. But it tells me it will put me into manual mode, I see no way to update the gapps, so I give up. I did this same update with my Droid Razr Maxx and it did work, had to change the Settings, More, Mobile Networks, Network Mode, and choose CDMA + LTE/EvDo to get my phone back, but it worked. I wanted to try to update by Settings, but ended up in Safe Strap, so I choose the ROM zip and added the gapps zip. I cleared the caches and did a factory reset, and it worked, but I had to setup the entire thing all over again, huge PITA! Now, in this forum somewhere, instructions say to flash the rom and gapps, did not say factory reset was necessary. Anyway, it is done on the phone, took a while to setup, switched back and forth from stock to 10.2 until I was comfortable enough with 10.2 to run it all the time.
But this Samsung GT-P5113 is a totally different animal. I wade my way through 60 pages of posts, finding out that some stuff does not work, but the worst thing is that root is gone! Losing root here for me would be a disaster, I have no way of restoring it in CM10.2 that I know of.
Has anyone actually updated a Samsung Tab 2 10.1 to CM10.2 successfully? How did you do it? Method and apps please? Links appreciated. Will I lose root? Must I factory reset or can I update and keep my accounts?
Somebody please address this very one specific device to make it perfectly clear for those of us that have it, have root, moderate experience, and need/want to get this done. Since the GT-P5113 is the same for Gt-P5100, this thread will cover the entire GT-P51xx line. Somebody please help so I can get this done without wrecking or bricking my device. I love Linux and use it often to root or update my phone, at least I do not need drivers for Windows but will accept whatever you can offer with gratitude. Thank you guys!
...well, it looks like the screenshots did not upload or at least do not work for me, have to give images in post.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

problem with rooting gtp5113
dear ohmster, I need help desperately the problems I encountered rooting gtp5113. I know it is not reply to your post but I think you can help me to
resolve the problem.

chongfl said:
dear ohmster, I need help desperately the problems I encountered rooting gtp5113. I know it is not reply to your post but I think you can help me to
resolve the problem.
Click to expand...
Click to collapse
chongfl,
What exactly do you need, buddy? My tablet is now running on CyanogenMod ROM 10.2 so I did get it to work and it is real nice. There is an option in ClockworkMod ROM Manager under "Recovery Setup" to choose CWM ROM Manager (Which does not work for this update.) OR TWRP. I selected TWRP over CWM ROM Manager and I was able to perform the update. Then go back with CWM and install the gapps package. I like it and it worked for me.
But if you want help, you have to be very specific as to what your issue is, what make/model device, and what you have or have not done and what happened. Otherwise myself or anyone else cannot help you unless we know what your issue is.
Oh wait a minute, your post title says lost root. So what happened, you updated, got the update done, and now do not have root anymore? Are you sure? You can look for the su binary, superuser app, busybox file, or if you want to make it real easy, go to the Play Store and download a "Root Checker". This free app will tell you if the phone is rooted or not. I think there are many versions of root checker,. but here is Root Checker at the Play Store.
Use an app like that to find out if you really lost root or just cannot find it. And then tell us what you found, what you need, make and model of the device, version of Android you are running. (I have 4.3.1 now and have to update my signature.), and what ROM you installed. Okay?
If my post helps you in any way, please click the big "Thanks" button under my name on the left.

Same question
Hey there just saw your post and I just successfully rooted my wife's Tab 2 10.1 P5113 with clockwork mod recovery and the CM10.1 for android 4.2.2 like yourself. I now want to put CM10.2 for Android 4.3 on it but cannot find the correct zip file anywhere. What did you do? where did you go to get it? I think I'm missing something.... I'm very tech savvy but new to rooting so any info would be appreciated!

johnf84 said:
Hey there just saw your post and I just successfully rooted my wife's Tab 2 10.1 P5113 with clockwork mod recovery and the CM10.1 for android 4.2.2 like yourself. I now want to put CM10.2 for Android 4.3 on it but cannot find the correct zip file anywhere. What did you do? where did you go to get it? I think I'm missing something.... I'm very tech savvy but new to rooting so any info would be appreciated!
Click to expand...
Click to collapse
What say John.
You said you have the GT-P5113! Okay, so you have to use the GT-P5110 file. Now I can help. Gee, I have been spending all my time on the phone with CM11 because it is really exciting and "a whole new world on an entirely new level". I might update my tablet with you since it has been a while and there might be a later package for me. I will then go to CM11.
Here is a quote from the instructions page for your ROMS (Click this line to visit page.).
"As the IR blaster is not supported in CyanogenMod for the P5113, it is essentially a P5110 as far as CM is concerned. Therefore, if you own a P5113, please use the p5110 CM builds for flashing."
You know, I have spent all my time updating CM10.2 tp CM11 on my phone that I haven't updated the tablet yet. Kind of a dumb thing, the phone is important for communication and I got a monthly bill with it. So it would have made MUCH more sense to update the Tablet first, then do the phone. But I stubled on a really active thread, over 150 posts, about my phone, the update to CM11, that I read it and got interested. Plus, I was watching for updates to CM10.2 and when I saw there was an update and I got excited, ready to go, until....
...I saw the "update" was not to another CM10.2, but to CM11. Now THAT is a totally different animal. I have been ROMing and doing computers long enough to know a major version change means BIG update and usually means "Clean Install". I stopped dead in my tracks to read up first.Good thing too, because there were not very many updates for 10.2, only a few, never "stable" and then they went directly to CM11. Since CM10.1 and CM10.2 were both Jellybean versions, CyanogenMod did not waste a lot of time on CM10.2. I count 5 updates for CM10.2 and no more. Because Jellybean is "old school", CM11 is Kit Kat and totally different. A LOT different. Matter of fact, I cannot find anymore CM10.2 files on the CM website. They dropped it for CM11. 10.1 & 10.2 were mostly the same anyway, not much of a difference, CM10.2 developing to stable did not seem worthwhile anymore because Android is now taking a different direction and a very welcome one. Very slick, very smooth, totally different and agressive memory management. No more 20-30 apps running all the time, fighting for that precious memory. CM11 puts things to sleep pretty quick when they are not used, there are kernel modules now in something called the Xposed Framework, LOTS of them that let you customize the entire system, how it works, overclocking, almost anything you want.
Check for yourself, here are the pages for the GT-P5110, they do not make a rom for GT-P5113 because they are essentially the same but for the IR blaster so you can use it for a remote to control your TV or something like that.
Instructions Page
Download Page
This quote explains the difference between the two models and why they do not make a special rom for the GT-P5113.
"As the IR blaster is not supported in CyanogenMod for the P5113, it is essentially a P5110 as far as CM is concerned. Therefore, if you own a P5113, please use the p5110 CM builds for flashing."
There are no CM10.2 updates anymore. They dropped it. I have 5 on my device but the updates were easy because they were not a big deal, it was pretty much the same thing. Nothing special for updating. So, for you, the next big update would be CM11 and you take the very latest one they have, get the right gapps, and there is a special kernel called the "JBX" kernel you can apply that will allow all sorts of upgrades to the core of the system like tweak memory, CPU speed, sleep, battery use, governors for the CPU, color balance for the screen.
You need to find the right thread to read and follow to upgrade the GT-P5113 to CM11, read it, take notes, save pages that are guides, ask questions, and READ. Then gather your stuff and get ready to try. You will need a different Recovery Environment to install with too, like TWRP instead of CWM. Because you have to flash not only the rom, but the gapps as well and if you choose, and you should, the jbx kernel with it. ClockworkMod does not do "multiple zips", at least I don't think it does. I had to change inside of CWM to TWPR recovery mode just to get my last updates done.
Alright I found it. This is where we have to move the discussion to. Since you cannot update to CM10.2 because it is no longer supported and was dropped, you move on to CM11. You need the instruction page, with downloads, shows you where to get the files, the recovery tools you can use, plus 49 pages of discussion about it. They give a list of recovery tools, CWM is listed but "CWM 6.0.4.4 or newer (or recoverys based on it" is the only one supported. If I were you and I will be you shortly, I would probably use TWRP. I am using in on my phone in Safe Strap and it gives 6 slots to install roms into, a LOT of features, backups, restores, wipes, and can install more than one zip at a time.
Here is the page you want:
[ROM][P51xx][4.4.2]CyanogenMod 11 (CM11)
Since I have spent all my time updating the phone to CM11, I have not worked on the tablet yet nor picked a recovery yet. I will probably use TWRP, this one.
TWRP 2.6 - Samsung Galaxy Tab 2 10.1 (p5100 or p5110)
It is a LOT different than ClockworkMod Rom Manager and it is nice. Here is a whole page of recoveries you can use for this on XDA.
Now read, read, ask questions, and READ.
You can get the jump on me if you want, I already bookmarked the page and will be doing my tablet soon. Don't take this lightly and spend a week or two reading, asking questions, googling on Kit Kat, and get ready for this. I can tell you it is super cool and WAY worth it. At first you will be overwhelmed when you install the right stuff and all the things you can configure. But it will become clear and this is the best, BY FAR!
You have to really read up on this. The Droid Razr has over 150 pages in the thread so a LOT of people have done it and got over the bugs and are finally enjoying it in all of it's glory. Not sure how far along the Samsung Tablet is with Kit Kat so reading up is a must. You are not missing anything with CM10.2, it is only CM10.1, warmed over with a little extra icing on the same cupcake. CM11 is a serious upgrade.
If you want to see what I have been doing with my Droid Razr Phone, plus learn A LOT about CM11, how it works, what was/is wrong with it, how it is now, read this thread. It is over 225 pages already!
Okay man, I will see you over on the CM11 tablet page. If you found this post helpful, please click the Thanks button. See you on the other side, John! :good:

LiquidSmooth-Kitkat-v3.0-NIGHTLY 19/12/2013[UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank u to the Liquid Team for continuing this project!
Many credits go to CyanogenMod for their device trees and their code that was incorporated into this project.
Downloads and installation
+ Download the ROM
+ Download the (Recommended) GApps
+ Copy the ROM to the SD
+ Copy the GApps to the SD
+ Install the ROM and the GApps
+ If you are already in LiquidSmooth, do a cache wipe and dalvik cache wipe
+ If you come from any other ROM, do a wipe data / format system
+ Reboot
CREDITS
LIQUIDSMOOTH TEAM and everyone they are involved with!
chainfire for root!
MEET THE TEAM
Liquid0624
Deadman96385
jsnweitzel
Somber73
TheBr0ken
Cdub50
Sat this one out
Donations are always appreciated
Liquid0624​
XDA:DevDB Information
LiquidSmooth, a ROM for the HTC One S
Contributors
phoenixita
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 2.15
Version Information
Status: Testing
Created 2013-12-19
Last Updated 2013-12-29

Reserved
http://www.androidfilehost.com/?fid=23269279319197376
I've not tested it!
Let me know! Use Flemmard's recovery.
BUGS
Rapier said:
I've flashed it using TWRP (the modded version) and PA GAPPS (full package as recommended on LS's Facebook page. Gone through initial setup, everything went smooth. Started to setup accounts and play with the settings. I've switched the dark mode on then started with the settings. What I've found so far:
- I LOVE the boot animation. It is great
- the sources are probably synchronized with latest CM1 nightly since the USB computer connection/mass storage/MTP is present in the Storage menu (this was added to CM11 in latest nightly 20131218)
- trying to access volume settings give FC in Settings. So the volume can be changed only via vol buttons that brings up the expandable panel. But the other options remain inaccessible (like the capability to set different volumes for notifications and ring) for now
- ROM seems incredibly smooth. Don't know what those guys do but always LiquidSmooth was incredible in this aspect. No lag, everything opens quick, liquid almost
- unfortunately when I first left the phone entering sleep, I could not wake it anymore. I think phoenixita mentioned this for one of the other ROMs...screen remain blank (not the backlight, the whole screen) and only soft buttons lit. Couldn't do anything else but powering off the device and started up again
- upon startup...lots of process com.android.sistemui FCs. I barely could power it off again. Restarted few times...same thing. Restarted to recovery, wiped cache and after optimizing apps the FCs started again.
Well that's my short experience with it, I've also played with the basic apps like Mail, Gmail, Calendar, Dialer, Contacts, Maps and so on, all are working (at least how long I've played with them)
Edit: I see others noticed the wake-up/sistemui FC as well. I'll try what phoenixita suggests. Dirty flashing over BeanStalk could be an option? Nevermind...I'll try it anyways
Click to expand...
Click to collapse

You beauty!. Thanks will test
Sent from my One S using XDA Premium HD app

is for hboot 2.16 or 2.15?

Merche300 said:
is for hboot 2.16 or 2.15?
Click to expand...
Click to collapse
2.15! Building for 2.16 is like building for another device i don't know if i have all this time! I'll try for 2.16 right now.

Merche300 said:
is for hboot 2.16 or 2.15?
Click to expand...
Click to collapse
You are either joking or to lazy to read at least the OP.
Tell you what...regardless of which hboot is for, it is surely not for you
Sent from nowhere over the air...

Merche300 said:
is for hboot 2.16 or 2.15?
Click to expand...
Click to collapse
Pmsl....Read op its hardly a novel...
Sent from my One S using XDA Premium 4 mobile app

Any feedback?

Download is slow, so no report yet....

The ROM is very fast and smooth but I miss the support for German or other languages
Sent from my HTC One S with Tapatalk 4

Hai96 said:
The ROM is very fast and smooth but I miss the support for German or other languages
Sent from my HTC One S with Tapatalk 4
Click to expand...
Click to collapse
LS is only in english you can use morelocale2 but you won't hve full traslations! I'm italian and searching the net and asking To teamliquid they won't support other languages cause they have no time! Language pack were available for LS 4.2.2 and $doryd$ joined the teamliquid to port languages but it was just for 4.2!

Ok, Thanks!
But there is one big Bug, if you want to wake up your device from standby the display won't turn on, only the buttons are lighting. If you reboot you will get a forced systemui FC bootloop.
Sent from my HTC One S with Tapatalk 4

Hai96 said:
Ok, Thanks!
But there is one big Bug, if you want to wake up your device from standby the display won't turn on, only the buttons are lighting. If you reboot you will get a forced systemui FC bootloop.
Sent from my HTC One S with Tapatalk 4
Click to expand...
Click to collapse
Not here too! DAMN! Try dirty flashing over a cm11....and see if it works as a workaround. There is something wrong with our device/device-common trees!
I mean flash cm11 let it boot and then flash liquid over it with gapps!

I've flashed it using TWRP (the modded version) and PA GAPPS (full package as recommended on LS's Facebook page. Gone through initial setup, everything went smooth. Started to setup accounts and play with the settings. I've switched the dark mode on then started with the settings. What I've found so far:
- I LOVE the boot animation. It is great
- the sources are probably synchronized with latest CM1 nightly since the USB computer connection/mass storage/MTP is present in the Storage menu (this was added to CM11 in latest nightly 20131218)
- trying to access volume settings give FC in Settings. So the volume can be changed only via vol buttons that brings up the expandable panel. But the other options remain inaccessible (like the capability to set different volumes for notifications and ring) for now
- ROM seems incredibly smooth. Don't know what those guys do but always LiquidSmooth was incredible in this aspect. No lag, everything opens quick, liquid almost
- unfortunately when I first left the phone entering sleep, I could not wake it anymore. I think phoenixita mentioned this for one of the other ROMs...screen remain blank (not the backlight, the whole screen) and only soft buttons lit. Couldn't do anything else but powering off the device and started up again
- upon startup...lots of process com.android.sistemui FCs. I barely could power it off again. Restarted few times...same thing. Restarted to recovery, wiped cache and after optimizing apps the FCs started again.
Well that's my short experience with it, I've also played with the basic apps like Mail, Gmail, Calendar, Dialer, Contacts, Maps and so on, all are working (at least how long I've played with them)
Edit: I see others noticed the wake-up/sistemui FC as well. I'll try what phoenixita suggests. Dirty flashing over BeanStalk could be an option? Nevermind...I'll try it anyways

Rapier said:
I've flashed it using TWRP (the modded version) and PA GAPPS (full package as recommended on LS's Facebook page. Gone through initial setup, everything went smooth. Started to setup accounts and play with the settings. I've switched the dark mode on then started with the settings. What I've found so far:
- I LOVE the boot animation. It is great
- the sources are probably synchronized with latest CM1 nightly since the USB computer connection/mass storage/MTP is present in the Storage menu (this was added to CM11 in latest nightly 20131218)
- trying to access volume settings give FC in Settings. So the volume can be changed only via vol buttons that brings up the expandable panel. But the other options remain inaccessible (like the capability to set different volumes for notifications and ring) for now
- ROM seems incredibly smooth. Don't know what those guys do but always LiquidSmooth was incredible in this aspect. No lag, everything opens quick, liquid almost
- unfortunately when I first left the phone entering sleep, I could not wake it anymore. I think phoenixita mentioned this for one of the other ROMs...screen remain blank (not the backlight, the whole screen) and only soft buttons lit. Couldn't do anything else but powering off the device and started up again
- upon startup...lots of process com.android.sistemui FCs. I barely could power it off again. Restarted few times...same thing. Restarted to recovery, wiped cache and after optimizing apps the FCs started again.
Well that's my short experience with it, I've also played with the basic apps like Mail, Gmail, Calendar, Dialer, Contacts, Maps and so on, all are working (at least how long I've played with them)
Click to expand...
Click to collapse
could you try dirty flashing over a cm11 nightly?

phoenixita said:
could you try dirty flashing over a cm11 nightly?
Click to expand...
Click to collapse
I was in recovery after I've restored BeanStalk. I'll try flashing over it first to see if it's working, then I'll try over CM11 latest nightly as well

Rapier said:
I was in recovery after I've restored BeanStalk. I'll try flashing over it first to see if it's working, then I'll try over CM11 latest nightly as well
Click to expand...
Click to collapse
lemme know!

phoenixita said:
lemme know!
Click to expand...
Click to collapse
LOL. It works and more than that, I got some extra features as well since I've flashed it dirty over BS...like the network speed meter in status bar (an option that is not present in CM nor in LiquidSmooth ROM). Only strange thing now is that sistemui restarts itself every time when I connect the phone to USB...it's restarting in a loop without any message. I've rebooted phone and I'll try again.

Rapier said:
LOL. It works and more than that, I got some extra features as well since I've flashed it dirty over BS...like the network speed meter in status bar (an option that is not present in CM nor in LiquidSmooth ROM). Only strange thing now is that sistemui restarts itself every time when I connect the phone to USB...it's restarting in a loop without any message. I've rebooted phone and I'll try again.
Click to expand...
Click to collapse
You and phoenix are a great duo together. Phoenix always building and supporting our device and Rapier always tests and provides quality feedback. Thanks to you both for your contributions, very much appreciated. I had those systemui errors constantly on the BeanStalk build, as well, so I reverted back to a 4.3 ROM until the issues are more ironed out. This is expected considering KitKat is still in some infant stages and our device needs a lot of pruning to get it right. Is it true that the battery life is horrendous in 4.4? Thanks to you both again, keep it up! Very eager to try 4.4 again when there is no more systemui errors.

phoenixita said:
Not here too! DAMN! Try dirty flashing over a cm11....and see if it works as a workaround. There is something wrong with our device/device-common trees!
I mean flash cm11 let it boot and then flash liquid over it with gapps!
Click to expand...
Click to collapse
Didn't worked, I still have the same problem with the display...
Sent from my HTC One S with Tapatalk 4

how to fix cm12 modem update and problems thread

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
TOP TIP "For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed." Thanks go to tobitege for this.

zaphodbeeb said:
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
Click to expand...
Click to collapse
+1. I also flashed the latest official CM nightly, booted it and checked if everything was working and then flashed the latest unofficial Temasek's rom. Everything works fine.
Cheers

@zaphodbeeb: thanks for having created this!
This morning I tested an extended version of the CM-12 flashable zip containing more partitions of the current nightlies.
First test brought me a jackpot in that it flashed without an error message, but soft bricked my phone (black screen, no adb nor fastboot), but power button rebooted in a special mode "HUSB_BULCK" (viewable in device manager). Takin' up the challenge, so after plenty of searching/reading and multiple tries to install the right drivers, I got it going through Color OS installation with special phone flashing tool, then flashing X44 again, unlocking, custom recovery+rooting... that was (deserved) fun!!
Though in the first moments it scared me s***tless!
Long story short, totally agree to just flashing the full nightly and directly clean on top any LP rom you want, if you want to be sure to have it right.

FWIW I flashed the alpha modem.zip after flashing and booting SlimLP ROM. Worked fine, absolutely no problems.

cam30era said:
FWIW I flashed the alpha modem.zip after flashing and booting SlimLP ROM. Worked fine, absolutely no problems.
Click to expand...
Click to collapse
I dirty flashed SlimSaber-bacon-5.0.2-20150110 build on top of SlimSaber-bacon-5.0.2-20150102 and then flashed alpha modem everything works fine.

zaphodbeeb said:
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
Click to expand...
Click to collapse
Great info! Would you please add a screenshot showing the baseband version? Everything seems to work but my version is starting with ".3.0.c6...". Thanks!

That weird baseband version is the correct one, no worries.

radium22 said:
Great info! Would you please add a screenshot showing the baseband version? Everything seems to work but my version is starting with ".3.0.c6...". Thanks!
Click to expand...
Click to collapse
Good idea. Done. Now this really is the end of my contribution on this subject.

zaphodbeeb said:
Good idea. Done. Now this really is the end of my contribution on this subject.
Click to expand...
Click to collapse
So first flash the 3rd zip (cm12 nightly)
Then dirty flash the main Rom or whats the next step?
Thank you

The full nightly should be flashed first, then wipe clean in recovery and install your actual rom (or restore).

So, I have been looking at every single rom since xmas and I haven't yet taken the plunge.
I keep hearing about the modem flash, and while I am not scared at any flashing, I am a bit unsure what happens with the modem flash.
Are all the bands in this alpha modem flash? Can I expect my phone to able to make calls and connect to 4G (LTE) / 3G (UMTS and HSPA+) afterwards?
I do apoligize for me being somewhat retarded in this regard..

losthilien said:
So, I have been looking at every single rom since xmas and I haven't yet taken the plunge.
I keep hearing about the modem flash, and while I am not scared at any flashing, I am a bit unsure what happens with the modem flash.
Are all the bands in this alpha modem flash? Can I expect my phone to able to make calls and connect to 4G (LTE) / 3G (UMTS and HSPA+) afterwards?
I do apoligize for me being somewhat retarded in this regard..
Click to expand...
Click to collapse
Yes, your phone should continue to operate as normal, all services and bands included.
Transmitted via Bacon
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
@zaphodbeeb, valiant effort in trying to stop the flow of modem questions in dev threads! Unfortunately it requires people to search and read and the vast majority are far too lazy for that lol.
Transmitted via Bacon

I went for number 3. Did a backup of my temasek ROM. Did a full wipe and installed cm nightly. Had full signal and thought great, this is the right modem. Restored my temasek and signal is gone again.
Any idea why? Did I restore too much of my temasek? Boot, system and data.
Thanks

It might just need another reboot after initial restore to reconnect.

I seem to have no issues with cell data on the new modem (running CM12 nightly) but the WiFi sucks. Is this part of the modem or the ROM? Frequently disconnects to my home WiFi and range seems worse than CM11. Hopefully this will be fixed in a modem update soon.

VQ30DE said:
I seem to have no issues with cell data on the new modem (running CM12 nightly) but the WiFi sucks. Is this part of the modem or the ROM? Frequently disconnects to my home WiFi and range seems worse than CM11. Hopefully this will be fixed in a modem update soon.
Click to expand...
Click to collapse
Not sure what to tell you. I have no WiFi problems. SlimLP ROM

So I just recovered from a hard brick with a dead battery.... it was brutal. I'm looking to do things more carefully going forward. I'd like to keep CM11S as primary. But obviously I want lollipop asap. If I backup CM11S nandroid... wipe clean, flash CM12 nightly for the modem and such, and then clean wipe and restore CM11S to primary from nandroid... will the modem changes that CM12 nightly made persist? I'd like that.... then I could flash some lollipop roms as secondaries and benefit from the modem changes that cm12 made?

The CM11S and the current CM-12 nightlies both contain the full phone partitions when flashing, so when you flash either of them you'll get that version's full modem package.
For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed.

tobitege said:
The CM11S and the current CM-12 nightlies both contain the full phone partitions when flashing, so when you flash either of them you'll get that version's full modem package.
For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed.
Click to expand...
Click to collapse
Top Tip man. I like.:good: I'll include in the OP.

timmaaa said:
Yes, your phone should continue to operate as normal, all services and bands included.
Transmitted via Bacon
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
@zaphodbeeb, valiant effort in trying to stop the flow of modem questions in dev threads! Unfortunately it requires people to search and read and the vast majority are far too lazy for that lol.
Transmitted via Bacon
Click to expand...
Click to collapse
You will notice the subtle message added to my sig also, using simple large letters for those with limited reading abilities.

"No SIM card - 31000" - Galaxy S5 G9000P

Recently I have flashed my S5-G9000P for the first time with the Resurrection OS RR-O-v6.0.0-20180405-klte-Official.
After working alright for the first day or so, texts would not send. Then, at the top of my screen it says "No SIM card - 31000". I don't really know much about modding phones, so here is what I tried so far:
- Resetting the phone
- Removing the SIM card then reinserting, then resetting the phone again
- Resetting my mobile data options
So far these above options haven't helped the problem. I have looked at similar threads to this and none seem to have the same problem based on their descriptions.
Thanks for your time.
Phone - G9000P Galaxy S5
Android Version - 8.1.0
Kernel version (if that's important) - 3.4.113-lineageos-g592be94 (gcc version 4.9.x 20150123 (prerelease) (GCC) ) [email protected] #1 Thu Apr 5 13:41:19 CEST 2018
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.

Well I can State the Facts... has happened here tooooo..... on LineageOS 16 and 15.1. The only fix that I have done, which may help, is Rebooting the Phone.
Yep, tat was the only thing I actually have done, When and IF it happens.
Same thing though, "NO SIM Card" " Corrupt Sim Card" and I Tink there was another one too. All if which, (Knowing that it was running correctly, prior this) I just rebooted. maybe once, maybe like 3-4 times. before it actually goes away.
Now, knowing the phone was running correctly is the Key , I believe. IF your in the process of Flashing, yep, maybe restart that. However, if its running right an all, no reason to do any flashing. why--- Well, was built in the First run batch of them. the phone is rather good and all, cant even see me spending over a $1,000.00 for a new phone, that's Ficking Nutz !!! I am sure, they did built it to last a life time, but what is it, a cell phone built in 2012. Before my warranty was over, I rooted, and got rid of all thre Samsung crap. Ran smooth. Been Flashing ever since.....

E.4.113-LineageOS-g592be94 mobile data not working
Hippie459MN said:
Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.
Click to expand...
Click to collapse
You have in your signature a new rom, does that rom is working ok? The only thing that is driving me nuts is that I can’t have my data usage, I installed RR-O-v6.0.0-20180405-klte-Official on my gsm900M what do you suggest!?
Edited, i found it! just needed to edit the APN settings! i google them for my case that is Mexico, and now i have mobile data!!

Im still running lineageOS. I just havent updated my signature yet. I am going to be getting a new phone in the next week or so though. Pretty sure the motherboard (Internal storage) is taking a dump on me. Phone will work great sometimes for 2 weeks then apps start crashing like mad and only way to fix is to uninstall and reinstall and only way to fix it is to do a full wipe and reinstall the rom. Sometimes it will even start messing up within an hour or two. Things like google play services, the stock dialer, and bluetooth will randomly crash. I have tried just about everything. Different roms, going to stock software, nothing works. And when it tries to do do a backup in TWRP, it always fails in the data partition and always at different points saying it cant read the data partition or some junk. I forgot but I am giving up on it. I have another S5 but wont have it for another week or two.

[ROM][OFFICIAL] Omnirom for Oneplus7pro [10]

CLOSED PER OP REQUEST
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
DOWNLOAD Official
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS
MAJOR BUGS:
huh ?
Minor bugs:
flash on your own risk.
FLASHING
First Time:
First Time:
update fastboot and adb ( https://developer.android.com/studio...platform-tools )
download twrp
fastboot boot twrp-blabla.img
flash stock OOS (we use stock vendor, if you have that skip this step)-(but make sure your both slots are fine (look flashing oos update below))
flash omni
reboot to bootloader
fastboot boot twrp-blabla.img again
flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED
reboot
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
updating when stock OOS update is released:
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash oos
flash omni
reboot bootloader
boot twrp
flash gapps
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7 Pro
Contributors
darkobas, vache, maxwen
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: OOS 10
Version Information
Status: Stable
Created 2019-10-02
Last Updated 2019-11-19

amazing , thanks

The flashing instructions are clear, but it does not mention to wipe data coming from OOS stable 10. Is that correct?

Gordietm said:
The flashing instructions are clear, but it does not mention to wipe data coming from OOS stable 10. Is that correct?
Click to expand...
Click to collapse
That should be ob obvious, but i will add it

[ROM][BETA] Omnirom for Oneplus7pro [10]
Just installed the new version.
What version of open gapps working fine on this build?
Sent from my iPad using Tapatalk Pro

paatha13 said:
Just installed the new version.
What version of open gapps working fine on this build?
Click to expand...
Click to collapse
Always nano

paatha13 said:
Just installed the new version.
What version of open gapps working fine on this build?
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Read OP : flash open gapps nano (ONLY GAPPS NANO ARE CURRENTLY SUPPORTED

[ROM][BETA] Omnirom for Oneplus7pro [10]
I mean this one specific will work?
Or something different?
https://sourceforge.net/projects/opengapps/files/arm64/beta/20190928/
Sent from my iPad using Tapatalk Pro

paatha13 said:
I mean this one specific will work?
Or something different?
https://sourceforge.net/projects/opengapps/files/arm64/beta/20190928/
Click to expand...
Click to collapse
Yes

Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.

B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
Good luck

B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
Probably you missed something, skipped one step etc.

B3n_Huxtable said:
Well i won't be using this rom. spent the last few hours trying to get this to work. nothing is working at all. Got it to boot then try to transfer my files back over. The phone then crashes and goes to a black screen with "qualcomm crashdump mode" Been installing roms on this phone since release with no issue. Finally given up with this one. Currently stuck in fastboot due to this.
Click to expand...
Click to collapse
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.

gogoffm said:
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
Click to expand...
Click to collapse
No, oos camera also works fine

I have no idea what it is. Had to boot a fastboot rom just to get back up and running after that last crashdump. going to go back to OOS for a little I think. I have never had a rom do this but this one has done it every time I have tried. Thing is I love Omni so I hope one day i can get it running properly.
---------- Post added at 01:40 PM ---------- Previous post was at 01:38 PM ----------
gogoffm said:
I flashed the built which shows up on the weekend , had the same prob but when you use adb push you can transfer files to.your phone w/o probs. The rest was working for me fine only bigger prob was if you flash the oos10 cam then the phone reboots into crashdump. Removing the cam solved that. It's Beta, it's still in progress don't forgett that.
Click to expand...
Click to collapse
Don't worry i didn't forget lol. That's why i'm going to keep trying after every release. It will work for me one day.

[ROM][BETA] Omnirom for Oneplus7pro [10]
Everything fine with installations no had any issue with first attempt.
Installing nano gapps not had any issue too this time at opposite with weekend build.
Seems this build more stable and I'm now charging the phone,download my usual staff from play store,will setup my device and will start to work on it later when phone full charge.
Thanks @darkobas.
darkobas said:
No, oos camera also works fine
Click to expand...
Click to collapse
Yes I can confirm OOS camera working fine.
Sent from my iPad using Tapatalk Pro

Does anyone know of an app or mod that allows the navigation buttons to be inverted? The custom navbar app doesn't work on 10 yet and that isn't integrated into the rom yet. I'll live but it is tough to try to retrain the brain, ha!

First impressions using couple of hours is solid.
Battery life look promising and satisfactory.
Very smooth experience so far.
Speaker loudness and quality is on par with oxygen just like with Pie version.
Brightness level seems on par with high oxygen levels although I haven't test it in sunlight, will do tomorrow [emoji14]
Stock(android 10) gesture navigation works great but prefer oxygen one and since using nova launcher I'm with vivid gesture navigation app since when using third-party launcher automatically stock gesture navigation are disabled.
There's dark mode but I'm not fan of it since it's dark gray and not black that prefer (will use substratum to apply truly black theme almost everywhere)
Vast majority Omni features working fine so far.
Wi-Fi, mobile data, so far all excellent, BT will test tomorrow intensively.
Almost all oxygen features are present and worked fine, except vibration need some tuning but that also appy to stable OOS 10 version.
On Pie vibration was better both Omni and OOS.
High brightness level is still present
I found some bugs though like dt2w not such reliable almost half of the attempts needed 2 and rare 3 times to wake up screen or even press the power button at end because not responding at all.
Aldo digital wellbeing to me every time try to open I'm getting fc.
Safety net not passing through magisk also.
I assume will improve in future build don't forget it's still beta.
More observations and safe conclusions will have after couple of days of using the new rom.
But so far general impressions after few hours is at good and satisfactory level and the build is safe to be daily driver for sure.
Sent from my GM1913 using Tapatalk

Just wondering why I can't download the Samsung wearable app in the Google Play Store on this. When I get it from the APK it tells me that this software which is on my phone is not compatible with the watch is there a way to fix this so I can connect my Galaxy watch to this amazing ROM this happens to me on every single ROM except CR Droid 9.0 don't know why:crying:

This is a pic of what the Samsung wearable app said