Download link: https://drive.google.com/file/d/1gLshzM9zYEvR0Cknl4eh6KI32nEZbL5O/view?usp=sharing
I tried backing up the userdata.img, but that kept filling up my device storage. It was going beyond 19GB in size. So I cancelled the operation.
Enjoy these files, they will be useful for ROM porting, system restore, or system downgrade.
Editing these files can lead to a brick or a non booting state. So be careful.
I pulled all of these files from my device's system partitions.
What did you do to dump these? Did you use dd to dump them or any other method? I dumped a few partitions from my BNTV460 a while back, but I'm unsure if I did it properly, so I was curious of how you dumped it from your BNTV650.
turtleletortue said:
What did you do to dump these? Did you use dd to dump them or any other method? I dumped a few partitions from my BNTV460 a while back, but I'm unsure if I did it properly, so I was curious of how you dumped it from your BNTV650.
Click to expand...
Click to collapse
I temp rooted the Nook. Then I pulled the firmware files with ADB.
I saw that global MediaTek root tool posted earlier, I was just going to dump the partitions myself. Thank you for posting these OP! Does anyone know if there's a TWRP image for our devices? There's one posted for a "Barnes & Nobel Nook Tablet", but I haven't a clue if it's for the BNTV650.
I did make a TWRP for this device.
tgp1994 said:
I saw that global MediaTek root tool posted earlier, I was just going to dump the partitions myself. Thank you for posting these OP! Does anyone know if there's a TWRP image for our devices? There's one posted for a "Barnes & Nobel Nook Tablet", but I haven't a clue if it's for the BNTV650.
Click to expand...
Click to collapse
How to unlock the bootloader:
1) allow OEM unlocking in developer options in the device settings
2) download ADB onto your computer https://developer.android.com/studio/releases/platform-tools.html
3) cd to the directory in CMD
4) enter this command: adb reboot bootloader
5) once the device is in fastboot mode, do: fastboot oem unlock
How to flash the stock OEM recovery:
1) fastboot flash recovery STOCK_recovery.img
How to flash the tested buggy TWRP recovery:
1) fastboot flash recovery TESTED_recovery.img
How to flash the untested TWRP recovery:
1) fastboot flash recovery UNTESTED_recovery.img
How to reboot back into the OS:
1) fastboot reboot
Downloads:
- Stock: https://drive.google.com/file/d/1Z7AJH6fSbeOkLLWt2JVwsCKiwxt0vlYK/view?usp=sharing
- Tested: https://drive.google.com/file/d/1R4ph5Z5mofsac0Qd352H_BEEz9JS4wBA/view?usp=sharing
- Untested: https://drive.google.com/file/d/1zP81MuR5LLvdYuDvYQHPVCJlgCOUBPlt/view?usp=sharing
secretwolf98 said:
How to unlock the bootloader:
1) allow OEM unlocking in developer options in the device settings
2) download ADB onto your computer https://developer.android.com/studio/releases/platform-tools.html
3) cd to the directory in CMD
4) enter this command: adb reboot bootloader
5) once the device is in fastboot mode, do: fastboot oem unlock
How to flash the stock OEM recovery:
1) fastboot flash recovery STOCK_recovery.img
How to flash the tested buggy TWRP recovery:
1) fastboot flash recovery TESTED_recovery.img
How to flash the untested TWRP recovery:
1) fastboot flash recovery UNTESTED_recovery.img
How to reboot back into the OS:
1) fastboot reboot
Downloads:
- Stock: https://drive.google.com/file/d/1Z7AJH6fSbeOkLLWt2JVwsCKiwxt0vlYK/view?usp=sharing
- Tested: https://drive.google.com/file/d/1R4ph5Z5mofsac0Qd352H_BEEz9JS4wBA/view?usp=sharing
- Untested: https://drive.google.com/file/d/1zP81MuR5LLvdYuDvYQHPVCJlgCOUBPlt/view?usp=sharing
Click to expand...
Click to collapse
Oh, there are recoveries? Thanks! What's wrong with the buggy version?
I will try to update this thread soon with the latest software update. If I can remember how I pulled the system files.
secretwolf98 said:
I will try to update this thread soon with the latest software update. If I can remember how I pulled the system files.
Click to expand...
Click to collapse
Did B&N release a software update?
tgp1994 said:
Did B&N release a software update?
Click to expand...
Click to collapse
Yep. It is v1.0.21. With the build date of June 2020. And with the security patch of May 5, 2020.
so there is no twrp or custom rooted rom for this device?
Related
Hi,
After much read of guides, I post here my SIMPLE guide for OTA upgrades when your Moto G is unlocked and you use systemless root and TWRP.
This guide is safe and works!
For example, with this guide you can upgrade from STOCK MPJ24.139-23.4 to MPJ24.139-63:
Warning: I assume you know the concepts "fastboot", "systemless root" and TWRP.
For the original stock firmware search here for your exact MODEL and VERSION: http://mirrors.lolinet.com/firmware/moto/athene/official/
1) Reboot to TWRP and make a FULL BACKUP of your current firmware. Use the SD-Card and not the internal memory.
2) To Apply the OTA you need to restore BOOT.IMG and SYSTEM.IMG.
2a) If you rooted your device, for sure your BOOT.IMG isn't the original one. You can:
- Option 1: Restore it from an original backup of your firmware (if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "boot.img" and flash it in the fastboot mode using "fastboot flash boot boot.img".
2b) If you use Systemless SuperSU then your system partition can be untouched. In case of doubt, or if the patch shows an error, you can restore it...
- Option 1: Restore it from one backup of your firmware (only if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "system.img_sparsechunk.0-7" and flash them in the fastboot mode using these 8 commands (execute one, wait until completes, then execute the next one):
Code:
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
3) Boot to the TWRP Custom Recovery (you don't need to restore the original Recovery partition).
4) Download the OTA (Blur_Version.24.24.4.athene.retail.en.US.zip) or copy it from the downloaded directory. Copy the ZIP file to a computer, extract the file "/META-INF/com/google/android/updater-script" and edit it... Remove these three lines (this only removes the check of the running build, because you like to execute it inside TWRP):
Code:
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-63/64:user/release-keys" ||
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-23.4/4:user/release-keys" ||
abort("Package expects build thumbprint of 6.0.1/MPJ24.139-63/64:user/release-keys or 6.0.1/MPJ24.139-23.4/4:user/release-keys; this device has " + getprop("ro.build.thumbprint") + ".");
After that, copy (repack) this edited file to the ZIP file of the OTA. I suggest to change the name of the ZIP, for example to "Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip". Now, you can run this patch file running TWRP.
5) Copy the patch OTA file to the SD-CARD, boot to the TWRP and apply the OTA... After several minutes the task completes. Reboot and check if the update is done and all works well. Your data needs to be already there...
6) Reboot into the fastboot mode and reflash the TWRP Custom Recovery using "fastboot flash recovery twrp-3.0.2-0-athene.img". Then boot in the recovery mode and do another Backup (for save untouched "system.img" and "boot.img" partitions).
7) Now you can re-root using the TWRP mode and SuperSU 2.78 in Systemless mode (remember to execute "echo SYSTEMLESS=true>>/data/.supersu" prior to install the SuperSU.zip)
I hope this helps you!
This guide only uses the minimum and required steps.
:good:
If you like to download one already patched OTA, then download it from here (join the two files first!):
Part 1: http://www.sendspace.com/file/dkws7p
Part 2: http://www.sendspace.com/file/xaompg
Part 1: http://www.sendspace.com/file/e3of46
Part 2: https://www.sendspace.com/file/a3tl4r
CRC:
filename=Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip
size=508332365
crc32=AFEC5752
Thank you, I was wondering about just this. Will come In handy.
Do you need to resign the zip with signapk?
Thanks for you guide!
I used it to update my Lenovo P2 to Nougat.
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Indianvixen9 said:
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Click to expand...
Click to collapse
I've heard this from a few people. I got the Amazon variant little more than a week ago. Unlocked BL and rooted lickety splits, no issues.
I consider myself pretty tech savvy, but the post might as well have been in Swahili. Can it be dumbed down any further?
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
t0mm13b said:
Do you need to resign the zip with signapk?
Click to expand...
Click to collapse
No, just re-zip! :victory:
Dbush72 said:
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
Click to expand...
Click to collapse
Done! :highfive:
Thank you for the reply and refreshing the download links
As far as I can tell you are flashing this via TWRP which is why the zips dont need signed is that correct?
I have an xt1625 non-amazon version that im working with.
I tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml which didnt work with this error:
E3005: "EMMC:/dev/block/bootdevice/by-name/boot:
has unexpected contents
I also tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml
Failed with the same error as last time
I also tried flashing Blur_Version.24.31.48.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml which does seem to pass the version checks but gives this error:
"eom/app/BRApps2/oat/arm/BRApps.odex" has unexpected contents.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void... Well, probably not.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* A lot.
*
* Tl;dr: if your device crashes and burns, I'm sorry, but I'm not to be blamed.
*/
Hey guys.
This is a guide on how to install official Android 8.1.0 "Oreo" on our beloved, forgotten, poor Moto G5s (montana). As you all may know, Lenovorola still hasn't released Oreo for everyone worldwide. Only a few Latin American countries are receiving the update, with Brazil due to receive it Soon™, since we've already received the August security patch (still Nougat though :/).
Update 2018.09.29: Brazil and India have also started receiving Oreo, but with a different build (OPP28.65-37-2).
However, this is Lenovorola we're dealing with, so I went ahead, captured the OTA and created a TWRP flashable zip, by patching the June firmware (NPPS26.102-49-11) with said OTA. And also, there's the standard .xml.zip to be used with fastboot, directly from Moto.
For those of you who want to keep everything stock, locked bootloader and all, I recommend going with the fastboot zip. For those who already have unlocked their phone's bootloaders and have TWRP installed, or are coming from a custom ROM but don't want to fiddle around with fastboot, you should use the TWRP flashable zip.
I can't stress this enough. ALWAYS BACK UP YOUR STUFF!!!! Do a TWRP backup (data, system, boot). I recommend backing up the contents of your internal storage as well. And for those willing to downgrade at some point, back up your persist and efs partitions, otherwise you'll lose IMEI!
Oh, and I assume you already have adb, fastboot and the Motorola USB drivers installed. In case you don't...
Motorola USB Drivers
Android SDK Platform Tools (includes adb & fastboot)
If you use Linux, you don't need to install any drivers, but you may have to configure udev to allow fastboot to detect your device. But that, along with telling how to configure adb and fastboot, is beyond the scope of this thread.
I don't know how things work in the Apple side, so kindly don't ask me how to do that on macOS.
This firmware should work on all Moto G5s models (XT1791/2/3/4/5/7). I can't tell if it works on model XT1799-2 (aka Green Pomelo / Qingyou).
A few warnings:
1. Forced encryption has not been disabled. So, if your phone is not encrypted, it will be encrypted again upon the very first boot. Don't interrupt the process, otherwise you'll lose ALL of your data! (You can flash @Zackptg5's dm-verity / forced encryption disabler if you want to)
2. Xposed doesn't work, whether it's installed to /system or via Magisk (systemless). I've already opened an issue on GitHub and am awaiting a reply.
3. (Fastboot only) Updating to this firmware will also update your bootloader and partition table. If you're unsure about that and/or afraid of a possible hard brick, skip the gpt and bootloader lines.
4. Please install the proper build for your software channel. For retbr and retin, use OPP28.65-37-2. For the other channels, go with OPP28.65-37.
5. If your phone's software channel is retbr or retin and you have already flashed the -37 build, you can simply dirty flash the -37-2 build over it. No need to factory reset / fastboot erase userdata.
With that out of the way, let's get to what matters most.
Downloads:
Build OPP28.65-37 (retla):
Fastboot ZIP (Android File Host | MEGA)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Build OPP28.65-37-2 (retbr & retin):
Fastboot ZIP (Android File Host)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installation Guide:
Fastboot ZIP:
1. Download (obviously)
2. Extract the contents to a folder of your choice
3. Go to the folder which you extracted the files to
3. Inside the folder, open a command prompt, PowerShell, terminal or whatever you use as a command line interface
4. Put your device into fastboot mode if you haven't already done that (just hold Vol Down + Power for a while) and connect it to your PC
5. Execute the following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.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 system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
reboot
6. Have fun
Click to expand...
Click to collapse
TWRP Flashable ZIP:
1. Download (duh)
2. Put the file at the root of your internal storage (/sdcard)
3. Reboot to TWRP
4. Do a factory reset (optional if coming from stock Nougat) and then format /system
(If your device is encrypted and you want to remove encryption, you will have to format /data and then flash the forceencrypt disabler I mentioned above after flashing the ROM)
5. Flash the zip
6. Reboot
7. Have fun
Click to expand...
Click to collapse
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
@Cesarcami53 for telling us that the update was out for retla
@erfanoabdi for his Motorola OTA Link Generator and IMG Patch Tools
@lohanbarth for mirroring the fastboot zips to AFH / Mega
In case I forgot someone, please do let me know.
F.A.Q. (Read this before crying!!!!)
Q: Why did you come up with this?
A: Because Lenovorola is pulling a Samsung, taking forever to officially deliver the Oreo update to everyone.
Q: ERMAHGERD DIS ROM SUCKZ, MAH BATTERY IS DEAD IN 30 MINS, PLZ HALP!
A: Please do blame Motorola, or yourself, or your apps' developers, but not me. I haven't got anything to do with that. I haven't changed anything.
Q: What works and what doesn't?
In theory, everything should work, and nothing should be broken, since this is a stock ROM.
Q: Will you add feature xyz?
A: No.
Q: Why no inbuilt root/Magisk/xyz/abc?
A: Because not. 1. There's something called freedom of choice, and that must be respected. / 2. I want to keep everything as bit-perfect as possible, and as close as possible to what you would get by flashing a real OTA.
Q: How do I report bugs?
A: If you wanna report a bug, send me a logcat. In case of a kernel panic, /proc/last_kmsg will help.
Q: How do I flash this?
A: I suggest you scroll up and read the OP. The instructions are there.
Q: How do I tweak this ROM?
A: For theming, there's full OMS/Substratum support. Xposed doesn't work, so no extra tweaks for now.
Q: This kid is such a n00b!
A: Oh well then, why don't you go do something like this yourself, instead of criticizing my work and wasting your time?
Reserved again
Oh look! Another reserved post!
And as a bonus, have this nice little dark boot logo from me, which hides that dreaded "N/A" and also "bad key" things. Extract the zip file and flash the logo3.bin file inside using fastboot:
Code:
fastboot flash logo logo3.bin
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Which security pet
Official or Soak test?
Kamin4ri said:
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
[/SIZE]
Click to expand...
Click to collapse
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
I can tell you that this build work very well in european distribution (reteu).
Basicly everything work including sim and nfc(paying not tested yet)
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Also not able to download, please offer another download Location!
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
ilovepanda said:
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Click to expand...
Click to collapse
No. Your bootloader will be updated if, and only if, you install via fastboot and actually execute the respective command.
[email protected] said:
Official or Soak test?
Click to expand...
Click to collapse
This is the official firmware released for retla (Latin America). However, the soak tests in Brazil haven't finished yet. I'll update the OP with the link for the Brazilian firmware as soon as it's available.
NZedPred said:
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
Click to expand...
Click to collapse
Thank you, friend! I'll be definitely using that guide again.
7opex0 said:
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
Click to expand...
Click to collapse
Only if you're flashing via TWRP. If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
giugiura said:
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Click to expand...
Click to collapse
dau999 said:
Also not able to download, please offer another download Location!
Click to expand...
Click to collapse
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Kamin4ri said:
If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
Click to expand...
Click to collapse
Okay then! Thanks for information.
7opex0 said:
Okay then! Thanks for information.
Click to expand...
Click to collapse
Not at all!
Kamin4ri said:
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Click to expand...
Click to collapse
Please upload it on some other cloud so that we can download it thanks for help sir
In advance
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205
root: for A.87 stock rom
Unlock bootloader and place the mentioned two files to Platform tools folder on your pc.
Download "vbmeta.img" and "Magisk_patched.img"
• adb devices
• adb reboot bootloader
•fastboot devices
• fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• fastboot flash boot magisk_patched.img
• fastboot reboot
+++±+++++++
Guide to flash Recovery
- Connect your phone to PC, Allow USB Debugging. Now Type These Commands.
adb reboot bootloader
fastboot devices
fastboot reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recoveryname.img
fastboot reboot recovery
To keep custom recovery flash twrpkeep.zip when's booted to recovery :
Bro my device is a.89 ..is this vbmeta working...?
qeb said:
Bro my device is a.89 ..is this vbmeta working...?
Click to expand...
Click to collapse
Yes it work on all a10 update
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
misiek998 said:
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
Click to expand...
Click to collapse
oh, thank's men. edited.
Hello, Can I use the VBMeta on android 11 or no? thanks!
Ryeeeeel said:
Hello, Can I use the VBMeta on android 11 or no? thanks!
Click to expand...
Click to collapse
Can't root rui 2.0 (Android 11), and can't install custom recovery except "los recovery" but can't do any thing with it just wiping cache and data partition.
do not try to flash custom recovery on realme ui 2.0 , it will brick your device
I need to ask, this guide will work with A88/A89 update?
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
adamuadamu said:
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
Click to expand...
Click to collapse
Yes. Just flash the original firmware using SP Flash-Tools. However, youmust make sure it is the full 7-8 GB ROM, and not an OTA file. Also, ensure that you are flashing the correct ROM for your model. If your model is an RMX2155, you'll need to follow this guide steps 1-through-to-10 (inclusive):
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
If it is any other model, just do what is said to work. Unfortunately, I don't know much about the other versions.
thanks the explanation.
I've found a 2155 ROM or at least a file that's said to be - ie. I've found a file 'RMX2155export_11_C.09_2021070809260000', extracted that, there was a huge file 'RMX2155export_11_C.09_2021070809260000.ofp' inside; using oppo-decrypt from github I've got bunch of files with names that seem to be SPFlashTool ROM.
Assuming it's a proper ROM: if I have already unlocked the bootloader, do I have to flash the rom and do the 10 steps from the tutorial or could I replace recovery.img and magisk-patched boot.img and flash rooted rom immediately? Sorry if it sound noobish, but I don't want to brick the phone.
I'm curious to try to go back to stock ROM for a while, because of call quality (I believe changing it to Vietnam needed for unlock made the call quality worse) and to check the camera and it's libraries - I'm running crdroid, photo quality is disappointing no matter what GCam/settings/tweaks I use and there are only imx682/imx471 libs on the phone there are samsung libs, but diagnose apps like aida show the main sensor is imx682, but the EU version of realme 7 is said to have different back camera sensor (GM1). Not sure if RMX2151 ROMs would include proper GM1 libs if that's true about sensor differences between RMX2151 and 2155.
My Zenfone9 AI2202 (JP) Stopped at bootloader screen.
When I select recovery, it reboots and goes back to "Start" screen.
I used the following as a reference
Rooting Zenfone 9 with Magisk
Guide has been reworked to be more clear and based on comments. [Part One] Backup Data Update phone to latest version [Part Two] Download the Firmware for the Zenfone 9...
forum.xda-developers.com
Steps
- I have implemented the following steps
- Update OTA with Version WW-33.0804.2060.113 (2023/03/31)
- Download Same version of firmware
- dump boot.img using Payload Dumper GUI
- I patched boot.img with Magisk
- Execute the following command.
$fastboot flash boot patched_boot.img
I fell into a bootloop.
It is recognized as a fastboot device by Windows11.
Tried
I flashed boot.img before modifying it with Magisk.
Maybe I had wrong version on my device.
ASUS Flash Tool v2.0.1.0 only recognizes it as State: Fast boot device
I referred to the following
https://www.getdroidtips.com/asus-zenfone-9-ai2202-firmware-flash-file/
It says I can select "apply update from sd card." in Recovery mode,
But when I press the power button in Recovery mode, it reboots and won't let me enter recovery mode.
Question
How do I write the whole firmware?
I wish there was a flash-all.bat in the firmware like in Pixel series...
couldn't start from TWRP
$fastboot oem device-info
Device unlocked: false
The device may not have been successfully unlocked.
But then shouldn't fastboot flash boot boot.img fail?
Can boot.img be written without unlocking?
pompom252 said:
couldn't start from TWRP
Click to expand...
Click to collapse
I couldn't boot twrp after flashing magisk too until i remove magisk completely
pompom252 said:
My Zenfone9 AI2202 (JP) Stopped at bootloader screen.
When I select recovery, it reboots and goes back to "Start" screen.
I used the following as a reference
Rooting Zenfone 9 with Magisk
Guide has been reworked to be more clear and based on comments. [Part One] Backup Data Update phone to latest version [Part Two] Download the Firmware for the Zenfone 9...
forum.xda-developers.com
Steps
- I have implemented the following steps
- Update OTA with Version WW-33.0804.2060.113 (2023/03/31)
- Download Same version of firmware
- dump boot.img using Payload Dumper GUI
- I patched boot.img with Magisk
- Execute the following command.
$fastboot flash boot patched_boot.img
I fell into a bootloop.
It is recognized as a fastboot device by Windows11.
Tried
I flashed boot.img before modifying it with Magisk.
Maybe I had wrong version on my device.
ASUS Flash Tool v2.0.1.0 only recognizes it as State: Fast boot device
I referred to the following
https://www.getdroidtips.com/asus-zenfone-9-ai2202-firmware-flash-file/
It says I can select "apply update from sd card." in Recovery mode,
But when I press the power button in Recovery mode, it reboots and won't let me enter recovery mode.
Question
How do I write the whole firmware?
I wish there was a flash-all.bat in the firmware like in Pixel series...
Click to expand...
Click to collapse
Did you unlock your phone via Asus unlock app tool?
this is the link thread to restore back to stock
ZenFone 9 (AI2202) Repair to bootloader package
Download: Link 🔗 Steps: 1. Only works on EDL mode. 2. Run script 0-8475_update_image_EDL_fh_loader.bat 3. Update Official OTA package in recovery or install UserRAW in bootloader Thanks ASUS Taiwan, @EdwardWu6688 , and don't use it for...
forum.xda-developers.com
and for future reference, do not ever ever EVER
"Fastboot boot twrp.img"
Read the thread below, Asus have boot protection so fastboot boot is blocked and can lead to brick
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 9
Official TWRP is now available: https://twrp.me/asus/zenfone9.html IMPORTANT NOTES: CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6). This device has a recovery partition (2...
forum.xda-developers.com
Jairus980 said:
and for future reference, do not ever ever EVER
"Fastboot boot twrp.img"
Read the thread below, Asus have boot protection so fastboot boot is blocked and can lead to brick
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 9
Official TWRP is now available: https://twrp.me/asus/zenfone9.html IMPORTANT NOTES: CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6). This device has a recovery partition (2...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I used Asus unlock app tool.
However, seeing that it is not locked, it may be that the unlocking was not successful.
I have attached a screenshot.
Is an EDL cable required to enter EDL mode?
pompom252 said:
Thanks for the reply.
Yes, I used Asus unlock app tool.
However, seeing that it is not locked, it may be that the unlocking was not successful.
I have attached a screenshot.
Is an EDL cable required to enter EDL mode?
Click to expand...
Click to collapse
adb dont work while on fastboot mode, you cant do via "adb"
I suggest you read the thread above
"ZenFone 9 (AI2202) Repair to bootloader package"
Take your time to read one by one
Jairus980 said:
adb dont work while on fastboot mode, you cant do via "adb"
I suggest you read the thread above
"ZenFone 9 (AI2202) Repair to bootloader package"
Take your time to read one by one
Click to expand...
Click to collapse
Thank you very much. In the relevant thread, you had the information after exchange about whether "EDL cable" is needed or not.
It is important to read carefully.
I solved the problem by running "flashall_AFT.cmd" with device recognized as fastboot device.
Android 12 is now booted!
I was worried that IMEI would disappear, but I was able to keep IMEI.
My device was purchased in Japan, so it was equipped with Felica, which could also continue to be used.
Thank you very much for your good advice.