Database Info

[Q] I have a Hero flashed for metroPCS and I need to put it back to the original ROM

I have a Sprint HTC Hero (200), it has already been flashed for boost mobile, I am not sure if that means it has a custom ROM but I believe so
I cant download anything from Market (for some reason wont connect, probably from the flash)
I would like to put it to Cyanogen, but would like to set it back to original factory settings (and rom) before i do so...
I tried putting the phone into recovery, used the adb shell command to do it, just sends me to a black screen with a phone with a red triangle/exclamation point overlapping it...
and i figured out that holding the volume down while pressing the volume opens this (assuming its a custom recovery, but not sure how to use it or if it even supports the functions i need)
at the bottom of the recovery there is 3 pictures of android skating (like the cyanogen mod logo), and also...
this is what the custom recovery menu shows
(in green writing)
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.42.02.10.29
Mar 1 2010, 16:02:39
then says
HBOOT
<VOL UP> FastBoot Mode
<BACK> Simlock
<HOME> Recovery
when i push volume up it then changes to say...
FASTBOOT
<VOL DOWN> HBoot Mode
<MENU> Reset Device
<ACTION> Restart to HBoot
im not sure what the recovery is, can anybody help me?
when i HOME in HBoot Mode (Recovery) it just send me to that black screen withe the phone and the red exclamation point
THANKS IN ADVANCE! ANY HELP GREATLY APPRECIATED!
(anybody know how i can check to see if the phone is rooted without having access to the android market? i think if it IS rooted i might be able to just install ClockWorkMod, right?)

It has the original recovery image. Do you have the superuser app in your app drawer?
私のEVO 3Dから送信される。

