Random reboot and Unlocked bootloader - ZTE Axon 7 Questions & Answers

So a couple of times my phone has randomly rebooted into the fastboot screen and then it tells me that my bootloader is unlocked and that the phone is unsafe with a very poor spelling. I have to try to reboot it multiple times for it to go back into the phone. Any thoughts on the subject? I guess I could lock up the bootloader and I wouldn't have any bad messages but that defeats the purpose.

swehes said:
So a couple of times my phone has randomly rebooted into the fastboot screen and then it tells me that my bootloader is unlocked and that the phone is unsafe with a very poor spelling. I have to try to reboot it multiple times for it to go back into the phone. Any thoughts on the subject? I guess I could lock up the bootloader and I wouldn't have any bad messages but that defeats the purpose.
Click to expand...
Click to collapse
In the B27 update you'll be getting that splash screen , doesn't matter if you boot to recovery, system , bootloader, you'll get that screen ....you just need to wait for 5 sec. And will boot to where you want to go.
So that's how it is now, i know hate that screen but is there now , unless you want to go the Tenfar way.

DrakenFX said:
In the B27 update you'll be getting that splash screen , doesn't matter if you boot to recovery, system , bootloader, you'll get that screen ....you just need to wait for 5 sec. And will boot to where you want to go.
So that's how it is now, i know hate that screen but is there now , unless you want to go the Tenfar way.
Click to expand...
Click to collapse
Thanks. I didn't know if it was only me or not. Makes me feel a little better about it.

swehes said:
Thanks. I didn't know if it was only me or not. Makes me feel a little better about it.
Click to expand...
Click to collapse
No problem, that splash annoying screen only happens when you/we are Unlock bootloader.

Related

Question regarding warranty

