Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Asdforcer said:
Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Click to expand...
Click to collapse
I'm stuck with this problem too. The exact problem. Have you found a way to fix it?
I have exactly the same problem with my Huawei Tablet.
If I boot with the original ROM and look in the "/log" - directory with adb shell, there is a cust.log. The contents say, that the specific ROM is not original or factory.
I think even the bootloader is unlocked, there is a kind of signature checking.
EDIT: @Asdforcer: Have you tried to boot the original boot.rom with "fastboot boot" - command?
How to remove FRP on Huawei Y6 TIT U02
Hi,
Since I try to update firmware from HUAWEI website, my phone comes non stop booting (bootloop). Any one can help me how to fix my phone?
Asdforcer said:
Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Click to expand...
Click to collapse
Try to unlock your bootloader
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v215 tested by and boots fine.
https://github.com/phhusson/treble_experimentations/releases
Things to consider
WHAT WORKS:
audio -music and speaker phone
camera-front and back (yes pop-up camera works)
video-camera front and back
video playback --(tested youtube in browser) - recorded video playback
Phone calls
messages
auto rotate
brightness
wifi tethering
mtp
flashlight
lift to wake (needed to turn off then on to activate it)
adaptive brightness
dark theme
gps
WHAT DOESN'T:
--Fingerprint
--phone works/ but dialer app has message that device is unsupported
--off-mode charging -- when charging with phone off, bootloader logo screen stays on, instead of battery icon
--screen recording-- after enable dev option // feature flag // settings_screenrecord_long_press .. you can access
screen record from long press power menu, long press screenshot menu, but recording will not save or stop
recording.-- setting option to on does not survive reboot
-- screen shot -- taking screen shot forces a bug report creation. (maybe this is not an issue, only a setting)
.
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Sergeantslaughter said:
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Click to expand...
Click to collapse
our device does not have VBmeta
the directions that say flash VBMETA, say use the stock meta file from stock firmware. so because that file is not used here, this is why you get the error message, ......
actually from your command you did not tell fastboot the location of the file you are trying to flash Unless you have a file called "vbmeta.img" in the current command terminal location. But again back to my original statement, our device does not have this file, so IF you do have the file, it is from other device anyway.
I guess I see how to flash the gsi but how do I get twrp installed?
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
only one permission file needed to be added. This is also expected to be included in the next release anyway.
Need to be fully stock
--boot
--vendor
--recovery
fastboot flash system **GSI.IMG**
fastboot oem reboot recovery
perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
tested version was AOSP 10.0 v201
V203 boots without having to add the extra permission XML file.
Current version v204 not tested yet.
https://github.com/phhusson/treble_experimentations/releases
additional step to get version lower than v203 to boot
Download the additional permission file from
https://github.com/phhusson/device_...0.0/privapp-permissions-me.phh.treble.app.xml
While system is on boot animation screen. (this is as far as it will go on its own)
After the adb push, for me at least, the phone starts to continue its boot operation. Still do the reboot anyway.
Click to expand...
Click to collapse
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Sergeantslaughter said:
I guess I see how to flash the gsi but how do I get twrp installed?
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Click to expand...
Click to collapse
I have not been using twrp with GSI, but if you want to try goto twrp thread. Note that the twrp is currently only working with adb command line interface. No touch screen activity.
start by looking at the threads here. You will find twrp thread there.
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Sergeantslaughter said:
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Click to expand...
Click to collapse
aosp has root built in. If you prefer majisk, you need to first remove the included -su, and then need to use PHH-Majisk, not standard version.
Information on that should be found in gsi thread. It is not device specific.
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Sergeantslaughter said:
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Click to expand...
Click to collapse
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
mrmazak said:
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
will that work? i cant get my phone to power on at all and adb is not recognizing it...
mrmazak said:
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
That repeating sound is sign of bootloop.
Spflash tool is the recommended repair tool.
Download the factory restore package,
Extract the downloaded file.
Open flashtool, select scatter file from the extracted download. Ensure tool is on "download only" mode
Clear all select boxes in the tool window. Put check only in the recovery line.
Press download button, plug USB into phone. The bootloop in the phone is enough to make connection start.
What twrp did you use, where did it come from. Did you verify md5 of the downloaded file.
The only twrp I found was the one I shared, and it did not cause that kind of issue for me. So maybe you did something that you didn't mention?
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Sergeantslaughter said:
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Click to expand...
Click to collapse
Oh, last step is unplug USB. Then long press power button.
10 second should do. But maybe 20
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
Same happened to me, ended up fixing issue by using spflah tool (latest) and updated stock rom (mrmazak posted it) ?
I haven't bought the N1 yet but just might thanks to @mrmazak testing! Anyone tried Q v204 yet? Also curious if PHH regular Pie is bug free.
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v204 not tested by me yet.
https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Do not tell me in v 203 which version to download? I tried several but all to no avail
elephone p8000
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Sergeantslaughter said:
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Click to expand...
Click to collapse
Elephone p8000 is at least 3 years old. And would not think twrp from it will work on your bold n1.
As for why your PC shows your bold n1 as different phone, I can only guess that your PC drivers are somehow modified.
Or your phone is maybe not stock?
I had to flash miui through mi recovery flash to get back to stock rom after some issues, which have all been resolved except for a corrupted bootloader. Now I can't flash twrp anymore, every time I have tried any fastboot command apart from fastboot devices, the fastboot screen on the phone turns black with the letters "press any key to shut down". How can I solve this problem? Miflash also won't work, for some reason it gives error that echo and device are mismatching even though I am sure that I am using the correct beryllium global images for my poco f1. Thank you for your time.
TempAccount10001 said:
You can remove the mismatch inform the .bat file (usually at the beginning )and try flashing
Click to expand...
Click to collapse
Thank you for your answer! I have tried that solution (I found that some people with this issue were able to fix it that way) but for me it didn't work. Fortunately, I was lucky enough to also find this https://forum.xda-developers.com/t/cant-flash-twrp-press-any-key-to-shutdown-in-fastboot.3952763/ (more specifically, commands for a .bat file) which fixed the issue for me 10 minutes ago I just came to update the thread!
Hi guys been spending all night trying to figure out but seems nothing is working. HELP! I know i can get it to work.
So tried to root my A2017G previously but saw all the horror brick stories so ended up just doing the multiple OTA updates via SDCARD upgrade.zip and finally ended up with OREO BO3 version. running fine except for ridiculous battery meter levels playing up but just kept it charged most of the time.
1) at first I tried to check bootloader unlock status from fastboot. But somehow unable to as fastboot is not there! So i thought maybe fastboot is corrupt (stock recovery options ok / also power plus down gets stuck in FTM mode (easy to reboot with adb command) So unable to check bootloader (i am thinking its probably still locked)
2) so got latest version of TWRP 3.3 something and flashed it --> result in phone black screen but detectable (I assume in EDL mode.) '
3) Tried to flash Nougat B10 EDL with EDL tool (working now but after everything is ready to flash it says"" 13:02:38: {ERROR: WritePort:5164 Could not write to '\\.\COM8', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times""
4) MiFlash unable to read hello packet. But i tried pressing power and connecting quickly and suddenly starts flashing B10 nougat EDL ROM but doesnt complete with a "function: sahara_rx_data:237, unable to read packet header" error. Should I be using a stock rom with Meta-INF folder rather than the EDL version? Also should i be flashing OREO stock rom rather than nougat with MiFlash? or it doesnt matter?
5) tried the DFU tool initially qualcomm and com8 detected but says disconnected. (so its in EDL probably but somehow still disconnected?
So currently
1) trying to let the phone battery run out, though i doubt its any use as i probably bricked it installing twrp without unlock bootloader on OREO.
2) Also downloading Oreo stock rom to try and flash with miflash.
Any help or point to some discussion i missed would be helpful thanks. Just wanna get root and GPS tools running so I can let the kids catch some Pokemon without GOing outside.
Seems like the battery had to run out first. Then it started recharging . After about 5 mins I just pressed power button without up or down. Phone rebooted nicely back into Oreo. PhEW... Then i used a stock 2017g EDL for nougat B10 (7.1.1) and flashed with Miflash by going into proper EDL (used ADB reboot EDL command)
Ok some more small hiccups along the way but being able to access EDl i managed to flash TWRP 3.2.1 and then load it up and flash SuperSU for root.
Now to read the threads on how to get rid of the bootloader unlock screen as well as load in the battery saving scripts.
Hi, I am using a oneplus 7t pro mclaren edition. I have soft-bricked the device. I tried to change the filesystem in twrp to f2fs when i was in stock rom (I know it was a stupid mistake). Now the boot and recovery partitions are destroyed. I can boot to actual fastboot mode. Tried to use payload dumper but whenever it tries to boot fastbootd it says
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Tried erase everything I got the following error using "fastboot -w"
Erasing 'userdata' OKAY [ 0.229s]
/home/abhijith/Documents/op7t/output/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I have heard of MSM unbrick tool but as far as i know it only works in windows , before installing VM with windows , I want to know if there is any other way i can recover my device. I have a11 fastboot rom and a12 stock rom. Please help
I have exactly the same problem, same errors etc. if I find any solution I'll post it here. Can't use my phone until then I guess. It all happened after my phone was bricked after trying to install TWRP (previously used LineageOS Recovery).
I followed this guide which resulted in the same errors as for you: https://forum.xda-developers.com/t/...ock-fastboot-roms-for-oneplus-7t-pro.3991189/
Okay, I managed to unbrick my phone, but you won't like the (probably only) solution:
- You NEED Windows (7-10) for this, as the tools are only available on this platform, sadly
- There is this one Indian Guy that will save you:
- Includes how to install all drivers and how to get your phone into COM Mode
- This uses the MSM tool. For 1+ 7T Pro, get it here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
- This is going to STOCK RESET you phone 100%, meaning that your bootloader will be locked etc.
- If you get into any Chinese menu after the phone reboots, you can use Google Lens for translation
I can't believe this worked because it just feels so hacky, but trust me, it's a good last resort as you can always put your phone into COM Mode, regardless of how hard you messed up the system [citation needed].
For me even in device manager qualcomm device itself is not showing :0
abhijiths362 said:
For me even in device manager qualcomm device itself is not showing :0
Click to expand...
Click to collapse
Follow the video. When all drivers are installed and you hold both volume buttons while the device is off, it will show up as a COM/serial device for a few seconds before booting.
Important: Only connect the cable while already pressing the buttons or it won't work.
I was able to get to edl mode and msm tool was detecting but now i am facing sahara communication error i dont have official cable so maybe that might be the reason will try that also
@Colin_T Thanks for the help. I was able to install stock rom to my oneplus 7t pro. I really want to install pixel experience, in the instructions it is saying flash oos 12 firmware. But in the official website i am only seeing 11. What to do?