Database Develop

Help!! Rooting problem...i think

Okay, I've been trying to root my sprint hero for 3 days now. I flashed it to Cricket service actually. So here are the commands I am using:
C:\Users\Ashton>cd\
C:\>cd AndroidSDK\Tools\
C:\AndroidSDK\tools>adb devices
List of devices attached
HT02AHF00747 device
C:\AndroidSDK\tools>adb shell chmod 0755 /data/local/asroot2
C:\AndroidSDK\tools>adb shell
$ /data/local/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
[+] Using new pipe_inode_info layout
Opening: /proc/627/fd/3
SUCCESS: Enjoy the shell.
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#cd /system/bin
cd /system/bin
#cat sh > su
cat sh > su
# chmod 4775 su
chmod 4775 su
#
Okay, that's exactly what's displayed on my screen. I didn't put the # or $ signs in there. That's just what appeared as I was typing the commands. When I try to flash a recovery image, it won't install. I get a Signed Failure error. Any ideas? What am I doing wrong? Also, does a cricket rom for sprint hero exist? Or should I use a Non-Sprint ROM? I mean, it's a sprint hero, but it has been flashed. Thanks Everyone!

This has nothing to do with Development.

...sorry, i thought...
I'm not sure where else to post it. I thought it did, since the rooting guides and roms are posted under Development.

Would the General are be more appropriate? I'm not trying to post in the wrong places. But I don't want to post there and get the same response. lol, Just need help. Not looking to tick anyone off.

This has nothing to do with Development.
Click to expand...
Click to collapse
Not being mean but who made you the cdma hero police.. you never actually help anyone. just tell them they are wrong for posting here.
to the OP, try to type
exit
adb shell
then the rest of flashing instructions
Sent from my HTC Heroc using the XDA mobile application powered by Tapatalk

Thanks Jus10o. I'll try that. Sometimes I miss windows mobile. Lol, flashing android is a pain.

ashton2091 said:
Thanks Jus10o. I'll try that. Sometimes I miss windows mobile. Lol, flashing android is a pain.
Click to expand...
Click to collapse
I came from WinMo as well. Trust me, once you get the hang of it, it's easier and faster than RUUing every time.

Okay, I tried the above. Here's what I happened. I am rooted (i think). I used a file explorer to to backup the recovery image. It said it was successful. Then I rebooted into the Recovery Menu. Still looks like the stock one. Three lines of options with blue fonts. I try updating the image from there, but all I get is "Can't open /cache/recovery/command". fustrated, It sucks to be a noob all over again.

I forgot to mention, I also did a factory reset before trying to write the image as suggested in the instructions.

Thread moved.

Jus10o said:
Not being mean but who made you the cdma hero police.. you never actually help anyone. just tell them they are wrong for posting here.
to the OP, try to type
exit
adb shell
then the rest of flashing instructions
Sent from my HTC Heroc using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
ROFL ROFL ROFL You GO Girl! What rock have you been under? I do nothing BUT help in these forums. Also, I DID tell the OP they posted in the wrong section. Im pretty sure when I said "This has nothing to do with Development." that meant he posted in the wrong section. By the way, the mods made everyone the CDMA Hero Police. Apparently, you cant read the forum rules and guidelines either. Here, let me help you,
http://forum.xda-developers.com/showpost.php?p=6372744&postcount=2
From Ryan's quote,
Mods, including myself, are not here to keep the forum organized after the fact, we need your help to keep it organized, clean and grouped.
To the dedicated members that care to keep this forum, subforums included, clean and organized and grouped.
Please start reporting threads to the mods to take action. Using this button.
Click to expand...
Click to collapse

Look everyone, don't get at each other like that. It's not cool. Lol, it's okay. I really didn't know. I mean, the fact that the rooting section was here, I thought it was okay to post here. But hey, it's in the right place now. I understand the forums can't be trashed with everything posted everywhere. Lol, really it's cool.

