Database Users

cant restore phone with ruu 1.29

it gets to writing signiture and says it cant update this rom. is there a newer ruu from sprint. it used to work till i got my replacement phone in.

I had same issue..
what I did was (and this only worked cuz I had this already done) Rooted the phone with RA 1.5.2 recovery and flashed Fresh 1.0
once I got it to successfully load into fresh.. then I ran the RUU 1.29 and it worked..

still cant get it to let me un root it. it says that it is the wrong rom to do it. is there a new ruu

Have you tried flashing while in quick boot?

sorry to be such a newb. but what is quick boot and how do i get to it

Power your phone off. Hold the volume down button and power it on. You will get a menu and one of the options is quick boot (I think it's volume up but I'm not positive).
With it hooked up to your computer, check device manager in windows and make sure you don't have any missing phone drivers. If you don't then run the RUU.

ok trying that now. and no errors with drivers

still doesnt work as soon as it gets to updating signature it stops. i dont get it. i have done it a million times with no problems. now it wont work

do you have "usb debugging" turn OFF?

I can confirm testing it with debugging off it still doesn't work. I've tried a million times as well, same problem. I'm not sure if we have to flash the stock rom image before doing so, but in flashrec it only gives me the option of backing up image before actually flashing one and I get an error "Backup Failed: Could not run command" not sure if that has anything to do with it

RUU 1.29 CDMA Sprint
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.

mulcahyd said:
Here's how I got it to work. I reflashed mine couple weeks ago with stock sprint rom (orginal factory state). You need to have HTC sync connected first. Once you establish connection than run RUU 1.29. The hero will drp connection than automatically re-install drivers than it will continue to load the original rom from sprint.
Click to expand...
Click to collapse
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.

flipzmode said:
I was working with someone who was having an issue flashing the RUU (failing at checking license). I took him in to fastboot and we literally tried manually running the restore step by step. Basically what the RUU does but manually. And it would still fail at the license. It wasn't a driver issue.
But your fix will work for people whose RUU says it can't find the phone after it reboots it.
Click to expand...
Click to collapse
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...

obannvi said:
So how do we get it to work? I get the same error, unfortunately. I was thinking about trying your hero ruu update that you put out...
Click to expand...
Click to collapse
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?

flipzmode said:
The one on ppcgeeks? Heh I need to pull that. I used it earlier and found that after using it I had no access to the /data folder. Not huge deal if you are using it to take your phone back to Sprint or something, but no good if you are wanting to use it. I need to fix the script but am swamped right now.
What's your reason for wanting to RUU? Is your phone "with google" branded?
Click to expand...
Click to collapse
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...

obannvi said:
I have the "With Google" branding. I wanted too revert back and get it swapped out. I also wanted to reflash Fresh to it...
Click to expand...
Click to collapse
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.

flipzmode said:
So of the people that have been having the issue where it fails at the licensing issue and gives you: Error[140]: Bootloader Version Error, all the ones I've talked to (only a couple of you) have had "with google" phones. Although all have said that they were able to RUU before and can't anymore.
If you strictly want to return to stock so that you can return the phone then I can help you. PM me.
Click to expand...
Click to collapse
I just dont understand why its sluggish. It was never sluggish before. I figure by reverting back to stock and then re-freshing it, it should be ok.

You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.

flipzmode said:
You can try just clearing your cache (my app installer in my sig can help you do that) and then flashing fresh on top of itself to see if that helps the speed issue.
Click to expand...
Click to collapse
I'll give it a shot. I do have a nand backup of my original install before I installed Fresh...I did that prior and then I installed Fresh again...

Didnt work, still sluggish. I did a wipe through the recovery menu so we'll see what happens.

Why "no signature" with official ROM?

