yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] humaders99:
Hey I needed to unroot my phone too and I tried a bunch of things then I was following procedures to root my phone again because I tried installing the Rom that was posted by the person that posted before me and I messed up and got lots of errors when I got the phone started and had to force close a bunch of things constantly. Anyways I followed step 3 of the tut for rooting TELUS desires on this forum site and when it restarted I got my stock TELUS Rom back unrooted. This is the step I followed

3. Go to HBOOT, this is done by shutting down your phone and powering on the device while holding the Power button down and pushing Volume down at the same time, once HBOOT is loaded do a wipe (Clear Storage). You can navigate the menus by using the volume rocker and the Power button to select your option.

xdaforums.com/showthread.php?p=7818278 is the link to the tut I was following.

I dunno how it worked but it did, I got my stock TELUS Rom by doing this. Maybe I got lucky and maybe you might too. Oh and just for your info, the tut I used to root my desire initially was this one xdaforums.com/showthread.php?t=750888. Good luck
[Desire Q&A, Help & Troubleshooting] humaders99:
My guess is that the reason this worked is cuz the way I rooted it kept a backup somewhere internal on the device or maybe the telus desires already have a built in backup or something
[Desire Q&A, Help & Troubleshooting] -Mr. X-:
Well the telus rom does have a back up app in it for your sms email and settings, However i suspect i probably forgot to add the format and wipe commands to the update script as i banged that together pretty quick, ill investigate and re-upload some time today. In the mean time you did the right thing and initiated a wipe manually.

Users downgrading back to stock should also reinstalling the stock telus radio as well.
[Desire Q&A, Help & Troubleshooting] humaders99:
So how do you think I was able to get the stock Rom back? It had everything back to when I just got the phone. When I started the phone again it took me through the initial setup and everything as if I just got the phone. Was it your Rom that was loaded on my phone? Just curious cuz I had no idea what I was doing lol
[Desire Q&A, Help & Troubleshooting] -Mr. X-:
you must have loaded the telus stock eclair build i did.
[Desire Q&A, Help & Troubleshooting] humaders99:
Thank you very much! I was so relieved to get thing back to the unrooted stock telus Rom. Now I can make use of my warranty :)
[Desire Q&A, Help & Troubleshooting] -Mr. X-:
well better hope they dont check for a custom recovery, and also flash the telus radio back to it

found here http://www.mightyrom.com/mrx/MRX/Bravo/Radio/Signed/32.41.00.32U_4.08.00.09.zip
[Desire Q&A, Help & Troubleshooting] humaders99:
This is going to be a noob question but how would they know its a custom recovery? Is there any info on my phone that can indicate that? and also how would one flash the telus radio on an unrooted phone such as mine?
[Desire Q&A, Help & Troubleshooting] -Mr. X-:
if you power on the device holding Vol down it will boot to HBoot, from there choose recovery and i bet you still have the custom recover installed

you can also install that radio from there.
[Desire Q&A, Help & Troubleshooting] fwers:
how do i load this ? at the moment i have od 3.6.0.. wanna go back to stock for warranty purposes
[Desire Q&A, Help & Troubleshooting] humaders99:
Hey so I tried going into the recovery and it would just stay at the white screen that had HTC written in green and didn't change. I did this 3 times and same result. Do you know what this means?
[Desire Q&A, Help & Troubleshooting] -Mr. X-:
yah it freezes some times a trick i use to stop this is to keep tapping vol down after u choose recovery.
[Desire Q&A, Help & Troubleshooting] humaders99:
Your little trick worked beautifully

So i was able to get into the ClockworkMod Recovery so i guess that means that the custom recovery is still there? when i went into some of the things this is what came up if it means anything at all

When i go to "apply sdcard:update.zip" i get a bunch of "no"'s and one "yes - Install /sdcard/update.zip

when i go to "install zip from sdcard" then "choose zip from sdcard" i get the following options:

- Android/

- DCIM/

- LOST.DIR/

-TitaniumBackup/

- backup/

- clockworkmod/

- download/

- rosie_scroll/

- rssreader/

So i guess because of this custom recovery thing it can void my warranty? know of any solutions? You seem like you know your stuff and sorry for bugging you so much, i just really wanna figure this out asap
[Desire Q&A, Help & Troubleshooting] -Mr. X-:
put the radio zip on the sd card then u can choose to flash it.

