Hello,
I'm new to the Android scene and already I have a problem.
I successfully upgraded my HTC Magic with Cyanogenmod.
I did it exactly like it said in the instructions on cyanogenmod wiki.
Installed Android SDK R05 for Windows and used:
bc-4.2.15.1-ebi1-signed
recovery-RA-sapphire-v1.6.2H.img
update-cm-4.2.15.1-signed
DRC83_base_defanged
HTC_ADP_1.6_DRC83_rooted_base
So i did the magic on Magic and the CyanogenMod worked, at least until recently.
My co-worker asked me to lend him my sdcard so i opened the magic and took out the sdcard from my htc that was on while i did that.
Than the trouble came forth...After a reboot the phone started booting for a long time...than it showed an error that the sdcard wasn't unmounted properly, and it didn't go away even when i inserted the sdcard back in, even after a hundred or so reboots. Than it started to crash the processes (acore and such)
Than after a milionth reboot the screen and the accelerometer stoped working, soon after that the keys followed the screen and the acc. I was thinking maybe the screen and the keys stoped working permanently and wanted to throw the phone away. But after another optimistic restart the keys worked for some time than the ball when pressed stoped responding...so i could highlight an icon on the home screen but couldn't start it. Than i accidentaly pressed it on the screen and it worked, but shortly after that everything was dead again. Than the phone started rebooting on a low battery. When rebooting to bootloader (with the battery fully charged) the screen flashes and nothing responds. But it still shows in a flash those three androids on the skates. And i can't seem to adb push the recovery.img to the sdcard...states some Read only problem. Sdcard seems alright through the card reader. So that is about it of all the problems.
So i was hoping some experts on here could give me some feedback on the device. Is it finished or can I rescue it. I really fell in love with this phone so I would much rather here the second option. I'm attaching the log from adb logcat if it is for any use to any of you...
Thanks in advance
Related
Im using DeepShining X4 rom. all of a sudden when i was switching tabs, my phone froze, so i soft reset and it would get past the Touch Pro2 screen.. i left it for at least 10 minutes and nothing. so i reset it again.. again.. 3-4 times, with the same result.. idk why, but i went into bootloader mode [vol down+power+reset] got the tri color screen, and found no hard reset option so i naturally soft reset.. this time, i got past the Touch Pro2 welcome screen and it went on to the other two welcome screens, but stops at the windows one.. wtf is going on?! how can i flash another rom without accessing my files?? alsdkjflaskdj. someone please help, im freaking the eff out.
You don't need to flash a new ROM, just hard reset manually. Turn off the device completely (yank the battery if necessary). Now, press the power button, the send key, and the end key all at the same time. You should get a prompt instructing you how to hard reset. Follow the instructions and you'll be fine.
Somehow your windows has become corrupt. It is digital media afterall and it does happen. No need to freak out. You will get through it.
As DaveTheTytnIIguy said pull the battery, let sit a few minutes, reinstal and then while holding the end and send buttons at the same time push the power button. Follow instrucions on the screen. I think it says push volume up to do a hard reset.
You will loose any apps and files that were stored to the phone. Anything from the SD card will be fine but will have to be reinstalled to get it working.
If you made a backup of your phone you could now load this and then everything would be back to the way it was. This is why I do weekly backups and load everything to storage card. It also helps to backup the storage card once in a while as they have been known to go bad as well.
Afternoon all,
Last night I left my Desire charging as normal, having recently installed the Remote Media App. I suspect it used up all my storage with some sort of indexing process, as I returned to the phone this morning to find it perpetually showing the glinting HTC logo.
A reboot failed to clear it, and booting into recovery mode reveals"E:Error in DATA:data/recovery/log, (No space left on device)"
I've tried connecting to it with adb, but I get the following error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is there any way out of this bind? I had/have ClockWorkMod recovery installed in order to use ROM Manager, but I'm not terribly clued up on what else is out there on offer.
Any advice would be greatly appreciated.
Kyle
Try rebooting the phone into recovery mode and wipe/factory reset and see if this fixes it?
(Although you will loose all your apps/settings/scenes, though)
This should resolve the problem though.
hehe, there is always that option. I was hoping not to lose texts, settings, etc though this time round. Sadly my backup is more than a few days old.
I was mistaken in thinking I had ClockWorkMods recovery image installed, it appears to have gone back to the default image. I've just discovered a modified recovery ROM from JesusFreke here http://forum.xda-developers.com/showthread.php?t=443041 which may be of use.
Having to wipe and start from scratch again is a disgustingly appaling out of space failure mode. >:-/
bin the phone and use a pineapple
That recovery image is for G1! Don't even think about flashing it.
Even if you have stock recovery, you should still be able to clear storage from HBOOT.
Regards,
Dave
One other thing that might be worth trying is booting the device in safe mode.
Whilst the phone is power down, hold down the menu button and then power on - keep menu held down until the phone is fully booted.
I doubt that it will help in this situation, since clearly /data is completely full, but there's always a slim chance it work.
Regards,
Dave
munkehman said:
bin the phone and use a pineapple
Click to expand...
Click to collapse
Thanks for the advice m, I'll be sure to kick you in the nads next time you cross the border
Sadly Safe Mode fails too. The HTC logo appears and glints for a while, and then briefly vanishes just to reappear again. My thumb got sore after 5 minutes of holding the button down
I realised that was a G1 ROM shortly after reading more about it! I see there may be a more suitable recovery ROM at http://forum.xda-developers.com/showthread.php?t=709146 that I can flash. Failing that, then I'll clear storage and consign myself to failure
Wahey! It's sorted! Well, it was sorted a couple of hours ago, but a meeting got in the way
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
kylegordon said:
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
Click to expand...
Click to collapse
Sorry to dig up an OLD OLD thread, but your "guide" helped me out last night.
In addition to looking for "big" items in the data partition, I also moved some of the Google updates (5meg Maps.apk anyone ?) from /data/app to /system/app ... renaming to overwrite the original version from my Rom.
Thanks Again.
Hello All,
I've been browsing and searching pretty much all day, so I'm now going to ask for help.
Symptoms:
My screen is black. No white bars. Nada.
I know the phone turns on because the charging light goes off and the phone vibrates once when I press the down volume and power to go into recovery.
Preceding events:
I had just finished making a phone call, and the phone rebooted. I (was) running OMGB v6. When it came back, it started into a boot loop. It would run through the splash animation and then restart.
So, I decided to clear everything out and re-flash. Pulled my card out, wiped everything. Backed up my card, cleared it out, formatted it, and put the rom image in the root directory. When I tried to flash, I received the following error:
Cant mount /dev/block/mmcb1k0p1 (Invalid Argument)
Mounting /dev/block/mmcblk0p1 on /data failed: Invalid argument
I pushed parted (and a few other files) in adb and checked out what was going on. It looked like my phone's internal memory had somehow become screwed. So, I followed the directions outlined here:
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage (Sorry, can't post links yet. I'm not that cool. .smirk.)
When I got to the step of re-flashing PN31IMG.zip, Everything seemed to go through fine, then it rebooted and Voila! The screen is dead.
I think it may be because I have the slcd version, but I have no way of knowing for sure.
Any input or suggestions would be both welcome and helpful.
EDIT: Can you even get into hboot?
And you formatted your SD card as FAT32 right?
Probably a SLCD screen and the PB31IMG was for 2.1/AMOLED.
Try this guide. http://forum.xda-developers.com/showthread.php?t=786436
Flash the PB32IMG.zip in part 2. It's the stock 2.2 with support for the SLCD model. Thats just my 2 cents.
Input: In addition to searching and browsing, you should post your thread in the right section.
and yes as said above it was probably the incorrect screen version.
EDIT: I am doing just as you advised. Will post after trying. Thanks!
I am fairly certain that I can get into hboot, as this is what happens:
Press and hold down volume and Power
Wait 5 seconds, release power/volume down
Charging light goes off
Camera shutter clicks
I wait a good 15 seconds, just in case it's scanning my sdcard
Then, I presume it is in hboot and press the volume down key to move the selection to recovery, then press power to select, so that I can *hopefully* adb to fix it
It vibrates, as though going into recovery, But I can't see anything on the screen from start to finish, so I'm not sure.
And I have to be screwing it up somewhere, because no device is detected in adb
kaiserII101 said:
Input: In addition to searching and browsing, you should post your thread in the right section.
and yes as said above it was probably the incorrect screen version.
Click to expand...
Click to collapse
Thank you, kind sir.
As I am obviously ill-educated as to the correct place to post, would you mind pointing me in the right direction; or, as you agree with my assessment, offering a solution?
Update:
So, I finally got the timing right and booted the phone enough to get to adb.
I pushed parted and associated files to the phone and re-partitioned the internal memory (Swap, EXT2, FAT32), then disconnected from the computer.
I pulled the battery for 30 Minutes. Unnecessary? Probably. But I'm saying what I did just in case someone else has this issue.
While the battery was pulled, I downloaded:
ttp://dougpiston.com/files/RUU/build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
I formatted a 4gb card FAT32, and loaded said zip on the card's root directory. Then I turned the phone on and held the down volume to enter hboot.
I waited 5 minutes. Then I pressed the up volume key to confirm installation aaaaaaannnnddd......
I waited. 15 minutes this time. Then I pressed volume up to confirm phone reboot. 90 seconds later my screen came on, and booted into VZW stock!
Oh, and kaiserII101 - I would like to extend my personal thanks to you for pointing out that this was in the wrong thread.... ..... and then not responding. Where I come from, that's called asshattery. Not appreciated. Next time you feel obliged to make a snarky comment instead of actually being helpful, do us all a favor: Don't.
dismal moron said:
Update:
So, I finally got the timing right and booted the phone enough to get to adb.
I pushed parted and associated files to the phone and re-partitioned the internal memory (Swap, EXT2, FAT32), then disconnected from the computer.
I pulled the battery for 30 Minutes. Unnecessary? Probably. But I'm saying what I did just in case someone else has this issue.
While the battery was pulled, I downloaded:
ttp://dougpiston.com/files/RUU/build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
I formatted a 4gb card FAT32, and loaded said zip on the card's root directory. Then I turned the phone on and held the down volume to enter hboot.
I waited 5 minutes. Then I pressed the up volume key to confirm installation aaaaaaannnnddd......
I waited. 15 minutes this time. Then I pressed volume up to confirm phone reboot. 90 seconds later my screen came on, and booted into VZW stock!
Oh, and kaiserII101 - I would like to extend my personal thanks to you for pointing out that this was in the wrong thread.... ..... and then not responding. Where I come from, that's called asshattery. Not appreciated. Next time you feel obliged to make a snarky comment instead of actually being helpful, do us all a favor: Don't.
Click to expand...
Click to collapse
Most cool - glad that worked, and thanks for posting the means to correct it so others may benefit from your experience!
Had a similar thing happen as well a while back ~ since then, I've made weekly copies of my SD card onto my PC - overkill perhaps, but then there's always a full backup of my goodies.
Happy modding!
I'm glad you got it working and I'm even more glad that I don't have the SLCD version of the Dinc. They just have so many issues...
Have fun!
A bit after using setcpu, My phone wouldn't respond when I tried to wake it up.
I had it set to ~700 powersaver when screen off and ~800 conservative in normal, but 1.5ghz when plugged in. It was plugged in and when I woke it, the screen wouldn't respond. I got to the homescreen by flipping open the keyboard (to unlock, I have no pattern). I think everything was working except for the touchscreen and soft keys.
Eventually, I pulled the battery, and now it won't boot.
when I turn it on it takes me to the screen with the androids on skateboards and when I push power for the first option it says
"SD Checking...
Loading...[PC10DIAG.zip]"
it takes a long time for it to get the message "No Image!"
then it looks for the .nbh, (not found) and starts looking for more files, none found
any fix? or am I screwed?
I brought it second hand, so no warranties...
BUMP
Help please?
Should I find and download the PC10DIAG.zip and put it on my sdcard?
I kinda need it fixed asap.
Ok, well I saw that I shouldn't flash the PC10DIAG.zip since I'm S-Off, So i tried to flash recovery through fastboot, still couldn't get into recovery, even though it seemed to flash successfully, and no matter how many times I rebooted it or how.
eventually I tried "Fastboot reboot" and the thing started up normally, wtf?
problem solved, but I'd kinda like to know what was wrong just because.
otherwise this thread can be closed
Phone Details:
HTC ONE M8x
Stock Rom (Rooted)
Kit Kat (can't remember the exact version)
Unlocked BootLoader
S-ON
Ok so I'm having a bit of trouble with my phone which all started after a sudden reboot.
Heres the full story so the pros might be able to understand what happened:
While I was browsing the internet, my phone started lagging really badly. After a few more seconds of lag, the screen suddenly froze. When I tried to reboot the phone, the screen just offed and wouldn't turn on anymore though I could still feel the haptic feedback from touching the screen. Holding the power button still brought up the power menu so I decided to reboot and hope for the best. After the reboot the phone was still laggy but not as bad as before however a new problem appeared. I noticed that opening the File Manager App took longer than average and that moving/copying files from internal to external storage would freeze the app for a while but still finish the command.
After getting irritated of the sudden hiccups I decided to boot into the Recovery Menu (mine is TWRP) and try something to see if it works.
I cleared 'Dalvik Cache' and 'Cache' first then rebooted. The phone started like normal but when it got the part of Updating Apps, it stopped at Starting Apps. So I decided to reboot into Recovery again, after clearing the Dalvik Cache and Cache again I went to 'Reboot', but... (HERE'S WHERE THE BIG PROBLEM HAPPENED) instead of choosing 'Power Off', I clicked 'System' and the phone froze. After a while, the phone rebooted but this time it didn't want go past the point where it shows the ONE logo. Panicking, I went to the recovery mode again and went straight to 'Reboot', when I clicked 'Power Off', the notice at the top said:
No OS Installed!
Which led me to believe the phone wouldn't boot because of the lack of an OS... (OBVIOUSLY):crying:
Questions:
1) Is this problem considered as Soft-Brick or Hard-Brick?
2) How can I fix my phone?!
3) Can I install a stock ROM to fix it?
Moderator Information,
Thread has been closed, as you already have a thread open for this issue.
Many thanks,
Stephen