Showing posts with label users. Show all posts
Showing posts with label users. Show all posts

Sunday, 11 October 2015

[LOST IMEI] Warning for D410HN users (Brazilian Dual-SIM with NFC variant)



This warning also serves to other variants.

I see that many users of this variant are using other variant binaries and images trying to unlock the bootloader and install TWRP recovery.

My advise is to not do this or you can end with a brick.

Even worse, when trying to unbrick the phone, people are using other variant nand backup images, this will lead you to the infamous lost IMEI problem, and from this point if you don't have your modemst partitions backups, you are lost.

Flashing KDZ won't recover these partitions, they are unique to your phone and are not flashed in a normal KDZ flash, the only way to flash them is in TWRP or ADB.

I already supplied the proper D410HN Kitkat v10c and Lollipop v20a/b/c (they are the same) unlocked aboots and bootstacks but people insist flashing files from other variants.

My advise is, after rooting your phone, before doing anything else, the first thing you must do is to backup your modemst1 and modemst2 partitions to make sure you IMEI data is safe. You can make this backup in ADB or Android Terminal app with:


Code:


dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/storage/external_SD/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/storage/external_SD/modemst2.img


This will save modemst1.img and modemst2.img in your external microSD. If you want to save in your internal SD, replace /storage/external_SD to /sdcard.

Also, make a nand backup image in case of you need to make a testpoint or direct flash in nand to attempt to unbrick the phone.


Code:


dd if=/dev/block/mmcblk0 of=/storage/external_SD/unbrick.img bs=512 count=323583

This will save an unbrick.img in your external microSD. If you want to save in your internal SD, replace /storage/external_SD to /sdcard. Do not share this file with anyone else, this image have your IMEI data.

Why make your own unbrick.img file?

If you look at the partition table, you will have this:





Code:


GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit s
unit s
(parted) print
print
Model: MMC 8WMB3R (sd/mmc)
Disk /dev/block/mmcblk0: 15269888s
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start      End        Size      File system  Name      Flags
 1      16384s    147455s    131072s  fat16        modem
 2      147456s    149503s    2048s                  sbl1
 3      149504s    150527s    1024s                  rpm
 4      150528s    151551s    1024s                  tz
 5      151552s    152575s    1024s                  sdi
 6      152576s    156671s    4096s                  aboot
 7      156672s    157695s    1024s                  rpmb
 8      157696s    158719s    1024s                  tzb
 9      158720s    162815s    4096s                  abootb
10      162816s    166911s    4096s                  pad
11      166912s    173055s    6144s                  modemst1
12      173056s    179199s    6144s                  modemst2
13      179200s    211967s    32768s                misc
14      212992s    278527s    65536s    ext4        persist
15      278528s    323583s    45056s                laf
16      327680s    372735s    45056s                boot
17      372736s    417791s    45056s                recovery
18      417792s    423935s    6144s                  fsg
19      425984s    427007s    1024s                  fsc
20      427008s    428031s    1024s                  ssd
21      442368s    443391s    1024s                  DDR
22      458752s    459775s    1024s                  encrypt
23      459776s    460799s    1024s                  rct
24      475136s    491519s    16384s    ext4        drm
25      491520s    507903s    16384s    ext4        sns
26      507904s    548863s    40960s                factory
27      548864s    614399s    65536s                fota
28      622592s    624639s    2048s                  sbl1b
29      624640s    690175s    65536s    ext4        mpt
30      704512s    909311s    204800s  ext4        cust
31      917504s    918527s    1024s                  eksst
32      933888s    5128191s  4194304s  ext4        system
33      5128192s  6971391s  1843200s  ext4        cache
34      6971392s  15223807s  8252416s  ext4        userdata
35      15237120s  15269854s  32735s                grow

(parted)






This ubrick image have your partition table and the partitions until sector 323583 (partition 15 - laf), which is enough to enter in download mode and flash KDZ with LG Flash Tool and make a complete and perfect recover. This also explains why when you flash an unbrick image from a unknown source and variant you lose your IMEI, modemst1 (11) and modemst2 (12) partitions are flashed along, overwriting your unique data.

Keep your backups in a safe place and now you can go ahead and unlock the bootloader, install TWRP, change partitions size and etc knowing that if anything goes wrong, if you manage to unbrick your phone, you won't loose your IMEI.

Good luck :good:



Music player dev - protecting users against Stagefright 2?



We write a music player app. The info on Stagefright 2:

https://blog.zimperium.com/zimperium...-mp3mp4-media/

says that third party music players that use Android's standard media playing libraries are vulnerable. OS patches are on their way but we'd like to do our bit, we support down to 2.1.

But dev-level details on the exploit seem to be hard to find right now.

