Database Develop

Rooting G1 - Telnet prompt showing question marks in diamonds? Help!

I have rooted my phone once before like a year ago, and it worked like a charm - but when the official 1.6 came out it apparently unrooted me (I assume thats what happened?) All I know is now when I try to run root required apps it tells me I'm not rooted.
So I figured to just start over from the beginning. I downgraded to RC29 no problem, but when I get to the telnet step it shows a pattern of question marks in diamonds, with boxes separating them. Like this:
<?><?>[]<?><?>[]<?><?> <?><?>[]<?><?> #
I run the commands anyway, (with the Recovery Image and HardSPL on the root of my SD card) - with each command returning two hash marks # #. But the commands don't seem to do anything, because even when I finish ROM Manager tells me I'm not rooted.
Back in Telnet, I can 'ls' to see my directories, including a root folder - but I'm not sure that means anything.
Not sure where to go from here - any help would be greatly appreciated...
-TQ

........................................

The following Observation was made :
Wrong Section. Belongs in Q/A
K so when u go in adb and type adb shell do you see # or $
Please let us know.

Apologies for posting in the wrong forum. And thanks for moving it.
I can't connect to my phone via ADB - I just get 'device not found' even though I have the USB drivers downloaded. If I do 'adb devices' it shows a blank list.
I've looked into how to resolve this, but with no luck. The phone shows up in device manager under the 'Disk Drives' category as "HTC Android Phone USB Device" when everywhere I read says it should show up under the ADB interface section as "HTC Dream Composite ADB Interface".
I've tried USBDeview to reinstall it properly - no dice. And I tried manually updating the driver with ones I downloaded, but windows says I already have the best driver installed.
I don't know what to do now...

New member, have a few questions.

Ive had the hero for a while now and now feel its time to root it since there doesnt look like there will be anymore major updates.
I had first tried to root it through the unrevoked method and couldnt get passed code #8: su
It just kept saying that su wasnt a valid code or something like that. so after a couple other tries i scrapped it. eventually found the 1-click way and did that on my phone. But nothing seems to have changed. The frst thing i wanted to do was uninstall the useless sprint apps such as sprint tv etc... but was unsuccessful in finding a way.
If you guy could give me a little insight on what i need to do or point me in the right direction i would appreciate it.
there is just so much info on this site that it makes it a littl overwhelming for somebody just getting into the game.

