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

[UPDATED][Video] How To Root Transformer & Downgrade Honeycomb 3.1

WE ARE NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE! FOLLOW THE INSTRUCTIONS AND YOU SHOULD BE FINE!
IF YOU HAVE HONEYCOMB 3.1 OR SOME OTHER FIRMWARE OTHER THAN 8.2.3.9 THEN YOU CAN DOWNGRADE VERY EASILY
[HERE IS HOW TO DOWNGRADE]
Some prerequisites to the rooting process:
1) You must have a Windows 7 or XP for this tutorial.
2) You must have a micro SD card in your tablet throughout the procedure. It is safe to remove it AFTER you finish the ALL steps. There's no minimum size requirement but 2gb should be fine.
3) The files needed to root your device from here:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
4) An Asus Transformer (16 or 32gb) running Honeycomb 3.0.1...SEE DOWNGRADE INSTRUCTIONS IF YOU ARE ON HONEYCOMB 3.1
5) Data cable
6) Me guiding you
Alright now that you have everything set, lets begin the rooting process!
1) You need to make sure your device has USB Debugging activated. To do this go to Setting>Applications>Development and make sure there is a check box next to USB Debugging. Leave the other two options unchecked.
2) Check what your Build Number is. Go to Settings>About Tablet>Build Number. Make a note. If it it says 0423 at the end (or anything after) then you use V5. If its anything below (ex. 0421) then you use V4. Got it?
3) Hook up your Transformer to your computer via the USB Cable. Avoid USB hubs if possible.
4) If you are using Windows 7 then the drivers will install automatically. I have provided you with the link to the drivers here:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
4) Download & Install the Asus Sync software. I know its annoying to have to install bloatware that you will probably never use but in this case, your Windows machine will not detect your device without it.
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
5) Insert the MicroSD card into your Transformer and make sure that the tablet recognizes it. I have had issues with some cards not being detected.
6) Now we need to download the Android SDK. You can download it here.
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
7) Install the Java Developer Kit if you dont have it already. You can find it here:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/
*Edit*
Even after you install the JDK the SDK installer might say that its not installed. Just click back then next again (or restart the installer again) and it should work-Thanks Codiox
8) Install the SDK to the root of your hard drive and put it in a folder called Android. This means when you click the local disk C: drive the first folder you should see is the Android folder. This will make using the command prompt simple.
9) Go to Start>All Programs>Android SDK and click in the SDK Manager. When you're presented with the option to install all updates (and you have time to do so) let it all install. All you really need though is the Android SDK Provision tools update. You can hit cancel once that is installed successfully.
10) Open up the command prompt
11) Lets being with the terminal commands. Make sure you press the ENTER button after every command line. You can copy and paste the commands if you want; if you do so, you dont need to press enter to go to the next line.
12.
Code:
adb devices
make sure your device is detected
13.
Code:
adb push gingerbreakBB /data/local/
14.
Code:
adb shell chmod 777 /data/local/gingerbreakBB
15.
Code:
adb shell
you will get a $ sign.
16.
Code:
./data/local/gingerbreakBB
nothing will happen at first, but after about 5 minutes, you will see a long list of "vold" commands....let this run its course...go grab a sandwich or something.
If for some reason it says permission denied, try running these commands immediately after running the
Code:
./data/local/gingerbreakBB
command. DO THIS ONLY IF YOU GET PERMISSION DENIED LIKE IN MY VIDEO! If you didnt get the permission denied error, continue to step 20.
17.
Code:
rm /data/local/tmp/boomsh
then type.
18.
Code:
rm /data/local/tmp/sh
then redo step 16 again which is
19.
Code:
./data/local/gingerbreakBB
20. After about 7-10 minutes you will be presented with a # sign. THIS IS GOOD!
21. Open ANOTHER command prompt window; the same way you opened the first one. DO NOT FOR ANY REASON CLOSE THE FIRST COMMAND PROMPT. LEAVE IT OPEN IN THE BACKGROUND!
22. type
Code:
adb devices
23. PAY ATTENTION HERE! Remember when I told you to look at your build number? We need that information now. If your tablet has a build number ON OR AFTER 0423 then use this command
Code:
adb push CWM_BLOB_V5 /data/local
If it has a build number BEFORE 0423 (ie. 0422) then use this command
Code:
adb push CWM_BLOB_V4 /data/local
24. Whatever number you used above, you will continue to use it throughout the installation! REPLACE THE # SIGN WITH WHATEVER YOUR NUMBER ABOVE WAS; EITHER 4 OR 5.
Type
Code:
adb pull /data/local/CWM_BLOB_V# cwmblob_retransfer
then
25. Return BACK to the PREVIOUS command prompt that had the # sign just sitting there.
26. Type
Code:
dd if=/data/local/CWM_BLOB_V# of=/dev/block/mmcblk0p4
Replace # with your number (4 or 5)
27.
Code:
adb shell
28.
Code:
reboot
29. Your device will reboot now. This will take a bit longer than a normal reboot so be patient.
30.
Code:
adb remount
31.
Code:
adb push su /system/xbin
32.
Code:
adb push Superuser.apk /system/app/
33.
Code:
adb shell
34.
Code:
reboot
THAT'S IT! Congratulations! You have successfully rooted your Asus Transformer. I hope this tutorial made it simple for you. Let us know if you have any questions!
Credit Goes To Androidroot.mobi devs for the original rooting process.
Original Thread:
http://asustransform.com/forum/index.php?/topic/19-how-to-root-your-asus-transformer/

