Database Info

Simpler instructions for installing modified recovery image

Here are some instructions for installing JesusFreke's modified recovery image. You have to install the modified recovery image before you can install modified firmwares. These instructions are simpler than the existing ones because they don't require the use of adb or telnet.
Firstly, you need to already have firmware version RC29 or RC7. To check which version you have go to "Settings" and then "About phone". At the bottom you will see a "Build number" which will include "RC" and then a number. If you have RC30 or RC8 then you need to downgrade. THAT WILL WIPE ALL THE DATA/APPLICATIONS ON YOUR PHONE. Instructions for downgrading are here.
Now that you have RC29/RC7:
Download 'AndroidMod.zip' from one of the links in JesusFreke's post
Extract 'recovery_testkeys.img' from that zip and copy it to your SD card.
Download 'install.zip' which is attached to this post below.
Extract 'install' from that zip and copy it to your SD card.
Put the SD card in the phone or disconnect the phone if it is attached by USB.
Reboot the phone (switch it off and then on again).
When it has finished booting type the following at the home screen. It will start searching your contacts, but don't worry about that. Also, you won't see any visible sign that the first command worked. Just go ahead and type the second command straight afterwards:
cd sdcard<press enter>
sh install<press enter>
After a moment your phone should reboot itself. To check that the flashing worked, switch off the phone and then hold down the home key while you switch it on again. Keep the home key held down until you see the recovery screen (with the "!" triangle and the picture of the phone). Then press Alt+L on the keyboard and if you see "Using test keys" on the second line of text then the modified recovery image is installed and you can now install a modified firmware.

Cool! Thanks for that... much simpler... anyone else tried this yet?
I'm going to attempt all this later.
Phil

i just tried it and it works. confirmed.

great for beginners!
Hey tried it and it works!! Now how about one on restoring data after backup.

thanks for this just tryed it and worked first time.

First off thanks for all information here. Am I correct that after I downgrade to rc29 I then follow the instructions in this thread and then I can install jf 1.3 rc30. Or do I have this all wrong?

gottifour said:
First off thanks for all information here. Am I correct that after I downgrade to rc29 I then follow the instructions in this thread and then I can install jf 1.3 rc30. Or do I have this all wrong?
Click to expand...
Click to collapse
you are correct. once you have the modded recovery image, you can use jfs update zips.

korndub said:
you are correct. once you have the modded recovery image, you can use jfs update zips.
Click to expand...
Click to collapse
Sweet! Thanks for the reply. I will attempt this real soon. Do you have any suggestions before I begin? After I modify the firmware I will not get ota updates anymore right? Lets say the cupcake update, or any other for that matter, does come out. I would just have to wait untill a smarter person then me converts it to a new modified image to flash to my phone? Is that right? Thanks for any help. I'm sure this is probably the worng place to ask all of these questions. d

gottifour said:
Sweet! Thanks for the reply. I will attempt this real soon. Do you have any suggestions before I begin? After I modify the firmware I will not get ota updates anymore right? Lets say the cupcake update, or any other for that matter, does come out. I would just have to wait untill a smarter person then me converts it to a new modified image to flash to my phone? Is that right? Thanks for any help. I'm sure this is probably the worng place to ask all of these questions. d
Click to expand...
Click to collapse
in one of the zips from JF is an app that will REsign any update.zip, so when an ota comes you just have to wait for the update.zip to show up then you could REsign it with the dev keys, pretty easy, but it will probably show up pretty fast now that almost every G1 is probably running that keyset.
bhang

UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right? I did type telnetd at the home screen and pushed enter. nothing happened. I know I'm missing something just not sure what yet? I did install the telnet client from the market as well. I'm not understanding something it appears. Anyone?

