[Q] Bricked Samsung Infuse - HELP! - Samsung Infuse 4G

I read this post http://forum.xda-developers.com/show....php?t=1524081
I used the link (Heimdall One-Click Return to Stock UCLB3) and followed both steps carefully. The first time I ran heimdall and it finished it went to reboot. It brought up a menu named Android system recovery <3e> samsung Recovery Utils - for BML - then gives me 4 options. reboot system now, apply update from sdcard, wipe data/factory reset, and wipe cache partition. I tried reboot system now only and it brought me right back. Same with wipe data/factory reset and wipe cache partition, same results. I then tried to run heimdall again this time flash bootloaders. This brings me all the way to the at&t screen, but then boot loads the at&t screen again and again. This is as far as I can go. I think I got into this problem initially when I was told my at&t to wipe data/factory reset because I was unable to get any phone signal. I then on my own clicked wipe cache partition and immediately was faced with this issue. Please help me! I don't know what else to do!!
Edit: it will turn on, but will only boot up to the at&t screen. I was unable to get it to turn on previously.
Thank you!
Nate

n.cote21 said:
I read this post http://forum.xda-developers.com/show....php?t=1524081
I used the link (Heimdall One-Click Return to Stock UCLB3) and followed both steps carefully. The first time I ran heimdall and it finished it went to reboot. It brought up a menu named Android system recovery <3e> samsung Recovery Utils - for BML - then gives me 4 options. reboot system now, apply update from sdcard, wipe data/factory reset, and wipe cache partition. I tried reboot system now only and it brought me right back. Same with wipe data/factory reset and wipe cache partition, same results. I then tried to run heimdall again this time flash bootloaders. This brings me all the way to the at&t screen, but then boot loads the at&t screen again and again. This is as far as I can go. I think I got into this problem initially when I was told my at&t to wipe data/factory reset because I was unable to get any phone signal. I then on my own clicked wipe cache partition and immediately was faced with this issue. Please help me! I don't know what else to do!!
Edit: it will turn on, but will only boot up to the at&t screen. I was unable to get it to turn on previously.
Thank you!
Nate
Click to expand...
Click to collapse
read post #2 and #3
read the REF - HOW TO thread

qkster said:
read post #2 and #3
read the REF - HOW TO thread
Click to expand...
Click to collapse
qkster,
The link in post 2 does not allow me to download the file. Can you provide me the file some other way? Step one has been completed, again only boots up to the at&t logo. Also, once step 2 is done, is step 3 necessary? I only want the software stock, nothing rooted or changed if possible. Thanks!
Edit: I found another site to get the link you had in post 2, but now my phone only boots partially to the at&t screen, it freezes, and then completely starts over to the samsung screen instead of boot looping the at&t screen..I think I may have really done something good, lol.

n.cote21 said:
qkster,
The link in post 2 does not allow me to download the file. Can you provide me the file some other way? Step one has been completed, again only boots up to the at&t logo. Also, once step 2 is done, is step 3 necessary? I only want the software stock, nothing rooted or changed if possible. Thanks!
Edit: I found another site to get the link you had in post 2, but now my phone only boots partially to the at&t screen, it freezes, and then completely starts over to the samsung screen instead of boot looping the at&t screen..I think I may have really done something good, lol.
Click to expand...
Click to collapse
as long as it still boots up, it's still good.
make sure your battery is charged.
the kernels in #2 and #3 is for cwm red recovery. either one is fine. if you just want stock att..you may need to boot into stock recovery. reset and try flashing again.

qkster said:
as long as it still boots up, it's still good.
make sure your battery is charged.
the kernels in #2 and #3 is for cwm red recovery. either one is fine. if you just want stock att..you may need to boot into stock recovery. reset and try flashing again.
Click to expand...
Click to collapse
I am a true newbie! What you said sounds good, please help me as to what I need to do to get into the stock recovery reset and flash again. I don't have any experience in this, so I do not know what steps I need to do or what to download and so on.
I should also add that the battery is charged, so that part is good! Also, if booting into stock recovery is press up down volume + power button then I tried that. I tried both options of factory reset and also cache; nothing changed. Anything else I can do, or is it done at this point?
Thanks for your help!

