Hello,
After an unsuccessful attempt to upgrade a firefox OS phone from 1.3 to 1.4, I bricked it
This is the current status :
It is a ZTE Open C. Bought at LDLC. I am not fully sure whether it is a FFOS_EU_EBAYxxx or a FFOS_FR_ZTE_OPENC.xxx
Normal boot: it does not go beyond the firefox logo and gets stuck there
If I boot in FTM mode (volume down and power), I see it when I do fastboot devices.
It does not go in recovery mode any longer, after I did : "fastboot flash recovery recovery-clockwork-6.0.3.3-roamer2.img". Before that, I did manage to go in recovery mode, but none of the zips I tried would work. I would get an unsuccessful signature verification all the time.
In recovery mode - when it was working - I was unable to see the device with adb devices nor fastboot devices.
I do not believe it is rooted.
Help appreciated
If you have bought your device on LDLC (french online shop) it's a FR version.
Try to flash the image provided by ZTE France here (tool is for Windows only) :
http://www.ztefrance.com/downloads/Pack_root_du_ZTE_Open_C.zip
(this is a "rooted" image so that you'll be able to compile & flash your own FirefoxOS afterwards )
[SOLVED] Unbricked (and successful upgrade)
Thanks for your reply!
Actually, we finally managed to unbrick it.
In case somebody else is looking for this, the procedure is detailed here.
In our case, as adb wasn't working, we booted in FTM mode (volume down and power), were we could use fastboot.
Then
fastboot devices
fastboot boot cw_recovery_dp.img
when screen goes black, adb shell /sbin/black_screen_fix.sh. In our case, this does not seem to do anything? we do control c
adb shell /sbin/cw_recovery.sh. This works great.
We get a recovery screen from which we can apply updates without being bothered by 'invalid' signatures
Regards,
Related
Hi there,
i bought a used nexus 7 (2012/1st gen) which only boots into recovery (cwm v6.0.2.3) but doesn't show the menu. Only the cwm logo in the center and the version at the bottom left. (see picture attached)
I can't boot into fastboot (Vol Down+Power). This only leads to recovery again. But as mentioned above there's no content, no menu.
The previous owner told me he tried to flash Cyanogenmod 11 which failed and since then it is stuck in this behaviour.
I'm on ubuntu 14.04 and installed android-tools-fastboot and android-tools-adb.
With adb i can get a shell on the device in recovery mode but don't know what to do from there.
"adb reboot bootloader" doesn't work, the device is not responding
Can anyone help or am i doomed?
Update: I downloaded latest TWPR for "grouper" (2.7.1.1) and tried
" adb shell flash_image recovery openrecovery-twrp-2.7.1.1-grouper.img "
which lead to
" failed with error: -1 "
on step futher...
Update:
I was able to get into the bootloader with this method:
http://forum.xda-developers.com/showpost.php?p=53587109&postcount=74
(thx acotica)
Now i am trying to flash the stock rom of the nexus 7 (https://developers.google.com/android/nexus/images?hl=de)
But i am not able to flash the bootloader. The version now is 4.18 and i can neither downgrade or upgrade. fastboot always gives me an error and won't proceed since it would need the bootloader to be 4.23
any help?
Flashing the stock image didn't work as expected.
Bootloader not working anymore
The device is now stuck at the google splash screen with the little open lock below.
I can't enter fastboot anymore, Power+Vol Down kicks me straight to the screen mentioned above...
The device is not recognized by adb or fastboot anymore...
Any hints how i should proceed?
Hi all,
I've been tracking this thing down all day to absolutely no avail. The main reason I'm after it is I've heard it changes the partition layout to enable a larger /data partition (Essentially turns the phone into a KIS 3).
The download links Comebuy are all completely down it seems, I've even tried using Wayback Machine but that's not coming up with much good either.
Does ANYONE have these tools - as I said, the one for flashing Android to the phone?
Thanks a lot everyone!
Hi.
I have the Open C upgrade tool zip. Is that what you need?
I've uploaded all Open C / Kis 3 Windows flash tool firmwares here. https://drive.google.com/folderview?id=0B9Xj0WNW4yX4b2tOXzFjN1RDRmc&usp=sharing#list
Also see Stock ROMs thread over at MoDaCo for regular firmware updates. http://www.modaco.com/forums/topic/373101-zte-kis-3-zte-open-c-stock-roms/
KonstaT said:
I've uploaded all Open C / Kis 3 Windows flash tool firmwares here. https://drive.google.com/folderview?id=0B9Xj0WNW4yX4b2tOXzFjN1RDRmc&usp=sharing#list
Also see Stock ROMs thread over at MoDaCo for regular firmware updates. http://www.modaco.com/forums/topic/373101-zte-kis-3-zte-open-c-stock-roms/
Click to expand...
Click to collapse
Will these work even if the device won't boot? I can't enable debug mode if I can't get past boot screen.
johnnynmonic said:
Will these work even if the device won't boot? I can't enable debug mode if I can't get past boot screen.
Click to expand...
Click to collapse
Why doesn't the device boot? What happened?
If you can boot to recovery (volume up + power) you can flash a firmware package. If you have Firefox OS bootloader you can boot directly to bootloader with volume down + power key combination and use fastboot to flash/boot recovery image first. I doubt Windows flasher will recognize your device.
KonstaT said:
Why doesn't the device boot? What happened?
If you can boot to recovery (volume up + power) you can flash a firmware package. If you have Firefox OS bootloader you can boot directly to bootloader with volume down + power key combination and use fastboot to flash/boot recovery image first. I doubt Windows flasher will recognize your device.
Click to expand...
Click to collapse
I don't know what happened, it belongs to my friend's daughter. She said she ran it down to 0% battery, then it never would boot up again. It SOMETIMES will boot as far as a welcome screen to set up language, but then says settings failed to start, exchange failed to start. I can't seem to get it into fastboot, but I can get it into recovery. Have tried flashing from sd, and via adb. Any image always fails. Have tried to load stock .zip images and even twmp and cwm, everything fails with either improper signature or footer. So not the end of the world, it's not even my phone, but I'm a chronic fiddler/tinkerer, and the fact that I can't make it work is maddening . Thanks for any tips.
johnnynmonic said:
I don't know what happened, it belongs to my friend's daughter. She said she ran it down to 0% battery, then it never would boot up again. It SOMETIMES will boot as far as a welcome screen to set up language, but then says settings failed to start, exchange failed to start. I can't seem to get it into fastboot, but I can get it into recovery. Have tried flashing from sd, and via adb. Any image always fails. Have tried to load stock .zip images and even twmp and cwm, everything fails with either improper signature or footer. So not the end of the world, it's not even my phone, but I'm a chronic fiddler/tinkerer, and the fact that I can't make it work is maddening . Thanks for any tips.
Click to expand...
Click to collapse
I assume it was running Firefox OS? On Firefox OS bootloader it just hangs on Firefox splash screen when you've booted to bootlader. Do you have proper fastboot drivers installed? ZTE uses generic Google mode for fastboot (18d1:d00d - e.g. USB driver from Android SDK works I've been told).
Stock recovery only allows you to flash matching stock firmware (and packages that are signed with ZTE's private keys). If you can get to bootloader you can flash/boot any recovery (stock or custom) and use it to flash firmware.
KonstaT said:
I assume it was running Firefox OS? On Firefox OS bootloader it just hangs on Firefox splash screen when you've booted to bootlader. Do you have proper fastboot drivers installed? ZTE uses generic Google mode for fastboot (18d1:d00d - e.g. USB driver from Android SDK works I've been told).
Stock recovery only allows you to flash matching stock firmware (and packages that are signed with ZTE's private keys). If you can get to bootloader you can flash/boot any recovery (stock or custom) and use it to flash firmware.
Click to expand...
Click to collapse
Thank you for taking the time to reply. I got it to get to the language selection (where it hangs if I can get it to boot that far). I plug it into the USB, and on the phone select connect to pc via software - then adb was able to detect it as a device. From there did: adb reboot bootloader, and once there was able to use fastboot to install cwm. From CWM was able to flash the EU_FFOS-Android kitkat rom. Works fine now. I see you've spent actually quite a bit of time making different roms and tutorials for theses ZTE phone in various forums. Thanks for sharing your knowledge with the community.
edit: I don't think it had FFOS. vol down+power never seemed to do anything (just perpetual bootsplash). Recovery failed to flash even stock roms (I'm in Thailand, downloaded the stock rom you linked to in another forum, also the stock UK rom. Always returned an error about the footer).
Please help, I need proffessional help.
Android Phone: ASUS Zenfone 2 Laser 5.0 (ROOTED)
Android Firmware: 5.0.2 Lollipop
Aim: To enter into Fastboot mode and Recovery Mode without problems
Situation: Recently installed TWRP Recovery in-app and through software, but when I try to enter in Fastboot Mode (HOLD POWER & VOLUMEUP) or even Recovery Mode (HOLD POWER & VOLUMEDOWN), I just end up in a hanged out ASUS Logo. I can't do anything except pulling out the battery myself and putting it back then booting the device through power button to boot it normally. I don't know if it's the problem with the model, or the phone's system itself, or it's just a bug, or a problem when I rooted my device through ADB.
(Note: When I rooted the device, I wasn't even able to see the blue "FASTBOOT MODE" when I tried it, I only saw the ASUS logo as well.)
For anyone who has any idea on what's going on with my device, please reply and help me. I really want to have the benefits of a rooted phone completly and I'm a new root user so I need assistance.
For anyone who has an idea on what I've done or on what should I do, please help me. Someone told me that I flashed the recovery and locked the bootloader, so it got damaged. If so, would Unlocking the Bootloader (from Wiki.CyanogenMod's Site) help my case?
CrimsonShade09 said:
For anyone who has an idea on what I've done or on what should I do, please help me. Someone told me that I flashed the recovery and locked the bootloader, so it got damaged. If so, would Unlocking the Bootloader (from Wiki.CyanogenMod's Site) help my case?
Click to expand...
Click to collapse
Do you can acesse to twrp recovery on your device
Same problem.....waiting for helping, please
mohamedelkholy said:
Do you can acesse to twrp recovery on your device
Click to expand...
Click to collapse
I think I have "access" to TWRP recovery. However, I can only access it through booting it up from ADB. I used the command "adb reboot bootloader" to boot it to fastboot mode, however only the ASUS screen appears but I treated it as the fastboot mode itself. Then I checked if it was really on fastboot mode through "fastboot devices" and it showed my serial number. I can only enter into TWRP using "fastboot boot twrp.img" . I don't know if I already installed it because although I opened it, I can't do it from the phone (POWER+VOLUMEDOWN)
Ok now boot twrp and then flashamodified zip or cm13 and your phone should eork you dhould to have unlockrd bootloader
Hi to all, i'd re-open this 3d for the same problem. After months I'm trying to re-sleep my ZE500KL. It was in "can't load invalid boot image" loop. I tried to force recovery mode and (wrongly) force to update from update.zip the stock fw stored in the uSD.
Since this time I can't enter in recovery mode more but fastboot only. The problem is that, in spite of the USB drivers are installed, fastboot does not recognize any connected device.
I've run Win 10 pro with a zenbook ux333fn laptop and I remembered android 6 on the phone, the last time I saw it alive.
I've tried also to install twrp 3.1, with no positive results.
Anyone can suggest me any solving way?
Thanks to all
...anybody?
Up.....
sh4d3_ said:
Hi to all, i'd re-open this 3d for the same problem. After months I'm trying to re-sleep my ZE500KL. It was in "can't load invalid boot image" loop. I tried to force recovery mode and (wrongly) force to update from update.zip the stock fw stored in the uSD.
Since this time I can't enter in recovery mode more but fastboot only. The problem is that, in spite of the USB drivers are installed, fastboot does not recognize any connected device.
I've run Win 10 pro with a zenbook ux333fn laptop and I remembered android 6 on the phone, the last time I saw it alive.
I've tried also to install twrp 3.1, with no positive results.
Anyone can suggest me any solving way?
Thanks to all
Click to expand...
Click to collapse
Up...
QFIL or AFT can be the solution.
I have a similar problem, a hard bricked Z00ED (ZE500KL) not able to get into fastboot or recovery.
after reading some thread here an there. that are Processor / Chipset specific flash tools that help flash bootloaders and repartition hard bricked device.
For mobiles with MediaTec devices, there is a tool called SP Flash Tool. I wasted a whole day with it. then understood that Z00ED (ZE500KL) has a Qualcomm Processor MSM8916
Therefore we need a Qualcomm Flasher here (QFIL )
But nos I am stuck with getting firmware for ZE500KL that can be used by QFIL tool, It should have a firehouse*.mbr file that is the programmer (dependent on CPU of the phone) and a rawprogram*.hex file that I don't know where to get from.
Thanks... It seems a bit less wild, but in any case no solving, yet
Up! ...anyone?
Up!
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
inwarse said:
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
Click to expand...
Click to collapse
You downloaded the KENZO (this is not oneplus2! ) TWRP and flashed it on another phone (oneplus2), just normal that it doesn't work and your phone is messed up.
If you can enter fastboot (vol up and power button to boot) you can rescue your phone:
-enter fastboot (vol up + power, while phone is completely off, u can also hold it until you can see "fastboot" written on the screen)
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
If something is not clear, use google, because this is most likely basic stuff you have to know when flashing your phone
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
inwarse said:
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
Click to expand...
Click to collapse
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
wertus33333 said:
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
Click to expand...
Click to collapse
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Oh, the link is dead, sry for that. try this one (GDrive links are up and working).
inwarse said:
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Click to expand...
Click to collapse
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Do you still have TWRP? If yes go to TWRP and shut down the phone there, afterwards you should be able to enter qualcomm mode again.
otherwise you have to try (i think 10s power button will shut the device completely down). You should be able to enter qualcomm mode if the device is fully shut off (your scenario sounds as if the device is not fully shut off when u connect it to the pc).
Just to go sure: You are absolutely sure to have a oneplus2, are you?
inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Could you resolve the issue?
wertus33333 said:
Could you resolve the issue?
Click to expand...
Click to collapse
nope. kept running into issue after issue, so got dejected and gave up.
Hi
I have Acer A501 with unlocked bootloader running OMNI 4.4.4 Tegraowners ROM with ROOT
I was probably unlocking way back using blackthund3r APFlash tool with
Bundle 17: A500 and A501 BL v8 / Thor Recovery 1.7.3 ICS Unlocked / Skrilax Bootloader v8 and Thor Recovery 1.7.3 for the A500 and A501
While booting message says:
Code:
Bootloader Version 0.03.11-ICS (Custom Mode)
I wanted to upgrade to 5.1.1 due to more and more aps not working under 4.4, but I', unable to enter recovery mode
Whenever I try to enter it, either by combination of power vol, or by using Quick Reeboot tool from Google play store ( com.antaresone.quickreboot) , tablet starts to go into recovery, shows message :
Code:
Bootloader Version 0.03.11-ICS (Custom Mode)
Booting recovery kernel imageCustom
then goes black screen and starts to load again from beginning but with normal ROM ...and hangs. Only reboot helps ( and tablet then loads as nothing has happened )
I tried to upload recovery openrecovery-twrp-2.6.3.0-a500.img : using same Quick Reeboot i restarted tablet in fastboot mode, but it's only shows message
Code:
Bootloader Version 0.03.11-ICS (Custom Mode): Starting fastboot USB download protocol
and nothing happens, message stays, and if I connect tablet via USB and do adb devices , no device is connected.
I also tried to enter APX mode and load everything from basics using blackthund3r tool , but even though USB driver is installed ( in device manager everything is ok, and it's shows as "Nvidia APX something"), tools claims no proper drivers are installed. Tried to do so under Windows 10 , and also tried to use VirtualBox WIndows 8
I know this device is old , and tegraowners forum is no longer online, but is there any other way to fix the recovery tool so that I can install newer ROM ?
kubarom said:
Hi
I have Acer A501 with unlocked bootloader running OMNI 4.4.4 Tegraowners ROM with ROOT
I was probably unlocking way back using blackthund3r APFlash tool with
Bundle 17: A500 and A501 BL v8 / Thor Recovery 1.7.3 ICS Unlocked / Skrilax Bootloader v8 and Thor Recovery 1.7.3 for the A500 and A501
While booting message says:
I wanted to upgrade to 5.1.1 due to more and more aps not working under 4.4, but I', unable to enter recovery mode
Whenever I try to enter it, either by combination of power vol, or by using Quick Reeboot tool from Google play store ( com.antaresone.quickreboot) , tablet starts to go into recovery, shows message :
then goes black screen and starts to load again from beginning but with normal ROM ...and hangs. Only reboot helps ( and tablet then loads as nothing has happened )
I tried to upload recovery openrecovery-twrp-2.6.3.0-a500.img : using same Quick Reeboot i restarted tablet in fastboot mode, but it's only shows message
and nothing happens, message stays, and if I connect tablet via USB and do adb devices , no device is connected.
I also tried to enter APX mode and load everything from basics using blackthund3r tool , but even though USB driver is installed ( in device manager everything is ok, and it's shows as "Nvidia APX something"), tools claims no proper drivers are installed. Tried to do so under Windows 10 , and also tried to use VirtualBox WIndows 8
I know this device is old , and tegraowners forum is no longer online, but is there any other way to fix the recovery tool so that I can install newer ROM ?
Click to expand...
Click to collapse
Can you get into fastboot?
turnert said:
Can you get into fastboot?
Click to expand...
Click to collapse
Hi
I think I can't :
I tried to upload recovery openrecovery-twrp-2.6.3.0-a500.img : using same Quick Reeboot i restarted tablet in fastboot mode, but it's only shows message
Code:
Bootloader Version 0.03.11-ICS (Custom Mode): Starting fastboot USB download protocol
and then neither adb devices is not detecting anything ,nor is fastboot command. So i think I cannot get into fastboot but can't be 100% sure
kubarom said:
Hi
I think I can't :
I tried to upload recovery openrecovery-twrp-2.6.3.0-a500.img : using same Quick Reeboot i restarted tablet in fastboot mode, but it's only shows message
and then neither adb devices is not detecting anything ,nor is fastboot command. So i think I cannot get into fastboot but can't be 100% sure
Click to expand...
Click to collapse
Is your tablet rooted?
turnert said:
Is your tablet rooted?
Click to expand...
Click to collapse
Yes, and root is working (quick reboot app requires root and correctly ask for permissions when rebooting tablet to recovery or fastboot mode)