Related
Hi guys and girls.
New to XDA but not to Android.
I need some help big time as I'm totally stuck and I'm about to send my phone to "will it blend".
Long story short my memory card will not read when inside the phone all I get under phone storage is "unavailable" with mount being greyed out.
HTC DESIRE HD 2.3.3 (Not Rooted)
Things I have tried:
Factory reset soft/hard both through phone and through power + vol down.
Tried two different mem cards both coming up in storage as "unavailable" the general fix seems to be formatting in fat32 on desktop pc I have done that for both cards (which are both readable on PC) and have even tried formatting through command prompt still no luck.
read alot in ADB/fastboot as it is something I'm abit unfamiliar with saw that users where able to restore sd card function by installing adb then running command prompt: "fastboot oem enableqxdm 0" I get a message saying it was successful I reboot guess what...same problem. One thing I have noticed is if I type "adb shell" I get "Daemon started on port 5079". (I have enable debugging) followed by device not found. have tried two diff usb cables both work with my S2 on either media faceplate or backplate usb ports still no luck. Trust me on this one guys I have searched far and wide and I'm just about read to quit on this. I'm at a dead end any advice would be awesome.
I've tried to resolve the adb method by installing various drivers (running windows 7pro 64bit) the issue I seem to get is that windows doesnt like the drivers Im trying to assign so im forced into have to update them manually through "let me choose a driver from location" blah blah blah...
There is a system update available which may possibly fix my issue however suprise suprise I can't download the update without having an sd card. I have even tried downloading a HTC sdmount widget whether Im downloading the wrong one I dont know? I have got HTC sync installed as others claimed this helped windows detect the correct drivers but then technically speaking its not an ADB interface?? just like to point out that both of the sd cards work flawlessly in my s2. anyone who can help me will get paypal'd a beer!
Thanks
Seb.
OK, I had same problem with my Desire S. I'm running Win7 64bit as well. I un-installed HTC sync, including the drivers. Control Panel>Programs & Features. I then download the latest HTC sync. Went back to Programs & Features and un-installed HTC sync but, left the drivers. Rebooted PC and Win7 picked up Desire S.
Hope this helps
How old is your phone? Depending in which country you are in you may still be under warranty.
Try cleaning the contacts?
Not too sure if you can mount the sd card on phones that are not rooted, or if you have the hboot option/recovery. Fastboot turned off, phone off, then press and hold the down volume button and while pressing it down, press the power button.
If you are not sure what you are looking at do not play around with those options, and it may not work. Not sure if you get those options if you are not rooted.
Do not root your phone, it is improbable it will help, and chances are, it may cause more problems than help.
First option, find out about the warranty.
Edit: just noticed you can boot into hboot. Not too sure if you have the option for recovery and even less if you get the option to mount sd card through there.
2nd edit: I'm not responsible for bad advice. I still haven't had my second cup of coffee
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.
eloquence intshe
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
3rd edit: to find out if the adb is working properly and you got the htc sync installed type in whatever the command is in adb to see if it detects your device.
However, try cleaning the contacts and find out about the warranty.
Sent from a dream.[/QUOTE]
How do I clean the contacts on the sd reader? it doesnt look very accessible unless I remove part of the housing? also what command prompt do you recommend I try first? like I said I tried "adb shell" and got no device found I'll update in a second as soon as I have tried this I have just uninstalled htc sync now all I need to do is assign driver to "android 1.0" in device manager then I'll take it for a spin.
Thanks dude
Ironman MarkV said:
Thanks for the reply.
Hehe dont worry you can have some of mine I'm on the 4th cup thats how stressed I am getting with this. Just trying Taysider's method for trying to re-enable the sd card function. I have disabled fastboot using your method so is there a way of mouting sd in recovery? because Im sure I may have tried that already and all I got was an icon of a phone with a red exclamation mark infront of it?
thanks
Click to expand...
Click to collapse
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Teichopsia said:
Re-read my previous post, there' another edit.
Thing is, Im not too sure what options you get nor l, well, anything related to non rooted phones. Do not root your phone as I mentioned previously. Mainly because first you ought to find out if you are still under warranty. If you are, send it to them.
Exclamation mark? Do a search, there were a few threads talking about that a few weeks back, but I believe it was about something else entirely, people effen up their phones trying to root.
From here on, the best advice I can give you is step back, take a break, continue later. There is probably too much info in your head right now.
1- see if adb can detect your phone.
2- try cleaning the contacts, do a search cause I can't remember if the cleaning of contacts was also for the sd card or only the wifi antenna.
3- Check your warranty, I can't stress this enough.
4- Coffee is kicking in
5- Check if you can detect the sd card through recovery. My assumption is that recovery works something like safe mode in windows, only an assumption.
6- Wait till someone more knowledgable than myself joins in. Chances are it would either be darunion, gleviatan or some chap who's nick I cant remember but starts with an M.
@guyinthecorner: you can skip this one - and I'm still waiting for that flashable zip.
Sent from a dream.
Click to expand...
Click to collapse
Lol, already saw your username and was like 'Yup, problem solved ;-)'
Flashable zip is being a pain in the rear, should have it soon (reading a crap-ton of tutorials to help me)
Sent from my Desire HD using Swype beta for Android!
Hi, as you probably know I have Acer Iconita tab A100, I've been using it for 5 months, it was working great and everything and than suddenly it couldn't boot, I tried all ways of hard reset, when I enter recovery, I can do nothing but wait and in the end i get this:
E:/dev/block/mmcblk1 does not exist
Fining update package...
E: failed to mount /mnt/sdcard (No such file or directory)
Can't mount /mnt/sdcard/update.zip
Installation aborted
When I enter fastboot I get the following message:
Bootloader version- (some numbers , not if it's important) - ICS, Starting USB download protocol.
And it stays there forever. :S Please help
(when i try booting it, it remains forever on ACER or ANDROID screen)
Its bricked, if its under warranty then ship it out to acer for a board replacement.
Sent from my HTC DNA
Hey
I don't have the box or the receit >.< So I can't , though some people on other forums said that i could enter fastboot and do something with a program called ADB which can be found in Android SDK. :S
domob said:
I don't have the box or the receit >.< So I can't , though some people on other forums said that i could enter fastboot and do something with a program called ADB which can be found in Android SDK. :S
Click to expand...
Click to collapse
Not on this device you can't. Once it bricks its done for. Go on acers site and put in the snid on the sd cover flappy thing and check for warranty, then get into a chat with a rep to get it sent in. If its off by a month or two tell them you got it for a present from a period just inside the 1 year and they may reset it to be covered, they did it for me even though I was already covered they asked when I purchased it, said I dunno but I got it as a present on blah blah date, they reset the 1 year to that. Box and receipt not required nor asked for nor wanted.
Sent from my HTC DNA
The eMMC module "crashed" in my Nexus 7, and it got into write-locked mode as much as I can tell.
Actually I get -110 on init, I can't reach the block devices in adb, as it says it's busy.
What I can do:
Get into bootloader mode
Get into recovery mode (The screen stays at TWRP logo, but I can adb shell in it, but I can't read or write the mmc blocks)
Now this is not much help in write locked mode of course, but then I ran into this thread.
I could try the same with my Nexus 7, but I need some help:
Reset command (if there is any) for H26M64003DQR (I guess that's what is inside the 32GB version)
A dump from the boot and some other neccesary partitions.
As an alternative if someone knows the pinouts of eMMC chip I can use to solder to an sd card reader, it would help a lot.
As a second alternative, if anyone knows a way to boot right from usb, it would help too.
If anyone could help me with this, I would be really grateful.
Having the same issue and need help
I'm also having the exact same issue. No access to the eMMC at all -- all attempts to mount or read from it results in I/O error (-110 error when checking via dmesg).
It all happened randomly and I thought it was just a random restart. But after it was stuck for 30 minutes on the Google logo, I found out something was not right.
Does someone have any ideas? I would be **very** interested and grateful if I can get this fixed. The warranty just expired two months ago... :crying:
leoetlino said:
I'm also having the exact same issue. No access to the eMMC at all -- all attempts to mount or read from it results in I/O error (-110 error when checking via dmesg).
It all happened randomly and I thought it was just a random restart. But after it was stuck for 30 minutes on the Google logo, I found out something was not right.
Does someone have any ideas? I would be **very** interested and grateful if I can get this fixed. The warranty just expired two months ago... :crying:
Click to expand...
Click to collapse
I've tried everything, and as far as I can tell, you have 2 options:
Solder a microsd card to the proper pins on the motherboard. (When I looked, nobody knew those pins, maybe there is some development since then)
Buy a new motherboard. - That's what I did, it was about 75$ from eBay. It's working beautifully since.
Xmister said:
I've tried everything, and as far as I can tell, you have 2 options:
Solder a microsd card to the proper pins on the motherboard. (When I looked, nobody knew those pins, maybe there is some development since then)
Buy a new motherboard. - That's what I did, it was about 75$ from eBay. It's working beautifully since.
Click to expand...
Click to collapse
I think I'll buy a new motherboard: is this one [1] okay?
Also, would you mind writing up a quick guide as to how to change the motherboard? I've found a video on YouTube for disassembling but unsure on how to change the motherboard safely. Thanks!
L i n k s (sorry, but there's a restriction; you know what to do with the l i n k s):
[1] www-ebay-fr_itm/ASUS-Google-Nexus-7-tablet-Gen-2-2013-16gb-motherboard-logic-board-100-working-/271623781886
[2] www-youtube-com_watch?v=uv3u78YNUHk
Yes, it's okay.
I've done the disassembling from a youtube video too. Just be careful, the case can be easily cracked on the corners. Memorize(or take photo from) every cable's place. There is a few hidden screws holding parts of the MB you should be aware of, but you'll find them if you search.
It's not that hard, just be patient and gentle.
Good luck!
Thank you! I'll try this and hope I can revive my Nexus 7.
Did you also try booting from a USB flash driver through an OTG cable before replacing the motherboard? I'm just curious what you did end up trying when you say you tried everything.
I'm not the OP, but as I've had the same issue, I can definitely say it wouldn't have helped, since it was a hardware failure.
Hi all.
I suspect this question has been asked before and I have found loads on how to do's, but I can't seem to achive what is needed, so any help, however small is greatly appriciated.... he goes.
Customer has brought in an HTC One M8. Details I can give from the Fastboot screen is:-=
***Software Status: Official***
***LOCKED***
M8_UL_CA PVT SHIP S-OFF
CID-111111111 (<---- 8X1'S)
HBOOT-3.10.0.0000
RADIO-1.29.214500021.12G
OpenDSP-V51.2.2-00593-M8974_FO.1015
OS-6.12.401.1
eMMC-boot 2048MB
Dec 17 2015,14:15:48.3
It is stuck in a boot loop that alsways shows the HTC boot screen, reboots to the HTC screen and promptly then to the Android recovery screen:-
Android Recovery
HTC/htc_m8/htc_m8
6.0/MRA58K/buildteam12171409
user/release-keys
Use volume up/down and power
Reboot system now
Reboot to bootloader
Apply update from ABD
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Power off
_________________________________
Supported API:3
handle_cota_install: install cwpkg to /cache/data/cwtemp/cwpkg.zip
handle_cota_install: install cwprop tp /cache/data/cwtemp/cw.prop
Write host_mode success
handle_cota_install: No CW files. Skip cw installation
Sorry to have to type this in as I cant seam to get images to upload.
Now, this seems to be a common problem and most suggestions are re flash the firmware using RUU. The first stumbling block I am hitting is the phone is not being detected on any PC that I use, by any cable I use, either by Windows ( USB detected sound plays and disconnected plays if I unplug but no detection in device manager, I have loaded the HTC ABD drivers, installed HTC manager and Android studio but again no detection) or on a Mac.
Question is, can I reset this phone back to a working state or should I direct the customer back to a HTC service centre?
BTW the phone phone is a European model and currently on 3.
Thanks in advance.
Marc
PC1staid said:
Now, this seems to be a common problem and most suggestions are re flash the firmware using RUU. The first stumbling block I am hitting is the phone is not being detected on any PC that I use, by any cable I use, either by Windows ( USB detected sound plays and disconnected plays if I unplug but no detection in device manager, I have loaded the HTC ABD drivers, installed HTC manager and Android studio but again no detection) or on a Mac.
Click to expand...
Click to collapse
Try another USB cable, and another port on the PC.
Also, go into bootloader, select fastboot (if not highlighted in red already) using vol keys, and confirm with power button. Then see if the phone's serial number is returned with the command: fastboot devices
PC1staid said:
Question is, can I reset this phone back to a working state or should I direct the customer back to a HTC service centre?
BTW the phone phone is a European model and currently on 3.
Click to expand...
Click to collapse
Its not the Euro version. Its US version, hacked to accept Euro software. Due to this, and SuperCID (11111111) its obviously been modified, and HTC won't honor any warranty (if that is what you are asking).
I also wouldn't be surprised if the back cover was replaced (again, voiding the warranty). What does the model number on the back say?
redpoint73 said:
Try another USB cable, and another port on the PC.
Attempted this with 2 PC's, 1 Laptop all running Windows 7 Pro with SP1 64 bit and a Mac. Tried the cable that came with my Samsung S5 ( Not the USB 3 cable) plus 2 other cables that I use in the workshop and the original cable suppled by the customer. Phone not detected in device manager on any of the PC's, however the plugged in and unplugged sounds do play. Mac sit's idoly twiddleing its thumbs...
Also, go into bootloader, select fastboot (if not highlighted in red already) using vol keys, and confirm with power button. Then see if the phone's serial number is returned with the command: fastboot devices
Went into bootloader and fastboot. only option I have to locate the S/N is via show barcodes. the S/N is:- HT444WM04348
Its not the Euro version. Its US version, hacked to accept Euro software. Due to this, and SuperCID (11111111) its obviously been modified, and HTC won't honor any warranty (if that is what you are asking).
I dont think it would be under warranty as customer reckons it is over 12 months old.
I also wouldn't be surprised if the back cover was replaced (again, voiding the warranty). What does the model number on the back say?
Click to expand...
Click to collapse
Shown on the back is OP6B110 M8x
Hope this gives some more helpfull info.
PC1staid said:
Shown on the back is OP6B110 M8x
Hope this gives some more helpfull info.
Click to expand...
Click to collapse
Now that you mention that, I think there may be an Australian variant (OP6B110) which also has the product ID (M8_UL_CA) indicated on the bootloader screen.
Either way, its not the Euro variant; and its been modified by a previous owner (as mentioned).
Any luck getting USB fastboot working? Once you do, do fastboot getvar all, and post the output (delete IMEI and serial number before posting) so we can verify the MID and make sure you are running the right RUU.
exactly the same problem
Hi.. I have also been facing the same problem since today morning. phone completely conked off and not connecting to pc either. the connecting and disconnecting sound is there but device driver error so not installed. pls help... phone model is OP6B100. Bought from US and being used in India
sonalgirdhar said:
Hi.. I have also been facing the same problem since today morning. phone completely conked off and not connecting to pc either. the connecting and disconnecting sound is there but device driver error so not installed. pls help... phone model is OP6B100. Bought from US and being used in India
Click to expand...
Click to collapse
No, its not the same problem. The OP is in a bootloop, which is very different from the screen not coming on.
Folks need to stop saying "same problem", because it really never never never is. Just a minor detail or 2 that is different, makes a huge impact on the condition and the way forward.
Leave the phone on charger for several hours, and then hold power for 30 seconds of so, and see if you can get the screen to come on.
If the screen doesn't come on, there isn't much we can do.
redpoint73 said:
No, its not the same problem. The OP is in a bootloop, which is very different from the screen not coming on.
Folks need to stop saying "same problem", because it really never never never is. Just a minor detail or 2 that is different, makes a huge impact on the condition and the way forward.
Leave the phone on charger for several hours, and then hold power for 30 seconds of so, and see if you can get the screen to come on.
If the screen doesn't come on, there isn't much we can do.
Click to expand...
Click to collapse
Sorry I meant I am also getting the same screen with phone stuck in bootloop amd not moving beyond this screen.
sonalgirdhar said:
Sorry I meant I am also getting the same screen with phone stuck in bootloop amd not moving beyond this screen.
Click to expand...
Click to collapse
"completely conked off" (your previous words) is not a good description of the above. Misleading, really.
Hold the vol down button during the bootloop cycle. Don't let go until you are on the bootloader screen. Then try to connect with fastboot.
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc.. I bought my phone in USA and now using it in UK.
Called HTC and they said they will not accept US phone for repair even though it's in warranty..
tushard007 said:
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc.. I bought my phone in USA and now using it in UK.
Called HTC and they said they will not accept US phone for repair even though it's in warranty..
Click to expand...
Click to collapse
Hi.. Did u find any solution to the problem. The service center here also refused to take a phone bought outside india.
Hi..
Please find attached the result of 'fastboot getvar all'. i had also shared the same with HTCDev team and the reply is as below:
"Hello Sonal
I sincerely thank you for sending us the information that was requested . According to the information you have provided, I was able to identify the reason why the device can not receive updates at this time. For your device to without any problem , it must have all the original software or settings and STOCK.
To begin , let me explain how our devices are distributed to security S -ON to protect your settings and to ensure proper operation. Security on your device has been disabled ( S -OFF) which has allowed the following parameters change at this time prevent the upgrade is installed
cidnum : 11111111 < ---- this parameter will not get your device updates
Here are the options for you:
Option 1 - Return all device settings to their original settings or STOCK. - First you must change the parameters specified as these were originally. Once this is done, now again to contact STOCK install the operating system.At this time, HTC doesn't officially support obtaining S-Off on our devices. Having said that, I'll be happy to take a look at what's going on and at least point you in the right direction. I know this may cause some limitations in the assistance I am able to provide to you but I am more than happy to do what I can to assist you through your issue . We are happy if you contact us about any problems you might, in any part of their development process. .To begin with, the following websites are some examples where we recommend you start your research on S-Off. http://forums.xda-developers.com http://www.androidcommunity.com http://androidforums.com Please note the above web sites are not operated by HTC. We can not validate or guarantee the information contained therein.
Do not hesitate to reach out to us if you have any questions. You can contact us back via email, using the second link listed below (The one at the end of the sentence "To send a reply to this message, please click here"). "
Can you please help with the next steps to get the phone working again.
sonalgirdhar said:
Please find attached the result of 'fastboot getvar all'.
Click to expand...
Click to collapse
Flash the 6.12.401.4 RUU.
See the download in Post #3 of the following thread, and instruction in Post #17 of that thread: http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
sonalgirdhar said:
i had also shared the same with HTCDev team and the reply is as below:
Click to expand...
Click to collapse
Asking HTC for support by sharing info that indicates your phone was modded, was a bad idea. Of course they are going to say "we don't support this" and "return the phone to stock".
No need to go back s-on or change CID. Just run the RUU as I mentioned.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
tushard007 said:
My HTC is having same error after Android 6.0 update.
It's not getting connected to pc..
Click to expand...
Click to collapse
USB connection issues are usually due to issues on the PC, not the phone.
Try a different cable, different USB port (as I suggested in a previous post). Install (or re-install) HTC Sync. You may even need to try a different PC (Win7 and USB 2.0 get the best results).
Also, bear in mind that phone needs to be in bootloader-fastboot mode, for fastboot commands to work. Booted into OS or recovery for adb to work.
redpoint73 said:
Flash the 6.12.401.4 RUU.
See the download in Post #3 of the following thread, and instruction in Post #17 of that thread: http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
Asking HTC for support by sharing info that indicates your phone was modded, was a bad idea. Of course they are going to say "we don't support this" and "return the phone to stock".
No need to go back s-on or change CID. Just run the RUU as I mentioned.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
USB connection issues are usually due to issues on the PC, not the phone.
Try a different cable, different USB port (as I suggested in a previous post). Install (or re-install) HTC Sync. You may even need to try a different PC (Win7 and USB 2.0 get the best results).
Also, bear in mind that phone needs to be in bootloader-fastboot mode, for fastboot commands to work. Booted into OS or recovery for adb to work.
Click to expand...
Click to collapse
@redpoint73 Thank you so much, have been able to update the RUU. Updating apps now
Dear All,
I tried to restore from CM11 and did a sideload of latest amazon bin and that corrupted boot and device wont boot and to complicate the i some deleted the partitions with latest bin so the phone is stuck in Qualcomm HS-USB QDLoader 9008 mode. Please can some one upload image of 32GB version US phone so i can boot this phone. There is no mode adb or fastboot mode as we corrupt. Only way is to use Qualcomm tools to restore partition table and image.
Please someone help with this.
Any help is much appreciated.
Regards
Sudhakar J
@ggow can you help him? @pipataki
I think that is the same problem I had with my first fire phone broken... but I didn't know how to restore it and finally, I left to use as restore any broken component of new one...
If I could do something, tell me... I don't have 32GB to share in Google Drive, but in pipataki.com I can use what I need... the problem is that is a local web server, so the internet speed is the same I have at home... about 1 mega of upload speed (100 kB/second)
http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
Is this what ar you trying to do? ...
Amazon Firephone Stuck in Qualcomm HS-USB QDLoader 9008
Dear Pipataki,
Yes that is what i am trying to do.
1. Is there a possibility of posting partition table and boot only
2. I can arrange for google drive if that will make it easy for you.
I checked in local stores no one has the same phone.
Regards
Sudhakar J
jsudhams said:
Dear Pipataki,
Yes that is what i am trying to do.
1. Is there a possibility of posting partition table and boot only
2. I can arrange for google drive if that will make it easy for you.
I checked in local stores no one has the same phone.
Regards
Sudhakar J
Click to expand...
Click to collapse
I think that if I do a Factory Reset and try to copy and paste the the / dir, maybe you could have it... but the problem is how to copy.
With the shell beeing root user would be possible, I supose...
jsudhams said:
Dear All,
I tried to restore from CM11 and did a sideload of latest amazon bin and that corrupted boot and device wont boot and to complicate the i some deleted the partitions with latest bin so the phone is stuck in Qualcomm HS-USB QDLoader 9008 mode. Please can some one upload image of 32GB version US phone so i can boot this phone. There is no mode adb or fastboot mode as we corrupt. Only way is to use Qualcomm tools to restore partition table and image.
Please someone help with this.
Any help is much appreciated.
Regards
Sudhakar J
Click to expand...
Click to collapse
Do you need only /boot partition or all partittion tree?... I ask you because in my last ROMs, there is no boot.img , all is in a folder... so if you need the boot partition only unzip the rom and you have it, I supose...
I tried this morning to copy all the partition tree... but was inpossible, i have no idea how it could be done... but maybe using the folders of my ROM like partittion items would solve it... (I don't know another way to restore)... if you solve it, let me know... for try to repair the other fire phone broken I have...
Same Here
pipataki said:
I tried this morning to copy all the partition tree... but was inpossible, i have no idea how it could be done... but maybe using the folders of my ROM like partittion items would solve it... (I don't know another way to restore)... if you solve it, let me know... for try to repair the other fire phone broken I have...
Click to expand...
Click to collapse
I have the same problem, trying to change the rom with ADB, never woke up again.
I thing the solution may be with something like this...
http://www.androidbrick.com/ultimat...s-are-unbrickable-qhsusb_dload_qpst_qfil_edl/
http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
I am not an expert, but there seems to be some programs from Qualcomm to flash the entire system. I guess that there must be some program also to extract the system from a working phone...
I will post any news.
gastonfama said:
I have the same problem, trying to change the rom with ADB, never woke up again.
I thing the solution may be with something like this...
http://www.androidbrick.com/ultimat...s-are-unbrickable-qhsusb_dload_qpst_qfil_edl/
http://www.androidbrick.com/unbrick...-have-the-right-kind-of-rom-qhsusb_dload_edl/
I am not an expert, but there seems to be some programs from Qualcomm to flash the entire system. I guess that there must be some program also to extract the system from a working phone...
I will post any news.
Click to expand...
Click to collapse
The problem is that doesn't work sahara protocol to recover... I just try, but sahara fails...
it would work changing the battery and/or screen?...
I had the same thing
I have bricked two phones now trying to get out of this situation.
Under Linux all the Partitions are available for viewing and some are even RW enabled like system and boot etc etc
Pushing via dd a stock system.img and boot.img does not seem to get you out of this "emergency mode" for want of better wording
Sadly the sdcard is NOT RW but is RO and forcing RW only cause the phone to bootloop back to this "emergency mode" so I could not push the the stock update.bin thinking maybe it would automatically install it then reboot.
Since I did have a backup of most partitions using dd I flashed what I could and that blow the fuse so now I get nothing at all from the phone totally dead, not even seen or detected by the PC.....
So the score is 2 - 0 to Amazon so far.
Maybe everyone who's phone is warranted should brick them and send em back to Amazon for repair and keep doing it over and over so they will eventually release the proper tools, firmware and just maybe unlock the bootloader when they are sick of spending $10000's on repairs and shipping. :fingers-crossed:
bigrammy said:
I have bricked two phones now trying to get out of this situation.
Under Linux all the Partitions are available for viewing and some are even RW enabled like system and boot etc etc
Pushing via dd a stock system.img and boot.img does not seem to get you out of this "emergency mode" for want of better wording
Sadly the sdcard is NOT RW but is RO and forcing RW only cause the phone to bootloop back to this "emergency mode" so I could not push the the stock update.bin thinking maybe it would automatically install it then reboot.
Since I did have a backup of most partitions using dd I flashed what I could and that blow the fuse so now I get nothing at all from the phone totally dead, not even seen or detected by the PC.....
So the score is 2 - 0 to Amazon so far.
Maybe everyone who's phone is warranted should brick them and send em back to Amazon for repair and keep doing it over and over so they will eventually release the proper tools, firmware and just maybe unlock the bootloader when they are sick of spending $10000's on repairs and shipping. :fingers-crossed:
Click to expand...
Click to collapse
If i was millionaire, i will buy all amazon fire phone's for 100$, but just who are in warranty. to brick them and send in warranty to [email protected] amazon company budget
ozan2 said:
If i was millionaire, i will buy all amazon fire phone's for 100$, but just who are in warranty. to brick them and send in warranty to [email protected] amazon company budget
Click to expand...
Click to collapse
Ok... That's the problem, you are saying the pure true... If we had the bootloader unlocked at least we could repair by ourselves...
In my case, as not having support of Amazon in my country, I don't have another way that only buy pieces and pray... Because the shipment to send and return to reseller cost the same...
My amazon fire phone is left in the amazon logo
My amazon fire phone is left in the amazon logo, it does nothing more, than there will be a solution. Thank you. Greetings from Venezuela
rafael_79 said:
My amazon fire phone is left in the amazon logo, it does nothing more, than there will be a solution. Thank you. Greetings from Venezuela
Click to expand...
Click to collapse
I have to replace motherboard, (and lower sensors, but these ones is because in the dissasembly broke)... so i think the only solution if is this type of brick is to buy a new moterboard, I hope to receive on monday the sensors, and fire again... but I will not spend more money with this phone...
(the motherboard is about 25$ more or less)
pipataki said:
I have to replace motherboard, (and lower sensors, but these ones is because in the dissasembly broke)... so i think the only solution if is this type of brick is to buy a new moterboard, I hope to receive on monday the sensors, and fire again... but I will not spend more money with this phone...
(the motherboard is about 25$ more or less)
Click to expand...
Click to collapse
I currently have 2 Firephones 32GB unlocked, and I would like to just change the motherboard to get 64GB, so I would like to know where you bought this motherboard at such a cheap price of $ 25.00?
Also I would like to know if it is very complicated or difficult to change the motherboard of the Amazon Firephone?
ulises.rodriguez said:
I currently have 2 Firephones 32GB unlocked, and I would like to just change the motherboard to get 64GB, so I would like to know where you bought this motherboard at such a cheap price of $ 25.00?
Also I would like to know if it is very complicated or difficult to change the motherboard of the Amazon Firephone?
Click to expand...
Click to collapse
in ebay, shipmentt not included... I only say the price without additional suplements like shipment or others (my motherboard is 32 GB)
seller:fine-part-gallery fire phone motherboard
put this in ebay app or via browser, and you have it... now is about 15$+11$(shipment)...
I think the fire is only in 16 or 32 GB, there isn't 64GB
about replacing it will do my cousin, who is the expert in electronik things of my family...
but is a bit complicated, openning first time, the lower sensors crash..
pipataki said:
in ebay, shipmentt not included... I only say the price without additional suplements like shipment or others (my motherboard is 32 GB)
seller:fine-part-gallery fire phone motherboard
put this in ebay app or via browser, and you have it... now is about 15$+11$(shipment)...
I think the fire is only in 16 or 32 GB, there isn't 64GB
about replacing it will do my cousin, who is the expert in electronik things of my family...
but is a bit complicated, openning first time, the lower sensors crash..
Click to expand...
Click to collapse
Fire Phone is avaible in 32gb and 64gb only. Dynamic perspective sensors are problem because are sticked