Related
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
mochamoo said:
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
Click to expand...
Click to collapse
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Thank you. My s4 is rooted. I *think* that I have solved my issue. I was able to get it to go into Odin mode power+vol down. I didn't connect to a computer (am at work and all of my android tools are at home). I just cancelled out of Odin mode and it booted up just fine. Now I tried to go into recovery again and got the same error as above and was able to get out of it the same way. I was able to go into ROM manager and flash regular non-touch CWM recovery and was able to boot to it without issue.
I suspect that my flash of the touch via terminal emulator didn't work right. Can anyone who has done it this way let me know how long the flash should take? I was at the su prompt and entered the dd line above (copy and pasted to avoid typos). It appeared to do something...there were some numbers maybe 5 or 6 per line and then it went back to the prompt so thought it was done. This didn't take it more than about 15 seconds to do. What should I see here?
I know that I can just flash it via ROM manager but wanted to be able to do it myself without rom manager and also be able to flash the latest twrp img if I want to (goo.im seems broken at the moment). Maybe I will try to do it via Odin later.
TIA.
you rock
I just got this same error and your steps worked perfect
Same problem except on i545vrufnk1
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Hello, I went to flash a recovery package with flashify and got the black screen with kernel fail. I was on the latest nk1 kernel.
please help
Hi! I'm really sorry to revive such an ancient thread but I've a similar problem.
I tried to use the dd command to update TWRP and wound up at this spot, but I was running a custom 5.1.1 system (jflte dev something or other from oct 2014 - recovery needed to be updated in order to install 7.1.1). So I tried to ODIN back to the old bootloader because I read it may have just become locked again, and now the system seems broken or missing, I'm not sure which. Phone no longer boots into the system and I get this error at recovery, so I'm hoping that if I flash an older factory image onto the phone, it'll restore it.
My question is, if I flash a stock image onto the phone, will it overwrite the bootloader and make my custom recovery dreams impossible? I went as far as to transplant the insides of this phone into a replacement when it first broke to maintain my MDK bootloader, so I'm really hoping I didn't **** myself here.
----
Edit:
So I've fixed my phone! The whole ordeal wasn't too too bad, but it was somewhat time consuming and difficult to divine on my own.
Now, I realize now I may have actually flashed the wrong .img file, which may have caused this whole issue. I'm actually not certain, because through the method that I fixed this problem with, I was able to flash what I would later find out was an incorrect .img for the recovery (jfltexx instead of jfltevzw ) but it did work properly, and I only found out when I got an error on trying to install the LineageOS zip.
I tried a bunch of things, but the one that worked was converting a twrp .img file to a .lok (loki) file. At the time of this writing, it happens that there's a bug in the latest twrp version that also prevents you from installing the system, but downgrading back to an older version will work, and I assume after 3.1.2 the bug will be fixed.
In order to do this, I wiped the system back to an MDK 4.2.2 system image I found here: https://forum.xda-developers.com/showthread.php?t=2301259
(dead link? Here's an archive: https://archive.is/LDnaY - I hit a bunch of dead links when I was figuring this process out and it was frustrating)
which preserved the mdk bootloader (because flashing anything newer than this will lock the bootloader, I've been told. I didn't dare try.)
I rooted that image by downgrading to the prerelease kernel and using motochopper to root, then upgraded back to the mdk kernel.
Then I grabbed the loki_tool from this thread:
https://forum.xda-developers.com/lg-g2/general/guide-how-to-flash-cwm-6-0-4-4-lokitool-t2813514
(Dead link? Here's an archive: https://archive.is/F7k29 )
and used a twrp .img file to create the recovery.lok file
Flashing through this method restored my custom recovery, and also made the samsung unlocked padlock bootscreen go away (I miss it already!). Having Android 7.1.2 on this phone is quite a treat though!
Hope that anyone else who winds up here in the future finds this useful! And I hope those links
I am trying to flash TWRP on 10B (was running 23C and did KDZ flash back to 10B). Rooted via Stump, installed BusyBox, TWRP Mananger and Official TWRP App. Since TWRP didn't appear to install TWRP I did some more research I read people had success with 'Partitions Backup' to backup stock recovery partition and then use 'Flashify' to install TWRP. So I downloaded the twrp-3.0.2-0-vs985.img and installed that to recovery after backing up stock. Next reboot takes me into TWRP. If I then boot normally and then shutdown and enter recovery again I'm back in stock recovery. So it's like the flash is temporary.
Anybody care to educate me about what I am doing wrong. I'm sure this was easier in the days of the 'all-in-one' root/TWRP installer but can't download that anymore and I'm tired of the updates and poor performance so want to try custom ROM's.
Any help would be appreciated. I am thinking maybe I need to install recovery again when booted into TWRP? Not sure.
I am wondering if the flash doesn't work because I flashed a TWRP img without the "bump" designation? I am beginning to think the best way to install reliably is using the 'dd' command from adb over remote PC connection (or via su in a terminal shell if advisable)? Any thoughts on using this method and whether I can go right to the latest version of TWRP for the vs985 (twrp-3.0.2-0-vs985.img).
skay said:
I am wondering if the flash doesn't work because I flashed a TWRP img without the "bump" designation? I am beginning to think the best way to install reliably is using the 'dd' command from adb over remote PC connection (or via su in a terminal shell if advisable)? Any thoughts on using this method and whether I can go right to the latest version of TWRP for the vs985 (twrp-3.0.2-0-vs985.img).
Click to expand...
Click to collapse
I think you might have solved your own problem! You can't use just any TWRP image. It has to be specifically bumped for the G3.
iBolski said:
I think you might have solved your own problem! You can't use just any TWRP image. It has to be specifically bumped for the G3.
Click to expand...
Click to collapse
Thanks for the reply iB. I only tried flashing with the VS985 img files. But I didn't start with one that specifically had the "bump" or "bumped" designation in the filename. I am wondering if the later version that I used doesn't actually install bump to recovery but it intended to be installed as an updated version of TWRP on a previously "bumped" recovery image? Sorry for getting into the weeds here but I actually just stayed rooted on 23C for quite a while until I couldn't take it anymore. I looked at moving up to G4, G5, V10 and V20 but it seems like the G3 is the best value LG phone for custom ROMs and hardware is still not bad overall.
Anyone know of a way to determine if recovery has been flashed with TWRP img before attempting 'factory reset' option? I based my questions thus far on the assumption that if it flashed successfully I would see only the 'factory reset' and 'reboot' options in the new recovery, but I see all 5 options as before flashing TWRP.
skay said:
Anyone know of a way to determine if recovery has been flashed with TWRP img before attempting 'factory reset' option? I based my questions thus far on the assumption that if it flashed successfully I would see only the 'factory reset' and 'reboot' options in the new recovery, but I see all 5 options as before flashing TWRP.
Click to expand...
Click to collapse
It's been a long time (over a year) since I last used TWRP on my G3 (which is now in the cell phone cemetery as it died last December), but I believe if you boot normally, hook your phone to your PC and use adb reboot-recovery, it SHOULD go straight into TWRP, but I could be wrong. Otherwise, factory reset is the only way to get to it. The normal "recovery" screen shows up first, from what I remember and you have to go that route to get to TWRP. You should always, always back up your phone whenever doing things like this anyways. I don't know if there is a way to "verify" that it is installed, so once again, backup everything first. Just in case.
Thanks for the help and the confirmation that the standard recovery is expected once it's installed. Based on videos I expected something different. But I tried it after backing up and it works fine. Now time to flash!!
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
sako21 said:
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
Click to expand...
Click to collapse
Flash latest A13 update u will get stock recovery
pankspoo said:
Flash latest A13 update u will get stock recovery
Click to expand...
Click to collapse
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
sako21 said:
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
Click to expand...
Click to collapse
Just try keep unrooted boot. Img backup of your current rom.
Then go ahead though it's got currpted (one person faced that at insta but he used that commnads when he has twrp it must work with stock recovery) but after restoring boot imgae all was fine.
But try at u r own risk later don't tag [email protected] pankspoo - guide
Thanks. Will try that out.
And yes, wont tag you!
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
Wait u want to relock bootloader?
You need a otg adapter. Put Stock boot.img and the last ota update file to the usb storage.
flash stock boot.img via FKM
go to developer settings and lock oem
uninstall magisk with restore all (not image)
start phone in bootloader
fastboot flash relock
fastboot reboot recovery
select update from storage
use otg adapter with ota file
install
restart
done
For any assistance contact @sakarya1980
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
did you get the relock bootloader?
If you're still searching for the stock recovery, I've attached the .img file (unzip it first)
Hi everyone. I recently bought an Alcatel 1t 7 (8067) tablet, 1Gb ram, 16Gb rom, just wifi (no 4G), mt6580 processor, android oreo go edition; a very simple and cheap tablet, but it seemed me a very nice one, because is slim and lightweight; worhty of root access, but also a custom recovery. I prefer TWRP recovery because it's more organized... ¡Anyway!... So I got down to work, but at first, as I didn't know how to backup all firmware, and when I learned how to do it and did it (esentially I could "tame" sp flash tools, hehe), I had already lost my original recovery file. Is needless to say that TWRP recovery, as far as I know, isn't available for this model, so I needed to port it, but as at first, I didn't know how to back it up, I overwritten it with other recoveries that didn't work. I mean, at this time, the tablet is working but is without recovery tool. I'm not going to talk about root access, because I already could get it, by using magisk manager, but I need my recovery image file, back; both to reinstall it and port it to TWRP.
So finally, if anyone has this stock recovery file, the full stock rom for it, or even better the ported TWRP for this tablet, please share it to me.
Thanks in advance for your attention.
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
aIecxs said:
just boot into android, stock recovery will be repaired from /system/recovery-from-boot.p automatically
Click to expand...
Click to collapse
Thank you for reply. Ok, I booted android. I have enabled usb debugging so, when android booted, I connected it to adb, and opened "adb reboot recovery" command, to be sure that android would reboot into that mode; but it didn't, it just rebooted several times on boot screen, and when it "got tired" of rebooting, it booted into android. Didn't boot into recovery, so I guess, It didn't repair it.
PS: I was looking for that file "recovery-from-boot.p" on that path, and there isn't such file, i can't find it.
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
you can port TWRP with kernel from boot. you can use this TWRP as base
aIecxs said:
on older devices it is /system/etc/install-recovery.sh or something, it's maybe disabled if your device isn't completely stock anymore?
Click to expand...
Click to collapse
¿Must that file have the same size that the original recovery image? Because the only file named recovery that i can find on that path is named "recovery-resource.dat" and its size is 807kb, and as I have seen before, is that recovery images have several Mb of size.
aIecxs said:
you can port TWRP with kernel from boot. you can use this TWRP as base
Click to expand...
Click to collapse
Two questions about it; as far as I can remember twrp image must be compatible not only for the same chipset, but the same screen resolution ¿Am I right? Also, this tablet is 600x1024 px, or 1024x 600 on landscape mode. All TWRP that I have installed on former machines, worked on portrait mode, so I wonder miself ¿Could TWRP also work on landscape mode?
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
aIecxs said:
/system/etc/recovery-resource.dat "generates a binary patch that creates the recovery image starting with the boot image. (Most of the space in these images is just the kernel, which is identical for the two," so the resulting patch is a executable file with smaller file size than the actual recovery.) It's just few lines of code.
https://android.googlesource.com/platform/build/+/b32161a^!/
Click to expand...
Click to collapse
Ok... I can find that file on my tablet, but I'm not so skilled android user, as for rebuild recovery from that file or even port TRWP from that file, so ¿Is there an easy way to do it ( or at least, comprehensible for middle skilled android users) ? ¿How? (and supposedly this machine is easy to port and root, they say on internet. I also have a huawei y7 2018 for rooting, that seems harder to root. But that's a another (my next) struggle in here, hehe)
aIecxs said:
TWRP is available in landscape mode. you can read more about here
[GUIDE]Porting TWRP without source
Click to expand...
Click to collapse
Another question. ¿Are those programs who claim to help to port TWRP with just some clicks, reliable? (for instance TWRP porter for mediatek)
aIecxs said:
I don't think touchscreen will work at all, so resolution doesn't matter. you can use TWRP from cmd line
https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
All the TWRP recoveries that i have ported before, have had a working touchscreen, but as I understand, resolution requirement is not only for touch calibration, but for correct displaying of TWRP GUI (that all buttons and options fit on the screen), Now I've read that new versions of TWRP adjust automatically to any screen resolution, ¿Is that right?
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
HCU-client needs 4 credits for Huawei.
I may reply in new thread.
aIecxs said:
dump boot.img off device. you can use SP Flash Tool read back. download base TWRP and unpack with AIK. replace kernel and see what happens. if TWRP booted with black screen try to enter adb shell. get partition list from adb shell. create proper twrp.fstab and flash again. you should have functional TWRP now even without working GUI.
if touchscreen is disabled it might possible to hexpatch kernel with ghidra like I did for mine.
Click to expand...
Click to collapse
¡No, man! If TWRP porting is kinda hard having the stock recovery image, without it, is a brain smashing task (or at least for me). I mean, I really don't understand well, how to port twrp starting only with boot.img, I mean, without recovery img. I've saw tutorials about the use of carliv kitchen (windows version), and seems easy, but all tutorials are made with stock recovery.img available, not with boot.img. So, what can I do there?
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
aIecxs said:
as I said. replace kernel with that from boot.img and see what happens? the generic base TWRP actually is recovery.img already, so you might lucky and it works? trial + error...
Click to expand...
Click to collapse
I saw a tutorial about. It said that I must to unpack stock recovery and twrp recovery, and replace some files of unpacked twrp recovery, with respective unpacked stock recovery files, and edit some files on twrp unpacked folder, and finally repack it.
Until that point, I assume that it should work, I mean, having stock recovery. But I did that, but using boot.img, I renamed all boot resources, to recovery, for instance, boot.imgkernel to recovery.imgkernel; and replaced it, repacked it, and reflashed it, but nothing happened, I mean, it didn`t want to boot into recovery. It`s interesting to "experiment", but I`m gonna try to find its original stock recovery, to at least get it back.
Hello!
I would like some help, alcatel 1T7" 8086 no4g I likely bricked it. There's nothing else than a black screen. The tablet doesn't react to anything. The computer finds it as unknown USB tool. No visibilty is shown. What can i do with it,for it to work? Or should i just put it in the trash?
Thank you for the reply.
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
Boot to fastboot mode and install TWRP or any custom recovery on both slots.
Now reboot to recovery and change the active partition.
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
What happens when you turn your device on? Are you able to boot to bootloader? Does the screen turn on at all?
If the file size was wrong, you were probably using the wrong file...although there's been issues with the latest Platform Tools, and bad USB cables can cause problems too.
TheMystic said:
Boot to fastboot mode and install TWRP or any custom recovery on both slots.
Now reboot to recovery and change the active partition.
Click to expand...
Click to collapse
TWRP isn't really relevant to A/B devices unless installing a custom ROM. If he's able to get into bootloader, TWRP isn't going to be any more help than reflashing the factory image.
V0latyle said:
TWRP isn't really relevant to A/B devices unless installing a custom ROM. If he's able to get into bootloader, TWRP isn't going to be any more help than reflashing the factory image.
Click to expand...
Click to collapse
In case of a bootloop, one can boot into recovery if it is installed on both slots. And from there the active partition can be changed, and this is possible only using custom recovery.
This is my understanding. I could be wrong because it's been a while since I got away from all these stuff, which are also becoming increasingly complex for no proportionate returns.
TheMystic said:
In case of a bootloop, one can boot into recovery if it is installed on both slots. And from there the active partition can be changed, and this is possible only using custom recovery.
This is my understanding. I could be wrong because it's been a while since I got away from all these stuff, which are also becoming increasingly complex for no proportionate returns.
Click to expand...
Click to collapse
The problem is, the recovery kernel is packaged into the boot image alongside ramdisk and the system kernel. Most A/B devices like Pixels do not have a recovery partition. TWRP does not support the compression that's used for the stock recovery as packaged, and if you flash the TWRP image to /boot, it overwrites everything else - meaning that your system will only boot to TWRP, because that's the only thing in /boot.
You could potentially live boot TWRP since this doesn't flash the boot partition, but again this is generally unnecessary and won't be of much help when you can simply reflash the original boot image
V0latyle said:
The problem is, the recovery kernel is packaged into the boot image alongside ramdisk and the system kernel. Most A/B devices like Pixels do not have a recovery partition. TWRP does not support the compression that's used for the stock recovery as packaged, and if you flash the TWRP image to /boot, it overwrites everything else - meaning that your system will only boot to TWRP, because that's the only thing in /boot.
Click to expand...
Click to collapse
Are all these done to enhance security or discourage custom mods? Or both?
For a short time when I had rooted my OnePlus 8T, I would flash TWRP on the inactive slot. That's because Oxygen OS would replace any custom recovery with its own recovery during boot, so this allowed me to boot into the inactive slot (which now has TWRP) and then run commands from there, so I don't have to use a PC each time.
TheMystic said:
Are all these done to enhance security or discourage custom mods? Or both?
Click to expand...
Click to collapse
Neither. It's just compression to reduce the amount of space the recovery kernel takes up in the boot image. If TWRP supported this compression we could potentially replace the stock recovery with TWRP. But, there isn't really much need to do this; most custom ROMs for the Pixel series just flash everything via web ADB.
TheMystic said:
For a short time when I had rooted my OnePlus 8T, I would flash TWRP on the inactive slot. That's because Oxygen OS would replace any custom recovery with its own recovery during boot, so this allowed me to boot into the inactive slot (which now has TWRP) and then run commands from there, so I don't have to use a PC each time.
Click to expand...
Click to collapse
That's not the case here. The boot slot cannot be changed without booting into TWRP. You could potentially install TWRP to boot_b, then set slot B as active; upon the next boot, the device will load TWRP. You could then do whatever you need to in TWRP, then set slot A as active, but you'd have no way of getting back to TWRP.
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
The likely reason this occurred is because you used Platform Tools 34+. These 34 versions can't boot into fastbootd. For now you should be using Platform Tools 33.0.3.
You can't just switch slots and boot up the slot you switched to. You can only boot into the slot where the last firmware was flashed to. Therefore, when you changed your slot from b to a, you would have to flash the firmware onto slot a before it would boot into that slot.
If you can still get into the bootloader/fastboot mode, try flashing the factory image or using Android Flash Tool.
Lughnasadh said:
The likely reason this occurred is because you used Platform Tools 34+. These 34 versions can't boot into fastbootd. For now you should be using Platform Tools 33.0.3.
You can't just switch slots and boot up the slot you switched to. You can only boot into the slot where the last firmware was flashed to. Therefore, when you changed your slot from b to a, you would have to flash the firmware onto slot a before it would boot into that slot.
If you can still get into the bootloader/fastboot mode, try flashing the factory image or using Android Flash Tool.
Click to expand...
Click to collapse
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
V0latyle said:
What happens when you turn your device on? Are you able to boot to bootloader? Does the screen turn on at all?
Click to expand...
Click to collapse
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that, its only a black screen.
Is there any way to flash the firmware or change the partition through other means that does not require bootloader/fastboot?
Xeust said:
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that its only a black screen.
Click to expand...
Click to collapse
Ah. It sounds like the bootloader can't start, so the device is probably in QUSB mode. Unfortunately your only recourse is to have it repaired, as the files and tools you'd need to fix this are not publicly available. While it's possible to find the software (QPST/QFIL) you won't be able to find the necessary binary images to reflash your device.
Xeust said:
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that its only a black screen.
Click to expand...
Click to collapse
There have been several people who have ended up like you after using Platform Tools 34+. None have been able to recover that I know of. The issue is known to Google (they are working on a fix). Can you confirm you were indeed using Platform Tools 34.0.0 or 34.0.1?
Lughnasadh said:
There have been several people who have ended up like you after using Platform Tools 34+. None have been able to recover that I know of. The issue is known to Google (they are working on a fix). Can you confirm you were indeed using Platform Tools 34.0.0 or 34.0.1?
Click to expand...
Click to collapse
Yes it was the 34.0.1
V0latyle said:
Ah. It sounds like the bootloader can't start, so the device is probably in QUSB mode. Unfortunately your only recourse is to have it repaired, as the files and tools you'd need to fix this are not publicly available. While it's possible to find the software (QPST/QFIL) you won't be able to find the necessary binary images to reflash your device.
Click to expand...
Click to collapse
If there's nothing I can do on my own, is it still possible to get it repaired? Or my only option is to send it back to google?
Xeust said:
Yes it was the 34.0.1
If there's nothing I can do on my own, is it still possible to get it repaired? Or my only option is to send it back to google?
Click to expand...
Click to collapse
If you're still under warranty, try to get repair that way. Warranty or no warranty, Google will probably refer you to a repair center like uBreakiFix.
V0latyle said:
If you're still under warranty, try to get repair that way. Warranty or no warranty, Google will probably refer you to a repair center like uBreakiFix.
Click to expand...
Click to collapse
Unfortunately not under warranty anymore. And its hard to reach google. or ubreakifix from my country :/
Thank you everyone. I conclude that my chances are pretty slim so I guess I'll consider getting a new phone.
Xeust said:
Unfortunately not under warranty anymore. And its hard to reach google. or ubreakifix from my country :/
Thank you everyone. I conclude that my chances are pretty slim so I guess I'll consider getting a new phone.
Click to expand...
Click to collapse
If you do end up contacting Google, you can refer them to this issue. Frankly it's there fault. They know their current Platform Tools are borked and yet still leave them up on the site for people to download and use.
Anyway, I wish you luck.
For those of you having the Platform Tools 34+ bug, as I did because I'm old and stupid at times, you may want to go thank this guy since using the 33.0.3 version of the PLatform Tools
did the trick for me.
V0latyle said:
Neither. It's just compression to reduce the amount of space the recovery kernel takes up in the boot image. If TWRP supported this compression we could potentially replace the stock recovery with TWRP. But, there isn't really much need to do this; most custom ROMs for the Pixel series just flash everything via web ADB.
That's not the case here. The boot slot cannot be changed without booting into TWRP. You could potentially install TWRP to boot_b, then set slot B as active; upon the next boot, the device will load TWRP. You could then do whatever you need to in TWRP, then set slot A as active, but you'd have no way of getting back to TWRP.
Click to expand...
Click to collapse
Wait, hold up. TWRP? On the Pixel 6? That exists?
(edit: nevermind, think I misread)
Deleted, since it's not for here.
Jaitsu said:
Wait, hold up. TWRP? On the Pixel 6? That exists?
(edit: nevermind, think I misread)
Click to expand...
Click to collapse
That What I want to know!