Hey i'm pretty new to this but i got my pixel phone stuck in a boot loop when it did the second restart after fastbooting the new boot img using the Chainfire method
im not too sure what i did wrong...
it is a best buy phone but im using it on AT&T and not VW but i did unlock it, it said in the fastboot menu and had a little warning/unlock pic
i searched around a bit but nothing i tried worked and so i tried to just unlock it but now it tells me its corrupt and remote oem is not allowed
...i assumes thats when i ****ed up
so any help would be useful thanks.. :/
Here i made a video for that. https://www.youtube.com/watch?v=5Ewo1ou_53o
my phone is locked
i tried to unlock it but i keep getting device not found (null) or whatever it says ...even after i update my drivers
......also i switched to a different computer than when i tried to root and and it looped .. should i use the original or would that even matter?
HeyItsGhost said:
my phone is locked
i tried to unlock it but i keep getting device not found (null) or whatever it says ...even after i update my drivers
......also i switched to a different computer than when i tried to root and and it looped .. should i use the original or would that even matter?
Click to expand...
Click to collapse
how can you root your device without unlocking your bootloader?
i guess you cant do anything about it, you have to send it to google or your phone company.
Your device is sadly bricked and with a locked bootloader you cant do anything :/
Hello everybody,
My phone had some weird glitches, factory reset didn't work, and the capacative buttons didn't work anymore, and I had to restart the play store to install the apk after it downloaded the app. I made a new User, the buttons worked again and I could normally install apps. But it was a temporary fix, and as I couldn't factory reset I decided to unlock my bootloader because that resets your phone. So what I did is:
1. I installed all the proper drivers
2. I opened an commandprompt in the adb folder
3. I typed adb devices, it said unauthorized, I authorized it on my phone, and it said that it was authorized after that.
4. I typed adb reboot bootloader
5. I waited untill it went into fastboot mode and typed fastboot oem unlock (I had the function to unlock the bootloader enabled in developer options).
My phone rebooted after this, now it only shows the OnePlus logo and powered by android, it doesn't boot further. I can't return the phone as I bought it second hand. When I connect the phone to the laptop that I used for it (The usb cable was connected directly to the motherboard, incase that matters and it was an original 4 pin samsung cable), it recognizes it as an Android device, so I think it's a soft brick.
How to fix this? Thanks in advance.
-Oczosinkoo
Hi !
You can try this tutorial
https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Good luck !
A while ago my phone wanted to do an EMUI update and halfway through it something failed and now my phone is stuck in a bootloop where it gets to the carrier logo screen then restarts and displays Huawei eRecovery (which does not work). I am aware that there are plenty of threads about this issue but none of them have really helped me. My phone was running completely stock software and the default development settings are active (OEM locked etc.) except maybe USB debugging. I've tried to send it back to my carrier but because it has a broken screen they won't take it under any warranty, I have also tried Huawei but their online help is awful and the closest service centre is over 10 hours away. I have no intentions of replacing the screen because for the price of it I may as well just buy a new phone.
As far as the model goes it is a MHA-L09 from Australia (bought via Optus), I have a bootloader code and my IMEI number.
I've tried to access the phone through bootloader and adb. adb doesn't recognise the phone whatsoever but bootloader does (using adb devices and bootloader devices respectively in cmd) but other bootloader commands have no effect as the OEM is locked.
I was just wondering whether I'm able to flash a new rom onto it given the circumstances or whether I should just buy a new phone altogether.
EmeraldStar82 said:
A while ago my phone wanted to do an EMUI update and halfway through it something failed and now my phone is stuck in a bootloop where it gets to the carrier logo screen then restarts and displays Huawei eRecovery (which does not work). I am aware that there are plenty of threads about this issue but none of them have really helped me. My phone was running completely stock software and the default development settings are active (OEM locked etc.) except maybe USB debugging. I've tried to send it back to my carrier but because it has a broken screen they won't take it under any warranty, I have also tried Huawei but their online help is awful and the closest service centre is over 10 hours away. I have no intentions of replacing the screen because for the price of it I may as well just buy a new phone.
As far as the model goes it is a MHA-L09 from Australia (bought via Optus), I have a bootloader code and my IMEI number.
I've tried to access the phone through bootloader and adb. adb doesn't recognise the phone whatsoever but bootloader does (using adb devices and bootloader devices respectively in cmd) but other bootloader commands have no effect as the OEM is locked.
I was just wondering whether I'm able to flash a new rom onto it given the circumstances or whether I should just buy a new phone altogether.
Click to expand...
Click to collapse
You can use DC-Phoenix to flash firmware.
There are tutorials on how to use it on their website (DC-Unlocker)
Ah, you have bootloader code. Then you might be able to fix this for free.
PM me on telegram, link in my signature
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
M3DUS4 said:
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
Click to expand...
Click to collapse
this could be because the galaxy A51 wasnt built with fastboot, and the code to launch this option was just reused from a different device, or because something isnt connecting properly.
Hello, I have the same ... Android 11 (and currently 12) (from Frija). So it is not the fault of incorrect configuration or with connecting. Only something is wrong with this phone ...
I have this device and this solved it for me:
Enable OEM unlocking in developer settings
Shut down the phone
Hold volume up and volume down
Plug in a USB cable connected to a computer (the computer being turned on)
Keep holding
You're in download mode!
Side note: This might not work in USA or Canada, I am from europe and it works here. I have no idea if it works in another region. Also, you can't just flash a recovery.img on Samsung since there is no real "fastboot", you have to use download mode and Odin.
But I know how to enter download mode... Problem is Fastboot mode...
There is no fastboot mode on a modern Samsung device. If there is, it's fake and you cannot flash anything with it. As you can see even from Wikipedia, Odin is the Samsung replacement of fastboot.
So no fastboot, only download mode.
If a guide is saying to use fastboot, it is not compatible with Samsung.
If you would tell me why you specifically need fastboot, I'll be happy to tell you how you can do it with Odin, if possible.
Because I have Samsung Galaxy A51 5G (A516B) with new Android 12 and I can't do a root! Because I can't upload TWRP (custom recovery) because I haven't OEM unlock option in Deveoper Option. I tried trick with set back date by 7days but not succes. Everything I;ve metioned here - I did at my phone with Android 11.
And... I have read that I can turn this fu**ing OEM option by comend at ADB: fastboot oem unlock.
Phew ...
So this fastboot method is the last method to do a root with my phone.
Upload TWRP by Odin in download mode -ends red warning - of corse...
Have you any ideas?
I would be grateful for help...
I have read this fastboot method at:
How to Unlock Bootloader On Samsung Galaxy Phones [EASY GUIDE]
Are you looking for a Complete tutorial on How To Unlock Bootloader on Samsung Galaxy Phones? If yes, then you have come to the right place.
www.guidetoroot.com
Yeah, that guide is not relevant on any modern Samsung device. Besides, even if it was, which it isn't, you would first need to enable OEM unlocking from the Developer Settings.
But the fact that you don't have an option for OEM unlock is weird, since I have the exact same device model and it is there for me.
May I ask what is your region and is your phone locked to a telephone carrier?
My region is PLS - Poland. And not - phone is not locked. Have you the newest system Android 12?
Yes, I do. It's weird that there isn't even an option for you.
I'll try to come up with some new ideas if I have time...
I'll be glad for it...
Hej, do you have any idea?
stanwin said:
Hej, do you have any idea?
Click to expand...
Click to collapse
Have you tried everything listed here?
BloodyFruitDestroyer said:
Have you tried everything listed here?
Click to expand...
Click to collapse
Yes, I did. Evething exept the last one...
You could try it. It might be risky, but it's the only option I personally can come up with right now.
I've tried this option but Odin stuck on "files verification". Any help?
have any of you encountered this problem?
And how did you solve it?
You can also try searching for combination firmware for your device online
Wiko life 3
Tryed
fastboot OEM unlock , fastboot OEM-unlock ,
fastboot OEM_unlock , fastboot oem unlock ,
fastboot oem-unlock , fastboot oem_unlock ,
fastboot flashing unlock .
fastboot Flashing get_unlock_ability
returns;
0 not unlockable.
When I began I was able to get it into an energy down load mode but, have not been able to again
1) So how is this phone flashed
2) Is there a recovery that can be used on it
3) How is it rooted
You ever figure this out? Got the same phone and wanted to play with it properly.
Edit: I'm not seeing the OEM Unlock switch under device settings/developer settings. Completely missing for me.
Not sure if you have ran across any method yet but this will probably do it for you. I just got this phone but I have not looked to see if it has an mtk processor that is compatible with the program. I have used it to root a couple of other wikos but not the bootloader. Anyways here is the link to the program. https://github.com/bkerler/mtkclient
I personally could not get it to work in windows because of the USB drivers the site says to use gave me a bsod. If you search on here for rooting the wiko u307as I posted about my experience with the software. I wish I knew about this program years ago.
hey guys mtkclient will unlock the bootloader but make sure to back up the original firmware with mtkclient before you change anything, i got ahead of myself, i forgot to make a backup, i tried to flash gsi, now im stuck in bootloop without the stock firmware to fix it.
Does anyone know how to get a Wiko Life3 to connect to a PC windows 7 USB drivers not available and cant even get it to connect to any tools.