as for the recovery i don't think there is a way to go back
[Desire Q&A, Help & Troubleshooting] humaders99:
I suppose I'll just have to wait for a telus RUU to come out?
[Desire Q&A, Help & Troubleshooting] -Mr. X-:
don't hold your breath, telus ruu are about as illusive as bigfoot. unless we see froyo update.
[Desire Q&A, Help & Troubleshooting] humaders99:
I suppose a froyo update is all i can hope for. Thanks for all your help!
[Desire Q&A, Help & Troubleshooting] dr_pepper:
Try returning it - what do you have to lose. Either they say you've voided your warranty and they give you your phone back or they accept it and refund or give you a new one. I doubt Telus keeps a database of phones that are rooted and therefore warranties voided. Meaning if they don't take it back and if a some point down the road Telus releases Froyo - try then.
[Desire Q&A, Help & Troubleshooting] humaders99:
Good point, I'll give it a try
[Desire Q&A, Help & Troubleshooting] canadacam39:
If you've still got a problem, just take it in. They really don't give a damn.

My SD card was messed up (asking for PUK code). I tried calling them, but I only got a machine :mad:

I decided to go in then, and they checked it out. The dude didn't even know. I was running a vanilla rom too (Cyanogen 7 Nightlies) :p

He did notice the lockscreen, so I just gave him the excuse "I adb-pulled all of the HTC stuff". Judging by the look on his face, he didn't even know what adb is.

Just take it in, they won't care.
[Legend Android Development] TheGrammarFreak:
In some of the ROM's I've seen here the lockscreen is transparent, but in the ROM I use it's not, and I should like to know how to make it transparent.

If this would involve downloading source code, changing it and recompiling it, just let me know and I'll forget about it for now, but if it's something that a relative beginner might be able to accomplish then any pointers would be appreciated.
[Legend Android Development] TheGrammarFreak:
Well, I'll give it a shot, and let y'all know. We'll see what happens. I assume it's a boot into recovery and then use ADB pull to get the apk? And then push it back when when I've finished?

EDIT:

Well, I've pulled the APK, edited the file and am now backing up my phone before I push it back. I hope this works...

EDIT 2:

Well, I tried, and failed. It got stuck in a bootloop... I just pushed the original framework-res.apk back to get back to a working system.
[Legend Android Development] lyka:
Read your logcat, it will give you advices on what's wrong.

Did you signed framework-res.apk with fakesign?

You could try to make a small update.zip and flash it instad of pushing.
[Legend Android Development] TheGrammarFreak:
Ok, well I'll look at into logcat.

I didn't know I had to sign it, I'll do that too. <-- How? A Google search yielded little,unless I was looking for the wrong thing

And I'll look into update.zip's later. Thanks for all your help.

EDIT:

Well, I had a go with logcat, and none of it means anything to me. I'll keep trying though. I may have filtered the wrong things. The thing is I'm not quite sure what I'm looking for. Oh well, I'll get there eventually. Doing this makes me realise how great ROM developers are...

Thanks again for your help with this
[Legend Android Development] TheGrammarFreak:
I've been trying hard with no luck. :(

The ROM I'm using is Azure (0.5), if anyone has any ideas on how to go about making the lockscreen I would be grateful for the help.

Cheers.
[Legend Android Development] Quanny2000:
You can't push files to the system partition, we don't quite have access to it yet.... your best bet is to create an update zip and clockwork it in as mentioned above....
[Legend Android Development] TheGrammarFreak:
Well, I do it with my phone in clockworkMOD recovery, with /system mounted, and it seems to work fine...
[Legend Android Development] r3ptil3:
where 2 find non-transparent screen lock

im pretty new to all this and am not that technical, so please bear with me

i have successfully rooted my legend and have installed custom rom speedlegend v.06

it comes with a lockscreen which is transparent.

i dont like the transparency and was wondering if you could point me in the direction of the link where i can find the lockscreen w/o a transparency?

id be happy with juz a black background with the clock and unlock and silent buttons

im not confident enough with coding or messing with coding to try and manually edit it

on a side note, do you think there would be any way to change the sliding "sound off" tab to make it enter vibration mode rather than no ring at all?

thanks in advance!
[Legend Android Development] TheGrammarFreak:
Well, if you follow the instruction up there ^ and set it all to #00000000 you'll get a black background.

I was about as noob as you when I tried to do it first (it was about my 3rd post), it's easy. You'll be fine.
[EVO 4G Android Development] kf2m:
Apparently a number of folks lost their 4G keys. Kinda sucks when you are in a 4G market, and cannot take advantage since your 4G keys are hosed. Redsolar came up with a process for moving/editing your 4G key to a hobbled phone.

