iOS 7 Killed Off Some Unlicensed Lightning Cables, But Here’s A Fix That Might Work For You | Cult of Mac

iOS 7 Killed Off Some Unlicensed Lightning Cables, But Here’s A Fix That Might Work For You | Cult of Mac

iOS 7 Killed Off Some Unlicensed Lightning Cables, But Here’s A Fix That Might Work For You

481

Tweet

John Brownlee (3:18 am PDT, Sep 19th)

It’s not just you: iOS 7 has seemingly killed off support for some unlicensed, third-party Lightning cables.

We’re seeing numerous reports from users that iOS 7 has blocked support for many knock-off Lightning chargers. When you plug them in, iOS 7 will warn you that the cable is unlicensed and may not function properly, and will then fail to sync or charge. This does not appear to be universal, some cables are still working fine despite the warning. But a large number have been rendered non-functional.

I can confirm this myself. I have a short, three-headed hydra of a cable that I love to use with an external battery pack when I’m on the go: when head is a Lightning charger, the next a 30-Pin, the final one a micro-USB. Since iOS 7 officially dropped, the Lightning adapter has stopped working, while the rest of the cable syncs and charges just fine.

You might recall that when the earliest iOS 7 betas hit, iOS 7 would warn users when an unsupported Lightning cable was plugged in, but otherwise didn’t take any action. Unlicensed Lightning cables would sync and charge just fine. Starting with the GM, however, Apple has apparently started enforcing compliance with its MFi licensing program for all third-party cables… and shutting out anyone who dares to release a Lightning knock-off without paying Apple their share.

However, some devious third-parties have already figured out how to fool Apple’s detection mechanism. It’s possible that some of the unlicensed cables that still work implement this crack.

Although I have had no luck getting this to work with the third-party Lightning cable I have here, some users are having luck with this workaround:

1. Turn on USB power.
2. Plug in Lightning cable to iPhone.
3. Dismiss any warnings.
4. Unlock your iPhone.
5. Dismiss any remaining warnings.
6. Now with the screen turned on, unplug the Lightning cable.
7. Plug it back in.
8.Dismiss warning again. It should now charge.

It should be no surprise that Apple is officially ending support for third-party, unlicensed Lightning cables. The fact that counterfeit cables can now be detected using Lightning’s advanced chip detection was a major reason why Apple shifted to the standard to begin with.

Still, this is a big bummer to me, and no doubt a lot of other Apple customers. It might not be licensed, but my tri-headed hydra of a cable served me well, and there’s nothing licensed that does the same thing. Fingers crossed someone fixes this, and soon.

Is your unlicensed Lightning cable still working after the iOS 7 update? Is it broken? We’re trying to gather more data. Let us know what cable you have, and if it’s still working in the comments.

Read more at http://www.cultofmac.com/246236/ios-7-killed-off-unlicensed-lightning-cables-but-heres-a-fix-that-might-work-for-you/#F2mvBCc5P6bFSYMJ.99

APP][2.1+][ V1.14] BetterBatteryStats

http://forum.xda-developers.com/showthread.php?t=1179809
I wrote BetterBatteryStats because I was missing the great battery history that Spare Parts allowed to call on Froyo:
- General "other stats "overview: Awake, Deep Sleep, Screen On, Phone On, Wifi On, Wifi Running ratios
- Kernel Wakelocks
- Partial wakelocks
- Alarms/Wakeups
- CPU States
- Network stats
- Process stats with User and System CPU time


BetterBatteryStats is calling the "batteryinfo" service of Android to retrieve data already lying there without generating overhead.

BetterBatteryStats is focussing and has been tested on Froyo, Gingerbread, Honeycomb (3.1, thanks to daveid), ICS on different ROMs and Kernels. 

What are wakelocks and why should you care about them?
When it comes to Android the most discussed and commented topic that I know is battery drain / battery life. I'm a quite heavy user because I spend a lot of time on the train every day reading my mails, surfing and listening to music but still my phone is off for a long time during the day and while I accept the battery being drained while I use the phone I care about it draining slowly while "doing nothing".