no i do not have it, and i tried the clockwork install and when i type the su command it says could not grant permission or something along those lines
so i am not sure why i am getting the adb errors, it wont let me root through adb (cant figure out why, everything seems to be functioning correctly, just some commands dont go through, says permission not granted or something similar...
and i tried installing z4root for some reason the phone is saying that it has no program to run the apk... but i just tried downloading a different apk and it installed fine...
any ideas?

i am following this tutorial
http://wiki.cyanogenmod.com/wiki/HTC_Hero_(CDMA):_Full_Update_Guide
and under "rooting the hero (cdma)"
on step 5, i have tried this many times many different ways, i tried doing abd push rageagainstthecage-arm5.bin /data/local/tmp/ (like it says) but it doesnt work, so i do it without the space between .bin and /data, and it works (also tried without the /data..ect.. completely, same result)
then i type adb shell and a $ appears, and then i type chmod 755 (also tried chmod 755 /data...ect... and chmod 755/data...ect...) and it says "Usage: chmod <MODE> <FILE>
so i put in /data/local/tmp/rageagainstthecage-arm5.bin like it says to, but it says not found, and if i try to just do rageagainstthecage-arm5.bin it says permission denied...
why is it saying permission denied? when i use the /data..ect... string (with a space between) its "not found" but if i do the same thing without the string or with the string attached, it works up untill the last part of step 5
any help greatly appreciated, this is really bothing me =/

Untraumatized said:
i am following this tutorial
http://wiki.cyanogenmod.com/wiki/HTC_Hero_(CDMA):_Full_Update_Guide
and under "rooting the hero (cdma)"
on step 5, i have tried this many times many different ways, i tried doing abd push rageagainstthecage-arm5.bin /data/local/tmp/ (like it says) but it doesnt work, so i do it without the space between .bin and /data, and it works (also tried without the /data..ect.. completely, same result)
then i type adb shell and a $ appears, and then i type chmod 755 (also tried chmod 755 /data...ect... and chmod 755/data...ect...) and it says "Usage: chmod <MODE> <FILE>
so i put in /data/local/tmp/rageagainstthecage-arm5.bin like it says to, but it says not found, and if i try to just do rageagainstthecage-arm5.bin it says permission denied...
why is it saying permission denied? when i use the /data..ect... string (with a space between) its "not found" but if i do the same thing without the string or with the string attached, it works up untill the last part of step 5
any help greatly appreciated, this is really bothing me =/
Click to expand...
Click to collapse
Download and install this: http://db.tt/Bltsa73
When it says rebooting you need to turn your phone off and then turn it back on. You should be rooted then

thanks i acctually managed to get z4root on it (did factory reset and it made market work again) so i got z4root and used astro from market to install it and then had root, got clockworkmod from rom manager, and flashed CM7, its nice
but in the process i ended up messing up my motorola defy, and now im kinda worried (the defy is mine, the hero is my friends)
after doing all the adb shell stuff and everything to get the hero working, after i finished i plugged my defy into my computer to charge, and now its stuck in bootloader mode... (and the battery is too low)
so im charging my battery in my friends broken defy he left here for me to fix (broken screen) and when its a good amount charged i can do something, but what should i do? i almost bricked it once, dont wanna do the same thing, i just want my CM7 back lol...
if you dont know its ok, just looking for somebody who may have some help, i need my defy =/

Untraumatized said:
thanks i acctually managed to get z4root on it (did factory reset and it made market work again) so i got z4root and used astro from market to install it and then had root, got clockworkmod from rom manager, and flashed CM7, its nice
but in the process i ended up messing up my motorola defy, and now im kinda worried (the defy is mine, the hero is my friends)
after doing all the adb shell stuff and everything to get the hero working, after i finished i plugged my defy into my computer to charge, and now its stuck in bootloader mode... (and the battery is too low)
so im charging my battery in my friends broken defy he left here for me to fix (broken screen) and when its a good amount charged i can do something, but what should i do? i almost bricked it once, dont wanna do the same thing, i just want my CM7 back lol...
if you dont know its ok, just looking for somebody who may have some help, i need my defy =/
Click to expand...
Click to collapse
try doing an sbf restore just look it up?

I need to know the opposite, how do I flash my hero to metro pcs?
Sent from my SPH-D710 using xda premium

[Hack] remove a lockscreen pin via adb with sqlite3

There are a couple other ways posted for folks who have forgotten lockscreen password or pattern, but this methods REMOVES the PIN. for pattern and password follow other methods
This method requires root access and debugging enabled.
*if debugging is not enabled it can be done from any custom recovery
-reboot recovery and follow code
PIN
Code:
adb shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=65536 where name='lockscreen.password_type';
sqlite> .exit
# exit
adb reboot
step one
Code:
adb shell
make sure you have # in the command prompt/terminal (if not type su)
step two
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
you will now see sqlite>in command prompt/terminal
step 4
Code:
update secure set value=65536 where name='lockscreen.password_type';
still sqlite>
step 5
Code:
.exit
you will see the # again
step 6
Code:
exit
you will now be in the path/to/adb command prompt/terminal again
step 7
Code:
adb reboot
Enjoy full access to the device
Now lets say you think your wife is cheating on you (which she probably is) and you want to check her sext messages but return the PIN back when you are done.
Code:
adb shell
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update secure set value=131072 where name='lockscreen.password_type';
sqlite> .exit
# exit
adb reboot

I find this a bit scary, how would you normally prevent ADB or Recovery hacking like this if your device gets stolen?

BrotherG said:
I find this a bit scary, how would you normally prevent ADB or Recovery hacking like this if your device gets stolen?
Click to expand...
Click to collapse
I recommend Avast Anti Theft.
When your device gets stolen, the new owner will take the sim card out and put his in huh?
Well, anti theft sends a pre-entered number a warning that an other SIM is in it. Via sms commands, you can turn GPS on, send the location, block root and stuff.
It wont be deleted as it is a system app
I use it.
Thanks for the job, needed this for hacking my bros phone xD
Greets!

hahaha. .... these Feds could of used this method. They couldnt get past the lockscreen. Great read here.
How a Pimp’s Android Pattern Lock Foiled the Feds
http://gizmodo.com/5893410/how-a-pimps-android-pattern-lock-foiled-the-feds

Looks like CyanogenMod is working on securing ADB
Security and You
March 16th, 2012
jeagoss
1
Many of you may not give it a second glance, but among all the furor and concern about permissions requested by market apps and privacy, all Custom ROMs (CyanogenMod included) ship with one major security risk — root!
We have been struggling with how to handle this for quite a bit, and took a first step with the first public CyanogenMod 9 alpha builds, by disabling the previously-default root access over USB. You can still get adb root access by running “adb root” in terminal, should you ever need it.
We recently merged 3 patches into CyanogenMod 9, to further address this: http://goo.gl/eCjDV http://goo.gl/oWAFI and http://goo.gl/34vai.
What follows is an explanation of the changes, how they affect you and our reasoning behind them.
What do the patches do?
They disable root selectively and in a configurable way. Users will be able to configure their exposure to root as:
Disabled
Enabled for ADB only
Enabled for Apps only
Enabled for both
How does this change affect the usage of your device, and root apps you have installed?
On a default CyanogenMod installation, root usage will have to be explicitly enabled by the user. This means that the user is fully aware that any application that uses root may perform actions that could compromise security, stability and data integrity. Once enabled, the process mirrors that of the current process, apps that request root will be flagged by the SuperUser.apk and the user will have to grant selective access.
Why the change?
At CyanogenMod, security has always been one of our primary concerns, however, we were hesitant to make a change that might disrupt the current root ecosystem. With CyanogenMod 9 we have the opportunity to do things better, whether its the code in the OS, UI/UX, or security – we are taking this time to do things with a fresh approach.
Shipping root enabled by default to 1,000,000+ devices was a gaping hole. With these changes we believe we have reached a compromise that allows enthusiasts to keep using root if they so desire but also provide a good level of security to the majority of users.
What concerns remain?
Many of you reading this are savvy enough to note a remaining hole in this approach – recovery and unlocked bootloaders. The bootloaders are out of our hands, there is little to nothing we can do on that front.
Regarding recovery – with unlocked bootloaders, a malicious user could just flash a new recovery image (without any potential security we could apply) or just dump the data partition. This however, requires physical access to the device. As such, the security standards for this are highly reliant on you, the device owner. Data encryption is available in ICS to safeguard your data. (Warning for emmc only users – encrypted /data means recovery will be non-functional.)
The onus is on you to secure your device; take care of your possessions, and this risk is minimal. Always make sure you take devices out of your car before you go into the mall and remove them from pockets before washing laundry. Common sense is a basic security tool.
But Why?
We honestl
Click to expand...
Click to collapse
Source: http://www.cyanogenmod.com/blog/security-and-you

mDroidd said:
I recommend Avast Anti Theft.
When your device gets stolen, the new owner will take the sim card out and put his in huh?
Well, anti theft sends a pre-entered number a warning that an other SIM is in it. Via sms commands, you can turn GPS on, send the location, block root and stuff.
It wont be deleted as it is a system app
I use it.
Thanks for the job, needed this for hacking my bros phone xD
Greets!
Click to expand...
Click to collapse
All true, if speaking of a casual thief- maybe you left the phone on the bar and someone couldn't resist the temptation. A couple of months ago my wife's phone was recovered in such an occasion- got an sms from Avast Theft Aware with the new number, contacted the rather surprised "honest finder" and he decided to return it back to us.
Anyway, two weeks ago went scubadiving and when returning to the car found the window broken and sure, among other stuff (wallets, scuba gear etc) also both our phones were stolen. However, this time it looks like the thieves were not quick to put their own sim card. Actually, it looks like they've removed the batteries, thrown the sim cards away (the're useless anyway as the carrier blocks the sim).
Since then, no signs whatsoever that the phones have been turned on, sims replaced or that someone has tried to type wrong security pin or whatever- no sms notifications, no emails, no webtracking, nothing.
My guess- the thieves sell them for a small fee (20% of street price?) to some lab or someone who knows "how to deal with it"- do a good wipe (not just factory reset) and remove whatever stuff was installed- system app or not- then put them on market for sale as second hand. Or maybe they just wait with patience a few weeks until you stop looking for it?
So, sometimes these apps like Avast, Cerberus and the such work, sometimes not. Better to keep the phone safe and not rely on it being stolen by a stup!d thief...
On the bright side, one can consider it as an opportunity for upgrade

