Database Develop

flash_image: not found

I can't find the flash_image command in my android (i have just installed the lastest HTC_ADP_1.6_DRC83_rooted_base) so i cant install cyanogen 1.4 ... please any workaround or help will be very appreciated
Thanks in advanced
chineseman

You are going to be directed to ask this in the Q&A section.

chineseman said:
I can't find the flash_image command in my android (i have just installed the lastest HTC_ADP_1.6_DRC83_rooted_base) so i cant install cyanogen 1.4 ... please any workaround or help will be very appreciated
Thanks in advanced
chineseman
Click to expand...
Click to collapse
You just type it in terminal.

chineseman said:
I can't find the flash_image command in my android (i have just installed the lastest HTC_ADP_1.6_DRC83_rooted_base) so i cant install cyanogen 1.4 ... please any workaround or help will be very appreciated
Thanks in advanced
chineseman
Click to expand...
Click to collapse
Take it from someone who just spent last evening re-rooting their phone, reinstalling apps etc...I would get familiar with ADB. And fast:
http://forum.xda-developers.com/showthread.php?t=502010
From there, you can pretty much do whatever you need to the phone, and it's a LOT less hassle.

I've got the same problem,
I can't flash via adb shell, because flash_image is not found
using fastboot , i flash recovery img file, which doesn't give me errors
but I still don't get cm's recovery.
I'm stuck at the stock HTC ADP1.6 rom

sleepy_sanchez said:
I've got the same problem,
I can't flash via adb shell, because flash_image is not found
using fastboot , i flash recovery img file, which doesn't give me errors
but I still don't get cm's recovery.
I'm stuck at the stock HTC ADP1.6 rom
Click to expand...
Click to collapse
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=567943

can't get into recovery mode
B-man007 said:
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=567943
Click to expand...
Click to collapse
I just did. The problem was solved via fastboot, which I've tried. Itdoesn't give me errors and says writing 'recovery'.... OKAY, but I still don't get cm's recovery mode.

sleepy_sanchez said:
I just did. The problem was solved via fastboot, which I've tried. Itdoesn't give me errors and says writing 'recovery'.... OKAY, but I still don't get cm's recovery mode.
Click to expand...
Click to collapse
does your phone show up when you type
Code:
fastboot devices
?
EDIT: Also, try updating to cyan's latest build from the stock recovery
Alt-L
Alt-W
Alt-S
Make sure you rename cyans update to update.zip
then try updating the recovery from there
if that doesnt work, try
Code:
fastboot erase recovery
and then reflash the recovery

yes, I'm able to see the device in fastboot.
I am able to erase and flash the recovery and get no error, but I can't login to the cm's recovery. Actually for some reason, the first time I try to go to recovery, the phone ignores me and boots directly to android.
. I did try to update from stock recovery, however I get installation aborted error during the update
It turns out flash_image isn't available in htc's stock rom, so I copied it to /system/bin . What happens when I try to flash the recovery img the first time is like this: I get
mtd: erase failure at 0x002e0000 (I/O error)
mtd: erase failure at 0x002e0000 (I/O error)
mtd: skipping write block at 0x002e0000
the second time i get no messages.
if I try flash_image erase recovery, it says
can't find erase partition

Ok, found my answer after googling with some people who had similar problem in an unrelated forum
ah ... i think the problem is that the recovery is replaced with each reboot.
first do:
adb root
adb remount
adb shell
cat /system/etc/install-recovery.sh > /system/etc/install-recovery.sh.disabled
rm /system/etc/install-recovery.sh
cat /system/recovery-from-boot.p > /system/recovery-from-boot.p.disabled
rm /system/recovery-from-boot.p
Flash a recovery-image like before ... I would recommend this one (from cyanogen) - the one I'm using: http://n0rp.chemlab.org/android/cm-recovery-1.4.img
Click to expand...
Click to collapse
after this I was able flash and login to cm's recovery

