Chainfire's RegionLock Away App SIM Unlocked my TMobile Note 3 sm-n900t

*** since people can't seem to be held accountable for screwing up their phones because they can't read... Here's the disclaimer: this is in the Note 3 section (TMO Note 3 section to be exact). It's your own damn fault if this bricks your phone. As with anything else, you assume responsibility for any and all negative results. ***

So here's the skinny. I SIM-unlocked my UNACTIVATED T-Mobile Note 3 via Chainfire's RegionLock Away app.

I bought the Note 3 SM-N900T direct from T-Mobile with the sole purpose of using on AT&T - without thinking about it being SIM-locked to T-Mobile. Of course I found this out when I put the AT&T SIM in out of the box - only to be reminded that it was locked and I needed the network unlock code from T-Mobile.

I also didn't want to activate a SIM on T-Mobile (spending at least $10 for a week-long plan) just to turn around and spend $25 on an unlock code. So after seeing Chainfire talk about fixing the Region Lock on the Note 3 I decided to give the following a test:

1. Put the T-Mobile SIM (unactivated, unregistered) that came in the box into the Note 3
2. Rooted via Chainfire's CF AutoRoot
3. Bought RegionLock Away app
4. Ran the app, and instead of rebooting - I said Reboot Later (I THINK THIS IS VERY IMPORTANT)
5. I then powered off the Note 3.
6. Took out the T-Mobile SIM and replaced it with my AT&T SIM
7. Turned on the device - BOOM! no Region Lock, and NO SIM Lock. I was able to setup my APN without any "wrong network" errors, and it's working like a charm.

Interezante

Cómo navegar por la web de manera anónima sin morir en el intento http://bitelia.com/2013/12/navegar-web-manera-anonima

My World Mobile Feliz navidad

https://www.dropbox.com/s/k2d2dl3lgw1hrvu/P0000126211-J0000151583-1219131446-d41d8.f4v.mp4

SAMSUNG GALAXY NOTE 3 ROOT

Download
SM-N900 (International Exynos): CF-Auto-Root-ha3g-ha3gxx-smn900.zip
SM-N9005 (International Qualcomm): CF-Auto-Root-hlte-hltexx-smn9005.zip

SM-N900T (T-Mobile US): CF-Auto-Root-hltetmo-hltetmo-smn900t.zip
SM-N900P (Sprint): CF-Auto-Root-hltespr-hltespr-smn900p.zip
SM-N900R4 (US Cellular): CF-Auto-Root-hlteusc-hlteusc-smn900r4.zip
SM-N900W8 (Canadia): CF-Auto-Root-hltecan-hlteub-smn900w8.zip

SM-N900S (Korea): CF-Auto-Root-hlteskt-hlteskt-smn900s.zip

SM-N9002 (China): CF-Auto-Root-hlte-h3gduoszn-smn9002.zip
SM-N9006 (China): CF-Auto-Root-hlte-h3gzc-smn9006.zip
SM-N9008 (China): CF-Auto-Root-hlte-h3gzm-smn9008.zip
SM-N9009 (China, untested): CF-Auto-Root-hlte-h3gduosctc-smn9009.zip

Untested versions: please let me know if they work!

Other models

T-Mobile US thread: http://forum.xda-developers.com/show....php?t=2467369
Sprint thread: http://forum.xda-developers.com/show....php?t=2469904

CF-Auto-Root is not yet available for all carrier-specific Note3's. Link me to stock firmwares for these devices as they appear, and I might be able to make a device-specific CF-Auto-Root.

Galaxy S4: How to remove carrier label and replace 4G LTE icons

 Samsung Galaxy S4 (SGH-I337) was able to run on the 4G LTE network, which has data transfer rates up to 10x faster than 3G, so you can do lots of things very fast. If you are on AT&T 4G coverage, the 4G LTE icon will appear in the notification bar, it’s different from international smartphone that only has H+ or LTE icon. Moreover, in the notification bar you can also notice a carrier label that indicates you are using the AT&T SIM card.

