Have anyone successfully booted Android 12 beta 2GSI?
I followed the guide from https://www.xda-developers.com/how-to-install-android-12/ multiple times, but every time Phones boots to fastboot.
Any Clue?
Having exactly the same drama with mine, either boots to existing system or bootloader. I flashed it back to stock on both slots and tried on each slot and booted to bootloader both attempts. next attempt was a factory reset and tried the dsu loader in developer options and still no dice, boots to existing A11 system every time.
I did have a brief trawl through the treble forum but didn't see much relating to a12 beta there, might have a better look another day as may be an answer in there somewhere.
Related
I know this situation has come up in the past, but most of the essential links are broken in all threads I could find.
background: this my wife's Verizon xt926. It has never been rooted and the bootloader is locked. She applied all system updates to it, so I can only assume it is using the most recent version (which is important as the locked bootloader prevents downgrading). Several days ago it crashed, and despite multiple attempts at factory default wipes from the default recovery software, it continues to be non-functional. It boots to the Motorola M logo, but no further. Recovery options are available, but do not fix the issue.
What I have tried so far:
factory reset via recovery
fastboot restore using out of date stock rom
adb sideload using out of date stock rom (didn't even begin to work)
From what I've read, fastboot should be able to fix the issue, but I need an up to date stock rom and a working copy of RDS lite on my machine. Is that correct? Does anyone have a stock rom they can share? I've already scoured the internet and have found many helpful articles explaining the process, but none with actively working links. Most of them link to sbf.droid-developers.org, but that site gives 403-forbidden on all pages.
Thanks,
jwilson8767
jwilson8767 said:
I know this situation has come up in the past, but most of the essential links are broken in all threads I could find.
background: this my wife's Verizon xt926. It has never been rooted and the bootloader is locked. She applied all system updates to it, so I can only assume it is using the most recent version (which is important as the locked bootloader prevents downgrading). Several days ago it crashed, and despite multiple attempts at factory default wipes from the default recovery software, it continues to be non-functional. It boots to the Motorola M logo, but no further. Recovery options are available, but do not fix the issue.
What I have tried so far:
factory reset via recovery
fastboot restore using out of date stock rom
adb sideload using out of date stock rom (didn't even begin to work)
From what I've read, fastboot should be able to fix the issue, but I need an up to date stock rom and a working copy of RDS lite on my machine. Is that correct? Does anyone have a stock rom they can share? I've already scoured the internet and have found many helpful articles explaining the process, but none with actively working links. Most of them link to sbf.droid-developers.org, but that site gives 403-forbidden on all pages.
Thanks,
jwilson8767
Click to expand...
Click to collapse
I can't believe no one responded to this... Here you go man this should be everything you need http://www.droidrzr.com/index.php/topic/54379-fxz-442-1834615/
I recently ran into the issue during custom rom work. I reflash the stock android ZIP, it starts booting, then I hard reset it with the power button and try to reach bootloader again. This, as it turns out, is terrible to do if you want a fast setup. The moment it starts and you reboot it, the boot image is corrupted (that's my guess) because escaping the boot screen during a clean flash bricks your phone. If you're reading this, it happened to you as well.
The answer is so flipping obvious and it took me an hour to figure it out - nowhere on the internet is there a "solution" for this problem, no matter how frequent it is. But there are lots of people who deal with this, whether still on their factory images (like the Pixel 3 EDL issue) or like me bouncing from custom to stock. So here's the answer:
ALL YOU HAVE TO DO IS SIDELOAD THE CURRENT SOFTWARE OTA OR A BETA OTA FROM ANOTHER FUTURE VERSION.
It doesn't recognize timestamps before your current software, so you'll need to assume you're on the latest of whatever you're on and do that. Future versions work as well, so if you wanted to reach 12 in one shot, your phone's bootloader would fully accept it as long as the file isn't corrupted. If you need a sideloading or flashing guide, here you go.
For me, I flashed the latest build of Android 11 (August patch) and rebooted during the boot up. What I did was download the OTA of the same exact file to my laptop, and entered adb sideload coral.xxx.x.zip. (The name of the file) It ran all the way through and it started up perfectly normal.
I hope this helps someone!
P.S. I don't have any pictures or tutorials, I only wrote this to help others understand what happened and how to fix it. Probably wouldn't have needed to say it if the forum for it existed.
Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.
First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.
Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.
3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!
Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?
Hi all
I have a bit of a problem after flashing the Google GSI (android 13) on my Lenovo Tab P11. Everything seemed to work well. Rebooted into the OS without any issues, everything seemed to work (Wifi included). I then swapped and deployed LineageOS 20 GSI which again, seemed to go okay but I had a google play protect issue.
During a quick check, I was planning on just rolling back to the Google GSI one, but accidently locked my device with
./fastboot.exe flashing lock
instead of unlock. And, taking no notice of the on screen prompts proceeded to relock the device which effectively bricked it. Nothing would load, not even recovery or fastboot.
A fair while later I managed to get recovery/fastboot working again by redoploying the boot.img, recovery.img and vbmeta.img from the stock ROM. I then discovered my current-slot had changed from b to a, so swapped that back too. This allowed the device to at least go into fastbootd so I ccould reflash it. I put the LineageOS back on, but now Wifi isn't working. Rolled back to Google GSI and the same.
I've tried following guides to re-install stock, but that's failing as well. I have read a couple of posts detailing issues with Wifi on GSI but the fixes didn't do anything or weren't necessarily inline with what I had. I suspect I have missed something I need to push back out to the device, but at this point I'm a bit stuck.
Anyone came across this before, or can point me where I can get some more information on it?
ta
whether some partitions are deleted or corrupted. You have the original backup qcn . try restoring it or trying to fix the partitions
I don't understand. I've refreshed this thing 3 times now with no luck. Every single time I sideload a ROM, I always land back on the Fastboot screen. It simply won't let me boot into any ROM. It was just working yesterday, but not today. Any help please?
LuckyTheCoder said:
I don't understand. I've refreshed this thing 3 times now with no luck. Every single time I sideload a ROM, I always land back on the Fastboot screen. It simply won't let me boot into any ROM. It was just working yesterday, but not today. Any help please?
Click to expand...
Click to collapse
firmware issue, same as mine. Crdroid and Los20 requires android 12 fw. Derp and Yaap requires Android 11 fw