My smarthphone is a Doogee F7. I bought it two weeks ago, just to root and to study. In the last week I rooted it with Magisk, no problems. However in this morning I received a notification I had a Magisk Manager update available, so I updated it. I opened up the manager, and saw there was a newer version of Magisk available also, so I installed that (directly, recommended) after reboot came a softbrick:
"Orange State. Your devices has been unlocked and can't be trusted. Your devices will boot in 5 seconds" occurs infinitively.
So, the USB debugging in my phone was off (yeah, now I know that it must be on ) and the bootloader was blocked also.
I can access the "Android Recovery" screen. Therefore, I tried to "Wipe data/factory reset" and after reboot the system, but it didn't resolve. I tried also "Wipe cache partition" but it did nothing as well.
So on, at fastboot screen I tried to unlock with the command "fastboot oem unlock" but it was not possible:
"(bootloader) Start unlock flow
FAILED (remote: '
Unlock operation is not allowed
')
fastboot: error: Command failed"
I read about test point but my phone doesn't have screw, the cover is glued.
I tried to use ADB sideload as youtube video whose title is "How to Unbrick device using TWRP/CWM ADB sideload [HD]" , but my computer recognize my device as "MTB USB Device", and when I am updating the ADB interface is not recognize even I searching for.
My phone doesn't have TRWP installed, when I rooted I just run TRWP for install Magisk.
I tried to upload images here but I am a new member and I can not until I reach 10 posts.
So, I am wondering about my phone can be recovered. Please, if anyone can help me, I will be very grateful .
Edited: The rom is the original, the stock rom.
maybe this helps...
Download and Install Stock ROM On Doogee F7 [Offficial Firmware]
https://rootmygalaxy.net/stock-rom-on-doogee-f7-offficial-firmware/
It worked, THNX!
CXZa said:
Download and Install Stock ROM On Doogee F7 [Offficial Firmware]
Click to expand...
Click to collapse
I followed all the steps on this site and it worked! Thank You! :laugh::good:
Related
Hello, I'm a little bit new to all this, so any help and detailed instructions are very very helpfull.
So I have Gigabyte GSmart Aku A1 device (MediaTek 6589), I don't know if it's bricked or what but apparently is not working quite well.
When I turn on my phone, it just loads and loads and loads and nothing happens (waited for about 4-5 hours), that was starting to happen after I somehow installed CWM on my device with some tutorial, CWM worked for the first time and after next reboot, it disappeared and stock recovery came back (and the problem with infinite loading screen - only showing logo).
I have ADB drivers installed, SDK aswell, tried to put stock firmware (got it from official site) and in like 1/4 of installation it says:
Code:
symlink: some symlinks failed
After that, I tried to install few versions that I downloaded from that official site, but same error again and again. (I tried to install with SD card and with ADB too. ADB is only working when I go to "apply update from ADB" in recovery. I have also used 2 different types of SD cards.)
That didn't worked either, so I got to some russian forum, and using google translator I downloaded 5-6 types of custom ROM's / Firmwares. That didn't worked either, one time when installing one of those ROM's - it said something about signature..
After that I was trying to install those ROM's with ADB and with SD Cards aswell, but turns out that every single time I get error saying: "Installation aborted.".
I have ofcourse tried to wipe data/factory and to wipe cache too, but nothing helps..
Also, when I'm in ADB console, when I type any command besides adb sideload or adb devices, I get error saying: "error: closed". I cant get into fastboot with adb console.
I really don't know what to do anymore, so any help would be very very appreciated. Thank you for your help in advance, if you need any videos, pictures or something, just tell me.
Edit: When I go to "wipe data/factory reset" in recovery, it says: "Mount /data error.".
BUMP!
BUMP^2!
luuksa said:
BUMP^2!
Click to expand...
Click to collapse
i would look for stock rom in form of full mtkdroidtools backup and preloader drivers for your mtk chipset
and flash it using flashtool (it uses preloader[you can determine if it's available/undamaged by turning phone off and opening device manager on pc and plugging phone to pc if there will be a flash in device manager before the charging starts it will flash ])
Hello,
I am having a big issue with my Sony Xperia Z2 Tablet. I tried to install a new rom on it and I am stuck in the recovery step.
I achieved to unlock the phone, install the fastboot drivers and flash the boot of my device. I can access to the CWM-based Recovery v6.0.5.1 menu but I just can't put the new rom in my /sdcard/xx directory.
I've tried to use the "adb push cm-11-....-windy.zip /sdcard/0/" command line, but I receive the message: "error: device not found".
I then check the command "adb devices" and indeed the device is not listed even though the device is connected. I then tried to reboot the device (after wiping the data/factory reset, cache partition and dalvyk cache, but my tab is not rebooting on anything. I have nothing but the wave background. Once the device got at that stage, the "adb devices" commande shows the following message: CB51xxxxxx unauthorized. It looks like I have a driver problem or something similar, but I tried to install different drivers and nothing worked so far.
So from there, I am lost, I can't boot my system with the original rom and I can't transfer any new rom in the memory to install a new one.
I would appreciate it a lot if anyone could give me some leads on how I could transfer the new rom on my device or at least recover the original sony firmware so that I can use my tablet again.
Thank you for your answers and time
P.S. I also tried the slideloader option, but since it seems to work on the adb program, it's not working either.
Solved
¨Djyinks said:
Hello,
I am having a big issue with my Sony Xperia Z2 Tablet. I tried to install a new rom on it and I am stuck in the recovery step.
I achieved to unlock the phone, install the fastboot drivers and flash the boot of my device. I can access to the CWM-based Recovery v6.0.5.1 menu but I just can't put the new rom in my /sdcard/xx directory.
I've tried to use the "adb push cm-11-....-windy.zip /sdcard/0/" command line, but I receive the message: "error: device not found".
I then check the command "adb devices" and indeed the device is not listed even though the device is connected. I then tried to reboot the device (after wiping the data/factory reset, cache partition and dalvyk cache, but my tab is not rebooting on anything. I have nothing but the wave background. Once the device got at that stage, the "adb devices" commande shows the following message: CB51xxxxxx unauthorized. It looks like I have a driver problem or something similar, but I tried to install different drivers and nothing worked so far.
So from there, I am lost, I can't boot my system with the original rom and I can't transfer any new rom in the memory to install a new one.
I would appreciate it a lot if anyone could give me some leads on how I could transfer the new rom on my device or at least recover the original sony firmware so that I can use my tablet again.
Thank you for your answers and time
P.S. I also tried the slideloader option, but since it seems to work on the adb program, it's not working either.
Click to expand...
Click to collapse
I found a solution, I flashed my tablet with flashtool and a working ftf file. Then I could have my tablet running the original sony rom and finally I could transfer the cyanogen rom into the tab. Everything is running fine now.
Hello everyone,
This is my first post on xda and I've read some of the posts etc and I thought it's time to begin to start questions related to my problem. This will be kinda long post and I'll try to give as much as information from my device specs to what I did to my device up to this point so you guys can understand my problem maybe help me or simply you can say its bricked and I can done with it. And last, I'm kind of newbie with android environment.
As you can see from the title my device is 'Reeder a8i Quad tablet' which is currently in Turkey. Device specs are following:
Uses Intel atom bay trail, Android 4.4.4, TF card (similar to sd)
bootloader title says 'droidboot' and for the recovery there is no install from sdcard or something like that.
There is almost little knowledge with the device and official site is not helping ( I guess they don't care at all )
Some Turkish forums actually got some idea about rooting and flashing stock rom. ( Later in 2015-2016 they released 5.1 for the device and that's all ). Forums actually use old how-to's from reeder support with images how the process done for upgrading android system.
First I try to find some ways to root the device but unfortunately my lack of knowledge and almost no guide for root get me stuck in the first time. I had 4.4.4 android and I was looking at ways to root it. My friend used King Root to root an old samsung phone but later he deleted it and suggested me to use it since I couldn't find any other way. I give it a try and use king root and followed instructions and voila! I had root access on my tablet and quickly installed greenify, root browser, uninstall ( for stock applications and especially google apps ) and later I installed superSU with terminal. Now for the fun part. I did give all these apps root access and deleted stock apps including google apps and 1-2 apps that king root installed while rooting. After deleting google apps I screwed up and keep getting crash reports for some of the services. I didn't know what I did to that point for google so I simply wipe data and wishing reverting all the things. After boot, there is king root app, google services again crushing and tablet looked unstable. I installed root checker which gives me that no 'root access' so I opened king root app and it couldn't root with error messages. I installed gapps for 4.4.4 and google services returned normal. Connected my tablet to pc and use king root again to root. Again device is rooted. Installed same apps, deleted king root apps and entire google apps, services, etc from tablet. Now I got no problems with google, successful root and happy face.
After closing my tablet and opened some day I saw that I don't have root access and king root app again no help at all. Again connected pc, app seems unstable with says my device is rooted and sometimes says not rooted. There was something wrong for sure and again wipe data etc. But now I found reeder tablet stock rom from the internet ( website is closed just today! ) including tons of tools and drivers and roms for other devices including mine. It's not actually site just index so you just go in a folder click and download etc. Installed my drivers, I already had android studio so adb fastboot etc but I did download some quick tools for just for this. I remember my device couldn't open so I just did some things from adb and fastboot and after 1 day work it's opened with 4.4.4. But google kept crashing so I understand that I didn't flash a stock rom entirely. Again root with all the apps and I simply use the device for some apps.
Up to this point I want to call part 1 because after this may be 3-4 months passed and about 2 days ago I started to play with tablet again. Now I installed some network tools to play with. Trying to use some MITM or cookie stealing etc. I used tons of apps including kali linux's nethunter tools which I get from their zip file. Obviously some of them not work and some other are. Still my root is unstable one time it says rooted one time says not. So It kept bothered me but now I don't want to use king root tried to search other ways to replace it with supersu. There is a guide here to use a shell script but it didn't worked so I found an app to replace it. It says done but king root app kept crashing and this point is where I called point of no return ( at least for me ) I downloaded king root app to my pc and tried to root it. It says rooted and now reboot etc. After that nothing changed and still the same. Btw, before tried root I used fastboot to try to open bootloader with boot.img from stock rom but I don't know what it actually does so. Again app is crashing there is no root access so I wanted to install stock rom. There is a guideline for 4.4.4-5.1 for my tablet and there is a tool named 'Manufacturing flash tool v6+' from intel. But I need an OTG for that since I don't have one. Flashing tool uses an xml file. Since I have that from stock rom's folder. I thought give it a try but nothing happened and tool supposed to detect my device but it didn't. At that time I could use fastboot and adb without a problem so I assumed tool got some sort of bug and installed again but result were same. I tried to wipe data and reboot but I got recovery screen with '3E' error. I tried to get into recovery screen to use adb and do something. I desperately used fastboot flash boot boot.img, fastboot flash recovery recovery.img and system system.img from 4.4.4 but not only it failed with the error 'end of footer from /tmp/update.zip not 0xFFFF file exists' but somehow corrupt the device rom and now I was stuck with reeder logo with infinite loop. After that I wanted to give that manufacturing flash tool a try again and same result. I did buy an otg cable for tablet and for my phone which screen destroyed couldn't unlock since touch screen almost not working and usb debug is closed to open that phone as well. There are files from reeder help desk to upgrade it to 5.1. I copied those files to tf card and used otg cable on my keyboard. Guide says press ESC key until bot manager is coming up. There is a screen with bot manager including bios settings. Guideline and tools says it's for upgrading bios so I did those steps and now again recovery mode. Opened manufacturing flash tool with my 5.1 xml but no result so I found something under menu to 'Print flash file cmds' used it and it simply bunch of fastboot commands. I opened fastboot and executed all those commands one by one for myself. Eventually some of them are failed with 'fastboot oem unlock' etc. Since it's changed into flashing unlock which both commands give error from tablet 'unknown command' I followed steps. ( At the end of the post I will give the xml commands from manufacturing flash tool ) After that at I used 'fastboot flash esp_update' provided with esp.zip file successfully. After that 'fastboot flash fastboot droid.img' failed. Following with 'fastboot flash boot boot.img' 'fastboot flash recovery recovery.img' 'fastboot -S 200M flash system system.img' all those commands failed and couldn't install the 5.1 manually.
At this point if I wanted to open my device it simply tries to update bios with the same file ( if tf card inserted ) other than that still at recovery with 3E and adb sideload not working with the error I got above 'end of footer from /tmp/update.zip not 0xFFFF file exists'
I know that my post is long and tried to give as much as information as I can. I just hope device is not completely bricked and there is a way to solve this. Any questions about information about device etc you can shoot I try my best to answer. Thank you for people who are reading this to spare their time.
Manufacturing flash tool xml file commands and success or fail after I executed them in DNX mode ( volume up + down + power at the same time )
fastboot flash osloader "I861B1C_1601001_64_20160115\efilinux-userdebug.efi" - success
fastboot boot "I861B1C_1601001_64_20160115\droidboot.img" - success
sleep - failed
fastboot oem enable_oem_unlock - failed
fastboot oem unlock - failed
fastboot oem wipe ESP - success
fastboot oem wipe reserved - success
fastboot oem start_partitioning - can't remember
fastboot flash gpt "I861B1C_1601001_64_20160115\partition.tbl" - success
fastboot oem enable_oem_unlock - failed
fastboot erase system - success
fastboot format cache - success
fastboot format config - success
fastboot format logs - success
fastboot format factory - can't remember
fastboot oem stop_partitioning - failed
fastboot flash ESP "I861B1C_1601001_64_20160115\esp.img" - success ( After this point I assume device is rebooted and opened a screen which is kinda new with big green 'NORMAL BOOT' text )
fastboot erase keystore - success
fastboot oem verified - success
fastboot format data - success
fastboot flash esp_update "I861B1C_1601001_64_20160115\esp.zip" - success
fastboot flash fastboot "I861B1C_1601001_64_20160115\droidboot.img" - failed
fastboot flash boot "I861B1C_1601001_64_20160115\boot.img" - failed
fastboot flash recovery "I861B1C_1601001_64_20160115\recovery.img" - failed
fastboot -S 200M flash system "861B1C_1601001_64_20160115\system.img" - failed
fastboot continue - failed ( it says success but reboot never happened )
i recently got into playing with andorid , and kinda bootlooped my device,
its htc nexus 9 wifi , i rooted it with wrong version supersu
inject.img
patched.img
then it went into bootloop since im new , and panicked i factory reset it , now its stuck in bootloop and i cant enable developer mode.
can i use odin like solution that can get me in , or what are my options
thanks for reading
rohanzakie said:
i recently got into playing with andorid , and kinda bootlooped my device,
its htc nexus 9 wifi , i rooted it with wrong version supersu
inject.img
patched.img
then it went into bootloop since im new , and panicked i factory reset it , now its stuck in bootloop and i cant enable developer mode.
can i use odin like solution that can get me in , or what are my options
thanks for reading
Click to expand...
Click to collapse
If you can boot into bootloader, you can fastboot flash the images from https://developers.google.com/android/images (or just try running the entire N9F27N script) from your fastboot folder in cmd prompt or the Mac equivalent if you use Apple.
Sent from my Nexus 9 using Tapatalk
usb-debug is not enabled.
the thing is , when i rooted i got locked out then i factory reseted it , but it still is in bootloop,
i am unable to connect with device this is what i see when run the script ,
the cmd prompet say "<waiting for device >"
does it ever happened to anyone , getting locked without getting developer mode > usb-debug enabled , and then flashing factory rom ?
Can you still access TWRP, if it was already on the device.
Flash any custom rom, enable the option and flash stock again (if you want).
If it is stock recovery, sideload an OTA image instead.
https://developers.google.com/android/ota
Manually boot recovery and you shouldn't need usb-debug enabled, I hope.
A bit of research and it is required unfortunately
Edit: You don't need usb-debugging for fastboot flashing.
Also Nexus Root Toolkit might prove helpful to setup drivers on your pc and restore your device to working order.
^^^ It is out of date software, so hesitant to recommend it.
rohanzakie said:
the thing is , when i rooted i got locked out then i factory reseted it , but it still is in bootloop,
i am unable to connect with device this is what i see when run the script ,
the cmd prompet say "<waiting for device >"
does it ever happened to anyone , getting locked without getting developer mode > usb-debug enabled , and then flashing factory rom ?
Click to expand...
Click to collapse
Boot to bootloader and use fastboot commands. Fastboot flash system system.img
Etc.
Use the files extracted from factory image.
rohanzakie said:
the cmd prompet say ""
Click to expand...
Click to collapse
I've definitely had this experience. You can try disconnecting the cable then reconnecting. When that doesn't work, you have to remove all the drivers or at least run through "updating" the Android drivers in hardware settings. You won't actually be updating drivers just re-installing from the PC. Wug's toolkit mentioned above may be your best choice if you don't have TWRP. The toolkit will provide you with an exe called usbdeview which enables driver removal. I didn't mention an OTA sideload because I thought you did need ADB for that. If you can get PC to recognize the device in cmd, then you can fastboot flash images.
Sent from my Nexus 5X using Tapatalk
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com