Hi guys, I recently had the misfortune of getting my Nexus 7 bricked.
Right. So if I claim warranty, how do I go about it? I don't mean the contacting htem and stuff. But what do I say to them to ensure maximum chance of getting the warranty?
I mean, I have voided the warranty by installing custom software on my Nexus. But is there any way I could actually logically persuade them to give me warranty? Or is it just luck? Hoping you get a not-so-smart technician to verify it is suitable for warranty?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Hi guys, I recently had the misfortune of getting my Nexus 7 bricked.
Right. So if I claim warranty, how do I go about it? I don't mean the contacting htem and stuff. But what do I say to them to ensure maximum chance of getting the warranty?
I mean, I have voided the warranty by installing custom software on my Nexus. But is there any way I could actually logically persuade them to give me warranty? Or is it just luck? Hoping you get a not-so-smart technician to verify it is suitable for warranty?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Just call & request an RMA number. If it's truly bricked, they will not be able to ascertain that you installed a custom ROM.
Thank you for that answer but I thought RMAs were for when you returned the device within the first 15days?
And sadly, its obvious that there is a custom rom instAlled. Its hardbricked with an unstoppable bootloop, showing Clockworkmod recovery
Sent from my GT-S5570 using xda app-developers app
What if i do specify some hardware fault that my nexus did have? Like the ghost touch issue. could i get it replaced under that pretext?
Sent from my GT-S5570 using xda app-developers app
Sorry for bumping but I really do need some help. Please?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Thank you for that answer but I thought RMAs were for when you returned the device within the first 15days?
And sadly, its obvious that there is a custom rom instAlled. Its hardbricked with an unstoppable bootloop, showing Clockworkmod recovery
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Why do you say that it is hard bricked? It's near impossible to hard brick a Nexus device. If you see the Google logo when the device powers on, you should be able to go into fastboot mode. Then just use fastboot commands to flash TWRP or CWM recovery and then just flash a ROM from recovery.
veeman said:
Why do you say that it is hard bricked? It's near impossible to hard brick a Nexus device. If you see the Google logo when the device powers on, you should be able to go into fastboot mode. Then just use fastboot commands to flash TWRP or CWM recovery and then just flash a ROM from recovery.
Click to expand...
Click to collapse
Yea, it is hard-bricked. As it is stuck in a bootloop involving CWM-Fastboot-CWM------
It's a long story, which is actually in this thread. http://forum.xda-developers.com/showthread.php?t=2468392
The circumstances of my bootloop are eerily similar, right down to the name of rom I flashed. Or it's probably because of that.
I flashed a new ROM (Kaos Droid 7.0.0) and the fitting gapps some minutes ago from CWM Touch. Everything worked as supposed, no errors, no warnings, nothing. Then I rebooted the Nexus 7 and now it's stuck in the worst bootloop I have seen so far:
The Google Screen appears, stays for some seconds, then I see a screen with the CWM Logo and the text "ClockworkmodRecovery 6.0.38", after this the device seems to reboot and the sequence starts from the beginning again.
I can not get into recovery, I can connect to my PC via USB but connection and disconnection happens every few seconds (because of the bootloop).
Click to expand...
Click to collapse
But I'd rather you answered my questions about warranty since this problem seems totally unfixable. It doesn't respond to any keypress I make except for long-press power.
nobody_nowhere said:
Yea, it is hard-bricked. As it is stuck in a bootloop involving CWM-Fastboot-CWM------
It's a long story, which is actually in this thread. http://forum.xda-developers.com/showthread.php?t=2468392
The circumstances of my bootloop are eerily similar, right down to the name of rom I flashed. Or it's probably because of that.
But I'd rather you answered my questions about warranty since this problem seems totally unfixable. It doesn't respond to any keypress I make except for long-press power.
Click to expand...
Click to collapse
Weird. But if it's rather obvious that you voided the warranty, I don't think they'll send you a new one.
That's the problem. The Google logo does appear and technically I'm supposed to be able to use my fastboot commands to undo the issue. But it doesn't work. Since the nexus doesn't respond to a single button press. So I cannot enter fastboot mode proper.
Yea, I knew that. But what if I get it replaced on some other reason than that?
Sent from my GT-S5570 using xda app-developers app
BrianXP7 said:
Did you somehow interrupted a bootloader flash or wrote "fastboot erase bootloader"? If not and the "Google" logo still appears, you really don't need an RMA.
Click to expand...
Click to collapse
No. It's like when you type reboot recovery. It just goes directly into cwm. And then it reboots and again. And again.
https://dl.dropboxusercontent.com/u/12668781/Nexus7_bootloop.mkv
BrianXP7 said:
Since you can't access MTP, you can try ADB Sideload. (It's a feature in later versions of ClockworkMod Recovery and Team Win Recovery. Why are you still using CWM by the way?) It'll transfer the flashable ZIP to the root of /sdcard and it'll flash immediately after.
RMAs should be only used for last resort bootloader bricks if you don't have access to the proprietary blobs. Luckily, you're fine.
Click to expand...
Click to collapse
Mate, my nexus does not respond in any way to the keypresses I make. So I cannot access clockworkmod, or fastboot mode, or even try to force a regular boot. It just bootloops on and on, completely unimpressed by my presses
BrianXP7 said:
Oh, my mistake. I didn't see your video. Sorry about that. (Bootlooping might be incorrect terminology for recovery. I'm not sure.) Try reflashing another recovery image like TWRP instead? That's the best I can give you for now.
Click to expand...
Click to collapse
Okay, I love that you're atleast trying to help. But the point is I literally have no way of flashing anything on it. I cannot do anything to it, bro. Whatever I do it just keeps bootlooping on and on. If I could access fastboot, I could easily fix this problem but I can't so.
I'd love your feedback concerning what I should do with regards to warranty
BrianXP7 said:
Again, it's not a bootloader brick. You don't need an RMA. In the video, you simply left it booting normally (then falling back to recovery). Also, it's not recovery's issue. It's probably the internal ROM that's made unbootable by some kind of OTA update.
To enter Fastboot mode, turn off your device completely. After, hold Power + Volume Down. Release Power (keep holding Volume Down) when "Google" displays. If done successfully, it'll display an Android lying down. That's Fastboot mode.
Unless you somehow damaged your hardware keys, you might be completely screwed. In order for your RMA to be accepted, you need to remove any trace of modification and relocking the bootloader. If you did restore it to an RMA acceptable state, it's already usable. (Screwing with the bootloader completely, or APX mode, will be accepted as they can't detect if you unlocked the bootloader or not.)
Click to expand...
Click to collapse
hmmmm. Is there a way of completely disabling the bootloader or something?
BrianXP7 said:
Yes, but you need access to Fastboot. If you did have access Fastboot, might as well fix it yourself. Basically, you flashed an incorrect bootloader image or interrupt the writing process. (Just don't think about it unless you have a bootloader backup.)
Click to expand...
Click to collapse
Okay, Can you do something for me?
Type su and then reboot recovery on the terminal.
Now when the Google Image is shown in the beginning, can you try to put it in Fastboot mode instead? Power + Volume Down, like you said.
Tell me if it works
BrianXP7 said:
What? I think you're over-complicating things. You don't even seem to try.
Just turn your device off. (Forced, normally, however you want.) Hold Power + Volume Down until "Google" appears. (That's when you release the power button but keep holding Volume Down.) If you see an Android laying down with a few options such as "Reboot normally", you're in Fastboot mode.
After that, just flash the stock factory images. It's as simple as that.
Click to expand...
Click to collapse
Did you try to do that for me?
I need You to do that for me. And tell me if it works. My Nexus 7 simply cannot be saved. Whatever I do, It doesn't respond. I know all about Fastboot mode, and recovery mode, and flashing factory images. I'm not a n00b like you seem to think. I do have a problem, but it seems to have been caused by random hardware fault rather than a fault on my part. But the result is the same.
nobody_nowhere said:
Did you try to do that for me?
I need You to do that for me. And tell me if it works. My Nexus 7 simply cannot be saved. Whatever I do, It doesn't respond. I know all about Fastboot mode, and recovery mode, and flashing factory images. I'm not a n00b like you seem to think. I do have a problem, but it seems to have been caused by random hardware fault rather than a fault on my part. But the result is the same.
Click to expand...
Click to collapse
@GedBlake;, you're the only person who understood my problem and tried to help me before. Could you perhaps do the same again?
nobody_nowhere said:
@GedBlake;, you're the only person who understood my problem and tried to help me before. Could you perhaps do the same again?
Click to expand...
Click to collapse
Hi, nobody_nowhere..
I will try, but I'm not quite what it is you're asking of me...
If it's concerning RMA, then I don't think I'm going to be of much help, I'm afraid... as I don't know the procedure for claiming under warranty (ie., RMA), having never done it myself.
My own Nexus 7 is just a liitle over a year old now, and I've so far been fortunate in having only had minor, and easily recoverable softbrick/bootloop type situations.
In your second post on this thread, you suggest that RMAs were time limited to just 15 days. I'm not completely sure, but I think this is incorrect. In most countries/jurisdictions, warranties usually run for 12 months. This is certainly the case here in the UK.
The thread you mention, well, having read it yourself, you'll know that I attempted to resolve the problem experienced by the OP of that thread... and it all came to nothing in the end.
There seems to be two recognisable categories of 'brick'... hardbrick, typically caused by a damaged, corrupt or wholly erased bootloader... and softbrick, which can have any number of causes, but is usually always resolvable - principally by accessing fastboot mode. Fastboot mode, is a sort of a 'get-out-of-jail' free card... and I've used it many times in the past.
But if you can't access fastboot mode (apropos of your current predicament), but the bootloader still works (if it didn't, NOTHING AT ALL would happen), your technically not hardbricked.
You have an unrecoverable soft brick... semi-hardbrick maybe? - a third category of 'brick'??
With regard to claiming under warranty... as I've already said, I really have no idea how to go about doing this, but I assume some sort of 'phone conversation would initially start the ball rolling and some questions would be asked of the owner of the Nexus 7...
...but, if it is unambiguously clear (and it sounds like it is, with CWM boot looping), that you've installed custom software, then there's no point in being disingenuous. As soon as they receive the device, they'll know. It you're honest with them, you might have a fair chance of them fixing it. If you lie outrightly, your credibility suffers.
Your best bet, I think, is to emphasize that's it's a hardware issue - emphasize the buttons aren't working properly. Emphasize that you're a knowledgeable Android user, and you're familiar with fastboot, and flashing custom software. The idea, here, is to make it more of a hardware problem, than a software problem - because it then throws the ball back into their court. And personally, I happen to think it is a hardware problem. I have no idea if this will work or not - I'm really just guessing here.
Whether installing custom software itself is sufficient to void warranty is a discussion that could fill an entire thread many pages over, such is the ambiguity of the issue.
It's generally considered, though, that unlocking the bootloader alone, is enough to leave your warranty in tatters... but flashing a Google factory stock image requires the bootloader to be unlocked anyway. So, I'm not quite sure how that contradiction squares itself away!
Indeed the flash-all.* script, that ships with factory stock images, unlocks the bootloader as matter of course. Of course, Google recommend re-locking the bootloader afterwards.
And what of Nexus 7 Jellybean 4.2.2 users, several months ago, who could root without unlocking the bootloader at all, using the motochopper "exploit".
Does rooting with an exploit count as installing custom software... you're messing with /system after all?
Ultimately though, I think that you may have to face an unpalatable truth - that tinkering with your device, does sometimes go wrong... in ways that leave even the most experienced users baffled (and I'm not even close to that level of knowledge and expertise).
There are some posters, here on XDA, who have in their sig., a list of previously owned devices... crossed out... and the word BRICKED next to them. These are the guys with thousands of posts to their name... and their 'graveyard' of dead devices are their metaphorical battlescars.
As soon as you type fastboot oem unlock, you're tacitly accepting that this may happen to you some day... you've effectively 'removed the back' of of that expensive clock/watch/HiFi system or Nexus 7... in the belief you can make it 'go' faster or perform better. Most of the time, you will be successful, and you will make it perform better, with whatever Custom ROM or kernel you've chosen to install.
But sometimes, something will go so horribly wrong... that there is no way back.
And all that is then left is the capriciousness of the company you have warranty with (via RMA)... and you're own negotiating skills.
I really do wish there was some button sequence, or command line I could suggest... but when dealing with the warranty people... you're on your own, sorry to say. Ultimately, and essentially... they may choose to repair it, or not. And beyond that, there's not much else I can add.
Except... best of luck.
Rgrds,
Ged.

Stuck on google screen

I did a factory reset after it locked up now I have the black screen of death with white letters GOOGLE. I can get to the bootloader screen which just returns me to this screen again! I am not tech savvy so please be patient!
mac20132 said:
I did a factory reset after it locked up now I have the black screen of death with white letters GOOGLE. I can get to the bootloader screen which just returns me to this screen again! I am not tech savvy so please be patient!
Click to expand...
Click to collapse
easiest way fix it would be with one of the toolkits which will let you download a reflash the phone, im guessing the bootloaders still locked?
iain26 said:
easiest way fix it would be with one of the toolkits which will let you download a reflash the phone, im guessing the bootloaders still locked?
Click to expand...
Click to collapse
'Lock mode" is locked. when I go to bootloader and hit recovery I just get google screen, restart is the same thing. which toolkit would would I use and where can I get it. this is an Asus Nexus 7 purchased in 2012. I still don't know what happened to it. I was using it (I did have a bunch of tabs open and Dish Anywhere app was running too) and it began slowing way down so I tried closing tabs and it locked!
Thanks in advance for your help!
u'll find some in the development section, i usually use skipsofts toolkit bug wug's works just as well. from there you can download and flash the stock rom
iain26 said:
u'll find some in the development section, i usually use skipsofts toolkit bug wug's works just as well. from there you can download and flash the stock rom
Click to expand...
Click to collapse
I downloaded Skipsofts toolkit. It worked... YEAH... then it downloaded 4.4.2 and I am now screwed... back to google bootloop hell!

Report Your Problems with the Official ASUS Bootloader Unlock Tool Here

There's a bunch of threads about the bootloader unlock tool existing, not any real place to aggregate reports of problems with it. So, if you've attempted to unlock your bootloader using the official ASUS tool and are having problems, please post your situation.
Reported instances:
myself
DeathStolas
ASUS_Khang
Rattraps123
m3t4lw01f
creison
both are experiencing bootloader unlock limbo. The tool seems to have worked, but going into fastboot shows two progressive screens:
1) Unlock Successfully reboot in 5 seconds
2) FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Clearing the cache goes through the loop again. Mind you, this loop only happens when you're trying to get to the bootloader. If you go to recovery or normally boot, you won't have any issues.
However, any commands sent via fastboot fail, so the bootloader is still locked. Attached is an image of the second bootloader screen.
ASUS_Khang is already getting in touch with technical folks to investigate as well, but I figure it best to see if anyone else is having issues with the official tool.
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...

			
				
