Can't flash stock anymore, please help? - Moto Z Questions & Answers

So I did a stupid thing and flashed SuperSU after updating to Android Nougat (UK) in TWRP, the phone won't boot, both of my TWRP backups will not restore my data (bootloop at untrusted device page).
Fastboot won't flash the stock MM anymore either and I get a FAILED every time after validating it says security version downgrade, (attached image).
Any help in getting my phone to boot would be much appreciated, I've never seen anything like this before.

It's OK! Don't panic. I did this too.
Reflash Rogers -45 firmware then adb sideload nougat again. You'll be back up and running.
From my experience with Nougat these last few days, do NOT flash SuperSU and do not try to modify the system partition in anyway or you will soft brick.
Also there error you're seeing is expected. You can't flash MM GPT over Nougat it won't let you (or then you'd really be bricked)
Just flash all of MM again so that Nougat can be sideloaded again

Prfndhatrdofman said:
It's OK! Don't panic. I did this too.
Reflash Rogers -45 firmware then adb sideload nougat again. You'll be back up and running.
From my experience with Nougat these last few days, do NOT flash SuperSU and do not try to modify the system partition in anyway or you will soft brick.
Also there error you're seeing is expected. You can't flash MM GPT over Nougat it won't let you (or then you'd really be bricked)
Just flash all of MM again so that Nougat can be sideloaded again
Click to expand...
Click to collapse
Thank you that's a relief, I just flashed Rogers -45 but get "No command." at recovery when I go to sideload nougat, do I flash TWRP again? I followed your easy flash guide, was I right in doing that? Thanks for your help
Edit: after flashing TWRP again and clicking ADB Sideload it gets stuck at "starting ADB sideload feature" not sure where i've gone wrong. Its 2am here so i'll try again tomorrow, appreciate all your help.

supacrazyguy42 said:
Thank you that's a relief, I just flashed Rogers -45 but get "No command." at recovery when I go to sideload nougat, do I flash TWRP again? I followed your easy flash guide, was I right in doing that? Thanks for your help
Click to expand...
Click to collapse
Don't flash TWRP.
When you are at No command, hold the power button for like 2-3 seconds (I sometimes press the volume key too) and you should see some commands!

Prfndhatrdofman said:
Don't flash TWRP.
When you are at No command, hold the power button for like 2-3 seconds (I sometimes press the volume key too) and you should see some commands!
Click to expand...
Click to collapse
Thanks, when running the flashfile.bat is it normal for it to say "not found" on each? I tried holding power, and again with volume after starting from scratch flashing Rogers -45 but still get No command. and then a bootloop Completely lost

It also has no baseband and says Console null but i'm not sure if that's relevant. Just can't seem to get into recovery at all now, tried flashing recovery again separately too.

Not Found error is fine, ignore that.
Also Baseband will be blank until after the first boot of nougat. Trust me!
OK so go back to recovery. You need to get the commands for recovery to appear.
Try again. Go back to Recovery, hold power button at the No Command and press Volume Down then power Up then let go of everything. The commands should show up. Try again! Ill see if i can record a video of me doing it shortly.
If you need to, re run the RSD Batch and try again.

Prfndhatrdofman said:
Not Found error is fine, ignore that.
Also Baseband will be blank until after the first boot of nougat. Trust me!
OK so go back to recovery. You need to get the commands for recovery to appear.
Try again. Go back to Recovery, hold power button at the No Command and press Volume Down then power Up then let go of everything. The commands should show up. Try again! Ill see if i can record a video of me doing it shortly.
If you need to, re run the RSD Batch and try again.
Click to expand...
Click to collapse
Brilliant! That worked to get commands, thank you. Time to try sideloading

Prfndhatrdofman said:
Not Found error is fine, ignore that.
Also Baseband will be blank until after the first boot of nougat. Trust me!
OK so go back to recovery. You need to get the commands for recovery to appear.
Try again. Go back to Recovery, hold power button at the No Command and press Volume Down then power Up then let go of everything. The commands should show up. Try again! Ill see if i can record a video of me doing it shortly.
If you need to, re run the RSD Batch and try again.
Click to expand...
Click to collapse
Yet another problem, sorry, but now in recovery i'm on "apply update from ADB" any idea why i'd get "cannot read Filename.zip " when trying to sideload? I tried mfastboot v2

