Develop Bugs

[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016]

PERISIST ERROR IN TWRP WHILE FLASHING ANY ZIP.....? THEN HERE IS THE GUIDE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
1. You get "e: cannot mount /persist" in recovery
2. Can't access to internal storage.
3. Boot loop on Lollipop 5.0 and above
4. IMEI number is lost even after formating cache and fastboot flash cache.img
5. No signal even after formating cache and fastboot flash cache.img
Then your persist partition have to be fixed​
Follow instructions carefully to solve this issue
NOTE : UNLOCK your device bootloader first before doing this
1. Download this " persist file & ADB+&+Fastboot of yureka " provided by @Annabathina
2. extract them in PC
3. open ADB+&+Fastboot of yureka
4. place presist.img file which you have extracted in ADB+&+Fastboot folder
5. Hold shift key and right click on mouse and select Open command window here
6. Connect your device to pc..... and make sure that drivers are installed properly..... ( VERY VERY IMPORTANT )
a. Type : adb devices
If your device is connected you will get it in connected devices list
b. Type : adb reboot-bootloader
Your phone will restart into bootloader.
c. Type : fastboot -i 0x1ebf flash persist persist.img
7. Disconnect your device from PC and REBOOT​
ADB+&+Fastboot : link
persist : link
Useful links
ADB for pc : link
YU usb drivers : link
PdaNet drivers : link
@Annabathina............................for Guide
Ricks ............... for Presist file
YU YUREKA
YU YUREKA PLUS​
XDA:DevDB Information
[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016], Tool/Utility for the YU Yureka
Contributors
Annabathina
Version Information
Status: Stable
Stable Release Date: 2016-04-21
Created 2016-04-21
Last Updated 2016-04-23

Reserved

Reserved

I dont get a multirom function in the advanced settings menu. Is it because im using twrp 3.0.... Or is it bcoz of persist partition ?
Sent from my AO5510 using XDA-Developers mobile app

After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..

Bazilbycom said:
After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..
Click to expand...
Click to collapse
Have you solved it?

saurav007 said:
Have you solved it?
Click to expand...
Click to collapse
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers

Hi,
For me the message is : is not possible to erase this partition
Thanks a lot for your help

still same error.....what to do now..??

Bazilbycom said:
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers
Click to expand...
Click to collapse
Earlier i was getting error even after installing all the drivers, all i needed was to update PDAnet on phone as well & it does everything.
Thank you it worked well!

still stucking
i was suffering of problem error persist but using this method it solved the error is gone but not still my device stuck on boot i tried many custom roms stock rom formats and all but still it stuck after 2 of android logo. in twrp recovery in mount option the system, persist, firmware are uncheck .i think it means they are not mount right??? i click many time to check and reboot but still logo stuck problem please give me solution!!!!!!!
Thank You

Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk

vijaysingh1996 said:
Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk
Click to expand...
Click to collapse
This isn't TWRP flashable zip. You have to flash via fastboot (see OP) after extracting the img from downloaded zip file.

Failing on my Pantech Sky Vega Iron 2 IM-A910S (codename: ef63) and bootloader unlocked.
In Fedora Linux the command continues to display "waiting for device" message even though the device is detected by "fastboot devices" command, although its serial number is not displayed and ???????? is display in that place.
While in Windows 7 (64-bit), the following error message is displayed after execution of the command "fastboot -i 0x1ebf flash persist persist.img":
target reported max download size of 1610612736 bytes
sending 'persist' (4324 KB)...
OKAY [ 0.165s]
writing 'persist'...
FAILED (remote: It is not surpport in user build.)
finished. total time: 0.186s
Any one please help...

In my device it showing can't load persist
After typing last line

shekarsahani said:
In my device it showing can't load persist
After typing last line
Click to expand...
Click to collapse
Can you post CMD screenshot?
Make sure the file name is same as in CMD.

Unfortunately I can't is send cmd screenshot it is not uploading..
When I type fastboot -i 0x1ebf flash persist persist.img then it shows error cannot load 'persist.img'

Can't encrypt w CM 12.1