Further reading..

http://xdaforums.com/showthread.php?t=716694

Some discussion made that once a phone is sent into either Sprint or Insurance for replacement the 4G keywould be rendered useless by Sprint. In a way I doubt that. It would be more prudent to invalidate the MAC address than the key. Since Wimax keys are generally used to en/decrypt the data. I believe that authentication fails because the network handshake is encrypted. But the initial connection is granted via the MAC address, then validation via the encrypted handshake. It would be easier to invalidate a MAC address than it is to do that with using the actual key (MAC=96 bits vs RAS key=2048). Hence smaller/faster hash table.

What I propose is that someone who has a rooted Evo that has either "lost", or severely damaged (but still accessable via USB by fastboot) their phone that will be going back to Insurance to pull their 4G key by redsolar's process. I in turn will hexedit the key to reflect my MAC address, load it on my borked phone, and see if once Sprint deactivates the phone donor if I would still have 4G. At that point we will know if Sprint is using the MAC address, or the actual key to allow/deny access to Wimax.

The thing is if it works it will have to be one donor key, to one borked phone. Redsolar already proved that two keys operating at the same time will not work. Maybe a repository? We have alot to gain and nothing to lose.

Anyone up for this?

Discuss.
[EVO 4G Android Development] SteelH:
I have a smashed evo that still can be accessed via ADB, even better, I never used 4G on it because at the time there was no 4G here. I am not sure about fastboot access at this time, but as I said ADB worked so I figure fastboot prolly does too. I work 48 hours this week, so not sure when I could try it.
[EVO 4G Android Development] kf2m:
Awesome. If adb works so will fastboot, you just have to boot into bootloader.