sleepy_sanchez said:
Ok, found my answer after googling with some people who had similar problem in an unrelated forum
after this I was able flash and login to cm's recovery
Click to expand...
Click to collapse
Thanks for posting that. So the reason the stock recovery was flashed is because you booted on the 1.6 recovery instead of flashing cm right after, correct?

B-man007 said:
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=567943
Click to expand...
Click to collapse
Yes it did works!! my SPL was very outdated... then after update my SPL i could use fastboot!

@sleepy_sanchez you're my hero tried the whole day to get the cm recovery on my stock ADP1.6... thanks nandroid is back as well as my backup from 4.9.1.1

@ B-man007 yes after I flashed stock adp image, I couldn't flash cm's image immediately(since I had to rename htc's adp1.6 image to sth else and the cm's image to update.zip). my CM 1.2 recovery was overwritten somehow, or disappeared during the many times I tried to get my G1 working(wiping reinstalling htc's image) . and I couldn't flash CM 1.4 recovery neither using fastboot nor adb.

sleepy_sanchez said:
@ B-man007 yes after I flashed stock adp image, I couldn't flash cm's image immediately(since I had to rename htc's adp1.6 image to sth else and the cm's image to update.zip). my CM 1.2 recovery was overwritten somehow, or disappeared during the many times I tried to get my G1 working(wiping reinstalling htc's image) . and I couldn't flash CM 1.4 recovery neither using fastboot nor adb.
Click to expand...
Click to collapse
ahh ic. judging from the instructions you posted, it looks like the HTC recovery image has a script to replace the stock recovery upon each boot

I can't install recovery via fastboot, cos after ENTER this command:
fastboot flash recovery recovery.img my PC freezes.
So I wanted flash it via terminal, take a look at my log:
{
"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"
}
File is placed directly in /sdcard

ZduneX25 said:
I can't install recovery via fastboot, cos after ENTER this command:
fastboot flash recovery recovery.img my PC freezes.
So I wanted flash it via terminal, take a look at my log:
File is placed directly in /sdcard
Click to expand...
Click to collapse
Sorry for bump. I have the exact same problem as you. Anyone know the soloution?
Thanks

Do you have flash_image installed? Is flash_image executable? Is flash_image in your path?
Btw.: This is a G1 thread, not a Desire thread.

from those who display flash_image: not found
this works for me:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/nombre del recovery.img
(for me: recovery-RA-sapphire-v1.7.0G.img)
reboot recovery
and its done!

[INFO] ClockworkMod 5.0.2.0 [09-05-11]

Originally posted by Koushik Dutta on Google+:
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes: update from 09.05.11
Fix the fact that some users were loosing root access with 5.0.1.0
Fix menu bug Even if you select no during wipe dalvik cache, it still says it wipes it (it is not actually wiping it, it is just a display bug)
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
Click to expand...
Click to collapse
To flash recovery for Nexus S, download recovery and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img

ill try
Sent from my Google Nexus S using XDA Premium App

I'm on it!

Or you can directly flash it from Rom Manager

You can also just put it on SD and flash from terminal then reboot.
Edit- before someone asks
su(press enter)
flash_image recovery /sdcard/5014cw.img(press enter)
reboot recovery(press enter)
Obviously the sdcard/* is whatever you rename the file
sent from my nexus s on a kang from simms

zadnica said:
Originally posted by Koushik Dutta on Google+:
To flash recovery for Nexus S, download recovery and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
I wish I would have seen this BEFORE I updated. It kept taking me to bootloader screen!!!!! But I unistalled and installed and finally got it to work!
Sent from my Nexus S using Tapatalk

Hey guys,
Everytime I restore from a backup through Rom Manager with the new recovery, I lose root. Right now, I'm stuck at work and cannot flash a rom, theme, battery mod, etc. I'll go back to 4.0.1.4 as soon as I go home
Am I the only one?
Edit: Found a solution==> Reboot into Recovery, flash su.zip again, and it's all good now!
f.

suhas_sm said:
Or you can directly flash it from Rom Manager
Click to expand...
Click to collapse
doesn't work for me..

I always recommend not using rom manager for anything flashing related, most problems occur for people when they're using rom manager and get fixed when done through recovery or in this case terminal/adb
RevengeITA said:
doesn't work for me..
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms

sinik420 said:
I always recommend not using rom manager for anything flashing related, most problems occur for people when they're using rom manager and get fixed when done through recovery or in this case terminal/adb
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img

I prefer my previous post using terminal
zadnica said:
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms

When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version

It took me two or three tries through terminal
Robin_216 said:
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms

Robin_216 said:
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
Click to expand...
Click to collapse
What the errors?

Worked like a charm thanks

Backups are significantly faster, thanks. (Flashed using fastboot)

zadnica said:
What the errors?
Click to expand...
Click to collapse
{
"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"
}
These are the errors that appear. I however managed to flash it with rom manager after some tries so it works now.
Sent from my Nexus S using XDA App

Robin_216 said:
These are the errors that appear. I however managed to flash it with rom manager after some tries so it works now.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I had the same issue. What helped for me was (in Terminal) :
su
mount -o rw,remount /dev/block/mtdblock3 /system
chmod 755 /system/bin/flash_image (wait for a minute)
(Reboot if the next step didn't work)
flash_image recovery /sdcard/RECOVERY.img
Click to expand...
Click to collapse

If I use the latest one, can I boot into recovery by using Rom manager? Will Rom manager detect my latest clockworkmod?
Accidentally sent from my Nexus S using XDA Premium App

Strangely, *immediately* after flashing the new recovery, I have begun to experience the Nexus S Google Voice Search bug. In the two months I've had the phone, this never happened - not even once.
This was with a two week old CM nightly, and a Matrix kernel.
Regardless - I'm hoping we'll start to see 2.3.6 kernels/roms come out soon which will fix it permanently. I'm just shocked that this issue popped up immediately after flashing the updated Clockwork.

Partitions not mounting @boot

Hey Guys,
first off i had this issue once before, but in that case i could restore a cwm backup from sd card and after sometime the problem fixed itself,
this time, i switched to bacon and i wanted to prepare the p880 for my sister to use, i downloaded zaiben, formatted my external sd card and put the rom on it, i rebooted to recovery wiped( i used the clean to install new rom in philz recovery if i remember correctly) everything and flashed the rom and exactly as last time, the flash seems to go way too fast and ofc i cant boot into android. now as i formatted my sd i have no backup to restore to. kdz flashing seems hopeless as well, as none of the tools recognize the phone when i put it in s/w upgrade mode,
for proof: i checked /system with aromafm and found it being empty after flashing a rom, i even tried extracting the rom zip on sd and moving the content from the zip to /system manually but after a recovery reboot, /system was empty again( only empty "bin" folder)
is somebody able to explain me why i have this issue and maybe how to fix it, or upload a clean cwm backup of whatever rom for me to use?
thx

Thanks for the help until now, really.......
In Further investigation i could find out that Roms ARE actually flashing properly, but /system and probably other partitions are not being mounted
At Boot or in recovery(manually mounting works Here) which is why aromafm reports an empty /system, after a manual Mount in either recovery itself of Aroma console i can See /system being filled with Rom files, now i will change the thread title accordingly, and now ASK: can i force /system to be mounted at Boot somehow? Someone pls answer this time

Okay this is ridicoulous.... why am i getting no help AT ALL?, thank you srsly.....
i investigated even further and suspected that something with fstab might be wrong, but fstab file looks fine to me:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 rw
if someone bothers to answer: what do you think?
pls help........

bump
please help

What recovery are you using? Are you sure your partitions aren't formatted to F2FS? (which would explain why the (F2FS-) recovery can mount the partitions but the system cannot as it expects an ext4 formatted partition rather than a F2FS formatted one)

i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions

~MaX~ said:
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
Click to expand...
Click to collapse
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?

laufersteppenwolf said:
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
Click to expand...
Click to collapse
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
{
"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"
}

~MaX~ said:
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
Click to expand...
Click to collapse
hmm, can you please grab me a kmsg? (from when it is stuck)

laufersteppenwolf said:
hmm, can you please grab me a kmsg? (from when it is stuck)
Click to expand...
Click to collapse
could you give me a quick how to on using adb in recovery from pc? i put the phone in sideload mode and tried "adb shell dmesg" but the output just was "error close" and using the command in aromafm terminal gave me an endless stream of log
(Also currently need to charge the phone a bit)
EDIT: NVM kmesg incoming....
okay next question, how can i dump the output into a file and how do i know where it hangs? time in recovery is not correct anymore(i set it once but after reboot it was wrong again, also in kmesg the time again seems to be different)

does that part help? i think it has to do with boot

~MaX~ said:
does that part help? i think it has to do with boot
Click to expand...
Click to collapse
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site

laufersteppenwolf said:
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
Click to expand...
Click to collapse
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?

~MaX~ said:
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
Click to expand...
Click to collapse
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..

laufersteppenwolf said:
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
Click to expand...
Click to collapse
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does

~MaX~ said:
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
Click to expand...
Click to collapse
1) yeah, I know, easiest way to fix that is to simply pull the battery and then boot into recovery
2) if the bootanimation shows up, it means the kernel as well as the ramdisk have booted properly. So in this case, you should be able to grab a last_kmsg as well as a logcat

hi
today I installed that application " LG-Optimus-4XHD-Recovery-v1.0.apk "
I have selected ClockworkMod Custom Recovery.
It showed that Operation is successful.
than i clicked on "Boot Recovery" to restart my Phone in CloclworkMod Custom Recovery.
since then I am getting only Starting animation. (LG LOGO).
nothing happens.
My battery was full when i performed this procedure
any help please

[Tool] - Easy Update and Adjust / Update: 22/12/2015 V1.3

P7 - Easy Update and Adjust​
Hello friends
I have built a tool for our phone.
Included are the following options:
::. [1] - Stock Firmware-Update with TWRP
::. [2] - Flash Recovery.img
::. [3] - Flash boot.img
::. [4] - Delete set_immutable.list / Full root
::. [5] - Start Recovery
::. [6] - Start Fastboot
::. [7] - Reboot Phone (in fastboot and ADB)
This tool simplifies working with adb / fastboot and flash the firmware, a recovery.img or Boot.img
Changelog:
Code:
22/12/2015 V1.3:
* Version without recovery.img
* Deleted automatic restart after flashing recovery or boot .img
17/05/2015 V1.3:
* New menu Item: Flash boot.img
* Translation "improved"
23/11/2014 V1.2:
* Now Supported P7-L00, L05, L07, L09, L10 (included recovery is for L10! - i dont know if L00... Use the same).
16/10/2014 V1.1:
* Fully translated to English
* stockrecovery.img included
* At the start of the program is checked whether this is in the correct directory
Downloads:
Code:
22/12/2015: [ATTACH]3585481._xfImport[/ATTACH]
17/05/2015: [ATTACH]3317262._xfImport[/ATTACH]
23/11/2014: [ATTACH]3035237._xfImport[/ATTACH]
16/10/2014: [ATTACH]3018266._xfImport[/ATTACH]
15/10/2014: [ATTACH]3016196._xfImport[/ATTACH]
Instructions:
Code:
1. Insert P7-Easy_Update_and_Adjust.exe into your ADB Folder.
2. If you want to flash a special recovery put the .img File into the "recovery" Folder.
3. If you want to flash a special boot.img put the .img File into the "boot" Folder.
4. Now you can start...
On start of this tool a recovery folder will be created with stockrecovery.img in it.
This is the folder who you can put in all your recoverys. If you will be flash a recovery you see a menu of all and can choose yours.
For "[4] - Delete set_immutable.list / Full root" - You need Busybox on your Phone! Download and install it from Playstore.
Descriptions:
Code:
ADB Mode: Phone is complete booted up and USB debugging is enabled.
On your phone MTP or HiSuite mode must be enabled - Non mass storage.
Recovery Mode: Phone is in recovery e.g. TWRP.
Fastboot Mode: Phone is in bootloader.
Screenshots:
{
"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"
}
If someone needs help, says me know in this thread.​
Use @ your own risk!
regards,
87Insane

87insane said:
Hello friends
I have built a tool for our phone.
Click to expand...
Click to collapse
Looks good!
I can help with translations if you want.

GawDroid said:
Looks good!
I can help with translations if you want.
Click to expand...
Click to collapse
Hi,
english is no problem...only my time is the problem.
But tomorrow, i think its ready. THX for your help with ADB shell.
Sent from my HUAWEI P7-L10 using XDA Free mobile app

Hi,
does it mean that by using your tool I will be able to flash a new factory ROM (dload\Update.app format), even if I had put a TWRP recovery to my P7?
Without changing back the TWRP to stock recovery?

ctibor said:
Hi,
does it mean that by using your tool I will be able to flash a new factory ROM (dload\Update.app format), even if I had put a TWRP recovery to my P7?
Without changing back the TWRP to stock recovery?
Click to expand...
Click to collapse
Yes...no...
This tool makes what you make manuelly. Go back to stock, flash, and back to twrp. With backup and delete immutable after update.
Instructions are in this tool...you can easy try this...i hade to do this manuel.
Sent from my HUAWEI P7-L10 using XDA Free mobile app

ctibor said:
Hi,
does it mean that by using your tool I will be able to flash a new factory ROM (dload\Update.app format), even if I had put a TWRP recovery to my P7?
Without changing back the TWRP to stock recovery?
Click to expand...
Click to collapse
Are you checked that and be happy? I would like to create a tool that can use anybody and need ideas from you and other users

what about this:
Recovery_P7_all.exe v 1.4
http://4pda.ru/forum/index.php?showtopic=573880&st=2240#entry35842662

habbaz said:
what about this:
Recovery_P7_all.exe v 1.4
http://4pda.ru/forum/index.php?showtopic=573880&st=2240#entry35842662
Click to expand...
Click to collapse
the tool I do not know. do you have experience with it? unfortunately I can not speak Russian.

87insane said:
the tool I do not know. do you have experience with it? unfortunately I can not speak Russian.
Click to expand...
Click to collapse
no, i don't know Russian language.
but you can use the Google translator.

habbaz said:
no, i don't know Russian language.
but you can use the Google translator.
Click to expand...
Click to collapse
Yes i do this but i cant open a exe file in my Android. Its a Russian exe file...iam safety ^^

Hi, did someone tested the tool? ( the first one) does it work? Because I want to install TWRP and I don't want to risk ?

If your bootloader is open, no Problem.
Put the twrp recovery .img in the recovery folder and choose flash recovery.
Only ADB and fastboot commands. If you have trouble - Plesse give me a info.

Does this program works alone? Do I need android SDK? Thank you for support!

luca3011 said:
Does this program works alone? Do I need android SDK? Thank you for support!
Click to expand...
Click to collapse
On my first post you can see it.
Instructions:
1. Insert P7-Easy_Update_and_Adjust.exe into your ADB Folder.
2. If you want to flash a special recovery put the .img File into the "recovery" Folder.
3. Now you can start...
This tool needs ADB and fastboot.

Thank you so much!

to me it does not work
I always have, only this
I want this

palokm said:
to me it does not work
I always have, only this
I want this
Click to expand...
Click to collapse
What do you want to do? If you want the second your phone has to be in ADB mode.
You are in fastboot mode ...
ADB mode = phone complete bootet with USB debugging activated.

I can not get into the ADB

palokm said:
I can not get into the ADB
Click to expand...
Click to collapse
Can you explain me what are you doing?
Wich phone do you have - L10 or another?

I'd like you to explain
but I do not know English
I use a translator
I have a L10
Do instructions

[TUT][HOW-TO] How to root Xiaomi Redmi2 and install CWM

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