Related
I was working on an interesting app on my N7 (grouper). I left it on for about a week after the week I found the N7 stuck in a boot loop. I can get it into the boot loader and can do fastboot things but I can't flash a recovery or rom.
I get this error when I try.
sending 'recovery' (7766 KB)...
OKAY [ 1.013s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 4.848s
I was able to get to the recovery splash screen if I booted recovery (no flash) but thats it.
Trying to start from the bootloader gives me a "Booting failed" error.
My guess is I managed to cook the flash so no more writing or reading is possible. What say you fine fellows have I made it into masonry?
Can you boot into stock recovery.If yes try factory reset otherwise
Try the wugs toolkit
It has options to restore your phone
Hello to everyone,
I'm stuck in a very bad situation with my ZTE open (codename Inari).
I've flashed the phone for upgrading to 1.4 version software, but something goes wrong...
In startup the phone stuck with the splash boot image (the logo with the FirefoxOS text)
Now the phone boot only in a fastboot way (with ROAMER2 codename), and whathever firmware I try to flash into phone give this error:
with fastboot windows version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
with fastboot linux or mac version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
in each way the phone reboot.
I've tried also the NandDL_firefox.exe software, but It seems to be in trouble with the ARMPRG file (that I don't really what it is, and the software come in chinese language)
So, if I press the VolUp+power the phone does nothing (still with the logo described up),
the VolDown+Power the phone does nothing.
Only with the VolUp+VolDown and Power button the phone going into Download Mode (the pc recognized the phone as "ZTE WCDMA Handset Diagnostic Port"...
Maybe this can be the last salvation, this mode is recognized by QPST suite software, but I don't know from where I can start to use this software...
Someone can help me?
Or someone want a bricked phone to hard testing?
Thanks
scari said:
Hello to everyone,
I'm stuck in a very bad situation with my ZTE open (codename Inari).
I've flashed the phone for upgrading to 1.4 version software, but something goes wrong...
In startup the phone stuck with the splash boot image (the logo with the FirefoxOS text)
Now the phone boot only in a fastboot way (with ROAMER2 codename), and whathever firmware I try to flash into phone give this error:
with fastboot windows version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
with fastboot linux or mac version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
in each way the phone reboot.
I've tried also the NandDL_firefox.exe software, but It seems to be in trouble with the ARMPRG file (that I don't really what it is, and the software come in chinese language)
So, if I press the VolUp+power the phone does nothing (still with the logo described up),
the VolDown+Power the phone does nothing.
Only with the VolUp+VolDown and Power button the phone going into Download Mode (the pc recognized the phone as "ZTE WCDMA Handset Diagnostic Port"...
Maybe this can be the last salvation, this mode is recognized by QPST suite software, but I don't know from where I can start to use this software...
Someone can help me?
Or someone want a bricked phone to hard testing?
Thanks
Click to expand...
Click to collapse
have you tried flashing the original firmware from the zte website? and then start all over? From what I remember, you can put the firmware directly on the sd card and flash from the recovery menu.
foxob said:
have you tried flashing the original firmware from the zte website? and then start all over? From what I remember, you can put the firmware directly on the sd card and flash from the recovery menu.
Click to expand...
Click to collapse
There is a little little little problem.
The recovery menu doesn't exist anymore...
I've (maybe bad) flashed the recovery partition, so it's now inaccessible...
Pushing the VOLUP+Power button the devices doesn't start in recovery mode...
Only Download Mode is available, but I don't know what it is really
Thank you
scari said:
There is a little little little problem.
The recovery menu doesn't exist anymore...
I've (maybe bad) flashed the recovery partition, so it's now inaccessible...
Pushing the VOLUP+Power button the devices doesn't start in recovery mode...
Only Download Mode is available, but I don't know what it is really
Thank you
Click to expand...
Click to collapse
so this doesn't work? too bad. that has helped me save my zte open a few times.
foxob said:
so this doesn't work? too bad. that has helped me save my zte open a few times.
Click to expand...
Click to collapse
no, that method doesn't work definitely...
:crying:
are you able to get into fastboot?
hecatae said:
are you able to get into fastboot?
Click to expand...
Click to collapse
the phone stuck in fastboot mode when the power button is pressed.
The only other method to start up the phone is download mode (VolUP+VolDown and power button).
scari said:
the phone stuck in fastboot mode when the power button is pressed.
The only other method to start up the phone is download mode (VolUP+VolDown and power button).
Click to expand...
Click to collapse
cant you flash recovery using ADB ????? i think you might, just find a recovery that does work on your mobile and flash it using adb if it works you can install or flash atleast something to work with.
Arrowblue said:
cant you flash recovery using ADB ????? i think you might, just find a recovery that does work on your mobile and flash it using adb if it works you can install or flash atleast something to work with.
Click to expand...
Click to collapse
when I flash the phone with windows this is the result:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
and when I try to flash with ADB under Mac Os this is the result:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
and I try to flash the original boot image and the modified one,
but without success...
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Thanks
bijilidk said:
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Thanks
Click to expand...
Click to collapse
This happens when you flash wrong version. You must be using the twrp for KK, while MIUI is LP.
So try this one
https://userscloud.com/a25aszfwkn2z
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
bijilidk said:
Tried but not working same error is showing.
Once I did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
sasukay said:
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
Click to expand...
Click to collapse
No hope tried everything..same error.
bijilidk said:
No hope tried everything..same error.
Click to expand...
Click to collapse
Extract "boot.img" from the root of MIUI rom zip and flash that with "fastboot flash boot boot.img"
Then flash the twrp for lollipop
Otherwise, you'll need to flash the firmware through QFIL Downloader
bijilidk said:
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
It seems you successfully flashed the twrp recovery...............
If your recovery is right i.e.according to your previous os
Then just u need to enter into recovery by pressing 3 buttons at the same time....
if not worked then flash another twrp version....
-Sourav_8434
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
bijilidk said:
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
Click to expand...
Click to collapse
Please explain how you did it. I'm also stuck with blank screen and only vibration
neerut said:
Please explain how you did it. I'm also stuck with blank screen and only vibration
Click to expand...
Click to collapse
Refer this link. I used the ( THIRD METHOD )Installing the firmware using Lenovo Downloaders.
https://boycracked.com/2015/06/03/unbrick-lenovo-a6000/
So everything is solved here right ? you can close this thread now i think !
before it happen this z5 is bootloop so i have to reinstall the rom, but during the flasing on twrp it saay failed, and i decide to revert to stock ROM, but it fail too, gooling and try every method include for another phone type and got nothing, and when i connect my phone to PC it just detect my External memory SD card, i trying to wipe cahce/dalvik, installing twrp another version, flashing stcok ROM, in fastboot i try to flash the system and recovery, it say ...OK but it bootloop when i reboot... and i cant mount data,system,internal on twrp...
hope someone can help me to fix this issue
what Rom are you trying to install at the moment for exactly?
nheolinkin said:
what Rom are you trying to install at the moment for exactly?
Click to expand...
Click to collapse
at the moment no ROM installed cause when trying to install ROM i was wipe everything... i think the main problem is my internal storage, i cant found it.. and cant do anything cause no internal memory detected..
kuranzi said:
at the moment no ROM installed cause when trying to install ROM i was wipe everything... i think the main problem is my internal storage, i cant found it.. and cant do anything cause no internal memory detected..
Click to expand...
Click to collapse
TWRP can not detect internal storage right?
Then you still can sideload stock rom via ADB if you have pc with necessary driver.
i was about to make a thread for my problem but found this something similar instead:
well first. idk what the solution for OP is
my problem is that my recovery(twrp 3.0.2 m2) is unable to mount system cache data partitions so i cant wipe them or flash a rom
so to tackle this i went to fastboot erased the partitions and then tried to flash latest twrp m5 but the recovery did not change (still m2) then i tried various stock recoveries and twrp 2.7.8.0 but nothing is working(meaning that i have the same twrp 3.0.2 m2)
even flashing boot and system from fastboot is not helping
at the end i tried the unbricking method by swiczak and it locked my bootloader(a custom recovery can't work with locked bootloader)
Try flashing partition.tbl files from JB and LP raw fw
Try one by one, if one works then leave it as it is...
I recommend u to use the 2.3gb system partition tool by ryanjms07...
Once flashed, try to wipe everything from fastboot and then flash boot and recovery, n then try rom flashing...
nheolinkin said:
TWRP can not detect internal storage right?
Then you still can sideload stock rom via ADB if you have pc with necessary driver.
Click to expand...
Click to collapse
yeah i have all driver for adb, but i cant flash anything cause no internal storage detected, i have try downgrade the twrp version, and it say success on fastboot but when i enter recovery it not change, still m5..
TechNova said:
Try flashing partition.tbl files from JB and LP raw fw
Try one by one, if one works then leave it as it is...
I recommend u to use the 2.3gb system partition tool by ryanjms07...
Once flashed, try to wipe everything from fastboot and then flash boot and recovery, n then try rom flashing...
Click to expand...
Click to collapse
can u give the link pls sir
sry late reply, have to go to net cafe xD
kuranzi said:
can u give the link pls sir
sry late reply, have to go to net cafe xD
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/zen...uide-increase-size-partition-zenfone-t3443639
Assuming u have windows in ur pc, along with proper drivers installed,
Download ADB files as well as this file,and extract all in same folder, reboot ur fone to bootloader and run repartition.bat file,
After finishing flashing, wipe all the partitions via fastboot cmds(i hope u know this).
TechNova said:
Here: http://forum.xda-developers.com/zen...uide-increase-size-partition-zenfone-t3443639
Assuming u have windows in ur pc, along with proper drivers installed,
Download ADB files as well as this file,and extract all in same folder, reboot ur fone to bootloader and run repartition.bat file,
After finishing flashing, wipe all the partitions via fastboot cmds(i hope u know this).
Click to expand...
Click to collapse
thanks sir, ill try this method
Update @TechNova
got 1 error there,
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.704s]
finished. total time: 0.705s
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 1320777045 bytes
sending '/tmp/partition.tbl' (1 KB)...
OKAY [ 0.491s]
writing '/tmp/partition.tbl'...
OKAY [ 0.670s]
finished. total time: 1.163s
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: GPT command failed
)
finished. total time: 0.521s
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>fastboot erase cache
erasing 'cache'...
OKAY [ 1.586s]
finished. total time: 1.587s
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.651s]
finished. total time: 0.652s
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>pause
Press any key to continue . . .
after that i try to reflash the fastboo,boot,recovery, but didnt change still M5 when i enter recovery..
kuranzi said:
thanks sir, ill try this method
Update @TechNova
got 1 error there,
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.704s]
finished. total time: 0.705s
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 1320777045 bytes
sending '/tmp/partition.tbl' (1 KB)...
OKAY [ 0.491s]
writing '/tmp/partition.tbl'...
OKAY [ 0.670s]
finished. total time: 1.163s
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: GPT command failed
)
finished. total time: 0.521s
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>fastboot erase cache
erasing 'cache'...
OKAY [ 1.586s]
finished. total time: 1.587s
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.651s]
finished. total time: 0.652s
F:\Android\ADB Fastboot\Android+Debug+Bridge+v.+1.0.32\Android Debug Bridge v. 1.0.32>pause
Press any key to continue . . .
after that i try to reflash the fastboo,boot,recovery, but didnt change still M5 when i enter recovery..
Click to expand...
Click to collapse
That probably means that ur NAND chip is messed up. Only service center is the option left for u then.
You need a brand new emmc
TechNova said:
That probably means that ur NAND chip is messed up. Only service center is the option left for u then.
Click to expand...
Click to collapse
paktepu said:
You need a brand new emmc
Click to expand...
Click to collapse
ohh damn it, i was hope this is not hardware fail, ok then, thanks for helping everyone
Hi so I want to revert back to factory image, however I keep on getting "file not found" or "target didn't report max-download-size" error. I already installed the drivers, unlock the bootloader and when I check fastboot devices, the phone shows up.
Any help would be greatly appreciated.
Ive had similar performance within the bootloader menu. Some things to check on your pc verify that the phone is showing up in device manager as essential phone fastboot. You may need to restart the pc or change usb port to get it to properly communicate.
You should also be able to revert to the factory image through the normal recovery; instead of attempting to install twrp to flash the stock image (sounds like what you might be trying to do your post is a little unclear) you can always just run the normal essential recovery partition and then use adb sideload from there to restore the factory image.
From essential's website
https://www.essential.com/developer/beta-builds
Your device is now in Recovery mode. An Android logo with red exclamation mark should appear on screen.
Hold the Power button, then press the Volume-Up button one time. When the menu appears, select Apply update from ADB.
Run the following command: adb devices. Then check that your device shows up with “sideload” next to its name
Run the following command: adb sideload ota_file.zip where ota_file.zip is the name of the file you downloaded and verified
Once the update finishes, select Reboot system now to reboot your phone
I tried this and it seems to work great but if I select slot b it will not boot properly. Has anyone else tried this?
I don't believe that the Essential bath file flashes both slots. I had to use the BTS file to fix my phone.
Halp
Zargone said:
I tried this and it seems to work great but if I select slot b it will not boot properly. Has anyone else tried this?
I don't believe that the Essential bath file flashes both slots. I had to use the BTS file to fix my phone.
Click to expand...
Click to collapse
Did you manage to successfully flash the stock image? If yes, would you kindly provide the steps that you performed? Im trying to get back to Oreo from Android P Beta so that I can have my unit replaced
I just got one of these phones as payment for some consulting. I booted into fastboot mode and checked fastboot devices before agreeing on the deal and I see the device listed. I get home and start to unlock bootloader etc...only to continue getting this error...
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.005s
This was a simple process on my Huawei. WHats going on here does anyone know?
lolifer said:
I just got one of these phones as payment for some consulting. I booted into fastboot mode and checked fastboot devices before agreeing on the deal and I see the device listed. I get home and start to unlock bootloader etc...only to continue getting this error...
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.005s
This was a simple process on my Huawei. WHats going on here does anyone know?
Click to expand...
Click to collapse
Have you enabled oem unlock in developer options?
I cannot boot into android to check. I literally got this phone a couple hours ago. Is there anyway to enable it via fastboot?
The guy that I got it from told me it was stuck on boot logo. I simply hooked it up to laptop, installed adb/fastboot, and drivers and booted to fastboot and ran fastboot devices which gave me the serial #. So i figured I would be able to restore it no matter as long as fastboot could see the device.
lolifer said:
I cannot boot into android to check. I literally got this phone a couple hours ago. Is there anyway to enable it via fastboot?
The guy that I got it from told me it was stuck on boot logo. I simply hooked it up to laptop, installed adb/fastboot, and drivers and booted to fastboot and ran fastboot devices which gave me the serial #. So i figured I would be able to restore it no matter as long as fastboot could see the device.
Click to expand...
Click to collapse
There is no way to unlock bootloader if you can't enable oem unlock option in developer menu.
You can try to boot to recovery and do a factory reset,or try switching slots a/b and see if you can boot ur phone.
gm007 said:
There is no way to unlock bootloader if you can't enable oem unlock option in developer menu.
You can try to boot to recovery and do a factory reset,or try switching slots a/b and see if you can boot ur phone.
Click to expand...
Click to collapse
i already did those options. each time FB fails to write because of locked state. I cannot access recovery. I tried to> fastboot boot boot.img and this is what I get:
platform-tools_r28.0.1-windows\platform-tools>fastboot boot boot.img
Downloading 'boot.img' OKAY [ 0.935s]
booting FAILED (remote: 'unknown command')
Finished. Total time: 0.962s
EDIT**** Just specified a USB device using fastboot -s. Looks like the partitions were created but just couldnt wipe userdata. What is SuperBlocks backup?
C:\Users\Leebo\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot -s PM1LHMD762601033 -w
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: 672d99c8-c617-11e8-8c24-45c467b7c233
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
Finished. Total time: 1.068s
lolifer said:
i already did those options. each time FB fails to write because of locked state. I cannot access recovery. I tried to> fastboot boot boot.img and this is what I get:
platform-tools_r28.0.1-windows\platform-tools>fastboot boot boot.img
Downloading 'boot.img' OKAY [ 0.935s]
booting FAILED (remote: 'unknown command')
Finished. Total time: 0.962s
EDIT**** Just specified a USB device using fastboot -s. Looks like the partitions were created but just couldnt wipe userdata. What is SuperBlocks backup?
C:\Users\Leebo\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot -s PM1LHMD762601033 -w
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: 672d99c8-c617-11e8-8c24-45c467b7c233
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
Finished. Total time: 1.068s
Click to expand...
Click to collapse
You will need to side load the OTA.
You cannot flash.
tech_head said:
You will need to side load the OTA.
You cannot flash.
Click to expand...
Click to collapse
But I cannot get adb to work, only fastboot. I install essentials ADB, download Essential drivers. Am I missing something? In Device Manager while in fastboot it says Essential Fastboot Phone.
Im starting to think the original owner must have had twrp and installed OTA update without going back to stock recovery. If I were to assume this the case, what would be the next step to recover?
tech_head said:
You will need to side load the OTA.
You cannot flash.
Click to expand...
Click to collapse
How do I go about sideloading from fastboot?
Don't know. My phone is rooted and bl unlocked
lolifer said:
How do I go about sideloading from fastboot?
Click to expand...
Click to collapse
Pretty sure you cannot sideload with fastboot. Anything flashing related in the bootloader with fastboot requires an unlocked bootloader. If twrp was previously installed than he would unlocked the bootloader at some point. What happens when you boot to recovery from the bootloader? Or the hardware buttons?
galakanokis said:
Pretty sure you cannot sideload with fastboot. Anything flashing related in the bootloader with fastboot requires an unlocked bootloader. If twrp was previously installed than he would unlocked the bootloader at some point. What happens when you boot to recovery from the bootloader? Or the hardware buttons?
Click to expand...
Click to collapse
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
lolifer said:
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
Click to expand...
Click to collapse
Yeah, was just curious about what you were seeing in recovery. If your bootloader is locked and you have somehow lost recovery I am not to sure what else you can do. You said you switched slots and still were unable to boot to recovery?
lolifer said:
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
Click to expand...
Click to collapse
Ok...
Let's try this thing...
Grab the fastboot images from the Essential website...
Download and unzip it...
Try flashing boot to it's partition...
Theory- signed by the OEM?
Once you can get to recovery... You can use ADB
rignfool said:
Ok...
Let's try this thing...
Grab the fastboot images from the Essential website...
Download and unzip it...
Try flashing boot to it's partition...
Theory- signed by the OEM?
Once you can get to recovery... You can use ADB
Click to expand...
Click to collapse
...downloading images for PIE now.
EDIT**Here is the fastboot result..
C:\Users\Administrator\Downloads\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_b' (20769 KB)...
OKAY [ 0.830s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.845s
lolifer said:
...downloading images for PIE now.
EDIT**Here is the fastboot result..
C:\Users\Administrator\Downloads\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_b' (20769 KB)...
OKAY [ 0.830s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.845s
Click to expand...
Click to collapse
Damn...
I woulda thought for sure you could flash signed image...
just fired up miraclebox and did a read info under the qualcomm section and this was my result.
Starting..
Waiting for Phone...
Phone Found..
version:0.5
unlocked:no
off-mode-charge:1
charger-screen-enabled:1
battery-soc-ok:yes
battery-voltage:3721
version-baseband:2.0.c4-M1.2
version-bootloader:mata-4452425
variant:
partition-type:userdata:ext4
partition-size:userdata: 0x1987357000
partition-type:system_b:ext4
partition-size:system_b: 0x100000000
has-slot:nvdef:yes
has-slot:dsp:yes
has-slot:vendor:yes
has-slot:devcfg:yes
has-slot:cmnlib64:yes
has-slot:cmnlib:yes
has-slot:boot:yes
has-slot:keymaster:yes
has-slot:abl:yes
has-slot:mdtp:yes
has-slot:mdtpsecapp:yes
has-slot:bluetooth:yes
has-slot:modem:yes
has-slotmic:yes
has-slot:hyp:yes
has-slot:tz:yes
has-slot:rpm:yes
has-slot:xbl:yes
has-slot:system:yes
current-slot:_b
slot-retry-count:_b:0
slot-unbootable:_b:no
slot-successful:_b:no
slot-retry-count:_a:0
slot-unbootable:_a:yes
slot-successful:_a:no
slot-count:2
slot-suffixes:_a,_b,
secure:yes
serialnoM1LHMD762601033
product:Mata
max-download-size:0x20000000
kernel:uefi
all:
0.011s
>>Process Done...