Since not everyone is pleased with the number of icons on Notif bar, then there are some people who want to get rid of it. Removing icons and carrier label can’t be done easily due to the fact that there’s no Setting to remove them. But for those who have rooted device, there is still a way to achieve it.

Image: Samsung
Screenshot: XDA

To remove AT&T (or other) Carrier label on on Galaxy S4 and replace the 4G/4G LTE icons with stock icons is a breeze, we just need to change a couple of lines in “build.prop” which is located at /system folder. For those who are interested in applying this mod, you can read the guide below.

1. Since we have to edit a system file (build.prop), root access is required.
2. Get Build Prop Editor from Play Store. You can also utilize a file explorer app that allows read/write system files, such as ES File Explorer.
3. Locate for this line (AT&T model):
   ro.product.device=jflteatt
   ro.product.model=SAMSUNG-SGH-I337
   ro.product.name=jflteuc
4. And change it to:
   ro.product.device=jflte
   ro.product.model=GT-I9505
   ro.product.name=jfltexx
5. Before the changes can be saved, a reboot is necessary.

Do not forget to backup your Galaxy S4 build.prop file before performing any changes, so in case there are some apps that won’t work as soon as you implement this you can restore it.

How to root Samsung Galaxy Note 3 SM-N900A

These are the instructions to root Samsung Galaxy Note 3 SM-N900A (AT&T) using Odin on Windows Computer.
Requirements: Your Samsung Galaxy Note 3 should have at least 60-70 percent battery to perform the rooting process.

Root Samsung Galaxy Note 3 SM-N900A

Step 1: Download and install Samsung Kies on your Windows Computer. In case Samsung Kies is already installed then skip this step.

Step 2: Download (2.20 GB) and extract the Note 3 SM-N900A root files on your computer. After extracting you will be able to see the following files:

Step 3: Remove external MicroSD card from the smartphone if you are using it. In case you are not using any external SD card then skip this step.
Step 4: Now, Switch Off your Smartphone.

Step 5: After switching-off the phone, you need to boot into Download Mode. To boot into download mode Press and hold Volume Down Key, Home Button and Power key at same time for 5-8 seconds until download mode is active.

Step 6: In the Download mode you will be able to see a Warning Yellow Triangle Sign. In this situation you have to press the Volume up key to enter Odin Download mode.

