DO NOT USE THIS UTILITY ON THE LATEST 4.1.2 OTA UPDATE.
{
"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"
}
This is ONLY for the DROID RAZR M XT907. Do NOT use this on an XT905!
DROID RAZR M Utility 1.20
Use a Download Manager such as "Orbit Download Manager" for best downloading results.
Mirrors:
Dev-Host
Batakang
Filesize: 595 MB (624,299,179 bytes)
MD5: 4867E801B70FCB54A33A1B7EC47BA6A6
- Windows Instructions
Extract .zip to its own folder on the Desktop.
Install the required drivers. The folder with the drivers is called "Drivers [WINDOWS ONLY]" and is included in the Utility folder.
Double click the ".bat" file. This will be called "WindowsUtility.bat" the image is just for reference.
- Mac & Linux Instructions
Extract the .zip to any folder you like, the /Downloads/ or /Desktop/ folder should work just fine.
Open a Terminal window. (On Mac: Applications > Utilities > Terminal)
Learn your 'sudo' password. This is almost always your Admin password on a Mac computer. On Linux you should already know what this is, its yours account password if your account is an admin as well.
Type the following code into the Terminal Windows, places where it says ***DRAG HERE*** are telling you to simply drag the folder there. For example: cd ***DRAG FOLDER HERE*** then press 'Enter' after each line.
Code:
cd ***DRAG UNZIPPED UTILITY FOLDER HERE***
chmod +x ./LinuxMacUtility.sh
bash ./LinuxMacUtility.sh
You will be asked for your sudo password at least once in the Utility process, so make sure you followed the instructions to learn it.
Functions of the DROID RAZR M Utility 1.20:
*These are not to be done in numerical order. Options 3,4, and 6 require Root Access.
Code:
1 Flash 4.1.2 Stock System, Kernel, and Radio (Data Wipe) [from AP Fastboot]
2 Flash 4.1.2 Stock Recovery [from AP Fastboot]
3 Flash TWRP 2.323 Custom Recovery by Hashcode - UNLOCKED BL REQUIRED [from Normal Boot]
4 Flash CWM Custom Recovery by Hashcode - UNLOCKED BL REQUIRED [from Normal Boot]
5 Motochopper Root Exploit by Dan Rosenberg [from Normal Boot]
6 Unlock Bootloader (Install Motopocalypse App) [from Normal Boot]
Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP Recovery by Hashcode.
Number 4 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM Recovery by Hashcode.
Number 5 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled.
Number 6 Explained -- This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters.
Thanks to Hashcode for CWM and TWRP. Thanks to Djrbliss for Motochopper and Motopocalypse!
Thanx a lot for the update. Please, tell where did you get stock images of 4.1.2 for Verizon Droid RAZR M. As i know sbf or xml is not released yet.
da900 said:
Thanx a lot for the update. Please, tell where did you get stock images of 4.1.2 for Verizon Droid RAZR. As i know sbf or xml is not released yet.
Click to expand...
Click to collapse
It will be on http://sbf.droid-developers.org/ soon enough. I don't need to share my sources, and doing so would ensure I couldn't get them early for you folks anymore who need them
Why not include TWRP 2.4?
scottocs said:
Why not include TWRP 2.4?
Click to expand...
Click to collapse
Many users on DroidRzr reported bugs on 2.4 and not on 2.323. When 2.5 launches I will update this tool
Sent from my Galaxy Nexus using Tapatalk 2
mattlgroff said:
Many users on DroidRzr reported bugs on 2.4 and not on 2.323. When 2.5 launches I will update this tool
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Seems as though it has been released.
http://teamw.in/project/twrp2
Well, maybe not for this particular device. I may have spoken too quickly.
scottocs said:
Seems as though it has been released.
http://teamw.in/project/twrp2
Well, maybe not for this particular device. I may have spoken too quickly.
Click to expand...
Click to collapse
Yup. It wasn't out last night, anyway. Hashcode is the one to watch for release rather than officially.
Sent from my Galaxy Nexus using Tapatalk 2
How long should the "sending system" step take? It's the first one when I try to flash 4.1.2 and it's taking a really long time
i'm using the this on a mac and i'm getting a couple of error messages, I was wondering if someone could point me in the right direction of fixing things.
I get this error when after i enter the commands listed to start the app:
32 bit Mac System
chmod: ./fastboot.osx32: No such file or directory
I select option 1 and this error comes up
sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found
sudo: fastboot: command not found
i'm running this on a macbook w/ a C2D. that first error makes me think this might be meant for a newer Mac. Thanks in advance guys
Your directory doesn't exist where it's expected - you sure you're running it from the right place?
Sent from my XT907 on CM10 using Tapatalk 2
I'm just getting "sending system" hanging forever...I tried flashing 4.1.2 stock recovery too and same thing "sending recovery"
Does the rom selected on safestrap matter? I wouldn't think so
Not sure what's going on
Dyelon said:
I'm just getting "sending system" hanging forever...I tried flashing 4.1.2 stock recovery too and same thing "sending recovery"
Does the rom selected on safestrap matter? I wouldn't think so
Not sure what's going on
Click to expand...
Click to collapse
Need 2GB+ RAM free and not using USB 3.0 ports.
Sent from my Galaxy Nexus using Tapatalk 2
delete this
---------- Post added at 04:12 PM ---------- Previous post was at 03:40 PM ----------
Dyelon said:
delete this
Click to expand...
Click to collapse
thanks so much dude...I finally got it to work. I have a lot of android devices and I was using a different micro usb cable. Sorry about that.
you're the man!
only question I have now is...when booting the phone, safestrap isn't coming up anymore. does that mean the partition it created is wiped as well as the space it was taking up replenished to the stock ROM?
thanks again man
I tried following the instructions and this is all I get. phone was in AP Fast boot, I'm just trying to flash TWRP
ktracho13 said:
I tried following the instructions and this is all I get. phone was in AP Fast boot, I'm just trying to flash TWRP
Click to expand...
Click to collapse
Choose 3: TWRP...
Sent from my GT-P3113 on CM10.1 using Tapatalk HD
sloosecannon said:
Choose 3: TWRP...
Sent from my GT-P3113 on CM10.1 using Tapatalk HD
Click to expand...
Click to collapse
I did and it does nothing
ktracho13 said:
I did and it does nothing
Click to expand...
Click to collapse
Isn't option 3 done in normal boot not fastboot?
Sent from my XT907 using xda premium
---------- Post added at 01:03 PM ---------- Previous post was at 01:00 PM ----------
ktracho13 said:
I tried following the instructions and this is all I get. phone was in AP Fast boot, I'm just trying to flash TWRP
Click to expand...
Click to collapse
Yeah use normal boot with USB debugging enabled. Not fastboot
Sent from my XT907 using xda premium
Erisnoob said:
Isn't option 3 done in normal boot not fastboot?
Sent from my XT907 using xda premium
---------- Post added at 01:03 PM ---------- Previous post was at 01:00 PM ----------
Yeah use normal boot with USB debugging enabled. Not fastboot
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
thanks for the help I managed to flash TWRP is it normal the whenever I plug the phone to the computer it immediately reboots into TRWP ?
oh and before rebooting it says "AdB shell has been granted permission"
Will either Option 1 or 2 allow me to update to 4.1.2 without wiping my data? Id like to update, but OTA require i put all the bloatware back. Id like to just flash 4.1.2 without having to redo my phone.
It's a data wipe. You could flash just the radio, boot image etc... Those are extracted and available on another forum. Or you could reinstall the bloat as system apps.
Related
I don't think anyone has posted a tutorial for this on XDA yet (apologies if they have!!!) and the Google Translate of Mur4ik's original instructions on 4PDA is pretty poor so here's what I did to get my phone set up.
What does this do?
This process flashes a modified KDZ which will change the way your phone's memory is partitioned. The result will be that you have 234mb of internal storage for your apps, 150mb for the system and 64mb for cache.
According to Mur4ik, this is the optimum allocation of memory for best performance.
Once this process has been done, any ROM that you flash will have more internal storage space without any further modification. You should not flash a data2system rom.
With this method you will still be able to apply update.zip files with recovery (like Mur4ik's rom updates). This feature does not work on data2system roms.
Things you'll need:
1) KDZ Updater
2) Mur4ik's modified KDZ (MD5SUM: e582d471ed9aede3dd9279b20f7a948c)
Assumptions:
1) You know how to back up your ROM
2) You have access to a Windows PC with drivers installed for your phone
First of all you should back up your current ROM with recovery.
OK, let's get started:
Turn the phone off, remove the battery, SIM & SD Card.
While holding Volume-Down, connect the phone to your PC and run KDZ Updater. The phone display will show "Download Mode".
Select "CS_Emergency" Phonemode in KDZ Updater and select the "20E 234 150 64.kdz" KDZ file downloaded above. Then click "Launch software update"
{
"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"
}
The update will now start. During the update the phone screen will display "Download Mode" and eventually an animation of the battery cover being replaced. At this point you can disconnect the phone and replace your SIM, SD Card and battery *
Put your phone into fastboot mode (hold Camera and press Power) - the fastboot screen will now be BLUE and have white text displayed on it (this is correct).
Connect to your PC and in a terminal type:
Code:
fastboot erase system
fastboot erase userdata
fastboot erase cache
flash recovery back on to your phone
Code:
fastboot flash recovery recovery.img
Boot your phone into fastboot or recovery
Your phone is now ready to go and you can either restore a backup with recovery or flash a ROM with fastboot. You must be sure that your backup or fastboot images do not exceed the sizes stated above. So, your system.img must not be larger than 150mb, your data.img must not be larger than 234mb and your cache.img no larger than 64mb.
Note: If you were already using a data2system rom and want to restore your backup after carrying out this process then you must do the following in the backup's folder on your sdcard:
- replace your boot.img with one from a standard version of your rom (i.e. non-data2system)
- rename your "data.img" to "system.img" and your "system.img" to "data.img"
- delete the file "nandroid.md5"
- open an adb shell (or run terminal on your phone) and type "su" <enter>, "cd" to the backup folder, type "md5sum *.img > nandroid.md5" <enter>
- you can then restore the backup with recovery.
How to restore your phone to standard memory allocation?
Follow the steps above but use any standard fastboot enabled kdz (like this one). Then flash your rom or restore your backup - just remember you now have a smaller data partition
Special thanks to Mur4ik, EazyLuke & M1st3r1
You do of course follow these instructons at your own risk. Have fun!
*For me, the update process continued successfully beyond this point but some people have reported errors after the animation appeared so it is safer to remove the USB cable here.
many thanks for your tutorial!
What are the advantages compared to d2sys of lavero.burgos with anton_ch metod?
desmail said:
many thanks for your tutorial!
What are the advantages compared to d2sys of lavero.burgos with anton_ch metod?
Click to expand...
Click to collapse
This method means you can flash any custom rom and it will be data2system automatically instead of having to wait for someone to convert it. Plus you can use your existing backups.
Sent from my GT540 using XDA Premium App
Should not the type of phone in KDZ Updater be 3GQCT instead of CDMA which is what is shown in your picture? Just a thought incase it bricks anyones phone
gizmo001i said:
Should not the type of phone in KDZ Updater be 3GQCT instead of CDMA which is what is shown in your picture? Just a thought incase it bricks anyones phone
Click to expand...
Click to collapse
No. That's not important in CS_EMERGENCY mode.
Sent from my GT540 using XDA Premium App
OK my bad
OK, I have a bit of a problem. The KDZ Update has stopped and my phone has come up with a load of writing which says
[Blue Error Handler] Arm11 is crashed
[Press Volume Up Key] Rebbot&Savelog
[Press Volume Down
Linux Kernel Panic
Process init 9pid: 1)
followed by a load of codes. Does anyone have any ideas?
gizmo001i said:
OK, I have a bit of a problem. The KDZ Update has stopped and my phone has come up with a load of writing which says
[Blue Error Handler] Arm11 is crashed
[Press Volume Up Key] Rebbot&Savelog
[Press Volume Down
Linux Kernel Panic
Process init 9pid: 1)
followed by a load of codes. Does anyone have any ideas?
Click to expand...
Click to collapse
Did the kdz update say "finished"? Or did it hang before then?
Sent from my GT540 using XDA Premium App
It hung before finishing
gizmo001i said:
It hung before finishing
Click to expand...
Click to collapse
Repeat the process from step 1.
Sent from my GT540 using XDA Premium App
til the same, it crashes a step 212. Going to download original KDZ and try that
I think it's fine if it stops at 212, as far as I remember mine stopped also at 212.
Do you do the process without the battery? (you should)
And at some point the phone shows an animation that tells to put the battery back in. I think at this point it's finished.
Try downloading the kdz from this mirror:
http://narod.yandex.ru/disk/10706845001/20E_234-150-64.kdz
@eazyluke My guide looks ok to you?
Sent from my GT540 using XDA Premium App
This happened to me as well. I fixed it by putting sim, sdcard and battery back-in.
Then re-booted to fastboot using camera button + inserting usb cable. Fastboot came up with blue screen.
Then I ran in cmd
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot flash recovery recovery.img
rebooted to fastboot again
then flashed M4 using fastboot and then rebooted and I got my phone back.
Phone showed 234mb of storage free on re-boot
If this behaviour is confirmed then I'll add it to the guide. Mine flashed without error...
Sent from my GT540 using XDA Premium App
Mine didn't show any error, the process just didn't continue at some point, I think at 212. But everything is fine.
ive said that behavior clearly in my slightly-changed-translated from 4pda..
it's here: http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
m1st3r1 said:
ive said that behavior clearly in my slightly-changed-translated from 4pda..
it's here: http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
Click to expand...
Click to collapse
I see but mine went all the way through & said "finished" like it should. So that can happen too.
Sent from my GT540 using XDA Premium App
re-downloaded the kdz file and it all went well this time, so the file must have got mucked up a little during download. Either that or it those pesky LG gremlins playing about again. Thanks for everyones help though. I did have a little wobble of a panic for a while there lol.
gizmo001i said:
re-downloaded the kdz file and it all went well this time, so the file must have got mucked up a little during download. Either that or it those pesky LG gremlins playing about again. Thanks for everyones help though. I did have a little wobble of a panic for a while there lol.
Click to expand...
Click to collapse
Glad iit worked for you.
Sent from my GT540 using XDA Premium App
BIG THANKS TO MUR4IK FOR THIS TOOL! Be sure to donate to him and support his work!
Cannot get the builder to run or use Linux/Mac? Solution here!
In this guide I will be showing you how to resize your data + system partitions for more/less space.
Things you will need:
LG GT540 w/ A Fastboot ROM installed
LG drivers and Fastboot/ADB drivers installed
Windows (with .NET Framework 3.5 SP1 installed. If you have trouble launching the program, (re)install .NET 3.5 SP1. Also this tool will not work with Wine on Linux.)
Your phones USB cable.
WARNING: MAKE SURE TO NANDROID BACKUP YOUR ROM BEFORE CHANGING THE PARTITION SIZES! YOU MAY NEED IT LATER. ALSO, THIS TOOL DOES NOT REMOVE RECOVERY.
First of all, grab the SwiftBootloaderBuilder.zip from http://kulkoff.com/swift/ or from here.
(Mur4ik's site is recommended)
Next, put your phone into Fastboot Mode (Camera+Power)
Extract the files to your Desktop using any archiving program. Then go to the folder you extracted. Right Click and Select 'Run as Administrator'
{
"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"
}
You will see a window like this pop up:
Now we can alter the partition sizes. If you want the same effects as Mur4ik's 234MB DATA KDZ, choose 150MB system, and the data column will change accordingly. If you want a bit more system space (eg. To run airbus360's LG Optimus One ROM) Select 190 system. Basically, adjust the settings to how you want. My recommendations are:
For SwiftDroid, joe.stone AOSP, airbus360 AOSP, EleganceSwift, MMXTREM 2.1 Lite, Quarx Black ROM: 150 system 234 data
For airbus360 Optimus One: 190 system 194 data
For stock 2.1: 250 system 134 data
Once you have decided on the size you want, hit 'Flash New Bootloader' and confirm you really want to do this. You will get a 'Done' message and then click OK. Select 'Wipe Data' and then Reboot Device. After you click reboot, hold down HOME until recovery pops up.
Now you have two choices. Either install a new ROM from scratch, or restore your nandroid backup you made earlier.
This tool also has the option to remove fastboot and recovery from the device, so you can return to stock firmware, and possibly use regular LG updates again.
Thats it!
If you've got any questions, PM me or reply to the thread.
Also, don't forget to say
if I helped!
Anyone with WinXP SP3 32-bit has got it working successfully?? I still can't make it work. Resizing, removing fastboot & recovery doesn't work for me.
not sure it works on 32bit. it was tested by mur4ik using a 64bit windows7 computer.
bs828 said:
not sure it works on 32bit. it was tested by mur4ik using a 64bit windows7 computer.
Click to expand...
Click to collapse
It works on 32bit Win7
Sent from my GT540 using XDA Premium App
Works perfectly for me on win7 32bit! thanks for making this!!!
tejasdj12 said:
Anyone with WinXP SP3 32-bit has got it working successfully?? I still can't make it work. Resizing, removing fastboot & recovery doesn't work for me.
Click to expand...
Click to collapse
I have only tried on Windows 7, but i'll try it on my netbook soon (that runs XP)
Working fine for me (XP SP3 w/ .NET 3.5 SP1) No issues at all, also partitions resize ok too.
Hi. Thats should be added in header that this "tool" has a requirements MS .NET frameworks 3.5 SP1 and adove.
Mur4ik,
Because this tool can save the bootloader instead of flashing it, would it work to save the bootloader using the tool in Wine, then flashing it with fastboot (maybe a solution for Linux users) What would the command be to flash this boot bootloader?
Thanks.
effortless. said:
Mur4ik,
Because this tool can save the bootloader instead of flashing it, would it work to save the bootloader using the tool in Wine, then flashing it with fastboot (maybe a solution for Linux users) What would the command be to flash this boot bootloader?
Thanks.
Click to expand...
Click to collapse
Code:
fastboot flash APPSBL your_file_filename.mbn
Mur4ik said:
Code:
fastboot flash APPSBL your_file_filename.mbn
Click to expand...
Click to collapse
Thanks, I will try later!
EDIT: Doesn't matter, .NET 3.5 SP1 wont install, also using Winetricks didn't help. But what I might do is, create a load of bootloader files (on my Windows machine) and then upload them, so users can flash w/ fastboot.
Anyone knows how to get fastboot on fresh stock ROM without that KDZ stuff? Coz I'd just bricked my phone (dead phone), but the LG people in India are too generous to fix it in two hours.
I won't take any risks with KDZ. But I'm missing Swiftdroid and other stuff. Please can someone tell how do I install fastboot somehow without using KDZ?
tejasdj12 said:
Anyone knows how to get fastboot on fresh stock ROM without that KDZ stuff? Coz I'd just bricked my phone (dead phone), but the LG people in India are too generous to fix it in two hours.
I won't take any risks with KDZ. But I'm missing Swiftdroid and other stuff. Please can someone tell how do I install fastboot somehow without using KDZ?
Click to expand...
Click to collapse
You could root your phone then use root explorer and copy the flash image file to the bin folder then run the command mur4ik posted in this thread but change fastboot to flash_image run the command in terminial that should work.
This is the command
su
flash_image APPSBL your_file_filename.mbn
Sent from my GT540 using XDA Premium App
eoghan2t7 said:
flash_image APPSBL your_file_filename.mbn
Click to expand...
Click to collapse
Which file should I flash? The one that's created by Swift Bootloader Builder? Will it enable fastboot? (ATM I don't have fastboot in my phone)
tejasdj12 said:
Anyone knows how to get fastboot on fresh stock ROM without that KDZ stuff? Coz I'd just bricked my phone (dead phone), but the LG people in India are too generous to fix it in two hours.
I won't take any risks with KDZ. But I'm missing Swiftdroid and other stuff. Please can someone tell how do I install fastboot somehow without using KDZ?
Click to expand...
Click to collapse
You might be able to flash it using flash_image. But either: flash_image may not be able to access the appsbl partition or it may not be able to be changed 'on the fly' so to speak. You can try this, not sure if it will work, root is needed, not sure if it will brick your phone, I have not tried this method.
Download either:
150 system 234 data
250 system 134 data
and also download flash_image from here
Put the .mbn and flash_image file on your SDCard.
Open a terminal emulator and type the following:
Code:
su (press allow when prompt comes up)
cd /sdcard/
chmod +x ./flash_image (if this doesn't work, try chmod +x flash_image)
./flash_image appsbl appsboot_150_234_64.mbn (or appsboot_250_134_64.mbn)
sync
Now try entering fastboot and flash recovery. In theory, it should work.
oh snap, Eoghan beat me to it
@eoghan and effortless.
Thanks for your help, I'll try that later.
EDIT: One doubt, I don't think it's possible to resize partitions while using them.
Lets hope it works, then once at 2.1, there is no need for KDZ anymore (sort of)
tejasdj12 said:
@eoghan and effortless.
Thanks for your help, I'll try that later.
EDIT: One doubt, I don't think it's possible to resize partitions while using them.
Click to expand...
Click to collapse
It will resize, as the partition table is only changed on boot (as far as I know)
Nope, it says "Can't find appsbl partition"
tejasdj12 said:
Nope, it says "Can't find appsbl partition"
Click to expand...
Click to collapse
It might be case sensitive, try APPSBL instead
NOTE: This procedure is only for Android 5.1. If you updated your phone to Android 6, please see post #404 for notes on how to root it properly! Special thanks to @LonePlykin for the 6.1 information in post #404!
Credits
- I did not come up with the procedure to root this phone - that work was done by member @hackvcs - I just put this guide together using the method that he developed (and using the custom recovery that he put together). Please give all credit to @hackvcs!!! Also, the links to the files below are not my links - they are links that other members provided (member who provided them is listed below).
Pre-requistes/Downloads:
- HTC Desire 626s phone
- Official TWRP Recovery Images: https://twrp.me/devices/htcdesire626s.html - Thanks @Captain_Throwback!
- Recovery images (custom CyanogenMod recovery and stock recovery image) - provided by @hackvcs (https://mega.nz/#!sp0wCThZ!MQVTq6y_8DJShrvNrY4L-JtJBDHOQhnaLRq8UiqLruQ)
- SuperSU binary .zip file - link provided by @mussio (https://download.chainfire.eu/696/SuperSU)
1. Unlock bootloader
- Enable "Unknown Sources" on your phone:
- Settings->Security: Check "Unknown Sources" checkbox- Enable "Developer Mode" and enable "USB Debugging" and "OEM Unlocking" settings
- Settings->About->Software Information->More: Tap on "Build Number" until it tells you that Developer Mode is enabled.
- Settings->Developer Options: Enable "OEM Unlocking" and "USB Debugging" options.- Actually unlock the bootloader by going to the HTCdev "Unlock Bootloader" website (www.htcdev.com/bootloader) and following the directions to unlock your bootloader. You will need to create an account on this website before being able to unlock the bootloader. I'm not going to provide step-by-step instructions for the bootloader unlock procedure since the HTCdev website already provides a step-by-step procedure. However, here are a few key notes regarding this procedure:
- The bootloader unlock procedure will reset your phone back to factory defaults. Make sure to backup anything that you need on the phone before unlocking the bootloader. You can optionally install the "HTC Sync Manager" (link provided on HTCdev website) to backup your phone before starting the process.
- In the "Select your device" box on the first screen of the bootloader unlock procedure, select "HTC Desire *" as the device type.
- If you are running the latest firmware on your phone, you do not need to worry about the phone update page when you first start the unlock process - just scroll to the bottom of the screen and click the "Proceed to Step 1" button to start the procedure.
- You will need to install Java if you don't already have it installed - there is a link to download Java right on the same page as the bootloader unlock procedure.
- You will need to download and install the fastboot binaries provided in step 4 of the bootloader unlock procedure. Unzip the fastboot.exe file included in the zip to a directory that you will use to root your HTC Desire 626s (I recommend creating a new directory for this - something like "C:\HTC626s") - later, you will also put the other files you need (recovery image file and SuperSU binary .zip file) into this same directory so that everything is in one place.
2. Install custom recovery
Once you have successfully unlocked your bootloader, you will need to flash a custom recovery (TWRP recommended). This recovery image will replace the stock recovery on your phone and allow to flash the SuperSU binaries in the next step.
- Connect your phone to the PC via USB cable and let the PC install the necessary drivers for the phone.
- Reboot the phone into "Download" mode:
- Power off phone
- While holding the Volume Down button, press the device Power button. Continue to hold the Volume Down button until the phone boots into "Download" mode. To confirm that the bootloader is unlocked and that you are in "Download" mode, you should see the following two lines at the top of the screen:
- "hTC download mode"
- "*** Unlocked ***"- Once you have confirmed that you are in download mode and the bootloader is unlocked, it's time to flash the custom recovery:
- Open a Command Prompt (aka DOS prompt) window and change to the directory where you put the fastboot.exe file. If using the recommended directory, you would type this command in the Command Prompt window to change to that directory:
- Type "cd \HTC626s" and press [ENTER]- Make sure that the recovery file is in the same directory (type "DIR" and press [ENTER] to see the files in the current directory). If it is not in the current directory, put it there before continuing (via Windows Explorer). Also, I'd recommend renaming the recovery image to "recovery.img" - it makes typing the commands a little easier and reduces the likleyhood of a typo. So before continuing, you should have both "fastboot.exe" and "recovery.img" in the current directory.
- In the command prompt window, type "fastboot flash recovery recovery.img" and press [ENTER] - this will flash the custom recovery to your device.
3. Install SuperSU superuser binaries
Now that we have the bootloader unlocked and the CyanogenMod recovery installed, we are set to flash the SuperSU binaries to actually root the device. Before continuing, make sure that you have copied the SuperSU binary .zip file to the internal storage on your phone! Once we boot into CyanogenMod, you will have to navigate to this .zip file in order to install it. It MUST be on the *internal* phone storage (not on the MicroSD card).
- Reboot your phone into recovery:
- Power off the phone
- Power on the phone while holding the "Volume Down" button. Keep holding "Volume Down" until the phone boots into Download mode.- Scroll down to "Reboot to bootloader" and press the power button.
- Once in bootloader mode, scroll down to "Boot to recovery mode" and press the power button. At this point, you should be in the CyanogenMod recovery menu.
- Scroll down to "Apply Update" and press the power button
- Scroll down to "Choose from internal storage" and press the power button
- Navigate to where you stored the SuperSU .zip file and select it - the SuperSU binaries will be installed on the phone.That should do it! You should now have a rooted HTC Desire 626s. Reboot the phone into Android and confirm that you have a SuperSU icon in your app drawer and then confirm that the device is actually rooted.
NOTES:
- Your phone MUST be in "Download" mode when flashing the custom recovery! You CANNOT install the recovery image when the phone is in "Bootloader" mode. If you receive this message: "remote: cannot flash this partition in s-on state", that means that you are trying to flash the recovery image while the phone is in "Bootloader" mode - you MUST be "Download" mode when flashing the recovery image!
- Bootloader MUST be unlocked before attempting to install a custom recovery. Verify that you bootloader is unlocked by checking for "*** Unlocked ***" text at top of the screen when the phone is in "Download" mode.
- After rooting, you can always revert back to the stock recovery if you'd like - the stock recovery image is provided in the same .zip file that contained the CyanogenMod recovery image (provided by @hackvcs).
Again, big thanks to @hackvcs for coming up with the custom recovery - which was the key to getting root on this device!
Great write up. Clear and concise. If you cannot root with this, you have not followed every step. I missed a step the first time. Figured it out and worked perfectly.
Sent from my HTC Desire 626s using XDA Free mobile app
Thank you so much for your time and effort to get this done. I bought the phone two weeks ago and have been running a search on Google of desire 626s root and filtered by results in last 24 hours just about every day haha. Now I just need to get to a computer. Thanks again!
Ipoke Smot said:
Great write up. Clear and concise. If you cannot root with this, you have not followed every step. I missed a step the first time. Figured it out and worked perfectly.
Sent from my HTC Desire 626s using XDA Free mobile app
Click to expand...
Click to collapse
HELP, says cant load recovery img. why????:crying::crying::crying::crying:
Make sure the recovery.img file is in your current directory (the directory where you type the fastboot command). Type "dir" and press [ENTER] to make sure it's in the same directory as the fastboot.exe file. Post a screenshot of the error and the dir command output.
Thanks for the post.. just a question.. will this work with an HTC Desire 626x ?????
Success
I was successful on HTC 626s on MetroPCS. Will we see a cyanogenmod build?
Sorry guys if my question is too remedial, but do I have to install the entire sdk to unlock the boot loader? I'm using a friends computer and it's a rather large download. I guess what I'm asking is, is there a certain component I can download to keep the install minimal? Or do I have to install the complete sdk?
talksickisil said:
Sorry guys if my question is too remedial, but do I have to install the entire sdk to unlock the boot loader? I'm using a friends computer and it's a rather large download. I guess what I'm asking is, is there a certain component I can download to keep the install minimal? Or do I have to install the complete sdk?
Click to expand...
Click to collapse
This will install the adb components you need. Also has an option for drivers if needed.
http://androidxda.com/download-best-android-adb-driver
Wow I'm so glad I asked! Thank you! Will try this later today. So I won't need the sdk?
talksickisil said:
Wow I'm so glad I asked! Thank you! Will try this later today. So I won't need the sdk?
Click to expand...
Click to collapse
No need to download SDK
http://forum.xda-developers.com/showthread.php?p=48915118
What is this?
This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in early 2013. I saw another ADB installer on XDA, but it wasn't good enough for me so i'm finaly posting it here. It's very small and fast installer for tools and drivers.
I think that all you really need for this process is the fastboot.exe that is available for download from the HTCdev site. I didn't use ADB at all to unlock the bootloader/root my phone - just fastboot.exe.
Thanks for the help guys! I'm back to report that the process was a success! I am rooted. Also just a heads up: stay away from xposed for now. Got stuck on the boot screen until my battery died after I installed it
wooooow, tanks bro, woks perfect, now I'm going to erase all the garbage of my carrier 'TELCEL'.
[Q] there is no problem if I keeping installed on the device the cyanogen recovery??...
saludos de Monterrey....
Help I can't load recovery
Sent from my SM-N910T
---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------
{
"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"
}
Sent from my SM-N910T
---------- Post added at 12:09 PM ---------- Previous post was at 12:01 PM ----------
jtrosky said:
I think that all you really need for this process is the fastboot.exe that is available for download from the HTCdev site. I didn't use ADB at all to unlock the bootloader/root my phone - just fastboot.exe.
Click to expand...
Click to collapse
Please help
Sent from my SM-N910T
Something is not night with your recovery.img - it's a directory instead of a file. I'm guessing that the actual recovery image in inside of the recovery.img directory....
Ok let me adjust
Sent from my SM-N910T
ubigred said:
Help I can't load recovery
Sent from my SM-N910T
---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------
Sent from my SM-N910T
---------- Post added at 12:09 PM ---------- Previous post was at 12:01 PM ----------
Please help
Sent from my SM-N910T
Click to expand...
Click to collapse
Bro, I think recovery.img is not in the same folder of fastboot.exe , I say that because I see in the print screen <DIR> recovery.img, that mean is in a folder... or recovery.img is a folder...
Thank you for help guys. I figured it out. I needed to rename the actual Cyanogen file to recovery.img.
I made the mistake of renaming the folder. I haven't rooted an HTC since the Evo. It clearly showed. Process took way too long. This is why I stick with Samsung phones.
Sent from my SM-N910T
Gps
Hey is he going to have problems with their GPS since using their phone I didn't at first but now I can't get a GPS lock for the life of me anyone have any ideas? Thank you
Halo all
Most owners here have rooted (kingroot) their system and attempted to update the rom, forgetting OTA conflicts. Although the consequences are usually resolvable, not in the case of mediatek and our model.
To start, I highly recommend using Ubuntu linux off a flash drive running live, else I suggest using windows 7 (perhaps in a vm too) although it didn't work with me (mediatek driver issues) (users reported that it works fine with windows 10, set wifi connection as metered to prevent automatic driver updates)
Optional: Create a live Ubuntu (download the 64bit version!) stick using this tut: http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
After booting into Ubuntu, remove modemmanager by typing in terminal : sudo apt-get remove modemmanager
Hit y and continue...
Download folder list:
1)spflashtool from http://spflashtool.com/, "Linux 64-bit"
2)CWM(626g+)
3)Scatter file(626g+)
4)Stock cwm backup ~800MB
Link to Download: me1ga.nz/#F!t1A1HJQJ (rename to "mega")
Decryption key:
Code:
!teT23YQ_1PH52USChW3k6g
Google drive mirror folder: https://drive.google.com/folder/d/0BwgllNFqdXuQMXR0a29mZms2VDA/edit
Skip 1,2,3 for Windows users
Flash time:
1)Extract the zip in Home directory, open Terminal again then cd SP_Flash_Tool_exe_Linux_v5.1520.00.100 (tip: type cd SP then hit tab to autocomplete)
2)then: chmod +x *
3) last: sudo ./flash_tool.sh
4)Choose the scatter file and recovery img downloaded like in the pic (checkboxes too):
{
"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"
}
5)Make sure your phone is off, click Download then plug in the phone using a USB2 port...
6)CWM installed!
7)extract the stock cwm backup zip to sdcard in this following order of directory: clockworkmod/backup/(the extracted contents here)
8)Reboot the phone by hold Vol Down + Power then leave it, due to the issue it will enter cwm automatically
9)navigate to "backup and restore" and choose restore then the folder your copied (in date format)
10)reboot, dun! :highfive:
Big Credits and thanks to: https://www.facebook.com/htc626gplusdev/info/?tab=page_info , for custom recovery...
Hit thanks if this has helped you, would motivate me to update the links lol
Hi, this is to install the cwm recovery... Right? But how do i flash my phone with an HTC stock rom? Because i don't have a back up to restore my phone. And htc already has a default recovery. Can't i use that to flash my phone with the stock rom file? Maybe via adb sideload?
diml0rd said:
Hi, this is to install the cwm recovery... Right? But how do i flash my phone with an HTC stock rom? Because i don't have a back up to restore my phone. And htc already has a default recovery. Can't i use that to flash my phone with the stock rom file? Maybe via adb sideload?
Click to expand...
Click to collapse
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
tpr0 said:
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
Click to expand...
Click to collapse
Sorry i though your link was an update to cwm, not the rom. Just saw the size of the file. Thanks i will try this. This is what I was looking for actually. Too bad i just deleted my arch Linux though ??
tpr0 said:
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
Click to expand...
Click to collapse
can't download :
https://www.dropbox.com/sh/1oev7ymmh...mXInVs_va?dl=0
returns:
This account's public links are generating too much traffic and have been temporarily disabled!
diml0rd said:
can't download :
https://www.dropbox.com/sh/1oev7ymmh...mXInVs_va?dl=0
returns:
This account's public links are generating too much traffic and have been temporarily disabled!
Click to expand...
Click to collapse
Link updated
Hello, sorry, I have the same problem my phone is 626g, I do not know if this guide is, however, the link ww w.dropbox.com/s/drc102llim...atter.txt?dl=0 and the link:w.dropbox.com/s/wt0r1q8xqs...71609.img?dl=0[/url] not working.
Thank you there is nothing about this problem and service HTC wash their hands with this.
tpr0 said:
I think understanding the title of the thread would answer your question, no this is not "install the cwm recovery" it is required in order to restore stock ROM unofficially, there is no way around it to date, if you are afraid/don't trust the stock ROM backup I provided, then wait for HTC to release RUU and simply use fastboot to update (? mediatek)...
Follow the steps, I've provided everything, you don’t need a backup, download my backup etc...
Click to expand...
Click to collapse
sorry but the other two links are broken as well. i have the STOCK CWM.zip now
Hello again, I found the scatter file. But when you download and plug the USB, I get the following message.
PTM changed for ROM; it must be downloaded
Any help please? I read that this was solved by selecting all + download format rather than just download, but I have some fear in doing this.
Cheers
---------- Post added at 10:13 PM ---------- Previous post was at 09:53 PM ----------
Yes, unfortunately we need these files that are not found anywhere. They would be so kind as to re-upload?
Thank you
Cheers
I've been looking for 3 days and there is no way you're tpr0 alone gives a solution, could you please reupload the files? I am eternally grateful. Thank you very much Greetings.
reprono said:
I've been looking for 3 days and there is no way you're tpr0 alone gives a solution, could you please reupload the files? I am eternally grateful. Thank you very much Greetings.
Click to expand...
Click to collapse
Ch
Can you please be more specific about which file? Here's how it looks on my side : http://m.imgur.com/wKhtNtQ
I'll reupload to Google drive soon :good:
tpr0 said:
Hello, sorry for late, I'm also surprised why this solution isnt popular as many users faced the same issue
Can you please be more specific about which file? Here's how it looks on my side : http://m.imgur.com/wKhtNtQ
I'll reupload to Google drive soon :good:
Click to expand...
Click to collapse
please upload these files to your google drive folder:
2)CWM(626g+): https://www.dropbox.com/s/wt0r1q8xqs...71609.img?dl=0 (source and developer in the credits section)
3)Scatter file(626g+):https://www.dropbox.com/s/drc102llim...atter.txt?dl=0
---
just saw that you already did! :good: thanks
Any guidelines for people who are stuck with windows?
Thanks this worked but now my phone is being recognised as "HTC Desire 320" and every time I boot up it says incorrect CID
alvi.mahmud said:
Any guidelines for people who are stuck with windows?
Click to expand...
Click to collapse
You can use VirtualBox to boot linux, use ubuntu 14.04 iso as 'cdrom', install guest additions then follow the procedure. ill post a quick guide soon :good:
tpr0 said:
You can use VirtualBox to boot linux, use ubuntu 14.04 iso as 'cdrom', install guest additions then follow the procedure. ill post a quick guide soon :good:
Click to expand...
Click to collapse
Mine worked on Windows 10
ahmedshauq said:
Mine worked on Windows 10
Click to expand...
Click to collapse
It 'should' work on windows, though at certain settings Windows updates the driver with incorrect version. I recomended Linux to avoid problems with drivers
ahmedshauq said:
Thanks this worked but now my phone is being recognised as "HTC Desire 320" and every time I boot up it says incorrect CID
Click to expand...
Click to collapse
Anyone know a fix?
I just tried it with same result. But I also noticed that I can use only one sim now (SIM management in settings is gray) and language is mixed english with czech (my default).
Awaraine said:
I just tried it with same result. But I also noticed that I can use only one sim now (SIM management in settings is gray) and language is mixed english with czech (my default).
Click to expand...
Click to collapse
I can use both Sims though
After xiaomi decided to push an update of miui with lollipop, they decided to change partitions and firmware is new too which is bad (as it causes bootloop) if you want to switch to Cyanogenmod 13 which has got official support recently.
So its good to get back on kitkat MIUI to switch to Cyanogenmod.
Let's get started!
THINGS YOU'LL NEED:
1. ADB and Fastboot tools: http://d-h.st/oFLb
2. Stock MIUI kitkat ROM: http://bigota.d.miui.com/V6.7.1.0.K...ICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
3. 7zip (Probably the best file manager) http://www.7-zip.org/download.html
4. Drivers: http://d-h.st/a5kA
How to install drivers: Download and extract the above zip contents in a folder. Right click on My Computer > Manage > Device Manager. If your drivers are not installed correctly, it will show as unknown device in device manager. Right click unknown device > Click update driver software > Browse and select the extracted folder. If warning is shown, ignore it and proceed.
5. Patience and some brain xD :silly:
INSTALLATION:
Windows 7/8/8.1 is recommended
1. Extract the adb and fastboot tools in folder on your desktop named Redmi 2.
2.Download and extrack the fastboot ROM in the same folder too. Use 7zip software here to extract it.
3.Now move mouse to empty space in folder and while pressing shift, press right click. A menu will open. Select " open command prompt here" option. A command prompt window will open.
4.Power off your phone. Let it vibrate. Press and hold "Volume down and power" buttons until it enters fastboot mode.
5.Connect the phone to PC/Laptop in fastboot mode itself. Let the OS install drivers, make sure you have working internet connection.
6.Type the following command:
Code:
fastboot devices
Fastboot will return serial number of device(It can be any number don't worry if it looks weird). Click button below to see screenshot:
{
"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"
}
7.If a blank space is returned, make sure drivers are installed correctly and phone is connected correctly.
8.If everything is okay, type the following commands one after another when previous process is complete.
I have shown a example for flashing recovery image below. Likewise you have to proceed for others.
Code:
1.fastboot flash boot boot.img
2.fastboot flash system system.img
3.fastboot flash userdata userdata.img
4.fastboot flash recovery recovery.img
5.fastboot flash cache cache.img
9.After this is completed, type the last command:
Code:
fastboot reboot
10.DONE.
Your phone will now boot in MIUI kitkat and you are ready to flash the official CM13!
Follow this guide for CM13:http://forum.xda-developers.com/redmi-2/how-to/rom-install-official-cyanogenmod-13-t3374589
HIT THANKS AND FEEL FREE TO ASK QUESTIONS HERE.
bootloader isn't locked, only partitions change bro
I flashed the images via fastboot and got bootloop...........
PROdelision said:
I flashed the images via fastboot and got bootloop...........
Click to expand...
Click to collapse
Device variant?
Did you try cm13? Try and tell.
Sent from my 2014818 using Tapatalk
is this how to the same with if i use MiFlash?
sennayan said:
is this how to the same with if i use MiFlash?
Click to expand...
Click to collapse
Yes. I'll try to update this with screenshots etc today.
Sent from my 2014818 using Tapatalk
Is this working with 2014813?
frosty234 said:
Is this working with 2014813?
Click to expand...
Click to collapse
It should.
Sent from my 2014818 using Tapatalk
noobpremium said:
It should.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
I made it with 2014813, and now I am stuck at boot with MI logo.
What can I do?
bisato said:
I made it with 2014813, and now I am stuck at boot with MI logo.
What can I do?
Click to expand...
Click to collapse
Flash twrp and go for cm13 :good:
Sent from my 2014818 using Tapatalk
I was now able to once Start after installing "your" twrp. I wiped data etc, but now it gives me error 7.
Edit: solved by once again flash twrp IMG through twrp itself. THX noobpremium
Device variant: 2014811, a.k.a. Wt88047, a.k.a. Redmi 2 WCDMA
I exactly followed your post and flashed the images via fastboot and got a bootloop.
Then used fastboot to install & boot a twrp-3.0.0-0-wt88047-20160309.img and proceed to install a cm-13.0 NIGHTLY-wt88047 ROM and, again, got a bootloop
plasticdoc said:
Device variant: 2014811, a.k.a. Wt88047, a.k.a. Redmi 2 WCDMA
I exactly followed your post and flashed the images via fastboot and got a bootloop.
Then used fastboot to install & boot a twrp-3.0.0-0-wt88047-20160309.img and proceed to install a cm-13.0 NIGHTLY-wt88047 ROM and, again, got a bootloop
Click to expand...
Click to collapse
Did you follow cm13 guide properly?
Did you wipe system partition
Sent from my 2014818 using Tapatalk
Hey so, I'm running HM2014811 redmi 2 on lollipop miui. I've followed your article, but when i try to flash system.img, fastboot comes up with an error (remoteata too large). So what should i do.
Luke T. Kirk said:
Hey so, I'm running HM2014811 redmi 2 on lollipop miui. I've followed your article, but when i try to flash system.img, fastboot comes up with an error (remoteata too large). So what should i do.
Click to expand...
Click to collapse
First erase data partition with this command:
Code:
fastboot erase userdata
And then flash userdata again
Edit: Maybe you'll need to erase system partition too and flash again.
Sent from my 2014818 using Tapatalk
noobpremium said:
First erase data partition with this command:
Code:
fastboot erase userdata
And then flash userdata again
Edit: Maybe you'll need to erase system partition too and flash again.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
Nope, It's still saying 'remote: Data too large" on trying to flash either system.img or userdata on fastboot
Any other suggestions?
Luke T. Kirk said:
Nope, It's still saying 'remote: Data too large" on trying to flash either system.img or userdata on fastboot
Any other suggestions?
Click to expand...
Click to collapse
I was finally able to install the ROM listed at the 1st post, i.e., ROM wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
This how I did it from a computer running Ubuntu Linux 14.04.04 LTS:
1. @ PHONE: put phone in fastboot mode
2. @ PC:
2.1. unarchive the file wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
2.2. go to the unarchived directory and execute:
sudo ./flash_all.sh (this command executed from an Ubuntu Linux terminal)
2.3. After a while it reboots and then it takes a long time (>5min.?) to show you the MIUI 6 interface
Done.
D.
plasticdoc said:
I was finally able to install the ROM listed at the 1st post, i.e., ROM wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
This how I did it from a computer running Ubuntu Linux 14.04.04 LTS:
1. @ PHONE: put phone in fastboot mode
2. @ PC:
2.1. unarchive the file wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
2.2. go to the unarchived directory and execute:
sudo ./flash_all.sh (this command executed from an Ubuntu Linux terminal)
2.3. After a while it reboots and then it takes a long time (>5min.?) to show you the MIUI 6 interface
Done.
D.
Click to expand...
Click to collapse
Super thanks. I'll add it to OP for ubuntu guys. I have ubuntu too but i dont use it for flashing [emoji14]
Sent from my 2014818 using Tapatalk
plasticdoc said:
I was finally able to install the ROM listed at the 1st post, i.e., ROM wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
This how I did it from a computer running Ubuntu Linux 14.04.04 LTS:
1. @ PHONE: put phone in fastboot mode
2. @ PC:
2.1. unarchive the file wt88047_global_images_V6.7.1.0.KHJMICH_20150826.0000.7_4.4_global_dcc2d135ee.tgz
2.2. go to the unarchived directory and execute:
sudo ./flash_all.sh (this command executed from an Ubuntu Linux terminal)
2.3. After a while it reboots and then it takes a long time (>5min.?) to show you the MIUI 6 interface
Done.
D.
Click to expand...
Click to collapse
Thank you, i'll try it out. I should have included the fact that im running os x. So yes, i'll execute the flash all from terminal.
"flash_all.bat" will work alternative of typing commands manually? (2014818)