yashsingh1/xdaforums huggingface dataset:
[Xperia Z General] mandibox:
DRM restored

Mine was also restored.

Tho the mess over here, on a Xperia Z2, was absolutely a little mistake that costed the phone's life: I changed dpi setting under /system/build.prop and couldnt get the phone to startup properly (bootloop). So to get it connected to the PC, the only exit was to unlock the bootloader and flash some 3rd party recovery mode. By doing so I knew I was gonna lose DRM keys, TA Partition was gonna be screwed... anyway, I had to do it. So I got into the OS partitions, I copied (too late) the TA Partition that was still there, and I could make a backup of not much things... the recovery did some backup, I'll check later its contents. Very complicated to explain details of what I did, but after it, to get the phone back working, I downloaded a brand new stock firmware, which also restored my TA Partition and my DRM keys somehow...

I made a test. I used a tool (Backup-TA-9.11) that downloaded from the phone the new TA Partition. And then I compared it to the old one (using same tool), and I saw that the old one was totally f***d up!

I'm also happy I have my DRM Keys back with the TA Partition working!

Good luck people
[Xperia Z General] xerwudjohn:
HOW did you do that? are you sure about that? please check your service test/security if both first three lines are Ok.
[Xperia Z General] mandibox:
Hello!

Sorry for the late response

I now figured out the DRM Keys are not really restored.

At the time I did not know about them, and lost them by mistake.

But I found another post that kinda helped me getting them back: http://xdaforums.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672
[Xperia Z General] Zewarxx:
Man I restored them twice and it still gives me the :/
[Xperia Z General] iiAustinL:
One question, is it possible to have your DRM keys intact with a locked bootloader, and be able to access fastboot?

I know for a fact that in Flashtool, it stated that fastboot features were accessible.

So, this whole time I thought that I might have accidentally unlocked my bootloader until I came across this thread.

I remember when I first got the phone, I was unable to access Fastboot mode due to a locked bootloader, but now I am able to.

20/001/2015 19:01:57 - INFO - Device connected with USB debugging on
20/001/2015 19:01:57 - INFO - Connected device : Sony Xperia Z
20/001/2015 19:01:57 - INFO - Installed version of busybox : BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
20/001/2015 19:01:57 - INFO - Android version : 4.4.2 / kernel version : 3.4.0-perf-g32ce454 / Build number : 10.5.A.0.230
20/001/2015 19:01:57 - INFO - Checking root access
20/001/2015 19:01:58 - INFO - Root Access Allowed
20/002/2015 19:02:27 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
20/002/2015 19:02:28 - INFO - Device will soon enter fastboot mode
20/002/2015 19:02:28 - INFO - Device disconnected
20/002/2015 19:02:41 - INFO - Device connected in fastboot mode
20/002/2015 19:02:45 - INFO - Device Status: FASTBOOT mode
20/002/2015 19:02:47 - INFO - Fetching fastboot version info from connected device
20/002/2015 19:02:47 - INFO - FASTBOOT version info: [ version: 0.5 ]

