Hello everyone,
First time here and completely lost with my Coolpad F2.
Tried to flash recovery this way it is described here:
movilesdualsim.com_tema_coolpad-f2-cambiar-recovery-cmw.88858
sorry, cannot put the link to the outside page yet
but after restarting the phone I got the message:
Image signature verify fail
and the start-up logo of the F2. Pretty much this is it, the phone turns off. I can't get into the recovery either as it shows the same message each time I want to turn it on. I guess it's bricked somehow and I must have done something wrong with the tutorial.
Does anybody have any idea how do tackle it?
If some more information is needed just let me know - I'm completely new to this and don't exactly feel there can be a cure for that.
thanks.
anyone?
Try to search on needrom http://www.needrom.com/category/coolpad/page/2/ maybe you can find a solution here.
Maybe you already try to write that recovery, can you factory reset from the recovery?
Hello there, here https://www.facebook.com/tw101.rom.factory
you can find the Recovery and the original firmware to unbrick the phone, to put the phone in fastboot:
1. Press Volume UP + Power
2. Insert cable.
Make sure you've the fastboot driver installed in the drivers.
as reported on http://www.movilesdualsim.com/ you must install the right adb drivers PDAnet
http://junefabrics.com/android/downloadold.php
If you are interested
snake664 said:
Hello there, here https://www.facebook.com/tw101.rom.factory
you can find the Recovery and the original firmware to unbrick the phone, to put the phone in fastboot:
1. Press Volume UP + Power
2. Insert cable.
Make sure you've the fastboot driver installed in the drivers.
as reported on http://www.movilesdualsim.com/ you must install the right adb drivers PDAnet
http://junefabrics.com/android/downloadold.php
Click to expand...
Click to collapse
Hi there Snake, if you are interested, please join this thread
I was forwarded tot this subforum, maybe someone could help me here?
I tried to root the tablet, and thought I had all the steps required to do so. I just rooted my OPO without problems and wanted to do the same with the Asus. As I've said, I thought I had all the steps but saw I missed some things and followed a mix of different tutorials on xda-developers.com. I had downloaded the ASUS v5.0.11 update and the 5.0.11 root. I could get into bootloader with Vol-Up + Power, it opened the android with helmet-bootloader without problems. I used the fastboot commands: - fastboot erase cache - fastboot erase system - fastboot flash update "updatename".zip
there it failed to flash the zip
Then I saw I had to use the fastboot 4.7.3 and not the 5.0.11 one. So I tried to flash that one I found somewhere. Then I installed recovery 4.7.3 and then I got a bricked asus
I have no idea in what order I did things, and I'm sure I did a lot more than I've described. But now I can't get into bootloader with Vol-Up + Power, and when I try to access the bootloader with adb reboot bootloader, I don't see the android with helmet anymore, but just the usb-icon with a red gauge. When I try to start the tablet, it hangs on the bootscreen 'Asus, in search of incredible'.
I want to get into bootloader again so I can play with fastboot-commands again, or if someone knows what to do by the things I've just tried to describe.
I would cry if only I could get into the OS again.
The story begins when I had twrp. i flashed the oneplus_x_oxygenos_3.1.1_community_build usb debugging turned on, and oem unlocking. I was successful, I had stock oxygen OS but I lost twrp in doing so.
retried to install twrp, it did not work, when i tried going to recovery it's stuck on oneplus logo. i tried to fix it with this , did't notice it was for Oneplus 2, so.... hard bricked my phone, i was able to recover with this but i could not install twrp. so i installed the stock recovery MM which works now. OS does not work anymore. for some reason when i try to flash the oxygenos_3.1.1 with stock recovery, it still fails. even when i tried installing a lower version rom.
Can anybody help me? this is my daily driver phone. currently using my nokia feature phone for calls and texts......
what I have:
Stock recovery
nandroid backup that i cannot use because i don't have twrp,
usb debugging turned off,
and oem unlocking off.
can access fastboot, sideload.
no access to OS.
Hatred for Pokemon Go
yay it's alive!!
this worked for me! http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
moderator kindly delete my post. Thanks!
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Exodusche said:
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Click to expand...
Click to collapse
I guess some confusion might have been caused when it was posted on the OnePlus forums (and apparently a quote from a OnePlus rep) that the new build was "compatible" with TWRP. This was later clarified (by a poster, not OnePlus) to mean V41 of the blu-spark TWRP.
Chat with support confirms.
Kashaila said:
Sorry to keep you waiting. I apologize for the confusion. I have just confirmed from the specialist that TWRP is compatible with the new rollout.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...nity-beta-for-oneplus-x.464812/#post-15231909
Perhaps the mistake arises because it is not clear was that whilst TWRP is compatible, you couldn't actually flash the new community build with it! TWRP is only compatible (like you say) AFTER the flash!!
https://tapatalk.com/shareLink?url=...share_tid=3464987&share_fid=3793&share_type=t
[guide] unbrick device
This should help...
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
tjeus said:
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
Click to expand...
Click to collapse
Change computer.
Try with an old windows 7.
Or, try this: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Iirc, it's the same for Windows 10.
Sent from my ONE E1003 using Tapatalk
Himanshu Gusai said:
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Click to expand...
Click to collapse
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache etc.
Then i went to flash sultan(with twrp, can't remember the version but i think it was new one), i had to change update script in .zip file to ONE before i could flash it.
Then when it flashed i tried to restart but it said no system.
I decided not to restart and flash OOS 3.1.3, it flashed and restarted...but it was constantly restarting, logo would show and 1 sec after it would restart, and it stuck in a loop. No recovery, no fastboot...
With a guide above i managed to get it to install recovery and rom, but when booting, after loading android apps, it would just say finishing boot and restart again...
So i had recovery and tried to flash a new recovery but bootloader is locked, and cannot be unlocked because, oem unlock is disabled....
I tried to flash OOS 3.1.3 with stock recovery but after clicking YES for flashing phone turned off. When i tried to turn it on it only shows logo, nothing booting....
And now when i try to use MSM Download tool everything is done but phone still doesn't boot anything at all......now it won't even get to the part with loading android apps.....
Can anyone help?? Could someone please upload recovery.img and system.img that i could put in MSM folder, maybe if it would flash that files it would work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Ovakisan said:
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Click to expand...
Click to collapse
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Exodusche said:
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Click to expand...
Click to collapse
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Ovakisan said:
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Click to expand...
Click to collapse
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Exodusche said:
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Click to expand...
Click to collapse
The problem is that after going through guide, MSM downloader would say that its done, and it wouldn't boot in android, sou you can't get into developers options to enable OEM unlocking. And throught fastboot you can't do anything because its not enabled...
anyway if anyone is reading this that has same issue, just don't stop restarting, this little fu**** just managed to boot into android and i managed to get into dev options(after 3-4 restart, and 1 wipe cache data in stock recovery). after setting OEM unlock to enabled i tried to shut down phone through normal shutdown procedure but it got stuck, but force shut down with button worked and it saved OEM unlocking option on enabled. so i managed to unlock bootloader with fastboot.
So im with stock recovery now, lollipop ROM, should i try to flash OOS 3.1.3 now, or do i have to do something else prior to flashing????
I'm kind of scared now to do anything :'D
EDIT: ok, i ran into problem again -.-
twrp is flashed, latest. now when i try to flash cm13 or sultans cm13 i get this error.
http://imgur.com/a/BSpK1
Hey there,
i was wondering if anyone got an idea how to get root access / TWRP working on a Doogee T6 Pro ?
I don't really find anything online that seems to be working and of course most one-click root tools dont work for China phones.
Anyone got any idea ? The official forums look empty as well.
It looks good
Applesoap said:
Hey there,
i was wondering if anyone got an idea how to get root access / TWRP working on a Doogee T6 Pro ?
I don't really find anything online that seems to be working and of course most one-click root tools dont work for China phones.
Anyone got any idea ? The official forums look empty as well.
Click to expand...
Click to collapse
Some useful tips for rooting MAZE Alpha, perhaps will help you : MAZE Alpha root
Use the method I to patch your boot.img with Magisk-v14 and flash the result image, it must works
Here is the HowTo, have done it 3 times yet:
First, get the correct TWRP Version for Doogee T6Pro ( i dont remember where i got it, i can upload it somewhere if someone have a good location) and the SuperSu Zip.
Then, activate the Developer Options in the Device Settings and Activate the OEM Unlock and USB Debugging in there.
The next Step is to Boot the Device in Fastboot mode. you can either do it by USB with the Terminal Command: "adb reboot bootloader" or you can turn the device of and then reboot it by pressing the Volume Up Button and the Power Button simultanously (quite difficult, didnt Work every Time). You will get to a menue with 3 options: Boot to Recovery, Fastboot and Normal. Switch through these Options with the Volume Up Button and Select it with the Volume Down. Go To the Fastboot Option and Select it.
In Fastboot Mode, plug in the device to an computer and type the terminal command "fastboot oem unlock" (in windows, you have to install the fastboot tools. i dont remember that i had to install them in ubuntu... im not sure). this will wipe the whole data of the device. its important to reboot the device afterwards normaly. otherwise it could happen that you get stuck in an bootloop later ( happend twice to me ) this normal system boot will last much longer then normal, so get a coffee or tea
the next step is do get to fastboot mode again and then send from your computer the command: "fastboot flash recovery twrp-recovery-filename.img". this will flash the recovery.img on the recovery partition.
than go to the bootloadermenue and this time you dont choose fastboot but the recovery option. this will start TWRP
while TWRP is running, you can copy the SuperSU zip to the device with Nautilus or in windows systems with windows explorer. then select "Install" in TWRP and select the SuperSU.zip.
After the installation, reboot to normal system and you are ready with rooting!
if something goes wrong, it can happen that booting to normal system will get you stuck in an bootloop. the last time i could repair the system by booting into recovery (TWRP) and select the Wipe menue and there the Format option. the other time i downloaded the original system from Doogee and flashed all partitions. im not sure if that was necessary.... but who knows :fingers-crossed:
Hi! I just bought a Honor 9 STF-AL00, build: STF-AL00C00B201.
As it is the chinese version, I wanted to rebrand it, so I follow the instructions on https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719.
Unlocking bootloader was successful and as chinese firmware, it did not had a FRP lock.
The first time, rebranding stopped just before the menu.
The second time, I could access the menu and did the install.
But it looks like it did not go as expected because when the phone booted, it did not load TWRP but eRecovery.
So I booted in fastboot, it says phone locked & FRP locked.
I booted once again in eRecovery to download package from server and recovery but it says getting package info failed.
I tried to install stockrom from sd but it didnot work out.
I still have the bootloader code, but now i cant even install TWRP.
Can anyone please help me?
It is a brand new phone, I even havent use it yet and it's already bricked :'(
I install an service full repair stock via dload
http://androidhost.ru/v5
it is working right now.
oblivion2222 said:
Hi! I just bought a Honor 9 STF-AL00, build: STF-AL00C00B201.
As it is the chinese version, I wanted to rebrand it, so I follow the instructions on https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719.
Unlocking bootloader was successful and as chinese firmware, it did not had a FRP lock.
The first time, rebranding stopped just before the menu.
The second time, I could access the menu and did the install.
But it looks like it did not go as expected because when the phone booted, it did not load TWRP but eRecovery.
So I booted in fastboot, it says phone locked & FRP locked.
I booted once again in eRecovery to download package from server and recovery but it says getting package info failed.
I tried to install stockrom from sd but it didnot work out.
I still have the bootloader code, but now i cant even install TWRP.
Can anyone please help me?
It is a brand new phone, I even havent use it yet and it's already bricked :'(
Click to expand...
Click to collapse
You can always re-unlock your phones bootloader again, the key is always same, then flash or boot twrp with fastboot.
Some developers says the command for oreo is: fastboot flash recovery_ramdisk [file name] but I used this: fastboot flash recovery_ramdisk_a [file name]
You even can try to just boot twrp without flashing it to your recovery by simple typing: fastboot boot [file name]
If fastboot can flash twrp, turn your phone off then hold volume up/+ and power button same time and hold them until the state of unlocked warning appears.
You can use dload method or you can use HuRupdater method to flash firmware. You'll find introduction for how to do it.
Just search on xda