Step 7: Now, Open N900AUCUBMI1_OneClickBin.exe (You have extracted this in Step#2) on your computer. Then connect your phone to the computer.

Step 8: Once you have connected the phone to the computer, Odin will automatically recognize the device and show “Added” message at the lower panel.

Step 9: Now, click on the “Start” button in Odin to begin the Flashing process.

Step 10: Once flashing is completed, your smartphone will restart automatically and you will be able to see “Green” Pass message in Odin. Then Disconnect the phone from the computer.

Step 11: Now, again Power off your Phone.

Step 13: Now, again you have to enter into the download mode. To enter download Mode Press and Hold Volume Down Key, Home Button and Power Button for 5-8 seconds until you boot into recover mode.

Step 14: In the Download mode you will be able to see a Warning Yellow Triangle Sign. In this situation you have to press the Volume up key to enter Odin Download mode.

Step 15: Now, run Odin3.exe (You have extracted this in Step#2) on your computer. Then connect your phone to the computer.

Step 16: Once you have connected the phone to the computer, Odin will automatically recognize the device and show “Added” message at the lower-left panel.

Step 17: Once your device is detected by Odin, click on the “PDA” button and select the Root_de_la_Vega.tar file that you have extracted in Step #2.


Step 18: Now, click on the “Start” button in Odin to begin the Flashing process.

Step 19: Once flashing process is completed your smartphone will restart automatically and you will be able to see Green Pass message in Odin. Then disconnect your Smartphone from the computer.

Step 20: Now Extract Root_de_la_Vega.zip file on your computer. After extracting copy the extracted files to the root of the internal sdcard.


Step 21: Now, again restart your Smartphone (very important step).

Step 22: Once your Phone is restarted, Delete the root files from Phone Memory that you have copied in the Step#20.

Step 23: After deleting the files, again restart the device (very important step).

Step 24: Now your Samsung Galaxy Note 3 SM-N900A is Rooted. To check whether your phone is rooted correctly, open Applications Menu, there you will be able to see a new app installed, called SuperSU. If this app exist then it means you have successfully rooted your device.

Points to remember:
[*] Data loss process: Your Phone Data like contacts, pictures, videos, music and etc will be deleted it you follow the above tutorial. So, make sure to take backup of your important data before following the rooting process.
[*] Warranty Void: Your Samsung Galaxy Note 3 SM-N900A Warranty may be Void after following the above tutorial.
[*] Once rooting process is completed you can insert back your MicroSD card.
[*] If you want to root Samsung Galaxy Note 3 N900 then see root note 3 n900.
[*] Credits: Thanks to “designgears” XDA Developer for providing the root files for Note 3 N900A. Without the root file, the above tutorial was not possible.

**Updated** Restore for MJ5 - Knox 0x0 - picture walkthrough.

---

I got stuck in a bootloop after editing my build.prop, so I flashed MI9 over my MJ5. (Stupid move, it turns out). I ran into the emergency firmware issue when I tried using designgears image ---- when using Odin, the system.img fails and odin never flashes the cache.img (where the sec_csc.zip file typically gets flashed). Result - We get stuck in emergency download mode.

Using Heimdall, you can flash individual partitions, and uploads finish without sending the Note into emergency download mode. And if anyone is curious, no, it will not overwrite firmware files whose binaries have been fused to 2 (no downgrading firmware or installing custom recovery)

BUT -- We are free to use kn0x0ut without fear of softbricking!

**Thanks to:
147aaron - OTA update
Designgears - RDLV
A.S._id - MJ5 Firmware
drakeymcmb - kn0x0ut support / mirror

1) Download and install Heimdall from here for windows. You'll need this for 32-bit windows, or this for 64-bit windows


2) Download the following files;

MI9_fix.img.ext4

Quote:

Originally Posted by drakeymcmb Heres a mirror https://mega.co.nz/#F!icMTnSQY!bMBNFmUnn2_K8olSTYpwIA Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

update.sh

sec_csc.zip

patch.zip

apply_patch

rldv.zip

Put everything except for the system.img on your external SD card

3) Download and install the MJ5 partions. Use Odin to flash these files (match the file names with the different upload slots)

AP_N900AUCUBMJ5.zip

BL_N900AUCUBMJ5.zip

CP_N900AUCUBMJ5.zip

HLTE_USA_ATT_32G.pit

4) Now is the time to use Heimdall.

install the vcredist package downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"

from the dropdown, select MSM8960

click the "install driver" button.

you should see a success message


5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.

Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.

click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.

6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery



7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.

8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you rmember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place

9) After flashing the sec_csc, the Note will reboot.

This will give you stock MI9 with MJ5 firmware. You can choose to stop here if you don't want to root/upgrade to MJ5

10) Extract rldv.zip to the root of your internal sdcard (NOTE **my script knocks out knox). Reboot, then once SuperSu installs, Reboot again.


This leaves you with rooted MI9 on MJ5 firmware. Continue on to update to MJ5.

11) Unzip the patch.zip file from my earlier post to the root of your SD card. You should now have the path "/sdcard/patch/".


12) Move apply_patch to /system/bin using a root explorer or ADB. Make sure the permissions are set right.

13) Move the update.sh to the root of your internal sdcard, fire up ADB and run these commands in your ADB window:


su
mount -o rw,remount /system
sh /sdcard/update.sh
reboot

When you reboot, you're finished! You know have a fully working and rooted MJ5 system! If this helped, please hit thanks or donate

I'm finishing up a custom rom image for us. We'll be able to flash it without the inventive, but dirty, kn0x0ut script

Instalar ICS Final en Atrix 2