gottifour said:
UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right? I did type telnetd at the home screen and pushed enter. nothing happened. I know I'm missing something just not sure what yet? I did install the telnet client from the market as well. I'm not understanding something it appears. Anyone?
Click to expand...
Click to collapse
use the telnet client to telnet to localhost. *then* you will have root. (note: that's only applicable for RC29. to get root on JFv1.3, just type su in terminal emulator).
To know if you have root access, check the prompt you get. if you get #, then you have root access. if you get $, you don't have root access.

JJC1138 said:
Here are some instructions for installing JesusFreke's modified recovery image.
Click to expand...
Click to collapse
well this is a big help for many people thank you for your addition

JesusFreke said:
use the telnet client to telnet to localhost. *then* you will have root. (note: that's only applicable for RC29. to get root on JFv1.3, just type su in terminal emulator).
To know if you have root access, check the prompt you get. if you get #, then you have root access. if you get $, you don't have root access.
Click to expand...
Click to collapse
I got the #
Thanks so much for everything so far..This is really awesome!!

gottifour said:
UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Click to expand...
Click to collapse
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
gottifour said:
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right?
Click to expand...
Click to collapse
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.

JJC1138 said:
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
Click to expand...
Click to collapse
Thanks for the reply and for simplifying this for everyone. I was confused at first but now I understand better. I have the modified RC30 working now with the dev boot loader as well. Oh and a new theme too. Thanks again!!!

JJC1138 said:
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
Click to expand...
Click to collapse
Correct, this is a really good idea! Instead of typeing telnetd to start it as root, you are typing in and running the script that will root your phone-- as root! I'll update my sticky post shortly.

worked for me now do i delete the install file, DREAIMG file and Recovery test keys files or do i have to keep em?

l0uisz said:
worked for me now do i delete the install file, DREAIMG file and Recovery test keys files or do i have to keep em?
Click to expand...
Click to collapse
You can delete them off your SD card after they're installed.

[23/05] rooting the "Magic" - we have a root! [MODS?]

MODS - can you please move this thread to the sapphire development forum and stick it? thanks
_______________________________________________________________
WE HAVE A ROOT NOW
haykuro said:
GOT ROOT?
http://droiddeveloper.com/hrbuilds/boot-new.img.zip
1. download this, extract boot-new.img to your computer.
2. place your device into bootloader mode (BACK+POWER, or VOLUME DOWN+POWER)
3. fastboot boot boot-new.img
4. wait for device to boot
5. adb push boot-new.img /sdcard/boot-new.img
6. adb shell flash_image boot /sdcard/boot-new.img
that's it!
your device now has root via adb shell.
i'm making the rooted recovery.img now for magic
Click to expand...
Click to collapse

It shouldn't be too hard.
Viper only needs to update his QMAT for creaatin goldcards for the Magic.
Then you have to flash the RC29 nbh with it.
If only adb successes connecting to the magic with rc29 of g1, you can start telnetd.
Then you should be able to. Flash a custom recovery image to flash a modified cupcake.

maxisma said:
It shouldn't be too hard.
Viper only needs to update his QMAT for creaatin goldcards for the Magic.
Then you have to flash the RC29 nbh with it.
If only adb successes connecting to the magic with rc29 of g1, you can start telnetd.
Then you should be able to. Flash a custom recovery image to flash a modified cupcake.
Click to expand...
Click to collapse
Well, you see what I meant? all the expert are here!
Let's wait for Viper comment and/or ideas.

But one problem:
I don't know if the RC29 is compatible with the Magic. Maybe someone has to create a custom .nbh with customized drivers for the magic.
And please. Don't call me an expert
It's only an idea I know linux commands etc. But i know only some basics of programming (e.g. to make a DOS caluclator in C++ )

maxisma said:
But one problem:
I don't know if the RC29 is compatible with the Magic. Maybe someone has to create a custom .nbh with customized drivers for the magic.
And please. Don't call me an expert
It's only an idea I know linux commands etc. But i know only some basics of programming (e.g. to make a DOS caluclator in C++ )
Click to expand...
Click to collapse
I am far from being an expert but even if RC29 works and the DREAM test recovery works (which I doubt), it has no support for virtual keyboard, so right after he gets root he will need a hacked rooted ROM for the Magic. Isn't it safe to assume that until someone cook a special ROM for the Magic he is stuck with a rooted but unusable device?

A much bigger problem: how in the hell can you telnet in the Magic with no keyboard? Or even get past the setup wizard? In other words, even with RC29 there'll be no way to get root or even use the phone. This is gonna be a hell of a lot more difficult than it was for the G1(and it was pretty damn difficult for that)

Well, I guess HTC created this function for their reasons (tests etc.) and now it's only a matter of time until someone will find the way to do it too.
that's the reasone I posted the request, I seen things in XDA that i could never believe before, let's hope it'll happen again ...

Will this post help? http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
The guy pk detailed a 27 step, step-by-step guide to unlock those HTC Dream outside UK and US. Hope it helps.

chuazy said:
Will this post help? http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
The guy pk detailed a 27 step, step-by-step guide to unlock those HTC Dream outside UK and US. Hope it helps.
Click to expand...
Click to collapse
"2) Launch Terminal Emulator
3) Enter the following:
cd /sys/class/mmc_host/mmc1:*"
Terminal Emulator doesn't seem to work without hardware keyboard(doesn't bring up vk for me on G1 using cupcake, I'd imagine it wouldn't work on magic either). Speaking of which, you guys with Magic's wouldn't be able to use any of the recovery mode options either since those all require a hw keyboard. So even if you got a JF build you wouldn't be able to flash it.

