Database Develop

Trying to uninstall a couple of apps, please help

Hi all. I am wanting to get rid of a couple of apps I don't use (mainly Amazon MP3 and Work Mail). What I've tried is, while phone is in recovery mode, remount the /system
No Success:
Code:
$ adb remount
remount failed: Invalid argument
I've also tried this as suggested by some other members:
Code:
$ adb shell
mount -oremount,rw /dev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
Yet I'm still unable to see/use /system/app. Is there anyone that might know what's wrong here?

ogwilson said:
Hi all. I am wanting to get rid of a couple of apps I don't use (mainly Amazon MP3 and Work Mail). What I've tried is, while phone is in recovery mode, remount the /system
No Success:
Code:
$ adb remount
remount failed: Invalid argument
I've also tried this as suggested by some other members:
Code:
$ adb shell
mount -oremount,rw /dev/block/mtdblock3 /system
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
Yet I'm still unable to see/use /system/app. Is there anyone that might know what's wrong here?
Click to expand...
Click to collapse
I could totally help you to uninstall these apps by spending a minute and typing up a few commands to allow you to do so.
But I won't, because you neglected to post this in the proper forum.

You will need to know the EXACT name of the apps you want to remove.
Reboot in to recovery
Alt+x
<enter>
#mount -o rw /dev/block/mmcblk0p2 /system
That will put your system folders in ReadWrite
Pay attention to the space's between
mount and -o
-o and rw
rw and /dev
mmcblk0p2 and /system
You can also use Terminal app
$su
#mount -o remount,rw /dev/block/mtdblock3 /system
I personaly use Root Explorer, its easy.

uansari1 said:
I could totally help you to uninstall these apps by spending a minute and typing up a few commands to allow you to do so.
But I won't, because you neglected to post this in the proper forum.
Click to expand...
Click to collapse
I'm sorry, I thought this was the correct forum. You don't have to be nasty about it, and you could at least point me in the right direction if you neglect to help otherwise.
Lakers3408 said:
You will need to know the EXACT name of the apps you want to remove.
Reboot in to recovery
Alt+x
<enter>
#mount -o rw /dev/block/mmcblk0p2 /system
That will put your system folders in ReadWrite
Pay attention to the space's between
mount and -o
-o and rw
rw and /dev
mmcblk0p2 and /system
You can also use Terminal app
$su
#mount -o remount,rw /dev/block/mtdblock3 /system
I personaly use Root Explorer, its easy.
Click to expand...
Click to collapse
Thanks for the help. I was able to successfully mount it using
Code:
#mount -o rw /dev/block/mtdblock3 /system
however, when i then try adb uninstall /system/app/Mail.apk, i get this
Code:
[email protected]:~$ adb uninstall /system/app/Mail.apk
/sbin/sh: pm: not found
not sure what this means exactly though. Your help is greatly appreciated, despite what some sour posters may think otherwise.

ogwilson said:
I'm sorry, I thought this was the correct forum. You don't have to be nasty about it, and you could at least point me in the right direction if you neglect to help otherwise.
Click to expand...
Click to collapse
No, I do have to be nasty about it... there have been way too many people like you around here lately, and it's irritating to say the least. Had you simply opened your eyes and read just the titles of the stickied threads in this very forum, you'd have seen this thread title!
"This is DEVELOPMENT section not General!!!!"
That means, go to General or Q&A to ask your question.
I'll tell you what though... go and start a new thread in the proper forum, and I'll explain step by step how to uninstall these apps.

@uansari
Just answer the damn question and send him on his merry way. Instead of going back and forth arguing like 5 year olds! You took the time to reply twice, if you would of gave him the answer on the first reply it would end there.
Anyways
@ogwilson
Try this after mounted
# rm /system/sd/app/Mail.apk

Lakers3408 said:
@uansari
Just answer the damn question and send him on his merry way. Instead of going back and forth arguing like 5 year olds! You took the time to reply twice, if you would of gave him the answer on the first reply it would end there.
Anyways
@ogwilson
Try this after mounted
# rm /system/sd/app/Mail.apk
Click to expand...
Click to collapse
Thank you, this worked wonderfully.
As for the other guy, I have read that thread over a few times when I first got my phone and I figured that the general questions thread was more for issues that didn't involve tinkering with the phone in these ways. Thats what I thought the development forum was for. And thats all you had to say. So I'm sorry if it wasn't exactly clear the first time, but people like you scare off people who simply are not clear on the exact rules, when the uses of each forum aren't extremely outlined and detailed.
Thanks again for the help Lakers. Is there a way for me to close this thread?

