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.
long story short, my relative came to me for help after he decided to install a new ROM and made a simple error of forgetting about the OEM unlock option in the settings menu beforehand. an error occurred along the way and he tried to go back to stock. now when the phone boots it goes into the bootloader (which is locked) and gives a start up failed message saying to use Software Repair Assistant.
trying to go into recovery gives a
Code:
AP Fastboot Flash Mode [Secure]
Fastboot Reason: UTAG *bootmode* configured as fastboot
failed to validate system image
ERROR : Failed to pass validation. backup to fastboot
Boot up failed
i tried flashing TWRP but its giving errors too. are there any known workarounds to unlocking the bootloader or forcing a recovery/twrp to work?
thanks, all
Hello guys,
my tablet wont boot anymore its stucks on the logo (the first thing at powerup).
i get only access to the fastboot mode but its locked(looks like :DEVICE LOCKED) (so i think i have no permission to change anything right?)
i tried allready commands like
"fastboot unlock" or "fastboot flashing unlock_critical" but it response alltime "FAILED (remote: Command not allowed)"
so anybody has an idea to rescue my future knifeboard ? :crying:
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
lucmaas99 said:
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
Click to expand...
Click to collapse
Every two or three days people report here they bricked phones by forcing update or Factory reset (or relocking Bootloader) from custom or rooted phones (or by having TWRP) - one must first go back to the original stock firmware he had, before upgrading/resetting/relocking...
And this thread will also not help to somebody else -
since 'somebody' will not read (before bricking the phone) ;(
---
Do you still have TWRP - use HWOTA to flash stock
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
If you have no TWRP but Fastboot is showing Bootloader unlocked, you should be able to flash TWRP.
If Fastboot is showing Bootloader locked but FRP unlocked, you should be able to unlock Bootloader.
But if there is no more TWRP and Fastboot is showing FRP and Bootloader locked - maybe DC Phoenix can help you
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
lucmaas99 said:
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
Click to expand...
Click to collapse
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
lucmaas99 said:
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
Click to expand...
Click to collapse
I cannot flash anything because I cannnot enable USB debugging in developers options
zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
What can I do I can access phone but cannot unlock bootloader because cannot use remote commands and I can not get into any recovery menu I am out of idea's
lucmaas99 said:
I cannot flash anything because I cannnot enable USB debugging in developers options
Click to expand...
Click to collapse
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
zgfg said:
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
Click to expand...
Click to collapse
Modelnumber: EVA-L19
Build: NRD90M test-keys
I think I should not supposed to have test-keys doesnt seem correct?
So I got my phone to boot but everytime I want to do something in recovery or something else It wont boot anymore and than I need to make the battery run out of juice. are there anyfix without needing root recovery or fastboot.
ADB wont work because usb debugging wont turn on (tried many things), Fastboot kinda works but gives the error (remote command not allowed)
Cannot get into any Recovery I can boot to OS
OK so I have this PRA-LX1, long story short after a dload tonight to go back to stock ROM I ended up with softbricked phone, I can only enter Fastboot/Rescue mode.
Anything else ends up either in error 8 (ROM) or error 11 (Recovery) error.
- I have access to fastboot via adb/fastboot in a PC terminal
- I have FRP Lock, Phone Locked
- Nearly any fastboot command I send ends up in FAILED (remote: command not allowed!)
- I have my bootloader unlock code, but can't unlock because no botting ROM to check OEM unlock in developer options
- Can't flash any recovery (fastboot "not allowed" error)
- Can't seem to launch a new Dload with Vol+&Vol-&Power. Gives black screen "error mode: please update system again - Error Func NO 11 (recovery image)"
I'll try to let the blank screen drain the battery to get a new try to the Dload method... tomorrow