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

newb help please... help with adb copying files.... no permissions??

Sorry... newb question... can not figure out this deal...
Trying to copy the jupiter files to my phone... can not.
I dont have permissions... how can I get permissions opened up?
Below is some of what I am getting in regards to errors -
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb push jupiter.xml /system/etc/jupiter.xml
failed to copy 'jupiter.xml' to '/system/etc/jupiter.xml': Permission denied
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb push jupiter.xml /sdcard/jupiter.xml
failed to copy 'jupiter.xml' to '/sdcard/jupiter.xml': Permission denied
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb shell
$ su
su
Permission denied
$
Note - this is a samsung captivate phone with a fresh cognition 2.36b rom and I used one click root on it to root the phone after the build..... (but I think the rom was rooted to start with??
Sorry ... just need a way to get access to this phone - trying adb.... also is there a windows file manager that would browse/edit the contents of this phone?
thanks in advance Kevin

PLEASE DIVERT ALL QUESTIONS TO Q&A FORUM NEXT TIME.
IF you're on Froyo.. for some reason froyo does not allow pushing to /system .. at least for me that's the case (someone correct me)
root your phone:
1. adb push /sdcard/jupiter.xml
2. adb shell
3. su
4. cp /sdcard/jupiter.xml /system/gps/jupiter.xml (or wherever you need to put it)
5. do the same for the rest of the files.. but tbh
THERE'S NO FIXING GPS YET

darkamikaze said:
PLEASE DIVERT ALL QUESTIONS TO Q&A FORUM NEXT TIME.
THERE'S NO FIXING GPS YET
Click to expand...
Click to collapse
What he said.

If froyo didn't fix your gps then you are sol. But don't be so sure its still broke, it can take some time on the first lock. Once it gets a lock within 5-10 meters it should work decent afterwards with the occasional hiccup usually when its not used every day. But some are reporting poor performance still with froyo.
A factory reset can fix some bugs I have seen on jf7 and ji6 on my phone causing the gps to turn off. Jj4 doesn't seem to have that bug on my phone. Cog2.3b6 is jj4 based
Some claim to have performance degrade over time, I think that's all placebo but others have completely different experiences with gps than I do. I notice it having to occasionally need to get new gps data causing a delay in the initial lock but it seems more random than progressive and I never fail to get a lock.
If you are trying to use the jupiter.xml file in the gps solution thread from clshortfuse our what ever his name is, you will likely see an no improvement to a slight improvement. It gets faster locks on eclair roms but on froyo the jupiter file already resembles his and the major difference being that his forces the google server for gps data.
Sent from my SAMSUNG-SGH-I897

OK thanks for all the help so far -
I had a n82 phone, like 2-3 years ago, it was awesome.... google maps and all... blue dot was where the phone was... I could watch me walk around my house... it would show me getting the mail walking down the drive way to the mail box and back....
I have an iphone 3gs....works fine.... maybe not quite as good as the n82 did, but works ok, locks quick and will the blue dot with in a few feet of me IN MY HOUSE.
While I dont get this whole GPS problem on this phone I hear you about not trying to fix it.
I have some limited unix experience... used vi and other stuff, was able to move,copy, edit and replace files... change permissions and other standard stuff.
So if the cognition rom is rooted as is, and I was rooted before the rom, I assume I still am rooted....
Why wont the commands I tried work?
I did not try the other commands noted in this thread, yet, I will soon.
So is it my phone? or do I have the commands/syntax wrong?
If I am going to stick it out with the phone I need to figure out how to fix it.
thanks again for your help.
Kevin

Any ideas or reasons why this command would not work?
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb push jupiter.xml /sdcard/jupiter.xml
failed to copy 'jupiter.xml' to '/sdcard/jupiter.xml': Permission denied
My file on my PC is in the folder I am working from ....\tools and I assume I should have permissions to the sdcard folder?
Any help would be appreciated.
thanks Kevin

Have you made sure to grant superuser permission on the phone?
I had that issue the first time I tried it and found that I hadn't granted superuser access.
Also to the OP, if you switch to Perception, DG includes the Jupiter fix in the ROM.

You can't push to /system in FROYO.
you have to push it to /sdcard first
adb shell
su
cp /sdcard/jupiter.xml /<LOCATION>
and chmod it
and chown it.

thanks for the help... to make sure I have the right permissions I need to use the chmod and chown commands -
Do I need to mount the system first? Something like -
Code:
adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/*
thanks again, Kevin

haeffnkr said:
thanks for the help... to make sure I have the right permissions I need to use the chmod and chown commands -
Do I need to mount the system first? Something like -
Code:
adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/*
thanks again, Kevin
Click to expand...
Click to collapse
I would never do 777 on any file. Jupiter.xml should be 644 and user and group root.
Sent from my SAMSUNG-SGH-I897 using XDA App

[How To] Recover from a soft brick

A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now

Thanks! Extremely happy you are deving for this phone

What's the best way to backup my stock partitions before I keep playing with those files?
Titan Backup works for that?
Or just a tar cf /mnt/sdcard/systembackup.tar /system , works?
Thanks in advance.

uskr said:
What's the best way to backup my stock partitions before I keep playing with those files?
Titan Backup works for that?
Or just a tar cf /mnt/sdcard/systembackup.tar /system , works?
Thanks in advance.
Click to expand...
Click to collapse
I would just use the tar solution, much easier to deal with.
You can also use ADB, adb pull /system system
Also, the retail dump I did matched my phone dump bit for bit, as long as you have that you should be fine.

Thanks! I am messing around with the APKs and scripts to get the webtop to work without the dock. So I wanted to make sure I was covered.

designgears said:
I would just use the tar solution, much easier to deal with.
You can also use ADB, adb pull /system system
Also, the retail dump I did matched my phone dump bit for bit, as long as you have that you should be fine.
Click to expand...
Click to collapse
I already did both adb pull of system and tar, but how did you do the retail dump?

lpsi2000 said:
I already did both adb pull of system and tar, but how did you do the retail dump?
Click to expand...
Click to collapse
tar dump as root of system

One last question.
Once I deodex my /system/app, should I just do a adb push app /system/app and then rm /system/app/*.odex ?
I am used to use the update.zip trick on the captivate. But I am not sure how to proceed on this phone.

uskr said:
One last question.
Once I deodex my /system/app, should I just do a adb push app /system/app and then rm /system/app/*.odex ?
I am used to use the update.zip trick on the captivate. But I am not sure how to proceed on this phone.
Click to expand...
Click to collapse
push apps, then push framework, reboot, then delete all the odex files, reboot
from system do something like; find . -name "*.odex" -exec rm {} \;

designgears said:
push apps, then push framework, reboot, then delete all the odex files, reboot
from system do something like; find . -name "*.odex" -exec rm {} \;
Click to expand...
Click to collapse
Unrelated to this, I could sware yesterday I got to the recovery screen where I was able to wipe stuff and also be able to use update.zip. Although I did not use and update files but saw the option there. Today I am looking everywhere but the recovery screen does not come up with the options. I only see exclamation point and the droid. May be I am going nuts but can anyone confirm this.

lpsi2000 said:
Unrelated to this, I could sware yesterday I got to the recovery screen where I was able to wipe stuff and also be able to use update.zip. Although I did not use and update files but saw the option there. Today I am looking everywhere but the recovery screen does not come up with the options. I only see exclamation point and the droid. May be I am going nuts but can anyone confirm this.
Click to expand...
Click to collapse
tap at the bottom right of the screen right above the search button

designgears said:
tap at the bottom right of the screen right above the search button
Click to expand...
Click to collapse
ahha, thank you. Now I know I am going crazy. I used it yesterday to wipe when the system was unstable on me after playing around with the framework. I am must have stumble on that by accident. I am wondering if this documented yet somewhere around here.
Also too bad we cannot get root from there yet.

Well thank you for this. So when it boots to run, does it do a sys check to verify files are the same size or what? Anyway went to my local AT&T store and they swapped it out for me.

realawill said:
Well thank you for this. So when it boots to run, does it do a sys check to verify files are the same size or what? Anyway went to my local AT&T store and they swapped it out for me.
Click to expand...
Click to collapse
No, I just made a bad edit and it was FC hell

IT DOES NOT WORK WITH ME
I have been trying this trick for many times. The device restart and SuperOneClick hanging without any result.

designgears said:
No, I just made a bad edit and it was FC hell
Click to expand...
Click to collapse
Crazy....mine just would not reboot. But good to know that there is a way to recover. Love the phone but hate Motorola. Wish that it was easy as the Cappy.

Cool stuff. I may snatch the framework off the phone in stock form and make a batch package for this so folks can easily just double click to restore their framework and system app folder.
Good work DG...

I never get past that initial... Starting RSD protocol support screen. Is that fast boot? If so I'm a retard...
EDIT: I need the face palm sticky. It's not Volume UP...it's Volume Down. Reading comprehension for the loss...

azy8000 said:
IT DOES NOT WORK WITH ME
I have been trying this trick for many times. The device restart and SuperOneClick hanging without any result.
Click to expand...
Click to collapse
I have done this several times now, it works

I soft bricked my Atrix earlier this morning, and used this to recover. The time limit is a serious pain!
I ended up needing to separate /system into 5 separate pushes of 30MB each in order to get them done in time.
Oddly, after restoring everything, the phone is no longer associated with my motoblur account, and I can't add it.
Also, I think there my be some files in /system that are unaccounted for by the filesystem, as there is 70MB more than what is present.
Edit:
Restoring the system fixed both above problems.

OLYFR_U4_1.5.2 Market Fix

Here is a simple fix for the market issues between stock and 1.5.2 - it assumes you have flashed the 1.5.2 sbf, and also re-rooted your device.
adb shell (or open a terminal on your phone)
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
reboot
I have been running with this most of the day with no issues noticed..
-G

how funny i JUST discovered this earlier today was going to post it on the forums. great minds think alike . my n64oid is back!

Funny, I just told someone else how to do this this morning. I'm surprised this hasn't come up sooner. I've been using this since the sbf has been released with no problems, guess I should have posted this solution sooner my b :-(
Sent from my MB860 using Tapatalk

Anyway to do this through terminal?
Sent from my MB860 using XDA App

Same commands without the first adb shell..

How do I enable RW to system?
Trying to do the market fix script but get RO error on write to /system.

from a command prompt in windows/linux:
you: adb shell
reply: $
you: su
(accept prompt on device, make sure it's unlocked and @ homescreen or it might not pop up)
reply: #
you: mount -o rw,remount /dev/block/mmcblk0p12 /system
reply: (copies it back)
you: sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
reply:
you: reboot

What are the "market issues?"

Da_G said:
from a command prompt in windows/linux:
you: adb shell
reply: $
you: su
(accept prompt on device, make sure it's unlocked and @ homescreen or it might not pop up)
reply: #
you: mount -o rw,remount /dev/block/mmcblk0p12 /system
reply: (copies it back)
you: sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
reply:
you: reboot
Click to expand...
Click to collapse
Thanks,
I made some assumptions that people would know the prerequisites
I edited the original.
-G

relaxed said:
What are the "market issues?"
Click to expand...
Click to collapse
Well, I had several apps I paid for that I could not load. I had the same issues with my G-Tablet until I loaded my N1 build id in the same file a while back..
-G

Well I did it with the first method and it works fine except the market doesn't update to the new market.
ghost_o said:
Thanks,
I made some assumptions that people would know the prerequisites
I edited the original.
-G
Click to expand...
Click to collapse
Sent from my MB860 using Tapatalk

Fixter said:
Well I did it with the first method and it works fine except the market doesn't update to the new market.
Click to expand...
Click to collapse
First method?
The sed command is the only command I have posted.. You could use 'vi' directly on the device as well.. My market updated to the new version just fine after I made the change. (albeit I used vi on the device through adb shell). I just posted the sed string for people not familiar with unix, or who might want to script it..

ghost_o said:
First method?
The sed command is the only command I have posted.. You could use 'vi' directly on the device as well.. My market updated to the new version just fine after I made the change. (albeit I used vi on the device through adb shell). I just posted the sed string for people not familiar with unix, or who might want to script it..
Click to expand...
Click to collapse
I meant to say the first method where you only posted
Adb shell
su
sed
reboot.
Nothing about remounting, like what Da_G posted. Might have something to do with it?

Fixter said:
I meant to say the first method where you only posted
Adb shell
su
sed
reboot.
Nothing about remounting, like what Da_G posted. Might have something to do with it?
Click to expand...
Click to collapse
Ahhh, you must have already run something that re-mounted it rw for you. It would have failed otherwise... You can always try to put it back, and let the market update, and then change it again to get the apps back. I seriously doubt that is what is keeping your market from updating though.

ghost_o said:
Ahhh, you must have already run something that re-mounted it rw for you. It would have failed otherwise... You can always try to put it back, and let the market update, and then change it again to get the apps back. I seriously doubt that is what is keeping your market from updating though.
Click to expand...
Click to collapse
Thats exactly what I'm thinking. That doesn't have to do anything with the Market updating... Stupid market... -kicks-

Fixter said:
Thats exactly what I'm thinking. That doesn't have to do anything with the Market updating... Stupid market... -kicks-
Click to expand...
Click to collapse
should be able to reverse by switching up this part:
sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
to:
sed -i 's!OLYFR_U4_1.2.6/1296900353!OLYFR_U4_1.5.2/1298398352!' /system/build.prop
then have the market update without a problem and then reapply the fix, though I'm sure you thought of this already XD

Djazin said:
should be able to reverse by switching up this part:
sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
to:
sed -i 's!OLYFR_U4_1.2.6/1296900353!OLYFR_U4_1.5.2/1298398352!' /system/build.prop
then have the market update without a problem and then reapply the fix, though I'm sure you thought of this already XD
Click to expand...
Click to collapse
Yeah I tried that with no success... I wonder if it was the Gingerblur.

Works great. I was wondering where some of my apps had ran off to!

sed: write error
Hey, I was wondering if anyone here could help me.
I've reflashed from GingerBLUR 6.5, and can't seem to apply the market fix. I keep getting a write error when I apply the sed command.

You have to be rooted, and remount /system as read/write prior. The mount command right before the serd command is needed. Also, make sure your "su" command is successful. If not, the rest will not work..

HELP! Su was in the folder but device not found!

I followed the instructions exactly but now device not found and I folowed the video exactly, su is in the folder (((
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
abd reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
The adverts are back on the screen, what do I do please
Its nearly 2am in the morning

device is found now, what point do I pick up the command prompts up at?
please

Rovers82517 said:
please
Click to expand...
Click to collapse
ah, man, I'm seriously lost, it fails everytime with these 2 commands,
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
the su file is definately in the platform-tools folder :/

Rovers82517 said:
ah, man, I'm seriously lost, it fails everytime with these 2 commands,
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
the su file is definately in the platform-tools folder :/
Click to expand...
Click to collapse
If your drivers are installed correctly now, use the root tool in development section. Then there are no mistakes. If you insist on the manual method though, you need to put the su file and superuser.apk in your folder titled carol and Start over completely

onemeila said:
If your drivers are installed correctly now, use the root tool in development section. Then there are no mistakes. If you insist on the manual method though, you need to put the su file and superuser.apk in your folder titled carol and Start over completely
Click to expand...
Click to collapse
the files are in there, I've checked and double checked.
when I can get it to see the device again the command prompt has a # instead of a $
I can't afford to brick this thing, I don't know of any other methods, can you tell me what you mean or post the link?
It's gone 2am now I could do with even a little sleep tonight
Thank you for replying
ah, my bad, I know what tool you mean cheers dude

Rovers82517 said:
the files are in there, I've checked and double checked.
when I can get it to see the device again the command prompt has a # instead of a $
I can't afford to brick this thing, I don't know of any other methods, can you tell me what you mean or post the link?
It's gone 2am now I could do with even a little sleep tonight
Thank you for replying
ah, my bad, I know what tool you mean cheers dude
Click to expand...
Click to collapse
No problem, sometimes it just takes a lot of banging your head.

still no luck
I've copied both files to 'carol' as well as platform-tools, what have I done wrong?

Fixed but I'm not sure how
It repeatedly said file not found but in the end I decided to skip to step 4 on QemuRoot and it had worked lol very strange
Think I'll leave it a while before I attempt custom roms lol
Thanks for your help peeps

Rovers82517 said:
It repeatedly said file not found but in the end I decided to skip to step 4 on QemuRoot and it had worked lol very strange
Think I'll leave it a while before I attempt custom roms lol
Thanks for your help peeps
Click to expand...
Click to collapse
From my personal experience is best way how to root kindle fire by qemu (development part of forum) its quite easy... to solve problem if your device isn't found I had to create folder .android in my “documents“ like it is when you will instantly sdk
You have to create it via command line... mkdir .android
Create there required file how it is described in qemu thread. Reinstal kindle adb drivers and try qemu once more.. that worked for me like a charm.
Tomorrow when I will be on PC I will post step by step guide
Kerbik