+1 Thanks!

So its a no go on vista 64 bit
LEEDROID GB3.0.1DESIRE HD using XDA PREMIUM

combat goofwing said:
So its a no go on vista 64 bit
LEEDROID GB3.0.1DESIRE HD using XDA PREMIUM
Click to expand...
Click to collapse
sorry i keep forget that Vista existed at one point ...yes it should work fine on vista

Does anyone know when it will get 3.1 support?

PatrikSelin said:
Does anyone know when it will get 3.1 support?
Click to expand...
Click to collapse
Not until someone updates the modifies blob files for 3.1. However you can use this how-to to root the 3.0.1 build then flash a 3.1 ROM. Unless you're on 3.1 now with no root...then ur SOL for just a but longer
Sent from my ThunderBolt using Tapatalk

damn,!!!!! awsome post should be sticky, thank u for your support and work

Added to ultimate thread. Nice job.

Should be in the dev section as a sticky.

Trouble installing development kit
I installed the Java SE Development Kit 6 Update 25 (64-bit) but when I try to run the SDK tools setup it says the JDK is not found. The Development Kit shows up in my programs and I've installed it and reinstalled it about 3 times now, including downloading a fresh file and rebooting my computer. Is that the wrong file? I'm running Windows7 on a 64-bit computer. TIA - sheureka

PatrikSelin said:
Does anyone know when it will get 3.1 support?
Click to expand...
Click to collapse
If you have root already you can update to 3.1 using the modified update that is floating around here. Sorry I don't have a link.

sheureka said:
I installed the Java SE Development Kit 6 Update 25 (64-bit) but when I try to run the SDK tools setup it says the JDK is not found. The Development Kit shows up in my programs and I've installed it and reinstalled it about 3 times now, including downloading a fresh file and rebooting my computer. Is that the wrong file? I'm running Windows7 on a 64-bit computer. TIA - sheureka
Click to expand...
Click to collapse
just click on the "back" button, then the "next" button and you'll be fine. its a known bug.

Good write up. There are two problems. You do not give credit to the source of the root method (apache/bumblebee and rayman) and they specifically asked that their method not be reposted, only linked.

If you watched the video you would know that I took a minute to thank the developers of over at androidroot.mobi (which include all the people you just mentioned). As for their files, I respected their wishes... again I specifically said this in the video that I will honor their wishes. The link on my site takes them directly to their site. I do not host any of their files. As for the write up itself, this is my variation of their work. I wrote everything you see in my own words so newbies will understand it without confusion. Their procedure didn't work for me so I just tweaked it to make it work for me and decided to share. I'm not trying to steal their work, I think people here know my true intentions. I just wanted to help and promote my site a little. I hope that clears up everything. I will add additional credit on the main page so there's no confusion.
Sent from my Transformer TF101 using Tapatalk