best way to test if you have root is open terminal emulator and type su if you get a # in the prompt you have root.
Or from adb try
adb remount
adb shell and if you have a # instead of a $ in the prompt you have root.
If that works then to remove the crappy sprint apps open a cmd and type
adb remount
adb shell
cd system/apps
ls
then look through and find the ones you dont want and type this
rm my_bloat_app.apk (replace my_bloat_app with the app you don't want)
and hit y to comfirm and its gone.

madeSICC said:
...The frst thing i wanted to do was uninstall the useless sprint apps such as sprint tv etc... but was unsuccessful in finding a way.
Click to expand...
Click to collapse
Titanium Backup can do it. Download it and learn how to use it. It will become your friend.
If it can't do it, you still aren't rooted!

Remount: Not Found

Hi Everyone!
I was trying to change the sales code using remount command by rotohammer but at terminal emulator and ADB I get remount: not found.
ROM: Overcome 1.4.2 with 2.1.2 kernel
Terminal Emulator
ROOTED.
Regards.

Dear DarkPal ,
if u only want to actually change your product code, u can use SGS csc selector
after that when it reboot u , it will see yellow words show
"installing multicsc-XXX" XXX is the product code.
For the overcome rom, there have 7 product code for u to choose, but I don't exactly know which is for your country.
To verify , u can connect it to KIES and it will show your product code.
For the ADB issue, which kind of flashing process u use? hemediall or odlin?
I sometimes can't have ==> adb devices as I have 2 I9000 and 1 TAB, always flash TAB and I9000 for my friends. So the usb driver sometime can't work. as too many device have being connected. If this happened, I will try step by step in the following until the driver work again.
re-install device driver by KIES
adb kill-server and than reboot the computer
control pannel=>system manager=>device manager=>uninstall samsung usb driver and than connect the phone and window will reinstall the driver.
regedit user-local-key =>samsung=>kies=>deviceDB=>clear all things and then reboot
usually these steps will let me redetect the device
But in some older rom of I9000 , it never be connected as the rom fault in USB connection app. But this will not the case for overcome rom itself as I tried it before and have no issue,it work fine..
hope this help
p.s. if u just want to hack KIES, use spoofFW, it have some preset product code for the western country, after hack you can update through KIES to the newest official firmware of your own country.
p.s. use this command in adb shell or terminal emulator on your tab to get in to csc selection section:
am start -a android.intent.action.MAIN -n com.android.Preconfig/com.android.Preconfig.Preconfig

ADB does detect the device my friend and gives it a number. The issue is that some commands in adb are not working. Remount command being one of them.
I flash through ODIN.
Thanks for SGS selector

bump.
I still get the remount: not found which is rendering ADB not usable for me. Any help would be appreciated.

I asked the same question a few weeks ago, using same odlin.
I was hoping rotohammer would chime in and state the issue.
Went to Android SDK and downloaded all they said to get, and still no remount.

[Q] Need help restoring my KFSOWI

Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.

Does nobody have an idea? Would be very sad if I couldn't use it anymore. Although I'm the only one to blame. Does someone have experience on sending it back to amazon for warranty? As far as I know rooted devices lose their warranty.. :-/

Karelian_ said:
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Click to expand...
Click to collapse
At this point, I would send it back to Amazon. all they will check for is physical damage and send it back to China. I hear some people bricking their tablet several times and getting a replacement. Thing is that Amazon's warranty questions are only water damage and did you drop it questions. So you don't even have to BS them to get a replacement.

If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app

braider said:
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
There are no exploits for this boot loader yet. Don't think a fastboot cord will do much at the time.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app

Did noone come up with a solution, because i did the same thing, with the framework-res.apk
i can make a fastboot cable if itll do any good without an unlocked bootloader. could i possibly push the most recent update.bin from amazon and restore the device to stock???
---------- Post added at 04:06 AM ---------- Previous post was at 03:10 AM ----------
i wouldnt take bricked for an answer and i found a fix
what i did was make sure the kindle was connected to adb and typed the following
adb reboot
adb wait-for-device shell su
the shell managed to snag the SU file and displayed # before the device looped thru all of the boot apps over and over, but then CMD froze.
so i tried this
adb reboot
adb wait-for-device shell su mount -o remount,rw -t ext4 /dev/block/platform/omap/omap.hsmmc.1/by-name/system /system
and in one line got root access and remounted the system as RW
my problem was that framework-res APK was replaced with ZIP so all i had to do was rename it
# cp /system/framework/framework-res.zip /system/framework/framework-res.apk
and success!!
# exit
$ exit
adb reboot
and she booted right up!!!!

First response so please be kind. My KFSOWI is stuck in the bootloop too. I have a factory cable and can get into fastboot but don't have any factory images to restore. Anyone have any ideas?

Do you get any adb access? I don't think casebook will be any help until someone unlocks the bootloader
Sent from my KFSOWI using XDA Premium 4 mobile app

[Q] Pull data with broken screen

Hello,
I googled and searched the forum but none o the threads apply to my problem as far as I can see. :/
So my old phone finally dies more or less... and I am trying to get the picture from the internal storage.
My setup: I9000, running CM11 (not sure which nightly exactly), rooted, BUT usb-debugging could be off I dont know for sure.
I can go to recovery mode but as the screen is broken I am limited with my actions. So using
Code:
adb devices
I can see my device
Code:
<long number here> recovery
Here is what I tried:
Code:
adb pull / H:/backup
This does not work because after a short while it aborts with an error message: "... no such file or directory"
Using
Code:
adb shell
followed by cd sdcard gives me a "cant cd to sdcard"
If I try to cd into other directories they are empty when trying to list them with ls.
su is also not found but adb root shows that it is already running as root.
Afterwards I tried Android Commander but that also did not work for me because Android Commander did not show my device and it also crashed after a while.
To make a long story short I am desperate...
What else can I try to get my data?

push
no one?

SaphirX said:
push
no one?
Click to expand...
Click to collapse
I don't think you can just PULL the whole "/" partition. The long number you listed there is likely to be your IMEI number (Just a guess).
EDIT: You might want to check this out: http://stackoverflow.com/questions/19225467/backing-up-android-device-using-adb