supacrazyguy42 said:
Yet another problem, sorry, but now in recovery i'm on "apply update from ADB" any idea why i'd get "cannot read Filename.zip " when trying to sideload? I tried mfastboot v2
Click to expand...
Click to collapse
Also had the same problem. Reboot your computer, rename the zip to something like update.zip or something. If that doesn't work, reinstall your ADB drivers.

Prfndhatrdofman said:
Also had the same problem. Reboot your computer, rename the zip to something like update.zip or something. If that doesn't work, reinstall your ADB drivers.
Click to expand...
Click to collapse
Finally worked on a fresh start with another PC You're a life saver man :good:

supacrazyguy42 said:
Finally worked on a fresh start with another PC You're a life saver man :good:
Click to expand...
Click to collapse
Cheers!

please help phone bricked
i have the same problem and tried reflashing the stock rogers 45 firmware but i get these lines in terminal and it doesntwork. fastboot flash partition.. writing partition (bootloader) validating gpt.default.xml (bootloader) security version downgrade image primary_gpt failed validation preflash validation failed and some other lines basically saying the same thing. am i doing something wrong?

dchitolie said:
i have the same problem and tried reflashing the stock rogers 45 firmware but i get these lines in terminal and it doesntwork. fastboot flash partition.. writing partition (bootloader) validating gpt.default.xml (bootloader) security version downgrade image primary_gpt failed validation preflash validation failed and some other lines basically saying the same thing. am i doing something wrong?
Click to expand...
Click to collapse
Sent PM, I can only walk you through how I fixed it but it sounds similar. Is it saying downgrade error for every single file or just the first two? If just the first two I'd follow the easy flash to Nougat guide step by step.

Also I'm curious, is it possible to downgrade to MM from this? Flashing stock MM will just result in bootloops and downgrade errors again I assume.

Prfndhatrdofman said:
It's OK! Don't panic. I did this too.
Reflash Rogers -45 firmware then adb sideload nougat again. You'll be back up and running.
From my experience with Nougat these last few days, do NOT flash SuperSU and do not try to modify the system partition in anyway or you will soft brick.
Also there error you're seeing is expected. You can't flash MM GPT over Nougat it won't let you (or then you'd really be bricked)
Just flash all of MM again so that Nougat can be sideloaded again
Click to expand...
Click to collapse
You saved my ass! Thank you so much!

supacrazyguy42 said:
Also I'm curious, is it possible to downgrade to MM from this? Flashing stock MM will just result in bootloops and downgrade errors again I assume.
Click to expand...
Click to collapse
You can reflash 45 only so you can sideload Nougat again. Thats why you might see errors when flashing 45 because some of those items cant be downgraded anymore. Theres no going back to MM once you flash nougat.

Prfndhatrdofman said:
You can reflash 45 only so you can sideload Nougat again. Thats why you might see errors when flashing 45 because some of those items cant be downgraded anymore. Theres no going back to MM once you flash nougat.
Click to expand...
Click to collapse
Thanks for clearing that up :good:

I flashed Nougat in my phone, but the built quality of the rom is not stable. Is there any way to get back my stock MM 6.0. My device is Moto Z Play.

aniket1311 said:
I flashed Nougat in my phone, but the built quality of the rom is not stable. Is there any way to get back my stock MM 6.0. My device is Moto Z Play.
Click to expand...
Click to collapse
Assuming it's the same as with the Moto Z, if you're on the Nougat bootloader (from using OTA or by flashing everything including the new bootloader) there's no way back to android MM currently.

Related

Restoring Stock Rom on KIW-L24 but keeping TWRP