I have to laugh at the fact that someone on XDA unlocked the bootloader successfully with none of these problems and then ASUS give an "Official Unlock Tool" that screws up the phone of any who uses it... In the words of Alanis Morrisett - "Isn't it Ironic"...
m3t4lw01f said:
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
Click to expand...
Click to collapse
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Same problem here. I used the official unlocker tool and it did what it said it was going to do, but... I got the mythical "Bootloader 5 sec reboot".
asus is working on a fix.
playingmax said:
asus is working on a fix.
Click to expand...
Click to collapse
I'm sure that they are, but it would be interesting to see a source for that claim.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
m3t4lw01f said:
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
Click to expand...
Click to collapse
Sounds good. Can't wait till this is all sorted out and I can continue on with installing Cyanogenmod for my SO. She is really excited since it's her first Android phone.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
here you go
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
look at Khang Thai (ASUS REP) reply. they are working on a fix.
Kona67 said:
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Click to expand...
Click to collapse
Same issue ... I tried without a pin .. now added a pin and it asked me for it when trying to run the app again ... but that didn't help !
Help Ausus!!!
Mine says unlock failed rebooting in 5,4,3,2,1.
any way to relock bootloader as zenfone 6,5,and 4 have
When the 5 second bootloader issue is fixed you should hear about it here first, we have an Asus employee helping us: http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
https://fsfe.org/news/2012/news-20121106-01.en.html
Enviado do meu iPhone usando o Tapatalk
Looks like a user has solved the 5 second reboot issue. Check out the rather convoluted method here: http://forum.xda-developers.com/showthread.php?p=63498472