irst I typed in :
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
However, in spite of what he stated, sqlite>in command prompt doesn't appear.
Instead, I get
/system/bin/sh: sqlite3: not found
how do i set sqlite working?
I'm unable to launch sqlite3 from adb shell
I can manually launch sqlite from the folder but not in cmd

You have to install sqlite3 - https://play.google.com/store/apps/details?id=ptSoft.util.sqlite3forroot&hl=en

Is there a tutorial for a password locked screen too?

Is there another way to bypass the pin code lockscreen? Cus´ I´m always stucking on:
" /sbin/sh: sqlite3: not found "
I have installed sqlite from market

any idea?

whoa, you guys are amazing, this worked like a charm on a password locked tablet
polaroid pmid70c

this is a scary concept if you value your android device consider installing a paid service like dyndns and install the paid version of real vnc onto the device and have ssh setup as well this would help to recover your phone in the event it becomes stolen you could ssh into it launch apps view and control the phone remotely via vnc hell even take pictures ,, turn on gps all sorts of cool things

holm94 said:
Is there another way to bypass the pin code lockscreen? Cus´ I´m always stucking on: " /sbin/sh: sqlite3: not found " I have installed sqlite from market
Click to expand...
Click to collapse
your phone is root enabled? Superuser or SuperSU app installed? Connect USB and run "adb root" and that works?
Try this installer app again https://play.google.com/store/apps/details?id=ptSoft.util.sqlite3forroot&hl=en
I flashed the root feature with SuperSU update zip file in recovery mode, and rebooted.
I grabbed a 'sqlite3' binary made for ARM cpu from the 'net and manually pushed it to my phone's /system/xbin/ directory.
1. unzip this sqlite3 file
2. power on device in custom recovery mode, ('factory mode' also may work, such as in some chinese phones, including my Jiayu)
3. connect USB cable, and in recovery mode, mount the /system directory and any other directorys you will use (see screenshot)
4. open a command prompt (terminal) on computer and run these commands
Code:
[I]adb root[/I]
[I]adb remount[/I]
[I]adb push sqlite3 /system/xbin/sqlite3[/I]
[I]adb shell[/I]
[I]chmod 755 /system/xbin/sqlite3[/I]
[I]sqlite3 -h[/I]
...
exit
adb reboot
* alternate method: if #4 'adb root' does not work, then turn on phone to normal running mode and do:
Code:
adb push sqlite3 /data/local/tmp/sqlite3
adb shell
su
mount -o rw,remount /system
cp /data/local/tmp/sqlite3 /system/xbin/
rm /data/local/tmp/sqlite3
chmod 755 /system/xbin/sqlite3
sqlite3 -h
...
exit
exit
adb reboot
"exit" twice for alternate method.
All this can be done over Wifi instead of USB via a SSH server app.
^_^
I can run all the commands fine, but the PIN lock is still there on my phone after reboot. Android 4.2.1, Jiayu Chinese ROM. So method does not work.