Read this over a few times, Nate.
http://forum.xda-developers.com/showthread.php?t=1437548
it should tell you about how to get into recovery for reset
and how to get into download mode for a reflash
there is a lot of info there...read it a few times..reading the whole thread will help too

Related

[Q] No longer able to boot into ClockworkMod Recovery after latest ROM flash.

After flashing the latest ROM I was messing around with (WajkIUI 2.1.6) the phone would crash and reboot within 30 seconds of booting up. The previous ROM that was running was FAUXMIUI_RG2xV2.0.0 (01/08/2011 [v2.0.0]OVERCLOCK) that was stable except for when I’d turn wi-fi on after being off for 8 hours or so phone would reboot.
I figured I would boot into ClockworkMod Recovery and restore one of the nandroid backups, I tried booting into recovery I found out that I could not. When I hold the volume down and press the power button I see the screen that says software update (like when flashing with OneClickRecoveryFlasher).
Whenever I flash a new ROM I will Wipe data/factory reset, wipe cache partition, and then wipe dalvik before installing zip. I’ve always run cyanogenmod nighties; FAUXMIUI_RG2xV2.0.0 was the first MIUI ROM I’ve used.
When I run OneClickRecoveryFlasher, I do not see any errors on the command prompt so I am assuming it was successful, or at least thinks it was.
I tried to Restore LG G2x Stock Recovery using OneClickRecoveryFlasher and then flashing v5.0.2.0 and still no ClockworkMod Recovery, also tried v4.0.1.5 and still no ClockworkMod Recover.
I then tried http://forum.xda-developers.com/showthread.php?t=1248644 and with that I was able to get back to stock 2.3.3, tried to use OneClickRecoveryFlasher to flash ClockworkMod, still no go.
I tried LG Mobile Update and that proceeded to install something, not really sure what the update was, after the update finished, phone rebooted into stock 2.3.3. Shut the phone down and tried to flash ClockworkMod and still nothing.
I did a hard reset following http://mobilephonerepairguides.blogspot.com/2011/04/lg-g2x-hard-reset.html
I also tried http://forum.xda-developers.com/showthread.php?t=1183168, that got me to stock 2.3.3 but I still could not boot in to ClockwordMod Recovery.
I’m having a hell of a time wrapping my head around what I screwed up. Did I somehow destroy the recovery partition, is that possible? Any ideas what I broke and how to fix it? Can I used adb to view the partition table, would that tell me if something was corrupt?
Any help and ideas would be appreciated, I have tried doing my due diligence and I apologize if I missed something obvious.
Thanks,
-Matt
Faux never made a miui
Did you nvflashed recovery? If no then do that first.
NVIDIA NEVER AGAIN!
If you did the LG Updater it returned your phone to stock everything, including recovery. You need to use NVFlash (One Click method okay) to reflash CWM and then you should be good to go.
When the phone is completely off, hold volume down, then hold the power button and don't let go of both until the second lg logo.
If you hold volume down too early it'll give you the software update screen.
Well that's embarrassing, thanks buru898 that did the trick and got me into CWM Recovery. I never remember holding the power button for that long but it worked and I'll remember that for next time.
Thanks
fcisco13 said:
Faux never made a miui
Did you nvflashed recovery? If no then do that first.
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Sorry, I only wrote in the actual zip file name, I meant RG2x-MIUI v2.1.6-MultiLang/Powered by Faux Kernels CM v0.4.8(01/08/2012)[v2.0.0].
Thanks

stuck on htc boot screen..

