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...
Related
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.
Only apply if you have a stock Roger's Magic without root!
The following procedure flashes the stock Roger's boot image with root access enabled to your Roger's Magic :
1. Copy this update to your SD-card.
2. Download RAv1.0's rooted recovery here.
3. Boot the device in fastboot mode.
4. Connect the device to your machine over USB.
5. $fastboot boot recovery-RAv1.0H.img
wait a few minutes and unplug your device from USB
6. Choose option "Apply sdcard:update.zip" from the menu
If the flashing doesn't work you might need to flash this SPL update from your sd-card after fast booting with recovery-RAv1.0H.img
If you want to have a rooted recovery as well, you can check out this post.
Enjoy
Special thanks to :
Haykuro for all his help ^^ , buy him a Nesquik!
JesusFreke for his JFv1.43's recovery
Would this work on the Rogers Dream?
alritewhadeva said:
Would this work on the Rogers Dream?
Click to expand...
Click to collapse
No it would not work.
It works! Woot Root!
Edit: Confirmed root adb access by pushing these onto my phone. Now my Rogers is more awesome! Huzzah!
how do i do the fifth step
"5. $fastboot boot recovery-RAv1.0H.img"
when i connect in fast boot method, i get a a found new hardware dialog box running windows vista ultimate x64 eition
trincisor said:
how do i do the fifth step
"5. $fastboot boot recovery-RAv1.0H.img"
when i connect in fast boot method, i get a a found new hardware dialog box running windows vista ultimate x64 eition
Click to expand...
Click to collapse
Did you install the drivers properly?
Now we need to get more roms working with the Rogers! Any ideas on how we con go about that?
is there any reason that this wouldn't work on the Dream ?
jpa- said:
is there any reason that this wouldn't work on the Dream ?
Click to expand...
Click to collapse
1. I don't think the kernel inside the recovery image would work on the dream.
2. The boot image inside the update is from the Magic, not from the dream.
There's no harm in trying to fastboot the recovery image... but I don't think it will work. Let us know if it would!
Don't we need rooted recovery to be able to restore our backups? Just confirming......
parrot5 said:
Don't we need rooted recovery to be able to restore our backups? Just confirming......
Click to expand...
Click to collapse
recovery-RAv1.0H.img is rooted...
Wow... Thanks Amon_RA! I can now install some input methods that I couldn't do...
We still can't just choose any ROM out there, correct? Or now that we have ROOT we are invincible? .. hehe
Here's another possible noobish question: there doesn't appear to be any su installed by default into the stock Rogers rom (ie. attempting to su from the console results in "su:not found"). Any ideas?
parrot5 said:
Wow... Thanks Amon_RA! I can now install some input methods that I couldn't do...
We still can't just choose any ROM out there, correct? Or now that we have ROOT we are invincible? .. hehe
Click to expand...
Click to collapse
The boot images inside the "any ROM" would have to be repacked using Haykuro's discovered offset
So make sure you know what you are doing and always make a backup of your current configuration first!
Any specific ROM you would like to run on your rooted Rogers?
skittleguy said:
Here's another possible noobish question: there doesn't appear to be any su installed by default into the stock Rogers rom (ie. attempting to su from the console results in "su:not found"). Any ideas?
Click to expand...
Click to collapse
Just download Koush's su from his blog here.
* Unzip the ZIP file (it will create a folder called Superuser).
* Run install.bat (or install.sh if you are on Linux) from the Superuser directory.
Amon_RA said:
The boot images inside the "any ROM" would have to be repacked using Haykuro's discovered offset
So make sure you know what you are doing and always make a backup of your current configuration first!
Any specific ROM you would like to run on your rooted Rogers?
Click to expand...
Click to collapse
Not sure I know what I'm doing I do not know how to mod an image.
I saw on the forum that a few people mentioned the Ion ROM is the fastest of the bunch? I definitely would want to try it. I know many other people who want the Hero ROM instead
Amon_RA said:
Just download Koush's su from his blog here.
* Unzip the ZIP file (it will create a folder called Superuser).
* Run install.bat (or install.sh if you are on Linux) from the Superuser directory.
Click to expand...
Click to collapse
Thank you so so much for all your work. You have truly made my month
wow it worked.. damn.. now i might have to get me a mytouch3g when it gets released
I followed the instructions and the phone rebooted... should I be able to su now?
I get permission denied..
thanks for your work on this Amon_RA & Haykuro!
All the best,
Rob
thank you for this.
i have a rooted rogers magic with su access.
wifi-tether is not working for me with the rogers rom. need to install a new rom i guess.
This is available for the G1 and i think it might also work the Magic. It's got a lot of features such as partition sd and format ext 2/3 and so much more.
I managed to download it however i am having some trouble installing it. It has to be done through terminal emulator and the Magic doesn't have
a physical keyboard and the onscreen keyboard doesn't even pop up. Any help on how to install this will be greatly appreciated. Thanks !
Amon Ra's (New) Custom Recovery v1.2.2
To Install:
Copy it to your sdcard and open the Terminal Emulator app then type in this code:
su
(if a message pops up click always allow)
flash_image recovery /sdcard/recovery-RA-dream-v1.2.2.img
Download NOW!!!
http://rapidshare.com/files/287548589/recovery-RA-dream-v1.2.2.img
they have several terminal emulators that have the onscreen keyboard built in... orrrrrrrrrr u can always press and hold the menu key when ur in the program to have it open
go to the market and just type in terminal it will pop up with many diff ones that support the magic
I am sure he is quite capable of posting his own threads in this, or any other section, such as he did here: http://forum.xda-developers.com/showthread.php?t=530492
the 1.2.2 update works fine on the MT3G, running it right now
I think this is a disgrace remove this thread i think amon is quite capable of posting his own work like he always does rather than getting in the lime light
Just to stay on topic, Amon_RA has posted personally in the Dream thread that this should work in a MT3G.
shadowleo85 said:
they have several terminal emulators that have the onscreen keyboard built in... orrrrrrrrrr u can always press and hold the menu key when ur in the program to have it open
go to the market and just type in terminal it will pop up with many diff ones that support the magic
Click to expand...
Click to collapse
but for the magic you obviously need an on screen keyboard- you cannot access the onscreen keyboard, nor terminal from recovery. this is how they differ- and this is why Amon_RA has made dedicated Magic recoveries that you can use adb commands while in recovery.
I am sure he will release a magic version of 1.2.2 once he finishes up his 1.6 ion rom which he must be working on (I hope)....
redmdc said:
I think this is a disgrace remove this thread i think amon is quite capable of posting his own work like he always does rather than getting in the lime light
Click to expand...
Click to collapse
agreed! close this thread k?
people stop *****ing
anyone wants to install on 32b magic
open adb and type when phone is in fastboot mode
fastboot flash recovery recovery-RA-dream-v1.2.2.img
i put the .img file in the tools folder
hope this helps
i flashed on my magic (32A) and it don't work!
boyscout80 said:
i flashed on my magic (32A) and it don't work!
Click to expand...
Click to collapse
Don't listen to the person who posted this thread.. instead, read this: http://forum.xda-developers.com/showthread.php?t=530492 there Amonr_RA explains how to test his recovery first before flashing.
MontAlbert said:
but for the magic you obviously need an on screen keyboard- you cannot access the onscreen keyboard, nor terminal from recovery. this is how they differ- and this is why Amon_RA has made dedicated Magic recoveries that you can use adb commands while in recovery.
I am sure he will release a magic version of 1.2.2 once he finishes up his 1.6 ion rom which he must be working on (I hope)....
Click to expand...
Click to collapse
I installed the latest recovery img on my Magic (32B) and I can use ADB commands just fine in recovery mode. I didnt know you couldnt at any point not use them.
What would rock is an onscreen keyboard in console... now that would be amazing to finally detether my rom flashing from the comp.
http://www.youtube.com/watch?v=9e7mMxVInJg
It works on the MyTouch 3G, trust me.
There's your proof. Enjoy.
boyscout80 said:
i flashed on my magic (32A) and it don't work!
Click to expand...
Click to collapse
Yeah, it's not 32a compatible...
(Nothing for the dream/32b is without tweaking it..)
I didn't post anything here yet because I plan to update the 32A and 32B ones soon.
OP - reboot your phone into SPL mode, then fastboot flash recovery recovery.img(whatever the name of the file is)
Alright I really want to use this recovery but right now im using cyanogen 1.4 + JF recovery..how do i go about switching? sorry to thread jack.
Amon_RA said:
I didn't post anything here yet because I plan to update the 32A and 32B ones soon.
Click to expand...
Click to collapse
is it even possible to get a virtual keyboard to work in console? through recovery?? please say yes, and that youve made this magical feature part of the update
Sorry to ad to this idiotic thread. All you have to do to use vk in terminal is hold menu button down. Numbers will not work in terminal so download a terminal that does or just rename file so it has no numbers in it. Its not rocket science you newbs make stuff so hard n complicated.
Wait for Update Guys
Amon_RA said:
I didn't post anything here yet because I plan to update the 32A and 32B ones soon.
Click to expand...
Click to collapse
Okay i'll wait on that one, i know some people have already tried it on the magic
but i don't wanna screw up my phone trying to flash this one. I'll stick with v.1.2
for now. Thanks Amon_RA
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.
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!
How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.
GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?
hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.
GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left
GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?
hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.