the internal storage is corrupted - Honor 5C Questions & Answers

hi my phone is hard breaked
i cant flash rom after flash stuck on huawei boot logo
i flashed b130 but after reset factory stock on black screen
i restore twrp back up b130 but the internal storage is corrupted i cant created folder,copy and download file and take screen plz help me

Fardinjal said:
hi my phone is hard breaked
i cant flash rom after flash stuck on huawei boot logo
i flashed b130 but after reset factory stock on black screen
i restore twrp back up b130 but the internal storage is corrupted i cant created folder,copy and download file and take screen plz help me
Click to expand...
Click to collapse
what the **** are you talking about?
---------- Post added at 11:12 AM ---------- Previous post was at 11:11 AM ----------
Fardinjal said:
hi my phone is hard breaked
i cant flash rom after flash stuck on huawei boot logo
i flashed b130 but after reset factory stock on black screen
i restore twrp back up b130 but the internal storage is corrupted i cant created folder,copy and download file and take screen plz help me
Click to expand...
Click to collapse
Okay, what firmware are you actually right now?

scuzzy1337 said:
what the **** are you talking about?
---------- post added at 11:12 am ---------- previous post was at 11:11 am ----------
okay, what firmware are you actually right now?
Click to expand...
Click to collapse
nmo-l31c185b171

Fardinjal said:
nmo-l31c185b171
Click to expand...
Click to collapse
Are you african? Sorry really, because this firmware is african.

How to fixed?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

SCUZZY1337 said:
what the **** are you talking about?
---------- Post added at 11:12 AM ---------- Previous post was at 11:11 AM ----------
Okay, what firmware are you actually right now?
Click to expand...
Click to collapse
SCUZZY1337 said:
Are you african? Sorry really, because this firmware is african.
Click to expand...
Click to collapse
no im from qatar this frimware is Middle East

Fardinjal said:
How to fixed?
Click to expand...
Click to collapse
Omfg, do you have TWRP?

SCUZZY1337 said:
Omfg, do you have TWRP?
Click to expand...
Click to collapse
yes

Fardinjal said:
yes
Click to expand...
Click to collapse
Uhmmm, you have to flash custom ROM, sooo, i found one for you:
First of all, you have to flash Update.zip:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v81105/f1/full/update.zip
Then, you have to flash at the second time this:
http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_NMO-L31_hw_meafnaf.zip
But before you flash, wipe the Internal Storage, System, Data.
And you're all set!

tnx i go to test

Fardinjal said:
tnx i go to test
Click to expand...
Click to collapse
Soooo, how is it going???
---------- Post added at 11:57 AM ---------- Previous post was at 11:56 AM ----------
Fardinjal said:
tnx i go to test
Click to expand...
Click to collapse
And d00d, this is not a hard-brick, that's soft-brick xD

Hi my YU Yuphoria 5010 started acting up since last week ,when i noticed that the phone was restarting randomly and the settings was missing and even if i clicked on the settings logo in the notification panel, nothing would happen .So i decided to flash a Cusstom ROM instead and boot into recovery.While trying to wipe cache,dalvik and data I got an error message "uable to mount data,cache ,system(invalid argument) and internal memory* was showing up as 0.So i thought my phone was bricked and tried reviving it with the sd card method.But everything else except for system flashed , and got an error FAILED (remote: flash write failure ) just for system .Anyway now I could boot into recovery using fastboot boot command and the internal memory started showing up correcty. The fastboot command is the only way i could get into recovery, if i try power+volume down it would just come up with the empty battery logo. After this i installed qualcomm drivers and manually changed the driver to Qualcomm HS-USB QD Loader 9008 and tried flashing through QFil with a flashable stock ROM and ended up with the error message:"Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol** at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)** at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail".
But after going through some of the posts I found that my phone might not be bricked in the first place.My device just shows up as 'Android' under Other devices in Device Manager.
The following are the details from device manager.
Device type: Other devices
Manufacturer: Unknown
Location Port_#002.Hub_#003
Problem code : 0000001C
Physical Device Object name: \Device\USBPDO-6
Hardware IDS: USB\VID_2A96&PID_300A&REV_0100
USB\VID_2A96&PID_300A
{259abffc-50a7-47ce-af08-68c9a7d73366}[13]: 6.0
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[4]: <true>
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[6]: <true>
I also tried to restore through TWRP recovery using the back up my brother created on his YU 5010A to no success.Changing the file system type and back to ext4 also didnt help. I use a Windows 10 64bit Laptop.
What could I possibly do to revive my phone?Kindly help.

maverickmacca said:
Hi my YU Yuphoria 5010 started acting up since last week ,when i noticed that the phone was restarting randomly and the settings was missing and even if i clicked on the settings logo in the notification panel, nothing would happen .So i decided to flash a Cusstom ROM instead and boot into recovery.While trying to wipe cache,dalvik and data I got an error message "uable to mount data,cache ,system(invalid argument) and internal memory* was showing up as 0.So i thought my phone was bricked and tried reviving it with the sd card method.But everything else except for system flashed , and got an error FAILED (remote: flash write failure ) just for system .Anyway now I could boot into recovery using fastboot boot command and the internal memory started showing up correcty. The fastboot command is the only way i could get into recovery, if i try power+volume down it would just come up with the empty battery logo. After this i installed qualcomm drivers and manually changed the driver to Qualcomm HS-USB QD Loader 9008 and tried flashing through QFil with a flashable stock ROM and ended up with the error message:"Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol** at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)** at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail".
But after going through some of the posts I found that my phone might not be bricked in the first place.My device just shows up as 'Android' under Other devices in Device Manager.
The following are the details from device manager.
Device type: Other devices
Manufacturer: Unknown
Location Port_#002.Hub_#003
Problem code : 0000001C
Physical Device Object name: \Device\USBPDO-6
Hardware IDS: USB\VID_2A96&PID_300A&REV_0100
USB\VID_2A96&PID_300A
{259abffc-50a7-47ce-af08-68c9a7d73366}[13]: 6.0
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[4]: <true>
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[6]: <true>
I also tried to restore through TWRP recovery using the back up my brother created on his YU 5010A to no success.Changing the file system type and back to ext4 also didnt help. I use a Windows 10 64bit Laptop.
What could I possibly do to revive my phone?Kindly help.
Click to expand...
Click to collapse
Go create a new thread of your problem, thank you.
---------- Post added at 02:28 PM ---------- Previous post was at 02:23 PM ----------
Fardinjal most be probably bricked his phone again, shiiit xd

