yashsingh1/xdaforums huggingface dataset:
[Other SmartWatches] erdemmetin1982:
Friends, I got my zeblaze thor pro 3g. The device looks very solid. I liked it very much. I've also installed the 20181215 update package. I can change the screen when I am looking at it? I've added a custom application, but I haven't started using it yet. I need support for the awakening sensitivity. I expect your support, thank you for your interest.
[Other SmartWatches] erdemmetin1982:
The waking sensation of the clock behaves inconsistently.

Please watch the video below.

https://youtu.be/TMc5t6dh8Qg
[Other SmartWatches] rescorci:
I have bought the Bakeey I3 Watch, that is basically identical to the Zeblaze Thor Pro in all aspects (screen, size, memory, processor, etc); only difference is with the bezel design (see comparison video here youtu.be/OqOy1hXZ_Mk )

The thing is that the accelerometer does not seem to be working (no screen-on when rising, pedometer not functioning)

Will this Zeblaze stock ROM work if flashed into the I3 ? Will that help to fix the sensor issue? Thanks
[Other SmartWatches] Riiminhyo:
My screen not working after update ota,please

[youtube]wL3FmWkR7-A[/youtube]
[Other SmartWatches] raouff:
Zeblaze thor pro is dead screen?

Hello

I bought a new SmartWatch called zeblaze thor pro its works fine just when i need to update playstore service its turn off and the screen goes black no matter what i push button and plug usb nothing happens except that its detected in the usb pc as mtk device.

So i try to flash it with sp flash tool and original firmware just give me a error 4032 code... So what i think its not in the fastboot mod ? if somebody can help me out and show the key combination to entre the fastboot mode or any other method just make it booting again... Thankx for advance
[Other SmartWatches] Noidremained:
The watch should not be in fastboot mode when you flash it, it should just be turned off. Have you tried both "download only" and "firmware upgrade"?
[Other SmartWatches] Fullkaos2913:
I need please

Amigo necesito este archivo porfavor mi reloj no enciende

---------- Post added at 06:35 PM ---------- Previous post was at 05:44 PM ----------

Hola, amigo acabe de dañar mi thor pro no encuentro los archivos, alguien me puede ayudar con esto? el link que tienes a no estan los archivos.

Hello, friend I just damaged my thor pro I can't find the files, can someone help me with this? the link you have to the files are not
[Other SmartWatches] Noidremained:
you can get the firmware here: https://discourse.fullandroidwatch.com/t/thor-pro-3g-updated-18th-sept-2018/34314
[Other SmartWatches] PAWANJAGGA:
Zeblaze thor pro 3G smart watch

Please send me original fimware send me zeblaze thor pro 3G smart watch
[Nexus 6P General] mdfarazb2:
Glad to see this exclusive thread... just came here to report that I've been using your fix since Jan this year ( https://xdaforums.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279/post75220708 ) and yeah my phone's still alive and running fine. Kudos to your work... Great job you did there... saving hundreds of bucks... Really appreciated!

Thanks again. :)
[Nexus 6P General] SH15:
Hi osmosis,

I have done everything you said and I got stuck in step 7, when I enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip", the return message is:

adb: sideload connection failed: closed

adb: trying pre-Kitkat sideload method...

adb: pre-Kitkat sideload connection failed: closed

I tried swiping where it says "Swipe to Start Sideload" and then doing step 7, but when I swipe my computer stops recognizing my device.

Thank you
[Nexus 6P General] osm0sis:
You need to let your computer install drivers for adb sideload. If your computer is having trouble with that for some reason and the recovery otherwise works then just adb push the zip to /sdcard and flash it from on the device instead of sideloading. :good:
[Nexus 6P General] SH15:
Thank you for answering. I had to adb push the file to /sdcard and then I flashed it using TWRP, however even after installing the file the phone is still stuck on the Google logo screen when booting up. I don't know what to do.

Thank you
[Nexus 6P General] osm0sis:
That's weird. The fact that the recovery worked suggests the 4core fix works for you. Maybe flash the lastest factory image then the BLOD AK2 zip.
[Nexus 6P General] FlameSting:
Can this be flashed on top of the Oreo img from the previous thread? Is this one for Oreo?

I've applied the previous Oreo one and my phone's past the Google logo loop and is now in the loading animation for Lineage OS.
[Nexus 6P General] osm0sis:
Please read the OP. It works over any ROM, any custom kernel, any recovery.
[Nexus 6P General] SH15:
Thank you very much! I flashed the newest factory image for Oreo and then re-flashed the BLOD AK2 zip and it worked. Thank you for your help! :good:
[Nexus 6P General] Deathstroke1:
Idk if I'm in the right place.