Buenas, cómo les va? En este tutorial les voy a enseñar a instalar Ice Cream Sandwich en sus Atrix 2.
Cómo ya sabemos, AT&T y algunas operadoras de India ya han liberado oficialmente esta versión. Y como siempre, Latinoamericanos y demás seguimos esperando.
Pero bueno, no importa, aún así tenemos mejore versiones.

A tener en cuenta:

El Atrix 2 se divide en 2 versiones. MB865 y ME865 por lo cual los hace DISTINTOS. Pero si se puede instalar un firmware de MB865 en un ME865 y viceversa.
Y, cómo saber que versión tengo? Bueno, es fácil. Depende de el lugar de compra. Pero por si las dudas podemos ir a 'Ajustes -> Acerca del teléfono'



Y otra cosa a tener en cuenta es, si tu teléfono es MB865, tenés que saber si es de AT&T o de otra empresa (NO-AT&T).
Esto sólo lo podremos saber por el lugar de compra. Si lo compraron en Claro, Movistar, Personal, u otro lado, va a ser NO-AT&T. Y si tu teléfono, lo compraste en alguna tienda de AT&T o tiene el logo de la empresa debajo de los botones, obviamente, es AT&T.

Requisitos:

- Atrix 2
- RSD Lite 6.0
- Cable USB
- Drivers de Motorola
- BATERIA AL 100%
- Firmware adecuado para el teléfono

Procedimiento:

1: Descargamos el firmware adecuado ->Bajar-<

2: Descargar e instalar RSDLite ->Bajar<- a="">

3: Instalar los drivers de motorola

4: Descomprimir el .zip del firmware. Abrir RSDLite. Apretamos el botón de los 3 puntitos '...' y abrimos el archivo .xml



5: Apagar el teléfono. luego apretar ambas teclas de volumen (arriba y abajo) al mismo tiempo y luego, sin dejar de presionar las teclas, encender el telefono. Se inicia con la pantalla negra y aparecen distintas selecciones, ir a AP Fastboot con la tecla de volumen hacia abajo, una vez sobre AP Fastboot presionar la tecla volumen hacia arriba, entra a otra pantalla negra donde dice:
AP Fastboot Flash Mode (S)

6: Conectar el teléfono y darle 'Start'

El proceso tarda unos minutos. Y NO TOCAR EL TELÉFONO, NI APAGAR LA PC.

7: Una vez terminado, el teléfono se prende. Y la primera vez que lo prendemos, también tarda en arrancar. Así que no se pongan impacientes y esperen.

Motorola Atrix 2 (MB865, ME865) Software

Motorola Atrix 2 (MB865, ME865)

