i forgot to say that i can not reach recoverymode anymore…
I’m sorry to hear that. As long as you can still connect using fastboot installing the offical FP2 OTA image should be possible. Have you tried that already?
Hi, Thanks for the help…
what i did: I loaded this file to the sdcard:
and performed a flash from sdcard. Unfortunately after that, the phone showed the withe screen “loading…” for 3-4h befor i pushed the pwd button and the phone whent black and a reboot or recoverymode wasn’t reachable anymore.
I think you or I might confuse recovery/fastboot. Can you still boot the phone into the fastboot mode or the recovery? How does that look like? How did your fastboot command line looked like?
If fastboot still works: Try to install a recovery first
If recovery still works: Try to install the OTA (works with the default recovery) or the Stock Android (needs different recovery).
I’m not sure if the OTAs are complete “full” FP2 software versions (1.1.5, 1.1.6 and 1.1.7 exist) or just partial upgrades. If all fails, I (or others) can send you a recovery that should be able to install the stock Android. But it’s important to know what your phone can still do and how it can be “reached”.
Im not able to reach recovery
Im able to reach fastboot and see a device nr. with
I wold love to get a recovery and install a stock Android.
Try this first:
Installing stock Android + recovery: You can just install the stock Android (no other recovery needed) using the stock build images (they contain recovery.img*, boot and system) using
If all that works, you can try the TWRP:
TWRP-recovery: Can you ask @Moritz | @Max_S (!) for a link (23 days old! Don’t use this one, maybe there is a better one out there!) to his latest recovery?
the link is not by me, but by @Max_S. He ported the TWRP recovery and as far as I know it’s the latest version. I flashed it just 4 days agp and it worked fine on my FP2, so if there is no valid recovery on the phone at the moment, I would second @fp1_wo_sw_updates’s suggestion on putting one there. I believe I mentioned that earlier in this threat somewhere already
I believe, the ota does not include the recovery, so probably flashing the TWRP and then using it to flash the ota stock system is the best way to go…
Good luck and keep us posted!
Hi, and many thanks for the Help here.
If I wold get the .img files - whats the order to flash my phone?
Do i start with the recovery.img or wit the boot.img and what all do i need to flash. Whats required?
fastboot flashall takes care of all that if the files are around and as long as the phone is in fastboot mode and “reachable”.
Well, I don’t think that the order is that important (but I’m not entirely sure). I’d try
$ fastboot flash boot boot.img $ fastboot flash recovery <insert name of TWRP recovery image here> $ fastboot flash system system.img
If that doesn’t work, replace the last command by
$ fastboot -w flash system system.img
or even flash more images as some people have tried with self-compiled versions:
Edit: @fp1_wo_sw_updates If that’s possible, nice! Though I thought
fastboot flashall only works if you have a build environment which was set up properly (with
android-info.txt present and so that flashall knows which device to flash etc.).
[quote=“tphysm, post:46, topic:12032”]
[/quote] i am missing. Does somebody have me an example of that?
I’m still not sure whether
flashall will work even if you have that file. Note though, that if you flash the images one by one, you don’t need that file.
Anyway, in my
out-directory, the file in question only consists of one line:
Mine just contains:
Just a quick terminology question: If you can’t get to recovery mode to perform a hard reset then the phone is not soft bricked but hard bricked right? So do you guys agree to change the title?
Usually I would agree, but in this case apparently fastboot mode is still working, which might enable the user to still recover his phone (by flashing a new recovery and then doing al the rest…). So I would still say it’s softbricked as oppoed to hardbricked, where there is no option left for the user but to send in the device.
But that’s just my take on things
Well, as far as i can tell im able to enter fastboot because i can get the device nr. by typing
fastboot devices and it prints “234F6a0” (what ever that means)
And i realy hope i don’t have to send it back
On the other side, what @paulakreuzer says makes sense, because the only two modes where i see something on the screen is the standard fastboot “FAIRPHONE” - Logo with at the bottom “powered by android” and the Charging Battery animation when plugged to a USB power supply.
On XDA there is a guide for recovering a hardbricked FP1 and I guess it works similiarly to fastboot recovering FP2. (But I don’t really understand most of it, so you be the judge of it.)
Ha. That’s true… ok, then maybe we should change it to something broader. Maybe just “bricked”? That would definitely include all the possible modes If people come here regularly we could also make it a wiki. Or start a new wiki with some simple steps for people who’s phones won’t turn on anymore…
yes i already read that, but the needed binaries aren’t available it seams…
there is a link to the FP1 binaries, but im shure that i can’t use those because the Hardware is total different.
I woldn’t change the topic because the top of the thread is really about softbricked phones…
Why would you want to use any binaries? Are you still planning on flashing your self-built os? I would rather recover your phone with the stock rom to be sure everything works fine again, before you go on and experiment any further…
Did you succeed in restoring the recovery? What’s your current status?