I recently re-installed CM 12.1 and have found that I can't encrypt my phone. Every time I try to encrypt, the phone shows the Android working screen for about 5 seconds, then restarts. No encryption.
Very strange, bc previously I was able to encrypt while running the exact same version of CM. Stats below.
Sony Xperia Z1C
CM 12.1-20161016-NIGHTLY-amami
Recovery: TWRP 3.0.2-0
Any idea what I'm doing wrong? Thanks!

Hi,
most likely, this is because you formatted you data partition with a twrp that doesn't support decryption and hence your partition is too big now.
Try my build which support decryption (https://www.androidfilehost.com/?fid=24533103863142425), backup your stuff, format data and try again.
Cheers

most likely, this is because you formatted you data partition with a twrp that doesn't support decryption and hence your partition is too big now.
Click to expand...
Click to collapse
Thank you derf!
Question: I've also been unable to install AICP using this version of TWRP, but I've been able to install CM12 on multiple occasions. Do you think this is related?
Thanks!

@derf elot I can't seem to get the new recovery to install. Terminal says it's successful, but when I boot into recovery, it's still 3.0.2-0, and I get an error when I try to format data. Any ideas? Deets below.
Here's a readout from Terminal:
./fastboot flash recovery twrp-3.0.2-1.img
sending 'recovery' (11660 KB)...
OKAY [ 0.397s]
writing 'recovery'...
OKAY [ 0.774s]
finished. total time: 1.172s​
Then I reboot, and then reboot again into recovery. I see TWRP 3.0.2-0. When I try to format data, I get
E:Unable to wipe '/data' - - unknown file system 'atuo'
Unable to format to remove encryption​Even though I'm not encrypted.
What am I doing wrong?

Recovery must be instaled in FOTA i think?
P.S. try Rashr app from the store to flash recovery to FOTA.

zlata said:
Recovery must be instaled in FOTA i think?
P.S. try Rashr app from the store to flash recovery to FOTA.
Click to expand...
Click to collapse
I just tried Rashr. Same results: Even though I'm installing TWRP 3.0.2-1, I still see TWRP 3.0.2.0 when I boot into recovery. And I'm still not able to format data.
How do I install via FOTA? Is there a fastboot or adb command?
Thank you!

@zlata would this command work?
Code:
fastboot flash FOTAKernel twrp-3.0.2-1.img

Hi,
yes, that should work. It might be because of some fstab settings I put in there.
Please try the attached one, unzip and flash the .img. Let me know.
Cheers

derf elot said:
Hi,
yes, that should work. It might be because of some fstab settings I put in there.
Please try the attached one, unzip and flash the .img. Let me know.
Cheers
Click to expand...
Click to collapse
Success! I was able to format data, restore from a backup, and encrypt my phone. Thank you @derf elot!!!
I'm still unable to install AICP for some reason, but it doesn't seem to be a TWRP issue. I'll solve in an AICP thread. Thank you!!!

[ROM][10][UNOFFICIAL] OmniROM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download :
GApps : https://dl.omnirom.org/tmp/def/
microG : https://dl.omnirom.org/def/
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it).
Get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
You should see a recovery like screen with a red "fastbood" message
Extract payload.bin using payload dumper (google it for tutorials)
fastboot -w (warning : this will wipe all your data)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
UPDATE
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram group for One Hyper : https://t.me/MotoOneHyper
XDA:DevDB Information
OmniROM, ROM for the Motorola One Hyper
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-02-02
Created 2020-02-02
Last Updated 2020-08-15

I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?

orimigato said:
I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?
Click to expand...
Click to collapse
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?

vache said:
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?
Click to expand...
Click to collapse
Yes I got an OTA when I got my phone today.

orimigato said:
Yes I got an OTA when I got my phone today.
Click to expand...
Click to collapse
Download stock ROM that match your current version from https://mirrors.lolinet.com/firmware/moto/def/official/
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7

vache said:
Download stock ROM that match your current version from ...
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
Click to expand...
Click to collapse
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed

orimigato said:
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip

vache said:
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!

