[HOW-TO] How to flash a factory image / return to stock / unlock / root #

Search This thread

simorangkir_dcs

Senior Member
Oct 9, 2012
448
140
Jakarta
Vivo X60 Pro
after i update to 4.3 my device only shows 8GB, I tried to enter recovery but ended up with died android image with red exclamation mark.

anyone can help me?

Edit1: nevermind, I got it right
 
Last edited:

Ivan Fuentes Hagar

Senior Member
Jan 5, 2012
245
60
Los Angeles
You can still boot a recovery without flashing it, but you have to specify the kernel command line

Solution 1 (works on my N4, not sure it will work for all hardware revisions) :
  1. fastboot boot customrecovery.img
  2. you see a blank screen
  3. get the default fastboot kernel command line : adb shell cat /proc/cmdline
  4. adb reboot-bootloader
  5. Append lge.kcal=0|0|0|x to the default fastboot kernel command line :
    fastboot -c "your_default_command_line lge.kcal=0|0|0|x" boot customrecovery.img

worked flawlessly, thanks!
 

hughfollett

Senior Member
Sep 17, 2011
1,732
912
Guys I followed this guide as it was the first time flashing stock roms with this, but I used the flash-all.bat and I had no problems with memory..

Inviato dal mio Nexus⁴ |
Rom: 4.3 stock | Kernel: stock
 

chrone

Senior Member
May 5, 2012
1,050
369
Surabaya
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU or Koush's Superuser; NOTE: None of them currently work properly with JRQ66V (i.e., 4.3). Standby.

i managed to gain root by using this following article from Chainfire here. my friends are also successful getting root in maguro gsm device. :)

the trick is we have to choose "NO" when prompted to disable flash recovery after flashing the custom supersu made by Chainfire himself as posted in CWM 6.0.3.3/4 recovery.

EDIT: CWM users, you need to uncheck the option to "disable stock recovery flash", if it shows up.
 
Last edited:

spicediablo

Senior Member
Oct 26, 2011
1,663
239
Malaysia
OnePlus 11
How's the performance? some users reported it isn't working properly and experienced high CPU load and battery drain.

i managed to gain root by using this following article from Chainfire here. my friends are also successful getting root in maguro gsm device. :)

the trick is we have to choose "NO" when prompted to disable flash recovery after flashing the custom supersu made by Chainfire himself as posted in CWM 6.0.3.3/4 recovery.
 

VoiD_Dweller

Senior Member
Aug 5, 2011
944
897
Orlando, FL
Moto G Power (2021)
i managed to gain root by using this following article from Chainfire here. my friends are also successful getting root in maguro gsm device. :)

the trick is we have to choose "NO" when prompted to disable flash recovery after flashing the custom supersu made by Chainfire himself as posted in CWM 6.0.3.3/4 recovery.

I read that this method causes massive battery leaks with some daemonsu or something?
 

chrone

Senior Member
May 5, 2012
1,050
369
Surabaya
How's the performance? some users reported it isn't working properly and experienced high CPU load and battery drain.

I read that this method causes massive battery leaks with some daemonsu or something?

I got 3% drain per hour when on WiFi with auto sync, 3rd party app push notification, and location reporting enabled.

While on 3G same setup and a bit of active usage, I got around 10% drain per hour.

All was reported by better battery stats app though.

The supersu app was set with no toast notification for already permission granted app, and also without any logging.


In summary I might say it is the same as it was on 4.2.2. Hehe

Sent from my Nexus 4 using Tapatalk 4 Beta
 
  • Like
Reactions: spicediablo

spicediablo

Senior Member
Oct 26, 2011
1,663
239
Malaysia
OnePlus 11
This is tempting me to flash mine!!:D. I really need root to work as I use TB to restore my apps+data



I got 3% drain per hour when on WiFi with auto sync, 3rd party app push notification, and location reporting enabled.

While on 3G same setup and a bit of active usage, I got around 10% drain per hour.

All was reported by better battery stats app though.

The supersu app was set with no toast notification for already permission granted app, and also without any logging.


In summary I might say it is the same as it was on 4.2.2. Hehe

Sent from my Nexus 4 using Tapatalk 4 Beta
 
  • Like
Reactions: chrone

Federico_96

