Database Info

Updating advice please ! Reroot failure

Hi everybody ! Ill try to keep it simple as I'm sure its covered somewhere but here goes ....
Ive been using my shield portable, rooted, for ages now no problems.
Like many Ive updated it in short ever since nothing whatsoever has worked properly , most annoyingly the screen doing backflips when you go near it and hundreds endless strange updates when rebooting.
Anyway I don't think you or I or any of us want to waste time trying to figure out why its done any of this but I just want to be able to fix it. I guess I'm going to have to start again somehow! its worth noting here that all my backup apps like Helium now don't seem to work.
After the update I of course ReRooted and it appears fine from boot loader , still says unlocked. but upon usage its clearly very confused about whether its rooted or not !
In short its useless. Advice please My kung Fu warriors
May your arrows fly straight and true

I have no idea about the various issues, but I would perform a factory reset, and clear cache and dalvik cache using at least 3 swipes per each function. The method of rooting I recommend is by flashing a zip of SuperSU from a custom recovery menu. CWM or TWRP are both available for the NSP. After flashing SuperSU, when you reboot and go into SuperSu you'll see that it's installed (locked down tighter) as a system app.
Downloads:
SuperSU (latest stable version) v2.65
CWM Recovery Menu (latest version) v6.0.4.4
TWRP (Modified recovery (based on TWRP v2.8.7.0)
Sorry. This is the best I can offer you right now. If this doesn't work I would reflash the stock images of whatever OTA you wanna be on. The images can be found @:
SHIELD Open Source Resources and Drivers. You'll need at least the platform-tools portion of the Android SDK (to use Fastboot to flash from recovery). A user friendly PC app that can basically do all this sort of stuff is Shield Ram v1.1. You might find that easier to use.
Oh and here's the latest Minimal ADB and Fastboot Drivers installer [v1.3.1]
If you need further help, let me know.

Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again

[/COLOR]
Marrhead said:
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
Click to expand...
Click to collapse
Yeah, pretty much the rule is generally "as long as you can still see the screen, it's probably fixable". Sounds to me like your best bet, would be to download the OTA you wanna be on, and flash a new install to your Shield. It's the quickest way from A-B. I'm about 99% sure that this would solve the problem (as long as you re-root it properly). Though if you have your reasons, you can try some of the other things first. You're welcome and let me know how things go!

So where does one get the latest OTA?
cheers

Marrhead said:
So where does one get the latest OTA?
cheers
Click to expand...
Click to collapse
I did link up the main Nvidia page that would lead to the OTA images, but here's a direct link to DL just the OTAs:
Edit: you can get there through the link I included in my previous post: SHIELD Open Source Resources and Drivers. I'm having issues with editing posts, and all sorts of odd **** with the link trying to post a more direct link. It's an Nvidia site, just scroll down to Shield Portable Recovery OS Images (something like that).
Unfortunately there are only Linux and Windows downloads available. I'm not sure what your best option would be, as you have a Mac. You could contact Nvidia support, and see what they say about it. Sorry, but I don't think I can probably help much more than this.When I contacted Nvidia support about a year ago, they were pretty helpful. Hopefully you get this sorted soon. Oh and the OTAs are flashed via a terminal/command prompt. So if you can emulate DOS on your Mac (which I don't see why not...DOSbox? maybe) then that sounds to me like the solution.

Ok , hit another brick wall. Im using a windows computer now, followed all the instructions i can find, and now the bootloader seems dysfunctional.
Ive got adb and fastboot and its recognising the device but once rebooted into bootloader which loads fine, the commands say no device found and nothing works in this mode.
If i hit recovery mode then a little dead android appears! poor little guy.
I tried shield ram but it had same problems, seems to run fine but cant find shield once its in bootloader...
Ive got the image zip of the update i want to flash but no idea if im doing it right- not sure how to use it.
Help!

[Rom][NXH20B] Huawei Watch 2 BT LEO-B09/LEO-BX9 Global Fastboot [Factory Images]

Finally The wait is over
For all of you outside waiting for Global Firmware ROM... here it is:
I have tried it in a LEO-BX9 working flawless... last version received with chinese firmware by OTA was NXH19R
As previously done text is copied from giangishanghai as most are applicable. Thanks @giangishanghai for all the help and the patience :angel
- Make sure you have ADB activated on watch and all files needed on your pc (there are plenty of guides on xda so please search and read it if needed).
- Download 7z file from here : https://mega.nz/#!ozB12QrD
Decription Key
!U6_ZwGwPNUNj3P0PCfpsDtVoGpPG_x1csvR8I1ECOqU
-Edit: You will find 6 .img files:
bootloader, boot, cache, recovery, system, userdata.
-EDIT: In this link you will find whole Recovery software and images if needed:
https://mega.nz/#!YiZkjKyR
Decription Key
!vlUDAZz3mEJsSOpKYgbX5YaITUN59uL3YaVRSOtpVcU
-Edit: Before going to Bootloader, make sure ADB is working and your watch is recognized properly:
Run
Code:
adb devices
Result should be your Watch ID and the word "device" (unathorized or anything else will not work, when unathorized appears make sure to check your Watch for a prompt to authorize something, as it is in Chinese, choose the option with more characters - third one as I remember-)
-Boot the watch into bootloader mode
shut down the watch, press the power button and quickly press twice when the first vibration finished.
-Use the following commands one by one:
(DO NOT flash the bootloader.img)
IMPORTANT!!!: Make sure to run ALL commands below, from the ADB folder, where you have to previously copied all 6 *.IMG files, otherwise you will receive a lot of errors.
For Example if your ADB folder is in C:\adb, the command prompt should be in "C:\adb" so you make a DOS dir command and you see all 6 *.img files plus some ADB files
Then start with following commands one by one in exact order....
fastboot oem unlock (no needed if you already unlock your watch)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
DONE!!
EDIT: ****PLEASE READ IF YOU EXPERIENCE ANY TOUCH ISSUES******Thanks @mcdull
I were able to flash the rom without any issues. HOWEVER...
Originally I suggested NOT to temper with the bootloader so that we can keep the very low level of the device untouched to prevent hard bricking.
But I experienced inaccurate touch screen after applying the ROM. And then I finally convinced myself to flash the bootloader to see if it can fix it.
It is now confirmed that flashing the bootloader will NOT change the model number. So the device model is determined by its hardware. And I can check the FCC of Leo-bx9 in official website, so there must be somewhere in the world selling this BX9 with global rom.
What's more important is that the touch screen is now working perfectly. All part of the screen is now touchable and accurate.
All in all, if you have any touch issue, you may be able to resolve it by flashing the bootloader. Bare in mind that Huawei can be told that you have tempered the bootloader if they dig deep. But I am prepared to give up the warranty for a Global Rom.
Click to expand...
Click to collapse
*****END OF EDIT******
After all this steps your watch reboot and the first thing you will see is a message in English, then you can choose the language you want.
Please don't forget to say thanks and also to @giangishanghai who was really really helpful on remote assistance and also @mcdull who was always promptly replying to help the community

Thank @dr_chch for your great contribution.
I were able to flash the rom without any issues. HOWEVER...
Originally I suggested NOT to temper with the bootloader so that we can keep the very low level of the device untouched to prevent hard bricking.
But I experienced inaccurate touch screen after applying the ROM. And then I finally convinced myself to flash the bootloader to see if it can fix it.
It is now confirmed that flashing the bootloader will NOT change the model number. So the device model is determined by its hardware. And I can check the FCC of Leo-bx9 in official website, so there must be somewhere in the world selling this BX9 with global rom.
What's more important is that the touch screen is now working perfectly. All part of the screen is now touchable and accurate.
All in all, if you have any touch issue, you may be able to resolve it by flashing the bootloader. Bare in mind that Huawei can be told that you have tempered the bootloader if they dig deep. But I am prepared to give up the warranty for a Global Rom.
@dr_chch, grateful if you could include this in your tutorial. Thanks a lot for your contribution that making all these possible.

thank you. It was a pleasure for me to help.
sorry but I am trying to hit thanks button since two days ago with no result.... dunno why...
regards

mcdull said:
thank @dr_chch for your great contribution.
I were able to flash the rom without any issues. However...
Originally i suggested not to temper with the bootloader so that we can keep the very low level of the device untouched to prevent hard bricking.
But i experienced inaccurate touch screen after applying the rom. And then i finally convinced myself to flash the bootloader to see if it can fix it.
It is now confirmed that flashing the bootloader will not change the model number. So the device model is determined by its hardware. And i can check the fcc of leo-bx9 in official website, so there must be somewhere in the world selling this bx9 with global rom.
What's more important is that the touch screen is now working perfectly. All part of the screen is now touchable and accurate.
All in all, if you have any touch issue, you may be able to resolve it by flashing the bootloader. Bare in mind that huawei can be told that you have tempered the bootloader if they dig deep. But i am prepared to give up the warranty for a global rom.
@dr_chch, grateful if you could include this in your tutorial. Thanks a lot for your contribution that making all these possible.
Click to expand...
Click to collapse
done updated thanks!!

Thx all you guys

Will try this out today
I have a LEO-BX9 currently running the Chinese ROM version. I've downloaded the new files. I will try this out later today and post my results as well.
A real huge thanks for getting the ROM and posting the steps. I've been following the forum for a month and it's impressive to see how you guys kept at it until you reached the finish line! Keep up the good work bro's! @giangishanghai and @dr_chch - You guys rock!
Edit: Works flawlessly! Just follow the instructions to the letter. Shiny new English ROM purring like a kitten!

Big thanks, I have the chinese LEO-BX9, works perfectly. the installation only takes less than 2-3 mins.

Will flashing bootloader and re-locking get Android Pay working?

mrgnarchr said:
Will flashing bootloader and re-locking get Android Pay working?
Click to expand...
Click to collapse
hello,
yes it should work.
regards

Hi guys
I flashed the below ROM on my BT version
Leo-L09S 2.1.7_Firmware_general_05014AHH from (Guide: How to flash english firmware to chinese huawei watch 2 sim card variant) on my BT version by mistake....
The watch does not boot at all.. No response when I press the power button cant go into fastboot or anything... its completely dead... Please let me know what can be done...

dr_chch said:
Finally The wait is over
For all of you outside waiting for Global Firmware ROM... here it is:
I have tried it in a LEO-BX9 working flawless... last version received with chinese firmware by OTA was NXH19……
Click to expand...
Click to collapse
Thx for all you do .May I know would you like 2 share a Chinese firmware?
Regards

Done updated,google fit is awesome.Thx dr_chch.

I'm trying to do this, but my Huawei Watch 2 is being recognized as a MTP device and wont appear under the device list when I type "abd devices". How do I fix this? Thanks.
---------- Post added at 02:44 PM ---------- Previous post was at 02:21 PM ----------
So, somehow I made it work. But I didn't do the commands properly and now the watch seems to be bricked. Is there any way I can bring it back into fastboot mode so I can flash the image correctly?
---------- Post added at 02:53 PM ---------- Previous post was at 02:44 PM ----------
Managed to get into fastboot and it seems to work fine. Thank you

What is the difference between this and stock?

devilsden said:
Hi guys
I flashed the below ROM on my BT version
Leo-L09S 2.1.7_Firmware_general_05014AHH from (Guide: How to flash english firmware to chinese huawei watch 2 sim card variant) on my BT version by mistake....
The watch does not boot at all.. No response when I press the power button cant go into fastboot or anything... its completely dead... Please let me know what can be done...
Click to expand...
Click to collapse
I have the same problem :crying: , anyone can help ?? thank so much

Black screen after flash bootloader
Hi Friends,
I tried the installed the first 6 file but it stuck at fastboot page, I restart several times but still not help.
After bootup it goes to fastboot mode.
then I tried to flash the bootloader to see whether it could help, but it turns to black screen.
totally no response , only a black screen, no vibrate holding the power button.
please help !!
thank you for any advice!

[Rom][NWD1.170711.002] Huawei Watch 2 BT LEO-B09 Chinese Fastboot [Factory Images]
I finally have uploaded the Chinese version of the Factory Images, and here is the link:
https://www.jianguoyun.com/p/DRcrvN0Q3O-HBhjeiTQ (The file is currently under transmission by the time of this post. It should be available within hours.)
On download completion, find the .exe file in the zip archive and open it with any compressed file manager, where you will see several .img images. Flash them right onto your watch following the instructions on https://forum.xda-developers.com/wa...09-leo-bx9-t3616779/post72542838#post72542838 with ADB and FASTBOOT tools.
It works quite perfectly on my watch. Nevertheless, I am not responsible for any possible damages.
Go check it out! @dr_chch

Yonghao Liu said:
I finally have uploaded the Chinese version of the Factory Images, and here is the link:
https://www.jianguoyun.com/p/DRcrvN0Q3O-HBhjeiTQ (The file is currently under transmission by the time of this post. It should be available within hours.)
On download completion, find the .exe file in the zip archive and open it with any compressed file manager, where you will see several .img images. Flash them right onto your watch following the instructions on https://forum.xda-developers.com/wa...09-leo-bx9-t3616779/post72542838#post72542838 with ADB and FASTBOOT tools.
It works quite perfectly on my watch. Nevertheless, I am not responsible for any possible damages.
Go check it out! @dr_chch
Click to expand...
Click to collapse
Hi, I flash your images, everything works normally expect notify. When notify appears on phone, there is no vibrate and no sound on wear, just notify card shown silently.
My wear had global version system, but Google Map gave a wrong location, so I try China version.
I use light flow to test notify. When I open option "silence phone while wearing watch", phone doesn't sound too but still vibrate. If I close this option, phone sound and vibrate. But watch always doesn't action.

Yonghao Liu said:
I finally have uploaded the Chinese version of the Factory Images, and here is the link:
https://www.jianguoyun.com/p/DRcrvN0Q3O-HBhjeiTQ (The file is currently under transmission by the time of this post. It should be available within hours.)
On download completion, find the .exe file in the zip archive and open it with any compressed file manager, where you will see several .img images. Flash them right onto your watch following the instructions on https://forum.xda-developers.com/wa...09-leo-bx9-t3616779/post72542838#post72542838 with ADB and FASTBOOT tools.
It works quite perfectly on my watch. Nevertheless, I am not responsible for any possible damages.
Go check it out! @dr_chch
Click to expand...
Click to collapse
Hi friend!I'm a Chinese Huawei Watch 2 User,do you have the LTE version Chinese Factory Image?I spend a lot of time to find it.But I falied.By the way,Are the LEO-B09S and the LEO-DLXX the same model?My device is LEO-DLXX,if I got a LEO-B09S Chinese Factory Image,can I flash it?
Thanks a lot!

CallMeEggLeader said:
Hi friend!I'm a Chinese Huawei Watch 2 User,do you have the LTE version Chinese Factory Image?I spend a lot of time to find it.But I falied.By the way,Are the LEO-B09S and the LEO-DLXX the same model?My device is LEO-DLXX,if I got a LEO-B09S Chinese Factory Image,can I flash it?
Thanks a lot!
Click to expand...
Click to collapse
I tried the international image on a LEO-DLXX, works fine, but without the SIM capabilities (4G, calls and etc), and during the boot there is a message about being using a different operating system. I suppose you'd get the same with the Chinese version.

OnePlus One softbricked

I never thought that this would happen, especially after 6 years of being an ardent flashaholic but here I am like another noob requesting for guidance.
So it started a few days back when the Flashaholic in me wanted something to divert my mind from the monotonicity of a good ROM.I was using "[8.1.x][WEEKLIES] CarbonROM | cr-6.1 [bacon]" Rom on my 3 year old bacon happily when I decided to try "Crdroid ROM for OnePlus ONE crdroid-4.6".
As mentioned in the instructions I followed the steps to each word i.e. wipe,flash rom and then gapps (using modded twrp-3.2.1-K2-bacon.)and the ROM booted fine.I setup it as usual post boot however I faced few reboots which made me doubt myself so i thought of reflashing the same ROM again but the butter fingers got the best of me and while selecting partitions to WIPE( I guess) I selected some incorrect partition and after the flash my phone went into bootloop..
I tried to boot into recovery but I wasnt able to so but I knew I could boot into recovery using Fastboot so I reflashed the recovery while in fastboot mode and ran fastboot boot TWRP.img as I wasnt able to boot into recovery with VolumeDown+Power.I tried to fetch the nandroid backup but to my astonishment it was gone and my /data partition was wiped clean.I blame myself as I must have done something wrong as I was panicked.
Since then(last sunday)my phone has been in bootloop and doesnt start in recovery unless I boot recovery from fastboot. I have spent countless hours to fix it and the things I have tried already are mentioned below
1)Flash Stock rom (CM11,CM12,CM13)
2)Erase and flash persist.img
3)Flashed CM13 snapshot or bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip followed by RR 5.8.5 ,RR 6.0 ,Carbon rom 6.1 and c-droid 4.6
4)Flashed coloros and then stock rom(CM11,CM12,CM13) or RR 5.8.5 ,RR 6.0 ,Carbon rom 6.1 and c-droid 4.6
I have gone through this awesome guide ultimate-answer-to-bacon-flavored- by @Timmmmaaahh ,other noob friendly guides indexes , compilations ,threads on softbrick and hardbrick topics and used almost every tool created for one plus one.
I have ruled out below
1)Volume button not working as I can boot into fastboot fine using VolumeUp+Power button
2)Battery not working as my phone can stay in fastboot for pretty much a day with 50% battery or bootloops throughtout the day
I am really out of my depth and I am trying to find where I had kept my nandroid backup on Laptop/Drive but I dont think even that can help me now.I have lost a lot of precious and Important data due to my panicking and wouldnt want to lose my phone so any help and guidance would be really appreciated.
Hopefully I am posting in the correct place and havent breached any XDA rules!Aplogies in advance if I have