Hi, Sorry to start a new thread but I have a specific Android 2.1-invoked difficulty. (I think. Indeed, I hope.)
This is my phone. I can give the serial number if it helps anyone.
hero cvt ship s-on
hboot-1.76.007 (hero10000)
m1crop-010f
touch panel-syn0104
radio-6.35.06.18
Aug 4 2009, 19:43:30
My Hero is completely unmolested. Just a Hero supplied by my subcontracted Vodafone supplier. I have done nothing to it except load apps. It is not rooted. I think. Until yesterday, I did not know what "rooted" meant. Well, not in this context, and unless you are Australian you will not get that joke.
So I got the OTA ROM notice to upgrade - supposedly the prep part of Android 2.1. I accepted it and it all went fine. No problem - all done. Rebooted and running 2.73.405.5...
Nothing happened for a fortnight until Sunday evening when the second OTA part came through. I accepted. It downloaded, the 75% wait thing happened, it rebooted... It stopped at the famous triangle warning screen. I waited, waited, waited, went to bed and got up. "Hero" it said - it is hung at the Hero screen. I rebooted a few times. Nothing. Stuck. Took the battery out for a few hours, took the SDcard out, swapped SDcard, took out the SIMcard, put them back. Nothing. Hung at Hero screen. So I read a few websites = "Reflash the ROM, you fool". OK, how do I do that? And so I found the two boot methods...
Rebooting with VOL DOWN works - ie it is available but does nothing. FASTBOOT can be seen but does nothing. RESET DEVICE does nothing. HBOOT fails and says no image. USB connection is found by Windows - it appears as a device in Control Panel but reflashing the RUU.exe from the HTC website gets error 170. No connection. Hsync is loaded, says not connected. Obviously I cannor mount it. So I extracted the rom.zip from the official RUU and did the HOME+POWER Android System Recovery sdcard and update.zip malarkey. It found the zip but says "No signature". Now, this is the official HTC ROM from the website, matched to my serial number - extracted from the EXE because the EXE won't work because it won't connect - and it says no signature. I thought that that was impossible. Reading about, I think that that happens when trying to put strange ROMs onto unrooted phones. And I have no idea how to even begin doing stuff like that even if I had an interest in it.
And so I have stopped before I turn the bloody thing into a paperweight. If it is not already one such.
BTW it is under warranty. Should I just send the damn thing back to HTC?
One other message I do not understand is that when I load the system recovery, the first thing that comes up (in yellow, under the blue menu choices) is "E:can't open /cache/recovery/command". I have no idea what that means but it may mean something to somebody. There are no directories like that on the SDcard so I guess that it is referring to the internal memory.
I have tried to give as much info as I can but I am not an Android freak. I am though pretty IT savvy and at a loss to understand what has happened. I think that my phone may be branded to somewhere I do not understand but that does not explain why the official ROM has a signature issue. Or am I just a dim noobie?
Any and all help will be gratefully and humbly accepted. Thanks. Great phone BTW.

And another thing...
I did have a thought that maybe the signature part of the gig resided in a part of the RUU that isn't in the ROM.ZIP and that maybe that is why it is failing. Alas, I have no idea if that is the case or not. If it is the case, I will need advice as to how to make the phone connect to the USB so that I can use the RUU.EXE - which screen would be best etc.
Thanks again.

Are you on Windows 7? If so you may want to find an xp machine as I know people with Windows 7 including me have problems. I use a Windows XP virtual machine.

Good idea
Good idea, Andrew. Thanks. I'll report back.

menelaus said:
Good idea, Andrew. Thanks. I'll report back.
Click to expand...
Click to collapse
It will work, remember to install the HTC SYNC application and enable debugging on the phone. Good luck.
P.S I like your terminology "My Hero is completely unmolested. " lol...

Excellent!
Windows 7 it was, Andrew, thank-you. You are a Genioid. Although I have never had a problem before.
Now, shall I try updating to 2.1 again before restoring all my stuff.... Yes!
Thanks again. Much appreciated.

menelaus said:
Windows 7 it was, Andrew, thank-you. You are a Genioid. Although I have never had a problem before.
Now, shall I try updating to 2.1 again before restoring all my stuff.... Yes!
Thanks again. Much appreciated.
Click to expand...
Click to collapse
Good luck...