orimigato said:
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!
Click to expand...
Click to collapse
Wew cool it worked, i was running out of ideas xD

First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !

orimigato said:
First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !
Click to expand...
Click to collapse
Thanks for the detailed report.
1. About bluetooth, noticed that later while testing, already fixed.
2. You'd better install back Moto Camera 2 from Play Store if you want to get all stock features.
3. Never used that feature tbh, could you grab some logs ? (i'll make some tests on my side anyway)
I'll try to release the new build later today.
Edit : Created an account here : https://www.linphone.org/freesip/home
Then used https://freephonebox.net/ to call me, and it seems to work. (see attached screenshots)

SIP
Retried the SIP and now it is working. Possible was not working earlier since my old phone was still registered. Thanks for checking:good:

Any idea when you could have a build available? Thanks in advance for your efforts :good:

orimigato said:
Any idea when you could have a build available? Thanks in advance for your efforts :good:
Click to expand...
Click to collapse
Sorry, it was delayed cause i was working on dolby. Ill post it tomorrow.
Edit : New build ->https://www.androidfilehost.com/?fid=4349826312261718849 (check OP for update instruction)
Changelog :
- Fix bluetooth audio playback
- Added Dolby audio (Use QS Tile to open it for now)
- Added Google Feed to launcher
- February security patch
- Fixed tap to wake
- Synced kernel source with CAF
https://gerrit.omnirom.org/q/status:merged
https://github.com/boulzordev/device_motorola_def/commits/android-10
https://github.com/boulzordev/kernel_motorola_sm6150/commits/android-10

Bluetooth works perfectly now. Dolby is also very nice. Many thanks!

Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?

htcmusic said:
Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?
Click to expand...
Click to collapse
Yes what's the best root method you guys using?

young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
I will receive this phone next week (US version) and I will use patching boot.img method

mingkee said:
I will receive this phone next week (US version) and I will use patching boot.img method
Click to expand...
Click to collapse
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7

young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
young-ster said:
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7
Click to expand...
Click to collapse
I see it
https://mirrors.lolinet.com/firmware/moto/def/official/RETUS/

Howto - Root your bramble with Magisk

Hi everyone,
I just got my bramble today. And yes, the first thing I did, was unlocking the bootloader and rooting it.
Here I tell you how I did it.
You need a ADB/Fastboot suite installed and this rooted kernel.
Section 1: Unlocking your Bootloader Unlocking your Bootloader will erase all your data - so best case is a brandnew and clean bramble...:
1. Go to settings - "About phone" and tip 6 times on "Build number" until you see "congratulations, you are a developer"
2. Go to settings - "System", tip on "Advanced" and then on "Developer options". Now you can see "OEM unlocking". Enable it (yes it warns you about security and stuff... It´s your choice - I did it ).
3. Install Adb and Fastboot suite and scroll to the adb-folder inside your windows explorer and when you are there, copy the rooted boot.img to your adb-folder (you need that for section 2).
4. Right click + shift on the white background of your adb-folder "open power shell window here"
5. Reboot your bramble holding vol- and you will enter the fastboot screen. Connect your bramble to your pc and type in your power shell window the following code:
Code:
./fastboot flashing unlock
and hit enter
6. Your bramble will warn you that unlocking your bootloader is insecure! And one really important thing again: This will format all your data
7. Use the vol-/vol+ keys to accept and violla, you unlocked your Bootloader!
Section 2: flashing the patched boot.img
1. Luckily you already copied the rooted boot.img to your adb folder and you are still in your power shell window. That gives you everything for 2.
2. type the following in your power shell window:
Code:
./fastboot flash boot boot.img
3. hit enter and
4. reboot to system (yes it has to be setup again since your data got wipede) and install Magisk manager after setting up your system
Congrats, your system is now rooted with Magisk!

@TNSMANI, sorry, unfortunately I put this into the wrong forum. It hast to be unter "Guides news and discussion". Would you be so kind to put it from here to there? Thx.

Hey now ..thanks for posting .
I'm bootloader unlocked but when I run command to root ./fastboot flash boot boot.img.img
I get no such file or directory although I have it in my adb folder
If I take the last .img out I get okay
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bkdodger said:
Hey now ..thanks for posting .
I'm bootloader unlocked but when I run command to root ./fastboot flash boot boot.img.img
I get no such file or directory although I have it in my adb folder
If I take the last .img out I get okay View attachment 5138473
Click to expand...
Click to collapse
He's got a case of the "didn't enable show file extensions" in windows. I downloaded my own system image and then patched the boot.img with magisk manager. I hate for you to have to piece it together, but I got my phone yesterday and worked through these things. Check it out here:
https://forum.xda-developers.com/pixel-4a-5g/help/magisk-boot-img-patching-flashing-t4191955

bkdodger said:
Hey now ..thanks for posting .
I'm bootloader unlocked but when I run command to root ./fastboot flash boot boot.img.img
I get no such file or directory although I have it in my adb folder
If I take the last .img out I get okay View attachment 5138473
Click to expand...
Click to collapse
Funny, maybe Gdrive removes double endings... I'll edit my post, thx!

Hey there,
after following your instructions Magisk Manager does not seem to detect Magisk (see Attachment). Can anyone help me figure out what am i missing?
Here's my consoleoutput:
Code:
$fastboot flashing unlock
OKAY [ 0.290s]
Finished. Total time: 0.291s
-------------------------------
$fastboot flash boot ./boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.850s]
Writing 'boot_b' OKAY [ 0.310s]
Finished. Total time: 3.520s
-------------------------------
Also: will there be a way to hide the 'device-is-unlocked-warning' on boot?
Thank you!

