Hello guys,
I tried to update my phone to marshmellow, it got stuck at 95% and after it it entered a bootloop, I thought on just installing a custom recovery and take it from there but when I use fastboot it gives me a Remote: command not allowed error, I have my bootloader unlocked, I am thinking this has to do with not having USB debugging enabled, I can´t access the phone to activate it though. I have also tried to flash lots of stock roms through sd putting them on dload folder on Sds root but it fails right away at 5% it says update install failed, at this point Im not sure what to do... Any ideas?
thanks
Related
I was running CM12 and everything was fine. I received a notification to update to CM 13 and I selected yes. It installed OK, but no GAPPS. I tried everything I could think of to install GAPPS, and kept getting errors. IN my frustrated efforts, something happened to my TWRP and now I only have CM Recovery. I'm trying to reinstall TWRP but my phone is being recognized as a "Marshall London Bootloader Interface" ONLY when in the Fastboot and Recovery mode. I have Huawei Hisuite installed and it recognizes the phone fine when powered on, but as soon as I boot into Fastboot and Rescue mode, it reverts to the MLB interface. I am at my wits end as to how to get my PC to recognize my phone properly when in Fastboot and recovery. I did try removing and reinstalling drivers when in Fastboot, but the Marshall Interface keeps on getting inserted. Any suggestions?????? (I also seem to have erased the SD card that has my original system backup files on it. I tried to flash several downloaded stock ROMs using CM recovery, but they all error out. )
I was finally able to re load TWRP using the Huawei Hi Suite. I flashed Carbon ROM and GAPPS and everything seems to be OK but I still cannot use ADB because the phone is recognized by Windows as a Marshall device ONLY when in bootloader mode and ADB does not find the device. When I connect normally it is recognized as a Mate 2 and it connects normally to Hi Suite. I have no idea what could be wrong, but I have read of other people who have this mysterious "Marshall" device show only up when in bootloader mode. Anyone have any ideas????? Can I go back to stock from here if I don't have a saved recovery image to see if I can fix this???
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
ScoobSTi said:
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
Click to expand...
Click to collapse
I explained what "Marshall Device" is in the first post. I ended up going back to stock (322) and loosing root. I then updated to 5.1 using the SD card. Everything seems to be working OK. Maybe I'll root again and start over when I have more time.
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
Hello guys,
i wanted to upgrade my Ressurection Remix ROM and managed to softbrick my phone. While flashing the software (Flashing system partition unconditionally) TWRP got stuck.
My phone got an unlocked bootloader and i already tried to flash the global MIUI ROM via EDL and also fastboot. The flashing process is successfull but after i restart my phone i'm stuck at the MI Logo with the moving Android Circles for loading.
I let this run for ~6 hours, no progress at all.
I also tried flashing the Global DEV Rom, same as above.
Factory Reset via Recovery Mode (with MI Suite) also didn't do the trick.
I think something with the bootloader went wrong. Any ideas to unbrick it?
I can access Fastboot and EDL Mode, unlocked Bootloader. I also got a TWRP backup with System and Data Partition, but currently only the original Revocery is installed.
Any help is very much appreciated, thank you.
Did you tried using this guide to flash stock firmware/recovery?
http://en.miui.com/a-234.html
Yes, the problem is not to flash the Fastboot ROM, but after successfully flashing the ROM i got stuck at the MI Logo with the loading Android dots
That's weird.. this bootloop usually happens when you flash stock MIUI and still have TWRP installed, can you check if you have stock recovery after fastboot flash?
After i flashed the global DEV ROM i got the stock recovery where i can choose between Wiping Data, switch to MI Suite etc.
Edit: Its not really an bootloop, it just gets stuck there without doing anything
Update: Got TWRP back, now if i want to flash any ROM (doesn't matter if stock/custom) i'm stuck at TWRP saying: "Patching system unconditionally..." it stays there for hours.
Any advice in this case?
guys,, i was facing same problem. I also agree that 8012... status does not matter to unlocking bootloader. I was tried all but fail after granted permission. I was tried daily. after 5 days when I tried with old mi unlock tool I got error at 50%. After that restarted my phone and clicked on settings and in developer menu, I watched i clicked on allow unlock bootloader but I forgot to click on usg debbuging. after clicked it I went for fastboot with old unlock tool and I got success. thankyou.
Try my method you will get success. hit like. stay tune. tandob is here to help you guys.
tandob said:
guys,, i was facing same problem. I also agree that 8012... status does not matter to unlocking bootloader. I was tried all but fail after granted permission. I was tried daily. after 5 days when I tried with old mi unlock tool I got error at 50%. After that restarted my phone and clicked on settings and in developer menu, I watched i clicked on allow unlock bootloader but I forgot to click on usg debbuging. after clicked it I went for fastboot with old unlock tool and I got success. thankyou.
Try my method you will get success. hit like. stay tune. tandob is here to help you guys.
Click to expand...
Click to collapse
That has absolutely nothing to do with the problem mentioned above.
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:
Hi guys been spending all night trying to figure out but seems nothing is working. HELP! I know i can get it to work.
So tried to root my A2017G previously but saw all the horror brick stories so ended up just doing the multiple OTA updates via SDCARD upgrade.zip and finally ended up with OREO BO3 version. running fine except for ridiculous battery meter levels playing up but just kept it charged most of the time.
1) at first I tried to check bootloader unlock status from fastboot. But somehow unable to as fastboot is not there! So i thought maybe fastboot is corrupt (stock recovery options ok / also power plus down gets stuck in FTM mode (easy to reboot with adb command) So unable to check bootloader (i am thinking its probably still locked)
2) so got latest version of TWRP 3.3 something and flashed it --> result in phone black screen but detectable (I assume in EDL mode.) '
3) Tried to flash Nougat B10 EDL with EDL tool (working now but after everything is ready to flash it says"" 13:02:38: {ERROR: WritePort:5164 Could not write to '\\.\COM8', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times""
4) MiFlash unable to read hello packet. But i tried pressing power and connecting quickly and suddenly starts flashing B10 nougat EDL ROM but doesnt complete with a "function: sahara_rx_data:237, unable to read packet header" error. Should I be using a stock rom with Meta-INF folder rather than the EDL version? Also should i be flashing OREO stock rom rather than nougat with MiFlash? or it doesnt matter?
5) tried the DFU tool initially qualcomm and com8 detected but says disconnected. (so its in EDL probably but somehow still disconnected?
So currently
1) trying to let the phone battery run out, though i doubt its any use as i probably bricked it installing twrp without unlock bootloader on OREO.
2) Also downloading Oreo stock rom to try and flash with miflash.
Any help or point to some discussion i missed would be helpful thanks. Just wanna get root and GPS tools running so I can let the kids catch some Pokemon without GOing outside.
Seems like the battery had to run out first. Then it started recharging . After about 5 mins I just pressed power button without up or down. Phone rebooted nicely back into Oreo. PhEW... Then i used a stock 2017g EDL for nougat B10 (7.1.1) and flashed with Miflash by going into proper EDL (used ADB reboot EDL command)
Ok some more small hiccups along the way but being able to access EDl i managed to flash TWRP 3.2.1 and then load it up and flash SuperSU for root.
Now to read the threads on how to get rid of the bootloader unlock screen as well as load in the battery saving scripts.