ashton2091 said:
Look everyone, don't get at each other like that. It's not cool. Lol, it's okay. I really didn't know. I mean, the fact that the rooting section was here, I thought it was okay to post here. But hey, it's in the right place now. I understand the forums can't be trashed with everything posted everywhere. Lol, really it's cool.
Click to expand...
Click to collapse
Dont boot into recovery, just boot up your phone and do this....
Put the New recovery image on your sdcard, by either opening it up on your computer. Or put the file into your c:/android-sdk/tools folder and type this
adb push NameOfRecovery.img /sdcard/ (make sure you name recovery the exact name as it appears on your computer or rename it to just "recovery" so its easy to remember)
once its on your sdcard and your phone is on charge only.. Not mounted to the computer type this
adb shell
cd /sdcard/
flash_image recovery NameOfRecovery.img

Okay, I think I know what the prob is now. Even if it's not the prob, it will have to be fixed. I have the wrong stock image. I have v1.56 which I think blocks rooting. Trying to downgrade. Thanks Everyone

{Development}Evo-Derived one click root method.

Current Status 7/14
Without the NAND being unlocked, we are unable to re-write to the recovery partition. Other than that everything is working good. Unlocked NAND=One Click Root!
This method is directly based on the new root process for the Eris released on xda.
Original thread can be found here
The following information is taken directly from the thread mentioned above with some small modifications by me for the Incredible.
Big thanks to tereg for the toolkit and the guys who rooted the EVO with a file write/chmod race condition exploit that gave me the idea for this.
jcase noticed that a race isn't actually nessisary to exploit the chmod 777 on the file I've been working with, simplifying the script alot.
I used the files from the adb development pack that Tereg put together. Download them here. You don't need them for this root process as long as you have a working adb install.
You will need adb access. Install the android sdk for your platform (macos, windows, linux) get it for your OS here.
If you don't know how to install the sdk, search xda, there are a ton of howtos for that.
Files to download:
hack-v5-DINC.zip
A ROM file
Android SKD (skip if you have a working adb)
Instructions for linux/OSX.
Have adb in your path, or move the files contained in hack-v5-DINC.zip into your sdk/tools directory so your pushes will work properly.
FOR ALL OS's Make sure your phone has Applications->Development->USB Debugging turned on.
Do NOT have your phone in Disk Drive Mode, have it in Charge Only.
Open a terminal window in your /tools/ directory. Type this at the prompt.
Code:
sh runinlinux.sh
This will take a few minutes, follow the instructions on your screen.
If you get adb: command not found, edit runinlinux.sh and change every
Code:
#/bin/bash
adb push flash_image /data/local/
adb push recovery.img /data/local/
adb push testfile /data/local/
etc...
to
Code:
./adb push flash_image /data/local/
./adb push recovery.img /data/local/
./adb push testfile /data/local/
etc...
Instructions for windows (thanks tereg!)
Download the hack.zip file and extract it to the desktop. So, you have a folder on the desktop called hack. I would recommend moving or copying those files (EDIT: that are contained in the hack folder) to the C:\android-sdk-windows\tools folder. Why? Because the script runs "adb ____" commands, and unless you've set up adb to be able to run anywhere within the command prompt, the script won't run. So, it will universally work if the files in the hack folder are placed in C:\android-sdk-windows\tools
So, open a command prompt by pressing WindowsKey+R, or going to Start-Run (in WinXP) and typing
Code:
cmd
in the text box there and press OK
If you are in Windows Vista/Windows 7, go to the Start Menu, then type in
Code:
cmd
in the search bar in the lower right-hand corner of the start menu and press enter, and locate Command Prompt in the search results, or go to Start -> All Programs -> Accessories -> Command Prompt
Type
Code:
cd C:\android-sdk-windows\tools
and press enter
Now, I recommend pushing the ROM you want to flash to the SD card now.
Code:
adb push ROM.zip /sdcard
Then, type
Code:
runindos.bat
to execute the script.
You might have to run it 2 or 3 times for it to work. If it fails, just reboot the phone normally, then run
Code:
runindos.bat
again once the phone is booted back up and you're ready.
----------(Thanks again tereg!)
It will scan for a long time, give it at least 5 minutes. If it doesn't come back after 5 minutes cntrl +c to stop it, start the process again. MOST PEOPLE HAVE TO RUN THIS AT LEAST TWICE!
If your device reboots into a new screen with options on it, you now have root in recovery mode. At this point you will be flashing your Incredible's brains, so YOUR PHONE WILL BE BLANK AFTER LOADING A NEW ROM! All of your apps/numbers will be gone from the phone.
I suggest a nand backup first.
Download and copy one of these ROM's to your sdcard as update.zip and flash it with flash zip from sdcard by selecting "Install zip from sdcard".
The first boot after loading a new ROM takes quite a while to show any activity to the screen. Give it a good 5 minutes before you start wondering if it's ever going to come back.
---
runinlinux.sh
---
Code:
#/bin/bash
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 rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
echo "Files copied and permissions set, rebooting HTC Andriod 2.1"
adb reboot
echo "Your phone will now reboot into normal mode, then reboot into recovery mode. If it does not reboot the second time, wait 10 minutes and manually reboot and begin again."
echo "Your phone is now rebooting in Rooted Recovery mode, do a backup and load your ROMs"
adb wait-for-device
adb shell /data/local/flash_image recovery /data/local/recovery.img
adb reboot recovery
---
runindos.bat
---
Code:
@echo off
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 rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
echo "Files copied and permissions set, rebooting HTC Andriod 2.1"
echo "Your phone will now reboot into normal mode, then reboot into recovery mode. If it does not reboot the second time, wait 10 minutes and manually reboot and begin again."
adb reboot
adb wait-for-device
echo "Your phone is now rebooting in Rooted Recovery mode, do a backup and load your ROMs"
adb shell /data/local/flash_image recovery /data/local/recovery.img
adb reboot recovery
This thread is intended to be an think-tank, similar to the one on the eris forums where I got the idea from. Let the ideas flow!

