Database Users

[Q] Duth(netherlands) G1 Cant Root

T-mobile G1
Firmware version 1.6
Baseband Version 62.50S.20.17U_2.22.19.26I
Kernel Version 2.6.29-00479-g3c7df37
[email protected] #19
Build Number DRC92
Hi guys ,new in here.
I have a T-mobile G1 that i Bought From Netherlands . I wanted to root and upgrade it into cyanogen but i had to downgrade it first into 1.5 or 1.0 . i tried many links and guides but i always get the 00028002 error and then the rainbow screen with the Serial0 error. many had the same problem but no clue ... Any Ideas??? i am 100% sure that the format of my SD is FAT32 but not sure about the file i download. i tried many.I cant even install the original SPL.
Thanks in advance!
on the Rainbow screen it shows these for me :
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.2

i have same problem

Can somebody pleas help us? of is a way or not , because is stressfull to waith for a message

What is easier than trying to downgrad is useing exploid exploit
Here is a draft of the steps:
http://forum.xda-developers.com/wiki/index.php?title=User:Ezterry/G1_1.6_To_Custom_Firmware
I made it in a rush so clean if need be.. but don't completely re-write if you want to do that post elsewhere.
As for the problem with downgrading is the files are only intended for US/UK dreams and you don't have one of those..
however my steps above are probably also safer for those with said dreams.. since it tries to avoid the brick potential with dangerSPL

Now i have been trying that link, but i cant go forward from step 3
run the following adb commands:
* adb push exploid /sqlite_stmt_journals/exploid
* adb push flash_image /sqlite_stmt_journals/flash_image
* adb push recovery-RA-dream-v1.7.0-cyan.img /data/local/recovery-RA-dream-v1.7.0-cyan.img
* adb push spl_1_33_2003.zip /sdcard/spl_1_33_2003.zip
* adb shell chmod 755 /sqlite_stmt_journals/exploid /sqlite_stmt_journals/flash_image
* adb shell /sqlite_stmt_journals/exploid

red_net0 said:
Now i have been trying that link, but i cant go forward from step 3
Click to expand...
Click to collapse
You run them from your computers command line..
Is there an error?

IT dosnt work and yes i have that line from cmd on my computer

red_net0 said:
IT dosnt work and yes i have that line from cmd on my computer
Click to expand...
Click to collapse
Unless you give details I'm not sure how you expect anyone to help
"It doesn't work" could mean:
1) adb/fastboot isn't properly installed on your computer
2) you are not running adb from the directory with the files
3) you are making a typo in the command line (or I made a typo in the commands in that document.. unlikely but not impossible)
4) phone doesn't have USB debugging enabled or is not plugged into the computer
5) Your USB port on the phone is fired.

Ok i think the first adb running and the 2cond I think? How can i running that adb ?

red_net0 said:
Ok i think the first adb running and the 2cond I think? How can i running that adb ?
Click to expand...
Click to collapse
Try either the xda thread for adb/fastboot/sdk or the adp1 developer site
wiki page said:
[size=+2]Install ADB/Fastboot[/size]
For this to work I expect that you have adb/fastboot installed on your computer and understand that adb/fastboot commands are entered into your computer; not the phone
The XDA thread on setting this up is: http://forum.xda-developers.com/showthread.php?t=532719 Otherwise additional information is on the htc adp site: http://developer.htc.com/adp.html#s2
Click to expand...
Click to collapse
Many windows users find it easiest to put the files in the tools directory with adb. That said I'm primarily OSX and set up the path to allow me to access the commands anywhere.

I have been trying to install adb but i dont have the SDK Setup.exe file!

2cond thing that i see is
that
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
I dont have a rooted HTC Dream

That line lies; adb is used by developers on non rooted devices all the time..
the setup is the windows drivers..
Questions about adb *if* posted in the adb thread will be read by many more windows users that may be able to help.
You don't need to pm if you are asking the question in this thread.

I thing
I have the problem that i cant downgrade i have been 1 month trying to downgrade my g1 no lukky!:S

