! Only For TEST !
Just for testing, I don't have bl unlock, so I wanted to share it here
Flash like other recoverys by fastboot flash recovey_ramdisk <twrp_file_name.img>
Reboot after to recovery by the know way or by fastboot reboot recovery.
I hope it works, report the result here.
Download :
drive.google.com/uc?id=1AISnTXjM_BW90zUJ7AZsQhRjKuNBm2v9, anne_twrp_1.0.img.
After flashing TWRP I turned off my mobile phone. I turned it back on to enter recovery mode, and the initial TWRP screen appears with version 3.3.1-0. Then it is turned off and restarted by entering bootloader mode automatically. You have not loaded TWRP recovery.
P20 Lite - ANE-LX1 9.1.0.132(C432) - Bootloader and FRP unlock - No root - No magisk install.
Thanks for trying, it is enough to understand the issue, I did made some changes, it may work now. Hope you can test this :
drive.google.com/uc?id=1MExm4E4ls7rbJQpjxQ8KGF4OojSI08HM&export=download
The result was the same. The TWRP start screen appears and then it has been restarted to enter the bootloader automatically. This time the TWRP startup screen has lasted longer, then has remained with black screen -also longer- and entered the bootloader.
I hope it will help you.
This is last try I can give, I tryed everything possible. I have some hops on this, this is the link:
drive.google.com/uc?id=1hQqxAnX7L0AVcLPOhwvlgzm6setKvoVb&export=download
If you were able to get logcat/kmsg, it would be a great job.
How do I do that?
Flashing an image by bootloader is one thing, but from adb shell commands I don't have much idea. It will delete programs (pm uninstall)...
Sorry, if my English is not very good. I'm using a translator. I am Spanish.
Did the last twrp same as other?
It is done by adb, if you run: adb logcat >> log.txt for a while and cancel the commend. And also for kmsg, it is by: adb shell cat /proc/kmsg >> /sdcard/k.log, and after adb pull /sdcard/k.log k.log.
NB: I won't deleted any thing
Mate all the recoveries you've posted have the same problem. They don't boot. In the title of your thread I can see the recoveries you've built are based on the A/B partitioning scheme, while the P20 Lite is A-only. I think that's the reason why you can't get it to boot. Looking forward to see this progress and hopefully be stable enough to use some day.
a/b partitioning works on p20 lite if it was updated to emui 9 pie, i have a working recovery for p20 that works with a/b and system as root, you can find it here /huawei-p-smart/development/recovery-twrp-3-2-1-0-t3953343
Yeah, there is a lot of working ones. I just wanted to know why mine didn't boot as other? We used the same trees for building. Idk.
Related
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
nea102 said:
This afternoon I installed LineageOS and all was well with the world. I then installed TWRP as I wanted to install Magisk and the EMUI camera. However, it then started bootlooping and nothing I've tried seems to be working.
I can get into Fastboot and it lets me flash stuff, but nothing boots. I tried the unbricking guide as well, but none of the three files work - I get a "No space left on device" error for each of the files.
If anyone can provide me with an idiot's guide to sorting this I'll be massively grateful.
Click to expand...
Click to collapse
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
I had used that guide, was following that when I was getting the out of space errors.
However, I got it all sorted in the end - I just downloaded a different (older) version of the firmware and that worked.
Help for you
samlis said:
Hi, look at this perhaps it can help you
https://forum.xda-developers.com/ma...e-10-flash-oreo-update-package-t3716814/page3
Click to expand...
Click to collapse
Hi good day.
I have been following your work from another page, and now in XDA.
I had not read your message, and, I changed the recovery for the stock, and, I was an idiot to close the bootloader.
What happened? Brick simple on my cell phone, did not come out (because I fixed it) of the image of erecovery (EMUI) without tabs or options, a rather rare image.
How do I solve it:
1. I did not enter fastboot, I did not correctly enter the stock recovery (I had deleted the twrp), I had closed the bootloader (my stupidity)
2. Be patient and wait for the battery to run out (wait a day for it).
3. Open cmd and place the command to open the bootloader (fastboot oem unlock) and execute.
4. Put the device in fastboot mode when connecting to the laptop (I did not work several times, the fastboot came out with error FUNC No 10 and NO 2), after numerous attempts and not to let it charge the battery too much (because it was restarted and towards brick in the EMUI logo), correctly enter the fastboot and unlock, when you enter step 3 automatically, it will be executed. I had an advance in removing the cell phone from the brick.
5. It reboots and wonderfully happened to the Rom (that had previously installed), that is to say, the erase was not executed when the bootloader had previously closed.
6. As I had little energy, it was turned off, but I connected it and entered charging mode without restarting (before I did it).
7. Wait for a load of at least 5%, and install the Catuva21 TWRP from the tutorial.
8. I put it by command to restart in fastboot, but I generate error (Error Func No 10 and No 2).
9. I turn off the cell phone and with volume up and power key
10. Enter the TWRP correctly, verify that it is installed.
11. Restart system and log in to the system. I had not deleted anything, but to avoid problems, I hope to load 55% and execute the steps to install the rom.
12. Enjoy and dry spilled tears.
Experience lived and I hope you do not do something that developers do not advise.
Grcias and happy day.
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
heindrix said:
Hi all,
Although my device isn't Mate 9 (mine is Nova 2s a.k.a HWI-AL00), but i'll share my experiece here.
Since EMUI8.0 Oreo, it's becoming more and more tough to get back to oreo stock after you mess/brick your device, maybe that's why HW plan to shutdown their bootloader unlock page.
Couple days ago, i got bored with my Nova 2s stock, and try to mess around to get root.
After flashing twrp (of course my bootloader is unlocked) and using modded rom which already contains magisk, i decided i want to go back to stock again, since the modded rom is not good to use.
This is where all the hassle began...
Maybe my most stupid move was, i formatted all partitions listed in twrp (so many partitions i can't remember).
After few days crying and try to find solutions, today i get to the point where it can download the rom package from HW ERecovery interface.
What i'm doing :
- download full package rom, extract the zip, and extract the *.app file using HuaweiUpdateExtractor, now you can see many *.img's there
- enter fastboot and flash twrp and boot into twrp
- flash these images : system.img into system partition, vendor.img into vendor partition
- exit twrp and get into fastboot again
- fastboot flash these images : kernel.img into kernel partition, ramdisk.img into ramdisk partition, recovery_ramdis.img into recovery_ramdisk partition
- shutdown device and let it boot normally
- it boot into HW eRecovery, and there's a menu to download rom full update package from server, i choose those menu (to download it, you must connect the device to wifi connection)
now i'm still waiting for the result, hopefully when the download finished, it can flash those packages nicely, i'll update the information to you guys later.
Click to expand...
Click to collapse
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
yoni sofer said:
Can you link here the twrp file that work for you? i have mate 10 pro (bla-l29) and i tried couple versions and none of them work well. thenks
Click to expand...
Click to collapse
take a look here, mate.
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Hey guys,
I already soft bricked my device (I think) -.- I rooted it with the patched boot image and accidently installed a magisk module which caused a boot loop.
I booted into TWRP and didn't read that for now we can't mount the important partitions, so there went that. I rebooted to stock recovery and erased my complete device (factory reset + userdata) and now it bootloops into the bootloader.
Can't boot stock recovery or ROM.
Is there any chance to recover it with the current tools we have or do I have to wait for a fully working TWRP?
Any tip is appreciated
Is this topic something you can work with?
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
MarkSnijders said:
Is this topic something you can work with?
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
Click to expand...
Click to collapse
Thanks for the hint, but no chance. After flashing the recovery and reboot, the 7t pro always reboots to bootloader :-\
Edit: Could switch the boot slot and was able to enter recovery. Tried the modified one with adb function, but sideloading a rom is not possible adb: sideload connection failed: closed
I think I have to wait for TWRP
dre-z said:
Thanks for the hint, but no chance. After flashing the recovery and reboot, the 7t pro always reboots to bootloader :-\
Edit: Could switch the boot slot and was able to enter recovery. Tried the modified one with adb function, but sideloading a rom is not possible adb: sideload connection failed: closed
I think I have to wait for TWRP
Click to expand...
Click to collapse
Try this:
- Reboot to bootloader (If not possible, hold "Volume Down" & "Powerbutton" to boot into recovery, from there select "Boot Fastboot")
- Open CMD and type "fastboot flash boot boot.img" (I attached the 7tPro AA Boot.img)
##EDIT##: Well, unfortunately I'm not allowed to post extern links, so you have 2. options. Somewhere here in the Opt7tPro threads, some guy posted a link where he uploaded the stock boot image. Should be found here https://forum.xda-developers.com/7t-pro/help/rooting-oneplus-7t-pro-t3983533/page2 (scroll down ). Option 2, you downlaod the 7T OTA from OP website and extract the payload.bin with the programm "payload_dumper-win64". This will extract a more or less working boot image..
Your phone should then be able to boot normally again.
If it does, you will probably find out, that your WiFi, Speakers & Camera won't work.
Don't worry, this is because you maybe need the BA boot.img.
Then there are to options.
1. You wait until OP releases the original files on their website, as they did with the 7t
2. You go to "Settings", "System" & "Factory Reset", to reset your phone. (By now, this is the only way to fix the problem, so you can use the patched boot again)
If you choose option 2, after the "installation" screen, where it asks to enter your language, you must boot your phone into fastboot again.
Then you can flash the patched boot image again and your phone should work as normal
I was on same situation, i planned to root, but not found really 7T PRO rom, 7T ot 7 PRO has totally different ROMs, so i made a big mistake, to flash different rom. Phone stuck in boot loop. After 1.5 day google searching, i found one, that can bring back phone to live. I found a fresh 7T PRO rom, and simply flashed back, it booted, and finally everything's works good. Must to download fresh factory rom: https://androidfilehost.com/?fid=4349826312261606254, unzip it to any folder, start your phone in fastboot mode, plug in usb cable, (other eng plug to PC) and then simply do double click at the unzipped folder to flash all.bat file. You will get some errors, it's totally normal. Within 4-5 minutes your phone will works again. Hope it will work at you.
You, my fellow xda guys, are amazing!!! The solution with the stock boot.img helped me out!
Now I can start using my 7t pro after 3 days ^^
Hi everybody
I've got a problem...
Downloaded latest OTA update from "xiaomi.eu", agreed to install, the phone then rebooted in to fastboot mode and does nothing else.
Rebooted the phone with adb command "fastboot continue" and this went well...it rebooted the system.
Now every time i restart the phone it reboots in to fastboot mode and i have to "fastboot continue" again.
I am also not able to enter recovery because the phone always enters fastboot mode.
Reinstalled recovery (Twrp-3.4.2B_toco_by.alex.msk1407.img) via ADB succesfully, but when i "fastboot reboot recovery" it reboots back into fastboot.
I'm also not able to boot into EDL mode.
Any solution?
Thanks
"MI NOTE LITE 8GB/128GB" running "MIUI by xiaomi.eu 12.1.1 | Stable 12.1.1.0(RFNMIXM)
Hi, I 'm in the same case, same model, same version.
I investigated and I can provide more details to help the community to look where to get a match to lightning our lanterns.
I downloaded the last OTA from built-in updater then the device was trapped in fastboot loop.
Unable to reboot/boot with adb/fastboot commands, but able to flash, I tried with différents recoveries,whose the last TWRP (testing version) let us discover the "super partition" (need fastbootd implantation to see it) This is the new OTA update partitioning.
We have to set up the proper flags via adb to perform successfully the update , or cancel the update process to retrieve original partitioning (non-updating state).
The commons way to restore recovery/fastboot might don't work, because system/vendor partitions are hidden inside "super partition" so might result of unknown/doesn't exist partition.
I am still seeking (Android dev super partitioning) and I'll be back when I'll discovered more...
EDIT : Doublon ? Another thread is open
https://forum.xda-developers.com/t/...astboot-after-updating-to-android-11.4223957/
EDIT: many users had a similar issue.
Will try with any another GSI rom, downloading...
opposatto said:
Hi, I 'm in the same case, same model, same version, I investigated and I can provide more details to help the community which lantern to pickup.
I downloaded the last OTA from built-in updater then the device was trapped in fastboot loop.
Unable to reboot/boot with adb/fastboot commands, but able to flash, I tried with différents recoveries,whose the last TWRP (testing version) let us discover the "super partition" (need fastbootd implantation to see it) This is the new OTA update partitioning.
We have to set up the proper flags via adb to perform successfully the update , or cancel the update process to retrieve original partitioning (non-updating state).
The commons way to restore recovery/fastboot might don't work, because system/vendor partitions are hidden inside "super partition" so might result of unknown/doesn't exist partition.
I am still seeking (Android dev super partitioning) and I'll be back when I'll discovered more...
EDIT : Doublon ? Another thread is open
https://forum.xda-developers.com/t/...astboot-after-updating-to-android-11.4223957/
Click to expand...
Click to collapse
Thank you. I'll be for updates
salsaecoentros said:
Thank you. I'll be for updates
Click to expand...
Click to collapse
Looking around https://source.android.com/devices/tech/ota/dynamic_partitions/implement
opposatto said:
Looking around https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Click to expand...
Click to collapse
EDIT : so here is the idea, not tried yet:
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Alex msk's twrp is not compatible with android 11. Use orangefox or pitchblack recovery.
Btw i would recommend not upgrading to android 11 at the moment. It has a lot of bugs.
ApexPrime said:
Alex msk's twrp is not compatible with android 11. Use orangefox or pitchblack recovery.
Click to expand...
Click to collapse
So that's the problem....didn't think about that.
Thanks...i Will try one of them and them get back to you.
Thanks
salsaecoentros said:
So that's the problem....didn't think about that.
Thanks...i Will try one of them and them get back to you.
Thanks
Click to expand...
Click to collapse
Hi...
Sorry for the late Replay.
So i did like you said and installed new twrp and...what do you know...ir worked like a charme. No more issues.
Thank you do much.