[email protected] said:
"2) Launch Terminal Emulator
3) Enter the following:
cd /sys/class/mmc_host/mmc1:*"
Terminal Emulator doesn't seem to work without hardware keyboard(doesn't bring up vk for me on G1 using cupcake, I'd imagine it wouldn't work on magic either). Speaking of which, you guys with Magic's wouldn't be able to use any of the recovery mode options either since those all require a hw keyboard. So even if you got a JF build you wouldn't be able to flash it.
Click to expand...
Click to collapse
But you do understand this function must be exist right? even if you can't find it now, HTC created it because they do use the recovery mode options for test and stuff...

avimak said:
But you do understand this function must be exist right? even if you can't find it now, HTC created it because they do use the recovery mode options for test and stuff...
Click to expand...
Click to collapse
Unless they do so using some external hardware which is fully possible...(think external keyboard, possibly through extUSB)
EDIT: btw: not trying to be an ass or say that you guys are screwed, just pointing out problems that will need to be solved in order for this to work.

[email protected] said:
Unless they do so using some external hardware which is fully possible...(think external keyboard, possibly through extUSB)
EDIT: btw: not trying to be an ass or say that you guys are screwed, just pointing out problems that will need to be solved in order for this to work.
Click to expand...
Click to collapse
Well, if external USB keyboard is the only thing it takes to root my device - I'll buy one, and root the rest of the Magic Israeli users for free

You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.

maxisma said:
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
Click to expand...
Click to collapse
I got it:
$ (I can write stuff)...
what next?

@avimak:
You mean, you've connected your magic with installed rc29?

maxisma said:
@avimak:
You mean, you've connected your magic with installed rc29?
Click to expand...
Click to collapse
No, I have the Magic (vodafone version) connected to my PC (win xp) and I can run ADB shell.

avimak said:
No, I have the Magic (vodafone version) connected to my PC (win xp) and I can run ADB shell.
Click to expand...
Click to collapse
ok.
But i meant someone has to test if a magic downgraded to rc29 (via goldcard) works.
Not the orig. Firmware.

maxisma said:
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
Click to expand...
Click to collapse
That's true for the terminal once the operating system has started, but they'll be hosed if they ever reach a boot looping problem or need to flash any ROM.
EDIT: Well not if they boot loop on the android screen, but if it loops on the SPL, then they're hosed.

[email protected] said:
That's true for the terminal once the operating system has started, but they'll be hosed if they ever reach a boot looping problem or need to flash any ROM.
EDIT: Well not if they boot loop on the android screen, but if it loops on the SPL, then they're hosed.
Click to expand...
Click to collapse
Can you please write it again in simple words?
It's a bit "pro only" talking. I got my Android yesterday...

maxisma said:
ok.
But i meant someone has to test if a magic downgraded to rc29 (via goldcard) works.
Not the orig. Firmware.
Click to expand...
Click to collapse
There is an option to go back to the orig. version after the downgrade? can I "dump" my OS somewhere and Install it again from SPL if it failed the rc29?
I'm coming from WM - I'm speaking they lang...

Us sprint 2.1 rom leaked.its exe file . For non rooted

http://www.4shared.com/file/WU7XiKt-/RUU_Hero_C_Sprint_2206511_sign.html
to all dev. its said the leak for sprint 2.1 .is exe file.non rooted phone can upgrade it. heard everyyhing work fine. im gsm version. im not respondsible for any damage or bricked of your phone.
the source from facebook htc hero page.
Sent from my Hero using Tapatalk

IS FOR SPRINT. NOT GSM. BE ALERT
Sent from my Hero using Tapatalk

orangeclanz said:
http://www.4shared.com/file/WU7XiKt-/RUU_Hero_C_Sprint_2206511_sign.html
to all dev. its said the leak for sprint 2.1 .is exe file.non rooted phone can upgrade it. heard everyyhing work fine. im gsm version. im not respondsible for any damage or bricked of your phone.
the source from facebook htc hero page.
Sent from my Hero using Tapatalk
Click to expand...
Click to collapse
Nice to see the CDMA Hero has it's official 2.1 fame .. but come on lazy HTC, where is 2.1 for the GSM cousin? Let's hope tomorrow is THE day..