help me, im stuck at " error: device unauthorized. Please check the confirmation dialog on your device."

I know this is super old thread but I used this method and combination with other commands I found on internet to bypass my lockscreen on att samsung galaxy s7 phone I had forgotten pin code on.
I was using fingerprint for a couple of months and rebooted phone for an update and it requires pin code first time before using fingerprint again and I had flat out forgot it. When it got to 1 hour wait between input retrys I searched and found this and other methods. I read no methods work unless rooted.
Luckily and thank God I'm rooted and usb debugging turned on and I have adb installed configured and have used with phone before....thank God. Because pretty much every and anything else on the phone is turned off on phone so I keep off the grid.
I know I'm dragging this out but I want to document and reiterate the value of xda. I will try and remember exactly what I did and may just redo it to be sure and list my exact steps.
One thing, I don't have sqlite3 curser when connecting with adb....I have hero2qltatt or something like that .....I'll get corrected with an edit when I go thru again to make sure.
Also, once I got past lockscreen, when I went into setting/lockscreen&security/ on the phone it still showed pin,fingerprint as security but somehow which still baffles me there was a pick for 'swipe' available....but I still don't know how that happened or how it appeared but I kept trying different pin codes to try to reset that which now there were no limits or time delays but still couldn't remember and then I saw a pick for 'swipe' and that solved it all. I rebooted again to be sure and perfect. Then I went in to recovery and wiped cache and now my phone is back exactly as before.
I wrote down the pin code this time.
Eventually soon I will rerun my steps and document exactly and maybe there is already a more recent account but I found this one first and it pretty much worked....thanks.
OK this is what I used:
adb shell
cd data/system
su
rm *.key

