[Q] recovery without USB connection? - Fairphone

Is there any way to recover the fairphone if the OS doesn't boot any more and the USB connector is broken (out of the mainboard; irreparable)? I have used the phone with the broken USB connector for about half a year now with an external charger, alternating between two batteries, without any further problems.
This morning when trying to get around the restrictions of an app on the Play Store I backed up my build.prop, made a couple of changes to it ('ro.product.model = Nexus S', and 'ro.product.manufacturer = samsung') and then overwrote the changed file again with the backed up original. Everything worked fine until I turned the phone off. Now the booting process gets stuck on the blue 'Fairphone' screen. I can enter recovery mode and have attempted a hard reset (step 2 of fairphone.zendesk.com/hc/en-us/articles/201134418-How-to-perform-a-Hard-Reset-on-my-Fairphone – unfortunately I can't do step 1) – alas, to no avail, factory reset and cache wipe don't seem to help. Perhaps this is not too surprising if the boot failure is in fact due to some hangup with the build.prop (it could be something completely different as well though, these things may have just happened to coincide).
I'd be really grateful if anyone can help with any of the following (again, all of this with the caveat the USB connector has broken out of the mainboard):
1) Is there any way at all to access the external SD from recovery mode (if so, I could download the Kola Nut installer and see if an update sorts the problem)?
2) Is there some way to check what's wrong with the system from within recovery mode, i.e. have a look at the build.prop (if 1) doesn't work)? Enable ADB over WiFi from recovery mode somehow?
3) Is there any way to get the user data backed up off of the mainboard (say onto external SD) from within recovery mode or otherwise (if everything else fails and I have to get a new mainboard)?

Hey, I#m also interested in a solution. My usb is also broken and I just bought a second Battery and external Charger, a few days ago I flashed the unofficial 4..4.4 Rom and I won't to update it from time to time, so I hope that is possible without a Connection to the PC.
P.S. : Its a shame that the USB Port is so fragil, I think there are many users out there with this problem...

Related

[Q] Strange issue with not charging and not detecting - USB device not recognized

Hello all.
This is more of a solution that I will post, but also a question - why.
So, here's my story.
I purchased an unlocked maguro yakjuux 4.0.1 GSM Galaxy Nexus, after playing around with it, I decided to unlock the bootloader and root it - no big deal. Got an OTA update that upgraded my phone to 4.0.2, however broke my NFC ability, so I decided to take matters into my own hands.
Flashed 4.1.1 JB (Official stock image).
Everything worked fine, until one glorious day it stopped detecting as removable storage. Upon googling, I found that people had similar issues with custom kernels and the "fast charge" USB charging option, however, as I am using the stock kernel, this did not apply to me.
I unplugged the Nexus, brought it over to another computer, plugged it in, and got "USB Device Not Recognized" - "device malfunction" - no media connection (data transfer) and also, it stopped charging as well! It just charged via USB on my other machine, but no longer.
Brought it back to the other machine, and yep, device malfunction, no charge no mass storage removable device.
I thought about trying to mount the storage under my custom TWRP recovery that I flashed along with the Stock JB image, nothing.
Pulled out the power, battery, plugged the battery back in, and then the micro-USB cable. And behold, it shows the "Chaging" image (White battery symbol that you get when you charge via AC/USB power with the phone off). I thought that the situation was fixed.
Restart - plug in - same thing! How the heck is it NOT charging (note, I waited for it to charge with the phone off, so the battery DID charge) over USB power (and AC power) with the phone on?
This lead me to believe that there was something up with the phones software.
I loaded up TWRP, made a backup and then was ready to revert to stock (wipe - factory reset), Then I wiped the cache partition, and the Dalvik cache.
I then thought, what the heck, why not reboot and give it another shot, and it worked! The phone started charging and detecting again!
Why? Why did wiping the caches fix it? And furthermore, what happened?
So to anyone that has a similar issue, perhaps a Wipe of the cahces (both Dalvik and regular cache) might fix it - if you have CWM or TWRP, if not, I think you might have to do a factory reset.

[Q] ROM update fail, cannot flash with Odin