Looks like it's working
EDIT: However, this is exactly the same as Villain 5.2 (the same leak that is).

Pretty stable
It does work well.. What an improvement from the previous version

HomerSp said:
Looks like it's working
Click to expand...
Click to collapse
But not on GSM Hero's - grrrrrrrrrrrrrrrr

Didn't the GSM hero come out before the CDMA one? How come the CDMA one came out first?

hkr said:
But not on GSM Hero's - grrrrrrrrrrrrrrrr
Click to expand...
Click to collapse
It does if you port it (I only have gsm) ;-)

HOW LEGIT IS THIS RUU THOUGH? who can co-sign it? my buddy wants to use it but doesn't want to take any chances..

someonenewhere said:
Who can co-sign it?.
Click to expand...
Click to collapse
What?
I need a Mercedes? Can someone co-sign it?
Just playing

Old news >> http://forum.xda-developers.com/showthread.php?t=661057
All of our dev's 2.1 builds are already based on this build.
FYI, when the final (non-test) build .exe comes out, flashing your phone with it may render your phone unrootable.

someonenewhere said:
HOW LEGIT IS THIS RUU THOUGH? who can co-sign it? my buddy wants to use it but doesn't want to take any chances..
Click to expand...
Click to collapse
I put it on my Hero with no problems. My guess is its very close to the RC. Or he could just wait!!

Once you have used this leaked RUU from Sprint, how do you go and flash one of the ROMs here? When I attempt to do it, I get a pic of a generic HTC phone with a red triangle and a red exclamation point. I have to do a battery pull to get it to go away.

Don't flash a ruu that doesn't have root. The exploits used to gain root are probably patched. Also this will over write your custom recovery. Leaving you with no way to flash custom roms. Wait until someone puts out a build with root.

tedya said:
Once you have used this leaked RUU from Sprint, how do you go and flash one of the ROMs here? When I attempt to do it, I get a pic of a generic HTC phone with a red triangle and a red exclamation point. I have to do a battery pull to get it to go away.
Click to expand...
Click to collapse
Sounds like you already installed the ruu I'm guessing?..lol.
You need flash a custom recovery to the phone now to be able to flash custom ROMs.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid backup your phone first thing >> Next you choose flash .zip and choose any custom ROM signed .zip on your sdcard to flash. >> After it flashes, reboot.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image

danknee said:
Sounds like you already installed the ruu I'm guessing?..lol.
You need flash a custom recovery to the phone now to be able to flash custom ROMs.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid backup your phone first thing >> Next you choose flash .zip and choose any custom ROM signed .zip on your sdcard to flash. >> After it flashes, reboot.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
Hi Dankee. I am having difficulties pushing flash_image. This is what I type/get:
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Any ideas? Thanks so much.

tedya said:
Hi Dankee. I am having difficulties pushing flash_image. This is what I type/get:
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Any ideas? Thanks so much.
Click to expand...
Click to collapse
you cant gain root in any other way now theres no known exploit for 2.1 yet so your basically screwed till someone finds a exploit next time gather information before you run some random program that hasnt even really been verified

Yeah, I have learned my lesson I think. I think I am going to wait around until there is an exploit for 2.1 before I end up bricking this thing. I ended up getting the flash_image pushed but now I can't reboot and use the recovery image. It goes straight to a HTC with red triangle and red exclamation point. Luckily I was able to do a battery pull and it rebooted straight to the RUU 2.1 ROM. I thought I had bricked the thing. Whew! I'll see what some of the masterminds come up with here.
I think all I am missing is being able to go into bootloader and do the v1.6.2 recovery image and then flash a custom ROM.

http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-a
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-after-using-2-1-ruu.html
This worked for me thanks to GBhil!

Thanks SooooneR! This worked for me. I am flashing one of DamageControl's ROMs right now. Very cool.

Rogers HTC Dream - froyo update

Question to those who have updating their Dream from Rogers, was it at all slow or where their noticeable improvements?
I have one at my disposal but running stock OS (1.5/1.6 i assume). Anyone have a nice and easy to follow tutorial to update this phone without hassles? Also does updating android OS require rooting the device?
Thanks in advance.