I have been searching for hours..and still couldn't find an asnwer..
at first when my phone was still alright I did a factory reset and after that
it stuck on a boot screen with android in the middle...for a long time
then I use vol down + power method to reset it and clean everything (like system,cache and boot) all of them...
now I stuck on the green htc boot screen
I tried to install rom and kernel but still won't work I wonder whats the problem now
any idea???
thanks
nias9527 said:
I have been searching for hours..and still couldn't find an asnwer..
at first when my phone was still alright I did a factory reset and after that
it stuck on a boot screen with android in the middle...for a long time
then I use vol down + power method to reset it and clean everything (like system,cache and boot) all of them...
now I stuck on the green htc boot screen
I tried to install rom and kernel but still won't work I wonder whats the problem now
any idea???
thanks
Click to expand...
Click to collapse
You haven't searched that bad, if not you would have come across this:
http://forum.xda-developers.com/showthread.php?t=1396229
Anyway, are you rooted? if you are rooted and did a factory reset then you don't have a Rom in your phone and that is why you are stuck on the splash screen. You even wiped everything, so probably erased usb debugging drivers from the device.
Well, you have these choices: 1) If you still can access your custom recovery (CWM or 4EXT) then you need to put a rom in your sdcard and flash it. You will have your phone back. You can even restore a nand backup and have your system as it was at that time.
2) If you are S-OFF, but can not access a custom recovery, then flash it again and follow option 1)
3) Use a PD98IMG.zip file to flash a RUU in hboot and you will get back. In the link I provided above, you have several links to those files.
In all cases, you will need an sdcard reader or someway to get the files to your sdcard.
Hope it helps....
thanks!!!!
problem solved
I'm having the same problem stuck on the android boot screen I can access recovery and tried to flash a few different roms but with the same results.
Fortis4Eva said:
I'm having the same problem stuck on the android boot screen I can access recovery and tried to flash a few different roms but with the same results.
Click to expand...
Click to collapse
Did you read the link that glevitan posted a couple posts above yours? Did you try what it says? Which option? What happened?

[Q] No Response

I have downloaded the Indian firmware -> Retail Indian - 5.5.1-EDEM-28-37-SEARET and have updated the file via bootstrap.
I have performed factory reset, wiped cache, wiped dalvik and everything was working fine for 4 hours.
Now my phone is not responding to any keys, a green light is blinking at the top, I have removed the battery and switched it on after replacing it.
It turns on, shows the signal and other icons but the lock button is displayed and it doesnt respond.
If I call to my number I am able to answer it and after ending it again it goes back to same stage.
Please help. I am stuck here.
sandydude said:
I have downloaded the Indian firmware -> Retail Indian - 5.5.1-EDEM-28-37-SEARET and have updated the file via bootstrap.
I have performed factory reset, wiped cache, wiped dalvik and everything was working fine for 4 hours.
Now my phone is not responding to any keys, a green light is blinking at the top, I have removed the battery and switched it on after replacing it.
It turns on, shows the signal and other icons but the lock button is displayed and it doesnt respond.
If I call to my number I am able to answer it and after ending it again it goes back to same stage.
Please help. I am stuck here.
Click to expand...
Click to collapse
You might have to flash the fkz...
I dont have the fkz file, I have a zip file in the sd card.
It will be really helpful if you can provide me steps to do that or can you let me know how to enter recovery mode with CWM.
I am really freaking out, please help me out.
I took a backup of the original ROM before installing this ROM.
sandydude said:
I dont have the fkz file, I have a zip file in the sd card.
It will be really helpful if you can provide me steps to do that or can you let me know how to enter recovery mode with CWM.
I am really freaking out, please help me out.
I took a backup of the original ROM before installing this ROM.
Click to expand...
Click to collapse
Ok, go to this post, it is the beginners thread, and it explains how to flash the fxz factory restore file:
http://forum.xda-developers.com/showthread.php?t=1396650
And need to pick your fxz file from here, not sure of the exact one you need:
http://sbf.droid-developers.org/edison/list.php
Follow the instructions in the link above about halfway down the first post there. Just use the right file from the link I provided, instead of the AT&T retail version in the beginners thread.
The instructions will start with:
HOW TO FLASH A FXZ:
sandydude said:
I dont have the fkz file, I have a zip file in the sd card.
It will be really helpful if you can provide me steps to do that or can you let me know how to enter recovery mode with CWM.
I am really freaking out, please help me out.
I took a backup of the original ROM before installing this ROM.
Click to expand...
Click to collapse
Download the fkz from here.Be sure to choose your region.
First off what OS are you running on you computer?
Download RSD Lite and drag and drop the fkz into RSD. Then boot your phone into fasboot by powering up while holding vol up+down.
Read the noob thread for more detailed instructions found here.
Thank you for the instructions and your help.
This is a AT&T phone which I got it from US.
Shall I install the original AT&T?
I have few steps meanwhile waiting for someone to reply.
I pressed vol up/down and power button and went into system recovery
wiped cache and did factory reset and I tried to install from Sd card.
It said E-verification failed.
I thought I lost hope and I restarted to see if it works.
Now I am able to see the setup screen when we first switch on the phone.
The android setup. I dont want to risk getting into this mess again, this is my sister's phone and she will kill me if it doesnt work properly.
I want to install the actual At&T version. Can I install it from SD card via CWM recovery?
I would be happy to continue with the current Indian version, I am afraid after few hours it will again go into the same mode as it happened today morning when I installed the Victory Rom, I dont understand why I am facing this problem even though I am following all the instructions.
Are there any apps which I shouldn't install like Titanium recovery, my backup, ES file manager? Is the battery saving mode got anything to do with this?
I am really sorry for asking so many questions, I am confused and I need your help badly. I wont play with this phone for ever if I set this straight.
Please advise.
You would want to boot into AP Fastboot then use RSD Lite to flash the AT&T fkz.
farshad525hou said:
You would want to boot into AP Fastboot then use RSD Lite to flash the AT&T fkz.
Click to expand...
Click to collapse
yep, you need to flash the fxz. when you turn your phone on hold both volume buttons and choose ap fastboot. then use rsd lite to flash the fxz.

