Related
I'll give you a little pre-story.
Short version:
I have CWM recovery on android 4.12 but when I try to flash either PACman Rom or CM It gives me assert: failed getprop error. After removing the first line of the updater script in the zipfile I don't get the assert error, it just states
Finding update package...
Opening update package...
Installing update...
Installation Aborted.
Long version:
Initialy I was running Android 4.04 (ICS) with CWM recovery. I decided to flash the PACman rom(http://forum.xda-developers.com/showthread.php?t=2388267). I did the following.
1. Rebooted into CWM recovery.
2. Did a factory reset.
3 Wiped Dalvik cache.
4. Flashed ROM
5 Flashed Kernel
After completing these steps I rebooted my phone to find a "Security Error" message under the LG logo. It would automaticlly shutdown after 20 seconds. So what I initially tried was to flash the 10G KDZ which didn't work out because the LG tool is ****. However the 20B KDZ did work (which is Android 4.1.2). After the flashing had completed my phone booted normally. I was able to root my phone using this guide http://forum.xda-developers.com/showthread.php?t=2173465. I was also able to install CWM recovery. Now the following problem is this when I want to flash the PACman rom or the CM ROM I get the following error assert failed: getprop("ro.product.device") == p760 || getprop ("ro.build.product") == "p760" E:error in (path to zipfile) (status 7) Installation aborted. I got around that by removing the first line of the of the updater script. I don't get the error but it just states "Installation aborted".
Thanks in advance.
BausDroid said:
I'll give you a little pre-story.
Short version:
I have CWM recovery on android 4.12 but when I try to flash either PACman Rom or CM It gives me assert: failed getprop error. After removing the first line of the updater script in the zipfile I don't get the assert error, it just states
Finding update package...
Opening update package...
Installing update...
Installation Aborted.
Long version:
Initialy I was running Android 4.04 (ICS) with CWM recovery. I decided to flash the PACman rom(http://forum.xda-developers.com/showthread.php?t=2388267). I did the following.
1. Rebooted into CWM recovery.
2. Did a factory reset.
3 Wiped Dalvik cache.
4. Flashed ROM
5 Flashed Kernel
After completing these steps I rebooted my phone to find a "Security Error" message under the LG logo. It would automaticlly shutdown after 20 seconds. So what I initially tried was to flash the 10G KDZ which didn't work out because the LG tool is ****. However the 20B KDZ did work (which is Android 4.1.2). After the flashing had completed my phone booted normally. I was able to root my phone using this guide http://forum.xda-developers.com/showthread.php?t=2173465. I was also able to install CWM recovery. Now the following problem is this when I want to flash the PACman rom or the CM ROM I get the following error assert failed: getprop("ro.product.device") == p760 || getprop ("ro.build.product") == "p760" E:error in (path to zipfile) (status 7) Installation aborted. I got around that by removing the first line of the of the updater script. I don't get the error but it just states "Installation aborted".
Thanks in advance.
Click to expand...
Click to collapse
Is your phone booloader unlock? You must unlock your phone boot loader before flash any custom rom.
artit said:
Is your phone booloader unlock? You must unlock your phone boot loader before flash any custom rom.
Click to expand...
Click to collapse
Well I assume since I have CWM Recovery that my phone's bootloader is unlocked. Correct me if I'm wrong.
BausDroid said:
Well I assume since I have CWM Recovery that my phone's bootloader is unlocked. Correct me if I'm wrong.
Click to expand...
Click to collapse
No. Please look for how to unlock bootloader in L9 General & Q&A forum, and select thread that match your phone model.
artit said:
No. Please look for how to unlock bootloader in L9 General & Q&A forum, and select thread that match your phone model.
Click to expand...
Click to collapse
Turns out bootloader was locked. I have followed the guide and unlocked it but the same problem still occurs. [Did factory reset , cache wipe , dalvik cache wipe.
Thanks for your input
BausDroid said:
Turns out bootloader was locked. I have followed the guide and unlocked it but the same problem still occurs. [Did factory reset , cache wipe , dalvik cache wipe.
Thanks for your input
Click to expand...
Click to collapse
If your phone bootloader is unlocked and you also remove assert model check line from installer, you shouldn't get that error status 7.
Please try to make sure that your phone bootloader is unlocked by boot your phone in S/W update mode. The bootloader unlock text will print at the top of that screen.
artit said:
If your phone bootloader is unlocked and you also remove assert model check line from installer, you shouldn't get that error status 7.
Please try to make sure that your phone bootloader is unlocked by boot your phone in S/W update mode. The bootloader unlock text will print at the top of that screen.
Click to expand...
Click to collapse
I can confirm that it is unlocked. The text in the upperleft corner reads "Bootloader Status: Unlocked".
BausDroid said:
I can confirm that it is unlocked. The text in the upperleft corner reads "Bootloader Status: Unlocked".
Click to expand...
Click to collapse
If you still unable to flash any custom rom please try to flash stock kdz or use LG mobile support tool to recover your phone. Once my phone is in strange condition, I can flash custom rom but I cannot boot it (My bad, I use wrong update script when I test my rom). My phone always stuck at LG logo. Flash kdz, restore CWM and flash rom don't help. The last thing that make my phone boot up again is LG mobile support tool.
BTW if you phone model is not P760 you should restore your old baseband by flash you original kdz. (You flash P760 to unlock your boot loader right?)
artit said:
If you still unable to flash any custom rom please try to flash stock kdz or use LG mobile support tool to recover your phone. Once my phone is in strange condition, I can flash custom rom but I cannot boot it (My bad, I use wrong update script when I test my rom). My phone always stuck at LG logo. Flash kdz, restore CWM and flash rom don't help. The last thing that make my phone boot up again is LG mobile support tool.
BTW if you phone model is not P760 you should restore your old baseband by flash you original kdz. (You flash P760 to unlock your boot loader right?)
Click to expand...
Click to collapse
Well the problem is that I can't flash the stock 10G KDZ because the LG Mobile Support Tool only allows me to install 20B KDZ. Your question could be interpreted in two ways so I will give you two awnsers .
Q Why did I flash my p760?
A Because after flashing PACman rom on android 4.0.4 I got a security error
Q How did I unlock my bootloader?
A I first rooted the device. Installed CWM recovery, then did adb reboot oem-unlock
So the question is how do I flash 4.0.4 KDZ if the LG mobile support tool does not allow me?. Or how do I resolve the ROM installation issues?.
Thanks again
BausDroid said:
Well the problem is that I can't flash the stock 10G KDZ because the LG Mobile Support Tool only allows me to install 20B KDZ. Your question could be interpreted in two ways so I will give you two awnsers .
Q Why did I flash my p760?
A Because after flashing PACman rom on android 4.0.4 I got a security error
Q How did I unlock my bootloader?
A I first rooted the device. Installed CWM recovery, then did adb reboot oem-unlock
So the question is how do I flash 4.0.4 KDZ if the LG mobile support tool does not allow me?. Or how do I resolve the ROM installation issues?.
Thanks again
Click to expand...
Click to collapse
For flashing ICS
In JB rom offline flash program cannot detect your phone in S/W update mode. Most people stuck at about 15% and the program told them that their phone is not connect. If you want to flash 4.0.4 ICS kdz you should
- boot your phone up (if it can boot up),
- connect usb cable and put your phone in LG software mode.
- Do an offline flash again but select DIAG instead of EMERGENCY. You phone should reboot into S/W update mode automatically. After that it will get pass 15%.
But If you cannot boot your phone up, you need to flash you phone model ICS u-boot and x-loader via fastboot. After that offline flash program can detect your phone in S/W update mode.
For rom istallation, I'm sorry I don't understand why you cannot flash custom rom. Maybe your download is corrupt? Please check file md5 with rom uploader.
artit said:
For flashing ICS
In JB rom offline flash program cannot detect your phone in S/W update mode. Most people stuck at about 15% and the program told them that their phone is not connect. If you want to flash 4.0.4 ICS kdz you should
- boot your phone up (if it can boot up),
- connect usb cable and put your phone in LG software mode.
- Do an offline flash again but select DIAG instead of EMERGENCY. You phone should reboot into S/W update mode automatically. After that it will get pass 15%.
But If you cannot boot your phone up, you need to flash you phone model ICS u-boot and x-loader via fastboot. After that offline flash program can detect your phone in S/W update mode.
For rom istallation, I'm sorry I don't understand why you cannot flash custom rom. Maybe your download is corrupt? Please check file md5 with rom uploader.
Click to expand...
Click to collapse
I did the above but I get a page error(only with the 4.04 kdz). When my phone was bricked I had the same problem thats why I flashed 20B. Thanks for your time.
So, here is the problem i am facing with my moto E
I followed the tutorials from this site and had flashed my MOTO E to stock ROM 3-4 times due to different reasons, i was successfully able to do that using the STOCK ROM that i had for android kitkat 4.4.4. Last month i updated my moto E to android lollipop. After that it kept asking me to install a 12MB update which i tried installing quite some times but was not able to install. It showed some error while installing the same. So, i started ignoring that. A couple of days ago i once again tried to install that update and after installing the update when the phone turned on, it logged on into FASTBOOT MENU saying:
hab check failed for boot
failed to validate boot image
Fastboot reason: Fall-through from normal boot mode
So, i thought Flashing it once again might solve the issue. When i tried flashing it, on the command screen it gives ERROR for 4 files i.e. boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2 saying::
<bootloader> invalid signed image
<bootloader> preflash validation failed
And on my phone screen it says "Invalid PIV signed image"
For all other instructions it says OKAY
Now it is again and again turning ON into this fastboot mode only...
Since i already had flashed my moto using the same custom rom , i think the files must be okay...
PLEASE HELP :'(
Why did you flashed 4.4.4 and then ota updated to 5.1 ? This process should've bricked your device in the first place.
Anyway 5.1 stock image files are available, did you tried flashing them? (fastboot mode)
-z3r0- said:
Why did you flashed 4.4.4 and then ota updated to 5.1 ? This process should've bricked your device in the first place.
Anyway 5.1 stock image files are available, did you tried flashing them? (fastboot mode)
Click to expand...
Click to collapse
sorry, i didn't knew that i shouldn't update my phone after installing the stock rom. No i haven't tried flashing my phone with android 5.1 stock file, i thought maybe flashing my phone with android 4.4.4 will downgrade my phone back to kitkat. Will try it now...will be helpful to me if you could get me a link for android 5.1 stock file as well, i tried finding the same, but it says for moto e2 which comes originally with lollipop but mine comes with android 4.4, its so confusing for me which stock file to download....
thanks for the help
Here : http://forum.xda-developers.com/showthread.php?t=2755857
"RetailDSDS" - Is for Indian version
-z3r0- said:
Here : http://forum.xda-developers.com/showthread.php?t=2755857
"RetailDSDS" - Is for Indian version
Click to expand...
Click to collapse
tried it, still giving the same error, preflash validation error :'(
Hi,
I believe my nexus 5x is "soft bricked" or in a "boot loop" (sorry newb here). The phone will restart and turn off during the boot animation. I am able to get into recovery mode and have attempted to use adb sideload to apply the latest 7.1.1 OTA zip from google's website. During that process (50% through) it said I could not update it because I needed to load a current or newer version. I realized I am on beta 7.1.1 NPF26F but am unable to locate the OTA zip for this.. I did download one online (seemed legit) but got an error E: signature verification failed, E: error 21. At this point I am a bit lost and unsure what to do.. any help would be appreciated.
Mike
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
es0tericcha0s said:
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
Click to expand...
Click to collapse
I do not believe my bootloader is unlocked. I tried to go through the " fastboot oem unlock " steps today but I need to turn on USB debugging on the device (which I cannot do) to even have that option. Will I need to wait until the OTA.zip is released or is there another way ?
http://storage.googleapis.com/andro.../preview/bullhead-npf26f-factory-0e9ab286.zip
is this the factory image or the OTA?.. guessing by the size its the factory image. I am unaware how to flash this if my USB debugging is LOCKED. Please help
This guide is outdated now. Please refer to the thread OPs of the respective projects.
Hi all, I am starting this thread with the very reason to educate and help newbies as well serve as a resource guide that could be used by all. I will try my best to update this thread often. You can ask any question regarding Moto Z2 Play aka albus here. Our XDA Community will try to help you. Make sure you always read before posting the same queries. If you're stuck in a problem, make sure you provide us with as much as information of what you were exactly doing and what happened along with your device details ofcourse.
Also remember that unlocking the bootloader will void your warranty. Relocking it won't give you back your warranty. If you are visiting a service center for repairs of any kind, they will come to know that you have unlocked your bootloader (you put a code on their site lol). But yea you can try your luck by visiting them after you lock your bootloader using the fastboot firmware.
No one, but you are responsible for whatever you do to your device. If something happens due to your ignorance or lack of backups or knowledge, only you are responsible, not the developer, not the XDA Community. Just read the respective posts, search (at XDA and at Google) before posting and you might probably find answers. Cheers.
Setting up adb/fastboot on your system:
These drivers are quite essential for every android user.
How to use?
Windows:
Minimal Fastboot/ADB: https://www.androidfilehost.com/?fid=745425885120698566
Just install the setup. Reboot your phone in bootloader mode (Power off and then press and hold power + vol down simultaneously) and connect via USB cable. On your computer, navigate to the directory where you installed them. Press shift+right click and choose Open Command Window / Powershell here. Type:
Code:
fastboot devices
If you get a serial number, fastboot is working.
For adb to work enable Developer Options and turn on USB Debugging on your device. Open Settings app on your device and go to About Phone section. Next, tap 7 times on Build Number and get the Developer Options enabled.
Now authorize USB Debugging by allowing it (Choose something like Always trust)
Type this on your command window / powershell window:
Code:
adb devices
Again it should return a serial number.
If both these fail, you might consider rebooting your computer or even installing (MDM) motorola device manager. Make sure you don't have any crappy or outdated drivers. (Always keep your system upto date ) Anything else, you'll have to google up things.
Motorola Device Manager:
For more info regarding adb/fastboot open this: https://developer.android.com/studio/command-line/adb.html
Linux users might need to install it from their respective package manager repos, Ubuntu for example:
Code:
sudo apt install android-tools-adb && sudo apt install android-tools-fastboot
Arch Linux on the other hand:
Code:
yaourt -S android-tools --noconfirm
Similarly for the other distros.
Commands are the same. fastboot needs to be used with sudo.
Unlocking the bootloader:
Unlocking Bootloader
>>> Unlocking Bootloader will overwrite any data stored on your device, backup your files before proceeding <<<
Unlocking Bootloader:
1- Register
Head to Motorola website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and register your E-Mail ID.
Open Settings app on your device and go to About Phone section. Next, tap 7 times on Build Number and get the Developer Options enabled.
Head back to Main Settings Menu and go to Developer Options and switch the 'Allow OEM Unlock' option.
2- Getting Unique ID for each device
Reboot to Bootloader/fastboot mode (power off the device, then press the power and volume down buttons simultaneously).
On your computer, go to the directory where you installed the adb/fastboot drivers (or make sure this folder is in your $PATH to acess fastboot and adb system wide).
Open CMD/Powershell/bash in here. (Windows users might need to Shift+Right Click and choose "Open Command/Powershell Window here" , Linux users can open terminal as per their respective distro. Now , type
Code:
Code:
fastboot oem get_unlock_data
You will get something like this:
On a Windows Desktop, the returned string format would be:
Code:
(bootloader) 0240540162024205#4C4D3556313230
(bootloader) 30373as313630330df332323239#BD00
(bootloader) 8A672BA4746C2CE0a328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
On a Mac OS Desktop, the returned string format would be
Code:
Code:
INFO0A40040192024205#4C4D3556313230
INFO30373731363031303332323239#BD00
INFO8A672BA4746C2CE02328A2AC0C39F95
INFO1A3E5#1F53280002000000000000000
INFO0000000
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
Code:
0240540162024205#4C4D355631323030373as313630330df332323239#BD008A672BA4746C2CE0a328A2AC0C39F951A3E5#1F532800020000000000000000000000
3- Unlocking the device:
Check if your device can be unlocked by pasting this string in the specific field on the Motorola website, and clicking “Can my device be unlocked?”
NOTE: If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of that page. Click on it and wait for the unique code to be sent to your mail.
After you got the code type the following :
Code:
fastboot oem unlock your_code
and wait your device to reboot !
Flashing TWRP Recovery:
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to format data once via twrp wipe options and reboot back to twrp for functioning of /data
Downloads : http://www.androiddevs.net/downloads/
Keep the twrp recovery file (.img extension) in the adb/fastboot folder
Reboot to bootloader, open cmd/bash and type:
Code:
fastboot flash recovery filename.img
(if you want permanent flash) or
Code:
fastboot boot filename.img
(if you want temporary
boot)
Now you must flash the verity disabler zip.
HIGHLY RECOMMENDED:
After the twrp is done and you have successfully rebooted to system, it is a good time to reboot to TWRP again and backup your phone. (System and Boot most necessary)
Flashing Stock ROM:
Will be updated as soon as the fastboot version of the stock ROM is available.
Unbricking your hard bricked/dead device:
Connect your device via the usb cable, extract this zip file to the adb/fastboot folder and then run:
blankflash.bat file if on windows; the .sh file if on linux.
Once this is completed, you must flash the full stock firmware via fastboot. This is MANDATORY.
Blankflash zip: http://cloud.vache-android.com/Moto/albus/blankflash/blankflash.zip
Reserved
please forgive the ignorance, but is this device fully unlockable in the same fashion that Nexus devices are, similar method if i'm reading this correctly? Im very used to unlockable bootloaders on VZW
OneArm said:
please forgive the ignorance, but is this device fully unlockable in the same fashion that Nexus devices are, similar method if i'm reading this correctly? Im very used to unlockable bootloaders on VZW
Click to expand...
Click to collapse
Yeah, I am not sure what is going on this time around with the VZW variant. Since the Droid Z was bootloader locked and the unlocked Z wasn't (but not VZW compatible) I am almost expecting the same here, but I keep being told that the unlocked version of the Z2 will work on Verizon so maybe they just don't care anymore. I mean, the unlocked Nexus 6 and VZW Nexus 6 were pretty much the same phone too, and both were bootloader unlockable.
The only thing that gives me pause from going out now and getting the VZW version vs the unlocked model (whenever its slated to come out) is that Motorola's Bootloader Unlock page doesn't have it listed (yet). Either it can be and they are behind on updating the list, or it can't... at which point the unlocked one will be listed with a (Except VZW Model) like the other phones have. But... if either version works on VZW... what's the point of making one unlockable and the other not? Seems like a waste of time.... of course VZW's past decisions on phones don't make sense in some aspects.
All I know is... I want one of these if they are unlocked. Once the keyboard mod is released I will be back to the nerdy bliss that is a sliding keyboard and making this phone the spiritual successor to the Droid 4.
After flash twrp when rebooting the mobile system, stopped in screen of bootloader unlocked .... how to proceed help me: /
---------- Post added at 06:05 PM ---------- Previous post was at 05:46 PM ----------
After installing TWRP it asked for the encryption password so I put it and it opened normal I went to restart> system, then appeared option to install the application twrp, I slipped it to be installed, then went on reboot> system and stopped on the screen Of bootloader unlocked .. help me: |
m.lucas said:
After flash twrp when rebooting the mobile system, stopped in screen of bootloader unlocked .... how to proceed help me: /
Click to expand...
Click to collapse
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
yunzo said:
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
Click to expand...
Click to collapse
how should I proceed? My device has no ROM only TWRP installed. :s
m.lucas said:
how should I proceed? My device has no ROM only TWRP installed. :s
Click to expand...
Click to collapse
Start TWRP, and you can transfer zip file from PC by using "adb push"
"adb sideload" may work too.
yunzo said:
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
Click to expand...
Click to collapse
Don't use SuperSU.
Use Magisk-v13.0(54e6a79)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Junior Passos said:
Don't use SuperSU.
Use Magisk-v13.0(54e6a79)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
Click to collapse
Thank you for information.
I have just tried Magisk, but failed with error message as below.
Code:
mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v13.0(54e6a79).zip'
It is same for latest version (c4377ed).
yunzo said:
Thank you for information.
I have just tried Magisk, but failed with error message as below.
Code:
mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v13.0(54e6a79).zip'
It is same for latest version (c4377ed).
Click to expand...
Click to collapse
Latest version don't work.
I use Magisk-v13.0(54e6a79) on my Moto Z2 Play.
Z2 Play stock ROM needed.
Anyone help to search complete stock Noughat Rom, for the Z2 Play (Indian retail unit model no XT 1710-10), I did not find yet. Please help will be highly appreciated.
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
tywinlannister7 said:
Reserved
Click to expand...
Click to collapse
Z2 Play stock ROM needed.
Anyone help to search complete stock Noughat Rom, for the Z2 Play (Indian retail unit model no XT 1710-10), I did not find yet. Please help will be highly appreciated.
@niteshpant kindly edit your post and remove the reserved post from the quote.
Moreover, the links will be added here as soon as the firmware is available.
Junior Passos said:
Latest version don't work.
I use Magisk-v13.0(54e6a79) on my Moto Z2 Play.
Click to expand...
Click to collapse
As I wrote before, I have failed both of 54e6a79 and latest.
Error message on TWRP is same.
Have you met this message but rooted successfully after boot?
Today I tried system-mode SuperSU, and met boot failure which continues to show Motorola/lenovo logo.
It is different from dm-Verity failure (which shows unlock warning).
Stuck in TWRP, Help
I have successfully flashed the TWRP but now it is looping at TWRP and when try to do factory reset, in just seconds it is boot again and shows TWRP main screen again, moreover storage shows about 50000 mb in internal memory, secondly my memory card is not accessible, selection is not working only shows internal memory. As I think at this stage my bootloader(stock) is fine, original stock recovery is replaced by the TWRP 3110 . My factory Android rom is still there in my phone because twrp inernal memory option shows about 50000 mb space captured in internal storage. I have clear delvik and cache but all fails, how I can get the OS by the TWRP. I assume if my old OS has been erased then twrp should have give the "no OS install" massage but this is not happening in my case. Any help...... I am not doing something more due to complete device failure in this stage mainthing is this no factory rom image is available yet, very annoying issue.... regards
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
hey did you get it fixed and can you please send the link to the stock rom
yayjk said:
hey did you get it fixed and can you please send the link to the stock rom
Click to expand...
Click to collapse
TRY ASKING THE QUESTION ON THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
---------- Post added at 05:00 PM ---------- Previous post was at 05:00 PM ----------
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
TRY ASKING IN THIS THREAD
https://forum.xda-developers.com/android/help/how-to-make-simple-android-apps-qna-t3776780
How to Unbrick Lenovo K8 Plus 4GB
Hi All
I tried many stock roms and many versions of SP flash tool but none helped me to unbrick my lenovo k8 plus (4gb ram).
I was trying to downgrade it to Naugat from Oreo but it shows same error every time.
Error is (SP Flash tool version latest 5.18)
" Error_Status_Sec_Insufficient_Buffer( 0xC002004B)
[Hint]:
Verified boot is enabled.
Please download signed image (md1img-verified.img) or disable verified boot."
Plzzz help same problem
Enabled verified boot ...how to disabled
Same problem my lenovo k8plus
Enabled verified boot ...how to disabled
You need to use "Lenovo Moto Smart Assistant" instead of SPFlash tool to flash and you will be good to go. You can get the tool from the Lenovo official website.
JDsingh007 said:
hi
so i have a Lenovo K8 plus 3 GB ram variant. Let me explain what happened first.
I unlocked my device's bootloader to flash the patched boot image for magisk root, then this orange state sign started showing up eerytime i booted up. then when the latest update rolled out in march, i decided to relock the bootloader and then update my device. did it and then a red state sign showing up accompanied by bootloop (it said something like rollback kernel too). so I formatted the whole thing via sp flash tool and downloaded the stock rom.
now when i try to flash it, preloader flashes FINE, recovery flashes FINE, but when it comes to md1img it shows this error: STATUS_INSUFFICIENT_BUFFER (0xC0010007). I tried flashing all the files individually to find the cause of the problem and see exactly which particular flash file was causing the problem. results are as follows.
[STATUS_INSUFFICIENT_BUFFER (0xC0010007) ]- this error was displayed while flashing these files - md1img, md1dsp, md1arm7, md3img.
[ STATUS_SEC_IMG_TOO_LARGE (0xC0020005)] - only popped up while flashing the oem image.
when I exclude these files from the queue, the rest files flash fine.
In short, I have a bricked phone which i am unable to flash via sp flash tool.
Thanks in advance
Click to expand...
Click to collapse
Try with Lenovo Moto Smart Assistant. I too have bricked my phone... but I've successfully started my phone using this tool. you will get official signed ROM from here.
you can use LMSA tool to rescue,90% sucessfully ,don't use splashtool beacause it's many error if you choose wrong version
Had the same problem. Can confirm Lenovo's tool sucessfully recovers ohone from bricked state. A lifesaver!
Downloaded from https://lenovomobilesupport.lenovo.com/br/pt/downloads/ds101291-rescue-and-smart-assistant-lmsa
then updated to version 5.9.2.4 from inside the app itself