Related
A friend of mine as the same phone as me, the Huawei Ascend P6, and when she said hers was broken I said I would take a look. I have played around with flashing Android Roms etcetera, but I am totally stuck with this problem.
The problem is as follows: when booting the phone it shows the Huawei Ascend logo (as it should) for a couple of seconds, but then instead of the Huawei animation it shows the name "android" and gets stuck there (see attachment).
After some researching I put the UPDATE.APP file from the Huawei website in the dload folder on the root of the SD-card and tried rebooting. I tried a several times, but nothing happened.
Next I successfully booted in recovery mode but even when starting recovery the screen shows errors (see attachment):
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument
Installing a ZIP file, wipe cache and wipe data give even more errors.
So I thought I would try flashing through ADB/fastboot, and used the HuaweiUpdateExtractor tool to get the images. I can get manually in fastboot mode, but when I try to flash an image get the error
Code:
FAILED (remote: flash failure, ErrNo:2)
I tried using different files, USB ports, cables, linux and windows but nothing seems to help. Has anyone an idea what to do next?
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
blueIBI said:
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
Click to expand...
Click to collapse
Since I can not boot and it's not my own phone I have no clue what the version is
Luckily my PC recognizes the phone in fastboot (indeed with a weird name with a lot of ?), but I am not able to flash twrp because every time I try I get a FAILED response... Maybe the file I have is wrong. Could you point me to a thread about falshing twrp?
here is a guide for unlocking bootloader: http://forum.xda-developers.com/showthread.php?p=50724517
here is a twrp for JB roms: http://forum.xda-developers.com/showthread.php?p=47633501
here for KK roms: http://forum.xda-developers.com/showthread.php?p=51718302
maybe you need to unlock your bootloader at first
changes not working
Thanks for the links! I am able to flash an image, but for some reason my changes won't stick. When I boot in fastboot it says it is locked and I am able to unlock it, but everytime I reboot it is locked again. The same happens with twrp, I am able to flash the image but for some reason when I boot back into recovery nothing has changed.
My fastboot commands and output:
Code:
C:\Android>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 1.952s]
finished. total time: 1.952s
C:\Android>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.012s]
finished. total time: 0.012s
C:\Android>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Android>fastboot flash recovery twrp_2_6_3_3_recovery.img
sending 'recovery' (8690 KB)...
OKAY [ 0.259s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.650s
Any idea?
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
blueIBI said:
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
Click to expand...
Click to collapse
That's what I was afraid of..
I think the unlock code doesn't work correctly on this phone for some reason, but I don't think I'll be able to get an unlock code specific for my device from Huawei, without serial number and such which I can't get since the phone doesn't boot.
I hope there is some warranty left...
Results
If anyone is interested (perhaps in the future), the phone was sent for repairs and is working again. They probably replaced the motherboard, but luckily it all fell under the warranty.
Thanks to blueIBI for trying to help!!
Hey guys,
my girlfriend has an M9. Saturday it lied idle on the table and rebooted itself. When it booted it just showed the white screen with the HTC logo and the read disclaimer warning.
I rebooted with power off and volume up and the phone just bootlooped all the time. Shows black screen with HTC Logo.
I tried to press the Vol down button on a restart but that didnt work it just bootlooped as before. Then I pressed Vol up +down and could enter the bootloader. From there I entered twrp and tried to wipe the system and then it just shows:
"Could not mount /data and unable to find crypto footer." and it failed to mount /cache , /system, /data, /devlog, /carrier , /cota , /preload and "Unable to mount storage" followed by failes in /data and cache.
Every fail have an (Invalid argument).
I also tried following fastboot commands:
format system
Couldn't parse partition size '0x0X118000000'.
erasing 'system'...
OKAY [ 0.241s]
finished. total time: 0.241s
format data
Formatting is not supported for file system with type ''.
format cache
Couldn't parse partition size '0x0X14000000'.
erasing 'cache'...
OKAY [ 0.270s]
finished. total time: 0.270s
flash zip 0PJAIMG.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2368399706 is not a multiple of the block size 4096
OKAY [ 1.015s]
writing 'zip' 1/1...
(bootloader) HOSD CL#671447
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.209s
The output of getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.161.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_96.00.51201G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: VODAP102
all:
finished. total time: 0.006s
Could someone please tell me if it even possible to rescue the phone? Is there something I forget to try or do somebody know something?
I appreciate every help i could get.
And forgive my bad english.
I think Twrp has gone mental.. If i remember correctly you have to flash back to stock. Follow flippy's thread in the general section.
Beamed in by telepathy.
Thx for the answer first.
I already tried what is shown at the spreadsheet of Flippy. I downloaded the right RUU again and gave it one more try but the same. It appears "Start ui_updating". After a few seconds the screen turns black and it appears the HTC logo on an black screen and it vibrates and turn black agan and again the logo with vibration. If i immediatly try to flash it a second time, itcontinues,shows name of system types but the percent is still 0. When it reaches a certain system type (after 10 or 12) it reboots to the white screen with the green HTC logo and the red disclaimer and stuck there.
Do you have an idea?
I have the same error. We have to do something and solve this. Can you solve it?
you can also just get a backup for twrp, which is matching your cid/mainversion, wipe everything except your internal storage and restore the backup
Like i said at the beginning, its not possible to wipe the partitions. They cant be mounted by twrp. I tried already to install an TWRP Backup with the right CID but even that failed because twrp couldn't write to the partitions.
THX for your answers
Ah fock, at first remove your imei from first post, then tell me if your phone is s-offed or not
Sent from my HTC One M9 using XDA-Developers mobile app
Oh sry overlocked that the imei was there.
The phone is s-on.
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
DeeZZ_NuuZZ said:
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
Click to expand...
Click to collapse
It wont work. Phone dont let us to write anything
We cant change cid, mid, lock and unlock bootloader. It is emmc issue. Emmc have to change.
P.s. my phone is s-off.
degerli43 said:
It wont work. Phone dont let us to write anything
We cant change cid, mid, lock and unlock bootloader. It is emmc issue. Emmc have to change.
P.s. my phone is s-off.
Click to expand...
Click to collapse
you should be able to fix it with an install of a RUU. s-off has more chances for that.
the other guy should try to flash the firmware zip in RUU mode, not just normal mode. it should work.. if not he has to get a RUU, if that doesn't work.. yea only RMA or how it is called for you should help. if they won't fix it, sell the device, and get another one
DeeZZ_NuuZZ said:
you should be able to fix it with an install of a RUU. s-off has more chances for that.
the other guy should try to flash the firmware zip in RUU mode, not just normal mode. it should work.. if not he has to get a RUU, if that doesn't work.. yea only RMA or how it is called for you should help. if they won't fix it, sell the device, and get another one
Click to expand...
Click to collapse
When i type fastboot oem rebootRUU the phone rstarting rebooting continuously so i cant flash anything. It s very expensive device here and i love it. I will be so sad if it wont fix
DeeZZ_NuuZZ said:
get stock recovery for your mainversion/cid, re-lock the bootloader, and flash a signed firmware matching your cid/mainversion, and flash with fastboot oem rebootRUU
then fastboot flash firmware nameofthezip.zip and do this a second time and then fastboot erase cache and reboot into download mode, unlock bootloader again and flash twrp and you should be able to wipe everything
Click to expand...
Click to collapse
Ok when i type fastboot oem lock in the download mode, it restarts and stops again in the bootloop on the HTC logo with blackscreen. If I press Vol UP+DOWN I can see that the device is still unlocked.
Do you have any other ideas? And thx for your help
VGLink said:
Ok when i type fastboot oem lock in the download mode, it restarts and stops again in the bootloop on the HTC logo with blackscreen. If I press Vol UP+DOWN I can see that the device is still unlocked.
Do you have any other ideas? And thx for your help
Click to expand...
Click to collapse
Get the proper HTC fastboot files and try with that...if that doesn't work, your phone is dead..I can't help further, sorry
Sent from my HTC One M9 using XDA-Developers mobile app
Hi, its not possible to enter RUU or to relock or Flash the Phone. It seems its gone dead by itself. Nevertheless thank You for your help .
Hi,
TL;DR: Bootloader unlocked. "fastboot boot twrp.img" worked fine until I upgraded to OxygenOS 5.1.4 (from 5.0.4). Now "fastboot boot twrp.img" just does nothing.
I had a OxygenOS system (Android 8.0, I believe it was OOS 5.0.4), rooted with Magisk. Everything was fine. Stock recovery, I wanted to change it as little as possible. I could use twrp-3.2.1-x_blu_spark_v8.70-op5_op5t.img perfectly, via "flashboot boot /path/to/img".
Today I decided to upgrade. I had an OTA notification for months, for OOS 5.1.4 (Android 8.1). I made a full backup with TWRP. Read about latest ROMs, seems 5.1.6 has some Bluetooth issues.
I opened the 5.1.4 OTA notification, curious to read the Changelog. A message said I had a rooted phone, and the update would install a full version instead of the OTA. Also, I'd lose root. Nothing I didn't expect, but I still wanted to flash with TWRP. Unfortunately, the updater had already downloaded the ROM and suddenly restarted. I did not want to interrupt the update, so let it go through.
Phone booted on OOS 5.1.4 without problems. Unrooted, of course. I went into fastboot mode, and tried loading TWRP with "flashboot boot /path/to/twrp-3.2.1-x_blu_spark_v8.70-op5_op5t.img". The image gets downloaded, and boot takes about 10s (most of which is a warning message that my bootloader is unlocked). After that, I just drop back to the 1+ bootloader screen. If I then try repeating the same "flashboot boot ..." command, I get the error "FAILED (remote: 'Failed to load/authenticate boot image: 00000050')".
I tried:
Several TWRP versions, from Blu_Spark, Codeworkx and siankatabg. Don't remember all of them, but at least the latest ones, i.e. twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img, twrp-3.2.3-0-20180822-codeworkx-dumpling.img and TWRP_3.2.3-Pie_siankatabg_OP5.img.
Removing the screen pattern, lock screen None.
Upgrading to OOS 5.1.6 via stock recovery.
Different USB cable.
I can boot the phone to the OS just fine. But without TWRP I cannot flash Magisk, to root the phone. I have not tried flashing TWRP to recovery, because at least I know stock recovery works and don't want to lose that.
This is what I have from device-info (did not change from before the upgrade, when TWRP was working):
Code:
$ ./fastboot oem device-info
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
OKAY [ 0.001s]
Finished. Total time: 0.001s
This is how I'm trying to boot TWRP. From the OS, I hold the power button, press Reboot, then choose Bootloader (I have advanced reboot enabled). That takes me to a pretty screen with a menu and options to start the OS, boot to recovery, or restart bootloader. I can select using the volume up and volume down keys, but I just ignore the options and type the fastboot commands:
Code:
$ ./fastboot devices
<redacted> fastboot
$ ./fastboot boot ~/Android/OnePlus5t/TWRP/twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
Downloading 'boot.img' OKAY [ 0.819s]
booting OKAY [ 10.106s]
Finished. Total time: 10.936s
The 10s is basically the Android warning message saying the boot loader is unlocked and the data cannot be trusted. I get that when booting to normal OS as well. After that warning goes away, instead of getting TWRP, I just get a black screen with "1+ Bootloader".
In that screen, I can still type fastboot commands, but now I have a different error:
Code:
$ ./fastboot boot ~/Android/OnePlus5t/TWRP/twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
Downloading 'boot.img' OKAY [ 0.822s]
booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
Finished. Total time: 0.835s
I'm at a loss here. Can someone help? I've considered trying out the RedWolf alternative thing, but am worried it might mess with encryption or something. I could flash TWRP, but really worry that 1) if it doesn't work, I won't have any recovery at all, and 2) I'd like to keep the stock recovery as a fallback.
This could perhaps be more of a question for the developers? I posted here because I was not allowed to post in the "OnePlus 5T ROMs, Kernels, Recoveries, & Other Development" section.
Hello kind saviour,
I accidentally deleted my build.prop file and now my phone is stuck on "the boot loader is unlocked and software integrity cannot be guaranteed..." screen at boot.
I use the AOSIP rom for OnePlus 7t,if that helps.
I do NOT want to lose any data and preferably not lose any system settings either.
Updating the ROM is OK for me. Please let me know if that is a good idea however.
The good part:
fastboot boot TWRP.img works, sdcard data de-cryption works, i can access files with MTP. Already made a backup of most important data.
I do not know which AOSIP version I have, but it's not the latest.
Doesn't work: fastboot boot magisk-patched.img (image might be too old?)
Doesn't work: fastboot reboot fastboot + fastboot boot boot.img -> Error:
*FAILED (remote: 'Download is not allowed on locked devices')
Booting from A instead of B goes into infinite booting animation.
adb commands during twrp don't work
No adb access anywhere else
I have no backup of build.prop
I have a builT.prop file and i suspect i saved it with wrong name (but I still can't access /system partition)
I had access to /system partition during first twrp boot, but accidentally mounted it as read only the first time.
After following reboots to twrp, system is always unmountable (both from slot a as well as slot b).
Even after deleting twrp folder from pc, the system partition remains unmountable:
*Failed to mount '/system_root' (Permission denied)
*Failed to mount '/vendor' (Permission denied)
bootloader is unlocked & phone is rooted with magisk.
If you could help me with a solution where i can keep my data you would make me soo happy. Having a rough time with life lately and you could be my second coming of Jesus
Thanks in advance.
Dirty flash latest aosip with TWRP or with fastboot
HueyT said:
Dirty flash latest aosip with TWRP or with fastboot
Click to expand...
Click to collapse
Thank you! I will try that later today and report back.
I tried dirty flashing the latest AOSIP update, and it made everything worse. (Maybe I was on the wrong slot??)
Now there is no fastbootD, no recovery, and neither possible to fastboot boot twrp.img!
Only thing that worked was the bootloader (fastboot).
I didn't even get the usual "the boot loader is unlocked and software integrity cannot be guaranteed..." screen.
However, i changed slot with fastboot and now I have recovery and fastbootD and can boot twrp again.
Now I'm really worried about messing up my next steps, so would be super grateful for any help you can give me. I believe we are near a solution here.
Big Questions:
Should I dirty update the rom from fastbootD or from TWRP?
Which *SLOT* do I update from?
History of how everything went wrong:
Spoiler: command line messages and responses
fastboot update OSiP-10-Gapps-hotdogb-20210621-img.zip
Code:
--------------------------------------------
Bootloader Version...: unknown
Baseband Version.....:
Serial Number........: 9de0f5c0
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error:
Setting current slot to 'b'
FAILED (remote: 'set_active command is not allowed on locked devices')
fastboot: error: Command failed
fastboot oem device-info
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
//I manually rebooted to bootloader (fastboot) here//
fastboot oem device-info
Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
(bootloader) op_abl_version: 0x31
(bootloader) cal_rebootcount: 0x31
OKAY [ 0.050s]
Finished. Total time: 0.053s
fastboot reboot fastboot
Code:
Rebooting into fastboot
OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Update: i found a solution by updating adb/fastboot .exe files,
flashing twrp-3-5-1_10-hotdog-sdcardfs.img
and dirty flashing the latest aosip image in twrp's fastboot mode
I got a "QUALCOMM CrashDump Mode" message once but it boots to aosip now. We will see if the crashdump messages appear again or not.
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
0sm1um said:
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
Click to expand...
Click to collapse
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
demonntlxda said:
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
Click to expand...
Click to collapse
Well sadly Xiaomi locked down EDL mode and that needs people working for Xiaomi to fix it.
Sadly a service center will not fix it because they will convince you to dump your phone in a rubbish bin and buy a new mi 11 because Xiaomi could earn more.
So that is a bummer but your phone needs a new motherboard.