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
Related
I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3
crxforya said:
I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3
Click to expand...
Click to collapse
Sounds like you need to flash a good hardSPL in terminal and then with fastboot-usb, flash recovery.
Hard SPL
Do you know where I can find a good one. And doesnt it require me to have a working recovery in-order to flash the spl???
thanks for your response.
crxforya said:
Do you know where I can find a good one. And doesnt it require me to have a working recovery in-order to flash the spl???
thanks for your response.
Click to expand...
Click to collapse
Anything that can be flashed in recovery/console/terminal can be flashed (more safely, according to lbcoder, ezterry, etc) in fastboot-usb. So you want to use the .img file out of this zip and flash it in fastboot to the hboot partition. This spl is a recoded sapphire 2005 hboot, made to look like 2004 -- for DVT board 32As, but less risk of crossing wires with radio, AFAIK. The second one is just a straight-up 2009, which is pretty current. I assume you have a Sapphire MT3G, not a Magic MT3G (Fender/v1.2) because I wouldn't count on these files working for you. If you happen to have DangerSPL installed (although that's not necessary with MT3G) check the rooting/SPL instructions on that forum to make sure these files are right. Good luck!
NOTE: Here's a good Wiki on SAFELY flashing hboot/radio/recovery images that I found in Firerat's sig. As someone who has bricked a G1 by willy-nilly flashing, I implore you to have a look-see:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_Bootloader
rynosaur said:
Anything that can be flashed in recovery/console/terminal can be flashed (more safely, according to lbcoder, ezterry, etc) in fastboot-usb. So you want to use the .img file out of this zip and flash it in fastboot to the hboot partition. This spl is a recoded sapphire 2005 hboot, made to look like 2004 -- for DVT board 32As, but less risk of crossing wires with radio, AFAIK. The second one is just a straight-up 2009, which is pretty current. I assume you have a Sapphire MT3G, not a Magic MT3G (Fender/v1.2) because I wouldn't count on these files working for you. If you happen to have DangerSPL installed (although that's not necessary with MT3G) check the rooting/SPL instructions on that forum to make sure these files are right. Good luck!
Click to expand...
Click to collapse
BUT, no adb , so chances are no fastboot..........
OP needs to get over the adb issue
Firerat said:
BUT, no adb , so chances are no fastboot..........
OP needs to get over the adb issue
Click to expand...
Click to collapse
Hmmm, I remember that way back in the day, JF included native ADB access in first custom RC30 Roms and then he packaged it into his custom recovery, but I don't know if losing a recovery image means losing ADB access and therefore fastboot access whatsoever?
Ill have to check
I have used adb before but Im not at my personal computer so I am not able to utilize the adb shell, and the computer that I am using, I do not have access to install. Is there another option that does not require adb, or is there a reason that I cant flash a sappimg file unroot, and start over???
crxforya said:
I have used adb before but Im not at my personal computer so I am not able to utilize the adb shell, and the computer that I am using, I do not have access to install. Is there another option that does not require adb, or is there a reason that I cant flash a sappimg file unroot, and start over???
Click to expand...
Click to collapse
No problem at all doing that, nbh overwrites radio, hboot, recovery. Just make sure you have the rooting files stored locally, i.e. custom rom, custom recovery, custom/hard/eng SPL, new radio, recovery test keys, etc.
crxforya said:
because I dont have access to install adb at my location.
Click to expand...
Click to collapse
rynosaur said:
Hmmm, I remember that way back in the day, JF included native ADB access in first custom RC30 Roms and then he packaged it into his custom recovery, but I don't know if losing a recovery image means losing ADB access and therefore fastboot access whatsoever?
Click to expand...
Click to collapse
did you read the post?
no adb = no fastboot
@crxforya'
your best bet is
Code:
su
ash
flash_image recovery /sdcard/recovery.img
if it fails, scroll up with track ball, and hit enter again, repeat until it works
crxforya said:
I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3
Click to expand...
Click to collapse
read this it might help it did for me when i try 2 use ROM MANAGER APP n i lost my recovery-->>> http://forum.cyanogenmod.com/index....toasted-not-bricked-phone-thread/page__st__40
No luck
Thanks for your help Firerat, It seems that everytime I hit enter to flash recovery it just gives me another command line. Ive done it about 30 times and doesnt appear that its gonna take. Do you know what I would need to do to unroot, and start over. I looked at the Unlockr website and the process with the NBH file looks like it works until i reboot and it is still 2.1. Any help there I really appreciate it.
ur recovery is corrupted try this
To boot into fastboot you need to hold back and power.
Then plug the original usb cable into your pc then into phone. your phone should say FASTBOOT USB
If not you will have to use USB deview (a few posts above). Then using it unistall anything that says Android or HTC or ADB or Fastboot... You get the idea.
Then unplug and replug the usb cable to your pc.
Windows should say that there is an unrecognised item or something, go into device manager and there should be one with an "!" mark, or a wizard to install the drivers appears.
When it asks you where to find drivers, click the option that says select where the drivers are (advanced), or something. Then point it to the folder were the USB drivers are and let it do its work.
After its finished start cmd and use the command "cd" to go to the tools folder where your sdk is extracted if it was at "C:\android-sdk-windows\tools" you would type in cmd "cd C:\android-sdk-windows\tools"
Then put in "fastboot devices" and it should give you your phones serial number, as long as the drivers work and you are in fastboot (phone should say FASTBOOT USB)
If that works we are back on track
{
"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"
}
Ok now download the latest Amon_Ra recovery XDA link
Now check the md5 using this tiny standalone app Download.cnet.com link this is self explanatory, as the md5 sum is on the XDA link.
Ok, so now you have checked that its not corrupted, move the .img file to the tools folder. For me it would be "C:\android-sdk-windows\tools" . (The .img file needs to be where the fastboot.exe is, so it finds it.)
Now this is where you get the stuff you type in to cmd.
Fastboot devices
Fastboot erase recovery
Fastboot flash recovery recovery-RA-dream-v1.7.0.img
Click to expand...
Click to collapse
same problem
i have the same problem except i have danger spl, i noobed it up and tried to flash recovery with cm 5.0.7...
i tried to flash the recovery a bunch of times, and i treid to get into fastboot, but idk where the drivers are, and idk how to find them.
help plz
crxforya said:
Thanks for your help Firerat, It seems that everytime I hit enter to flash recovery it just gives me another command line. Ive done it about 30 times and doesnt appear that its gonna take. Do you know what I would need to do to unroot, and start over. I looked at the Unlockr website and the process with the NBH file looks like it works until i reboot and it is still 2.1. Any help there I really appreciate it.
Click to expand...
Click to collapse
ok, thats interesting
straight after you do that
logcat
<track ball> then c
( or in terminal preferences, change the control key )
I'm guessing you see
I/flash_image( 2410): header is the same, not flashing recovery
so, try flashing a different version ( 1.6.2 ) , then 1.7.0
edit: or
Code:
erase_image recovery
flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
I need to start over
What does changing the control key do??? I know Im a noob!! Sorry and thanks for your help
Same problem here, on mt3g with latest super bad. I no longer have recovery and cant seem to flash one. And the latest amon-ra says not to flash from terminal if using latest cyanogenmod, yet my computer doesn't recognize my device, so I cant use adb.
-------------------------------------
Sent via the XDA Tapatalk App
Well im back at the out of memory messg
well after erasing recovery and trying to reflash on the 3rd time it gave me the out of memory error again. Now that script you made Fire do i just
su
sh firstboot.txt and your script will work???
crxforya said:
well after erasing recovery and trying to reflash on the 3rd time it gave me the out of memory error again. Now that script you made Fire do i just
su
sh firstboot.txt and your script will work???
Click to expand...
Click to collapse
well, I have a spaming script here
http://forum.cyanogenmod.com/index.php?/topic/3867-broke-recovery/page__view__findpost__p__39273
spamming the flash in CM5 seems to be working for most
Code:
#!/system/bin/sh
test=1
while [ "$test" = "1" ];do
flash_image recovery /sdcard/recovery.img
test=`echo $?`
done
echo "we got there in the end....."
[attachment=1106:spamflash.txt]
get that onto your sdcard
rename the recovery image to recovery.img and put on the sdcard
then
Code:
su
sh /sdcard/spamflash.txt
that will keep trying to flash until it works
another way is to flash before android starts ( plenty of free memory available )
this is a firstboot.sh script
Code:
flash_image recovery /data/recovery.img
if [ "$?" = "0" ];
then
rm /data/recovery.img
echo "recovery flashed"
else
echo "recovery flash failed..."
fi
[attachment=1107:firstboot.txt]
get that onto your sdcard
then
Code:
su
cp /sdcard/firstboot.txt /data/firstboot.sh
again rename the recovery image to recovery.img, but for this method you need to put it on /data/
It will 'self clean', i.e. if it works it will delete the recovery image, and the bit which runs the firstboot.sh deletes that ( but it will delete that regardless of it working or not )
Click to expand...
Click to collapse
deltawye said:
Same problem here, on mt3g with latest super bad. I no longer have recovery and cant seem to flash one. And the latest amon-ra says not to flash from terminal if using latest cyanogenmod, yet my computer doesn't recognize my device, so I cant use adb.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
When my phone does not recognize the USB connection I simply reboot my G1 while the USB is is still connected and that seems work for some odd reason.
I had the same problem. All I did was install rom manager, flash the rom manager recovery nothing. From there flash RA- recovery nothing and then did that back and fourth until it worked I also tried flashing it with one click root hope all help. Also tried the terminal. Hope you fine a way. Good luck!!!!!!!
-------------------------------------
Sent via the XDA Tapatalk App
DO NOT RUN THIS ON THE G2X! The partition layout is different, doing so will do bad things to your device. I will release a G2X compatible version when I am back online in a week's time!
For the past couple of days I have been working on creating a ClockworkMod recovery image for the LG Optimus 2X. I'm pleased to announce that the first full release is available!
Some points to note - READ THESE CAREFULLY!
Use at your own risk! I have successfully used the backup and restore functionality (nandroid), and am currently testing other functions.
If you manage to break your device completely, this ROM should get you back up and running.
Download
I have packaged the recovery itself and the installation system together in one download zip.
3.0.1.4 r1 DOWNLOAD (ROMraid Load Balancing) - MD5: 7145b425f95a87dc5bde29ac4eba48ff
Installation automatically on your device
NEW: If your device is rooted, my 99p 2X Recovery Boot app (mentioned below) can now flash the recovery image for you the first time you run the app and on subsequent version updates!
Installation on Windows, Linux and OSX
- Download the zip file above and extract to a directory
- Connect your device and ensure 'USB debugging' is enabled
- WINDOWS - double click 'install-clockworkmod-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-clockworkmod-mac.sh' followed by './install-clockworkmod-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-clockworkmod-linux.sh' followed by './install-clockworkmod-linux.sh'
If you wish, you can also manually install the recovery by pushing the clockworkmod.img file to /data/local/ with adb and running 'dd if=/data/local/clockworkmod.img of=/dev/block/mmcblk0p7' from a root shell.
Launching Recovery
To boot ClockworkMod Recovery, either:
Turn the device on while holding the volume down and power buttons until recovery loads
Download the OPTIONAL 99p 'LG 2X Recovery Boot' application from the Android Market (NOTE: This app is completely optional - if you do use it, thanks for your support!)
Source / Updates
I'll be posting the device profile and source changes on my GitHub shortly, and will issue fixes / new Betas as required.
Enjoy!
P
{
"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"
}
Thanks Paul !
You are the best. I am wating for the crowd to test this so I can use it for my mission critical work phone but the future seems bright.
Hi Paul... first of all - Great job here
Second - if one can't get root access via SuperOneClick, like myself, is this still usable?
Inebriatef said:
Hi Paul... first of all - Great job here
Second - if one can't get root access via SuperOneClick, like myself, is this still usable?
Click to expand...
Click to collapse
Root access is not a pre-requisite.
P
mirror (if it's ok with you Paul)
http://www.mediafire.com/?udkabus35wlr2w3
Great job paul
THANKS! Installing now
Update:
If you get error in windows just change adb-windows.exe to adb.exe
First, thank you very much, Paul. Great job!
Two questions.
1) This method overwrites the standard recovery on the phone, correct?
2) To revert back to standard recovery, one have to flash the whole phone using nvflash, correct?
ULJ said:
First, thank you very much, Paul. Great job!
Two questions.
1) This method overwrites the standard recovery on the phone, correct?
2) To revert back to standard recovery, one have to flash the whole phone using nvflash, correct?
Click to expand...
Click to collapse
1) Yes
2) No, you could just dd the stock recovery.img from the NVFlash archive.
P
<- This is me "patiently" waiting for CyanogenMod and Paul's online kitchen for the 2x
GREAT work as always, Paul!
paulobrien said:
1) Yes
2) No, you could just dd the stock recovery.img from the NVFlash archive.
P
Click to expand...
Click to collapse
Okay. Thanks.
Im just curious, who supplies the NVFlash archive? And is the standard recovery image supplied by Nvidia or LG? Since it is part of the NVFlash archive.
Found out why i can get no root access... i got no adb access at all.
First time pluggin in phone after install of LG drivers, it says that the adb interface thingy can't install.
This also causes that i can't install CWM.
Any suggestions as to what is wrong?
Thank you, Paul!
Successful nandroid backup I will try to make a custom rom.
Paul its was a good idea to let clockworkmod make backup to external sd because its not possible to mount usb storage in recovery menu yet.
Inebriatef said:
Found out why i can get no root access... i got no adb access at all.
First time pluggin in phone after install of LG drivers, it says that the adb interface thingy can't install.
This also causes that i can't install CWM.
Any suggestions as to what is wrong?
Click to expand...
Click to collapse
I hade the same problems. Download the LG drivers from this site, worked for me.
www {dot} junefabrics.com/android/driver.php
(could not post links, so replace {dot} with a .)
Inebriatef said:
Hi Paul... first of all - Great job here
Second - if one can't get root access via SuperOneClick, like myself, is this still usable?
Click to expand...
Click to collapse
Tried Z4root?
Nilssonnet said:
I hade the same problems. Download the LG drivers from this site, worked for me.
www {dot} junefabrics.com/android/driver.php
(could not post links, so replace {dot} with a .)
Click to expand...
Click to collapse
thx, it works now
yipeee! now i can expect a real custom rom
Ok first backup done! Works perfect! Thanks for all the effort!
Korumera said:
Ok first backup done! Works perfect! Thanks for all the effort!
Click to expand...
Click to collapse
Same here. Thank you very much, Paul!
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
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)