Develop Bugs

[Q] Help! - Rooted Zenfone 2 (ZE551ML) bricked after OTA accidently

followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?

Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?

If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.

joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...

I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps

Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse

xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.

This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse

xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.

actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.

dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.

5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?

ZE551ML Stuck in bootloader. No access to recovery what so ever.

So after 2 hours of searching, trying and failing, I just decided to post here and see what help I can get.
Situation is exactly like the title. Had Lineage 14.1 installed, and decided to update the phone. Rebooted the phone and went to TWRP recovery. For whatever reason, I decided to reboot the phone, which ended up in it coming back to TWRP. This repeated until I got the stock recovery, which put me into bootloader instead. Bootloader is now locked, I can no longer get into recovery, and I'm stuck in bootloader for as long as this continues.
So far I have tried:
--------BEFORE TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Factory Resetting
Formatted and flashed ROM
A couple of ADB commands
--------AFTER TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Replaced recovery image file with stock
Idiotically replaced bootloader image file with stock (Locked, can tell since Android N is no longer bugging me with preboot notification which was present before when bootloader was unlocked)
Idiotically replaced the system image file with stock
A slew of fastboot commands (You can comment and I can see if I have attempted them)
Attempted to continue the fastboot process
Attempted to use an automatic rootkit. Did not like my device, so it did nothing at all.
Manually unplugging the battery
Haven't tried:
Placing rom in sd card, like I've seen people say elsewhere. (No SD card available)
Anything else you tell me that I haven't done
I'm not really interested in keeping any files that I've had before, if that is not already made clear.
Anyone that can help me, I really want this to end. :crying: :crying:

BillJake said:
So after 2 hours of searching, trying and failing, I just decided to post here and see what help I can get.
Situation is exactly like the title. Had Lineage 14.1 installed, and decided to update the phone. Rebooted the phone and went to TWRP recovery. For whatever reason, I decided to reboot the phone, which ended up in it coming back to TWRP. This repeated until I got the stock recovery, which put me into bootloader instead. Bootloader is now locked, I can no longer get into recovery, and I'm stuck in bootloader for as long as this continues.
So far I have tried:
--------BEFORE TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Factory Resetting
Formatted and flashed ROM
A couple of ADB commands
--------AFTER TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Replaced recovery image file with stock
Idiotically replaced bootloader image file with stock (Locked, can tell since Android N is no longer bugging me with preboot notification which was present before when bootloader was unlocked)
Idiotically replaced the system image file with stock
A slew of fastboot commands (You can comment and I can see if I have attempted them)
Attempted to continue the fastboot process
Attempted to use an automatic rootkit. Did not like my device, so it did nothing at all.
Manually unplugging the battery
Haven't tried:
Placing rom in sd card, like I've seen people say elsewhere. (No SD card available)
Anything else you tell me that I haven't done
I'm not really interested in keeping any files that I've had before, if that is not already made clear.
Anyone that can help me, I really want this to end. :crying: :crying:
Click to expand...
Click to collapse
What is your IFWI version number in bootloader ?

IFWI Version: 0094.0183

BillJake said:
IFWI Version: 0094.0183
Click to expand...
Click to collapse
Flash raw 4.21.40.184 M with AFT in bootloader
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966

Thank you so much. Fixed my phone.

BillJake said:
Thank you so much. Fixed my phone.
Click to expand...
Click to collapse
Marvelous , drop a thank you to realyoti in the link , hit his thanks button too.:good::highfive:

various issues with google variant

I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?

I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.

stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:

I agree. I got it used tho which is an issue.

Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.

stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.

Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.

Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?

stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.

Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.

I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.

MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:

stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.

smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.

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

NERVOUS about flashing Lineage 18 :-(

HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler

Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom

Tsuragi said:
Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom
Click to expand...
Click to collapse
Thanks Tsuragi,
Forgot about that - it was me who posted that solution some time ago duh!
Pootler

pootler said:
HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler
Click to expand...
Click to collapse
Hey bro same experience, thats why im stock in android 10 with unlock bootloader. but i successfully flashed lineage with unofficial twrp but the problem is i cant flashed gapps thats why i cant install pre apps and cant use the default message and call. please help me