Database Users

Remove CityID after root and recovery flash

So I've rooted and installed the new recovery on my incredible. I want to remove CityID now, forgot to after root. When I launch recovery and run adb devices it shows my device. I then run adb shell, immediately getting the # for su (instead of the $ prompt for non su access). I execute /system/bin/rm /system/app/CityID.apk as instructed by the wiki and get /sbin/sh: /system/bin/rm: not found. I browse to /system/bin and do a listing and see nothing. So am I doing something wrong?
**EDIT**
Forgive my ignorance, but I forgot to mount system in the partitions menu of recovery. Doubtful this would be of any help to anyone, but there ya go.

Also in the How To:
StirCwazy said:
So I've rooted and installed the new recovery on my incredible. I want to remove CityID now, forgot to after root. When I launch recovery and run adb devices it shows my device. I then run adb shell, immediately getting the # for su (instead of the $ prompt for non su access). I execute /system/bin/rm /system/app/CityID.apk as instructed by the wiki and get /sbin/sh: /system/bin/rm: not found. I browse to /system/bin and do a listing and see nothing. So am I doing something wrong?
**EDIT**
Forgive my ignorance, but I forgot to mount system in the partitions menu of recovery. Doubtful this would be of any help to anyone, but there ya go.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=709220 - It's a few posts down, but will update first post later today.

~# ???

hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...

ezy1022 said:
hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...
Click to expand...
Click to collapse
clockworkmod recovery is root by default, there is no su cause you don't need it. # = su prompt versus $ = user prompt...

Shadowmite said:
clockworkmod recovery is root by default, there is no su cause you don't need it. # = su prompt versus $ = user prompt...
Click to expand...
Click to collapse
So all is good?

Yes....all is good. Reported.

I'm not issuing warnings yet for questions posted in development which may fall under that scope. I have requested a Q&A sub-forum be created for DI. We'll see how that pans out. Until then, please post questions in the thread where you believe your issue is coming from. Otherwise, please post questions in the DI/General sub-forum until a Q&A forum is created. Thanks!

ezy1022 said:
hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...
Click to expand...
Click to collapse
i have that problem right now. i have the original root(via loop.bat) in place, nothing else. i get the symbol "~#" too when i try to enter the adb shell while in recovery. adb devices show that my phone is attached and i am able to execute most commands. but there are some commands like "cd" that only work in the shell.
so we are going to need to resolve this eventually.
yes, you do not need su in recovery but you will need adb shell.
if there's anyone out there who can help us with this "~#" when typing adb shell in recovery, it would be greatly appreciated.

If you see that then that means you are using adb shell. No need for Su, but if you're removing apps etc mount the /system in the partitions menu of clockworkmod. Then cd /system/app to edit your apps.
Sent from my ADR6300 using XDA App

Bricked Phone?

Ok I got A Problem. Went to flash a new rom after backing my current one up with rom manager everything went fine till I went to flash it and now it says
E: Failure at line 7 symlink dumpstate SYSTEM:bin/dumpcrash
I dont have a working phone. Tried several different roms and nothing.
what do I need to do??

can u boot in to recovery mode " vol up + power button " ? and dont use Clockworkmod recovery as its known to have issues with the eris.
use the other recovery.
Thanks T.A.

Yes I can Boot into recovery thats it.
How do I go about Flashing a New Recovery Manager

Topaz is right.... Amon_RA FTW !

How do I install that now though. I have been searching through forums looking cant find a step by step
Forgot to say I was a Leaker before they found the method.
would this work
http://forum.xda-developers.com/showthread.php?t=725096&highlight=Flash+Amon's+recovery

metzy75 said:
How do I install that now though. I have been searching through forums looking cant find a step by step
Forgot to say I was a Leaker before they found the method.
would this work
http://forum.xda-developers.com/showthread.php?t=725096&highlight=Flash+Amon's+recovery
Click to expand...
Click to collapse
might work, I imagine you could also try this....
http://forum.xda-developers.com/showthread.php?t=725047
this gives you the S-OFF bootloader and Amon_RA for recovery
you might wait to see if others weight in on the best approach here.