-NEVERMIND, just tried flashing XzKernel-26 by alnikki25k, and it didn't boot.
[Xperia Z General] LaurynasVP:
Personally, I can't understand how other people is possible to bring their DRM keys without having TA-Partition. It's all fictive information and I'm totally sure, that no one have restored DRM keys within new ROM installation. And I can bet 100% that it doesn't matter - is it STOCK or CUSTOM ROM. Your DRM Keys aren't going to be restored within new ROM. It's impossible. The only way to get your DRM keys back is to restore your own TA-Partition (flashing any other person's TA-Partition will definitely brick your device), where DRM keys are located at.

Locking your bootloader doesn't restore your DRM keys. All you can do for now is to temporarily get some functions working only with some MODS, which are located somewhere in XDA.
[Xperia Z General] ast9011:
my drm keys are lost after re locking BL. now i want to unlock it again but it fails every time i enter the unlock code.. is this because of lost drm keys? any assistance please?
[Moto G General] Zerelth:
Ok since LuneOS has been officially supportted, should we consider porting it to our beloved Moto G (It's availble for N4 and N7 though)

Look here: http://pivotce.com/2014/09/01/official-release-of-luneos-and-project-updates/
[Moto G General] MarckozZ:
Honestly, I wouldn't port it since it is not a very friendly OS right now... Besides, it's not as clean and nice as KK..
[Moto G General] Zerelth:
Yeah well, I'm just saying that it COULD be ported to our device. Though I'd prefer using PA now XD
[Moto G General] MarckozZ:
Obviously it's possuble to port it.. But, if someone does it, it will be just like an experiment, not for daily driver since you'll drive crazy, you'll miss KK more that ever :p
[Moto G General] ZareliMan:
It's a nice initiative but this is one of the few devices that I'd rather keep stock, as it supports 4.4.4 and you can get pretty nice functionality on the stock rom (which is very optimized) with some xposed packages.

If a dual boot option is possible I would maybe try LuneOS.
[Moto G General] keenofhiphop:
MultiROM is already ported to moto G falcon... just a matter of time and developers.

In fact, what we need is a port of libhybris, that can be used to boot Linux systems, currently available Sailfish OS and LuneOS, I would prefer Sailfish... However, to do this work, we need someone who has the skills, the device and wants to do it, because it is some difficult sh*t to and not comparable to build a custom ROM.

I experienced that, most of the time, it lacks two those aspects. We could as well pay a dev to do so, but i don't know...

However, MultiROM doesn't work with recent Sailfish ports and probably won't.

There is a guide on how to port Sailfish OS to existing android devices, which includes setting up libhybris, of course. The problem is, it's cased on cyanogenmod 10.2 which we don't have on the moto g and there are some problems with KitKat.

The Moto G is a device with a lot of fans, but as well there are more which use the falcon variant and so have to wait. But I believe it will only be a matter of time, till libhybris will be working either the falcon the peregrine

Gesendet von meinem XT1039 mit Tapatalk
[Android Apps and Games] StercoreCode:
Maybe interesting car-runner.The most important that you can spend your time without benefit.

Only one question - how to win?:p

https://play.google.com/store/apps/details?id=com.stercore.code.android&hl=ru
[Micromax Canvas 4 A210] raj729:
how to make 512 mb ram android phones faster
[Micromax Canvas 4 A210] magmapsycho:
try to close apps that still run in memory even after you close them to free up ram or avoid installing them completely
[Micromax Canvas 4 A210] ceasar47:
Stop auto start of apps.... Like fb,messenger,whatsapp etc....
[Micromax Canvas 4 A210] yogesh.kalyana:
Start using rooted apps!

first start using Greenify and cleanmaster with root acess

that is definately help you !
[General Topics] cswarrior:
Hey everyone!

I signed up to be with Softbank(Jp) last year and got myself the Sharp 203sh, it's a good phone but I wanted a new phone. I did a bit of research and found a few sites with the SIlver Sim card APN setup and thought it'd work for the new phone.

Today I recieved the phone and inserted these settings but it couldn't connect to the data services but only the calling services.

I did more research and found out that android devices from softbank uses a unique username and password for their APN.

Does anyone know how to extract the information out from my softbank droid? If i root my phone (i don't know if i can unroot it) and use catlog , would i be able to grab the information?

any help is appreaciated! thanks in advance!!
[General Topics] puchg350:
Silver SIM

Will you please give me the details about Silver Sim card setup? I have a silver SIM but cannot even use calling services. Thanks
[General Topics] cswarrior:
Sure i`ll PM you the info. I`ve got the silver sim that comes with a 2year contract though, are you using the same one?
[General Topics] puchg350:
Thanks, but somehow I found the solution. My Silver SIM is only good for old phones, but not for smart phones. It seems I must replace the SIM. If it doesn't work, I will ask you for more details.
[General Topics] cswarrior:
Oh I see, that's cool, hopefully it does out for you.I really want to sort my apn issue out but no luck
[JAMin, XDA Neo, S200 General] coldmantis:
Hi I was in Hong Kong and I bought the O2 XDA NEo the problem is that everytime I hit around 45% the shuts off, if I try to turn it on it will go to the windows splash screen and go into a restart loop but if I charge my phone it won't happen. Is something wrong with the phone or the battery is diffective?
[JAMin, XDA Neo, S200 General] RaptorRVL:
How long does your phone last on a battery? And what are you using with that (e.g. when you always have bluetooth and wifi enabled the battery won't last as long as when you don't have those enabled).

Because it could be your battery is faulty, or the chip on the battery is faulty (from which the % is read).

If your phone, fully charged, lasts for a few days (3,4,5 depending on what you do) it doesn't seem the battery would be faulty but the readout is not that good.

Have read things before about phones shutting down when it says there is still 20% battery left or something which might just be a mis-reading. When I use the battery of my old magician the readout seems to be fine although when I use the battery that came with the prophet I saw it shutdown once at 10% (though I never make that, because it's always charged before that point :) ).
[JAMin, XDA Neo, S200 General] coldmantis:
its actually gotten worst now it will shut down at around 60% and will go into a restart loop if I try turning it on
[JAMin, XDA Neo, S200 General] RaptorRVL:
hmm, something is not right (doh). I recommend you bring the device back for servicing.

However, if you have a battery laying around from a magician or another prophet try it with that one and see what happens. At least you can rule out the battery/device. But otherwise you can leave the tech-guys to that :)
[JAMin, XDA Neo, S200 General] coldmantis:
I did order a new battery from ebay but its not here yet so I can't rule it out and as for repair it will be kind of hard since I bought it in Hong Kong while on a vacation and now I'm back to canada.
[JAMin, XDA Neo, S200 General] coldmantis:
so I finally got the battery from ebay the 45% shut off problem is gone but now I have new problems, I notice with this battery the neo runs slower which dont' make sense and for some reason it won't charge when the neo is off only when on, also it won't charge pass 89% so the light on top is never green??. The first thing I did when I got this battery is fully discharge it until the phone shut off and recharged it while its on because it won't charge when it's off? any ideas or did I get another defective battery??
[JAMin, XDA Neo, S200 General] RaptorRVL:
Hmm.. that's weird. Did you upgrade it with another rom perhaps (e.g. AKU 3.2 or something). Because those roms sometimes have troubles with charging.

But the phone should be charging allright when you turn it off (well, make it go in standby that is). Or do you completely turn the device off?

Can't imagine you have 2 faulty batteries though :/ Maybe there is something wrong with the device? Hard to tell...
[JAMin, XDA Neo, S200 General] coldmantis:
completely turned off and I'm using 2.3 rom LvsW_Edition
[JAMin, XDA Neo, S200 General] coldmantis:
great I tried flashing to the dopod rom got an error and stuck at the 3 colour screen i think its the bootloader what do i do now?
[JAMin, XDA Neo, S200 General] RaptorRVL:
erm... well you could try the 2.20 qtek rom which seems to be working well for quite some people (found here).

Although you have to make sure you read that thread good and use the ROMUpdateUtility_NoID.exe (found on ftp) to upgrade (or you download RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe and take the ROMUpdateUtility_NoID.exe from that using WinRAR, but it's wasting bandwidth a bit :) ).

Update instructions:

1: With the qtek 2.20 rom you need to extract the zip and the exe file in the zip with WinRAR.

2: Then there is one folder called 'OutputFile' and a folder called 'RUU_TOOLS'.

Inside the RUU_TOOLS there are some other folder (prophet -> WWE), when you go through them and in the WWE folder you see a bunch of files (readme.doc, enterbootloader.exe etc etc).

You need to copy ROMUpdateUtility_NoID.exe to the WWE folder with all the files. And you also need to copy the 'nk.nbf' file to the WWE folder (from the 'OutputFile' folder).

3: And then you need to put your phone in bootloader mode and run ROMUpdateUtility_NoID.exe to upgrade, which should work nicely then.

Hope that was a good and clear explaination :)
[JAMin, XDA Neo, S200 General] coldmantis:
I just reflashed the rom with LvsW_Edition and it brought my phone back to life but I still have the 89% problem but thanks for your help anyways
[JAMin, XDA Neo, S200 General] RaptorRVL:
Well, I have no idea what could be wrong.

My phone charges when it's turned off, so I guess it must be a phone problem :/ Maybe a charger problem, but that seems unlikely.
[JAMin, XDA Neo, S200 General] coldmantis:
well I don't know what happened I guess after the 2nd discharge the phone is stuck at 98% charge now not 89% I dont' think it's the phone or the charger since the old battery that dies at 50% charges with the phone on or off, I'll keep discharging this battery maybe it will eventually bring it to 100% full charge
[JAMin, XDA Neo, S200 General] coldmantis:
I had enough with this battery its completely unusable with this battery in my phone it slows down so much that navigation is impossible, I have to reset the damn thing every time. I was reading on a post here regarding a 1800mah capacity battery for the prophet so I bought that on eBay and sending this garbage back.
[LG Optimus L90] lecterek:
Hello everyone,

my D405n is partially correctly recognized as w7n:

ro.product.board=w7n

ro.build.product=w7n

ro.cm.device=w7n

ro.product.device=w7n

ro.build.product=w7n

ro.cm.device=w7n

However partially incorectly as w7ds:

ro.hardware=w7ds

ro.boot.hardware=w7ds

I have unrooted my L90 using towelroot, unlocked bootloader and install recovery with

[GUIDE] Unlock Bootloader and Flash Custom Recovery L90 D410, D405n, D405 [CWM][TWR] method using file for D405n and flashed ROM from @Quarx. In order to flash the ROM I had to remove hardware=w7 check. Now automatic update works in the sense, that incremental update is downloaded, but due to hardware=w7 check I have to modify the updater script every time. Any idea how to correct ro.hardware and ro.boot.hardware entries? I have attached my build.prop file and output from getprop command, if that could be helpful.

Best regards
[LG Optimus L90] shinobisoft:
I'll send [MENTION=513620]Quarx[/MENTION] a link to this thread.
[LG Optimus L90] SubliemeSiem:
Strange, I have a D405n too, but never had this issue. I wrote a guide explaining the way I unlocked the bootloader here. I used Quarx' latest TWRP, which can be found in his thread and just did a full wipe and flashed CM after that. Seemed to work for me. I would just try reflashing the KDZ again and restarting the unlock process with the newest files available.

EDIT: I just checked my build.prop and my w7n is recognized as a w7. The device is still recognized as the D405n though, so NFC does show up in the menu.
[LG Optimus L90] lecterek:
OK, thx. I hope he could provide some suggestions.
[LG Optimus L90] lecterek:
Is it necessary to flash the KDZ? Flashing/dd aboot.bin again should be sufficient I think. I did it, but situation is the same. I have checked aboot.bin files for D405n linked by people in different posts over xda forum (your link as well) and all the files are identical, so in my opinion there is no newest aboot.bin. Concerning TWRP I have tried latest Quarx version and also this version. No difference concerning w7n and w7ds mismatch.

Yesterday I tried also to flash Quarx' CWM instead of TWRP and surprisingly automatic update worked with no problem with hardware=w7 check. However, output/content of getprop command and build.prop file are unchanged. Strange. Looks like with TWRP hardware=w7 check fails while with CWM everything is OK, which would indicate different getprop output for different recovery.
[LG Optimus L90] SubliemeSiem:
Might be you guys got the D405n with softwareversion 10a, where my device had 10b.. Seen this before and most users with that combination seem to have issues. Might also be a total coincidence though. I don't know what the difference is, but I do know the Russians that made the aboot.bin files made a seperate one for D405n_10b and for D405_10a. So either the version for D405n combined with 10a is missing or you should be able to use one of those two versions.. But once again, this is pure speculation, I don't know if this can cause these issues.
[LG Optimus L90] lecterek:
Is it OK, to use aboot.bin_D405_10a for D405n? I mean, no soft brick in that case? With stock ROM I had 10b as well.
[LG Optimus L90] SubliemeSiem:
I'm not sure, but even then you should still be able to flash the kdz and start over. It doesn't take that long to go through the entire process, I've done it multiple times already. I don't have these problems, so I can't experiment with these files.
[Android Q&A, Help & Troubleshooting] raj729:
is there any custom rom stable for a76 mmx its getting too slow on stock rom....
[Android Q&A, Help & Troubleshooting] Rishabh02:
You can try lollifox
[Samsung Galaxy S II Plus] GHsR:
Greetings to all! I ported the firmware MIUI v5 based on cm11 m9 for I9105, but there are bugs in the firmware and should be corrected. I need help for that would fix bugs. Now it is impossible to fix Call Recording.

Log when you press Record:

D/AudioPolicyManagerBase( 152): getInput() inputSource 4, samplingRate 8000, format 1, channelMask 10, acoustics 0
W/AudioPolicyManagerBase( 152): getInput() could not find profile for device 80000040, samplingRate 8000, format 1,channelMask c000
E/AudioRecord( 715): Could not get audio input for record source 4
E/AudioRecord-JNI( 715): Error creating AudioRecord instance: initialization check failed.
E/android.media.AudioRecord( 715): Error code -20 when initializing native AudioRecord object.
V/Mp3Recorder( 715): Apply new AudioRecord
V/Mp3Recorder( 715): Mp3Recorder prepared
D/MiuiPhone:MiuiCallRecorder( 715): stopRecording(3)
E/MiuiPhone:MiuiCallRecorder( 715): Error when stop call recording
E/MiuiPhone:MiuiCallRecorder( 715): java.lang.NullPointerException
E/MiuiPhone:MiuiCallRecorder( 715):	at miui.media.Mp3Recorder.stop(Mp3Recorder.java:321)
E/MiuiPhone:MiuiCallRecorder( 715):	at com.android.phone.MiuiCallRecorder.stopCallRecord(MiuiCallRecorder.java:139)
E/MiuiPhone:MiuiCallRecorder( 715):	at com.android.phone.MiuiCallRecorder.startCallRecord(MiuiCallRecorder.java:120)
E/MiuiPhone:MiuiCallRecorder( 715):	at com.android.phone.MiuiCallNotifier.startCallRecord(MiuiCallNotifier.java:288)
E/MiuiPhone:MiuiCallRecorder( 715):	at com.android.phone.MiuiInCallScreen.handleOnscreenButtonClick(MiuiInCallScreen.java:267)
E/MiuiPhone:MiuiCallRecorder( 715):	at com.android.phone.MiuiInCallTouchUi.onClick(MiuiInCallTouchUi.java:342)
E/MiuiPhone:MiuiCallRecorder( 715):	at android.view.View.performClick(View.java:4445)
E/MiuiPhone:MiuiCallRecorder( 715):	at android.widget.CompoundButton.performClick(CompoundButton.java:100)
E/MiuiPhone:MiuiCallRecorder( 715):	at android.view.View$PerformClick.run(View.java:18446)
E/MiuiPhone:MiuiCallRecorder( 715):	at android.os.Handler.handleCallback(Handler.java:733)
E/MiuiPhone:MiuiCallRecorder( 715):	at android.os.Handler.dispatchMessage(Handler.java:95)
E/MiuiPhone:MiuiCallRecorder( 715):	at android.os.Looper.loop(Looper.java:136)
E/MiuiPhone:MiuiCallRecorder( 715):	at android.app.ActivityThread.main(ActivityThread.java:5139)
E/MiuiPhone:MiuiCallRecorder( 715):	at java.lang.reflect.Method.invokeNative(Native Method)
E/MiuiPhone:MiuiCallRecorder( 715):	at java.lang.reflect.Method.invoke(Method.java:515)
E/MiuiPhone:MiuiCallRecorder( 715):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:796)
E/MiuiPhone:MiuiCallRecorder( 715):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:612)
E/MiuiPhone:MiuiCallRecorder( 715):	at dalvik.system.NativeStart.main(Native Method)
V/Mp3Recorder( 715): AudioRecord released
V/Mp3Recorder( 715): Mp3Recorder released
[Samsung Galaxy S II Plus] LuK1337:
Call recording isn't even working on CM.
[Samsung Galaxy S II Plus] GHsR:
Thank you, I have not tested this on cm.
[Samsung Galaxy S II Plus] GHsR:
Found a patch to record a conversation with a line for the kernel.

code.google.com/p/2-way-call-recording/wiki/BuildKernelForMSM7227

code.google.com/p/2-way-call-recording/source/browse/patches/vocpcm.s

Who can check it?
[Samsung Galaxy S II Plus] LuK1337:
it's for MSM7227, we have BCM processor.
[Samsung Galaxy S II Plus] SH1M4BD3:
Make the build posdible for s2vep too mate, thanks

OrdinaryNoob
[Samsung Galaxy S II Plus] GHsR:
I have not found this patch for BCM

Soon will create build for I9105P from patchrom
[Samsung Galaxy S II Plus] GHsR:
Test version of MIUI v5 4.4.4 for I9105P

https://yadi.sk/d/W3bqwY_wbEHVB

Does not work:

1. Compass

2 Activation of SIM card services xiaomi

3 Bugs in miui browser

4. Call Recording

Nfc not tested
[Samsung Galaxy S II Plus] ehsan.gdrzi:
does it work on 4.2.2

or just 4.1.2 ???
[Samsung Galaxy S II Plus] GHsR:
it work on 4.2.2
[Samsung Galaxy S II Plus] SH1M4BD3:
S2vep??trully works without need to flash s2ve recovery???

OrdinaryNoob
[Samsung Galaxy S II Plus] SH1M4BD3:
Here some reviews : works great okay Music improved,Equalizer works..worth to flash..great job mate keep it up..miui6 :D

OrdinaryNoob
[Samsung Galaxy S II Plus] GHsR:
works on s2vep recovery