Related
hi everybody,
I'm usually more active on auto forums but I need your help.
wanting to install a custom rom, I'm a but lost in the manipulations. Last night when I wanted to turn on the tab (only with the power button), I had the google logo that was displayed at the top right and the small rectangle of recovery menu (start, recovery, reboot bootloader and poweroff). With buttons I could choose one of four functions. I had access to the recovery menu, when I choosen restart bootloader, it well reboot and poweroff worked well too. By when I clicked start I had a small line at the top left telling me "boot failed"
I try to flash everything thanks to a tutorial.
So I'm DL the original elements but still the same issue. Having struggled until 3am I give up. This morning when I tried to turn on the tab, I did even more than what I have explained below whatsoever with the power button or volume down + power nothing happens the screen stays black.
Any Ideas?
PS sorry for the language I'm french
If you bought it from a local store or if a local store carries it, I'd recommend just retuning for a new one. Haven't seen anyone having your problem. If it won't even turn on, then any store should exchange it, or return it, with no questions ask once they see how your tablet is behaving!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
stanglifemike said:
If you bought it from a local store or if a local store carries it, I'd recommend just retuning for a new one. Haven't seen anyone having your problem. If it won't even turn on, then any store should exchange it, or return it, with no questions ask once they see how your tablet is behaving!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
Click to expand...
Click to collapse
I'm seriously thinking of this solution but I'm afraid before they give me a new one they send it to their after sales service. If they find out I have rooted it and unlock the bootloader they will make nothing for me
Have you tried returning it to stock to see if it'll boot then? It could just be a bad flash.
sfreemanoh said:
Have you tried returning it to stock to see if it'll boot then? It could just be a bad flash.
Click to expand...
Click to collapse
I tried every thing.I downloaded nakasig-jwr66v-factory-aebc7b11 and I flash everything but nothing happens. Yesterday evening I was able to boot it (even if it was a bad bood I had only access to recovery mode), but from this morning I tried everything but nothing happens. Even if I plug it to my PC impossible to boot it. The PC do not recognize it (I checked in ADB mode and fastboot mode but the PC do not recognize it)
Good English friend. Can you boot into TWRP? If yes, install any custom ROM after a thorough wipe in recovery. Good luck!
Sent from my Nexus 4 using Tapatalk 4 Beta
swagstr said:
Good English friend. Can you boot into TWRP? If yes, install any custom ROM after a thorough wipe in recovery. Good luck!
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you .
No it doesn't works. For the time being my first to issue is to succeed to boot it at least as yesterday evening.
So if I'm understanding you correctly the Nexus 7 won't even turn on at all now, right? Try holding the power button down for at least 30 seconds and see if it will turn on.
Also, the Nakasig image is for the 2012 version of the Nexus 7 and won't work with the new one. The new 2013 version is named Flo but Google hasn't released the factory images for it yet. However, if you can get the device to power on and back into bootloader mode you should be ok as there are a few unofficial versions of the Flo image on the forum.
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
geckocavemen said:
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
Click to expand...
Click to collapse
+1 Try plugging it in for awhile too. You want to get to the bootloader - the screen with the Android where you go through the options with the volume buttons. Once there,you can use fastboot to flash TWRP and fix from there. Again, stay away from the OLD Nexus files.
Sent from my Nexus 7 using Tapatalk 4
geckocavemen said:
So if I'm understanding you correctly the Nexus 7 won't even turn on at all now, right? Try holding the power button down for at least 30 seconds and see if it will turn on.
Also, the Nakasig image is for the 2012 version of the Nexus 7 and won't work with the new one. The new 2013 version is named Flo but Google hasn't released the factory images for it yet. However, if you can get the device to power on and back into bootloader mode you should be ok as there are a few unofficial versions of the Flo image on the forum.
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
Click to expand...
Click to collapse
I tried to keep on the power button during 1 min with and without charger and pluged to PC : nothing happens. I tried the same thing with volume down + power and nothing happens either
I'm not sure what might help next. Perhaps someone with more experience will come along with advice. If it were me I would probably return it and tell them the power button stopped working.
stef77972 said:
I tried every thing.I downloaded nakasig-jwr66v-factory-aebc7b11 and I flash everything but nothing happens. Yesterday evening I was able to boot it (even if it was a bad bood I had only access to recovery mode), but from this morning I tried everything but nothing happens. Even if I plug it to my PC impossible to boot it. The PC do not recognize it (I checked in ADB mode and fastboot mode but the PC do not recognize it)
Click to expand...
Click to collapse
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
I'm seriously thinking of this solution. I'm just worry if asus find out everything I made
andyli1985 said:
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
Click to expand...
Click to collapse
Hmm.. This is possible. If your device will not turn on, I'm thinking you are SOL my friend. Or in your native tongue: merde pas de chance. Hopefully that conveys it
Sent from my Nexus 7 using Tapatalk 4
andyli1985 said:
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
Click to expand...
Click to collapse
Yes I used this one but I think I have the old version
stef77972 said:
Yes I used this one but I think I have the old version
Click to expand...
Click to collapse
Oh boy... *Grabs popcorn*
Sent from my Nexus 7 using Tapatalk 4
stef77972 said:
Yes I used this one but I think I have the old version
Click to expand...
Click to collapse
the old nexus 7 or the new 2013 model with a camera on the back? is yours wifi only or 3g capable?
The only thing i can think of is to plug into your pc's usb port and hold the power button for 30sec.
Then unplug from PC and press power button for about 15sec and you should see the google logo - if not, i think your bootloader is bricked from flashing the wrong one.
If you do see the google logo, keep holding power and also press vol down as soon as you see the logo - should get you into the bootloader.
Messing up the bootloader is the only way you can brick a nexus, feel sorry for ya man
noob question: so you are using a Nexus 7 (2013) and you flashed an old-nexus-7 ROM on your device? If you're using the new one, here is the ROM for the new one http://forum.xda-developers.com/showthread.php?p=44054613.
I have just had the same problem. Flash the old nexus 7 kernel on the new one, luckily I fixed it
There is a different forum for the 2012 Nexus 7 here. This forum is for the 2013 version.
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
UPDATE: So it wasn't bricked it, as I was able to return to the home screen. After a day of using it though, with the Nexus being buggy (freezing and crashing), it just died. I can't boot it or anything. It's plugged in, but nothing's happening.
Desperate User said:
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
Click to expand...
Click to collapse
Download factory image and do a factory restore:
https://developers.google.com/android/nexus/images#razorjss15q
I personally don't like toolkit. Recommend to root it yourself step by step.
I, being very technically unsavvy, have no idea what to do with the images.
Alright, here's the good news. You haven't bricked your nexus. You can and will fix this yourself, without a tool kit.
Read this thread:
http://forum.xda-developers.com/showthread.php?t=2379797
Then read it again and again until you understand the steps to fix your tablet. I was in your shoes once, years before toolkits were available and I learned how to fix worse problems then you have currently. Take your time.
Desperate User said:
I, being very technically unsavvy, have no idea what to do with the images.
Click to expand...
Click to collapse
Great user name given what you just posted
Desperate User said:
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
Click to expand...
Click to collapse
Same thing happened to me a month ago. Most important thing, don't freak out. Hold power for 20sec to hard reboot, then as soon as google logo appears hold down volume button to enter bootloader screen. From there you can do anything
http://forum.xda-developers.com/showthread.php?t=2391301
Did you boot into the phone after you unlocked the bootloader but before you tried to root? Do you have a custom recovery installed?
doe you have a custom recovery?
if so check if you still have your internal storage, i had the same problem as you but there is a bug going around when u unlock your bootloader your internal memory is wiped see this threat for feather explaining: http://forum.xda-developers.com/showthread.php?t=2380913
In my case i booted to fastboot and did the command fastboot -w and then it created new user partitions and then i could flash the stock image and then it worked again
Hope i helped u
No custom recovery, but I have an update:
So after using the vol- and power buttons, I was able to bring the Nexus back to its home screen for a day (so it wasn't bricked), but it was really buggy- freezing on my and shutting down. Now though, I think it's bricked; I can't power it up, can't do anything. So I can't turn it on now :/. Probably gonna take it to see a repair store sometime soon.
@bananagranola: no I didn't
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Sent from my Nexus 7 using xda app-developers app
HuxenShah said:
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't know, maybe you should make your own thread rather than hijack mine.
Desperate User said:
No custom recovery, but I have an update:
So after using the vol- and power buttons, I was able to bring the Nexus back to its home screen for a day (so it wasn't bricked), but it was really buggy- freezing on my and shutting down. Now though, I think it's bricked; I can't power it up, can't do anything. So I can't turn it on now :/. Probably gonna take it to see a repair store sometime soon.
@bananagranola: no I didn't
Click to expand...
Click to collapse
owh, does it al least charger when u plug it in?
silvan g said:
owh, does it al least charger when u plug it in?
Click to expand...
Click to collapse
I can't tell. The damn thing doesn't respond to anything. It's plugged into the wall right now and not doing anything. My PC doesn't recognize that it's plugged in.
Desperate User said:
I can't tell. The damn thing doesn't respond to anything.
Click to expand...
Click to collapse
Try plugin it in the charger and wait 5 min and then try to boot it with power+volume down
HuxenShah said:
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Click to expand...
Click to collapse
If you're not rooted, it's just a stock update. There isn't any more risk than there is for any stock version, and you shouldn't lose data. If you buy a Nexus 7 2013 a few months down the line, after current stock with JWR66N is sold out, I believe it'll come with that update out of the box.
Desperate User said:
I don't know, maybe you should make your own thread rather than hijack mine.
Click to expand...
Click to collapse
I understand you're frustrated, but that was a little rude...he's just trying to get help, just like you.
Desperate User said:
I can't tell. The damn thing doesn't respond to anything. It's plugged into the wall right now and not doing anything. My PC doesn't recognize that it's plugged in.
Click to expand...
Click to collapse
Unrecognized in ADB or fastboot? Can you get into bootloader (boot while holding power and volume-down)? If you haven't tried fastboot while the phone is in the bootloader, and you can get into bootloader, try "fastboot devices." If you can do that, download a custom recovery and flash it from fastboot. Then format data and reboot.
silvan g said:
Try plugin it in the charger and wait 5 min and then try to boot it with power+volume down
Click to expand...
Click to collapse
Done and nothing
Download the platform tools: http://www.androidfilehost.com/?fid=9390355257214632011 and
TWRP for the WiFi: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.0.0-flo.img or LTE version: http://techerrata.com/file/twrp2/deb/openrecovery-twrp-2.6.0.0-deb.img
Unpack the platform tools zip into a folder, copy the openrecovery-twrp-2.6.0.0-deb.img file into the same folder and open a command prompt into this folder (hold shift while right clicking on the folder and the option should be there).
Try to turn the nexus off by holding the power button for 30 secs, connect it via USB to your PC and wait till the screen shows the white charging information. Now press the volume down button on the nexus and keep holding it while you press the power button. After a moment you should see the green android with the open belly and some device information on the screen.
Now go to the command prompt you opened and enter: fastboot boot openrecovery-twrp-2.6.0.0-deb.img for the LTE or fastboot boot openrecovery-twrp-2.6.0.0-flo.img for the WiFi version.
After a few seconds you should see the recovery screen, if it asks you for a password just hit cancel, there choose "Wipe" and then "Format Data" and confirm that you want to format data. After it has done its stuff go back to the main menu and choose reboot and let it boot into system. Now it should work again.
Guhrasoh said:
Download the platform tools: http://www.androidfilehost.com/?fid=9390355257214632011 and
TWRP for the WiFi: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.0.0-flo.img or LTE version: http://techerrata.com/file/twrp2/deb/openrecovery-twrp-2.6.0.0-deb.img
Unpack the platform tools zip into a folder, copy the openrecovery-twrp-2.6.0.0-deb.img file into the same folder and open a command prompt into this folder (hold shift while right clicking on the folder and the option should be there).
Try to turn the nexus off by holding the power button for 30 secs, connect it via USB to your PC and wait till the screen shows the white charging information. Now press the volume down button on the nexus and keep holding it while you press the power button. After a moment you should see the green android with the open belly and some device information on the screen.
Now go to the command prompt you opened and enter: fastboot boot openrecovery-twrp-2.6.0.0-deb.img
After a few seconds you should see the recovery screen, if it asks you for a password just hit cancel, there choose "Wipe" and then "Format Data" and confirm that you want to format data. After it has done its stuff go back to the main menu and choose reboot and let it boot into system. Now it should work again.
Click to expand...
Click to collapse
That would be great, but when I plug in the tablet to the PC the screen doesn't show any information. That and I can't turn on my Nexus in any way, including the volume down and power method.
Desperate User said:
That would be great, but when I plug in the tablet to the PC the screen doesn't show any information. That and I can't turn on my Nexus in any way, including the volume down and power method.
Click to expand...
Click to collapse
How long has it been charging? I'd give it a couple hours, then try the bootloader again.
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Perchy35 said:
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Click to expand...
Click to collapse
Just use my guide, at the bottom of it it has everything you need to reflash stock firmware hold the power and volume down button until you get to the fastboot/ bootloader screen, also since you replaced the battery and did your own repair we still might not be able to help you because there's to many variables of user interference now, and yes Google kind of has made it a bit more complicated to root devices now unfortunately
Thanks for the reply, please can you put a link to your guide?
Perchy35 said:
Thanks for the reply, please can you put a link to your guide?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Perchy35 said:
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Click to expand...
Click to collapse
Yes. Hold power and volume down, it'll look a few times and catch, you'll see fastboot. The Android guy and red and white text. May take a few loops
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Perchy35 said:
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Click to expand...
Click to collapse
Whats the carrier?
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Here you go. Amazon Jeter Firmware. That's the main folder.
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Spaceminer is correct, once you catch that sweet spot with the phone to get it in bootloader/fastboot mode just flash the firmware and you should hopefully be good to go, if you want it rooted my guide covers that to but let's just get you a working phone first before you try to root lol
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
You can either flash 8 or 9, what I would do is flash 8 then update it to 9 then if you want it rooted root it
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hey so out of curiosity did you get it fixed and working?
ninjakira said:
Hey so out of curiosity did you get it fixed and working?
Click to expand...
Click to collapse
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
Also can I check that without USB debugging selected this method will override and flash still?
Perchy35 said:
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
I am having issue with the last part, getting "The credentials you provided cannot be determined to be authentic" ?
Also can I check that without USB debugging selected this method will override and flash still?
Click to expand...
Click to collapse
Wait what are you needing your Moto id for? The links for the stock firmware are in my guide, just follow the bottom section of it
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Perchy35 said:
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
Click to expand...
Click to collapse
If you don't have the bootloader unlocked then that is something you can do if you want the phone rooted if not you don't have to unlock the bootloader to flash stock firmware
Perchy35 said:
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Click to expand...
Click to collapse
You either didn't install adb minimal or you have a bad cord, type fastboot devices and if nothing pops up saying you have a device in fastboot then it's one of the 2 things I said, extract the contents from the rar or zip file you got from adb minimal download, then install what you extracted
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Perchy35 said:
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Click to expand...
Click to collapse
Sorry been at work and I'm ona break, I totally forgot though you can use Moto smart Assistant for pc to fix this more than likely, so download and useMoto smart Assistant
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Larzzzz82 said:
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Click to expand...
Click to collapse
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
simplepinoi177 said:
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
Click to expand...
Click to collapse
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
helpless_user said:
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
Click to expand...
Click to collapse
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
In fastboot you can boot to a recovery.img; fastboot boot twrp.img
Download TWRP .img here.
(that recovery menu allows adb mode also).
Here you can(re)flash zip/image etc.
Format /data to ensure it is not encrypted.
For example, flash the extracted images of the OTA images from Google.
simplepinoi177 said:
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
Click to expand...
Click to collapse
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Not able to figure out the exact fix
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
@OP, I am still stuck with the exact same issue. How did you exactly fix it? After running the solution given, I'm back at the infinite logo screen again.
Edit: It worked, thank you so much! This is a life saver.
simplepinoi177 said:
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Click to expand...
Click to collapse
Hi i have the same issue with different device lenovo tab m10 tbx605L and i cant boot the recovery.img it throws me this error.Can u give me any ideas?
helpless_user said:
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Click to expand...
Click to collapse
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
EDIT: Quoted the wrong poster. My reply is an answer to the quoted poster instead of the poster who revived a dead thread with a question for a totally different device.
Strephon Alkhalikoi said:
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
Click to expand...
Click to collapse
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
safaan0313 said:
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
Click to expand...
Click to collapse
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Strephon Alkhalikoi said:
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Click to expand...
Click to collapse
Hmm well thanks for your indirect F**k off
safaan0313 said:
Hmm well thanks for your indirect F**k off
Click to expand...
Click to collapse
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Strephon Alkhalikoi said:
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Click to expand...
Click to collapse
Right I knew that.I am sorry.I was so damn angry at my own mistake.I AM S O R R Y.But off the record I just repaired my tab
My device went into brick while flash android14 fail .At the beginning,it can boot to fastboot mode,but now it's no response at all& can't get into fastboot.The google help center need original purchase email ID for further help,i can't find it due to I bought the pixel6 pro from second hand market .
How to rescue the pixel6pro brick without fastboot?
Google pixel flash tool online and boot into fast boot follow instructions and you should be able to bring it back
Here's the link:
Android Flash Tool
flash.android.com
thelostsoul89 said:
Google pixel flash tool online and boot into fast boot follow instructions and you should be able to bring it back
Here's the link:
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
thanks for your advice,but the device can't boot to fastboot mode
ok6669 said:
thanks for your advice,but the device can't boot to fastboot mode
Click to expand...
Click to collapse
I apologize your original post said that it can... not that it can't
thelostsoul89 said:
I apologize your original post said that it can... not that it can't
Click to expand...
Click to collapse
thelostsoul89 said:
I apologize your original post said that it can... not that it can't
Click to expand...
Click to collapse
^_^
Can you boot into the recovery? You could sideload an ota
Code:
adb sideload "path to ota.zip"
Tip: right click on the ota.zip and select 'copy as path' and paste it
fil3s said:
Can you boot into the recovery? You could sideload an ota
Code:
adb sideload "path to ota.zip"
Tip: right click on the ota.zip and select 'copy as path' and paste it
Click to expand...
Click to collapse
nope,brick deeply
ok6669 said:
My device went into brick while flash android14 fail .At the beginning,it can boot to fastboot mode,but now it's no response at all& can't get into fastboot.The google help center need original purchase email ID for further help,i can't find it due to I bought the pixel6 pro from second hand market .
How to rescue the pixel6pro brick without fastboot?
Click to expand...
Click to collapse
Did you hold power and volume up for 15-30 seconds? Also, did you try and charge it? Could be dead
Let's put it this way, you're phone won't awaken until it's internal signature can be re verified. It uses ACM as an initial protocol then goes into a serial gadget mode. At the current moment someone straight up stole my Pixel 6 or else I would still be working on a unbrick solution. If anyone's willing to donate a bricked one I'm all for putting in the effort to continuing development.
The nature of the dead brick is to ensure that no data on your phone can be compromised. So the the method to unbricking also requires you to a sort of NAND erase, as seen on previous Exynos devices. I had just gotten all the tools set up and even made my own ACM handshake in coordinance with the Open Source Vendor Code and someone just decided, oh hey, look it's a nice phone let's take it. And now I have to continue making payments on it. Life sucks sometimes.
NonStickAtom785 said:
Let's put it this way, you're phone won't awaken until it's internal signature can be re verified. It uses ACM as an initial protocol then goes into a serial gadget mode. At the current moment someone straight up stole my Pixel 6 or else I would still be working on a unbrick solution. If anyone's willing to donate a bricked one I'm all for putting in the effort to continuing development.
The nature of the dead brick is to ensure that no data on your phone can be compromised. So the the method to unbricking also requires you to a sort of NAND erase, as seen on previous Exynos devices. I had just gotten all the tools set up and even made my own ACM handshake in coordinance with the Open Source Vendor Code and someone just decided, oh hey, look it's a nice phone let's take it. And now I have to continue making payments on it. Life sucks sometimes.
Click to expand...
Click to collapse
I think you are the one unbrick the pixel 6pro who is the most closest.i fell that you are very humor person.Life can't be as good as you think, but it won't be as bad as you think
So I have the same problem. It restarted and said something about your files are corrupt and cannot be trusted. I got it to boot to bootloader, used android tool online and it did the same thing. Now I cannot get the phone to turn on at all. So now I need help please!!! I cannot afford to buy a new phone currently.
did you try plugging in for 30 mins? If can’t boot to anything after that, only Google can fix it.
Arealhooman said:
did you try plugging in for 30 mins? If can’t boot to anything after that, only Google can fix it.
Click to expand...
Click to collapse
Yeah Google's fix is $600. Which is ridiculous. I had it plugged in all day, now I just have it sitting on my dresser hopefully it will just start on it's own. I don't know what else to try. I tried pressing the power button for 60 seconds. I tried power volume up for 60 seconds. I tried power button volume down for 60 seconds. Nothing seems to work. Yet if I plug it in to my laptop, you can hear the ding as if it connected. So I don't know what to think.
Jdemio said:
Yeah Google's fix is $600. Which is ridiculous. I had it plugged in all day, now I just have it sitting on my dresser hopefully it will just start on it's own. I don't know what else to try. I tried pressing the power button for 60 seconds. I tried power volume up for 60 seconds. I tried power button volume down for 60 seconds. Nothing seems to work. Yet if I plug it in to my laptop, you can hear the ding as if it connected. So I don't know what to think.
Click to expand...
Click to collapse
Sounds like a dead display, especially if its being recognized by a laptop
ok6669 said:
My device went into brick while flash android14 fail .At the beginning,it can boot to fastboot mode,but now it's no response at all& can't get into fastboot.The google help center need original purchase email ID for further help,i can't find it due to I bought the pixel6 pro from second hand market .
How to rescue the pixel6pro brick without fastboot?
Click to expand...
Click to collapse
If your phone is recognized as Pixel Rom recovery, then I am very sorry to you. only the official Google service will save you, or you will find the same phone with a broken screen in the trash that you can take a fee from there and put it on yourself
Jdemio said:
Yeah Google's fix is $600. Which is ridiculous. I had it plugged in all day, now I just have it sitting on my dresser hopefully it will just start on it's own. I don't know what else to try. I tried pressing the power button for 60 seconds. I tried power volume up for 60 seconds. I tried power button volume down for 60 seconds. Nothing seems to work. Yet if I plug it in to my laptop, you can hear the ding as if it connected. So I don't know what to think.
Click to expand...
Click to collapse
What is it recognized as?
Arealhooman said:
它被认为是什么？
Click to expand...
Click to collapse
pixel cdc -amc device! and then disappear
idark11 said:
If your phone is recognized as Pixel Rom recovery, then I am very sorry to you. only the official Google service will save you, or you will find the same phone with a broken screen in the trash that you can take a fee from there and put it on yourself
Click to expand...
Click to collapse
Google is not serve in our country,asking google for help is not convenient for me
ok6669 said:
pixel cdc -amc device! and then disappear
Click to expand...
Click to collapse
Pic?
Jdemio said:
Yeah Google's fix is $600. Which is ridiculous. I had it plugged in all day, now I just have it sitting on my dresser hopefully it will just start on it's own. I don't know what else to try. I tried pressing the power button for 60 seconds. I tried power volume up for 60 seconds. I tried power button volume down for 60 seconds. Nothing seems to work. Yet if I plug it in to my laptop, you can hear the ding as if it connected. So I don't know what to think.
Click to expand...
Click to collapse
i think google have the secret weapon to recover the brick pixel,it 's a simple software problem for google. a piece of cake