[Jan] said:
Hey there,
after following your instructions Magisk Manager does not seem to detect Magisk (see Attachment). Can anyone help me figure out what am i missing?
Here's my consoleoutput:
Code:
$fastboot flashing unlock
OKAY [ 0.290s]
Finished. Total time: 0.291s
-------------------------------
$fastboot flash boot ./boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.850s]
Writing 'boot_b' OKAY [ 0.310s]
Finished. Total time: 3.520s
-------------------------------
Also: will there be a way to hide the 'device-is-unlocked-warning' on boot?
Thank you!
Click to expand...
Click to collapse
That´s really strange! I have exactly the same console output... And it works for me.
Might it be possilbe that you use another rom build? I used the November -b build.
Maybe you can first update to the last os and then retry flashing my boot.img.
About BL-Warning. I have the same... And I dont´t know how to remove it. We would need to manipulate the bl, what I would not do...! Just ignore it!

Voodoojonny said:
;83961089']
That´s really strange! I have exactly the same console output... And it works for me.
Might it be possilbe that you use another rom build? I used the November -b build.
Maybe you can first update to the last os and then retry flashing my boot.img.
Click to expand...
Click to collapse
For me, it also didn't work with your pre-patched boot.img (also on latest November update). Had to download the factory image and patch it myself to make it work.

Voodoojonny said:
That´s really strange! I have exactly the same console output... And it works for me.
Might it be possilbe that you use another rom build? I used the November -b build.
Maybe you can first update to the last os and then retry flashing my boot.img.
About BL-Warning. I have the same... And I dont´t know how to remove it. We would need to manipulate the bl, what I would not do...! Just ignore it!
Click to expand...
Click to collapse
Hm.. actually been on the latest available build. Can you confirm this boot.img is working for build-id *.003.B1? (Also appended file-checksum, even though I doubt the file is damaged).
Code:
$shasum -a 256 ./boot.img
50fc81f5f59def3f366fcddd7976cbcbdc406172685c3e8a6cc24968d55c5964 ./boot.img
-------------------------------
$adb shell getprop | grep "ro.build.date\|ro.build.date\|ro.build.id\|ro.build.tags\|ro.build.product\|ro.build.version"
[ro.build.date]: [Tue Oct 6 11:12:31 UTC 2020]
[ro.build.date.utc]: [1601982751]
[ro.build.id]: [RD1A.201105.003.B1]
[ro.build.product]: [bramble]
[ro.build.tags]: [release-keys]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [6886588]
[ro.build.version.min_supported_target_sdk]: [23]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.build.version.release]: [11]
[ro.build.version.release_or_codename]: [11]
[ro.build.version.sdk]: [30]
[ro.build.version.security_patch]: [2020-11-05]
-------------------------------
Simma said:
For me, it also didn't work with your pre-patched boot.img (also on latest November update). Had to download the factory image and patch it myself to make it work.
Click to expand...
Click to collapse
Thanks, will try this as well!
UPDATE: Got it successfully rooted by patching the factory image.