Size	MD5	Carrier	File
519.1 MiB	B492800E160D3BFF22F731DA1F870FD0	Retail Hong Kong / Taiwan	5.5.1-1_GC-109_HKTW_cfc.xml.zip
573.3 MiB	409B0BF2A5E35B4E04E78D36DEB66532	Retail Chinese	5.5.1-1_GC-90_EDISON-11_CHN_cfc.xml.zip
579.3 MiB	9B7D2E720C2E4E1C06BA2276C5C1C669	China Unicom	5.5.1-1_GC-90_EDISON-11_CU_cfc.xml.zip
521.5 MiB	A1885DFCB9C7C23CA4BFDE9460160614	Retail Hong Kong / Taiwan	5.5.1-1_GC-90_EDISON-11_HKTW_cfc.xml.zip
509.3 MiB	8F4300E365D53FF61A42995A71F86B96	Retail Hong Kong / Taiwan	5.5.1-1_GC-90_EDSHKTW-2_cfc.xml.zip
572.7 MiB	FFCD99DEE4247A448E74B099418C747D	Retail Hong Kong / Taiwan	5.5.1-1_GC-90_EDSHKTW-6_cfc.xml.zip
517.4 MiB	E3ADED313D157C252281C1358D7A9C5A	Asia (Operator)	5.5.1-EDEM-27-ASIAOPS_cfc.xml.zip
514.4 MiB	2BE357B133BE393DED0AC06219F87A1A	Retail South Africa / UAE	5.5.1-EDEM-27-MEARET_cfc.xml.zip
517.3 MiB	F452799D01461D307BD4F0593066B4CF	Retail Asian	5.5.1-EDEM-27-SEARET_cfc.xml.zip
519.1 MiB	66DAC29B986310CD5C8B718FA5123C16	Asia (Operator)	5.5.1-EDEM-28-37-ASIAOPS_cfc.xml.zip
516.2 MiB	B21E0B852624FE3BB151049E2A540C55	Retail South Africa / UAE	5.5.1-EDEM-28-37-MEARET_cfc.xml.zip
519.2 MiB	63EF21A6DF3869329AB6B0A54CD74F8F	Retail Asian	5.5.1-EDEM-28-37-SEARET_cfc.xml.zip
518.5 MiB	9A3EC3BB5E48338C68551C8CAA1C9CA3	Telecom New Zealand	5.5.1-EDEM-28-TNZ_cfc.xml.zip
493.7 MiB	7D39A39218B393BF876812AE69EE3D6A	Unknown Carrier	5.5.1-EDL-27-RETAIL_LATAM_cfc.xml.zip
551.7 MiB	2ED3D5067EB94D7E1C8F23DE66DE4421	Unknown Carrier	5.5.1-EDL-32-CLARO-LATAM_cfc.xml.zip
558.5 MiB	8B18008306F830A58EBFAD49183C35EA	Iusacell Mexico	5.5.1-EDL-32-IUSACELL-MX_cfc.xml.zip
557.7 MiB	997D7E5BEB0648D1AC28C1013E70DD2E	Unefon Mexico	5.5.1-EDL-32-UNEFON-MX_cfc.xml.zip
560.7 MiB	2FA7DF38F04A70F69E26B6FC656941C8	Unknown Carrier	5.5.1-EDL-34-MOVISTAR-AM_cfc.xml.zip
560.7 MiB	E3F7275EF1BE783DCDFA699BABE4AFFF	Unknown Carrier	5.5.1-EDL-34.1-MOVISTAR_AM_cfc.xml.zip
320.8 MiB	43D340E9F4087754BB54B9F2718E843E	Asia (Operator)	6.7.2_EDEM-18-ASIAOPS_cfc.xml.zip
324.5 MiB	DDB63EE7C0AE6497AE272C81A20EE985	Retail South Africa / UAE	6.7.2_EDEM-18-MEARET_cfc.xml.zip
320.8 MiB	EAEE7B95377EE5C5E00C7F3E713C2F54	Retail Asian	6.7.2_EDEM-18-SEARET_cfc.xml.zip
334.7 MiB	2BF9CCD528C05D26523ACC5B38AC76C6	ATT US	InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
477.0 MiB	293E0F7E89DC9FA54F612C1A83FE69D8	ATT US	InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
470.9 MiB	FCC0FBFDEDEAE084F90E34BF2523EB27	ATT US	InlineFlashing_edison_5.5.175.25_cfc_p3_APBP.xml.zip
324.9 MiB	6C3F61AD918F9B8B7FCFED9796E2C60F	Retail Chinese	fastboot-p3_edison-edison-user-4.0.4-6.7.2_GC-180-EDS-20-31-release-keys-ChinaRetail-CN_chn.tar.gz
313.0 MiB	F9031AE87C9886BED871BDDB3B3ACD89	Retail Hong Kong / Taiwan	fastboot-p3_edison-edison-user-4.0.4-6.7.2_GC-220-EDS-3-65-release-keys-Retail-05_hktwn.tar.gz
589.0 MiB	0D8C4E3149C8AD785164029F0B356315	Retail Chinese	fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar.gz
595.0 MiB	517A332CFD7B1BF34C65DBD4BFB969D1	Retail Chinese	fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaUnicom-CN_cu.tar.gz

SGH-T599 FIRMWARE