reboot

[Q] Atrix 4G problems after root

So last night I rooted my phone using an article from brief mobile. Can't post a link since I'm a new user so here's some copy paste:
Extract the ADB-Fastboot package and root image to your C:\ Drive under a new folder titled “root”
Put your device into Fastboot mode: – Turn off your device. – Hold down the power button and downward volume button until you see “Fastboot” on your screen – Push the upward volume button
Open your command prompt (Start >> run “cmd” >> enter)
Type the following commands
cd C:/root
fastboot flash preinstall root.img
fastboot reboot
Enable USB debugging (Settings >> Applications >> Debugging)
Type the following commands
adb shell
/preinstall/dosu
Type the following commands
/bin/mount /system -o remount,rw
cp /preinstall/su /system/bin/su
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
Congratulations! You are rooted!
Anyways everything worked out fine, the only hang up was an error that said "fastboot is not recognized as an internal or external command, operable program or batch file" after typing /preinstall/dosu. Anyways I tried it a few different times and then googled it and found another site that said just ignore the error. So I went on and finished the guide. Everything seemed successful, root was achieved. After rooting I removed a few bloat programs and went to bed for the night. Today I have had issues with the notification bar at the top crashing randomly, if I restart the phone the bar is there but eventually it just goes away. Also if the phone is asleep or I'm on any screen but the home screen when someone calls the phone rings but the thing that pops up that allows you to answer never comes up. I also do not get any text message alerts, the messages come through but I'm never alerted I have to open texts and see if I have any. So after all these issues I thought maybe I uninstalled something that was needed so I opened up Titanium Backup and re-installed all of the programs I uninstalled. Still no dice the problem persists. So I did a factory reset on the phone and still am having the same problem. Can anyone help me? Sorry if this was long winded, just trying to be descriptive.
Thanks

Any help out there?
Sent from my MB860 using XDA

Maybe you should try wipe data/factory reset?
Clear apps data-SystemUI,Settings,Notification bar etc.

miui-lover said:
Maybe you should try wipe data/factory reset?
Clear apps data-SystemUI,Settings,Notification bar etc.
Click to expand...
Click to collapse
Then you can move on over to here:
Neutrino
http://forum.xda-developers.com/show....php?t=1398819
Or any other ROM you might want to flash.

How To Root An AT&T HTC One X [No Longer Working]

This root was rendered unusable at this time due to AT&T disabling the Ready2Go app installation feature. Working on a work around now.
Original content:
http://www.androidpolice.com/2012/0...the-att-htc-one-x-on-version-1-85-or-earlier/

Hope you get your One X soon dude!
Confirmation number: 8PH11891CA483914J

In! Thanks Justin!
Billy

Damn, thanks a lot!

jcase said:
Now comes the timing critical part, you have to use ATT Ready2Go to Download "AT&T Mark the Spot", and interrupt the install process right after the download has finished. Easiest way is to reboot the device, but we have found other ways to do it.
Click to expand...
Click to collapse
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.

id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.

id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office

jcase said:
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.
Click to expand...
Click to collapse
Hah, well now I just feel dumb as I am on try 10 or so. I must not be able to hit the timing right at all. I'll keep at it, as I am constant as the northern star.

Don't feel dumb, it is very timing critical, with few real indicators of when to pull it off.
Maybe xfinrodx or designgears can chime in on this one

noobsquared said:
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office
Click to expand...
Click to collapse
Turn your ringer off, it will silence the startup sound. At least I can help with that!

id10terrordfw said:
Turn your ringer off, it will silence the startup sound. At least I can help with that!
Click to expand...
Click to collapse
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.

I have been deleting the file from data/install
adb shell
cd data/install
rm com.att.android.markthespot.apk
exit
then repeat the process...i'm in double digits on attempts...going to have to walk away from it for a bit.

going on 10x for me and still nothing. Any suggestions?

id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!