ogwilson said:
Thank you, this worked wonderfully.
As for the other guy, I have read that thread over a few times when I first got my phone and I figured that the general questions thread was more for issues that didn't involve tinkering with the phone in these ways. Thats what I thought the development forum was for. And thats all you had to say. So I'm sorry if it wasn't exactly clear the first time, but people like you scare off people who simply are not clear on the exact rules, when the uses of each forum aren't extremely outlined and detailed.
Thanks again for the help Lakers. Is there a way for me to close this thread?
Click to expand...
Click to collapse
Although he was jerk about it, he is right questions like your do belong in the Q&A. So in the future when in doubt please post in the Q&A.
As for YOU closing this tread, it can't be done. A Mod will move it or close it for you.
Also
You may want to copy and paste the commands on to your pc incase you forget them and you will.

Lakers3408 said:
Although he was jerk about it, he is right questions like your do belong in the Q&A. So in the future when in doubt please post in the Q&A.
Also
You may want to copy and paste the commands on to your pc incase you forget them and you will.
Click to expand...
Click to collapse
Yea I figured he was right or else he wouldn't have responded so strongly about it. I've acknowledged that and now know for the future that anything that I have a question about must go in Q&A.
And yea every time I get help on an obscure issue that requires obscure commands, I always paste them into a note document and save to my android folder. Now hopefully a mod can move this. Thanks again!

Lakers3408 said:
Although he was jerk about it, he is right questions like your do belong in the Q&A. So in the future when in doubt please post in the Q&A.
Also
You may want to copy and paste the commands on to your pc incase you forget them and you will.
Click to expand...
Click to collapse
Yes, I am a jerk, but I offered to help... just not in the wrong forum. I see no benefit in encouraging others to continue posting questions in this forum.
Anyway, this thread will be locked soon.

This is why I try not to post anything is this forum, I'm afraid to get chewed out for it.

Pinesal said:
This is why I try not to post anything is this forum, I'm afraid to get chewed out for it.
Click to expand...
Click to collapse
Lmao!
Yeah some people got bullied in high school or are still being bullied and this is there way of bullying back!
To be safe just post your question in the Q&A and you should be safe. But I'm sure some jerk will tell you that it does not belong there and it belongs in Development or Themes or Apps

Lakers3408 said:
Lmao!
Yeah some people got bullied in high school or are still being bullied and this is there way of bullying back!
To be safe just post your question in the Q&A and you should be safe. But I'm sure some jerk will tell you that it does not belong there and it belongs in Development or Themes or Apps
Click to expand...
Click to collapse
No one will ever tell you that, lol... questions belong in the Q&A forum. It's not rocket science kids.

Start asking your questions in the right sub-forum (Q&A) (Theme) or even in (General), or i will be forced to ban you for 3 days or till you learn.
Thanks
Thread Trashed!!

[HOW-TO] apps2sd on n1 cyanmod

I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
As usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
EDIT:When updating to a new CM rom you WILL encounter a boot loop, simply run the steps below AGAIN during the loop cycle and then reboot the phone and it should work.
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj

Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?

heroskyy said:
Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?
Click to expand...
Click to collapse
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.

nonmindo said:
I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
AS usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj
Click to expand...
Click to collapse
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.

kamasi36 said:
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.
Click to expand...
Click to collapse
awesome! thank you! Ive always been confused about that

heroskyy said:
awesome! thank you! Ive always been confused about that
Click to expand...
Click to collapse
Ha. me too man. You have to learn fast on here. They expect us to know all this stuff coming in the gate. Just holla back if you need some more help. I'm a noob too but managed to figure it out.
http://forum.xda-developers.com/showthread.php?t=532719
This might help you get started. make sure you get everything updated because this is kind of dated.

kamasi36 said:
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.
Click to expand...
Click to collapse
Yeah cyanogen (especially) and dhanj should be credited more than me. I didn't really do anything but add on how I got it working for me.
One thing to mention, if cyanogen doesn't implement this officially in his ROM (and for most people it's probably not needed) you'll have to redo this procedure each time you flash/update so I'd suggest keeping the 2 files saved.

@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3

dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
Thanks dnanj. Just upgraded to ext. 3. apps2sd b4 now.

You betcha....as always, just sharing information whenever I can.

am i suppose to get a conformation in shell if the commands worked?

Ohal_yeah said:
am i suppose to get a conformation in shell if the commands worked?
Click to expand...
Click to collapse
When the commands complete, you should be brought back to the prompt where the shell awaits the next command.

I apologize for not looking deeper into who deserves credit here, thanks for those of you that do know!! I was simply just trying to make it easier to get the information to people that might want it...
as for the debate of needing a2sd or not, i was out of space right from the get-go because of all the apps i had on my mt3g...so to me i definitely need it out of the 1gb partition i made on my sd card i have .82 free now lol...

completed all steps but everything still saves to internal memory

JustinLoe said:
completed all steps but everything still saves to internal memory
Click to expand...
Click to collapse
a small glitch probably when you run the last command before adb reboot, it fails to create the directory as it exists, probably change the name to solve it, it happened to me once

dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA

jakontil said:
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA
Click to expand...
Click to collapse
ext3 is essentially a ext2 file system with journaling.
Click Here to read about ext3 and it's benefits over an ext2 fs. As to why ext2 over ext3 for apps2sd, since journaling improves reliability of the fs, that makes it more ideal than ext2.

it works great thanks!

hi dnanj
thanks for the link

sorry but im stuck here
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb push 04apps2sd /system/etc/init.d/
failed to copy '04apps2sd' to '/system/etc/init.d/': Is a directory
C:\android-sdk-windows\tools>
why does cmd show me this error can you help me out please..very much appreciated

I need help about rooting

Hello everyone.
First off all i hope this post is in the right section.
Let me get this out off the way first:
Im not good at english, and im not good at cmd files and so on.
But! i can succecsfully root my phone and get the # in cmd.
The reason im rooting is becouse i want the market patch so i can see all apps.
Here is my questions:
1. Whenever i try to adb push vending......
It says "the file is read-only" i cheked its not read only
So how do i fix that?
2. In the guide to root the phone he says:
"You can do anything then! Look at /system, /data, etc etc. You're broken free, my friend"
Where can i see the /system and so on? he says look at, but where can i look at it? how can i like acces the folders?.
So on the easy way, i search a way to install the market patch.
Thank you everyone

Bump, i really hope someone will help

Anyone? please?