has this been tested to work on the INC? if not why has this been posted.

outsid0r said:
has this been tested to work on the INC? if not why has this been posted.
Click to expand...
Click to collapse
uhm....do you read?
"This thread is intended to be an think-tank, similar to the one on the eris forums where I got the idea from. Let the ideas flow!"
no. this is not working yet. thats why the title even has {development} in it. the process is almost working, and this is a develpoment thread to work out the issue-which is also in big letters at the top...see where it says
"Without the NAND being unlocked, we are unable to re-write to the recovery partition. Other than that everything is working good. Unlocked NAND=One Click Root!"

So once we solve a much more difficult problem, the less difficult will be easier.
Makes sense.

We already know how to unlock the nand vs the exploit posted last night...also unrevoked will have it done In a few days anyway
Sent from my HTC Incredible using the XDA App

adrynalyne said:
So once we solve a much more difficult problem, the less difficult will be easier.
Makes sense.
Click to expand...
Click to collapse
the difficult problem has already been solved. the unrEVOked team already has the NAND unlocked. now its whether they want to share and make it a true one-click root method, or if they are going to keep it a secret and keep koush's clockworkmod recovery as the only possibility. this tool still uses the clockworkmod recovery, but after a NAND unlock your given the option to change. since koush is working for them too, im starting to think more and more that they are going to keep the monopoly.
im hoping that they will just incorporate their NAND unlock method into this root process. they can even re-lock it after the process is done as they do in their re-flash tool to preserve the monopoly, but a true one-click root is now possible with their co-operation. ive messaged them asking if they want to help out. we will see soon enough, so cross your fingers!

they can even re-lock it after the process is done as they do in their re-flash tool to preserve the monopoly
Click to expand...
Click to collapse
You just lost a ton of respect from me, and I suspect more than a few others. Talk about biting the hand that feeds you.

adrynalyne said:
You just lost a ton of respect from me, and I suspect more than a few others. Talk about biting the hand that feeds you.
Click to expand...
Click to collapse
So I see we have this starting up again....shakes head at OP..
@adrynalyne best to just ignore these people...its not like the winmo days is it man? Le sighe

Good advice, you are right. I will ignore this stuff in the future.
No, not like the winmo days at all. I've never seen so much anomisity and jealousy in a community before like there is for Android.

All I can say is we already intended to release this method, we were making a pretty robust obfuscation for it. But again the community has jumped before thinking and posted the bug for HTC to fix. There might not be any root's left after this one is burnt. Which it now is. Our tool will be released as is soon enough.
We don't care to create a monopoly, we happily work with others that ASK. Those that just jump and tell the world all the secrets we don't want plugged are just stupid, plain and simple.

adrynalyne said:
You just lost a ton of respect from me, and I suspect more than a few others. Talk about biting the hand that feeds you.
Click to expand...
Click to collapse
LOL Whatever, it isnt like respect from you is something anyone cares about. I like someone with the nerve to speak the truth no matter how unpopular it might be.