noobsquared said:
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.
Click to expand...
Click to collapse
Um, why are you doing a factory reset?
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
I will give that a shot, and I should have thought of that. Thanks!

xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Good advice, was the first person to test it for me. I confirmed it with 4 users before posting, and all got it eventually.

id10terrordfw said:
I will give that a shot, and I should have thought of that. Thanks!
Click to expand...
Click to collapse
I was the first one I'm aware of who used this exploit a couple weeks ago. I won't claim that the process is clean, but it should work for you if you do it the way I intended the instructions to read... Good luck!

Thanks for all the help but I think this red bull is not working today.
Here is what I did:
First CMD:
Code:
adb shell
cd /data/install
ls -l <- it only gives me the file name..it doesn't tell me the size.
Also, I delete the file and run the first command in second CMD and right after that I see this in ls -l:
[email protected]:/data/install $ ls -l
ls -l
lrwxrwxrwx shell shell 2012-05-25 12:16 com.att.android.markthesp
ot.apk -> /data/local.prop
Second CMD:
Execute:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
Wait to execute:
Code:
adb reboot

xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $4}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot

dharani1234 said:
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $5}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot
Click to expand...
Click to collapse
If you can get a working script, that was reliable I would love to post it in the OP. To get an idea of the size, you could install the app, and do adb shell ls -l /data/app/<filename>

Sudden loss of service with CM7 on Sprint

Weird. I've been running CM7.1.1 on a Nexus S D720 for several months with no issues. This morning, I made some calls, a few texts and suddenly the phone said "No Service". Signal status was -1dbm. Called Sprint service they said they had no outages in this area. After removing battery, powering off, rebooting several times I figured she was toast. I booted into CWM recovery and restored a backup image from Jan 2012. Took about 5 mins. Rebooted phone and suddenly I had service. Also noticed my phone downloading ICS from Sprint updates.
So, what's up with that? Did sprint send out the update, noticed my phone didn't match stock, and disabled service?

They were probably mad that you were still on CM7. Kidding, sounds like a PRL problem.

xdart said:
Weird. I've been running CM7.1.1 on a Nexus S D720 for several months with no issues. This morning, I made some calls, a few texts and suddenly the phone said "No Service". Signal status was -1dbm. Called Sprint service they said they had no outages in this area. After removing battery, powering off, rebooting several times I figured she was toast. I booted into CWM recovery and restored a backup image from Jan 2012. Took about 5 mins. Rebooted phone and suddenly I had service. Also noticed my phone downloading ICS from Sprint updates.
So, what's up with that? Did sprint send out the update, noticed my phone didn't match stock, and disabled service?
Click to expand...
Click to collapse
If you ever have some funky issues like that you could always try a hands free activation.. Has helped me in the past on any issues.

qccoles said:
They were probably mad that you were still on CM7. Kidding, sounds like a PRL problem.
Click to expand...
Click to collapse
Haha.. could be. How do I re-root this thing with 4.0.4 on it? Found some stickies in the nexus s forum but they are from 2011... still looking.

xdart said:
Haha.. could be. How do I re-root this thing with 4.0.4 on it? Found some stickies in the nexus s forum but they are from 2011... still looking.
Click to expand...
Click to collapse
Do you mean how do you root while on stock ICS? http://www.youtube.com/watch?v=GSD92Qjt5Og works perfectly.

qccoles said:
Do you mean how do you root while on stock ICS?
Click to expand...
Click to collapse
Yep, that's what I mean. I'm on Linux though, so would need to dig out the appropriate files as well as commands from the run.bat file and apply them at the command line (I have adb and fastboot).
The dates on some of the files in One-Click-Nexus-S-4G-5.1.zip are from Nov. and Dec of 2011. Would it be wise to use these even though there are newer versions available?
eg:
* Superuser-3.1.3-arm-signed.zip from androidsu.com/superuser/
* download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.0-crespo4g.img