When you have root, you need to mount r/w partition:
- adb push tattoo-hack.ko ./data/local/bin/tattoo-hack.ko (if you haven't did it before)
- adb shell
$
- su
#
- # insmod /data/local/bin/tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
And now you have mounted in r/w, so:
- adb push Vending-Tattoo-patched.apk /system/app/Vending.apk
p.s. ah...you can access system folders with Root Explore (it needs root)

I never had to mount anything. I did the latest root hack in the sticky at top of forum and then i installed the full market apk. Worked a treat.

ephumuris said:
I never had to mount anything. I did the latest root hack in the sticky at top of forum and then i installed the full market apk. Worked a treat.
Click to expand...
Click to collapse
I'm happy for you, but someone like me (and mafiapanda in that case) did old manual root.

Ty
Thank you im going to try it out now, thanks

Okay, after i get the
#
then i did what you said.
i get it again
# adb push vending.....
"adb not found"
Ehhmm can you help me there?
Everyting was succesfull except pushing it.

mafiapanda said:
Okay, after i get the
#
then i did what you said.
i get it again
# adb push vending.....
"adb not found"
Ehhmm can you help me there?
Everyting was succesfull except pushing it.
Click to expand...
Click to collapse
Of course, it's normal
You have to write "adb push vending....." non in "adb shell" but in "adb" (open another cmd and as for example "cd c:\android\tools", then "adb push" etc.)

Stupid me
Am so thankfull to you guys, you really helped me alot Thank you really much!

Okay, now i get "permisson denied" when im trying to "adb push vending..."
I opened a new CMD and typed cd c android tools, i just get permission denied.
Can anyone help me about that? Thank you guys so far

mafiapanda said:
Okay, now i get "permisson denied" when im trying to "adb push vending..."
I opened a new CMD and typed cd c android tools, i just get permission denied.
Can anyone help me about that? Thank you guys so far
Click to expand...
Click to collapse
Have you opened new cmd closing the other or not?
You don't have to close the first cmd.
Try. If it doesn't work, probably there are some problems with the root procedure, in that case try that solution: Root in 1 click. It contains: root, boot.img, market (also recovery if you choose it).

Yea, i have tryed root in 1 click, but does it really include market?

Root in 1 click gives me the same error ?
Okay maybe this is alot to ask for but is there anyone out there that can make a video of it all from rooting to push market. i would be so thankfull.
And its not just for me, it would help alot out there. im so thank full

Damn, now it says "read only file system" again.
Can anyone post a detalied how-to Thank you really much.
Im going to bed now, cheking this post tommorow.
Btw, i would love to have talk with someone on msn, steam or mail.
Am from denmark if it matters.
THANK YOU

mafiapanda said:
Damn, now it says "read only file system" again.
THANK YOU
Click to expand...
Click to collapse
You have to repeate that every time you reboot:
- adb shell
$
- su
#
- # insmod /data/local/bin/tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
And then you have mounted in r/w:
- adb push Vending-Tattoo-patched.apk /system/app/Vending.apk
(one time)

Okay I Will try that when I get home. Can I use the 2. 1 market I mean so I can have all the 500 apps or is it only for 2 1 firmware modded phones?

mafiapanda said:
Okay I Will try that when I get home. Can I use the 2. 1 market I mean so I can have all the 500 apps or is it only for 2 1 firmware modded phones?
Click to expand...
Click to collapse
Use v2 patch, not 2.1. It has worked for me.

YES! I cant ****ing believe it!! I succed !! im am so happy
Thank you very very very much 1000 times.
YES MAN im so happy now.
Maybe i should at a guide to this forum? i dont know if anyone needs it but..
Okay last last question, when i search for "video" i see 300 results which am very happy for but, on the picture he had 500 how can i get 500 ?

mafiapanda said:
YES! I cant ****ing believe it!! I succed !! im am so happy
Thank you very very very much 1000 times.
YES MAN im so happy now.
Maybe i should at a guide to this forum? i dont know if anyone needs it but..
Okay last last question, when i search for "video" i see 300 results which am very happy for but, on the picture he had 500 how can i get 500 ?
Click to expand...
Click to collapse
You're welcome
300 rather than 500? I'll try..

{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.

Flash recovery with adb

Really didn't want to start a new topic, but couldn't find an answer anywhere. I'm trying to flash dg's recovery with adb. When ever I try to push the file I get permission denied. I have su working with adb, and adb is working correctly. What am I doing wrong? Thanks to any one that can help.
Sent from my LG-P925 using XDA App

I am having the same exact problem you are. I am running windows 7 and even tried cmd and run as admin but that didn't work either. Anyway yea any help would be appreciated. Also yes my phone is rooted and in Debug Mode when trying to push recovery.img.

Hmm, sorry I don't know. Fix permissions maybe, if you can? Stupid little things like making sure usb debugging is on?
Just a heads up, questions belong in a different section ("Q&A for Thrill" if it exists, or general I think), they take that stuff pretty seriously around here, and if you end up reading and learning here for a while, you'll understand why!

switch to your ADB directory (or at a command line if you already set your environment variables) and type adb root then try again. It might work

Komodo Rogue said:
Hmm, sorry I don't know. Fix permissions maybe, if you can? Stupid little things like making sure usb debugging is on?
Just a heads up, questions belong in a different section ("Q&A for Thrill" if it exists, or general I think), they take that stuff pretty seriously around here, and if you end up reading and learning here for a while, you'll understand why!
Click to expand...
Click to collapse
I dont think we have a q&a as of right now lol....I dont even know if we have a moderator
Sent from my SAMSUNG-SGH-I997 using XDA App

Sorry if this is the wrong section. No q/a for the thrill. And i didn't know if the general forum was the place for adb question. Again sorry my fault. Thanks for all replays but im still stuck with the same thing.

adb root didn't work. Said adbd cannot run as root in production builds. Also I do have USB Debugging enabled as well as Rooted the device. As for fixing permissions I would need CWM First to be able to get to that option

malickie said:
adb root didn't work. Said adbd cannot run as root in production builds. Also I do have USB Debugging enabled as well as Rooted the device. As for fixing permissions I would need CWM First to be able to get to that option
Click to expand...
Click to collapse
Do this:
open command prompt and type:
adb shell
su (click allow on phone if prompted)
chmod 777 /data
ls -l (then look at the data directory and it's permissions should now be drwxrwxrwx)
Try it again after that. It's because the /data directory is not set to R/W by default.

timbrendelaz said:
Do this:
open command prompt and type:
adb shell
su (click allow on phone if prompted)
chmod 777 /data
ls -l (then look at the data directory and it's permissions should now be drwxrwxrwx)
Try it again after that. It's because the /data directory is not set to R/W by default.
Click to expand...
Click to collapse
Thank You, that did it .

malickie said:
Thank You, that did it .
Click to expand...
Click to collapse
Cool beans

Thanks so much!!!

00mred00 said:
I dont think we have a q&a as of right now lol....I dont even know if we have a moderator
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
It says Mr. Clown is the moderator, and his sticky says not to ask questions. I don't know if I've actually seen him on here though, so I see where you're coming from, the thrill isn't getting much traffic! But you're right, no q&a section.
fn1046 said:
Sorry if this is the wrong section. No q/a for the thrill. And i didn't know if the general forum was the place for adb question. Again sorry my fault. Thanks for all replays but im still stuck with the same thing.
Click to expand...
Click to collapse
Oh hey no worries mate. I really couldn't care less, considering how empty Thrill Development is, and I would have came to the same conclusion as you. All I meant to do was give you a heads up that some people get angry about that kind of thing

Well my issue is i cannot get the recovery.img pushed to the phone...ive downloaded it and don't know where to place it for it to send...when i do adb push recovery.img/data it just gives me a list of all the adb commands. I was gonna try to use root explorer and manually push it but i dont know where to place it...any suggestions?

Put the recovery.img in your android-sdk tools folder before you try to push
Sent from my LG-P925 using XDA App

Hey can one of you guys possibly upload a stock recovery backup. I think mine is borked as I tried to go back to stock and it keeps going into clockworkmod recovery when setting up factory defaults in the stock rom. It would be much appreciated.
thanks