Related
Hi,
I've never changed anything on my transformer as far as custom roms, never gained root, never even previously booted into the stock recovery. But after one night i woke up to my tablet being burning hot while it was charging. Further investigation showed that it was just rebooting over and over.
I turned it off. left it off to cool down, turned it on.
Bootloop.
I then downloaded the asus firmware put it on an SD card and followed the steps for installing it through asus recovery.
Bootloop.
I can't seem to find a guide on how to actually get nvflash going which is how i'd assume i should fix this.
By the way, I killed my warranty 6 months ago when my girlfriend stood on my tablet (it was on the bed and she walked on the bed in shoes/heels) and cracked the screen. It's been running fine and when it's on it's not noticible. But obviously without the warranty i'm kind of ****ed for an issue that probably Asus did cause.
This actually happened a few weeks ago but my last effort to fix it went south and i haven't thought about it for a while but now i was thinking of taking another crack at it again..
Short question (TL;DR):
Can someone link me a good guide to get nvflash to put either a better recovery or a new non-corrupt rom on my tablet?
Update1: Okay so people here confirm that I have fastboot enabled. But i don't understand how to use it. I've installed the fastboot driver. I've below posted what outputs when i try to push a CWM recovery to it (it looks fine but doesn't seem to work?).
If anyone has some links to how to use any tools via fastboot or APX to recover from here that would be good. Even if you just want me to dump information just tell me how and i'll run anything.
Update2: This time i found out that the fastboot icon is visible to anyone with JB. But fastboot isn't unlocked unless you run the asus apk. So I do not actually have fastboot enabled. Which explains the strange behaviour below.
Because even after trying to install asus official firmwares from SD card and failing, the only alternative remaining is to send it back to asus.
well you need to get it to boot in order to unlock.
perhaps follow the downgrade instructions in general?
lafester said:
well you need to get it to boot in order to unlock.
perhaps follow the downgrade instructions in general?
Click to expand...
Click to collapse
That resulted in a dead android with a red exclaimation mark from his chest cavity.
No dice.
Any other ideas?
Edit: There's a newer version than the one which is on my device, but updating causes it also to die Stupid triangle of death.
I've got 4 options in the pre-boot stuff; which is RCK Android USB and Wipe Data. None of these seem helpful, i was hoping there might be a way to push across using adb but i guess that requires root beforehand.
skythra said:
I've got 4 options in the pre-boot stuff; which is RCK Android USB and Wipe Data. None of these seem helpful, i was hoping there might be a way to push across using adb but i guess that requires root beforehand.
Click to expand...
Click to collapse
If the USB option is available, that should mean your tablet is unlocked and you can use fastboot from your PC to flash a custom recovery.
_that said:
If the USB option is available, that should mean your tablet is unlocked and you can use fastboot from your PC to flash a custom recovery.
Click to expand...
Click to collapse
Okay, that's odd, well so this is a good thing for me then. I can just follow one of the guides here for pushing a firmware onto it? Can you recommend one?
My understanding is i need to get ADB to work by installing the google tools and then install the ADB driver and something something.. I'm going to go read up now about that and pray to my favourite diety of the minute. I assume there should be one for electronics..
Okay so,
using fastboot, installing the drivers and etc. I tried to flash a custom recovery, but so far it doesn't look like it worked; here's the output:
C:\Users\X\Desktop\Android Tools\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.552s
C:\Users\X\Desktop\Android Tools\platform-tools>fastboot -i 0x0B05 flash rec
overy recovery-jb-touch.img
sending 'recovery' (6866 KB)...
OKAY [ 0.867s]
writing 'recovery'...
OKAY [ 0.069s]
finished. total time: 0.944s
C:\Users\X\Desktop\Android Tools\platform-tools>fastboot -i 0x0B05 reboot
rebooting...
It doesn't reboot my tablet at all. It doesn't load the recovery from any form of way i can tell. I'm at a loss again. I still can't find a guide to use fastboot to send any kind of stock firmware or custom firmware to the tablet reliably either. So i'd like any tips/links etc please
Okay so i'm still struggling to do this alone with tidbits strewn across the internet. Every time i think i find new information I find that I can't follow the directions because something else prevents me. Having 'fastboot' hasn't really helped me at all yet.
So i found http://android.stackexchange.com/questions/28077/bricked-my-asus-tf300t-manual-jb-update and i was using that but i'm still finding odd behaviour with fastboot.
Let me explain in copy-paste form.
C:\Users\Skythra\Desktop\Android\platform-tools>fastboot devices
???????????? fastboot
C:\Users\Skythra\Desktop\Android\platform-tools>fastboot devices
015d262e990c0c08 fastboot
C:\Users\Skythra\Desktop\Android\platform-tools>fastboot flash system 01\blob
sending 'system' (800199 KB)...
OKAY [ 97.595s]
writing 'system'...
OKAY [ 0.067s]
finished. total time: 97.665s
C:\Users\Skythra\Desktop\Android\platform-tools>fastboot devices
???????????? fastboot
After using fastboot and issuing a second command it then stops for a countable 5 seconds before it says ??????????. If i say fastboot -reboot it says success but it doesn't reboot the device. So here's my understanding of what happens:
I load the staging area with the BLOB file
The copy to the staging area completes
fastboot goes crazy and doesn't listen
Next reboot doesn't do the android installation (which people have mentioned but i've never myself seen)
I go back to bootloop
If i reboot the device go back to fastboot, i can send it the command "Fastboot reboot" and it works. But any command after "Flash" nothing else works.
So far there has been a total of zero success I'm about to try the older firmware instead of the same as what's on there.
Okay so,
Apparently because fastboot is there doesn't mean I have real fastboot access. Probably this is my guess:
With JB you get access to Read from fastboot but it doesn't truthfully write. The simplified USB interface might take your data as it's sent but it's probably not storing it.
So the truth of the matter is i'm NOT unlocked. It's exactly as I thought.
I can't recover from trying to move any version of asus official firmware onto the ext_sd card and RCKing (even when the android man appears to work correctly, it still clearly restarts into a bootloop).
So this has to be sent back. Which likely won't be covered by warranty due to the fact that many months ago my now-ex-girlfriend broke the screen.
Fantastic
I can only assume this: Either the OTA update failed and my TF700 then melted itself from the charging+bootloop heat. Else when my ex stood on it, it broke something that would only be used in recovery.
Either way I'm down my 700AUD item and sad for the experience
Ahwell. I suppose i could change the title of this to "Solved" and update the OP as "Unfixable".
Seeing what ASUS was telling people fixing their Prime would cost for user incurred damage, you might be better off just to buy a new tablet. Fixing it would only save a hundred bucks or so and they might void your warranty.
hi - i have in my nexus 5 only the google logo and the unlocked key is on the screen;
when i get to fast boot it does see the device.
when ienter " fastboot oem device-info
igot device tampered true
device unlock true
off mode charge - true
when i try to write twrp recovery it says sending recovery okay and writing recovery okay.
but ucant enter to the recovery of twrp.
when i try to flash an image it says:
writing bootloader
failed (remoteflash write failure)
rebooting into bootloader okay
writing radio - failed remoteflash write failure
target reported max size of 1073741824bytes
is there any way to save my phone?
i can enter adb its says on the phone "now send the package you want to apply to the device with "adb sideload filename"..
how do i can send an image?
thank u
re
i try to flash with the lg flash rool - i did everything ok and it stuck in 6% and says"user data erase fail" what can i do?
You're using the batch commands included with the stock ROM to re-flash?
Hi my Nexus 5 also suddenly die too. And I have the same exact problem that you have when trying to flash it. I looked for hours on the internet tried formatting, erasing and many other alternatives and nothing. There are some people experiencing this same problem like us. For no reason the memory is getting corrupt or died. I get mant errors on the cache when I boot to regular recovery. The only recovery that I have manage to boot to (except for the original one) is Clockworkmod using fastboot boot "therecoveryname.img". With clockworkmod I have adb working but still can get the phone to boot or accept factory images. I can't lock the bootloader either.
I think this error was cause by the software. There was a very similar problem that never got fixed for the nexus 7 when lollipop came out.
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
No I don't need to. I tried just to see if the phone will relock itself. I read somewhere in the internet that if you can't relock/unlock the device the nand if fried.
If you look for these errors there are people with LG G2 and LG G3 that are having something similar happen. I think LG hardware is partly behind the problem. I call Google and told them about it and the put me through LG which want me to send the phone for repairs but not free. My guess is that it will be way to expensive to repair and that is not worthy.
Hopefully someone with real repair skill can give us light if this is something fixable by software.
audit13 said:
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
Click to expand...
Click to collapse
I had two different Nexus 5 phones that were stuck in a bootloop with the spinning coloured KK animation.
Every time I unlocked the bootloader, the bootloader would always re-lock itself when rebooting. Even when I managed to unlock the bootloader, I could not re-flash a stock ROM because the bootloader kept relocking itself.
Whenever I unlocked the bootloader, the phone would only take 2 ot 3 seconds to wipe the phone which is too fast.
In the end, I purchased a nexus 5 with a smashed screen to use its motherboard in my defective N5.
I have never come across a post where someone was able to solve the problem unless they had LG replace the motherboard with a new imei.
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
llong31 said:
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
Click to expand...
Click to collapse
If you can access bootloader, you're still OK. Take a breath, grab a recent adb/fastboot download. The Minimal ADB 1.41 copy isn't the latest but it'll work for this purpose. Redo your flash-all.bat. Be patient. May need to flash boota and bootb if you receive errors about boot slots. Search for CZ Eddie's flash-all instructions if unsure.
llong31 said:
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
Click to expand...
Click to collapse
Download the toolkit and choose option to download and install the latest factory build and when it asks if you want to erase data type n (no) so you will not lose anything. Just make sure you are on the slot that was active which i believe u said was b
quangtran1 said:
If you can access bootloader, you're still OK. Take a breath, grab a recent adb/fastboot download. The Minimal ADB 1.41 copy isn't the latest but it'll work for this purpose. Redo your flash-all.bat. Be patient. May need to flash boota and bootb if you receive errors about boot slots. Search for CZ Eddie's flash-all instructions if unsure.
Click to expand...
Click to collapse
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result. The below is the same for boot_a and boot_b
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
llong31 said:
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
Click to expand...
Click to collapse
Well, you're always welcome to send it to me. I'll fix it at no charge one time, plus shipping. I have a team of testers whose only tasks are to break phones, tablets, laptops just so we can put them back together.
llong31 said:
C:\Program Files (x86)\Minimal ADB and Fastboot
Click to expand...
Click to collapse
Get off of minimal and on to Google's fastboot. May not help but there have been a far number of problems with this phone and minimal to not try.
Sounds like when I lost a recovery in one slot doing a sideload in TWRP. I did the temp TWRP load and then added TWRP properly from there. No issues after.
llong31 said:
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result. The below is the same for boot_a and boot_b
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
Click to expand...
Click to collapse
I had to do the flash all once because I wiped the whole OS. I just ran it without specifying _a or _b and it worked like a charm. I think where to flash it is in the bat file so it puts it in the right place on its on. I didn't take out the -w to save my data.
TonikJDK said:
Get off of minimal and on to Google's fastboot. May not help but there have been a far number of problems with this phone and minimal to not try.
Click to expand...
Click to collapse
This was going to be my suggestion. It's all I ever use when flashing through fastboot.
Also, as I believe the above poster stated, I don't specify_a or_b when flashing stuff. It usually just works for me.
Hope you get it all working again. If you can access the bootloader, I believe you will be able to.
GeekMcLeod said:
This was going to be my suggestion. It's all I ever use when flashing through fastboot.
Also, as I believe the above poster stated, I don't specify_a or_b when flashing stuff. It usually just works for me.
Hope you get it all working again. If you can access the bootloader, I believe you will be able to.
Click to expand...
Click to collapse
I am not so sure minimal even supports dual partitions. It's latest version is from April. Long before all of this. Might be why people are getting in trouble. It works if you don't specify partition sometimes it seems....We might be on to something here.
quangtran1 said:
Well, you're always welcome to send it to me. I'll fix it at no charge one time, plus shipping. I have a team of testers whose only tasks are to break phones, tablets, laptops just so we can put them back together.
Click to expand...
Click to collapse
Interest to know what you do? Can I have a job
aholeinthewor1d said:
Interest to know what you do? Can I have a job
Click to expand...
Click to collapse
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to drivers to incompatibilities to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
quangtran1 said:
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
Click to expand...
Click to collapse
That sounds awesome. Here I am doing tech support from home talking to miserable people all day. But yea it's crazy how quiet it is here. I don't really mean the development side of things either I just mean on general any time I've had new phones at release the forums were filled with people. Hoping after the holidays and as back orders are shipping we get some more people here that can figure this out.
I know I won't have an issue rooting and installing TWRP but I'm a little nervous to flash Roms before this is figured out. Especially because I don't stay on any single ROM that long I like to experiment.
aholeinthewor1d said:
That sounds awesome. Here I am doing tech support from home talking to miserable people all day. But yea it's crazy how quiet it is here. I don't really mean the development side of things either I just mean on general any time I've had new phones at release the forums were filled with people. Hoping after the holidays and as back orders are shipping we get some more people here that can figure this out.
I know I won't have an issue rooting and installing TWRP but I'm a little nervous to flash Roms before this is figured out. Especially because I don't stay on any single ROM that long I like to experiment.
Click to expand...
Click to collapse
Understandable.
quangtran1 said:
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to drivers to incompatibilities to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
Click to expand...
Click to collapse
Im sure you didnt mean it this way, but I didnt do anything to brick the phone, I wasnt flashing twrp or a rom or tinkering in any way. I was just using the camera. The more I'm reading, the more I'm thinking its an issue with 7.1.1 with pixels and nexus 6p's. I RMA'd this, we'll see what happens.
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
llong31 said:
Im sure you didnt mean it this way, but I didnt do anything to brick the phone, I wasnt flashing twrp or a rom or tinkering in any way. I was just using the camera. The more I'm reading, the more I'm thinking its an issue with 7.1.1 with pixels and nexus 6p's. I RMA'd this, we'll see what happens.
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
Click to expand...
Click to collapse
There was absolutely no negative connotation in my comment. I stand by my experience that it is improbable to brick a smart phone. I'm just flabbergasted that it happens at all to anyone these days.
llong31 said:
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
Click to expand...
Click to collapse
Thank you for trying, and letting us know how it went. We are all still gathering info, and it's much appreciated. And glad they rma'd it.
TonikJDK said:
Thank you for trying, and letting us know how it went. We are all still gathering info, and it's much appreciated. And glad they rma'd it.
Click to expand...
Click to collapse
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
llong31 said:
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
Click to expand...
Click to collapse
Sure, a corrupt system would certainly cause the battery replenishment logic to misbehave. It won't know when to fast charge, when to maintain, when to trickle, etc.
llong31 said:
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
Click to expand...
Click to collapse
Did you have an outdated fastboot binary? If you can still get in bootloader, I'd try with the good fastboot from the Android SDK.
This is a standard US Google Pixel 128GB that I picked up in January from Swappa. I have not ever modified it in any way. Never been dropped or abused either.
Since early April, the phone would randomly freeze and reboot itself. Sometimes it would be days between reboots, sometimes it would reboot multiple times even before it finishes booting. It's usually random, but I noticed it would always reboot if I am recording a really long video (5-10 minutes). Audio also failed once (no sound could be heard from speaker or earpiece) even after rebooting multiple times. Three days ago, while recording a long video of my kid at Disneyland, it froze. This time, the reboot failed to. The screen flashes some garbled stuff on the screen. Only difference this time is that I know the internal flash memory was almost full before I even started recording the video.
I can't get the phone to boot at all. If I press the vol-down button (doesn't even need the power button), I can get to the bootloader menu. In the bootloader menu, if I choose "Start," Restart bootloader," or "Recovery mode," the screen will flash again forever (I've waited hours). If I choose "Barcodes," then I will see all the proper IME/SKU/Serial numbers and barcodes. Choosing "Power off" works too, if it's not plugged in -- if it's plugged into power, the screen will flash a "static" screen endlessly. I took a video of this happening at Disneyland.
https://youtu.be/VlQ_PpZQ9SY
https://youtu.be/5m8_u0nQ4hE (the flashing screen)
After I got back from vacation, I plugged it into a Windows PC. No ADB access, but I can get fastboot to see it. Trying to reflash the lastest stock image (https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3) fails with this:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.810s]
writing 'bootloader_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.919s
rebooting into bootloader...
OKAY [ 0.052s]
finished. total time: 0.055s
< waiting for any device >
Click to expand...
Click to collapse
The screen would flash the same garbage as it tried to reboot into bootloader. I hold down the volume-down button to get back in and it continues:
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.430s]
writing 'radio_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.542s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
< waiting for any device >
Click to expand...
Click to collapse
Once again the screen would flash the same garbage as it tried to reboot into bootloader. I hold down the volume-down button to get back in and it continues:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: FA6C70300873
checking product...
OKAY [ 0.052s]
checking version-bootloader...
FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1703151359'.
finished. total time: 0.367s
Press any key to exit...
Click to expand...
Click to collapse
That's it. The bootloader screen does show BL and Baseband versions as "N/A", but can't these be overwritten? And is it normal for the device to say LOCKED? This is everything on my bootloader screen:
BL: N/A
Baseband: N/A
Product/Variant: sailfish-US-PVT
Serial Number: FAxxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Toshiba
DRAM: 4096MB Hynix LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Click to expand...
Click to collapse
If it'll help, I can get better photos/videos of the phone. The screen flashes some random distorted Google/Android logos and some "static"-looking pixels.
Any clue about what I should do? I would like to be able to get my photos/videos from the phone. I would also like to be able to recover the phone. Doing both would be awesome. I'm not sure if there is a hardware issue or software issue, but this phone has been horrible since April.
I think either your phone is bricked or your hardware has failed. Fastboot error shows that it cannot identify your bootloader so you have to get a replacement through Google. Check Google photos to see if there are backups of the videos.
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Tulsadiver said:
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Click to expand...
Click to collapse
But wouldn't stock recovery support adb commands? I never checked but if it does he could adb pull files off of sdcard
UPDATE: Someone suggested I try draining the battery and try rebooting. Didn't think it would help, but was desperate, so I left the phone on. A few hours later, it shutoff. I put it back on a charger overnight. Now I can't even start it again. This thing is a brick. So disappointed in Google.
justinxfan said:
I think either your phone is bricked or your hardware has failed. Fastboot error shows that it cannot identify your bootloader so you have to get a replacement through Google. Check Google photos to see if there are backups of the videos.
Click to expand...
Click to collapse
I make sure to backup every night while charging and on WiFi, but this happened at Disneyland and I had the entire day's videos not yet backed up. :crying:
Tulsadiver said:
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Click to expand...
Click to collapse
danielt021 said:
But wouldn't stock recovery support adb commands? I never checked but if it does he could adb pull files off of sdcard
Click to expand...
Click to collapse
adb didn't see the device. Just fastboot.
ken830 said:
UPDATE: Someone suggested I try draining the battery and try rebooting. Didn't think it would help, but was desperate, so I left the phone on. A few hours later, it shutoff. I put it back on a charger overnight. Now I can't even start it again. This thing is a brick. So disappointed in Google.
I make sure to backup every night while charging and on WiFi, but this happened at Disneyland and I had the entire day's videos not yet backed up. :crying:
adb didn't see the device. Just fastboot.
Click to expand...
Click to collapse
Yep sounds like the boot loader is screwed. Phone is a brick. She thing happened to my Nexus 7. I had to replace the motherboard.
did anyone got any leads on this... the same issue with my pixel 128gb... unfortunately it is out of warranty. a working solution would be a great help.
AlphaOrion said:
did anyone got any leads on this... the same issue with my pixel 128gb... unfortunately it is out of warranty. a working solution would be a great help.
Click to expand...
Click to collapse
Sorry to hear this, but I didn't have any solution except for replacing the entire phone. You should contact Google anyhow.
this is so disappointing...I wonder how many people this has happed to already, I was using the phone and it just randomly shut off and wont turn back on..almost exactly what the OP is experiencing...obviously phone is now out of warranty and apparently motherboard needs to be replaced (which is ridiculous!!)….I've never had a phone brick on me ever, never thought it would actually happen, especially on stock everything.
---------- Post added at 08:02 AM ---------- Previous post was at 07:57 AM ----------
Maybe its me....but it seems like more and more people are having this issue...looks like as the hardware gets older the more prone to partition being corrupted....this is not acceptable for a 2 year old phone
I have had numerous pixel replacements. One of them was a hard brick like yours. Even took it to iFixit and they confirmed it was dead. So it may not be uncommon.
I just don't get if photos and videos were so important if no one ever does a weekly backup? Use Google drive, use Google photos, use your USB cable to PC if you don't trust Google.
Phones break, get over it. You want a fast phone? Expect it to die even faster. 2 years for a phone is normal, if you don't think it is get then budget phones are there, with the long life low hardware aspect
I had TWRP and Magisk flashed. Now I wanted to go back, flashed factory, locked the bootloader and now I can only boot into fastboot. Everything elsa ends in a bootloop with a short flashing Google logo.
So anywone with the newest G91 Max phone.
Device: Blu g91 max g0690ww
I couldn't find any info on rooting this since it's so new. So here is how I did it:
Here's the firmware link in case you wanted to patch the boot file yourself. But I'm including it already patched for convenience.
Blu_G91_Max_G0690WW_MT6785_V11.0.03.01_Generic_211222
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
**Your phone will be erased and warranty void**
Download Magisk patched boot file:
magisk_patched-24301_6WKnK.img - shared with FileRun
bananaspider.com
Place file in your fastboot folder.
Under Developer Options of phone, turn USB debugging ON, turn OEM unlocking ON.
Boot to Fastboot mode: hold volume up, down and power until phone screen turns off. Release power until text on screen. Use the up volume to select Fastboot mode and down volume to choose it.
Now that you are in fastboot mode, plug phone into computer and: (I'm using Linux)
Open command or terminal from your Fastboot folder:
[email protected]:~/Downloads/platform-tools$ fastboot devices
1010305022004085 fastboot
[email protected]:~/Downloads/platform-tools$ fastboot flashing unlock
(bootloader) Start unlock flow
OKAY [ 43.978s]
Finished. Total time: 43.978s
[email protected]:~/Downloads/platform-tools$ fastboot flash boot magisk_patched-24301_6WKnK.img
Sending 'boot_a' (32768 KB) OKAY [ 1.056s]
Writing 'boot_a' OKAY [ 0.081s]
Finished. Total time: 1.154s
[email protected]:~/Downloads/platform-tools$ fastboot reboot
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.204s
Once booted, Check Magisk for root.
**DEVS! Any ROM support here?
First of all, thank you! I was successful after following your instructions.
Unfortunately, my sim card is no longer being recognized. Did you have any issues with this?
Hey thanks a lot good to know it helps somebody. no issues with the SIM card so far. I'm using mint mobile SIM.
jasonbiggs said:
Hey thanks a lot good to know it helps somebody. no issues with the SIM card so far. I'm using mint mobile SIM.
Click to expand...
Click to collapse
I am using T-Mobile and it was working at first but then after I restarted the phone it stopped working. All the options for mobile network are grayed out. I tried factory resetting and doing everything over again with the same result. I also verified that it is not the SIM Card. I am at a loss here. I also re-locked the boot loader, which led to a boot loop but I was able to get the phone back into fastboot mode and fixed that. I'm going to try to flash the stock image and see if it helps.
Yes I flashed the stock image just to see if I could and it worked flawlessly maybe that'll help you out good luck.
jasonbiggs said:
Yes I flashed the stock image just to see if I could and it worked flawlessly maybe that'll help you out good luck.
Click to expand...
Click to collapse
Thank you. I didn't actually end up flashing the stock image yet, but I did do a factory reset again and then I left the house for about 30 mins and had left it on the setup screen at home. When I came back the sim card and mobile data were working, so perhaps it just needed some time to connect or what not.
z0ne_tripper said:
I am using T-Mobile and it was working at first but then after I restarted the phone it stopped working. All the options for mobile network are grayed out. I tried factory resetting and doing everything over again with the same result. I also verified that it is not the SIM Card. I am at a loss here. I also re-locked the boot loader, which led to a boot loop but I was able to get the phone back into fastboot mode and fixed that. I'm going to try to flash the stock image and see if it helps.
Click to expand...
Click to collapse
you probably aren't using the correct boot img. Did you use the one provided, or did you root it yourself?
dtingley11222 said:
you probably aren't using the correct boot img. Did you use the one provided, or did you root it yourself?
Click to expand...
Click to collapse
I used the one provided and after that I also patched one myself to see if there was a difference in the very beginning, but it was the same problem. All I had to do was wait about 30 mins and it worked just fine.
z0ne_tripper said:
I used the one provided and after that I also patched one myself to see if there was a difference in the very beginning, but it was the same problem. All I had to do was wait about 30 mins and it worked just fine.
Click to expand...
Click to collapse
oh ok cool
@jasonbiggs there probably is multiple gsis that are available for the phone. search phh gsi or andy yan gsi for lineage.
Any help with Blu S91 Pro? Can’t find firmware download anywhere.
Hey Jasonbiggs I have a BLU G91 MAX but in the developer optimazion when I first got it in the developer options they dynamic system updates so I installed when it said restart to finish installing my dynamic system update when it went to reboot the blu sigh came up but in small whit letters next to it say your phone's corrupted press power button within 5s to continue booting but then my auto rotate wouldn't work and a bunch of other features so I researched and sone1 said unlock the bootloader which I did with an OTG cable and 2 phones using the bugjaeger app and I have to leave my bootloader unlocked because if I close then alot of my apps won't work even tho i don't have a computer I disabled dynamic system updates but it still has the corrupt file and the only way to get rid of that is with a PC but since bootloader is unlocked I was just gonna root it with a better gaming ROM but idk how to that but sorry for the long message but I downloaded your page with the steps to the bootloader thing that is helping people so I was ted what do you think should cause I never closed my bootloader so please anything would be helpful