[Jan] said:
Hm.. actually been on the latest available build. Can you confirm this boot.img is working for build-id *.003.B1? (Also appended file-checksum, even though I doubt the file is damaged).
Code:
$shasum -a 256 ./boot.img
50fc81f5f59def3f366fcddd7976cbcbdc406172685c3e8a6cc24968d55c5964 ./boot.img
-------------------------------
$adb shell getprop | grep "ro.build.date\|ro.build.date\|ro.build.id\|ro.build.tags\|ro.build.product\|ro.build.version"
[ro.build.date]: [Tue Oct 6 11:12:31 UTC 2020]
[ro.build.date.utc]: [1601982751]
[ro.build.id]: [RD1A.201105.003.B1]
[ro.build.product]: [bramble]
[ro.build.tags]: [release-keys]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [6886588]
[ro.build.version.min_supported_target_sdk]: [23]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.preview_sdk_fingerprint]: [REL]
[ro.build.version.release]: [11]
[ro.build.version.release_or_codename]: [11]
[ro.build.version.sdk]: [30]
[ro.build.version.security_patch]: [2020-11-05]
-------------------------------
Thanks, will try this as well!
UPDATE: Got it successfully rooted by patching the factory image.
Click to expand...
Click to collapse
I don't know what I'm doing wrong I can't patch it .. unsuccessful..ughhh

bkdodger said:
I don't know what I'm doing wrong I can't patch it .. unsuccessful..ughhh
Click to expand...
Click to collapse
My advice would be:
- ensure you got the factory image from developer.google.com corresponding to your buildnumber
- ensure you are using canary magisk manager (which is the only version as of today supporting redfin and bramble)

[Jan] said:
My advice would be:
- ensure you got the factory image from developer.google.com corresponding to your buildnumber
- ensure you are using canary magisk manager (which is the only version as of today supporting redfin and bramble)
Click to expand...
Click to collapse
I check the build is latest ...my Magisk is below

bkdodger said:
I check the build is latest ...my Magisk is below View attachment 5138961
Click to expand...
Click to collapse
Magisk version fits.
What about the boot.img file? It should be originated from path '*/bramble-{buildnumber}-factory-{sha}.zip/bramble-{buildnumber}/image-bramble-{buildnumber}.zip/boot.img'.

[Jan] said:
Magisk version fits.
What about the boot.img file? It should be originated from path '*/bramble-{buildnumber}-factory-{sha}.zip/bramble-{buildnumber}/image-bramble-{buildnumber}.zip/boot.img'.
Click to expand...
Click to collapse
Oh maybe I'm doing this part wrong ? I moved over the top file

bkdodger said:
Oh maybe I'm doing this part wrong ? I moved over the top file
Click to expand...
Click to collapse
It's the boot.img inside the next zip (image-bramble...)

Simma said:
It's the boot.img inside the next zip (image-bramble...)
Click to expand...
Click to collapse
Thanks for reply ..it was in there and I finally got it rooted ...I really don't know why it was not working but the third time was the charm ...[emoji16]

I'm trying to install Magisk, but I need a custom recovery. I can't figure out how to install one. TWRP app keeps force-closing when I try to install it, and there's no Pixel 4a 5G listed in devices in the TWRP website. I also can't find anything from ClockworkMod.

Hey, there ist no custom recovery available yet, becouse this phone is brandnew! There will be TWRP and other recoveries in the future, until then, we need to be creative. One way is extracting and patching the boot.img and reflash it via fastboot. How to do that is described in OP!

I got Magisk working. However, I cannot pass safetynet. I tried the props workaround mentioned in the 4a guide, but it still does not work.

