Folks,
I've spent two days trying to sort this out, so you guys are my last hope!!
My Moto G XT1039 (4G) simply will not load a recovery ROM. It has been unlocked successfully but always falls down when I go onto the bootloader screen. When I select recovery (by clicking volume up), it simply says "boot failed".
I've tried all kinds of different recovery files like Clockworks, TWRP etc. and all with the same result.
I've followed all the instructions to the letter re: copying the SuperSU to the SD card. I've also tried copying it to the root of the phone itself.
When flashing the recovery I get the mismatched partition size error, but from what I've read, this is quite common. To combat it I've used the 'erase' function on fastboot and tried again and again. I've even gone back to Android 4.4.4 from 5.1 and still the same result.
I've tried to just load the recovery out of the ram by using the 'load' command, and all I get is a purple screen and then it goes black. This worries me. I'd have thought that should load come what may. The phone works fine once it boots up normally, btw.
I have no important data on here so I'm willing to go to extreme lengths to get this done. Can anybody help me here? I hate popping up in forums and just asking ****, but I've spent a lot of time reading this forum to try and find a solution, and none of them have worked!
Thanks in advance!
Try fastboot boot recovery.img and tell me if it boots the image you're attempting to flash?
Hi there, i would be happy to help you with this , seeing as i have had multiple problems like this with my Moto G3.
Please drop me an fb message @ https://www.facebook.com/profile.php?id=100010666541958 , and we can work together to sort this out. Then post a fix here on the forums.
therealduff1 said:
Hi there, i would be happy to help you with this , seeing as i have had multiple problems like this with my Moto G3.
Please drop me an fb message @ https://www.facebook.com/profile.php?id=100010666541958 , and we can work together to sort this out. Then post a fix here on the forums.
Click to expand...
Click to collapse
Not to undermine your help, but can't you help out by discussing etc. in this thread? That way other users can follow along, help, and solve similar problems themselves also.
Again, I don't mean to belittle your help (it's much appreciated), but if you can help please do so here where others can see.
HTCDreamOn said:
Try fastboot boot recovery.img and tell me if it boots the image you're attempting to flash?
Click to expand...
Click to collapse
Sorry, in my original post I said 'load' when I meant 'boot'. I've already tried this and I just tried it again just to be sure..... all the phone does is it just boots to a purple screen and hangs when I do what you've suggested.
mikeboorman said:
Sorry, in my original post I said 'load' when I meant 'boot'. I've already tried this and I just tried it again just to be sure..... all the phone does is it just boots to a purple screen and hangs when I do what you've suggested.
Click to expand...
Click to collapse
huh that's weird, as all this does is load into ram so I'm not sure why even that won't work.
Can you tell me what your bootloader screen says?
HTCDreamOn said:
huh that's weird, as all this does is load into ram so I'm not sure why even that won't work.
Can you tell me what your bootloader screen says?
Click to expand...
Click to collapse
Thanks for trying to help by the way. It's much appreciated.
The bootlader on the phone adds two lines of yellow commands for a split second before everything goes purple. One of them is something like "CMD download" and the other is a line that has the number 0982800 at the end of it, but it definitely isn't an error message.
Terminal says this:
mikeboormanmbp:~ applemacbook$ cd desktop
mikeboormanmbp:desktop applemacbook$ cd fastboot-mac
mikeboormanmbp:fastboot-mac applemacbook$ cd android
mikeboormanmbp:android applemacbook$ ./fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.323s]
booting...
OKAY [ 0.253s]
finished. total time: 0.577s
Not many clues here I'm afraid!
mikeboorman said:
Thanks for trying to help by the way. It's much appreciated.
The bootlader on the phone adds two lines of yellow commands for a split second before everything goes purple. One of them is something like "CMD download" and the other is a line that has the number 0982800 at the end of it, but it definitely isn't an error message.
Terminal says this:
mikeboormanmbp:~ applemacbook$ cd desktop
mikeboormanmbp:desktop applemacbook$ cd fastboot-mac
mikeboormanmbp:fastboot-mac applemacbook$ cd android
mikeboormanmbp:android applemacbook$ ./fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.323s]
booting...
OKAY [ 0.253s]
finished. total time: 0.577s
Not many clues here I'm afraid!
Click to expand...
Click to collapse
As you can't even use the bootloader properly its probably best to try to flash a stock img being as fastboot is still working for now. Ask here if you need help with this.
EDIT: See post below
Looks like this thread was posted at the wrong place. Xt1039 to my knowledge is not a moto g 2015...it's a moto g 1st gen, right? I have a moto g 1st gen as well (but a different sku) and could only flash recovery images from carrier (get the device from carrier), also couldn't find a way to boot into recovery. I recommend flashing your xt1039 to the latest firmware for your device and then rooting if you want (I was able to root via booting a superboot img file). Doubt you'll be able to sidelead roms. If you're ready to invest in a moto g 2015, would love to further discussing under this section. Cheers.
HTCDreamOn said:
As you can't even use the bootloader properly its probably best to try to flash a stock img being as fastboot is still working for now. Ask here if you need help with this.
Click to expand...
Click to collapse
Yes, I'd be really grateful for some help with it. So I guess I need a link to download the correct stock image, and then a command for fastboot to flash it?
Related
Hello everybody
It seems I'm quite late with this issue so I wasn't sure whether to post in an old thread or open a new one...
A few days ago my 12-year-old nephew, for 3 month a really proud owner of a Nexus S I9023 came to me desperately sad: He had tried to update to ICS (the manual "update.zip method") and ended up with a totally unresponsive phone like many others back in December.
I do not own an Android device myself and this stuff is all new to me (so sorry for any dumb questions or thoughts ;-) ), but after some googling and finding this great forum and especially AdamOutler's tool (and reading about other people's success with it) I was confident to be able to bring the Nexus back to life. But I'm still stuck at a certain point...
What I've done so far:
-I installed Ubuntu 10.04.3 LTS natively on a PC (I failed with using a virtual installation on my Mac).
-Installed JavaSDK and the UnBrickable Resurrector.
-Downloaded the Android SDK from here and installed it following this advice (I didn't download fastboot separately as it was included in the SDK).
-Downloaded a full ROM from here , extracted the bootloader.img and boot.img from the .zip, downloaded recovery-clockwork-5.0.2.0-crespo.img and put all that stuff in the fastboot directory.
Ok, ready to go now (I think):
I start the Resurrector (R40), select "Nexus S", remove the battery, plug in USB, replace the battery (now the Resurrector recognizes the Nexus) and click "Perform Resurrection" (without holding any button on the Nexus). After a few seconds the Resurrector reports success, showing the "Android with speech bubble" and saying "Fastboot mode" below. On the Nexus the Search- and Homebutton (the both on the right side) are now lit-up, but the display is still black.
At this point I'm wondering if everything went ok, shouldn't the Nexus now already show its bootloader screen like on Adam's image or the battery charging screen ? Anyway, according to the Resurrector everything is fine, so let's continue.
I start Terminal and cd to the fastboot directory. Just to be sure the Nexus is recognized:
Code:
lsusb
Bus 002 Device 023: ID 18d1:4e20
Code:
fastboot devices
34329EB4B3F800EC fastboot
Now I'm not exactly sure what to do next. As far as I've understood some have now flashed the bootloader, boot & recovery images first, others have "booted from the recovery.img (?)", in both cases I end up with this:
Code:
fastboot flash bootloader bootloader.img
sending 'bootloader' (1536 KB)...
OKAY [ 1.629s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.631s
Code:
fastboot boot recovery-clockwork-5.0.2.0-crespo.img
downloading 'boot.img'...
OKAY [ 4.374s]
booting...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 4.376s
But when I try to unlock, I only see this:
Code:
fastboot oem unlock
...
I wait several minutes but nothing happens. I stop this by unplugging the phone and an error appears:
Code:
FAILED (status read failed (No such device))
finished. total time: 561.710s
(I assume waiting nearly 10min is enough?)
I also tried to run fastboot as root with sudo, but that doesn't change anything. I'm really stranded at this point. :-(
This is my first contact with Android and I'm also not very familiar with Linux, but in my humble understanding I should be just one little step away from success, shouldn't I?
For me everything seems to work properly, the Resurrector reports success, saying the Nexus is in fastboot mode now, fastboot is running and recognizing it and also my attempts to "fastboot flash" or "fastboot boot" obviously work until the "Bootloader Locked" error pops up.
So the two big questions are:
1. Is it ok that after successful resurrection only Search and Home are lit-up, but the display remains black or should I see the bootloader or battery charging screen?
2. Why is fastboot stuck while unlocking?
I'm also wondering if it's worth it to set up a Linux/Windows dualboot installation to run fastboot or even Odin in Windows, I can't imagine that I have a better chance that way, this should work with Linux alone, shouldn't it?!
So, I hope I haven't bored you too much ;-)
I would really appreciate some help to make my nephew happy again...
Have a nice weekend!
If the bootloader is locked then you need to OEM unlock then on the screen it should say unlock bootloader? I need to press up with the volume keys and press ok power button.. Then it should be unlocked try that then white everything yo the phone
Sent from my Nexus S 4G using xda premium
In order to unlock oem, you first need to fastboot unlock which you did.
Then, confirm it on your phone which you didn't b/c you can't see/don't have fastboot screen.
And i think you didn't have fastboot screen b/c you didn't hold the buttons like you supposed to.
That's what everyone has to do to enter fastboot.
I think you should follow this thread.
And download and use the ROM package he has linked.
And instead of ODIN which requires Windows, you can use Heimdall which can run on Linux/Mac.
And search how to use Heimdall before flashing.
And if you don't have a backup, download some ROM (stock one preferred) to flash instead of restoring backup.
Also, search how to flash a ROM and clean/full wipe in CWM before flashing.
Same situation here, please help me.
Hello Cicofz and everybody,
I am stuck in about the same situation. Only a little later, my phone bricked on a 4.0.4 upgrade.
I used resurrection and on my phone the same Search and Home lit-up, the display remains black! but resurrection tells me it is in download or Fastboot mode. My fastboot on Mac doesn't get stuck, it tells me everything is Oke. However there is no possibility to get the screen on and really start fastboot on my phone...
So i think I'm stuck on the same thing you got stuck on some weeks ago.
Did you solve the problems in the meanwhile? If so can you please let me know how you did this.
If anybody els can help me please Do...
regards KnoefKnoef
Hello KnoefKnoef,
yes, I was able to bring the Nexus back to life (and a big grin back on my nephew's face) ;-) Afterwards it turned out pretty easy, just fastboot with Ubuntu, no need for any Windows stuff.
It's getting late here in Germany, so I'll try to recall and post what I've done tomorrow. I'm not sure, but I think I've even copied the whole terminal session so I can tell you step by step. I must have a look at the PC I used for it tomorrow...
Good Night
It is running... and yes it is on ICS 4.0.4.
thanks for your Quick reply, butt help is not needed anymore.
After using UnBrickable Resurrector in Linux I got the phone in download mode. with the home and search light glowing.
Then I Switched to Windows using this tread: *OFFICIAL* Android 4.0.4 IMM76D ROM for Nexus S 4G http://forum.xda-developers.com/showthread.php?t=1575502
It ended in a message Failed. Butt the phone was reboot-able. And best of all it is running on ICS 4.0.4.
So I'm very happy now.
It was quite a procedure doing all this on a MAC using Windows and Linux. Butt I eventually managed to do it....
Thanks for your input...
knoefknoef said:
thanks for your Quick reply, butt help is not needed anymore.
Click to expand...
Click to collapse
Pleased to hear that
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.
Hey guys, I'm a new poster but have been reading these forums for a while, hope you can help me solve this huge problem I have..
So I was rooting my Motorola Razr I today, did the Bootloader unlock, everything great, started rooting, everything went nice until all of the sudden this happens:
remount succeded
error: protocol fault (no status)
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting...
error: device not found
Flashing Secured Kernel back...
< waiting for device >
I waited a while to see if it would reconnect by itself, nothing happened, then I restarted the boot, got another "waiting to find device to reboot", but nothing..
Then I disconnected the phone and tried to restart it, but the only menus I can get to are the fastboot and the screen that says that the bootloader is unlocked..
Is there any way I could restore the system or restart the rooting process and get it all the way through?
Any help is appreciated.. Thanks!
P.S.: I have a screenshot of the whole root process window, just can't post it here because I'm a new user.. If anyone is willing to help I can send it to them via email or pm.. Thank you again!
EDIT: sorry, this might be the wrong subforum.. Mods feel free to move it where it belongs..
snowbirddd said:
Hey guys, I'm a new poster but have been reading these forums for a while, hope you can help me solve this huge problem I have..
So I was rooting my Motorola Razr I today, did the Bootloader unlock, everything great, started rooting, everything went nice until all of the sudden this happens:
remount succeded
error: protocol fault (no status)
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting...
error: device not found
Flashing Secured Kernel back...
< waiting for device >
I waited a while to see if it would reconnect by itself, nothing happened, then I restarted the boot, got another "waiting to find device to reboot", but nothing..
Then I disconnected the phone and tried to restart it, but the only menus I can get to are the fastboot and the screen that says that the bootloader is unlocked..
Is there any way I could restore the system or restart the rooting process and get it all the way through?
Any help is appreciated.. Thanks!
P.S.: I have a screenshot of the whole root process window, just can't post it here because I'm a new user.. If anyone is willing to help I can send it to them via email or pm.. Thank you again!
EDIT: sorry, this might be the wrong subforum.. Mods feel free to move it where it belongs..
Click to expand...
Click to collapse
If you have an unlocked BL its really simple... flash CWM recovery. Then download SuperSU from chainfire's site and flash it with CWM and you have root.
As for the system, guess you have to flash with RSD a stock system and re-root.
Sent from my RAZR HD XT925
saloums7 said:
If you have an unlocked BL its really simple... flash CWM recovery. Then download SuperSU from chainfire's site and flash it with CWM and you have root.
As for the system, guess you have to flash with RSD a stock system and re-root.
Sent from my RAZR HD XT925
Click to expand...
Click to collapse
Sounds simple enough, thanks :good:
I actually brought the phone to a neighbor who probably knows more about this stuff than I do, sent him a link to this thread too, maybe he figures it out, if not i'll try what you said tomorrow..
Will keep you posted on how it plays out.. Thanks!
So my neighbour is saying he can't get anything to work, that possibly the phone is bricked :crying:
I'm gonna go by his place in a bit and try what saloums7 said, but if my neighbor is right and the phone IS bricked, is there any way to possibly unbrick it?
I'll be the ass. This is the wrong forum.
You are not your iPhone 5
#tylerdurden
SFG said:
I'll be the ass. This is the wrong forum.
You are not your iPhone 5
#tylerdurden
Click to expand...
Click to collapse
Lol yeah I just realised
snowbirddd said:
Sounds simple enough, thanks :good:
I actually brought the phone to a neighbor who probably knows more about this stuff than I do, sent him a link to this thread too, maybe he figures it out, if not i'll try what you said tomorrow..
Will keep you posted on how it plays out.. Thanks!
Click to expand...
Click to collapse
If you can't boot the phone try downloading the corresponding fastboot files from the firmware super thread and flash with RSD. Then flash CWM with fastboot commands (mfastboot works better for flashing recovery) and then from CWM you can install SuperSU and root.
Sent from my RAZR HD XT925
saloums7 said:
If you can't boot the phone try downloading the corresponding fastboot files from the firmware super thread and flash with RSD. Then flash CWM with fastboot commands (mfastboot works better for flashing recovery) and then from CWM you can install SuperSU and root.
Sent from my RAZR HD XT925
Click to expand...
Click to collapse
I can only find a firmware superthread for the XT925, but mine is an XT890, do they both use the same firmware? Meaning, can I use the XT925 firmware in mine? Thanks
EDIT: Nevermind, I found the firmware I need.. Gonna try to flash it now
EDIT 2: Excuse my noobness, but I think you might have misunderstood what I said.. I do have access to the fastboot menu.. When you say that I should flash the fastboot files, you mean only if I can't get into fastboot right? Or do I have to do it anyway? thanks
EDIT 3: Well I think I might be getting onto something now, I'm following the steps used in the "How to Update/unbrick" video of "TheRazrGuy".. I'll keep you guys posted
Ok so I downloaded the fastboot files for my phone but there is not a single file in there thats flashable through RSD, no xml file, nothing, only .img and .exe.. Did I download the wrong thing or can I flash these files too?
Oh shoot, now the RSD is stuck in "Please manually power up this phone" but when i press the power button the little green light lights up but the screen won't turn on at all... Can I still flash something through RSD if this happens? Meaning could I turn RSD off now and restart it and try to flash again or a different file?
snowbirddd said:
Oh shoot, now the RSD is stuck in "Please manually power up this phone" but when i press the power button the little green light lights up but the screen won't turn on at all... Can I still flash something through RSD if this happens? Meaning could I turn RSD off now and restart it and try to flash again or a different file?
Click to expand...
Click to collapse
I think you're better off asking in the RAZR I forums... they will be better equipped to help you...
Sent from my RAZR HD XT925
Hi Folks,
The problem I am facing is, that, after i used the TWRP-formatting method, my TF700 won't get past the opening-screen of TWRP, instead, this screen continues to kind of blink in a 3 second rythm.
I installed the newest ZOMBI-POP, learned, that it didn't install the Google-Play-Services and the Gopple-Play-Store, reflashed it again and got massive lags (didn't check for the apps though) . I decided to wipe data and did this in twrp, using the command-line sbdag proposed, in the 'advanced' section. Somehow, I must have messed it up, because the 'blinkin' occured since then. I went into fastboot and tried to reinstall twrp 2.85, the result was the following:
C:\adb>fastboot devices
015d29955e53f60e fastboot
C:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7276 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.010s
Since then, the device 'blinks' as described and i even can't switch it off. Is there anything I can do? Searching the forum didnt give any results (maybe because of my minor knowledge) . I appreciate any help or tip, Thanks in advance!!
Tom
edit: Seems, that the problem was a not-working/installed adb-driver, i reinstalled it and fastboot flash worked. So, after two nights of try and error, it solved itself, finally when I overcame to get help here But trying to get into twrp still remains in that blinking with no step egtting further. Booting the system works.
frozentoes said:
But trying to get into twrp still remains in that blinking with no step egtting further. Booting the system works.
Click to expand...
Click to collapse
This means that TWRP crashes after starting, then it's restarted by init. Run "adb pull /tmp/recovery.log" and paste it.
Hello _that,
thank you for your reply. Alay, I did a step back, reflashed twrp with adp (2.8.5, i know, its not the recommended choice 'cause of the formatting-issue, but I will step around it) and flashed my B4-restore back. Since now, it works quite well in the behaviour that it showed before, a bit slow and a bit laggy, but working. I did this, because the device went hot and had a massive battery-drain, altough I installed the patch. Pretty sure, I messed something up while following the recommendations and tuts here, no one to blame but me! I appreciate the help I always find here by reading through the posts and I really appreciate the effort by every helper here - and yours and sbdags for the massive fun you put back in a tablet, that has been abandoned by its creators!! One issue I found with installing RC1 was, that it did not install gplaystore and gplayservices, was that left out or does it fall under rtfm?
Thanks
Tom
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.