Hey everyone! I'm new around XDA, but i know its a great community!
Well, it looks that its my time to request some help...
Today i got my hands on a Huawei P20 PRO Twingo, the model is CLT-L29 , it came locked by google (FRP), and i tried some stuff i found allover google and YouTube around a bypass that currently doesn't work anymore, because my android versions seems more recent and doesn't have the functionality that i need to bypass the FRP.
Then i started making some more research around the subject and found a guy that could help me downgrading the firmware by fastboot mode, but the device doesnt want to enter on that mode, i turn it off, press the VOL DOWN for a while then i connect the USB, i even tried a different laptop, nothing...
After that i tried to press all the Volume keys with power key... it entered on a screen "EMUI" that says "SOFTWARE INSTALL FAILED! GET HELP FROM xxxx.EMUI COM/BLABLABLA) and says "Reboot system now"...i then press reboot now, and i does a regular reboot and starts up to select language etc, all good... BUT FRP locked...
Whats going on? Do you guys think someone already attempted to do something on this device? Or its the system locking it for security?
Thanks a lot for your time reading this! Hope to get some replies and hopefully solve this!
I managed to get inside eRecovery mode, pressing up volume for a while with the device turned off, and plugging the USB...
then i did "download latest version and recovery"... well.... it successfully downloaded a 3.8gb file and installed, but after reboot i still can't set it up to fastboot mode
Related
I was running a lollipop bootloader and since i wanted to upgrade to marshmallow i had to update the bloodloader too, so i flashed a new stock boot.img obtained from a stock rom and soon after that i also flashed twrp, i think i somehow bypassed the new (locked?) bootloader with a custom recovery and now i'm stuck in "Rescue Mode".
Device is now stuck into that mode, i cannot turn it off or enter recovery, as soon as i restart my phone it goes into rescue mode, i have already tried all key combinations and also tried to force install from sdcard, my computer is not recognizing my device either so i can't use adb, i had no idea bricking a device like this was even possible, i'm quite desperate.. please help.
[How i fixed it] I somehow managed to get out of Rescue Mode, what i did wrong was not holding vol down + power long enough, you have to hold them down until phone restarts, that takes about 10 seconds, after that you will feel a vibration and huawei logo will appear, keep holding buttons down for 4-5 more seconds before taking your fingers off, it should then go into fastboot, once you're there adb should work and you will be able to unlock the bootloader if it is not unlocked already, after that you should be able push data to device or flash recovery again. If adb still doesn't work check usb drivers, your best bet is probably downloading HiSuite.
Awesome! :good:
Glad you got it going! I'll close this thread now! But here is your device section for future use, http://forum.xda-developers.com/t/huawei-p8
Cheers!
Ok, I bought a galaxy s7 from my friend, because he was getting a new phone, but I discovered that wifi wasn't working at all, so I thought it had to do something with the firmware and I decided to flash the rom with odin, with a newer version of the firmware.
This is where all my problems started, when I restarted my phone for the first time I noticed that the startup/booting animation was some weird ****, not like the usual one (the samsung logo) but was a weird loud animation with the letters of MTK, in that moment what came to my mind was that I just could be a custom rom or just a custom boot animation, so I didn't gave it too much attention, I continued to do what I was gonna do and tried to boot my phone into download mode with the classic normal method , Volum Down+Home+Power, when I tried this apparently It didn't work, I could stay there pressing the buttons for like 5 minutes and nothing would happen, and once I would release them, the phone would turn on and do the weird animation and boot like normal, at this point I was already worried so I proceded to Root my phone with KingRoot and install an app to manually boot my phone into download mode, it didn't worked. After hours of searching for a solution I found about ADB and I did all the steps to boot my phone from there, still nothing, when I typed the "abd reboot download mode" or something like that, the phone would just restart and do the ****ing weird animation again, so I tried booting into recovery mode and when I tried to do it, an android robot would appear laying on the ground with his chest open, and the words "No command". When I would press the home button the phone would react and send me to the recovery mode, normal.
So I'm begging you guys for help, since I don't know what to try now.
It looks like the download mode or maybe the firmware is broken, and I can barely do something without the download mode, pls help.
What I've tried so far:
-Basic 3 buttons method (can't remove battery, it's an s7)
- ADB method
- ADB fastboot method
- Vol Up+Vol Down+Home+Power
- Can't do anything with Odin since I need download mode
- Tried to install twrp recovery mode from ADB but says that It didn't found the file
If someone knows a solution for this please tell me what I can do. Sorry for bad english, right now I'm kinda exhausted because I've been trying over and over methods for like about 6+ hours
i had the same problem, phone is password pretected and cannou use factory reset and also phone wownt boot in download mode
OhLookItsChris said:
Ok, I bought a galaxy s7 from my friend, because he was getting a new phone, but I discovered that wifi wasn't working at all, so I thought it had to do something with the firmware and I decided to flash the rom with odin, with a newer version of the firmware.
This is where all my problems started, when I restarted my phone for the first time I noticed that the startup/booting animation was some weird ****, not like the usual one (the samsung logo) but was a weird loud animation with the letters of MTK, in that moment what came to my mind was that I just could be a custom rom or just a custom boot animation, so I didn't gave it too much attention, I continued to do what I was gonna do and tried to boot my phone into download mode with the classic normal method , Volum Down+Home+Power, when I tried this apparently It didn't work, I could stay there pressing the buttons for like 5 minutes and nothing would happen, and once I would release them, the phone would turn on and do the weird animation and boot like normal, at this point I was already worried so I proceded to Root my phone with KingRoot and install an app to manually boot my phone into download mode, it didn't worked. After hours of searching for a solution I found about ADB and I did all the steps to boot my phone from there, still nothing, when I typed the "abd reboot download mode" or something like that, the phone would just restart and do the ****ing weird animation again, so I tried booting into recovery mode and when I tried to do it, an android robot would appear laying on the ground with his chest open, and the words "No command". When I would press the home button the phone would react and send me to the recovery mode, normal.
So I'm begging you guys for help, since I don't know what to try now.
It looks like the download mode or maybe the firmware is broken, and I can barely do something without the download mode, pls help.
What I've tried so far:
-Basic 3 buttons method (can't remove battery, it's an s7)
- ADB method
- ADB fastboot method
- Vol Up+Vol Down+Home+Power
- Can't do anything with Odin since I need download mode
- Tried to install twrp recovery mode from ADB but says that It didn't found the file
If someone knows a solution for this please tell me what I can do. Sorry for bad english, right now I'm kinda exhausted because I've been trying over and over methods for like about 6+ hours
Click to expand...
Click to collapse
No idea really but just to be sure. Did you try switching off phone completely and then trying 3 button combo for download mode?
Also post that **** boot animation logo as that might help us figure what you have flashed on phone.
Sent from my SM-G930F using Tapatalk
SOLVED already!
Hello everyone,
i'm new to this so excuse if i do wrong something (title etc..).
I wanted to root my Huawei vns-l31 so i used the srk tool for enable the bootloader and then install the twrp; it seemed that all go right but when i tried to reboot in recovery mode i probably did something wrong in the timing with the combination of buttons and now the phone is stucked on the blackscreen with the message "your device has been unlocked etc etc.. your device is rebooting now.." the problem is that the device it's not really rebooting. I've tried the pwr for 10s, vol up+pwr, vol down+pwr but nothing..the phone doesn't go on fastboot and so i can't flash back anything. Pls help me i've read many threads on xda but no one worked for me.
again sorry if i broke some rules and for my bad english
Thanks to all that will answer this post.
Edit:i Just let the phone turno off because of the battere and then in reboot It showed me the three usual options..Maybe It was Just a bug. Still i dont know why It doesn't open the twrp..I'm Just bad at timing?
I use this forums a lot for info but in this case i can't find any leads of whee to go with this, so wondering if someone can chip in some ideas?
I flashed a ROM via flashtool but wasn't happy with it, so i thought i'd just go back to stock and so used flash tool AKA emma to flash one of the options given there.
First attempt to flash it said "flash failed" or something like that and had the "flashing failed, connect to computer" note in the phone when booting it. (I'm sort of making up the terms, not that much into the tech ). Anyway, i tried flashing the same FW again and this time it went through really quick being 'completed' in a few seconds.
Now when i try to boot it gets stuck in the 'Sony' logo. Can go into Fastboot but no Flash Mode (nothing happens using the vol down key), and USB debugging seems to be off now as well.
Emma only works in Flashmode so can't do anything with that. Flashtool doesn't offer anything useful in Fastboot and Xperia Companion recognises the phone when in Fastboot but asks that i unlock the screen and enter MTP...
Any help of where i can go with this?
Thanks
P.s. While keeping buttons pressed randomly it went once into flash mode, but trying to flash a ROM with flashtool it got stuck at "reding device data" and i haven't been able to enter the mode again. Is there an alternative key press combination that i stumbled on by chance? I think i just kept vol up and power held for a while and let go at a random number of phone vibrations
Just tried: Flashed twrp via fastboot and then rebooted into recovery. Same thing. It still opens to Sony splash screen and stays there
Ok, i'm kind of talking to myself here, but mild success and something that might help someone.
Managed to get back in flash mode. Don't know if it's a fluke, unique to this phone, or how it's actually meant to work, but the sequence is:
From the freezed up splash screen, and the USB connected, press and keep pressed power+vol up (hard restart/shutdown)
You get a single vibration, if you let go here it restarts. Keep pressing
You get a triple vibration, if you let go here it shuts down. Keep pressing
You get a single vibration, if you let go here it starts in fastboot. Keep pressing
You get a second single vibration, if you let go here it starts in flash mode.
Possibly a fluke but don't want to have to try again!
Anyway, i managed to flash the last working firmware and it's all good, yet this is the unwanted one. So issue is i still need to downgrade the phone to 7.1.1
Please help!
Hello! This is a distress call, because I think I brickered my S10e, through my own fault ...
Trying to install the TWRP according to the instructions given in the Hades Rom, I made two unforgivable mistakes, since years of flashing roms ...
1) I took the wrong installation file (I have the G970F/DS, and flash the beyond2lte file, instead of beyond0lte)
2) I omitted to force boot of TWRP just flashed.
Result: I cannot enter download mode as I did before (the phone does not blink), and trying to enter recovery, out of 20 attempts, it only turned on 2 times and does not go beyond the warning screen that the oem is unlocked, and it is not a safe state. I press power to continue as it says, and the screen turns off. Of course it doesn't start normally with the power button either.
I found out recently that been connected to the PC, it is recognized by it, and I even could access to it though the Windows explorer... Ergo, it's not dead, but the screen is in the infamous "black screen of death". Tried the usb jig emulator, by sugestion of denon480, but it didn't work (see screen capture).
Is there a way to force it into download mode, to flash the correct recovery, or eventually an official firmware? The cell phone is immaculate, I can not resign myself to it turns paperweight !!!!!
I put this here, because the problem was in TWRP recovery flashing, I didn't arrived to the Hades ROM installing process, and this way I can reach more people...
I appreciate any help.
Cheers
https://1drv.ms/u/s!Aqmv5IkqbGj3mwqTWmEd3VJxPPHs?e=V3UVSP
I don't even think it is possible to brick Samsungs like that. Are you following the right steps to download mode? Ergo,
Step 1 – Turn OFF your Galaxy S10.
Step 2 – Now press and hold the following buttons on your phone together: Volume Down + Bixby Button.
Step 3 – Next, plug in one end of the USB-C cable to a computer and the other end to the phone. As soon as you will connect, your phone will power on.
I have the same problem. I do not know if the OEM unlocking has something to do with that as I can not turn on OEM although it is not missing but it is not active and can not be turned on. I tried all the solution available online but it looks like no one knows what to do even the so called experts know nothing at all and the only things they know is the direct easy way. So disappointed
Same problem here... any solutions?