Bloodyskullz said:
Question to those who have updating their Dream from Rogers, was it at all slow or where their noticeable improvements?
I have one at my disposal but running stock OS (1.5/1.6 i assume). Anyone have a nice and easy to follow tutorial to update this phone without hassles? Also does updating android OS require rooting the device?
Thanks in advance.
Click to expand...
Click to collapse
try this:
http://theunlockr.com/category/howto/android_how_tos/htc-g1-dream-how-tos/
Follow instructions. This seems to me to be the easiest guide. Be careful of the Rogers/T-Mobile thing. Seems there are different radio's and such. I don't know anything about Rogers. As far as Roms, I use HTCclay's Superfly TCBY. Lot of memory left on phone. Just try a few to see which you like. Good Luck.
By the way, you do have to be rooted. The guide will walk you through it.

crz6662 said:
try this:
http://theunlockr.com/category/howto/android_how_tos/htc-g1-dream-how-tos/
Follow instructions. This seems to me to be the easiest guide. Be careful of the Rogers/T-Mobile thing. Seems there are different radio's and such. I don't know anything about Rogers. As far as Roms, I use HTCclay's Superfly TCBY. Lot of memory left on phone. Just try a few to see which you like. Good Luck.
By the way, you do have to be rooted. The guide will walk you through it.
Click to expand...
Click to collapse
I would say to try the ROM in my sig (the stock ROM)
works for g1 and 32B Magic

he is going to need the EBI1 kernel to go with the rom.

Ok I am reviving this thread because I want to make sure I am following the right steps in doing so. Don't want to mess this up.
Successfully rooted the phone following video I found in the second post of this thread. Can't link you to it because I am still a new member =S! I checked the radio version of the phone and it is 3.22.20.17. Which ROM is recommended?As I said, I just want to get rid of this terrible stock rom from rogers and put froyo (which in turn also allows me to get touch screen keyboard activated) on here.
Thanks in advance.

With that radio you will need to flash ebi1 kernels after you flash the roms.
I completely forgot that Rogers blocked the virtual keyboard with their firmware. That's such bull****.
Sent from my HTC Hero using XDA App

asb123 said:
With that radio you will need to flash ebi1 kernels after you flash the roms.
Click to expand...
Click to collapse
Now you have more information in the link in your sig. Question: Can you re up the RS link you have there? Also, rooting the phone just means that you have the app called Superuser?
Now I get quite lost the moment you start explaining the options HTC Dream users have. Is there a recommended ROM to download for this phone considering its specs?
I completely forgot that Rogers blocked the virtual keyboard with their firmware. That's such bull****.
Click to expand...
Click to collapse
Yes it is sad that rogers has done this. Do whatever they can to screw the consumers over. Just found out it is 1.5.

Any help on this?

Ok still lost on trying to do this and want to follow the set up from cyanogen but its really complicated. I don't want to make a backup of contacts and stuff because it wasn't originally my phone.
Do I still need the amon_ra's recovery?

