{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: If you screw up your tablet doing this, it will not be covered under warranty. Hardware defects should still be covered. If you have found anything helpful, please click "thanks" on my post, and visit the original threads of our amazing developers and leave thanks there too! Before you go on, please BACKUP ALL IMPORTANT FILES YOU DO NOT WANT TO LOSE TO A SAFE LOCATION.
If you have rooted other android devices before, rooting your Archos G9 may be a little difference. Instead of rooting stock firmware, We first install SDE (special developer edition) firmware using official ARCHOS firmware. Once SDE menu is installed it adds an option in recovery to install developer firmware. This is when we install a modified firmware that has busybox and super user included. This guide is very safe to follow. Chances are most problems you run into are very easy to recovery. Please view the FAQ at the bottom of this post if you have questions or run into problems. Because we don't have to flash recoveries or mess with the bootloader like some Android devices require, and because all methods are universal to G9s, this rooting process is very safe and easy to follow. This guide is very easy: No need to install any drivers, root methods, anything! Not even ADB is required. So easy, your grandma could do it...? Quote from ARCHOS:
ARCHOS said:
Important notices to be acknowledged before downloading and installing the SDE firmware:
Once the SDE firmware is installed on a device, this device will be watermarked and ARCHOS will be able to detect that this firmware has been installed once.
After SDE firmware installation, you will not be able to play DRM protected content anymore.
Installing the SDE firmware is considered by ARCHOS as a voiding of the warranty and ARCHOS declines all liability and responsibility for any issues resulting from the installation of this SDE firmware.
ARCHOS strongly advises that only experts in embedded software development should install this firmware.
This firmware is provided "as is" and is not supported by ARCHOS.
The firmware must be installed on a unit with a firmware version above 4.0.1 (Ice Cream Sandwich). Once the SDE firmware is installed, powering on the device while pressing the 'volume down' button will now trigger a "Boot Menu". This menu allows to select which operating system is to be launched (Android, the newly installed Developer Edition or the Recovery System). If the device is powered on while pressing jointly the 'volume down' and the 'volume up' buttons, the Developer Edition will be launched. If the device is powered on without any other button pressed, Android will be launched.
Installing a new ARCHOS (Android) firmware WILL NOT remove the SDE firmware. In order to uninstall the SDE, boot into the recovery using the Boot Menu, select "Developer Edition Menu", then "Uninstall Developer Edition".
Click to expand...
Click to collapse
STEP 1: Install SDE
Prerequisites: You must own an Archos 80/101G9 and be on fimrware 4.0.1 (ICS) or higher.
Step 1: Download SDE firmware HERE
Step 2: Boot into recovery by holding the volume rocker up and pressing the power button simultaneously
Step 3: Select "Update Firmware"
Step 4: Plug your device into your computer using the USB cable that came with your device
Step 6: A new drive should appear in "My Computer", copy the file you downloaded "firmware_archos_it4.aos" to this device
Step 7: Press the power button and wait for the instalation to finish
STEP 2: Install rooted firmware.
Before you begin, you will need SDE installed. Please follow step 1 before you begin if you have not already. If you have SDE installed, you can continue. Any downloaded applications and personal media should remain untouched. Installing a new ARCHOS (Android) firmware WILL NOT remove the SDE firmware. In order to uninstall the SDE, boot into the recovery using the Boot Menu, select "Developer Edition Menu", then "Uninstall Developer Edition". Please download files to your PC hard drive.
Please visit the following thread by surdu_petru and download and extract:
- Stock_Root_4.0.25.zip - 206.48 MB
http://forum.xda-developers.com/showthread.php?t=1955910
Step 1: Power your device on
Step 2: Once your device is on, and your home screen is visible, plug your device into your PC. If you do not have ADB installed on your computer, skip steps 3-6 and follow step 6a.
Step 3: Open a command prompt on your PC and type
Code:
adb devices
Step 4: Ensure your device shows up so you know it's connected properly and adb is active
Step 5: Type
Code:
cd desktop
This is to change the directory to where you download the two files
Step 6: Type
Code:
adb push archos.ext4.update /mnt/storage
Give it some time to transfer, it is a large file and will take several minutes, you will be presented with transfer info once the transfer is complete.
Step 6a: If you followed steps 3-6, no need to follow this step. If you do not have ADB, you can simply copy archos.ext4.update to the root of your Archos storage (the main folder when you connect your Archos).
Step 7: Power off your device
Step 8: Boot into recovery by holding the volume rocker down and pressing the power button simultaneously
Step 9: If you see "Archos Boot Menu" or something similar, select "Recovery System"
Step 9: You should now see "Archos Recovery" with the following options "No" "Reboot" "Update Firmware" "Repair System" "Format System" "Developer Edition Menu". Select "Developer Edition Menu"
Step 10: Select "Remove Android Kernel" (if the option is present, if not, skip)
Step 11: Select Flash Kernel and Initramfs
Step 12: Copy zImage and initramfs.cpio.lzo to the drive that appears
Step 13: Reboot your device. Your device should now be rooted.
Frequently Asked Questions! (FAQ)
Will this guide work for my Archos 80 G9? For my 101 G9? I have Archos 101 G9 OMAP 4430. I have 250GB hdd model! I have turbo edition!
Yes this guide will work for ALL Archos G9 users. This includes 80 G9s and 101 G9s. This includes all 8gb G9s and 16gb G9s and 250GB G9s and 1.0 GHz G9s and 1.2 GHz G9s and 1.5 GHz G9s and OMAP 4430 G9s and OMAP 4460 G9s and board version V5 etc etc. ALL G9s!
Can I just drag the .zip file to the RAMDISK that appears when I flash zImage and initramfs?
No! Archos recovery cannot read ZIP files. You must first EXTRACT, then copy the contents of the extracted folder. NOT the folder itself. This means you will have two files on the RAMDISK, and no additional folders. If you don't know what a RAMDISK is, try Google or Wikipedia. If you get stuck in a boot loop because you forgot to extract archos.update.ext4 or drive.zip, you must follow the instructions below.
Help! I am stuck in a bootloop! Archos splash screen appears and keeps rebooting. I messed up when I was rooting, and now android will not boot! I accidentally formatted my device, and now I cannot boot into android.
This is a simple mistake and in 99% of cases it is easy to fix. Follow these steps:
Step 1: Download official Archos G9 firmware for ALL G9 tablets (aos file) HERE
Step 2: Boot into recovery turning your device off and then holding volume down + power at the same time
Step 3: Choose "Update Firmware"
Step 4: Connect USB cable to computer and tablet
Step 5: A removable device should appear (RAMDISK), copy the file you just download straight to that drive
Step 6: Press the power button once the file is done copying. DO NOT UNPLUG your device until it has finished updating and has booted back into android.
If you did not format your tablet or delete any personal media, your files should be unaffected.
Will I lose SDE menu if I update my tablet with official AOS or OTA update
As of the latest update, no official update from Archos has removed SDE menu. You should be fine, and your SDE menu should remain untouched.
This method may void your warranty if you screw up something software related. Your device will be marked and Archos can detect if you have this installed. If you wish to follow a slightly more difficult (possible dangerous) method, which will not mark your device, you can follow it here (note you will need ADB installed): http://forum.xda-developers.com/showthread.php?t=1542058
Ok thanks i wait the root, the multiboot....
ty
ty so much finnely rooted with rom
For the buzz in FRANCE
http://www.jbmm.fr/?p=27900
Why
Step 10: Select "Remove Android Kernel" (if the option is present, if not, skip) ?
cajl said:
Why
Step 10: Select "Remove Android Kernel" (if the option is present, if not, skip) ?
Click to expand...
Click to collapse
Hi!
It's OK !
..once you removed Android Kernel -> the second time does not appear....so the option is not present !
cajl said:
Why
Step 10: Select "Remove Android Kernel" (if the option is present, if not, skip) ?
Click to expand...
Click to collapse
Android kernel is "official" one and bootloader uses it by default (reboot= stock firmware is loaded)
Recovery checks:
-if stock kernel is present- option Remove Android Kernel is visible in SDE menu
-if SDE kernel is present- option Uninstall SDE is visible in SDE menu
No kernel=no option to remove it
I have installed SDE using your previous guide (I haven't rooted it yet, since I'm still sceptical). Is it safe to remove it and install the official one? I remember one post on the other thread, which said that you can't add it again if you uninstall it. Here it is.
Also, can you unroot by just flashing the official firmware?
tgkokk said:
I have installed SDE using your previous guide (I haven't rooted it yet, since I'm still sceptical). Is it safe to remove it and install the official one? I remember one post on the other thread, which said that you can't add it again if you uninstall it. Here it is.
Also, can you unroot by just flashing the official firmware?
Click to expand...
Click to collapse
not sure where he got that from. you can always add it again if you've uninstalled it...official or nonofficial
Yes its always safe to remove the SDE menu, sde firmware etc. If you run into troubles, simply reflash official firmware. It's worked for everyone else. If you have SDE, then getting sde firmware is simple and safe. I'm not sure what you're sceptical about or what you mean "you haven't rooted it yet". you mean you have SDE menu, just no SDE firmware? if so, simply place archos.ext4.update on the root of your internal storage, then boot into recovery and flash zimage and initramfs
I have since stated why re-installing SDE was not working.
http://forum.xda-developers.com/showthread.php?t=1648538
One can always get SDE back after uninstalling.
Even easier, now that the official SDE .aos has been released.
zando2712 said:
I have since stated why re-installing SDE was not working.
http://forum.xda-developers.com/showthread.php?t=1648538
One can always get SDE back after uninstalling.
Even easier, now that the official SDE .aos has been released.
Click to expand...
Click to collapse
yes. very easy, very safe. just dont blame us or archos if you screw up your tablet
Shano56 said:
yes. very easy, very safe. just dont blame us or archos if you screw up your tablet
Click to expand...
Click to collapse
Did you actually read what I said?
Never blamed anyone... was merely asking for assistance in getting root back.
Also was trying to clarify whether it was even possible because I tried so many times.
Followed your tutorial many times but it was just not re-enabling SDE.
Do not get me wrong... your tut is well written, I was just missing that part of plugging tab to USB 'after' it was turned on.
Like I said, with the official .aos there will be no recurrence, by me, or anyone else.
No need to be on the offensive
zando2712 said:
Did you actually read what I said?
Never blamed anyone... was merely asking for assistance in getting root back.
Also was trying to clarify whether it was even possible because I tried so many times.
Followed your tutorial many times but it was just not re-enabling SDE.
Do not get me wrong... your tut is well written, I was just missing that part of plugging tab to USB 'after' it was turned on.
Like I said, with the official .aos there will be no recurrence, by me, or anyone else.
No need to be on the offensive
Click to expand...
Click to collapse
I apologize! that part "dont blame us or archos if you screw up your device" was directed at everyone not you. I did not mean to direct that towards you, you just misinterprated what I was trying to say. I was agreeing with you. sorry for my miswording
I tried rooting my Archos 101 G9.
I followed the instructions on the OP, but the new kernel didn't boot properly. It just showed a black screen. If I don't remove the official kernel, nothing happens. I have to roll back to stock ROM. archos.ext4.update does nothing. Could you please help me?
tgkokk said:
I tried rooting my Archos 101 G9.
I followed the instructions on the OP, but the new kernel didn't boot properly. It just showed a black screen. If I don't remove the official kernel, nothing happens. I have to roll back to stock ROM. archos.ext4.update does nothing. Could you please help me?
Click to expand...
Click to collapse
Yes ...we can help you ...
First , please write here , step by step what you have doing until now !
1. I removed the unofficial SDE menu.
2. I installed the official SDE menu.
3. I downloaded and unzipped 4_0_6_update.zip and kernel_update.zip
4. I pushed archos.ext4.update to /mnt/storage
5. I removed the Android Kernel
6. I flashed the unofficial kernel
I did everything above twice.
I also tried with your (surudu_petru's) ROM.
If I don't remove the Android Kernel, nothing happens (expected).
I hope I gave you enough information.
Thanks in advance.
Sent from my ARCHOS 101G9 using XDA
tgkokk said:
1. I removed the unofficial SDE menu.
2. I installed the official SDE menu.
3. I downloaded and unzipped 4_0_6_update.zip and kernel_update.zip
4. I pushed archos.ext4.update to /mnt/storage
5. I removed the Android Kernel
6. I flashed the unofficial kernel
I did everything above twice.
I also tried with your (surudu_petru's) ROM.
If I don't remove the Android Kernel, nothing happens (expected).
I hope I gave you enough information.
Thanks in advance.
Sent from my ARCHOS 101G9 using XDA
Click to expand...
Click to collapse
Hi !
Thanks...
...but can you format your device ? see "Format System -> Reformat Device -> OK ! I understand -> Ok! ", than copy original .aos 4.0.6 firmware ....after reboot copy archos.ext4.update in /mnt/storage/ , reboot in SDE , go to " Recovery System" -> Developer Edition Menu-> Remove Android Kernel-> I Understand -> OK! -> Developer Edition Menu-> Flash Kernel & Initramfs -> and copy here zImage and initramfs.......I hope this help you !
Shano56 said:
Prerequisites: You must own an Archos 80/101G9 and be on fimrware 4.0.1 (ICS) or higher.
Step 1: Download SDE firmware HERE
.....
Click to expand...
Click to collapse
Hi all,
It's this tutorial ok even for an Archos 80 G9 Turbo 250GB? Mine have ICS 4.0.3. (official 4.0.6 firmware).
Yes for all archos gen 9
surdu_petru said:
Hi !
Thanks...
...but can you format your device ? see "Format System -> Reformat Device -> OK ! I understand -> Ok! ", than copy original .aos 4.0.6 firmware ....after reboot copy archos.ext4.update in /mnt/storage/ , reboot in SDE , go to " Recovery System" -> Developer Edition Menu-> Remove Android Kernel-> I Understand -> OK! -> Developer Edition Menu-> Flash Kernel & Initramfs -> and copy here zImage and initramfs.......I hope this help you !
Click to expand...
Click to collapse
I've followed your instructions precisely, but the problem still exists. Too bad I lost my files. I think it is over for me, unless you have another solution. In this case, I'll be happy to follow it.
Related
This thread covers things already covered before. This is not a mindless repeat but an attempt to collect information contained in previous guides into one step by step guide to help people having difficulty finding all the information they need to do each of the things listed in the title. If there is missing or incorrect information please let me know and I will update.
Root, nand unlock, radio update, Froyo Rom install (Two Froyo sections. One is if you want to use Cyanogen and one is if you want to use another Froyo rom)... all in one.
Section 1: "Rooting the phone"
Section 2: "Nand unlocking"
Section 3: "Updating your radio"
Section 4A: "Installing Cyanogen Rom"
Section 4B: "Installing other Froyo Rom"
Section 5: "Installing Amon_RA Recovery" (Alternative to Clockwork, optional section for those wishing to give it a try)
Section 6: "Restore to stock rom and radio and turning S-ON" (Good for an RMA)
Section 7: "Installing custom themes" (Just a placeholder currently for an upcoming update)
Section 8: "Installing custom splash screen"
Section 9: "Installing Ubuntu on your Incredible" (Just a placeholder currently for an upcoming update)
This guide is meant to be a quick guide with all of the information to root your phone, nand unlock it, radio update it and put a Froyo rom on it, all in one easy place. For those of you who have done all of this you know how hard it can be to find all of this information.
I claim absolutly no credit for any of this. If you wana give credit, give it to the people who did all of the work, not me. The only thing I accept credit for, and trust me, this is a VERY tiny contribution to the hard work that all of these devs have done, is to put it all in one place.
Disclaimer: I am not a dev. I can not help you with your unique problem, consult the real devs, the ones who made the guides to which I will link. Following this guide or any of the ones I am referencing to can be dangerous and can cause you to end up with a bricked phone (Bricked: Dead, gone, finished, useless, trash, worthless, $400 paper weight, a phone with one app: "Black screen") Notice: Bricking ones phone can cause unwanted side effects such as the desire to scream uncontrollably or the desire to chock the nearest person, continue at your own risk. While following these guides carefully can greatly reduce the risk of a bricked phone, the risk is still inherent and one does continue at their own risk and can not hold this poster or any of the poster of the guides referenced responsibile for any damages caused to the phone, OS or anything related thereto. (I'm not a lawyer, so sorry if that doesn't cover every loophole, point is, don't blame us)
**** MAKE SURE YOU HAVE YOUR PHONE PLUGGED IN FOR ALL OF THIS!!! YOU DON'T WANT YOUR PHONE DYING AT ANY POINT IN THIS GUIDE****
First let's download all of the files we will be needing.
Go here: http://unrevoked.com/#inc
Download both Unrevoked3 and Unrevoked Forever.
Go here: http://adrynalyne.stfuthxbye.net/radio/2.15.00.07.28/PB31IMG.zip
Download this file, it is the 2.15 radio update (DO NOT PUT IT ON THE SDCARD YET)
Now that we have the files, let's get started.
Section 1 "Rooting the phone"
Step 1: Power on your phone.
Step 2: Go to settings.
Step 3: Go to Applications.
Step 4: Go to Development.
Step 5: Select USB debugging.
Step 6: Connect your phone to your computer.
Step 7: Run the Unrevoked3 file that you downloaded.
Additional Step: If you get stuck here with this message on Unrevoked3, "Waiting for bootloader; Make sure driver is installed!" then go to this webpage and follow the instructions there.
Step 8: After it finishes you will be in what is called recovery. It is a black screen with green text options. Reboot should be selected already, press the optical trackball to reboot your phone.
Step 9: Once your phone has rebooted pull down the notification bar and turn on the disk drive part of the USB connection so you can access the files on your sdcard.
Step 10: Save all of the contents of your sdcard to a folder on your computer.
Step 11: Go to My Computer (I am assuming you using Windows because if you were using Linux you probably would have figured all of this stuff out for yourself, however if you are using linux like me, you know how to adapt these parts of the guide to fit your Linux) and find your sdcard (make sure it's your sdcard and not the internal storage of your phone)
Step 12: Format the sdcard to fat32.
Step 13: Place your files back on the sdcard.
Step 14: Place the unrevoked forever zipped file on the sdcard (in the bottom directory, in other words, not in any folders)
Step 15: Go to the market application on your phone and find and install "Rom Manager" by ClockworkMod.
Step 16: Pull down the notification bar and turn off disk drive. (Select charge only)
Step 17: Open "Rom Manager" (it will ask for root permission, grant it)
Step 18: Select "Backup Current ROM" (This is a nandroid backup and will save you countless hours trying to get your phone back to operable status should you mess something up, it will however do nothing to help you if you brick your phone, that's different.)
Once it is done with the backup it will reboot the phone. Congrats, you now have a rooted phone and a backup created!
Section 2 "Nand unlocking"
("But I already rooted my phone, what is this?" Ummm... well it's hard to explain but basically it's a FULL rooting, in laymans terms, one that will allow you to flash stuff that hasn't been signed, like a radio update. I may be a little bit off on the description but I will update it if someone wants to explain it a little better than that)
If you run into a problem in this section or section 4A or 4B with the recovery saying it is unable to find /cach/update.zip go into Rom Manager and at the bottom there is an option to install old recoveries, install an older recovery like 2.5.0.1 and attempt the section again.
Step 1: Go into "Rom Manager" app.
Step 2: Select "Reboot into Recovery"
Step 3: The green text menu will appear upon reboot. Select "install zip from sdcard" (Note: You can use your optical trackball to move around the menu, then press it to make a selection.)
Step 4: Locate the unrevoked forever zip you placed on the sdcard earlier and install it.
Step 5: Once the install is done press the power button to move back once in the recovery menu.
Step 6: Reboot your phone.
Congrats, you now have a FULLY rooted phone. Be sure to thank the Unrevoked team for their hard work! Thanks guys!!! We love you!!
Section 3 "Updating your radio"
NOTICE: This section is by far the most dangerous sections of all of this stuff. For this reason I will give a warning about what NOT to do before I even tell you what to do. During this process we will be updating the radio. When we go to update the radio it will ask you if you wish to update using the file it has found. You will answer yes and allow it to do the update. Should you mess up at any point and be asked again to do the update, DO NOT DO IT!!! If you update your radio twice with this file, you WILL brick your phone. Once again, DO NOT update the radio twice with this file.
Note: This section can only be done if you have done the previous section, Nand unlock. Also there has been a bit of confusion when trying to update the radio, please ensure that you follow the steps carefully as some people are attempting to update their radio from recovery. Updating your radio is done from HBOOT, not recovery.
Step 1: Locate the "PB31IMG.zip" file you downloaded earlier.
Step 2: Place it on the sdcard (in the bottom directory)
Step 3: Power off your phone.
Step 4: Hold the volume down button and then press and hold the power on button at the same time. This will boot you into a screen that says something about HBOOT.
Step 5: At this point it will scan for a file and find the "PB31IMG.zip" file on your sdcard and ask if you wish to update with it. Select yes.
Step 6: You should see a bar on the right that shows you the loading progress. Once it is done, press the power button and the menu options should change.
Step 7: You should now have an option to reboot your phone, press the volume down button and then the power on button to select it.
Step 8: Once your phone is booted go to settings.
Step 9: Select "About Phone" (At the bottom)
Step 10: Select "Software Information"
Step 11: Ensure that in the "Baseband version" section it says "2.15.XX.XX.XX" (No, not really X's, just any numbers there will do)
Step 12: Install a file manager on your phone. Astro File manager will do.
Step 13: Locate the "PB31IMG.zip" file on your sdcard and delete it. (You want to remove it off of your sdcard so you don't make a mistake and update your radio again, bricking your phone)
Congrats, you now have an updated radio!! (Hopefully a phone that isn't bricked either cause you were sure to follow my warning)
There are two Section 4's. Section 4A is for people wishing to install the Cyanogen Rom. Section 4B is for people wishing to install another Froyo 2.2 Rom of their choice. Do not do both sections, I have added the other section so that people have a choice as not everyone wants to use Cyanogen.
Section 4A "Installing Cyanogen Rom"
Step 1: Open "Rom Manager" app.
Step 2: Select "Download ROM"
Step 3: Select "CyanogenMod"
Step 4: Select "CyanogenMod 6.0.0-RC3" (If the numbers are greater than that, that is fine, just means there has been a Cyanogen update)
Step 5: Select Download (If it gives you the option, download google apps too)
Step 6: It should ask if you want to wipe with this install, select yes, it will also ask if you want to do a backup, I recommend you do.
Step 7: Once it is done with the update it should reboot and you are finished.
Section 4B "Installing other Froyo Roms"
Step 1: Find and download the froyo rom of your choice. (Jager and Skyraider are a couple choices but there are others, happy hunting)
Step 2: Place the rom on your sdcard (in the bottom directory)
Step 3: Open "Rom Manager"
Step 4: Select "Reboot into Recovery"
Step 5: Once in recovery select "install zip from sdcard"
Step 6: Locate the rom you placed on your sdcard and install it.
Step 7: Once the update is finished select "wipe data/factory reset"
Step 8: Confirm the wipe. (This will keep you from getting stuck in a boot loop)
Step 9: Reboot your phone.
Note: If you did not wipe your phone after installing a new rom and are stuck in a boot loop, pull your battery out, replace it and hold the volume down button and the power button at the same time. This will place you in HBOOT. Once it has checked your SD card for any signed updates use the volume down button and select the "RECOVERY" option by pressing the power button. This will reboot your phone into recovery where you can preform the "wipe data/factory reset" to get you out of the boot loop.
Congrats, you have a rooted phone with the nand unlocked, the radio updated and a VERY sweet cooked rom on your phone. Your phone should be speedier than ever. Enjoy and be sure to thank the rom developers for their hard work!!
Section 5 "Installing Amon_RA Recovery"
http://forum.xda-developers.com/showthread.php?t=758874
Step 1: Go to the thread linked above.
Step 2: Find the latest version of Amon_RA recovery and download the file ending in ".img" (labeled recovery reflasher)
Step 3: Plug your phone into your computer.
Step 4: Go to settings.
Step 5: Go to Applications.
Step 6: Go to Development and disable USB Debugging.
Step 7: Start running Unrevoked3.
Step 8: Select the menu option "File" in Unrevoked3.
Step 9: Select Custom Recovery.
Step 10: Locate the Amon_RA recovery ".img" file that you downloaded and select it.
Step 11: Turn USB Debugging back on. Your phone will now go through the process of installing Amon_RA Recovery. Leave it alone till it is sitting in recovery.
There are some nice features in Amon_RA, take a look around if you want. The nandroid backup and restore is quite elaborate. Enjoy.
Section 6 "Restoring to stock rom and radio"
The following section is for anyone looking to restore their phones to stock rom 2.1 and radio 1.0. Do not follow this section unless you are wanting to revert back to stock radio and rom.
Step 1: Download this file: http://www.mediafire.com/?n3bmd2bkz55k1b9
Step 2: Connect your phone to your computer.
Step 3: Save all the files on your sdcard to a folder on your computer.
Step 4: Format your sdcard to fat32.
Step 5: Place the "PB31IMG.zip" file that you downloaded onto the sdcard in the bottom directory.
Step 6: Power down the phone.
Step 7: Hold the volume button down while pressing the power on button. (This will place you in HBOOT)
Step 8: HBOOT will find the file on the sdcard named "PB31IMG.zip" and ask if you wish to update with it. Answer yes. (It will start to load and restart HBOOT and scan for the file again, don't panic, let it do it's thing.)
Step 9: When it is finished it will ask you to reboot the device, press volume up to reboot.
Step 10: Remove "PB31IMG.zip" from the sdcard.
You should now have a stock rom and radio, good if you are wanting to do an update to the OTA 2.2.
Section 7: "Installing custom themes" (Just a placeholder currently for an upcoming update)
Future update!!
Section 8: "Installing custom splash screen" (Just a placeholder currently for an upcoming update)
This can only be done once you have unlocked the nand, done S-OFF in other words.
Step 1: Go here and find the custom splash you want. (Or if you have one from somewhere else you want to use just follow the rest of the directions)
Step 2: Make sure the file is named PB31IMG.zip.
Step 3: Place the custom splash on the sdcard bottom directory.
Step 4: Shut down the phone.
Step 5: Boot into HBOOT by holding down the volume down button and the power key at the same time.
Step 6: When it asks you if you wish to update answer yes by pressing the volume up key.
Step 7: When it is finished press the volume up key to reboot.
Step 8: Remove the PB31IMG.zip file from the sdcard.
Congrats on your custom splash and bootscreen.
Section 9: "Installing Ubuntu on your Incredible" (Just a placeholder currently for an upcoming update)
Future update!!
References:
Rooting: http://unrevoked.com/#inc
Nand unlocking: http://unrevoked.com/#inc
Radio Update: http://forum.xda-developers.com/showthread.php?t=737400
Cyanogen Froyo ROM: http://www.cyanogenmod.com/
To any others I missed: Thank you all for your very helpful guides and tons of information. You devs are what makes the android community awesome!
I check the forums pretty frequently but just incase you feel you have a need to email me, here is my address.
Email: [email protected]
Nicely done. This should answer a lot of questions. Perhaps this should be a sticky?
Perhaps but we will leave that up to the mods and the members. If the members find it useful enough then I am sure they will get it stickied
Sent from my Incredible.
Your guide has already cause one user to have problems.
You say "find PB31IMG.zip in this thread." The only PB31IMG.zip in that thread is the stock RUU back to 1.00.03.04.06, not the 2.15 radio. You should probably upload the 2.15 radio yourself and link to it.
Berzerker7 said:
Your guide has already cause one user to have problems.
You say "find PB31IMG.zip in this thread." The only PB31IMG.zip in that thread is the stock RUU back to 1.00.03.04.06, not the 2.15 radio. You should probably upload the 2.15 radio yourself and link to it.
Click to expand...
Click to collapse
Thank you, on it right away.
Sent from my Incredible.
Berzerker7 said:
Your guide has already cause one user to have problems.
You say "find PB31IMG.zip in this thread." The only PB31IMG.zip in that thread is the stock RUU back to 1.00.03.04.06, not the 2.15 radio. You should probably upload the 2.15 radio yourself and link to it.
Click to expand...
Click to collapse
The guide has been updated. Thank you for catching that. The user who had the problem, are they still able to flash another radio?
Here is the link to the updated 2.15 radio
http://adrynalyne.stfuthxbye.net/radio/2.15.00.07.28/PB31IMG.zip
Yes, all that happened was it took them back to stock.
Thank God. Please keep me updated on the progress of this user so I can fix any other discrepancies in the guide. Thanks a lot for your help.
Sent from my Incredible.
Question. I'm not going to install Forever, but I've been rooted for a long time. However, I am still running the 1.00 radio. Can I just use the 2.15 radio PB31IMG.zip file over the 1.00 radio? If not, then will installing this PB31IMG.zip file factory restore my phone or just update the radio? I thought with the 1.00->2.05 radio, it would make you factory restore your phone, not sure if that was the case with 1.00->2.15
TheWhiteBandito said:
Question. I'm not going to install Forever, but I've been rooted for a long time. However, I am still running the 1.00 radio. Can I just use the 2.15 radio PB31IMG.zip file over the 1.00 radio? If not, then will installing this PB31IMG.zip file factory restore my phone or just update the radio? I thought with the 1.00->2.05 radio, it would make you factory restore your phone, not sure if that was the case with 1.00->2.15
Click to expand...
Click to collapse
You can not do a radio update from 1.00 to 2.15 without either doing a factory reset of sorts with that OTA file or doing the unrevoked forever.
Sent from my Incredible.
dadicus said:
You can not do a radio update from 1.00 to 2.15 without either doing a factory reset of sorts with that OTA file or doing the unrevoked forever.
Sent from my Incredible.
Click to expand...
Click to collapse
There doesn't exist a signed RUU with the 2.15 radio, so in order to get the 2.15 radio, you HAVE to use unrevoked forever. The closest you can get is 2.05 radio
Berzerker7 said:
There doesn't exist a signed RUU with the 2.15 radio, so in order to get the 2.15 radio, you HAVE to use unrevoked forever. The closest you can get is 2.05 radio
Click to expand...
Click to collapse
Thanks for that info, I was unaware of that.
Sent from my Incredible.
In the very first steps, I have already got an error, "Waiting for bootloader; Make sure driver is installed!" Which driver? This is my first time roting, everyone says how easy it is but every direction I see is distinctly different and though I feel I can usually hold my own in the tech world, I am lost. Please lend a brotha a hand.
yomonk1 said:
In the very first steps, I have already got an error, "Waiting for bootloader; Make sure driver is installed!" Which driver? This is my first time roting, everyone says how easy it is but every direction I see is distinctly different and though I feel I can usually hold my own in the tech world, I am lost. Please lend a brotha a hand.
Click to expand...
Click to collapse
I am working on a solution for you. Hang in there.
You are doing this on windows right?
Sent from my Incredible.
yomonk1 said:
In the very first steps, I have already got an error, "Waiting for bootloader; Make sure driver is installed!" Which driver? This is my first time roting, everyone says how easy it is but every direction I see is distinctly different and though I feel I can usually hold my own in the tech world, I am lost. Please lend a brotha a hand.
Click to expand...
Click to collapse
dadicus said:
I am working on a solution for you. Hang in there.
You are doing this on windows right?
Sent from my Incredible.
Click to expand...
Click to collapse
Got it! Went to the webpage "hboot driver" in the unrEVOked package and followed those directions, it worked. I'm on my way. formatting card now (forever...) then reload and moving on! The big problem this morning is that I wont be able to do ANYTHING else until the servers come back up. Whats up with that anyway?? Cant do anything without that!
(And yes, Windows) Thanks for your help
By servers you mean the android market? You can still do a search for Rom Manager and install it.
Sent from my Incredible.
dadicus said:
By servers you mean the android market? You can still do a search for Rom Manager and install it.
Sent from my Incredible.
Click to expand...
Click to collapse
No, everything seems to be down this morning. Cant search anything, no webpages work. Seems many others are experiencing this too.
So like locally you mean? That sucks.
Sent from my Incredible.
yomonk1 said:
No, everything seems to be down this morning. Cant search anything, no webpages work. Seems many others are experiencing this too.
Click to expand...
Click to collapse
I added in an additional step for the problem you were having in case others come up against the same problem. Thank you for informing me on what you did to fix the problem.
I just modified the guide. I changed section 4 to two different sections. Section 4A is for those wishing to update to Cyanogen 6.0.0-RC3 rom. Section 4B is for anyone who does not wish to use Cyanogen and wants to try another Froyo rom.
I wanted to make the guide more universal as I created the guide to be a kinda catch all and felt that limiting the instruction to one rom was biased. Even though I have tried other roms and prefer Cyanogen's rom, I wanted to leave that choice up to the users.
This thread is primarily intended for n00bs.
I would like to say thanks to xda forum members: Noejn, Zecanilis, drellisdee, The_ERROR etc. Also thanks is due to Godlike! at tech-mania.com for his tutorials. Thanks is due especially to The_ERROR for proofreading the post and to other users for their suggestions written in the thread.[/SIZE]
---------------------------------------------------------------------------------------------
NEW - 3 May 2011 - Simplified Guide to Root & install version 1.2 of Custom Thunderg Recovery by AmonRa/modified by Drellisdee on LG P500
ALWAYS MAKE A BACKUP BEFORE CUSTOMISING YOUR PHONE.
[CUSTOMISING A PHONE USUALLY INVOLVES: ROOTING >>>> INSTALLING CUSTOM RECOVERY >>>> INSTALLING CUSTOM ROM]
The instructions written below have been tested by me using an Indian unbranded GSM model of LG P500 which came with stock Android 2.2.1 (V10C). The procedure to be followed for any LG P500 phone is the same.
This post is split into 4 major sections -
1. INSTRUCTIONS FOR ROOTING
2. INSTALLING ANDROID SDK ON A WINDOWS PC (This step is needed to install Custom Recovery on phone using adb from PC. Can be omitted if Recovery is installed from phone using Terminal Emulator)
3. INSTALLING A CUSTOM RECOVERY
4. INSTALLING CUSTOM ROMs
MUST READ: If you haven't read this thread already, please do read it - Dictionary for n00b - What is.../What does ...mean?
---------------------------------------------------------------------------------------------
1. INSTRUCTIONS FOR ROOTING
To know your present firmware version - Go to Settings/About Phone
Only phones which come with stock android 2.2 could be rooted till recently.
UPDATE - 24 April 2011 : A tool called 'GingerBreak APK' is able to root phones running stock android 2.2, 2.2.1 & 2.2.2. Read about it HERE. This tool enables rooting without the need for downgrading the firmware to 2.2. If 'GingerBreak APK' doesn't work out for you, continue reading to understand the procedure to root your phone after downgrading your firmware. Note: 'GingerBreak APK' permanently roots your phone. Also,GingerBreak might not install BusyBox and SuperUser apps properly on your phone. These apps are required by many rooted apps for their proper functioning. So, use Root Checker from android market to verify the proper installation of these 2 apps.
If your phone runs stock android 2.2, enable 'USB Debugging' on Phone (Settings/Applications/Development). Install z4root (copy the apk file to the sd card and open the file after browsing to the location using the phone's file manager), run it and root the phone. Find it HERE.
Choose the permanent root option as it is still possible to force unroot if needed.
Restart the phone and launch z4root to check the root status. A successful rooting should show 'Unroot' option when z4root app is opened.
{Note: z4root automatically installs Busybox and Superuser application(which appears as an icon in your app drawer) on the phone.}
If rooting fails with z4root, there is another application called SuperOneClick which can root your phone. Read about it HERE
For phones that came with stock 2.2.1 or 2.2.2 installed, rooting first involves downgrading the firmware to 2.2.
Downgrading the firmware can be done with KDZ-FW-UPD.exe (procedure outlined below)
(KDZ-FW-UPD.exe has been claimed to work best with windows xp 32bit.)
FIRST: DOWNLOAD THE Android 2.2 FIRMWARE FOR YOUR DEVICE. For this, go to: [ROMS] Original LG Firmware list and read about the procedure to download the original firmware.
{Tips: Use Ctrl+F in browser to search for Country name, Remember to change the alphabet in 2 places in the final link to download the firmware, Do not bother about the 'CDMA' tag attached to country code. It works for the GSM model phones too. If the link to find out the country codes doesn't work, use the 2nd method mentioned in the post to find out the country code using your phone's IMEI or ESN number }
Download the required Firmware onto your PC.
Links to Original firmware versions for Indian P500 are mentioned in THIS POST
Procedure to install original firmware using KDZ-FW-UPD.exe ( KDZ FIRMWARE UPDATER ) This procedure can also be used to restore the stock firmware and recovery onto your phone in case you want to give your phone to the service centre during warranty period as the phone will appear similar to as you bought it from the store.
[Note: This procedure was used to install V10B_00.kdz(android2.2) over V10C_00.kdz(android2.2.1) on an unbranded Indian GSM model of LG P500 using a Windows 7 Ultimate 64bit updated to date PC.]
1. Install LG PC Suite IV from SD card which came with phone by connecting the phone to PC through USB cable. This is done to install the drivers for the phone on the PC (the procedure is as follows)
- Enable the 'USB Mass Storage Only' mode in the phone's Settings/SDcard & Phone Storage menu.
- Connect phone to PC with the USB Cable.
- Press the 'Turn on USB Storage' button which appears on phone.
- Browse to the folder containing the 'LG PC Suite IV' on the phone's SD card using Windows Explorer and run the LG Installer file. PC Suite will now install on your system along with the required drivers for your phone.
- Cancel setting up PC Suite or continue setting up PC Suite if you want to Sync or backup the phone data.
- After closing PC Suite, Safely remove the USB device from your system.
- Press the 'Turn off USB Storage' button on phone screen.
- Detach the USB Cable.
- Disable the 'USB Mass Storage Only' mode in the phone's Settings/SDcard &Phone Storage menu.
Alternatively, I also tried installing the latest drivers via LG Mobile Support Tool from LG's website (available HERE) but KDZ-FW-UPD.exe (mentioned below) crashes when run. This could be happening only to me, so please try for yourself before writing off this method.
2. For my comfort more than anything else, I switched off the screensaver and other power saving features on the PC and also set the screen timeout delay on the phone to 30 minutes.(Settings/Display/Screen Timeout)
3. Charge the phone to the maximum.
4. Enable USB Debugging on Phone (Settings/Applications/Development).
5. Detach all other peripherals from your PC. Exit all running applications on your PC especially other PC suites if any. Also exit running programs from the notification bar on the desktop. (Also uninstall Nokia or other phone drivers & microsoft visual ++ runtime environments - not an essential step.)
6. Disable 'LGE Virtual Modem' in PC's Device Manager. (In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.)
7. Unmount the SD card from the phone (Settings/SDcard & Phone Storage).
8. Open phone back and remove the SD Card.
9. Download KDZ_FW_UPD_EN.7z onto your PC and extract it to a folder. Available HERE.Direct Download Link. (MD5 of 7zip file - 813A28BE9182AB604A1D43E745CE7AD7)
10. Run the msxml.msi file and complete the installation.
11. Connect the phone to PC with USB Cable.( If you are using a desktop PC, make sure you use USB ports that are in the back of your PC, avoid the front ports.)
12. Run KDZ_FW_UPD.exe from the extracted folder.
13. Chose TYPE as 3GQCT & Phone Mode as DIAG.
14. In the 'KDZ file' space, browse for the firmware you want to install. (In this case V10B_00.kdz)
15. Press the 'Launch software update' button.
16. The firmware flashing process is now underway.
If all goes well, in 5-10 minutes the phone will be flashed with the new firmware.
I shall describe in detail what happened with my phone - 10-15 seconds after launching software update on PC, my phone screen turned blank and in a couple of seconds the phone entered the 'Emergency Mode'. During this mode the screen was yellow with Emergency Mode written along the middle of the screen. The phone stayed in the same way till the Software update procedure finished on the pc and the phone turned blank. I waited a while for it to reboot but after a minute or so, I manually switched on the phone. The phone came alive and following the LG boot animation, the android logo screen came up. The phone spent about 2 whole minutes in that state before booting up fully and entering the home screen. Update: Wait till phone reboots by itself or wait for a while before manually switching it on.
17. After booting up fully, detach the phone from the pc.
(If the phone gets stuck in the android boot logo screen during first boot, doing a hard reset by pressing and holding the VolDown+Home+Power buttons may resolve the problem.)
Go to 'About Phone' in Settings and confirm the change from 2.2.1 or 2.2.2 to 2.2.
Root the phone using z4root as mentioned before.
If rooting fails with z4root, there is another application called SuperOneClick which can root your phone. Read about it HERE
IN CASE OF PROBLEMS DURING DOWNGRADING FIRMWARE, read the following thread completely. Various types of errors and various measures to correct them including some innovative ones like shaking the phone etc. are mentioned here - [HOWTO] Phone not responding at all - last chance to repair. It is advisable to read this thread completely before attempting to downgrade the firmware using KDZ_FW_UPD.exe to become aware of all the possible problems you might encounter and their possible solutions.
PS: Here is the link to the phone drivers that came with my SD card. One user reported a problem wherein kdz updater would recognise the phone but the update process would fail during kdz unpacking. the problem was resolved by using the drivers i sent him. So, if anyone has the same issue, it might be worthwhile to try out the following drivers. I wouldn't advise everyone to follow this method, but those of you who are feeling lucky might try it out. Download Link
---------------------------------------------------------------------------------------------
2. INSTALLING ANDROID SDK ON YOUR WINDOWS PC
This step is required to install Custom Recovery on your phone using adb from your PC. Using a Custom Recovery, you can make a backup of your current ROM, restore backups, create partitions on your SD card, wipe your phone and the SD card and then also go on to install Custom ROMs using the Flash from Zip option.
Installing a Custom Recovery can also be done in other ways. Using Android SDK from your PC is just one method.
(Custom Recovery can alternatively be installed on your rooted phone using the commands given in the next section using a Terminal Emulator. This method removes the need for installing Android SDK on your PC and connecting your phone to PC. Download Terminal Emulator from Android Market. Install on phone. Run it and give it root permissions when prompted by the 'Superuser' application. As mentioned in the next section, copy the 2 files (flash_image & the custom recovery image file) needed to install Custom Recovery onto the root directory of SD card. Reboot phone. Open terminal emulator and type 'su' without the quotes and press Enter. This will take you to the root shell (#) from the default user shell($). Carefully type in the 7 commands mentioned in the next section one after the other. After typing in the last command (reboot recovery) and pressing enter, WAIT. The phone will reboot. Custom Recovery will have been succesfully installed on your device.
Hint: Copy the installation commands as a text file to phone & copy and paste the commands one by one into terminal emulator using a text editor. Please make the necessary changes to the installation commands depending on the recovery version used)
To install Android SDK on PC, there are a few requirements/downloads which have to be completed first:
JDK (Java Development Kit) - Download Here
JRE (Java Runtime Environment) - Download Here
Android SDK installer - Download here
So after all the downloads are completed, you are good to go. Run PC as Administrator.
First of all install the JDK, then the JRE and then the SDK Installer.
{If when android sdk installer is run, you get an error that JDK or JRE is not detected even after their installation, wait for a while, shut down the computer and restart and run the SDK installer once again.}
Make sure that while installing the android sdk, the installation directory should be the root of a partition i.e. it should be in the following form: C:\android-sdk, where you should replace the letter C with the letter you have assigned to the partition that you want to install it in.
Now that the Android-SDK is installed, go to the installation directory and start the SDK Manager. You need to add the components of the Android SDK to your installation. Before that I would like to inform you that you can save time if you download only what is necessary. If you are on Android 2.1 then you should download the 2.1 sdk, for 2.2 the 2.2 sdk and so on. You do not need to have all the versions for this thing to work. Just your version would do. So to start adding components, I recommend that you read THIS
After installing the desired components, you need to do perform some simple steps in order to use the adb terminal just like the cmd terminal for Windows.
For that purpose, here are the steps to be followed:
Right click My Computer, select Properties, and click Advanced System Settings. (Windows XP users - Right click My computer and just click Properties and select the Advanced Tab)
Click on Environment Variables, in the System Variables box, scroll down to the variable name 'Path' and double click to edit it
It would read something like " %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static".
Here you need to add a semicolon ( ; ) and add the path of the tools folder in android-sdk.
It should finally be like this " %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\android-sdk\platform-tools {or the location where adb.exe resides on your system}
Click OK wherever asked and then restart your computer.
Now open a command prompt window and type adb and hit enter. If a terminal window is displayed, you have done it all right.
If it gives some error message, read the article carefully and see what you have messed up with.
---------------------------------------------------------------------------------------------
Tip:
Using adb - How to install apps from PC without having to copy them first to the SD card?
If you want to install apps in one click, all you need to do is download the .apk file of your application to your PC and set the open with option to this batch file which you can download HERE
Save the batch file on the desktop of your PC before setting the option to 'Open With'.
---------------------------------------------------------------------------------------------
3. INSTALLING A CUSTOM RECOVERY
(Procedure of installing Custom Recovery using a terminal emulator from your phone instead of installing android SDK on your PC and connecting your phone to PC is mentioned in the last section.)
UPDATE - 3 May 2011 : Very simple way of installing Custom Thunderg Recovery by AmonRa/modified by Drellisdee version 1.2. Originally posted by ungaze in this post.
1. Download Android Terminal Emulator from Android Market. Install it on your rooted phone.
2. Download the file "amon_ra_recovery_installer.zip" from here or here. Check the MD5 hash value of the downloaded 'zip' file using tools like HashTab etc. before proceeding further. Correct MD5 value : 86db8a52b01f049cadb8f097a4c5bd9e
3. Extract the contents of the 'zip' file to the root of the sd card (ie. not inside any folder) using tools like 7-Zip or WinRAR or any other similar tool.
4. Open the terminal emulator app on your phone and type in the command 'su' without the qoutes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions to the terminal emulator app. Click 'Allow' and proceed. You will notice that the shell prompt has changed from the previous user shell '$' to root shell '#' in the emulator app.
5. While in the root shell '#', type in the following command and press Enter. Wait and the phone will reboot into the Custom Recovery.
Code:
sh /sdcard/rf.sh
Once you are up and running with a rooted phone, you will need to download the 2 files needed to install the Custom Recovery. They are:
Download No:1: flash_image - (This file is the same one needed to install any of the 3 versions of Custom Thunderg Recovery by Drellisdee given below)
Download Link (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Mirror Link (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Mirror Link - requires registration at androidforums.com. (MD5 of zip file - 13FED5DF927214D744A256DAB4C3DC06)
Download No:2: Custom Recovery image file - Choose & download any version among the 3 available after reading what is written below.
Custom Thunderg Recovery by Drellisdee has versions 1.1, 1.2 and 1.2.1 at the time of writing this. I personally prefer version 1.2 as it supports backup & restoration of ext4 Partition on SD Card. Version 1.2.1 is a little experimental in nature & it may not fit all devices as it has a size near 5 MB.
Link to xda-forum thread for Custom Recovery P500/Thunderg - HERE.
The different versions of the Custom Recovery image files are available at the following pages
Custom Recovery P500/Thunderg v1.1
Direct Download link - (MD5 of zip file - eb4ea2ffb26f387a891bb4d7261a0e5f)
Mirror Link - (MD5 of zip file - eb4ea2ffb26f387a891bb4d7261a0e5f)
Custom Recovery P500/Thunderg v1.2
Direct Download link - (MD5 of zip file - 217FC9115899A41195CF124CAF07B880)
Custom Recovery P500/Thunderg v1.2.1
Direct Download link - (MD5 of zip file - 388aac16b1184ab15b5500b2b32d914c)
Please check the MD5 hash values of downloaded files to ensure that files are not corrupted using tools like HashTab etc.
Now to install Custom Recovery, Copy the two files [ the chosen recovery image file (*.img) & the flash_image file (flash_image) ] and paste in the root of your SD card (root means the directory L:\ where L is the letter for your Phone's USB Storage. In short, don't create a folder and paste the files inside it on your SD card).
{Note that the recovery image file should have an .img extension and flash_image file should have no extension when placed on the SD card}
Reboot the phone. Connect phone to PC.
The next step requires Android SDK to be installed on your PC.If you have installed the Android SDK, follow these steps:
Go to Start Menu & Run and type cmd (run as Administrator)
In the cmd window, type adb. If you have installed it correctly, you will see a lot of text on the screen. If you get an error message then you have probably not installed the Android SDK properly.
Type adb shell and hit enter
Type su and hit enter
See your phone at this time and touch the 'Allow' option which SuperUser shows you
Now the terminal window will have a # sign appended to it instead of the previous $ sign. See this screenshot for a better understanding
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now one by one, copy the following lines, in the serial order and paste it into the terminal window and press enter following each line(right click on window and paste, CTRL + V won't work)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (if it gives error message here, simply proceed to the next step)
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/LGp500-recovery-v12.img (If the recovery version chosen is different from v1.2, type the appropriate file name of the recovery image here instead.)
reboot recovery
Click to expand...
Click to collapse
Wait. The phone will reboot now.
Note:{If you get this error after step 4
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
failed on '/system/etc/install-recovery.sh' - No such file or directory
Simply move on to the next step.
If you get any errors other that those mentioned here, please do not proceed with the last command of 'reboot recovery'. If you do so, recovery may not be correctly installed and you will lose all data on the phone as the phone will be reset to factory defaults. Please go back to the instructions and see what you have done wrong.
NOTE: If on booting into the recovery you get the following message at the bottom of the screen -
E: 'Bad Boot Message'
Don't panic, it's perfectly normal and you can proceed with what you want to do from the recovery.}
Detach the phone from the PC.
To access the Custom Recovery, turn off the phone and then press & hold Home+Vol Down+Power buttons to boot into the Custom Recovery.
---------------------------------------------------------------------------------------------
Once you have booted into the recovery, the touch screen won't work. The actions assigned to the different buttons are given here. Use them to navigate through the different options in Custom Recovery.
Up & down: vol-up and vol-down key
Select: Menu key (left most)
Back: Back (3rd from left)
---------------------------------------------------------------------------------------------
What does Custom Recovery look like & What does it do?
Note: In Custom Recovery versions 1.2 and above, zips can be extracted from inside folders. So, save the zips in a folder named AAA and flash the zip after browsing inside the folder through recovery. The folder name should be named 'AAA' so that it appears among the first on the recovery screen, since scrolling is not an option in recovery.
Note: There is also an unofficial port of ClockworkMod Recovery availble. I do not recommend this recovery for newbies as it isn't compatible with all Custom ROM's out there.
---------------------------------------------------------------------------------------------
4. INSTALLING CUSTOM ROMs
BEFORE FLASHING ANY ROM, DO A NANDROID BACKUP FROM CUSTOM RECOVERY
Since all the ROMs have their own kinds of partitions to be created and other requirements, you can check them at the ROM specific pages.
General procedure to follow for installing a Custom ROM
Boot into Custom Recovery
Wipe your cache, dalvik cache, SD card
Make partitions according to the ROM requirement
Wipe cache again.
Connect Phone to PC
Toggle USB MS and paste the ROM zip file to a folder called AAA in the root of the SD card
Disable USB MS.
Detach phone from PC.
Select 'Flash from zip' option in Custom Recovery menu
Select the ROM file
Flash the ROM file
After flashing is finished, Reboot the phone.
Note: It will take some time to flash and reboot into your new Custom ROM. The phone may stay with the boot logo displayed for a number of minutes. Do not switch off phone during this period.
---------------------------------------------------------------------------------------------
In case of problems with phone, read: [HOWTO] Phone not responding at all - last chance to repair
Also read: [READ FIRST] [REF] Repository of howto's, roms, kernel, etc.
If you feel benefited by this thread, I humbly request you to rate this thread and vote it to the front page. The option to rate and vote is present in the title bar of the thread on the right side.
Please post your feedback. Also THANKS is always welcome. Use the THANKS button (below right) if you feel that I deserve it.
Update - 24 April 2011 - New rooting method without needing to downgrade firmware.
Update - 3 May 2011 - Very simple way of installing Custom Thunderg Recovery
Update - 3 May 2011 - Added Simplified Guide to Root & install Custom Recovery on P500
i have done all steps but cannot boot in custom recovery may be pressing the keys wrong please help
Thank you very much for posting this! I think it's only missing a section for downgrading, and changing from one custom rom to another, and it's perfect!
I guess my memory card died.. The USB-MS Toggle doesn't launch anything on my PC, tried several times.Now what?
FnH84 said:
I guess my memory card died.. The USB-MS Toggle doesn't launch anything on my PC, tried several times.Now what?
Click to expand...
Click to collapse
Have you installed the drivers for the phone on your computer? If you haven't, your phone will not be detected when toggling usb mass storage.
saileshchowatia said:
i have done all steps but cannot boot in custom recovery may be pressing the keys wrong please help
Click to expand...
Click to collapse
Did you read the thread I have linked to at the end of the article? it may help you.
FnH84 said:
Thank you very much for posting this! I think it's only missing a section for downgrading, and changing from one custom rom to another, and it's perfect!
Click to expand...
Click to collapse
The procedure for downgrading the firmware is included in the article. The procedure is the same for installing any version of original firmware on the phone.
Procedure to change from one custom rom to another various with each rom.some may need a wipe while others might need repartitioning your sd card.
victortangocharlie said:
Have you installed the drivers for the phone on your computer?
Click to expand...
Click to collapse
Yes. It worked fine before. I tried to flash with CM7, and something went wrong. The whole SD-card is empty, works on another phone though. However, Windows will not recognize it no matter what I do
Do you mean to say that your sd card is empty our that you can't see the sd card contents on your computer?
victortangocharlie said:
Do you mean to say that your sd card is empty our that you can't see the sd card contents on your computer?
Click to expand...
Click to collapse
Both. I put the memory card on another phone and it said it was empty. Also, custom recovery says it's empty and from mount menu, I can see it keeps unmounting.
Have you tried another card on your phone?
victortangocharlie said:
Have you tried another card on your phone?
Click to expand...
Click to collapse
I managed to get the card work via another card reader. I put the zip files on it and trying again now. Hope it will work.
EDIT: It works!!!
nvm.....................
Glad to hear it.
Sorry for noob question, but after downgrade to 2.2, root, can I flash any rooted 2.2.1 ? And is there any?
Once you have rooted your phone, you can install any custom rom meant for p500. This includes all android versions. And, you don't have to apologise for being a noob, this thread is meant for noobs primarily. everyone has to start someplace. There are many rom's accessible on this forum including android versions 2.2 to 2.3.3. I suggest you try Nessy#Euridice ROM by Dookmatt. I am using it and it is easy to set up.it is based on android 2.2.2
Thanks,
So if there isn't any method for root on 2.2.1, how they managed to give us pre rooted 2.2.1 roms?
I seek the fastest and stable rom with OC, but Im used to CM7 tweaks,.so im interested in it the most. So is it usable? Beside cm7 which is the fastest?
Guess, you will have to ask the people who make the rom's. I don't know about the cm7 rom.haven't used it myself.
IFLPI said:
Thanks,
So if there isn't any method for root on 2.2.1, how they managed to give us pre rooted 2.2.1 roms?
I seek the fastest and stable rom with OC, but Im used to CM7 tweaks,.so im interested in it the most. So is it usable? Beside cm7 which is the fastest?
Click to expand...
Click to collapse
rooting a stock Rom is hard where as as rooting a custom made rom is easy because u only need the framework to create ur custom rom....
and about CM7 u can choose between many flavours.... its upto u ..
hi
hey man thanks for the wonderful tutorial!!
i just broght my phone 2weeks back. got it after lots of requests to dad!!
i wanna try all the stuff but im damn scared if i would brick my phone..
although i have the exact same phone as yours..unbranded indian optimus one with v10c
should i try it or is there a risk that ill brick it..?
if i brick it.. is there a chance that i can get it repaired? or will the lg ppl refuse to support me because i screwedwith it??
thanks in advance!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Setup, Preparation and Prerequisites
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter the bootloader - Turn the phone off. Hold volume down + power. The bootloader is also known as fastboot mode.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Try this first, but if that doesn't work look here. Still having issues? Give this a try. None of these working? Hopefully this does the trick.
Downloads
Download a custom recovery of your choice and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP) or ClockworkMod (CWM)
Root:
SuperSU
Information
Rooting a nexus device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has. Using a toolkit will only make things worse in the long run...learn to do it properly. It has been proven that every time you use a toolkit, god kills a kitten. Save the kittens.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Plug the phone into your PC, then open a command prompt window window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.
After the above command has finished excuting, run the following (DO NOT skip this step, it is more important than you think):
Code:
fastboot reboot
The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.
Close the command prompt window.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock rom
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. Leave the phone at the home page of the custom recovery.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the Nexus 5 Android Development and Nexus 5 Original Android Development section) onto the phone (remember the location where you copy it to)
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. To install a custom rom the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the rom > select the rom > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the rom, and finally reboot the phone.
Keep in mind that the first boot after installing a custom rom & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted...Plus you saved a kitten. Enjoy
Troubleshooting & FAQ
Why am I seeing a red triangle with a dead android when booting into recovery even after I flashed a custom recovery?
What you are seeing is the stock recovery, meaning that the custom recovery that you flashed did not install correctly. Try the following suggestions:
Make sure you are using the USB cable that came with your phone. Only use other ones, if the stock one isn't working
Try using different USB ports. USB 2.0 ports (the ones that ARE NOT blue) are preferable. USB 3.0 ports (the blue ones) may cause problems with connectivity.
If you are on a desktop, use the ports on the back of the tower instead of the ones in the front. These ports are directly connected to the motherboard, rather than the ones in the front which are usually attached to a header cable which then indirectly connects to the motherboard.
My phone wont boot into android. I can only access the bootloader and custom recovery. What do I do?
Suggestion 1: Factory reset via recovery.
TWRP Instructions:
Boot into recovery
Wipe > Swipe to Factory Reset
Reboot
CWM Instructions:
Boot into recovery
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
Reboot
If that doesn't work continue onto Suggestion 2.
Suggestion 2: Push a ROM to your phone and flash it.
Download a ROM onto your computer. If you don't have time to look for a ROM, just download the stock ROM.
Move the downloaded ROM onto your desktop, and rename the file to "ROM.zip" (without the quotation marks)
Boot phone into recovery
Open command prompt and run the following commands:
Code:
cd Desktop
adb push ROM.zip /sdcard/
Wait for it to finish copying the file, then flash the ROM. If you need further details on how to flash a ROM take a look at the OP, section 3. Rooting, Option B)
If that doesn't work continue onto Suggestion 3.
Suggestion 3: Flash the factory images.
Flash the factory images
My phone wont boot into android. I can only access the bootloader. What do I do?
Flash the factory images
My phone exploded. What do I do?
Tape it back together then flash the factory images
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
dombera said:
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
Awesome, thx
Sent from my Nexus 4 using Tapatalk
This is awesome, will come in handy.
Sent from my HTC Desire using XDA Premium 4 mobile app
Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
---------- Post added at 01:43 AM ---------- Previous post was at 01:41 AM ----------
Xero258 said:
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Click to expand...
Click to collapse
If you unlock bootloader & root, and modify some system files, OTAs may not be able to pass some pre-install checks, at least this has happened to me on N4 before. I added one line to /etc/build.prop, also one of the older SuperSU versions had to be uninstalled for pre-install OTA checks to pass.
Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
Click to expand...
Click to collapse
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
I see some Desire folks
Did u order one chromium?
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
talz13 said:
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
Click to expand...
Click to collapse
If you wipe cache exactly after you unlock the bootloader, without booting, no.
Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
Not yet. Hoping to eventually get it though.
Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful
Click to expand...
Click to collapse
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
I'm not a really famous desire user but yes I bought it. Did you buy it to? Happy to see some other desire users.
Sent from my HTC Desire using XDA Premium 4 mobile app
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
boysetsfire said:
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
Click to expand...
Click to collapse
It should work fine, but whats wrong with booting it up for the first time?
Chromium_ said:
It should work fine, but whats wrong with booting it up for the first time?
Click to expand...
Click to collapse
Nothing wrong, just the laziness of not wanting to do the initial setup two times
Chromium_ said:
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Click to expand...
Click to collapse
abaaaabbbb63 said:
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
Click to expand...
Click to collapse
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Whyzor said:
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Click to expand...
Click to collapse
Yes that is correct, they do not boot. I will update the OP now, sorry for the confusion.
Originally I had read the following threads and it seemed that they were somewhat functioning, but it is now confirmed that neither one boots.
TWRP
CWM
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Credits
@social-design-concepts for his great work and exploit for Intel Tab Devices
@vampirefo for CWM binary for Intel devices + Linux scripts
@vache for the full Repacked CWM image
Devices Compatible
A1-840FHD
A1-840 (HD)
A1-830
B1-810
A1-850
A1-860
B1-820
A3-A30
Requirement
Install the official Generic Google USB Drivers on your Desktop (http://developer.android.com/sdk/win-usb.html) - Also available in the TOOLKIT Package
Enable USB Debug on your Device
Guide 1 - Boot Tethered CWM
Compatible with
A1-840FHD (firmware 1.042_AV0K1_RV0MRC02_WW_GEN1 and older)
A1-830
Download
myKIT_BATCHv1.1.2.7z available at http://forum.xda-developers.com/showthread.php?t=2681783
myKIT_BATCHv1.1.2d_PATCHKIT.7z at http://forum.xda-developers.com/showthread.php?t=2681783
INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z at http://forum.xda-developers.com/showpost.php?p=51090059&postcount=3
SuperSU zip UPDATE at http://download.chainfire.eu/supersu
Procedure
Copy SuperSU UPDATE ZIP on your Device
Make sure you properly installed USB Driver and enable USB Debugging on your Tab
Unzip myKIT_BATCHv1.1.2.7z and move myKIT_BATCHv1.1.2d_PATCHKIT.7z & INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z in the mykit-downloads directory
Start run-me.bat and type ACCEPT, press Enter. The toolkit is upgraded to 1.1.2d.
Close it, plug your Tab with USB Cable and start run-me.bat again
Type ACCEPT, press enter, type "2", press enter,
Your tab should prompt if you want to authorize debugging, choose Yes/Allow
On your deskop, the script should auto detect the Tab like this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Type A2, press enter, type 1 for INTEL_TRIAL_TETHERED_CWM_PKGKIT and press enter
Type ACCEPT, press enter
The @social-design-concepts scripts will now reboot your tab into Bootloader mode and start the exploit
If the Exploit is OK, CWM will boot on your tab :
You can now use Vol+ and Vol- to navigate, and press Power to validate
Go to "install zip", "choose zip from sdcard", "0"/, and select your UPDATE Super ZIP
Flash it ! Go back to the main menu and reboot your device
Your tab is now rooted, enjoy
Guide 2 - Boot Tethered CWM
Compatible with
A1-840FHD (firmware 1.057_AV0K1_RV0TRC01_WW_GEN1 or more recent)
A1-840 (HD)
B1-810 [confirmed by @alexys77]
A1-850 [confirmed by @Darrian]
A1-860 [confirmed by @edotcom]
Download
IntelAndroid-FBRL.7z available at http://forum.xda-developers.com/showpost.php?p=57505512&postcount=2375 thx to @social-design-concepts
SuperSU zip UPDATE at http://download.chainfire.eu/supersu
Procedure
Copy SuperSU UPDATE ZIP on your Device
Make sure you properly installed USB Driver and enable USB Debugging on your Tab
Unzip IntelAndroid-FBRL.7z
Plug your Tab with USB Cable and start launcher.bat
Your tab should prompt if you want to authorize debugging, choose Yes/Allow
Type ACCEPT ont the cmd screen, press enter
On your deskop, the script should auto detect the Tab like this (device status online + color blue) :
Type "T3", press enter
Note: if the T3 exploit doesn't work on your device, you can try T2 or T1
The @social-design-concepts scripts will now reboot your tab into Bootloader mode and start the exploit
If the Exploit is OK, CWM will boot on your tab :
/!\ Please note that the tethered CWM has just boot, it has not be flashed, we can't flash a custom recovery while our bootloader are locked. /!\
You can now use Vol+ and Vol- to navigate, and press Power to validate
Go to "install zip", "choose zip from sdcard", "0"/, and select your UPDATE Super ZIP
Flash it ! Go back to the main menu and reboot your device
Your tab is now rooted, enjoy
Guide 3 - Boot Tethered CWM or TWRP
Compatible with
B1-820 (LP 5.0)
A3-A30 (LP 5.0.2) confirmed by @paugustin
Procedure
Follow all steps described by @social-design-concepts on his updated thread :
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Advice/FAQ for Acer Tab Device : :
You should use the CWM recovery and the T4 exploit
TWRP boots, but no touch available
CWM runs fine, but cannot mount internal storage or /data, you MUST use an external SDCard
Flashing SuperSU and Installing Xposed Framework for LP is working great on B1-820 !
Guide 4 - Flash CWM Recovery (permanent)
vache said:
CWM for A1-840 FHD (only) based on Dell Venue 8 one. (http://forum.xda-developers.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925)
Tested successfully.
ADB_Fastboot.zip for Intel Devices (use this to flash)
CWM-v6.0.3.7_A1-840FHD.img.zip
stock_recovery.zip
To flash it :
Code:
fastboot flash recovery CWM-v6.0.3.7_A1-840FHD.img
Then use droidboot menu to reboot in recovery.
Click to expand...
Click to collapse
Thx @vache & @vampirefo
Firmwares
Flashable via (stock) Recovery
A1-830
SDs_Acer_AV0K0_A1-830_1.007.00_WW_GEN1.zip
SDs Acer_AV0K0_A1-830_RV01RC02_WW_GEN1.zip
SDs_Acer_AV0K0_A1-830_RV01RC05_WW_GEN1.zip
A1-840
SDs_Acer_A1-840_AV0K1.RV00RC00_AV0K1.RV0ERC02_WW_GEN1
SDs_Acer_A1-840_AV0K1.RV00RC00_AV0K1.RV0LRC01_GC_GEN1
SDs_Acer_AV0K1_A1-840_RV0XRC02_WW_GEN1.zip
SDs_Acer_AV0K1_A1-840_RV0ZRC03_WW_GEN1.zip
A1-840FHD
SD_Acer_A1-840FHD_AV0K1.RV00RC00_AV0K1.RV0BRC01_WW_GEN1.zip
SD_Acer_A1-840FHD_AV0K1.RV00RC00_AV0K1.RV0MRC02_WW_GEN1.zip
SDs_Acer_AV0K1_A1-840FHD_RV0TRC01_WW_GEN1.zip
B1-810
SDs Acer_AV0K0_B1-810_RV02RC03_WW_GEN1.zip
SDs_Acer_AV0K0_B1-810_RV02RC04_WW_GEN1.zip
A1-850
SDs Acer_AV0K0_A1-850_RV00RC01_WW_GEN1.zip
Thanks a lot. Successfully rooted my tablet.
One question. After rooting I rebooted into recovery. The stock recovery booted up. Is there a way to keep the CWM recovery flashed during the rooting process?
stari_alca said:
Thanks a lot. Successfully rooted my tablet.
One question. After rooting I rebooted into recovery. The stock recovery booted up. Is there a way to keep the CWM recovery flashed during the rooting process?
Click to expand...
Click to collapse
We can't flash it for now
This exploit only can boot it
We need to unlock the tab to be able to flash something
Envoyé de mon A1-840FHD en utilisant Tapatalk
Great Guide!
Unfortunately it doesn't work with the very similar A1-840HD:
http://forum.xda-developers.com/showpost.php?p=56580827&postcount=2158
Hi there,
How did you guys manage to install the MTP device drivers (the one that pops up in Device Manager when you enable the USB debbugging)? I´m on a Windows 7 (32 bits) and the folder we are instructed to download and unzip apparently does not contain the required files/driver.
Any help is appreciated as I can´t manage to pass that initial point.
Thanks in advance,
Mix
EDIT: I eventually got it to install correctly by using the USB Driver package from Acer:
http://global-download.acer.com/GDF...ep3=A1-840FHD&OS=ALL&LC=en&BC=ACER&SC=EMEA_27
I used the option in the toolkit which installs the drivers. If I remember correctly once you run the .bat file and ACCEPT you are given this option. I used 32 bit version of Win 7 as well.
Sent from my A1-840FHD using XDA Free mobile app
Works on A1 830
I just got the Acer Iconia A1-840FHD from a BestBuy and I want root access.
PLEASE somebody find out how!
I am hoping to get Linux up and running to run WINE on it since it is x86 architecture from being Intel.
Edit:Why did they make the name so similar?
I have the "rootable" FHD and yet there is an HD as well.
I hope rooting still works.
Then again,according to the manufacturing date,they have barely been out.
retroben said:
I just got the Acer Iconia A1-840FHD from a BestBuy and I want root access.
PLEASE somebody find out how!
I am hoping to get Linux up and running to run WINE on it since it is x86 architecture from being Intel.
Edit:Why did they make the name so similar?
I have the "rootable" FHD and yet there is an HD as well.
I hope rooting still works.
Then again,according to the manufacturing date,they have barely been out.
Click to expand...
Click to collapse
Did you try this guide?
I'm not sure I understand your post and what you want to do.
My product and safety information booklet says FHD on it despite mine only having 1GB of RAM.
Is there a root method working on the A1-840HD?
I may try Kingo since they still get updates and just added an exploit for Nexus Android 4.4.4 as well.
I hope it has support for this device.
Is there any way to step back and put everything as it was without root?
For any reason if we need to send the device to the warranty, this should be like original system state.
borisgregoris said:
Is there any way to step back and put everything as it was without root?
For any reason if we need to send the device to the warranty, this should be like original system state.
Click to expand...
Click to collapse
Well... I don`t have this tablet but think of buying one and I think that this could be done.
CWM has backup feature so I think that you could try backup current ROM and after you did that then root your device and if the problem pops you load CWM again and then restore original state.
If you already rooted then I think that someone that hasn`t rooted the device could make backup of ROM and upload it somewhere on the Internet.
Here is a full UPDATE zip ROM for A1-840 only (not compatible with A1-840FHD), flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Many thanks Shreps.
My image is Acer_AV0K1_A1-840FHD_RV0MRC02_WW_GEN1
Your image have "RV0ERC02" instead "RV0MRC02". Is this a problem?
borisgregoris said:
Many thanks Shreps.
My image is Acer_AV0K1_A1-840FHD_RV0MRC02_WW_GEN1
Your image have "RV0ERC02" instead "RV0MRC02". Is this a problem?
Click to expand...
Click to collapse
It means that my image is older than yours (which make sense, it's not the latest firmware)
But I think you can get some file from it and make your tab working fine again.
If it doesn't work, you can try to full flash the update zip to "downgrade" to a stable version (and then, you should get some OTA updates to get back to the latest version)
Here is some OTA manual download if needed :
Code:
WW_GEN1 AV0K1_RV0MRC02_AV0K1_RV0TRC01 227,47MB http://global-download.acer.com/GDFiles/Application/OTA/635537141647405935_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0MRC02_AV0K1_RV0RRC02 227,33MB http://global-download.acer.com/GDFiles/Application/OTA/635526789434977662_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0BRC01_AV0K1_RV0MRC02 45,86MB http://global-download.acer.com/GDFiles/Application/OTA/635490499381942196_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV09RC01_AV0K1_RV0MRC02 49,69MB http://global-download.acer.com/GDFiles/Application/OTA/635469761667577586_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV0JRC02_AV0K1_RV0MRC02 42,13MB http://global-download.acer.com/GDFiles/Application/OTA/635469757626803549_OTA_Acer_1.0_AV0K1_A.zip
WW_GEN1 AV0K1_RV08RC01_AV0K1_RV09RC01 37,53MB http://global-download.acer.com/GDFiles/Application/OTA/635402969903280635_OTA_Acer_1.0_AV0K1_A.zip
Enjoy
Hi, thanks for the image. Custom recovery fails for me:
assert failed: getprop("ro.product.model") == "A1-840"
Error in /cache/sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
I tried to find some solution, removed the assert line from the updater script and then custom recovery failed the flash because it couldn't verify whole-file signature. I assume the reason for this is because I modified the updater script within update.zip.
Should the assert line specify "A1-840FHD" as the model? Is this why the first error happens?
I'm trying to flash stock and unroot because, sadly, I think I need to send the device back. Having lots of trouble with the touchscreen.
Shreps said:
Here is a full UPDATE zip ROM, flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840FHD/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Click to expand...
Click to collapse
Shreps said:
Here is a full UPDATE zip ROM, flashable via stock Recovery in case something get wrong with /system
http://mon-nuage.net/A1-840FHD/
Check if you're on a WW_GEN1 or GC_GEN1 Region.
cc @borisgregoris @social-design-concepts
Click to expand...
Click to collapse
stari_alca said:
Hi, thanks for the image. Custom recovery fails for me:
I tried to find some solution, removed the assert line from the updater script and then custom recovery failed the flash because it couldn't verify whole-file signature. I assume the reason for this is because I modified the updater script within update.zip.
Should the assert line specify "A1-840FHD" as the model? Is this why the first error happens?
I'm trying to flash stock and unroot because, sadly, I think I need to send the device back. Having lots of trouble with the touchscreen.
Click to expand...
Click to collapse
Hi, same error here.
After flashing in stock recovery give me the assert failed error.
Its secure to flash the OTA files? I'm curious if they send me the same error that the update.zip. I'm afraid to brick the tab .
You're right guys
I didn't tried thoses firmware ZIP and it seems it's for A1-840 (HD) and not for A1-840FHD...
So, I will move the download link (rename the folder).
Sorry for the inconvenience
but, @borisgregoris you can still try to push file that are missing for your camera issue.
I will try to upload a full "/system" pull of my tab this weekend, this will not be flashable, but you will have all system files from my A1-840FHD.
Shreps said:
You're right guys
I didn't tried thoses firmware ZIP and it seems it's for A1-840 (HD) and not for A1-840FHD...
So, I will move the download link (rename the folder).
Sorry for the inconvenience
but, @borisgregoris you can still try to push file that are missing for your camera issue.
I will try to upload a full "/system" pull of my tab this weekend, this will not be flashable, but you will have all system files from my A1-840FHD.
Click to expand...
Click to collapse
I've already copy the missing files to my \system but only in the \app folder. Unfortunately still without camera.
I'm afraid to make things worse.
I don't know if it's secure to make a copy of all your \system structure (without overwriting my files and copying only the missing ones).
borisgregoris said:
I've already copy the missing files to my \system but only in the \app folder. Unfortunately still without camera.
I'm afraid to make things worse.
I don't know if it's secure to make a copy of all your \system structure (without overwriting my files and copying only the missing ones).
Click to expand...
Click to collapse
You should also set the right permissions and owner to the files like other file in the same directory.
Envoyé de mon One+
AnandMore's How-To Guide For Beginners
Xiaomi Redmi 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Intro:
This thread will serve as a location for basic how-to guides for the Xiaomi Redmi 2. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index:
Post #1 - Rooting your Redmi 2
Post #2 - Flashing Custom Recovery
Post #3 - Flashing Custom ROMs
Post #4 - Flashing Custom Kernels
Resources:
Everything you need for Xiaomi Redmi 2 is available in the below given thread -
[INDEX] Xiaomi Redmi 2
Rooting your Redmi 2:
This guide will root your device through Stock MI Recovery(Works with TWRP also), but this is not Native Root. A new app named SuperSU will be installed, which will give root Permission.
Note:
Rooting does not Void Warranty.
Caution:
This is a safe process, but I am not responsible for anything bad that happens to your phone.
In most cases this approach of rooting should not block OTA updates.
Steps to follow for rooting:
Download the Root.zip and Copy the file to the folder 'Internal storage' (root of internal storage).
(File at the end of thread)
Open the Updater app, Press the 3 dots at Right Top Corner, A menu will open. Tap on “Choose Update Package“ and select the Root.zip File.
Wait until device will reboot.
After reboot a new app SuperSu will be installed.
Open the app and Choose "Continue".
Choose "Normal", Don't Choose TWRP/CWM, device will go into Boot Loop.
Note - Don't Choose TWRP/CWM, it will brick your device.
After sucessful updation , press ok.
Your Phone has now Root Permission.
Open any app using Root permission and SuperSU will ask for Permission.
Enjoy your rooted Redmi 2.
Un Root The Device:
For Un Root , open the SuperSU app,tap on Settings, Choose Full Unroot.
Your Device is Un Rooted Sucessfully. The SuperSU app will be removed.
Flashing Custom Recovery:
From Mobile:
Install Flashify app from Playstore
Once installed, access the application through app drawer.
Allow root access now and get navigate to Flashify’s home screen.
First take a backup of your recovery in case something goes wrong. (RECOMMENDED)
Now tap on recovery image and by "Choose the file" menu locate the .img file you want to flash.
After successful flashing it will ask you to reboot your device.
Done! You have custom recovery on your phone.
From PC:
Enable USB debugging, go to settings>about phone and then tap on Android/MIUI version 5 times. Developer Options will be enabled. Now go back to settings>Developer options and enable USB debugging.
ADB and Fastboot Drivers installed on your PC. I can provide you the drivers but it would be a better option to install MiFlash to get all the necessary drivers and Miflash software with you for future use.
Install Miflash on your PC. Lets suppose we installed it in C:\Xiaomi folder.
You can see two folders, proceed to "adb' folder
Then proceed to "Google" folder.
Proceed to "Android" Folder.
We are at our destination.
Now Hold down "Shift" button on your computer keyboard and right click with mouse on an empty part of the window. You will see that in the menu that appears, you have an option - "open command window here". Click on that
To verify if ADB is working and installed correctly, type "adb version" in the command window that opened without the code. You should get the adb version which means its working fine.
Turn off your Phone. When its completely switched off, press and hold "Volume Down" and "Power" button together and then the phone will turn on in Fastboot mode.
Use the USB cable to connect Phone to PC.
Copy the Recovery.img in the Android folder where we are running the Command prompt. (C:\Xiaomi\adb\Google\Android in my case as i installed Mi flash in C:\Xiaomi folder)
Now go back to command promt and enter the following commands -
Code:
fastboot devices
Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command to flash recovery image -
Code:
fastboot flash recovery recovery.img
Once you enter this command, the recovery image will be flashed on your device. Once it is completed, enter the final command to reboot your phone -
Code:
fastboot reboot
Your phone will reboot.
You have have now completed flashing custom recovery replacing Stock Mi recovery on your Xiaomi Redmi 2.
Flashing custom ROMs:
Steps to Follow:
Download and transfer the custom ROM you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
Select “Wipe” from TWRP main menu and do a “Swipe to Factory Reset” on the bottom of screen.
Note: This will factory reset your device. If your custom ROM doesn’t require a factory reset, then simply skip this step.
Go back to TWRP main menu, tap on “Install” and select the custom ROMs .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom ROM installation process. This may take some time.
Once your ROM is successfully flashed, you’ll see “Wipe cache/dalvik” option, select it and then do “Swipe to wipe” on bottom of screen.
Once cache & dalvik wipe completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom ROM you just flashed. Since this will be the first reboot after flashing a new ROM, it might take some time to rebuild cache and finish boot, have patience.
Flashing Custom Kernels:
Steps to Follow:
Download and transfer the custom Kernel you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
In the TWRP main menu, tap on “Install” and select the custom Kernel .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom Kernel installation process. This may take some time.
Once flashing completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom Kernel you just flashed. Since this will be the first reboot after flashing a new Kernel, it might take some time to rebuild cache and finish boot, have patience.
For list of all available Roms visit this thread :
http://forum.xda-developers.com/redmi-2/how-to/available-custom-marshmallow-roms-redmi-t3278535
Click to expand...
Click to collapse
Better if you make lollipop ROMs thread too
Superb work bro thanks ...u
Isn't MIUI rooted out of the box already? [emoji52]
Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
Developer ROMs are. Global ROMs aren't.
Device comes with global ROM :3
noobpremium said:
Better if you make lollipop ROMs thread too
Click to expand...
Click to collapse
I made both lollipop and marshmallow roms in one thread. So you think i should make seperate one for lollipop.
Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
All roms(Beta,developer,stable) for Redmi 2 are not Pre rooted.
Added videos tutorials for better understanding.
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
my phone also rebooting. please help me. how to go to recovery?
srmohanrajan said:
my phone also rebooting. please help me. how to go to recovery?
Click to expand...
Click to collapse
1) Switch off the phone.
2) Press the Volume Down, Volume Up and the Power Button at the same time, about 2-3 seconds until the mi logo shows up.
3) Recovery mode menu will appear.
Fr3ak23 said:
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
Click to expand...
Click to collapse
Follow the same steps to boot into recovery and flash SuperSU v2.4.6 zip via recovery
(And remember you are responsible if anything happens to the device)
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Fr3ak23 said:
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Click to expand...
Click to collapse
No problem bro !
✌
Great !
New CM 12.1 is awesome, finally the camera works
I am curious on why I keep on losing root access. I never had that issue with any other phones and custom ROMs.