outsid0r said:
has this been tested to work on the INC? if not why has this been posted.
Click to expand...
Click to collapse
Please read. Think tank! I applaud this dude for trying. More than many others do here!

fader01 said:
LOL Whatever, it isnt like respect from you is something anyone cares about. I like someone with the nerve to speak the truth no matter how untrue it might be.
Click to expand...
Click to collapse
Fixed that for ya.

adrynalyne said:
You just lost a ton of respect from me, and I suspect more than a few others. Talk about biting the hand that feeds you.
Click to expand...
Click to collapse
Shadowmite said:
All I can say is we already intended to release this method, we were making a pretty robust obfuscation for it. But again the community has jumped before thinking and posted the bug for HTC to fix. There might not be any root's left after this one is burnt. Which it now is. Our tool will be released as is soon enough.
We don't care to create a monopoly, we happily work with others that ASK. Those that just jump and tell the world all the secrets we don't want plugged are just stupid, plain and simple.
Click to expand...
Click to collapse
it seems like my comment was taken the wrong way.
for one, clockworkmod recovery is the only one that works on the DINC AFAIK, amon_ras isnt working on here either.
the monopoly is basically a monopoly because of the lack of other available options, not necessarily because its enforced.
i apologize if it came off the wrong way or insulted anyone with the preceding comments.
i meant this thread as a co-operative think-tank, it wasnt my intention to start a big ordeal.

adrynalyne said:
Good advice, you are right. I will ignore this stuff in the future.
No, not like the winmo days at all. I've never seen so much anomisity and jealousy in a community before like there is for Android.
Click to expand...
Click to collapse
@adrynalyne yeah its a real rough community at times, but what ya gonna do right...its hard for me to ignore them at times too
@shadowmite. thanks for your guys hard work....the ignorant ones are everywhere nowadays, hope they don't get you guys down.
Cheers!

Shadowmite said:
All I can say is we already intended to release this method, we were making a pretty robust obfuscation for it. But again the community has jumped before thinking and posted the bug for HTC to fix. There might not be any root's left after this one is burnt. Which it now is. Our tool will be released as is soon enough.
We don't care to create a monopoly, we happily work with others that ASK. Those that just jump and tell the world all the secrets we don't want plugged are just stupid, plain and simple.
Click to expand...
Click to collapse
hmm. well i guess thats what happens when people try to help out the community...maybe next time i just wont do anything... :/
and FYI...i did contact you. i sent you a PM earlier today.
this method has been used on the EVO and hasnt been plugged, and its been in the works on the Eris-also an HTC phone- for quite a long time, and in the same way this is...a co-operative community effort to make the phone the best that it can be.And its still not been plugged.
id worry less about HTC plugging the exploits and more about getting the exploits available to the public.

Correct, you are not the original one leaking the method. But my point is devs capable of finding things like this should be capable of thinking about it being plugged. HTC fixed our recovery hold in the next OTA. Now it's quite possible nand and this root will be patched also. we have NO OTHER WAYS IN... Thats it. besides some VERY complicated exploits we are OUT after the next ota.
I got your pm's, but only after you posted this.
It's a moot point, our one click root is due out in a few minutes. we were going to further lengths to protect the method, but it's out anyway at this point.

Shadowmite said:
Correct, you are not the original one leaking the method. But my point is devs capable of finding things like this should be capable of thinking about it being plugged. HTC fixed our recovery hold in the next OTA. Now it's quite possible nand and this root will be patched also. we have NO OTHER WAYS IN... Thats it. besides some VERY complicated exploits we are OUT after the next ota.
I got your pm's, but only after you posted this.
It's a moot point, our one click root is due out in a few minutes. we were going to further lengths to protect the method, but it's out anyway at this point.
Click to expand...
Click to collapse
well i apologize for the fact that i may/may not have ruined your chances to make a big announcement for your release, but IMO its kinda bs that you keep the info on lockdown. the whole point of android is that its open. a select amount of people shouldnt consider themselves the gatekeepers of important information.