Wakelocks or to be more precise partial wakelocks is a pattern (in fast a class) than helps devs to make sure that important pieces of their code do not get interrupted.
Basically the phone has (simplified, kernel devs don't shoot) three states:
1. awake with screen on
2. awake
3. sleeping (that's you phone favorite state)

The transitions are from (1) to (2) and finally from (2) to (3). Now as long as you use your phone it's in (1) and does not leave that state as long as you keep using it interactively. If you stop using it the phone is aiming to go to (3) as fast as possible.
And here's where wakelocks are important: as our phones as smartphones they tend to do background processing. Some of this processing is important like e.g. making a phone call, listening to music or synchronizing your contacts.
As the phone wants to go from (2) to (3) and on the other hand you don't want to hang up while you are in a call the app keeps hold of a wakelock to prevent that transisiton. When you hang up the partial wakelock gets release and here we go (the phone goes to sleep).

So partial wakelocks is a tool and it's not something that we should forbid for obvious reasons. Now there are cases when the design on an app is not real life proven (conditions of poor of no converage) and the wakelocks have negative effects because they are held unnecessarily or for too long.
BetterBatteryStats identifies these wakelocks and using your expertise or the once from our users here you can understand what happens and find a strategy to change that for the better.

Try it yourself

[AOSP] Official 4.3 - S4 Google Edition Rom

►►[AOSP] Official 4.3 - S4 Google Edition - Finaly - Feel the Experience of Nexus◄◄ - xda-developers

gt-i9505 google edition rom / firmware

Free vpn services

most of them seems to be pptp unsecure.

http://us.hotfreevpn.com/
http://superfreevpn.com
http://www.justfreevpn.com/
http://real-vpn.com/
http://www.allfreevpn.com/list-of-free-vpn.php
http://us.newfreevpn.com/
http://www.freecanadavpn.com/
http://www.getusvpn.com/

[Rom]Google Edition Galaxy S4 rom for i9505[8 August][Odexed rom android 4.3 & 4.2.2] - xda-developers

[Rom]Google Edition Galaxy S4 rom for i9505[8 August][Odexed rom android 4.3 & 4.2.2] - xda-developers



i9505 android stock rom

Google Edition Galaxy S4 for i9505
Enjoy pure android 4.2.2 & 4.3 Odexed, Full rooted & busybox

 Google Edition Galaxy S4 for i9505 without any visual changes fully stock, clean & stable

Slingbox Answers Forum: Remote Control Setup to LexuzBox F90HD

Slingbox Answers Forum: Remote Control Setup to LexuzBox F90HD
Arquivo .BIN para controle F90 do SlingBox
Remote Control Setup to LexuzBox F90HDlexuzbox f90 slingboxslingbox funcionar com Lexuzbox F90HD

Re: Remote Control Setup to LexuzBox F90HD

In the 6 months since my last posting this device has appeared on the Logitech database, so I have been able to build a Custom Remote.  Give it a try and please let me know if it works.

Attachments:

• Lexusbox F90HD.zip (2.2 K)

https://docs.google.com/file/d/0B47a_Ts285PeM3VrNkI0ZWtINlk/edit?usp=sharing

Find your lost phone with Android Device Manager

Find your lost phone with Android Device Manager | Official Android Blog

Find your lost phone with Android Device Manager

August 2, 2013

Have you ever lost your phone in between the couch cushions or forgot it in a restaurant? Or maybe searching for your phone before you rush out the door is part of your morning routine? Later this month, the new Android Device Manager can help you out. It's one of a few simple features you can use to keep your device—and the data you store inside—safe and secure.

Locate and ring your misplaced device 
If you ended up dropping your phone between those couch cushions, Android Device Manager lets you quickly ring your phone at maximum volume so you can find it, even it's been silenced. And in the event that your phone or tablet is out of earshot (say, at that restaurant you left it at last night), you can locate it on a map in real time.

Protecting your personal information and data
While losing your phone can be stressful, Android Device Manager can help you keep your data from ending up in the wrong hands. If your phone can’t be recovered, or has been stolen, you can quickly and securely erase all of the data on your device.

Availability and getting started 
This service will be available later this month on devices running Android 2.2 or above; to use it, you also will need to be signed into your Google Account. There will also be an Android app to allow you to easily find and manage your devices. Stay tuned!

Posted by Benjamin Poiesz, Product Manager, Android

How To Root Android 4.3 On Nexus 4, 7, 10 And Galaxy Nexus | Redmond Pie

How To Root Android 4.3 On Nexus 4, 7, 10 And Galaxy Nexus | Redmond Pie
http://www.clockworkmod.com/rommanager

Android 4.3 came to life for Nexus devices earlier last week, and since then, it has received significant attention. For those lucky owners of these devices, the new version of Google’s smartphone and tablet operating system has a lot to offer, and then some more, in terms of fixes and improvements. Now that all of that’s settled and done, and the code has been rolled out to AOSP, it’s time for modifications and developer-community-driven enhancements.

Of the last category, the first are foremost that comes is rooting, i.e., gaining superuser access for your device. Luckily, thanks to developers such as Chainfire, that’s already pretty doable on the likes of Nexus 4, 7, 10, and Galaxy Nexus. In this article, we’ll guide you how to root Nexus 4, Nexus 7 (2012), Nexus 7 (2013 – unstable), Nexus 10 and Galaxy Nexus running Android 

Before we begin, please note that you follow these instructions at your own risk. While tested and proven safe, any resulting damage to your device from following this procedure is on you. We cannot be held liable for a bricked/damaged device.

For the sake of this guide, we’ll be using two different methods. The first one uses Chainfire’s Auto Root that’s more suited for the Nexus 7, while the generic flashing of custom recovery and SuperSU for the rest of the devices.

Root Nexus 7 (Wi-Fi & 3G) using CF-Auto-Root

Requirements:

• CF Auto Root package for Nexus 7 Wi-Fi [download] / CF Auto Root package for Nexus 7 3G [download]
• Android USB driver for Nexus 7 installed on you computer.
• USB Debugging enabled on the device.
• 80% or more battery power remaining on the tablet.
• Set up Android ADB and Fastboot on Windows.

Please note that these instructions are for carrier unlocked variants of Nexus 7, and will work only on Nexus 7.

Procedure:

Step 1: Extract the downloaded CF-Auto-Root package and keep the files in a convenient location on your machine.

Step 2: Reboot the Nexus 7 into fastboot mode using the combination of volume up, volume down and power buttons.

Step 3: Once in fastboot, connect the device to the PC using the supplied USB cable. Wait for the fastboot drivers to configure themselves.

Step 4: Navigate to the folder where the downloaded files from CF Auto Root were extracted, and look for the file that says “root-windows.bat”. Double-click to run it.

Step 5: Follow the on-screen instructions until you reach the point when the tablet reboots back into normal mode.

There you have it – your Nexus 7 on Android 4.3 is now rooted. You may verify that by going to the app drawer and looking for SuperSU app.

Root Nexus 4, 10 and Galaxy Nexus using SuperSU

Requirements:

• Android SDK configured on your computer
• Custom recovery like ClockworkMod or TWRP which you can flash using the Nexus Root Toolkit.
• Nexus 4, 10 or Galaxy Nexus with unlocked bootloader which you can have using the Nexus Root Toolkit mentioned above
• SuperSU 1.50 by Chainfire [download]

Procedure:

Step 1: Download the SuperSU ZIP package and transfer it to the root of your device.

Step 2: (Optional) If you don’t have a custom recovery installed, do it now using your preferred method (ideally you’d want to do that via fastboot).

Step 3: Boot the device into recovery and flash the SuperSU ZIP file.

Step 4: After you’ve flashed the superuser package, wipe cache and dalvik cache, just to be on the safe side.

Step 5: Reboot.

That’s it – your Nexus 4, 10 or Galaxy Nexus is now running rooted Android 4.3.

Fazendo backup da Chave de Segurança Bradesco Eletrônica [Android]

http://android.webhostid.com/2013/05/how-to-backup-restore-and-changing-your-android-id-with-titanium-backup/

http://www.ibrunosousa.com/2012/10/backup-token-bradesco-android.html?m=1

Fazendo backup da Chave de Segurança Bradesco Eletrônica [Android]
Pessoas vão comentar: "Ué? Android? No seu site?". Sim. Android no meu site. Embora não pareça, este site não é dedicado só pra Wireless, é dedicado para tecnologia em geral. :)

Enfim, no Bradesco, temos a opção de cadastrar um "Token", ou "Chave de Segurança", em nosso smartphone Android ou um dispositivo com iOS.

Entretanto, quando fazemos um "Hard Reset" em nosso Android, ou simplesmente trocamos de ROM, a chave de segurança é perdida, mesmo fazendo o backup da mesma utilizando o "Titanium Backup" por exemplo.

E para recadastrar essa chave, temos que ligar para o nosso gerente, entrar em contato com o Fone Fácil, enfim, é aquele parto todo!

E então? Como fazer o backup da chave?
Fácil. Primeiramente é necessário que seu Android esteja rooteado. Caso não esteja, ou você não saiba do que se trata, uma rápida pesquisa no Google resolve.

Segundo: Faça o download do aplicativo "Titanium Backup".
Instalado o aplicativo, execute-o, e dê as permissões de "Super Usuário" ao app.

No aplicativo aberto, obvio, clique na guia "Backup/Restauração" (1) e em seguida, clique em "Clique para editar os filtros" (2).

Na próxima tela, digite no campo de pesquisa "Armazenamento de Configurações" (1). Clique no simbolo de "✓" (2)

Em seguida, clique no único arquivo que ficou disponível na lista (1), e selecione "Backup" (2).

Feito o backup, repita a operação, dessa vez colocando no campo de pesquisa, o aplicativo "Bradesco". (Ao ser solicitado do que deseja fazer backup, selecione "App + Dados").

Agora, quando precisar restaurar a chave de segurança, faça o seguinte:

Abra o Titanium Backup, clique no botão de "menu" no topo do app (1), e selecione "Gerenciar o Android ID" (2).

Na pop-up aberta, selecione "Restaurar o Android ID de um Backup" (1), e selecione o backup feito anteriormente (2).

Feito isso, reinicie seu aparelho, restaure o "backup + dados" do aplicativo do Bradesco, e experimente usar a chave de segurança :)