Bloodyskullz said:
Ok still lost on trying to do this and want to follow the set up from cyanogen but its really complicated. I don't want to make a backup of contacts and stuff because it wasn't originally my phone.
Do I still need the amon_ra's recovery?
Click to expand...
Click to collapse
Think of what you need to do:
1) Obtain root access so that you can flash a new recovery
2) Replace recovery so that you can flash new SPL
3) Flash new SPL so that you can be more compatible with roms / kernels
4) Flash a new rom (IE/ Cyanogenmod 6), and a compatible EBI1 kernel (for instance, Brian Crook's ones on the Cyanogenmod website)
Without getting into huge detail, you do it in this order to prevent your device from being unable to boot / recover.

You can flash the new RADIO and SPL from here: http://forum.xda-developers.com/showthread.php?goto=newpost&t=831139
Along with that, you use the appropriate supported +14MB EBI0 kernel.
More RAM is good

Well that makes sense.
Now I am following the Cyanogen wiki link (can't post there) and it says to launch flash rec but I can't understand from where I have to do this. Anyone care to help? And how does the Andriod SDK help?

Bloodyskullz said:
Well that makes sense.
Now I am following the Cyanogen wiki link (can't post there) and it says to launch flash rec but I can't understand from where I have to do this. Anyone care to help? And how does the Andriod SDK help?
Click to expand...
Click to collapse
Andriod sdk has the adb component needed to initiate commands to your device from your computer. then you need the android windows usb drivers.after installing sdk to see if you have connection with your device, open console on your computer start>run>type cmd and hit enter at the prompt type adb you should get several lines back kind of an options menu. at next prompt type adb devices. if your device is recognized you will get back:
device XXXXXXXX (this will be an actual number).
if you dont get any devices back with your phone attached to usb then you probably need the driver. just google it.
as for flashrec I dont believe I used this. I used exploid to gain root and install 1.33.2005 spl

Where do I get the android driver for windows (7 64bit specifically)? Adb command aint working in my cmd.
So what do I do about flashrec? Man updating this thing is driving me nuts. So many unexpected curves.

I also have Windows 7 64bit and I didn't need a driver it just works for me. Please tell us exactly what you are typing in and what output you are getting. You could also try the instruction to install the usb driver here:
http://developer.android.com/sdk/win-usb.html
What is your build number in settings? If it is 1.89.631.1 you are following the wrong guide. (see the top of that guide)

beav_35 said:
I also have Windows 7 64bit and I didn't need a driver it just works for me. Please tell us exactly what you are typing in and what output you are getting. You could also try the instruction to install the usb driver here:
http://developer.android.com/sdk/win-usb.html
What is your build number in settings? If it is 1.89.631.1 you are following the wrong guide. (see the top of that guide)
Click to expand...
Click to collapse
When I type in ADB command it just states that the command is not recognized (even when SDK is open).
Build number 1.85.631.5.
Now when I turn on phone it accepts it after I plug it into computer. I can mount sd card to copy files without issue.
Do I need another tutorial (preferably video since its easier for me but text is just fine)?

Bloodyskullz said:
When I type in ADB command it just states that the command is not recognized (even when SDK is open).
Click to expand...
Click to collapse
This doesn't mean that it can't find your phone, it means that it can't find the adb.exe.
Bloodyskullz said:
Build number 1.85.631.5.
Click to expand...
Click to collapse
That is a pre-911 build. Don't see too many of those any more. Rogers harassed everyone into updating.
Bloodyskullz said:
Now when I turn on phone it accepts it after I plug it into computer. I can mount sd card to copy files without issue.
Do I need another tutorial (preferably video since its easier for me but text is just fine)?
Click to expand...
Click to collapse
http://www.bleepingcomputer.com/tutorials/tutorial76.html
http://forum.xda-developers.com/showthread.php?t=502010
http://www.youtube.com/watch?v=Z3SpI7m7mFI

Does the zip file for the android SDK make a difference if I can't install it through the .exe? It keeps saying that it doesnt detect the Java SDK when I try to install.

Yes, you can use the .zip. Extract it, run setup.exe, install Platform-tools, cd to the platform-tools directory then you can use adb. Fastboot is in the tools directory. That was just changed in the 2.3 sdk update so I don't know if the guide has been updated yet.

beav_35 said:
Yes, you can use the .zip. Extract it, run setup.exe, install Platform-tools, cd to the platform-tools directory then you can use adb. Fastboot is in the tools directory. That was just changed in the 2.3 sdk update so I don't know if the guide has been updated yet.
Click to expand...
Click to collapse
The only .exe file in the zip is the SDK Manager which isnt exactly an install.

System backup please?!

Hi people. Ive just bricked my Relay by installing Chainfire3D(dont laugh at me I know im stupid)))). So can anyone do a backup the system by Recovery mode and send me to my email [email protected] or attach it here, I will put it in my SD and do a restore from recovery mode(i didnt brick it fully, I guess its called softbrick).
I would really appreciate anybodies help. Please people I really need help...Thanks in advance)))

Just flash a new ROM in recovery, or if you plan to just do a restore of a system partition you would need to give out more information as to flash the correct one as each ROM will have a different system partition

the cavaca
Hey, just emailed the stock ROM, and the stock Recovery. You will need to install the stock Rom first, then flash the stock recovery. Hope it helps.

SuddenGun007 said:
Hey, just emailed the stock ROM, and the stock Recovery. You will need to install the stock Rom first, then flash the stock recovery. Hope it helps.
Click to expand...
Click to collapse
Thanks man, really appreciate your help.

HaykKarapetyan said:
Thanks man, really appreciate your help.
Click to expand...
Click to collapse
To install I need to know a couple of things, are you using a computer with Windows? Also do you have a custom recovery on your phone? Hold onto the Volume up key+Home+Power, when it vibrates and shows "Recovery Mode" in little blue letters on the screen let go of the buttons and it will boot into recovery mode. If it looks like the picture here [cdn.droidviews.com/wp-content/uploads/2013/01/android-recovery-on-galaxy-s3.jpg], this is stock recovery. If it has "ClockworkMod Recovery" you are off to a good start. Let me what you have.