Try downgrading to RC7.....instead of RC29.
I had DRC93 (Dutch G1) and I followed the follwing link step by step
http://forum.xda-developers.com/showthread.php?t=727688
remember to use RC7
.....mine is working perfectly

[Q] rooting problem: "device not found"

Hi: I'm a long time lurker here on xda-dev, but I'm a first time rooter and this is my first time posting here.
I appreciate any help that I can get, and I will try to be as descriptive as possible so that I don't waste anyone's time. You should know that I am running OS X 10.6.7 (which is 64 bit if that makes a difference). I know that it's possible to root from OS X because I've been in contact with a fellow xda'er about his success with it and my subsequent problems. You will notice from the screenshots that I have a bootcamp partition because I plan on installing Windows 7 at some later time. I think that this may be a driver issue, but really dunno why I would have this driver problem if the person who I know has had success with OS X 10.6.7 didn't have any problems. Not sure if this matters, but I am using this sdcard: http://amzn.com/B003WGJYCY
Things that I've done that you might ask me if I've done:
-Debugging is on (I've toggled it a few times too)
-temprooted with Visionary
-Extracted the Shift file to the root of my sd card
-Checked the md5 of the file in Shift using Terminal emulator (it matches what the guide says it should be)
-Reinstalled the SDK
-Reinstalled Visionary
-Re-Extracted the 'Shift' file to my sdcard.
I am trying to root my shift following this guide : http://forum.xda-developers.com/showthread.php?t=932153
I have installed Android SDK and for have installed the packages that you can see in this screen shot: http://oi55.tinypic.com/2dvimb6.jpg
I then temprooted using Visionary: After a few failed temproots, I did get a successful temproot, which I am verified by gaining SU with the app Terminal Emulator.
I open up command prompt and do the commands that you can see in this screenshot and as you can see after ./adb shell I get "error: device not found" : http://oi51.tinypic.com/2ztcymt.jpg
As you can see, I can open adb, but the adb shell command returns an error that no device is found. I've also done this: http://oi51.tinypic.com/264t6o5.jpg
So, what do you think?

i forgot to mention that my phone is in charge only mode when I execute ./adb shell

is it connected to a 2.0 USB port?
Also have you tried restarting your phone and mac?
I also saw on another forum that Superuser had to be uninstalled then try temp rooting again.
Also are you keeping an eye on your phone while trying to gain su access? You have to click yes when it asks if you wanna give permission.

You could always try rooting via terminal on the phone. That's what I did, no PC involved.
^ Shift Faced

Thanks for your responses.
I assume these are USB 2.0 ports on my 2010 MacBook Pro. I've uninstalled superuser a couple of times, but when I use terminal emulator to check if I'm temprooted, it shows back up in my apps list.
I have never had the option of giving adb superuser permissions, but yes I have kept my eye on the phone to make sure that the phone wasn't requesting this.
@jesusice -- even though I did the md5 check on the phone, I never thought of rooting the phone through terminal emulator. Would I just follow the directions from the guide, and just input all of the commands into terminal emulator? Anything else I should know about if I try this?

dubs.law said:
@jesusice -- even though I did the md5 check on the phone, I never thought of rooting the phone through terminal emulator. Would I just follow the directions from the guide, and just input all of the commands into terminal emulator? Anything else I should know about if I try this?
Click to expand...
Click to collapse
That's what I did. Had been waiting for perm root so long and was so excited I couldn't stand to wait until I got home and just put the commands into terminal on the phone. Just make sure that you input all commands EXACTLY. It was recommended by others to do it from desktop so you can be sure and copy and paste the commands so as to cutdown on errors but I'm not sure why... I can copy and paste from the phone It's just kinda a pita.
^ Shift Faced

Does the phone have to be plugged in the wall or into the computer at all to do this without a computer?

dubs.law said:
Does the phone have to be plugged in the wall or into the computer at all to do this without a computer?
Click to expand...
Click to collapse
Nope.
^ Shift Faced

So, there is no adb commands, you just flash the "eng spl" , correct?

I rooted without a computer. Thanks!

dubs.law said:
I rooted without a computer. Thanks!
Click to expand...
Click to collapse
Awesome! I was coming on to tell you I don't really remember all the details as it was a long time ago and that I couldn't help any
Exciting doing it from the phone, right? The fear of bricking is fun
^ Shift Faced

[Q] Problem Rooting Kindle Fire

I received a Kindle Fire as a birthday gift yesterday, and have went step by step through a number of guides to try and root the device to no avail. I'm thinking the problem involves the steps where you do adb kill-server, then adb devices. When I type in adb devices into command prompt It will say something to the effect of 501A005220001 and then beside it, it will say offline. I know I have the correct USB drivers and have edited all the files properly, but no matter what I do it always says it's offline, so when I get to the point where you use SuperOneClick, it will kill the adb server, restart it, then freeze.
Has anyone else had this problem or know how to fix this so I can root my device? I would greatly appreciate whatever help I can get!

I found by simply changing which USB port I was plugged into fixed the problem.

[Q] ADB - Device Not Found (v6.2.1)

Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.

CrimsonSentinel13 said:
Before the 6.2.1 update, I was able to connect to the Fire just fine. There was the occasional issue with it killing the USB port on my PC & then I would have to reboot it in order for ADB to see the Fire again. Now I can't get ADB to talk to the Fire at all, even though it shows up in the Device Manager & I'm able to connect the storage up to Windows 7 just fine. As a frame of reference, I'm able to get my Sony Ericsson Xperia PLAY to be seen by ADB.
Does anyone know how to get ADB fixed on my Fire & is there a way to push an insecure build of ADB to it? Thanks.
Click to expand...
Click to collapse
BurritoRoot causes the normal adbD to behave as an unsecure one, but if your not seeing the kindle under adb devices then you have PC side problems likely.

I figured it might be PC side. I've tried everything I could after updating the Android SDK. Updating everything with what's needed for the Fire to be seen hasn't worked. I'm a bit at a dead end for ideas... I tried even using the USB3 controller on my mobo but no luck either.
Edit: Fixed!
I uninstalled the Kindle Fire from the Device Manager & got it reinstalled. It now works perfectly with ADB. I'm in the process of rooting it as I type this.

I have the same problem.
However, I have 2 fires, one running CM7 and the other 6.2.1.
The PC recognizes the one running CM7 but not 6.2.1.
So, I don't think it is the PC.
No matter what I do, adb and fastboot, device not found.
Can not access the one with 6.2.1.
Does not show up in device manager.
I have read and try various things from xda, Rootzwili and Liliputing.
​

follow this video thats wht helped me get past that part ur on
http://www.youtube.com/watch?v=KapnjR89ICA&feature=player_embedded
u have to make sure u update the drive for ur kindle with the driver from sdk
this is also helpful tooo
http://forum.xda-developers.com/showthread.php?t=1409120

What worked for me was following this guide up to step 3. Then, with the device manager it launches, i deleted ALL my adb/android devices and then I let windows re-install the driver when I plugged the kindle (you may need to choose the driver manually), then I could finally access fastboot/adb via cmd..

Solved problem, Thank You.
I have many drivers on my PC, Motorola, Samsung, HTC and Android.
I noticed on one boot the Kindle was listed as Samsung Android Phone.
I uninstalled the Samsung drivers.
Connected the Kindle. All is fine.
Connected my Samsung SGS II, it found the drivers.​

Crimson, thanks for sharing your fix of uninstalling then reinstalling. Worked for me.

hi, i would like to apologize in advance, i am new to adb so i'm not sure if i'm even doing it right, but i have successfully rooted and installed cm7, after much googling. i did it a while ago and used the clockwork mod method. i would like to replace it with twrp but the only way i have found to do it is by using adb or the kindle fire utility, which if i understand correctly uses adb. the only problem with that is that i can't get adb to recognize it. i'm assuming it's because i don't have the proper drivers for the "cm7 kindle" because i install them for the stock kindle. please help me. i have no idea how to fix this. thanks
edit: ok guys i'm really sorry, i'm an idiot, i forgot that i had turned off usb debugging. turned it back on, worked perfectly. again sorry.

Fire HDX 7 password bypass

My daughter dropped her HDX 7 and the screen shattered. I was able to secure a new one for her but she had some serious sweat equity into a few games she was playing on the old one. I am trying to get the game files of the old one to move to the new one but the touch screen won't work and as such, will not take her password. (due to the drop).
Is there an easy way to bypass this? I am trying to access the kindle drive from my PC for purposes of copying the files (done a million times) but with the device technically locked, the device does not show in file explorer.
Any suggestions welcome.
Thank You!
Chris

Do you have Safestrap installed?

EncryptedCurse said:
Do you have Safestrap installed?
Click to expand...
Click to collapse
No I don't. The device is purely vanilla right as it came from the factory.

Chriss9, you should try to get adb working. That should allow you to pull data.

lekofraggle said:
Chriss9, you should try to get adb working. That should allow you to pull data.
Click to expand...
Click to collapse
Can you tell me where to get it and maybe some instructions? Thanks so much!!
Chris

Look into the rootkit in the dev section. That should install the drivers for you. Then, search for how to use adb. You may need to download the developer kit from Google as the toolkit is a little limited.
You need to pull the data to your computer then push it to the new Kindle.

ADB pull on locked phone? // Simulate input
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk

Grtschnk said:
It may be that ADB pull won't work with a locked (stock) device... But of course you could still give it a try.
Here is a smaller download of the ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
However another possible way to use the ADB for your purpose would be:
Code:
adb shell
input tap x y
Where you would use the input tap x y to simulate a screen tap. Tapping the screen "virtually" since it's broken. This way you could unlock it (and then use the pull command). For x y and you have to insert the correct screen position of the keys on the keyboard. I haven't tested it, but we could give it a try. Just tell us if you have any luck connecting through ADB!
regards Grtschnk
Click to expand...
Click to collapse
Thanks for the suggestion. I installed ADB on my PC and when I use "ADB DEVICES" my device does not show on the list though it does show in Windows explorer. Am I out of luck here?
Thank you again for your kind support.
Chris

Assuming you have the latest Fire OS 4.5.1 : (If you have the older version installed there may still be a glimpse of hope (see long answer))
Short answer: Sorry, looks grim.
Your ADB is switched off and there is no way I know of to switch it on.
I wanted to make sure it wasn't just a driver issue with your computer so I checked with my Kindle:
ADB set off: Kindle in Windows, but not detected by ADB-program
ADB set on: Kindle in Windows and detected by ADB-program
Long answer (may be frustrating to read because it states all the possibilities the Kindle lacks): On a nonlocked (in terms of bootloader, not screenlock) device there would have been some possibilities. Install a custom recovery that has ADB built in and pull the files or try to enable ADB from within recovery inside the ROM. If the device could act as a USB host a mouse or keyboard could have been hooked up. The Kindle supports Bluetooth input devices but they have to be set up first (from within the device, not possible without touch). If your device has older Fire OS you could try the mentioned steps, however that's beyond my expertise. So I don't know if it is possible/will work. You'd have to check other threads about flashing the device or hope that someone else posts advice in this thread.
I became a Kindle owner quite recently, so I can't guarantee everything I wrote is correct, but I believe as long as noone magically finds a way to unlock the bootloader the more experienced users will agree to my post.

Did you install the driver as well? I recommended the toolkit because comes with the driver and if you are not used to installing adb drivers on Windows, it can be a bear. But, Grtschnk may be right. I always enable it n all my devices. It is the first thing I do.

Just to be really sure about possible driver issue: You (chris) could try to connect an Android phone via ADB (I'm assuming you have one). Enable ADB on it and see if connects. Unfortunately this will only prove more that your Kindle turned into a piece of plastic :/

Grtschnk, unfortunately, that won't prove anything. ADB requires separate drivers for each device. Again, that is why I recommended the rootkit. It sets it up for you and can even test it.

That's why I compared with my Kindle, computer and S2 (CM11). Newly set up computer, no SDK, just Minimal ADB. Never installed special drivers for Kindle or S2. Newest Visual Studio (2013) runs on the machine, but without additional packages there is no Android support.
However if I was in the situation myself I would have also tried the full SDK.