Hi SGH-T599 users!
I don't have this device myself, but a S3mini which is pretty much the same device.
Since no official firmwares is to be found yet, and @Unjustified Dev made CM10.1 and CWM I thought it would be good to make something for odin as an option to get back to stock.
These are reworked images taken from devices with dd-method.
Each tar contains boot.img, cache.img, system.img and recovery.img.
Boot and recovery repacked to be accual size. System and cache totaly repacked to sparse ext4-img files.
I also added supersu, su binary and busybox so these are pre-rooted
If you for some reason want to unroot, go to supersu settings and tick full unroot.

T599-Pre-rooted.zip - 600.17 MB
T599N-Pre-rooted.zip - 572.45 MB
T599V-Pre-rooted.zip - 579.90 MB

Included is also a zipped "modem.bin" If you messed up your modem you can get it flashed to device with Terminal Emulator.
Put "modem.bin" on your sdcard. In TM, type:

Code:

su
dd if=/sdcard/modem.bin of= dev/block/mmcblk0p16

"one-click-root" (works on s3mini so I think it works here as well)
Enable USB debug. VRoot_1.6.0.3689_english.zip
Otherwise cydiaimpactor is known to work.

Links to related threads which together made everything possible:
[ROM] [4.3.1] [OFFICIAL][Nightlies][Codinaxx Galaxy Exhibit T599X Variants]PAC-Man
[ROM][4.2.2.][UNOFFICIAL] CyanogenMod 10.1 for Galaxy Exhibits
[Recovery][CWM] SGH-T599- Working
[System, Boot & Recovery Dump][8-27-13] SGH-T599 (4.1.2) JZO54K.T599UVAMB5

IF COMING FROM CM10.1, FIRST GO TO RECOVERY AND MAKE A FACTORY RESET
HOW TO FLASH:
Download Odin 3.04 and install samsung drivers.
Unzip downloaded firmware.
Open Odin, put phone in download mode (vol-/home/power).
Connect phone to computer, and place the *tar.md5 in PDA-box.
Make sure F-reset time and auto reboot is ticked. Press START.

blackberry 9380 initialisation failed done

blackberry 9380 initialisation failed done

 

9790 sim initialization failed.

9790 sim initialization failed.

 

try this solution...
if vcc/vsim in sim conector not come

 

 

TUTORIALES DE FLASHEO "LG - E960 NEXUS 4 GOOGLE" A SU ESTADO DE FÁBRICA/ACTUALIZAR MANUALMENTE

TUTORIALES DE FLASHEO

Pues bien, una vez tengamos los drivers correctamente instalados, hayamos conseguido el acceso Root, instalado un recovery alternativo... Habrá gente a la que esto se le quede corto, que tenga ganas de trastear todavía más, flasheando ROMs cocinadas, kernels alternativos... Pues para ellos y para todos aquellos que quieran dejar su Nexus 4 como recién salido de la caja, este post contendrá todos los tutoriales de flasheo para cada cosa en este orden:

• Devolver Nexus 4 a su estado de fábrica
• Flashear una ROM alternativa
• Flashear un kernel alternativo

Antes que nada, decir que es recomendable tener el terminal con un buen nivel de carga de batería (entre el 75 y el 100%), asi como una copia de fotos y videos, por cualquier cosa que pudiera pasar.
Empezamos!

DEVOLVER NEXUS 4 A SU ESTADO DE FÁBRICA/ACTUALIZAR MANUALMENTE

Este procedimiento se recomienda cuando:

• Hayamos trasteado bastante y no nos guste el resultado
• Queramos volver por cualquier motivo al estado original del Nexus 4
• No nos responda y creamos que puede ser debido a una mala actualizacion
• Queramos actualizar manualmente a una nueva versión de Google
• Queramos descartar problemas de software antes de enviar al SAT (realizar este procedimiento es totalmente legal y no invalida garantía)

Para hacerlo, da igual que versión tengamos, si tenemos una ROM cocinada instalada o lo que sea...
Tendremos que tener descargada la imagen de la versión que queramos flashear en nuestro Nexus 4.
El listado de imagenes oficiales se encuentra disponible aquí:

Nexus 4: https://developers.google.com/androi...s/images#occam
PD: Ya que Google ha eliminado por motivos desconocidos el enlace a la imagen de JOP40D, aquí os dejo un mirror: http://d-h.st/Wx1
Es la original, podeis estar tranquilos

Para este tutorial, pondremos como ejemplo, la ultima version JDQ39

ATENCIÓN: ESTE PROCESO ELIMINARÁ TUS APLICACIONES INSTALADAS Y TUS CUENTAS, PERO NO PERDERÁS NI TUS FOTOS NI VIDEOS (AUNQUE SE RECOMIENDA HACER UNA COPIA SI ES POSIBLE, POR CUALQUIER FALLO QUE PUDIERA SUCEDER). TAMBIÉN PERDERÁS EL ACCESO ROOT Y CUALQUIER RECOVERY MODIFICADO QUE TUVIERAS

• Seleccionaremos el enlace y descargaremos el archivo a una carpeta que recordemos (por ejemplo, la misma de antes, C:\N4)
• Una vez descargado, lo abriremos y extraeremos el contenido a una carpeta (por ejemplo, C:\N4\ACTUALIZACION) y observaremos varios archivos:
  • Un archivo .img. Es el BootLoader
  • Un archivo .zip. Es la imagen de fábrica
  • Otro archivo llamado radio-XXXXXXX.img
  • Otros dos/tres archivos con el nombre flash-all y flash-base que no utilizaremos
    
    
• Pondremos el Nexus 4 en modo FastBoot y lo conectaremos por USB
• En la carpeta donde se encuentra el contenido extraído, pulsaremos Shift + Botón derecho en un espacio vacío de la carpeta y pulsaremos "Abrir ventana de comandos aquí"
• Es recomendado hacer una limpieza de archivos anteriores (CON ESTOS COMANDOS DE ESTE PASO NO PERDEREIS FOTOS NI VIDEOS, PERO SI APLICACIONES). Escribiremos la siguiente serie de comandos (pulsando Intro al final de cada uno)
  
  Código:

  fastboot erase cache
  fastboot erase recovery
  fastboot erase system

  Y ya tendremos el sistema limpio para empezar el flasheo
• Para empezar a flashear, el primer paso será actualizar el BootLoader. Para ello escribiremos:
  
  Código:

  fastboot flash bootloader X.img

  Donde X es el nombre del archivo .img (el bootloader)
  NOTA: Si os aparecen mensajes de que no contiene boot.sig, recovery.sig o system.sig, no les hagais ni caso
• Reiniciaremos el teléfono en modo fastboot directamente con el siguiente comando:
  
  Código:

  fastboot reboot-bootloader

• Flashearemos también la banda base con el siguiente comando:
  
  Código:

  fastboot flash radio T.img

  Donde T es el nombre del archivo de la RADIO/BANDA BASE
• Reiniciaremos de nuevo el bootloader con el siguiente comando:
  
  Código:

  fastboot reboot-bootloader

  Como podeis apreciar en el video, si no lo haceis puede dar error en el flasheo
• El siguiente paso será flashear la imagen. Para ello escribiremos el siguiente comando:
  
  Código:

  fastboot update Y.zip

  Donde Y será el nombre del archivo .zip
  
  NOTA: Si alguien quisiera hacer una instalacion TOTALMENTE limpia de la Nexus 4, puede hacerlo con el comando
  
  Código:

  fastboot -w update Y.zip

  El cual borrará todas las aplicaciones, fotos, videos, descargas... Que haya en el teléfono. Estará totalmente como recién salido de la caja
• Y si no se nos reinicia solo, reiniciaremos el terminal con el comando
  
  Código:

  fastboot reboot

AVISO: Tened en cuenta que el primer inicio puede tardar mas de lo habitual

Y con esto habremos conseguido dejar nuestro Nexus 4 TOTALMENTE de fábrica, es decir, con la ROM Stock, sin acceso root ni recovery modificado, ni nada de nada