Related
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
Hey all; first post and 100% green with rooting. This is my first attempt and i'm hitting a stumbling block.
First off, I've been using the guide on "theandroidsoul"(can't post a link due to post count, but a quick google search should bring you to the exact one)
I have successfully setup ADB, unlocked the bootloader, flashed TWRP 3.2.3-1 and have been able to boot into it using ADB.
However on step 10 of the guide i'm using, it's not too clear if i should skip formatting the device memory or go ahead and do it. I did it. I suspect this might be where i went wrong.
Regardless, i'm able to move Magisk onto the internal storage and TWRP is able to install it successfully.
Once i try to reboot, the "bootloader unlocked" warning screen shows, then the oneplus boot screen appears. It shuts down and reboots like this a second time, then the screen goes black and the front LED illuminates white and nothing happens. I can shut down the phone by holding the power button, then boot into fastboot manual using power + volume up. However if i try to boot the phone normally or boot into recovery mode, it repeats the same symptoms.
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB. But no matter how many times i try to install Magisk(I tried both v18 the guide mentions and the latest v19 from their site) i can't get it to boot.
I'm aware i also used an outdated version of TWRP(the one the guide mentions). i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?
Hi all,
I'm facing the same issues as Josh and came seeking help, as well, so any help would be greatly appreciated! This is my first foray into Android coming from Windows 10 Mobile, which I'm still using two weeks after purchasing the 5T because of these issues. No matter what I do, I cannot get it to work and am now stuck in the same loop as mentioned above.
I'm attempting to install LineageOS and followed the instructions on its official site to a T, but have never been able to get it to boot into the OS. The only difference from the original poster's issue is that I'm not trying to root the device.
Thanks again for any help!
Josh Hex said:
....
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB.
....
i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?
Click to expand...
Click to collapse
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.
Amix73 said:
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.
Click to expand...
Click to collapse
Thank you. I'll give it a shot and will let you guys know how it works out!
Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
dm-verity device corrupted Force Dump
Kernel_restart
Click to expand...
Click to collapse
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Which specific model do you have, region? Which twrp was used?
Werchio said:
Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Click to expand...
Click to collapse
TWRP?! There are no working twrps for 7T series.
gpz1100 said:
Which specific model do you have, region? Which twrp was used?
Click to expand...
Click to collapse
Oneplus 7, EU region (guacamoleb). TWRP that I have managed to boot into is 3.3.1-70.
Aswin08 said:
TWRP?! There are no working twrps for 7T series.
Click to expand...
Click to collapse
My bad. It is a Oneplus 7 Guacamoleb, TWRP version is 3.3.1-70
Oneplus 7T Qualcomm CrashDump Mode
Hi Everyone,
My OnePlus 7T got stuck in QUALCOMM CRASHDUMP MODE.
First, i wanted to know the reason why this crash is happening as i can see many users reporting the same in many forums.
Note : It is my brand new phone purchased 2 days back.
Thanks !!
Restor your firmware with the msmtool
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" .
Now ADB,Fastbootd and Windows 10 / Mac OSx do not see my device, let alone recognize
It's possible that your phone is corrupted. Double freezer bag phone, express all excess air out from bag, zip both bags tightly, stick phone in freezer for 1 hr to deplete battery, then try buttons and msmtool
So, I made a big blunder.......
I have a global version OnePlus 7T, HD1903, 128GB ROM + 8GB RAM, and I wanted to install Magisk. I'm not at all experienced with android rooting and adb (think toddler level) and so I'm following a YouTube tutorial, until I accidentally flash the Magisk apk file instead of the boot image from the phone (both were in the downloads folder, and I didn't see). Stuck in a bootloop. Flashed the boot.img from the stock image from the oneplus website after using payload dumper, and didn't get WiFi and SIM functionality.
Decided to lock my bootloader, thinking that locking it will cause a wipe, which will restore everything. Now currently, I'm stuck at 'Your device is corrupted and won't boot' with a locked bootloader, unable to get into fastboot or recovery.
Does anyone have any idea what to do?
I have never had to use this before, but there is an Unbrick tool that may get you back up and running.
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
I tried for like 3 hours to find a boot.img and i had root on my phone, but without wifi and sound.
a quick google search showed me that it was because i had a wrong version of the boot.img, afterwards i found another one and now after i have tried installing twrp, booting and flashing using adb (stock and modified versions of boot.img) but it just keeps bootlooping. in twrp i cant wipe, make a backup, see any files in /storage/ and i have no clue what to do next.
What model 7T do you have? HD1907? What was the rom that you were using before you installed TWRP on? OOS12 does not support TWRP. Custom rom A13 does not support TWRP. Only a few custom rom A12 and OOS11 support TWRP.
Idk but I'm just wondering if flashing the last working rom image (dirty flash)? That would eliminate TWRP(?) and eliminate Magisk(?) while hopefully keeping the device from being wiped possibly?
*** Hopefully someone could/would verify this before you attempt... ***
i was on android 11 but i cant remember the version, i have HD1903 (EU ver). i THINK i had the one from the oneplus website(https://service.oneplus.com/us/search/search-detail?id=2096229) but idk anymore
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
MimKA22 said:
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
Click to expand...
Click to collapse
Msmtool back to oos11
can you describe how to use it or send a link to tutorial or smth thx man <3
MimKA22 said:
can you describe how to use it or send a link to tutorial or smth thx man <3
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
i cant find the file for my current version and it doesnt work if i try it with the only version that is android 11
and i cant turn my phone back on
and after i installed the drivers i had to restart my pc and now there is this thing at the bottom right:
testmode
windows 10 pro
...
i waited until my phone had no more battery charge and now im bootlooping again :/
nvm it just booted
im downgrading it now and i dont get the error "smth communication smth" in msmtool anymore
alr it worked my phone is wiped again but i can turn on wifi and sound
but how do i root my phone now? I have an Idea, im gonna write step by step what i think gets me a rooted phone please confirm if that would not break my phone ^^' (bootloader already unlocked)
1. enable usb debugging and allow my pc
2. download and install the latest magisk version from the github
3. download magisk patched boot.img for ver 11.0.5.1BA BUT since i cant find anything on the internet im gonna have to use the zip file from the unbrick tool thing (https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/EU_HD65BA/R/) and then patch the boot.img using magisk myself
4. then use platform tools and type following commands: "adb reboot fastboot", "fastboot flash boot {the patched boot image file}"
5. then use magisk to direct install the root thing
i just realisized the unbrick thing that i wanted to use instead of a boot.img doesnt have a boot.img in it... WHERE CAN I FIND A BOOT.IMG brooo androidfilehost.com doesnt have it the unbrick tool doesnt have it
omg i realized i could update my phone to 11.0.9.1 then download the same version from official website and use the dumper to get the boot.img **** meee
wait it sais its 11.0.9.1HD65 AA and not BA **** me
k nvm i just changed the site settings to germany and now its BA
i just went for it and now my phone is rooted thank you very much for your help i would've prob tried to revert back to stock for like 2 weeks and then cry that i cant root my phone thank you so much xd