Best equalizer apps for android

https://www.youtube.com/watch?v=_qC6yTBxCs4&feature=youtube_gdata_player

[GT-I9505] CF-Auto-Root - Chainfire

[GT-I9505] CF-Auto-Root - xda-developers

Chainfire CF-Root
SGS4 GT-I9505 I9505
Root.

I9505 Samsung galaxy s4 I9505 Pre-Rooted Stock ROMs Odin/CWM

[ROMS] WORLD PREMIERE: I9505 Pre-Rooted Stock ROMs Odin/CWM [DEODEXED XXUBMF8 Online] - xda-developers
Firmware / rom I9505 sgs4

Main benefits of using this method are:

- FULLY ROOTED
- No need for Insecure Kernels.
- Complete, Odin flashable Packages.
- Can be used on Non-Rooted devices.
- Binary Flash Counter will NOT increase
- System status will stay NORMAL/OFFICIAL.
- Only 1 file and you have a complete firmware including Root permission.
- Fully working KIES & OTA updates (FYI: root will be lost after software update)

Using LVM In Rescue Mode repair lvm file system

System Recovery Week: Using LVM In Rescue Mode - Fedora Daily Package

System Recovery Week: Using LVM In Rescue Mode

This article is part of System Recovery Week, examining techniques used to perform maintenance or recovery on a Fedora system in special circumstances.