ban_dover said:
well i apologize for the fact that i may/may not have ruined your chances to make a big announcement for your release, but IMO its kinda bs that you keep the info on lockdown. the whole point of android is that its open. a select amount of people shouldnt consider themselves the gatekeepers of important information.
Click to expand...
Click to collapse
From our wiki, which you appearently haven't read:
http://unrevoked.com/rootwiki/doku.php/public/unrevoked2
That doesn't seem fair! Android is about open source.
In some senses, we agree; but at times, a tradeoff needs to be made. Releasing the source code for this, we believe, would compromise the greater ability to unlock devices like these in the future. Given the choice between sacrificing the liberty of running code on our handsets and the liberty of reading the code by which we unlock it, we feel that the millions of handsets are more important. It is unfortunate that we must make such a choice, and we look forward to the day in the future that no such decision need be made.
Click to expand...
Click to collapse

Shadowmite said:
From our wiki, which you appearently haven't read:
Click to expand...
Click to collapse
already read it.
i dont take my opinions from things i read. i take the information and draw my own conclusions. and in this case my conclusion is that, while i can see your point i still disagree.

[Q] Hero CM7 RC2 stable I think!

flashed CM7 RC2 I think month or so ago. Phone's been running fine slow but fine. Today Im texting the gf and look down and see blank wall paper. Reboot teh phone htc screen comes up vibrates then starts over. Cant do **** with this think besides stick down the front of my pants! Ive powered and booted to hboot, fastboot etc., cant get it to go into recovery any help would be greatly appreciated before I have a stroke!

FAIL. This should be in Q+A. Can you start ADB and access the device? Are you s-off? How did you root the phone? What have you tried? What recovery do you have? Can you read? Is the battery full? Did you search?

well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an a...?

Questions don't belong in the Development section <---please click link and read....moved to general...

TMcGuire17 said:
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an ass?
Click to expand...
Click to collapse
I might be an a.., but I am helping, that's why I asked a bunch of questions. You are not s-off, you would know if you were. ADB is a program you use on your computer, not the phone. I asked because you can flash a recovery image using ADB even though the phone won't boot - so my new question here would be do you have ADB on your computer? You should have ADB if you rooted a long time ago, before there were 1-click root methods. I would recommend charging your phone, since many reboots would kill it. Wait til the charging light turns green. Once it's green boot into the bootloader, then access your phone via ADB and see if recognizes the device. If it does we can work from there. As to your BS about posting in dev because it felt better, that's lame as hell, I would have helped in q+a as well, but I would've been less of an ass because you were posting in the correct section. Anyway, charge it up, and reply if you know how to use ADB or not, then we can move on.
EDIT: I just reread your posts, did you say you can boot into your ROM, just not recovery? If so you can also flash a recovery image using terminal emulator. Let me know.

@TMcGuire17
Let’s take the aggression down about 5 notches and remember that when asking for help it is important to post in the correct section. The fact that you want your question answered quickly does not change the fact that this thread has no place in development. XDA is not tech support and while members can be very helpful you should not expect answers from anyone. When you have to search for the answer or figure out a solution…you are able to learn…understand…and then help others…and that is what XDA is about. Calling people names is never acceptable...I have edited your post. I am tempted to close this thread but I will leave it open in the hopes that you find your answer…but any more name calling or bickering and this thread is closed.
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)

krook6023 said:
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
Click to expand...
Click to collapse
LOL ok my bad. I get angry. It's the Irish in me.

Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace

TMcGuire17 said:
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
Click to expand...
Click to collapse
Scotch-Irish actually, red beard to prove it, lol. You shouldn't need to update your adb If you have adb, and on windows, and it's old, try this: open command prompt from your start menu. type "cd C:\android-sdk-windows\tools" (or just copy paste that with no quotes) then type "adb devices" and if it says "random numers phone" like "2222555555 HTC recovery" or whatever, you're good. Report back.

I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running

TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
So now does it show your device?
sent from a series of tubes.

No it still wont execute the command

If it does, type "adb shell" enter "su" enter "flash_image recovery /sdcard/nameof yourrecovery.img"

Thanks il Duce. If I get adb running Ill try it and post back.

TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
Hey TMcGuire, If you updated to the latest SDK, the new path for ADB is no longer \Tools (unless you moved a bunch of files) Try c:\androidsdk\platform-tools

TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
This is not the correct path. Try typing "cd C:\androidsdk\tools" enter, then try "adb devices" OH YEAH and do you know if you had usb debugging on in the phone settings? You may have to run the RUU if you didnt. That can be done from fastboot, but try the other command first, then the flash command.
Edit, platform tools like posted above mine, sorry I dont have the new sdk.
sent from a series of tubes.

Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!

so here is where Im at. fastboot lists my device. I've try to flash the rom from fastboot but no go. Tried to copy the ROM renamed update.zip to the sdcard via fastboot then I was gonna run update but it returned: sending '/sdcard' (72819 KB) FAILED (sounds familiar )(remote not allow)

TMcGuire17 said:
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
Click to expand...
Click to collapse
look here:http://forum.xda-developers.com/showthread.php?t=958968
read the info, I think jasonmaloney put the zip you need near the end of the thread.

Read, tried failed. It wont push anything to the device. Always comes back as failed remote: not allow

[Q] Help with rom installation?

Hey everyone!
I am new to everything about android and just rooted my phone a couple weeks ago. I want to install the decrapified rom burin not 100% sure how to do it. I need CWM to do this right? Can I get back to my original rom if I don't like it or something goes wrong? I also hear some users talking about backing up the device. How do we do this? I know that there are lots of questions and I know some person (maybe two lol) could point me in the right direction. Thank you!
Torin

Torin_93 said:
Hey everyone!
I am new to everything about android and just rooted my phone a couple weeks ago. I want to install the decrapified rom burin not 100% sure how to do it. I need CWM to do this right? Can I get back to my original rom if I don't like it or something goes wrong? I also hear some users talking about backing up the device. How do we do this? I know that there are lots of questions and I know some person (maybe two lol) could point me in the right direction. Thank you!
Torin
Click to expand...
Click to collapse
Android Development is not for questions or Problems
Please post in the correct Forums
Moving to General