Hi,
My brother's SGH-T989D phone (Koodo / Telus) crashed during an android update. Now, the phone boots to a black screen with the taskbar on top. There is no menu screen anymore. No apps at all. Doing a factory reset via the recovery mode does not change anything.
My PC does not detect the phone. Therefore, I am unable to install a new ROM with Odin. Here are all the infos I have :
1. The phone boots, but there is absolutely nothing except the task bar (I can toggle the wifi and bluetooth on and off, thats it...). There phone says preparing SD storage upon booting. There are no SD card and SIM card.
2. The phone is able to go into recovery and download modes.
3. My PC does not detect the phone. I know the Samsung drivers, Odin v3.07 and USB cable are working properly because I am able to connect my own phone which is also a SGH-T989D.
4. In recovery mode, there is a dead android with a red triangle with an "!" in the background.
5. It used to have the stock gingerbread Koodo ROM, and was probably updated over the air to the newest ICS from Koodo.
6. The phone was never rooted or messed with. I don't think it was ever connected to a computer before.
7. It is not under warranty anymore.
I've spent hours trying to get it recognized by the computer. I've tried putting the ROM on the SD card and applying the update via external storage in recovery mode. I get a message about Signature verification failure.
I've tried cleaning the micro-usb slot. Blowing in it resulted in the computer saying "Unknown device malfunctioned" a single time, which leads me to believe it only did that because some saliva created a short somewhere in there. The connections look clean.
I'm about to throw this phone off the building. What is wrong with it?
**EDIT**
Forgot to mention...the phone does charge when connected to the usb cable.
kamikazee1989 said:
Hi,
My brother's SGH-T989D phone (Koodo / Telus) crashed during an android update. Now, the phone boots to a black screen with the taskbar on top. There is no menu screen anymore. No apps at all. Doing a factory reset via the recovery mode does not change anything.
My PC does not detect the phone. Therefore, I am unable to install a new ROM with Odin. Here are all the infos I have :
1. The phone boots, but there is absolutely nothing except the task bar (I can toggle the wifi and bluetooth on and off, thats it...). There phone says preparing SD storage upon booting. There are no SD card and SIM card.
2. The phone is able to go into recovery and download modes.
3. My PC does not detect the phone. I know the Samsung drivers, Odin v3.07 and USB cable are working properly because I am able to connect my own phone which is also a SGH-T989D.
4. In recovery mode, there is a dead android with a red triangle with an "!" in the background.
5. It used to have the stock gingerbread Koodo ROM, and was probably updated over the air to the newest ICS from Koodo.
6. The phone was never rooted or messed with. I don't think it was ever connected to a computer before.
7. It is not under warranty anymore.
I've spent hours trying to get it recognized by the computer. I've tried putting the ROM on the SD card and applying the update via external storage in recovery mode. I get a message about Signature verification failure.
I've tried cleaning the micro-usb slot. Blowing in it resulted in the computer saying "Unknown device malfunctioned" a single time, which leads me to believe it only did that because some saliva created a short somewhere in there. The connections look clean.
I'm about to throw this phone off the building. What is wrong with it?
**EDIT**
Forgot to mention...the phone does charge when connected to the usb cable.
Click to expand...
Click to collapse
IDK if this will help you. IF the phone isn't rooted or a custom recovery installed I don't believe you can reinstall the ROM. It does say 'signature verification error' so you might be able to turn off MD5 checking before install. It will be in the settings menu if TWRP is used. I don't believe its an option to do if on stock recovery.

HTC 10 unable to flash etc..

Hi All,
My Dad has given me has HTC 10 has the battery drain is crazy, when look at the phone the capacitives back and recent apps were not working only the menu button.
i checked the settings and nothing out of the blue why this was happening, so the first thing i did was factory reset the phone, this didnt resolve the issue.
So i though i would reflash the RUU on his phone but the phone will only show has slow charge on my Windows pc, laptop and chromebook, i cant get it to to pick up in ADB etc...
I also hard reset it too in the boot menu (again even if i load in to boot loader the phone isnt detected ) I have over 10 usb c cables (and these work fine on my HTC U11 and allows mew to go in to debug mode etc.. on that phone)
does anyone know what to do so i can flash it to an old version, his CID is H3G__.001 but i cant find the RUU for this only the HTC__.001 and this fails with incorrect footer etc.. i just also tried installing the update via the sd card and getting the same errors.
regars
Scott
The Capacitive buttons and the charge port are part of the same board. You could have an issue with that board. If the phone isn't rooted, to allow adb over Wi-Fi, you might be out of luck.

Custom ROM will not boot, can't use TWRP, can't use fastboot, can't use Jodin, ARGH!!

Hey all,
My S4 Mini LTE got a bit water damaged. Was booting up fine for a while, but now is not getting past the splash screen (using Ressurection remix v. 6.0), just keeps splashing on and on, and I can't seem to successfully connect to my Mac to fix it.
TWRP is acting weird: not letting me wipe caches ('unable to mount storage') not showing any internal storage (0mb), only showing SD card at 15mb, and some buttons like reboot option are just freezing. It seems to be able to format (with some errors), but then acts the same way after.
On my Mac Fastboot is not showing any devices.
Similarly, I can't get OS X to recognize the phone with android file transfer.
The only thing that seems to recognize it is connected is Jodin, but it gives an error when trying to obtain my PIT!
edit: Heimdall ALMOST seemed to let me flash the kernel and recovery, but then gave some error right at the end.
Might be new motherboard time?!?!
Please help!
Motherboard change is easy
Yeah just replaced it... now power seems to turn off randomly in my pocket and mouthpiece doesnt work... eh probably just buy new phone