Logical Volume Management (LVM) is a powerful storage system layer which abstracts the logical view of storage from the actual physical layout. It is automatically configured in the default Fedora storage configuration. LVM enables you to grow and shrink volumes, add storage from new devices to existing volumes, and migrate volumes between storage devices, all without taking the system offline. In fact, the system-config-lvm package provides a convenient way to perform all of these operations using a graphical interface.

However, you can't (yet) shrink a filesystem while it is mounted. This isn't a limitation of LVM itself, but of most filesystems, including ext3. To shrink a partition that is always mounted when the system is running -- such as the root filesystem -- it's necessary to boot from another medium, which is where rescue mode comes in (see yesterday's article). It may also be necessary to use rescue mode to recover from some particularly nasty corruption or misconfiguration issues.

To do LVM and filesystem-resizing work within the Fedora rescue mode, boot the rescue mode from disc as usual, but select Skip when the system offers to mount your hard-disk partitions. Unfortunately, this will mean that your volume groups will not be detected or activated, so you will need to do that manually.

The commands normally used for logical volume management such as vgdisplay, pvcreate, and lvreduce are actually symbolic links to a single executable named lvm. These symbolic links are not available in rescue mode, so you must explicitly use the lvm command followed by the operation you wish to perform: if you wish to do a vgscan, for example, enter the command lvm vgscan.