WhiteAsIce said:
I got Magisk working. However, I cannot pass safetynet. I tried the props workaround mentioned in the 4a guide, but it still does not work.
Click to expand...
Click to collapse
Have you tried hiding the apps in Magisk? Do you want safetynet for a specific app that won't launch/complains about being rooted? Try MagiskHide in Magisk Manager if you haven't. Exclude those apps to hide root from them.

Trying to install latest TWRP on Moto G5 gives error (bootloader) Image size exeeded partition limits

Hi
I decided to try installing Lineage OS on a moto G5. I used this guide on the lineage OS website: https://wiki.lineageos.org/devices/cedric/install
That guide pointed me to the TWRP downloads page where I downloaded the latest version, which is currently:
twrp-3.5.2_9-0-cedric.img17.1M 2021-04-05 15:20:14 EDT
I downloaded this, renamed it to "twrp.img", put it in the same folder as my adb tools, then ran the command: "fastboot flash recovery twrp.img"
It gave me the following output in the command prompt:
"(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17536 KB) OKAY [ 0.562s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed"
I googled this and found a few people mentioning this problem on other devices, but couldn't find a solution. Out of curiosity, I downloaded an older version of TWRP which has a smaller file size. I managed to flash that recovery so I thought I had cracked the problem!.. but since I was using an older version of TWRP it meant that actually flashing the Lineage ROM didn't work. As I understand it, the latest Lineage Rom will only work with latest TWRP.
Does anyone know what the problem is?
I managed to do everything else fine, aka I unlocked the bootloader using code from Motorola website.
I will need to sort something out because in trying to fix this I followed a guide which had me wipe everything and now the phone has no OS at all!
Is this a problem with TWRP's file size being too big now for this old phone's recovery partition? Or am I just being stupid?

trickyDicky314 said:
Hi
I decided to try installing Lineage OS on a moto G5. I used this guide on the lineage OS website: https://wiki.lineageos.org/devices/cedric/install
That guide pointed me to the TWRP downloads page where I downloaded the latest version, which is currently:
twrp-3.5.2_9-0-cedric.img17.1M 2021-04-05 15:20:14 EDT
I downloaded this, renamed it to "twrp.img", put it in the same folder as my adb tools, then ran the command: "fastboot flash recovery twrp.img"
It gave me the following output in the command prompt:
"(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17536 KB) OKAY [ 0.562s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed"
I googled this and found a few people mentioning this problem on other devices, but couldn't find a solution. Out of curiosity, I downloaded an older version of TWRP which has a smaller file size. I managed to flash that recovery so I thought I had cracked the problem!.. but since I was using an older version of TWRP it meant that actually flashing the Lineage ROM didn't work. As I understand it, the latest Lineage Rom will only work with latest TWRP.
Does anyone know what the problem is?
I managed to do everything else fine, aka I unlocked the bootloader using code from Motorola website.
I will need to sort something out because in trying to fix this I followed a guide which had me wipe everything and now the phone has no OS at all!
Is this a problem with TWRP's file size being too big now for this old phone's recovery partition? Or am I just being stupid?
Click to expand...
Click to collapse
Note later 64bit twrp version for some reason exceed partition size. If you require a permanently installed TWRP use an old version.
To use the later versions of TWRP you need to boot to TWRP instead each time you want to use it.
Click to expand...
Click to collapse
see
[Official] [5th April 2021] TWRP 3.5.2_9-0 Moto G5 [Cedric] [32/64bit Roms]
Official TWRP For Moto G5 Cedric Post 1 - Instructions Post 2 - FAQs For full details and notes see Official TWRP for Cedric Site For TWRP news change logs etc see TWRP Official Site Instructions For non rooted and rooted phones...
forum.xda-developers.com

As clearly stated on my twrp thread. To use newer versions you have to temp boot to twrp
Or use an older version if you want a permanently installed twrp
twrp-3.5.0_9-0 I think is the latest version you can flash rather than only being able to boot.

