Alcatel One Touch P310X Android Tablet - Not Opening (hard brick) - Alcatel OneTouch Pop C7 Questions & Answers

I have an Alcatel P310X Android tablet. Here the tech details below:
TECH DETAILS:
alcatel Pop 7 - Full tablet specifications
www.gsmarena.com
Android Version: 4.4.2 (Jelly Bean)
I was using fastboot, ADB tools on Ubuntu Linux. While I was installing custom ROM (CM-13) I removed the recovery file nonintentionally.
Now:
1. adb command not working
2. just opening the fastboot screen.
3. only I see a black screen. There is no initial screen or logo.
I want to install TWRP recovery image over fastboot and after that install CM-13 or any suitable rom.
Can anybody help me to solve this problem?

Related

[Q] ZTE v9 lite tab bood BIG Problem

hello!
I have anew ZTE v9 light tap but i found that it isn't suppor arabic, so tried to install new android
and save old version as backup on sd card using clockworkmod recovery
now new android is not loading only animation image repeated
and Cann't access factory reset menu using Power + (-) i see clockworkmod screen and volume keyes is not working with it
what can i do??
thank you!
Click here to get to ZTE V9 Development
Hi,
it seems to be that your boot.img is faulty.
Put your device in bootloader (fastboot) mode.
Download the ROM which you wanted to install ,again and grab the boot.img and the recovery.img (if there is one)
Open ADB:
Type in: adb devices
adb reboot bootloader
fastboot flash boot.img
When it is complete , type this command in to flash recovery.img (if there is one)
fastboot flash recovery.img
Doesn't matter if your device don't start correctly , you will be able to get in recovery and flash the rom again.

Unbricking Zte Open C (Firefox OS)

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,

Doogee X5 Max Pro Root Recovery OTA

