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
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
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
[Resource/DevTools] TheCollectiveHelpPackageSCH-i800[everything you need & some]72813
{
"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"
}
TheCollective SCH-i800 Help package
http://wiki.cyanogenmod.org/w/P1c_Info
---------------------------------------------------------------------------------------------------------------------------------------------
TheCollective is Proud to present to you StockRooted-sch-i800 Verzion Galaxy Tab
For what ever reason we all need to get back to the default factory state.
soft brick
resale
loss of stablity
to name a few.
Here are the steps you will need to take.
First let's point out that this package contains EVERYTHING YOU NEED for this Except the windows PC to which it will be used on.
Before we begin Install Samsung usb device drivers located in the package.
**\tools-resources\drivers
Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
next is unpacking Hemdall 1.3.2 (The only one that worked for me on my SCH-i800)
**\tools-resources\Heimdall\
heimdall-suite-1.3.2-win32.zip
But here is a link to the developers page so you can download the original/newer if you want.
http://www.glassechidna.com.au/products/heimdall/
You will also need *Microsoft C++ 2012 32bit [if 2013 32/64bit has already been installed you will need to remove it first to install 2012]
This needs installed on your machine because it has .dll files Heimdall uses.
**\tools-resources\MicrosoftC++12\
vcredist_x86.exe
Now you will need to install the drivers this is also needed for Heimdall.
unzip heimdall and go into the drivers folder where you will see /zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device (or whatever it says, eg genirc serial device) (tho NOT massStorageDevice)
[good idea to remove any other usb devices as they can and sometimse do interfere with the packet data sending/receiving]
Click the button "replace driver" and let heimdall download/install the drivers. {libusb0 is the one that worked for me, but try another if it dont for you, there are three}
Run Heimdall-Frontend.exe as admin
Files provided To Flash Your Tab with
**\TheCollective-StockRooted-sch-i800.tar.gz >--TheStockRooted 2.3.5 that came on your tab.
**\tools-resources\HumberOS\heimdall-uses
boot.img >-- a CM10.1 kernel with TWRP for sch-i800
recovery.bin >-- CM10.1 twrp for sch-i800
if you need the pit file --> my-sch-i800.pit [extract it from the stock tar gz]
Ok, Let's get to flashing over the files and getting your tab back to normal.
1: Connect your tab to your PC
2: Launch your tab into download as it is already connected to your PC.*(Do this by holding the volume down and pushing the power button)
3: Go in to the folder "Heimdall" and start " heimdall-frontend.exe" as ADMIN
4: Set up the file you are about to LoadPackage tab. [It should look something like image.]
5: After you have the file in place click load, it will change tab to flash with files listed, simply click start to flash.
ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems.
Tab should boot. [if not factory data reset in recovery e3 and reboot]
Click to expand...
Click to collapse
After this is should be just like you took it out of the box, and already rooted.
Hope this helps!
---------------------------------------------------------------------------------------------------------------------------------------
If you wish to unroot I've included SuperOneClick shortfuse.
just hit unroot
If you wish to install CM or other AOSP rom here is some helpfull info.
Heimdall command line
Flash boot.img with heimdall command line like this:
Press Power + VolDown untill you get the Download screen or PC <–> Tab screen.
on PC open CMD prompt in the folder of Heimdall and place boot image in same folder
type this command string:
Code:
heimdall flash --kernel boot.img --recovery boot.img
Or just replace boot.img inside the ROM ZIP with your desired kernel.
*TIPS
In case you get any strange symptoms.
Flash full TheCollective-StockRooted-sch-i800.tar.gz (with repartition) via Heimdall.
Flash the Kernel included in the package using the heimdall command above.
Boot directly into CwM Recovery, holding Power + VolUp.
Flash CM10.1 ROM, if it reboots by itself repeat the step above.
If you want Google’s stuff, flash latest GApps for Android 4.2.2.
Only Reboot after everything.
Wrong MAC? Wrong IMEI? Try restoring files from /sdcard/backup/efs*/* to /efs/. If you don’t have a backup, then start over with FULL Restock, and next time save your backup/efs folders, which are created everytime you install CM10.1.
Market problems? Clear Google Services Framework data and reboot.
No touch? That means you got the wrong kernel installed. A couple of builds had problems identifying the exact model. Just flash your kernel through recovery or heimdall / odin.
No boot? Stuck at the SAMSUNG logo? Flash the correct kernel using Download Mode using heimdall!
Deep Sleep not kicking in? Try wiping cLock’s data or freezing / removing it (com.cyanogenmod.lockclock).
--------------------------------------Highlights of What you get inside---------------------------------------------------------------
**\TheCollective-StockRooted-sch-i800.tar.gz
The Heimdall package
**\tools-resources\drivers\Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Samsung Mobile Drivers for usb
**\tools-resources\Heimdall\heimdall-suite-1.3.2-win32.zip
Heimdall
**\tools-resources\HumberOS\heimdall-uses\boot.img
CM10.1 humberOS Kernel P1c
**\tools-resources\HumberOS\heimdall-uses\recovery.bin
TWRP Touch Recovery 2.5.0.0
**\tools-resources\HumberOS\CwM_CM10.1-humberos_kernel_p1c-20130715.zip
CM10.1 humberOS Kernel P1c
**\tools-resources\MicrosoftC++12\vcredist_x86.exe
Microsoft C++ redisturbutial
**\tools-resources\ODIN-1.7\
Odin3 v1.7.exe
If you need it for modems or kernels
**\tools-resources\PartitionTool4microSD\pwhe8.exe
if you get encryption failed, you might find this usefull to partition your external sdcard [deeper instruction online at rootzwiki]
**\tools-resources\SuperOneClick\SuperOneClickv2.3.3-ShortFuse.zip
unroot/root what ever just good to have hard to find
DOWNLOAD
MD5 Sum: F0F9C9FA54219EDFA50E85163D9A7C54
Excellent job of documentation! Thanks for all the hard work.
I come up with an MD5 of f0f9c9fa54219edfa50e85163d9a7c54 Anyone want to confirm?
robjective said:
Excellent job of documentation! Thanks for all the hard work.
I come up with an MD5 of f0f9c9fa54219edfa50e85163d9a7c54 Anyone want to confirm?
Click to expand...
Click to collapse
F0F9C9FA54219EDFA50E85163D9A7C54
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4 Beta
Appreciate the thread! Is it possible to get a mirror though? The current host keeps cutting me off whenever I try to download the file... Can't make it past 200MB no matter what I try; other files download fine.
Going through the whole process but "Heimdall.exe" stopped working EVERY time I press start. Any ideas?
Cellulah said:
Appreciate the thread! Is it possible to get a mirror though? The current host keeps cutting me off whenever I try to download the file... Can't make it past 200MB no matter what I try; other files download fine.
Click to expand...
Click to collapse
I had the some problem. Tried it at work with FF, Chrome, and Free Download Manager and all would fail at some point after about 2/3 done.
Came home and tried and got it first try.
tinpanalley said:
Going through the whole process but "Heimdall.exe" stopped working EVERY time I press start. Any ideas?
Click to expand...
Click to collapse
Perhaps bad DL.
Make sure you follow all instruction.
Don't skip any steps.
Don't forget to have the correct ms c++ redist istalled.
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
Perhaps bad DL.
Make sure you follow all instruction.
Don't skip any steps.
Don't forget to have the correct ms c++ redist istalled.
Sent from my GT-P5110 using Tapatalk 4
Click to expand...
Click to collapse
I'll try again. The download was fine but I suppose I could try again.
No use.. same error every time . Tried with each driver as well. All I get is this:
tinpanalley said:
No use.. same error every time . Tried with each driver as well. All I get is this:
Click to expand...
Click to collapse
Tell me more about your operating system that your using.
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
Tell me more about your operating system that your using.
Sent from my GT-P5110 using Tapatalk 4
Click to expand...
Click to collapse
Windows 7, 64-bit
Intel i5-2400 3.10 GHz
Just a question. Every time I boot to recovery <3e>, and try to wipe data, I get the following:
E:failed to mount /data (Invalid argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions
Could this have anything to do with why I'm not able to get out of my bootloop?
tinpanalley said:
Just a question. Every time I boot to recovery <3e>, and try to wipe data, I get the following:
E:failed to mount /data (Invalid argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions
Could this have anything to do with why I'm not able to get out of my bootloop?
Click to expand...
Click to collapse
Yes. I had same issue on my captivate trying to restore stock from a cm7
To fix I had to flash in the kernel and recovery from cm and in cwm under advance mounts format data. Back then on that device speedmod kernel allowed users to select format method (fat32/ext4/etc)
But also hemidall should format with the repartition. But that is assuming it can read and mount the partition.
You can use this package but instead of flashing the ROM package,
Load the pit and load only the kernel and recovery
Then boot into cwm and mount and format data (might as well while your at it mount and format system, and cache)
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
You can use this package but instead of flashing the ROM package,
Load the pit and load only the kernel and recovery
Then boot into cwm and mount and format data (might as well while your at it mount and format system, and cache)
Click to expand...
Click to collapse
I did try this but I still get the crash of heimdall.
Also what does "mount and format data" mean? I can format data, system and cache but I don't see "mount" at all.
The Collective DL Fails
So I am trying to download the package that is for this which would be most helpful for me as I'm trying to help out my pastors wife with her Galaxy Tab, I started the download and it got all the way up to 144MB and quit, and file won't work.
Is there somewhere else that you can put it so we can try downloading from there? Can I give you my dropbox and you can drop it in there?
Again just to say I don't have a problem with HEIMDALL I have a problem downloading your link for the files needed for the flash.
I would really like to try to get this working for her as I've been looking around for a solution for this thing for about 2wks already and its been blowing my mind.
So we need the DL fixed so we can download the Collective Package.
Thanks again for the help and great write-up.
Lem
:angel:
chi_tilt said:
So I am trying to download the package that is for this which would be most helpful for me as .......
So we need the DL fixed so we can download the Collective Package.
Thanks again for the help and great write-up.
Lem
:angel:
Click to expand...
Click to collapse
Try a direct download link
http://www.theandroidcollective.org/i800/public/TheCollective-HelperPackage_sch-i800.zip
Sometimes download errors like yours seem to happen when the user is behind a proxy.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
No 3G with alroger's latest kernel
I guess this is a pretty common issue for CDMA user's. alroger's download page says to copy the modem.bin to the /radio. I downloaded the original verizon modem binaries for my sch-i800 but I don't see a /radio folder. In the about tablet section, baseband is unknown. I just created a radio folder on the root of the tablet and renamed my download modem.bin and stuck it in there. I'm about to reflash the just the kernel but I'm pretty sure that's not how it works. So how do I get my radio/modem back and get 3g working with this kernel? cafe-ti.blog.br/1956~cm10-1-sgt7-p1000.html
arielja87 said:
I guess this is a pretty common issue for CDMA user's. alroger's download page says to copy the modem.bin to the /radio. I downloaded the original verizon modem binaries for my sch-i800 but I don't see a /radio folder. In the about tablet section, baseband is unknown. I just created a radio folder on the root of the tablet and renamed my download modem.bin and stuck it in there. I'm about to reflash the just the kernel but I'm pretty sure that's not how it works. So how do I get my radio/modem back and get 3g working with this kernel? cafe-ti.blog.br/1956~cm10-1-sgt7-p1000.html
Click to expand...
Click to collapse
Easiest way is to tar the modem.bin and Odin it into the device.
Load it into the phone slot
Sent from my GT-P5110 using Tapatalk 4
Help to download...
Hi... I have tried many times to download the package (TheCollective-RootedStock-Odin-sch-i800.tar.md5) but I can not , the download starts fine, but not complete!.
If you could upload to another server like 4shared, mediafire, dropbox... I would be very grateful..
Still not working as it should
So I have downloaded the package finally and I Have done all the steps according to your writeup. Still doesn't give me a fresh startup on the tablet, I still get many error popups and also all my apps are still there.
What could I be doing wrong? Could there be something wrong with the tablet?
Any help on this would be great, as I'm dumbfounded on this already.
Thank You
Lem
ARE YOU SEARCHING TO ROOT YOUR REDMI 2 ?
DISCLAIMER:DO THIS ON YOUR OWN. I'M NOT RESPONSIBLE FOR ANYTHING HAPPENS TO YOU AND YOUR DEVICE.PLEASE DONOT MIRROR THE LINKS
CLICK HERE FOR NATIVE ROOT
IF YOU ARE GETTING STOCK RECOVERY EVEN AFTER FLASHIN CWM, SEE THIS POST
STEP 1- FLASHING CWM ON YOUR PHONE
1.At first, you'll need the "adb" and "fastboot" tools. Get them HERE
2.Extract them into a folder, let's name it "Redmi2" (You can give your own name to the folder. That doesn't matter here.)
3.Now get the CWM .img file from HERE
You can use Philz Touch recovery also. Get HERE
4.Rename cwm.img or philz.img you downloaded above and as "recovery.img" and place it in the Redmi2 folder.
Now the folder will look like this-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.Press and hold "shift" button and right click in the blank area of the folder and click on "open command promt window here". The command prompt will open.
6.Now turn off your Redmi2. Wait until it vibrates. After it's vibrated press and hold "Volume down and Power" keys together until it boots into "fastboot mode". Now connect the Redmi2 to your PC/Laptop through USB cable in fastboot mode itself.
7.Get to the command prompt now.
Now type: " fastboot devices " (without these- " " )
Like this-
8.Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command
9.Now enter the next command: " fastboot flash recovery recovery.img "
Like this-
10. Now this ends...
Type the last command: " fastboot reboot "
Like this-
11.Now your phone will reboot with ClockWorkMod(CWM) installed. CHEERS...
STEP 2- ROOTING YOUR PHONE
1. Firstly get the SuperSU.zip from HERE
2. Now copy the downloaded zip to your sdcard (not in any folder just in sdcard)
3. Boot into CWM recovery by turning off the phone and pressing "Volume UP and Power" button together after the phone vibrates.
4. Once CWM main menu is displayed, select "Install from zip" and browse to the zip that you downloaded earlier and select it.
5. Install the zip. If you get any warning, ignore and proceed.
6. After the installation is complete, reboot your device. (I think you can do that)
7. VOILA..!!! YOU ROOTED YOUR REDMI2
PLEASE HIT THANKS
JOIN OUR FACEBOOK GROUP HERE
CREDITS:
1. I don't claim any credit for "adb and fastboot tools" and the "recovery.img" and "SuperSu.zip"
2. Thanks to @subhrajiNath on Miui english forums who wrote the original guides.
Thread link is here and here
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
postadelmaga said:
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
Click to expand...
Click to collapse
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
? not flashing ?
noobpremium said:
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
Click to expand...
Click to collapse
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
postadelmaga said:
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
Click to expand...
Click to collapse
get "Flashify" app from playstore and first take backup of stock recovery and then flash the cwm with it. Thats it..
Actually I didn't knew this method before i made this guide..
Anyway, fastboot gives us a different feel, doesn't it? :v
wait I don't know flashify but it looks it needs root to flash the recovery ... but I think I need cwm to root ... so I think this is not gonna work ...
Ok got it, this may be useful to anybody face the issue with recovery:
I discovered you can workaround the issue in this way:
Temporary boot into CWM:
HTML:
fastboot boot recovery.img
Root the device using CWM
Flash CWM using flashify
[ CWM when you log out ask you for root so maybe it is not necessary to use the zip file ( but I'm not very expert so maybe I'm wrong)]
You can install GAPPS with CWM `gapps-kk-20140606-signed .zip` but be careful, whenever you update MIUI you will look all software installed using CWM. ( superSu and GAPPS for example )
thanks
thanks!
eienkisu said:
thanks!
Click to expand...
Click to collapse
Pleasure
Okay bro :good:
I'll update the OP
I confirm #postadelmaga the CWM recovery does not stay, the only way to do access it is the fastboot boot recovery.img Here's how I succeeded with two phones now.
power on, start wifi, do Miui updates
install ADB or the files above on PC
reboot to fastboot with voldown+pwr
now comes fastboot boot recovery.img
in CWM, sideload SuperSu and Gapps
connect you preferred VPN (if in China)
install and update all Google apps needed
delete most Chinese apps
hey i m unable to flash recovery plzz help
Device version 2014818
Sent from my 2014818
Hi buddy could you plz port touchwiz from galaxy prime?
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
not working.
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
godwintgn said:
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
Click to expand...
Click to collapse
Are you on win7? I got this same issue on my win7... try on win8 it works flawlessly
Please hit thanks if done
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Shrihari007 said:
Hi buddy could you plz port touchwiz from galaxy prime?
Click to expand...
Click to collapse
TW sucks man.. why do you want it :/ anyways I'll try
leuk_he said:
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
Click to expand...
Click to collapse
Thanks to you bro.. I'll update the OP for those who are facing some issues with my guide's precedure..
OP Updated
I've updated the OP with the other guide's link.. please check it out if you're having some issues with this one
godwintgn said:
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Click to expand...
Click to collapse
Try on some friend's PC or something
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)