Therefore, to discover and activate all volume groups, you must execute these commands:

sh-3.2# lvm vgscan
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
sh-3.2# lvm vgchange -ay
2 logical volume(s) in volume group "VolGroup00" now active

You can display information about the logical volumes using lvm lvs (or lvm lvdisplay for a more verbose display):

sh-3.2# lvm lvs
LV VG Attr LSize Origin Snap% Move Log Copy%
LogVol00 VolGroup00 -wi-a- 28.66G
LogVol01 VolGroup00 -wi-a- 992.00M

Note that the LV and VG names are not very descriptive -- which is why it's a good idea to override the default names during system installation. In this case, we know the approximate size of the LV containing the root filesystem, so we can determine that it is LogVol00 in VolGroup00.

Armed with this information, you can now check (fsck) the filesystem, shrink the filesystem within that logical volume, and then shrink the LV. Because of the potential for rounding errors, it's best to shrink the filesystem to a size slightly smaller than the new LV size, resize the LV, and then grow the filesystem to fully fill the LV:

sh-3.2# e2fsck -f /dev/VolGroup00/LogVol00
e2fsck 1.40.2 (12-Jul-2007)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking refernce counts
Pass 5: Checking group summary information
/dev/VolGroup00/LogVol00: 122967/7514560 files (0.9% non-contiguous), 1113272/7512064 blocks

sh-3.2# resize2fs /dev/VolGroup00/LogVol00 19G
resize2fs 1.40.2 (12-Jul-2007)
Resizing the filesystem on /dev/VolGroup00/LogVol00 to 4980736 (4k) blocks.
The filesystem on /dev/VolGroup00/LogVol00 is now 4980736 blocks long.

sh-3.2# lvm lvresize VolGroup00/LogVol00 --size 20G
WARNING: Reducing active logical volume to 20.00 GB
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce LogVol00? [y/n]: y
Reducing logical volume LogVol00 to 20.00 GB
Logical volume LogVol00 successfully resized

sh-3.2# resize2fs /dev/VolGroup00/LogVol00
resize2fs 1.40.2 (12-Jul-2007)
Resizing the filesystem on /dev/VolGroup00/LogVol00 to 5242880 (4k) blocks.
The filesystem on /dev/VolGroup00/LogVol00 is now 5242880 blocks long.

Note that the operations following the first resize2fs do not need to be performed in rescue mode -- you can reboot the system at that point and continue after the system has booted normally. Earlier versions of the Fedora rescue mode may not set up the symbolic link /dev/VolumeGroup/LogicalVolume, so you may need to refer to/dev/mapper/VolumeGroup-LogicalVolume (e.g., use /dev/mapper/VolGroup00-LogVol00 in place of /dev/VolGroup00/LogVol00).

[How-To] Recover repair fix LVM Partition On Damaged HDD

[How-To] Recover LVM Partition On Damaged HDD ~ Web Upd8: Ubuntu / Linux blog

[HOW-TO] RECOVER LVM PARTITION ON DAMAGED HDD

The following post was send by WebUpd8 reader rkv and it's a mix of story / how-to recover the LVM partition on a damaged HDD. Read on!

Scenario:

80GB SATA HDD, Bad Sectors, 4 Primary Partitions, boot, root, swap and a 60GB Volume Group can boot into the OS (very slow), LVM not recognized.


Solution:

I connected the hard-disk to another Linux box as a secondary drive, took a while to boot indicating bad HDD. After 20 mins (yeah 20 mins), box booted into single user mode, login as root.

I then ran the following commands:

dmesg

found lots of bad blocks errors.