maverickmacca said:
Hi my YU Yuphoria 5010 started acting up since last week ,when i noticed that the phone was restarting randomly and the settings was missing and even if i clicked on the settings logo in the notification panel, nothing would happen .So i decided to flash a Cusstom ROM instead and boot into recovery.While trying to wipe cache,dalvik and data I got an error message "uable to mount data,cache ,system(invalid argument) and internal memory* was showing up as 0.So i thought my phone was bricked and tried reviving it with the sd card method.But everything else except for system flashed , and got an error FAILED (remote: flash write failure ) just for system .Anyway now I could boot into recovery using fastboot boot command and the internal memory started showing up correcty. The fastboot command is the only way i could get into recovery, if i try power+volume down it would just come up with the empty battery logo. After this i installed qualcomm drivers and manually changed the driver to Qualcomm HS-USB QD Loader 9008 and tried flashing through QFil with a flashable stock ROM and ended up with the error message:"Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol** at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)** at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail".
But after going through some of the posts I found that my phone might not be bricked in the first place.My device just shows up as 'Android' under Other devices in Device Manager.
The following are the details from device manager.
Device type: Other devices
Manufacturer: Unknown
Location Port_#002.Hub_#003
Problem code : 0000001C
Physical Device Object name: \Device\USBPDO-6
Hardware IDS: USB\VID_2A96&PID_300A&REV_0100
USB\VID_2A96&PID_300A
{259abffc-50a7-47ce-af08-68c9a7d73366}[13]: 6.0
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[4]: <true>
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[6]: <true>
I also tried to restore through TWRP recovery using the back up my brother created on his YU 5010A to no success.Changing the file system type and back to ext4 also didnt help. I use a Windows 10 64bit Laptop.
What could I possibly do to revive my phone?Kindly help.
Click to expand...
Click to collapse
You can bring it to a service center. Please don't post it here. This is a subforum for Honor, not Yuphoria.
Sent from my Honor 8 using XDA Labs

maverickmacca said:
Hi my YU Yuphoria 5010 started acting up since last week ,when i noticed that the phone was restarting randomly and the settings was missing and even if i clicked on the settings logo in the notification panel, nothing would happen .So i decided to flash a Cusstom ROM instead and boot into recovery.While trying to wipe cache,dalvik and data I got an error message "uable to mount data,cache ,system(invalid argument) and internal memory* was showing up as 0.So i thought my phone was bricked and tried reviving it with the sd card method.But everything else except for system flashed , and got an error FAILED (remote: flash write failure ) just for system .Anyway now I could boot into recovery using fastboot boot command and the internal memory started showing up correcty. The fastboot command is the only way i could get into recovery, if i try power+volume down it would just come up with the empty battery logo. After this i installed qualcomm drivers and manually changed the driver to Qualcomm HS-USB QD Loader 9008 and tried flashing through QFil with a flashable stock ROM and ended up with the error message:"Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol** at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)** at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail".
But after going through some of the posts I found that my phone might not be bricked in the first place.My device just shows up as 'Android' under Other devices in Device Manager.
The following are the details from device manager.
Device type: Other devices
Manufacturer: Unknown
Location Port_#002.Hub_#003
Problem code : 0000001C
Physical Device Object name: \Device\USBPDO-6
Hardware IDS: USB\VID_2A96&PID_300A&REV_0100
USB\VID_2A96&PID_300A
{259abffc-50a7-47ce-af08-68c9a7d73366}[13]: 6.0
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[4]: <true>
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[6]: <true>
I also tried to restore through TWRP recovery using the back up my brother created on his YU 5010A to no success.Changing the file system type and back to ext4 also didnt help. I use a Windows 10 64bit Laptop.
What could I possibly do to revive my phone?Kindly help.
Click to expand...
Click to collapse
Yuphoria has a separate forum . Kindly post the issue there

SCUZZY1337 said:
Soooo, how is it going???
---------- Post added at 11:57 AM ---------- Previous post was at 11:56 AM ----------
And d00d, this is not a hard-brick, that's soft-brick xD
Click to expand...
Click to collapse
no this is hard brick because i cant flash any ram and any build number just can use twrp backup

Fardinjal said:
no this is hard brick because i cant flash any ram and any build number just can use twrp backup
Click to expand...
Click to collapse
This is soft brick, not a hard brick, because when you get a hard brick it means you can't do nothing anymore...

Fardinjal said:
no this is hard brick because i cant flash any ram and any build number just can use twrp backup
Click to expand...
Click to collapse
Do you need any help still bro? )

Haha , great that this guy is in a position to help all . Key going bro :highfive:

gopinaidu77 said:
Haha , great that this guy is in a position to help all . Key going bro :highfive:
Click to expand...
Click to collapse
No problem, because i see that XDA community is friendly, and it's interesting to help all, when you know how :highfive:

Related

[HELP] MemoPad 7 (176CX) stuck after OTA