Thanks!
[EVO 4G Android Development] SteelH:
That's easy enough then. I'll have to charge up a battery and go read that other post, unless you want to p[aste the commands I need to do in here.
[EVO 4G Android Development] kf2m:
Here you go!

1. Open command line window (cmd)

2. Make sure you have no PC36IMG.zip files in the root of your SD Card, or it will take a while to power your phone up

3. Power down your phone

4. Power it up while holding down the Volume Down key

5. HBOOT will attempt to scan for PC36IMG files. Let's hope you read carefully and don't have it on your SD Card root

6. Once HBOOT fails to find the file, use Vol Up/Down buttons to go into Fastboot mode

7. Connect the USB cable to your phone (and PC). You may have to install the USB drivers that come with Android SDK, but chances are if you are looking for this solution, you already have them installed and working

8. The FASTBOOT mode will switch to FASTBOOT USB (that's good)

9. Test your fastboot by typing "fastboot oem h" in command window you opened earlier (note, no adb, or adb shell anywhere, the command is "fastboot oem h". From here on all fastboot commands are issued in that window

10. If you see less than ~40 lines of output, you don't have a propertly rooted phone, and you need to do step 1 and step 2 (see above)

11. Dump your wimax data by issuing "fastboot oem saveprt2sd wimax -n wimax.bin" command (varies, anywhere between 7 to 8.5 MB, mine was 7MB)

12. Dump complete partition (~12MB) by issuing "fastboot oem saveprt2sd wimax -n wimax.bin -a" command

13. Reboot your phone

14. Pull the data files you dumped to a safe place ("adb pull /sdcard/WIMAX.BIN" and "adb pull /sdcard/WIMAXRAW.BIN"). Note the capitalization, it's important

PM me when you do it. I'll set up an account on my FTP box for you so you can upload it.
[EVO 4G Android Development] redsolar:
One major flaw to this attempt

0. The public/private keypair contains your phone's MAC address as part of your certificate's Common Name (CN), which is also most likely validated against the current mac on your phone

1 (corollary of 0). The phone must be an "activated and in service" phone for this to work. So if someone is keeping their broken paperweight and paying sprint the monthly fee for it - sure, this will work

2 (corollary of 1). Using a pair of keys from a deactivated phone will not allow you 4G access, sorry :(.

If through some miracle of Sprint's negligence the above is not true, I will tip my hat off to you :)

The negligence would mean that they are not checking anything but whether your public key is signed by HTC, and are happy with the actual MAC address that your phone provides them during authentication. That would be a major major flaw, since MAC address is so easy to change in fastboot.
[EVO 4G Android Development] AssassinsLament:
If you read redsolar's thread, you'll see that I've tried this. It's worth it to try again, but for reference purposes, I have tried and failed.

Here's what I've tried:

I've cloned a friend's wimax certs, changed the mac to mine. It worked. Downfall, is that only one of us can be on 4G at a time. (There doesn't seem to be any checking of mac address vs wimax cert)

I actually purchased someone's wimax certs from a phone that is no longer in service, and changed the mac to mine. Didn't work. Flashed back my friend's certs, worked.

Conclusion, the certs are most likely blacklisted if the phone is not in service.
[EVO 4G Android Development] quietpopcorn:
Just curious as I no longer live in a 4G area. What causes this "hosing of keys"?
[EVO 4G Android Development] redsolar:
Most of us who lost it did it through a botched wimax update. It's believed to have originally been released by revoked and circulated for a while during the last Eclair update for evo (1.47)

When wimax was initially a pain to flash. It used a write_raw_image command which overwrote wimax partition and in most cases did so over the unrecoverable SSL key pair.
[EVO 4G Android Development] kf2m:
Hmmm.. I would be using my valid MAC address. Usually it is the MAC since like IP's only one can exist on a network. Though it is quite probable that Sprint's implementation of Wimax does do a key hash. From the original spec of Wimax, the MAC authentication is done first at connection, then an encrypted handshake follows. The only way to see that is by using a Service Monitor, and watch the transaction. But you can't see what happens after the encryption starts (but you can watch what goes on before and after). HTC can't recreate your Wimax keys because Verisign's algorithm uses a random seed generator. So even if you where to get the keys from both the proceeding, and post MAC addresses to do a compare the RSG would be different on all three keys. Verisign made it easy for makers of electronics that use key encryption, it's just a simple web interface that in the case of cellphone the engineer plugs in a starting MAC address, and the number of keys to produce, and the computer just spits them out to the flash table.

I'm still willing to try. Can't screw up my Wimax anymore than what it is.
[EVO 4G Android Development] wsantiagow:
Very interesting. I lost mine on 1.47.651. Never used Unrevoke. Thats besides the point. I have a question which I'm sure I have asked before, but just want to make sure that the info I received was accurate.

I have backed up my Wimax partions (I have a wimax.bin that is around 8MB and another wimax.bin that is 12MB). If I ever lost or hosed my wimax, could I just push this partition backup onto the phone and I should get my wimax up and running again?

Thanks for any info! :)
[EVO 4G Android Development] kf2m:
If you followed redsolar's procedure, yes.
[EVO 4G Android Development] bigbiff:
I would guess they are using a CRL (Certificate Revoked List) that is probably added once you deactivate the phone. I really hate that they didn't store the certs in a cert8.db and key3.db file on /system or something... :mad:
[myTouch 3G Slide Q&A, Help & Troubleshooting] SCossio:
Team, I have successfully rooted my slide. Im using the original stock ROM

Im using the following:

Firmware Version: 2.1 -update1

Kernel Version: 2.6.29 - 5f8ed145

htc-kernel@and 18-2 #1

Build Number: 1.18.531.1 CL164069 test-keys

Now for some reason im running out of internal ROM space to install apps. (I am down to 14 mb) When I go to my t-mobile app and choose "My Device" it tells me the internal memory is like 145mb and that I have used up most of it

I know this phone with OTA was suppose to have like double the ROM.

What can I do to double it or unlock the additional internal ROM

Any one who can guide me to a forum or Wiki on "How to" would be great

Any one who wants to share additional steps would be also great.

please be advised that i did attempt to use the new Cyanogenmod and even with that ROM installed I still only have 145mb app space.

any tips and tricks would be great as well

Thanks to everyone who helps.
[myTouch 3G Slide Q&A, Help & Troubleshooting] r0man:
[Q] = question

questions go where?

Development?

Seems logical.

check my dub rom bro
[myTouch 3G Slide Q&A, Help & Troubleshooting] Ace42:
The phone is setup like this(512 Total)

/Cache(~80MB)

/System(~240)

/Data(~145)

Total-465MB

I dont know where the remaining space is at.
[myTouch 3G Slide Q&A, Help & Troubleshooting] r0man:
/tmp

/misc

/boot

:P
[myTouch 3G Slide Q&A, Help & Troubleshooting] Ace42:
thanks, only knew 3

Maybe a dev can figure out how to make--> http://xdaforums.com/showthread.php?t=717874

that compat with the slide, rooted phones dont need the dumb /cache.
[myTouch 3G Slide Q&A, Help & Troubleshooting] turboyo:
Look up my thread on moving dalvik to cache partition will free up a good amount of mbs
[myTouch 3G Slide Q&A, Help & Troubleshooting] SCossio:
Okay....so at this point if I wanted to do apps2sd how can I do that?? How can I do it without having to install cyanogen mod....can anyone direct me to the correct forum??
[myTouch 3G Slide Q&A, Help & Troubleshooting] bhilgeman:
Here is a link to the newest rooted OTA. It is 100% stock Slide Espresso rooted with apps2sd (ext style)

If you want apps2sd to free up some space you need to partition your sd card to have a ext partition on it. Then just flash ROM I linked you to. It will automagically wipe your phone during install so as always make sure you do a nandroid backup.

Here is a link to the thread where you can find everything you need to know about this ROM. I do not recommend flashing the add-on pack. There are a few things broken in it.

http://xdaforums.com/showthread.php?t=747002
[myTouch 3G Slide Q&A, Help & Troubleshooting] SCossio:
Awesome....I downloaded the ROM and updated to it, but still not getting the A2SD

I even tried to use "Rom Manager" to partition the memory card but its not working. It just wipes everything and it reboots on the part that says "partitioning SD..." but after the reboot nothing happens....so my question is....Once i have installed the ROM...what do I do now to get the A2SD?....whats the first step? and what Ext number is it? Ext 2 or Ext 3?

please shine some light, thanks
[myTouch 3G Slide Q&A, Help & Troubleshooting] bmfc187:
You need to get the ubuntu live CD and partition your sdcard from there...google ubuntu and download the latest ubuntu desktop image, burn it to a cd and then reboot, boot into the ubuntu disk and go to system/administration/gparted and partition your sdcard...ext3 is best...

Then on your slide:

go into a terminal and type su then hit enter. Then type

chka2sd

And hit enter. It'll tell you whether or not your apps are on sd and give you some options. The one you need to do is

a2sd install

You can also type

a2sd help

For a list of other commands like moving dalvik-cache to sd, etc.

-BMFC
[myTouch 3G Slide Q&A, Help & Troubleshooting] ratchetrizzo:
he also needs to move the dalvik-cache to the ext partition.

it's all in that thread for the rom.

Once you get it setup properly, it works really well. I have 141 apps installed and I have 101MB free still.
[Captivate General] JacenSolo2001:
Did something to my captivate, when it starts and gets to the desktop, it stops force closing the launch and android accore something. I have no way of getting to anything, settings or otherwise.

I'm able to get it into recovery mode, but if i run reinstall packages it says it can't open /sdcard/update.zip.

I can connect to adb and see the device, but i can't seem to push the update.zip to it. I also have a $ i thought it should be a #.

Any ideas on how to proceed, no way to get into anything on the phone, and adb is acting odd. It shows:

List of devices attached

I89789fda6da	recovery
[Captivate General] dewt:
If an aftermarket launcher is your problem, use adb uninstall to get rid of it or any other apk that is causing problems.
[Captivate General] JacenSolo2001:
its the actual launcher thats erroring out - I can't even figure out how to get adb to let me browse the files on the phone. I have the update file that will resolve the issue, but no way to get it to the internal sdcard
[Captivate General] asrrin29:
in order to push files I think you need root. if you've rooted your phone, use the su command to get the # prompt, which is super user status.
[Captivate General] JacenSolo2001:
ok, here's where I'm at:

Android system recovery screen, with the 4 options, reboot, reinstall packages (which can't find the zip file), and the 2 deletes. This is the only place i can use adb at from here:

I do an adb devices and get

List of devices attached

I89789fda6da	recovery

So at this point, is there a way anyone knows of to get the zip file to the internal sdcard?

oh and btw: the phone is rooted
[Captivate General] dewt:
Do you have busybox on the phone? If you do, do this:

adb shell
cd /sdcard/
busybox wget <url to update.zip>
[Captivate General] JacenSolo2001:
i don't think busybox is on there any longer, it just says busybox: not found
[Captivate General] sborodin:
I don't get it: what wget will get? Are you saying I need a web-server on my windows laptop?

Please be more specific: update.zip sits on my D:\tmp. How wget will see it?

Example please
[Captivate General] alphadog00:
If you can get into recovery mode, have you tried a master clear? If you can't copy files via ADB and you can't use any apps on your phone, then that is your only choice. Or an Odin one click restore to stock.