Bootloader loop after flashing T-Virus - Nokia 8 Questions & Answers

Hello,
I've been trying to install Pixel Experience on my phone following these guides
Install PixelExperience on NB1 - PixelExperience Wiki
Install PixelExperience on NB1 - PixelExperience Wiki
wiki.pixelexperience.org
Nokia 8 (NB1) Full ROM Installation Guide
In this guide, you will find: What you should do before installing a custom ROM on your Nokia What are the button combinations of Nokia 8 for reboot to download mode, recovery mode, and etc How to install T-Virus (project treble) on Nokia 8 How...
forum.xda-developers.com
Just as described I've downloaded Nokia drivers. My phone already had unlocked bootloader via official HMD method so i went over to the next step and T-Virus.
I entered fastboot sucesfully by enabling USB debugging. Downloaded T-Virus from the guide link and executed Windows command. Followed all steps in command window.
During the process I've noticed repeating error "Invalid sparse file format at header magic" if it's important.
Anway it finished and said that my phone will enter ROM now but after restarting it's back at bootloader.
I tried entering recovery via key combinations but they won't work.
I can detect my phone in fastboot and even when i type in
fastboot reboot recovery
It will still reboot into download mode.
Any help appreciated how to get my phone to work again.

Okay, crisis averted, I reverted T-Virus and now i can boot to android again.
But I still want to know why T-Virus failed and cause bootloop on my device?

I've noticed that despite having unlocked bootloader my critical is locked. Could t
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
his be the source of issue?

Yup that was it.
I had to repeat fastboot flash unlock unlock.key and then fastboot flashing unlock_critical to get critical unlocked and now T-Virus installed without any issues.

Hey got the same problem, how did you revert and unlock critical?

Related

Unfortunatelu, the process com.android.settings has stopped

Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Please any help is greatly appreciated I have been up now for nearly 20 Hours trying to get this done.
Exactly like this
dugie33 said:
Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Click to expand...
Click to collapse
Because you are boote din bootloader mode. ADB can't work when in bootloader mode, only from custom recovery or from a booted rom + usb debug on. Here a nice table I made last week to explain the same thing to another guy:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (remove your imei and sn before posting)

Moto G5s Plus Bricked

Here's the background on how it got bricked
i tried unlocking bootloader whcih went succesfully.
then flashed twrp, also succesfully. Could boot into it and the rom
So i started flashing a custom rom without a backup..erased system,cache,dalvik,userdata etc and went into flash rom but it was 64bit rom but my twrp was 32 bit.
i tried installing 64 bit one but phone wont boot into it.
so i decided to flash stock through fastboot
i downloaded a rom which was for moto g5 plus...i didnt realised 5s plus and 5 plus were two different phones...fricked up there
i went to reboot and the phone just went blank, wont display anything,wont boot or any response at all.
but its being recognized as Fastboot Sanders S on my PC and i can access fastboot but phone wont turn on no matter what roam i flash through fastboot.
I was on latest Oreo 8.1 august patch and the flashing goes smoothly, only getting error in bootloader...."security downgrade" stuff
Is there a way i can fix this or is the device just gone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG][/IMG]
dr3mz said:
Here's the background on how it got bricked
i tried unlocking bootloader whcih went succesfully.
then flashed twrp, also succesfully. Could boot into it and the rom
So i started flashing a custom rom without a backup..erased system,cache,dalvik,userdata etc and went into flash rom but it was 64bit rom but my twrp was 32 bit.
i tried installing 64 bit one but phone wont boot into it.
so i decided to flash stock through fastboot
i downloaded a rom which was for moto g5 plus...i didnt realised 5s plus and 5 plus were two different phones...fricked up there
i went to reboot and the phone just went blank, wont display anything,wont boot or any response at all.
but its being recognized as Fastboot Sanders S on my PC and i can access fastboot but phone wont turn on no matter what roam i flash through fastboot.
I was on latest Oreo 8.1 august patch and the flashing goes smoothly, only getting error in bootloader...."security downgrade" stuff
Is there a way i can fix this or is the device just gone?
[/IMG][/IMG]
Click to expand...
Click to collapse
If you got fastboot, then just flash the stock firmware and boot it. Note:- remove bootloader and gpt commands from the fastboot so it won't get brick.

Question I locked the bootloader by misstake