******************Root Recovery Doogee X5 max pro*******************
Your waiting Time IS Now Finished Here is Complete Guide to Root Doogee X5 Max Pro install twrp And More,
Hit :good:
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
Install twrp-
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly, rename twrp to recovery.img
type fastboot flash recovery recovery.img to flash recovery
Type fastboot reboot
Rooting-
Download BETA-SuperSU.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in twrp. Go to Install zip, find SuperSU.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Other Solutions-
i have doogee x5 max-s (i geuss limited editon in algeria ) with mtk6735 . i do evrything and all steps but when i reboot to recovery mode i have ( no command ) in the screen .... how to fix that ? sorry for my ****ty english XD
I had the same Issue but i have found a solution!
After you have flashed the twrp recovery, dont reboot the phone! the "recovery.sh" will replace the twrp on every boot!
Just pull off the battery after flashing, disconnect usb and put the battery back in to the phone.
Now get in to the recovery by pressing volume up and power button together until the select bootmode menue appears.
select recovery with the volume up button and enter with the volume down button.
and now you should be in the twrp main menue.
i hope it works for you too!
greetz from the lizard
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
pitro1 said:
It does not work from step 12, all the drives are correctly installed and windows recognizes the cell, the recovery image is in the internal memory and also in the sd but of the error "can not load Recovery.img". I tried all the tutorials on the net to do root and nothing worked.The flash does not recognize to pass the recovery also the installed drivers because windows recognizes the cell phone.
Click to expand...
Click to collapse
use sp flash tools to flash recovery, scatter also added with twrp
Flash does not pass the file in the download only option, the process does not start. I reinstalled ROM by firmware mode all ok, but the process of passing recovery on command 12 and 13 of the error message. I manually copied the recovery to the sd and internal memory but also from the error. Does not find the file speaks that it is not a command found.
pitro1 said:
It does not work from step 12, "can not load Recovery.img".
Click to expand...
Click to collapse
Don't use Capital R's
fastboot flash Recovery Recovery.img
Code:
fastboot flash recovery recovery.img
Doogee X5 Max Pro - Update 01/16/2017 + TWRP-3-0-2 & SuperSU-v2.79
Working root for Update 01/16/2017
Title: Doogee X5 Max Pro
Listed: 01/19/2017 11:21 pm
ROM Version: ROM Android 6.0
Doogee X5 Max Pro - Update 01/16/2017
TWRP-3-0-2 + SuperSU-v2.79
Use This Version Flashtool
SP_Flash_Tool_v5.1620.00.000
XN Logos said:
use sp flash tools to flash recovery, scatter also added with twrp
Click to expand...
Click to collapse
Until today I could not do root on x5 max pro. In the method below even downloading the twrp when starting with the power + volume down button start with a menu in Chinese and if you start with volume up + power goes in the default recovery mode.
Same as Pitro1 I am on 16.01 update and I cannot install twrp no matter what I try.
I tried x32 and x64. I tried rebooting directly on recovery or first load system and then adb reboot recovery. I tried to format all first (now I lost my Imei and so on lol). I downgraded and updated again. Downgrading works only with 26.12 version. All others are giving me Colorado lines on the screen and nothing else...
OEM unlock, file transfer, adb, fastboot, drivers detection, are all working good. Only I cannot install twrp...
Also I cannot write nvram nor with SN Writer 2.1504 nor with Imei & SN Writer 1.7.2, MetaAP mode fails all the time...
I'm just about to send it back...
How i rooted my Doogee X5 Max Pro
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
i returned the phone as i had no imei anymore.
i got a new one, i did not put any sim or whatsoever, i just unlocked bootloader, and updated to 16.01 version
then i tried to install twrp via fastboot and it did not work, i did it with sp flash tools as advised and removing the battery prior (don't forget to!). it worked !
Stripe_nl said:
How i rooted my Doogee X5 Max Pro
- Unlock Bootloader tutorial in the first post By XN Logos.
- Updated ROM to Android 6 with SP FLASH TOOLS V.5.16.20
- boot phone for 1st start and activate Developer and USB debugging
- Installed TWRP-32x + SuperSu with SP FLASH TOOLS V.5.16.20
Click to expand...
Click to collapse
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Hi. I have tried to root my x5 max pro with flash tools to load TWRP, but it always restarts normally and the TWRP does not come out. I found you and I started to try this method to load the TWRP. Does everything good, unload bootloader and load recovery, but loading the TWRP gives me error .:
Device unauthorized.
This adb's $ ADB_VENDOR_KEYS is nor set; Try adb kil-server if that seems wrong
what I do?
rooting X5 Max pro in Ubuntu 16.04
Hi all, this is my first china phone and I basically bought it only to experiment, I'm a linux power user but this is the first time I 'play' with an android OS.
thanks to multiple guides and posts on this and other forums I'm getting somewhere and learning a lot about how to manage an android OS, I'm sharing a bit of info I unovered about doing this under ubuntu but I'm also stuck and in need of guidance, please help me.
Linux specific issues:
I'm running ubuntu 16.04 LTS, installed fastboot and adb tools from ubuntu repos, with these tools and no other modification to my system I could follow the tutorial on how to unlock the OEM bootloader with adb and fastboot.
accordingly to this post about SP flash tool in linux you might need to blacklist a modem manager module in order for SP flash tool to connect to the phone, you also need to install usb development tools (package libusb-dev) and check through dmesg that your linux OS can actually properly read mediatek usb devices.
After following the above mentioned instructions (both the linux sp flash tool tutorial and the bootloader unlocking howto) I could get SP flash tool linux (multiple version) to see the phone after you connect it while SP flash is downloading the new recovery image and flash it with an ok message.
If you get stuck with a BROM error 1013 remember to start sp flash tool with root privileges.
Phone specific issues:
I can get SP flash tool to flash my phone recovery with an ok message confirmation but the phone keeps rebooting with doogee recovery and not twrp. I'm on the newest stock ROM update (20170116) as of current post date. I've been using 32 bit TWRP images from multiple sources and linux version 5.1620 of spflash tool from their website
so my questions are as following:
1) after reading other posts I think I might have to play with different versions of SP flash tool and TWRP until I get the right combination, I think I might be using 64bit spflash tool for linux to flash a 32bit rom or something like that, can anybody confirm precise version number of the stock rom, TWRP and SP flash tool that worked out for you?
2) should I try to install the whole stock ROM posted in this chinadevices thread before trying to flash only TWRP recovery? please also check the linked thread for multiple custom ROM being ported to this phone, please also note that the full stock rom this poster uploaded (it's in the "all firmware" link) contains another flashing tools with chinese instruction called MultiDownloadTool.
www.china-devices.com/forum/index.php?threads/doogee-x5-max-pro-mt6737-custom-roms.20527/
3) I don't have access to a windows installation right now, but I do have a Win10 VM under Vmware workstation 12 pro, so I could try windows version of sp flash tool, do you guys think that USB passthrough would work?
ibrooks said:
How old is your phone and what build version was it at before you started? Because this doesn't work on mine. Which of the "Android 6" ROMs did you flash to start with as I've tried flashing mine back to an earlier one in case it's something with the later stuff that my phone has come with but they either don't make a difference or they won't even boot.
I tried the method in the first post here and the phone wouldn't even boot (switch on and you get the Doogee logo in silver for a few seconds then it reboots and does the same again). I had to flash the stock ROM from NeedROM to get it working again.
I've tried flashing TWRPx32 and x64 available NeedROM both with SPFlash tools and with ADB. Generally flashing it with ADB from the command line leaves the phone in that boot-loop. If I flash it with SPFlash when you try to boot into Bootloader afterwards you get the Doogee logo in silver for a few seconds then it seems to reboot again on it's own and boot normally - you don't even get the menu to choose Fastboot, Recovery or Normal. From then on trying to boot to the Bootloader gives you the menu but choosing Recovery gives you the standard recovery.
It's almost as if something is overwriting the recovery partition with the original after I flash TWRP onto it.
Anyone got any suggestions about where I might be going wrong or a way around whatever additional security they might have put in there?
Click to expand...
Click to collapse
Same here. May a work around would be finding out the oem commands in fastboot. I have seen a tutorial to get them, but you have to be root: https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/
I search a simple method
Why all so complicate? I am searching for a simple way to root.
For my old Doogee X5, I discovered just
update-ROOT-DOOGEE_X5.zip
Copy the zip to the micro-SD-card
Settings -> Phone info -> Update -> menu "update local" -> choose zip from micro-SD-card.
Start update.
That's all!
Now I search for such a simple solution for my new Doogee X5 MAX pro.
I do not want any methods with "volume down power", because my X5 MAX pro has the menus after "Volume down power" start in Chinese language.
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
This version finally works ! Thank you
Neaw said:
Recovery TWRP x32
http://www.needrom.com/download/twrp-x32-rom/
http://www.needrom.com/category/doogee/serial-x-doogee/x5-max-pro/
Click to expand...
Click to collapse
Hi there,
I just tried the first file you posted, (twrp-x32-rom), and this one works for me after all previous attempts to boot up TWRP failed. Thanks for the link !
What I had tried before:
I have a relatively new X5 Max Pro, which I ordered a week ago. I updated the firmware to the newest version (20170116) using the OTA update function.
Then I tried to flash TWRP using the files from "needrom.com" which seem to have worked on older versions of the phone/firmware, but did not work for the newer versions.
I tried 32bit and 64bit TWRP versions and flashed them with SP flash tool, but when pressing Vol+/Power the phone would not boot into TWRP recovery. Insted, when selecting "Recovery" from the boot menu, the phone would show the Doogee logo in silver, then blink once, then boot up normally. When repeating this process, then phone boots into Stock recovery, indicating that the TWRP I flashed was replaced by stock recovery.
However, I just flashed the recovery.img from "TWRP LATEST" (the first file posted by Neaw) with SP flash tools and was finally able to boot into TWRP. I installed the superSU-zip 2.79 included in the link, and I am now rooted. Once again, thanks for posting this :good:
Greetz, Ollek74
Doogee X5 MAX! SERIUS PROBLEM......
Hello Guys i have a serious problem with my phone.....i have Malware on it and i cant uninstall it or anything alse.....the worst thing is that my phone not responding in any connection except that charging.....i can't have access on my storage cause this is not allowed or gives the choice! i tried everything but nothing nor the usb debugging or anything else please give me your help!!!!