Nexus 5 stuck at boot animation after flashing stock 5.0

First of all, I have gone through every similar post, but none helped and so created a new post
Device: Nexus 5
Tried to flash: Stock 5.0 image from Google's website
Bootloader unlocked: Yes
Method used: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Tried step 1, it gave an error: archive does not contain system.sig, but it still went ahead with the process and when tried to boot into recovery to perform a wipe data/factory reset, it showed a small Android logo with a red triangle and exclamation mark.
So I tried step two and manually flashed all the files in the order and in the end (after erasing cache), I tried booting into recovery again and got the same thing. Android logo with a red triangle and exclamation mark inside it. I thought the recovery wouldn't have flashed properly, I booted into bootloader again and manually flashed recovery.img and tried. Still the same. WIthout doing a wipe data/factory reset, I do not think the phone will boot up properly. What am I to do here? Stuck in this and cannot use the phone at all. Any help at all is welcomed. Thanks in advance!
Any questions, please ask me.
Edit: I tried locking and then unlocking the bootloader and tried step 2, while booting into the recovery mode, instead of the red triangle, I got the standing Android logo with the blue sphere sort of thing revolving in it. What do I do next when I see that Android logo? Thank you
troll_warhead said:
First of all, I have gone through every similar post, but none helped and so created a new post
Device: Nexus 5
Tried to flash: Stock 5.0 image from Google's website
Bootloader unlocked: Yes
Method used: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Tried step 1, it gave an error: archive does not contain system.sig, but it still went ahead with the process and when tried to boot into recovery to perform a wipe data/factory reset, it showed a small Android logo with a red triangle and exclamation mark.
So I tried step two and manually flashed all the files in the order and in the end (after erasing cache), I tried booting into recovery again and got the same thing. Android logo with a red triangle and exclamation mark inside it. I thought the recovery wouldn't have flashed properly, I booted into bootloader again and manually flashed recovery.img and tried. Still the same. WIthout doing a wipe data/factory reset, I do not think the phone will boot up properly. What am I to do here? Stuck in this and cannot use the phone at all. Any help at all is welcomed. Thanks in advance!
Any questions, please ask me.
Edit: I tried locking and then unlocking the bootloader and tried step 2, while booting into the recovery mode, instead of the red triangle, I got the standing Android logo with the blue sphere sort of thing revolving in it. What do I do next when I see that Android logo? Thank you
Click to expand...
Click to collapse
I just flashed my nexus 5. i am getting the *.sig error too. After flashing, it was taking very long time in boot animation. I nearly to force shutdown. But after around 10 minutes, it is successfully boot.
sorry for my english, just wanted to share my experience. hopefully it help
troll_warhead said:
First of all, I have gone through every similar post, but none helped and so created a new post
Device: Nexus 5
Tried to flash: Stock 5.0 image from Google's website
Bootloader unlocked: Yes
Method used: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Tried step 1, it gave an error: archive does not contain system.sig, but it still went ahead with the process and when tried to boot into recovery to perform a wipe data/factory reset, it showed a small Android logo with a red triangle and exclamation mark.
So I tried step two and manually flashed all the files in the order and in the end (after erasing cache), I tried booting into recovery again and got the same thing. Android logo with a red triangle and exclamation mark inside it. I thought the recovery wouldn't have flashed properly, I booted into bootloader again and manually flashed recovery.img and tried. Still the same. WIthout doing a wipe data/factory reset, I do not think the phone will boot up properly. What am I to do here? Stuck in this and cannot use the phone at all. Any help at all is welcomed. Thanks in advance!
Any questions, please ask me.
Edit: I tried locking and then unlocking the bootloader and tried step 2, while booting into the recovery mode, instead of the red triangle, I got the standing Android logo with the blue sphere sort of thing revolving in it. What do I do next when I see that Android logo? Thank you
Click to expand...
Click to collapse
The first boot takes a LONG time. Just let it go for a while.
jsgraphicart said:
The first boot takes a LONG time. Just let it go for a while.
Click to expand...
Click to collapse
So, I did try as you said. I left it but it kept booting for more than 20 minutes. What to do now?
Same thing happened to me.. You just have to do a factory wipe and then reboot..
When you get to the screen with dead android, with the power button pressed, press vol up key once and you will be in the recovery screen. Do a factory wipe from the screen and reboot..
It should be working now..
manujosephv said:
Same thing happened to me.. You just have to do a factory wipe and then reboot..
When you get to the screen with dead android, with the power button pressed, press vol up key once and you will be in the recovery screen. Do a factory wipe from the screen and reboot..
It should be working now..
Click to expand...
Click to collapse
Incredible. That, worked! I did a rookie mistake by pressing both at the same time which led to nothing. Got it up and running. Thank you everyone for their inputs, couldn't have done without it
The factory wide and reset does not work for me. Stills tuck at the boot animation.
I recently had the same issue with my Nexus 5 and have been back and forth with Google Play support to resolve the issue with no success on that front. However I did get my issue resolved, which was caused by a corrupt /persist filesystem. What I did was this:
Flash CWM Recovery
Reboot into Recovery
notice that /persist isn't mounted, try mounting it and it will fail
Launch and ADB shell
run 'e2fcsk /dev/block/platform/msm_sdcc.1/by-name/persist'
let it fix any errors found
try to mount the /persist partition, it should work now
(Optional) reboot to bootloader, flash whichever recovery you want or stay with CWM
reboot into system, all should be fine now
After successfully repairing and mounting /persist within CWM Recovery I powered off and just flashed the stock 5.0 image from the Google Factory Images page.
A special thanks to bitdomo for his information here which ultimately fixed my issues:
http://forum.xda-developers.com/showpost.php?p=54252961&postcount=3