SuddenGun007 said:
To install I need to know a couple of things, are you using a computer with Windows? Also do you have a custom recovery on your phone? Hold onto the Volume up key+Home+Power, when it vibrates and shows "Recovery Mode" in little blue letters on the screen let go of the buttons and it will boot into recovery mode. If it looks like the picture here [cdn.droidviews.com/wp-content/uploads/2013/01/android-recovery-on-galaxy-s3.jpg], this is stock recovery. If it has "ClockworkMod Recovery" you are off to a good start. Let me what you have.
Click to expand...
Click to collapse
So my computer runs Windows Vista and i have ClockworkMod Recovery. At the bottom in the Recovery mode it says CWM- based Recovery v6.0.1.2

HaykKarapetyan said:
So my computer runs Windows Vista and i have ClockworkMod Recovery. At the bottom in the Recovery mode it says CWM- based Recovery v6.0.1.2
Click to expand...
Click to collapse
So to get back to stock, on your recovery there should be an option to sideload a file using ADB. Your going to have to use these instructions to get ADB onto your Windows install.
1. Make sure Java is installed on your system go to.....www.java.com/ and install their version, and restart computer if necessary.
2. Then go to http://developer.android.com/sdk/index.html to download the SDK for android allowing use of ADB. You will need to extract this folder to your C: drive. 1-Create a folder on the root of your C: called Android, then unpack the SDK you downloaded into this folder, and open up sdkmanager.exe and install updates and packages. The main one you want is called "platform-tools" which holds the ADB.exe file you will need.
2.A) Make sure you clear/format your cache/dalvik cache/ and data before you flash the zip in the instructions below.
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you.
4. Now it will be waiting for the program you just installed to "push" the zip to your phone. So go to the Start menu, and type in the search box cmd and hit enter.
5. Now type in "CD C:\Android\(**whatever SDK file you have**)\platform-tools\" and hit enter. When typing you can hit the TAB key to autocomplete the folder name. Now your directory should of changed, and you should be able to type "adb sideload (you will need to type in the full path of the file where you stored the Stock JB image at (the one I emailed you). and hit enter. Once it sideloads you should be able to reboot and it will bootup regularly, after this I would suggest flashing philz touch recovery which has a few more features.

SuddenGun007 said:
So to get back to stock, on your recovery there should be an option to sideload a file using ADB. Your going to have to use these instructions to get ADB onto your Windows install.
1. Make sure Java is installed on your system go to.....www.java.com/ and install their version, and restart computer if necessary.
2. Then go to http://developer.android.com/sdk/index.html to download the SDK for android allowing use of ADB. You will need to extract this folder to your C: drive. 1-Create a folder on the root of your C: called Android, then unpack the SDK you downloaded into this folder, and open up sdkmanager.exe and install updates and packages. The main one you want is called "platform-tools" which holds the ADB.exe file you will need.
2.A) Make sure you clear/format your cache/dalvik cache/ and data before you flash the zip in the instructions below.
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you.
4. Now it will be waiting for the program you just installed to "push" the zip to your phone. So go to the Start menu, and type in the search box cmd and hit enter.
5. Now type in "CD C:\Android\(**whatever SDK file you have**)\platform-tools\" and hit enter. When typing you can hit the TAB key to autocomplete the folder name. Now your directory should of changed, and you should be able to type "adb sideload (you will need to type in the full path of the file where you stored the Stock JB image at (the one I emailed you). and hit enter. Once it sideloads you should be able to reboot and it will bootup regularly, after this I would suggest flashing philz touch recovery which has a few more features.
Click to expand...
Click to collapse
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions

HaykKarapetyan said:
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions
Click to expand...
Click to collapse
605 MB I should have said......what I meant was that in your first reply you told to install rom and then flash recovery and I dont think all that is done by only these 5 steps

HaykKarapetyan said:
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions
Click to expand...
Click to collapse
Since you have ClockworkMod you won't be needing the "stock-recovery.zip" I sent you. You will only need the "JB-stock-system.zip". Now when the drivers install make a checklist and make sure you have Java installed...and then the Android SDK. It really is a 3 step process, but since you soft-bricked your phone you can't simply copy the stock-system.zip to your sdcard and flash that in recovery. You will need adb to communicate with your phone while in recovery.

SuddenGun007 said:
Since you have ClockworkMod you won't be needing the "stock-recovery.zip" I sent you. You will only need the "JB-stock-system.zip". Now when the drivers install make a checklist and make sure you have Java installed...and then the Android SDK.
Click to expand...
Click to collapse
So in 5th step I should locate to that 605mb.zip,without extracting it

stimuli erpio
HaykKarapetyan said:
So in 5th step I should locate to that 605mb.zip,without extracting it
Click to expand...
Click to collapse
Yes that is correct, the recovery when it installs will unpack it for you.

SuddenGun007 said:
Yes that is correct, the recovery when it installs will unpack it for you.
Click to expand...
Click to collapse
Alright man, thanks. Still installing the freaking drivers)))