fdisk -l

took a couple of minutes for the output but showed all the partitions.

vgdisplay

didn't recognize any volume groups.

Now i realized that the HDD is failing, as all the above commands are taking a lot of time, so I thought taking a physical dump using dd will help a lot. I could take the raw dump of the entire /dev/sdb4 (the lvm partition) but i just needed data from the home folder i.e. 45 GB / 60 GB so I decided to try some more.

Nnow i tried to recover the lvm metadata for the volume group ( Thanks Purna! )

lvgchange -ay

After 30 mins, i got no message, but fdisk -l shows a lot of mapper devices. vgdisplay gave me all the logical volumes in the physical volume.

Thanks for good labeling, i can see HOMEVOLUME, USRVOLUME, VARVOLUME, TMPVOLUME so now i know that i need to recover the HOMEVOLUME partition. So quickly I tried to mount the /dev/LVMVOLUME/HOMEVOLUME device but after couple of minutes, I got bad FS type error. I even tried specifying the partition type -- ext3 but with no luck.

I then thought its time for "the best command in linux": dd.

dd /dev/LVMVOLUME/HOMEVOLUME /mnt/homelvm.iso

But it failed, gave some bad block error. Target file was 0 kb!

On further research, i found some switches for dd, to ignore bad blocks and move on:

dd /dev/LVMVOLUME/HOMEVOLUME /mnt/homelvm.iso bs=64k conv=noerror,sync

You might be wondering why i specified block size as 64k, the reason is, if dd encounters a bad block, it will skip, so the block size defines how much to skip, so 64k ensures dd copies as much data as possible but will take lot of time to complete, as opposed to specifying higher block size, which will be fast but recovery wont be that successful.

Anyways so I left it overnight and in the morning i have my 47 GB iso file.

So enthusiastically i tried to mount it:

mount /mnt/homelvm.iso /opt -o loop

But didn't work, gave me unknown file system error.

So then i tired the command:

fsck.ext3 /mnt/homelvm.iso

It started checking the disk for errors, and found lots of them, i had to type yes for all the questions. I should have specified the "assume yes and move on" switch, but didn't want to cancel and take chances so after the file system check completed, i tried to mount the iso image again and VOILA, it returned the prompt quietly (I love Linux when it does this!)

All the files needed were intact, I checked few files, they were okay, there might be some corrupt files, but will find out only when I open them.

Hope this article helps!


Also check out how I fixed the "Couldn't mount because of unsupported optional features (2000200)" error.

Root XT910 Jelly Bean (EASY way) - xda-developers

Root XT910 Jelly Bean (EASY way) - xda-developers

Works on ant Motorola Razr XT910 (xt-910) with android 4.1.2 jelly bean

Here are the steps:

1) Install Sun VirtualBox on your Windows PC. [EDIT: Link ---> https://www.virtualbox.org/wiki/Downloads <--- aint="" alt="" border="0" class="inlineimg" he="" img="" michelbfr="" my="" nbsp="" provided="" src="http://forum.xda-developers.com/images/smilies/wink.gif" style="max-width: 665px; overflow-x: auto; vertical-align: middle;" swell="" title="Wink">]

2) Download the VirtualBox .ova file here:
dl.dropboxusercontent.com/s/bb53ayj5c3nd5ie/Root_Bionic_JB.ova?token_hash=AAGSOYfPuDXTur_e9qlY l2JRERovPyfMwe-2xNzHXg4Lxg&dl=1 [EDIT: Link dead, see below]

3) Import the .ova file into VirtualBox. (Click "File" then "Import Appliance".)

4) Start the imported VM in VirtualBox (Click the big "Start" Button. It has a green arrow icon.)

5) Follow the instructions on the Linux console."
I also apologize for not coding links etc, I am not an advanced forum user. I just really wanted to share this with anyone who may not have come across this as of yet. If any of you need any further assistance I can try to help as I have successfully used this method and I know absolutely nothing about linux. Enjoy!

EDIT: New link uploaded for step #2 http://www.mediafire.com/download.php?84f3hkx11bpl3fc <---- b="" michelbfr="" nbsp="" thanks="">[LINK UPDATED]
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