I recently replaced my battery (2nd time this week, first one was bad) and everything was working fine. Then my phone started randomly rebooting. Googled it and apparently it's one of the first signs of BLOD. Followed this and the phone stopped shutting down randomly. Now the phone only works if plugged into a power source. Idk if I did something wrong or the battery is trash (even though it was working fine all day)

I'd appreciate an guidance [emoji24]
[Nexus 6P General] kurniawan77:
This saved my day! Thanks everyone! Got my 6P booted up again... and it's not even rooted
[Nexus 6P General] queengab:
I want just only to thanks [MENTION=4544860]osm0sis[/MENTION] and it's genial solution!

Thanlks i recover my phone and saved a lot of money.

I understand it could be a temporary solution but thanks!!!

gabriele
[Nexus 6P General] godd:
After I flashed twrp and try to go to Recovery there is a message "Your device software cannot be checked for corruption. Please lock the bootloader." And after that it goes back to bootlloop. Any idea what to do next? Thanks
[Nexus 6P General] osm0sis:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
[Nexus 6P General] jd603:
I had my phone hang on the google logo a couple times, but rebooting it fixed it. Is this an early sign of this problem? Just replaced battery and so far it seems fine.
[Nexus 6P General] lbrenes:
I am in this same boat... RIP N6P, this is my 2nd N6P Google replaced the first one due to the BLOD and now the replacement is dead.

Thanks for all the efforts and help.
[Nexus 6P General] jbjcurly:
It seems the basketbuild site is down. Any chance you could throw the modded twrp for oreo and the 4core fix up here?
[Nexus 6P General] CavyS:
Same as the guy above. Sites down need mirrors or something?
[Nexus 6P General] osm0sis:
Mirrored in the OP. Thanks!

Edit: And BasketBuild is also back! :good:
[Nexus 6P General] Lughnasadh:
Not really much else you can do, unfortunately.
[Nexus 6P General] MrSpies:
My Nexus 6P with BLOD was also saved from the waste heap with this guide. Thanks to all involved! However I was saddened a bit to find that Google Pay no longer works. Being a total noob at this sort of thing anyone know of a simple way and can provide step by step instructions on how to get Google Pay working again as well as keeping the BLOD patch in place? Cheers!
[Nexus 6P General] Lughnasadh:
I don't believe this BLOD fix affects Google Pay in any way. Something else is interfering with it.
[Nexus 6P General] osm0sis:
Unlocking the bootloader would trip SafetyNet. Magisk should get it working again though.
[Nexus 6P General] MrSpies:
Thanks for the quick replies and pointing me towards Magisk. I had feeling it would not be as simple as just relocking the bootloader.
[Nexus 6P General] PraneethMv:
Hey, I've tried this method and successfully booted to system and set up the device. But when I first boot into recovery and it is asking password to decrypt data, and even after I flashed the BLOD fix and rebooted, it is asking pwd to decrpt data. Can I know is there any pwd like that or am I missing something?
[Nexus 6P General] osm0sis:
As long as you're not using FBE you should probably update to the newest TWRP .img and flash the BLOD zip over it to patch it. Detailed instructions are in the OP.
[Nexus 6P General] PraneethMv:
Thank you! Missed that point. Will do that. :D
[Nexus 6P General] nicholasknicks:
Anyone who managed to replace the battery can you please link me to where i can buy a good battery
[Nexus 6P General] bilatche:
For me I did the replacement in a shop.

And it last two weeks before coming a serious BLOD.
[Nexus 6P General] zhxhwyzh14:
Hi, dear developer. I use pixel experience ROM in my blod nexus 6p. In the newest update, it has enabled system-as-root. So when i flash blod patch in twrp, it showed "Unknown ramdisk compression". What can i do？ Could you help me？ Thank you very much.
[Nexus 6P General] igylan:
I tried Crdroid and Carbon also. Somehow it comes through with an error when flashing the patch though the ROM has no problem. Hope someone can shed a light on this.
[Nexus 6P General] MeHR@N:
I also have this "Unknown ramdisk compression" thing when installing BLOD patch over latest Pixel Experience and Bootleggers rom ☹️
[Nexus 6P General] paulfadiv:
Developer, Hello! Please help. Blog blog Nexus 6P displays this error when updating Pixel Experience ROM. "Unknown ramdisk compression".
[Nexus 6P General] jarpco8484:
Hi:

Well, one more with "Unknown ramdisk compression" after flashing the patch during the installation of the newest versions of almost all the pie roms available for the nexus 6p, so sad.... Any help will be very appreciated.:good:
[Nexus 6P General] osm0sis:
Wow, super annoying that a ROM would change something fundamental like system-as-root so late in a device's life. :rolleyes:

Basically what happened is this: someone in control of the device trees all these ROMs are based on decided to make the Nexus 6P an A-only system-as-root device, resulting in there being literally no ramdisk in the boot.img anymore. See here: https://source.android.com/devices/bootloader/system-as-root

So, since all the boot-up root / directory stuff is now in the system partition, or possibly even vendor, I'll have to mount at least /system as read-write in recovery as well and patch the init.*.rc files there.

I don't have a lot of time right now, but I do have it on my list to fix. I'll get to it as soon as I can, and if you're frustrated in the meantime you should take your complaints to the ROM developers who should have known this would affect all BLOD devices still in use.
[Nexus 6P General] igylan:
I had a hunch it had something to do with the rom devs than with the patch. Oh well, thanks for keeping our old devices running.
[Nexus 6P General] zhxhwyzh14:
Thank you for your work.
[Nexus 6P General] Lughnasadh:
Thank you very much for letting everyone know what is going on. The Angler rom threads are full of posts describing this problem and not one developer or maintainer (to my knowledge) has even responded to these posts. But here you are, someone who doesn't even have a working 5X (or 6P for that matter) anymore, has a ton of other projects going on and a life to live as well, letting everyone know the cause of the problem. For that alone, I'm very grateful. So....thank you.
[Nexus 6P General] eladr1dj:
Hi, hello XDA developers and users. I have found this thread and I have read it completely, including the comments, since I am a user of a Nexus 6P.

My phone STILL does not have BLOD, but from what I have read it is a matter of time that is affected and finally dies, so I was interested to know the temporary solutions. I already have the Bootloader unlocked and the OEM has been active for some time, so that when the BLOD occurs, I have part of the work done. Now, I have some doubts that I hope you can answer. I am using compilation OPM. 181205.001, security patch December 5, 2018.

1 - With the compilation I currently have, is the solution of flashing with TWRP 4core the file `` N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip´´?

2 - Is there any pre-patched Boot.img image for the OPM compilation. 181205.001? Link please

3 - Can I downgrade to a lower version like OPM3.171019.013, of which I already have a pre-patched Boot image, without any brick risk for downgrade?

I hope you can answer my questions, and I apologize if the answer to any of them is in the thread, after having read so many pages, I may have missed something. Oh, and forgive my lousy English.
[Nexus 6P General] CityHunter004:
Can anyone update blod patch for fbe roms ? ??
[Nexus 6P General] Lughnasadh:
Look 5 posts above yours.
[Nexus 6P General] blackmonk19:
[MENTION=4544860]osm0sis[/MENTION] - Just wanted to say "thanks buddy" for all your hard work... My Nexus 6P had a good run... :)
[Nexus 6P General] metalhead2175:
Nexus 6p not booting in recovery mode (bootloop unlocked )

Hi Everyone,

It's been 5 days am day n night trying to fix and keep of reading articles but still hard luck.Please answer my few questions which will clear my mind.

1. What cause bootloop basically in 6P ?

2.It can be repair through hardware ? if Yes then how ?

Scenario :

I followed this article https://www.xda-developers.com/nexus-6p-bootloop-fix/ and flashed N2G48B_4Cores.img which happened successfully but i didnt flashed twrp3.I thought it was optional and i will not experiment but after 13 hours. it again went to bootloop now i again run terminal and whole procedure but phone is not reacting at all just on logo with lock.When tried recovery it showed no command in videos but mine is just rebooting with bootloader unlocked warning and then google logo with lock.

I tried to install twrp through terminal using this article https://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

but phone reacting to commands.

Android version was 8

Please Help.I am looking forward for help.

Regards,

Danish
[Nexus 6P General] Lukeet33:
Any news on time scale of blod update fix will take? Thanks for your development keeping our devices alive
[Nexus 6P General] Lughnasadh:
I noticed you mentioned trying other methods but not this method. Give it a try.
[Nexus 6P General] osm0sis:
Never ask for ETAs. But to reiterate what I've already said, I'm busy and won't be able to get to it for several weeks.