Already turned S-OFF the only reason I have clock work is because my noobie ass used rom manager for convience

metzy75 said:
Already turned S-OFF the only reason I have clock work is because my noobie ass used rom manager for convience
Click to expand...
Click to collapse
"noobie ass" is funny.
jcase's approach in your link is probably all you need then

Phones about to get thrown at the wall. Nothing is working, do the adb push moves file fine then couple commands down it says not there

metzy75 said:
Phones about to get thrown at the wall. Nothing is working, do the adb push moves file fine then couple commands down it says not there
Click to expand...
Click to collapse
if you do
adb devices
does its show a device HTCxxxxxxxxxx (some alphanumeric)?

Do this
Code:
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
adb reboot recovery
try this in fastboot ( SEND + POWER )
not sure u can push files into /data/local/
hopefully it will work and if not and all fails.
put a rom on sd card and boot into recovery and hopefully clockworkmod recovery will flash it.

Yep, really have no idea what to do. I run the commands in what you gave me and the stupid thing says file its there when i use root command to navigate there its right there. idk whats going on.

TopazAaron said:
Do this
Code:
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
adb reboot recovery
try this in fastboot ( SEND + POWER )
not sure u can push files into /data/local/
hopefully it will work and if not and all fails.
put a rom on sd card and boot into recovery and hopefully clockworkmod recovery will flash it.
Click to expand...
Click to collapse
doesn't show its connected, I have fastboot USB showing on the eris
tried flashing many roms no good same error

http://forum.xda-developers.com/showthread.php?t=651669
May help in that it includes the Amon_RA file and offers a different approach...
good luck

have you ever heard of the jitterbug?

