tl;dr Android OS is missing from my Nexus 6 for an unknown reason, fastboot isn't working (nor is flashing via recovery), /system and /firmware partitions read 0 MB in each. Help!
Context
My Nexus 6 is a replacement I got in the beginning of February after some speaker issues with my original N6. The device was unlocked, encrypted, used TWRP as custom recovery, and rooted (with Chainfire's SuperSU). I was running stock 5.1 (shamu-lmy47d). My root apps were few: AdAway, TitaniumBackup, SuperSU, Solid Explorer, and Cerberus (no account activity with Cerberus in the past two weeks). I'm familiar with fastboot, custom recoveries, flashing, etc. I've been doing this on my Droid X, Nexus 4, Nexus 7, and Nexus 6 for years and never had anything like this happen (nor have I really run into issues I couldn't figure out).
Situation
While using Sync for Reddit, some apps started crashing. Then Sync stopped loading anything. Then seemingly every app on my device reported a crash. Thinking a reboot would fix whatever was going on, I rebooted my phone. The boot animation didn't end after ten minutes, so I shut my phone back off and got into recovery.
I tried rebooting to system from TWRP. The first thing I noticed was that TWRP did not prompt me for a PIN. When I tried rebooting to system, I was greeted with the following message: "No OS installed! Are you sure you wish to reboot?". Confused, I went to the backup page to check partition sizes. TWRP showed "System (0MB)", "Data (56975MB)" (that's 57GB--I probably had 20GB maximum).
TWRP logs read as follows:
Code:
Data successfully decrypted, new block device '/dev/block/dm-0'
Updating partition details...
[COLOR="Red"]E:Unable to mount '/system'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage[/COLOR]
Successfully decrypted with default password.
Updating partition details...
[COLOR="Red"]E:Unable to mount '/system'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.[/COLOR]
Full SELinux support is present.
[COLOR="red"]E:TWFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to open '/cache/recovery/.version'.
E:Unable to mount '/data'[/COLOR]
MTP Enabled
A factory reset from TWRP returns the following:
Code:
Factory Reset Complete
[COLOR="red"]Failed[/COLOR]
and in the log:
Code:
[COLOR="red"]E:Unable to mount '/data'
E: Unknown MTP message type: 1[/COLOR]
Formatting Cache using make_ext4fs function.
[COLOR="red"]E:Unable to mount '/cache'[/COLOR]
Updating partition details...
[COLOR="red"]E:unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage.[/COLOR]
I will now post the results of several fastboot commands. Some analysis will follow at the end of this post, but I don't really have a clue as to what is going on.
Code:
$ fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (522112 KB)...
OKAY [ 17.483s]
writing 'system'...
OKAY [ 8.162s]
sending sparse 'system' (510197 KB)...
OKAY [ 17.036s]
writing 'system'...
OKAY [ 7.362s]
sending sparse 'system' (515601 KB)...
OKAY [ 17.891s]
writing 'system'...
OKAY [ 8.047s]
sending sparse 'system' (188485 KB)...
OKAY [ 6.661s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 94.184s
Code:
$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 6.105s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.676s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 13.678s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: moto-apq8084-71.08
Baseband Version.....: D4.0-9625-02.95
Serial Number........: ZX1G322CNQ
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (7681 KB)...
OKAY [ 0.243s]
writing 'boot'...
(bootloader) Failed to flash partition boot
(bootloader) Failed to flash partition boot
FAILED (remote failure)
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
Code:
$ fastboot -w
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.758s
Code:
$ fastboot format system
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.002s
I'll try any suggested commands as nothing appears to be working anyways. At this point, I don't care about my data. It's encrypted anyways, so it's probably unrecoverable regardless of if I get my phone working again.
I think the partition table somehow got destroyed or the flash memory failed. What's curious is that /data, /boot, /recovery, /EFS are still intact while /firmware and /system are not. I blame hardware because the issues started while the OS was booted (what on the OS level has permissions to write to /system and /firmware?) and nothing writes to the partitions anymore (they can't even be mounted!).
I'm looking for help in any way, especially the in the following:
(1): Finding the cause of this issue and squashing it if it's a bug in Android, TWRP, or some other software.
(2): Getting my phone back to a working state. Again, I don't care about the data on the device.
(3): (if 2 fails) getting my phone locked and removing TWRP so that I can RMA it--Google has already offered a replacement, but I don't want to send it in unlocked and with TWRP (may cause them to charge me for the replacement)
If this is indeed a software-caused error (again, I don't think my actions of using Sync for Reddit caused this issue), I'm terrified that this may affect others who are less capable of seeking help, or those who have critical data on their devices.
Thanks for reading. Please offer any guidance you may have.
-Ethan
kudos to you for providing so much detail for your problem. It's a rare sight here. It really helps people who are trying to help you.
I have a feeling your device is completely fried as even fastboot isn't working. I remember I had a similar problem with the OS disappearing but I solved it with a fastboot flash. If that doesn't work for you, I'm not sure what can. But then again, I'm not a seasoned tinkerer when it comes to android partitions. Let's wait for someone with more knowledge to share their opinion.
@rootSU do you have any ideas here? Can he mount in TWRP and possibly push the files needed or is TWRP too broken at this point?
Thank you for providing such details with the errors. I wish everyone was so thorough.
Thanks for the replies so far @exb0 and @Evolution_Freak!
For the record, "fastboot devices" and "adb devices" do work. It just appears that any thing operating on the file system does not work. Strangely, I was able to "adb push" a ZIP over and tried to flash it from recovery (flashing failed, of course). I was also able to move the ZIP around using TWRP.
I wonder if it would be feasible to move files into place manually and get a working system again by doing that. I don't want to do that unless it appears to be my only option and there's a good chance of it actually working.
I don't frequent XDA, so help getting knowledgeable community members would be greatly appreciated.
Even if you got it working, if it went *this* bad, you don't want the risk of futures failure. Flash as much stock as you can after formatting each partition using fastboot and return it.
rootSU said:
Even if you got it working, if it went *this* bad, you don't want the risk of futures failure. Flash as much stock as you can after formatting each partition using fastboot and return it.
Click to expand...
Click to collapse
Good point. I think my plan is to get it back to a locked state without TWRP. But how to get there, I have no idea. As you can see in the logs, I can't flash anything with fastboot :\ How can I format the partitions? I might be able to do that.
ethanmad said:
Good point. I think my plan is to get it back to a locked state without TWRP. But how to get there, I have no idea. As you can see in the logs, I can't flash anything with fastboot :\ How can I format the partitions? I might be able to do that.
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
You can try and also:
fastboot format system
fastboot format userdata
fastboot format cache
See if you can then flash system.img, userdata.img and cache.img separately.
Also, which version of adb/fastboot are you using? if you are using the one from the Android SDK i would recommend running the sdk update manager and making sure the SDK platform tools are the latest version
@rootSU I believe the OP already tried "fastboot format system" and got the error "Formatting is not supported for filesystem with type 'raw'."
Didgeridoohan said:
@rootSU I believe the OP already tried "fastboot format system" and got the error "Formatting is not supported for filesystem with type 'raw'."
Click to expand...
Click to collapse
Yes, it says in his post
I will add this, do NOT attempt to OEM lock again. I'm glad it had failed when you tried. Otherwise, we would already be done here.
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
---------- Post added at 07:25 AM ---------- Previous post was at 06:50 AM ----------
Did some searching and found this:
https://help.ubuntu.com/community/DataRecovery
However, being that you've already tried writing to the damaged partitions, it might not be of any help.
---------- Post added at 07:45 AM ---------- Previous post was at 07:25 AM ----------
Not even sure that those tools would apply here but this seems to be a very rare or random error you've encountered.
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
SFVDan said:
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
Click to expand...
Click to collapse
I had initially thought of this but his phone is still recognized by a PC as it normally should be and not as qhusb bulk. But if this could be a possible solution to his partition problem, then thank you for pointing him in that direction. :good:
IINexusII said:
Also, which version of adb/fastboot are you using? if you are using the one from the Android SDK i would recommend running the sdk update manager and making sure the SDK platform tools are the latest version
Click to expand...
Click to collapse
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
Evolution_Freak said:
I will add this, do NOT attempt to OEM lock again. I'm glad it had failed when you tried. Otherwise, we would already be done here.
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
---------- Post added at 07:25 AM ---------- Previous post was at 06:50 AM ----------
Did some searching and found this:
https://help.ubuntu.com/community/DataRecovery
However, being that you've already tried writing to the damaged partitions, it might not be of any help.
---------- Post added at 07:45 AM ---------- Previous post was at 07:25 AM ----------
Not even sure that those tools would apply here but this seems to be a very rare or random error you've encountered.
Click to expand...
Click to collapse
What's wrong with running oem lock? What damage would it do?
I'll try using that link when I get home.
And the error is very strange, yes.
SFVDan said:
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
Click to expand...
Click to collapse
Thanks, that looks like it might help. I'll try when I get home. To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
@opssemnik is this is a similar issue to what your post is about? I'm not quite sure what qhusb_bulk means, but my phone is recognized as "Nexus 6" in the file explorer and fastboot/adb devices show the device.
ethanmad said:
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
What's wrong with running oem lock? What damage would it do?
I'll try using that link when I get home.
And the error is very strange, yes.
Thanks, that looks like it might help. I'll try when I get home. To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
@opssemnik is this is a similar issue to what your post is about? I'm not quite sure what qhusb_bulk means, but my phone is recognized as "Nexus 6" in the file explorer and fastboot/adb devices show the device.
Click to expand...
Click to collapse
Had your OEM lock succeeded, with no OS installed, you could have inadvertently bricked yourself. It's in your best interest to leave it unlocked until you're sure you can boot into Android and ensure that the "allow OEM unlock" stays ticked after a reboot. If you'd like more information on that, click the top link in my signature.
First things first though, let's get you up and running.
ethanmad said:
To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
Click to expand...
Click to collapse
That you knew enough to do so IS indicative -- at least from my perspective. Well done! Keep us all posted.
ethanmad said:
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
Click to expand...
Click to collapse
Just as an FYI, the most current version of ADB is 1.0.32. The Ubuntu repositories do not contain the up to date version.
Louie998 said:
Just as an FYI, the most current version of ADB is 1.0.32. The Ubuntu repositories do not contain the up to date version.
Click to expand...
Click to collapse
Correct. I had to download and install the full SDK to get the latest version. Couldn't flash the OTA with the version that was available from Ubuntu repositories.
If this just happened out of the blue, your internal storage probably has (hardware) issues, flash back stock boot and recovery and return it. Unless you have some data you really want to recover, what's the point of trying to fix it? You can never trust this device again.
Chainfire said:
If this just happened out of the blue, your internal storage probably has (hardware) issues, flash back stock boot and recovery and return it. Unless you have some data you really want to recover, what's the point of trying to fix it? You can never trust this device again.
Click to expand...
Click to collapse
That's part of the problem, he can't get anything to flash. Everything attempted errors out.
Related
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
Ye, great chance that the emmc is damaged. But it still looks to me as if it is software damaged, not hardware, because of the successful flash of recovery. And it is on the same memory module.
Just as in the other post of this phone can u try this and give me the output of especially the flash of gpt.bin (partition table file). I never got an exact answer to it, for my liking, maybe i read over it.
If that doesn't flash (give me the output then i know for sure ), try flashing the boot.img and see what happens. I assume nothing will change from flashing the boot.img, but u gotta try something.
Next we can do is have a look at that intel flashing file, it looks promising. I never had to go to this part so i am out of general ideas (think outside the box maybe?). Maybe we can fiddle something from here. It looks to me like it can flash more than fastboot can, u just need the right files and some we can make, hopefully if i read the sources available to us right.
Hazou
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash gpt gpt_s
igned
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'gpt' (32 KB)...
OKAY [ 0.358s]
writing 'gpt'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 1.094s]
finished. total time: 1.460s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash motoboot
motoboot
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'motoboot' (23273 KB)...
OKAY [ 2.635s]
writing 'motoboot'...
(bootloader) flashing image dnx...
(bootloader) flashing image ifwi...
(bootloader) flashing image bos...
(bootloader) flashing image logo...
(bootloader) flashing image ulogo...
OKAY [ 2.338s]
finished. total time: 4.981s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash boot boot
_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.243s]
writing 'boot'...
OKAY [ 1.549s]
finished. total time: 2.799s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash recovery
recovery_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'recovery' (11264 KB)...
OKAY [ 1.338s]
writing 'recovery'...
OKAY [ 1.563s]
finished. total time: 2.907s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash motobp mo
tobp
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'motobp' (17091 KB)...
OKAY [ 1.714s]
writing 'motobp'...
OKAY [ 76.674s]
finished. total time: 78.396s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash system sy
stem_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.377s]
writing 'system'...
OKAY [ 2.576s]
sending 'system' (102400 KB)...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
OKAY [ 11.154s]
writing 'system'...
FAILED (remote failure)
finished. total time: 25.509s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash cdrom cdr
om_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'cdrom' (53258 KB)...
OKAY [ 4.891s]
writing 'cdrom'...
FAILED (remote: Preflash validation failed)
finished. total time: 6.273s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot erase cache
erasing 'cache'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase cache fail
FAILED (remote failure)
finished. total time: 1.897s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot erase userdata
erasing 'userdata'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
FAILED (remote failure)
finished. total time: 8.110s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>
So it looks like only few partitions are broken but how to repair it without unlocking bootloader??
Hmm, it does flash a part of the system if I read it correct. After the first one it gives errors to all partitions after it.
Can u reboot to recovery now, we finally flashed it right. Didn't work last time.
The things I wanted to do with the Intel thingy, are already done with flashing motoboot. So the things I had there are done.
Verstuurd van mijn GT-P5110
Nope, still red logo on recovery. The same was flashed by RSD and same errors appeared as on fastboot. Only different is after flashing RSD I can turn normal powerup and phone restarts to red logo from AP Fastboot but after flashing fastboot commands an error appeared.
Chamelleon said:
Nope, still red logo on recovery. The same was flashed by RSD and same errors appeared as on fastboot. Only different is after flashing RSD I can turn normal powerup and phone restarts to red logo from AP Fastboot but after flashing fastboot commands an error appeared.
Click to expand...
Click to collapse
Yep, this happens because it has nothing to start.
There is just 1 more think I can think off, because all others are closed (locked) or don't work. Or if unlocked we still don't have access.
Does the command "fastboot oem format" does something?
Verstuurd van mijn GT-P5110
Completely forgot about this command, I'll try it after work.
FAILED (remote: Restricted OEM command)
Then its over I think. We can't flash a custom recovery and fiddle around with it. Because maybe by not asking for system/data partition at start etc u can reformat the emmc with parted or other application.
Sorry, only Motorola can fix it. Or u need to replace the motherboard maybe? But that's something else.
Oh, try 1 more thing. Is it possible to load a custom boot image by the command "fastboot boot (image)"? Don't think so, but who knows. So u won't flash it.
Verstuurd van mijn XT890
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.412s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.614s
Bootloader blocks it??
Chamelleon said:
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.412s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.614s
Bootloader blocks it??
Click to expand...
Click to collapse
Yup, the defy could do it if i remember correctly. Hoped that this one would either. I am out of ideas now, but will have one more look. Don't expect anything, because we already tried most if not all the things we can do.
Edit:
All other things i can think of need to have adb access, and that can only be done by having an unlocked bootloader or root access. Because with root access u can flash a recovery even when u have a locked bootloader most of the time. But we don't have access to the system as well as the partitions, so we are stuck.
That Intel thingy can only flash the bootloader and the bootloader wont repartition the emmc. But we can try anyway if u want. Its a little bit different then the unbrick methode, just a little.
Verstuurd van mijn XT890
Today I flashed Samsung C3595 with partition table from S5610 and it's working well so "different" methods are not scary for me.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
Hi Chameleon.. i'm having a phone with similar issues (I created a post about it). I have tried steps one and two to no success. To unlock it do you do it via the official way (I ask because I don't know much, maybe there are other ways of doing it)
Yup, only official way.
Wysłane z Motorola RAZR i
here is the thing i talked about. Its just one more command with the unbrick method. But if u never try, u never know.
I assume u have all the files for the unbrick method still installed and on your PC. So u have the xFSTK driver and xfstk-dldr-solo.exe on your drive and working.
In the unbrick folder where the dnx and ifwi files are add the latest files from your latest firmware (dnx, ifwi and motoboot!).
Download the unbrick3.txt and rename to unbrick3.bat inside the folder with the original unbrick.bat
Now open a cmd shell inside the folder where the batch file is located. And then run unbrick3.bat.
After this try rsd lite again with the latest firmware u used.
Most likely it will not work... but ye, u gotta try.
I got this from an acer/asus device. It is the official unbrick methode from that device.
hey guys, i ve got the same problem. the phone stucks on the red M logo. i'm not familiar "aka" noob with this things. I wonder if anyone can give me a help?
I tried to wipe data and participation. the phone completes this commands but again stucks on the red logo.
hjahmetoglu said:
hey guys, i ve got the same problem. the phone stucks on the red M logo. i'm not familiar "aka" noob with this things. I wonder if anyone can give me a help?
I tried to wipe data and participation. the phone completes this commands but again stucks on the red logo.
Click to expand...
Click to collapse
Luckily, u don't have the same problem. U only have to search for a rsd lite flash guide. Flash your latest firmware that is available for your phone and country/brand. And all will most likely be good.
Hazou said:
here is the thing i talked about. Its just one more command with the unbrick method. But if u never try, u never know.
I assume u have all the files for the unbrick method still installed and on your PC. So u have the xFSTK driver and xfstk-dldr-solo.exe on your drive and working.
In the unbrick folder where the dnx and ifwi files are add the latest files from your latest firmware (dnx, ifwi and motoboot!).
Download the unbrick3.txt and rename to unbrick3.bat inside the folder with the original unbrick.bat
Now open a cmd shell inside the folder where the batch file is located. And then run unbrick3.bat.
After this try rsd lite again with the latest firmware u used.
Most likely it will not work... but ye, u gotta try.
I got this from an acer/asus device. It is the official unbrick methode from that device.
Click to expand...
Click to collapse
Yesterday I tried it and unfortunately nothing changed, still can't erase or write to those partitions.
XT890 Stuck on Red Logo. Probably damaged partitions
I woke up this morning to find that my Motorola XT890 is not working. I followed all the procedures for hard rest got the same result as listed below.
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
Contacted Motorola customer service, followed all the procedures as prescribed by Motorola customer service still stuck at Red Logo. Motorola has requested that I send it in for repair. The phone is 11 months old and under warranty. The unfortunate thing is that this is the second time I am sending the phone to Motorola for repair.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
I tried to update my moto XT1097 AT&T locked version and it did not complete the update successfully. It goes until flashing the boot.img, failed and don't go any further. I supposed it is because it is a locked phone. After this, the phone went to a fastboot mod loop. Even If I tried to sideload the orignial rom or use the fsaboot comandts to restore the original rom it remains in this mode.
It generates a first error when I tried to issue the command "fastboot flash partition gpt.bin" returning this:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.013s
And the phone display shows "hab check failed for primary_gpt"
I am issuing this command from the folder where the files of the original rom are located.
I tried to use a different gpt.bin file, from other ROMs and the same thing happen. I also tried another Lollipop ROM and not luck at all.
What I understand is that the gpt is the partion table that indicates where begins and where finish the diferent partitions into the phone, so I guess the problem could be resolve if I can change the gpt file into the phone for the original one.
I have tried to follow with the rest of the instalation but the motoboot and the boot files also are rejected and the system files are denied due an authentication problem.
The roms I have tried are:
ATT_XT1097_4.4.4_KXE21.187-38_cid1_CFC.xml
TMO_21.21.42.victara_tmo.tmo.en.US
4.4.4_to_5.0-11OTA
And the first one I used, which reach the same stage every time is:
RETBR_XT1097_5.0_LXE22.46-17_cid12_CFC.xml
I really appreciate any help and ideas you can give me to get my phne back to kitkat. I am not an expert but I am willing to do and learn what it takes
Did you solve this? How?
I am into this problem too. Any news?
After not messing with my wife's M7 for quite some time, I am back for another go at it. She managed to mess up her LG G3, so recovering the M7 is now back on the table. My goal has been to try to recover the data on the phone, so I have not tried a factory reset. Deleting the cache partition in the recovery menu also proved futile.
I have HBOOT 1.57, and a looked bootloader. I have ADB and Fastboot on my PC, and can get the phone into FASTBOOT USB, but my attempts to copy over TWRP 2.7.0.1 haven't worked.
What I got was this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1514139648 bytes
sending 'recovery' (7918 KB)...
OKAY [ 1.132s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.780s
Can it be done with a bricked phone and a locked bootloader, or am I just wildly grasping at false hope?
groovyz1k said:
After not messing with my wife's M7 for quite some time, I am back for another go at it. She managed to mess up her LG G3, so recovering the M7 is now back on the table. My goal has been to try to recover the data on the phone, so I have not tried a factory reset. Deleting the cache partition in the recovery menu also proved futile.
I have HBOOT 1.57, and a looked bootloader. I have ADB and Fastboot on my PC, and can get the phone into FASTBOOT USB, but my attempts to copy over TWRP 2.7.0.1 haven't worked.
What I got was this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1514139648 bytes
sending 'recovery' (7918 KB)...
OKAY [ 1.132s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.780s
Can it be done with a bricked phone and a locked bootloader, or am I just wildly grasping at false hope?
Click to expand...
Click to collapse
I hate to be the one, but you are wildly grasping for a false hope. You need unlocked bootloader in order to flash custom recovery
That is actually a pretty big relief at this point. I was more mad that I was doing something wrong than I was about recovering the phone. Thanks! I should have asked the question hours earlier so I didn't waste all that time. I picked up some new understanding though, so all was not lost.
Factory Reset seems to have failed!
Mine shows:
-- Wiping data...
Formatting /data...
Backup Data Preload
Backup CW Package
Restore Data Preload
Restore CW Package
Formatting /cache
Data Wipe Complete.
Write host_mode:0 done
Then it gives me the same system recovery menu. Rebooting just put it right back into the same loop.
Lineage 17.1 for the Sony Xperia 10 II
Please note this is currently for the dual-sim model ONLY. When you need a single-sim variant leave a comment, so we can work an that...
Code:
/*
* Disclaimer - your warranty may be void.
*
* I'm not responsible for bricked devices, dead OTGs or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Features
OTA updates - always delayed for 1 day (to prevent broken rollouts); when you want it immediately, checkout my GitLab pipelines
Increased volume steps to 25
Over-provisioned system image (580MiB), to allow install of OpenGApps and other stuff
Open Source (it is based on SODP, you can view all my patches and ci scripts here or here)
Package signature spoofing (needed by MicroG)
What does not work?
Stock camera app with wide and zoom cameras, you may use Open Camera to circumvent that.
Notification LED blinking - kernel driver bug (see here)
LiveDisplay
You tell me...
Download
There you have multiple options:
To get the complete package (both including the ota and imgparts; only needed for the initial setup) visit...
AndroidFileHost
GitLab (make sure to download the artifacts from the master branch)
To get ONLY the OTA package to update your system later on, visit (or open up the LineageOS Updater) ota.simonmicro.de - please note that only the last recent 14 days are accessible there.
Changelog
2021-02-28
Fixed wifi hotspot.
2020-12-18
Fixed cameras.
2020-11-27
Fixed ADB security.
2020-11-25
Added SELinux support.
2020-11-20
Added OpenGApps support.
2020-11-17
Initial release.
How to install your system
The following guide assumes, you have setup adb and fastboot already (make sure to always use the latest version of the toolkit, otherwise you'll may get problems during flashing) - for that take a look into the internet. Also you should already downloaded the complete package from above!
Unlock the bootloader - a "how to" is here...
Download the oem binaries from here, make sure to use exactly that version!
Boot into the bootloader (hold "Volume up + Insert the USB cable" until led lights blue) and then update the oem partition:
Code:
fastboot flash oem_a [EXTRACTED_OEM_IMAGE_FILE]
fastboot flash oem_b [EXTRACTED_OEM_IMAGE_FILE]
Flash now the Lineage recovery partition as well as the dtbo partition (they are inside the img folder of the complete package):
Code:
fastboot flash recovery [EXTRACTED_RECOVERY_IMAGE_FILE]
fastboot flash dtbo [EXTRACTED_DTBO_IMAGE_FILE]
Disable the verity checks for now, as your new recovery violates the Sony verity profiles of the Stock ROM:
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
Okay, you are now ready to boot the first time into the Lineage recovery, unplug the phone NOW!
To boot into recovery: Hold "Volume down + Power" until it vibrates...
You should now be booted into the recovery. We now clean any old data from Sonys Stock ROM - this is just to make sure you have a really clean install: Choose the "Factory reset" option.
The phone is now clean and ready to accept the new system. You now can either install just the OTA package and be done or flash every .img from the full package manually - the coice is yours. When you plan to flash the images manually, make sure to include boot, system, product, vendor, vbmeta_system, as these are normally part of the OTA update (I extracted the payload.bin to verify this!). For the latter approach you may orient yourself on my flashall.sh. I'll choose the simpler OTA-sideload approach for now.
Select "Apply update -> Apply from ADB" (now make sure the adb server runs as root - may use adb kill-server && sudo adb start-server to fix that) and execute (the OTA zip is inside the ota subdir):
Code:
adb sideload [OTA_SYSTEM_UPDATE_ZIP_FILENAME]
Something went wrong - help!
(Step 7-8) When you now see a device corrupt error
Don't panic!
You messed up the verity disable step from before - try again.
Try to switch the current boot slot (get current fastboot getvar current-slot and set new fastboot --set-active=, you can choose between a and b) and retry disableing verity disable again!
When your device fails to boot too many times (and crashes) the current slot could also get marked as corrupt. To reset that counter you'll need to reflash the boot partition - to see what is going on, try fastboot getvar all and look out for something like a unbootable flag.
(Step 9) When you get Operation not permitted during flashing
This is commonly caused by relocking and then reunlocking the bootloader (yay - buggy firmware). You'll need to relock, restore (and boot) the device with Flashtool using Sonys original ROM and start from fresh.
(Step 10) When you get the kDownloadPayloadPubKeyVerificationError error
Well, that's caused by using an other recovery than the provided one, as I use my own private keys to sign the build the recovery must also know them. Using an other recovery than the one from
the img folder of the complete package will most likely not include them (and when they do - I am in big trouble), and therefore fail. But you are in luck: It seems that the recovery writes
the data to the currently inactive slot and then fails. You could simply switch the system slot like described above!
Want to install Magisk?
Install the Magisk zip like the OTA system update by using adb sideload [MAGISK_FILE_NAME].
Want to install OpenGApps?
Make sure to use the pico-variant, as the system partition is even with over-provisioning really small (as the installer extracts some more stuff on the first boot) - then install the OpenGApps zip like the OTA system update by using adb sideload [OPENGAPPS_FILE_NAME].
Credits
As much I would like, I can't do everything by myself. A huge thank you to...
@MartinX3 for the used local_manifests and his device tree from his LineageOS organization
...the team behind @sonyxperiadev, for their great work (and their kernel sources)!
XDA:DevDB Information
LineageOS 17.1 for pdx201, ROM for the Sony Xperia 10 II
Contributors
Simonmicro, MartinX3
Source Code: https://gitlab.simonmicro.de/android/lineage/lineage-pdx201
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Sony OEM Package
Based On: AOSP
Version Information
Status: Beta
Hey,
as you guys may have already noted, I have stopped the active development phase for this LOS port a while ago. This was caused by me just not having enough time to do everything and additionally maintain a LOS port.
Today I'll upload the last maintenance build to the OTA server and mirrors. Of course I somehow included a little bug, which causes the system to complain about "an internal problem", which seem to be caused by some interaction with the OpenGApps package installer. Now, it is a feature. I'll may post one more update, if I figure this one out.
Nevertheless, I'll shut down the OTA service at 2022-06-01 (see https://status.simonmicro.de) and will then archive all project data. It was a great time to learn many (new/nasty) things about Android and how everything works. I have to say "thank you" to everyone, who supported me and was on board with this project.
See you next time,
simonmicro
-> https://forum.xda-developers.com/t/...r-xperia-10-ii-ota-sodp.4191601/post-86352693 <-
Reserved
First
At last The guide, source code looks great! Will install, check it next
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
bamdadkhan said:
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
Click to expand...
Click to collapse
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Simonmicro said:
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Click to expand...
Click to collapse
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
bamdadkhan said:
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
Click to expand...
Click to collapse
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Simonmicro said:
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Click to expand...
Click to collapse
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Thapsus-cz said:
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Click to expand...
Click to collapse
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Click to expand...
Click to collapse
See full log for flashing images:
sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
[sudo] пароль для :
Sending 'boot_b' (65536 KB) OKAY [ 2.441s]
Writing 'boot_b' OKAY [ 0.358s]
Finished. Total time: 2.812s
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'product' (432072 KB) OKAY [ 16.440s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vendor' (48084 KB) OKAY [ 1.725s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.005s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.016s
❯ sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
❯ sudo fastboot flash boot boot.img
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash product product.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash super_empty super_empty.img
sudo fastboot flash system system.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash vbmeta_system vbmeta_system.img
sudo fastboot flash vendor vendor.img
Sending 'boot_b' (65536 KB) OKAY [ 2.438s]
Writing 'boot_b' OKAY [ 0.378s]
Finished. Total time: 2.831s
Sending 'dtbo' (8192 KB) OKAY [ 0.302s]
Writing 'dtbo' OKAY [ 0.046s]
Finished. Total time: 0.357s
Sending 'product' (432072 KB) OKAY [ 16.212s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.699s]
Writing 'recovery' OKAY [ 0.557s]
Finished. Total time: 4.265s
Sending 'super_empty' (4 KB) OKAY [ 0.011s]
Writing 'super_empty' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.755s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'vendor' (48084 KB) OKAY [ 1.770s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Click to expand...
Click to collapse
xdauserart said:
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
See full log for flashing images:
Click to expand...
Click to collapse
I had the same problem yesterday with the same results. I struggled with it until morning. Eventually I downloaded the latest version of adb, flashed the stock rom again and started over. It was done in twenty minutes. Try the latest version of adb (I guess version 35 for Windows)
xdauserart said:
Done till the step 9.
Click to expand...
Click to collapse
...
Code:
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
This indicates you tried to use the bootloader (which also has fastboot support) to flash the images. I made sure to write the guide the way that it states you should use the fastbootd service of the recovery. I have the dumb feeling that many more will go your way and fail. Damn it.
Code:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Is fine, as you just erased all data - this also kills the partion so it cant be mounted anymore (that's the errors). This is indeed intentional as the system is now forced to really start fresh!
xdauserart said:
Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds"
Click to expand...
Click to collapse
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Two PR to fix back triple cam. But front cam is still broken.
https://github.com/sonyxperiadev/device-sony-seine/pull/29
https://github.com/sonyxperiadev/device-sony-pdx201/pull/15
--------------EDIT-----------------
Switch to CAF powerhal, better performance we have.
https://github.com/sjllls/device-sony-common/commit/de3b2bbbc33130891263d9e81ea2178a0f6783c4
https://github.com/sjllls/device-sony-sepolicy/commit/72059258eb0ff2c854996a05a5a23a8b73b55459
--------------EDIT-----------------
Renmember to let users flash with latest platform-tools, or they could not boot because of logical partition is not resized.
https://developer.android.com/studio/releases/platform-tools
Simonmicro said:
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Click to expand...
Click to collapse
I can confirm that Opengapps pico can now be installed without a bootloop. I'm at work and I don't have adb. I installed them directly as an update from the sd card using recovery. Everything works fine.
Can we get OpenGapps Nano support?
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
KriiXOne said:
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
Click to expand...
Click to collapse
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Simonmicro said:
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Click to expand...
Click to collapse
I'll try tomorrow after the math test that i'm studying for today, and will let ya know ^^'
Simonmicro said:
...
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Click to expand...
Click to collapse
Fixed it Just repeated the steps from the first one and used OTA on step 9. Thanks!
I have a Moto G6 Forge Cricket that I forgot the password to. I have been trying to boot into another image without data loss in order to go in and delete the password config files, but have not been able to get anything to work. USB debugging doesn't seem to be on, the bootloader is locked, and I have no idea if it's possible. I can access fastboot and android recovery. Fastboot says the product variant is "jeter XT1922-9", leading me to believe that it's just a reskinned moto g6 Play.
I have tried recovery loading update aroma file manager from SD card, which failed signature check. Updating over adb doesn't work, as the phone doesn't show up in adb at all, only fastboot.
I tried flashing TWRP recovery for the moto g6, and got the following output on PC:
C:\Android\SDK\platform-tools>fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17626 KB) OKAY [ 0.559s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
On the phone, I see a series of yellow cmd log lines leading up to "cmd: flash:recovery" followed by pink "Mismatched partition size (recovery)" Some posts said that this was an ignorable error and to just proceed into recovery, but when I did it just went to the normal android recovery.
I also tried just using fastboot boot, but that obviously didn't work due to the locked bootloader.
C:\Android\SDK\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (17626 KB) OKAY [ 0.563s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
I'm out of ideas and out of google search results that aren't SEO spam to read. If anyone knows something else I could try I would be happy to hear it. Thank you so much!
The only thing I can think of is using the factory recovery to erase the user partition / factory reset.