I have looked for months to find a way to remove the google frp from my ZTE Blade Vantage Z839 and there is not one video, post, forum, or code that I have found that will actually work. I can bypass it but that is as far as I can go I cant do anything else and I cant get the phone to side load or anything. I can not believe there isn't a single person that has a clue as to how to beat this thing and I have asked here and other places and either no one wants to help or they just cant either way i guess this is the one phone that is uncrackable as far as frp goes.
Make sure you use the bro?wser app or chrome... the google app wouldn't download for me
Techeligiblem
/2019/02/13/bypass-frp-zte-z835/
bro just download the firmware for it its like z839 B20 version firmware and use xiaomi miflash to flash the phone itll get rid of frp
PrivyetCyka said:
bro just download the firmware for it its like z839 B20 version firmware and use xiaomi miflash to flash the phone itll get rid of frp
Click to expand...
Click to collapse
Thanks for the reply, I am absolutely useless with technology, I would probably end up bricking the phone
Billy the doughnut said:
Thanks for the reply, I am absolutely useless with technology, I would probably end up bricking the phone
Click to expand...
Click to collapse
sorry i dont know how to fileshare big files so it took me a while but here ya go sendanywhe.re/9PPOQTQQ
Billy the doughnut said:
Thanks for the reply, I am absolutely useless with technology, I would probably end up bricking the phone
Click to expand...
Click to collapse
Look at all the "I bricked my phone" threads. Many times a little itch can turn into a real big scratch.
blackhawk said:
Look at all the "I bricked my phone" threads. Many times a little itch can turn into a real big scratch.
Click to expand...
Click to collapse
I literally made it foolproof lol i hand typed instructions, put the firmware file , qualcom usb drivers , adb and fastboot drivers, miflash, and even an edl tool to avoid manually booting into it if you get stuck somehow though just let me know
PrivyetCyka said:
I literally made it foolproof lol i hand typed instructions, put the firmware file , qualcom usb drivers , adb and fastboot drivers, miflash, and even an edl tool to avoid manually booting into it if you get stuck somehow though just let me know
Click to expand...
Click to collapse
Sorry mate was that message for me
Billy the doughnut said:
Sorry mate was that message for me
Click to expand...
Click to collapse
No you're fine lol he was just saying it's still easy to make a mistake and I was telling him I made it mistake proof lol you're all good. Hope it fixed it for you
Related
Hi everyone!
Just a little question, as I'm facing this situation right here:
is there a way to revive a phone that doesn't boot, nor lets me access recovery mode or fastboot or bootloader?
UltimateGoblin said:
Hi everyone!
Just a little question, as I'm facing this situation right here:
is there a way to revive a phone that doesn't boot, nor lets me access recovery mode or fastboot or bootloader?
Click to expand...
Click to collapse
Which phone are you talking about?
I'm talking about the Alcatel V860. It's absolutely an uncommon model, that's the reason why I'm speaking in general.
UltimateGoblin said:
I'm talking about the Alcatel V860. It's absolutely an uncommon model, that's the reason why I'm speaking in general.
Click to expand...
Click to collapse
Please ask specific questions as its related to the phone model. I'm not hopefully about it. You can get it serviced by "bootloader repair" Should be about 40$.
Some of the more common phones can be unbricked on your own.
LS.xD said:
Please ask specific questions as its related to the phone model. I'm not hopefully about it. You can get it serviced by "bootloader repair" Should be about 40$.
Some of the more common phones can be unbricked on your own.
Click to expand...
Click to collapse
I've already posted here, but I received only one answer, so I decided to speak more general just to know if it is theoretically possible to rescue a phone in the situation I described.
Anyway, do you think that there is no way that the pc can communicate with a phone that doesn't even reach the bootloader?
Ok, I'll ask a different question: the phone I'm talking about ended up this bad while flashing an official OTA.
How is that possible?
I thought there was no possible way that an OTA messed with the bootloader, or the recovery... or fastboot! Doesn anyone know what could possibly have gone wrong during the update?
UltimateGoblin said:
Ok, I'll ask a different question: the phone I'm talking about ended up this bad while flashing an official OTA.
How is that possible?
I thought there was no possible way that an OTA messed with the bootloader, or the recovery... or fastboot! Doesn anyone know what could possibly have gone wrong during the update?
Click to expand...
Click to collapse
Actually, it seems like your phone is bricked, there are some methods to unbrick some phones but I don't know if they would work for you, just try to do a Google search how to unbrick a bricked phone, and it might return with some useful stuff, try everything that's possible, because nothing worst can happen over a brick(except it can blast in your hand if you connect a high voltage in place of battery)(lol, it won't happen! )
Hit Thanks if I helped sent from my SM-T211
Already done that, I'm giving up if my pc cannot communicate with the phone.
At this point I'd only like to know how could an OTA corrupt the bootloader.
UltimateGoblin said:
Already done that, I'm giving up if my pc cannot communicate with the phone.
At this point I'd only like to know how could an OTA corrupt the bootloader.
Click to expand...
Click to collapse
Only thing you can do now is, go to store(from where you buy your phone, act dumb and tell them that this won't turn on, they might replace your phone!
Hit Thanks if I helped sent from my SM-T211
Thanks. Anyone else?
UltimateGoblin said:
Thanks. Anyone else?
Click to expand...
Click to collapse
So, what exactly you did?
Hit Thanks if I helped sent from my SM-T211
It wasn't me, it was my cousin, who flashed an OTA which apparently corrupted all the layers of the OS. I believe him, but I find it incredibly difficult to happen, so I wanted to know if that could really happen.
UltimateGoblin said:
It wasn't me, it was my cousin, who flashed an OTA which apparently corrupted all the layers of the OS. I believe him, but I find it incredibly difficult to happen, so I wanted to know if that could really happen.
Click to expand...
Click to collapse
What do you mean by ota corrupting all layers of os?
I never heard of it.
Hit Thanks if I helped sent from my SM-T211
It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.
UltimateGoblin said:
It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.
Click to expand...
Click to collapse
Try smart phone flash tool(on pc), I recently came across a thread in which author said he have a hard bricked xolo phone and it don't boot to anything, but responds to SP Flash tool. Give it a try, if might work.
I don't have it's link, Google it
Hit Thanks if I helped sent from my SM-T211
UltimateGoblin said:
It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.
Click to expand...
Click to collapse
Did that worked?
Sent from my SM-T211 using xda app-developers app
Ok I think I really may have messed up big time with this guys so I'm begging for some help.
]So I just recently bought a AT&T LG G3 on ebay in excellent condition everything worked great until I started experimenting. I rooted it using KingRoot but later decided I'd rather use another method of root because I prefer SuperSu to manage my root access...Anyways to make a long story very short. I needed to get into download mode but Kill Switch had already locked me out because I rooted it..I did not know that McAfee would lock my phone when I rooted.. and so as a last ditch effort I attempted to wipe the entire drive and re-flash the OS well to my surprise that did completely erase the OS as expected but not the Kill Switch. So now im stuck at LG Welcome screen and cant do anything.. I'm at the mercy of the web help PLEASE!!! smh
TriLTorch said:
Ok I think I really may have messed up big time with this guys so I'm begging for some help.
]So I just recently bought a AT&T LG G3 on ebay in excellent condition everything worked great until I started experimenting. I rooted it using KingRoot but later decided I'd rather use another method of root because I prefer SuperSu to manage my root access...Anyways to make a long story very short. I needed to get into download mode but Kill Switch had already locked me out because I rooted it..I did not know that McAfee would lock my phone when I rooted.. and so as a last ditch effort I attempted to wipe the entire drive and re-flash the OS well to my surprise that did completely erase the OS as expected but not the Kill Switch. So now im stuck at LG Welcome screen and cant do anything.. I'm at the mercy of the web help PLEASE!!! smh
Click to expand...
Click to collapse
You can't get passed that. There's no way around it. Only way if it's even possible is to pay a phone store that has a box that might can fix it. But other wise chances are slim
Sent from my iPhone using Tapatalk
hyelton said:
You can't get passed that. There's no way around it. Only way if it's even possible is to pay a phone store that has a box that might can fix it. But other wise chances are slim
Click to expand...
Click to collapse
Dang please dont tell me that I honestly just bought this phone a week ago..heh..Ive rooted and flashed multiple phones in my time but have never seen a "kill switch".
TriLTorch said:
Dang please dont tell me that I honestly just bought this phone a week ago..heh..Ive rooted and flashed multiple phones in my time but have never seen a "kill switch".
Click to expand...
Click to collapse
you can try this.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Jahanzaibawan said:
you can try this.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Click to expand...
Click to collapse
Thank you I will try this!!
TriLTorch said:
Thank you I will try this!!
Click to expand...
Click to collapse
Don't think that will work with the kill switch issue. That is if you loose download mode. But worth a shot.
Sent from my iPhone using Tapatalk
Jahanzaibawan said:
you can try this.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Click to expand...
Click to collapse
This method worked after many hours of trying and trying thank you for this ...unfortunately the phone which was unlock is now locked again and says that it is permanently locked to AT&T.. any Ideas?
TriLTorch said:
This method worked after many hours of trying and trying thank you for this ...unfortunately the phone which was unlock is now locked again and says that it is permanently locked to AT&T.. any Ideas?
Click to expand...
Click to collapse
What do you mean says its permanently locked to AT&T? Screen shot? Is it asking for a sim unlock code?
Sent from my iPhone using Tapatalk
hyelton said:
What do you mean says its permanently locked to AT&T? Screen shot? Is it asking for a sim unlock code?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yea the SIM unlock is permanently locked and I havent even had the opportunity to put a unlock code in. After finally getting the Download mode working and getting the OS back on it Dial 2945#*850# to insert unlock code and it says "this phone is permanently locked and can not be unlocked" I haven't even made a wrong attempt at it yet its just already locked.
Jahanzaibawan said:
you can try this.
http://forum.xda-developers.com/spr...very-guide-t3132359/post61280085#post61280085
Click to expand...
Click to collapse
This link worked pretty flawlessly just took a few tries shorting the pins out and plugging in the computer simultaneously but once the phone shows as its plugged into a com port and you have your tot file and dll ready for flash read directions very very carefully and this works great thank you so much!
TriLTorch said:
This link worked pretty flawlessly just took a few tries shorting the pins out and plugging in the computer simultaneously but once the phone shows as its plugged into a com port and you have your tot file and dll ready for flash read directions very very carefully and this works great thank you so much!
Click to expand...
Click to collapse
welcome buddy.?
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk
samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?
samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk
Hi all,
My Pixel bricked a few months back & was still under warranty. It was replaced & I've just today received the original bricked phone back to my surprise.
When plugged in via USB it shows as Qualcomm HS-USB QDLoader 9008
QFIL detects it but I can't find any .xml, .mbn, .hex files to flash it with.
Can i copy anything of the working phone (exact same model), to my laptop to then revive the bricked phone?
Thanks in advance for your advice...
Any luck with this? My girlfriend's Pixel is stuck in this mode as well. I can't find these files anywhere on the net. She's starting to get a little cranky.....please help!
Unfortunately the files you are looking for are not available. The have not been released
shagbag913 said:
Unfortunately the files you are looking for are not available. The have not been released
Click to expand...
Click to collapse
Thanks for the reply. How and when do these files usually get released? Do you advise I keep the device in hopes that I will be able to revive it in the near future?
Thanks!
Melnutz said:
Thanks for the reply. How and when do these files usually get released? Do you advise I keep the device in hopes that I will be able to revive it in the near future?
Thanks!
Click to expand...
Click to collapse
I wouldn't advise keeping it. They honestly will probably never be released, sadly.
Adventur0us said:
Hi all,
My Pixel bricked a few months back & was still under warranty. It was replaced & I've just today received the original bricked phone back to my surprise.
When plugged in via USB it shows as Qualcomm HS-USB QDLoader 9008
QFIL detects it but I can't find any .xml, .mbn, .hex files to flash it with.
Can i copy anything of the working phone (exact same model), to my laptop to then revive the bricked phone?
Thanks in advance for your advice...
Click to expand...
Click to collapse
Melnutz said:
Any luck with this? My girlfriend's Pixel is stuck in this mode as well. I can't find these files anywhere on the net. She's starting to get a little cranky.....please help!
Click to expand...
Click to collapse
shagbag913 said:
Unfortunately the files you are looking for are not available. The have not been released
Click to expand...
Click to collapse
Melnutz said:
Thanks for the reply. How and when do these files usually get released? Do you advise I keep the device in hopes that I will be able to revive it in the near future?
Thanks!
Click to expand...
Click to collapse
shagbag913 said:
I wouldn't advise keeping it. They honestly will probably never be released, sadly.
Click to expand...
Click to collapse
Wrong! I just did it!
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Follow that guide but with the files provided here https://forum.xda-developers.com/pixel/help/fix-google-pixel-help-noob-t3790470
(https://dl.google.com/dl/android/aosp/sailfish-opm4.171019.016.b1-factory-68c3a77d.zip)
All you need is a working bootloader, thank God. This just saved my ass.
Creed14 said:
Wrong! I just did it!
https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Follow that guide but with the files provided here https://forum.xda-developers.com/pixel/help/fix-google-pixel-help-noob-t3790470
(https://dl.google.com/dl/android/aosp/sailfish-opm4.171019.016.b1-factory-68c3a77d.zip)
All you need is a working bootloader, thank God. This just saved my ass.
Click to expand...
Click to collapse
Your right, IF you have a working bootloader. The op does not.
I was having this same issue. Currently running crDroid and selected the Reboot Recovery option from the advanced Power Menu. It turned off but didn't come back on. Tried booting into the bootloader but got nothing. Plugged it into my PC and saw the same device description then realized I probably had a hard brick. I was about to give up when I decided to just hold the power button alone and after about 20 seconds it booted normally. Looks like I dodged a bullet.
shagbag913 said:
I wouldn't advise keeping it. They honestly will probably never be released, sadly.
Click to expand...
Click to collapse
Is there a way to pull it off a working Pixel? I have two 128GBs Pixels with the exact that were running the exact same setup (Unlocked BL with LOS15.1)
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
psorincatalin87 said:
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
Click to expand...
Click to collapse
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
V0latyle said:
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
Click to expand...
Click to collapse
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
psorincatalin87 said:
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
Click to expand...
Click to collapse
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
V0latyle said:
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
Click to expand...
Click to collapse
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
psorincatalin87 said:
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
Click to expand...
Click to collapse
I downloaded the firmware with Frija and I get the same issue with Odin.
psorincatalin87 said:
I downloaded the firmware with Frija and I get the same issue with Odin.
Click to expand...
Click to collapse
What options do you have checked in Odin?
V0latyle said:
What options do you have checked in Odin?
Click to expand...
Click to collapse
I haven't touched any of the options, everything is on default.
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
nsfnd said:
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
Click to expand...
Click to collapse
OH.MY.GOD! Thank you very much, man! I love you! I could kiss you right now, stranger!
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
nsfnd said:
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
Click to expand...
Click to collapse
Nah, this is my last one.
psorincatalin87 said:
Nah, this is my last one.
Click to expand...
Click to collapse
don't be that way lol, it's fun, just do it on hardware you own. get a cheap phone off ebay to play with