Use any ROM build from before they switched to system-as-root and the existing BLOD zip will still work just fine. Common sense, people.
[Nexus 6P General] bangeko:
I unlocked my bootloader by flashing this file

Since my Nexus is not hardbricked I have to put it on 9008 mode by testpoint.

And the next steps are in this thread.
[Nexus 6P General] metalhead2175:
after flashing rom i flash blod and get error of " unknown ram compression format U

after flashing rom i flashed injector as per direction and get error of " unknown ram compression format Updater process ended with ERROR: 1

Detailed coz it's been 11 days but failed

Please help please please

---------- Post added at 05:31 PM ---------- Previous post was at 05:27 PM ----------

after flashing rom i flashed injector as per direction and get error of " unknown ram compression format Updater process ended with ERROR: 1

Detailed coz it's been 11 days but failed

Please help please please
[Nexus 6P General] bigcelo75:
Unfortunately the patch no longer works for ROMs that are now system-as-root. For now you aren't going to be able to update. Go back to the last version prior to system-as-root was implemented.
[Nexus 6P General] Lawlrus:
Too much to ask for new users to read a page or two of posts? Hell if you read the last four or five posts you would seen the new builds have issues with it.
[Nexus 6P General] mohdschizo:
Seems my angler dieded..

Been trying all those magic stuff the whole day but still failed to boot into twrp recovery (4cores)..

Thanks anyway for this thread. Dev are awesome!
[Nexus 6P General] DirtyPants:
ok so i got a problem today my phone started to bootloop i want to wipe cache via cmd exe screen but says permission denied. I think its because of password. İ cant go in to twrp phone bootloops again. Any suggestions? phone is rooted on stock oreo. tried 4 core but didnt do anything.
[Nexus 6P General] Ivan1967:
I've bought a Nexus 6P, with locked bootloader and screen password. Took me three months to fix it, but I wish I've had today's brain. Tried heating and freezin, just a waste of time and burned my rear camera lens, now it's blurry. Just had to wait till battery drains out and the phone booted like it should. I've been installing the last OTA recovery all the time to waste my time, rebooting and suddenly it went to Andoid. But, you have only 10 or more/less minutes to fix the bootloader and USB debugging, in my case I've had to remove screen password and FRP, too (previous owner refused to pass me the details). From second try, I successed following youtube flicks from some guy from India. The magic is not to put it on charger when it boots in Android (overheating), try to unlock bootloader and enable USB debugging in those ten minutes. After that, followed the guide to install Pixel Experience version of Android 10, 8 or 4 cores, just try. It's still working, but rear camera is busted and the battery must not fall under the 30%, starts acting weird. This is a cool phone and I can get everything what I need from it, I'll get over the newest games and stuff.
[Nexus 6P General] osm0sis:
The time has come! I've uploaded the new AnyKernel3-powered BLOD Workaround zip to the OP, and it should be working on both the system-as-root (SAR) and 2 stage init (2SI) ROMs that maintainers for these devices have switched to in order to support Android 10 (and in some cases have done so on Pie as well)! :victory:

My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!

I'm going to leave the AK2 zip up for posterity, so note the new zip's naming: N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip

A source repo for the updated zip is also available going forward: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector

Note that in my testing on my N5X FBE didn't seem to be supported on Android 10 for us so far (I had to format data instead and opted to stay unencrypted), so I've added a note about just using the old 4core FBE recovery to update to the latest official TWRP as well.

Sorry again for the wait, but I had to go get married and go on my honeymoon first. :D
[Nexus 6P General] Lughnasadh:
Thank you so very much. Your hard work and efforts are really, really appreciated, not only on this but on all your projects. :good:

Hope your wedding was a beautiful one and your honeymoon romantic and relaxing. Congrats again :)

P.S. Your BLOD fix has kept my Angler going for around 15 months now (knock on wood). Not too shabby :)
[Nexus 6P General] Lughnasadh:
UPDATE: Just flashed a Q rom and everything worked perfectly. (I did patch the modified 3.3.1-0 FBE TWRP that came with the rom with the workaround.zip and formatted /data before booting). No problems whatsoever. Great job and thanks again :good:
[Nexus 6P General] osm0sis:
My GitHub Sponsors profile just went live, so please do take a look at the link below - they're even matching the first year of funding for everyone! :D

As you might know, I work on these projects in my limited time off, so if you like the progress I'm making, or enjoy anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thanks for your support!
[Nexus 6P General] nauraza:
Do you mind to share the exact ROM you are using and translate the step 1 by 1 correspond to OP please?
[Nexus 6P General] Lughnasadh:
AOSiP DerpFest Q

