Develop Bugs

AOKP B30 Bootloop, wipe doesnt help

Hi!
Downloaded and clean flashed AOKP B30 and gapps, came from M4. Got into a bootloop. Went into recovery, wiped, still bootloop. Pushed an original image to the phone via Gnex Toolkit. Still bootloop!!
Now I have no idea what to do....
Please help!!

CWM cant find my sdcard either it seems!
If I try going into stock recovery, I get an android with a triangle.

Step 1: Take a deep breath. Your device is fine (although your data is probably gone).
Recovery cannot find /sdcard because there is likely an issue with your data partition, where /sdcard resides. The best thing to do is flash the stock images again. I recommend you do it manually so you can actually see what you are doing, instead of using a toolkit. Follow this procedure and you will be fine. And flash back CWM. (The android you are seeing with the red exclaimation point IS the stock recovery. To access the menu from there, repeatedly press volume up and power until you see the menu.)

Thanks for your help, but it seems the problem was that the phone was connected to the computer. So I probably just flashed stock and wiped my sdcard for nothing. Since everytime it bootlooped, the computer tried to install a driver.
I feel stupid.

eivi91 said:
Thanks for your help, but it seems the problem was that the phone was connected to the computer. So I probably just flashed stock and wiped my sdcard for nothing. Since everytime it bootlooped, the computer tried to install a driver.
I feel stupid.
Click to expand...
Click to collapse
Knowing is half the battle.. nexus is pretty brick proof
Sent from my francoPhone

[Q] Friend did a bad file flash, Hard bricked phone

Okay my friends wife had an unlucky bad file flash and ended up hard bricking somehow.
And keep this in mind that she never flashed a Int. version.
She flashed the SlimRom 3.1.0-D2SPR then she flashed the custom kernel unlocker file
to use the K747 kernel for slimrom, but the thing was ( She has TWRP ) when she slid the bar to flash
the file, the screen went back to the TWRP home page she waited 5-10 minutes then she tried reflashing the file again
and it said failed. Rebooted and the phone's hard bricked after installing the kernel. ( No LED when USB plugged in for recharge,
No power or haptic feedback. )
Her husband used the same method to install slim rom and his phone is fine
but the screen never went to the TWRP home page, it went straight into installing it.
The thing that boggles my mind is that she flashed everything in order and it hard bricked.
Rom first, rebooted recovery, kernel unlock, cache and dalvik cleared. rebooted recovery
When she tried flashing the K747 AOSP Kernel, she said it never went to the page screen that would show
it install, it just went straight to the home page, retry flashing but failed. ( here's the weird part I've never experienced. )
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.

Spark91 said:
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Click to expand...
Click to collapse
So, I'm just going to rattle through my thought process on this, just to get things clear in my mind:
Her phone cannot turn on at all. Do a battery pull/replace and make sure that there's no going into recovery or download mode. If that's the case, then JTAG might be your only solution.
This happened when trying to flash a kernel. It seems unlikely that a kernel would screw up the bootloader. I was under the impression that only recovery zips touch the bootloader/recovery partition.
If the kernel or Rom zip was for an international GS3, then it would try to write to the bootloader partition. But since you said your buddy's phone flashed the same files just fine, it seems unlikely that they flashed the international zips.
I've had TWRP fail to flash a zip. Each time I tried to flash a zip, it would say it failed. All I had to do was reboot into recovery (even if I hadn't flashed a ROM, so I had no system file), and then I could flash the file. Sometimes TWRP had those issues for me. Her story reminded me exactly of when that happened to me, but if hers won't load into recovery (or download mode), that's a major difference.
After all that, I honestly have no clue how this happened. It sounds to me like the JTAG is the best bet. You can find them online for around $60. Sorry this happened, and I hope you find a good fix for your friend's wife.