Or not.
andrewb84uk said:
Good luck...
Click to expand...
Click to collapse
Well, that was fun. Update failed again with...
can't chown/mod system/xbin
It seems that this is related to having an old SPL. That is all very boring and technical. I am back to my trusty RUU and will wait for a month or two before trying the update again. I have a living to earn.
Thanks for your help, Andrew.

Stuck at HTC screen, won't boot

Hello All,
I have run into a problem with my Heroc not wanting to boot. Some background:
ROM: CM7
Kernal: Jaybob's recent Kernal
Mods: Firerats
All was fine and dandy until yesterday, when I decided to reboot the phone (with a full battery charge). The phone shutoff and when restarted was stuck at the HTC screen. I've tried several times to get into recovery but it hangs at the HTC Screen.
I can enter Fastboot/Hboot. I did some digging and tried to unroot by using this method: http://forum.xda-developers.com/showthread.php?t=988741
Method 1, loading the imaging on the sd root and loading. Everything loaded fine but when I reboot it still hangs at the HTC screen. I have not tried to RUU being that I am on a Mac and don't have access to a PC at the moment. So RUU will be done later tonight hopefully, but I don't expect different results.
It seems like I have some messed up memory and its not allowing me to boot. Does anyone know of a fix? I'm not desperate because its time for an upgrade. I just wanted to hold off on using it until January when Sprint holds their press conference, assuming its an Android device. I'd like to see what I could get versus the phones on the market now.
Any help is appreciated, thanks in advance

srkmagnus said:
Hello All,
I have run into a problem with my Heroc not wanting to boot. Some background:
ROM: CM7
Kernal: Jaybob's recent Kernal
Mods: Firerats
All was fine and dandy until yesterday, when I decided to reboot the phone (with a full battery charge). The phone shutoff and when restarted was stuck at the HTC screen. I've tried several times to get into recovery but it hangs at the HTC Screen.
I can enter Fastboot/Hboot. I did some digging and tried to unroot by using this method: http://forum.xda-developers.com/showthread.php?t=988741
Method 1, loading the imaging on the sd root and loading. Everything loaded fine but when I reboot it still hangs at the HTC screen. I have not tried to RUU being that I am on a Mac and don't have access to a PC at the moment. So RUU will be done later tonight hopefully, but I don't expect different results.
It seems like I have some messed up memory and its not allowing me to boot. Does anyone know of a fix? I'm not desperate because its time for an upgrade. I just wanted to hold off on using it until January when Sprint holds their press conference, assuming its an Android device. I'd like to see what I could get versus the phones on the market now.
Any help is appreciated, thanks in advance
Click to expand...
Click to collapse
You definitely need to do an RUU. No way around it. know it sucks starting fresh again but it'll solve all these problems you have. If your s-off you can also do the RUU from Hboot but it's better to do it from PC as I have learned. Good luck man.

thanks a lot! om going to give it a try later tonight when i have access to a pc. Im not so much worried about starting fresh than I am losing the phone and using my upgrade now... I have a curve laying around and started to thing about using that for a while until I see something I like.
i will report back tonight or tomorrow when i am up and running again.

I had the same problem awhile back and it took me forever to get it fixed but I finally got it fixed. Search the forum for " stuck at HTC screen and look for the threads I started for as possible fix. I will try to find it and post the link here.
http://forum.xda-developers.com/showthread.php?t=1305479&page=3
My last post describes how I finally fixed my Hero, but you should read the whole thread.

williams1978 said:
I had the same problem awhile back and it took me forever to get it fixed but I finally got it fixed. Search the forum for " stuck at HTC screen and look for the threads I started for as possible fix. I will try to find it and post the link here.
http://forum.xda-developers.com/showthread.php?t=1305479&page=3
My last post describes how I finally fixed my Hero, but you should read the whole thread.
Click to expand...
Click to collapse
Thanks. I will give it a look.