Recover files from a Pixel 3 XL that cannot boot anymore

Hello everyone,
I come here because I have a big issue with my Pixel 3 XL.
It's up-to-date regarding the OTA updates i.e. I have the latest firmware installed.
I've never done anything special regarding "tweaking", such as enabling the developer mode i.e. the developer mode is unfortunately not enabled.
I was browsing the Internet and the phone suddenly rebooted unexpectedly. Then it was in a reboot loop. I pressed power and volume down buttons to enter the boot menu.
The boot loop stopped but I was unable to do anything to make my phone boot properly again. In the recovery menu, there is no option to wipe the cache partition.
There should be roughly 400 MB of free space on the phone. I was thinking that maybe this could have been the cause of the issue.
When the phone is off and not plugged to the charger, the percentage of battery decreases. When the charger is plugged, the percentage of battery does not decrease but does not increase either. It seems I cannot charge the phone anymore. Currently remains 13%.
When the phone is off and I press the power button, the Google logo shows up and the progress bar below has just time to appear before the phone vibrates and goes off.
I don't care much saving the phone, but it's extremely important to me to be able to recover the photos it contains (standard DCIM folder).
Most of what I found googleing so far is about wiping the cache partition, but there is no such option on my Pixel 3 XL.
Since the developer mode (USB debugging) was not enabled when the phone was working fine, I cannot use adb to pull files. I can sideload though. As far as I understood, in my situation it is not possible to enable the developer mode.
I've just heard about TeamWin Recovery Project, and still trying to figure out if this can help me.
Could someone please tell me how I can, at least, backup my photos?
Of course the best would be able to boot the phone normally, but really my first goal is to save my photos.
Is there a way to reflash the firmware with the same version, or another version, without losing data, just like what happens on a regular update e.g. when a new Android version is deployed?
Thank you.
magrac said:
Hello everyone,
I come here because I have a big issue with my Pixel 3 XL.
It's up-to-date regarding the OTA updates i.e. I have the latest firmware installed.
I've never done anything special regarding "tweaking", such as enabling the developer mode i.e. the developer mode is unfortunately not enabled.
I was browsing the Internet and the phone suddenly rebooted unexpectedly. Then it was in a reboot loop. I pressed power and volume down buttons to enter the boot menu.
The boot loop stopped but I was unable to do anything to make my phone boot properly again. In the recovery menu, there is no option to wipe the cache partition.
There should be roughly 400 MB of free space on the phone. I was thinking that maybe this could have been the cause of the issue.
When the phone is off and not plugged to the charger, the percentage of battery decreases. When the charger is plugged, the percentage of battery does not decrease but does not increase either. It seems I cannot charge the phone anymore. Currently remains 13%.
When the phone is off and I press the power button, the Google logo shows up and the progress bar below has just time to appear before the phone vibrates and goes off.
I don't care much saving the phone, but it's extremely important to me to be able to recover the photos it contains (standard DCIM folder).
Most of what I found googleing so far is about wiping the cache partition, but there is no such option on my Pixel 3 XL.
Since the developer mode (USB debugging) was not enabled when the phone was working fine, I cannot use adb to pull files. I can sideload though. As far as I understood, in my situation it is not possible to enable the developer mode.
I've just heard about TeamWin Recovery Project, and still trying to figure out if this can help me.
Could someone please tell me how I can, at least, backup my photos?
Of course the best would be able to boot the phone normally, but really my first goal is to save my photos.
Is there a way to reflash the firmware with the same version, or another version, without losing data, just like what happens on a regular update e.g. when a new Android version is deployed?
Thank you.
Click to expand...
Click to collapse
I don't think there is anything you can do without developer mode, but aren't your photos backed up to Google servers at https://photos.google.com?
dcarvil said:
I don't think there is anything you can do without developer mode, but aren't your photos backed up to Google servers at https://photos.google.com?
Click to expand...
Click to collapse
no, I don't synch with the Google cloud.
I've just read that in order to install TWRP, I needed a unlocked bootloader, which is not my case. Unlocking the bootloader would cause my data to be wiped (for security reason it seems). Is that true?
magrac said:
I've just read that in order to install TWRP, I needed a unlocked bootloader, which is not my case. Unlocking the bootloader would cause my data to be wiped (for security reason it seems). Is that true?
Click to expand...
Click to collapse
Unfortunately, that is correct. Unlocking the bootloader wipes the data. I know of nothing you can do.
was your problem resolved?

Categories

Resources