QW09 MTK6572 - Is TWRP Recovery or Upgrade to Android 5 possible?

I have a file for a twrp recovery image 3.5.4 and firmware but I have not been able to upgrade any firmware using the computer spflashtools or flashtool. I rooted with kingroot 4.5 then used terminal to replace it with supersu. Rebooted to fastboot using terminal but would not show up left waiting for device. on minimal adb. Recovery was android guy nothing else you could do. Tried flashify, mobileuncletools changed the recovery to a funos screen but still no twrp. Is Magisk possible on android 4 at all or could I possibly use firmware from another mtk6572 with android 5 or 6? I thought I had all drivers installed computer recognizes it as storage just wont appear as adb. Thank you for any leads
I didn't understand clearly. Do you trying to flash a rom with sp flash tool with watch on fastboot mode? if yes sp flash tool won't recognise the watch. Watch needs to shutted down (turned off) for sp flash tool. (Forgive my English)

Dual Boot Ubuntu Touch and Android Redmi7A Codename Pine

I wanted a Linux and Android in the same Cellphone. About Android, it's a Linux but with difference and it has all the features. Let's know 'how can we boot Ubuntu Touch and Android in the same Cellphone'.
1. First of all we need to unlock the bootloader of our device.
2. ADB and Fastboot drivers must be installed. Or you can download Android SDK Platform tools .
3. USB-Debugging must be enabled.
4. Connect phone with PC via USB. Reboot phone to fastboot mode (Volume-down + Power).
5. Drop the recovery image into the adb folder and open command prompt.
6. Enter the following commands:
Code:
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
TWRP 3.3.1-1
[If you already have custom recovery then just skip.]
7. Reboot to recovery (Volume-Up + Power; release Power when phone turns on, keep holding Volume-Up until you see screen of TWRP). If TWRP asks for PIN, enter the PIN of your unlock screen.
8. Wipe > Cache and System from Advanced Wipe. Format Data > Yes. Now reboot to recovery.
9. Flash firmware and vendor arm64.
10. Flash any Android GSI ARM64-AB. (I flashed AOSP ARM64-AB GO)
11. Flash Ubuntu Touch GSI. It works in arm64 a/ab.
12. Now which one you want to boot. If you want to boot Ubuntu Touch then flash Halium_Boot, if you want Android then Android_Patched_Boot, it's your choice.
Credits :
erfanoabdi (ubport gsi)
nikp123 & YaAlex (arm64 kernel)
Phhusson (AospGo GSI)
TheGame455 (firmware and vendor)
Khushraj Rathod (VoLTE Fix)
VoLTE-Fix for Android
VoLTE is not working in Ubuntu Touch GSI
Ubuntu Touch Passphrase : phablet
Special thanks to Canonical Ltd, ubport and Xiaomi.
Thanks
Is it possible to install only UBuntu Touch in this phone, without Android?
Jazzda said:
Thanks
Is it possible to install only UBuntu Touch in this phone, without Android?
Click to expand...
Click to collapse
What you want, GSI isn't good! It takes data partition.
Some people can not understand dual boot means you can keep both, and if you don't want another then just skip that part and only flash one.
First having a Custom Recovery
1. Unlocked Bootloader of Phone.
2. ADB and Fastboot drivers must be installed on PC/Laptop.
3. USB Debugging Enabled in Phone.
4. Connect phone with PC via USB.
5. Reboot phone to fastboot mode (Volume-down +Power).
Or Open command prompt in adb folder and type :
adb devices
adb reboot bootloader
6. Place the recovery image into the adb folder. Enter the following commands:
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
[Note: If you already have custom recovery then skip above.]
Installation Guide:
1. Reboot to recovery (Volume-Up + Power).
2. Wipe > Cache and System from Advanced Wipe. Format Data > Yes. Now reboot to recovery.
3. Flash firmware and vendor arm64.
Ubuntu Touch
4. Flash Ubuntu Touch GSI.
Android
5. Flash any GSI of ARM64-AB of Android.
6. Flash Boot Image.
Switching OS between Ubuntu and Android : Just keep both the Boot Zip file in storage and flash whichever you wanna boot.
Downloads :
TWRP Recovery
fw-vendor-arm64_pine_11.0.11_GLOBAL
For Ubuntu
Halium_Boot_Pine
Ubuntu Touch GSI
For Android
Redmi7A_patched_boot_11.0.11global_64bit
AOSP ARM64-AB GO
[AOSP GO GSI of Phhusson is working smoothly and takes less space, because it's go-edition.]
I think it's clear now, thanks
fw-vendor 11.0.11 vs 10.2.5, what's the difference and/or whats best?
i followed the steps after reboot the screen is stuck in fastboot mode.where to download hallium boot the link is broken
redmikos said:
i followed the steps after reboot the screen is stuck in fastboot mode.where to download hallium boot the link is broken
Click to expand...
Click to collapse
It's illegal to share kernel without copyright, so there is no sharing buddy, search it somewhere else. These days gpl, gnu has changed their definition. In past you could share without any restriction but not now. So why should I share them and get caught in legal proceedings.
You got it now!
at first thank you very much,are you still working on it? i have problem while record video, actually when i try to open the file, it looks corrupt and i can't run it, can i try to change some setting?sometime it work sometime no, i don t know why

Categories

Resources