Lenovo appear to have made downgrading from Nougat to Marshmallow difficult. The commands to flash certain images such as the bootloader and modem from fastboot have been disabled when the bootloader is unlocked, and relocking the bootloader seems to be impossible with the standard oem lock command. I had no knowledge that I would lose a certain degree of control over my P2 before I unlocked the bootloader, so I am rather disillusioned about it all at the moment.
When I first unlocked I was running the stock 3 UK Marshmallow firmware. I installed TWRP (modified) and somehow I soft-bricked my phone because one of the ROMs I tried flashing got stuck at the Kernel writing part and restoring TWRP stock backup froze when writing the boot partition so I was unable to get anything but a blue notification LED when resetting. I also attempted to restore stock backup with non-modified TWRP and that didn't help either. I wiped data each time I tried to do something, and also changed file system from F2FS to EXT4 and back again several times. Never in my 6 years of flashing ROMs had I encountered such issues.
Nothing was working, so all I could think to do was use fastboot commands to restore each stock image. Luckily this worked without a hitch because I hadn't upgraded to Nougat yet, but I still didn't know about the potential issues with downgrading, so when I flashed the ROW stock ROM, I upgraded it to Nougat in the OTA menu. Then I stumbled upon all the problems people have been having when they attempt to use fastboot to restore stock MM (the only ROM with fastboot parts for the P2?) the main one being that their signal stops working (modem partition corruption / incompatibility?) and even when upgrading again to Nougat, their signal is still gone. There is an ADB shell command that may or may not fix this.
Now I'm on stock ROW Nougat and stock recovery because I'm worried that I might inadvertently mess something up again and my only hope would be to fastboot flash back to stock and risk losing my signal. There doesn't appear to be a "safety line" when upgrading to Nougat for me atm because of the restrictions Lenovo seem to have put on fastboot commands.
Related
I really screwed her this time! Tried to fix myself for the past 2 days but now I have to ask for help.
-can access bootloader and twrp
-can use fastboot but not adb
-not nougat related
So I factory reset in twrp, all was fine. Went back and restored a backup and now it's bootlooping. I was on the version of twrp previous to the one that has the efs bug (3.0.2-0). I still tried the terminal commands in the 6p thread but it did nothing. I have since fastboot flashed the newest twrp.
I tried to fastboot flash the newest marshmallow factory imgs, the last mm update before nougat. That made the phone bootloop on the circles instead of freezing on the Google logo. The bootloader did update but not sure what else went on. Tried to restore the backup without any efs anywhere in a 50 foot radius, nothing new.
As I factory reset before the failed restore I must not have debugging on for adb.
I have an OTG cable if that's useful.
I've been rooted for years but haven't ever done anything this bad haha! Fingers crossed.....
I'm going to call Google today and get a new phone thru warranty.
Hi,
I'm struggling with battery drain on Oreo but it's not the case right now.
The problem is that I've successfully unlocked the bootloader and rooted my HTC 10 then flashed latest LeeDrOiD but the drain is still present. So I decided to try downgrade my phone to Nougat...
First of all, my device is S-ON, CID HTC__034.
I was following tutorials from this forum but I wasn't able to flash Nougat RUU (because of not using htc_fastboot, which I discovered later) even after flashing hosd. After reboot, my LeeDrOiD started (just like after factory reset) and everything was OK. Then, I tried with Marshmallow RUU (got same result) and with htc_fastboot (different error, still no downgrade, boot to LeeDrOiD). Suprisingly I was asked to enter PIN to decrypt my phone. I couldn't do that, because it shouldn't be set. After some attempts I've formatted my HTC and then flashed LeeDrOiD.
After all this operation my home button stopped working... That was the moment I decided to restore my stock Oreo backup.
Although my home button is still not working I thought that maybe I'll try to downgrade from stock but I'm not able to get into rebootRUU.
I've run out of ideas.
I can access download, bootloader and recovery mode but after typing fastboot oem rebootRUU my phone boots to system.
Is there anything I can do to bring at least my home button working?
Thanks in advance.
Regarding to title, I was trying to flash a custom rom on my Honor 7X but apparently with the crazy amount of idk twrp recoveries and failed flashes, the phone (totally empty with both system and data) decides to factory reset lowlevel after i try to fastboot oem relock bootloader and it stays stuck at 99%. Any troubleshooting tips would be great.
Well, am experiencing similar problems.
I was on rooted Stock, when I got a System update available prompt.
I uninstalled Magisk, Flashed stock recovery and did a Factory reset from the Stock recovery.
It booted up, but there was no Keyboard installed. I think, I had uninstalled the pre-installed one when I was rooted.
I couldn't get past the Setup Wizard, as the FRP was Locked and there was no way of typing the password.
I tried to flash the system.img from fastboot but it gave me 'Remote: command not allowed' error. (Even for flashing recovery)
I google'd a bit and ended up on a solution as to relock the bootloader, Turn on OEM Unlocking and lock the bootloader again.
I relocked the bootloader, it did a 'Low-level factory reset' and now the phone is even bootloop. (it boots into eRecovery from the Honor/Huawei logo)
I tried the 'Download latest version and recovery' from eRecovery. It's giving me 'Package verification failed' error.
'dload' method never worked for me, and it is still the same.
Any solution/suggestion?
Bootloader relock with empty system is a definite hard brick.
I think you may need to ues dload method and flash a service rom to get back up and running.
dload says software install failed, any ideas? @mrmazak
apparently now its back to usual after leaving it stuck at 99% overnight until the battery dies out, could go back to fastboot and stuff
How far did it get? Stop and fail at 5% happens when update not found or not correct update.app.
Of it loads higher that 5% then fails , that's probably not gonna be able to fix it.
We have only found 2 service roms. Both are bnd-l21c432 one is Nougat one is Oreo. Both have been used on other versions of honor 7x. But after it runs you need to run hurupdater or hwota with correct model / region fullOTA.
I recently found a moto g5 in one of my fellow "old tech" drawers and decided to turn it on, it was on the
1. May 2018
Security patch on nougat, I decided to use the inbuilt system updater to go to Oreo, and now....it crashes during flashing process after about 25-30% completion,
Now im guessing boot or System is not properly installed due to the zip file having aborted mid-flash
Recovery doesn't properly boot as that is used to install the update and thus imidiately goes to doing that
Also, it hang up during installation on random times, it basically has a record of 2mins of not crashing whilst still being stuck on 30%
I got it to "boot" when trying factory mode, yeah it crashed mid boot animation...not a help
Any suggestions? EDL mode maybe?
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
TheFixItMan said:
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
Click to expand...
Click to collapse
SOMEHOW it just decided to boot, I have never seen such behaviour, even on my g5s which I had for a while, (and am currently daily driving to school if it wasn't closed....NEVER
Maybe I'll unlock it and try somehow recreating it? Well it's in physically rough shape but all components inside are fine...so that can't be the reason....?
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
anonymous724 said:
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
Click to expand...
Click to collapse
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
riyan65 said:
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
Click to expand...
Click to collapse
no luck on this front, gets to the passcode screen, write in passcode then motorola logo shows and screen keeps on turning off and on.
Thanks for the effort though, much appreciated
Mine is similar to yours. Initially was on permanent loop of the following:
1. Boot to moto g splash screen... Repeat
2. Boot to lock screen then usually a few loops of 1. (after entering the patter or left Idle)
The phone initially didnt have any developer options enabled.
I wiped cache using recovery mode. Restarted and pretty much the same thing except that it would on rare occasions actually fully boot up usually only last a few minutes before cycling between steps 1 and 2 above.
I used those rare boot ups to backup all files and enable any USB debugging /oem unlock (incase I need to use a solution dependent on these being enabled.)
Factory resetted it and its still the same with the random successful boot amongst the numerous failed ones.
I managed to hook it up to Lenovo's Lmsa and flash the latest ROM. Now I get a lot more successful boots but still loops every so often. The downside is that I can no longer do any functions that make use of the audio/ mic/ video (can take pictures). If I do then it will crash and loop.
The hardware test on the LMSA passed for every component before flashing to the latest version. Post update it predictably fails on the audio/ mic components.
I guess I'll have to go back to the old version to see I get the audio back.
Not sure what is going on or if anyone else has this problem, but since I got the Moto G power I've had a problem booting into the system after flashing stock ROMs in fastboot. Everytime I try my device doesn't go past the blue Moto logo. I'm no stranger to rooting/flashing ROMs/or anything like that. I probably flash more than necessary always switching up my phones. Ive flashed fastboot ROMs for years with no problems. I've got used to just using LMSA and it never failed to fix my issue. Now, LMSA won't recognize my device in terms of matching firmware and I can't use it without validation. I can flash everything fine and start to boot but nothing after that. I've tried formatting, factory reset in both stock and twrp to no avail. Even restored my Omni backup countless times in twrp which usually did its job no problem. Tried flashing vbmeta etc.. am I just experiencing tunnel vision and missing something obvious or what? Any help would be appreciated I'm not the same without my phones working device is US retail unlocked 2041-4 Sofia on what I assume is the latest firmware. (lolli Moto)
You've been trying to boot it with the stock kernel and not a magisk patched one after restoring however? / Have you tried booting without a magisk patch kernel (stock) and userdata formatted?
I had the same problem updating the firmware and i had to first boot it with the non rooted kernel and userdata formatted to first boot.