sd_shadow said:
see
[Official] [5th April 2021] TWRP 3.5.2_9-0 Moto G5 [Cedric] [32/64bit Roms]
Official TWRP For Moto G5 Cedric Post 1 - Instructions Post 2 - FAQs For full details and notes see Official TWRP for Cedric Site For TWRP news change logs etc see TWRP Official Site Instructions For non rooted and rooted phones...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for fast reply! I will try just booting new version and installing. I didn't realize that would work, I thought u needed TWRP permanently installed for it to work, (am not experienced with this stuff).
Thanks again!

TheFixItMan said:
As clearly stated on my twrp thread. To use newer versions you have to temp boot to twrp
Or use an older version if you want a permanently installed twrp
twrp-3.5.0_9-0 I think is the latest version you can flash rather than only being able to boot.
Click to expand...
Click to collapse
Thanks for the reply! I hadn't seen that thread. I will try flashing lineage with temp booted TWRP. I don't need it permanently installed, I just thought it was a requirement.

trickyDicky314 said:
Thanks for the reply! I hadn't seen that thread. I will try flashing lineage with temp booted TWRP. I don't need it permanently installed, I just thought it was a requirement.
Click to expand...
Click to collapse
Most builds of Lineage Rom include the lineage recovery anyways.
So when you install the rom it will also install their recovery.

sd_shadow said:
Most builds of Lineage Rom include the lineage recovery anyways.
So when you install the rom it will also install their recovery.
Click to expand...
Click to collapse
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this

trickyDicky314 said:
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
Click to expand...
Click to collapse
You want stock firmware, custom roms don't overwrite everything.
Depends on your software channel. if it's a UK model it should be on RETGB
There are at least 2 different UK models XT1676, and XT1675.
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETGB/
To be sure you should check getvar all
Code:
fastboot getvar all
Easiest way to install stock is LMSA's Rescue
Just verify it's choosing the correct Model # and Software Channel
Spoiler: This is an example of what LMSA will look like, just a different device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

trickyDicky314 said:
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
Click to expand...
Click to collapse
Download stock firmware from below link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You want the latest retail version
Put phone into fastboot mode
These are the terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Download rom zip
Download gapps (open gapps arm64 nano)
Download magisk (for root)
Flash/boot twrp
Go to wipe
Format data (option on the right)
Restart to recovery
Swipe to allow system modifications in twrp
Go to wipe - advanced wipe
Wipe system data cache
Install rom zip
Install gapps
Install magisk
Wipe delvik cache
Restart
Once booted you can encrypt phone via settings if you want to

sd_shadow said:
You want stock firmware, custom roms don't overwrite everything.
Depends on your software channel. if it's a UK model it should be on RETGB
There are at least 2 different UK models XT1676, and XT1675.
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETGB/
To be sure you should check getvar all
Code:
fastboot getvar all
Easiest way to install stock is LMSA's Rescue
Just verify it's choosing the correct Model # and Software Channel
Spoiler: This is an example of what LMSA will look like, just a different device
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much for the help. I installed this programme but it didn't work when I selected the model etc
I tried the longer method provided by the fixitman and it worked! I got lineage installed!
Thanks again

TheFixItMan said:
Download stock firmware from below link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You want the latest retail version
Put phone into fastboot mode
These are the terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Download rom zip
Download gapps (open gapps arm64 nano)
Download magisk (for root)
Flash/boot twrp
Go to wipe
Format data (option on the right)
Restart to recovery
Swipe to allow system modifications in twrp
Go to wipe - advanced wipe
Wipe system data cache
Install rom zip
Install gapps
Install magisk
Wipe delvik cache
Restart
Once booted you can encrypt phone via settings if you want to
Click to expand...
Click to collapse
Thanks so much! This worked, I am now in Lineage OS! Thanks for taking the time to help out a newb like me by writing out every step

trickyDicky314 said:
Thank you so much for the help. I installed this programme but it didn't work when I selected the model etc
I tried the longer method provided by the fixitman and it worked! I got lineage installed!
Thanks again
Click to expand...
Click to collapse
Yeah, just skip that, and go straight to the rescue option