Related
This method works for both variants (16 GB and 32 GB). I just whant to make an thread because 2 days ago i just bricked my nexus 5x 16 GB by lock bootloader with Resurection
Remix installed and with an custom recovery (TWRP). After 1 day of searching i give it up. Yestarday i just start again and i did it .
THIS WAS TESTED WITH AN NEXUS 6P ORIGINAL CABLE. DO NOT USE AFTERMARKET CABLES BECAUSE DON`T HAVE THE SERIALS PINS AND THE LGUP AND PC WILL NOT SEE YOUR PHONE IN DOWNLOAD MODE
thanks to : bitdomo gee one JaCh0o sniperIT
support threads
http://forum.xda-developers.com/nexus-5x/help/device-locked-t3355549/post66318089#post66318089
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://developer.android.com/preview/download-ota.html
Steps
1. Download TOT file for your device
2. Download LG usb drivers
3. Download LGUP tool
4. Download 8994 dll for LGUP
5. Install LG usb drivers
6. Install LGUP tool
7. Install 8994 dll for LGUP
8. Turn off your phone
9. Press and hold the volume_up key while you connect the phone to the PC with usb cable.
10. Wait for Windows to install the new drivers
11. Start LGUP
12. Put the TOT file like in the screenshot.
13. Push start and wait
14. Let the progress to 100 %.
15. The phone will boot and will recive and message about your internal memory problem (16 GB variant) because the TOT file is for 32 GB model.
ignore that message
16.Now unlock bootloader (enter in develop mode tick that button enter on bootloader and just use fastboot oem unlock press yes . The phone will factory reset and enter
again on the android)
17. Reboot to bootloader and move the arrows till see recovery mode ! Keep press the power button when the recovery animation apear and press twice vol + and wipe data/cache
like a factory reset, and then just use ADB SIDELOAD from recovery
18. Copy on the adb folder the Android N 7 OTA and use on the pc on cmd adb sideload name.zip , after finish reboot
19. The phone will enter on Android N 7 . BECARFULL BECAUSE AFTER BOOT YOUR BOOTLOADER IS LOCKED AUTOMATICALY AFTER ANDROID 7 N WAS INSTALLED.
20. Unlock the bootloader and now can be write the official android 6.0.1 (don`t try to write only after the android n 7 was installed because you will recive an error about system and internal memory
again the TOT file is for 32 gb)
I followed the steps, however at step 15 my phone just froze at the Google logo, but I have the 32 GB variant so that may be expected (Note that I enabled OEM/bootloader locking like an idiot when trying to solve this a few hours ago). I waited ten minutes and it remained stuck at that logo, so I rebooted into the bootloader, went into recovery, and ran "adb sideload bullhead-ota-nrd90m-fdb8250a.zip". It seems like it installed without any problems, except when I booted back to system, I got stuck at the four dots again...
Could any LG experts provide insight? I'm about to just have the phone replaced, but I'm flying across the country in less than a week, so I'll need a phone...
jabarel said:
This method works for both variants (16 GB and 32 GB). I just whant to make an thread because 2 days ago i just bricked my nexus 5x 16 GB by lock bootloader with Resurection
Remix installed and with an custom recovery (TWRP). After 1 day of searching i give it up. Yestarday i just start again and i did it .
THIS WAS TESTED WITH AN NEXUS 6P ORIGINAL CABLE. DO NOT USE AFTERMARKET CABLES BECAUSE DON`T HAVE THE SERIALS PINS AND THE LGUP AND PC WILL NOT SEE YOUR PHONE IN DOWNLOAD MODE
thanks to : bitdomo gee one JaCh0o sniperIT
support threads
http://forum.xda-developers.com/nexus-5x/help/device-locked-t3355549/post66318089#post66318089
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://developer.android.com/preview/download-ota.html
Steps
1. Download TOT file for your device
2. Download LG usb drivers
3. Download LGUP tool
4. Download 8994 dll for LGUP
5. Install LG usb drivers
6. Install LGUP tool
7. Install 8994 dll for LGUP
8. Turn off your phone
9. Press and hold the volume_up key while you connect the phone to the PC with usb cable.
10. Wait for Windows to install the new drivers
11. Start LGUP
12. Put the TOT file like in the screenshot.
13. Push start and wait
14. Let the progress to 100 %.
15. The phone will boot and will recive and message about your internal memory problem (16 GB variant) because the TOT file is for 32 GB model.
ignore that message
16.Now unlock bootloader (enter in develop mode tick that button enter on bootloader and just use fastboot oem unlock press yes . The phone will factory reset and enter
again on the android)
17. Reboot to bootloader and move the arrows till see recovery mode ! Keep press the power button when the recovery animation apear and press twice vol + and wipe data/cache
like a factory reset, and then just use ADB SIDELOAD from recovery
18. Copy on the adb folder the Android N 7 OTA and use on the pc on cmd adb sideload name.zip , after finish reboot
19. The phone will enter on Android N 7 . BECARFULL BECAUSE AFTER BOOT YOUR BOOTLOADER IS LOCKED AUTOMATICALY AFTER ANDROID 7 N WAS INSTALLED.
20. Unlock the bootloader and now can be write the official android 6.0.1 (don`t try to write only after the android n 7 was installed because you will recive an error about system and internal memory
again the TOT file is for 32 gb)
Click to expand...
Click to collapse
hi. i did this but my phone was international version and with flashing this rom
my Boot loader locked and never unlock with nexus root toolkit
what can i do now?
mgtbmgtb said:
hi. i did this but my phone was international version and with flashing this rom
my Boot loader locked and never unlock with nexus root toolkit
what can i do now?
Click to expand...
Click to collapse
i have international too ! let me know what you did !
jabarel said:
i have international too ! let me know what you did !
Click to expand...
Click to collapse
my bootloader was locked too ! let me know all details but if your phone boots in bootloader will work even your bootloader is locked ! so you need to have and original cable or compatible one because if you boot on download mode your pc don`t reconigze the phone ! aftermarket cables don`t have serials pins !
1. boot on download mode
2.write that TOT file (maybe you will remain stuck on google logo after you write the TOT file)
3.Enter on recovery mode wipe/cache and then use adb sideload to write the ota zip file (this will repair your partiton )
let me know if you figure it out ! I`m on USA on vacation but tomorow i will fly home and i will try to help you more !
Huskehn said:
I followed the steps, however at step 15 my phone just froze at the Google logo, but I have the 32 GB variant so that may be expected (Note that I enabled OEM/bootloader locking like an idiot when trying to solve this a few hours ago). I waited ten minutes and it remained stuck at that logo, so I rebooted into the bootloader, went into recovery, and ran "adb sideload bullhead-ota-nrd90m-fdb8250a.zip". It seems like it installed without any problems, except when I booted back to system, I got stuck at the four dots again...
Could any LG experts provide insight? I'm about to just have the phone replaced, but I'm flying across the country in less than a week, so I'll need a phone...
Click to expand...
Click to collapse
reboot in recovery wipe/cache factory reset sorry for delay i was in vacation
plz 16gb tot
tuningsea said:
plz 16gb tot
Click to expand...
Click to collapse
it`s working with 32 gb too ! mine is 16gb i unbrick my phone with 32 gb TOT file.... thats the reason why i send via adb sideload the android n ota file to repair the partition table...
jabarel said:
i have international too ! let me know what you did !
Click to expand...
Click to collapse
hi again. i flash the tot. after that i wiped cache partition on recovery. and i flash the bullhead-ota-nrd90m-fdb8250a.zip with sideload on recovery. process completed successfully but in middle of flashing This message appears:
E: unknown command [log]
i checked log and This is what was written:
E:faild to mount /cache (invalid argument)
E:cant mount /cache/recovery/last_locale
locale is [(null)]
then i reboot and my phone stuck in boot and reboting again
my phone is locked so i cant flash cache.img with nexus root toolkit
what can i do body?
mgtbmgtb said:
hi again. i flash the tot. after that i wiped cache partition on recovery. and i flash the bullhead-ota-nrd90m-fdb8250a.zip with sideload on recovery. process completed successfully but in middle of flashing This message appears:
E: unknown command [log]
i checked log and This is what was written:
E:faild to mount /cache (invalid argument)
E:cant mount /cache/recovery/last_locale
locale is [(null)]
then i reboot and my phone stuck in boot and reboting again
my phone is locked so i cant flash cache.img with nexus root toolkit
what can i do body?
Click to expand...
Click to collapse
after you flash the tot file your phone starts? Try after you write TOT file to enter on recovery and use wipe/cache factory reset and see if boot ! Don`t write the ota file only after you check if starts after you write TOT file. I will upload for you another OTA file to try with this. i will send you the link, it`s a beta one because when you use this OTA will erase everything and will repair the partitions and will lock the bootloader. Try with this OTA file. Try to boot after you write the TOT file. I was destroy 2 days when i bricked my nexus, i know how it is......! Let me know if you will win this time. I hope you will unbrick your phone
https://drive.google.com/file/d/0B03qc7cQ-LeDSUFuMmYxOVZ2ZjA/view?usp=sharing
got to step 10 my phone was stuck at zero percent on the firmware update screen and the windows computer was not doing anything related to driver install
---------- Post added at 10:57 PM ---------- Previous post was at 10:24 PM ----------
my phone got stuck on the google logo after step 15 and i tried to do what yo said and go into recovery but when i boot itto recovery there is a Android man with a red triangle and an exclamation mark. plz help!! also twrp got erased when i use the lg tool
There is a combination of up and power button. Google how to get into stock recovery. This is what you see.
http://forum.xda-developers.com/showthread.php?p=69092591
Hello,
I was wondering how to create a TOT file by myself.
Is there any guide somewhere?
Sorry for raising this thread from the dead but what can I do if my device isn't recognized on my computer in mode 9008?
I connect it to my computer but it's not doing a thing and after a few seconds boot up with this error.
Hello Guys,
The issue is that i wanted to root my lenovo k8 note so follow this link "https://forum.xda-developers.com/android/development/tutorials-how-to-root-lenovo-k8-note-t3685502", Everything works file but in last rooting step no. 9
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
but in my device there has memory 59999mb so i ignored and reboot using twrp but it says no OS installed
and shows orange state, then i format phone using twrp but nothing happens again orange state and no os installed.
then i found another article with same issue "https://forum.xda-developers.com/android/help/lenovo-k8-note-stuck-boot-logo-flashing-t3751324/post75974342#post75974342" and found this
The bootlogo issue.
Hey! I read your post regarding your k8 note being stuck at the bootlogo.
Consider that you can still use TWRP, boot into it.
Then go ahead and download the SuperSU zip on your PC/laptop and connect your phone with a USB. You might be able to see the SD card folders on your PC, then you can just copy and paste it to the internal sd and flash it. You'll be good to go. If that doesn't work, in the TWRP Mode, go to advanced and select ADB sideload. You can now flash using ADB sideload.
Search for tutorials on ADB sideload. It's easy and that should work.
Click to expand...
Click to collapse
solution over there and flash supersu but nothing happens.
After so many try i locked oem bootloader in fastboot using command "fastboot oem lock", after this my lenovo k8 note show Red State.
Now i am not able to do anythig please help me out.
Basically my device is stuck at the bootloop with the
Red State
=> "Your Device has fail to pass verification and may not work properly
your device will boot in 10 sec trusted
Your device will boot in 5 seconds"
definitely I must have screwed up something.
Please help me to boot my Lenovo K8 note in normal mode.
Thanks
beingfhd said:
Hello Guys,
The issue is that i wanted to root my lenovo k8 note so follow this link "https://forum.xda-developers.com/android/development/tutorials-how-to-root-lenovo-k8-note-t3685502", Everything works file but in last rooting step no. 9
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
but in my device there has memory 59999mb so i ignored and reboot using twrp but it says no OS installed
and shows orange state, then i format phone using twrp but nothing happens again orange state and no os installed.
then i found another article with same issue "https://forum.xda-developers.com/an...-flashing-t3751324/post75974342#post75974342" and found this solution over there and flash supersu but nothing happens.
After so many try i locked oem bootloader in fastboot using command "fastboot oem lock", after this my lenovo k8 note show Red State.
Now i am not able to do anythig please help me out.
Basically my device is stuck at the bootloop with the
Red State
=> "Your Device has fail to pass verification and may not work properly
your device will boot in 10 sec trusted
Your device will boot in 5 seconds"
definitely I must have screwed up something.
Please help me to boot my Lenovo K8 note in normal mode.
Thanks
Click to expand...
Click to collapse
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Thanks
Anas Rahman said:
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Click to expand...
Click to collapse
Thanks for the reply but i recovered it using flash stock rom.
But i have another ques that can i flash twrp without oem unlock?
beingfhd said:
Thanks for the reply but i recovered it using flash stock rom.
But i have another ques that can i flash twrp without oem unlock?
Click to expand...
Click to collapse
No you can't
k8 note stuck on bootloop...??
need help.....my k8 note was running oreo....thn i downgraded to nougat...duo to bugs on oreo... thn i was facing more problems... so i decided to flash oreo again. ... i was trying to flash...but i was getting some brom error...so i thought it might be due to unlocked bootloader... so i tried to lock it.. and then try... and the system got deleted.... i cant even access fastboot... but device is detecting on sp flash tool... but getting the same error... help buddy... its urgent.. my device is not turning on... but the led is working....
DeepRBasak said:
need help.....my k8 note was running oreo....thn i downgraded to nougat...duo to bugs on oreo... thn i was facing more problems... so i decided to flash oreo again. ... i was trying to flash...but i was getting some brom error...so i thought it might be due to unlocked bootloader... so i tried to lock it.. and then try... and the system got deleted.... i cant even access fastboot... but device is detecting on sp flash tool... but getting the same error... help buddy... its urgent.. my device is not turning on... but the led is working....
Click to expand...
Click to collapse
This might be helpful https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
thank u somuch am also mobile sevice man it help full for me
Anas Rahman said:
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Click to expand...
Click to collapse
I have the same problem. please help us!
HARDROCK2614 said:
I have the same problem. please help us!
Click to expand...
Click to collapse
What problem do you have, please describe
I have lost all my mind and need serious help.
Recently, the march update came. i forgot that rooted phone should not be updated by the OTA update. And i did. As a result i got stuck in a bootloop. Then I had to use the oreo ROM from this forum and flashed it using SP Flash tool. It was a successfull flash. Then I used Maui META to write the IMEI for both sim. That was successfull too(Wifi and bluetooth addresses were working by themselves and i didnt write the serial number of the phone).
After working nicely for three days, i was using Whatsapp and a friend of mine sent me a .pptx file (powerpoint presentation). I opened it using WPS office app. I opened it multiple times in morning with no problems. But in the afternoon at about 2.53 PM while i was in my car, i was unable to open the file. The phone hanged. It heated up. To get out of the hang, i restarted the phone using the power button. IT DID NOT START. All it showed was the lenovo logo screen. And after doing more restarts, the phone went completely blank.
Now i cannot start it, or charge it. So i thought of flashing it again. But when i connect it to my PC, it keeps CONNECTING and DISCONNECTING. what i saw in the device manager was that the driver keeps changing very fast betwee MTK USB PORT and PRELOADER.
I found the solution to be updating the drivers manually. I did. Now the driver shows only DA USB VCOM and when it changes, it goes invisible in the PC and then appears back. Now when i start flashing, the first red progress bar appears as: Download DA 100%. and the flash hangs. After some time, this error will popup: ERROR: STATUS_UNKNOWN_STORAGE_TYPE (0xC0040009)
Please someone help me.
custom619 said:
Recently, the march update came. i forgot that rooted phone should not be updated by the OTA update. And i did. As a result i got stuck in a bootloop. Then I had to use the oreo ROM from this forum and flashed it using SP Flash tool. It was a successfull flash. Then I used Maui META to write the IMEI for both sim. That was successfull too(Wifi and bluetooth addresses were working by themselves and i didnt write the serial number of the phone).
After working nicely for three days, i was using Whatsapp and a friend of mine sent me a .pptx file (powerpoint presentation). I opened it using WPS office app. I opened it multiple times in morning with no problems. But in the afternoon at about 2.53 PM while i was in my car, i was unable to open the file. The phone hanged. It heated up. To get out of the hang, i restarted the phone using the power button. IT DID NOT START. All it showed was the lenovo logo screen. And after doing more restarts, the phone went completely blank.
Now i cannot start it, or charge it. So i thought of flashing it again. But when i connect it to my PC, it keeps CONNECTING and DISCONNECTING. what i saw in the device manager was that the driver keeps changing very fast betwee MTK USB PORT and PRELOADER.
I found the solution to be updating the drivers manually. I did. Now the driver shows only DA USB VCOM and when it changes, it goes invisible in the PC and then appears back. Now when i start flashing, the first red progress bar appears as: Download DA 100%. and the flash hangs. After some time, this error will popup: ERROR: STATUS_UNKNOWN_STORAGE_TYPE (0xC0040009)
Please someone help me.
Click to expand...
Click to collapse
I couldn't find more about the problem online, can you please upload a screenshot of the error. Try using the latest version of SP Flash Tool and see if the problem persists
I have lost all my mind and need serious help.
here are the screenshots. Note that the battery is in the phone always because i am unable to open the back cover. During the flashing process, i did not press the vol - button.
https://ibb.co/sq8knnj
https://ibb.co/VjqKQm3
https://ibb.co/4VkVPjs
https://ibb.co/cw2BzLC
https://ibb.co/kcjjJ74
Now in the following screenshots, i kept the vol - button pressed down. Note that the driver is stuck at preloader and not DA. Also the first bar is yellow color in both these cases. However, in the above situation, multiple files were flashed. But in this below situation, only this so called "flash" was done; that too unsucessful in the end.
https://ibb.co/1QKtsCb
https://ibb.co/Ssj58Zd
custom619 said:
here are the screenshots. Note that the battery is in the phone always because i am unable to open the back cover. During the flashing process, i did not press the vol - button.
https://ibb.co/sq8knnj
https://ibb.co/VjqKQm3
https://ibb.co/4VkVPjs
https://ibb.co/cw2BzLC
https://ibb.co/kcjjJ74
Now in the following screenshots, i kept the vol - button pressed down. Note that the driver is stuck at preloader and not DA. Also the first bar is yellow color in both these cases. However, in the above situation, multiple files were flashed. But in this below situation, only this so called "flash" was done; that too unsucessful in the end.
https://ibb.co/1QKtsCb
https://ibb.co/Ssj58Zd
Click to expand...
Click to collapse
The problem may be with your drivers, i see you have Preloader drivers only.
Follow this guide for installing drivers - https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Anas Rahman said:
The problem may be with your drivers, i see you have Preloader drivers only.
Follow this guide for installing drivers - https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
So i did as you said brother. I don' t know how but something happened. The phone, after a long time actually displayed up. It showed the LENOVO logo and down in the corner two things came in written :
>device unlocked
>Tool DL image Fail
I googled it up and found that it requires to flash the phone with the DA DL option ticked. I did that but it does not flash. The error is same as follows:
https://ibb.co/Ssj58Zd
Can you please guide me in the flashing process? I think the mistake is very small but i don't know where i am missing.
I have lost all my mind and need serious help.
custom619 said:
So i did as you said brother. I don' t know how but something happened. The phone, after a long time actually displayed up. It showed the LENOVO logo and down in the corner two things came in written :
>device unlocked
>Tool DL image Fail
I googled it up and found that it requires to flash the phone with the DA DL option ticked. I did that but it does not flash. The error is same as follows:
https://ibb.co/Ssj58Zd
Can you please guide me in the flashing process? I think the mistake is very small but i don't know where i am missing.
Click to expand...
Click to collapse
Okay so what i figured out is that in this state: (battery plugged in, no notification LED response, no response on power or volume buttons) the driver you require is MTK USB PORT.
I updated to this driver manually, and guess what? the phone actually flashed. But three files remained and the process hanged. (system, cache and userdata)
Now i get the errors:
>device unlocked
>Tool DL image Fail
and sometimes: >device otp failed
I am trying to flash the rest three files individually. Lets see what happens.
custom619 said:
Okay so what i figured out is that in this state: (battery plugged in, no notification LED response, no response on power or volume buttons) the driver you require is MTK USB PORT.
I updated to this driver manually, and guess what? the phone actually flashed. But three files remained and the process hanged. (system, cache and userdata)
Now i get the errors:
>device unlocked
>Tool DL image Fail
and sometimes: >device otp failed
I am trying to flash the rest three files individually. Lets see what happens.
Click to expand...
Click to collapse
Try flashing wihtout these three files, then boot to fastboot mode by pressing POWER+VOL UP and choose fastboot mode then flash these three files with fastboot commamds
Anas Rahman said:
Try flashing wihtout these three files, then boot to fastboot mode by pressing POWER+VOL UP and choose fastboot mode then flash these three files with fastboot commamds
Click to expand...
Click to collapse
I.AM.DUMBFOUNDED.
During flashing this error occurred:
(yellow bar in SPFlash tool)
[recovery] Download Flash 100%
ERROR: STATUS_MMC_ERR (0xC0040030)
[HINT]:
custom619 said:
I.AM.DUMBFOUNDED.
During flashing this error occurred:
(yellow bar in SPFlash tool)
[recovery] Download Flash 100%
ERROR: STATUS_MMC_ERR (0xC0040030)
[HINT]:
Click to expand...
Click to collapse
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Anas Rahman said:
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Click to expand...
Click to collapse
I Already tried this thread you suggested. No outcome.
Anas Rahman said:
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Click to expand...
Click to collapse
This group is possibly dead. No one has responded till today...
Hello, i have bricked my phone after an hurupdate, i dont know why but the phone have suddenly turn off during twrp hurupdater process and now i can't turn on the phone, i can plug in my pc & he recognize him as "fastboot devices" but when i try to flash something or unbrick via multi tool nothing happen (FAILED (remote: Command not allowed))
I can't do anything now.. Please help me !
Albanheraibi said:
Hello, i have bricked my phone after an hurupdate, i dont know why but the phone have suddenly turn off during twrp hurupdater process and now i can't turn on the phone, i can plug in my pc & he recognize him as "fastboot devices" but when i try to flash something or unbrick via multi tool nothing happen (FAILED (remote: Command not allowed))
I can't do anything now.. Please help me !
Click to expand...
Click to collapse
Erecovery has started working for some people. you can try that
mrmazak said:
Erecovery has started working for some people. you can try that
Click to expand...
Click to collapse
Nope .. nothing work ..
Anyone know how to unbrick ? ..
I think i have flashed the wrong update, i have bndl21 & i have flashed the bndl22 or bndal10, my phone is dead ?
Albanheraibi said:
I think i have flashed the wrong update, i have bndl21 & i have flashed the bndl22 or bndal10, my phone is dead ?
Click to expand...
Click to collapse
Shouldn't be, at least not from that, not completely.
Was this the first condition, or an added problem?
I think best thing to try is the service ROM.
This one is BND-L21C432..
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.. If this is not the correct version for your honor 7x
Now with dc phoenix i have restore the fastboot and the erecovery, i can flash all i want but nothing happens, just boot loop at "your phone is not trusted" screen.
I was on catuva's rom before brick and now i have the catuva splashboot screen even after full firmware retore by dc phoenix.
When i try to flash in twrp i see lot of errors related to partition table (invalid argument cust, odm, sytsem etc) it seems the partition table have a problem..
The DLOAD can restore this ?
When i try to restore via dload it stuck at 5% and it says "software install failed!" ..
Someone Help me ?..
Albanheraibi said:
When i try to restore via dload it stuck at 5% and it says "software install failed!" ..
Someone Help me ?..
Click to expand...
Click to collapse
You got failed using the "service-rom" dload?
This one is Oreo I believe. There is a nougat one also.
mrmazak said:
You got failed using the "service-rom" dload?
This one is Oreo I believe. There is a nougat one also.
Click to expand...
Click to collapse
Yes stuck at 5%..
i have try to flash the Honor 7X-Elemental V1(8.X-GPU) and i get an error at the end of process >
mount: failed to mount
/dev/block/platform/hi_mci.0/by-name/system at /system: invalid argument
What i am supposed to do with this error ?
Albanheraibi said:
Yes stuck at 5%..
i have try to flash the Honor 7X-Elemental V1(8.X-GPU) and i get an error at the end of process >
mount: failed to mount
/dev/block/platform/hi_mci.0/by-name/system at /system: invalid argument
What i am supposed to do with this error ?
Click to expand...
Click to collapse
Says in the install guide for it, you must be running at newest security patch in order to install elemental.
Please focus on one thing. Getting phone to boot full stock first before trying other rom. You are going to hard brck your phon if you keep doing flashes when the stock fails to install
mrmazak said:
Says in the install guide for it, you must be running at newest security patch in order to install elemental.
Please focus on one thing. Getting phone to boot full stock first before trying other rom. You are going to hard brck your phon if you keep doing flashes when the stock fails to install
Click to expand...
Click to collapse
When i try to rollback emui5 via twrp with your guide i have this error :
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update pakage from zip failed
E : unknown command [errno]
Updater process ended with ERROR : 9
Error installing zip file '/external_sd/HWOTA8/update.zip'
i remember that the phone has started to bootloop just after twrp flashed the wrong radio file..
This is the end ?
Albanheraibi said:
When i try to rollback emui5 via twrp with your guide i have this error :
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update pakage from zip failed
E : unknown command [errno]
Updater process ended with ERROR : 9
Error installing zip file '/external_sd/HWOTA8/update.zip'
i remember that the phone has started to bootloop just after twrp flashed the wrong radio file..
This is the end ?
Click to expand...
Click to collapse
I am not understanding how you say you follow my guide, then post the error.
This error shows you are trying to install ota update with TWRP.
My guide sets you to install ota update file with a modified stock recovery (no-check).
If you are having trouble because of bad translation, please do not assume what you need to do and wait for proper help and translation
mrmazak said:
I am not understanding how you say you follow my guide, then post the error.
This error shows you are trying to install ota update with TWRP.
My guide sets you to install ota update file with a modified stock recovery (no-check).
If you are having trouble because of bad translation, please do not assume what you need to do and wait for proper help and translation
Click to expand...
Click to collapse
Ok after update with hurupdater via twrp (he flashed the correct radio.img file) the phone have income from death !
Thank you for trying to help me !
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
tnsmani said:
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
Click to expand...
Click to collapse
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
EpicLawR said:
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
Click to expand...
Click to collapse
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
tnsmani said:
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
Click to expand...
Click to collapse
My device was detected as a 9008 by my computer, but by the tool it was detected as a com device. driver signature vertification was disabled when trying the tool multiple times, but i can try to use it on another computer.
Sideloading the OOS rom didn't work the first time i tried it, but i am not very familiar with that so i can try that again aswell.
Thanks.
EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Try to flash stock recovery if succeeded then wipe complete, after twrp with root and then install stock oos
Msmdownload is low level format tool, another method of flashing won't work if it isn't.
Since you said that msm reported succeed but after it you still got a hash fail, it's either you flash the wrong file or a you've got a bad emmc..
You can't easily brick a Oneplus device. At worst you've screwed up your options for self-contained flashing via twrp. The two most common issues restoring to stock via sdk tools on a PC are i) wrong drivers being used, make sure you've installed the oneplus drivers on your computer and the device is recognised properly; and ii) you don't have full admin rights - make sure you've run the CMD shell as administrator before you execute any of the sdk commands.
hello
1.do u unlocked your bootloader?
2.connect your phone to PC into bootloader, if you can... try these codes with fastboot
fastboot erase cache
then
fastboot flash recovery ***.img
then
fastboot boot ***.img
then you should see you recovery....
before flashing ROM go to mount and mount system,recovery and data
then flash ROM
I have been trying to install custom ROM in realme 6 pro. I followed a youtube tutorial and installed TWRP. Now when I try to wipe the system, it gives the error "unable to mount '/system_root' (invalid argument) and unable to mount '/vendor' (invalid argument)". I tried changing the system format from ext4 to ext2 and even used decryption zips. Nothing works. I can't even get the stock Recovery back to return to built-in ROM. I tried using the orange fox recovery but still got the same error. When I try to wipe using fastboot, it gives the error: "FAILED (remote: Check device console.)". Can someone please help?
stag7824 said:
I have been trying to install custom ROM in realme 6 pro. I followed a youtube tutorial and installed TWRP. Now when I try to wipe the system, it gives the error "unable to mount '/system_root' (invalid argument) and unable to mount '/vendor' (invalid argument)". I tried changing the system format from ext4 to ext2 and even used decryption zips. Nothing works. I can't even get the stock Recovery back to return to built-in ROM. I tried using the orange fox recovery but still got the same error. When I try to wipe using fastboot, it gives the error: "FAILED (remote: Check device console.)". Can someone please help?
Click to expand...
Click to collapse
Maybe same my device problem pls help me..
You will need to reinstall/flash the stock rom.
Then :
1)I flash TWRP with ADB/Fastboot
(2) boot into twrp recovery
(3) reboot to bootloader
(4) ADB/fastboot to flash Disable DM Varity file
(5) reboot into TWRP
(6) wipe/Format Data
(7) rebooted into recovery
(8) Advance/Fix AVB
(9) installed Magisk
(10) reboot to system
Then you will have the stock rom and have root control to debloat which will greatly improve battery usage time and unlike most custom rom everything will still be working.
IMHO using magisk with exposed module gravitybox for its custom features is smoother and quicker than any of the custom roms at this time.
beaker2 said:
You will need to reinstall/flash the stock rom.
Then :
1)I flash TWRP with ADB/Fastboot
(2) boot into twrp recovery
(3) reboot to bootloader
(4) ADB/fastboot to flash Disable DM Varity file
(5) reboot into TWRP
(6) wipe/Format Data
(7) rebooted into recovery
(8) Advance/Fix AVB
(9) installed Magisk
(10) reboot to system
Then you will have the stock rom and have root control to debloat which will greatly improve battery usage time and unlike most custom rom everything will still be working.
IMHO using magisk with exposed module gravitybox for its custom features is smoother and quicker than any of the custom roms at this time.
Click to expand...
Click to collapse
I already tried reinstalling the stock ROM using TWRP and orange fox. But I am getting the same error. Can you please guide me how should I go about it?
stag7824 said:
I already tried reinstalling the stock ROM using TWRP and orange fox. But I am getting the same error. Can you please guide me how should I go about it?
Click to expand...
Click to collapse
You need to use the Real Me Flash tool v1.1.3
[Tool] RFT - REALME Flash Tool to flash stock ROM (For Unlocked Bootloader)
REALME FLASHTOOLS V 1.1.3 This tool can make you easier to install stock roms, Rollback, Downgrade This program is made for Windows, with .NET Framework 4.5.1 This is VB.net program What the tool can do: - Flash phone - For now the tool...
forum.xda-developers.com
oxbowlarry said:
You need to use the Real Me Flash tool v1.1.3
[Tool] RFT - REALME Flash Tool to flash stock ROM (For Unlocked Bootloader)
REALME FLASHTOOLS V 1.1.3 This tool can make you easier to install stock roms, Rollback, Downgrade This program is made for Windows, with .NET Framework 4.5.1 This is VB.net program What the tool can do: - Flash phone - For now the tool...
forum.xda-developers.com
Click to expand...
Click to collapse
I have tried it already, it did not work
oxbowlarry said:
You need to use the Real Me Flash tool v1.1.3
[Tool] RFT - REALME Flash Tool to flash stock ROM (For Unlocked Bootloader)
REALME FLASHTOOLS V 1.1.3 This tool can make you easier to install stock roms, Rollback, Downgrade This program is made for Windows, with .NET Framework 4.5.1 This is VB.net program What the tool can do: - Flash phone - For now the tool...
forum.xda-developers.com
Click to expand...
Click to collapse
The mobile screen is stuck at realme logo, and the software keeps on waiting. How should I resolve this? Please help
stag7824 said:
The mobile screen is stuck at realme logo, and the software keeps on waiting. How should I resolve this? Please help
Click to expand...
Click to collapse
If it is stuck in a bootloop then press and hold the power button and the volume + (not volume- like to go into fastboot) hold the buttons until the phone shuts off , logo goes away. Reboot to bootloader/fastboot then plug it into the computer running the Realme Flash tool. Also make sure you have the device drivers are installed on the computer. Then wait and give it plenty of time it takes awhile and you will feel that it is stuck at several points but just be patient and let it run.
oxbowlarry said:
If it is stuck in a bootloop then press and hold the power button and the volume + (not volume- like to go into fastboot) hold the buttons until the phone shuts off , logo goes away. Reboot to bootloader/fastboot then plug it into the computer running the Realme Flash tool. Also make sure you have the device drivers are installed on the computer. Then wait and give it plenty of time it takes awhile and you will feel that it is stuck at several points but just be patient and let it run.
Click to expand...
Click to collapse
It worked! Thanks a lot. You are life savior
oxbowlarry said:
If it is stuck in a bootloop then press and hold the power button and the volume + (not volume- like to go into fastboot) hold the buttons until the phone shuts off , logo goes away. Reboot to bootloader/fastboot then plug it into the computer running the Realme Flash tool. Also make sure you have the device drivers are installed on the computer. Then wait and give it plenty of time it takes awhile and you will feel that it is stuck at several points but just be patient and let it run.
Click to expand...
Click to collapse
very precise, best instruction and advice ever!