Hi guys,
I am using the link below to perform the restore to stock from CM13 but I think I am not interpreting the questions in this post correctly.
http://forum.xda-developers.com/honor-5x/how-to/guide-kiw-l24-to-stock-t3318268
I tried to follow them to get my Honor 5x back to stock rom (while still keeping TWRP) and it was a no go. I kept getting stuck in a boot loop. I was able to immediately reflash CM13 though and get it functionaly. Would someone be kind enough to verify for me as to what steps exactly I need to follow (including ROM names, etc.)? I would greatly appreciate it.
Thanks.
@DigiGoon here's a person needing your help
I have a couple questions for you:
1) Before flashing CM13, what stock firmware version were you on? (e.g. b130, b140, b151, b331)
2) Before flashing CM13, did you take a NANDROID backup of your stock setup? Most guides have this step.
Follow these steps, and you'll get your stock ROM back.
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
Hope this helps you.
@DigiGoon
You are a lifesaver. That seems to have done the trick. Thanks a lot man!
fistfullofbeer said:
Hi guys,
I am using the link below to perform the restore to stock from CM13 but I think I am not interpreting the questions in this post correctly.
http://forum.xda-developers.com/honor-5x/how-to/guide-kiw-l24-to-stock-t3318268
I tried to follow them to get my Honor 5x back to stock rom (while still keeping TWRP) and it was a no go. I kept getting stuck in a boot loop. I was able to immediately reflash CM13 though and get it functionaly. Would someone be kind enough to verify for me as to what steps exactly I need to follow (including ROM names, etc.)? I would greatly appreciate it.
Thanks.
Click to expand...
Click to collapse
There is also a full, latest twrp, recovery backup o.o for b331
You restore everything except data, erecovery, and recovery... 1.6 gig download o.o does the job in one fell swoop as long as you have latest twrp.
Just did this the other day...
fistfullofbeer said:
@DigiGoon
You are a lifesaver. That seems to have done the trick. Thanks a lot man!
Click to expand...
Click to collapse
Happy to help buddy.
DigiGoon said:
Follow these steps, and you'll get your stock ROM back.
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Flash all other extracted files similarly firing these commands.
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
Hope this helps you.
Click to expand...
Click to collapse
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
gabepaul said:
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
Click to expand...
Click to collapse
Yes it does replace, and you simply need to reflash TWRP again
gabepaul said:
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
Click to expand...
Click to collapse
It replaces the TWRP, and if you are flashing stock via 3 button method, then there is no way you can keep it, but if you are getting on stock by flashing individual files then just dont flash the recovery file and you will just have the TWRP alone.
gabepaul said:
Just wondering, does this replace the TWRP recovery with stock? And is there a way to keep TWRP if so?
Click to expand...
Click to collapse
Instead of flashing full update.app , i can help u just to stop doing a lot of work after flash
DigiGoon said:
It replaces the TWRP, and if you are flashing stock via 3 button method, then there is no way you can keep it, but if you are getting on stock by flashing individual files then just dont flash the recovery file and you will just have the TWRP alone.
Click to expand...
Click to collapse
So which is the three button method and which is the other?
gabepaul said:
So which is the three button method and which is the other?
Click to expand...
Click to collapse
Three button method is nothing but by placing update.app in /sdcard/dload/
And then put off the phone followed by pressing vol down+vol up+ power button . This will let it install full stock rom and phone looks brand new in terms of software
gabepaul said:
So which is the three button method and which is the other?
Click to expand...
Click to collapse
As @gopinaidu77 said about three button method, its just that. And about the other one, in that you have to extract all the important img files from UPDATE.APP and flash it via fastboot commands.
DigiGoon said:
As @gopinaidu77 said about three button method, its just that. And about the other one, in that you have to extract all the important img files from UPDATE.APP and flash it via fastboot commands.
Click to expand...
Click to collapse
so I've tried both, and I'm getting stuck on the "Honor for the brave, powered by Android" screen.
I should probably also add that im trying to downgrade from lineage 14.0 Nougat to the android 6.1 emui 3.1
gabepaul said:
so I've tried both, and I'm getting stuck on the "Honor for the brave, powered by Android" screen.
I should probably also add that im trying to downgrade from lineage 14.0 Nougat to the android 6.1 emui 3.1
Click to expand...
Click to collapse
Sorry. 6.0.1 is emui 4.0.1 . Well bro , u can still unbrick ur device . Can i know which build number u are on before u flashed lineageos ?
gopinaidu77 said:
Sorry. 6.0.1 is emui 4.0.1 . Well bro , u can still unbrick ur device . Can i know which build number u are on before u flashed lineageos ?
Click to expand...
Click to collapse
Oh yeah, I have restored it already. I made a nandroid backup, and so when it happened, I just rebooted into fastboot and reflashed TWRP, then restored my phone from the backup. Not sure which build. Wondering what went wrong? And how I can successfully convert to stock
gabepaul said:
Oh yeah, I have restored it already. I made a nandroid backup, and so when it happened, I just rebooted into fastboot and reflashed TWRP, then restored my phone from the backup. Not sure which build. Wondering what went wrong? And how I can successfully convert to stock
Click to expand...
Click to collapse
Extract UPDATE.APP via Huawei Update Extractor tool, pull out relevant img files (system.img, boot.img, recovery.img, recovery2.img(if not in your device), cust.img) flash this one by one via fastboot by booting your device in fastboot mode, fire the given below commands.
Code:
fastboot flash <img name w/o extension> <full path to the relevant img file>
After this try the three button method, if it doesn't work then boot into eRecovery then tap "Download Latest Firmware". It will connect to Wi-Fi and will start downloading the latest firmware of your device. After the process gets completed you'll be on stock ROM with your bootloader in "Locked" state.
You are guiding wrong bro . There is a need of extension too. Else it will give error saying file not found
CUST issue
Hi,
I tried to do the same, Boot.img, system.img and recovery.img are flashed successfully but I cannot flash CUST.img, following error occurs, please help.
it says: while writing 'cust'...,
error: FAILED (remote: command not allowed)
Please help, thanks in advance.