Its possible that you can still fix this....
Couple questions. When you try to turn it on, what exactly happens? does it vibrate? what occurs?
There is a possiblity that you can bypass the idea of holding the power button and vol button, try to adb reboot recovery command. ive had this save me about 5 times now when flashing goes bad.
http://droidlessons.com/how-to-install-adb-on-a-windows-7-pc/
make sure adb is installed...
while the phone is trying to boot, keep typing or copy/pasting or in cmd pressing up and enter after you enter the command.
adb devices
if it gives you the UID of your phone you at least know that you might have the ability to fix it.
From here just type
adb reboot recovery and it will reboot into the recovery to allow you to flash a "good" kernel again.
Bit of advice.. I am always paranoid after going through this so many times of a bad flash. As a result i never stack flashes.. for instance.
if i want to flash a rom, kernel, modem, radio..
i wipe dalvik, flash rom, wipe dalvik, wipe system, wipe cache.
Reboot let android do its thing...
reboot into recovery.
wipe dalvik, flash kernel, wipe dalvik, wipe system, wipe cache.
reboot, let android fully boot up.
reboot into recovery
wipe dalvik, flash radio, wipe dalvik, wipe system, wipe cache.
reboot...you get the point.
Just precations i started doing because of issues ive had in the past. If you have a mac, the commands are a bit different so let me know...

This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!

topherk said:
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
Click to expand...
Click to collapse
When i had my evo things flashed slightly different.
There were many issues in kernel flashing where if the kernel didnt download properly or you had a bad dl. it will what we called soft-brick. This would allow the phone to "act" like it was booting up but only display a black screen and never boot. Screen would flicker, phone was active but nothing would display and it will not boot loop. kind of just freeze.
We noticed that if we connect the phone to the computer we could actually use adb to access the phone. from there we noticed that we could push recoveries, and even push kernels and radios to the phone even though it wasnt displaying anything.
I figured the easiest way to get through this issue is to see if you can Reboot Recovery through adb if it allows you, and hopefully then you can restore functionality.

Help possibly?
Can you get it into download mode and just use Odin to flash it?

[Q] Unable to fix bootloop - even tried STOCK flash in fastboot. No luck.