I read through the thread and it looks like you passed the black htc screen and got to the white one. I can't get passed the black and adb doesn't pick up the phone at this point. I'm still waiting to try the RUU and see if HTC sync picks up the device.
Very resourceful thread and I'll be sure to give all the suggestions a try before giving up.

HTC sync won't pick up the device and I don't think any other option will work since I don't have ADB access. I'm just gonna bite the bullet and look into a replacement.

Ok to verify your phone does boot at least to the bootloader? If so I have a doffeemr approach for you to take
私のEVO 3Dから送信される。

dastin1015 said:
Ok to verify your phone does boot at least to the bootloader? If so I have a doffeemr approach for you to take
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
yeah. I can get into bootloader and fastboot. whatcha got?
I have a new phone on the way. Amazon has ET4G for $79, too good to pass up so I used my upgrade. Ill still be curious to know how I can get the Hero up and running.

srkmagnus said:
yeah. I can get into bootloader and fastboot. whatcha got?
I have a new phone on the way. Amazon has ET4G for $79, too good to pass up so I used my upgrade. Ill still be curious to know how I can get the Hero up and running.
Click to expand...
Click to collapse
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=804692

I used a flashable RUU based off Flipz source and still no luck. I will give your RUU a try later tonight... Thanks

No luck. The phone freezes at the HTC screen and fails to go any further. :-(

srkmagnus said:
No luck. The phone freezes at the HTC screen and fails to go any further. :-(
Click to expand...
Click to collapse
i had same kinda deal from a bad radio flash
if you still have fastboot do
"fastboot erase system -w"
"fastboot oem boot heroc.hboot-1.46.2000.zip"
you may need to rename the file to HBOOT.
if that dose not work unzip the file take the hboot img and place on sdcard and place where your fastboot files are like in android/platform-tools.
this made a deference for me.
then try fastboot flash img hboot.img
this is what i went through here
http://forum.xda-developers.com/showthread.php?t=1086125
good luck if i can help let me know.

Thanks for the help oostah. I haven't been able to get ADB to recognize the device. When I get home I'll try it again and remove the hboot as suggested and give that a try.
Now that ICS is in beta for the Heroc my phone decides to crap out on me and I can't enjoy the hard work put in by the developers. Nonetheless, I am much appreciative of all the support put into the Heroc and have learned a lot from this community
I'll report back tonight with my results.

srkmagnus said:
Thanks for the help oostah. I haven't been able to get ADB to recognize the device. When I get home I'll try it again and remove the hboot as suggested and give that a try.
Now that ICS is in beta for the Heroc my phone decides to crap out on me and I can't enjoy the hard work put in by the developers. Nonetheless, I am much appreciative of all the support put into the Heroc and have learned a lot from this community
I'll report back tonight with my results.
Click to expand...
Click to collapse
you are welcome i have been there before.
your phone may not recognize ADB but it may still take fastboot commands. that was one thing that drove me crazy is that i could fastboot but not adb. let us all know how it goes.

I did "fastboot-mac devices" and got my device to show up, so it registered. however, when I go to erase system I get an error, "remote: not allowed". The same occurred when trying to flash the .zip and img files separately as suggested . At one point the devices started vibrating like crazy and shut off, the led started to blink green. I did get it back into Fastboot, but now it won't turn on.
Thanks for the help though It was already replaced and the new phone should be here tomorrow. I'm just going to miss the Hero since it was my first Android device and I learned a lot in this forum.
Thanks!

srkmagnus said:
I did "fastboot-mac devices" and got my device to show up, so it registered. however, when I go to erase system I get an error, "remote: not allowed". The same occurred when trying to flash the .zip and img files separately as suggested . At one point the devices started vibrating like crazy and shut off, the led started to blink green. I did get it back into Fastboot, but now it won't turn on.
Thanks for the help though It was already replaced and the new phone should be here tomorrow. I'm just going to miss the Hero since it was my first Android device and I learned a lot in this forum.
Thanks!
Click to expand...
Click to collapse
i still have one of my hero's that i let people play with when the come over. it still runs off wifi so they can play games yous gtalk what ever be nice to get it up and running for experience and fun lol now that your not in a have to mode.
do you have a nan back up from a sd card any place like on your pc if so look for your clockworkmod folder look for backups and you should see your backups open one of them you will see
boot
system
data
recovery
sd-ext
cache
they will be img files you can place them on your sd card and fastboot them back to the phone
"fastboot flash img boot.img"
"fastboot flash img system.img"
and so on
or
"fastboot boot img boot.img"
"fastboot boot img system.img"
and so on
or you can let it RIP

good to know. I'll give that a try if I can get it booted. I'm thinking its dead and needs a charge to get back into fastboot. I'd love to get it back up and running as a learning experience more than anything. I wont have time until tomorrow or Thursday . I will report back when I give it a try.

srkmagnus said:
good to know. I'll give that a try if I can get it booted. I'm thinking its dead and needs a charge to get back into fastboot. I'd love to get it back up and running as a learning experience more than anything. I wont have time until tomorrow or Thursday . I will report back when I give it a try.
Click to expand...
Click to collapse
will the charge light come on when plugged in if not there is a trick take a old usb cable cut one end off on the battery there are
= and - becare full connect the red wire to + and black to - tap them down so they dont move. let it set for 2 1/2 hrs should be good to go.

I need Help - Serious Acting up of Phone

I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.

live_free said:
I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.
Click to expand...
Click to collapse
what sbf did you flash? is it att bell etc? need some more info to help you out.

aideneisley3 said:
what sbf did you flash? is it att bell etc? need some more info to help you out.
Click to expand...
Click to collapse
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204

live_free said:
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204
Click to expand...
Click to collapse
STEPS:
1) Have the correct Motorola drivers installed for your PC (i.e. x32-bit or x64-bit).
2) Download RSD Lite (Links above) & install on your PC.
3) Choose a sbf file to download and flash from Motorola Atrix Firmware Super Thread: http://forum.xda-developers.com/showthread.php?t=1125944
If you are currently running firmware 4.5.91, I suggest that you only flash back to this firmware version. Flashing back to a eariler sbf/firmware version may have unintended consequences, the most serious of which is bricking your device.
*Note: U.S. AT&T users should only flash AT&T sbfs, internationl users should only flash their particular sbf versions.
4) Read the above sbf hints, trick, etc. to help prevent RSD Lite problems/errors.
5) Open RSD Lite and load the sbf file that you downloaded.
6) Put your device in RSD Protocol Mode by powering OFF, and upon powering back ON, hold both the power button and the volume UP button. Device should now say "Entering RSD Protocol Mode."
7) Connect your device to your computer via the usb cable, and select your device by clicking/highlighting it in RSD Lite.
8) Select START in RSD Lite and let the sbf flash process fully complete before disconnecting the device from the PC. There will be several reboots and the process make take 5 - 10 minutes to complete a FULL sbf flash.
9) If you have any errors or problems as a question, prefably in the Q&A section.
this is what i have done and worked for me! good luck
i copied this from the noob guide found here http://forum.xda-developers.com/showthread.php?t=1154600

Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.

