Hi guys,
I've got a bit of a problem. My phone is stuck in a boot loop, which is a problem I've dealt with before, with help from these threads.
But this time I'm really stuck. I can't access the HBoot screen like I normally can, by holding down the volume up and power off buttons simultaneously.
I am using (racks memory) I think it's the War something mod of Cyanogen 7 I believe. I installed it 5 months ago and it's been working fine. This is not a new or recent install!
The phone does suffer from low memory issues a lot, as do all Wildfire S's. I have managed to get around that previously by moving apps to the SD card or linking to it or making user apps into system apps. I was in the middle of chatting on whatsapp when suddenly the phoned just blipped and died on me.. then it went into the boot loop. It's never happened before and my suspicion is that it ran out of memory or something.
I've tried removing the battery and leaving it out for some time, no luck. I've tried restarting without the SD card and Sim card. No luck. I've tried connecting it to my laptop... no luck. All the usual tricks just aren't working.
I have TiBu installed and my most recent back up was less than 4 weeks ago. I also did a Nandroid system backup a few months ago, so I should be able to restore ok, I just can't access the HBoot screen.
The other weird thing is, when I left the loading screen going round long enough, like in the time it would normally have booted.. suddenly the sound of my new emails popping up plays... and today, even tho it was on the load screen, it made clicking sounds like when I activate apps when my finger touched the screen. It's almost like the phone has started up as normal, but the load screen just won't go away and underneath it all is normal.
I've never had anything quite like this happen before and I've been without my phone for 3 days now, so came here in desperation for some inspiration! hehe.
I am probably going to buy a new HTC phone with a large system memory cos altho I dearly love my Wildfire S, the low memory has caused me nothing but problems since I first bought it, and I have wasted hours and hours on it, trying to get around the problems caused by it. But until then, I need to get my contacts and messages back and continue to use it for now. I would also ideally like to keep it going and give it to my sister perhaps who doesn't have a smart phone. She won't need as many apps as I do, so it would likely suit her, or maybe my Mum.
Any help anyone can give would be massively appreciated. Thanks guys!
Can't access HBoot!
Hey is anyone out there? I know lots of people get stuck in boot loops and there's a million threads of support for that, but this is different. I can't access the recovery system either. I have clockwork mod on it and normally you can get into that fine. Trying to find help on this problem is really tough cos I have to wade through all the noob threads for standard easy fix boot loops. If anyone could help me on this I'd be extremely grateful.
This might be all I can offer but two things come to mind. The first is you said volume up its volume down to get into the bootloader. The other is to search in the wildfire forum regarding whatsapp. Recently I read a post about a guy who's phone crashed from whatsapp. I don't remember how he recovered you have to search on it; unfortunately the second time he couldn't recover.
Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Thank you!
MiCeltic said:
This might be all I can offer but two things come to mind. The first is you said volume up its volume down to get into the bootloader. The other is to search in the wildfire forum regarding whatsapp. Recently I read a post about a guy who's phone crashed from whatsapp. I don't remember how he recovered you have to search on it; unfortunately the second time he couldn't recover.
Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thank you for this... I'm willing to grasp at any thread at the moment. I did try the volume down option too but no dice there... but the whatsapp thread sounds promising, so I'm going to follow that up right now. It's after 4am and I've been sitting here working on this for hours and hours and at my wits end, so thank you! Fingers crossed!
Accessed HBoot!
Update:
Ok, I couldn't find the thread about whatsapp that was referred to above, but I have just tried accessing the recovery menu, using the volume down and power key, after first removing the sim card, but leaving the sd card in place. Suddenly that seemed to work! The menu came up!
I tried accessing it again with the sim card back in, and it refuses to come up again as before. So that at least is one issue resolved.
Now I'm having trouble mounting my SD card, which it says can't be mounted. I know the backups and recovery files are on the the SD card, but it just doesn't seem to see them there.
I wiped the dalvik cache in case that was causing any problems and it doesn't seem to have resolved this current issue so far. I'm going to keep trying other options as see how I get on, but I least wanted to share the solution to one of the problems my thread raised.
Further Update
I couldn't remember the name of my mod in the first post.. it was the WildChild mod.
After getting my phone into HBoot by removing the sim but keeping the SD card in, I found I was unable to mount the SD card. I researched this problem and some suggest the card may be corrupted.
I have checked the card on an external reader plugged into my PC and it read perfectly fine, and I managed to copy every bit of data on it across to the computer with ease. Others however found that after a reformat it eliminated any problems with mounting.. so that is what I am going to do and then try and restore the copy of the data I saved to the PC back onto the SD card.
Attempting now to reboot normally with the sim back in and the SD card removed this time produced a very desirable result. My phone started back up, albeit without the normal operating system. I was able to connect to wi-fi and my network and see a missed call voice mail message symbol. There are however no apps at all as yet and no background screen. I should mention that the phone did ask me to allow SuperUser permissions again.. I should also mention that I foolishly tried to Fix Permissions in CWM which then sat for a long time, eventually I removed the battery cos I thought it wasn't gonna do anything.. this is a big no no I now find out from the threads and I may have buggered it up a bit. I don't know.
My saga continues anyhow, and although I've not had much support on this, it might still be helpful for others to read and follow should whatsapp crashed their phone too and mess with their SD card somehow.
Another Update - Making Progress!
Next update on this...
I removed the SD card and put it in an external reader again on my PC.
Then I installed the free program Mini Tool Partition Wizard Home Edition and selected MiniTool Partion Wizard rather than the Power Data Recovery.
The Wizard allowed me to see the hidden partition on my drive. I understand now why it has always had trouble reading and writing to the SD card in the Ext section that was hidden. This should have been an EXT-2 or EXT-4 format partition I think, and mine is an EXT-3.
Maybe I'm wrong, I don't know much about these things and just learn as I go and by experiementing.
I had hoped to back up the hidden data in the partition but I was unsuccessful. Instead I found the Rebuild MBR (Master Boot Record) option and applied that to the entire SD card.
I then put it back in my phone, again without the Sim, and went into HBoot and recovery. I then went to my advanced back up and restore section and now the SD card is mountable and readable! I didn't have to wipe it or reformat!
I found my most recent up date which was the end of August... I wish I'd done them monthly, but oh well not too bad... and selected it and chose to Restore Boot.
Once it had completed I tried to reboot, but no dice. I put the sim card back in.. still didn't work... BUT I was now able to get into recovery again, this time without removing the Sim!
So inching along slowly here with this but making progress.
Next I plan to restore boot again, this time with the Sim card in.. and try and restart.. if that fails, I will go back into advanced recovery and try to also Restore System, and lastly restore SD-ext and see if each of those options repairs whatever damage that stupid Whatsapp did to my phone! I hope the little solution to various problems I've had are of some use to someone else here. Now wish me luck!
Wow, you were busy last night while most of the western world slept . I'm guessing if I posted at 11:10 PM and you said it was 4:00 AM, that your in the London timeline. I thought a little bit more, later, and I think that person's post I read fixed his phone by eventually getting into recovery and restoring, which as I remember worked that one time, until he reinstalled and used Whatsapp again some time later (it was at the insistence of a girl that used it). Whatsapp has, like 300 million users, but it does seem to give some people serious problems, and that's why I think most people are hesitant to try and help. They don't want to make things worse, since there are those instances of totally bricking a phone...but as long as a person can get into recovery, it's not bricked!
Interesting...I have done the, "fix mbr" in PCs many times, but I think you've taken it to new levels using it in phones! At least I don't remember reading anything much about someone doing it (in phones) before and it's brilliant, IMHO. You really did a great job sharing what you've done and I hope you get it fixed. I clicked a, "Thanks" for a good post follow up.
Insert standard disclaimer here: I'm not telling you to do anything, or what will or won't work, but sooner or later you're gonna have to restore that backup, but it's your choice on what to do; and, it sure seems like you know what you're doing, especially having made a backup to work from. I can appreciate the way you've gone piece by piece in your restore efforts to try and find where the problem occurred. The nice thing about the Wild Child ROM is it all works, and incidentally I think the developer uses ext2 for his extended SD card partition! It sounds like you reformatted to ext2 or ext4 from ext3, so the only thing there now is what came from restoring that backup piece in Clockwork; therefore, there's nothing that would be lost that isn't already; and, you backed up everything else on the SD card. So I don't want you to brick your phone either, but I'm wondering about wiping the cache and then the dalvik-cache, and then restoring your whole Nandroid backup?! I think your Whatsapp contacts are saved and so if the phone boots to a working condition you could just uninstall Whatsapp right away, boot into recovery and wipe cache and dalvik-cache again just to be safe, and then decide what to do about using Whatsapp again. As long as you can get into recovery, ultimately you could wipe, wipe, wipe and reinstall Wild Child to start all over if nothing else works.
On the other hand maybe you've already got this whole mess straightened out, if not, I'll again wish you - Good luck!
Solved!
So I next wiped the cache partition 3 times, as someone on another thread said sometimes it takes more than one go to clear it all properly for some reason.
I also wiped the dalvik cache again a couple more times. Then I went back to my back up and restored system. Then I tried to boot my baby back up.
I was falling asleep at this time but I remember the phone partially recovered. But most of the apps were broken. I had low memory issues too, so I uninstalled a few apps, managed to restore some individual apps or update them, and log in long enough to send messages to contacts with my email so I wouldn't lose them.
Then I fell asleep with the phone in my hand haha.. when I woke up I immediately continued with it and finally worked my way back to whatsapp being the last app I wanted to deal with. I managed to get into it and send some messages.
Then I did a full nandroid restore on everything.
The phone returned to it's state as of 2 months ago when I last did a nandroid back up. But some of my TiBu apps were backed up more recently. So I manually restored those and things were mostly back to how they were before and I am fairly happy with the low loss of data.
Whatsapp was working fine for a while.. but then it started having problems. It first had all my contacts there... then it lost their names but kept their numbers, then it lost all the old messages and right now I'm in the middle of trying to restore everything again and it's stuck on a restoration. I did a full uninstall of the app, restored the back-up, then it tried to update, but it always fails and now it's just hanging. So it definitely appears that whatsapp is one of the major causes of problems on my phone.
It was also one of the largest apps I had on there. Wildchild is an awesome rom, it only lacked video really and I installed a codec and player for that and got it working again, despite the guys on the Wildchild thread saying they didn't think it was possible. Yes I had trouble with it sometimes, but most of my trouble stems back to the low memory issues and the fact I broke all my apps up by spreading parts of them over the SD card, internal storage as user apps and system memory. That's a Wildfire S problem, not the fault of the Rom.
Anyway, I've made note of all the important numbers and will be buying a larger capacity HTC phone this week. Not sure which yet, but possibly a Sensation or Sensation XE, depending on my budget.
Thanks for your support MiCeltic. Yes I'm in London hehe. And I hadn't read anything about using MBR on a phone, but it was the SD card which had the problem and that certainly fixed it without having to wipe all my data.
I think what I have here is multiple layers of problems.. and I'm really pleased that after 3 days effort I managed to get past most of them. Once I get my new phone and transfer the contacts, I will have to think twice about using whatsapp.. it's my favourite app of all tho, so it will be hard to part with. This phone has many bugs.. I will completely erase it and reflash it when I get time and either keep it as a back up and maybe gift it to my sister or mum as I said before.
:good:
Last update
OK this is my past update on this... Whatsapp had one last surprise in store for me.
After it started messing up my phone again. I gave it one last chance. I completely removed it from the phone and installed it as new from the GooglePlay store. Then when I loaded it, it found the backed up Titanium BackUp messages and restored those.. then when I opened the app, it also had restored all my most recent messages, up to the day before it crashed the whole phone. I was amazed. They must have been stored on the server or something.. I think they sit there for 3 weeks. So I'm likely only missing one weeks worth of messages at most, about 4 weeks ago! Ha! Brilliant. I'm not doing a Nandroid backup cos everything is stable again and I hope to have no more troubles until it comes time to transfer all the date to the new handset... that's gonna take a while cos I will have to learn how to gain the boot mod rights all over again and maybe even flash a custom rom as the stock is sure to be loaded with bloatware. Still.. if it has a 1GB internal memory it shouldn't slow the phone down too much.. not compared to the tiny 150MB this little baby has!
If someone wants to close this thread now, feel free.
Cheers. :good:
You inspired me to read a little more last night and I did see where some people found a fix by uninstalling and then installing new (not from backup), then restoring their contacts. Seems like you've proved that point! Interestingly I read that ALL of your contacts are stored on the Whatsapp server, not just your contacts that have Whatsapp (Remember those permissions you accept when you install an app!). As I said, there are 300 million users, obviously not everyone has the problems, so hopefully it will work for you now and on your new phone, which after reading your posts I know you will make a back up of immediately and again after rooting...AND definitely before installing Whatsapp ! ! ! You might even find your next phone easier to root as a lot of them don't need an update of the bootloader on htcdev for the first step when unlocking and/or many can gain Soff!
Glad you got it working and now all's right with the world...well for now
Related
My phone is mullered :-(
Whenever I flash a new ROM, all I get is a constant boot loop on first boot.
Flashing a different ROM results in the same behaviour.
The only way out of it is to re-root, taking me back to version 1.15 or something, and then if i try to flash a new ROM - you guessed it, boot loop....
This first started when I had OpenDesire installed, which was fine to begin with, but then it randomly rebooted and started boot looping.
Since then I've tried about 4 or 5 different ROMs and nothing changes.
Any ideas as to what's wrong/a solution?
Just to add, I have one the lastest radios (.08) when I try and flash.
Perhaps flashing the radio after might help?
After much struggling, I've managed to sort it.
Ended up clearing storage in recovery, which helped so long as there was no SD card in it. Had to format and repartition the card, and fingers crossed, all seems well now.
Whenever you change between diferent ROMs it is a good practice to do a full wipe via recovery. 90 to 99% of the boot-loops can be fixed doing it...
The strange thing is that I did wipe between ROMs. I'm not sure why I had a problem this time round, as I haven't had with the previous 10 flashes...
Still, it's sorted now
Funny.. found this thread via google.
I'm having the exact same issue where no matter what rom I flash it gets stuck on bootloops during the startup animation and never makes it into the rom.
NANDroid backups are perfectly fine to restore, just unable to flash any new roms. Spent all last night trying everything from swapping recoveries, to re-rooting, flashing multiple roms, urgh.
Only thing I didn't try is re-formatting the SD card so gonna give that a go now (thanks to this thread) and report back later.
Annoying to say the least.
Well what do you know... a 'partition my SD card' through rom manager (after copying said contents to my computer) worked a charm.
Most interesting......... Praise this thread and any others that gain help from it.
Did you update your radio ?
Sent from my spectrum zx
Man i'm lucky. Two hugely annoying problems in one go.
First up, yes I have replaced my radio, many times The SD card was obviously not too happy with its ext partition, so repartitioning that worked.
I also had another issue crop up straight away that was probably caused by unhappy sdcard, where when restoring apps via titanium backup, phone would reset.
After running a RRU, re-rooting, all the full works.. I find that some of the apk backups are 1kb... Which is not normal. There were about 15 apps like this. I had a backup of these apps from a week or so ago and copied those to the titanium backup directory, restored, no problemo.
Even more annoyingly TB has a verrify backups option which reported all was well. FML.
Well that was a fun morning. Time to finally get back on track *sighface*
EDIT: PROBLEM SOLVED.
My story of woe:
I rooted my Desire using UnrEVOked and installed LeeDrOiD 2.3b (noA2SD), and everything was great, but things started going wrong when I tried to change to A2SD. I partitioned the SDcard in Rom Manager, but for a while the SD wasn't being recognised (little SD icon with a question mark in notification area), and even though that eventually fixed itself I was thereafter unable to make a Nandroid backup - in ClockworkMod it would just "Error while dumping boot image".
I decided to start from scratch and I very inadvisedly went into mounts and storage and formatted everything. I have a hunch this may be my problem.
I downloaded the RUU and was setting up to try using fastboot when the battery ran down, and now it will not turn on or charge. I've searched and searched, but come up with no solution other than sending it away for repair or more likely replacement.
Complication: it was bought second-hand from a non-reputable shop to start with, warranty is so far out the window it's not funny, and I need to keep the fact that I've bricked the Xmas present she got me from my partner.
Does anyone know of anything that can be done to restore a Desire when it won't even turn on? Or is this the end of my phone and my love life?
I'm really sorry for cluttering up the board with my idiocy, but I've been searching for hours and I really am at my wits' end! Please help if you can.
EDIT: Welp, a day later, on it turns and I am back on stock ROM! No idea what happened there, but thanks for the reassurance anyway, it really helped me stop worrying.
I'll try not to mess around with something until I fully understand it next time!
From what I have read the only way to really brick your phone is by altering the radio version or your HBOOT. I am no genius and I can't help fix your problem but i suspect hope isn't lost for you.
good luck mate
Can you get another battery for your phone? Maybe it will turn on.
Can you also post which Clockwork mod you were using?
redzyklon said:
My story of woe:
I rooted my Desire using UnrEVOked and installed LeeDrOiD 2.3b (noA2SD), and everything was great, but things started going wrong when I tried to change to A2SD. I partitioned the SDcard in Rom Manager, but for a while the SD wasn't being recognised (little SD icon with a question mark in notification area), and even though that eventually fixed itself I was thereafter unable to make a Nandroid backup - in ClockworkMod it would just "Error while dumping boot image".
I decided to start from scratch and I very inadvisedly went into mounts and storage and formatted everything. I have a hunch this may be my problem.
I downloaded the RUU and was setting up to try using fastboot when the battery ran down, and now it will not turn on or charge. I've searched and searched, but come up with no solution other than sending it away for repair or more likely replacement.
Complication: it was bought second-hand from a non-reputable shop to start with, warranty is so far out the window it's not funny, and I need to keep the fact that I've bricked the Xmas present she got me from my partner.
Does anyone know of anything that can be done to restore a Desire when it won't even turn on? Or is this the end of my phone and my love life?
I'm really sorry for cluttering up the board with my idiocy, but I've been searching for hours and I really am at my wits' end! Please help if you can.
Click to expand...
Click to collapse
The formatting wouldn't be the problem - it is standard practice to format (or wipe) cache/dalvik-cache/ etc. prior to flashing a new ROM. Problem might be the incomplete flash when the battery died. Have you tried putting it on the charger with the battery removed? Any charge light come on??
redzyklon said:
EDIT: PROBLEM SOLVED.
My story of woe:
I rooted my Desire using UnrEVOked and installed LeeDrOiD 2.3b (noA2SD), and everything was great, but things started going wrong when I tried to change to A2SD. I partitioned the SDcard in Rom Manager, but for a while the SD wasn't being recognised (little SD icon with a question mark in notification area), and even though that eventually fixed itself I was thereafter unable to make a Nandroid backup - in ClockworkMod it would just "Error while dumping boot image".
I decided to start from scratch and I very inadvisedly went into mounts and storage and formatted everything. I have a hunch this may be my problem.
I downloaded the RUU and was setting up to try using fastboot when the battery ran down, and now it will not turn on or charge. I've searched and searched, but come up with no solution other than sending it away for repair or more likely replacement.
Complication: it was bought second-hand from a non-reputable shop to start with, warranty is so far out the window it's not funny, and I need to keep the fact that I've bricked the Xmas present she got me from my partner.
Does anyone know of anything that can be done to restore a Desire when it won't even turn on? Or is this the end of my phone and my love life?
I'm really sorry for cluttering up the board with my idiocy, but I've been searching for hours and I really am at my wits' end! Please help if you can.
EDIT: Welp, a day later, on it turns and I am back on stock ROM! No idea what happened there, but thanks for the reassurance anyway, it really helped me stop worrying.
I'll try not to mess around with something until I fully understand it next time!
Click to expand...
Click to collapse
Hej, i hope you are fine and good in health. Same thing happened with my phone and till now it won't start i opened it disassemble then assemble everything but it won't power on even not charge ............ i am still stuck up with it even no idea what more to do
Can you please tell me how it power on ?? or what you have done with it ??
Waiting for your response.
Thanks in advance.
Hello XDA-Community,
I am in a little bit of trouble with my HTC Desire and I was unable to find any documentation on here on via google to help me out so I am hoping anyone of you guys can give me a hand. Any input is very much appreciated, thank you beforehand!
So, the situation is as follows:
I have a branded T-Mobile HTC Desire (not a T-Mobile customer, though) with Froyo 2.2 stock running, I am a regular user and haven't messed with the software previously apart from installing apps as usual. Until today, where the mess started..
It is one of the old Desires with AMOLED, I think HBOOT version 0.93 or something?
I just want to say I am not bad with computers but I've only started to wrap my head around anything android-tech related as in rooting, flashing, etc. , which is why I'm here.
Now today I decided I want to go and first off, root my device so I can have a titanium backup and possibly tomorrow or sometime soon flash the oxygen rom because I hear I can have increased batterylife with that, which is my main concern (and app2sd for everything) with the HTC Desire.
So I read through lots of guides and arrived at using unrevoked³ to root the phone which worked fine. I then went and bought Titanium Backup Pro so I could make a backup of the entire thing and start flashing sooner or later.
Now I guess I made the first mistake right at that point when I did not make a backup immediately but first used TB to delete some T-Mobile bloatware which I dont use, I used the Filter option and then Remove Bloatware in the Settings to tag the apps in question ("TopApps" and "MobileTV", they are silly and just for customers anyway). TB said I have to restart the phone to remove them, which I did. I wanted to remove them before I did the backup because it was already complaining about low space after I put TB on (you know the desire and its space limitations..). And what good are useless apps in a backup, anyway?
Now, when it rebooted, at first everything looked fine, it starts up normally and goes on with loading all the stuff, I have a few widgets, GoLauncherEx, etc. which takes a bit to load at first start. But having loaded for about 1 minute after pressing the button, and when I can already see some of the UI elements properly in place (I can actually enter SIMcode and everything, or just wait at the code-login-form) - the phone just soft-resets itself and starts booting again. and again. and again. always up to the same point, I reckon.
I have tried getting the SDK and look into adb logcat while it boots (where I am an absolute noob, admittedly), and I was going to paste the entire thing here but my windows 7 "cmd" only has the last 300 lines of output selectable and I can't figure out how to "save" the rest of the log flying by when booting. It shows a lot of k9-mail errors in the log but I am not sure of that is the problem because I havent messed with k9 for months (using it as push mail client).
I am now unsure if the problem is because of TB or because of the removed bloatware, or what is going on. Right now, the phone is unusable.
I wonder if anyone can help me get the phone going again or how I could access the phone data to retrieve the phone's calendar entries and SMS, and possibly as much of the settings/data so I can just go and flash oxygen on it. I would, however, love to have a complete backup of the stock thing running, with TB and NANDroid backup, so I require a running phone I guess. I have previously synced the phonebook entries to MyPhoneExplorer on my desktop but it apparently didnt catch anything else.
I have attached the logcat output that I could capture in the txt file, if it helps with anything.
Thanks anyone for help really! Much appreciated!
Teaches you not to mess around without backing up first. You can get quite a bit of stuff to sync to your Google account like contacts and calendar entries. It also backs up other bits of data too.
From now on, it looks like you can only flash another rom or use an ruu, either way your data is gone like SMS and all that good stuff.
Sent from my HTC Desire using XDA Premium App
Honestly, you probably won't be able to get your data if it doesn't even get passed the first lock screen cause you may have deleted something compulsory for it to boot.
Just flash a new rom or the stock rom if you want then after you've set it all up run a titanium backup batch to save everything. Then and ONLY then should you consider installing Oxygen because Oxygen will require a number of modifications to your desire.
thanks for reading through all of it, I didnt realize the post grew so long when I posted it last night.
I know it is a prime example for the backup sense, Meape.. :/
Aegishua, It does get past the first lock screen. if I enter the SIM Code (or just leave the SIM Out), I can actually interact with the phone for several seconds, it loads widgetlocker and requests the unlock pattern, but there's not enough time to actually do anything when I see the the home screen.
I was wondering if there is a possibility to, say freeze the bootup sequence via USB adb commands or something, like you would press Pause on a desktop PC during the POST screen (yeah I know, the comparison is a little off). So at that point I could at least have time to fetch stuff from the phone to the PC.
and I noticed, if it helps anything: when the backlight is off (display dimmed), shortly before the reset the backlight flashes a couple of times which it doesnt usually do at that point of booting.
oh, and a little question for the next probable step: aegishua, what do you mean only then? I was following this guide http://rootmydroid.co.uk/guides/gen...esire-wildfire-evo-incredible-with-unrevoked/ , and would I not just get the oxygen ROM and follow Pt.3 From Step 2 onwards? Since I cannot do Step 1 anymore (full TB). I.e. just put the rom on SDcard and wipe + flash? btw, the original Oxygen thread ( http://forum.xda-developers.com/showthread.php?t=971904 ) does not say what Radio I need to flash (do I ?)- anyone care to point me in the right direction? Thanks again, I know I'm a noob at this.
Thanks a lot for any input guys
I will not be able to look at this thread for the next few hours but here's a quick update, I now started the phone without sdcard or SIM and it actually works! I mean, lots of apps are missing and icons and stuff, but the phone stays on regardless. I'm gonna go figure out whats wrong with the sdcard content, but first: backup time
Hey
I apologize if a thread like this has appeared before, but i have just about had it with playing about with my desire after i tryed to flash a new ROM, il try and explain is as best detail as i can, and hopefully, one of you will be able to help me get back to normal, as im tearing my hair out over this now...
So...Last night, i noticed that LeeDroid (The custom rom i use) had updated his firmware to 3.0, and in the interest of keeping my phone upto date, i went ahead, downloaded the rom, put it on my SD, did a nandroid backup, wiped and flashed as i would normally
the install seemed to go fine, but when i rebooted the phone, it hung on the HTC screen for about 15-20 mins, so i figured the flash hadnt worked, so i went back, wiped again and restored my backup
this is where the issues begin, the bacup restores fine, BUT, when the phone reboots and loads up, ALL of my apps etc have gone, no longer apparently anywhere on my SD card (which is where most of them were stored) I now had a bare bones android, with no apps (not even market, as that was updated manually too)
at this point, i start to panic, i have seemingly lost everything off the phone (apart from the SD backup i had performed before), and only have a bare bones version of the LeeDroid rom i was using before, with no apps what so ever
so, i thought, i might as well start afresh, so i boot back into recovery, wipe again and re-flash a fresh Leedroid rom, which seemingly again, goes fine, but again, hung on boot
getting more worried still, my SD-EXT then stops mounting, giving me an error, so i re-partition it, format it, and try again, and again, it still hangs on boot
at this point, i realize im screwed, and just restore the bare bones backup i had saved on my computer (nandroid), which at least allows the phone to boot and be semi-usable
i have no idea what im doing wrong here, nothing wants to flash anymore, it just hangs, and i cant even seem to un-root the phone, all the RUU's i use just give me a "CUSTOMER ID ERROR" which i have no idea how to fix
can anyone PLEASE point me in the right direction, im panicing here, i cant seem to get anything to work, and i have been going around in circles for almost 7 hours now...
thanks very much
Looks like you'll need to start from sguare 1 again. Seems like the SD issue, might have corrupted the SD card.
My suggestion, is that you format the sd card (backup all files to the pc)
Create a new gold card again.
Flash to stock again if need be, then root.
You can download googleapps and flash it also. There are some downloadable links in this site you can save to your sd card. Or you can download it at cyanogenmod.com (where I downloaded mine I believe).
i thought going back to square one would be the way forward too, except that i cant seem to find an RUU that will work, as i mentioned, all of the ones i have tryed give me the CUSTOMER ID error, which i have no idea what to do with...
so, im a little stumped..
Your Gold Card is good? Better re-do it again. Because if your partitions blew away on your SD card, it probably cooked all of it.
You shouldn't have any problems finding a stock froyo ROM.
Moscow Desire said:
Your Gold Card is good? Better re-do it again. Because if your partitions blew away on your SD card, it probably cooked all of it.
You shouldn't have any problems finding a stock froyo ROM.
Click to expand...
Click to collapse
i have a stock froyo RUU, should i apply the goldcard, then try the update again then?
im new to this, so im probably going to need taking through all this
edit: so i made my SD into a goldcard. and now it wont mount on the phone, and when i run the RUU, it still gives me the CID error..
im going insane here, someone help >.<
ok, i got it
after doing some reasearch, i found that alot of people were saying that the phone needed to be S-OFF to flash it correctly
so, after reading up, and S-OFFing, i wiped, partitioned and flashed...
and, finally, after 9 hours of tinkering, errors etc, it has flashed and booted
this can be locked now, thanks
partitioned th sd card,
works sometimes, but glad we could somewhat lead you in the right direction, by proxy........
Little puzzeled by the s-off, but hey, it's fixed!!!
After flashing the latest CM9 nightly, I turned on my phone and found that it is running incredibly slow. Like, it takes over 15 seconds to launch any app. I have reflashed different nightlys and HO!NO!'s rom but the problem persists. I have also checked to make sure that I don't have any CPU settings that are keeping the processor slow. I even restored a nandroid backup, it didn't help.
I have now done the following:
-Wiped Data/factory reset
-Wiped Cache
-Wiped Dalvik Cache
-Install from zip
It is still slow.
Is there something I am overlooking? Any idea what is going on?
EDIT:
This is a logcat(whittled down to ~400 lines) of the issue happening in kernalpanics rom. I had the dialer open, put phone to sleep, woke up phone, and immediately started dialing a number. The phone hangs for about 5-15 seconds, and "catches up" later. The log starts right after I woke the phone, so it should pop up at the beginning.
http://dl.dropbox.com/u/16882142/logcat-copy.txt
Here are two videos of the problem(sorry for the wmv):
CM9
GB Rom
Recap:
-I have formatted SD card and tried without SD
-I have tried with and without the SIM card
-I have flashed many different nandroid backups
-I have formatted everything and installed new Roms (I couldn't get HO!NO!s Rom working though)
-I am trying to follow the "unbrick methods" to flash stock firmware. I cannot get the flash to start though(Post)
-I am running out of ideas!
Sounds to me like you got a lemon. Look into this http://forum.xda-developers.com/showpost.php?p=24179363&postcount=4
Out of curiosity is it a phone from bell?
No, its from AT&T. It is actually a refurbished replacement to a new phone I got in December. I want to return it to factory settings but ADB will not recognize the LGP930. This is incredibly frustrating, when I try to install the drivers through LG software I manually put in my IMEI and it says "File not found"
Thank you for the reply, I really need to try to restore this thing.
EDIT: To reiterate, something is seriously messed up with this phone. It takes ~30 second to launch any app. IT will say the program is not responsding and I have to "wait" instead of close to get it to load.
Try formatting system partition then install CM9 again.
Thank you for taking the time Drumist. I have actually already reformatted /system then reinstalled a nightly. I just did it again and still, it is messed up. My main issue right now is that I can't even connect this damn phone to ADB, I can't try to replace this with CM9, rooted, and CWM.
Can anyone help with the driver issue. HO!NO! won't even install anymore, it just sticks on the LG logo. So I am stuck with CM9, but the drivers don't work. Everytime I hook it up to either of my computers, it will detect it as LGP930 for a split second, then try to find drivers, then it recognizes the device as 4 different devices! LGE Modem, LG USB Composite device, LG GPS, and unidentified device. Please, does anyone know how to get into ADB, I am desperate here.
I essentially have an unusable phone. Just to make a call I have to click on phone, then it hangs for about 30 seconds until it says the app is not responding and asks if I want to force close it. I have to select wait, then eventually the app will load. All list-views work fine so I can scroll the contact list. But when i select a contact I have to wait another 30 seconds.
I have searched and read this forum for hours on what to do about the drivers, but no luck.
Is it possible that this is the fesult of a corrupted file system?
My very limited troubleshooting skills with Android says you've either got a/some app(s) running that's soaking up all the CPU/System resources, or there's some major I/O issues going on with your phone (whether because of messing with the ROM or with Hardware is unknown).
Unfortunately you've also stated that you can't get ADB to work, which throws a big wrench in the works to get some debug logs.
If you haven't already tried, there's a very helpful thread on getting ADB working on the Nitro (via stock Google USB driver, not LG). I highly recommend doing those steps and get ADB working for further troubleshooting: http://forum.xda-developers.com/showthread.php?t=1601159
Another thing to try, for giggles, pull the SDCard out and see if there's any performance gain...Maybe you've got a hosed SDCard, or bent/bad pins in the SDCard slot (worth a shot anyway).
Good luck!
Namuna! Thanks for your reply.
I figured out it is somehow related to the SD card, THANK YOU! I actually tried removing the SD card yesterday when the problem first started, but the trick is I have to boot my phone up with no card in it. Once I put a card in, even if I take it out, the problem starts up again.
Since my phone ran out of battery hours ago, I am at work, and I left my cable at home; I cannot try the google drivers. I won't be geting home until late so I'm going to have to do some more experimenting tomorrow.
You don't need the Google drivers now. LG drivers are working again.
I remember that that is the case Malnilion, but I need to try something.
Bad news, apparently I jumped the gun because my phone is super slow again, with or without an SD card.
I just really need ADB access, a log would be a godsend.
I have found I can get to ADB when in CWM, but I can't get the drivers to work when in CM9 so I can't get a logcat.
Try to adb in recovery. Did you format that SD card?
Sent from my LG-P930 using XDA
I now have a version of kernalpan1cs rom running on my nitro. Almost everything runs fine, but the slowness happens when I try to make any phone call and with other random apps.
I have ADB now, and I am going to post a logcat of what happens when I try to dial a number using the phone app, then when I try to make a phone call.
I just need some help, I can look at the logcat when I do ADB logcat, but I have a hard time keeping track of when the problems happen. There are so many things that happen immediately after it that I cannot keep track of where the previous information was in the console window.
BTW, I notice that when the slowness happens when I dial a number in the phone app that the log reports a bunch of stuff about going into wakelocks and coming out of wakelocks. I thought this was kind of weird.
2 things.
1. I salute you for sticking with this phone through all the issues you've had (and still continue to have). I would've got the thing back as close to stock as possible and then exchanged it for another Nitro a long time ago. You've already done it once, it seems the refurb you got is also suffering some hardware issues...Might be time to do it again!
2. If you are dead set on chasing this rabbit down its' rabbit hole though, then I suggest getting acquainted with another debug tool called ddms (http://developer.android.com/guide/developing/debugging/ddms.html). It's a GUI based debugger that utilizes logcat, but is much more robust with tools for filtering and viewing associated processes.
Good luck!
Have you tried replacing the sim? Sounds like a shot sim to me.
beaups said:
Have you tried replacing the sim? Sounds like a shot sim to me.
Click to expand...
Click to collapse
This is a good point, especially if it's the same SIM that you used on your previous Nitro...Thereby bringing the issues with it!
Thanks guys! First off, I have exams going on so this has definitely taken the backburner, otherwise I would be on top of this.
@beaups: I'm pretty sure it isn't the SIM, when the SIM is out the slowness continues in either ROM.
@Namuna: I think I will give ddms a try once I have some time(hopefully this weekend). Thanks for the tip, I usually like getting my hands dirty
This is a logcat(whittled down to ~400 lines) of the issue happening in kernalpanics rom. I had the dialer open, put phone to sleep, woke up phone, and immediately started dialing a number. The phone hangs for about 5-15 seconds, and "catches up" later. The log starts right after I woke the phone, so it should pop up at the beginning.
http://dl.dropbox.com/u/16882142/logcat-copy.txt
Lastly, if I try to exchange this phone for another, what should I do in order to make it more factory-like? Install a stock ROM? Uninstall CWM?
EDIT:
Here are two videos of the problem(sorry for the wmv):
CM9
GB Rom
I also got the same thing here after updating the cm9 followed by a wipe data.. Tried all the things listed.. format system, gb roms.. Have you had any luck with the unbricking method?
I have same situation about the super slow after cm9. However, i fixed the problem after using the unbricking method. everything back to normal now. You can take a try. It seems like cm9 mess up some I/O address, cause it only slow down whenever you need to input or output from system.(Example: phone call, music ..etc)
did it
had the same problem, [Guide] Unbricking Solution for LG Nitro HD (P930) did it for me, back to usual speed
Yes, the unbricking solution worked for me, I just had to use the method in the original post once I worked out some driver issues.
I still am wondering what caused this though.