[Solved] Bootloop after Flashing Boot.img and System.img

Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Meranico said:
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Click to expand...
Click to collapse
If you can boot to "downloader" use rebranding SW, it will fix everything
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
Thank you so much! My mobile phone is working again! :victory:
Edit: Small problem persists: I cannot use the buttons left and right of the scanner. They do not react.
Edit2: Could fix this. I flashed B120 and the buttons worked again.
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
whats rebranding sw and hoe do i do it as i have the smae problem please help
corey568brown said:
whats rebranding sw and hoe do i do it as i have the smae problem please help
Click to expand...
Click to collapse
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Meranico said:
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Click to expand...
Click to collapse
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
corey568brown said:
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
Click to expand...
Click to collapse
Good to know!
As I had the same problem as you do know: I flashed B120, which does not seem to have the bug with the buttons and upgraded via Firmware Finder to B130 and then to B150.
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work

Am I bricked?

Hey Guys,
i spent the last 8 hours to get my z back to life but without luck.
i was on aokp (official) as i decided to go back to stock rom, after i have seen that my device wouldnt boot a normally after the first flash, i flashed lineage os and from there it always tells me that it needs a password to start android. but i never had a passwort so i tried the one from my google account but it doesnt worked.
and now im stuck on the warning screen from the unlocked bootloader i can still go in recovery / bootloader mode but it doesnt matter what i flash it wont work.
SO PLEEASE HELP ME... i can give a small donate via paypal if you can help me the right way!
Hi.
You still have access to TWRP? if yes go to Advanced > File Manager then navigate to this path: /data/system
Look for this files:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
Delete them all. if one or two of them is not exist that's Ok, skip them.
Now reboot the phone and see the password request form appears or not.
P.S. Don't panic you not bricked your phone.
Hello and thank you for your answer. But i do not have this files.
in data/system/ i have 3 ordners "dropbox-add" "heapdump" and "perfd".
nexxer92 said:
Hello and thank you for your answer. But i do not have this files.
in data/system/ i have 3 ordners "dropbox-add" "heapdump" and "perfd".
Click to expand...
Click to collapse
Then i suggest try a full wipe.
Dalvik
Catch
Data
System (By wiping this partition hole android OS will remove)
after that try to flash an custom ROM (Lingoes, RR, orginal images)
I hope this will solve the problem.
Soo, after a full night of flashing ( im seriously feeling like a pro hacker with all those command windows open ) i have managed to get back to stock reteu wit november security patch and relocked bootloader.
The only thing which bothers me at the moment is when i start the phone normally it takes me directly in the fastboot menu, but the screen for bootloader unlock is gone and it still says status: modified.
How is it possible that the phone boots normally? And can i do OTA Updates now with relocked Bootloader?
Thanks in advance!
nexxer92 said:
Soo, after a full night of flashing ( im seriously feeling like a pro hacker with all those command windows open ) i have managed to get back to stock reteu wit november security patch and relocked bootloader.
The only thing which bothers me at the moment is when i start the phone normally it takes me directly in the fastboot menu, but the screen for bootloader unlock is gone and it still says status: modified.
How is it possible that the phone boots normally? And can i do OTA Updates now with relocked Bootloader?
Thanks in advance!
Click to expand...
Click to collapse
How did you do that. I'm trying and trying to get back to stock EU firmware. No chance, I always get verification problem, need signed boot bla bla.
Btw. For normal boot try this
fastboot oem fb_mode_clear
knjigo said:
How did you do that. I'm trying and trying to get back to stock EU firmware. No chance, I always get verification problem, need signed boot bla bla.
Btw. For normal boot try this
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
hi
i flashed an RETBR Firmware.. bootet it, installed update.zip to 7.1.1 with adb sideload and then flashed again with fastboot oem lock begin.
nexxer92 said:
hi
i flashed an RETBR Firmware.. bootet it, installed update.zip to 7.1.1 with adb sideload and then flashed again with fastboot oem lock begin.
Click to expand...
Click to collapse
Great for you. Where did you get update to 7.1.1?
I get always error not signed boot.
If you could provide some step by step manual how to flash stock rom and relock bootloader it would be great.
I was also on reteu german firmware.