live_free said:
Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.
Click to expand...
Click to collapse
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!

aideneisley3 said:
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!
Click to expand...
Click to collapse
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.

live_free said:
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.
Click to expand...
Click to collapse
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf

aideneisley3 said:
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
Click to expand...
Click to collapse
Yes. Same exact problem.

live_free said:
Yes. Same exact problem.
Click to expand...
Click to collapse
oh ok well then i'd have to agree with you then maybe it is a hardware problem... sorry i wasn't much help.
it wouldn't hurt as a last ditch effort to use motorola's software update program that you can download from their site it will tell you that there is no update and ask if you want to use it to restore your phone basically it reflashes it...
haha thats all i got. maybe someone else could offer more help.
good luck! =]

live_free said:
I did everything properly and now am in a boot loop, and I've done a battery pull.
Click to expand...
Click to collapse
apparently not.

in his defense replacement phones are refurbished (cough... broken and maybe fixed to like new). motorola gave me a replacement with broken senor so the screen didn't turn off when i was in a call and that was out of the box and when they replaced that one the screen was messed up it had super bright spots all over the screen so it is possible that it is moto's fault.
not saying it is moto's fault but that it is possible lol

[Q] NAND Rom flashing

Don't be decieved by the title.
My problem is that I literally can't seem to figure out what I need to do to flash:
http://forum.xda-developers.com/showthread.php?t=1166948
The Dorimanx rom.
I've downloaded it. but how do I flash it on the phone.
What I don't understand is that my first rom, Dandiest, came with a package, had an installer and everything. Installer.exe, DAF.exe, the things I needed to flash it.
I downloaded the Dorimanx rom, and I couldn't find any of those things there.
Nor could I find a simple explanation on how to get it on, probably because it is assumed you know what you're doing before getting it.
I've read at least half a dozen threads on how to, etc. and I still am absolutely lost. It's just very confusing, even though I have actually read the "first flashing rom" guide thing.
Call me stupid, but I literally just do not understand.