Sjflowerhorn said:
have you ever heard of the jitterbug?
Click to expand...
Click to collapse
Idk what a jitter bug has to do with this. But I got the recovery changed but nothing still flashes.
Got to line 8 instead of line 7
says cant chown/mod /system/bin
(no such file or directory
E: failure at line 8
set_perm_recursive 0 2000 07550

Sjflowerhorn said:
have you ever heard of the jitterbug?
Click to expand...
Click to collapse
holy crap... i almost fell outta my chair!!!! LOL (i used to tell this lady at work all the time.... you NEED a jitterbug!!!).
------------------------------------------------------------------------------------------------------------
in any case...
metzy75... you said you backed up (a NAND backup i'm assuming)... are you able to restore your backup? or same failure? different message?

metzy75 said:
Idk what a jitter bug has to do with this. But I got the recovery changed but nothing still flashes.
Got to line 8 instead of line 7
says cant chown/mod /system/bin
(no such file or directory
E: failure at line 8
set_perm_recursive 0 2000 07550
Click to expand...
Click to collapse
what ROM are you trying to flash?

zach.xtr said:
what ROM are you trying to flash?
Click to expand...
Click to collapse
Just Official eris one that came with that all in one zip. and plain jane as wwell
Plain Jane fails at line 7 and offical eris line 8

tenzomonk said:
holy crap... i almost fell outta my chair!!!! LOL (i used to tell this lady at work all the time.... you NEED a jitterbug!!!).
------------------------------------------------------------------------------------------------------------
in any case...
metzy75... you said you backed up (a NAND backup i'm assuming)... are you able to restore your backup? or same failure? different message?
Click to expand...
Click to collapse
Backups all failed.

Rooting... just getting su?

Hi there...
I'm finally considering rooting, however all the guides lead to flashing a custom rom... but actually I don't want to flash a custom ROM, I want to keep everything as it is, with the difference that I (and preferably only I) can become super user on the shell when I need to do some changes (like fixing the stock widget bug in the internal database).
I've read this right now:
http://forum.xda-developers.com/showthread.php?t=724741
And they say I can flash this files called EngTools.zip
Does this also work on the Hero assuming the guide (PossibleGSMRoot or something... fromt he villainforum) works on my phone?
I don't even want to permanently have some kind of AmonRa blabla recovery boot image on my phone. If I need it while I get root that's fine, but I want to get rid of it afterwards. I really don't need root for any applications liek overclocking etc. etc. just for smaller dives into the files system and changes there via adb.

olafos said:
Hi there...
I'm finally considering rooting, however all the guides lead to flashing a custom rom... but actually I don't want to flash a custom ROM, I want to keep everything as it is, with the difference that I (and preferably only I) can become super user on the shell when I need to do some changes (like fixing the stock widget bug in the internal database).
I've read this right now:
http://forum.xda-developers.com/showthread.php?t=724741
And they say I can flash this files called EngTools.zip
Does this also work on the Hero assuming the guide (PossibleGSMRoot or something... fromt he villainforum) works on my phone?
I don't even want to permanently have some kind of AmonRa blabla recovery boot image on my phone. If I need it while I get root that's fine, but I want to get rid of it afterwards. I really don't need root for any applications liek overclocking etc. etc. just for smaller dives into the files system and changes there via adb.
Click to expand...
Click to collapse
Hmmm. If you are on 2.1, then you can use the GSM root i posted over at VR. The recovery needs to be flashed to the phone though, so you can flash zips to the phone from there.
As for your wish to get rid of the patched recovery afterwards, you're missing out a lot, but if you can find the stock recovery img file, you can simply flash that using
"flash_image recovery FilenameHero.img" via the phone's shell or adb (once rooted, presuming you added the flash_image binary).
As for that file, I don't know, as I've never checked if that will work on the hero.
I'd be inclined to say DON'T TRY IT, since it will contain a kernel, and flashing the wrong kernel can brick your device's radio, essentially ruining it.
But if you locate the correct files for the GSM hero, and package them similarly, you could flash that onto your phone via recovery
Bear in mind the stock HTC ROM is basically full on the system partition, so you might have issues actually fitting the files on.

I've been a lurker for some time here but just before I had thought about exactly the same issue as OP... I always wondered why there's no way to just get root access temporarily. Most people told me I'd have to flash a custom ROM.
So today I finally looked into the matter and based on your (anon2122) post on VillainROM and the Eris exploits etc. I managed to do exactly what I wanted... and thought it's time to get an account...
I only really needed root for the Stock app currency issue: [HTTP]://forum[DOT]xda-developers[DOT]com/showthread[DOT]php?t=719149 which I was now able to fix.
HTC Hero GSM soft root guide by ixampl
(... credits belong to / based on: [HTTP]://www[DOT]villainrom[DOT]co[DOT] uk/viewtopic[DOT]php?f=110&t=2096)
1 Flashing a custom recovery image
1.1 Backup (1)
Code:
adb shell mkdir /data/local/backup
adb shell cat /data/local/rights/mid.txt > /data/local/backup/mid.txt
1.2 Uploading custom recovery image and image flashing tool and setting correct permissions
Code:
adb push recovery-RA-hero-v1.6.2.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery-RA-hero-v1.6.2.img
adb shell chmod 777 /data/local/flash_image
1.3 Center piece of the permissions exploit for the recovery ROM
Code:
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
1.4 Normal reboot
Code:
adb reboot
1.5 Now that the recovery ROM (/dev/mtd/mtd1) is accessible: Backup (2)
Code:
adb shell cat /dev/mtd/mtd1 > /data/local/backup/recovery.img
1.6 Flashing the previously uploaded custom recovery image
Code:
adb shell /data/local/flash_image recovery /data/local/recovery.img
1.7 Rebooting into recovery mode
Code:
adb reboot recovery
2 Adding root shell (optional)
2.1 Mounting all devices
Code:
adb shell mount -a
2.2 Adding rootsh
Code:
adb shell cat /system/bin/sh > /system/bin/rootsh
adb shell chmod 4755 /system/bin/rootsh
2.3 Rebooting into system
Code:
adb reboot
After this you can flash the recovery.img you backed up in step 1.5 just as you flashed in step 1.6 (adjust the parameters accordingly).

ixampl said:
I've been a lurker for some time here but just before I had thought about exactly the same issue as OP... I always wondered why there's no way to just get root access temporarily. Most people told me I'd have to flash a custom ROM.
So today I finally looked into the matter and based on your (anon2122) post on VillainROM and the Eris exploits etc. I managed to do exactly what I wanted... and thought it's time to get an account...
I only really needed root for the Stock app currency issue: [HTTP]://forum[DOT]xda-developers[DOT]com/showthread[DOT]php?t=719149 which I was now able to fix.
HTC Hero GSM soft root guide by ixampl
(... credits belong to / based on: [HTTP]://www[DOT]villainrom[DOT]co[DOT] uk/viewtopic[DOT]php?f=110&t=2096)
1 Flashing a custom recovery image
1.1 Backup (1)
Code:
adb shell mkdir /data/local/backup
adb shell cat /data/local/rights/mid.txt > /data/local/backup/mid.txt
1.2 Uploading custom recovery image and image flashing tool and setting correct permissions
Code:
adb push recovery-RA-hero-v1.6.2.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery-RA-hero-v1.6.2.img
adb shell chmod 777 /data/local/flash_image
1.3 Center piece of the permissions exploit for the recovery ROM
Code:
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
1.4 Normal reboot
Code:
adb reboot
1.5 Now that the recovery ROM (/dev/mtd/mtd1) is accessible: Backup (2)
Code:
adb shell cat /dev/mtd/mtd1 > /data/local/backup/recovery.img
1.6 Flashing the previously uploaded custom recovery image
Code:
adb shell /data/local/flash_image recovery /data/local/recovery.img
1.7 Rebooting into recovery mode
Code:
adb reboot recovery
2 Adding root shell (optional)
2.1 Mounting all devices
Code:
adb shell mount -a
2.2 Adding rootsh
Code:
adb shell cat /system/bin/sh > /system/bin/rootsh
adb shell chmod 4755 /system/bin/rootsh
2.3 Rebooting into system
Code:
adb reboot
After this you can flash the recovery.img you backed up in step 1.5 just as you flashed in step 1.6 (adjust the parameters accordingly).
Click to expand...
Click to collapse
That is a nice method.
I've long thought about making something similar, so maybe today I'll try, as an idea has come back to me...
I am thinking that I can avoid the whole recovery flashing, though I'm not going to say the idea till I've thought it through, as someone might try it before I realise how stupid an idea it is...
But I'll certainly see if it can get permanent root sorted out on the phone, although it won't give root adb access, as that is defined in the boot.img, though I guess I could flash that while I'm at it...
Good work.

Thanks!
Yes, a method to (safely) acquire super user access without flashing anything would be highly appreciated There's a small risk involved with flashing. Granted it usually causes no issues, but there is the slight possibility of bricking your phone.
Good work.
Click to expand...
Click to collapse
Thanks, although - as you know - I really didn't do anything special there
[...] although it won't give root adb access [...]
Click to expand...
Click to collapse
Yes, that's a minor annoyance, but really minor ... for the currency fix I naturally couldn't do
Code:
adb pull /data/data/com.htc.dcs.service.stock/databases/stock.db stock.db
or
Code:
adb push stock.db /data/data/com.htc.dcs.service.stock/databases/stock.db
but it's not that hard to just work around that via /data/local:
Code:
adb shell
$ rootsh
# cat /data/data/com.htc.dcs.service.stock/databases/stock.db > data/local/stock.db
then pull from there etc.
I really think "rooting" is a misnomer for most of the current guides.
I can see that most people "root" their phone in order to get custom ROMs (and I have no issue with that, it's just too much overkill for someone who just wanted to fix a small bug ) but In fact most people don't care about rooting per se, they care about flashing a recovery image which enables them to flash custom ROMs.
I actually wanted to try:
Code:
adb shell ln -s /dev/mtd/mtd3 /data/local/rights/mid.txt
...and see what happens if I remount after boot. If it causes the system to follow back the link with user permissions for the recovery ROM, maybe the system ROM could be (write-)accessed as well. Then again, it was my first venture into rooting so naturally there would have been no way to fix a broken system image safe for reflashing the 1.5 RUU.
Do you have any details about what the original purpose of the (original) mid.txt was? I mean, it was there, sitting in a directory named rights... quite an invitation (of course, we didn't actually "set" rights in that file or anything for the exploit, but still...)
Is it safe to delete mid.txt and will it be recreated with some default values by the system?
Click to expand...
Click to collapse

[HOW TO] Flashing ClockworkMod via ADB

So was helping someone flash ClockworkMod via ADB in another thread, just thought if I made a topic for it, everyone can see it so if people have any issues they can always use this method instead.
Anyway, here are the instructions:
The 'flash_image' is within the attached zip file! Use the file within the zip file, NOT the zip file itself
The 'recovery.img' is your chosen recovery file, get this off ClockworkMods website or if you have a copy use that. Then when flashing the recovery image where ever it says 'recovery.img' replace that with the name of the recovery file.
Put the recovery image and the flash_image on the root of your C drive.
So,
(make sure you're in the command prompt and have changed directory to where the adb file is)
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
It has now been flashed successfully
Hope this is of use to some people

Thanks! Very helpful.

varsaljr said:
Thanks! Very helpful.
Click to expand...
Click to collapse
As repeated in many places, press the thanks button instead of posting thanks

Hello, when i enter abd shell, then su.
I get acces denied..
what to do? :O

MrKiller2010 said:
Hello, when i enter abd shell, then su.
I get acces denied..
what to do? :O
Click to expand...
Click to collapse
u rooted and have superuser on your phone??

No i dont some one told me to do this cause my screen freezes when im trying to root it. Chek the How to root your blade.
Sent from my ZTE-BLADE using xda premium

You must be rooted for this, root using z4root or something
Sent from my ZTE-BLADE using Tapatalk 2

MrKiller2010 said:
No i dont some one told me to do this cause my screen freezes when im trying to root it. Chek the How to root your blade.
Sent from my ZTE-BLADE using xda premium
Click to expand...
Click to collapse
Dude i didn't know u weren't rooted yet. U don't need to use adb to root. Just Google z4root modaco and click on the first link. Install z4root and permanent root it. Don't forget to install rom manager and flash cwm from within it

Oh, well z4root doesn't work for me cause i got 2.3.5 i heard that the only way to root my blade is this: http://forum.xda-developers.com/showthread.php?t=1319257
and that doesn't work, it freezes when i enter the command "adb reboot bootloader" it reboots and stay on the ZTE logo and freezes. :S

MrKiller2010 said:
Oh, well z4root doesn't work for me cause i got 2.3.5 i heard that the only way to root my blade is this: http://forum.xda-developers.com/showthread.php?t=1319257
and that doesn't work, it freezes when i enter the command "adb reboot bootloader" it reboots and stay on the ZTE logo and freezes. :S
Click to expand...
Click to collapse
That's what it is supposed to do. That's it in fastboot mode. You need to go on to the next step at that point.

Well when i enter next command nothing happends.
Sent from my ZTE-BLADE using xda premium

matt4321 said:
You must be rooted for this, root using z4root or something
Sent from my ZTE-BLADE using Tapatalk 2
Click to expand...
Click to collapse
So what's the point in doing it?
Just install rom manager & use that instead.
---------- Post added at 04:17 PM ---------- Previous post was at 04:16 PM ----------
MrKiller2010 said:
Well when i enter next command nothing happends.
Sent from my ZTE-BLADE using xda premium
Click to expand...
Click to collapse
You need to install drivers for fastboot if you use Windows. Sometimes you might need to unplug the usb, then plug it back in again & try fastboot again.
It should at least give an error.

wbaw said:
So what's the point in doing it?
Just install rom manager & use that instead.
Click to expand...
Click to collapse
What's the point in using fastboot to flash clockworkmod, it's just another way of doing it, some may prefer other ways (yeah via rom manager is a lot easier i know) but spread the knowledge, may be of use to some people.

matt4321 said:
What's the point in using fastboot to flash clockworkmod, it's just another way of doing it, some may prefer other ways (yeah via rom manager is a lot easier i know) but spread the knowledge, may be of use to some people.
Click to expand...
Click to collapse
You don't need your phone to be rooted to use fastboot, it's a method for new stock roms that have all the common root exploits fixed.
So, what's the point in this method when using Rom Manager is much easier? If you've already rooted your phone then this has to be one of the hardest possible ways to install clockworkmod.

wbaw said:
You don't need your phone to be rooted to use fastboot, it's a method for new stock roms that have all the common root exploits fixed.
So, what's the point in this method when using Rom Manager is much easier? If you've already rooted your phone then this has to be one of the hardest possible ways to install clockworkmod.
Click to expand...
Click to collapse
I was never able to get fastboot working for my blade, always had driver issues, yet adb was fine. So I was able to use this method to flash and try the clockworkmod recovery touch that was released for us (turned out to be useless haha) but that couldn't be done via rom manager (well yeah, but you had to pay and i'm a poor student) so that's an example of when it could be useful.
point aside this is just another way, I just want people to learn as i am here to learn too.

Permission Denied
I need to flash CWM recovery using this adb method since I dont have data on the phone(Videocon Zeus V7500.. a clone of Commtiva Z51).
I have all the files in the right places but when I put the first command I get the following error :
I:\>adb push c:\flash_image /sdcard/
failed to copy 'c:\flash_image' to '/sdcard//flash_image': Permission denied ,
What permissions do I have to grant?

Try adb push c:/flash_image /sdcard/flash_image
Sent from my RACERII using xda app-developers app

Nevermind I figured it out, the problem was that I had mounted sd card to PC and I guess that was causing the problems.
I got it to work and have flashed CWM recovery now
Code:
I:\>adb push c:\flash_image /sdcard/
751 KB/s (26172 bytes in 0.034s)
I:\>adb push c:\recovery-clockwork-2.5.1.3-z71.img /sdcard
2444 KB/s (3831808 bytes in 1.531s)
I:\>adb shell
$ su
su
# su
su
# mount -o remount, rw /system
mount -o remount, rw /system
# cp /sdcard/flash_image /system/bin
cp /sdcard/flash_image /system/bin
# cd /system/bin
cd /system/bin
# chmod 777 flash_image
chmod 777 flash_image
# flash_image recovery /sdcard/recovery-clockwork-2.5.1.3-z71.img
flash_image recovery /sdcard/recovery-clockwork-2.5.1.3-z71.img
Thanks you very much for this thread

how to??
matt4321 said:
So was helping someone flash ClockworkMod via ADB in another thread, just thought if I made a topic for it, everyone can see it so if people have any issues they can always use this method instead.
Anyway, here are the instructions:
The 'flash_image' is within the attached zip file! Use the file within the zip file, NOT the zip file itself
The 'recovery.img' is your chosen recovery file, get this off ClockworkMods website or if you have a copy use that. Then when flashing the recovery image where ever it says 'recovery.img' replace that with the name of the recovery file.
Put the recovery image and the flash_image on the root of your C drive.
So,
(make sure you're in the command prompt and have changed directory to where the adb file is)
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
It has now been flashed successfully
Hope this is of use to some people
Click to expand...
Click to collapse
friend plss suggest me that how to use this flash_image and where should i put it
in mobile system or in pc drive c
plsss tell me clearly because when i use it in cmd it says su not found whts the mean of this plss tell me clearly one by one step
i am not able to understnd
pls pls pls help me
---------- Post added at 04:09 PM ---------- Previous post was at 03:55 PM ----------
mandloihitesh said:
friend plss suggest me that how to use this flash_image and where should i put it
in mobile system or in pc drive c
plsss tell me clearly because when i use it in cmd it says su not found whts the mean of this plss tell me clearly one by one step
i am not able to understnd
pls pls pls help me
Click to expand...
Click to collapse
heyy plss i m confused in command
i dont know what commnds should i usee
plss help me
plss
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
saaransh9 said:
u rooted and have superuser on your phone??
Click to expand...
Click to collapse
ya i rooted my phone and superuser is also installed on my phone then wht to do
????
clockworkmod is not working in recovery manager also
said unrecognized

thanks for this. Got me out of a jam