Soft bricked H930 - help!

My attempt to root my H930 went very wrong... So I started by unlocking the bootloader and flashing TWRP. After that I didn't manage to get in to TWRP. Instead it started to boot, but froze eventually. Now I can't get it to boot (It gets stuck on initial LG V30 screen), and I can't power it off. I can get into stock recovery (apparently it got far enough to replace TWRP) and download mode with hardware button combinations. But the download mode seems to be different from fastboot mode (looks different on phone, and fastboot can't find it) so I can't try to flash TWRP again. I also managed to get it into a check IMEI + S/N mode by holding all buttons at once...
I've tried flashing H93010f_00_OPEN_EU_OP_0925.kdz with LG UP/Uppercut (since I can get to download mode). It went fine but the situation is the same - no boot, no way to power off.
A factory reset from stock recovery doesn't help either.
Please advice..
Alright, I acually got in to fastboot mode even though I'm not quite sure how.. I basically first went in to download mode, and then pressed vol down + power to reboot, and ended up in fastboot mode. From there I flashed twrp again. And this time I managed to get in to TWRP. Since I didn't have a working ROM I went ahead and wiped all but external sdcard and tried flashing Boombox. It resulted in an "Error: 1"..
So I tried flashing H93010f_00_OPEN_EU_OP_0925.kdz from LGUP again, and now I'm back to a device that doesn't boot again.
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
jcsww said:
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
Click to expand...
Click to collapse
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
egendomligt said:
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
Click to expand...
Click to collapse
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
jcsww said:
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
Click to expand...
Click to collapse
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
egendomligt said:
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
Click to expand...
Click to collapse
Best of luck!
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
egendomligt said:
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
Click to expand...
Click to collapse
No clue!
Ok, I got it to boot again!
* I formatted data (not wiped) inTWRP - Not sure if this step was relevant
* Flashed stock recovery/boot/system from a KDZ dump called "LGH930GAT-00-V10c-222-01-OCT-12-2017+0" - found the link in some other thread here
* Rebooted and watched it boot - went in to "Android is upgrading..."-screen - rebooted - then booted normally.
Thanks for the help and a special thanks to @Perkash who helped me out through PM.

Question Anyone has stock recovery.img for nord 2 DN2101 for OS version DN2101_11_A.11?

I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
sako21 said:
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
Click to expand...
Click to collapse
Flash latest A13 update u will get stock recovery
pankspoo said:
Flash latest A13 update u will get stock recovery
Click to expand...
Click to collapse
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
sako21 said:
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
Click to expand...
Click to collapse
Just try keep unrooted boot. Img backup of your current rom.
Then go ahead though it's got currpted (one person faced that at insta but he used that commnads when he has twrp it must work with stock recovery) but after restoring boot imgae all was fine.
But try at u r own risk later don't tag [email protected] pankspoo - guide
Thanks. Will try that out.
And yes, wont tag you!
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
Wait u want to relock bootloader?
You need a otg adapter. Put Stock boot.img and the last ota update file to the usb storage.
flash stock boot.img via FKM
go to developer settings and lock oem
uninstall magisk with restore all (not image)
start phone in bootloader
fastboot flash relock
fastboot reboot recovery
select update from storage
use otg adapter with ota file
install
restart
done
For any assistance contact @sakarya1980
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
did you get the relock bootloader?
If you're still searching for the stock recovery, I've attached the .img file (unzip it first)

Categories

Resources