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.
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
hello iam just newer on xda , & i have probleme with my honor 9 lite is bricked whene iam downgrade my device used hisuite , the device fixed on fastboot mode and black screen , frp locked , bootloader locked
can anyone helpe me please
model : lld-l21
lilolahcen said:
hello iam just newer on xda , & i have probleme with my honor 9 lite is bricked whene iam downgrade my device used hisuite , the device fixed on fastboot mode and black screen , frp locked , bootloader locked
can anyone helpe me please
Click to expand...
Click to collapse
help meeeeeeee please
lilolahcen said:
help meeeeeeee please
Click to expand...
Click to collapse
Can you get into recovery?
Have you held power button for 10 seconds to reboot from fastboot if you can't use terminal
villapark75 said:
Can you get into recovery?
Have you held power button for 10 seconds to reboot from fastboot if you can't use terminal
Click to expand...
Click to collapse
no, i can't get into recovery because the device does'nt boot
i can use a terminal but , when i write fastboot reboot , the device reboots and returns to fastboot
What happens when you issue 'fastboot reboot' hit enter and immediately unplug USB from PC ?
Sparkrite said:
What happens when you issue 'fastboot reboot' hit enter and immediately unplug USB from PC ?
Click to expand...
Click to collapse
i didn' try it , But i flashed the device via adb fastboot
However, the flash does not pass , Just get me this error
failed (remote command not allowed )
lilolahcen said:
i didn' try it , But i flashed the device via adb fastboot
However, the flash does not pass , Just get me this error
failed (remote command not allowed )
Click to expand...
Click to collapse
that my adb show when i am use it
C:\adb>fastboot devices
MKJNW18531002486 fastboot
C:\adb>
C:\adb>fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.152s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.170s
C:\adb>fastboot flash recovery_vbmeta recovery_vbmeta.img
target reported max download size of 471859200 bytes
sending 'recovery_vbmeta' (6 KB)...
OKAY [ 0.004s]
writing 'recovery_vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.018s
C:\adb>fastboot flash recovery_vendor recovery_vendor.img
target reported max download size of 471859200 bytes
sending 'recovery_vendor' (16384 KB)...
OKAY [ 0.580s]
writing 'recovery_vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.597s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 28.857s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 28.889s
C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (16 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
please can you help me :crying::crying::crying:
lilolahcen said:
that my adb show when i am use it
C:\adb>fastboot devices
MKJNW18531002486 fastboot
C:\adb>
C:\adb>fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.152s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 1.170s
C:\adb>fastboot flash recovery_vbmeta recovery_vbmeta.img
target reported max download size of 471859200 bytes
sending 'recovery_vbmeta' (6 KB)...
OKAY [ 0.004s]
writing 'recovery_vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.018s
C:\adb>fastboot flash recovery_vendor recovery_vendor.img
target reported max download size of 471859200 bytes
sending 'recovery_vendor' (16384 KB)...
OKAY [ 0.580s]
writing 'recovery_vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.597s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 28.857s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 28.889s
C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (16 KB)...
OKAY [ 0.005s]
writing 'vbmeta'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
please can you help me :crying::crying::crying:
Click to expand...
Click to collapse
Hello. Hope you have enough data on your plan. First download the firmware from this link https: // androidhost . ru / 9X9 (remove the spaces while pasting). Once downloaded extract the contents from the zip file to your pc. Before proceeding make sure your smartphone is charged. In the extracted contents you will have a folder named 'Software'. Inside that folder you will have a folder named 'dload'. Copy the 'dload' folder to the root directory of a formatted sd card. Once it is copied insert the sd card inside your honor 9 lite and press the power, volume up and down buttons simultaneously until your phone enters recovery mode. From there it will take a few minutes for the software installation to be completed. Once the installation is finished your phone will be rebooted and you will have to finish the initial setting up process. If you follow these steps you can recover your phone but you will loose all the data previously present in the phone. Hope this works for you. Please reply if this is successful.
Leeban Joseph said:
Hello. Hope you have enough data on your plan. First download the firmware from this link https: // androidhost . ru / 9X9 (remove the spaces while pasting). Once downloaded extract the contents from the zip file to your pc. Before proceeding make sure your smartphone is charged. In the extracted contents you will have a folder named 'Software'. Inside that folder you will have a folder named 'dload'. Copy the 'dload' folder to the root directory of a formatted sd card. Once it is copied insert the sd card inside your honor 9 lite and press the power, volume up and down buttons simultaneously until your phone enters recovery mode. From there it will take a few minutes for the software installation to be completed. Once the installation is finished your phone will be rebooted and you will have to finish the initial setting up process. If you follow these steps you can recover your phone but you will loose all the data previously present in the phone. Hope this works for you. Please reply if this is successful.
Click to expand...
Click to collapse
Very late to the party, but wanted to thank you for a comprehensive, helpful answer.
The fact lilolahcen didn't respond is hopefully because his phone is working once again.
Good post ?
Thanks. I myself have gone through many guides available here at xda. So I hope I can be of some use for someone who is facing the same problems I have faced.
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