Well, I got to [*] vold: 0085 GOT start: 0x00017368 GOT end:0x000175e8 (right after the donate and thanks stuff and nothing ran. I went ahead to went to the other command screen and did that stuff, hoping something would shake lose. Exploit did not take a while. In fact nothing happened at all. I'm not sure what to do - should I reboot the tablet to see what happens or just unplug and start all over. Any ideas?
I just saw that someone over on AsusTransform site has exactly the same problem. I did unplug and everything seems to be running fine (though it's obviously not rooted) but it's a little scary.

sheureka said:
Well, I got to [*] vold: 0085 GOT start: 0x00017368 GOT end:0x000175e8 (right after the donate and thanks stuff and nothing ran. I went ahead to went to the other command screen and did that stuff, hoping something would shake lose. Exploit did not take a while. In fact nothing happened at all. I'm not sure what to do - should I reboot the tablet to see what happens or just unplug and start all over. Any ideas?
Click to expand...
Click to collapse
I have another person on my forum with the same issue. What was your battery life when you attempted this? His was below 20%. Are u using a USB hub? My recommendations are to reboot, try a different usb port, charge the tab above 50% if its low and try again. You most likely need to do steps 17-19 since you pushed the gingerbreak file already. Let me kknow iif that works.

ayman07 said:
If you watched the video you would know that I took a minute to thank the developers of over at androidroot.mobi (which include all the people you just mentioned). As for their files, I respected their wishes... again I specifically said this in the video that I will honor their wishes. The link on my site takes them directly to their site. I do not host any of their files. As for the write up itself, this is my variation of their work. I wrote everything you see in my own words so newbies will understand it without confusion. Their procedure didn't work for me so I just tweaked it to make it work for me and decided to share. I'm not trying to steal their work, I think people here know my true intentions. I just wanted to help and promote my site a little. I hope that clears up everything. I will add additional credit on the main page so there's no confusion.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Video and writeup are 2 different things. Thanks for adding the credit.
Sent from my Transformer TF101 using XDA Premium App

My battery was about 80% and I'm directly plugged into my desktop. - sheureka

sheureka said:
My battery was about 80% and I'm directly plugged into my desktop. - sheureka
Click to expand...
Click to collapse
I apologize, I was mistaken. This will not work on the following firmware
8.2.3.13
There is currently no way to root this and I dont think theres a way to downgrade either. I will adjust my post. Sorry about that :-( your tab is fine though. No harm done.
Sent from my Transformer TF101 using Tapatalk

Never mind.

[GUIDE] Workaround for attaining S-OFF (for Windows 8.1. users)

For those on Windows 8.1 who have just about given up trying to get S-OFF...
For reference I have an ATT HTC One, but showing in bootloader as m7ul (didn't seem to make a difference to any downloads/steps anyway so meh)....
hboot = 1.44
S-ON (hence the inability to install the new GPE 4.4 ROMs)...
So I have tried every single fix imaginable on these forums and the Internet in general... absolutely nothing has worked... trust me....
I then seen a comment from someone mentioning using Ubuntu to do it... I thought... no way, I'm not bothering, all that effort, and it'll still fail... well tell you what, via various forums, sites, fixes etc (lol) I got there in the end.
Prerequisites:
Rooted
hboot 1.44 (I haven't tested newer versions... assume you're looking here really because you had the same problems as me - test with other hboot versions at your own risk I guess)
Not sure if the version of Rom you are currently on matters, I was on 4.3 Google edition (Eragon V14), so don't ask me which to be on
Let's do the following:
1) Download Windows Ubuntu from here:
http://www.ubuntu.com/download/desktop/windows-installer
Click "Get the Installer"
Download and save the .exe to wherever you want
2) Right click the .exe and create shortcut
3) Change the target of the shortcut (right click --> Properties) to end with the following: \wubi.exe --32bit
4) Run the installer, and just go with any defaults
5) Once rebooted in to Ubuntu we are going to download and install fastboot and adb
6) Click the Windows key, type "Terminal" and hit RETURN
7) type the following at the "command" prompt: (do not type [RETURN] <-- lol)
sudo add-apt-repository ppa:nilarimogard/webupd8 [RETURN]
sudo apt-get update [RETURN]
sudo apt-get install android-tools-adb android-tools-fastboot [RETURN]
When prompted, enter the password you set up when you installed Ubuntu in the first place.
8) To confirm Fastboot now works (yes... it was that easy)
Boot your phone in to Fastboot (hold VOL DWN + Power --> Fastboot)
Connect up the phone to USB
In the terminal, type the following then press RETURN
sudo fastboot devices
You should see your device serial, confirming it is recognised by Fastboot ----
9) Now to download Rumrunner -- get the archive from the following location:
http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.tgz
Open the download (rather than save), and extract all files to the Home/Download folder (you can just click and drag them over)
10) Now, we need to allow the "soju" file to be executed
Right click the extracted file "soju" --> go to Properties --> Permissions tab --> Tick "allow executing file as program"
Almost there.....
11) Boot the phone back up and enable USB Debugging via Developer Options
Also change display timeout to 10mins, and set screen security to None
12) Disable Fastboot where applicable (Settings --> Power --> Fast boot)
13) Now to run the Rumrunner application....
Again, within the terminal, type the following:
cd Downloads [RETURN]
(if this doesn't work, you need to navigate to the folder you extracted the "soju" file to, so the cd (change directory) DOS command works fine here)
Now type the following (once you are in the same location as "soju")
sudo ./soju
If you are ready (definitely) to start the process, now press RETURN.
14) You will be asked twice to type "Yes" exactly as displayed followed by RETURN to confirm, please do not type Yes to the warnings that will come up periodically after the script starts (if you give them a moment, you will see them continue without any input from yourself)
15) Sit back... and wait for it to complete. The process took about 20mins in total to complete on my phone... and I've now got S-OFF. If you keep getting prompted for what to do with your phone being plugged in - just press cancel to the prompts.
p.s. if this worked - please press THANKS :good:
If anyone needs any clarification, let me know, I will try and respond as soon as possible (if others could help - that would be appreciated too)

Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!

EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
whats yer firmware fella?

painnpleasure said:
whats yer firmware fella?
Click to expand...
Click to collapse
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.

EM101 said:
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.
Click to expand...
Click to collapse
Ok thnx fella.im on 3.63.111.3 and having difficulties running rumrunners.ill give it another go then. I want to get to go Google edition aswel.

sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:

skythunder83 said:
sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:
Click to expand...
Click to collapse
Use the ls command to see what is in the directory you are in. Use the cd command to change directories. Keep searching til you find the directory where you put the soju file. Good luck.

Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.

EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
Glad to hear buddy. I also spent a considerable amount of time trying to find a solution to this and had just about given up.
Thanks for providing some additional notes on your steps too, might help someone else get theirs working too.
Sent from my One using XDA Premium 4 mobile app

alessiomoro1994 said:
Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.
Click to expand...
Click to collapse
By whatever means, you will need to initially be rooted. Unlocking via HTC Dev was how I got root.
Ironically this also (at the time, not sure if it's changed) doesn't work in Windows 8.1 lol and I had to root my phone using my parents laptop with Windows 7 installed.
They then upgraded to 8,1 so I couldn't use it to get S-OFF later on.
Sent from my One using XDA Premium 4 mobile app

I finally got s-off on my att htc one. Was pretty much trying the same thing as OP stated here, but had some difficulties with other things.
1. OP's instructions didn't work for latest ubuntu (13.10)
2. Had linux mint installed on my pc, but it was 64bit.. tried quite a bit to get it working there (adb and fastboot work), but rumrunner was not happy with 64bit
3. Finally tried it on Ubuntu 12.04.3 LTS 32 bit and everything was smooth with it
One other thing to note.. I used live USB instead of installing ubuntu on my pc. had no issues, but had to use a bit older version of ubuntu and 32 bit (even tho my pc has 16Gigs of memory)

Don't know what's different, but Rumrunner worked for me - hboot 1.56, ARHD 41.0 and Windows 8.1

I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app

roose21 said:
I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like the location of those packages has changed? Unless the reason it isn't working is because of the version of Ubuntu you're on. Hmm.
Sent from my One using XDA Premium 4 mobile app

Try this:
http://vondroid.com/threads/how-to-...on-ubuntu-and-other-linux-based-systems.9793/
Sent from my One using XDA Premium 4 mobile app

My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk

punisher195 said:
My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Use the "thanks" button and rate the thread then
Sent from my One using XDA Premium 4 mobile app

[how to] lock/unlock your bootloader without htcdev(s-off required)

READ THIIS!
*this thread is for m8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-kdj67f for fearlessly testing on vzw m7_wlv and putting up some screenshots in post 2. thanks!
-matthew0776 for fearlessly testing for sprint m7_wls
*i dont have m8. let me know if it works and ill add you to the credits.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
*i have tested this on my gsm htc one. if someone wants to test on vzw,ill add you to the credits
(yes this is m7. i dont have an m8 yet)
other useful threads:
remove tampered banner: http://forum.xda-developers.com/showthread.php?t=2708565
change mid without an eng bootloader: http://forum.xda-developers.com/showthread.php?t=2708581

mine!

@scotty1223 will this royally mess anything up if I try this on my Sprint M8?

BD619 said:
@scotty1223 will this royally mess anything up if I try this on my Sprint M8?
Click to expand...
Click to collapse
Possibly. If the flag is in a different spot,and you overwrite something important. You can dump p2 and p6 and I can take a look,if you'd like.
Sent from my HTC PG09410 using Tapatalk 2

scotty1223 said:
Possibly. If the flag is in a different spot,and you overwrite something important. You can dump p2 and p6 and I can take a look,if you'd like.
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
Hopefully this will give you the answer?
http://forum.xda-developers.com/showthread.php?t=2699165
or
http://forum.xda-developers.com/showthread.php?t=2696652

Thanks for working on this Scotty!
Also, thanks for getting the Sprint info to Scotty BD.
Both of yinz, thanks and thanked.
Sent from my EVO using Tapatalk

BD619 said:
Hopefully this will give you the answer?
http://forum.xda-developers.com/showthread.php?t=2699165
or
http://forum.xda-developers.com/showthread.php?t=2696652
Click to expand...
Click to collapse
unfortunately,no. it does show that the partition the flag is located in is in the same spot(pg1fs is p2) but i need to see that partition if you want me to verify the flag is in the same spot(it prolly is,but is not always across variants)
in a root shell(# prompt):
dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2
then upload the image and pm me a link.

scotty1223 said:
unfortunately,no. it does show that the partition the flag is located in is in the same spot(pg1fs is p2) but i need to see that partition if you want me to verify the flag is in the same spot(it prolly is,but is not always across variants)
in a root shell(# prompt):
dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2
then upload the image and pm me a link.
Click to expand...
Click to collapse
Check PM

BD619 said:
Check PM
Click to expand...
Click to collapse
Cool thanks. Will take a look when I get home this evening
Sent from my HTC6435LVW using Tapatalk

BD619 said:
@scotty1223 will this royally mess anything up if I try this on my Sprint M8?
Click to expand...
Click to collapse
scotty1223 said:
Possibly. If the flag is in a different spot,and you overwrite something important. You can dump p2 and p6 and I can take a look,if you'd like.
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
i can confirm that this unlock method works on the sprint variant

ak074 said:
i can confirm that this unlock method works on the sprint variant
Click to expand...
Click to collapse
Awesome, thanks
Sent from my HTC6435LVW using Tapatalk

Can anyone confirm on ATT M8 converted to GPE?
Sent from my HTC One_M8 using Tapatalk

How the hell do you get into the bootloader ...just received my m8 today on crappy voda ....not spending money on phones anymore I must of spent at least 3grand over the years, anyway ....I press down vol and power but doesn't do anything ....it will reboot with up vol and power ..that's all I can do. Do I need to turn of quickboot and enable debugging before I can load the bootloader ?....oh yes ...do we have s-off for international model ? ...because its staying in the box if I cant s-off and get supercid.

boe323 said:
How the hell do you get into the bootloader ...just received my m8 today on crappy voda ....not spending money on phones anymore I must of spent at least 3grand over the years, anyway ....I press down vol and power but doesn't do anything ....it will reboot with up vol and power ..that's all I can do. Do I need to turn of quickboot and enable debugging before I can load the bootloader ?....oh yes ...do we have s-off for international model ? ...because its staying in the box if I cant s-off and get supercid.
Click to expand...
Click to collapse
Try without quick boot,because as long as that is turned on the phone dosent really turn off but goes into some cind of standby mode like windows OS .
Sent from my HTC One X using XDA Premium 4 mobile app

Power and vol up till rhe phone turns off to reboot. When the screen turns off,move from vol up to vol down.
Or turn off fastboot and power off for a few seconds. Then power vol down
Sent from my HTC PG09410 using Tapatalk 2

A couple questions:
1). Does this actually change you back to locked the way <fastboot oem lock> would? or is it just changing the header text?
2). I see references to the Sprint M8 and this is in the M8 forum, but would if foul anyting up to try it on a Verizon M8 with the 3.16 HBoot?
Thanks for the clarification.

Please excuse the ignorance. How can you get s-off without rooting first?

anit77 said:
Please excuse the ignorance. How can you get s-off without rooting first?
Click to expand...
Click to collapse
You can't. Where does it say you can?

anit77 said:
Please excuse the ignorance. How can you get s-off without rooting first?
Click to expand...
Click to collapse
You cannot. There are temp root that work on some models otherwise you'll need HTCdev
Sent from my HTC One VX using Tapatalk

wgergely said:
A couple questions:
1). Does this actually change you back to locked the way <fastboot oem lock> would? or is it just changing the header text?
2). I see references to the Sprint M8 and this is in the M8 forum, but would if foul anyting up to try it on a Verizon M8 with the 3.16 HBoot?
Thanks for the clarification.
Click to expand...
Click to collapse
1) actual lock
2) it will work on vzw m8
Sent from my HTC One VX using Tapatalk