[HOW TO-ROOT&UNLOCK] OTA&KIES Updates+OFFICIAL Status+MDM/MDN ROOTED [GT-I9505] - xda-developers

[HOW TO-ROOT&UNLOCK] OTA&KIES Updates+OFFICIAL Status+MDM/MDN ROOTED [GT-I9505] - xda-developers

 [HOW TO-ROOT&UNLOCK] OTA&KIES Updates+OFFICIAL Status+MDM/MDN ROOTED [GT-I9505]

---

Hello everyone 

I've found SOLUTION for ALL people who USED or want to USE a Chainfire's CF-AutoRoot for GT-I9505
This method will reset System Status back to OFFICIAL and keep Full Root Access.

Works on ALL Firmwares, including XXUAMDM/MDN..!!! -TESTED  
vjuamdm root


DON'T USE MODIFIED_CF_AUTO_ROOT ON ANY OTHER PHONE AS IT CONTAINS KERNEL!!!

You've been warned!!

I DON'T take any responsibility for HUMAN ERRORS....
Follow the GUIDE and it WILL work, if NOT, it's because YOU are doing something wrong...

[GT-I9505] CF-Auto-Root - xda-developers

[GT-I9505] CF-Auto-Root - xda-developers

Everyone playing with this right now knows the drill, for the rest of you this post will be updated with more information soon. So here's only the short instructions: flash the included .tar.md5 as PDA using Odin, and make sure repartition is not checked. You should see a red Android coming up, and your device will be rooted. If the device boots normally without the red Android, reboot into recovery manually to trigger the process.

This root will trigger the flash counter, which you can reset (currently only the Qualcomm variant) using Triangle Away.

Downloads: 

Qualcomm-based GT-I9505: http://download.chainfire.eu/316/CF-...xx-gti9505.zip
(Should work on MD2 and newer, but not MDN and MDM firmwares)

Tec 4 All: TUTORIAL: CyanogenMod 10.1 no Motorola RAZR / RAZR Maxx

Tec 4 All: TUTORIAL: CyanogenMod 10.1 no Motorola RAZR / RAZR Maxx

Tutorial:

1 - Baixe a ROM mais recente e os GAPPS e coloque os dois no armazenamento interno do RAZR.

2 - Baixe e instale o Bootmenu Manager. Abra, dê permissões de Root e vá em Installer.

3 - Depois de instalado vá em Manager, deslize para a esquerda e ative todas as opções.

3 - Se quiser, faça um backup dos seus aplicativos usando o Titanium Backup ou pelo Bootmenu Manager (Reiniciar -> Recovery -> Backup & Restore -> Full Backup ou Seletive Backup de Data e System)

4 - Reinicie e clique no Android quando ele aparecer, vá em Recovery.

5 - Vá em Firmware Flashing e então Backup CID. 

7 (Opcional) - Volte e vá em Mount & Storage e dê Format System, Data e Cache. Isso NÃO afeta seu SD ou o armazenamento do RAZR.

8 (Opcional) - Agora volte e vá em Wipe e dê Wipe Data/factory Reset e então Wipe Dalvik Cache.

9 - Volte e Install ZIP package e então em Install ZIP from Storage.

10 - Use os botões de volume para navegar e o botão power para confirmar. Selecione o arquivo da ROM, aperte power, confirme. Espere terminar o processo. Demora um pouco mesmo.

11 - Agora faça o mesmo, mas escolha o arquivo dos gapps. Sem isso você não terá as configurações do início nem Google Play Store.

12 - Agora volte e vá em Reboot options e então em reboot.

13 - Espere o celular ligar, pode demorar até 15 minutos. Mais que isso reinicie novamente (power + volume menos) e de Wipe cache e wipe dalvik cache.

14 - Após ligar você poderá configurar o aparelho e restaurar seus aplicativos pelo Titanium Backup =)

ATENÇÃO: Se você quiser pode arriscar instalar sem fazer os passos 6, 7 e 8. Mas recomendo que pelo menos o passo 6 façam! Se não fizerem os passos 7 e 8 o celular provavelmente irá ligar e estará tudo lá os aplicativos, mas provavelmente ficará mais lento que o normal!