HaykKarapetyan said:
Alright man, thanks. Still installing the freaking drivers)))
Click to expand...
Click to collapse
I am using Linux, otherwise I would try to send you the drivers.
You might be able to use this http://www.solvusoft.com/en/update/drivers/mobile-phone/samsung/t-mobile/sgh-t699/model-numbers/

SuddenGun007 said:
I am using Linux, otherwise I would try to send you the drivers.
Click to expand...
Click to collapse
Naah thanks its fine, the computer's too old and tries to find some sort of update every single time I plug my phone in and takes hours to just say that the drivers are ip to date and im good to go, before all that ipdate stuff it doesnt let you to use the phone......well thats what you get from (at least) 6 year old Vaio Sony laptop))))

HaykKarapetyan said:
Naah thanks its fine, the computer's too old and tries to find some sort of update every single time I plug my phone in and takes hours to just say that the drivers are ip to date and im good to go, before all that ipdate stuff it doesnt let you to use the phone......well thats what you get from (at least) 6 year old Vaio Sony laptop))))
Click to expand...
Click to collapse
Oh crap I didnt see you had a link there, let me check that one out

This isn't probably the best thread to suggest this, but I recommend you look into a linux distro to install on your laptop. Before I had my current one, I was on a 7 year old HP compaq, and I put Lubuntu on it, and made it pretty much brand new. The only thing is getting used to the Linux filesystem,and commandline. Might take a few weeks of using it, but it really helped me out when XP was terribly slow. It also installs ADB and can interface with android phone. Maybe try a liveUSB so you don't have to install it.

SuddenGun007 said:
This isn't probably the best thread to suggest this, but I recommend you look into a linux distro to install on your laptop. Before I had my current one, I was on a 7 year old HP compaq, and I put Lubuntu on it, and made it pretty much brand new. The only thing is getting used to the Linux filesystem,and commandline. Might take a few weeks of using it, but it really helped me out when XP was terribly slow. It also installs ADB and can interface with android phone. Maybe try a liveUSB so you don't have to install it.
Click to expand...
Click to collapse
Thanks for advice... I guess I'll be getting a brand new computer in two months so and I was thinking of what I should do with this one, now I know)))), thanks....Can you believe it still tries to find and update something, I mean its horribly slow......anyway so one question just arose, if luckily, hopfully I get my phone back will it be still rooted or will I have to root it???

HaykKarapetyan said:
Thanks for advice... I guess I'll be getting a brand new computer in two months so and I was thinking of what I should do with this one, now I know)))), thanks....Can you believe it still tries to find and update something, I mean its horribly slow......anyway so one question just arose, if luckily, hopfully I get my phone back will it be still rooted or will I have to root it???
Click to expand...
Click to collapse
With the stock I gave you, you will not be rooted, it will appear as if you just turned it on for the first time, if you want to be root and use Cyanogenmod, I suggest instead of sideloading the image I gave you, go here and download this and sideload this rom (this is stable 10.2)
http://download.cyanogenmod.org/?type=stable&device=apexqtmo
Also here is awesome instructions (stepbystep) to install everything on it.
http://wiki.cyanogenmod.org/w/Install_CM_for_apexqtmo

SuddenGun007 said:
With the stock I gave you, you will not be rooted, it will appear as if you just turned it on for the first time, if you want to be root and use Cyanogenmod, I suggest instead of sideloading the image I gave you, go here and download this and sideload this rom (this is stable 10.2)
http://download.cyanogenmod.org/?type=stable&device=apexqtmo
Also here is awesome instructions (stepbystep) to install everything on it.
http://wiki.cyanogenmod.org/w/Install_CM_for_apexqtmo
Click to expand...
Click to collapse
Ok so if I download this and lets say put this zip in c:\Android what command should I run in cmd???