Flashed 3.3.1-0 FBE TWRP that comes with the rom

Immediately flashed the new workaround.zip

Reboot into TWRP

Wiped /data/cache/dalvik/system

Flashed Rom

Formatted /data in TWRP

Flash workaround.zip

Boot

Optional:

Rebooted back into TWRP

Flashed Magisk 20.1

Flashed the new workaround.zip

Reboot
[Nexus 6P General] osm0sis:
You should also be flashing the BLOD zip after ROM, since we need to hack ROM files now too.:good:
[Nexus 6P General] Lughnasadh:
Lol. Ooops, of course I knew that, just for got to put that in. Silly me :silly: Getting forgetful in my old age :D . Thanks for the correction :good:

[MENTION=10312543]nauraza[/MENTION] Flash the workaround.zip last and before booting anytime you update/change rom, kernel, boot.img, recovery or Magisk. When updating/changing recovery (TWRP) it should be flashed immediately after flashing the new TWRP and before you boot into the new TWRP.
[Nexus 6P General] nauraza:
Aww

U both really save me here.

I am about to giveup when the 6p lit again.:cool:

Btw, i am on AOSIP 9.0 since can find the Android Q like u mentioned.

Thanx a lot!!!

Overcoming the fear of dev's jargon bla bla bla. U guys make me wanna explore more on this ROM thingy. :D
[Nexus 6P General] Lughnasadh:
It's all osm0sis. I'm just a guy who has benefited from his hard work and try to help others when I can. :D

Btw, I wouldn't suggest flashing that rom anyway. The Q roms aren't really stable at the moment, imo. I would stick with Pie.
[Nexus 6P General] seeker010:
Hi - is there a 4core twrp 3.3.1? I am on lineage 15.1 with encryption when my 6P died and the 3.2.1 twrp doesn't support file based encryption :'(

Thanks!
[Nexus 6P General] Lughnasadh:
If you are currently on the twrp-3.2.1-0-fbe-4core-angler.img from the OP and you want to use 3.3.1, all you have to do is flash the 3.3.1 in your current TWRP and then immediately and before rebooting back into TWRP, flash the workaround.zip to patch the new TWRP, and then boot into the new TWRP.
[Nexus 6P General] seeker010:
Thanks! that worked great; but the FlashAfterUpdate scrip didn't work. And the /sdcard/FlashAfterUpdate folder got deleted. TWRP didn't ask me to unencrypt anything during an OTA update of LineageOS so don't know if the paths are different and need to be changed.
[Nexus 6P General] Lughnasadh:
You're welcome.

Assuming you followed these directions in Post #2, not sure I can help any further:

"On custom ROMs with built-in Flash After Update (i.e. OmniROM-based), place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/OpenDelta/FlashAfterUpdate/ ensuring the BLOD AK3 is last in the directory listing so that they will be flashed after each update."

Could be a TWRP issue :confused: . Maybe osm0sis can shed some light for you.
[Nexus 6P General] osm0sis:
If the ROM doesn't decrypt for automatic OTA you need to put zips somewhere else that isn't encrypted or boot to TWRP manually to flash your OTA zips each time for my FlashAfterUpdate addon.d script to be able to access them.
[Nexus 6P General] abdullah83:
this method isnt working for me i use every method but still can you help me with that my phone still stocking on google (i already install twrp)
[Nexus 6P General] PXeuda:
Hi Lughnasadh, maybe you have a link for the exact rom?
[Nexus 6P General] bigcelo75:
https://xdaforums.com/showthread.php?t=3877510

[ROM] Unofficial AOSiP DerpFest
[Nexus 6P General] danijaan:
Hi,

I am trying to revive my Nexus6p. I flashed the recovery attached in the OP. But I am not able to enter into recovery. The phone keeps looping after I select Recovery from the fastboot menu. Is there a way to enter into recovery?
[Nexus 6P General] Lughnasadh:
Quote from the OP:

"If no 4core recovery boots for you then you definitely have more components than just the performance cores separated, sorry but your device is a brick."

Unfortunately :(
[Nexus 6P General] danijaan:
I saw that quote in the OP, but still wanted to know/certain.

Thank you for your reply. It is really unfortunate. I liked Nexus 6P a lot after Nexus 5.
[Nexus 6P General] mohdschizo:
The same happened to me started on october.. tried all available method and still failed. Im using my old buddies back (Nexus6 - shamu)..