Senior Member
Jun 29, 2013
185
26
In the first part of the guide efrant says to don't install pdanet drivers if you're not sure that they're working, how can i know if they are working? i unlocked my bootloader and flashed manually twrp, so i guess drivers are working?
 

chiweed

Senior Member
Feb 20, 2012
129
46
Chicago
While most apps behave like root is working properly.. TB in particular does not appear to be working whatsoever. Any attempt to restore an app / data is failing for me (it just never finishes).

mils

Having similar issue but when attempting a backup I get insufficient free storage space using TB.

Sent from my Nexus 4 using Tapatalk 2
 
  • Like
Reactions: chrone

Top Liked Posts

  • There are no posts matching your filters.
  • 590
    I have created this thread to give a step-by-step on how to flash a stock ROM build available on Google's developer site. (For those that are unaware, an unlocked bootloader is needed, and unlocking is part of the instructions below.)

    I've also added a section on how to root for those that want it.

    Note: There are other methods that are abbreviated and/or faster, but I wanted to spell out each step in the process for the purposes of learning. I'm a big believer in doing things manually before using a "toolkit", much the same way that, in school, we are taught to do math first, before being allowed to use a calculator. See here for some further explanation.

    So, without further ado:

    How to flash a stock ROM

    Step-by-step

    Notes:
    1) For the n00bs: read the entire post before proceeding;
    2) MacOS-specific instructions: a) no drivers needed, and b) replace fastboot in the steps below with ./fastboot-mac

    A. Install the drivers
    1) Do not install LG drivers or the PDAnet drivers, or any other driver you come across. If you have, and you are SURE they are working properly, fine, leave them. Otherwise uninstall them if you are unsure;
    2) Download the drivers from here or from here;
    3) Install the drivers. See here on how to install them. Note that the driver has to install twice: once when your device is booted normally (not required for this tutorial) with USB Debugging enabled in Settings, and once when your device is booted in fastboot (i.e., bootloader) mode (which is required for this tutorial). (To enable USB Debugging, you first need to enable Developer options by going to Settings->About phone and tapping 7 times on the build number.) If you are using Windows 8, you will need to do this before installing the drivers.

    B. Backup your data
    1) Backup all your personal data (e.g., photos, music, etc.) OFF of your device and onto your computer by using whatever method you want that works for you, e.g., MTP, ADB, email, Dropbox, Box.net, whatever.
    2) This method will wipe your entire device, including the /sdcard folder, so once you do this, you will not be able to retreive anything that was on your device previously.
    3) See here on how to backup your apps and app data if you don't have root.

    C. Download the required files to your computer and extract them
    1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
    2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
    3) Download the version of Android you want from here. Make sure you are using an occam image which is for the Nexus 4. Most old versions are not usually available on that site; however, there is a mirror on this site: Random Phantasmagoria.
    4) Download the appropriate version (for your computer) of 7-zip from here and install it.
    5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
    6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
    7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
    8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.

    D. Type in the commands into the command prompt
    1) Make sure your computer recognizes your device by typing: fastboot devices
    2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
    3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
    4) Reboot by typing: fastboot reboot-bootloader
    5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
    6) Reboot: fastboot reboot-bootloader
    7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
    8) Reboot: fastboot reboot-bootloader
    9) Flash the system partition: fastboot flash system system.img
    10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
    11) Flash the kernel/ramdisk: fastboot flash boot boot.img
    12) Flash the recovery partition: fastboot flash recovery recovery.img
    13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
    14) Reboot: fastboot reboot
    15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.

    Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.

    Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).

    If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (which will obviously delete all your data & files in /sdcard...). Or do this.

    E. Optional -- Root
    If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.

    1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
    2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
    3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU or Koush's Superuser; NOTE: So far, only SuperSU v1.43 and newer currently work properly with JWR66V (i.e., 4.3). I've attached v1.51 below.
    4) Restart your device in fastboot mode and plug into computer;
    5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: Only if you are running the z20i bootloader: the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
    6) Wait for it to boot;
    7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
    8) Reboot. Done.

    Notes:
    1) Yes, you will receive the OTA update notification (when it is available) for the next update. WHEN you get the update notification, IF you want it to install automatically, you will need to ensure that that you are using the bootloader, radio, boot, radio and recovery images for the .tgz package you downloaded. Otherwise, the update will not install automatically.
    2) There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
    3) Do NOT re-lock your bootloader after you are finished. The is no need. 2) Having an unlocked bootloader does not affect anything related to the ROM/GoogleWallet/OTAs. Nothing at all. If your bootloader is locked, you CANNOT use fastboot commands. This is pretty much the only thing it affects. If your bootloader is locked, and you need to unlock it, it will wipe everything, including /sdcard. This is the major drawback of re-locking your bootloader. If you do want to lock your bootloader, the command is: fastboot oem lock
    85
    How to return to stock if your USB port is broken

    I am adding this how-to in case people need it, for return their device to Google, etc.

    This is NOT meant to replace going through the steps in post #1. They are there for your learning, and should be used as a primary method of returning your device to stock. However, if your USB port is indeed messed up, then you will not be able to use the instructions in post #1.

    Warning: if your USB port is indeed broken, and you complete all the steps below, you will have NO possible way at all to unlock your bootloader, or get root, or install a custom recovery. Period.

    1) Ensure that you have root, and a custom recovery (CWM or TWRP) installed;
    2) Download segv11's BootUnlocker app from the Play Store, install it and lock your bootloader with it;
    3) Download the odexed version of this file (stock JDQ39 ROM) and place it on your device;
    4) Download the JDQ39 stock boot image from here and the stock JDQ39 recovery from here.
    5) If you want, you can also download the 0.48 radio and the z10o bootloader from here.
    6) Reboot into CWM and flash the three files you downloaded in steps 3 and 4, and the file(s) you downloaded in step 5;
    5) Turn off your device and reboot into the bootloader;
    6) Go to recovery and access the stock recovery menu (i.e., when you see the android with the red triangle, hold power and press vol up) and do a factory reset and then wipe cache.
    7) Reboot your device. Do NOT install any OTA updates if they present themselves. Read and follow this post.
    8) Done. Now you are fully stock JDQ39 with a locked bootloader.
    20
    10
    No errors, I checked the MD5 of the factory image and it's fine. I even re-downloaded it. I did every step as listed in your procedure (even the optional ones). The phone is dead now, it's charging. It spent over 20 minutes on the X. Everything seems to work per your instructions. I don't get it. Could something be corrupted on my phone itself? System/Boot/Recovery images are all dated Jan 1/09, but I assume that's correct (it's from Google after all). Should I try directly flashing CWM recovery instead of stock during the initial process? I dunno...

    I will try your method from the beginning again tomorrow.

    I assume I'm not bricked if I can still do this stuff. It doesn't bode well if you don't know what's wrong either. I appreciate any further help/suggestions...

    It happened to me the same thing... I did everything right just as suggested in every step, but my phone won't get past the X logo... I solved it by going to the stock recovery (unhide the menu by pressing POWER+VOL. UP), wipe data/factory reset, wipe cache partition. Reboot (to me it rebooted automatically after wiping the cache partition) and everything went fine, it took very few time to get past the X logo...

    Hope it works for you too.
    8
    It's the bootloader.

    It happens since the 4.3 leak and the z20i bootloader.

    You can try flashing the old z10o bootloader (it boots 4.3 just fine) and then fastboot boot command will work.

    It's very annoying because I use to keep the stock recovery and only use CWM or TWRP to root. Now I have to flash a custom recovery, do my thing and reflash the stock one again.

    Cheers!

    You can still boot a recovery without flashing it, but you have to specify the kernel command line

    Solution 1 (works on my N4, not sure it will work for all hardware revisions) :
    1. fastboot boot customrecovery.img
    2. you see a blank screen
    3. get the default fastboot kernel command line : adb shell cat /proc/cmdline
    4. adb reboot-bootloader
    5. Append lge.kcal=0|0|0|x to the default fastboot kernel command line :
      fastboot -c "your_default_command_line lge.kcal=0|0|0|x" boot customrecovery.img

    Solution 2:
    1. fastboot flash recovery customrecovery.img
    2. launch the recovery from the bootloader
    3. wait until it's loaded
    4. get the bootloader kernel command line : adb shell cat /proc/cmdline
    5. adb reboot-bootloader
    6. fastboot flash recovery stockrecovery.img
    7. Use the bootloader command line to launch the recovery from fastboot :
      fastboot -c "your_bootloader_command_line" boot customrecovery.img