Torin_93 said:
Hey everyone!
I am new to everything about android and just rooted my phone a couple weeks ago. I want to install the decrapified rom burin not 100% sure how to do it. I need CWM to do this right? Can I get back to my original rom if I don't like it or something goes wrong? I also hear some users talking about backing up the device. How do we do this? I know that there are lots of questions and I know some person (maybe two lol) could point me in the right direction. Thank you!
Torin
Click to expand...
Click to collapse
1 yes, you need cwm to put decrapified
2 once u install cwm, make sure ur battery is full (at least 50%, but i'll just say full) and make a backup using cwm of ur current system
3 see: 2
Sent from my VS910 4G using Tapatalk

S.Meezy said:
1 yes, you need cwm to put decrapified
2 once u install cwm, make sure ur battery is full (at least 50%, but i'll just say full) and make a backup using cwm of ur current system
3 see: 2
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Awesome thanks. Now I cant get the adb shell to work. ive done it on my dads phone before so im kinda familiar with it but the sdk still seems to be updating or whatever. Should it work when its finished?
Like when I type "adb devices" it says nothing can be found.

What operating system is ur computer on? Make sure you have installed the LG drivers if Windows.. also, doesn't hurt to be up to date w the sdk...
Sent from my VS910 4G using Tapatalk

Running windows 7 sdk updated drivers installed.
Im typing
cd C:\android-sdk\tools\
adb devices
nothing pops up. It says it isnt recognized?

1. install and update adb sdk.
2. Plug your phone in and install the drivers so it is recognized by windows as the revolution.
3. once 1 and 2 are done set your phone to internet only and turn on debugging.
4. now try adb

Torin_93 said:
Running windows 7 sdk updated drivers installed.
Im typing
cd C:\android-sdk\tools\
adb devices
nothing pops up. It says it isnt recognized?
Click to expand...
Click to collapse
also it is cd c:\android-sdk\platform-tools\

Haxcid said:
also it is cd c:\android-sdk\platform-tools\
Click to expand...
Click to collapse
I just figured out it was\platform-tools\
Like wtf they moved it? lol
I also forgot about internet mode. Im going to give it a go and if I bump into any problems I will let you know

Once I try to get su access (after checking adb access) it says not recognized. Why?

Torin_93 said:
Once I try to get su access (after checking adb access) it says not recognized. Why?
Click to expand...
Click to collapse
we're still getting cwm on...? and u already put recovery-cwm-pr1.img on ur sd?

S.Meezy said:
we're still getting cwm on...? and u already put recovery-cwm-pr1.img on ur sd?
Click to expand...
Click to collapse
Yes its there
But the su command wont work
You have skype? I could screen share.

Torin_93 said:
Yes its there
But the su command wont work
You have skype? I could screen share.
Click to expand...
Click to collapse
Make sure your screen is on when you type su so you can accept super user permission on your phone.
Sent from my VS910 4G using XDA Premium App

After I type adb devices I get the list then its:
C:\android-sdk\platform-tools>su
Right?
Cause it says not recognized

No type, adb shell, then at the next line enter su
Sent from my VS910 4G using XDA Premium App

mtmichaelson said:
No type, adb shell, then at the next line enter su
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
Great thanks!!! Im in

cat /dev/zero > /dev/block/mmcblk0p14
write: no space left on device
cat /sdcard/recovery-cwm-pr1.img > /dev/block/mmcblk0p14
no such file or directory.
Im so confused. Now what.
Thanks for everyones help so far You guys are amazing!

Torin_93 said:
cat /dev/zero > /dev/block/mmcblk0p14
write: no space left on device
cat /sdcard/recovery-cwm-pr1.img > /dev/block/mmcblk0p14
no such file or directory.
Im so confused. Now what.
Thanks for everyones help so far You guys are amazing!
Click to expand...
Click to collapse
If you are copying it in Windows, copy it to the drive marked "internal." If not, then this is telling you that file isn't on your sdcard. You need to move it there.

Its in the internal. Should it go in a folder? What about the fact that it says no space left on device?
I have plenty of space?

Torin_93 said:
Its in the internal. Should it go in a folder? What about the fact that it says no space left on device?
I have plenty of space?
Click to expand...
Click to collapse
It shouldn't need to go in a folder. The error message about space is normal (expected).

Removing System Apps

I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?

System is protected: you can't modify it while the phone is booted. You'll have to make a zip or whatever to delete it in recovery.

You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly

fkofilee said:
You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly
Click to expand...
Click to collapse
It seriously took you all day to root? What went wrong?

Did you try just freezing the app instead?

Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2

afilopou said:
Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So you can no longer go into ES explorer, mount root/system go to system > apps and delete whatever you want ?
Sent from my HTC Incredible S using Tapatalk 2

The recovery flashed but wouldnt boot , managed to get round it when i discovered POB with his superboot Thank god for the desire C
Then i realised that i couldnt flash anything because I manged to install 6.0.2.8 as a boot img, and 6.0.3.0 as a proper recovery.
Then i didnt have any files on the device to flash boohoo so i managed to get ADB sideload working through the AIO One Toolkit... And managed to flash AHRD finally getting a working device,
As you see Im a seasoned vet at these things but the HTC One has been the first device that has stumped me....
----------------------
The apps issue is not unkwown for HTC however they havent done this for a while.... Back with the G2 they did exactly the same thing and yes ive frozen them but there should be away to remove system apps for us through root.... But i cant remember how, Throwing it into ADB Shell and requesting SU along with a Remount works fine but still would like to remove the apps.
Im also looking for someone with a locked phone... (Sim Locked) i have a theory and it worked on the Desire C Anyone wanna help?

fkofilee said:
I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?
Click to expand...
Click to collapse
Delete the apps with titanium and power off the phone. Don't do a restart.

Already tried that ^_^

You need to flash a custom kernel with a modified ramdisk to disable system protection Without doing that you're like deleting an app on windows with deepfreeze on it

Is that the only solution?
There are so many bloated useless and intrusive (cr)apps on this phone it's unbelievable.

Other solution is boot in recovery and delete it there. Either thru adb while in recovery mode, flashable zip or through file manager(if you're using TWRP). Other than that nope

Hmmm I'm thinking adb through recovery here but how do I got about doing this?

fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");

The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk

the simple way is ROM CLEANER, but isn't available yet for the One.
cheers

fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>

Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful

ogdobber said:
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");
Click to expand...
Click to collapse
MacHackz said:
The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk
Click to expand...
Click to collapse
limx said:
the simple way is ROM CLEANER, but isn't available yet for the One.
cheers
Click to expand...
Click to collapse
Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
issak42 said:
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful
Click to expand...
Click to collapse
All Wonderful Ideas folks, however i had a go at this last night, it was a fricking nightmare even mounting ADB through recovery