lol, calm down .. and welcome aboard.
There is no reason for us to call you stupid, we were all noobs at a point in time.
And (I'm certain) you did your part of reading and searching.
All what you have to do is follow this tut by me: http://forum.xda-developers.com/showpost.php?p=16528026&postcount=7
But swap step 8 with your ROM (obviously )
Over time, you won't need this.
[Presuming you don't want swap]

Marvlesz said:
lol, calm down .. and welcome aboard.
There is no reason for us to call you stupid, we were all noobs at a point in time.
And (I'm certain) you did your part of reading and searching.
All what you have to do is follow this tut by me: http://forum.xda-developers.com/showpost.php?p=16528026&postcount=7
But swap step 8 with your ROM (obviously )
Over time, you won't need this.
[Presuming you don't want swap]
Click to expand...
Click to collapse
cheers mate, though. Unless I don't have more than 150mb~ left for apps I don't want swap.
As far as I understand, it's an extension for the internal memory? right now i have nearly 1 gig on the Dandiest rom.
Anyways, thank you for your post mate.

Basementnugget said:
cheers mate, though. Unless I don't have more than 150mb~ left for apps I don't want swap.
As far as I understand, it's an extension for the internal memory? right now i have nearly 1 gig on the Dandiest rom.
Anyways, thank you for your post mate.
Click to expand...
Click to collapse
You are welcome, I am glad I was able to help you.
Swap is an (sort of) extension to the RAM, and not to your internal.
After flashing, you'll have more than 150 for apps, yes.

Marvlesz said:
You are welcome, I am glad I was able to help you.
Swap is an (sort of) extension to the RAM, and not to your internal.
After flashing, you'll have more than 150 for apps, yes.
Click to expand...
Click to collapse
Unfortunately the problem now is that the application will not connect to my phone... How do I fix that?
It recognizes USB (Serial -> USB thing) but won't connect.

What's won't connect to what?
In which step are you exactly stuck?
Do you have the required drivers? if not, you can install them by pressing the "Drivers" button on the HD2 Toolkit.

Marvlesz said:
What's won't connect to what?
In which step are you exactly stuck?
Do you have the required drivers? if not, you can install them by pressing the "Drivers" button on the HD2 Toolkit.
Click to expand...
Click to collapse
I didn't install the drivers at that time, no.
Though, when I run the .exe's it just opens a cmd, runs some stuff, then closes. is that right?

Basementnugget said:
I didn't install the drivers at that time, no.
Though, when I run the .exe's it just opens a cmd, runs some stuff, then closes. is that right?
Click to expand...
Click to collapse
Which exe are you alluding to? Within the toolkit? If memory serves most options should bring up another window that you need to go through. Make sure you've started the toolkit as administrator (right click). And if its not connecting properly you may just need to disconnect and reconnect.

HypoTurtle said:
Which exe are you alluding to? Within the toolkit? If memory serves most options should bring up another window that you need to go through. Make sure you've started the toolkit as administrator (right click). And if its not connecting properly you may just need to disconnect and reconnect.
Click to expand...
Click to collapse
Indeed, what .exe? is it the toolkit? if yes, then you must be doing something wrong. Because the toolkit has a GUI, not texted. Make sure you have installed it, and run it as an admin.

Marvlesz said:
Indeed, what .exe? is it the toolkit? if yes, then you must be doing something wrong. Because the toolkit has a GUI, not texted. Make sure you have installed it, and run it as an admin.
Click to expand...
Click to collapse
Not the toolkit, the drivers. You told me to download the drivers.
when I execute both the exe's, All I get is a CMD window, and it closes back down once it runs for approx half a second.
I was asking if that was correct, for installing the drivers.

Basementnugget said:
Not the toolkit, the drivers. You told me to download the drivers.
when I execute both the exe's, All I get is a CMD window, and it closes back down once it runs for approx half a second.
I was asking if that was correct, for installing the drivers.
Click to expand...
Click to collapse
I think that's allright.
To check if drivers are already there - enter bootloader mode (power + VolDown) and after that plug it via USB to your PC. If you hear sound of connecting device, i say its ok.
You won't have access to data on your phone, it won't show as a removable disc. In my case "My devices" shows my phone as "Qualcomm CDMA Technologies MSM". So if you hear that sound, just go to another step, to MAGLDR install. It should work.
I use this ROM myself, and its awesome. Hope this helps

Marquo said:
I think that's allright.
To check if drivers are already there - enter bootloader mode (power + VolDown) and after that plug it via USB to your PC. If you hear sound of connecting device, i say its ok.
You won't have access to data on your phone, it won't show as a removable disc. In my case "My devices" shows my phone as "Qualcomm CDMA Technologies MSM". So if you hear that sound, just go to another step, to MAGLDR install. It should work.
I use this ROM myself, and its awesome. Hope this helps
Click to expand...
Click to collapse
power + voldown gets me into the red/green/blue screen. Surely that isn't the bootloader.
Right now It won't connect anyway though.
EDIT:
I reconnected it into a diff port, now windows auto installed some HTC USB connect stuff. now it does recognize it. This was the required stuff?

Basementnugget said:
power + voldown gets me into the red/green/blue screen. Surely that isn't the bootloader.
Right now It won't connect anyway though.
EDIT:
I reconnected it into a diff port, now windows auto installed some HTC USB connect stuff. now it does recognize it. This was the required stuff?
Click to expand...
Click to collapse
That IS what we call a bootloader mode. I think it is what was needed. Now proceed with next steps and enjoy new rom

Marquo said:
That IS what we call a bootloader mode. I think it is what was needed. Now proceed with next steps and enjoy new rom
Click to expand...
Click to collapse
Cheers mate. it flashed, running for about an hour now. All my aps back on it. and dear jesus it is fast compared to the other rom I had. this is fantastic.

Basementnugget said:
Cheers mate. it flashed, running for about an hour now. All my aps back on it. and dear jesus it is fast compared to the other rom I had. this is fantastic.
Click to expand...
Click to collapse
Glad You like it. Remember that it is still developed, what means that some problems may, and probably will ocurr. If so, report at ROM thread(i see that you achieved 10-post level ). With my set, i haven't had any problems, i think im gonna wait with upgrade
Cheers

Marquo said:
Glad You like it. Remember that it is still developed, what means that some problems may, and probably will ocurr. If so, report at ROM thread(i see that you achieved 10-post level ). With my set, i haven't had any problems, i think im gonna wait with upgrade
Cheers
Click to expand...
Click to collapse
As far as I know i'm using the very latest ROM. And haven't had any problems so far. It's absolutely lightning fast. even though I have no idea if I did it right with the memory selecting stuff. I just did the 150+5mb. And suppose that is correct.
But yeah, zero problems. lightspeed. so im absolutely pleased. But I suppose if your rom is working fine.
Never change something that is working correctly.