Database Info

Getting root on RC29 without all keys on keyboard?

OK, this is going to sound waaaay out there.
In the past week, I've had two G1's crap out on me. Well, one crapped out on me (the keyboard), and the RMA came damaged. #3 arrived yesterday, and it's rooted, Cupcaked and ready to go.
I restored the RMA unit back to RC33 without root. Everything OK, it's good to go back to the factory.
On the first one though - I went back to RC29 and re-installed the original SPL. What I didn't realize was that the custom splash image that I had installed wouldn't be overwritten in the process, so you guessed it - I've got my custom image coming up right after the G1 splash screen.
I'm still on RC29, so I'd just root it, except for one nasty little problem - not all of the keys work. Particularly - the enter key, which makes starting the telnet daemon impossible (at least to me).
So that's where I am. Does anyone know how I might either be able to root this sucker without having access to the enter key (is it possible to run a script, or is there another keystroke combo substitute for enter)? Is it possible to remap keys? Is there some other way to change that splash image back?
Or am I resolved to sending this thing back with a splash image that screams 'hey, this thing isn't stock!'

use adb to start telnet?

You could probably use ADB somehow, not sure the specifics though. Just out of curiosity, what is ur splash??

giantcrazy said:
On the first one though - I went back to RC29 and re-installed the original SPL. What I didn't realize was that the custom splash image that I had installed wouldn't be overwritten in the process, so you guessed it - I've got my custom image coming up right after the G1 splash screen.\
Click to expand...
Click to collapse
You used RC29 DREAIMG.NBH and it didn't reset your custom splash? Interesting.

giantcrazy said:
Or am I resolved to sending this thing back with a splash image that screams 'hey, this thing isn't stock!'
Click to expand...
Click to collapse
yeah send it like that... i had the same problem as you... and forgot to change the splash image... but i sent it like that to tmobile... been 2 months already and they havent said anything....

I cant seem to get adb working - isnt the HardSPL a requirement for adb? Would it be running on a stock RC29 phone with the regular SPL?
I thought of trying an app with a soft keyboard, but I don't know whether that'll work. I ran out of time to play with it yesterday so today's first try will be the soft keyboard.
My splash isn't anything offensive, just a picture of my kids. And it does come up after the initial splash screen (it seems the NBH file is resetting the first splash only, since I had put it in both spots). Failing the soft keyboard, its going to be time to send it back the way it is and hope TMo doesnt get bent out of shape (the phone does work and its in pristine condition, just a few of the keys are shorted somehow, and the water damage indicator is as white as can be).
Thanks for the suggestions though!

The original Eng. SPL supports fastboot..
I don't know if you can find it - I'm pretty sure the one in the sticky is signed with the test keys. And if you do find it, will the phone let you apply it??
Just throwing out an idea...
Good luck.

boogie1077 said:
The original Eng. SPL supports fastboot..
I don't know if you can find it - I'm pretty sure the one in the sticky is signed with the test keys. And if you do find it, will the phone let you apply it??
Just throwing out an idea...
Good luck.
Click to expand...
Click to collapse
Interesting - I'll seek out and report back. Thanks for the tip!

Nope - no dice To get the engineering SPL installed you still need to have the modified recovery image working.
What am I missing here - does adb need something else to work? I thought it'd work with a stock phone, although without root it'd be of lesser value.

no special form of adb is needed to use adb, what you are going to need to do is try this:
adb shell input text telnetd
adb shell input keyevent 66
those two commands are exactly like if you had typed them on the phone itself the first obviously types telnetd and the second hits enter for you. try it out and let me know if you need any more help, i may or may not be on most of the day i am going to see star trek tonight
also you wanna make sure that usb debugging is turned on in your options i think it's settings>applications>developement>usb debugging but i might be wrong, my phone isn't nearby

tubaking182 said:
no special form of adb is needed to use adb, what you are going to need to do is try this:
adb shell input text telnetd
adb shell input keyevent 66
those two commands are exactly like if you had typed them on the phone itself the first obviously types telnetd and the second hits enter for you. try it out and let me know if you need any more help, i may or may not be on most of the day i am going to see star trek tonight
also you wanna make sure that usb debugging is turned on in your options i think it's settings>applications>developement>usb debugging but i might be wrong, my phone isn't nearby
Click to expand...
Click to collapse
Thanks for the suggestion - I did get adb back, but when I entered the first shell command after connecting, I got the 'telnetd' up , but the carriage return/enter seems to not be working.