xdart said:
Yep, that's what I mean. I'm on Linux though, so would need to dig out the appropriate files as well as commands from the run.bat file and apply them at the command line (I have adb and fastboot).
The dates on some of the files in One-Click-Nexus-S-4G-5.1.zip are from Nov. and Dec of 2011. Would it be wise to use these even though there are newer versions available?
eg:
* Superuser-3.1.3-arm-signed.zip from androidsu.com/superuser/
* download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.0-crespo4g.img
Click to expand...
Click to collapse
I used the exact file not even a month ago. Although SU updates through market and I went with TWRP instead of CWM. Everythings perfect over here. I couldn't tell you a thing about linux, although I do plan on making the switch from Win7 very soon.

qccoles said:
I couldn't tell you a thing about linux, although I do plan on making the switch from Win7 very soon.
Click to expand...
Click to collapse
UPDATE#2: Ok, so it seems the red triangle+bugdroid has something to do with the recovery image being hosed. There is also a file named /system/recovery-from-boot.p which needs to be renamed PRIOR to flashing with CWM, or CWM will not "stick" and the red triangle+bugdroid will keep coming up.
In order to rename it, you have to remount /system as read-write. After renaming the file to /system/recovery-from-boot.p.bac I rebooted into recovery and re-flashed CWM with fastboot, only this time I flashed in CWM 6.0.1.0 instead of the recovery image from the One-Click-Nexus-S-4G file. After wiping cache, dalvik cache, data and factory reset (from CWM) I selected "reboot system now" and was presented with and option to "YES - Disable recovery flash". This option apparently fixes the hosed recovery issue somehow (maybe renaming /system/recovery-from-boot.p ?) so I selected YES and rebooted. rebooting into recovery seems to work OK now with no red triangle.
UPDATE #1: I tried rebooting into recovery a few hours later and just get a screen with a green droid+red triangle icon. Um any ideas where CWM went?
Thanks for the info. I just got my D720 rooted in Linux with the commands below. Maybe it will be of help when you switch.
I am kind of picky about verifying md5sums. I like to be able to make sure they downloaded correctly/haven't been altered. I wasn't able to google the md5sum (c4cecfc494610d6c0f13b2237bd212a0) for root.zip in the One-Click-Nexus-S-4G file. Hard to say why it's not out there, but I opted instead for Superuser-3.1.3-arm-signed.zip from androidsu.com.
files used:
recovery.img (from the One Click..) - md5sum - 5988836a66f535c4a7d499ee417ee9c5
Superuser-3.1.3-arm-signed.zip renamed to root.zip - md5sum - b3c89f46f014c9df7d23b94d37386b8a
unlock phone (!!! wipes it !!!)
need to enable settings > applications > developer options > select "USB debugging" or adb won't see it
# adb devices (should show your device. if not adb kill-server; adb start-server and try again)
# adb reboot-bootloader
# fastboot oem unlock
# fastboot reboot
** Phone took longer than normal to reboot after this.
After rebooting
# adb reboot-bootloader
# fastboot flash recovery recovery.img << from One-Click-Nexus-S-4G
- use volume-down, select recovery and press power
- go to the mounts and storage menu
- if it says "unmount /sdcard" then you do not need to follow this step)
- if it says "mount /sdcard", then select it.
- select "+++++ Go Back +++++"
push root.zip to phone and install it
# adb push root.zip /sdcard/
- Select "install zip" from sd card
- Select "choose zip" from sdcard
- Scroll all the way down and select root.zip
- choose yes
- select "+++++ Go Back +++++"
- select "Reboot System now"
After rebooting, I found the SuperUser icon was indeed in able to su to root
# adb -s 416321DE1F8100FD shell
[email protected]:/ $ su -
[email protected]:/ #
UPDATE - Red Triangle + Bugdroid Fix
Login to the device and su to root. All the commands starting with 'su -' up to 'exit' are done on the device and NOT the host OS.
# adb shell
$ su -
# cd /system
# mount -o remount,rw /system
# mv recovery-from-boot.p recovery-from-boot.p.bac
# mount -o remount,ro /system
# exit
Reboot the device into recovery mode using volume+power, or adb reboot recovery
(These commands are done from the host, just for clarification)
# fastboot flash recovery /tmp/recovery-clockwork-6.0.1.0-crespo4g.img
After that, select recovery from the menu and you should get CWM 6.0.1.0 where you can do a backup or whatever.