Hello, what I did was the following:
1. signed on a new phone with account A, waited a week and unlocked the bootloader
2. signed on the same phone with account B
3. flashed fastboot rom on the device with mi flash tool, but forgot to uncheck the " lock the bootloader"
4. the phone is not starting - i can only get the recovery and the fastboot mode.
5. mi flash tool wont let me flash to locked device . Mi flash tool2 makes me go into Mi assistant mode, starts the instalation process but failes after a few mins ( on the pc i reach ~ 700% but on the phone the bar is on 4.99 or 52.78 % )
6. Xiaomi ADB/Fastboot Tools doesnt want to flash as the device is locked and if i try the OEM UNLOCK button i get "FAILED (status read failed (Too many links))"
7. If I try to unlock the bootloader again and I log account B i get message that i need to log on the phone and wait for a week
If i log accont A i get this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any Idea how to fix it
Thanks in advance, and sorry if this is the wrong place for this question
As far as I know, the only way is to ask after-sale for help.
ddspj said:
As far as I know, the only way is to ask after-sale for help.
Click to expand...
Click to collapse
They might have more underlying tools to unlock and flash your phone.
fastboot flashing unlock
for most of aosp rom this is the command. but i'm not sure that works on miui. i found a java tool that maybe can help you. https://miui.blog/any-devices/xiaomi-adb-fastboot-tools-one-utility/ i have used to debrand my phone without unlock it
I had to send it to a friend of mine who was able to install chaina rom, using EDL mode, but now, for some reason the IMEI's are gone. I can not add mi account, and for that reason I can't unlock the bootloader, right now I am battaling with the IMEI restoration ( i have the original imei's on the phone case) I am trying to use modem_meta_tool, but with no suxcess . I can't get my phone connected
Long story short, EDL mode was needed to get out of my original situation
seem you have lost imei cause you have installed china rom. or a rom incompatible with your region. try install global rom via edl. but if you lost imei, restore it is not simply... you can try to enter into engineering mode. i'm not sure but there's a function to change imei. but not working for all mtk processors

AOSP 11 fastboot flashing lock unknown command

Hi all,
By follow the sony open device aosp build instruction with all the steps successfully.
https://developer.sony.com/develop/...structions/build-aosp-android-android-11-0-0/
But when starting the phone, it shows an error message and nothing more
`Your device software can't be checked for corruption. Please lock the bootloader.`
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I try to relock the bootloader, it did shows that the device already unlocked
but when I try to lock, it shows 'unknown command'
Any ideas? thanks
Hey. Just a heads up--the screen notifying about unlocked bootloader is normal. Since unlocking the bootloader I get the same notification during startup and then it boots normally into the ROM. Whatever the startup issue is, I wouldn't conclude it's caused by unlocked bootloader based off that screen.
In regards to the issue with relocking the bootloader, I had ran into a similar nondescript error with adb while trying to flash TWRP, it read 'FAILED (Status read failed (No such device))' and after a lot of googling I found that the solution is to try different computers/USB ports. In my case I had to use another laptop's USB port while running Linux/EndeavourOS from thumb drive (fastboot was/is unreachable under Windows for my XZ1c).
upd. Oh, it seems relocking the bootloader is not as easy as fastboot oem lock. Nevermind.
I'm not sure which question you're asking.
If it's that you see the message, it's normal, because you (or someone else) unlocked your bootloader. It's normal, and a warning (not an error), not a sign that anything's broken. But you maybe want to check your ROM or recovery, if you weren't the one who installed them, or you don't trust the person that did.
If it's that you can't re-lock the bootloader, that's ... also expected. You can't. No one has found a way to re-lock the bootloader on the XZ1 compact. So that command will always fail. It's not supported on your phone.
If the phone won't boot or is broken, it's likely for some other reason.

S10 stuck on boot after custom ROM flash

Hi good evening, this is my first post in xda, I've used the forum since my first android back in the htc era, since 7 years I used my s8 with the hadesRom and everything was amazing, then I've broken my beloved s8, really the best smartphone ever, and I've bought an s10 a couple of month ago
Then, yesterday I start to follow the Magisk guide for unlock the bootloader and root my S10 G973F-DS and after it the the one for install the TWRP with the PlayStore method.
Unlocked the bootloader, rooted it, Magisk was installed, then I had the first problem: the internal storage was down to 25gb, I've wiped from recovery data and cache and the storage came back to normal, I've installed the twrp with the appstore method, rebooted to twrp, and wiped again data and cache as said in the hadesRom install guide and then all the system was gone, the twrp refuse to reboot to the stock one so I've tried to flash the HadesRom and now it's stuck in the Samsung GalazyS10 bootup splash screen, it just reboot with Bixby+volumeDown+Power but it always just go back to the splash screen, it doesn't recognize any other button sequence neithe the adb devices recognize it...
can I save it?
Thanks in advance..
Use ODIN to flash latest firmware again. Then use ODIN to flash LineageOS, then install lastest PixelExperience and boot on it. After boot PE, use ODIN again to flash TWRP and flash any rom u like.
Thanks for the answer, but I can't flash anything, it's stuck in this splashscreen, It only reboot with volume- bixby and power, but it just goes back to this one again.
I've tried flashing the orIginal fw, but it's not recognized by Odin so if I start Odin nothing appens actually.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Samsung Galaxy S10 G973F Test Point – EDL 9008 Mode
By using the Samsung Galaxy S10 G973F Test Point, you can easily restore the stock ROM, bypass FRP lock, or reset user data on your device via UFi Box. In
www.mobilerdx.com
This link may help u

Categories

Resources