Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.
No such options
Psychotic0666 said:
try to flash official recovery, extracted from the from that you installed.
after extraction, you would be able to see recovry.img thats the official recovery, wipe cache and data restart, probably it should work.
or download the global rom and install it via OTG.
Click to expand...
Click to collapse
Dude thanks, but i dont have WIPE CACHE RESTART OPTIONS, plus i cant boot into any recovery TWRP or CHINESE stock, Thankfully i found a way to unlock bootloader i guess via FASTBOOT, , still no response and unable to get into OTG OR DATA RESET OR CACHE RESET OPTIONS
Here is the list of options i got.
REBOOT SYSTEM NOW = BOOTLOOP AGAIN
REBOOT TO RECOVERY MODE = BOOTLOOP AGAIN
REBOOT TO EMEG RECOVERY MODE = Black Screen no response.
BOOT TO EDLOAD = Success as PC detects the phone as a Qualcomm Device, NUBIA Recovery soft (Very old) also detects phone
POwer off = Bootloop AGAIN
KIndly help
thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.
Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.
JerryYin said:
Hi, maybe you should flash the twrp and use twrp to flash the stock udate package, the RM3 twrp can flash stock ota
package
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.
Psychotic0666 said:
Did you try to flash official recovery extracted from the zip.
Fastboot flash recovery recovery.img?
---------- Post added at 09:13 AM ---------- Previous post was at 09:10 AM ----------
I had the same problem, flashing official recovery helped me to get the recovery working again and then i flashed the global rom.. It worked for me.
Click to expand...
Click to collapse
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.
JerryYin said:
Hi, maybe you should flash the stock recovery and then try to update your system. You can't directly flash a global version to a Chinese version, they sign with different key I think.
Click to expand...
Click to collapse
thel'vadam said:
Yep tried that shows success, even on locked bootloader, since my fastboot can be unlocked via CMD, i can push any recovery into the phone, the issue is, i cant boot into recovery using any key / menu combination.
Click to expand...
Click to collapse
My suggestion is that flash the global version recovery first, and see if it can boot.
JerryYin said:
My suggestion is that flash the global version recovery first, and see if it can boot.
Click to expand...
Click to collapse
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,
thel'vadam said:
Tried that now, still unable to get into new recovery settings, im stuck with the same options as mentioned above,
Click to expand...
Click to collapse
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"
JerryYin said:
How about use fastboot commands?
fastboot boot "your recovery file"
Or flash the recovery into boot section?
fastboot flash boot "your recovery file"
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED
thel'vadam said:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.130s]
booting...
FAILED (remote: unknown command)
finished. total time: 2.134s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot recovery.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.127s]
writing 'boot'...
OKAY [ 0.627s]
finished. total time: 2.757s
C:\Program Files (x86)\Minimal ADB and Fastboot>
NOTHING HAPPENED
Click to expand...
Click to collapse
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this
JerryYin said:
Okay`````just asked some friend work for nubia, you need to flash the vbmeta.img into vbmeta partition with same software version recovery file, you can try to flash both chinese and global version. I will come back on Monday to see if you solve this
Click to expand...
Click to collapse
Can please elaborate this a little bit, also be informed that my RM3 is indian variant, it has separate indian variant ROM available from Nubia India 1.96 GB, so In my opinion GLOBAL AND CHINESE ROM s both wont work, my luck rests with the indian ROM. Ill still try whatever you suggest.
Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work
Psychotic0666 said:
Meanwhile try this, extract the official room
Fastboot oem nub_unlock nubia_nx629j
flash parameter parameter.img
Reboot
Fastboot oem nub_unlock nubia_nx629j
Fastboot flash boot boot.img
Then recovery
Then splash
Then modem non-hlos.bin
At last system.Img
Fastboot reboot
Fat 32 pendrive with official zip, rename =UPDATE, flash via otg, try it out, it might work
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.166s]
finished. total time: 0.167s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modem
erasing 'modem'...
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.008s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.748s]
writing 'dsp'...
OKAY [ 0.343s]
finished. total time: 2.093s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash parameter parameter.img
target reported max download size of 805306368 bytes
sending 'parameter' (0 KB)...
OKAY [ 0.009s]
writing 'parameter'...
OKAY [ 0.004s]
finished. total time: 0.015s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 3.432s]
writing 'boot'...
OKAY [ 0.406s]
finished. total time: 3.840s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.139s]
writing 'recovery'...
OKAY [ 0.518s]
finished. total time: 2.658s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash splash splash.img
target reported max download size of 805306368 bytes
sending 'splash' (7419 KB)...
OKAY [ 0.207s]
writing 'splash'...
OKAY [ 0.056s]
finished. total time: 0.265s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 805306368 bytes
sending 'modem' (144180 KB)...
OKAY [ 3.778s]
writing 'modem'...
OKAY [ 1.045s]
finished. total time: 4.826s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system'...
OKAY [ 0.027s]
sending sparse 'system' 1/5 (778291 KB)...
OKAY [ 17.596s]
writing 'system' 1/5...
OKAY [ 0.004s]
sending sparse 'system' 2/5 (697207 KB)...
OKAY [ 22.095s]
writing 'system' 2/5...
OKAY [ 0.003s]
sending sparse 'system' 3/5 (752301 KB)...
OKAY [ 24.678s]
writing 'system' 3/5...
OKAY [ 0.003s]
sending sparse 'system' 4/5 (782303 KB)...
OKAY [ 30.918s]
writing 'system' 4/5...
OKAY [ 0.003s]
sending sparse 'system' 5/5 (723054 KB)...
OKAY [ 30.517s]
writing 'system' 5/5...
OKAY [ 0.002s]
finished. total time: 125.859s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>
STILL SAME
Did you flash the files from global rom?
same incident.
thel'vadam said:
Here is the thing, RM3 launched in india week ago, and it had lot of bugs, capacitive button YouTube, finger print find in page chrome, sub standard camera app and loads of other bugs, So i downloaded the Chinese ROM v2.30 and put it in root storage of phone, I did not unlock bootloader or Enable USB debugging, Installed the ROM, the installation went smooth, and the device did not boot, ERROR THE DEVICE IS CORRUPT IT CANNOT BE TRUSTED, AND WILL NOT BOOT, VISIT THE LINK etc. a common error on RM3 Devices, i tried everything on this post https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page2 and this https://www.getdroidtips.com/nubia-emergency-tool-unbrick/ and many other methods as well, the main difference here is the My device is not Bootloader unlocker is NOT rooted is not USB debugging enabled, Only positive is that i can install few things via FASTBOOT, except RECOVERY which is obviously locked. KINDLY HLEP
Click to expand...
Click to collapse
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?
godric12 said:
we have the same exact situtation. i tried every method here https://forum.xda-developers.com/red-magic-3/help/device-corrupt-trusted-boot-t3940057 and here https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9 still to no avail. did you try this on your phone?
Click to expand...
Click to collapse
i was once able to get a white screen with green highlighted squicircles, it did allow me to acess the boot from OTG option, i tried installing the indian ROM, it installed successfully, then after restart, same FASTBOOT LOOP WITH ERROR, i dont know how i got to that menu, i repeated the exact steps again, im still not able to get PAST BOOT LOOP.
Psychotic0666 said:
Did you flash the files from global rom?
Click to expand...
Click to collapse
YES TRIED ALL GLOBAL CHINESE indian, all variants. All recovery files all respective System.img files.
IM USING ORIGINAL IN BOX USB C cable if thats a thing,
Though i do get this ERROR (( Invalid sparse file format at header magic )) while pushing SYSTEM.img, it still suceeds, in 5/5 parts. after brief waiting.
Switch off the device and turn back on the Try going to recovery manually with vol and power button
Related
Hi all, I need some (or much) help I'm trying to update to the 602 version, to EMUI 3.0 or the lollipop but I really can´t figure out how, downloaded 'My Rom v3.3' according to instructions I should update to 602 I've already downloaded a CWM flashable 'http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343' tryed to flash CWM via fastboot but nothing happens when I try to go to recovery just as the latest TWRP, What I'm missing? Please help. :crying:
KV92GT said:
Hi all, I need some (or much) help I'm trying to update to the 602 version, to EMUI 3.0 or the lollipop but I really can´t figure out how, downloaded 'My Rom v3.3' according to instructions I should update to 602 I've already downloaded a CWM flashable 'http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343' tryed to flash CWM via fastboot but nothing happens when I try to go to recovery just as the latest TWRP, What I'm missing? Please help. :crying:
Click to expand...
Click to collapse
Hi! You need to flash the stock recovery, b133 or b135 unfortunately I do not have those files, there's a post pointing to stock recovery but links are dead, may be someone here could be kind enough to provide those images for us
KV92GT said:
Hi all, I need some (or much) help I'm trying to update to the 602 version, to EMUI 3.0 or the lollipop but I really can´t figure out how, downloaded 'My Rom v3.3' according to instructions I should update to 602 I've already downloaded a CWM flashable 'http://forum.xda-developers.com/ascend-p7/general/cwm-flashable-b609-p7-l10-complete-t3004343' tryed to flash CWM via fastboot but nothing happens when I try to go to recovery just as the latest TWRP, What I'm missing? Please help. :crying:
Click to expand...
Click to collapse
I am exactly in the same situation for several weeks.....
My actual config is
My-Rom V1.2
TWRP 2.8.1.0
I want to upgrade to either My-Rom 3.3 or Stock lollipop
The main issue is that I can't do that with my actual recovery, and no other recovery works on my phone, no idea why.
The only recovery img that is working is the one I use at the moment: openrecovery-twrp-2.8.1.0.img
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery [COLOR="Green"]openrecovery-twrp-2.8.1.0.img[/COLOR]
target reported max download size of 838860800 bytes
sending 'recovery' (11896 KB)...
OKAY [ 0.463s]
writing 'recovery'...
OKAY [ 0.582s]
finished. total time: 1.047s
Here's a little peak on all recovery img files I have tried so far:
cwm.img
recovery_cwm.img
CWM-6.0.5.0.img
B609_recovery.img
recovery-clockwork-3.0.0.5-ascend.img
TWRP-2.8.7.0.img
TWRP-2.8.7.0.img
openrecovery-twrp-2.8.1.0.img
And you can see below that the flashing procedure is completely normal for all attempts
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.671s]
finished. total time: 1.130s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery_cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.461s]
writing 'recovery'...
OKAY [ 0.559s]
finished. total time: 1.023s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\CWM-6.0.5.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.570s]
finished. total time: 1.032s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\B609_recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.634s]
writing 'recovery'...
OKAY [ 0.793s]
finished. total time: 1.430s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery-clockwork-3.0.0.5-ascend.img
target reported max download size of 838860800 bytes
sending 'recovery' (3636 KB)...
OKAY [ 0.145s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.317s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\TWRP-2.8.7.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (13182 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 0.643s]
finished. total time: 1.157s
I grabbed all those recovery img here on the P7 forums and they are apparently working for most of us.
Consider I flashed each of them at least 5 times. None of them works but the last one.
The most horrible is that I don't even know WHY ???????
I have read countless threads in this forum to unblock the situation and I am still nowhere because, if I have found a few people having the same issue, I could not found any valid solution.
If you can, please help.
Well... Here you have it
Do it at YOUR OWN RISK!
This is the STOCK RECOVERY B135 from my Huawey Ascend P7
You can flash it using flashify or go with the fastboot procedure
1. Unpack it
2. Flash it
'https://mega.nz/#!0pF0jawS!Q8NNIkYIy_k2e6abgTYvAoyT11M92HL5iG9riG3f7-k'
SiulGKT said:
Well... Here you have it
Do it at YOUR OWN RISK!
This is the STOCK RECOVERY B135 from my Huawey Ascend P7
You can flash it using flashify or go with the fastboot procedure
1. Unpack it
2. Flash it
'https://mega.nz/#!0pF0jawS!Q8NNIkYIy_k2e6abgTYvAoyT11M92HL5iG9riG3f7-k'
Click to expand...
Click to collapse
Thank you! downloading,do you recommend flashify?
KV92GT said:
Thank you! downloading,do you recommend flashify?
Click to expand...
Click to collapse
You'de welcome, yes!
SiulGKT said:
You'de welcome, yes!
Click to expand...
Click to collapse
Thank you very much SiulGKT it worked like a charm! now I will try to update to 3.3! :laugh:
Crippius said:
I am exactly in the same situation for several weeks.....
My actual config is
My-Rom V1.2
TWRP 2.8.1.0
I want to upgrade to either My-Rom 3.3 or Stock lollipop
The main issue is that I can't do that with my actual recovery, and no other recovery works on my phone, no idea why.
The only recovery img that is working is the one I use at the moment: openrecovery-twrp-2.8.1.0.img
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery [COLOR="Green"]openrecovery-twrp-2.8.1.0.img[/COLOR]
target reported max download size of 838860800 bytes
sending 'recovery' (11896 KB)...
OKAY [ 0.463s]
writing 'recovery'...
OKAY [ 0.582s]
finished. total time: 1.047s
Here's a little peak on all recovery img files I have tried so far:
cwm.img
recovery_cwm.img
CWM-6.0.5.0.img
B609_recovery.img
recovery-clockwork-3.0.0.5-ascend.img
TWRP-2.8.7.0.img
TWRP-2.8.7.0.img
openrecovery-twrp-2.8.1.0.img
And you can see below that the flashing procedure is completely normal for all attempts
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.671s]
finished. total time: 1.130s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery_cwm.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.461s]
writing 'recovery'...
OKAY [ 0.559s]
finished. total time: 1.023s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\CWM-6.0.5.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (11848 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.570s]
finished. total time: 1.032s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery \\NAS1\tom\Firmwares\HuaweiP7\B609_recovery.img
target reported max download size of 838860800 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.634s]
writing 'recovery'...
OKAY [ 0.793s]
finished. total time: 1.430s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\recovery-clockwork-3.0.0.5-ascend.img
target reported max download size of 838860800 bytes
sending 'recovery' (3636 KB)...
OKAY [ 0.145s]
writing 'recovery'...
OKAY [ 0.169s]
finished. total time: 0.317s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery D:\Users\tom\Downloads\TWRP-2.8.7.0.img
target reported max download size of 838860800 bytes
sending 'recovery' (13182 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 0.643s]
finished. total time: 1.157s
I grabbed all those recovery img here on the P7 forums and they are apparently working for most of us.
Consider I flashed each of them at least 5 times. None of them works but the last one.
The most horrible is that I don't even know WHY ???????
I have read countless threads in this forum to unblock the situation and I am still nowhere because, if I have found a few people having the same issue, I could not found any valid solution.
If you can, please help.
Click to expand...
Click to collapse
I've uploaded the b135, give it a try.
---------- Post added at 04:41 PM ---------- Previous post was at 04:36 PM ----------
KV92GT said:
Thank you very much SiulGKT it worked like a charm! now I will try to update to 3.3! :laugh:
Click to expand...
Click to collapse
Glad to see it! You're welcome! Good luck!
There's an improvement for sure, to not say a breakthrough
I am in the Huwaei recovery and it is currently installing the B609 update.app that I put in dload folder.
Crossing fingers!
A big up to you already man :good:
B135 Installed
B609 Installed
B621 installing
Thanks again @SiulGKT
SiulGKT said:
Well... Here you have it
Do it at YOUR OWN RISK!
This is the STOCK RECOVERY B135 from my Huawey Ascend P7
You can flash it using flashify or go with the fastboot procedure
1. Unpack it
2. Flash it
'https://mega.nz/#!0pF0jawS!Q8NNIkYIy_k2e6abgTYvAoyT11M92HL5iG9riG3f7-k'
Click to expand...
Click to collapse
Hello, I'm sorry but when i try to download your file, mega is asking for a key, can you give me this key?
Hope you still have it
Hi,I have a l09-c432 with oreo flashed(8.0.0.311 c900) and rooted with SuperSU. I wanted to unroot,because I wanted to switch to magisk. Now my boot image is gone and I can't go into TWRP,even if I reflash it. I know it was a dump mistake. Flashing boot.img don't work like on nougat,there is no boot.img in the update.app. any help would be very nice. Can't use my phone any more?
After flashing ramdisk and kernel(thx @Blackball) the bootloader error message is gone but i'm not able to install TWRP or boot into system. Any more ideas?
I guess you have to unbrick it..
Hello, I had A8 back A7, I did not go through Hwota, TWRP recovery 3.1.1 Fasboot error, I uploaded recovery TWRP 3.2.1, the system no longer bumps and I can not get anywhere, only to TWRP, Hwota no longer works and upload system via TWRP 3.2.1 (p10 plus) error 9.
Does anyone know how to help?
Or do you upload a complete system via Fastboot? not HWOTA, as the A8 does not work
@Firicel69 And how do i unbrick? With Nougat it was never a problem, but with Oreo i can't get it working. Tried to extract system.img from update.app, also failed, because update extractor don't open Oreo files. 7zip also don't work. But the thing that makes me really crazy is that i can flash TWRP without error messages, but i can't boot into TWRP.
Huawei-UPDATE.APP-Toolkit OREO
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (40692 KB)...
OKAY [ 1.019s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flash recovery2 recovery2.img
target reported max download size of 471859200 bytes
sending 'recovery2' (40692 KB)...
OKAY [ 1.018s]
writing 'recovery2'...
FAILED (remote: partition length get error)
finished. total time: 1.030s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Microsoft Windows [Version 10.0.16299.192]
(c) 2017 Microsoft Corporation. Všetky práva vyhradené.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-vtr.img
target reported max download size of 471859200 bytes
sending 'recovery' (32040 KB)...
OKAY [ 0.846s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.859s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Updating TWRP update.zip Error: 9 Error instaliinig zip file external_sd/hwota/update.zip
@Brandy20 thx for the tool, now i have everything extracted and was able to flash the system.img with fastboot. Phone is booting again, but factory reset isn't possible. So something is still wrong.
Brandy20 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (40692 KB)...
OKAY [ 1.019s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.029s
C:\Program Files (x86)\Minimal ADB and Fastboot>Fastboot flash recovery2 recovery2.img
target reported max download size of 471859200 bytes
sending 'recovery2' (40692 KB)...
OKAY [ 1.018s]
writing 'recovery2'...
FAILED (remote: partition length get error)
finished. total time: 1.030s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Microsoft Windows [Version 10.0.16299.192]
(c) 2017 Microsoft Corporation. Všetky práva vyhradené.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-vtr.img
target reported max download size of 471859200 bytes
sending 'recovery' (32040 KB)...
OKAY [ 0.846s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.859s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Updating TWRP update.zip Error: 9 Error instaliinig zip file external_sd/hwota/update.zip
Click to expand...
Click to collapse
These are the commands for Nougat, Oreo is different.
fastboot flash recovery_ramdisk recovery_ramdisk.img(or TWRP8_3.0.3.img)
Thats why you get "partition length get error"
These are commands for Nougat, Oreo is different. And what commands are for Oreo?
Error Mode
Attention!
Please update system agaim
Error!
Func No: 11 (recovery image)
Error No: 2 (load failed!)
The command for flashing the recovery is:
fastboot flash recovery_ramdisk recovery_ramdisk.img
This helps to rollback to nougat:
https://forum.xda-developers.com/p10/how-to/guide-to-rollback-huawei-p10-oreo-to-t3735156
I managed to flash and enter TWRP again and did the stuff mentioned in the link above. One step further
Now my P10 is back like it was delivered. After rollback you have to rebrand it with this tutorial and you are good to go.
https://forum.xda-developers.com/p10/how-to/huawei-p10-debrand-rebrand-update-guide-t3691013
How to proceed exactly. Could you get the data?
Could not we send TWRP backups complete P10?
First, when you are still on Oreo flash Oreo TWRP with the command in #13. Then you have to rollback to Nougat with the tutorial link from #13. After that you have to rebrand your phone with the tutorial link from #14. With the P10 it is a little bit more tricky to get into TWRP. When phone is off hold Power and Vol+ untill you feel the vibration. Release the power button but keep holding Vol+ until you see TWRP. This was my problem in the beginning.
2. Download Firmare L29C900B217 or L09C900B217 depending your model (only are 2 downloads) fromhttp://pro-teammt.ru/firmware-database/?firmware_model=VTR-L29c900&firmware_page=0
non-functional link?
Download the two files needed with firmware finder, this works.
Sent from my [P10] using XDA-Developers Legacy app
link error
---------- Post added at 09:31 AM ---------- Previous post was at 08:47 AM ----------
Then you have to rollback to Nougat with the tutorial link from #13 ???
There is a link in post #13, there you'll find the tutorial.
You have to install firmware finder from play store on any phone. Then download two files with this app from the firmware L09C900B217, update.zip and update_full_VTR-L09_hw_normal.zip. There are enough turorials for the firmware finder.
I have tried following guides on going back to stock rom but getting many errors in doing that. I have also tried flashing many different roms with TWRP. I get many errors when doing that one of them is local error 7. One also tells me that it detects OEM partition now at potter. The model of this device is XT1806.
This is my attempt to get things back to stock.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.094s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.538s]
finished. total time: 0.695s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (71925 KB)...
OKAY [ 2.068s]
writing 'modem'...
OKAY [ 1.067s]
finished. total time: 3.151s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (3024 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.203s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.488s]
writing 'dsp'...
OKAY [ 0.284s]
finished. total time: 0.787s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.063s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.188s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.492s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.375s]
finished. total time: 0.867s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.614s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 0.484s]
finished. total time: 1.098s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (256355 KB)...
OKAY [ 7.384s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 7.415s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (262115 KB)...
OKAY [ 7.538s]
writing 'system'...
OKAY [ 3.399s]
finished. total time: 10.937s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (259034 KB)...
OKAY [ 7.468s]
writing 'system'...
OKAY [ 3.535s]
finished. total time: 11.019s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262013 KB)...
OKAY [ 7.507s]
writing 'system'...
OKAY [ 3.523s]
finished. total time: 11.046s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 7.517s]
writing 'system'...
OKAY [ 3.387s]
finished. total time: 10.920s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 7.492s]
writing 'system'...
OKAY [ 3.283s]
finished. total time: 10.775s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (259637 KB)...
OKAY [ 7.466s]
writing 'system'...
OKAY [ 3.293s]
finished. total time: 10.775s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (240915 KB)...
OKAY [ 6.953s]
writing 'system'...
OKAY [ 3.633s]
finished. total time: 10.617s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 7.506s]
writing 'system'...
OKAY [ 3.650s]
finished. total time: 11.155s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (233189 KB)...
OKAY [ 6.672s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 7.237s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (65436 KB)...
OKAY [ 1.890s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.905s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (145482 KB)...
OKAY [ 4.172s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.172s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.813s]
finished. total time: 0.813s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase DDR
erasing 'DDR'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
I'll need a bit more information.
What stock ROM did you try and flash? There's stock Nougat for the xt1806 that is different that stock Nougat for the other versions (XT1800,XT1801,XT1802,etc). It seems the Stock Oreo build can be flashed to all of them with minor issues.
Also, why are you trying to flash an OTA using TWRP? That won't work.
pizzaboy192 said:
I'll need a bit more information.
What stock ROM did you try and flash? There's stock Nougat for the xt1806 that is different that stock Nougat for the other versions (XT1800,XT1801,XT1802,etc). It seems the Stock Oreo build can be flashed to all of them with minor issues.
Also, why are you trying to flash an OTA using TWRP? That won't work.
Click to expand...
Click to collapse
I figured out after that it was OTA. The point I was trying to show was that it is detecting potter on the OEM partition. All other roms like PixelExperience, Xtended Rom and Arrow all just give error 7. E1001 : Failed to update system image.
I am trying to flash stock ROM SANDERS_OPS28.65-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
briant97 said:
I figured out after that it was OTA. The point I was trying to show was that it is detecting potter on the OEM partition. All other roms like PixelExperience, Xtended Rom and Arrow all just give error 7. E1001 : Failed to update system image.
I am trying to flash stock ROM SANDERS_OPS28.65-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
Click to expand...
Click to collapse
Not sure about this but check in your root (/) and/or /vendor directory for default.prop file (/vendor might have a build.prop instead). Check to see if there's anything odd there. I once had a default.prop with entries from a long-forgotten custom ROM that was causing issues. See if potter is in any of them.
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
Not sure about this but check in your root (/) and/or /vendor directory for default.prop file (/vendor might have a build.prop instead). Check to see if there's anything odd there. I once had a default.prop with entries from a long-forgotten custom ROM that was causing issues. See if potter is in any of them.
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
default.prop
https://ghostbin.com/paste/bx9uj
build.prop
I could not find a build.prop file anywhere.
briant97 said:
default.prop
https://ghostbin.com/paste/bx9uj
build.prop
I could not find a build.prop file anywhere.
Click to expand...
Click to collapse
Every ROM has a build.prop, if I'm not mistaken, sitting in /system directory.
EDIT: Your default.prop looks good. Has sanders throughout and shows sdk25 (Nougat).
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
Every ROM has a build.prop, if I'm not mistaken, sitting in /system directory.
EDIT: Your default.prop looks good. Has sanders throughout and shows sdk25 (Nougat).
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
I cannot find a build.prop file /system only contains a lost and found directory.
I also looked through every single directory. Can someone provide me with a flashable build.prop file maybe that would help resolve.
This is oem.prop file. May need a way to resolve this file is part of the issue as well. This for sure contains potter info.
#
# OEM_BUILD_PROPERTIES
#
ro.build.version.incremental=b8ea
ro.build.version.ci=16
ro.mot.build.guid=54d0fbcff7908bd
ro.product.name=potter
ro.mot.build.oem.product=potter
ro.mot.build.customerid=retail
Also here is my recovery.log for when i tried to flash Xtended Rom
https://hastebin.com/uvejafafug.sql
briant97 said:
I cannot find a build.prop file /system only contains a lost and found directory.
I also looked through every single directory. Can someone provide me with a flashable build.prop file maybe that would help resolve.
This is oem.prop file. May need a way to resolve this file is part of the issue as well. This for sure contains potter info.
#
# OEM_BUILD_PROPERTIES
#
ro.build.version.incremental=b8ea
ro.build.version.ci=16
ro.mot.build.guid=54d0fbcff7908bd
ro.product.name=potter
ro.mot.build.oem.product=potter
ro.mot.build.customerid=retail
Also here is my recovery.log for when i tried to flash Xtended Rom
https://hastebin.com/uvejafafug.sql
Click to expand...
Click to collapse
simple just flash the correct stock image as i can see you can successfully flash bootloader of sanders
chirayu19091997 said:
simple just flash the correct stock image as i can see you can successfully flash bootloader of sanders
Click to expand...
Click to collapse
Can you please let me know how to do this correctly. As you can see above I tried to flash it via the bootloader back to stock using the commands. If I can use TWRP, where can I find a flashable stock rom. As so far nothing is working.
briant97 said:
Can you please let me know how to do this correctly. As you can see above I tried to flash it via the bootloader back to stock using the commands. If I can use TWRP, where can I find a flashable stock rom. As so far nothing is working.
Click to expand...
Click to collapse
As far as a TWRP flashable for the XT1806, this is what I used way back when. Nougat. Still on it as a primary ROM. No chance of OTAs or anything but I'm not interested in stock Oreo anyway.
https://forum.xda-developers.com/showthread.php?t=3738502
[ROM][STOCK][TWRP ZIP] Sanders Stock 7.1.1 rooted NPS26.116-61
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Here is my attempts to flash this stock file. It still wont boot to an OS. Just reboots to twrp.
Total brain freeze. I remember the rebooting into TWRP thing and there were numerous posts about it. Fix was trivial but for the life of me I can't remember.
As far as getting into the OS, have you tried manually via the bootloader screen?
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
Total brain freeze. I remember the rebooting into TWRP thing and there were numerous posts about it. Fix was trivial but for the life of me I can't remember.
As far as getting into the OS, have you tried manually via the bootloader screen?
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
How do you manually get into the OS via bootloader?
briant97 said:
How do you manually get into the OS via bootloader?
Click to expand...
Click to collapse
In TWRP, choose "reboot bootloader" and then in that, choose "start"
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
briant97 said:
Here is my attempts to flash this stock file. It still wont boot to an OS. Just reboots to twrp.
Click to expand...
Click to collapse
That 2nd shot is normal errors for that specific restore (even says so in the OP). Looks good so far, just need to get it to boot to OS
pizzaboy192 said:
In TWRP, choose "reboot bootloader" and then in that, choose "start"
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
That 2nd shot is normal errors for that specific restore (even says so in the OP). Looks good so far, just need to get it to boot to OS
Click to expand...
Click to collapse
It will not boot into the OS.
Anybody have any other ideas or thoughts. The oem partition is still the issue. Is there anyway to reflash this partition to the correct version?
I tried letting the phone boot over night as requested above but it never booted.
Hmm I made a bat file to fix this issue but can't find it
the concept is the bootloader accepts the firmware I told you can flash rom because you can flash Sanders bootloader and as seen in op
will see bat just hit me a private message me busy till 27 Nov 2018 and I can help on 27 or 28 IST
marcdw said:
Total brain freeze. I remember the rebooting into TWRP thing and there were numerous posts about it. Fix was trivial but for the life of me I can't remember.
As far as getting into the OS, have you tried manually via the bootloader screen?
LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
Sent you a private message.
I think you should try QPST flashing because this method will flash stock rom while device is off or even no battery,hope this can overwrite your prev wrong rom,
glewo45 said:
I think you should try QPST flashing because this method will flash stock rom while device is off or even no battery,hope this can overwrite your prev wrong rom,
Click to expand...
Click to collapse
https://androidmtk.com/use-qpst-flash-tool
I got to step 5 here and nothing shows under ports. I have tried when phone is at bootloader and also when phone is in twrp.
i have another huawei device, but not honor play.
Now the display can't show me anything even if I press the power button.
Then i connected my phone to my computer and i found that my phone had automatically booted bootloader without showing me anything on its display
i entered fastboot flash recovery recovery.img
it said failed remote command not allowes
i entered fastboot oem relock (password)
it said OKAY
i entered fastboot oem unlock (password)
it said OKAY
i entered fastboot flah boot boot.img
it said failed remote partition length get erro
i used hisuit but it failed when flashing recovery
So i can hardly do anything
how to deal with the problem?
pls help me
thank u
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Can you enter erecovery??
Nwereonye said:
Can you enter erecovery??
Click to expand...
Click to collapse
No. the phone cant show me anything. if i try to turn it off, it will restart.(according to my computer)
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
I'm busy these days. I'll post the log some days later
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
Today I download a package for my device from Firmware finder for Huawei. Then I used Huawei Update Extractor to extract some of the files and tried to flash them to my phone. But failed.
Here's the log
PS C:\WINDOWS\system32> fastboot devices
3CG4C16817019572 fastboot
PS C:\WINDOWS\system32> fastboot flash boot C:\Users\yyche\Desktop\update\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15494 KB)...
OKAY [ 0.400s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.430s
PS C:\WINDOWS\system32> fastboot flash crc C:\Users\yyche\Desktop\update\CRC.img
target reported max download size of 471859200 bytes
sending 'crc' (161 KB)...
OKAY [ 0.006s]
writing 'crc'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update
error: cannot load 'C:\Users\yyche\Desktop\update'
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update\FASTBOOT.img
target reported max download size of 471859200 bytes
sending 'fastboot' (3128 KB)...
OKAY [ 0.081s]
writing 'fastboot'...
FAILED (remote: Command not allowed)
finished. total time: 0.092s
PS C:\WINDOWS\system32> fastboot flash recovery C:\Users\yyche\Desktop\update\RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (35540 KB)...
OKAY [ 0.914s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.946s
PS C:\WINDOWS\system32> fastboot oem unlock 1**************4
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.004s
Do not flash the latest version, it seems u r tying to flash Android Pie. Try to flash Oreo (8.0) version of rom or the one that comes factory installed.
I've got to unbrick my phone, I think.
I can't boot into system or recovery cause my phone is bricked.
What should I do?
When I start fastboot and try to flash twrp, ther comes this message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery 4_twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.532s]
writing 'recovery'...
FAILED (remote: This partition doesn't exist)
finished. total time: 1.563s
This is an a/b device , use fastboot flash boot instead of fastboot flash recovery