ok, well my next suggestion is a stretch and i'm gonna need to research a few things to even know exactly what to do, but what if you change the mapping of the keys so that whan you hit the enter key the phone responds by pressing the alt key and visa versa. i am not sure where the key mapping is stored i am looking for it now, but it seems like it would work ok(in theory)

tubaking182 said:
ok, well my next suggestion is a stretch and i'm gonna need to research a few things to even know exactly what to do, but what if you change the mapping of the keys so that whan you hit the enter key the phone responds by pressing the alt key and visa versa. i am not sure where the key mapping is stored i am looking for it now, but it seems like it would work ok(in theory)
Click to expand...
Click to collapse
That was one of the first things I thought about trying, but couldn't find any way to remap the keys. I'm going to go back to searching for it.

Well, I'm giving up.
I've tried everything I can think of, along with a few suggestions here. It seems that unless I start the telnet daemon from the home page with the keyboard it just ain't happening. Not an adb command, not a soft keyboard (and I tried a couple). Nada.
Thanks again for all your help - now I just have to hope this thing doesn't run up a red flag over at T-Mo...

[Q] MSFT Employee HardSPL'd Device Messing Around

I have a device that used to belong to a MSFT employee. At Microsoft you can just hand in your device and they will put a new ROM on it for you. So first thing I did when I got it is to HardSPL (OliNex 1.90) it and load up a new ROM (the one on it was a couple of builds back, and GPS didn't work etc.).
The strange thing is that ROMS seem to be 'loosing' files (as far as I can tell - apps won't open etc.) after a few days of otherwise great operation. If the device is rebooted, it's almost like a hard-reset; although the installation takes next to no time: and it gets stuck on the splash. Hard resetting the device makes it work for a few days more. The device didn't have these problems with the MSFT ROM (which I stupidly didn't backup).
I have tried a few ROMs and they all seem to have the problem:
MagicROM_23541_Sense25_Mar01
TAELROM_v4.23541_SENSE_2.5_28FEB10_LD
Timolol_5100207TH (awesome ROM)
So my current plan:
Flash stock ROM.
Flash stock SPL.
Flash stock ROM (hoping it will clear anything funny MSFT put on it).
Hard SPL.
Flash Timolol Stock-Like (seems to have the problems the soonest - 2 days max).
Does anyone have any other ideas?
Thanks guys.

I assume since you posted in the Touch Pro2/Tilt 2 section, that you own one of those devices. The roms you have mentioned below are (I believe) for a touch pro/fuze device. That could be your problem. Although, I would assume that you have one as I'm sure a rom for a different device would even flash to the device period. If you have the right rom/device combo and its a touch pro, then you should post in the thread for the roms. More details such as network and device will help the most.

Ah crap - the dangers of having too many tabs open. Can I move the thread myself?

moitoius said:
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
Click to expand...
Click to collapse
i moved it for you good luck at finding a solution

I don't think it's a hot idea to flash the stock spl. I'm not sure that it can be over-written with hard spl-you'll have to ask in the hard spl thread. If you do it, you might be stuck with the stock rom. Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.

Farmer Ted said:
...Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Click to expand...
Click to collapse
Thanks, that is significantly fewer steps . I will do that for now and report back in 2 or so days...

Small update - just flashed the latest stock Fuze ROM. Just before the customization app come up I saw that device.exe crashed... In any case, I will see what happens with the custom ROM.

You may need to reformat the memory of your phone. Having device.exe crash on a stock rom during bootup is kind of weird. I've never done it myself, but there are threads on it in the Leo forum. I wouldn't try the apps that they've put together, though. I guess you can search around for "Task 29" to find out how to do it properly.

Moved as not ROM Development.

@OP:
If the device was flashed on a regular basis, it's possible that the device flash memory is near end-of-life.
You could try running Raphael Diagnostics on it to see if that sorts it out.
HTH,

What is the lifespan (in terms of flashes) for a device like this?

Plus minus 2 days - it has been able to go as far as 5.
According to this post: http://forum.xda-developers.com/archive/index.php/t-514940.html
These are good options:
http://forum.xda-developers.com/showthread.php?t=435527
http://forum.xda-developers.com/showthread.php?t=491554
This one in particular: http://forum.xda-developers.com/showpost.php?p=3446141&postcount=16 (it applies to Rhodium, but people have had success with it).
Apparently Task 2a (equivalent of 29) is disabled on the OliNex 1.90 SPL - so I can't do a NAND format without reflashing the stock SPL (not that I would attempt that myself in any case ).
I'll run RaphaelDiagnostics and see if that comes up with anything.
Thanks for the help so far guys, I first want to see if the stock flash I did works (I smell a Wiki page).

I tried out the raphdiag-it's pretty cool. I've been having a few weird issues lately on my fuze. In particular, all of a sudden my boot-up time seems to have gotten slow (millisecond to idle thread went from 65-70 sec to 90-95 sec, and I hadn't messed with start up programs). Also, I have been having an issue with files on the main memory becoming corrupted, which has just been weird. Anyway, I ran an 'info 8' with mtty a few weeks ago, and it came up with 7 bad blocks, which seems normal. So, I ran raphdiag this morning, and ran the format nand routine. I was a little surprised, because after running it, I soft reset and the phone booted up normally like after a hard reset. I thought that it was going to wipe the entire rom memory clean, leaving only the radio, bootloader and splash screen. It didn't seem much different from a hard reset. The good news is that my startup is faster. With a setup I was using beforehand, the millisecond-to-idle-thread speed was 76 seconds, and after the format it was down to 71 seconds. However, I ran an 'info 8', and the memory analysis hadn't changed at all (same 7 bad blocks). I'm not sure if the formatting (task 29 or this) is supposed to clear that up, though.
I put both the raphdiag.nbh and a raphimg.nbh on the root of my normal 16 gb card. When you go into bootloader, it does a quick image update (takes about 2 seconds), then the screen tells you to push power for a rom update or push the action button to go into diagnostics. From there, you have maybe 4 or 5 choices. Scroll up and down with the up/down buttons, then push action. The first is a set of hardware tests, the second is something like 'run in/on', which appears to be a test scheduler. The 3d is the NAND format option, and I think the 4th and 5th options are 'calculate rom checksum' and then 'skuid', or something like that. To exit, I just soft reset, or used soft reset/vol down to go back to bootloader. After the format, I tried to flash (I think it called it re-flash), but it said there was no image present. You may need to do this on a clean card to get it to work (that is, format and then flash off the same card without swapping things out).
The diag tests are kind of cool. There's an auto mode that runs through all of them, but you have to do things to get it to work. The first is an LED test. The screen turns red, you stare at it for 5 min wondering what the hell is going on, then push the action button for the hell of it. Then the screen turns green. Push it a bunch more times, and it goes through shaded and checkered screens and whatnot, then it tells you it passed the test. There's a test for the slider, and you need to slide the keyboard in and out. The qwerty test was weird. It's configured for a touch pro (not a fuze), so I didn't know what the hell to do at first. The screen just says 'QWERTY_KBD_1', or something like that. I tried hitting the '1' button, and fn-1, and it did nothing. Then I just hit the top left button, and it said OK and prompted to hit 2. So, you just push all the keyboard buttons from left to right, top to bottom. There are also tests for the other hardware buttons, except for the 4 main buttons on the d-pad (home, back, send, end), which was kind of weird. If you think your power button or vol down button is effed, this tool will confirm/deny it for you.

Right, so the RaphDiag didn't brick your device. It's a bit risky - so I will first resort to less extreme measures - at least I know there is one success story.

I seriously wouldn't worry about it, but you may want to have a card reader available in case you need to remove raphdiag from you sd card to get a flash to work. It's possible that I didn't get the nand format to work properly, but I think I did it right, because the device definitely needed to cold boot. I was just surprised that there was still an OS there.

I'll take your word for it - BUT - in terms of gaining knowledge I am going to try the steps in the posts I found. If the NAND does need a format there is no doubt that I will land up doing it - but I will have first-hand experience.
This really needs a Wiki page once I am done; so I want to squeeze as much info out of the device as I can.
Can anyone else think of any gotcha's before I potentially brick it?

I ran the format a second time. It's really fast; it takes maybe 5 seconds. I haven't figure out how to exit from that part of the diag other than soft resetting, which leads to a cold boot. I'm surprised it's so fast. A hard reset takes about 30 seconds. I guess that it's working properly.

Farmer Ted said:
I ran the format a second time.
Click to expand...
Click to collapse
You are either very brave or very rich . Right, so here is hoping I have to go the final resort route - nothing yet though.

[Q] VEGAn Observations/Questions

Naturally I bought a g Tablet Saturday and Woot has them today for almost $100 less! Oh well. Big big big improvement from my old FlyTouch2 which was a great idea poorly executed.
Immediately flashed VEGAn with supplements etc. All working VERY well but a few questions/observations.
1) If I wanted to hook this up to a USB or Bluetooth modem (well, actually a BlackBerry) it looks like there is no setup for this? Yes, I know if I could find a way to make the BB broadcast WiFi but its corporate so that's a nonstarter.
2) When I hold down the power button, the menu that comes up it clipped off at the bottom. Is that normal?
3) Screen lock on Kindle software is not getting the accelerometer fix somehow. The trick was to put the thing in portrait UPSIDE DOWN and lock the screen. That caused it to lock it 180 degrees off. But then when it is locked you can go back to right side up (to me, right side up is with the buttons to the top). Of course, if you want to lock it another way you have to experiment.
4) Camera Fun shows camera upside down. No big deal -- again accelerometer I think.
5) Sometimes I am sure the machine is asleep and when I turn it on it is booting from the birds screen. Anyone else seeing this?
6) I don't understand the .nomedia thing although I've read a lot about it. I don't seem to get files erased, but nothing shows up in Video. But if I navigate to the folder (on /mnt/sdcard2) and play videos that's fine. Then later the files will show up in video. Whoops spoke to soon. Now they are gone. What's up with that?
7) My old tablet had GPS but without the external antenna it was worthless. But it still managed to find rough location with WiFi somehow. I assume by figuring out the geographic location of the IP. That doesn't seem to work on this machine. Yes Use Wireless networks is checked in Location and security.
8) What's with the little plastic cover? How hard is it to take out? I don't want a little rubber dingle rolling around inside.
8) In System Preferences, About Device | Status consistently crashes.
9) Does the audio jack support a headset or just headphones? Yeah I know -- I could just try it.
If it matters I'm using Launcher Pro.
Still and all the VEGAn ROM is superb. Compared to the FlyTouch this is super fast, the screen is a joy, and the battery life wonderful. And with the woot deal only about $80 more than a FlyTouch2.

