Related
Good evening gents,
!UPDATE! 2023.01.31.
I uploaded the v2 and the v3 tool in post 89. !!!
New universal version by ionioni for restore, try that first: http://forum.xda-developers.com/x98-air/help/baytrail-dnx-mode-bios-flashing-tool-t3295105
Before you do anything read this post: http://forum.xda-developers.com/showpost.php?p=64792827&postcount=54
!!!This restoring methode doesn't work if you flashed 2.05b BIOS from Mirek 7.0 tool!!!
I have: Teclast X98 Air 3G - the processor: Z3735F, and the GPS not working - that is the ID:C5J8, and I got it with "BIOS 11/09/2015 14:25:40 Ver: tPAD205" This is the so called 2.05c version.
I flashed 2.02 BIOS on my c5J8 - it is BRICKED!!!
+++DON'T DO THAT+++
Thanks to ionioni we have a way to unbrick our devices (as long as they still boot into dnx).
I flashed the wrong BIOS on to my X98 Air 3G (ID: C5J8) and thought i bricked it beyond repair (except opening it up and flashing it with EEPROM Clip).
Now we have a solution to flash the DUAL BOOT - BIOS to the C5J8 through dnx mode:
WARNING: EVERYTHING YOU DO, YOU DO AT YOUR OWN RISK! Only for C5J8! Using it on other devices can HARDBRICK!!!
IMPORTANT: DO NOT CUT THE USB OR POWER AND WATCH OUT THAT THERE IS ENOUGH POWER IN THE ACCU.
1. Copy the following files into your fastboot directory on your pc:
UPDATE 2016.01.04.
New version with messages on the screen and possibility not to do the flashing in case you think it can do bad things on your tablet (100sec countdown while you can change your mind)
Ver.2
https://drive.google.com/open?id=0B1EG-i0pY3FIMnBqVUIzWHdJUDg
2. Boot the device into dnx/fastboot (pressing power and Vol+/Vol- at the same time)
3. Plug the device in via usb, open up a command prompt in your fastboot directory and type the following:
fastboot devices #Check if device is recognized
fastboot flash osloader efilinux.efi #Push Efiloader onto device
fastboot boot restore_bios_c5j8.img #restores the dual boot bios !!!I'm sorry here was a mistype before!!!
4. Wait for reboot. There are no messages during the flash. It takes between 3-5 Minutes. DO NOT FORCE REBOOT it WILL HARDBRICK! You will see what happen on the screen.
*******************************************************************************************************************
Here is my log about miracle:
d:\Install\Teclast\Android\X98_Air_3g_android_5.0_mirek190_v7.0\data>fastboot devices
Baytrail021118DF fastboot
d:\Install\Teclast\Android\X98_Air_3g_android_5.0_mirek190_v7.0\data>fastboot flash osloader efilinux.efi
sending 'osloader' (2463 KB)...
OKAY [ 0.110s]
writing 'osloader'...
OKAY [ 0.007s]
finished. total time: 0.118s
d:\Install\Teclast\Android\X98_Air_3g_android_5.0_mirek190_v7.0\data>fastboot boot restore_bios_c5j8.img
downloading 'boot.img'...
OKAY [ 0.837s]
booting...
OKAY [ 0.003s]
finished. total time: 0.840s
d:\Install\Teclast\Android\X98_Air_3g_android_5.0_mirek190_v7.0\data>
*************************************************************************************************************************
{
"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"
}
EDIT:
After the successfull restore there was some glitch in the tablet's behaviour - but I dont remember exactly -, so I advice, after restore boot into BIOS with Escape or Delete key AND there make "RESTORE DEFAULTS" and "SAVE CHANGES AND RESET".
Notes:
- if you have used Mirek's tool and something went bad for exapmle the Android does not start, that is not BIOS problem, particularly if the Windows running.
This restore is for the REAL BIOS failure when nothing start, the tablet only continously restarting in bootloop!
Be happy to have unbricked your BIOS. And thank ionioni !!
Sorry for my weak english.
So, years have passed, all links are well and truly dead, yet here I am again, looking for ionion's magic tool..... has it left this world????
:victory: Mine is saved too :victory:
A HUGE THANKS TO @ionioni !!!!!
blackbile said:
Good evening gents,
I have: Teclast X98 Air 3G - the processor: Z3735F, and the GPS not working - that is the ID:C5J8, and I got it with "BIOS 11/09/2015 14:25:40 Ver: tPAD205" This is the so called 2.05c version.
Click to expand...
Click to collapse
I got same configuration. Any chance to get GPS working?
Wysłane z mojego X98 Air 3G przy użyciu Tapatalka
I wish I could find a solution, but at this time I could't!!!
blackbile said:
I wish I could find a solution, but at this time I could't!!!
Click to expand...
Click to collapse
And in Windows? I do not have windows already at my tablet so I can't check.
What teclast is saying?
So far I thought that it was just something wrong with my because of me flashing rom etc.
But it seems now that this model has some issues.
Wysłane z mojego X98 Air 3G przy użyciu Tapatalka
The device exist in win10, but cant be initialized.
you should also thank @QuiGonJinn37 for parallel testing and helping
all in all, this call for help with the bios semi-brick made me wander a little over the Teclast devices and sure thing my next one will no longer be a Lenovo (i mean they are both China OEM's but same hw is basically half price at Teclast and as a bonus comes with the same crappy support as the Lenovo one )
That is very interesting method of flashing the bios - May I edit your work for other biosess ?
Another question - where is the service to run loader script ?
yes you may
in init.rc theres a new yaft_ser service defined that is started in the 'on boot' trigger sequence (dtach loads and runs yaft in detached mode and this one runs the loader script '/tasks/loader', path was defined at compile time, normally it just opens a 'system/bin/sh' for the terminal)
droidboot (or whatever outputs to the /dev/fb0) should be stopped before starting the new service so it won't interfere with the new terminal (will still work but you will have mixed stuff on the screen from the new terminal and from fastboot)
ionioni said:
yes you may
in init.rc theres a new yaft_ser service defined that is started in the 'on boot' trigger sequence (dtach loads and runs yaft in detached mode and this one runs the loader script '/tasks/loader', path was defined at compile time, normally it just opens a 'system/bin/sh' for the terminal)
droidboot (or whatever outputs to the /dev/fb0) should be stopped before starting the new service so it won't interfere with the new terminal (will still work but you will have mixed stuff on the screen from the new terminal and from fastboot)
Click to expand...
Click to collapse
Ok -thanks
I knew it was somewere in rc files but couldn't locate it yesterday I was too tired .
Thanks again.
All,
Thanks a lot for your contributions, they are always of great quality, and that's a pleasure.
with a special thanks to mirek190 & ionioni .:good: :good:
by the way,
I'm trying to flash back my bios on my C5J8. tablet (brand new from christmas.......)
I was trying to flash 2.5 bios using Mirek 7.0......then I'm now in Bootloop(Red Logo) (((
so I'm trying to follow the above procedure....but I get this error:
everything fine on the pc side,
but I get that on the tablet side,
EFILINUX [ 0.000462] ERROR[get_parth:334] couldn't find boot device handle
then I can restart to the red logo ((
If needed I still have saved my original bios using mirek tool.
So Please could you help me?
Thanks a lot,
best regards,
Florent
florent.m said:
EFILINUX [ 0.000462] ERROR[get_parth:334] couldn't find boot device handle
then I can restart to the red logo ((
Click to expand...
Click to collapse
the 'couldn't find boot device handle' error message is normal because the booting is not done as usual from the disk device but from memory ( = no device handle)
check that you downloaded the latest files (V2) that the owner of this thread posted at the beginning (maybe download again to be sure)
in the picture you took you issued as your last command
fastboot boot bios_restore_c5j8.img but the correct command for the V2 is
fastboot boot restore_bios_c5j8.img as that is the filename of the boot image (maybe the thread owner should update that line, is a leftover from the previous version)
be careful that if somehow(???) you use the first(obsolete now, it's not even there to download anymore) variant of the tool (but you shouldn't) it doesn't display messages on screen during flashing, yet the bios is still wrote so you should always wait 4-5 minutes after you issued the 'fastboot boot' command before you force a power off (that is if the tab doesn't reboot and/or you don't have status messages on the tab screen)
if it still doesn't work i can make you a custom tool (i don't have any x98 device so i don't know about various models) . pack your known working bios file and the droidboot.img from your stock rom and paste a link to that.
Yes guys, it was my fault, the command was incorrect, that was the reason could not find anything! CORRECTED in OP.
florent.m said:
All,
Thanks a lot for your contributions, they are always of great quality, and that's a pleasure.
with a special thanks to mirek190 & ionioni .:good: :good:
by the way,
I'm trying to flash back my bios on my C5J8. tablet (brand new from christmas.......)
I was trying to flash 2.5 bios using Mirek 7.0......then I'm now in Bootloop(Red Logo) (((
so I'm trying to follow the above procedure....but I get this error:
everything fine on the pc side,
but I get that on the tablet side,
EFILINUX [ 0.000462] ERROR[get_parth:334] couldn't find boot device handle
then I can restart to the red logo ((
If needed I still have saved my original bios using mirek tool.
So Please could you help me?
Thanks a lot,
best regards,
Florent
Click to expand...
Click to collapse
do you solved you problem?
I have the same problem with my m5c5 i use this files:
http://forum.xda-developers.com/x98-air/help/unbrick-bios-softbrick-withouth-eeprom-t3285054
after fastboot boot restore_bios_m5c5.img usb disconnect.
florent.m said:
so I'm trying to follow the above procedure....but I get this error:
everything fine on the pc side,
but I get that on the tablet side,
Click to expand...
Click to collapse
check the end of this post http://forum.xda-developers.com/showpost.php?p=64691255&postcount=9
Thanks a lot to all for your answers,
I'm not at home tonight,
so I'll test during this weekend and keep you posted,
Cheers,
Florent;
florent.m said:
Thanks a lot to all for your answers,
I'm not at home tonight,
so I'll test during this weekend and keep you posted,
Cheers,
Florent;
Click to expand...
Click to collapse
don't test that stuff i posted in my prev message, it is already confirmed NOT to work
the actual version for c5j8 that is now posted in OP is confirmed working as you can see also from the pictures he took (by @blackbile ) and should work
however if it still doesn't (i don't have no x98 device to test stuff) you can ask @blackbile to send you the 'blind' variant that we used at the beginning of all this stuff (be careful as that one doesn't display any status messages so WAIT until it reboots) and try with that
but since it is already tested working you should download again from the OP first post (just to be sure) and try again (make sure you follow all the steps)
if it is still not working maybe you are on another model? (m5c5 or c6j7 etc)
ionioni said:
don't test that stuff i posted in my prev message, it is already confirmed NOT to work
the actual version for c5j8 that is now posted in OP is confirmed working as you can see also from the pictures he took (by @blackbile ) and should work
however if it still doesn't (i don't have no x98 device to test stuff) you can ask @blackbile to send you the 'blind' variant that we used at the beginning of all this stuff (be careful as that one doesn't display any status messages so WAIT until it reboots) and try with that
but since it is already tested working you should download again from the OP first post (just to be sure) and try again (make sure you follow all the steps)
if it is still not working maybe you are on another model? (m5c5 or c6j7 etc)
Click to expand...
Click to collapse
Thanks ionioni for your support,
I try again downloadin the file & the edited script at the top of this post. everything seems Ok on the PC side, but on the tablet nothing happens after the error message, no mention of a flashing bios, and after 2 minutes, the tablet shutdown, and if I switch it on, go back to the red logo. I never see the bios flash tool display
If you can do something,
You will find here the version of my bios as I get from the Mirek tool, just zipped afterwards
Cheers
florent.m said:
Thanks ionioni for your support,
I try again downloadin the file & the edited script at the top of this post. everything seems Ok on the PC side, but on the tablet nothing happens after the error message, no mention of a flashing bios, and after 2 minutes, the tablet shutdown, and if I switch it on, go back to the red logo. I never see the bios flash tool display
Click to expand...
Click to collapse
i don't know what can i do, there are too many variables and too little details
what are the exact steps you are using? are you doing all this from dnx mode?
try and boot in droidboot(fastboot) mode using (from dnx mode)
fastboot flash osloader efilinux.efi
fastboot boot doridboot.img the droidboot.img file can be found in your stock rom
if you can boot in droidboot mode send me the droidboot.img file you used
again this is working at least on the c5j8 that @blackbile is using (confirmed with the pictures too), maybe others can confirm if they have used it
florent.m said:
All,
Thanks a lot for your contributions, they are always of great quality, and that's a pleasure.
with a special thanks to mirek190 & ionioni .:good: :good:
by the way,
I'm trying to flash back my bios on my C5J8. tablet (brand new from christmas.......)
I was trying to flash 2.5 bios using Mirek 7.0......then I'm now in Bootloop(Red Logo) (((
so I'm trying to follow the above procedure....but I get this error:
everything fine on the pc side,
but I get that on the tablet side,
EFILINUX [ 0.000462] ERROR[get_parth:334] couldn't find boot device handle
then I can restart to the red logo ((
If needed I still have saved my original bios using mirek tool.
So Please could you help me?
Thanks a lot,
best regards,
Florent
Click to expand...
Click to collapse
.
i have exactly same problm
how did you solve it.??
and where is the link for the restoring tool??
Hi guys.
I have been trying to get the HS-USB diag/modem ports enabled on my newly acquired HTC One Mini 2.
I read on the internet that i would have to root the device in order to accomplish this.
So I decided to give it a go!
> I have HTC Sync Manager installed on my Windows 10 PC
> I downloaded the TWRP recovery image
> I downloaded SuperSU
> I successfully unlocked the bootloader
> I installed TWRP Recovery like so:
in command prompt i typed - fastboot flash recovery twrp-2.8.7.0-m4.img <Enter>
sending 'recovery' (11460 KB)...
OKAY [ 1.448s]
writing 'recovery'...
OKAY [ 0.492s]
finished. total time: 2.103s
This is where it gets confusing. According to the instructions i am supposed to highlight Bootloader on the device and select Power. But on the device i am still in the Bootloader menu and there is no option for BOOTLOADER. Therefore i am not able to boot into TWRP.
All i see on the device is the following:
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER>
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
What do i do now? There is no option for BOOTLOADER and cannot boot into TWRP.
Not sure if I am searching using the right words, but I checked the forum and cannot find a solution.
Any help would be appreciated.
Thank you.
bashme said:
Hi guys.
I have been trying to get the HS-USB diag/modem ports enabled on my newly acquired HTC One Mini 2.
I read on the internet that i would have to root the device in order to accomplish this.
So I decided to give it a go!
> I have HTC Sync Manager installed on my Windows 10 PC
> I downloaded the TWRP recovery image
> I downloaded SuperSU
> I successfully unlocked the bootloader
> I installed TWRP Recovery like so:
in command prompt i typed - fastboot flash recovery twrp-2.8.7.0-m4.img <Enter>
sending 'recovery' (11460 KB)...
OKAY [ 1.448s]
writing 'recovery'...
OKAY [ 0.492s]
finished. total time: 2.103s
This is where it gets confusing. According to the instructions i am supposed to highlight Bootloader on the device and select Power. But on the device i am still in the Bootloader menu and there is no option for BOOTLOADER. Therefore i am not able to boot into TWRP.
All i see on the device is the following:
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER>
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
What do i do now? There is no option for BOOTLOADER and cannot boot into TWRP.
Not sure if I am searching using the right words, but I checked the forum and cannot find a solution.
Any help would be appreciated.
Thank you.
Click to expand...
Click to collapse
that is the BOOTLOADER.:silly:
to enter TWRP
go to HBOOT then enter RECOVERY
if not entering then its messed up . flash it again with new file or try different version.
+1 to Ktivity, you are already in bootloader, with losts of stuff ya shouldnt mess with, just click Hboot, then recovery.
BTW, what is the simlock option for, does that lock the sim??, scared to press it lmao.
gazza35 said:
+1 to Ktivity, you are already in bootloader, with losts of stuff ya shouldnt mess with, just click Hboot, then recovery.
BTW, what is the simlock option for, does that lock the sim??, scared to press it lmao.
Click to expand...
Click to collapse
It does not do anything unless you have just the correct files in your SD card that define the network and so on. Only service centers and network providers have such files.
Silly me lol
I selected HBOOT then RECOVERY but it goes back to the bootloader menu??
I have already re-flashed it. I guess i will have to find another file to flash.
Thanks for the advice guys
OK guys.
I flashed a different version of TWRP img file and it still does not boot into TWRP?
I noticed something else. When i select HBOOT, for around a two seconds several lines of info are displayed:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
I pasted a copy of the TWRP img file in the root of my SD card. But still it comes back to Bootloader??
Not sure what to do now?
Any advice guys, please?
Hi guys.
Still not able to load into TWRP. I briefly get the following info:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
Can anyone help please?
Cheers.
bashme said:
> I installed TWRP Recovery like so:
in command prompt i typed - fastboot flash recovery twrp-2.8.7.0-m4.img <Enter>
Click to expand...
Click to collapse
You are flashing the wrong recovery. Considering the m4 at the end of the image name, this is for the One Mini not the One Mini 2. Which is why you are not able to boot into TWRP.
Get the correct image from here
Hi csoulr666.
Thank you for your reply.
I downloaded the image from the link you kindly provided - recovery-twrp-2.8.5.0.img
When i issue the command fastboot boot recovery-twrp-2.8.5.0.img i get the following response
downloading 'boot.img'...
OKAY [ 1.489s]
booting...
OKAY [ 0.004s]
finished. total time: 1.499s
Then the device reboots into the standard htc home screen and NOT into twrp. At this point the USB cable is still attached to the device and PC. Not sure if this has any bearing on the normal boot??
I performed the above steps several times, but still the device boots up to htc home screen and not twrp.
In bootloader, i also selected HBOOT, i briefly get the following info:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
i then select RECOVERY, however the device stays in bootloader??
Very frustrating to say the least.
Am i missing something else?
Thanks for the advice up until now.
P.S please excuse me, i am a newbie so not that much familiar with rooting.
Cheers.
bashme said:
SD Checking...
No gift file...
Loading...[0P8BDIAG.zip]
No image!
Loading...[0P8BDIAG.nbh]
No image or wrong image!
Loading...[0P8BIMG.zip]
Loading...[0P8BIMG.nbh]
No image or wrong image!
Click to expand...
Click to collapse
if you dont want keep seeing this just remove SDCard while you performing the actions.
try this recovery instead
its normal the device boot into the rom unless you press the buttons to get into bootloader.
Brilliant.
I finally got into twrp with this recovery provided by kativiti. I have now successfully flashed supersu zip.
Wow that took some doing.
OK so now i need to find a suitable ROM that will help me answer my initial query, Enabling HS USB Diagnostic port. I was able to enable the hs usb diagnostic port on a Samsung just by installing Kies software. But was not able to get the hs usb diagnostic port enabled for several rooted Sony devices. I guess all the custom ROMs will do that?
Anyway I really appreciate the assistance i've had from all you guys.
Cheers and big thank you.
bashme said:
Brilliant.
I finally got into twrp with this recovery provided by kativiti. I have now successfully flashed supersu zip.
Wow that took some doing.
OK so now i need to find a suitable ROM that will help me answer my initial query, Enabling HS USB Diagnostic port. I was able to enable the hs usb diagnostic port on a Samsung just by installing Kies software. But was not able to get the hs usb diagnostic port enabled for several rooted Sony devices. I guess all the custom ROMs will do that?
Anyway I really appreciate the assistance i've had from all you guys.
Cheers and big thank you.
Click to expand...
Click to collapse
not sure what you asking and for what but after a search i found this:
open command prompt and type
adb devices (if your device shows continue)
adb shell
su -c 'setprop sys.usb.config diag,adb'
nothing happened on mine but i don't have HTC drivers installed. All you need in here
Hi kativiti.
Yes, this is exactly the adb setprop command i'm sending but nothing is happening. Usually, after issuing this command in device manager on my windows pc, new ports open up with exclamation marks and then either windows installs the drivers automatically or I have to do it manually. Only then I should see the newly installed HS USB diag port. I also noticed that the setprop command has different variations, therefore i am looking at tweeking the command. Back to the net i go.....
Previously, I was able to enable HS USB diag port using the above adb command on the Xperia Z and Samsung Mini S4. But I've not been able to activate HS USB on Xperia Z3 and now HTC One Mini 2. I was under the impression that if I rooted and flashed a custom rom onto the HTC One Mini 2, all developer features would be automatically available, especially the HS USB diag port??
To compound the misery, after much reading on rooting and flashing for HTC One Mini 2, I flashed cm-NostromoPop-v2.0-20150430-1330-memul.zip and open_gapps-arm-5.0-nano-20160401.zip. Thankfully the device is not bricked. However, now i get the following problems
When accessing Google Play Store - 'Check your connection and try again'
'Google Play Services won't run...' message repeatedly appears
I cannot boot into twrp recovery so that i can flash another rom
I read on the net that installing the wrong GApps file produces the above google problems? Could i have installed the incorrect GApps file?? Not sure how to verify this? Could the rom i installed be incorrect?
And what can i do to get into twrp recovery again? Not even the twrp recovery image i earlier flashed and successfully booted into has helped this time.
I am rigorously searching the net for answers, to no avail thus far.
Ahh the joy of messing with a phone. I'm very tired but will keep trying lol
Any help would be warmly welcomed.
Thanks in advance.
bashme said:
Hi kativiti.
Yes, this is exactly the adb setprop command i'm sending but nothing is happening. Usually, after issuing this command in device manager on my windows pc, new ports open up with exclamation marks and then either windows installs the drivers automatically or I have to do it manually. Only then I should see the newly installed HS USB diag port. I also noticed that the setprop command has different variations, therefore i am looking at tweeking the command. Back to the net i go.....
Click to expand...
Click to collapse
Start again...
first clear cache
fastboot erase cache
then flash recovery again.
Make sure that you get ROMs from official sources.
kativiti said:
Start again...
first clear cache
fastboot erase cache
then flash recovery again.
Make sure that you get ROMs from official sources.
Click to expand...
Click to collapse
OK so i cleared the cache through adb (fastboot erase cache)
i then successfully flashed twrp recovery. However, instead of the device rebooting to twrp recovery, all i see on the device is the cyanogenmod icon with a circle gradually appearing and disappearing around it.
I have attached a number of photos in sequence (DSC_000009.jpg, DSC_000010.jpg, DSC_000011.jpg, DSC_000012.jpg) showing the circle around the cyanogenmod icon.
Why has this cyanogenmod icon appeared? Is cyanogenmod updating? Or is the device bricked?
Also, is this the link for the official downloads - https://wiki.cyanogenmod.org/w/Devices
Appreciate your advice please.
Thanks again.
bashme said:
OK so i cleared the cache through adb (fastboot erase cache)
i then successfully flashed twrp recovery. However, instead of the device rebooting to twrp recovery, all i see on the device is the cyanogenmod icon with a circle gradually appearing and disappearing around it.
I have attached a number of photos in sequence (DSC_000009.jpg, DSC_000010.jpg, DSC_000011.jpg, DSC_000012.jpg) showing the circle around the cyanogenmod icon.
Why has this cyanogenmod icon appeared? Is cyanogenmod updating? Or is the device bricked?
Also, is this the link for the official downloads - https://wiki.cyanogenmod.org/w/Devices
Appreciate your advice please.
Thanks again.
Click to expand...
Click to collapse
you are stuck in bootloop because your ROM is corrupted. Remember you need to use the button to get into bootloader and then recovery.
kativiti said:
you are stuck in bootloop because your ROM is corrupted. Remember you need to use the button to get into bootloader and then recovery.
Click to expand...
Click to collapse
OK i did a little trial and error:
I simultaneously pressed the power and vol down button, however device did NOT boot into bootloader
I then simultaneously pressed the power and vol up button and device rebooted, but then went back into boot loop
Finally i simultaneously pressed power and vol up button and device started to reboot (screen went blank) and i immediately pressed vol down button, now it booted into bootloader
I then selected HBOOT > RECOVERY and it booted back into bootloader
So i decided to flash twrp recovery when in bootloader and again it went into boot loop
Unfortunately i am back to square one - in bootloader
I can now boot only into bootloader and not to normal UI. So i guess the rom is corrupt.
It's probably a silly question - Is there a way to install custom rom through ADB??
Thanks again
bashme said:
OK i did a little trial and error:
I simultaneously pressed the power and vol down button, however device did NOT boot into bootloader
I then simultaneously pressed the power and vol up button and device rebooted, but then went back into boot loop
Finally i simultaneously pressed power and vol up button and device started to reboot (screen went blank) and i immediately pressed vol down button, now it booted into bootloader
I then selected HBOOT > RECOVERY and it booted back into bootloader
So i decided to flash twrp recovery when in bootloader and again it went into boot loop
Unfortunately i am back to square one - in bootloader
I can now boot only into bootloader and not to normal UI. So i guess the rom is corrupt.
It's probably a silly question - Is there a way to install custom rom through ADB??
Thanks again
Click to expand...
Click to collapse
you can use ADB push but you need TWRP for that.
kativiti said:
you can use ADB push but you need TWRP for that.
Click to expand...
Click to collapse
OK so after much fretting i managed to get my device working.
I managed to boot into bootloader and then flashed an earlier version of twrp and it immediately booted into recovery.
From here i wiped cache, system...... and then installed CM12 with corresponding GApps.
Device now working...PHEW!
OK so now back to trying to get HS USB port activated using ADB commands, which i am trawling the net to find. I just don't understand why it is possible to activate HS USB port in Windows for Samsung and Sony, but not on this HTC One Mini 2?? The ADB setprop command you listed earlier is usually the one that triggers windows to open up the HS USB Diagnostics port, but it is not happening with this HTC One Mini 2? Anyway, i'll keep checking the net.
I have added an image just to show what it is i am trying to activate - Qualcomm HS USB Diagnostics Interface Port
Once again many thanks for your assistance kativiti.
reserved
So this is my problem
i tried to install Xposed installer and ****ed up
at the end i wiped everything on my phone using twrp
and then (like a total idiot) i flasht the wrong boot.img and recovery.img
my phone now only can boot into rescue mode ( which is useless) and fastboot mode
NOW THE BIGGEST PROBLEM
i cant falsh anything using fastboot and i tried every driver i could find
apperently it must be a special fastboot 2.0 driver
thast btw the same ways my device is listet in device manager in windows 7
PLZZZZZZZ Help
ladres said:
So this is my problem
i tried to install Xposed installer and ****ed up
at the end i wiped everything on my phone using twrp
and then (like a total idiot) i flasht the wrong boot.img and recovery.img
my phone now only can boot into rescue mode ( which is useless) and fastboot mode
NOW THE BIGGEST PROBLEM
i cant falsh anything using fastboot and i tried every driver i could find
apperently it must be a special fastboot 2.0 driver
thast btw the same ways my device is listet in device manager in windows 7
PLZZZZZZZ Help
Click to expand...
Click to collapse
normaly i would say "you fu***** it up because you didn´t read the other threads before you do some random s***" but i´m not going to write it today.
There are no special drivers for fastboot. the "Minimal ADB & Fastboot" package has everything needed.
If you phone isn´t recognized as android device:
- delete the drivers in the device-manager from windows. (Sometimes a restart solve problems)
- disconnect your phone from the computer first.
- boot your phone into fastboot mode.
- reconnect it.
then you should be able to flash via fastboot.
If fastboot shows something like "command not allowed", your device is probably FRP locked right now.
Tuerkay said:
normaly i would say "you fu***** it up because you didn´t read the other threads before you do some random s***" but i´m not going to write it today.
There are no special drivers for fastboot. the "Minimal ADB & Fastboot" package has everything needed.
If you phone isn´t recognized as android device:
- delete the drivers in the device-manager from windows. (Sometimes a restart solve problems)
- disconnect your phone from the computer first.
- boot your phone into fastboot mode.
- reconnect it.
then you should be able to flash via fastboot.
If fastboot shows something like "command not allowed", your device is probably FRP locked right now.
Click to expand...
Click to collapse
well the FRP locked is absolutly true do you know how i can unlock it ?
btw when i uninstall the fastboot driver for my phone and reconnect it only says
driver not found
thx for replay
ladres said:
well the FRP locked is absolutly true do you know how i can unlock it ?
btw when i uninstall the fastboot driver for my phone and reconnect it only says
driver not found
thx for replay
Click to expand...
Click to collapse
you have to search the drivers manualy. path should be minimal adb folder.
the frp unlock can be removed vie developer settings but you can´t access them.
which boot.img and recovery.img did you flash? if it´s from a mate s rom, then it shouldn´t affect your phone.
you could also try something else. take a micro sd card. place the dload folder with your current update.app in it. then boot your phone with vol+ (or vol + and vol-) and power. it then should do an force update.
Tuerkay said:
you have to search the drivers manualy. path should be minimal adb folder.
the frp unlock can be removed vie developer settings but you can´t access them.
which boot.img and recovery.img did you flash? if it´s from a mate s rom, then it shouldn´t affect your phone.
you could also try something else. take a micro sd card. place the dload folder with your current update.app in it. then boot your phone with vol+ (or vol + and vol-) and power. it then should do an force update.
Click to expand...
Click to collapse
I have a CRR L09
I restored everything using a twrp backup from a CRR L00 version
and since i wante to keep my hand off root and everything i decidet to falsh the boot.img and recovery.img
that i extracted from an original UPDATE.APP
i did that all with falshify
btw it seems that i have the right fastboot driver but fastboot wont let me falsh
eaven tho i falshed befor without FRP Unlock
and just so you know
i have sam os x and windows 7 and both give me the same error
lols-Mac-Pro:~ lol$ fastboot devices
UBE0215923001497 fastboot
lols-Mac-Pro:~ lol$ fastboot flash recovery /Users/lol/Desktop/recovery-B303.img
target reported max download size of 471859200 bytes
sending 'recovery' (28226 KB)...
OKAY [ 0.596s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.596s
lols-Mac-Pro:~ lol$
ladres said:
I have a CRR L09
I restored everything using a twrp backup from a CRR L00 version
and since i wante to keep my hand off root and everything i decidet to falsh the boot.img and recovery.img
that i extracted from an original UPDATE.APP
i did that all with falshify
btw it seems that i have the right fastboot driver but fastboot wont let me falsh
eaven tho i falshed befor without FRP Unlock
and just so you know
i have sam os x and windows 7 and both give me the same error
lols-Mac-Pro:~ lol$ fastboot devices
UBE0215923001497 fastboot
lols-Mac-Pro:~ lol$ fastboot flash recovery /Users/lol/Desktop/recovery-B303.img
target reported max download size of 471859200 bytes
sending 'recovery' (28226 KB)...
OKAY [ 0.596s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.596s
lols-Mac-Pro:~ lol$
Click to expand...
Click to collapse
well... i already wrote it in other threads that using an twrp backup, which is not yours can FRP lock you device. since you can´t boot your device, you also can´t remove the FRP lock. with the FRP Lock you can´t flash any files.
so you need an uncorrupted TWRP backup from someone with the same mate s model you have.
if you´re on stock recovery, try what i wrote the last post. Place dload folder with the Update.app for you model on an sd card and boot into update mode with VOL+ (and VOL- depending on the recovery version) and Power button at the same time.
Tuerkay said:
well... i already wrote it in other threads that using an twrp backup, which is not yours can FRP lock you device. since you can´t boot your device, you also can´t remove the FRP lock. with the FRP Lock you can´t flash any files.
so you need an uncorrupted TWRP backup from someone with the same mate s model you have.
if you´re on stock recovery, try what i wrote the last post. Place dload folder with the Update.app for you model on an sd card and boot into update mode with VOL+ (and VOL- depending on the recovery version) and Power button at the same time.
Click to expand...
Click to collapse
no the werid thin is
when i restored the twrp backup it actually booted thats when i tried to falsh the stock recovery and boot image
and i already tried with the hardware buttons
Vol+ gets me to Huawei eRecovery (tries to download firmware over wifi but failes)
Vol- gets me to fastboot mode
and btw that only works when i turn the phone off and hold the button and connect the usb cable
without the cable i automaticly get into rescue mode
with eiter
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed!)
or
Error!
Func NO : 11 (boot image)
Error NO : 2 (load failed!)
You have Ton press vol+ and vol- and power button all at the same time with the cable Unplugged. If you have an Update.App on your SD Card it will automatically Start the process without asking any questions.
Tuerkay said:
You have Ton press vol+ and vol- and power button all at the same time with the cable Unplugged. If you have an Update.App on your SD Card it will automatically Start the process without asking any questions.
Click to expand...
Click to collapse
i already tried that it only takes me to rescue mode
ladres said:
i already tried that it only takes me to rescue mode
Click to expand...
Click to collapse
with how much % does it fail and which reason does it show?
Tuerkay said:
with how much % does it fail and which reason does it show?
Click to expand...
Click to collapse
i get eiter
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed!)
or
Error!
Func NO : 11 (boot image)
Error NO : 2 (load failed!)
an thats it
can you make a photo of the screen this message appears?
it looks like you haven´t done what i have said since these aren´t messages which appear in the update mode.
Here you go
Sent from my HTC One using XDA Free mobile app
ladres said:
Here you go
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
well i don´t know where to start. just give an short explanation about the Huawei Recovery system.
The Huawei Mate S hast 2 ("TWO") recoverys installed. Recovery.img and Recovery2.img. just for safety reason if someone or something f***s up the primary recovery.img (first recovery). the first one is also the one you normaly swap with the TWRP backup.
The Huawei Mate S can be booted in 4 ("four") different modes
1. normal boot into android
2. boot into fastboot&rescue mode
3. boot into reset mode (twrp recovery if you swap recovery.img)
4. boot into update mode
you can reach menu 2-4 with vol+ and/or vol-. As long as you haven´t replaced bot recovery images. the button combinations vary depending on the flashed recovey(2).img version.
mode 4 only starts if you have an FULL UPDATE file in an dload folder in your internal or sd storage.
the update mode is the one that takes up to 30 seconds to start after the vibration. Keep holding the associated buttons and the power button until the device vibrates. then relase the powerbutton but keep holding the other buttons. then wait. after a while a cirlce with "EMUI update" will appear and install the update file you placed into the dload folder.
this method worked for me when i f****ed up and i also found some other thread with the same problem you have. did the same thing i just explained
Tuerkay said:
well i don´t know where to start. just give an short explanation about the Huawei Recovery system.
The Huawei Mate S hast 2 ("TWO") recoverys installed. Recovery.img and Recovery2.img. just for safety reason if someone or something f***s up the primary recovery.img (first recovery). the first one is also the one you normaly swap with the TWRP backup.
The Huawei Mate S can be booted in 4 ("four") different modes
1. normal boot into android
2. boot into fastboot&rescue mode
3. boot into reset mode (twrp recovery if you swap recovery.img)
4. boot into update mode
you can reach menu 2-4 with vol+ and/or vol-. As long as you haven´t replaced bot recovery images. the button combinations vary depending on the flashed recovey(2).img version.
mode 4 only starts if you have an FULL UPDATE file in an dload folder in your internal or sd storage.
the update mode is the one that takes up to 30 seconds to start after the vibration. Keep holding the associated buttons and the power button until the device vibrates. then relase the powerbutton but keep holding the other buttons. then wait. after a while a cirlce with "EMUI update" will appear and install the update file you placed into the dload folder.
this method worked for me when i f****ed up and i also found some other thread with the same problem you have. did the same thing i just explained
Click to expand...
Click to collapse
ok first of all the for all you help so far
secendly i did not whipe the recovery2 file since i never had the option
method 4 didnt work but maybe ist because my micro sd card is in exfat mode
ill try fat32
and one thing i havent mentiond yet is that i cant turn my phone off
i also only can enter fastboot and Huawei eRecovery mode by pressing the volume buttons and then plug the
phone into my computer
ladres said:
ok first of all the for all you help so far
secendly i did not whipe the recovery2 file since i never had the option
method 4 didnt work but maybe ist because my micro sd card is in exfat mode
ill try fat32
and one thing i havent mentiond yet is that i cant turn my phone off
i also only can enter fastboot and Huawei eRecovery mode by pressing the volume buttons and then plug the
phone into my computer
Click to expand...
Click to collapse
you don´t need to power it off. you can also reboot into the updatemenu from fastboot menu. just hold all buttons long enough and wenn the screen goes black, release the powerbutton after vibration.
sd card musst be fat32 i think
Tuerkay said:
you don´t need to power it off. you can also reboot into the updatemenu from fastboot menu. just hold all buttons long enough and wenn the screen goes black, release the powerbutton after vibration.
sd card musst be fat32 i think
Click to expand...
Click to collapse
didnt work
sd card is in fat32
i tried it exsactly like you toled me
and it took me to rescue mode again
btw the Vol up and vol down methoid used to take me to twrp
ive never seen the upadte mode
can you do an factory reset in the eRecovery?
if not, try
fastboot erase userdata
fastboot erase cache
in fastboot&rescue mode.
it´s possible that there is an incremental update file in your internal storage.
which update. app did you use? should be the last working version you used.
Tuerkay said:
can you do an factory reset in the eRecovery?
if not, try
fastboot erase userdata
fastboot erase cache
in fastboot&rescue mode.
it´s possible that there is an incremental update file in your internal storage.
which update. app did you use? should be the last working version you used.
Click to expand...
Click to collapse
eRecovery is aperently just for falshing using huawei server
but mate s seems not to be supportrd
fastboot gives me the same error as usual
sh-3.2# fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2# fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2#
i tride B115
and B114
ladres said:
eRecovery is aperently just for falshing using huawei server
but mate s seems not to be supportrd
fastboot gives me the same error as usual
sh-3.2# fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2# fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
sh-3.2#
i tride B115
and B114
Click to expand...
Click to collapse
CRR-UL00 or L09?
the eRecovery differs depending on the version used. i for example can factory reset via eRecovery.
It´s also strange that you can´t access the force update mode. this is an basic function you can´t erase.
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
oppili said:
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
Click to expand...
Click to collapse
Yes, im sure. On bootloader mode is in red color - Phone unlocked, but i not using Linux, im on Windows 7 and this not help me....
Try fastboot oem unlock - command again.
If still not works, try fastboot erase of that *.img file before flashing that new img file.
oppili said:
Try fastboot oem unlock - command again.
When i try this command...
c:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.004s]
finished. total time: 0.006s
If still not works, try fastboot erase of that *.img file before flashing that new img file.
Click to expand...
Click to collapse
I know about this but im above when i try erase all after this fastboot send me "Failed..." and i will be have dead phone, tell me - when i try erase command for all partitions - will be phone work wit fastboot after this??
THX
Are you the only user in pc ? Do you have admin rights ?
or
try any other pc
or
use Ubuntu OS
Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
thilak devraj said:
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
Click to expand...
Click to collapse
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
then you should take it to the service center. the only best thing you can do now..
Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
erase cache command is blocked by huawei in fastboot irrespective of locked or unlocked state. somewhere i read unlock lost permissions after update. if you have not tried unlock after update try it. driver can also be an issue, install hisuite it comes with drivers.
Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
shady143 said:
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
Click to expand...
Click to collapse
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
zzztidurvirus said:
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
Click to expand...
Click to collapse
First...many thanks for your interest!
Look, about bootloader, on boot mode is in red PHONE UNLOCKED, i try this command in fastboot:
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot oem backdoor info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ -0.000s]
finished. total time: -0.000s
so what is FB Lockstate??Is my bootloader unlocked or locked??
Here is another command which i try....
C:\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
Cant derermine partition type - is this problem?
I also try this....
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 1.033s]
finished. total time: 1.831s
C:\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
It seems that fastboot write recovery (with your help i need use admin rights now this work) but i still cant boot to recovery no matter how...
I can also flash and backup boot and recovery via Flashify or Rashr and when i open backup with HEX editor it seems that i succesfully upload TWRP but still cannot acess TWRP recovery....
This is all what i try in this time, of course i read your help words about Huawei extractor etc. but not try at this time, i hope i explain more detailed my problem. Look im not a newbie, i allready flash etc. my Lenovo and P9 lite what i have here but not understand where can be problem in this Honor 4x, it seems like corrupted recovery partition or can be problem in read only/write partition - i play with this option before....
anyway - run as admin - this help me a lot i think, THX and wait your answer.
EDIT: one thing, you think that when i try flash stock recovery (i can, no problem of course) it will be work?
Update: Big success, i just try flash stock recovery B064b and now im in stock recovery menu, im surprised but what now? I want update to Marshmallow 6.0....?
But in stock recovery is: phone and the data cannot be recovered. Continue?
Oh sorry, this is about "not sd card inserted" problem
What will now progress? I have inside B130 firmware and want Marshmallow, also TWRP recovery must i flash now especially for B130 firmware for work?
Update: Yes, all working now, factory reset, recovery etc. you help me a lot, only if you can tell me what number of firmware must i upload for Marshmallow, thx
Last update: So finally, coz im too hurry and dont want wait for your answer :angel:, i just upload from local update first Android 5.1.1. after this 6.0 and all is perfect and working!
My big thanks and kisses goes to you zzztidurvirus, im lucky and still cant beleive that all works, again thx!!
I did once on Win to revert back to Stock from CM12.1 by using img from update.app file. For my case, it's the MM update.app not working, I couldn't flash img files into phone, then I tried to flash files from LP, it worked. I boot into LP ROM and update from there to MM.
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
I had faced same issue but get back by using the that method.
Sumea said:
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Click to expand...
Click to collapse
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Lulu_568 said:
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Click to expand...
Click to collapse
Sadly not, as I tried both running ADB fastboot as admin from administrator command line and I tried three different recovery images from huawei, 6.0 (because the flash went bad during attempt to flash a 4.1EMUI with 6.0 B506 ROM for CHE2-L11) - And it keeps denying the write attempt with the same message. More info on the flash: I tried to TWRP flash from 5.1 rom to the EMUI4.1 6.0 ROM following guide someone made with updateappflasher.zip or something, during the flash the phone just crashed 60% in the bar and after that the phone is boot looping into recovery but it can't do anything. Like said any attempt to flash a stock rom even if a recovery seems to exist when booting VOL+ & POWER at the same time, but it will fail if attempting to do wipe data/factory reset in 40% mark. Forced updater can also be accessed but again, thanks to the firmware situation the phone is in it does not flash anything beyond 5% without crashing and being stuck or just giving an error message outright.
Only thing I might have not have is the right kind of ADB drivers but googling about CHE2-L11 I really cannot find a ADB drivers for this phone for life of me and dealing with windows 10 these days makes it worse. At least it used to be that I was with windows 7, back when I myself unlocked the bootloader of the phone and rooted it myself, I have some memory of that being harsh to deal with too, as I had hard time getting drivers that worked right with the phone etc.
I will check into this... At this point my friend bought a new phone already but I still will try to fix the phone for him since I feel personally pretty bad for pretty big mess I made.
I will also try this with a windows XP machine I have still, it is meant entirely for different things but at times like these it is somewhat nice to have a XP around. At least the darn driver problems are not a problem.
UPDATES:
I unbricked the phone. The stock recovery was intact enough for just a normal dload install of a update.app from huawei - why it did not initially work was probably the USB connection to computer and/or 64gig microSD card my friend had, not being compatible with Huawei's recovery updater. I myself had a 8gig card around which worked and I restored the phone ultimately to a 6.0 official ROM. I also went ahead to root it - and final find really was that the reason why recovery etc. would not flash, was because I wrote "fastboot flash RECOVERY twrp.img" - instead of "fastboot flash recovery twrp.img" - the latter works, and the all caps for "RECOVERY" results in illegal command error - and it was no bigger than that.
Meanwhile even after sorting this all out my friend already ended up buying a new phone so it hurts but I hope some other people find some info here useful.
THIS IS NOT GUARANTEED TO WORK! If it does not work, feel free to let me know here and i will do what i can to help, but remember I probably can't help everyone.
IMPORTANT: ON XDA-LABS APP THIS POST IS KINDA BROKEN IDK WHY SO LOAD IT IN BROWSER!!!!
If the guide worked for you, please hit thanks button! If you are generous and want to donate pm me
What this can fix:
When booting, you get this error:
Func NO : 10 (boot image)
Error NO : 2 (load image)
When booting to recovery, you get this error:
Func NO : 11 (recovery image)
Error NO : 2 (load image)
Bootloops
Can't boot into fastboot
Can't boot into recovery for other reasons
Can't boot to system for other reasons
ETC...
First thing first, there really isnt a way to keep your data so expect it all to be gone, unless it is saved on an external sd card. Also, this guide is specifically for the PRA-LX1 model, however it might work with other p8 lite 2017 models and a similar method may work with other huawei phones.
Requirements:
The device boots in to fastboot mode. (If it does not, scroll down to problem 1)
You have a pc with a usb port and fastboot/adb installed
You have a micro usb to usb cable.
Unlocked bootloader and oem unlock.
Micro sd card
Problem 1: Can't boot into fastboot?
Try this:
1. Make sure device is fully powered off
2. Connect device to any pc.
3. Press and hold volume- and power button at the same time until your screen turns on.
If this doesn't work then unfortunately i can't help...
Problem 2: Only fastboot boots, but not recovery or os:
Lets start by flashing TWRP...
If your device was on android nougat (7.x.x) or the rom you were flashing was nougat based then do this:
Download this file:
https://drive.google.com/file/d/1TjNHI9FNdwQS2HphsjGfQCHKephibiKn/view
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery *Nameofrecovery.img*
-----------------------------------------------------------------------------------------------------------------
If your device was on android oreo (8.x.x) or the rom you were flashing was oreo based then do this:
Download this file: https://drive.google.com/file/d/190zqju8ZmwZCzI4WXtujgKLFXvvuWTk8/view?usp=sharing
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery_ramdisk *Nameofrecovery.img*
https://www.mrviking.co.uk/440246340
Problem 3: You can only boot into fastboot and TWRP recovery:
Thats OK! Heres how to restore the phone:
IMPORTANT: THE FILES LINKED HERE ARE ONLY FOR PRA-LX1 DEVICES! If your device has a different model number, or these files did not work for you, follow this guide to get files for your device: https://www.mrviking.co.uk/440246340
This will also update your device to android oreo!
Put the micro sd card in your pc.
On your pc download these files:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279 (Download 0.3)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1194/g104/v148634/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...altice_all/update_full_PRA-L11_altice_all.zip
http://update.hicloud.com:8180/TDS/...34/f1/full/public/update_data_full_public.zip
Now Rename update_full_PRA-L11_altice_all.zip to update_all_hw.zip
Also rename update_data_full_public.zip to update_data_public.zip
Put all four files: update.zip, update_all_hw.zip, update_data_public.zip and HuRUpdater_0.3.zip into one folder on the external sdcard.
Take sdcard out of pc and put it into phone.
Boot into twrp tap on mount and select all partitions
Make sure 'mount system read only' is NOT checked.
Go back to twrp home
Go to install, find the huruupdater zip file
Flash ONLY hurupdater, DO NOT FLASH ANY OTHER ZIPS.
Follow instructions on screen.
Reboot to system and wait for the device to boot.
If it didnt boot, dont worry:
Go back to fastboot mode on your phone and pc, and download this file: https://drive.google.com/file/d/1daIos0yagHk9Kg-5hXLDwNYDHjP_N0EM/view?usp=sharing
Flash it with fastboot using:
fastboot flash recovery_ramdisk *Nameofrecovery.img*
now boot into recovery wipe cache wipe date/factory reset reboot to system
If none of this worked, try this last resort. (Likely won't work but it is worth a shot)
Firstly, place your micro sdcard into your pc. Create a folder called 'dload' in the root of it.
Now, locate the firmware files you downloaded from firmware finder.
Open the main update.zip file and extract the 'UPDATE.APP' file to the 'dload' folder in your sdcard.
Place sdcard back in phone
Make sure phone is powered off. (Can't power it off? Unplug anything connected (charger, pc, etc...) and hold the power button until screen goes black)
Hold all three function keys (VOL+,VOL- and POWER) until screen turns on.
Hope it works and wait
If it worked, please hit thanks button! If you want to donate pm me.
If it DID NOT work, post a reply here and either me or someone else will try and help.
Thanks!
tringo24 said:
I've got the same problem - I can boot to TWRP and bootloader.
I've wiped Dalvik/ART Cache, Cache, Data, System and formatted Data
When I try to flash HuRUpdater_0.4.zip I get:
Error finding input device
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/HuRUpdater_0.4.zip'
I've tried copying UPDATE.APP to 'dload' folder on external SD card, and EMUI hangs at 5%.
Is there anything else I can try? What does "Updater process ended with ERROR: 1" actually mean? I've googled it but haven't found anything useful.
Any help would be really appreciated!
Click to expand...
Click to collapse
Top tip - always follow all of the instructions. the version of TWRP listed in the instructions is the only one to use. I was using an incomaptible version. My phone if fixed!
tringo24 said:
I've got the same problem - I can boot to TWRP and bootloader.
I've wiped Dalvik/ART Cache, Cache, Data, System and formatted Data
When I try to flash HuRUpdater_0.4.zip I get:
Error finding input device
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/HuRUpdater_0.4.zip'
I've tried copying UPDATE.APP to 'dload' folder on external SD card, and EMUI hangs at 5%.
Is there anything else I can try? What does "Updater process ended with ERROR: 1" actually mean? I've googled it but haven't found anything useful.
Any help would be really appreciated!
Click to expand...
Click to collapse
Always use TWRP from OP
And if its not working, try Flashing Stock recovery and boot it and do tap some options e.g. reset/ clear cache etc. ( I got my mobile fixed via this method as Internal Memory got corrupted because of incompatible TWRP )
For problem 1 fix : Fully shutdown , connect the phone to via usb to pc , and fast hold down the volume - . Cheers
Edit : or the same : usb , power and volume - till you see the huawei logo , then just hold volume -
Frp and boot locked. dload/UPDATE.APP in fat32 formatted sd still error At 5%. Any way to recovery?
Thank you !!!
You saved my phone :victory:
lupastro82 said:
Frp and boot locked. dload/UPDATE.APP in fat32 formatted sd still error At 5%. Any way to recovery?
Click to expand...
Click to collapse
Force shut down the device (Hold power button) if it is on.
Connect to a pc
Hold down POWER and VOL- buttons untill screen turns on
If you see a screen with an android robot saying FASTBOOT at the top let me know, if not tell me that :good:
MrViking said:
Force shut down the device (Hold power button) if it is on.
Connect to a pc
Hold down POWER and VOL- buttons untill screen turns on
If you see a screen with an android robot saying FASTBOOT at the top let me know, if not tell me that :good:
Click to expand...
Click to collapse
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
lupastro82 said:
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
Click to expand...
Click to collapse
I'm exactly in ur same situation
I need ****ing help to unlock frp then i can solve the rest by my own.
lupastro82 said:
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
Click to expand...
Click to collapse
Have you tried flashing stock recovery img from fastboot?
MrViking said:
Have you tried flashing stock recovery img from fastboot?
Click to expand...
Click to collapse
i can try, but i think cannot work if frp is locked :/
atm, now, on boot i see advice for unlocked bootloader, then access to erecovery (but also if i fix dns with firmware finder dns and check firmware, still failed - and no reset etc).
if i reboot/power on with volume down > green robot with:
Code:
Attention!
Please update system again
Error NO : 10 (boot image) / or
Error NO : 2 (load failed)
if i reboot/power on with both volume button, check dload recovery, but still failed (damned huawei!!!).
now i check to work via fastboot. thanks.
---
[email protected]:~$ sudo $(which fastboot) flash recovery ./Scrivania/twrp-3.2.1-0-twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (4690 KB)...
OKAY [ 0.152s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.158s
[email protected]:~$ sudo $(which fastboot) oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
[email protected]:~$
[email protected]:~$ sudo $(which fastboot) flash recovery_ramdisk ./Scrivania/recovery.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (11204 KB)...
OKAY [ 0.362s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.369s
[email protected]:~$ sudo $(which fastboot) boot ./Scrivania/recovery.img
downloading 'boot.img'...
OKAY [ 0.378s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.381s
[email protected]:~$
Click to expand...
Click to collapse
lupastro82 said:
i can try, but i think cannot work if frp is locked :/
atm, now, on boot i see advice for unlocked bootloader, then access to erecovery (but also if i fix dns with firmware finder dns and check firmware, still failed - and no reset etc).
if i reboot/power on with volume down > green robot with:
Code:
Attention!
Please update system again
Error NO : 10 (boot image) / or
Error NO : 2 (load failed)
if i reboot/power on with both volume button, check dload recovery, but still failed (damned huawei!!!).
now i check to work via fastboot. thanks.
---
Click to expand...
Click to collapse
Wow thats a pretty bad brick. First try to boot to recovery like this:
1. Make sure phone is off.
2. Hold power and volume up until screen goes on.
3. When screen goes on quickly take fingers off buttons.
If it does not work, I think your only hope is to use funky huawei.
Do what this guy did (read the bottom of the first post)
https://forum.xda-developers.com/honor-7x/development/frp-lock-help-to-unbrick-honor-7x-t3769345
lupastro82 said:
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
Click to expand...
Click to collapse
Can you update to stock through erecovery via wifi? I had my phone frp locked + bl locked + bricked system. eRecovery was the only way out to get into a working system.
The unlock tool that costs too much is b.s and only works if it was locked because of Google Play account (tried it, did not unlock my frp).
After erecovery update and having a system, google play account was also locked because of stock firmware, this time I used the unlock tool. I used firmware finder afterwards for forcing an oreo update (because bl unlocking was grayed out). After oreo update, i enabled bl unlock from dev options and unlocked my bl again through fastboot. frp got unlocked along the way, i forgot when.
i can access in eRecovery, but when i check to download by wifi i still receive: "Getting package info failed" :/
-
via dload (8gb sd in fat 32 with only dload folder and old release UPDATE.APP inside it - but tested with more...) stuck for minuts at 5%, then reboot!
lupastro82 said:
i can access in eRecovery, but when i check to download by wifi i still receive: "Getting package info failed" :/
-
via dload (8gb sd in fat 32 with only dload folder and old release UPDATE.APP inside it - but tested with more...) stuck for minuts at 5%, then reboot!
Click to expand...
Click to collapse
Did you try what I mentioned?
MrViking said:
i can try, but i think cannot work if frp is locked :/
atm, now, on boot i see advice for unlocked bootloader, then access to erecovery (but also if i fix dns with firmware finder dns and check firmware, still failed - and no reset etc).
if i reboot/power on with volume down > green robot with:
Wow thats a pretty bad brick. First try to boot to recovery like this:
1. Make sure phone is off.
2. Hold power and volume up until screen goes on.
3. When screen goes on quickly take fingers off buttons.
If it does not work, I think your only hope is to use funky huawei.
Do what this guy did (read the bottom of the first post)
https://forum.xda-developers.com/honor-7x/development/frp-lock-help-to-unbrick-honor-7x-t3769345
Click to expand...
Click to collapse
sure yes, ill try, and enter in dload mode (but still fail) :/
MrViking said:
THIS IS NOT GUARANTEED TO WORK! If it does not work, feel free to let me know here and i will do what i can to help, but remember I probably can't help everyone.
If the guide worked for you, please hit thanks button! If you are generous and want to donate pm me
What this can fix:
When booting, you get this error:
Func NO : 10 (boot image)
Error NO : 2 (load image)
When booting to recovery, you get this error:
Func NO : 11 (recovery image)
Error NO : 2 (load image)
Bootloops
Can't boot into fastboot
Can't boot into recovery for other reasons
Can't boot to system for other reasons
ETC...
First thing first, there really isnt a way to keep your data so expect it all to be gone, unless it is saved on an external sd card. Also, this guide is specifically for the PRA-LX1 model, however it might work with other p8 lite 2017 models and a similar method may work with other huawei phones.
Requirements:
The device boots in to fastboot mode. (If it does not, scroll down to problem 1)
You have a pc with a usb port and fastboot/adb installed
You have a micro usb to usb cable.
Unlocked bootloader and oem unlock.
Micro sd card
Problem 1: Can't boot into fastboot?
Try this:
1. Make sure device is fully powered off
2. Connect device to any pc.
3. Press and hold volume- and power button at the same time until your screen turns on.
If this doesn't work then unfortunately i can't help...
Problem 2: Only fastboot boots, but not recovery or os:
Lets start by flashing TWRP...
If your device was on android nougat (7.x.x) or the rom you were flashing was nougat based then do this:
Download this file:
https://drive.google.com/file/d/1TjNHI9FNdwQS2HphsjGfQCHKephibiKn/view
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery *Nameofrecovery.img*
-----------------------------------------------------------------------------------------------------------------
If your device was on android oreo (8.x.x) or the rom you were flashing was oreo based then do this:
Download this file: https://drive.google.com/file/d/190zqju8ZmwZCzI4WXtujgKLFXvvuWTk8/view?usp=sharing
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery_ramdisk *Nameofrecovery.img*
https://www.mrviking.co.uk/440246340
Problem 3: You can only boot into fastboot and TWRP recovery:
Thats OK! Heres how to restore the phone:
IMPORTANT: THE FILES LINKED HERE ARE ONLY FOR PRA-LX1 DEVICES! If your device has a different model number, or these files did not work for you, follow this guide to get files for your device: https://www.mrviking.co.uk/440246340
This will also update your device to android oreo!
Put the micro sd card in your pc.
On your pc download these files:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279 (Download 0.3)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1194/g104/v148634/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...altice_all/update_full_PRA-L11_altice_all.zip
http://update.hicloud.com:8180/TDS/...34/f1/full/public/update_data_full_public.zip
Now Rename update_full_PRA-L11_altice_all.zip to update_all_hw.zip
Also rename update_data_full_public.zip to update_data_public.zip
Put all four files: update.zip, update_all_hw.zip, update_data_public.zip and HuRUpdater_0.3.zip into one folder on the external sdcard.
Take sdcard out of pc and put it into phone.
Boot into twrp tap on mount and select all partitions
Make sure 'mount system read only' is NOT checked.
Go back to twrp home
Go to install, find the huruupdater zip file
Flash ONLY hurupdater, DO NOT FLASH ANY OTHER ZIPS.
Follow instructions on screen.
Reboot to system and wait for the device to boot.
If it didnt boot, dont worry:
Go back to fastboot mode on your phone and pc, and download this file: https://drive.google.com/file/d/1daIos0yagHk9Kg-5hXLDwNYDHjP_N0EM/view?usp=sharing
Flash it with fastboot using:
fastboot flash recovery_ramdisk *Nameofrecovery.img*
now boot into recovery wipe cache wipe date/factory reset reboot to system
If none of this worked, try this last resort. (Likely won't work but it is worth a shot)
Firstly, place your micro sdcard into your pc. Create a folder called 'dload' in the root of it.
Now, locate the firmware files you downloaded from firmware finder.
Open the main update.zip file and extract the 'UPDATE.APP' file to the 'dload' folder in your sdcard.
Place sdcard back in phone
Make sure phone is powered off. (Can't power it off? Unplug anything connected (charger, pc, etc...) and hold the power button until screen goes black)
Hold all three function keys (VOL+,VOL- and POWER) until screen turns on.
Hope it works and wait
If it worked, please hit thanks button! If you want to donate pm me.
If it DID NOT work, post a reply here and either me or someone else will try and help.
Thanks!
Click to expand...
Click to collapse
Cheers Bruh Thank u so MUCH
Blackblock92 said:
Cheers Bruh Thank u so MUCH
Click to expand...
Click to collapse
No problem! Glad to hear it works
I've made a tutorial 1 day before you ^^
Hello i've made a tutorial on my thread for my solution to unbrick it so if you need to unbrick your phone with a different method
you can use my tutorial it has worked perfecty on my p8 lite 2017 and now he's on oreo
my phone personnaly was totaly broken i flashed some random things on my phone etc this is working 100% cause you are about to clear all the old android system for the new oreo one so for the peoples who got the same problem than me and got stuck
on the fastboot&rescue mode when VOLUME- + POWER for like 5 seconds with the phone off
(for the peoples who can't power off your device you can download the "universal fastboot and ADB tool" app and then click on reboot phone in the fastboot part)
the solution is to :
-Download the rom stock Oreo android 8.0 stechguide.com/huawei-p8-lite-2017-b370-oreo-firmware/
-exctract all files from the HuaweiUpdateExtractor find it on google it's easy just download update.zip
-extract and put the UPDATE.APP in the HuaweiUpdateExtractor
-run srk tool for huawei
-type 000 and press enter
-and now you have to flash all partitions that you have received from HUE commands are here:
[dont worry if some of theese are not working it's because certains commands are not allowed to use and certains commands are out of date :/ but dont worry the phone will boot correctly after ]
Code:
fastboot flash cache CACHE.img
fastboot flash crc CRC.img
fastboot flash curver CURVER.img
fastboot flash dts DTS.img
fastboot flash efi EFI.img
(i'm not putting erecorery imgs cause we cannot touch them it's an ultimate security from os :) )
fastboot flash fastboot FASTBOOT.img
fastboot flash hifi HIFI.img (only if you are the wifi is not working ;) )
fastboot flash kernel KERNEL.img
fastboot flash modem_fw MODEM_FW.img
fastboot flash modemnvm_update MODEMNVM_UPDATE.img
fastboot flash odm ODM.img
fastboot flash package_type PACKAGE_TYPE.img
fastboot flash product PRODUCT.img
fastboot flash ramdisk RAMDISK.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash sensorhub SENSORHUB.img
fastboot flash system SYSTEM.img
fastboot flash teeos TEEOS.img
fastboot flash trustfirmware TRUSTFIRMWARE.img
fastboot flash vbmeta VBMETA.img
fastboot flash vendor VENDOR.img
fastboot flash verlist VERLIST.img
fastboot flash xloader XLOADER.img
Now you have loader all partitions of an huawei p8 lite 2017 android 8.0 gg !
you just have to make a fastboot reboot to reboot your phone and enjoy !
notes:Everything is working properly after 3 day of use not any missing data some calls bugs but nothing hard
you will loose your TWRP recovery mode AND DO NOT INSTALL ONE OF THEM FOR NOW they are outdated for oreo wait some months (september on some sources)
you will loose all your data and the root (some sites prupose root methods for oreo p8 lite 2017 (and soft root this time :laugh:
idk about the bootloader but i keeped my imei number ^^
Thanks for your time and if anyone got questions i'm still here ^^
RedFiredu29!
btw that my first tutorial tell me if it's good ^^
RedFiredu29 said:
Hello i've made a tutorial on my thread for my solution to unbrick it so if you need to unbrick your phone with a different method
you can use my tutorial it has worked perfecty on my p8 lite 2017 and now he's on oreo
my phone personnaly was totaly broken i flashed some random things on my phone etc this is working 100% cause you are about to clear all the old android system for the new oreo one so for the peoples who got the same problem than me and got stuck
on the fastboot&rescue mode when VOLUME- + POWER for like 5 seconds with the phone off
(for the peoples who can't power off your device you can download the "universal fastboot and ADB tool" app and then click on reboot phone in the fastboot part)
the solution is to :
-Download the rom stock Oreo android 8.0 stechguide.com/huawei-p8-lite-2017-b370-oreo-firmware/
-exctract all files from the HuaweiUpdateExtractor find it on google it's easy just download update.zip
-extract and put the UPDATE.APP in the HuaweiUpdateExtractor
-run srk tool for huawei
-type 000 and press enter
-and now you have to flash all partitions that you have received from HUE commands are here:
[dont worry if some of theese are not working it's because certains commands are not allowed to use and certains commands are out of date :/ but dont worry the phone will boot correctly after ]
Now you have loader all partitions of an huawei p8 lite 2017 android 8.0 gg !
you just have to make a fastboot reboot to reboot your phone and enjoy !
notes:Everything is working properly after 3 day of use not any missing data some calls bugs but nothing hard
you will loose your TWRP recovery mode AND DO NOT INSTALL ONE OF THEM FOR NOW they are outdated for oreo wait some months (september on some sources)
you will loose all your data and the root (some sites prupose root methods for oreo p8 lite 2017 (and soft root this time :laugh:
idk about the bootloader but i keeped my imei number ^^
Thanks for your time and if anyone got questions i'm still here ^^
RedFiredu29!
btw that my first tutorial tell me if it's good ^^
Click to expand...
Click to collapse
That's interesting, never heard of that method!
However there are many good working twrps for oreo, especially the one by Dil3mm4.
MrViking said:
That's interesting, never heard of that method!
However there are many good working twrps for oreo, especially the one by Dil3mm4.
Click to expand...
Click to collapse
Yes i love searching for new solutions on this device but i never heard good unbrick methods for this phone
until our methods ^^
If you read this on XDA labs then please load it in the browser as for some reason lots of text is missing in xda labs.
Thanks ?