Hello,
A fellow colleauge of mine had a MemoPad 7 (176CX) which received an OTA update last week. After the installation the tablet restarted and then a dead droid appeared on the screen with an error message "no command found" then the device restarts automatically and everything starts again (dead droid - no command - reboot - dead droid...). So, it's in a boot loop. (As far as I know the device was rooted and he made a mistake to no un-root before the OTA update but it's irrelevant now)
As he asked for help I checked the XDA forums and found that my idea about reinstalling the factory default firmware should solve the problem. But I'm a little bit afraid of the continous boot loop. How will be able to reflash the firmware when the device keeps rebooting?
Any advice will be helpful.
Thanks in advance.
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:19 PM ---------- Previous post was at 01:19 PM ----------
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
Sorry for the double post.
---------- Post added at 01:22 PM ---------- Previous post was at 01:22 PM ----------
Sorry for the double post.
Hello,
Thanks for the reply. Unfortunatelly the issue seems to be a little bit more complicated.
So, things I checked:
- boot into droidboot with Vol+ + Power - works well, able to boot into droidboot. But see this strange notice in the bottom:
FASTBOOT INIT....
e:Failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
continue fastboot process
E:installer device ignored
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
Now, I can select Reboot Droidboot - no luck
Reboot - no luck
Recovery - reboot into bootloop
Power off - yeah, it works and turns of the device.
If I try to boot into Fastboot with Vol - + Powoer receive the dead droid with the No command message.
Any idea where can I go forward?
Nandr0idC0nsumer said:
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:19 PM ---------- Previous post was at 01:19 PM ----------
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
Sorry for the double post.
---------- Post added at 01:22 PM ---------- Previous post was at 01:22 PM ----------
Sorry for the double post.
Click to expand...
Click to collapse
waces said:
Hello,
Thanks for the reply. Unfortunatelly the issue seems to be a little bit more complicated.
So, things I checked:
- boot into droidboot with Vol+ + Power - works well, able to boot into droidboot. But see this strange notice in the bottom:
FASTBOOT INIT....
e:Failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
continue fastboot process
E:installer device ignored
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
Now, I can select Reboot Droidboot - no luck
Reboot - no luck
Recovery - reboot into bootloop
Power off - yeah, it works and turns of the device.
If I try to boot into Fastboot with Vol - + Powoer receive the dead droid with the No command message.
Any idea where can I go forward?
Click to expand...
Click to collapse
X2 With the OTA missing partition. Seemed like a straight forward update but completely screwed up my tablet. SOL for the moment. I imagine this post will become popular very quick.
Try the following:
Boot into DROIDBOOT
Download & Install Android Studio
Go into a cmd and type "fastboot devices"
If it shows a device, than:
Use a temp CWM session to flash 182.
Hello,
Nope, in Droidboot the PC cannot see and connect any device.
fastboot devices - return with empty line
fastboot getvar - return with <waiting for device>
minor correcftion. was able to access the device with fastboot devices and it shows the connected device as well. i followed the steps described here : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466 but no luck. what did i missed?
waces said:
minor correcftion. was able to access the device with fastboot devices and it shows the connected device as well. i followed the steps described here : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466 but no luck. what did i missed?
Click to expand...
Click to collapse
Fastboot? AWESOME! You're covered, Jimmy. (If you didn't have access to fastboot, you would be six callers ahead of us...)
Download this temp CWM:
https://www.androidfilehost.com/?fid=23991606952604606
open the batch file (with droidboot open on the tablet, and tethered to the pc), and type "ACCEPT". Now, type "T4", and click enter, and a temporary CWM session should open.
Now, (you'll need a external SD card), flash this file:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
And you should be on KitKat... and take OTAs from there to get to lollipop. Use the same temp CWM and flash SuperSU to get root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 01:50 PM ---------- Previous post was at 01:17 PM ----------
Just wondering... did you end up fixing the device? You don't seem to be very active on this fourm.
Nandr0idC0nsumer said:
Fastboot? AWESOME! You're covered, Jimmy. (If you didn't have access to fastboot, you would be six callers ahead of us...)
Download this temp CWM:
open the batch file (with droidboot open on the tablet, and tethered to the pc), and type "ACCEPT". Now, type "T4", and click enter, and a temporary CWM session should open.
Now, (you'll need a external SD card), flash this file:
And you should be on KitKat... and take OTAs from there to get to lollipop. Use the same temp CWM and flash SuperSU to get root.
Click to expand...
Click to collapse
Wondering if you could help me for a sec... I followed what you have here and all works fine but the sd card won't mount, I've formatted with both file systems but no. I'm very new but learning, what did I miss?
jakeco2u said:
Wondering if you could help me for a sec... I followed what you have here and all works fine but the sd card won't mount, I've formatted with both file systems but no. I'm very new but learning, what did I miss?
Click to expand...
Click to collapse
Tell me the exact steps you took.
Did you take the OTAs to Lollipop?
Nandr0idC0nsumer said:
Tell me the exact steps you took.
Did you take the OTAs to Lollipop?
Click to expand...
Click to collapse
Yes, was rooted, OTA to Lollipop and tablet stuck in bootloop. I followed your post and was not able to install your link but had success with WW_V12.10.1.17. The tablet stated it had been installed so I went back and reboot but its still stuck in the bootloop. Hope that makes sense.
Like I said, I'm new to working on these so be nice. Should I install firmware and source code from the Asus website?
jakeco2u said:
Yes, was rooted, OTA to Lollipop and tablet stuck in bootloop. I followed your post and was not able to install your link but had success with WW_V12.10.1.17. The tablet stated it had been installed so I went back and reboot but its still stuck in the bootloop. Hope that makes sense.
Like I said, I'm new to working on these so be nice. Should I install firmware and source code from the Asus website?
Click to expand...
Click to collapse
Did you factory reset after installing the WW_V12.10.1.17 ROM?
Nandr0idC0nsumer said:
Did you factory reset after installing the WW_V12.10.1.17 ROM?
Click to expand...
Click to collapse
I did, back to bootloop.
jakeco2u said:
I did, back to bootloop.
Click to expand...
Click to collapse
Did the Lollipop OTA finish? (As in, did you see all the BIOS updating text?)
Nandr0idC0nsumer said:
Did the Lollipop OTA finish? (As in, did you see all the BIOS updating text?)
Click to expand...
Click to collapse
I'm not sure if the bios updated (I assume we are talking about the first OTA round before the problem). It had finished the download, the droid was shown for a bit, and when I came back after about 1/2 hr. to check on it the 'Asus powered by Android' screen kept cycling about every minute. I didn't see bios updating text. BTW thank for the help...
And as the OP stated in fastboot i get:
E:installer device ignored
continue the fastboot process
E:failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
jakeco2u said:
I'm not sure if the bios updated (I assume we are talking about the first OTA round before the problem). It had finished the download, the droid was shown for a bit, and when I came back after about 1/2 hr. to check on it the 'Asus powered by Android' screen kept cycling about every minute. I didn't see bios updating text. BTW thank for the help...
And as the OP stated in fastboot i get:
E:installer device ignored
continue the fastboot process
E:failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
Click to expand...
Click to collapse
Try downloading each ROM from the OP, and flashing them in order.
Nandr0idC0nsumer said:
Try downloading each ROM from the OP, and flashing them in order.
Click to expand...
Click to collapse
Sorry, which ROMs? Are we talking about the firmware and kernels from the Asus website? I'm not seeing any ROMs in this post except the one you posted and the Asus one. And again, thanks for taking the time...
jakeco2u said:
Sorry, which ROMs? Are we talking about the firmware and kernels from the Asus website? I'm not seeing any ROMs in this post except the one you posted and the Asus one. And again, thanks for taking the time...
Click to expand...
Click to collapse
Sorry, didn't make what to download clear enough.
ME176C/X K013 ROMS AND UPDATES:
WW .182 ROM
http://dlcdnet.asus.com/pub/ASUS/Eee...3_2_23_182.zip
WW OTA 191
http://fota.asus.com/delta_package/e...104/update.zip
https://drive.google.com/file/d/0B5G...ew?usp=sharing
http://www26.zippyshare.com/v/49210353/file.html
WW OTA 198
http://www21.zippyshare.com/v/f1NwNFH5/file.html
WW OTA 199
http://www.mediafire.com/download/ec...c8j/update.zip
WW OTA 201
http://www48.zippyshare.com/v/PtRl8YI9/file.html
WW Lollipop release
http://www.mediafire.com/download/2v...1/lollipop.zip
download each one of those (sorry, lots of downloads lol) and flash them each in order using a temp CWM. then do a factory reset and reboot.
EDIT: some links are down. I'm assuming you already have the 182 ROM.
Flash the 182 ROM, and then flash all the updates you can download in order.
Nandr0idC0nsumer said:
Sorry, didn't make what to download clear enough.
ME176C/X K013 ROMS AND UPDATES:
WW .182 ROM
http://dlcdnet.asus.com/pub/ASUS/Eee...3_2_23_182.zip
WW OTA 191
http://fota.asus.com/delta_package/e...104/update.zip
https://drive.google.com/file/d/0B5G...ew?usp=sharing
http://www26.zippyshare.com/v/49210353/file.html
WW OTA 198
http://www21.zippyshare.com/v/f1NwNFH5/file.html
WW OTA 199
http://www.mediafire.com/download/ec...c8j/update.zip
WW OTA 201
http://www48.zippyshare.com/v/PtRl8YI9/file.html
WW Lollipop release
http://www.mediafire.com/download/2v...1/lollipop.zip
download each one of those (sorry, lots of downloads lol) and flash them each in order using a temp CWM. then do a factory reset and reboot.
Click to expand...
Click to collapse
OK, I tried to download these links most are dead and the three that did download came up as errors when attempting to flash them.
I'm going to try and explain the best I can with pictures as I can only assume I'm doing something wrong.
This is what I get when I go into fastboot, or droidboot or whatever.
OK, I install update from Asus website(as its the only file that hasn't caused an error.
After the install...
Wipe data...
Reboot... I don't know why it asks for root on reboot???
Then starts bootloop...
Any thoughts? Or should I just toss it.. It seems there has to be a way but it's beyond my skill set. Thanks again for the help.

Unbrick P9 single sim (using DC Phoenix)

There are many cases of people recovering their bricked phones but their solutions arent so clear when browsing the thread. For example, threads get abandoned once their phone was recovered, leaving people like me confused or stranded. I decided after days of trying to recover my phone share what I did to revive my P9. I hope this can help you.
Disclaimer***
- DC Phoenix costs 15 euros for 15 credits to use for 72h after initial flash (small price to pay compared to sending to repair shop or having a useless brick).
- i am NOT responsible for what you do to your phone if it broke
- this is what worked for ME, but im confident it would work for yours but no guarantees
- please read as it might give you some background information
- Bootloader code changes
- serial number resets to ABCDEF012345678
As most people on XDA, we like to flash stuff on to our phones. I was on EMUI 4.1 MM and I wanted to update to EMUI 5 Nougat. I did so successfully by installing twrp, flashing C432 oem info, and flashing B136 via SD card force update, and then using software update in the settings app to B182. Finally, I managed to flash B361 nougat via HuaweiUpdater2.0 and HiSuite.
Then, I decided to try and root my P9 but somewhere along the way, which I cant remember, I flashed the wrong recovery or something and my phone wouldn't boot - it was stuck at the huawei boot logo. I panicked and tried doing all these things using SRK tools, and HiSuite recovery mode, and eventually I was left with a super hard bricked P9. And for the next 3 days I tried all sorts of stuff to recover my phone. I really think I had tried everything (except sending to repair shop). Believe me, I think I had all of the symptoms of everyone in other threads along the way of trying to recovery it. I downloaded about 4 - 6 firmware files just trying to flash and flash but it kept being stuck at 5% or some error. I even bought the 15 euro credit to use DC Phoenix, which allowed me to flash the firmwares but it didn't change anything besides making my semi brick to brick again vice versa.. Nothing seemed to work. This was using Method 1 in their unbricking guide.
What worked.
There was a second method in the DC Phoenix unbricking guide, but the reason I didn't consider this method is because it required me to flash my P9's image file (.dgtks file) which seemingly can only be downloaded from DC Phoenix's download page (searched everywhere but nada). There is only the P9 Dual SIM image file, and I was afraid that this would have been very bad to flash. But in the end I had no real choice cause my warranty was void when I'd unlocked my bootloader.
Here's what I did:
Using DC Phoenix's guide, follow the steps for method 2.
When the guide points you to downloading the image file, find the image for EVA-AL10 (P9 Dual SIM) and flash it.
I followed the exact steps in the guide for method 2. *dont forget to remove your sd card during the process*
Once the flashing has finished, it should boot up briefly to encrypt the storage and reboot into update install screen. If not, then the phone should be fully booted up. There are no themes or any useful apps at this stage.
At this point you must flash your desired firmware using the force update method.
Simple - copy the dload folder of your firmware on to your sd card. On the home screen of your phone, there should be a tool (sorry i cant remember which) and once opened to have an option to force update via sd card. click that and you should be all good with your working phone. In my case, I wanted to flash the firmware EVA-L09C432B136. I copied its contents into the sdcards dload and flashed it without a hitch (i even got ota updates).
Please ask questions if you are unsure because I've probably missed some important stuff.
EDIT:
After flashing with DC Phoenix, for some reason the serial number becomes ABCDEF0123456789, and the bootloader unlock code changes, so the code is different from what you would get from the Huawei bootloader code
Thanks ever so much for above. I was bricked into a corner for the last day or so!
You are a life saver. I had accidentally installed the NRD90M test-keys version of Android N. Caused all sorts of issues. One of the issues with NRD90M was the fact there was no keyboard installed. I relied on google voice. When it restarted it wanted to be reactivated against my google account. FRP Lock had enabled itself. I used a USB A to USB C adapter and physically connected a computer keyboard and was able to enter credentials. I used DC Phoenix to flash the EVA-AL10 firmware as you did. I then used their HCU software to change my vender and country to hw,eu. After doing that I had to use DC Phoenix again to reflash EVA-AL10. Once reflashed I used the Software app on the phone to install VIE-L09C432B180 from the SD Card. I am now all working with Android M using a C432 (eu) firmware on a New Zealand Huawei P9 Plus. I should be able to install Android N now OTF. Thanks for your detailed post.
Question: so moodie007, do you confirm me: on P9 PLUS you flashed at the start the AL10 version of the "standard" P9 ?
It's not clear:
Once reflashed I used the Software app on the phone to install VIE-L09C432B180 from the SD Card
Click to expand...
Click to collapse
What software app did you used to install that firmware? the standard eRecovery (Vol+ Vol - Pwr buttons?)
Thank you so much, you literally saved my life.
what is the DC Phoenix,is it the same as the sd card?
moodie007 said:
You are a life saver. I had accidentally installed the NRD90M test-keys version of Android N. Caused all sorts of issues. One of the issues with NRD90M was the fact there was no keyboard installed. I relied on google voice. When it restarted it wanted to be reactivated against my google account. FRP Lock had enabled itself. I used a USB A to USB C adapter and physically connected a computer keyboard and was able to enter credentials. I used DC Phoenix to flash the EVA-AL10 firmware as you did. I then used their HCU software to change my vender and country to hw,eu. After doing that I had to use DC Phoenix again to reflash EVA-AL10. Once reflashed I used the Software app on the phone to install VIE-L09C432B180 from the SD Card. I am now all working with Android M using a C432 (eu) firmware on a New Zealand Huawei P9 Plus. I should be able to install Android N now OTF. Thanks for your detailed post.
Click to expand...
Click to collapse
can you give me a username and code,I'm in china,I cannot buy it use Alipay .and my phone is bricked,would help me,thx.
Hmm i think my phone is bricked, im unable to get into the menu to update the Update.app file from the dload folder on the SD card, i cant even get the phone to switch off it just keeps restarting itself and freezing on the 'your device has been unlocked and cant be trusted' screen....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if i try and turn the phone of it just turns itself back on and freezes on that screen again
Im able to get to the Fastboot & recovery mode screen if i hold volume down button.......
and if i hold down both the volume and power buttons i get this screen....
and not the firmware update screen i should be getting.
It has been suggested that i need to use DC Phoenix program to fix the phone but will this work seeings as i cant even get the phone to boot or even switch off??
BlockABoots said:
Hmm i think my phone is bricked, im unable to get into the menu to update the Update.app file from the dload folder on the SD card, i cant even get the phone to switch off it just keeps restarting itself and freezing on the 'your device has been unlocked and cant be trusted' screen....

if i try and turn the phone of it just turns itself back on and freezes on that screen again
Im able to get to the Fastboot & recovery mode screen if i hold volume down button.......

and if i hold down both the volume and power buttons i get this screen....
if i try and turn the phone of it just turns itself back on and freezes on that screen again
Im able to get to the Fastboot & recovery mode screen if i hold volume down button.......

and if i hold down both the volume and power buttons i get this screen....

and not the firmware update screen i should be getting.
It has been suggested that i need to use DC Phoenix program to fix the phone but will this work seeings as i cant even get the phone to boot or even switch off??
Click to expand...
Click to collapse
Install twrp through fastboot. Go into twrp. From there you can find a fix for your phone. You can install oeminfo and flash ROM. Good luck
rhodondendron said:
Install twrp through fastboot. Go into twrp. From there you can find a fix for your phone. You can install oeminfo and flash ROM. Good luck
Click to expand...
Click to collapse
Does twrp work with Nougat fw then, as i thought it didnt??
BlockABoots said:
Does twrp work with Nougat fw then, as i thought it didnt??
Click to expand...
Click to collapse
Yes...
But boot in dl mode with power +- and stay ....BUT REMOVE CABLE.....
rayman95 said:
Yes...
But boot in dl mode with power +- and stay ....BUT REMOVE CABLE.....
Click to expand...
Click to collapse
Holding the power and volume buttons doesnt boot me into the force update screen though, instead i get this screen....
Try to install twrp in fastboot and reboot immediately without the cable...
BlockABoots said:
Does twrp work with Nougat fw then, as i thought it didnt??
Click to expand...
Click to collapse
Twrp work fine with nougat. Find thread called twrp P9 with decryption support emui 5.x. Work like charn
rhodondendron said:
Twrp work fine with nougat. Find thread called twrp P9 with decryption support emui 5.x. Work like charn
Click to expand...
Click to collapse
Says its for the PLUS model only.
Im trying to use command lines via adb but keep getting 'FAILED (remote: Command not allowed)' responses, any ideas?
BlockABoots said:
Says its for the PLUS model only.
Im trying to use command lines via adb but keep getting 'FAILED (remote: Command not allowed)' responses, any ideas?
Click to expand...
Click to collapse
Just try this dude. https://forum.xda-developers.com/p9/development/twrp-t3565703/page1
same problem
where the same problem sir BlockABoots hows your p9?
Alfombra said:
where the same problem sir BlockABoots hows your p9?
Click to expand...
Click to collapse
Its still bricked atm
---------- Post added at 08:24 PM ---------- Previous post was at 08:20 PM ----------
rhodondendron said:
Just try this dude. https://forum.xda-developers.com/p9/development/twrp-t3565703/page1
Click to expand...
Click to collapse
The issue im having when trying to adb to the phone is i keep getting a message saying 'FAILED (remote: Command not allowed)'.
If i type adb devices its showing no devices, its as if the PC cant detect the phone, but when i plug it into the PC it makes the USB connection sound and also if i run HiSuite it says there is no device connected but if i select the recovery option it then detects the phone but after checking says there are no available packages for my model
BlockABoots said:
Its still bricked atm
---------- Post added at 08:24 PM ---------- Previous post was at 08:20 PM ----------
The issue im having when trying to adb to the phone is i keep getting a message saying 'FAILED (remote: Command not allowed)'.
If i type adb devices its showing no devices, its as if the PC cant detect the phone, but when i plug it into the PC it makes the USB connection sound and also if i run HiSuite it says there is no device connected but if i select the recovery option it then detects the phone but after checking says there are no available packages for my model
Click to expand...
Click to collapse
From what I get, you still can go to fastboot&rescue mode right? Just flash twrp through fastboot. No need for adb dude. (use fastboot command instead of adb command dude)
You can't connect adb if you can't boot. From the twrp you can try to fix your phone. Maybe change the oeminfo, or flash a rom, even shutdown your phone to do three button rom install. Do you get what I am saying?
rhodondendron said:
From what I get, you still can go to fastboot&rescue mode right? Just flash twrp through fastboot. No need for adb dude. (use fastboot command instead of adb command dude)
You can't connect adb if you can't boot. From the twrp you can try to fix your phone. Maybe change the oeminfo, or flash a rom, even shutdown your phone to do three button rom install. Do you get what I am saying?
Click to expand...
Click to collapse
fastboot commands dont appear to work either, i was trying early on with a recovery file.....

ZTE NUBIA Z9 MINI Bricked Plz HELP

Recently my phone has suddenly stopped all apps and system ui has crashed and a msg appeared that
"Encryption Failure plz reset ur phone" then i have reseted the phone and again the same msg has appeared
then i have gone to recovery it displays the msg like cant mount system,data,cache,etc
then i have also tried applying update from adb but it didnt worked then i have flashed twrp it shows internal storage as 0mb
then i have erased all system,boot,misc,data,cache from fastboot commands now i cant flash boot.img from fastboot it shows the msg "flash write failure" i also tried reformating data and system partitions from adb shell as i have access to twrp
my phone doesnt have usb debugging on and i have not rooted my phone can plz help :crying:
Please let me know if it get resolved.
PrabhakarKamath said:
Recently my phone has suddenly stopped all apps and system ui has crashed and a msg appeared that
"Encryption Failure plz reset ur phone" then i have reseted the phone and again the same msg has appeared
then i have gone to recovery it displays the msg like cant mount system,data,cache,etc
then i have also tried applying update from adb but it didnt worked then i have flashed twrp it shows internal storage as 0mb
then i have erased all system,boot,misc,data,cache from fastboot commands now i cant flash boot.img from fastboot it shows the msg "flash write failure" i also tried reformating data and system partitions from adb shell as i have access to twrp
my phone doesnt have usb debugging on and i have not rooted my phone can plz help :crying:
Click to expand...
Click to collapse
I have same kind of problem in my ZTE Z9 mini. I tried lots of thing but still shows E: Can't mount cache.....
Please share your exprience if you had a solution with your phone.
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
PrabhakarKamath said:
Recently my phone has suddenly stopped all apps and system ui has crashed and a msg appeared that
"Encryption Failure plz reset ur phone" then i have reseted the phone and again the same msg has appeared
then i have gone to recovery it displays the msg like cant mount system,data,cache,etc
then i have also tried applying update from adb but it didnt worked then i have flashed twrp it shows internal storage as 0mb
then i have erased all system,boot,misc,data,cache from fastboot commands now i cant flash boot.img from fastboot it shows the msg "flash write failure" i also tried reformating data and system partitions from adb shell as i have access to twrp
my phone doesnt have usb debugging on and i have not rooted my phone can plz help :crying:
Click to expand...
Click to collapse
Hi Prabhat, I have exact same issue with my Nubia ZTE Z9 min. I tried lots of this but still getting E:cant mount cache..... error again and again.
If you got solution of it. Please share with me..
rajesh9250 said:
I have same kind of problem in my ZTE Z9 mini. I tried lots of thing but still shows E: Can't mount cache.....
Please share your exprience if you had a solution with your phone.
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
Hi Prabhat, I have exact same issue with my Nubia ZTE Z9 min. I tried lots of this but still getting E:cant mount cache..... error again and again.
If you got solution of it. Please share with me..
Click to expand...
Click to collapse
Guys if you can send me a screenshot of the error i can explain the method to reflash boot image.
rajesh9250 said:
I have same kind of problem in my ZTE Z9 mini. I tried lots of thing but still shows E: Can't mount cache.....
Please share your exprience if you had a solution with your phone.
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
Hi Prabhat, I have exact same issue with my Nubia ZTE Z9 min. I tried lots of this but still getting E:cant mount cache..... error again and again.
If you got solution of it. Please share with me..
Click to expand...
Click to collapse
You can also try the below method.
Download ZTE Firmware From Below And Extract It
Switch Off Your Android Phone & Remove The Battery (If Battery is Removable)
Download SP Flash Tool and extract it on Your Computer
Run SP Flash Tool , Tap on The Download Tap.
Tap on The Scatter-Loading Button.
Select “Android_scatter.txt” from “Firmware” folder
Click the “Download” button
Connect Your Phone Through USB Cable
Read Full Flashing Process From Below
Copy the Zip to your Phone SD Card and Flash it through recovery Mode.
Please give firmware link it is not present
mm_rajesh said:
You can also try the below method.
Download ZTE Firmware From Below And Extract It
Switch Off Your Android Phone & Remove The Battery (If Battery is Removable)
Download SP Flash Tool and extract it on Your Computer
Run SP Flash Tool , Tap on The Download Tap.
Tap on The Scatter-Loading Button.
Select “Android_scatter.txt” from “Firmware” folder
Click the “Download” button
Connect Your Phone Through USB Cable
Read Full Flashing Process From Below
Copy the Zip to your Phone SD Card and Flash it through recovery Mode.
Click to expand...
Click to collapse
Please give link of firmware it is not present
PrabhakarKamath said:
Please give link of firmware it is not present
Click to expand...
Click to collapse
There is no formal firmware that we use You can flash any custom ROM or even the stock ROM.
Stock ROM : https://forum.xda-developers.com/android/help/help-nubia-z9-mini-indian-version-t3297449
Custom ROM : http://4pda.ru/forum/index.php?showtopic=702119&st=­4800
There are lot of options for custom ROM. Flash and send me screenshots if you get error.
mm_rajesh said:
There is no formal firmware that we use You can flash any custom ROM or even the stock ROM.
Stock ROM : https://forum.xda-developers.com/android/help/help-nubia-z9-mini-indian-version-t3297449
Custom ROM : http://4pda.ru/forum/index.php?showtopic=702119&st=­4800
There are lot of options for custom ROM. Flash and send me screenshots if you get error.
Click to expand...
Click to collapse
i cant find the scatter file plz help me:crying:
mm_rajesh said:
There is no formal firmware that we use You can flash any custom ROM or even the stock ROM.
Stock ROM : https://forum.xda-developers.com/android/help/help-nubia-z9-mini-indian-version-t3297449
Custom ROM : http://4pda.ru/forum/index.php?showtopic=702119&st=­4800
There are lot of options for custom ROM. Flash and send me screenshots if you get error.
Click to expand...
Click to collapse
the error msg is "no kernal(bad partition)"
" your phone is fused"

[GUIDE] Unbrick your device or recover from bootloop

Assalamu alaikum people,
Those on the telegram group know that I bugged you a lot about needing data partition. Because of my experience with unbricking and recovering the device, I can tell you a sureshot method that works to restore the device. Do not use this method if your device already works. There seems to be a lot of files inside the data partition which are necessary for the stock ROM to work. This method asks you to wipe data partition and so system update will not work. This should be a last resort. .
Many people seem to have come to the situation where they are in fastboot, and it says frp locked, so they cannot flash new twrp. And the system seems to be in bootloop and it does not work. What to do from there?
1. Download this file ->https://www.androidfilehost.com/?fid=673956719939832337.
2. In your SDCard, create a folder called TWRP and inside it, create a folder called BACKUPS (all in capitals). Inside this, create a folder called 7xtwrpbackup (small letters) and paste the contents of the zip that you have downloaded into this.
3. Boot to twrp in your device and go to restore. There you should see a folder 7xtwrpbackup. If you select it, you will get a checkbox below with recovery_ramdisk like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Select Yes and after restore complete, go back and select reboot and reboot to recovery.
5. Now, the new twrp will boot. In the new twrp, I want you to first go to wipe -> advanced wipe -> select dalvik/art cache, cache, data, internal storage and system.
6. Come back once again and select wipe, and this time, select format data. It will ask you to type yes. After that is done, come back once again.
7. Now select install and in that, install the openkirin RR image from telegram group or here -> https://forum.xda-developers.com/honor-view-10/development/rom-t3753555 (This step is optional because openkirin RR has a greater chance of booting than stock ROM. You can skip this step and directly boot stock)
8. Your system must boot now. If it boots, then all partitions are good. You can boot stock.
9. You can now can download stock from my post here and repeat from step 5-> https://forum.xda-developers.com/9-lite/development/stock-img-unlock-indian-version-t3767569
If this does not work, then look at the second method in the next post
Second method
If your first method does not work, then you can try this second method. Make sure you have enough data left in your internet connection (1.8 GB ish) before starting the process. Please note that this method will lock your bootloader, install stock recovery, flash the stock system and boot your phone. Of course, even if it relocks the bootloader, you can still unlock it using your code.
1. Download the zip
https://www.androidfilehost.com/?fid=746010030569970895
2. Extract it into sdcard directly (i.e. extract it to the root folder of your sdcard)
3. Make sure you have enough battery left (atleast 15%). Power off your phone. Now, press and hold vol up + Vol down + power buttons until the honor logo comes. Then, you can release all the keys. The system will go into emui recovery and restore your phone.
You will have stock phone at the end of the process.
Note:-If you still have bootloop at Honor logo, then power off the phone. Hold vol up + power button until the honor logo comes. It will boot into stock recovery. From there, you can do a factory reset and erase cache partition. Then the phone will definitely boot up.
Bricked my device Twrp doesn't work
Hello, I have bricked my honor 9 lite AL10(Indian Version). I have formatted my vender directory through Twrp by mistake now my device shows erecovery and reboots. Fastboot is working fine and FRP and Devices both shows unlocked means I can flash through fastboot. I don't want to lose my internal memory data.
Help me to unbrick my device !! :crying:
Oushal kDee said:
Hello, I have bricked my honor 9 lite AL10(Indian Version). I have formatted my vender directory through Twrp by mistake now my device shows erecovery and reboots. Fastboot is working fine and FRP and Devices both shows unlocked means I can flash through fastboot. I don't want to lose my internal memory data.
Help me to unbrick my device !! :crying:
Click to expand...
Click to collapse
Download vendor partition from here https://forum.xda-developers.com/9-lite/development/stock-img-unlock-indian-version-t3767569
Hello i am siddharth, i have relocked my oem by fastboot oem relock -------- after that yes/no option came i click on yes. It starts factory formatting after completion of formatting when the phone starts its showing your device has failed verification and got stuck in it. When i press reboot option it will directly comes to erecovery mode wher the option came to download new recovery when i connect my phone with wifi it starts searching for some time after that system update failed.
When i starts mobile directly to fastboot mode by pressing volume down button and power button the white screen with android comes appear i.e fastboot mode screen. In that screen in green colour i found that
Phone Relock
FRP lock
When ever i m trying to find the device in fastboot mode by typing fastboot devices my device showing there but no other command is working such as fastboot oem unlock -------, fastboot flash system system.img, all the time it comes Failed.
I have downloaded many UPDATE.APP and tried to load that by dload method but every time after 5% it come Failed to install.
I have downloaded UPDATE.APP form ur given link also. This is only the image in which my phone comes upto 23% install after dat failed.
Nothing working for me. Kindly help me.
Mail me if there is any solution @
[email protected]
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
None of the method worked for me my device still bootloops no matter what system.img or rom zip file i flash. The emui recovery method didn't work for me as it loaded up to 5% and then failed instantly. Please help me unbrick my 9 lite bro. Could you provide me the boot.img? i think my phone got bricked because i tried to i install magisk on treble rom (i guess?). But anyway PLEASE HELP ME (
Try extracting kernel.img from an update and flash that. It fixed it for me.
hi twrp is bootlooping as well
cant access
---------- Post added at 07:15 PM ---------- Previous post was at 06:52 PM ----------
hey i used the twrp from the link made a backup restored it now a get bootloop cant get into twrp it goes in ti it then it fcs then am back to bootloader unlocked warning
hi anyone got custom.img and userdata.img from this LLDL31C432B130 800130 a need to restore my device
Same Problem
[email protected] said:
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
Click to expand...
Click to collapse
Even I'm facing the same problem, if anyone has solution plz help.
---------- Post added at 10:15 AM ---------- Previous post was at 10:10 AM ----------
[email protected] said:
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
Click to expand...
Click to collapse
Even I'm facing the same problem.
mine goes to 5% doesnt do anything and then it fails
aveemashfaq said:
If your first method does not work, then you can try this second method. Make sure you have enough data left in your internet connection (1.8 GB ish) before starting the process. Please note that this method will lock your bootloader, install stock recovery, flash the stock system and boot your phone. Of course, even if it relocks the bootloader, you can still unlock it using your code.
1. Download the zip
https://www.androidfilehost.com/?fid=746010030569970895
2. Extract it into sdcard directly (i.e. extract it to the root folder of your sdcard)
3. Make sure you have enough battery left (atleast 15%). Power off your phone. Now, press and hold vol up + Vol down + power buttons until the honor logo comes. Then, you can release all the keys. The system will go into emui recovery and restore your phone.
You will have stock phone at the end of the process.
Note:-If you still have bootloop at Honor logo, then power off the phone. Hold vol up + power button until the honor logo comes. It will boot into stock recovery. From there, you can do a factory reset and erase cache partition. Then the phone will definitely boot up.
Click to expand...
Click to collapse
But this is for L31
---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------
My phone's frp and bootloader locked,and phone is booting to erecovery,what to do
need help with LLD-AL10C675 indian version
I have flashed a cutom treble rom phh-treble to be specific,used it for couple of days and then tried instaling the magisk from magiskmanager and after its done when i reboot it shows error mode with message Func no:10(boot img ) and func no:2 , i can boot into fastboot mode both frp and phone unlocked ,can some please help me to get back my phone into a usable condition thank you
sunny_deed said:
I have flashed a cutom treble rom phh-treble to be specific,used it for couple of days and then tried instaling the magisk from magiskmanager and after its done when i reboot it shows error mode with message Func no:10(boot img ) and func no:2 , i can boot into fastboot mode both frp and phone unlocked ,can some please help me to get back my phone into a usable condition thank you
Click to expand...
Click to collapse
To help you a full firmware is required and that's not available for (India c675) yet!
Before any modification to system you should have a full firmware in hand.
BS4388 said:
To help you a full firmware is required and that's not available for (India c675) yet!
Before any modification to system you should have a full firmware in hand.
Click to expand...
Click to collapse
yea that was a pretty big mistake i made without looking for it, i have been told by someone that we can pull out all the require d imgs from a phone in good working condition, i asked in the hopes that someone would be generous enough to do that for me , thank you ,and also does anyone have any idea about when the full firmware will be released
sunny_deed said:
yea that was a pretty big mistake i made without looking for it, i have been told by someone that we can pull out all the require d imgs from a phone in good working condition, i asked in the hopes that someone would be generous enough to do that for me , thank you ,and also does anyone have any idea about when the full firmware will be released
Click to expand...
Click to collapse
What's wrong with the version (675) from here :-
https://www.mobileheadlines.net/download-huawei-honor-9-lite-firmware-files/
Sparkrite said:
What's wrong with the version (675) from here :-
https://www.mobileheadlines.net/download-huawei-honor-9-lite-firmware-files/
Click to expand...
Click to collapse
there is no Fullota version in there
sunny_deed said:
there is no Fullota version in there
Click to expand...
Click to collapse
Go:
https://forum.xda-developers.com/9-lite/development/stock-rom-indian-firmware-c675-t3813875
sunny_deed said:
there is no Fullota version in there
Click to expand...
Click to collapse
My bad, I was only trying to help.............
Anyway you have it now (post above) thanks to @BS4388 and @VigneshS007 .

Maze Alpha X Bootloop Problem [SOLVED]

Hello everybody please help me. I tried to Root my phone I unlocked the phone while getting help from “dreambo” then I unlocked the phone and download twrp recovery then when I tried to start phone it only showed me recovery menu sistem was not opening then tried to chech “dreambo” again then i saw a picture (picture 1) there I wrote “fastboot flash recovery boot.alpha.x.img” instead of “fastboot flash boot boot.alpha.x.img” and now phones recovery didnt open and become bootloop it shows logo then turn off (video 1) then i cant able to to put phone into “bootloader mode” . I know this phone doesn’t have stock rom how can i fix this phone ?
dreambo Thread: Root and TWRP 3.2.1 for Maze Alpha X 6/64
(picture 1)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(video 1)​
video link: https://youtu.be/QYMCOQiExMg
Originally Posted
dreambo said:
I am almost sure that you have flashed the recovery image in the boot partition !
You have do that fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img
To have your phone working, just flash the attached boot.img : fastboot flash boot boot.alpha.x.img
Click to expand...
Click to collapse
Edit: Way to solve Problem:
Stive very thanks to my friend after a long time I fixed the phone. In order to do UNBRICK phone download this from link and than put phone into charge than connect phone to computer with usb and open "Flash tool" program than add “MT6757_Android_scatterr.txt” file than put it “Frimware Upgrade” than download and wait until it finished.
Stive87 said:
Unbrick Maze Alpha X 6/64GB only phone is black screen and phone is total brick (format all partition).
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view
Rom is no official :
System : official rom for Maze Alpha B6/64GB . (! no update after - OTA !!),
boot, logo and recovery is normal (copy from original my phone).
Good luck.
Sorry for bad english, my french ^^
Click to expand...
Click to collapse
Stive87 said:
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view?usp=drivesdk
full rom V03 6/64GB Rom Ofifcial Stock
https://drive.google.com/file/d/1WjXKj8abnghy_OjfUW5TYkAppjWg0amH/view?usp=sharing
Click to expand...
Click to collapse
Thanks to everyone who helped!!
help please
rafaello21 said:
help please
Click to expand...
Click to collapse
Became interested in this phone since I found a 6/128 model for 160$. If fastboot is failing (maybe because of the different partition size?) I'd go with SPFlashTool: if I remember well phone only need to be swithed off when you start downloading the image, therefore it goes well with bootloping if you choose the right moment
matteo.de-leo said:
Became interested in this phone since I found a 6/128 model for 160$. If fastboot is failing (maybe because of the different partition size?) I'd go with SPFlashTool: if I remember well phone only need to be swithed off when you start downloading the image, therefore it goes well with bootloping if you choose the right moment
Click to expand...
Click to collapse
I bought it 170$ when it was on discount no matter what i do “bootloader mode” not works because of the error that i did and no one helps
rafaello21 said:
I bought it 170$ when it was on discount no matter what i do “bootloader mode” not works because of the error that i did and no one helps
Click to expand...
Click to collapse
That's exactly what I'm saying: SPFlashTool doesn't require your phone to be in fastboot mode, only to be switched of when you plug it in. I had the same problem with an Archos Sense 55S after treying to root it. I wasn't able to enter neither fastboot or recovery mode, therefore I flashed the stock rom with SPFT
matteo.de-leo said:
That's exactly what I'm saying: SPFlashTool doesn't require your phone to be in fastboot mode, only to be switched of when you plug it in. I had the same problem with an Archos Sense 55S after treying to root it. I wasn't able to enter neither fastboot or recovery mode, therefore I flashed the stock rom with SPFT
Click to expand...
Click to collapse
I would do it if i have Stock rom ? i am very disappointed because of bought this phone how is it possible that phone doesnt have stock rom is there any possibility to fix this without stock rom?
rafaello21 said:
I would do it if i have Stock rom i am very disappointed because of bought this phone how is it possible that phone doesnt have stock rom is there any possibility to fix this without stock rom?
Click to expand...
Click to collapse
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
matteo.de-leo said:
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
Click to expand...
Click to collapse
Hi, can i use this to restore my phone? And do you know how? I did a search in the web but didn't fin any solution.
ttl1982 said:
Hi, can i use this to restore my phone? And do you know how? I did a search in the web but didn't fin any solution.
Click to expand...
Click to collapse
Hi ttl1982, before giving an answer I should know what are we talking about. Is it the same phone? And which version? What is the current situation (bootlooping into TWRP, bootlooping into Android)? Even assuming we're still talking about the Maze Alpha X, there are still too much variables!
matteo.de-leo said:
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
Click to expand...
Click to collapse
I have Maze Alpha X 6/64 model. If “bootloader mode” doesnt open how can i install ‘twrp’ ? About Thread article i read everything but my only problem is my phone dont open “bootloader mode”. And only solution is stock rom i think than you need SPFlashTool to install it. Maybe you know better than me how can i install “twrp” without opening “bootloader mode” ? I wrote above why this happened.
I click Power and Vol+ buttons as i show in the video phone turn of but doesn’t open “bootloader mode”
rafaello21 said:
I have Maze Alpha X 6/64 model. If “bootloader mode” doesnt open how can i install ‘twrp’ ? About Thread article i read everything but my only problem is my phone dont open “bootloader mode”. And only solution is stock rom i think than you need SPFlashTool to install it. Maybe you know better than me how can i install “twrp” without opening “bootloader mode” ? I wrote above why this happened.
I click Power and Vol+ buttons as i show in the video phone turn of but doesn’t open “bootloader mode”
Click to expand...
Click to collapse
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
matteo.de-leo said:
Hi ttl1982, before giving an answer I should know what are we talking about. Is it the same phone? And which version? What is the current situation (bootlooping into TWRP, bootlooping into Android)? Even assuming we're still talking about the Maze Alpha X, there are still too much variables!
Click to expand...
Click to collapse
Hi, Thanks for your quick response. I will share some more info like you asked.
- Phone: Maze Alpha X
- Version: 6GB RAM/128GB Storage
- Current situation: It won't start at all (when connected to Windows PC i get the 'USB device not recognized' error, so it does see something)
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
ADB is not recognizing the phone, so it can't be done that way (as far as my knowledge goes).
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
matteo.de-leo said:
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
Click to expand...
Click to collapse
I will try but phone turn off and one very quick. Is 1-2 seconds enough for doing what you are saying ? Twrp flash i have to do ? Is there any phone and have similar problem like this ? Can help with help of Video ? And i will try what you said and back to you thanks
ttl1982 said:
Hi, Thanks for your quick response. I will share some more info like you asked.
- Phone: Maze Alpha X
- Version: 6GB RAM/128GB Storage
- Current situation: It won't start at all (when connected to Windows PC i get the 'USB device not recognized' error, so it does see something)
I got this phone from my nephew. He broke it because he flashed the Maze Alpha (not X) 4GB RAM/64GB storage rom on it because he had TWRP bootloops.
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
ADB is not recognizing the phone, so it can't be done that way (as far as my knowledge goes).
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
Click to expand...
Click to collapse
I also wrote them several times about stock rom but they didn’t answer me i think company only think about money. Do we have to throw our phone to garbage because of one wrong thing ? What should i do ?
ttl1982 said:
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
Click to expand...
Click to collapse
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
Click to expand...
Click to collapse
Why do you say you don't have the right one? Did SPFlashTool return you some error?
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
Click to expand...
Click to collapse
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
matteo.de-leo said:
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
Click to expand...
Click to collapse
I tried when I click Power and Vol+ it does bootloop.But the only way to put phone into “bootloader mode” you need SPFlashTool. I dont know what can i do now. When phone was bootlooping i wrote several times “adb devices” but nothing happened
matteo.de-leo said:
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
I will try this, maybe that works.
Why do you say you don't have the right one? Did SPFlashTool return you some error?
Yes, it says 'status preloader invalid'
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
Click to expand...
Click to collapse
That explains a lot. But it is still not acceptable to answer no one imo
---------- Post added at 10:48 PM ---------- Previous post was at 10:34 PM ----------
matteo.de-leo said:
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
Why do you say you don't have the right one? Did SPFlashTool return you some error?
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
Click to expand...
Click to collapse
ttl1982 said:
That explains a lot. But it is still not acceptable to answer no one imo
Click to expand...
Click to collapse
I now get another error when flashing boot.img:
ERROR: STATUS_BROM_CMD_STARTCMD_FAIL
ttl1982 said:
ERROR: STATUS_BROM_CMD_STARTCMD_FAIL
Click to expand...
Click to collapse
As reported by another user on this website: https://forum.hovatek.com/thread-21351.html
The device attempted to power on before SP flash tool could flash files to it
Click to expand...
Click to collapse
Phone must be plugged (while switched off) to the USB port after having given the Download order to SP
---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------
By the way, it seems that this very website (in particular here https://forum.hovatek.com/thread-468.html) hosts a guide to dump a Mediatek firmware SPFlashTool compatible, together with the necessary files, but guess what? You need to register in order to download them, something that I'll definitely do if it just lets me
ttl1982 said:
I now get another error when flashing boot.img:
Click to expand...
Click to collapse
Which boot.img you chose ?
matteo.de-leo said:
Phone must be plugged (while switched off) to the USB port after having given the Download order to SP
Click to expand...
Click to collapse
What should i do exactly to use SPFlashTool ? What alternative ? When I connect my phone to pc it turn off turn on then power volume + and - buttons randomly and than turn on turn off stoped now it looks like this in the picture . Than i checked “adb devices” it says “waiting for devices”. The thing that “dreambo” shared “boot.alpha.x.img” and can i adjust this with SPFlashTool and install it ?
rafaello21 said:
Which boot.img you chose ?
What should i do exactly to use SPFlashTool ? What alternative ? When I connect my phone to pc it turn off turn on then power volume + and - buttons randomly and than turn on turn off stoped now it looks like this in the picture . Than i checked “adb devices” it says “waiting for devices”. The thing that “dreambo” shared “boot.alpha.x.img” and can i adjust this with SPFlashTool and install it ?
View attachment 4518023
Click to expand...
Click to collapse
I have used the exact same boot.img as you did.

Categories

Resources