Ok I'll answer some of my own questions:
5) I think this is the unresponsive power button problem. If you press and wait it seems ok. If you press, get impatient and press again you might reboot.
9) No, at least not with a Blackberry headset.

Most of these are answered on the forum somewhere, but I'll give it a shot..
wd5gnr said:
Naturally I bought a g Tablet Saturday and Woot has them today for almost $100 less! Oh well. Big big big improvement from my old FlyTouch2 which was a great idea poorly executed.
Immediately flashed VEGAn with supplements etc. All working VERY well but a few questions/observations.
2) When I hold down the power button, the menu that comes up it clipped off at the bottom. Is that normal?
Click to expand...
Click to collapse
I believe this is scrollable, but yes...
wd5gnr said:
5) Sometimes I am sure the machine is asleep and when I turn it on it is booting from the birds screen. Anyone else seeing this?
Click to expand...
Click to collapse
I get this sometimes, too. It is a known issue, and there may be solutions out there... I just deal with it.
wd5gnr said:
8) In System Preferences, About Device | Status consistently crashes.
Click to expand...
Click to collapse
Known issue.

These aren't much help (maybe reassurance?)
1) Pretty sure it's wifi only. Have trawled the internet looking for a usb or bluetooth alternative because wifi hammers the phone battery
2) It happens on mine as well, so it's not just you
5) Same here - I just turn it off when not in use now
7) Only GPS functionality seems to come with the need for an external GPS unit
8) Think this is normal
(Re reading above, it looks like I'm negative re VEGAn - this is not the case. It is way better than what came standard and does everything I need it to do)

Yeah I like it too. Haven't tried the others, but very satisfied with Vegan.

Another observation: Long pressing the Menu button (hardware) brings up the keyboard. However, long pressing the menu button on the status bar does NOT have that behavior.

Clemsyns newest kernel will fix sleep issues. Also has some other great improvements too.
Buttons on status bar do not respond to long presses. Home doesn't bring up its usual long press of recent apps either. Funny, i Never even tried long press on status bar keys before now.
Sent from my Chromatic Magic using XDA Premium App

I have Pershoot's kernel. I'll try changing. I presume I shouldn't need to clear too many things in CWM after flashing a kernel. Maybe the Dalvik cache?

[Q] Touchscreen re-calibration?

Hi all - my TF700 has been solid for about 9 months, but this past weekend the touchscreen started getting wonky and now it will work for 5-10 seconds and then not register any touches, until the power button is toggled to put it to sleep and then wake up and go through the process again. In my research, it appears as if this can be addressed through recalibration of the Touchscreen.
However, I don't even know if that's possible with my current stock/rooted setup. I did try booting into recovery, but I saw the RCK/Android/Wipe Data prompts, and didn't want to go anywhere without knowing what each would do. I'm guessing maybe the Android button, but I'm not sure.
Is there an easier way to recalibrate the touchscreen without doing a factory reset, or going to a new ROM yet?
Thanks!

This may be a hardware problem with the digitizer going bad. I would contact Asus, they probably will recommend a factory reset and you should try that anyway.
But a custom rom will not take care of this problem - at least I do not think this is software related....
Good that you are still under warranty!
FYI:
RCK will boot into the stock recovery which will not do anything unless you have an update file downloaded somewhere on your storage - it'll just show you an Android falling over with it's belly open a ! triangle. Scary if you don't know what it is! LOL
Android will boot you back into your system. This is a so called 'cold boot' and you could try that. I doubt it'll help, but it won't hurt either.
Wipe Data does exactly what it says. You better have everything you care about backed up before you execute that command.
You use the Volume Down button to navigate between the icons and the Volume Up to execute.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Hmmm. after enabling Developer mode (so I could d a Titanium backup), I decided to enable the touch sensing, and what I've found is that it appears as if there is a spot in the northeast quadrant (while holding vertically, with buttons on the right/dock connector on the left) that gets stuck in the 'touched' sense (the little dot sticks, and in the kindle reader, it acts like the text is selected).
Sometimes it gets unstuck when pressing the power button to sleep, and then re-logging in via the lockscreen code I have set. Sometimes it doesn't. I guess I'll contact support and see if I can capture it on video with my phone.

Pyperkub said:
Hmmm. after enabling Developer mode (so I could d a Titanium backup), I decided to enable the touch sensing, and what I've found is that it appears as if there is a spot in the northeast quadrant (while holding vertically, with buttons on the right/dock connector on the left) that gets stuck in the 'touched' sense (the little dot sticks, and in the kindle reader, it acts like the text is selected).
Sometimes it gets unstuck when pressing the power button to sleep, and then re-logging in via the lockscreen code I have set. Sometimes it doesn't. I guess I'll contact support and see if I can capture it on video with my phone.
Click to expand...
Click to collapse
Pyperkup,
Did you ever resolve this issue? I'm experiencing the Very same issue on my TF700T.
Thanks
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

calvinb1 said:
Pyperkup,
Did you ever resolve this issue? I'm experiencing the Very same issue on my TF700T.
Thanks
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Had to send it in on warranty.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

Single phantom touch on digitizer (that doesn't move)

The "show touches" option allowed me to find out why I had some trouble with the digitizer since yesterday. It is not cracked.
There is a single point on the screen showing a touch at all times. If I touch that point, it disappears then comes back 1-2 seconds later.
The digitizer still works as it registers my touches as well, but a lot of apps cannot register more than one touch at a time, so they ignore my touches.
I read somewhere that doing a hard reset (completely wiping everything) would re-initialize the digitizer and make it ignore that stuck point, but I don't want to do that if that's not correct as I'd have to reinstall everything, re-do my settings and still have to figure out how to fix the stuck point.
Or is there an app that can make the tablet ignore that one little touch.

alkizmo said:
edit - I realized that when I wrote "FIXED" in the title, it sounds like I solved my issue. What I mean is that the single phantom touch is not moving, it's in a fixed position (unlike most phantom touch problems seen on other tablets)
The "show touches" option allowed me to find out why I had some trouble with the digitizer since yesterday. It is not cracked.
There is a single point on the screen showing a touch at all times. If I touch that point, it disappears then comes back 1-2 seconds later.
The digitizer still works as it registers my touches as well, but a lot of apps cannot register more than one touch at a time, so they ignore my touches.
I read somewhere that doing a hard reset (completely wiping everything) would re-initialize the digitizer and make it ignore that stuck point, but I don't want to do that if that's not correct as I'd have to reinstall everything, re-do my settings and still have to figure out how to fix the stuck point.
Or is there an app that can make the tablet ignore that one little touch.
Click to expand...
Click to collapse
First I'd edit the post (advanced edit) and removed fixed from the title - you should get more help.
Factory reset - Settings/Backup & reset is where I'd begin. There are no promises that will fix your tablet.
To minimize the grief of a reset use App Backup in the app drawer. Choose Data & App - select all - backup - and copy file to /Removable/MicroSD - OK
Restore with App Backup only works on the same version the tablet was on when the backup was made!
I don't know what the next step would be if your problem is not cleared.

I edited it now. I tried when I first posted, but I didn't remember the advanced edit option for the title
Thanks for the trick on restoring my tablet. I'll try the hard reset.
If that doesn't work. I will be taking apart the tablet and see if I can re-seat the digitizer.
I already replaced it once. This time it isn't cracked, but I know it fell a foot down just before the problem started. It was in it's case, so it was a soft landing on its flat surface. I'm surprised those things are so fragile. Asus should feel bad.

alkizmo said:
I edited it now. I tried when I first posted, but I didn't remember the advanced edit option for the title
Thanks for the trick on restoring my tablet. I'll try the hard reset.
If that doesn't work. I will be taking apart the tablet and see if I can re-seat the digitizer.
I already replaced it once. This time it isn't cracked, but I know it fell a foot down just before the problem started. It was in it's case, so it was a soft landing on its flat surface. I'm surprised those things are so fragile. Asus should feel bad.
Click to expand...
Click to collapse
I think reset is the proper place to begin with the problem you're having.
A couple of things to consider.
Did the spot immediately appear at the time you replaced the digitizer?
Did you take an update that may have caused the spot to appear?
The above are just my thoughts, not actual questions and may not prove helpful.
I have dropped my tablet a couple of times with no noticeable damage.
Good Luck!

tobdaryl said:
I think reset is the proper place to begin with the problem you're having.
A couple of things to consider.
Did the spot immediately appear at the time you replaced the digitizer?
Did you take an update that may have caused the spot to appear?
The above are just my thoughts, not actual questions and may not prove helpful.
I have dropped my tablet a couple of times with no noticeable damage.
Good Luck!
Click to expand...
Click to collapse
The problem only appeared 2 months after I replaced the digitizer.
I didn't update
Anyway, since I already had my tablet setup to flash the touchscreen firmware in order to use a different TS, I simply ran the flashing procedure again. It fixed the problem in seconds
I admit that if my tablet wasn't already setup (unlocked, rooted, superuser access), it would have been faster to reformat (if that would have fixed the problem).
TL;DR - Problem solved, I flashed the touchscreen firmware to force it to reset instead of formatting my tablet back to factory settings.

alkizmo said:
The problem only appeared 2 months after I replaced the digitizer.
I didn't update
Anyway, since I already had my tablet setup to flash the touchscreen firmware in order to use a different TS, I simply ran the flashing procedure again. It fixed the problem in seconds
I admit that if my tablet wasn't already setup (unlocked, rooted, superuser access), it would have been faster to reformat (if that would have fixed the problem).
TL;DR - Problem solved, I flashed the touchscreen firmware to force it to reset instead of formatting my tablet back to factory settings.
Click to expand...
Click to collapse
I'm glad you managed to clear your issue. I'll try to remember your fix for the future.
Thanks for the info.