Unlocked Bootloader splash/boot page?

Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
metpolds said:
Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
Click to expand...
Click to collapse
Its not random, and if you look closer its a bootmenu. you can get past it marginally quicker by just tapping power button or use it to boot to recovery, fastboot/bootloader, etc.
And you cannot remove it.
You can go back to b20...
@nujackk and @lafester .. Thanks both of you for your comments. @nujackk I accept that the screen is a way of booting into fastboot mode, I just never used it, before I installed TWRP I always used MiFav Recovery to boot into fastboot. I am presuming that the screen is an integral part of the boot image and I shall continue to try and hunt it down.
@lafester as always lol your comment.
If either of you are interested I am just going to set up a new thread in "Themes Apps and Mods" where I shall post 3 flashable zip boot animations and hopefully in the coming days I will add to them.
metpolds said:
Presumably like all of you who have unlocked your bootloader, I am faced each time I boot with the garbage page with random text telling me "my software cannot be checked for corruption". Can anyone tell me where that page is stored (partition or folder) would be thankful for any information.
Click to expand...
Click to collapse
The screen is part of the bootloader image. I strongly advise you to just live with it since if you screw up the bootloader you're bricked.
Might I suggest you start by looking around in the bootloader unlock zip. Might give you some idea where it is or if it can be removed.
Also look at older list mentioning it, I remember seeing mention of other phones it's been used on, maybe someone has more info in one of those forums.
And I will look for those boot animations. If I can suggest a superman or superAndy would be nice
Good Hunting
metpolds said:
@nujackk and @lafester .. Thanks both of you for your comments. @nujackk I accept that the screen is a way of booting into fastboot mode, I just never used it, before I installed TWRP I always used MiFav Recovery to boot into fastboot. I am presuming that the screen is an integral part of the boot image and I shall continue to try and hunt it down.
@lafester as always lol your comment.
If either of you are interested I am just going to set up a new thread in "Themes Apps and Mods" where I shall post 3 flashable zip boot animations and hopefully in the coming days I will add to them.
Click to expand...
Click to collapse
I know what you are talking about - on older motorola phones we did away with it - it was just a stored image in those phones. Seeing as how here it is a fully functional menu I would bet any attempt to remove or replace it would most definitely brick the phone. I gave up on it a long time ago.
@lafester .. @nujackk .. @bkores .. @tabletalker7 .. Thanks guys for all your comments - I guess my next step eventually, there is no great hurry for this, is to make certain I have a couple of good backups before messing around with disassembling the bootloader and boot image. If I ever get anywhere with this I will let you guys know.
@nujackk I note your comments re the animations. I'm about to add another Andy animation to the thread but have searched in the past for usable Superman material without much success, however I will see what I can find.
Yeah I haven't seen many that were very good either, but keeping hope alive :fingers-crossed:

Soft brick, locked bootloader

locked bootloader and bootlooping, and i've searched to no avail, thanks in advance.
ps i tried nexus toolkit (wugfresh) and it gets stuck because bootloader is locked
masri1987 said:
Hi all, a friend brought to me a6p to fix, it's locked bootloader and bootlooping, and i've searched to no avail, thanks in advance.
Click to expand...
Click to collapse
If stock ROM/recovery you can still flash an OTA through recovery. There is an option there for OTA update. You have to have fastboot/adb set up and working on a PC. You cannot flash a full image, but you can flash an OTA. If that fails or you can't get it to work, then try a factory reset from recovery.
v12xke said:
If stock ROM/recovery you can still flash an OTA through recovery. There is an option there for OTA update. You have to have fastboot/adb set up and working on a PC. You cannot flash a full image, but you can flash an OTA. If that fails or you can't get it to work, then try a factory reset from recovery.
Click to expand...
Click to collapse
I can't even get to recovery due to bootloop, only thing i can get to on this phone is bootloader
masri1987 said:
I can't even get to recovery due to bootloop, only thing i can get to on this phone is bootloader
Click to expand...
Click to collapse
Well, then you are not SOFT bricked as your thread title suggests. With just a minimal amount of reading you would have found that boot looping + no access to recovery = BLOD. Especially when the bootloader is locked. There are literally dozens of threads on this, and it is a dead end. Your friend is out of luck.
Thanks all, Mod plz close thread. Phone is dead.
hair dryer?
masri1987 said:
Hi all, a friend brought to me a6p to fix, it's locked bootloader and bootlooping, and i've searched to no avail, thanks in advance.
ps i tried nexus toolkit (wugfresh) and it gets stuck because bootloader is locked
Click to expand...
Click to collapse
have you tried the hairdryer trick yet? focus the heat in the region of the back of the phone between the camera and the fingerprint reader. blast it with heat for 3-4 minutes and see if it trips off the big cluster and allows it to boot
Alternatively, I've discovered that instead of using a hair dryer, which completely roasts the phone and makes it hard to hold without using oven mitts during this process, I've used an incandescent lightbulb. It's faster and far more focused as to where it applies heat, again, while the phone is on/bootlooping, just touch the lightbulb against the metal back in the area between the camera and the fingerprint depression... with a 75w bulb it works in a matter of seconds.

Categories

Resources