[GUIDE] Connecting the LG G3 to Linux/ADB (Aka stop "waiting for device....")

[GUIDE] Connecting the LG G3 to Linux/ADB (Aka stop "waiting for device....")
A bunch of people seem to be having trouble using Linux and ADB with their new phones. This is a step-by-step guide. I hope it helps some people.
Disclaimer: I am not responsible for anything you do to your devices. Following these instructions may or may not damage your phone or computer or anything else. You understand that following these instructions is done at your own risk.
THIS GUIDE DOESN'T WORK FOR VERIZON USERS ---> Edit: Thanks to Annoyingduck, we have the technique for the Verizon variant in post #5. If you are a VZW user, start with step #8 below and then replace steps 14 and 15 with annoyingducks instructions!
This has been tested on Ubuntu 14.04. Other variants may require some small changes.
This has been tested on the D851 (TMobile) variant. Sprint and ATT should be the same I think.
REQUIREMENTS: You must have root access to your linux box.
1. Unplug your phone from the computer
2. Make yourself a "developer" on your phone. Settings > General > About phone > Software information ... then tap "Build number" a bunch of times until it says "You are now a developer" or something like that.
3. Go into the developer settings ... Settings > General > Developer options
4. Check "USB Debugging"
5. Plug the phone in to your computer
6. Drop down the notifications menu and click on the item that has the subtitle "Tap for more USB options". Most likely, the main title will say "Media Device (MTP)". Anyway - click on that.
7. Then choose the option "Send Images (PTP)"
8. Tap your way back Home and then eject and unplug the phone from your computer again.
http://developer.android.com/sdk/installing/index.html?pkg=tools
9. As root, edit or create the file: /etc/udev/rules.d/51-android.rules
10. Add this line (if it isn't already there) Note that the idVendor is 1004 !!! :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
11. Save the file and then run (as root):
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
12. Then as root, run:
Code:
sudo service udev restart
13. Then:
Code:
sudo killall -9 adb
14. Plug your phone in, then try
Code:
adb devices
15. Hopefully, you'll see something like "LGD85149abcd01 device" ... which indicates that it is time to celebrate.
Now go root your phone or start developing uber-apps or something else equally awesome.
If the guide was useful, don't forget to hit Thanks!
Good luck!
Frank.
PS. Special shout out to the guys who developed PurpleDrake. I hope this guide helps some of the questions that are being asked on that thread ... and eases their work load.

thanks.
this will definitely help those who want to try purpledrake root

I get lost at step 9 lol.

ailima said:
A bunch of people seem to be having trouble using Linux and ADB with their new phones. This is a step-by-step guide. I hope it helps some people.
Disclaimer: I am not responsible for anything you do to your devices. Following these instructions may or may not damage your phone or computer or anything else. You understand that following these instructions is done at your own risk.
THIS GUIDE DOESN'T WORK FOR VERIZON USERS
This has been tested on Ubuntu 14.04. Other variants may require some small changes.
This has been tested on the D851 (TMobile) variant. Sprint and ATT should be the same I think.
--> NOTE: Verizon users need to connect to ADB a little differently. <-- You'll have to find different instructions.
REQUIREMENTS: You must have root access to your linux box.
1. Unplug your phone from the computer
2. Make yourself a "developer" on your phone. Settings > General > About phone > Software information ... then tap "Build number" a bunch of times until it says "You are now a developer" or something like that.
3. Go into the developer settings ... Settings > General > Developer options
4. Check "USB Debugging"
5. Plug the phone in to your computer
6. Drop down the notifications menu and click on the item that has the subtitle "Tap for more USB options". Most likely, the main title will say "Media Device (MTP)". Anyway - click on that.
7. Then choose the option "Send Images (PTP)"
8. Tap your way back Home and then eject and unplug the phone from your computer again.
http://developer.android.com/sdk/installing/index.html?pkg=tools
9. As root, edit or create the file: /etc/udev/rules.d/51-android.rules
10. Add this line (if it isn't already there) Note that the idVendor is 1004 !!! :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
11. Save the file and then run (as root):
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
12. Then as root, run:
Code:
sudo service udev restart
13. Then:
Code:
sudo killall -9 adb
14. Plug your phone in, then try
Code:
adb devices
15. Hopefully, you'll see something like "LGD85149abcd01 device" ... which indicates that it is time to celebrate.
Now go root your phone or start developing uber-apps or something else equally awesome.
If the guide was useful, don't forget to hit Thanks!
Good luck!
Frank.
PS. Special shout out to the guys who developed PurpleDrake. I hope this guide helps some of the questions that are being asked on that thread ... and eases their work load.
Click to expand...
Click to collapse
Great and useful guide Bro !

For Verizon, just enable debugging, connect phone, choose internet connection, ethernet (that will enable debugging), then in terminal just run sudo adb devices, the rsa key will pop up on screen, check it to always allow. Adb will show device as offline in the terminal window, now just run adb devices again without sudo and your good to go...

Thank you!

If you have ARCH / Manjaro or any ARCH base just type
sudo pacman -S android-udev
Plug in phone and profit

Just as an FYI to Fedora and CentOS 64 bit users: If you get an error about libraries missing you need to add the 64 bit libraries.
Code:
yum clean all
Code:
yum update
Code:
yum install glibc.i686 zlib.i686 libstdc++.i686 ncurses-libs.i686
After that you should be good.

annoyingduck said:
For Verizon, just enable debugging, connect phone, choose internet connection, ethernet (that will enable debugging), then in terminal just run sudo adb devices, the rsa key will pop up on screen, check it to always allow. Adb will show device as offline in the terminal window, now just run adb devices again without sudo and your good to go...
Click to expand...
Click to collapse
This worked for me.

I thank this guide will help too
But, don't use his files to root only the orignal purpledrake files from xda !
http://www.androidrootz.com/2014/07/how-to-root-lg-g3.html

Awesome, thanks. Always try look for those vendor ID's and stopping my phones of trying to install some darn Windows applications.
Android is Linux, why does it need Windows to function?

Thank you!
If i may to add more links for what help others:
ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.3+ (and for win 8+)
http://forum.xda-developers.com/showthread.php?t=2588979
Fastboot problems on Windows 8+ x64 with USB 3.0
http://forum.xda-developers.com/showthread.php?t=2256359
How to install ADB and Fastboot on Windows for use with Android [Guide] 2 methods
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/

Thanks!!! This really helped

Thank you
Very helpful

Thanks for the guide. Would it work on Mac OS X ?

Ths,it wroks pretty good.

Didn't work first time even though I took great care in implementing the command line steps (permissions, file name, file contents, location). Had to go back from the start to notice the PTP step! Howcome it needs to be in Picture Transfer mode? ...Not essential, as I have adb working now, but thought someone might know.
Many, many thanks! Incidentally, i'm only putting it in debugging mode to hunt down what's turning on my G3's Bluetooth by itself. I've never turned BT on nor have I paired it with anything for any reason. I've had the phone two weeks and I've turned bluetooth off a half-dozen times or so. It shows no correlation with Airplane Mode or the WiFi NFC switch or anything else - just happens while the phone is sitting unattended. If anyone has insight on that one, please share it w/me somehow.

Additional steps
If after the steps above device is not detected by sudo ./adb devices, turn off development options: click all apps button->click Settings->click General->Developer options->turn it off, change phone connection to "charging", then change connection to "Send Images (PTP)", and turn back on Developer options, run sudo ./adb devices, and it should detect the phone

Thank you very much. Works for me - LG-F460K 4.4.2

Would this work on LG G4? Currently I have the "waiting for device" problem.