It's something to do with the metadata of the file, is that just id3 tags? If so it would be relatively simple to edit the file to sanitise them before passing them to MediaPlayer, maybe raising an error if the file can't be written to. Might have to use a third-party library to do that rather than Android's parser which might trigger the exploit.
It mentions 'Android previewing the file' - what does 'previewing' mean? Is that the browser calling MediaPlayer.setDataSource() or MediaPlayer.prepare()?
It also mentions 'libutils' - is that MediaPlayer accessing libutils or does the app need to access libutils in some other way? I'm guessing it's not only MediaCodecInfo and friends as they are API 16+.



Saturday, 10 October 2015

How can you guys survive without an SD slot (Especially Nexus users) ?



Hi,

Just wanted to discuss, as I'm curious about the opinion of people here, especially those (But not limited to) who are getting an Nexus phone which has obviously no SD card slot;

Had an Optimus One from 2011 to 2014 as my first phone and then switched to Galaxy S4. Sometimes I thought maybe I could have gotten a Nexus, or not sure, maybe a Nexus could be my next phone, or even a Sony (I like my S4. But when I got it, I didn't knew about KNOX haha. I'd rather not support Samsung in the long run with their KNOX flag I guess).

The lack of an SD card slot always drove me away from Nexus phones (Except Nexus One, which I did considered long ago), although it's true that Nexus phones look pretty amazing. How did you guys (Not limited to Nexus) chose a Nexus, not fearing that you might end up lacking storage at some point? I used to store Dreamcast ROMs in my SD card, and played around with Dolphin emulator for a while, these are quite huge files, and if you put movies in the phone too haha, space can run out pretty quick.

I have the 16GB variant of the S4 along with a 32GB microSD card (External SD close to full. Might upgrade to 64 eventually) - My 32GB card is close to full, so obviously a 32GB phone with no SD is a big no-no. 64GB would be the bare minimum, considered that storage space would be splitted between the user data (/Data/Media) and the /Data partition itself for app storage, also not forgetting the /System partition, I might even get tight on storage on a 64GB phone. So the wisest choice would be to get a 128GB version which is costly anyway.

I discussed about my point/needs myself, altough I'm especially curious, while I will have to say goodbye to SD cards slot at some point anyway, some people here did chose recent phones with lack of SD support without any fear of lacking storage (Which unfortunately drive me away from Nexus, but might consider a 128GB variant).

How is the lack of an SD card slot not a deal-breaker to you, and worth all the other features, guys?
Thank you for reading.



Marshmallow users : is voice dialer still alive ?



Hi,

I'm interested in the Marshmallow update for Nexus 6. I don't own a Nexus 6 so that's why I'm asking this question to you guys : when you long press the button of your wired headset while your screen is off and locked, does it still launch the ugly Voice Dialer or has it finally been replaced by Google Voice Search/Now ?

Because the Voice Dialer feature on my Galaxy S5 is just driving me nuts :silly:

Thanks !



Wednesday, 7 October 2015

For WhatsApp users



For you WhatsApp users that don't plan on rooting for whatever reason:

They just re-implemented Google Drive backups. Version 2.12.302 from www.whatsapp.com/android has this functionality enabled.
2.12.300 is the latest from the Play Store now.

Just FYI for those that use it and will eventually transfer it + history to your new 6P

:)



Z3 users: Sony’s Concept for Android: Marshmallow available to try for 10,000 users






Download the app to register:
https://play.google.com/store/apps/d...ignup&hl=en_GB

only for these countries: Denmark, Estonia, Finland, Germany, Iceland, Ireland, Latvia, Lithuania, Norway, Sweden and United Kingdom.

someone please share the APK



Join LG G4 (Indian Users) KIK Discussion Group



Hi Guys

Those who want help, Root about LG G4 and Other Devices and all Android APK Related discussions Join to Our KIK Messenger Group.

Just Install KIK Messenger and Search Group Hashtag #XDALGG4 or Scan the Below QR Code using KIK

This Group is not only for indian Users, Anyone can join who have any devices.





Tuesday, 6 October 2015

[Q] Is there still a great number of users that use the nexus player?



I'm looking into purchasing two nexus players so I can play games on both of them and play multiplayer with them, but is there still a great user base where if I were to buy these devices, would the support cease shortly or have a great longevity?



There is good news for Samsung Galaxy Note 4 users under T-Mobile



There is good news for Samsung Galaxy Note 4 users under T-Mobile that there device is in the list leaked by their carrier that it will get Android 6.0 Marshmallow soon check the list here for confirmation
As it stands, we can start taking bets which Android device — aside from the Nexi — will be the first to receive Android 6.0 Marshmallow. Any guesses?