you are sure, that you have flash thr TWRP and not only load TWRP via sideload into the ram?
please post the command, which you have send to the phone

So I use below command to install the twrp from fasboot
fasboot flash recovery <path/twrp file>
Also I've tried to flash twrp in recovery from twrp by selecting image file option but it doesn't boot into recovery ever
I've tried twrp 2.7,2.8,3.0,3.1 and 3.2 as well on every rom that I've flasher given the compatibility.
to boot into recovery as it's not accessible I use below command
Fastboor boot <path/twrp file>

Stupid thing it seems but try different micro usb cable

vedanth123456 said:
So I use below command to install the twrp from fasboot
fasboot flash recovery <path/twrp file>
Also I've tried to flash twrp in recovery from twrp by selecting image file option but it doesn't boot into recovery ever
I've tried twrp 2.7,2.8,3.0,3.1 and 3.2 as well on every rom that I've flasher given the compatibility.
to boot into recovery as it's not accessible I use below command
Fastboor boot <path/twrp file>
Click to expand...
Click to collapse
Okay, let's optimize your environment first. Make sure the path to your adb is c:\adb (don't flash stuff like "c:\users\dinky doodle\my awesome downloads\android shizzle\recovery manizzle"). Use the amazing 15 seconds adb installer and let it install the drivers as well. @kallum7 makes a good point, do try that.
Use the TWRP recommended in my guide and follow the clean flash steps (including CM13 step again).
More importantly: check md5 hashes on all your downloads. You really want to avoid flashing a corrupted recovery download. Only continue flashing ROMs once you have a stable TWRP installation going. If it's not properly booting to TWRP, do not bother flashing anything else.
When successfully booted in TWRP, make sure MTP is enabled under mount and connect it to your PC. Browse for possible backups via your computer. If you can't find any, you've probably wiped internal memory. If you didn't make a copy to your computer, the data is most likely gone forever (sorry).
Panicking is indeed a bad idea, we've all been there and it's an excellent learning process (you'll appreciate your failures later, lol). It's better to work step by step slowly, make sure you read everything thoroughly. When in doubt, just post here and we'll follow up. We'll get there, don't worry.
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
Oh and rename the recovery file to recovery.img and place it in your adb folder to avoid any complications. Less = more!

Because I had bricked my phone a few months ago and I changed my USB cable and it worked perfect

kallum7 said:
Stupid thing it seems but try different micro usb cable
Click to expand...
Click to collapse
Thanks mate..I did try that but it didn't endure fruitful results

Timmmmaaahh said:
Okay, let's optimize your environment first. Make sure the path to your adb is c:\adb (don't flash stuff like "c:\users\dinky doodle\my awesome downloads\android shizzle\recovery manizzle"). Use the amazing 15 seconds adb installer and let it install the drivers as well. @kallum7 makes a good point, do try that.
Use the TWRP recommended in my guide and follow the clean flash steps (including CM13 step again).
More importantly: check md5 hashes on all your downloads. You really want to avoid flashing a corrupted recovery download. Only continue flashing ROMs once you have a stable TWRP installation going. If it's not properly booting to TWRP, do not bother flashing anything else.
When successfully booted in TWRP, make sure MTP is enabled under mount and connect it to your PC. Browse for possible backups via your computer. If you can't find any, you've probably wiped internal memory. If you didn't make a copy to your computer, the data is most likely gone forever (sorry).
Panicking is indeed a bad idea, we've all been there and it's an excellent learning process (you'll appreciate your failures later, lol). It's better to work step by step slowly, make sure you read everything thoroughly. When in doubt, just post here and we'll follow up. We'll get there, don't worry.
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
Oh and rename the recovery file to recovery.img and place it in your adb folder to avoid any complications. Less = more!
Click to expand...
Click to collapse
Hi mate,So I pulled an all nighter yesterday and was somehow magically able to boot in TWRP.I don't remember what I did but I booted into TWRP 2.8.7.0 and the first thing I did was check if any nandroid backup was there but I was disappointed to see my /data with free 55326 MB also no backups on my drive.All my data is gone and I can't curse myself enough for that,moving on so I did manage to gather my sense and flashed TWRP 3.2.1-K2 and flashed RR-O-v6.1.0 but the phone goes into boot loop again and again.
Since then my phone is displaying some weird behavior so if I unplug my device and start my phone the phone won't boot and wont go past oneplus one splashscreen so I thought my battery is gone but if I can go in fastboot mode or TWRP mode while being plugged in and unplug my device but my phone wont die,it'll be in the respective mode for ages.
I do have a clean setup (K:\oneplus\adb\) that's how I stayed away from this mess since ages but I guess I got too cocky.
I have religiously followed your thread and it has helped me a lot so once I am home I will check the TWRP part again and get back with the results.
Once again..thanks for your guidance.

vedanth123456 said:
Hi mate,So I pulled an all nighter yesterday and was somehow magically able to boot in TWRP.I don't remember what I did but I booted into TWRP 2.8.7.0 and the first thing I did was check if any nandroid backup was there but I was disappointed to see my /data with free 55326 MB also no backups on my drive.All my data is gone and I can't curse myself enough for that,moving on so I did manage to gather my sense and flashed TWRP 3.2.1-K2 and flashed RR-O-v6.1.0 but the phone goes into boot loop again and again.
Since then my phone is displaying some weird behavior so if I unplug my device and start my phone the phone won't boot and wont go past oneplus one splashscreen so I thought my battery is gone but if I can go in fastboot mode or TWRP mode while being plugged in and unplug my device but my phone wont die,it'll be in the respective mode for ages.
I do have a clean setup (K:\oneplus\adb\) that's how I stayed away from this mess since ages but I guess I got too cocky.
I have religiously followed your thread and it has helped me a lot so once I am home I will check the TWRP part again and get back with the results.
Once again..thanks for your guidance.
Click to expand...
Click to collapse
This is weird I just restarted my phone to see if it magically starts but it went into bootloop(displaying splashscreen not boot logo) in contrast to earlier when it died instantly when not plugged in also I can't boot into my recovery now!
Once I am plugged in and the phone is on bootloop and if I hold the volumedown+Powerkey it boots into TWRP properly..
This is just weird and I havent seen this behavious in the past three years of using my old lovely bacon

Try using the color os toolkit https://steemit.com/oneplus/@delusionalgenius/how-to-unbrick-oneplus-one-bacon and even though it says do not use if it is soft bricked use it this helped me

Sorry for getting back rather late (again). I'm in the middle of organizing an event and it's leaving very little XDA time. Anyway...
Isn't a hardbrick tutorial kinda agressive? I mean, I've used it before, and it's excellent, but then my device was actually hardbricked. I'd rather go for the 'back to stock' method first, setting the system back to CM13, which is a much better base for further flashing compared to ColorOS.
@vedanth123456 if you didn't take any action yet then I suggest following this thread (skip step 4!!).
The deal is to flash all images from fastboot. This will – naturally – wipe every single partition on your device!
I suggest doing the fastboot flashing manually (copy paste each command one by one) to avoid your device getting its bootloader locked. You DO NOT want to lock the bootloader on a OnePlus One if you ever wish to unlock it again.
When you successfully booted CM13, go though its initial setup, [disable recovery protection in system or developer settings] (it's been so long since I've experienced this process that I'm not sure if this option was present in CM13; if you can't find it, don't mind), get back to fastboot mode and flash K2 TWRP. First thing to do at this point: create a full nandroid backup of your working CM13 setup and copy it externally. ROM flashing should now be successful. If not, I'm afraid your hardware is failing. Do try several ROMs.
Don't forget to check those md5 hashes!
By the way, your /data is supposed to be empty after a factory reset. /data merely contains settings and app data (user added information). Backups and user media go to the /sdcard partition, which is known as internal memory. If I may suggest a ROM, go for CrDroid. It's more stable compared to RR, it's still actively developed and it has similar features.

Timmmmaaahh said:
Sorry for getting back rather late (again). I'm in the middle of organizing an event and it's leaving very little XDA time. Anyway...
Isn't a hardbrick tutorial kinda agressive? I mean, I've used it before, and it's excellent, but then my device was actually hardbricked. I'd rather go for the 'back to stock' method first, setting the system back to CM13, which is a much better base for further flashing compared to ColorOS.
@vedanth123456 if you didn't take any action yet then I suggest following this thread (skip step 4!!).
The deal is to flash all images from fastboot. This will – naturally – wipe every single partition on your device!
I suggest doing the fastboot flashing manually (copy paste each command one by one) to avoid your device getting its bootloader locked. You DO NOT want to lock the bootloader on a OnePlus One if you ever wish to unlock it again.
When you successfully booted CM13, go though its initial setup, [disable recovery protection in system or developer settings] (it's been so long since I've experienced this process that I'm not sure if this option was present in CM13; if you can't find it, don't mind), get back to fastboot mode and flash K2 TWRP. First thing to do at this point: create a full nandroid backup of your working CM13 setup and copy it externally. ROM flashing should now be successful. If not, I'm afraid your hardware is failing. Do try several ROMs.
Don't forget to check those md5 hashes!
By the way, your /data is supposed to be empty after a factory reset. /data merely contains settings and app data (user added information). Backups and user media go to the /sdcard partition, which is known as internal memory. If I may suggest a ROM, go for CrDroid. It's more stable compared to RR, it's still actively developed and it has similar features.
Click to expand...
Click to collapse
Hi mate
Apologies for not acknowledging your message and not replying back earlier. I've been traveling using a spare phone and things just aren't the same on it.
To give u an update, I tried the steps mentioned in the link (which I had tried previously as well) but the phone didn't boot. Same bootlooping and issue with the twrp.
So I went through other forums and links and finally found an exe that worked.!!!!!! So the exe seems to be an modified version of the one mentioned in the hard brick method and has been created by someone else (NOT ME!!)
My phone after many moons has booted and its on the good old cyanogen CM 11.0 XNPH44S. I've tried numerous roms on this bad boy but there is some beauty in the simplicity of the good old roms.
My phone battery is charging pretty slowly and wifi is not turning on so I'm still tensed but the fact that it booted is a small victory. I would want to upgrade to a stable rom once my phone is charged and not displaying erratic behavior so I'll wait for a day and see how it works but I'll want to upgrade to a slightly latest rom probably not a battery hogging one.
I believe I'll have to first install an old twrp followed by nandroid backup(save on every goddammed devices I own), then some CM snapshot and finally the rom but please can you confirm and suggest.

vedanth123456 said:
Hi mate
Apologies for not acknowledging your message and not replying back earlier. I've been traveling using a spare phone and things just aren't the same on it.
To give u an update, I tried the steps mentioned in the link (which I had tried previously as well) but the phone didn't boot. Same bootlooping and issue with the twrp.
So I went through other forums and links and finally found an exe that worked.!!!!!! So the exe seems to be an modified version of the one mentioned in the hard brick method and has been created by someone else (NOT ME!!)
My phone after many moons has booted and its on the good old cyanogen CM 11.0 XNPH44S. I've tried numerous roms on this bad boy but there is some beauty in the simplicity of the good old roms.
My phone battery is charging pretty slowly and wifi is not turning on so I'm still tensed but the fact that it booted is a small victory. I would want to upgrade to a stable rom once my phone is charged and not displaying erratic behavior so I'll wait for a day and see how it works but I'll want to upgrade to a slightly latest rom probably not a battery hogging one.
I believe I'll have to first install an old twrp followed by nandroid backup(save on every goddammed devices I own), then some CM snapshot and finally the rom but please can you confirm and suggest.
Click to expand...
Click to collapse
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.

Timmmmaaahh said:
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Click to expand...
Click to collapse
Try bacon root toolkit you can perform most of the things very easily.

chineel said:
Try bacon root toolkit you can perform most of the things very easily.
Click to expand...
Click to collapse
Hey man, thanks for pinching in. I'm personally not a fan of these toolkits as one can accidentally lock the bootloader and I prefer manual style because it's educational and you see more of what's going on. It's like I preferred DOS over Windows 3.11 back in the day. That's pretty much the same, right?... ?

Timmmmaaahh said:
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Click to expand...
Click to collapse
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?

vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------
vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do

kallum7 said:
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
Click to expand...
Click to collapse
Mate ,can you please help me with the link ?
I know I can google it but I just dont want to take chances anymore

vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
I'd hate to say I told you so ?
Don't worry too much. The cool thing about flashing with Android is that there's always other ways to get to a working system. Plus, having a fizzled up system is how you'll learn the most about how this all works. You'll be a pro in no time. I personally got seriously into troubleshooting with a hard bricked OPO that had a wasted flash chip. Believe me when I say that's a whole other world of pain.
One question: did you wipe system/data/caches between the CM13 and the crDroid flash? That's kind of important. It would also be useful to mention the versions of everything.
I have no first person experience with broken EFS partitions but according to what I've read you'll indeed have to get ColorOS running. You could try wiping everything again and flash CM13 to see if that boots fine (with working connectivity) but I'm afraid you'll have to go through the whole works: wipe all, flash or fastboot flash ColorOS, get it running (verify IMEI), flash TWRP and backup EFS (MAKE AN EXTERNAL COPY), wipe all again, flash CM13, get it running, wipe all again, flash crDroid + Gapps, wipe caches and boot to a (hopefully) working system. If EFS broke again you can simply restore the backup made earlier instead of starting over.
Mind that when I say wipe all, it doesn't have to include internal memory or you'll be wiping backups you might need later on.
Alright, here goes your 27th attempt. Good luck! ?

mate here is the link https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 even though it says do not use on soft brick devices in your case you are going to have to

Anyone Wanna make $10? I'm stuck at a problem

Ok so here's the situation: I originally modded the K1 tablet years ago and completely forgot what i did, everything was fine until yesterday when for some reason it was off, when I went to turn it on it loaded into the OS but would immediately power off. I went into TWRP (version 2.8.7.0) and made a backup of my OS in that state. Dumped onto my computer (where I have a backup from 2015 as well), wiped my tablet (Dalvik Cache, System, Cache, Data) and grabbed a bunch of different ROMs from here to give a shot..... Here's where the problem is: The only bloody roms I actually got to install are Cyanogen mod from this guide:
https://forum.xda-developers.com/sh...-cyanogenmod-12-shield-tablet-lte-na-t3055043
and this stock rom from: https://forum.xda-developers.com/sh...rom-hyperstock-mra58k-shield-k1-v1-5-t3522897
however my tablet just indefinitely hung at the nvidia shield splash screen.
Honestly ive been at this for 4 hours and I just want a working tablet. I've gotten lost in firmware updates and some "blob" which i still don't fully understand. I've reached a level of frustration where i'm willing to just throw money at the problem (despite being fairly poor). If anyone wants to make $10 PM me your discord information and if you get a working OS the money is yours I'm sure we can work out some transfer or something. (preferably Lineage because I've read good things but I'll settle for a working tablet at this time)

Well after trying tg to follow the simple advice of "update TWRP" I somehow broke it and now it hangs at the nivdia screen when I try to do that too... I feel like i'm having a huge problem finding files for the original shield tablet (the one they sent out the replacement for due to the battery problem) or something because everything i touch is making this worse. I need an idiot proof step by step on how to fix this....

WhenSuddenly said:
grabbed a bunch of different ROMs from here to give a shot..... Here's where the problem is: The only bloody roms I actually got to install are Cyanogen mod
Click to expand...
Click to collapse
What happens when you try to flash other ROMs? Is there an error message (if so, what is the specific error?) or otherwise what is the result?
What ROMs did you try (other than the ones named). Were they stock based ROMs, or AOSP? If AOSP, did you flash gapps as required?
WhenSuddenly said:
I've gotten lost in firmware updates and some "blob" which i still don't fully understand.
Click to expand...
Click to collapse
Not sure what this means. Did you try to flash a stock recovery. If so, what happened, or where did you get stuck?
Or is this related to one of the custom ROMs you tried to flash?
WhenSuddenly said:
I've reached a level of frustration where i'm willing to just throw money at the problem (despite being fairly poor). If anyone wants to make $10 PM me your discord information and if you get a working OS the money is yours I'm sure we can work out some transfer or something.
Click to expand...
Click to collapse
Don't really expect or need the money. Sounds like you need it more! The whole point of these forums, is for folks to share and help each other. Most often, without the exchange of money. Many of us (myself included) have benefitted from the free contribution of others. So I'm happy to "pay it forward" and help (if I can), without compensation.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
WhenSuddenly said:
Well after trying tg to follow the simple advice of "update TWRP" I somehow broke it and now it hangs at the nivdia screen when I try to do that too
Click to expand...
Click to collapse
What happened exactly? You tried to flash TWRP by fastboot (or otherwise?). Did it say the process was successful, or no (if there was an error message, what did it say?).
So when you try to boot to recovery, it just hangs on the logo screen? Can you still get to bootloader?
WhenSuddenly said:
I feel like i'm having a huge problem finding files for the original shield tablet (the one they sent out the replacement for due to the battery problem)
Click to expand...
Click to collapse
What kinds of files are you looking for (the lack of specifics is killing me - and my attempt to help you - can you tell?)? Custom ROMs and TWRP, there is no difference between the "pyro" original Shield tablet, and the (2nd gen) K1.

redpoint73 said:
What happens when you try to flash other ROMs? Is there an error message (if so, what is the specific error?) or otherwise what is the result?
What ROMs did you try (other than the ones named). Were they stock based ROMs, or AOSP? If AOSP, did you flash gapps as required?
Not sure what this means. Did you try to flash a stock recovery. If so, what happened, or where did you get stuck?
Or is this related to one of the custom ROMs you tried to flash?
Don't really expect or need the money. Sounds like you need it more! The whole point of these forums, is for folks to share and help each other. Most often, without the exchange of money. Many of us (myself included) have benefitted from the free contribution of others. So I'm happy to "pay it forward" and help (if I can), without compensation.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
What happened exactly? You tried to flash TWRP by fastboot (or otherwise?). Did it say the process was successful, or no (if there was an error message, what did it say?).
So when you try to boot to recovery, it just hangs on the logo screen? Can you still get to bootloader?
What kinds of files are you looking for (the lack of specifics is killing me - and my attempt to help you - can you tell?)? Custom ROMs and TWRP, there is no difference between the "pyro" original Shield tablet, and the (2nd gen) K1.
Click to expand...
Click to collapse
Lol ok Sorry for the lacking in specifics so I'll try again from the top to answer all your questions: Regarding the ROMs I tried I just went down the list of all the popular ones on the xda form as it is presently (so Bliss, CM13, Resurrection Remix, Lineage, and a modified version of the stock rom which I can't find anymore)
when I tried to flash these through TWRP they all bounced back with an error (this was after a clean wipe). I can't elaborate further on that as I can't access TWRP any longer on the device but the only thing that said was flashed correctly was CM13. Technically speaking this CM13 should still be flashed to the device but I was getting help in a reddit post from Lineage OS (I'll link below) that gave me the advice to update TWRP to the latest version. I got the image file to install through my current TWRP and it said it was installed correctly. However when I tried to reboot my tablet into TWRP it just hung at the Nvidia screen. It also does this when I try to access the OS which should be running CM13. So to recap when in the recovery menu whenever I access OS or bootloader I just get it hanging on the Nvidia screen, and when I hit fastboot it just takes me back to the same 4 option menu. On my PC end (running windows 7) when I plug in the tablet I can see fastboot in device manager but I tried accessing it through the command menu and couldn't find the device.
Sorry for the brief spastic posting I got very frustrated the other day with the tablet but can now look at it with fresh eyes.
Link to the reddit: https://www.reddit.com/r/LineageOS/...d_tablet_original_lineage_failing_to/eh71q5t/

WhenSuddenly said:
the only thing that said was flashed correctly was CM13. Technically speaking this CM13 should still be flashed to the device but I was getting help in a reddit post from Lineage OS (I'll link below) that gave me the advice to update TWRP to the latest version. I got the image file to install through my current TWRP and it said it was installed correctly. However when I tried to reboot my tablet into TWRP it just hung at the Nvidia screen. It also does this when I try to access the OS which should be running CM13.
Click to expand...
Click to collapse
Updating TWRP is good advice. Some of the newer ROMs will often not be compatible with older versions TWRP (and can very well be the cause of the errors when flashing the ROMs). And v2.8.7 is a few years old, at this point.
When you flashed CM13, did you also remember to flash gapps (Google apps) in TWRP immediately after? This is mandatory for most AOSP type ROMs (such as CM13). And not booting to OS is an expected result after forgetting to flash gapps.
My recommendation at this point, would be to flash current version TWRP again using fastboot. Of course, you need to connect the PC by fastboot to accomplish that. Which brings us to your related issue:
WhenSuddenly said:
when I plug in the tablet I can see fastboot in device manager but I tried accessing it through the command menu and couldn't find the device.
Click to expand...
Click to collapse
So what is the exact response when you enter the command: fastboot devices
Does it just hang, or some error message (tell us the specific error message, if there is one).
Make sure your tablet is in bootloader-fastboot mode ("fastboot" should be highlighted or selected - I forget exactly what that looks like on this device, but it is sometimes portrayed with the word FASTBOOT highlighted in red, at the top of the bootloader screen).
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
WhenSuddenly said:
So to recap when in the recovery menu whenever I access OS or bootloader I just get it hanging on the Nvidia screen, and when I hit fastboot it just takes me back to the same 4 option menu.
Click to expand...
Click to collapse
I think you mean: "in the bootloader menu whenever I access OS or recovery I just get it hanging"
Without bootloader, the screen would not even come on. It would be a paperweight.

redpoint73 said:
Updating TWRP is good advice. Some of the newer ROMs will often not be compatible with older versions TWRP (and can very well be the cause of the errors when flashing the ROMs). And v2.8.7 is a few years old, at this point.
When you flashed CM13, did you also remember to flash gapps (Google apps) in TWRP immediately after? This is mandatory for most AOSP type ROMs (such as CM13). And not booting to OS is an expected result after forgetting to flash gapps.
My recommendation at this point, would be to flash current version TWRP again using fastboot. Of course, you need to connect the PC by fastboot to accomplish that. Which brings us to your related issue:
So what is the exact response when you enter the command: fastboot devices
Does it just hang, or some error message (tell us the specific error message, if there is one).
Make sure your tablet is in bootloader-fastboot mode ("fastboot" should be highlighted or selected - I forget exactly what that looks like on this device, but it is sometimes portrayed with the word FASTBOOT highlighted in red, at the top of the bootloader screen).
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
I think you mean: "in the bootloader menu whenever I access OS or recovery I just get it hanging"
Without bootloader, the screen would not even come on. It would be a paperweight.
Click to expand...
Click to collapse
Sorry for the incorrect terminology its been a while since I've been in the android modding scene.
Anyway when I access the bootloader on my tablet I get the 5 option menu of continue, fastboot protocol, recovery mode, reboot, poweroff. When I hit fastboot protocol on the menu it loops back to the same bootloader menu, I have no determinable way of telling if this is fastboot receptive or not. Now on the windows end of things this is what I'm seeing
https://drive.google.com/open?id=1zS7FjUB754iSnWal18ch4EiFtHykM0fD
(clearly seeing that I'm having trouble uploading a picture to this website you can tell how far my skill level has degraded in 5 years)

WhenSuddenly said:
When I hit fastboot protocol on the menu it loops back to the same bootloader menu, I have no determinable way of telling if this is fastboot receptive or not. Now on the windows end of things this is what I'm seeing
Click to expand...
Click to collapse
Selecting fastboot shouldn't change much, as to the appearance of the screen. It should be the same bootloader screen (with options) but should have some indication of "fastboot" being the selected mode. Usually near the top of the screen. I can't say exactly what it should look like, as I haven't used my Shield in a long time (since last summer, when I broke the screen).
If you can confirm the tablet is indeed in fastboot mode (take a photo, and post if, if you like) and still no response to the command "fastboot devices" (no quotes), then something may be wrong with the connection. Try another USB port on the computer, or try another cable.

Also, make sure you have the drivers installed on your PC (first item on the following webpage): https://developer.nvidia.com/gameworksdownload#?search=shield tablet

Oukitel WP6 General Discussion

As there's no thread on this device I decided to start one
The hardware of this device is really nice, but the stock ROM on it is total garbage. It has some built in power saving that closes all background apps no matter what the settings are, so after an hour so so you won't receive any more notifications from messaging apps such as telegram and outlook.
Since there are not even stock ROMs available anywhere I decided to take the risk of a brick and install phh's AOSP 10 GSI, no need for TWRP as everything can be done using ADB and fastboot. The procedure is the same as with any other phone: Unlock the bootloader, wipe all partitions in fastboot, install system image, restart and hope for the best. Luckily it booted up just fine and everything except VoLTE and VoWIFI works, @lucian.w153 found two little bugs which I didn't notice:
lucian.w153 said:
- In call volume not working, it is stuck at max which is very annoying
- You can't disable the second sim card, you need to take it out if you don't want it to consume battery.
Click to expand...
Click to collapse
It's an arm64 AB device, so any matching GSI should run fine on it.
I have tested phh's vanilla, FLOSS and GAPPS variants, they all work flawlessly barring those two bugs mentioned above.
GAPPS version is my daily driver now, the phone runs blazingly fast and battery lasts forever. All hardware (bluetooth, sensors, cameras etc.) works perfectly, no force closing or other issues.
Hope some more share their experience to help others.
Cheers

Finished. Done!

Joergelmann said:
Please provide complete instructions. I am an absolute beginner. Please a step to step instruction with links.
Click to expand...
Click to collapse
Ok, just the usual disclaimer: You may void your warranty or brick your device in the process, you do everything on your own risk and I'm not responsible if anything goes wrong.
Of course you will also loose any data on your device as it will be formatted in the process.
Prerequisites:
You need ADB and fastboot installed on your computer, follow these instructions for windows or these for MacOS or Linux.
Also you'll need to download the system image from phh's releases, it has to be arm64 AB but you can choose whichever one suits you best, with or without google apps, FLOSS etc. If you don't know what those are, please do some research in the forum first.
For most people system-quack-arm64-ab-gapps.img.xz will be the most suitable one as it's closest to a stock ROM with google apps. After downloading extract the .img to the same folder you installed ADB and fastboot to. Also rename it to something simpler like system.img for later.
Make sure you have sufficient battery in your phone before you start, at least 50%.
Once those are ready you need to unlock the bootloader of your phone. First enable developer options: Go to settings -> about device and tap on build number 7 times in a row quickly, you'll get a confirmation that developer options are enabled. Go to settings -> system -> developer options, there enable USB debugging and OEM unlock.
When done, connect you phone to your computer with the USB cable. Your phone will show an info in the statbar that USB debugging is enabled.
On you computer open a terminal in the folder where you installed ADB and type in the upcoming commands and press enter after each.
First type: adb devices
ADB should now detect your device, and a request for access will pop up on your phone asking to allow permission. Allow it.
Next type: adb reboot bootloader
The phone will reboot into fastboot mode, wait a few seconds until "fastboot mode" is shown on the bottom left of your phone's screen.
Now type: fastboot devices
Fastboot should detect your device
Next type: fastboot flashing unlock
Fastboot and your phone will ask you to confirm that you want to unlock your bootloader, confirm it using the volume buttons on your phone according to the instructions on your phones screen.
After the bootloader has unlocked successfully you need to format your device, type: fastboot erase userdata
You'll receive a confirmation that data has been formatted.
Type: fastboot erase system
You'll receive a confirmation that system has been formatted.
Now you can flash the system image, type: fastboot flash system system.img
This will take a while until all the data is sent and installed on your phone. You will receive a progress report and confirmation when it's done.
Finally type: fastboot reboot
You phone will reboot and load the new system for the first time, this takes around 2-3 minutes, be patient. You can disconnect the USB cable now. When the welcome screen pops up set up everything as usual and enjoy

Thanx a lot for the instructions.
It's worked out. Everything works fine.

Great to hear!
AOSP really is a blessing, big thanks to @phhusson for all his work on this too.
This device even beats the legendary K10000 in endurance, my current record stands at 12 days and 34h SOT xD

The only things missing is double tap to wake and the ability to disable the second sim card. Otherwise almost perfect. :good:

After watching the WP6 violence test video and also seeing several other positive reviews I decided to buy one...
Recieved it a couple of days ago and seems like a great phone, very impressed with the speed, battery, heft and general rugged feel of it etc..
However... this morning I dropped it out of my pocket (from no higher than 3ft) onto some gravel and was horrified to discover around 7 little scratches/idents/scuffs to the screen!
How can this possibly be after all I saw it put through? In the advert video it shows someone dropping the phone and picking it up without even needing to check it's OK which kind of implies it's not gonna get scratched easily. Either way I'm gutted!!
By contrast, I've had my HTC M8 for 3 years and has been dropped loads of times and doesn't have a single one of these indented scuffs to the screen, despite it not making any of the claims to ruggedness like the WP6.

I bought my WP6 just last week, and am really impressed with it running Nova launcher, battery life and performance are great! Unfortunately the sheer mass of the phone means it will damage itself in a fall. My old Runbo X5 would probably fare better in a fall, being much lighter, but nowhere near as good a phone.

Are you running the stock ROM or also AOSP @markpab ?
v220 is out here, in-call volume not fixed, maybe the SIM issue mentioned above, would someone like to try?
@TpX Thinnr, that's surprising. Mine fell on some gravel as well last week, but the only thing I can see is a little scratch on the rubbery corner top left of the device.

Yes, I'm running totally stock ROM, been ages since I last rooted a phone (Runbo X5). 5 days since first full charge, and still at 34%!

GroovyG said:
Are you running the stock ROM or also AOSP @markpab ?
v220 is out here, in-call volume not fixed, maybe the SIM issue mentioned above, would someone like to try?
No. No changes regarding bugs in v220.
I have installed Havoc-OS 3.6 now.:
https://sourceforge.net/projects/ha...00613-Official-GApps-arm64-ab.img.xz/download
This allows you to set at least two separate tones for the simcards. I then created a silent tone for the second simcard. If you can't deactivate the second card, at least I am at peace.
Click to expand...
Click to collapse

markpab said:
Yes, I'm running totally stock ROM, been ages since I last rooted a phone (Runbo X5). 5 days since first full charge, and still at 34%!
Click to expand...
Click to collapse
And you don't have the problem that all background apps are closed and no more notifications arrive after a while?

I get notifications from emails and texts no problem, but apps from the Playstore don't update or stop, such as battery widgets, status bar calendars, and some clock widgets. All the built in apps are fine.

Hi, My New wp6 is bricked. I need stock firmware [emoji20]
Enviado desde mi F5321 mediante Tapatalk

oscarhugo said:
Hi, My New wp6 is bricked. I need stock firmware [emoji20]
Enviado desde mi F5321 mediante Tapatalk
Click to expand...
Click to collapse
You can download the original stock rom directly from the oukitel website:
https://mega.nz/file/3NFFQaxZ#Wk8S5G-iqBpJI5HDK-AXMGebNDiRVdUMAGthW_JANS0
You don't need to create an account there.
But I don´t know how to install the rom. Someone else would have to explain that here please.

Doesn't work, i tried to flash and is not possible say: chip type not match!! target chip type is mt6771 load scatter chip type is mt6737.
old firmware?

What exactly did you do to "brick" it? You can't really totally brick those devices.
Can you still access it with ADB and/or fastboot? If so, just flash a GSI and you're back in business.

Totally bricked, no power... black screen. I try to flash with sp flash tool
Enviado desde mi F5321 mediante Tapatalk

Did you manage to recover it with SP Flash Tool?
I'm still curious what you did to cause the brick, would be helpful for others too if you let us know what you did.

Was a New phone, works great without sim. Once i put sim, crashing... And Black screen.. Bricked. [emoji20]
I can flash with sp tools but i need firmware for mt6771