Can't boot past Google logo white screen after flash-all.bat full restore

Hi all, been running a fairly stable non-Verizon (but on Verizon network) Pixel for several years now. Yesterday when using Google Maps my phone's screen blacked out and it immediately put itself into a boot loop. My bootloader is unlocked so it starts with the warning screen then the white background Google logo screen, then after ~25 seconds the screen blacks out again and it repeats.
I can hold down the power button to force the power off faster so I don't think it's a stuck power button. I have updated my SDK/platform-tools and have a fresh August factory image downloaded and re-downloaded, and all the images extracted to the correct folder and the flash-all.bat factory reset seems to run normally in cmd and on the phone (reboots happen at regular times, etc.) but as soon as it gets to the white background Google screen, cut to black after ~25secs.
I cannot reliably boot into twrp-3.2.3-1-sailfish.img, but it does work sometimes. ADB sideloading any ZIP does not seem to work (freezes TWRP and back into boot cycle). I can sometimes boot into stock recovery and have tried "Wipe data/factory reset" which appears to complete successfully but still does not get me past the white screen logo.
Anything else I can try? Does it seem broken to anyone else? I use custom roms, recently been on Bootleggers with no complaints, but I don't think it's related to that. Something seems irreparably corrupted or something, it was so weird that it just did it to itself mid-navigation and there's nothing I can do to restore it to any state--I even tried flashing last month's factory image, tried changing active slots, anything I could think of. Thanks for your time!
Jesse402 said:
Hi all, been running a fairly stable non-Verizon (but on Verizon network) Pixel for several years now. Yesterday when using Google Maps my phone's screen blacked out and it immediately put itself into a boot loop. My bootloader is unlocked so it starts with the warning screen then the white background Google logo screen, then after ~25 seconds the screen blacks out again and it repeats.
I can hold down the power button to force the power off faster so I don't think it's a stuck power button. I have updated my SDK/platform-tools and have a fresh August factory image downloaded and re-downloaded, and all the images extracted to the correct folder and the flash-all.bat factory reset seems to run normally in cmd and on the phone (reboots happen at regular times, etc.) but as soon as it gets to the white background Google screen, cut to black after ~25secs.
I cannot reliably boot into twrp-3.2.3-1-sailfish.img, but it does work sometimes. ADB sideloading any ZIP does not seem to work (freezes TWRP and back into boot cycle). I can sometimes boot into stock recovery and have tried "Wipe data/factory reset" which appears to complete successfully but still does not get me past the white screen logo.
Anything else I can try? Does it seem broken to anyone else? I use custom roms, recently been on Bootleggers with no complaints, but I don't think it's related to that. Something seems irreparably corrupted or something, it was so weird that it just did it to itself mid-navigation and there's nothing I can do to restore it to any state--I even tried flashing last month's factory image, tried changing active slots, anything I could think of. Thanks for your time!
Click to expand...
Click to collapse
I had this once. This worked for me; clean adb flash latest factory image and nothing else, let it boot to bootlogo, use button combo to get in stock recovery, in there wipe cache/ dalvik cache and reboot. Leave it alone for a few minutes.
Hope this will help, good luck.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
I had this once. This worked for me; clean adb flash latest factory image and nothing else, let it boot to bootlogo, use button combo to get in stock recovery, in there wipe cache/ dalvik cache and reboot. Leave it alone for a few minutes.
Click to expand...
Click to collapse
Hey, thanks for your time. By adb flash you mean the regular flash-all.bat or using fastboot flash commands to flash the imgs manually, right? Or is there some difference between fastboot and adb flashes? Then, my stock recovery does not have a wipe cache / dalvik option, only a wipe data / factory reset option. Is this hiding somewhere? Should I try that in TWRP instead of stock if I can get booted to an img of that? And then you're saying after the fastboot image install, immediately boot into recovery before letting it boot at all?
Jesse402 said:
Hey, thanks for your time. By adb flash you mean the regular flash-all.bat or using fastboot flash commands to flash the imgs manually, right? Or is there some difference between fastboot and adb flashes? Then, my stock recovery does not have a wipe cache / dalvik option, only a wipe data / factory reset option. Is this hiding somewhere? Should I try that in TWRP instead of stock if I can get booted to an img of that? And then you're saying after the fastboot image install, immediately boot into recovery before letting it boot at all?
Click to expand...
Click to collapse
Hi,
Sorry had to be more clear; yes, flash with the flash all.bat.
After the flash it will reboot, let it boot to google logo and try to get in stock recovery.
In stock recovery, if there is no clear cache/dalvik then yes, do wipe data/factory reset.
After the wipe let it boot for a while.
Don't flash anything else then the factory image until it booted up correctly and you set it up.
Good luck. If anything, just ask.
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
Sorry had to be more clear; yes, flash with the flash all.bat.
After the flash it will reboot, let it boot to google logo and try to get in stock recovery.
In stock recovery, if there is no clear cache/dalvik then yes, do wipe data/factory reset.
After the wipe let it boot for a while.
Don't flash anything else then the factory image until it booted up correctly and you set it up.
Good luck. If anything, just ask.
Click to expand...
Click to collapse
Appreciate it. Here's the order of operations:
- flash-all.bat
- After final reboot of flash-all.bat, hold volume down to get into bootloader immediately, then to recovery from there (no other way to boot into recovery mode faster AFAIK)
Unfortunately this is as far as I get. Choosing recovery after going to bootloader right after flash only takes me to the white screen for 25 seconds, then loop. At this point I can't get into recovery at all from bootloader, though it's been sometimes possible in the past. I think it's died, I've actually already ordered a new phone but will keep trying things with this one till that one arrives. I'll update if I'm able to get to recovery anymore, but like I noted in my OP I have tried the recovery factory reset already to no avail. It's too bad that I can't get it to work reliably enough to try your exact order of steps, but probably just a sign of larger problems.
Edit: Finally got to recovery and did the wipe again, and then it started booting to ONLY recovery after that! So the bootloop kinda changed but not so much for the better.
Jesse402 said:
Appreciate it. Here's the order of operations:
- flash-all.bat
- After final reboot of flash-all.bat, hold volume down to get into bootloader immediately, then to recovery from there (no other way to boot into recovery mode faster AFAIK)
Unfortunately this is as far as I get. Choosing recovery after going to bootloader right after flash only takes me to the white screen for 25 seconds, then loop. At this point I can't get into recovery at all from bootloader, though it's been sometimes possible in the past. I think it's died, I've actually already ordered a new phone but will keep trying things with this one till that one arrives. I'll update if I'm able to get to recovery anymore, but like I noted in my OP I have tried the recovery factory reset already to no avail. It's too bad that I can't get it to work reliably enough to try your exact order of steps, but probably just a sign of larger problems.
Edit: Finally got to recovery and did the wipe again, and then it started booting to ONLY recovery after that! So the bootloop kinda changed but not so much for the better.
Click to expand...
Click to collapse
That's a real bummer m8!. Starting to think there's a hardware problem of some kind.
Wish I could help you out a little more, but I can't from a distance.
Hope you're new phone does you well. What did you order? Another Pixel?
Cheers
Sent from my Google Pixel using XDA Labs
Sgace said:
That's a real bummer m8!. Starting to think there's a hardware problem of some kind.
Wish I could help you out a little more, but I can't from a distance.
Hope you're new phone does you well. What did you order? Another Pixel?
Cheers
Click to expand...
Click to collapse
Thanks again for the attempts to help, I got a couple tips from posting on reddit too that didn't get me anywhere either--I've all but called it on the Pixel! But appreciate your time.
I went with the OnePlus 7 Pro and am looking forward to it. I'm disappointed the Pixel didn't make it to a full 3 years of use for me, hoping I can get more out of the next one! Cheers
Jesse402 said:
Thanks again for the attempts to help, I got a couple tips from posting on reddit too that didn't get me anywhere either--I've all but called it on the Pixel! But appreciate your time.
I went with the OnePlus 7 Pro and am looking forward to it. I'm disappointed the Pixel didn't make it to a full 3 years of use for me, hoping I can get more out of the next one! Cheers
Click to expand...
Click to collapse
You're welcome. If I can, I will always try to help.
Hope you will enjoy your OP 7 pro, think it's a nice phone.
It's a shame it did'nt bring you 3 years of pleasure, hope mine will, but will see.
Cheers
Sent from my Google Pixel using XDA Labs

Categories

Resources