Friend's LG G3 Vigor Sprint
Was running KK with ARM7 Xposed, and the Gravity Box module didn't have full capabilities due to the LG Skin, and as Sprint/LG seem to have given up on OTA, we decided to go with CM13 instead.
I found a patched bootloader from an AT&T D725 version, and tried "dd"ing the aboot.bin. I'm sure the path was correct. But the Sprint LS885 didn't like it, and now the device does not respond at all. No screen on, lights vibrate, recovery, nothing. Doesn't show up in Windows at all.
Ubuntu sees it as 9 separate USB drives, all the files are there and through an SU terminal, I have permissions for all the directories. The only response I can get from the device is that after holding the power button for about 30 seconds, all the 'drives' unmount and a few seconds later reconnect. All the data is there as the sizes add up, but now I don't know what to do with it.
The filesystem structure is very strange as I'm only used to the emulated and false sd card from within Android itself. I tried deleting the aboot from /bin on the device, but after holding the power button, when it reconnected the aboot was back there, no luck.
Is there anything I can do, or am I buying my friend a new phone?
I searched for a few hours trying to find a bootloader for the LS885 version, but couldn't find anything. If we get this fixed, should I just go through Flashify with the CM build from the G3 Vigor thread here on XDA?
Will the lg flash tool be able to recognize the phone based on separate partitions with some porting tricks? Upside is I'm learning a lot more about how android works.
If I could get an Android emulator/vm going on Ubuntu, would the lg flash tool(in another VM...) be able to write the stock kdz to the Android VM, if I could find one? I could see what the partitions are supposed to be and just copy and paste from the aboot in the VM to the aboot partition that mounts in Ubuntu when I plug it in? So far I haven't even been able to find the stock boot image, let alone a whole kdz. Would anyone that has one of these G3 Vigors be willing to make an image for me?
Really want to figure this out, even though I got him on the Nexus train already.
Related
So I just got an LG G pad 10.1 VK700 from Verizon the other day. I rooted the device on the first day but never really added any additional apps or software.
Another member in the household was using the tablet and it asked if they wanted to accept the VZW Update for KitKat 5.0. They downloaded the update, and now the tablet is stuck in a bootloop at the Fastboot screen.
There are only 3 options I can select from this screen in the top left using the volume keys: RESTART, RESTART BOOTLOADER & POWER OFF. Any time I select either of the restart options, the screen just goes blank and hangs. I have to manually power off, and upon turning back on I am right back to this limited Fastboot menu.
Bottom left reads:
FASTBOOT MODE
PRODUCT_NAME - E9LTE_VZW
VARIANT - e9lte_vzw Toshiba 16GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - VZ7005xxxxxxx
SECURE BOOT - disabled
LOCK STATE - locked
I booted into Recovery mode, but any of the options I select from the System recovery menu send me right back to the Fastboot screen.
Is there anything to be done at this point?
UPDATE: Problem solved. Research into the other variants of the LG G Pad lead me to the the LG Mobile Support Tool, which you can find by googling B2CAppSetup.exe.
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
I have access to the device via usb / fastboot, adb is not registering. If anyone has any suggestions on what I can try, please let me know. I do not have a backup or a version of the OEM ROM. Every effort so far just sends me right back to the Fastboot screen with 3 options. Anything I can run from command prompt using fastboot alone that would help in this situation? Any way to do a factory restore without having an actual OEM image?
Well im stuck at the verizon screen too but for a different reason
JRSwole said:
So I just got an LG G pad 10.1 VK700 from Verizon the other day. I rooted the device on the first day but never really added any additional apps or software.
Another member in the household was using the tablet and it asked if they wanted to accept the VZW Update for KitKat 5.0. They downloaded the update, and now the tablet is stuck in a bootloop at the Fastboot screen.
There are only 3 options I can select from this screen in the top left using the volume keys: RESTART, RESTART BOOTLOADER & POWER OFF. Any time I select either of the restart options, the screen just goes blank and hangs. I have to manually power off, and upon turning back on I am right back to this limited Fastboot menu.
Bottom left reads:
FASTBOOT MODE
PRODUCT_NAME - E9LTE_VZW
VARIANT - e9lte_vzw Toshiba 16GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - VZ7005xxxxxxx
SECURE BOOT - disabled
LOCK STATE - locked
I booted into Recovery mode, but any of the options I select from the System recovery menu send me right back to the Fastboot screen.
Is there anything to be done at this point?
UPDATE: Problem solved. Research into the other variants of the LG G Pad lead me to the the LG Mobile Support Tool, which you can find by googling B2CAppSetup.exe.
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
Click to expand...
Click to collapse
Hello I have the exact same model I got 28th my g4 and successfully rooted with kingroot and used supersume to change it to supersu. Everything was perfect and running fine and I tried an entropy engine I use on my other rooted phone and it was not help so I disabled it and rebooted like I have with my other one before and it stuck at that horrible red screen lol. I haven't done anything else major to alter anything to do with the OS like installing an OTA and I can only get to the same screens as you. My problem is I don't have a PC and haven't in a very long time and if I get to one I wouldn't know where to start out, last computer I owned has a floppy disk lol but I don't see how I would need to re flash the entire OS because of an entropy engine hickup. If you or anyone know of a way to slap this thing back to reality I would highly appreciate it. I got very familiar with the android os and how it works but never had a PC to go beyond a basic root so technically I'm still a noob in a way. I only care to expand dual window to other apps if I get it fixed cuz I'm not gonna risk screwing with it any more now than I have to, my luck is too bad lol thanks in advance
dadrumgod said:
Hello I have the exact same model I got 28th my g4 and successfully rooted with kingroot and used supersume to change it to supersu. Everything was perfect and running fine and I tried an entropy engine I use on my other rooted phone and it was not help so I disabled it and rebooted like I have with my other one before and it stuck at that horrible red screen lol. I haven't done anything else major to alter anything to do with the OS like installing an OTA and I can only get to the same screens as you. My problem is I don't have a PC and haven't in a very long time and if I get to one I wouldn't know where to start out, last computer I owned has a floppy disk lol but I don't see how I would need to re flash the entire OS because of an entropy engine hickup. If you or anyone know of a way to slap this thing back to reality I would highly appreciate it. I got very familiar with the android os and how it works but never had a PC to go beyond a basic root so technically I'm still a noob in a way. I only care to expand dual window to other apps if I get it fixed cuz I'm not gonna risk screwing with it any more now than I have to, my luck is too bad lol thanks in advance
Click to expand...
Click to collapse
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
JRSwole said:
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
Click to expand...
Click to collapse
Thanks for your response, I have unfortunately tried that too and wipe cache, reset , all back to fastboot. I figured it would be impossible without a pc. Oh yea my stock recovery says modified in the top left corner, but anyway I can get access to a PC But honestly it's been awhile since I even needed to use one and don't know exactly where to start, like navigating around, and how to install what software on the pc. I can't find anyone that will walk me through it locally or online and every tutorial I find is missing some lil step I need. I know Android in detail but after basic root my experience hits a brick wall. I'm capable of more jus got to get broke in on a pc again. Now I only care to root for stuff like freezing apps, gesture control, and really want to use any app in dual window. Ain't screwing with any system tweaks again it was pointless lol I guess I need all the right files and hit up the pc...can't really do worse no??
Sent from my VS986 using Tapatalk
JRSwole said:
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
Click to expand...
Click to collapse
Oh yea I almost forgot I got side tracked earlier. I know there is already a twrp, I have 2 versions (2.8...something and the next version strait off twrp site. I was the one guy it wouldn't flash through flashify for but others claimed it did. God knows really, but I'm gonna wait till I have a PC of my own before I touch my g4 but man the ability to open any app in dual window is just too damn sweet...if I could only change that one word on build prop to false without all the other hassle
Sent from my VS986 using Tapatalk
JRSwole said:
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
Click to expand...
Click to collapse
I tried following your recommendation, but the LGMobile Support Tool said the device wasn't plugged in no matter which combination of buttons I pushed while running the Upgrade Recovery option, and I wasn't able to figure out how to get to download mode either.
gnomesinrome said:
I tried following your recommendation, but the LGMobile Support Tool said the device wasn't plugged in no matter which combination of buttons I pushed while running the Upgrade Recovery option, and I wasn't able to figure out how to get to download mode either.
Click to expand...
Click to collapse
If your problem is from an OTA failing due to taking it while modded and you can get to fastboot the following command might fix it:
Code:
fastboot erase cache
That will delete the OTA zip and break the bootloop.
my sprint lg g4 randomly cut off last night and it is now stuck on repeating the LG logo. My phone was on the stock rom and unrooted. I cannot take it to the sprint store because they said I have a small crack so the techs can't deal with it so m ony option is to spend another $200 on a new G4. I even factory reset the phone from recovery mode and that did nothing. Is there another way I can fix this?
Try connecting the mobile to the computer use the LG Bridge software and there you will find an option update error recovery.. which will basically download the latest same firmware and flash once again
that was a great idea but i tried to plug my G4 into the computer and it wouldnt be recognized even when i downloaded the drivers
Keep pulling the battery till it gets further. If the screen goes dark leave it alone for several hours. Then go into download mode and see if there is a system.img file on /data/media/0
ls -l /data/media/0
If there is an image file that is 4gb then reflash like you would do if you where following the root guide... BE CAREFUL though cause you will have to change the of= paramater to the name of the file of=/data/media/0/system.img or something like that
i honestly have no idea what u said. i plugged my phone up when the phone was in download mode and nothing happened. how can i check if there's a file on my g4 if i can cut the phone on? i have never rooted this specific device so how would i flash it?
So after accidently wiping everything I had on both SD and Internal memory trying to make a custom rom work, I was stuck with a phone that only has TWRP on it, basically. Now after I've been through this guide TO THE LETTER: http://www.droidviews.com/install-stock-android-marshmallow-lg-g3-d855-using-twrp-recovery/ I can see it installed an OS but I cant seem to get my phone to load it! SO then I tried entering recovery mode and getting back to default, it didn't change anything, so I tried installing Zoe rom (https://forum.xda-developers.com/lg-g3/development/zoe-rom-v1-0-mm-6-0-stock-v30a-d855-t3402087) and It STILL ONLY LOADS TWRP even though the installation seemed to be successful!
So what do I need to do? Just flat out delete TWRP? or what? Pleas advise as I'm desperate. If needs be, redirect me to how to just completely reinstall everything from scratch to 6.0 or 7.0 (preferably). I was on 4.x.x for ages and I just wanted to update, instead destroyed my phone. Sigh.
UPDATE: Another thing I've tried is to flash it with KDZ file from the PC. I can see the phone, I can transfer files to it, but windows DOES NOT recognize in the device manage so when I tried to use the flash tool, after clicking "Start" it pops a new window which gets to 60% and then stops saying the phone is not connected to the pc.
Malkishua said:
So after accidently wiping everything I had on both SD and Internal memory trying to make a custom rom work, I was stuck with a phone that only has TWRP on it, basically. Now after I've been through this guide TO THE LETTER: http://www.droidviews.com/install-stock-android-marshmallow-lg-g3-d855-using-twrp-recovery/ I can see it installed an OS but I cant seem to get my phone to load it! SO then I tried entering recovery mode and getting back to default, it didn't change anything, so I tried installing Zoe rom (https://forum.xda-developers.com/lg-g3/development/zoe-rom-v1-0-mm-6-0-stock-v30a-d855-t3402087) and It STILL ONLY LOADS TWRP even though the installation seemed to be successful!
So what do I need to do? Just flat out delete TWRP? or what? Pleas advise as I'm desperate. If needs be, redirect me to how to just completely reinstall everything from scratch to 6.0 or 7.0 (preferably). I was on 4.x.x for ages and I just wanted to update, instead destroyed my phone. Sigh.
UPDATE: Another thing I've tried is to flash it with KDZ file from the PC. I can see the phone, I can transfer files to it, but windows DOES NOT recognize in the device manage so when I tried to use the flash tool, after clicking "Start" it pops a new window which gets to 60% and then stops saying the phone is not connected to the pc.
Click to expand...
Click to collapse
I just got over something like this this morning. First, you need to ensure you have the LG Universal drivers installed for your phone. Get them here.
Next, reboot your machine.
After this, I made sure the PC recognized all 3 modes of my phone, TWRP mode (boot to TWRP, connect), Download Mode (boot to download mode with cable) and, at least in my case, the flashing lights mode (shows up as QHUD Bulk or something).
After that, I ran the KDZ restore program successfully.
Good luck and let me know how it goes.
Hi, I have a Nexus 5X 32GB with TWRP. It's bootloader is unlocked and it's been rooted with Magisk. I'm trying to update to Android 11 or LineageOS. While I was in TWRP, I wiped a few things to get ready for the new OS (11.) I know I didn't select "Internal Storage." Then I accidently restarted the phone. It gave an error that "No OS" is installed. I didn't pay attention to the warning and restarted. Now I can't boot into the phone. And I can't open the bootloader or TWRP to flash a new Android 11 (or old 8.1) OS. It stays on the Google logo screen with the unlock symbol at the bottom. Unlocked bootloader. I tried Power + Down Volume but I can't get it to the bootloader or fastboot or Recovery. Or TWRP. Just the Google screen. I've been searching the internet and this website for a fix. I've tried a lot. My Windows PC can't see my Nexus 5X. Should it? Since I can't boot into it? I'm going to try a Ubuntu Live USB. Will it be able to see it while it's on the Google screen? I found a Thread with instructions including LGUP, but I have to wait to get an OEM Fast Charger and USB Cable. It needs the pins. I don't know if OEM is correct since it didn't come with my phone. Will it work? I ordered one and it should be here in a few days. Then I can try that (on Windows.) If I could get to TWRP or Recovery I could reset my phone. I have bullhead in my Internal Storage "Download" folder. Not sure how to do that since Power and Volume Down isn't working. So how should I boot to bootloader or recovery or TWRP? Windows or Linux? Will my phone show up on my PC with the right drivers? When "powered off" or the "Google screen"? I'd be fine with wiping the whole thing (Including TWRP and start new.) Please reply. I'll be back when I get my new USB cable. Thanks
Bullhead is strong
Hello,
Did you try pressing power button until reboot ?
If a long-press on power makes your phone reboot, you are on the good way : Just hold Volume Down.
PS : Check if your buttons' hardware are ok
PS2 : Give feedback
LiteApplication
short answer...
Take it to a shop that uses miracle box.
Rescue your personal data, install twrp, fastboot, ROM.
Start researching what you're intending to do before beginning the project.
Most of the problems you seem to encounter are created by you not fully comprehending the task at hand.
Many things in life may be learned through this form of trial and error, but it's really not a good idea when it comes to software.
If you had a less well supported device, it would be nothing more than a paperweight right now.
Hi, I'm back...Thanks for replying. I already tried Power + Power Down. No bootloader or recovery or twrp. Just stuck on the Google screen. I had it rooted with magisk, unlocked of course, and TWRP. I wish I wouldn't have wiped it . Or at least installed Android 11 R. If I could get to the bootloader or TWRP, I could flash it. But all I get after holding Power and Volume Down is the Google screen. It won't boot any further. I tried a Hair dryer on a part in my phone but it didn't work either. I found a video where the guy put some sort of liquid or gel on the right part and used heat. I don't know what the gel was so I can't try it. After closing up my phone I get the Google screen. Any ideas?
Hi, I downloaded a copy of Miracle Box version 2.93. Can anyone find instructions for using it? I see a lot of options like: Factory Reset, Unlock Bootloader, Reboot EDL etc... Looks good. My problem is my phone won't show up. In "ports". I've had problems with drivers for my Nexus 5x on Windows. And I can't open my phone and switch from "charging" to "Media Transfer". I need that to see my phone on my PC. Can Miracle Box work without drivers for Windows? Or what drivers do I need (link)? How would a store use it to unbrick my phone? I can follow those instructions. Please reply. Thanks
What drivers should I use for Nexus 5X on Windows 10? Device Manager? I see Nexus Root Toolkit has an option "Soft-Bricked/Bootloop." I need drivers so Windows can see the device. And instructions on using Miracle Box. I'll check back in the morning.
Hi, I bought a used Nexus 6P on eBay. It should be here in a few days. I'll list my Nexus 5X on eBay. I'll say it is Soft-Bricked. Get some money back. Or what drivers do I need for Windows? I have 4 days till it gets here. Please reply. Thanks
Does Miracle Box work on Linux?
Hi, I'm back...I made a little progress. I got my Nexus 6P in the mail. It's working. Now I'd like to continue trying to fix my Nexus 5X. I don't want to take it to a store. Unless I have to. Windows can see my 6P fine, and I have adb/fastboot and drivers installed. It can't see my 5X. I tried "adb devices" on my PC and it comes up with no devices. My 6P works fine. Then I tried restarting it while holding Power + Volume Up/Down. It goes into "Download Mode." It says "Do not unplug while USB is connected." Its says "Firmware Update" but stays at 0%. I searched the web for Download Mode info. Then I plugged in my 5X with LGUP open. I read about that on a thread on this forum. It shows up as "Standby." That's good! So I tried 2 TOT's (H790 and H791.) LGUP ran through successfully. Now when I try to start my phone, it shows the Google screen but still gets stuck. I let it run overnight. I noticed the Google Logo screen now doesn't have the "lock" symbol I used to see. (I had the bootloader unlocked.) So it looks like LGUP locked the bootloader and hopefully did other things. That's good! It'd be nice if it flashed the stock Android 8.1. But, even after LGUP. It still won't boot up. Just stays on the Google screen with the unlock symbol gone. Does anyone know how I can fix it? Then I decided to try Miracle Box software without the box. I can't find info on how to use it. No videos on YouTube. I have my 5X connected to my PC with the OEM cable. Where do I start? MTK? Qualcomm? I got ONE thing to work so it CAN see my phone. "Wipe/Dalvik" completes successfully. That's good! The rest of the tools can't connect to my phone. It says no Device. I don't know what to use (pins, usb scan and etc...) So can anyone instruct me on how to use Miracle Box? How should I start? I need it to see my phone. Flash Stock. What phone pinouts and ports and fire hose? Should I find MTK drivers for my Nexus 5X? Or does it not use MTK? I think "Read" scans for devices. So can anyone explain to me how to use Miracle Box? A link? I need my phone to show up on more than Wipe Dalvik. I'd like to get this fixed myself so I don't have to take it to the store. Please reply. Thanks
P.S. When LGUP runs on my phone the progress of the Download Mode page on my phone moves from 0 to 100%. Then restarts and stays stuck on the Google Logo (without the old Unlock symbol.) So how do I setup Miracle Box?
I found another thread on xda:https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740?nocache=1
Trying a new tool but the TOT's say "The file you are trying to download is no longer available." I have my old TOT's from LGUP. Can anyone find another one? I have the 32GB Nexus 5X.
It looks like I need to set up phone pinouts. I'm not sure what I should use? I have a USB, not RX/TX. I tried using random pinouts and got to a message saying "Press Power to Connect my Phone." Then it says "bad comport." Not sure what comport to use. I tried 1, 3, 4 and 41 (from LGUP.) Miracle Box says it's using "comport 1" and connects successfully. So what pinouts should I use and what comport?
I see I need to find my USB pinouts. I read on gsm forum that if I were using RX/TX and used pins 1 RX and 7 TX I would use 7 RX and 1 TX. What pins do I have on my OEM LG Nexus 5X cable? And it looks like everyone says to use port 41. And I think I can download the pinouts. I see it already has "G5_D+6_D-4". Can anyone find Nexus 5X? For download? It looks like I need ports 2, 3, 4 and 5. Miracle Thunder says to scan those. And what is "Unstable Comport"?
Hi to all, yesterday I tried to root my phone following a guide here on XDA Developers (I don't remember which one). I have a Pixel 6 Pro and I tried to flash boot.img when the phone, after being restarted, starts to bootloop and then I try to turn it off. Then, the panic. The phone doesn't seem to be recognizable by ADB nor fastboot and the screen is permanently black. When I try to hold Power button and other combinations (while plugged to my PC) Windows emits some system sounds like "plugged" or "unplugged device" but I can't find my phone like recognizable.
Phone isn't hardbricked, but softbricked.
Re-flash Stock ROM.
xXx yYy said:
Phone isn't hardbricked, but softbricked.
Re-flash Stock ROM.
Click to expand...
Click to collapse
I can't interact with phone, I just see "Pixel ROM Recovery" on devices when I connect to my PC. I don't even know if it's in recovery, if it's on or off
You might be better off if this thread was moved to the Pixel 6 Pro forum -- I can move this if you request.
But determining if you can get into Fastboot/Bootloader Mode will determine whether this is soft-bricked or not; whether this is recoverable on your end or you'll have to bring it to Google/repair shop. At this point, the only way to get into that mode is through the button combinations -- I've seen some instances where user had to hold the button combination for 1-2 minutes before it popped up; and obviously the device will need to have sufficient battery charge...
simplepinoi177 said:
You might be better off if this thread was moved to the Pixel 6 Pro forum -- I can move this if you request.
But determining if you can get into Fastboot/Bootloader Mode will determine whether this is soft-bricked or not; whether this is recoverable on your end or you'll have to bring it to Google/repair shop. At this point, the only way to get into that mode is through the button combinations -- I've seen some instances where user had to hold the button combination for 1-2 minutes before it popped up; and obviously the device will need to have sufficient battery charge...
Click to expand...
Click to collapse
If you could move it to Pixel 6 Pro forum I'd be grateful, btw idk if I can reboot into bootloader. In fact I would like to know if I can. I tried to read this https://forum.xda-developers.com/t/...evices-with-deleted-bootloader-sboot.3573865/ but I can't understand many things. So if you know how to repair it, I would be very grateful
Chexet48 said:
If you could move it to Pixel 6 Pro forum I'd be grateful, btw idk if I can reboot into bootloader. In fact I would like to know if I can. I tried to read this https://forum.xda-developers.com/t/...evices-with-deleted-bootloader-sboot.3573865/ but I can't understand many things. So if you know how to repair it, I would be very grateful
Click to expand...
Click to collapse
First and foremost is seeing if you can get to Fastboot/Bootloader Mode; When your device is off and not connected to anything (at all, no cord connecting to PC or power plug or anything), hold the Power & Volume+Down buttons simultaneously for up to 2 minutes. If you cannot power on into this mode, you will not be able to flash your device's stock firmware to re-establish any system data that may have been corrupted. It is unlikely, but you may have other options if you can boot into Recovery Mode or somehow into the OS, but if you cannot get into Fastboot Mode, it is too unlikely that you would be able to boot into these. But if you are successful into loading Bootloader/Fastboot Mode...
There's two ways i would suggest you go about it...The first and easiest is to run the official Google Android Flash Tool -- You should be able to load up the latest factory firmware version for your device (Raven), and it should be able to flash the factory image onto your phone to get it working; BE SURE to check the "keep data" (or do not wipe; I can't recall off the top of my head) and to flash to both slots (just to be safe). The second way is to follow THIS GUIDE (as directed by roirraW "edor" ehT's Pixel 6 Pro guide who holds the defacto quintessential central guide in the Pixel 7 Pro forum in which is most up to date, but not catered to "raven") -- specifically you will find what is needed in the "Update and Root Factory Image" section; play close attention to the method using the "flash-all.bat" as that is the simplest and most straightforward way to go about it.. Please read everything and place close attention on being sure to go about it without "wiping" your device (removing the "-w" in the flash-all.bat file), else if you are able to recover your system, your data will not be there when coming back to it and everything would be factory reset.