Hey guys,
Long time lurker, ROM user since the Galaxy S days.
Weird, intractable bootloop problem here. Gets to boot animation sometimes gets to the "upgrading android" screen, then bootloops in a few seconds after upgrading a few apps. Usually bootloops during the boot animation (doesn't matter what ROM or Stock ROM I try). Ocassionally gets to my "SIM PIN" screen, then reboots before I have a chance to enter anything.
Normal State have Cyanogenmod and Franco Kernel running buttery smooth. (CM10.1M3 Snapshot + Franco 376 when problem started)
Problem Started When I tried to update CM to the new RC1 from the Cyanogenmod upgrade button in "settings". I had SuperSU installed overtop the built-in superuser. Everything was working fine.
What I have tried:
Have latest CWM: Have flashed, reflashed, wiped and re-wiped everything imaginable through CWM. All Caches, system sdcard, you name it, if it's an option in CWM I have tried formatting or wiping it and reflashing a ROM.
ROMs I have tried - CM10.1M3 Snapshot, CM10.1RC1 CM10.1RC2, ParanoidAndroid 3.5+ (Latest), Bigxie Maguro Latest.
Finally I got fed up and decided to go back to STOCK, unrooted, unlocked using fastboot.
I did:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader magurobootloader.img
> fastboot reboot-bootloader
> fastboot flash radio radioxxlj1.img
> fastboot reboot-bootloader
> fastboot -w update image-maguro-jdq39.zip
And after booting back into the STOCK google recovery (man I haven't seen that screen in AGES) and resetting factory clearing cache. Low and behold -
STILL BOOT LOOPS!!!! What the hell!?!
I'm at my wits end. Any suggestions would be great. What am I forgetting here?! I am absolutely desperate.

What is in the update image and where did you get it? I'd flash everything manually, skip the update command.

bodh said:
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
Click to expand...
Click to collapse
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.

Vihsadas said:
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Click to expand...
Click to collapse
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?

Vihsadas said:
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Click to expand...
Click to collapse
So decided to try TWRP just to see...well I dunno.
Interstingly enough when I got to hit "reboot" in TWRP it says "OS not installed!!" which is weird because I basically flashed the stock everything 4.2.2 (bootloader recovery, system, boot, everything) from fastboot. Then JUST flashed the TWRP recovery.
I really don't know what to make of this. I just tried keeping the battery out for like 2 minutes, then going back into fastboot and manually flashing:
bootloader
boot
radio
recovery
system
userdata
relocked bootloader
of the STOCK google maguro 4.2.2 (MD5 sum is good. It checked out)
And I still get a continuous reboot loop that doesn't even get past the "X" animation screen. Very ocassionally (1/10) it does get past that screen and I get to the screen where you choose your language, but right when I choose my language, the phone reboots and then continues the loop.
Honestly...Unless someone has another idea, I think I'm going to get another phone tomorrow and pray I'm under warranty. I hate to do it, because I've never had to do that before through all my flashing/ROM adventures...but I don't know what else to do. I've been using sideload for everything (except of course the fastboot flashing back to stock), but I doubt that has anything to do with it...I dunno crap.
anyone have any words of advice?

One thing I thought i might work was redoing the partition table in Odin. So I tried this method:
http://forum.xda-developers.com/showthread.php?t=2065470 (Thanks to Samersh72)
ODIN worked perfectly, download mode worked well, installed fine, and...
still bootloops!
Sometimes gets to "updating android" does a few apps, then bootloops. Once got to the screen where I select language, and before I could select anything - bootloop!
Do you guys think this is hardware? Right now I've installed stock 4.2.2 through ODIN and locked the bootloader in anticipation of returning the phone...

give a try to omap flash
Good Luck

samersh72 said:
give a try to omap flash
Good Luck
Click to expand...
Click to collapse
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?

Vihsadas said:
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Click to expand...
Click to collapse
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center

samersh72 said:
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
Click to expand...
Click to collapse
Yeah you're right. OK done.

While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus

bk201doesntexist said:
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
Click to expand...
Click to collapse
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?

Vihsadas said:
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Click to expand...
Click to collapse
Yes, but There's a build.prop property that enables ADB debugging.. Since you have access to a custom recovery, you can mount /system rw and make your changes there.
Sent from my Nexus

Similar issue
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!

lsal25 said:
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
Click to expand...
Click to collapse
I dont know if you already did but try to wipe /system also and then flash a ROM.
Sent from my Galaxy Nexus using XDA Premium HD app

Help - Bricked M9 - yes my fault come read and laugh (and help)

Hi all, I need help with a big big problem.. Long story short, I bricked the phone. I think it's gone forever but I'm trying to ask here if someone got ideas.
First I want to say I got another M9 rooted, custom rom installed etc and got no problems, but I did it long time ago, with older methods, while now I tried using Windroid Toolkit (http://forum.xda-developers.com/showthread.php?t=2499926).
Here's the story:
- Unlocked phone via HTCdev ==> OK and everything worked;
- Downloaded and installed Windroid Toolkit, and with this installed TWRP 3.0.0 ==> OK and everything worked;
- Always via Windroid toolkit installed SuperSU ==> Windroid Toolkit sends you in recovery TWRP and you select the right supersu.zip file. Installation completed ok, but when I rebooted phone, it went in loop: showed start white screen with HTC logo and red text ("This build is for development bla bla bla") for X seconds, then reboot, and so on forever.
At that point I was still safe because I could still enter bootloader/ recovery etc, BUT... Don't ask how, don't ask why :crying: :crying: :crying: , shame on me I entered recovery / ADVANCED/ WIPE and wiped: dalvik cache, cache, system, data, internal storage... ( yes I know.. total stupidity :silly: ).
So now I am stuck at white screen with HTC logo and red text. I cannot reboot, I cannot even switch off phone keeping POWER button pressed! ("yeah you moron, you deleted os!" I know I know..).
If I connect phone to PC i hear the USB Windows sound but giving "adb devices" says "List of devices attached" like nothing is connected.
Also tried with RUU.exe but nothing (first version I found for M9, it is just to tell you it cannot see the device "Ensure your device is connected to USB").
Now I am waiting for the phone to run out of battery so I can try to VOL DOWN + POWER btn but I have no hope...
So in the end, do you have some idea?
I am very angry because I always rooted and installed custom roms, starting from HTC Diamond, always bought only HTCs and never had a problem, now I did this bulls**t with the phone I bought as gift for my father..
Thanks everyone any help will be appreciated.

try VOL UP + POWER
i start with HTC Diamond too, used one X, M7 and now M9, it really hard to brick compare to previous phone

Press VOL DOWN + POWER until you reboot to bootloader. From there reboot to recovery and flash custom rom.
fyi I always wipe dalvik cache, cache, system, data when installing custom rom coming from other roms and I don't have any issues whatsoever.

Most likely just change supersu for version 2.65. M9 is finicky about supersu.
Beamed in by telepathy.

If you were not S-OFF and wiped "real" firmware partitions like hboot, radio and so on your device is not bricked at all as the others already stated
1. Try VOL UP + POWER or VOL DOWN + Power until you reboot to Bootloader
2. Enter Download / Fastboot mode and flash new recovery using fastboot flash recovery yourRecoveryFile.zip
3. Reboot into recovery
4. adb push yourCustomRomFile.zip /sdcard
5. Flash Custom Rom
6. Full Reboot
7. Enter Recovery
8. Flash supersu 2.65 or 2.71 Beta
9. Full reboot
10 Be happy

Ok guys really thank you, so do you say its is not bricked. I will try as soon as I have time and/or battery dies (already tried with VOL DOWN + POWER but not with VOL UP + POWER ).
With my other M9to flash custom rom I had to get S-OFF with Sunshine app.
If I can enter recovery, can I flash a custom rom even if i am S-ON? Now I am in unlocked state and S-ON.
Eventually can I try restore my other M9 backup, done with TWRP 2.8.7.1, to this M9 having TWRP 3.0.0-0? I will check but I think they got same firmware (3.35.401.12).
Thanks again everyone

You don't need to be S-OFF to flash a custom ROM. You only got to check if the ROM base matches the firmware that is currently installed on your device
S-OFF unleashes just a little bit more freedom to play with your device, but at the same moment the risk of making a mistake and really bricking the device is highly increased.
Sent from my HTC One M9 using XDA Labs

This is a good example of why I hate toolkits and advise people never to use them, unless you already know how to do all this stuff manually. It's too easy to get into trouble you don't know how to get out of.
Try pressing all three buttons until you reboot if the other options don't work.

iElvis said:
This is a good example of why I hate toolkits and advise people never to use them, unless you already know how to do all this stuff manually. It's too easy to get into trouble you don't know how to get out of.
Try pressing all three buttons until you reboot if the other options don't work.
Click to expand...
Click to collapse
Yes you are right, before to start play with roms and stuff I usually lost days and days reading everything possible for every passage, while this time I was like "Oh cool a toolkit! Easy way let's do it!". Anyway I don't want to give responsibility to Windroid toolkit, only my fault I did things without thinking too much.
Respect for eveyone working hard to give us knowledge and this beautiful forum!
I will keep you informed thanks again everyone

Ok guys here I am.
Everything ok now thanks everyone again.
With phone switched off due to dead battery I was able to start with VOL DOWN + PWR and I could reach bootloader, download mode and recovery. Installed custom ROM, flashed SuperSU 2.65 and now I am on the road again :good::good::good:.
Only problem left is since I installed ROM (ViperOneM9 4.3.0) I cannot use adb: adb devices return "unauthorized".
I read various posts and the problem seems to be the phone not showing prompt to accept RSA key.
If I connect my other M9 everything is ok.
I think to have tried most of everything people suggest in different posts:
- updated android sdk
- reinstalled android sdk
- deleted adbkey and adbkey.pub in my %user%/.android folder (it recreates files but still no prompt on phone)
- reinstalled drivers on PC
- reinstalled rom with wipe during aroma installer
- looking in the phone in "system/data/misc/adb" for keys files but my folder is empty (checked on my other fully working M9 and that folder is empty too)
- tried install Minimal ADB and Fastboot [4-27-16] http://forum.xda-developers.com/showthread.php?t=2317790
- toggled USB debugging on/off rebooting phone and PC
If you have more advice I am glad to hear.
Thanks again to everyone to get my phone back working!

Is your other m9 running the same rom? The problem wont be the pc. If you can see one you can see all. Adb is versatile like that..
Try adb at twrp or one of the other booting modes. I'm quite sure adb is twrp only..
Beamed in by telepathy.

shivadow said:
Is your other m9 running the same rom? The problem wont be the pc. If you can see one you can see all. Adb is versatile like that..
Try adb at twrp or one of the other booting modes. I'm quite sure adb is twrp only..
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi, on other M9 i have same rom but 4.2.1 version (4.3.0 on not working one).
If I go on recovery or bootloader or download mode adb return "list of device attached" like it dosnt feel nothing connected. On the other M9 all is ok.
I just tried install a VM with Windows 7 but I am not able to let it see the USB device

Thread closed at OP's request. He has been able to resolve the issue.

TWRP - Working /data decryption on Android 9 (3.3.1-0)

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research about modifying your android system before flashing this!
* YOU are choosing to make these modifications, and if you point the finger at
* me for messing up your device, I will laugh at you. Hard. A lot.
*/
As you might know, the official version of TWRP for Nokia 8 is not able to correctly decrypt /data partitions that were made using Android 9. This means, if you updated an oreo installation, you can still decrypt your data, but if you did a factory reset under Pie, TWRP will fail at decrypting. Since that makes large parts of it useless, I tried to figure out how to compile TWRP. The result is this TWRP build.
With the prepatched TWRP boot images I have been doing since October, it was required to create a new boot image for every security patch version, since otherwise the wifi driver would fail to load correctly. This new image does not have this problem, since the wifi driver is compiled into the kernel itself, and not loaded externally. This means that as of now I will not continue to upload images for new security patch images to my cloud storage. You can flash my new image on every security patch version and it will continue to work correctly.
How to install:
Reboot into fastboot mode
fastboot flash boot twrp-3.3.1-0-NB1.img
fastboot reboot
You need an unlocked bootloader for this.
After flashing TWRP you will normally boot into android. From there you can then reboot into recovery by doing adb reboot recovery, or powering off the device, and pressing the volume up while connecting it to a PC via USB.
Links:
TWRP: https://github.com/resident-nokia/twrp/releases
Device Tree: https://github.com/resident-nokia/twrp - You *could* build TWRP with the official tree as well but I had various issues with it.
Umbrella Kernel: https://github.com/resident-nokia/umbrella
Credits:
Dhruv Gadhavi - for the official TWRP
Numerous people from the telegram group testing my kernel and TWRP builds

Good Job

Thank you
Sent from my Nokia 8 using XDA Labs

Exactly what I was looking for!! Thanks bunches
It's still not working for me : (

I finally got it to work for me... But now I can't activate WiFi and my MAC address is reading "Unavailable"
Have already tried a factory reset, but then I still can't find any WiFi networks during the system setup

What about custom ROM's?

@THMSP
It's very interesting ?
And it's very good that you tried to make something for our device. Everyone's work will be useful I think.
In these days I also playing with Nokia system files, but only with Nokia camera. It's strange that the newest apks are not working on our device, in the beginning I was surprised, and now I took linuxct mod and made some small modifications (of course I'm a noob ?) to make it more stable. Now it's working not bad. I uploaded it to 4pda forum thread.
But that's not the point. The point is that for some ridiculous reasons HMD restricts Nokia 8 users, it's upsetting.
Anyway, you're doing great. If you don't mind, I'll add a link to your post from 4pda...
Thanks!

this is interesting, good job. I will keep an eye out for future updates regarding the custom kernel.

Great work! One great future for this Phone!

I mistakenly disabled an important system file now the phone reboots into recovery every time it finishes booting up. The problem now is that my current TWRP doesnt decrypt so now I cant get adb and fastboot to work so I can re-enable the app. How can I flash your patched TWRP so i can fix this boot issue? fastboot doesnt recognised my device when booting into download mode from inside TWRP.

MDV106 said:
I mistakenly disabled an important system file now the phone reboots into recovery every time it finishes booting up. The problem now is that my current TWRP doesnt decrypt so now I cant get adb and fastboot to work so I can re-enable the app. How can I flash your patched TWRP so i can fix this boot issue? fastboot doesnt recognised my device when booting into download mode from inside TWRP.
Click to expand...
Click to collapse
Did you install the Nokia 8 fastboot driver? If no, try to install it (https://github.com/StollD/nokia-driver-installer/blob/master/out/Phone_Nokia_USB_Driver_v1.4.0.exe) and see if your device is recognized in fastboot again.

THMSP said:
Did you install the Nokia 8 fastboot driver? If no, try to install it (https://github.com/StollD/nokia-driver-installer/blob/master/out/Phone_Nokia_USB_Driver_v1.4.0.exe) and see if your device is recognized in fastboot again.
Click to expand...
Click to collapse
I managed to install your patched TWRP from within the previous version of TWRP. but the "recovery" partition didnt show up as an option to flash so I flashed your img file to the boot partition. When I rebooted to recovery it worked and the file system was decrypted successfully. Now the problem I have is that when I boot into the OS, Im stuck on the Nokia logo and I keep hearing clicking sounds of the camera lense every 5 seconds. Its still stuck there. Any idea how I can fix this?

MDV106 said:
I managed to install your patched TWRP from within the previous version of TWRP. but the "recovery" partition didnt show up as an option to flash so I flashed your img file to the boot partition. When I rebooted to recovery it worked and the file system was decrypted successfully. Now the problem I have is that when I boot into the OS, Im stuck on the Nokia logo and I keep hearing clicking sounds of the camera lense every 5 seconds. Its still stuck there. Any idea how I can fix this?
Click to expand...
Click to collapse
Reflash the stock firmware using (N)OST. Every attempt to fix this manually is probably not worth the efford. After that, just reflash the TWRP image in fastboot.

THMSP said:
Reflash the stock firmware using (N)OST. Every attempt to fix this manually is probably not worth the efford. After that, just reflash the TWRP image in fastboot.
Click to expand...
Click to collapse
How do I do that? The phone simply wont turn on or off at this point. Its been stuck on the "nokia" screen for the past 2 hours or so. I am just trying to figure out a way to force switching it off since the power button wont respond. Then from then on I plan to just restore a Nandroid backup then restore app data using a Titanium backup I made earlier this week. If only I could get the phone to turn off. Do you have any idea how?

MDV106 said:
How do I do that? The phone simply wont turn on or off at this point. Its been stuck on the "nokia" screen for the past 2 hours or so. I am just trying to figure out a way to force switching it off since the power button wont respond. Then from then on I plan to just restore a Nandroid backup then restore app data using a Titanium backup I made earlier this week. If only I could get the phone to turn off. Do you have any idea how?
Click to expand...
Click to collapse
Keep all three buttons pressed for multiple minutes until the phone turns off. Then boot into recovery by holding down volume up while connecting the phone to a computer via USB.

THMSP said:
Keep all three buttons pressed for multiple minutes until the phone turns off. Then boot into recovery by holding down volume up while connecting the phone to a computer via USB.
Click to expand...
Click to collapse
I decided to let the battery drain. I am recharging now and will attempt to do a system restore once the percentage is at 20%. Btw, I see you are very active in Nokia 8 development and are one of the most knowledgeable members on this sub-forum. So I have to ask, do you ever plan on creating a custom ROM for the Nokia 8 in the future? It doesnt seem like any other people here are interested or have the knowledge to do it.

Okay I managed to restore my system to a previous state that has a prepatched twrp 3.2.3-1 . When i followed these instructions and flashed the updated twrp, the boot hangs at the yellow unlocked bootloader screen then after about 30 seconds boots back into download mode. It wont even let me turn it off and reboot to recovery. not sure how to fix this.
EDIT: decided to switch slots and flash this image on the new slot. Same thing happened. phone wont boot and it hangs and refused to turn off no matter how long i press the 3 buttons. I tried this at the worst time now Im left without a working phone on a weekend

MDV106 said:
Okay I managed to restore my system to a previous state that has a prepatched twrp 3.2.3-1 . When i followed these instructions and flashed the updated twrp, the boot hangs at the yellow unlocked bootloader screen then after about 30 seconds boots back into download mode. It wont even let me turn it off and reboot to recovery. not sure how to fix this.
Click to expand...
Click to collapse
Please post the exact fastboot commands you entered to flash the TWRP image. Also, please redownload it and try to flash it again, just to make sure the image isn't corrupted.

How do I unlock the bootloader on ??
Sent from my NB1 using XDA Labs

THMSP said:
Please post the exact fastboot commands you entered to flash the TWRP image. Also, please redownload it and try to flash it again, just to make sure the image isn't corrupted.
Click to expand...
Click to collapse
sudo fastboot flash boot_a twrp-3.2.3-2-NB1.img
sudo fastboot rebooot
^ These were the commands. even after switching slots the phone froze on boot and then booted itself back to download mode. AFter a couple of tries it just froze on boot and never wanted to turn off. Again, I had to let the battery drain to turn it off.. Now im chargin it again so I can restore my previous backup. Hopefully it will be able to boot into recovery