I tried to install some GSIs, but they were stuck at the costum Romes Loading animation.
I installed the Firmware with Emma
Locked it to update to Android 11 and unlocked it again
Installed TWRP and booted into it
Wiped system and userdata
Pushed to system.img file from the custom rom to my device into /sideload/
In TWRP install-System Image—> Pressed on the folder and on the system.img
It installed successfully
Rebooted
Stuck in Loading animation(PixelExpirience == A Google G with loading bar, LineageOs == The blue line with the bubble)
No crashes or so what, it just hangs in there for ~20 min and than I turn the device off with volume(+) and Power button.
I know Sony Xperia 1 is not officially supported for project treble, but since this thread(https://forum.xda-developers.com/t/...el-expierence-android-12-gsi-patches.4097433/) requires Pixel Experience GSI I thought it should be possible to run GSI on Sony Xperia 1.
Any idea what I might have donne wrong or are there other GSI roms I could try.
PixelEX = PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img 3.7 GB
LineageOS = lineage-19.1-20220613-UNOFFICIAL-arm64_bvS.img 2.0 GB
Bkeinn_ll said:
I tried to install some GSIs, but they were stuck at the costum Romes Loading animation.
I installed the Firmware with Emma
Locked it to update to Android 11 and unlocked it again
Installed TWRP and booted into it
Wiped system and userdata
Pushed to system.img file from the custom rom to my device into /sideload/
In TWRP install-System Image—> Pressed on the folder and on the system.img
It installed successfully
Rebooted
Stuck in Loading animation(PixelExpirience == A Google G with loading bar, LineageOs == The blue line with the bubble)
No crashes or so what, it just hangs in there for ~20 min and than I turn the device off with volume(+) and Power button.
I know Sony Xperia 1 is not officially supported for project treble, but since this thread(https://forum.xda-developers.com/t/...el-expierence-android-12-gsi-patches.4097433/) requires Pixel Experience GSI I thought it should be possible to run GSI on Sony Xperia 1.
Any idea what I might have donne wrong or are there other GSI roms I could try.
PixelEX = PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img 3.7 GB
LineageOS = lineage-19.1-20220613-UNOFFICIAL-arm64_bvS.img 2.0 GB
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/android-12-up-and-running-on-xperia-1.4331341/
I think you should take a look of this post.
In theory this would be the post I needed, but following this guide, with their files, made my Xperia 1 not even show the Rom’s Boot animation and instead ended up in a boot loop which stopped ~2 sec after showing the Sony logo.
But nevertheless thanks. I will ask in this post for help.
Try using fastboot method to install GSI ROM.
See this thread for reference : https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4128911/
Thanks, I did it.
What did I do different:
vbmeta.img from google(was a little bit bigger than the one from the TWRP)
Started from Android 9(directly from Emma)
Flashed system.img as well as vbmeta to system_a system_b/vbmeta_a, vbmeta_b
i have the same problem till now i cant flash any gsi i flashed android 11 and flashed after that vbmeta to a and b and flashed system.img and got infinite loading
Related
Hi guys,
First up here are the details of the phone that I am currently using:
Zeaplus M7
MediaTek MT6752
Android 5.0
Root = YES
Unlocked = YES
Secure = NO
The Problem
I have compiled CWM using the CM-11.0 branch, and TWRP using the OmniRom and TWRP Minimal sources, but I always end up with the same problem, regardless of whether I flash CWM or TWRP.
After flashing either of the recovery.img files to the phone, I can attempt to boot into recovery and what happens is the phone restarts, sits at the splash logo (boot screen) and sits there for around 15-30seconds (using the stock recovery, it will already have booted by this point), and then it will just restart the phone and it will continue to boot to the system as normal.
This happens on both CWM and TWRP. What is causing both the recoveries to hang at the boot screen without actually entering the recovery? Is there a way I can get a logcat or log of what is happening during the recovery bootup so I can check if there are any error messages going on behind the scenes that I am missing out on?
If you need anymore information please let me know!
Thanks
Just committed the most recent files for a CWM (11.0) build. (Also contains some older files used for the TWRP build)
https://github.com/alien-13/android_device_zeaplus_m7
Hopefully that may help out a little bit more. Not 100% sure what could be causing the issue as the P6000 has a working TWRP, and I have based this device tree around the P6000 device tree (with specific changes made to suit the M7).
Not sure if this will help, I also have the z+m7 , have tried the ele p 7000 Rom on it and it works fine, twrp installs fine, but will not download from playstore , both are from needrom made by s7yler, when I go back to m7 Rom with the p7000 twrp package exactly the same happens as happens to your phone, have noticed in m7 Rom and Mijue t500 Rom which are the same, there is a file called Encrypt, which I have never seen in other roms.could this be a problem
There is now a twrp for the zeaplus m7 on the zeaplus forum
Hello guys, I want to start to modify the kernel of my sony xperia z2.
First I decided to compile aosp android 6.0 for my z2.
I have done all things of the sony tutorial and the compilation was successful only the boot.img doesnt exists.
So I decided to flash system.img and userdata.img.
It was successful too.
After this I started my phone and it wont boot. Only the sony logo comes and Im able to boot to recovery.
after this i flashed carbon rom and now I only have 540 mb space on my device.
I compiled aosp in a ubuntu container (docker).
I have now some questions:
When I flash a ROM with fastboot and i only flash boot, system and userdata I cant hardbrick my z2 right?
boot.img is my recovery right?
system.img is my android rom including linux kernel right?
userdata should be the free space for data and apps ...
Where is the emei saved on the z2?
When I compile the kernel which option should I choose when I enter this command?
source build/envsetup.sh && launch
Some information:
I have currently TWRP as a recovery.
system.img 1,5 GB
userdata.img 550 MB
device is working
I hope my english isnt that bad...
Hi guys,
Just unlocked my bootloader and began the root process.
I followed part of this guide but without backing up my DRM keys. http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
I flashed my kernel and the recovery O.K.
fastboot flash recovery recovery.img
flashboot flash boot boot.img
I've tried two versions of TWRP and two different versions of the kernel AndroPlus.
When performing fastboot reboot after flashing both files my phones LED blinks RED once and then does nothing.
Dramatic and scary. What can I do to fix this? When trying to boot without the cable in my phone just vibrates once and does nothing. Screen doesn't light up at all. I'm so worried.
MatMew said:
Hi guys,
Just unlocked my bootloader and began the root process.
I followed part of this guide but without backing up my DRM keys. http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
I flashed my kernel and the recovery O.K.
fastboot flash recovery recovery.img
flashboot flash boot boot.img
I've tried two versions of TWRP and two different versions of the kernel AndroPlus.
When performing fastboot reboot after flashing both files my phones LED blinks RED once and then does nothing.
Dramatic and scary. What can I do to fix this? When trying to boot without the cable in my phone just vibrates once and does nothing. Screen doesn't light up at all. I'm so worried.
Click to expand...
Click to collapse
did you try to flash first the boot.img and after the recovery ?
acabreram said:
did you try to flash first the boot.img and after the recovery ?
Click to expand...
Click to collapse
I've tried another kernel and it's booting but hanging at the three dots. (bootscreen) been waiting a few minutes. hopefully it gets to system.
MatMew said:
I've tried another kernel and it's booting but hanging at the three dots. (bootscreen) been waiting a few minutes. hopefully it gets to system.
Click to expand...
Click to collapse
Ok yo can try this too
Y tried and working fine root & xposed
It's tus stock kernel but with the habilita to support root
Similar issue for me
I've had almost exactly the same issue today:
- I unlocked boatloader using Sony standard process
- I followed the steps under 'How to Install CM13' within CTXz's guide here
- After flashing the Kernel and THEN the TWRP, I reboot and the phone flashes red LED, then green, then off, then red and then stays on green for a while (screen is blank). My computer registers that there is a new connection by making a sound but doesn't show up any devices that I can see.
- Periodically, I get the device disconnection sound and the green LED goes off, then red comes on, then solid green again until next cycle.
- If I disconnect the cable, the LED goes off. When I try to turn the phone on without cable attached, it buzzes but does nothing - no LEDs. I can't tell whether it is on or not, except that doing hard reset with PWR+Vol.Up gives no reaction.
- When I re-attach cable normally, the red/green LED sequence starts immediately with no need to turn PWR on, which would suggest that the phone is perhaps on.
- I am able to get into bootloader as normal and fastboot registers the device just fine.
- There is no yellow LED
I started with Kernel AndroPlus v24 and TWRP 3.0.0.0.
Failing that, I tried Kernel v20. Then I tried AndroPlus' twrp-2.8.7.0-E5823-32.0.A.6.152.
Have also tried Kernels v20 and v21 with TWRP 3.0.0.0.
I haven't had any fast boot errors - all flashes come back 'OKAY'.
I'd be very grateful for any help? Have I missed something?!
update to my post above:
I used: 'fastboot boot recovery.img' and this fired up the Sony logo with white screen and blue LED. However, after 10 mins of waiting, there was no change in status and I still couldn't get into TWRP with pressing Vol buttons, even after several restarts and unplugging, replugging etc.
Then, I realised the stock ROM on my phone before this whole process was Lollipop 5.1.1 Build 32.0.A.6.200. So, I flashed older versions of the Kernel and TWRP. Now, I can boot into the ROM and use the phone (almost) as normal except, being plugged in, it keeps re-detecting the USB cable. I now also get the Sony boot screen followed by yellow LED.
If I don't touch anything, it boots into the ROM. However, if I press a Vol button while the yellow LED is on during boot, then it just resets.
Thus, I still cannot get into the TWRP interface. Perhaps I need a TWRP version that is specific to my build - the one I have is from AndroPlus website and refers to the previous build (twrp-2.8.7.0-E5823-32.0.A.6.152.img)?
okay, further update (to save someone replying!)
I managed to boot into the system using AndroPlus Kernel v05a (I had Lollipop build ###.200), but still couldn't get into any TWRP.
I then followed the general process explained in this thread, albeit had to do a heck of a lot of research to understand the detail that is omitted from that (otherwise very useful and concise) original post. For example:
- how to actually use Flashtool (installing drivers and then getting hold of the right firmware from within the program);
- the difference between Fastboot and Flashmode;
- having to plug in the phone while it is loaded into the system before then flashing the selected firmware with Flashtool and ONLY THEN unplugging, switching off and booting into Flashmode.
- loading up the system after flashing the Kernel and TWRP so that I connect to computer and re-copy the erased SuperSU .zip file back onto storage, and then re-booting into TWRP and how to flash a zip file with TWRP.
Having now got a stock Marshmallow firmware rooted, my next step is to go back to the original guide I was following and try to install Cyanogen!
Thank you to all the people who have posted help guides throughout this site so that I could piece together what I needed to do - even though it has still taken me about 30 hours of my life to learn all this!
Hopefully my experience might help someone else in due course...
robledog said:
okay, further update (to save someone replying!)
I managed to boot into the system using AndroPlus Kernel v05a (I had Lollipop build ###.200), but still couldn't get into any TWRP.
I then followed the general process explained in this thread, albeit had to do a heck of a lot of research to understand the detail that is omitted from that (otherwise very useful and concise) original post. For example:
- how to actually use Flashtool (installing drivers and then getting hold of the right firmware from within the program);
- the difference between Fastboot and Flashmode;
- having to plug in the phone while it is loaded into the system before then flashing the selected firmware with Flashtool and ONLY THEN unplugging, switching off and booting into Flashmode.
- loading up the system after flashing the Kernel and TWRP so that I connect to computer and re-copy the erased SuperSU .zip file back onto storage, and then re-booting into TWRP and how to flash a zip file with TWRP.
Having now got a stock Marshmallow firmware rooted, my next step is to go back to the original guide I was following and try to install Cyanogen!
Thank you to all the people who have posted help guides throughout this site so that I could piece together what I needed to do - even though it has still taken me about 30 hours of my life to learn all this!
Hopefully my experience might help someone else in due course...
Click to expand...
Click to collapse
I had the same problem and solution is as is written here.
I had to flash Stock Firmware Marshmallow via Flashtool. After this I flashed kernel(boot) and recovery without problems and yellow icon will displayed.
Don't want to warm up this kind of old thread, but I have exactly the same issue (E8523). Would any of you mind to post their (stock) ROM versions which finally worked? I tried almost every combination that came to my mind (Customized CE1 32.2.A.0.224 => v31, several LP versions => more or less 20 to 32...).
Currently after installing the MM I mentioned the stock kernel worked, but when I flash the AndroPlus kernel (fastboot flash boot /path/to/boot.img) it won't boot up, black screen, looks like no dtb found (doesn't even try to load). This is also the message I get when I try to boot this img via fastboot directly.
I am sure I am missing something really stupid (quite new to android devices), but what?
IGNNE said:
Don't want to warm up this kind of old thread, but I have exactly the same issue (E8523). Would any of you mind to post their (stock) ROM versions which finally worked? I tried almost every combination that came to my mind (Customized CE1 32.2.A.0.224 => v31, several LP versions => more or less 20 to 32...).
Currently after installing the MM I mentioned the stock kernel worked, but when I flash the AndroPlus kernel (fastboot flash boot /path/to/boot.img) it won't boot up, black screen, looks like no dtb found (doesn't even try to load). This is also the message I get when I try to boot this img via fastboot directly.
I am sure I am missing something really stupid (quite new to android devices), but what?
Click to expand...
Click to collapse
Pro tip: hold shift and right click inside folder with recover.IMG or voot.IMG to open command prompt from that folder. Then all you have to do is type fastboot flash boot boot.IMG. I suggest trying to put a custom recovery like twrp on and flashing the xpower ROM from that, it will give you everything in one package.
Edit: fwiw I'm pretty sure custom recoveries have been able to flash .IMG fils for a few years now but I've never actually tried it. Might be worth a shot.
Thanks, but I haven't found cmd.exe on my linux machine yet^^ (I suppose wineconsole is cheating )
I know how to flash *stuff* to my phone, but that *stuff* seems only to work if some specific version of stock rom was installed previously. My best guess is the bootloader changes and supports different dtb formats on every version.
Stock Marshmallow 6.0.1 Customized CE1 32.2.A.0.224 does _not_ work for installing any version of AndroPlus kernel (tried a few...). It fails at boot (does not even load system, probably dtb).
Just in case someone might run into similar issues: What finally worked was Stock MM 6.0.1 Customized DE 32.2.A.0.224 with AndroPlus v31. It seems to be some older release (?), it says R2C instead of R9C for Customized CE1.
I could not find this information anywhere on the net (maybe its me), so for those with a slow internet connection the above version should work. You don't have to actually boot it, flashing is enough.
Thanks for sharing the information in this tread, it really helped me to unbrick my phone!
I started with Lollipop on my brand new Z3C and tried to root using AndroPlusKernel v31 / TWRP 3.0. This resulted in a softbick state, only being able to boot in fastboot mode.
After many hours struggling, an upgrade to stock Marshmallow (E5823_32.2.A.0.224) did the trick. This somehow seems ta make the device ready for the new kernel and recovery (I guess it has to do with the partitions in the filesystem).
Anyway, from stock Marshmallow I could start all over and succeeded to flash a custom bootloader, recovery and now have the ability to flash any desired rom! Thanks again.
To updrade to stock MM I used the instructions in this thread:
[GUIDE][18th Dec][4Noobs] Flashing A FTF File Using Flashtool
To set up TWRP recovery I used the instructions in this thread:
[ROM][UNOFFICIAL][6.0.1][E5823/E5803] CyanogenMod 13 for the Sony Xperia Z5C [ALPHA]
The stock rom I used for my E5823 is "E5823_32.2.A.0.224_R1C_CIS Generic_1298-5167.ftf" from xperiablog.net
Since I'm a new registered member I can't post external links
Google it and you're set!
IGNNE said:
Just in case someone might run into similar issues: What finally worked was Stock MM 6.0.1 Customized DE 32.2.A.0.224 with AndroPlus v31. It seems to be some older release (?), it says R2C instead of R9C for Customized CE1.
I could not find this information anywhere on the net (maybe its me), so for those with a slow internet connection the above version should work. You don't have to actually boot it, flashing is enough.
Click to expand...
Click to collapse
I'm having the same problem, where did you get that MM stock version from?
And what do you mean by "you don't have to actually boot it"?
Search for XperiaFirm and Flashtool. There is plenty.
You don't have to start your freshly installed Stock Rom version "...". You just have to flash it (write it to your phone) Now you boot your phone in fastboot mode and flash your custom kernel and mod rom of your choice. Seems to be some incompatible whatever between not matching kernel versions and the "stuff" flashing installs (suspect sth like bootloader, but no idea).
I have flased boot.img nd recovery.img on android 7.1.1 z5 compact my phone won't pass the sony logo
any help ?
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
starchild78 said:
I have flased boot.img nd recovery.img on android 7.1.1 z5 compact my phone won't pass the sony logo
any help ?
Click to expand...
Click to collapse
I've just discovered I can boot into twrp
anything I can do to fix this from there ?
I was in MIUI Eu rom, I think the 7.11.23 update change the boot logo/image. Now I'm in RR 5.8.5 I flashed many zip intended for changing boot image but still the Boot image doesn't change.
I have same issue here, after install 7.12.8 firmware. And i'm install pixel splash.img and bootanimation. Bootanimation changed successfully, but boot logo does't change.. Btw, there is " unlocked " text, below the boot logo
dev.azra said:
I have same issue here, after install 7.12.8 firmware. And i'm install pixel splash.img and bootanimation. Bootanimation changed successfully, but boot logo does't change.. Btw, there is " unlocked " text, below the boot logo
Click to expand...
Click to collapse
i posted it also to miui eu community, hope someone will help us
it's a new feature from xiaomi actually. if you want to have custom splash image, flash older firmware
Custom boot logo upgrade problem.
My boot logo used to change after I flashed another boot logo but I recently can't change it after flashing to another ROM called 'Alpha Centauri'. I flashed the logo 10 times but all in hell. Can anyone help me out.
Thanks in advance
primarina said:
I was in MIUI Eu rom, I think the 7.11.23 update change the boot logo/image. Now I'm in RR 5.8.5 I flashed many zip intended for changing boot image but still the Boot image doesn't change.
Click to expand...
Click to collapse
Alright, make a clean wipe of your phone,everything. Now flash this firmware: https://sourceforge.net/projects/xi..._V9.6.2.0.NCFMIFD_88bb9b1f76_7.0.zip/download (all credits go to this site which is updated with the latest firmware :https://forum.xda-developers.com/re...lopment/firmware-xiaomi-redmi-note-4-t3760917)
Then flash the file below and tell me if it has changed which it should. If it worked keep the same firmware and go to this site(which i got the logo from,credits to them actually) https://forum.xda-developers.com/re...ow-to-change-boot-logo-splash-t3572441/page17
Search for something like this: name_new_firmware and download it or request one icon of your choice for your new firmware
Flash this via fastboot. Working for me on fw 9.6.2.0
Loaded twrp with odin, then loaded aicp custom rom.
A year later loaded pixel pie custom rom
On power off the fone wouldn't restart in pixel, or twrp
I tried taking the Battery out and waiting 5 mis, 1hr, 3 hrs the fone still wont start.
BUT if the fone is left with the battery out for 3days it starts in both pixel and twrp no problem !!!
I also tried cleaning all partitions on twrp except sd card and loading my image of aicp which used to work, .. no change.
Anyone have an idea what this might be?
The phone is a samsung note 4 snapdragon originally on marshmallow android.
Im thinking of asking samsung to put marshmallow on again then reloading twrp and aicp
What happens when, instead of ACPI power off, you go to TWRP, reload TWRP, and then turn off the phone with TWRP?
If enabling works fine, the ACPI kernel may be to blame.
Be specific about which version of TWRP and ACPI you are using.
ze7zez said:
What happens when, instead of ACPI power off, you go to TWRP, reload TWRP, and then turn off the phone with TWRP?
If enabling works fine, the ACPI kernel may be to blame.
Be specific about which version of TWRP and ACPI you are using.
Click to expand...
Click to collapse
Sorry for delay, each restart takes 3 days!
Thankyou very much for your reply, appreciated,
Yes if close with twrp it opens without problem. If then close with power button have to wait 3 days before it restarts.
Note 4 snapdragon trite official Samsung phone bought uk originally marshmallow
Aicp _trite_q_15_unofficial 202 00 409 april 2020
previously used pexelrom, i dont know vesrion,it was pie though for note4 trite
Twrp 3 6 1 9.0 trite tar From https://eu.dl.twrp.me/trlte/
(the files were .img.tar I assumed this is ok for odin, battery removed and boot first into recovery)
Pleeas can you give me overview of kernal problem,
.........................
The aicp rom worked except battery ran down on pwer off (known fault) Image taken.
Tried pixel rom with incuded gapps pie version and couldnt get twrp (to make image)
Used odin to rload twrp 3 6 1 9.0 trite tar .img.tar file
reloaded my image of aicp
......................
limit of my knowledge here!
Could piexel rom have locked something for future custom roms using twrp
Could the later version of twrp be worse
I assume version of odin twrp are for the original phone (samy note4 snapdragon) not the last custom rom
.... Is twrp in a separate partition that isnt wiped by loading custom rom with twrp? Isit this that is the problem, or someting in the custom rom,. Ive got this far without rooting the phone,has pixel altered this.
......................
If you are installing a new/different custom rom, it's best to do a full wipe with internal memory included.
For many phone models, twrp 3.6.x performs worse than 3.5.2.x.
Since the twrp kernel is good for shutting down the phone, change the ROM to one that also shuts down the phone well.
Read the first post of the thread very carefully and understandingly:
[ROM][UNOFFICIAL][11] LineageOS 18.1 [tblte][trlte][trlteduos]
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS...
forum.xda-developers.com
and install LineageOS 18.1 by @ripee.
gwm121 said:
Sorry for delay, each restart takes 3 days!
Thankyou very much for your reply, appreciated,
Yes if close with twrp it opens without problem. If then close with power button have to wait 3 days before it restarts.
Note 4 snapdragon trite official Samsung phone bought uk originally marshmallow
Aicp _trite_q_15_unofficial 202 00 409 april 2020
previously used pexelrom, i dont know vesrion,it was pie though for note4 trite
Twrp 3 6 1 9.0 trite tar From https://eu.dl.twrp.me/trlte/
(the files were .img.tar I assumed this is ok for odin, battery removed and boot first into recovery)
Pleeas can you give me overview of kernal problem,
.........................
The aicp rom worked except battery ran down on pwer off (known fault) Image taken.
Tried pixel rom with incuded gapps pie version and couldnt get twrp (to make image)
Used odin to rload twrp 3 6 1 9.0 trite tar .img.tar file
reloaded my image of aicp
......................
limit of my knowledge here!
Could piexel rom have locked something for future custom roms using twrp
Could the later version of twrp be worse
I assume version of odin twrp are for the original phone (samy note4 snapdragon) not the last custom rom
.... Is twrp in a separate partition that isnt wiped by loading custom rom with twrp? Isit this that is the problem, or someting in the custom rom,. Ive got this far without rooting the phone,has pixel altered this.
......................
Click to expand...
Click to collapse
Thankyou ze for succinct helpful info.
I am reading very carefully as you suggest
In this section im unsure about ..........."type fastboot reboot" ...
Recovery is to get to twrp right? vol up pwr home with note 4, that would bring up menus on twrp, .there is a menu box for reboot.. Have I undersood this please?
I can follow ypour suggestion tomload an earlier version of twrp
is it possible a later twrp has anything to do with the loading kernal of the rom
"""Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."""