Related
I rooted my desire using the guide here:
http://nimbu.amorvi.com/2010/05/how-to-root-your-htc-desire/
i can tell it sucessfully works because i get the superuser app in my launcher.
I want to put this rom in my phone until R3 of the modaco rom is pre-baked.
http://forum.xda-developers.com/showthread.php?t=674688
although i am a bit confused, how do i get my phone into recovery and do i have to partition my memory card before i load the rom on, i didnt make my memory card a goldcard has my phone is generic.
Can anyone advise me?
Thanks for your help.
When you rooted, you had to put your phone into recovery by holding the volume down button while powering on, then run step 2 in the root process. just do this again to get to the green recovery menu.
Do be careful though, as a lot of people are posting with issues that have caused their handsets to be semi-bricked. Personally, unless you need to re-root, or root at all, I'd wait untill there is a fix for the other problem.
Ok thanks.
For the custom rom, do i have to do anything to the memory card or can i just install it straight away? im not too fussed about A2SD to be honest.
sonandreas said:
Ok thanks.
For the custom rom, do i have to do anything to the memory card or can i just install it straight away? im not too fussed about A2SD to be honest.
Click to expand...
Click to collapse
If you don't want A2SD then don't bother putting an ext partition on your card. Your custom rom thread should tell you if you need to wipe etc.
Ok thanks ive been reading about A2SD but id rather wait for it to be natively included by Google so not bothered about it.
Do i have to partition it or can i just go ahead and just flash the custom rom on my phone without worrying.
Sorry about the questions, just want to make sure its good to go
I flashed an A2SD rom without partitioning my SD card and it was fine. It worked perfectly.
As I said above though, be really careful unless you want to join the semi-bricked club that currently have desires that have no USB/Blutooth/and FM radio. If this happens you will be fairly stuffed untill a fix is released. That fix looks like it may be a fair bit away yet though!
I was a member of the club, but managed to blag a new phone by acting stupid in the shop!
Just wondering, what are the risks? I mean, other than voiding your guarantee.
Is it possible to use SD for everything, and only have android boot when the SD card is in.
Oh, and if there is 0-1% risk and it is possible to use SD (even if it will still show the duel boot loader even when SD card is out), I would please like a step by step guide to duel booting it. Everywhere I look is a "Install this bootloader here, get this ROM there, now figure it out for yourself."
To minimize risk of my device not coming back, can someone please tell me step by step, EXACTLY how to do everything.
thx for even reading it,
drnessie
This should help...
There is really no risk booting an android version from your SD card using Haret.EXE. There are some risks flashing the ROM to NAND which could leave your phone inoperable or 'bricked'. I have always flashed to NAND and have never had problems but trust me, I spent countless hours, reading and learning from many posters in the forums about how to do it properly. Using the search features in the forums, you will probably find answers and tutorials for booting Android from your SD card and flashing the ROM of your choice to NAND...
Here are a few good starting points:
Ongoing thread which should get you started:
http://forum.xda-developers.com/showthread.php?t=680518
Excellent step by step courtesy of 'Zenity':
http://forum.xda-developers.com/showthread.php?t=760518
Thanks for that!
Where do I find Haret.exe?
Scratch that, found Haret.exe.
Hey all! So, a couple weeks back, I flashed a BETA ICS ROM onto my Inspire (Desire HD). Being my normal ignorant, and noob-like self, I completely ignored the fact that the thread said "DEVS ONLY!"
Well, flash forward a couple of weeks, and my Inspire is all but bricked. The ROM did not have mobile data yet, did not have a connection to the micro-SD card, and it was not touchscreen ready yet. I have tried ADB, but to no-avail, my file system knowledge and overall lack of knowledge put me quite a predicament.
I have flashed many ROMs before, but I sincerely messed up big time on this try. So, would any of you be able to help me find a cure for this important issue? Is the fix really simple and easy, and I am just a bonehead?
Thanks!
Not sure what your issue is. You never clearly stated. Does the phone not boot? Stuck in the splash screen? you want to flash a new rom?
marsdta said:
Not sure what your issue is. You never clearly stated. Does the phone not boot? Stuck in the splash screen? you want to flash a new rom?
Click to expand...
Click to collapse
Oops, sorry! My problem is that my phone is stuck on the developer ROM, and I would like to fix it somehow. So, yes, I would like to get another ROM, but I have to remove this one first. The phone itself works great, but with no wi-fi, mobile data, and no touchscreen support, it is hard to live with.
Your nowhere near bricked. Going to ask the basics. Did you make a backup before hand? Did you have another rom on your SD card.?
If you answered yes to either then simply boot into recovery and flash the rom/ backup. You mentioned flashing roms before so I left out the steps.
If you answered no then you have two options. You can mount the SD card from within cwr. So download a rom on your PC. Mount the sd card, then flash away. Or take out SD card and use an adapter/other phone to transfer a new rom.
I was not smart enough to back up onto a computer, but I did back up onto the SD card. The only problem with this is that the ROM, and my computer, will not recognize that there is in fact an SD card inserted into the phone. So, in other words, it's like not having an SD card at all.
CWR will still read the sd card. Trust me. boot into CWR and restore your backup. And you be good as gold
Thanks! But, what exactly does CWR stand for? Haha, I'm not the most knowledgeable on the topic of Android, but is it like Clock Work Mod?
iTookTheByte said:
Thanks! But, what exactly does CWR stand for? Haha, I'm not the most knowledgeable on the topic of Android, but is it like Clock Work Mod?
Click to expand...
Click to collapse
yeah. CWR stands clockworkmod recovery
Okay, in that case, I'm not sure. All of my old files (CM7, CWM, etc.) were on the SD card, and it is unreachable. I have tried to boot into CWR, but it just gives me a black screen. I feel like this thing is just unable to be fixed!
its fixable. just the black screen in CWR is an obstacle. worst case is you have flash an ruu and start over with the whole rooting. i remember reading about the black screen in CWR give me a few minutes to find them to see what to do next
Okay! Thanks a bunch!
Pull the battery and put back in
Press and hold vol-down
Press power and bootloader will start
Select recovery using vol keys and press power
If you have a backup (you really should, and and if you don't consider this experience a learning one), restore it by selecting the backup / restore option
If no backup, goto mounts and select as storage, plug usb into pc and copy your favorite Rom over, then select back and flash from zip, select the zip and you should all be back up
But please, please I'm all for people learning and experimenting, but might be worth reading some of the basics guides and notes on roms before flashing the next one. Oh, and if I forgot to mention.... Do a backup before flashing ANYTHING saves heartache later, the enjoy
Sent from my HTC Desire HD using XDA App
THANK YOU! I remember this now! Thanks everyone
Your welcome, after all, we all have to learn sometime
Sent from my HTC Desire HD using XDA App
ok i couldn't find the specific thread i was looking for. i remember it being stickied but couldnt find it. did find something that might be usefull but it depends on if you have access to an sd card adapter or other phone to transfer the file needed to reflash CWR. If not i would suggest trying to see if flashing an ruu to help.
edit- I'm confused now. thought you said that when you boot into recovery all you get is a black screen?
So I've done some searching, and have yet to find a solution to the issue I'm having. GF's phone is the HTC Incredible as you can probably already guess by what subforum this is posted in. It's been running the CyanogenMod 7.1.0 Rom for quite some time alright. From everything I've seen, most people that have had issues with bootloops is because they have been flashing to a new rom/radio and skipped something/pulled the battery/or something along those lines. This phone has been running fine, and then out of nowhere I guess, started to restart itself continuously yesterday. I can get into HBOOT no problem, but that's about it. When I try to select Recovery, it just kicks right back into the bootloop. Anyone have any suggestions??? Phone isn't under warranty anymore, and her contract ends in a month and a half, so we don't want to have to buy a new phone before then if at all possible.
try reflashing recovery.
first start with a freshly formatted FAT32 sd card, download this file and place it on it
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
this should be the only file on your SD card. now turn off your phone and put the sd card in. now boot into hboot (vol down+power) and it should prompt you to update by pressing vol up. do this and when it boots back into hboot, remove the sd card and delete the file. then try booting into recovery
Tried it and still no change
there was a similar situation (stangely similar ) here
http://forum.xda-developers.com/showthread.php?t=1628585
both cases happened to be running cm 7 too...and randomly started boot looping and stuck with no recovery.
i would read through that thread and see if any of the steps will help you
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
downwardzspiral said:
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
Click to expand...
Click to collapse
you can try doing the steps in that thread. you may have better luck. Perhaps someone else on this board knows of another method that may help
Just because it didnt work for that guy, dosent mean it wont work for you. Are you s-off? Have you tried reflashing recovery yet?
it's S-Off and I've tried to reflash recovery
How about an ruu?
tried that. tried through the pc and the computer wouldn't recognize it. tried by updating it in HBOOT, and after the update, it would still just bootloop
Sounds like another possible hardware failure. My only other sugestion would be to try the fastboot flash of the misc img, but it probably wont work either. Its very strange, i have seen this 4 or 5 times now in the past couple months, all on cm7, and all unfixable. I dont want to start a war, but mabey something with cm7 or cm7 and a certain program or combination of programs, is causing this. Or mabey its just cause these phones are getting up there in age.
i too find it odd each one is cm7..
Well thanks for all the help anyways. A new phone it is I guess
the basic problem is CM 7 (for the Dinc). it is extremely common. i have seen it happen to so many people now. it drives me insane when i see people suggesting CM 7 "stable" to others (for the Dinc). i have tried to communicate this here and other places too... i have given up hope of people ever accepting this obvious situation. the "stable" version of CM 7 is simply not stable.
however...
a reflash of clockwork recovery has always gotten people out of the CM 7 bootloop. then they are able to get a working rom installed.
i don't understand why you can't get a recovery re-flashed.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
I'm suddenly having storage issues with every ROM that I flash after running a ROM with some script that isn't widely used.
First I'll give you a brief idea of my problem. I"m running out of storage and get notifications from the market saying as much after I download and reasonable amount of apps. The thing is... It show's I have used 738MB of ext4 out of 1.5 so that isn't the issue. The problem is internal memory. My phone won't move dalvik cache for some reason. When I run any ROM with a2sd or m2sd they both say that there is a problem and leave the dalvik cache where it is.
I think my internal folders are jacked up from 40ad2sdx or a zip that was used to clear memory before the ROM. There was a ext4 superwipe cleaner to load before the ROM. I did that without researching first. When I did go looking for the thread about it, it plainly said that it was for one phone only, and it wasn't my phone. I believe it was the Galaxy S3, but I can't be certain. It was a week ago. It was advised not to use it on any other phone because part of what it did was reset the internal folders. Does this mean I can now flash a ROM for the galaxy s3? Lol Just kidding.... Seriously, the second part is all my speculation and I have been wrong many times concerning android. Will somebody help me get my phone back in oem condition please?
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
nate234 said:
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
Click to expand...
Click to collapse
I did the wipe and flash to stock earlier today, then flashed the Pac man ROM but the issue is still there. I had looked at unrooting my phone earlier today also. I'm glad to read this because it lets me know that I do have some idea of what to do. Thanks for the reply. I'll post here again with the results. Check back soon.
EDIT----> Man, my phone is okay. I loaded up a fairly recent ROM by Tronit, and it worked fine. It was the ROMs. Just to be sure, I went back to the last two ROMs just to see, and they did the same thing again. Now I'm on the AOKP Unnoffical and it's working just fine. The a2sd is working perfectly like it should, and my dalvik cache is moving to ext4. It was just coincidental that the last three ROM's I loaded all have issue with the a2sd. It's funny how nobody else see's problems but me. I looked in the bin file of one of them and it's missing part of the a2sd file. The other two have weird init.d files that I don't know anything about. I'm assuming the a2sd problem is related to that. It's funny how I see lots of problems, and report them, but I get blown off by some people as a noob who is making mistakes. I am a noob, and I do make mistakes, but I know some of my theories about problems are correct...... I gotta get me some respect by compiling my own ROMs.
Status update..... My phone is jacked up for sure. It does work with the AOKP Unofficial by Tronit, but this morning when I cleared my cache with Smelkus Recovery, it had major problems with almost every app. Clearing the cache in recovery is something I've done with every ROM and this has never happened. I uninstalled all the apps and reinstalled them. Got them working again. Everything seemed to be okay. However, when I cleared my cache with Android Tuner, again it ruined every app. I've used android tuner every day for two months to clear the cache and never had problems like this. Something is very wrong.
*****edited and deleted for the sake of peace*****
Long story short, I flashed something made for another phone. I can't explain why I did this without taking up lots of pages, and it doesn't even matter really. Lets just focus on the solution. Here is the link. I flashed both of the zips in the link.
http://forum.xda-developers.com/showthread.php?t=1477955
So I think my permissions for the files on my phone are out of whack. Is that what I"m reading is the possible outcome of flashing these if your phone is not the one listed? Please post your thoughts. I need them.
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
g2435 said:
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I did that. Both with Smelkus, and Mini partition wizard. Same problems. I just tried to fix permissions with smelkus 4.3 on the AOKP Unofficial ROM and it took a minute for it to do it's thing. The line of dots was two full rows. So when It loaded back up, I suddenly see the same disk Icon in my notification bar, and now this ROM says it it out of memory. Man, it was working fine. I had twenty more apps on it too and I uninstalled them. It was working fine then, so with twenty less apps, it shouldn't suddenly say "Running out of Storage space."
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
nate234 said:
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
Click to expand...
Click to collapse
I flashed this about a eek ago, when I was looking for the ext4 wipe. I thought it was the same thing as another zip despite what it said. Stupid... I know. I think this may be the cause of my problems, but I can't be sure. I don't know at all really. Just speculations. I reflashed the CWM touch and used to flash a stock ROM. Gonna try that again. I ran the test on CWM touch and it said that the
/sys/class/android_usb/android0 was missing and unable to perform the test. Can this be the cause of my problems?
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
nate234 said:
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
Click to expand...
Click to collapse
I tried loading the Pacman ROM again with CWM and it wouldn't even load. It gets stuck in a bootloop. After that I flashed smelkus and went back to the Stock Rom.
*****edited and deleted for the sake of peace****
RADIO EDIT------
Sent from my PG86100 using xda app-developers app
edited and deleted for the sake of peace
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
I was finally able to get my phone straightened out. I loaded up a stock ROM then decided to use my SD Maid to look around. I found a file with completely different dates on it, but it wouldn't let me remove it. I ended up copying everything else in the subfolder and then deleted the parent folder. Then added everything else back. Wah lah.... magic. I don't know what that file was or where it came from but it was killing my internal memory. I'm wondering how it stayed from ROM to ROM. I dunno, but it's gone, and the Pacman ROM is lovely now. BOOM!!!!
jlmancuso said:
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Whatever I did only fixed part of the issue. I'm left with in a situation where every time I go into recovery my downloaded apps stop working. It is cutting part of them off whether I clear cache or not. All I have to do is power off into recovery, and when I reboot, all of my downloaded apps begin giving messages that "Unfortuately such ans such has stopped." My phone becomes inoperable. The only way I can keep it working is to send a new launcher to my phone from the market, let it install, then open it up and uninstall all the downloaded apps. I'm pretty sure this is an easy fix for someone like you Mancuso. I have a logcat and it show LOTS of errors that I have never seen before on any of my other logcats. What are my options? Tell me what to do to get my phone back to absolute OEM and then I'll reroot. UNLESS you know of some fix.
I've supplied a logcat from Catlog if you or anybody else wants to have a look. I'd really appreciate some help here. I love my Evo and I love learning this stuff. If somebody can help me positively identify the problem, I can most likely figure it out from there. Please give me your suggestions here. I'm nothing without some guidance on this. It's way out of my scope.
I've included a link to the ext4 script wipe that I used. How I got to this page, I do not know. However, I ran it because this page said it COULD POSSIBLY work on other phones despite the fact that it was made for another phone.
http://www.xda-developers.com/android/darkside-super-wipe-easily-wipe-partitions-when-flashing-roms/
And I flashed both zips from the thread that the story links users to. Here is the link for the two zips.
http://forum.xda-developers.com/showthread.php?t=1477955
I'm not sure this is the problem. I'll try to find the Vold.fstat thread that I tried on my own before you came up with the 40ad2sdx solution for the MIUI ROM.
This is the memory fix I tried as mentioned above.
http://forum.xda-developers.com/showthread.php?t=2246909
Please note that you see before and after pics of sd storage. You can see that my pics clearly resemble the after pics shown in this thread. I believe this is my problem. How can I undo this?
This post reflects the only things I did outside of normal flashing. My problem is here somewhere...
The fix you used is for samsung devices. That could have caused your problems.