Hi!
I need somme help, maybe from ADB specialists I guess.
One of my friends asked me if I could help with his DHD, here is the story:
This DHD is almost dead after a big shock. But it still can boot. Problem: the screen is cracked at the very bottom and now is responsive only for about 2mm at the very bottom, not even possible to unlock (can't push the ring more than 2mm)
He won't just change the screen since all the body of this poor DHD is completly destroyed too and kept in one thing with tape. The camera is dead too.
What he wanted form me is to try to get some datas back, make some backups of the apps, get the few photos that were in internal memory (and not on the SD) and most important, trying to get the contacts (he had many contacts in the phone memory instead of the SIM...bad luck!)
As he had a custom ROM, I thought at first I could boot in recovery and then get some datas back from here.
But impossible to manually boot into recovery, the volume button is dead (and missing!). Even with a metalic pin, I can't make it work, so can't boot into recovery or fastboot.
SO I need help!!!
=> Can I boot into recovery with the phone already booted to Android and something like adb command?
=> Is it possible to get the contact backs?
=> What else can I do?? xD
All help appreciated!
adb reboot recovery.
Related
I have a problem with my Tmobile MDAIII compact.
It dropped on the floor last week, the battery fell out and everything.. and after that it just hangs in the windows bootscreen.
Opened it up to see if there was any visible damage inside, but found nothing.
When I turn it on the screen shows:
IPL 1.12.0001
SPL 1.11.0001
GSM 03.21.90
OS 3.7.0.0
then it gos to the windows mobile splah/bootscreen
I have the PDAviet black and blue v4.0 touch ROM on it..
sof reset doesn;t work, it will just get stuck in the bootscreen again. if you touch a button it lights up the screen and keyboard, but even that stops responding afer a couple of minutes.
a hard reset is not an option right now cause I can't afford to lose my contacts and notes
flashing is not an option for the same reason.
had anyone here got any idea how to get this working again without a hard reset or a new flash..
I read that you can do more harm then good if you just use some commands you find, cause every bootloader has different commands so I carefully tried some MTTY commands in the bootloader, but in the end it didn't do anything. good or bad..
Is there a way to see where it hangs or gets stuck through some output console with MTTY or something? or get the contactlist out of it or the notes..
I SO cannot afford to lose my contacts or the notes in the damned thing. ( yes, I all hear you say " you should've backed up then!!" but hindsight is always 20-20 )
is it bootLOOPING or is it just hanging on the bootscreen?
if it's bootlooping try removing your SD card and then soft resetting
if it's hanging, your guess is as good as mine
It's hanging in that bootscreen/PDAVIET splash, it's not looping.. it just sits there mocking me..
There is no SD card present and no SIM either and if I insert those, it doesn't change a thing about its behaviour, it still hangs..
124 views and no one knows anything? no small clue, no tip, no nothing?
I think it's just broken.
The only option you can try I see is a hard reset. To bad you haven't made a backup or something on your computer. Lesson for the next time, if you contacts and notes are that important, Make a daily backup!!!
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
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.
I desperately i need sombodys help, wich is close to Newcastle or to Harlem, Amsterdam! First of all I have my desire rooted with S-on, i use to have Starbust Rom on it, i did have AmonRa recovery, so i did partitioning my sd in this way. But the phone starts to be a bit unstable, like luggy, and black screen. So i back up the rom, did a full wippe, then try to resstore. I got more backups, so i back up a wrong one, then i did the right one, without wipe, then the phone, starts to have a randomly boot loop with " quietlly briliant" i try to install another rom from sd, but the message is coming out : "can't mount /dev/block/mmcblk0p1(or/ dev/block/mmblk0)" (no such a file directory) .For me is sounds like "mathematic" formula....the main problem is, i'm a bit newbee, and i dont have a computer to folow the steps from the advices founded on the forum , and i dont have a stable adress to send it in service, cause one day i'm in England North Shields, one day i'm in Ijmuiden Amsterdam ( my job is so). But i was thinking maybe some one nice and with good heart can help me to fix my problem, and it wont be for free. I will pay for it! So please help me some how...buhuuubhuu((
The solution to your problem is quite simple actually,all you have to do is to regain control of your micro-sd card by following this http://forum.xda-developers.com/showthread.php?t=691639
So, open your phone in bootloader by holding vol- and power button and then selcet using the volume keys fastboot. keep the phone connected to your computer through the usb and from the android sdk or from r6-desire-root run in a cmd window "fastboot oem enableqxdm 0"
After this go in to recovery and load your favorite rom.
Thank you very much, it seems to be so easy, but my problem is that i don't have a personal computer. Looks like i need to wait till i get home in a few months....and no phone....
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?
Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!
Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.