Hello, I installed last Legacy Xperia CM11 kernel:
Code:
# .fastboot flash boot boot.img
Then I reboot:
Code:
# .fastboot reboot
Now I have a loop in the mobile with the Legacy Xperia animation.
I try to install older kernel, but same problem. How could I fix this?
Thanks and best regards.
Did you install the ROM? That kernel works only with CM11.0 LegacyXperia ROM.
Hello,
I fix it installing older kernel, then install again the last kernel.
Regards.
After install the kernel you need enter in the recovery and install the rom (KitKat for this kernel). If you don't change the rom, the phone doesn't work. :good:
http://forum.xda-developers.com/showpost.php?p=47895754&postcount=1
Steps required for correct installation (order is important):
1: Flash boot.img in fastboot & reboot into recovery
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
2: Enter recovery, go to mounts and storage
3: Format /system, then /data and then /cache (Important step!)
4: Flash update zip
5: Flash gapps (recommended package is the one provided in the link below)
The non booting issue is right there in the original 4.4 thread instructions
If it still doesn't boot then rather than multi flashing Kernels, you should flash the stock ICS 4.1.B.0.587 full ftf firmware and start again from the very beginning
Nathan
Hello everyone,
I need help to start on flashing g7 play etc. In the old days I flashed phones like galaxy s3, s4, s5 and Note 4, but I'm not an expert in all of this.
Then I changed to iPhone 6s and now I want to come back to Android.
My goal:
de-googled moto g7 play
Android 9/10 -> would prefer 10
if possible -> root
My Device:
moto g7 play - XT1952-1
(bootloader unlocked)
---
Build number:
PPYs29.105-134-7
---
If have read most of the Threads for the g7 play, but at the moment I'm a little scared to brick it.
I have some questions:
1. I copied together for myself a Instruction (at the end of post). Could you tell me if this is OK like this, or do I have to do additional things before start?
2. In my copied instruction, at the point of flashing the GSI (Instruction ROM: -> Step 1)
What does "Dirty flashing your g7 play" mean? Do I have something additional to do, before following the instruction, or is dirty flashing the following instruction of the post?
3. Modded phh -> I have no information about this, could you explain, or give me link?
4. Overlay -> I have no information about this, could you explain, or give me link?
Thanks for your help
---
INSTRUCTION: (it is a quick&dirty instruction)
ROM:
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img.xz
DTBO:
dtbo.img
(https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing)
---
---
Instruction ROM:
step 1
Dirty flashing your g7 play -> what does that mean, what to do???
step 2
extract the gsi
step 3
put phone in fastboot mode and enter the commands
$ fastboot -w
$ fastboot flash dtbo dtbo.img
$ fastboot flash system [this is where you put your android 10 img]
$ fastboot boot twrp.img
(https://forum.xda-developers.com/g7-play/development/gsi-images-g7-play-t3980807
#1)
------------------------
TWRP:
twrp.img
---
Instruction TWRP:
step 1
Fastboot boot twrp.img
step 2
Copy twrp to your external sdcard, or use adb push twrp.img /tmp/twrp.img
step 3
Go to Advanced > install recovery ramdisk then navigate to tmp or your external sdcard and select the twrp.img you copied
step 4
Use wipe > format > type "yes" to continue then use reboot > recovery from twrp's menus
step 5
Once twrp starts up again, wipe data & system, make sure system is mounted, then flash a GSI. Flash the universal disabler afterwards.
If you get a failed to unmount error, manually mount all partitions and reflash whatever it errored on
step 6
Optional: Flash my modded phh for root. (Install the apk after.) Never use Magisk! It will fail to root, cause a bootloop, or break twrp
FIX navbar on a GSI:
$ adb root
$ adb shell
$ setprop persist.sys.phh.mainkeys 0
$ reboot
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#403)
------------------------
Modded phh: -> LOS16 & 17
modded-phh-superuser.zip
phh-su.apk
(https://forum.xda-developers.com/showpost.php?p=81503713&postcount=240)
------------------------
Overlay: -> what does that mean???
treble-overlay-moto-g7play.apk.zip
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#404)
------------------------
@ggg777
First make sure you install the stock OS to both slots, including the bootloader. I forgot to flash bootloader_b, and got stuck in EDL last week. You don't want that to happen and it's not easy to get out of. If you do this first, you will not have to worry about getting bricked.
Use my instructions found here for twrp. Inside the instructions you'll also find a link to my modded phh. Flashing a GSI can be done with twrp or fastboot. You also don't need the dtbo.img anymore since it's embedded inside of twrp. The trickiest part really, is just getting twrp installed. If you're using twrp to install a GSI, wipe system, data, dalvik, then flash the image to system. (You'll get a location prompt.) After installing a GSI, copy the overlay to /vendor/overlay, and set permissions on it to 0644, then reboot. Flash modded phh for root if you're using LOS 16 or 17. I think it's already included in Phh's AOSP builds.
There's also a trick to dual boot your OS. I keep one slot with stock installed, that's debloated and rooted with magisk. The other slot I use for flashing GSIs. Twrp can't restore encrypted data for stock, but you can format /data using "yes" then switch slots and use "reboot recovery" to boot up stock with magisk. To swap back to the GSI, fastboot boot twrp, format data, switch slots from the reboot menu, reboot to recovery. If twrp starts, you changed slots successfully. Then just restore data for lineage and bootup.
Oh by the way, "dirty flashing" is just flashing an OS update without wiping data first. I don't recommend it though. Sometimes bugs from older builds will get carried over. You don't need to do that to install LOS 17 or Android 10. It might've been true at one time, but it isn't now. You can just do your wipes and flash the latest build.
Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help
ggg777 said:
Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help
Click to expand...
Click to collapse
Typically if you've taken an OTA then you already have both slots filled. You can check with...
Code:
fastboot getvar all
Near the bottom you'll see some slot information. If slot b is active, then you should already be covered. I still think it's best to manually flash both slots though. If you've never updated then slot b is definitely empty. This is what I do...
Code:
fastboot flash boot_a boot.img
fastboot sending image boot_a...
Successful!
Image not signed blah blah something that isn't important...
Hit the up arrow on the keyboard then just change _a to _b
Code:
fastboot flash boot_b boot.img
Same with system, only I run through the list of sparse chunks in one shot, then hit the other slot. Use the big series of sparse chunks (0-7) on both slots. Skip the two that would normally go to system_b.
Code:
fastboot flash system_a system.image_sparsechunk.0
fastboot flash system_a system.image_sparsechunk.1
fastboot flash system_a system.image_sparsechunk.2
etc...
Then on the other side the same way.
Code:
fastboot flash system_b system.image_sparsechunk.0
fastboot flash system_b system.image_sparsechunk.1
fastboot flash system_b system.image_sparsechunk.2
etc...
When you get to oem, do not use oem_other.img, flash oem.img to both slots instead. Basically just make sure you do that with everything. E.g. dsp_b modem_b. I'm sure you get the idea by now.
Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need
ggg777 said:
Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need
Click to expand...
Click to collapse
Hey im in a smiliar situation with the G7 Play (XT1952-2)
I have the same goal of running this phone without google..
I would like to install LineageOS with microG (signature spoofing)
Have you been successful with this? Do you have a A-Z list of instructions for a fellow newbie?
I wanted to root my Google Pixel C. So as a first step I tried to installed twrp3.4.0-0 using the commands like fastboot flash recovery TWRP.img etc as described in many webpages. My pixel C restarted in twrp. When Reboot>System, i get message "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 secs ", then a Beep sound then Google logo for few seconds and then again twrp. Fastboot reboot command again bring my Pixel C to twrp. I think it has softbricked and I don't want to lose it . Can someone kindly help what I do to restore it with stock or install custom rom and root it. My ultimate goal is to run Linux on Pixel C. I was using Windows 10 before but now I am using Linux usb. Thanks
I ended my boot looping by installing stock rom (ryu-opm8.190605.005-factory-25b457f3) downloaded from google website. For me flash-all.bat or flash-all.sh were not working and throwing multiple kind of errors. I did two things. First I used this guide from xda to set PATH variable "How to Use ADB or Fastboot From Any Directory on your Windows/Linux PC". Then I copied the .zip ROM file into "platform-tools" folder. Importantly I also extracted the .zip file within the .zip to same platform-tool folder. I manually installed each .img file one by one:
sudo fastboot flash bootloader bootloader_dragon-google-smug.img
sudo fastboot reboot bootloder
sudo fastboot devices
sudo fastboot flash boot boot.img
sudo fastboot flash cache cache.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash vendor vendor.img
System now working fine with stock ROM and recovery.
On 1st screen of TWRP, do not swipe to modify system partition, choose the leftmost option to skip that step.
It still allows you to flash zips like Magisk, but system partition remains intact and bootable.
satelliteseeker said:
On 1st screen of TWRP, do not swipe to modify system partition, choose the leftmost option to skip that step.
It still allows you to flash zips like Magisk, but system partition remains intact and bootable.
Click to expand...
Click to collapse
If only I had see this before I installed TWRP
Hi guys,
I have a rooted mi10t lite on MIUI.
Got an update today (miu v12.0.2.0.RJSEUXM) so downloaded it via phone and pressed 'reboot now'.
Issue is the phone reboots into TWRP recovery and when I boot back to system the phone still tells me to update the phone by rebooting it which goes back to TWRP.
I tried to install the update via TWRP > Install>
The internal storage is encrypted though so I moved the updated .zip file to my SD Card (root of SD card folder).
I go back into TWRP after a reboot and flash the install but get an error when trying to install the update. Not sure why?
Code:
E: Unble to decrypt FBE device
Updating partition details...
...done
Updating partition details...
...done
MTP Enabled
Installing zip file '/external_sd/miuupdatenumberetc.zip'
Checking for Digest file...
Error installing zip file ''/external_sd/miuupdatenumberetc.zip'
Updating partiion details...
...done
Any ideas please? I don't really want to update the phone if it results in me losing everything and having to install magisk and TWRP again, etc.
Thanks
1. to install OTA update from system, you have to have stock recovery
2. installed TWRP can not decrypt data partition
I would:
1. restore stock recovery
2. install OTA update
3. hotboot TWRP so you can decrypt data partition (fastboot boot twrp.img), install Magisk
Your Magisk modules and all data will remain intact.
i have the same problem. if i want to restore stock recovery, is it the right way to flash via fastboot the recovery.img from the fastboot rom, or i will get issues?
Long story short, read the previous thread: https://forum.xda-developers.com/t/...-product-vendor-odm-invalid-argument.4431903/
After succesfully installing the fastboot rom via Mi Flash, the phone is still in a bootloop. Tried flashing TWRP via fastboot command (fastboot boot twrp.img) but it can't decrypt the /data partition with the correct passcode anymore. after a reboot in recovery, the /cust partition also can't be mounted anymore, with error "Structure needs cleaning".
I do not have a backup of my system nor data partition, nor internal storage, so i absolutely need it to work again without wiping/formatting the data partition
EDIT: after flashing the fastboot rom again via mi flash and twrp via fastboot command, the cust error disappears but twrp still can't decrypt /data
EDIT: i decided to do a full wipe of my internal memory and the phone works again. this thread should be closed.