Ok, I extracted the boot system and flexrom from my brothers A500 which has Acer_A500_1.105.01_EMEA_GEN3 (unzip to see the update.zip, flexrom.img, boot.img and system.img).
Download here.
Let me explain what I did to restore mine to stock.
I bricked my device but thanks to the update.zip from this thread I was able to recover it.
Next I flashed the system.img and flexrom.img with the following commands in ADB (you need root obviously)
Important: in this order!
ADB shell
su
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
(takes about 30 secs, 100 MB)
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
(takes a couple minutes, it's 600 MB)
First I tried to flash the boot.img also but this resulted in an LNX checksum error during start-up and had to re-apply the update.zip. So don't do this.
After the flexrom.img and system.img were flashed I rebooted the A500. Note: the A500 will be unresponsive after flashing system.img so you have to reboot manually (holding power button).
I was able to select the proper language (Dutch in my case). But wifi wasn't working so I had to make this working again using these files (depending on your kernel). You can restore wifi using this post. You might need to run gingerbreak again for root.
After that was working I was given the option to update . I tried the update but it failed due to the boot.img. I rebooted the A500 and flashed the boot.img using ADB with this command.
ADB shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2
(takes a couple seconds, only 8 MB)
After it is finished do not reboot!! as this will result in a LNX checksum error.
Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3.
In any case your device doesn't offer you the update I included it with the download. The update.zip came from this post. In that case I would think you first flash boot.img and then reboot with the vol - button pressed while update.zip on your EXT_SD.
I hope this will help some people.
I redid the whole guide to check for errors and I found non.
What's new? Thanks for sharing
Nothing's new but this a way to restore your A500 back to Acer_A500_1.141.01_EMEA_GEN3 if you had to restore the tablet with an foreign update.zip.
i c. thank you.
Always keep a backup of the following partitions for any firmware version you want to restore to. (ie. i have these for my original 1.104.02 and 1.141.07).
mmcblk0p1 (recovery)
mmcblk0p2 (boot)
mmcblk0p3 (system)
mmcblk0p5 (misc)
mmcblk0p6 (flexrom)
mmcblk0p7 (??)
If bricked, use any of the base update.zips to get back to a bootable tablet.
Then to restore to your given version:
1. Push all your backup files to your device with the DD command EXCEPT mmcblk0p3 (system).
2. Run itsmagic to update the checksums
3. Push the mmcblk0p3 file last (this will cause the tab to lock up).
4. Reboot
If running the dd command from adb shell, you'll see when it finishes the push. If running it from a terminal emulator, give step 3 at least 5 full minutes to complete before rebooting.
I did this last night with my original 1.104.02 backup and then took the OTA to 1.141.07. worked perfectly.
Edit: I'm gonna update my rom flasher app to do this whole procedure
spaanplaat said:
Ok, I extracted the boot system and flexrom from my brothers A500 which has Acer_A500_1.105.01_EMEA_GEN3 (unzip to see the update.zip, flexrom.img, boot.img and system.img).
Download here.
Let me explain what I did to restore mine to stock.
I bricked my device but thanks to the update.zip from this thread I was able to recover it.
Next I flashed the system.img and flexrom.img with the following commands in ADB (you need root obviously)
Important: in this order!
ADB shell
su
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
(takes about 30 secs, 100 MB)
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
(takes a couple minutes, it's 600 MB)
First I tried to flash the boot.img also but this resulted in an LNX checksum error during start-up and had to re-apply the update.zip. So don't do this.
After the flexrom.img and system.img were flashed I rebooted the A500. Note: the A500 will be unresponsive after flashing system.img so you have to reboot manually (holding power button).
I was able to select the proper language (Dutch in my case). But wifi wasn't working so I had to make this working again using these files (depending on your kernel). You can restore wifi using this post. You might need to run gingerbreak again for root.
After that was working I was given the option to update . I tried the update but it failed due to the boot.img. I rebooted the A500 and flashed the boot.img using ADB with this command.
ADB shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2
(takes a couple seconds, only 8 MB)
After it is finished do not reboot!! as this will result in a LNX checksum error.
Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3.
In any case your device doesn't offer you the update I included it with the download. The update.zip came from this post. In that case I would think you first flash boot.img and then reboot with the vol - button pressed while update.zip on your EXT_SD.
I hope this will help some people.
I redid the whole guide to check for errors and I found non.
Click to expand...
Click to collapse
"Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3."
how you run the update if cannot reboot, i need to be clear the step before can proceed. thanks.
Euclid's Brother said:
Always keep a backup of the following partitions for any firmware version you want to restore to. (ie. i have these for my original 1.104.02 and 1.141.07).
mmcblk0p1 (recovery)
mmcblk0p2 (boot)
mmcblk0p3 (system)
mmcblk0p5 (misc)
mmcblk0p6 (flexrom)
mmcblk0p7 (??)
If bricked, use any of the base update.zips to get back to a bootable tablet.
Then to restore to your given version:
1. Push all your backup files to your device with the DD command EXCEPT mmcblk0p3 (system).
2. Run itsmagic to update the checksums
3. Push the mmcblk0p3 file last (this will cause the tab to lock up).
4. Reboot
If running the dd command from adb shell, you'll see when it finishes the push. If running it from a terminal emulator, give step 3 at least 5 full minutes to complete before rebooting.
I did this last night with my original 1.104.02 backup and then took the OTA to 1.141.07. worked perfectly.
Edit: I'm gonna update my rom flasher app to do this whole procedure
Click to expand...
Click to collapse
Thanks for sharing. I will make a backup just in case.
mrlonely78 said:
"Then I ran the update and it was successful. Tadaa stock A500 with firmware Acer_A500_1.141.01_EMEA_GEN3."
how you run the update if cannot reboot, i need to be clear the step before can proceed. thanks.
Click to expand...
Click to collapse
First you flash the boot.img but do not reboot (if you manually reboot you will get the LNX checksum error). Then check for the update. Once the update is downloaded it will automatically reboot to install the update. This is no problem as it will first check if there is a proper boot.img and then flash the update (it goes into recovery instead of just booting).
>I have a Nexus 7
>Rooted, with CWM recovery
>Paranoid Andoid installed, works fine
>Decide to try alternative Rom's
>Download and install CM
>Bootloops
>Flash to stock and unroot using Nexus Root Toolkit
>Root again, install TeamWin recovery
>Try and flash CM again
>Bootloops
>Flash to stock again, install TeamWin recovery
>Try Smooth Rom
>Starts fine
>Reboot
>Bootloops
>Flash to stock again, install CWM recovery
>Decide to flash Paranoid Android as I wish I hadn't changed anything
>Flash PA
>Bootloops
>Flash to stock again, install CWM recovery
>Flash PA
>Boots fine, all going well
>Reboot
>Bootloops
So basically, that is the situation, and I can't figure out why it is happening. I have flashed Rom's before with no problem, but ever since I tried CM, it's all funked up, so yeah, any help at all would be greatly appreciated
The one thing I don't see in your set of trials is whether or not the complete stock ROM (whether rooted or not) bootloops on it's 2nd boot the way all the other combinations seem to.
Did you do that, or did you presume that we would also presume that Stock always boots in your experiments (at least twice!)?
BTW, you don't need to follow then entire Stock installation script if your tablet bootloader (& radio in the tilapia case) are up to date. That will save you extra steps and the need to re-flash the recovery image afterwards. All that should be needed are:
Code:
fastboot erase system
fastboot format system
fastboot flash system system.img
[b][color=red]fastboot format userdata[/color][/b] *
* obviously this nukes EVERYTHING in userdata, so a complete backup of anything you want saved from /sdcard is needed beforehand. You could replace this step with just a "factory reset" procedure in the custom recovery if you want to avoid the hassle and are convinced that the userdata partition is not causing problems (it's filesystem looks healthy & is appropriately-sized for the variant of the device you have).
Note that this proposal assumes that "flash userdata userdata.img" from the factory install instructions is superfluous. (Unless perhaps there is some sort of "oneshot" logic in there that alters /system on the first boot but not thereafter) - otherwise, how could you erase all of /data and get a "factory reset" some time later? But I think the filesystem sent by this command actually has no files in it, so... same conclusion... superfluous).
bftb0 said:
The one thing I don't see in your set of trials is whether or not the complete stock ROM (whether rooted or not) bootloops on it's 2nd boot the way all the other combinations seem to.
Did you do that, or did you presume that we would also presume that Stock always boots in your experiments (at least twice!)?
BTW, you don't need to follow then entire Stock installation script if your tablet bootloader (& radio in the tilapia case) are up to date. That will save you extra steps and the need to re-flash the recovery image afterwards. All that should be needed are:
Code:
fastboot erase system
fastboot format system
fastboot flash system system.img
[b][color=red]fastboot format userdata[/color][/b] *
* obviously this nukes EVERYTHING in userdata, so a complete backup of anything you want saved from /sdcard is needed beforehand. You could replace this step with just a "factory reset" procedure in the custom recovery if you want to avoid the hassle and are convinced that the userdata partition is not causing problems (it's filesystem looks healthy & is appropriately-sized for the variant of the device you have).
Note that this proposal assumes that "flash userdata userdata.img" from the factory install instructions is superfluous. (Unless perhaps there is some sort of "oneshot" logic in there that alters /system on the first boot but not thereafter) - otherwise, how could you erase all of /data and get a "factory reset" some time later? But I think the filesystem sent by this command actually has no files in it, so... same conclusion... superfluous).
Click to expand...
Click to collapse
I kept flashing to stock so I know where I'm at each time, I'm pretty knew to all this so I don't want to confuse myself.
I'm just about to flash stock and see if that bootloops now.
I don't understand how any files could remain on there after a factory reset though, thats why can't grasp why it's bootlooping every time
okay, so I have flashed stock, and it DOES NOT bootloop
miketino said:
I don't understand how any files could remain on there after a factory reset though, thats why can't grasp why it's bootlooping every time
Click to expand...
Click to collapse
It does seem unusual. OTOH, a "factory reset" in the custom recovery never re-builds the /data ext4 filesystem - so I suppose if the filesystem itself was bolluxed up, that would persist across a (custom recovery) "factory reset".
The thing is, the sequence you describe involves re-doing things with the factory install, and either
Code:
fastboot erase userdata
fastboot format userdata
fastboot flash userdata userdata.img
or
Code:
fastboot format userdata
fastboot flash userdata userdata.img
seems like they certainly should be rebuilding the ext4 filesystem in the userdata (/data) partition.
I mentioned something like this in a couple other posts, but I have experienced odd troubles with the /system partition where I could occasionally create an empty (and new) filesystem using the "Wipe system" option in TWRP, and immediately after that, if I manually checked it's status using (TWRP's) "e2fsck" program, it would report massive problems
Code:
adb shell e2fsck -f -n /dev/block/mmcblk0p<PARTNUM>
which doesn't make any sense at all - a brand-new & empty filesystem should be perfectly clean!
Anyway, something you might want to try is to run the above e2fsck program as a sanity check just after you flash a ROM and just before you are getting ready to reboot into the normal OS. The "-n" option to "e2fsck" prevents it from altering anything, so this is a nondestructive (no touch/read only) test. (I've never tried to actually use e2fsck for a repair - I just start over either with fastboot or the recovery filesystem formatting).
Note that "e2fsck" needs the partitions to be unmounted, so e.g. in TWRP you would:
Code:
adb shell umount /system
adb shell e2fsck -f -n /dev/block/mmcblk0?? (grouper system = p3)
adb shell umount /sdcard
adb shell umount /data
adb shell e2fsck -f -n /dev/block/mmcblk0?? (grouper data = p9)
If they don't come up clean, obviously you need to do something. Because "mount /sdcard" seems to fail when performed manually in TWRP, I just re-boot the recovery from within TWRP to do other tasks, should that be necessary.
Hope this helps.
miketino said:
okay, so I have flashed stock, and it DOES NOT bootloop
Click to expand...
Click to collapse
I wonder if this means something screwy is being caused by the ROM flashing in the recovery. Maybe try the above suggestions just as a sanity check?
BTW, what recovery and version are you using?
Its Clockwork Mod Recovery, version 6.0.2.3
miketino said:
Its Clockwork Mod Recovery, version 6.0.2.3
Click to expand...
Click to collapse
fwiw, I just booted the touch version of CWM 6.0.2.3
Code:
fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img
to make sure that it had e2fsck present in it's /sbin. It does.
e.g. my (32 GB grouper) device:
Code:
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/UDA
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-name/UDA: 24564/1875968 files (0.4% non-contiguous), 2641387/7503608 blocks
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/APP
e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/APP
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-name/APP: 1100/41664 files (1.0% non-contig
uous), 121097/166400 blocks
also, "tune2fs" seems to be present too. You can get a listing of the filesystem creation options using the -l option, as in
Code:
tune2fs -l /dev/block/platform/sdhci-tegra.3/by-name/APP
although I will say I've compared this output before, searching for difference(s) between the way that fastboot formats things and the custom recovery does things and didn't see anything compelling.
[ TWRP might be different than CWM though - it has a utility called "make_ext4fs", whereas I think CWM uses "mke2fs" for fs creation. ]
HTH
Hi,
i tried to update my phone via the integrated updater. It did not start the update and now fails booting into android. it boots every time into twrp.
i tried several possible solutions:
reflash other version
reflash the latest version
flashed fulmics
factory wipe
reflashed twrp
tried to
inshadesofgrey said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
but failed
now i am out of knowledge...
has anyone an idea?
Regards!
Christian
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
one_ctrl said:
did you tried to restore everything to stock with a kdz file? you can find it on google and you can flash it putting the device in download mode and using lgUP / uppercut to do so.. if you need help you can send me a PM
Click to expand...
Click to collapse
Is there any better solution for this problem?
I solved it once with a full reinstall an this uppercut tool.
On reddit for other phones there is the solution to boot to bootloader and do
Code:
fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.001s
But this does not work.
It seems my phone boots to twrp because the lineage os updater app set s.th. to automatically boot to twrp. How can we remove this auto-boot to twrp flag?
Sorry for bringing up this again. I did an OTA update on lineageos on my lg g6. The phone booted correctly in twrp, I installed the update but now the phone boots directly to twrp without any way to let it boot the os. How did you resolve this?
Thanks
Only solution back to stock & after install LOS and wait until bug is fixed.
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Someone else has had this problem @gnackwatschn, you can find a way to fix the boot loop here https://forum.xda-developers.com/lg-g6/help/twrp-bootloop-lineageos-ota-update-t3746014/post75488796#post75488796
WARNING [brick]
eng3 said:
I use a lg g pad x 8.0 and ran into the same issue.
fastboot continue would not work.
the dd commands did not work either
I think the "msm_sdcc.1" is device specific.
In recovery, I used the file manager to look in /dev/block/platform and notice that "msm_sdcc.1" did not exist but there was one folder in there. I went in there and there was another and kept going til I found the "by-name" folder
then I ran the dd command replacing "msm_sdcc.1" with what was on my device.
I did it for "fota" and "misc" and then my device booted
Click to expand...
Click to collapse
WARNING! I ran into the same problem on the LG G6 with the nightly update dated Nov 1, 2018. Did what you did, but wrote down the command.
After navigating to the TWRP > Advanced > Terminal, first do
Code:
ls /dev/block/platform
Mine had one entrie: soc, which had two entries: 624000.ufshc and 74a4900.sdhci
only 624000.ufshc had a by-name directory containing fota and misc, so my commands ended up being:
Code:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/fota
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
The commands run, saying:
Code:
dd: writing '/dev/block/platform/soc/624000.ufshc/by-name/fota': No space left on device
8193+0 records in
8193+0 records out
4194304 bytes (4.0MB) copied), 2.783000 seconds, 11.5MBs
and similar for misc.
Reboot to system gives a warning, Your device has failed a routine safety check and will not boot.
Now I'm stuck.... guess its time to start another thread.
First of all, thanks for all the people here provide very useful message.
Acutally I encouter a lot of similar issues across the posts.
Please refer to the posts here:
Unbrick guide Z00l Ze550kl
Need QCN file for ZE550KL/Z00L (2GB Ram) Please.
[Solved]Stuck on logo when booting into custom ROM( Zenfone 2 laser ZE550KL Z00LD)
My model is ZE550KL 2GB/16GB version.
What need to be prepared (please look around from google)
1. CSCImage for recovery
2. QPST 2.7
3. Workable QCN, if you have no backup please make one from the other post. (you will need imei coverter and HxD)
4. Retail image WW_ZE550KL_1.17.40.1234-rel-user-20160304185904-secured-releaseAFT_QC
5. Offical latest image
6. TWRP
7. Minitool Partition Manager (I tried diskpart but not working, so please use this one)
8. Qualcomm Driver
Here are the procedures for reference (I do this for over 10 times and 3 nights)
Please make sure you have working QCN...otherwise you cannot recover the calling feature.
1. Erase aboot
fastboot_8916 erase aboot
use above command to erase the partition
you can unplug the battery and cable and replug them.
or simply use fastboot reboot command.
Result: Device enter into 9006 mode
2. Open Minitool Partition manager
Right click and Delete all partition.
Create one single partition using ext4 format
Once done, remove the battery and cable, replug them.
Result: Device enter into 9008 mode
3. If you installed QPST, you should have a program called QFIL
Please use it and extract the firmware from CSCImage, it should have all the items except emmc MBN, just copy it from the root folder.
If you do this correct (follow other post for more detail)
Replug the device will give you a fastboot screen
Result: Device with workable fastboot
4. Now you have a clean bootloader, but no other thing
Go to CSCImage and click flashall
Once it is done, all the partitions will be ok (sometimes I got /factory not mount, let's fix this later)
Result: you will have a engineering OS and bootloader unlocked, diag mode natively enabled.
5. Open Software Downloader from QPST, and recover the QCN, it will reboot the phone.
If you are not doing this correctly (and many issues here), you will get bootloop.
And you have to start over again.
My suggestion is do not touch any of the bootloader setting. (so do not try to use unofficial bootloader unlock guide)
Even you give a command like "fastboot oem adb_enable" it will cause a bootloop and have to start over.
So my suggestion is not touch any bootloader setting
Result: The phone calling and data should be recovered. You can test by making some call.
6. If you want to keep your bootloader unlocked, the retail image flashall you can search there is a "oem lock"
change to unlock and run it in fastboot mode.
Result: You will have a bootloader unlocked phone, with WW firmware.
You can start from here to do TWRP.
to fix /factory partition. you can install busybox and in adb shell, use mkfs.vfat for the partition.
What is CSCImage, I tried your method but got stuck on missing partitions. (Boot, Recovery, System, etc..)
christian.arvin said:
What is CSCImage, I tried your method but got stuck on missing partitions. (Boot, Recovery, System, etc..)
Click to expand...
Click to collapse
This means you didn't unlock your bootloader.
bootloader needs to be unlocked to flash the partition file, and then the partition will be recovered without data.
My bootloader was unlock.
I digged deeper in your method. And this is what i understand and let it be an information for those who will try.
Back up all partition before you delete all partitions. (Your serial and other sensitive data are stored in some of this partition)
Your method only restore 5 partition table that is inside the main0 gpt mbn.
Note: the whole partition table is listed in the both0 gpt mbn.
In my stupidity I renamed the both0 gpt to main0 gpt thinking that it would work. Instead I run into an unstoppable bootloader bootloop.
In an ending note my ZF2 Laser's only hope is a full eMMC reflash that requires external methods. Or let the official professionals handle it.
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma,
* thermonuclear war, or your mom getting upset with you for being on the computer all day
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
THIS GUIDE APPLIES TO JETER AND ALJETER DEVICES
FOR ALJETER DEVICE OWNERS ONLY.
there are ALOT of different variants of the aljeter so please before beginning this root method go to settings, system, about phone. look for either sw version or software channel verison and either remember what it says or write it down. me or anyone else will need this to help troubleshoot which aljeter variant you have. this will also be important to know incase you mess up and need to reflash stock firmware which those instructions are at the bottom of this guide.
The following devices have been confirmed to work on devices with Android 8 (Oreo)
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile/ Virgin Mobile
XT1922-9 Motorola Retail
The following devices have been confirmed to work with Android 9 (pie)
XT1922-7 (Jeter) boost Mobile/ Virgin Mobile.
XT1922-3 (Aljeter)
XT1922-5 (Aljeter retbr)
Please make backups using TWRP IN CASE OF FAILURE.
Original stock firmware FOR JETER can be found here. https://mirrors.lolinet.com/firmware/moto/jeter/official/ and here FOR ALJETER https://mirrors.lolinet.com/firmware/moto/aljeter/official/
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisite:
Unlocked bootloader.
FOR LINUX USERS. If you're using a linux distro then congrats this is all you should have to run. open command prompt and run this. "sudo apt-get install adb" without quotation marks. then follow Motorolas bootloader guide in provided link. continue to step 1 after.
FOR WINDOWS USERS.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio...platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Minimal adb/fastboot v1.4.3 installer can be found here. https://androidfilehost.com/?fid=746010030569952951
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
DECRYPTION AND BACKUP.
NOTICE
IF YOU YOU ARE USING THE 32GB MODEL OR THE 16GB MODEL AND ARE ON ANDROID 9 (PIE) PLEASE USE THE ANDROID 9 (PIE) MODEL TWRP. USERS WITH THE 16GB MODEL AND THE 32GB MODEL ON ANDROID 8 (OREO) WILL STILL NEED TO USE SEPERATE TWRPS
MAKE SURE TO SWIPE RIGHT IN TWRP TO ALLOW SYSTEM MODIFICATIONS.
Step 1.) Download and extract twrp image to the ADB/Fastboot folder on your computer.
FOR ANDROID 8 (OREO)
16gb model twrp: https://www.androidfilehost.com/?fid=6006931924117921836
32gb model twrp: https://www.androidfilehost.com/?fid=6006931924117927211
FOR ANDROID 9 (PIE)
https://www.androidfilehost.com/?fid=6006931924117921849
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding the power button and volume down button at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel)
Step 5.) time to backup your stock recovery and stock boot. use these commands one at a time.
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you need to revert to stock later.
Step 6.) time to decrypt which will also format your data so make sure to make a backup. while still booted in twrp touch the "wipe" button then touch "format data", type yes and after its all done reboot to bootloader use this command.
Code:
adb reboot bootloader
CONGRATS! if you read this correctly and or didnt skim then you have successfully decrypted your device and backed up your stock recovery and stock boot.img. proceed below for root process.
ROOT PROCESS.
Step 1.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery twrp.img
Step 2.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. swipe right to allow modifications. IT SHOULD NOT ASK YOU FOR A PASSWORD THIS TIME IF IT DOES YOU MESSED UP DURING THE DECRYPT PROCESS
Step 3.) Follow this link to the creators site to download the disabler zip. https://zackptg5.com/android.php#disverfe download it to your ADB/Fastboot folder.
Step 4.) Download the Magisk Beta v20.0 and or the latest zip file from https://github.com/topjohnwu/Magisk/releases to your ADB/Fastboot folder. (I personally use beta so I use beta in this guide but you don't have to)
Step 5.) Run the following command to push the dm_verity force encrypt disabler and magisk zip to your device
Code:
adb push Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip /tmp
adb push Magisk-v20.0.zip /tmp
This will push the Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip and Magisk-v20.0.zip to your /tmp folder
Step 6.) Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 7.) Flash Magisk-v20.0.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 8.) Reboot your device
Step 9.) Just wait for the device to boot up. might take a bit and it might seem its in a bootloop but if you followed this guide exactly as is just wait it out it took about 5-10 minutes before i got to the "lets get started" screen after updating to pie (android 9)
Step 10.) Verify Magisk Manager is installed and the root functionality works. sometimes the manager apk wont be installed so download the magisk manager apk from the provide links. click advanced to see if the boxes are unchecked. (2022 edit) If you see magisk app and magisk needs updated you can do it but I can't confirm if it's safe and what works and doesnt after
CONGRATS! IF YOU DIDNT SKIM MY GUIDE YOU SHOULD HAVE A SUCCESSFULLY ROOTED AND ENCRYPTION DISABLED DEVICE, HAVE FUN.
IF YOU MESSED UP, DIDNT PUT A COMMAND IN CORRECTLY, SKIMMED, OR ARE INA GENUINE BOOTLOOP/BRICK THIS SECTION IS FOR YOU
Step 1.) DOWNLOAD STOCK FIRMWARE HERE FOR JETER AND CERTAIN ALJETER DEVICES (from what i can tell usa variant aljeter devices are consided jeter) https://mirrors.lolinet.com/firmware/moto/jeter/official/ IF YOU REMEMBER OR WROTE DOWN YOUR SW CHANNEL VERSION THEN DOWNLOAD STOCK FIRMWARE FOR BASICALLY EVERY OTHER ALJETER DEVICE HERE. https://mirrors.lolinet.com/firmware/moto/aljeter/official/ UNZIP STOCK FIRMWARE TO YOUR ADB/FASTBOOT FOLDER TO FLASH IT. TO REVERT BACK TO STOCK YOU HAVE TO REFLASH STOCK FIRMWARE FROM THE BOOTLOADER if your device is bootlooped or bricked or not working right you have to reflash the stock firmware your device came with. PLEASE INPUT THESE COMMANDS ONE AT A TIME DO NOT DO THEM ALL AT ONCE. I KNOW ITS A HASSLE BUT IT GUARANTEES A SUCCESSFUL REFLASH. I CANNOT EMPHASIZE THIS ENOUGH
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastbot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
Credits: @kwiksi1ver for making the original guide. @topjohnwu for magisk. @shimp208 for minimal adb/fastboot. @Spaceminer for providing the new twrps for 16gb and 32 gb devices, and @Zackptg5 for making the Universal DM-Verity, ForceEncrypt, Disk Quota Disablers.
QUICK NOTE/EDIT: SINCE I DO NOT OWN THIS DEVICE ANYMORE I CANNOT CONFIRM IT BUT YOU SHOULD BE ABLE TO UPDATE TO THE LATEST MAGISK 24.3 FROM THE MAGISK APP AFTER YOU INSTALL V20, AGAIN I AM NOT ABLE CONFIRM IF IT WORKS, CAUSES BOOTLOOPS, OR ANYTHING SO KEEP THAT IN MIND, but hopefully it does work for yall I've also updated the ADB commands for the disabler to reflect its latest version and I've updated the magisk link to topjohnwus GitHub as that's where all updates happen/ go first
RESERVED
In order to update the confirmed working models for this guide, if anyone that has this device with a unlocked bootloader and does root and decrypt successfully using my guide and it's not on the confirmed device list. PLEASE JUST PM ME and let me know. Please include device model number, name, and if on aljeter your software channel version.( For example. Xt1922-5 aljeter, sw channel: retbr)
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
blowingoff said:
following the instructions exactly gets me into a really weird bootloop where my phone boots twrp, shows some log and then reboots and does the same thing over and over
Click to expand...
Click to collapse
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Kuntitled said:
I have the same issue. I used the recovery steps to go back to stock but every time i re-attempt to root/install twrp the bootloop comes back:
Also, it's failing to mount /data after Resurrection Remix wouldn't boot and it keeps giving me the unable to mount /data (invalid argument) problem. I need help badly. Can you help? Is it the TWRP's fault?
Click to expand...
Click to collapse
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Spaceminer said:
Are you encrypted? Because twrp will do that if you are. You have to use the wipe > format > type "yes" to continue method to remove encryption. Then reboot from twrp, directly back into twrp. Then it can mount /data properly, at which point you need to flash the encryption disabler. If you don't disable encryption you'll keep running into the same problem. You only have to do that once. After that you can use the regular wipe option. If you ever flash the stock vendor.img you'll need to do it again.
Also, please make sure twrp has been flashed to recovery. I don't think it'll work if you just boot through fastboot. If you followed all these instructions and magisk still refuses to install, or gives you a bootloop, then it's a ROM problem and not TWRP. Should that happen, let me know and I'll flash Resurrection remix and see if I can figure out what's going on. I've had ROMs refuse to be rooted before. Descendant ROM had this problem on some older builds.
Click to expand...
Click to collapse
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
blowingoff said:
as for me: I followed the instructions which tell us to only boot twrp during the data format and only then actually flash twrp.
but my problem is no magisk, as I always root my phone whenever i revert back to stock. it's just that decryption is not working on my xt1922-5
Click to expand...
Click to collapse
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes" to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Spaceminer said:
Do it like this.
1. fastboot flash recovery twrp.img
2. Use the volume keys while still in fastboot to select "recovery" then hit the power button.
3. Hit cancel at the decryption screen when twrp boots up.
4. In TWRP select wipe > format > type "yes"no to continue. Do not reboot the phone yet.
5. In twrp select reboot > recovery.
6. Once twrp boots up again, select mount and check the boxes for /data, /system, /vendor, /cache.
7. Now flash the universal encryption disabler.
8. Let it boot once, then go back into recovery and flash Magisk.
This should solve your problem.
Click to expand...
Click to collapse
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Kuntitled said:
My issue is as follows:
I had rooted my g6play months ago, back when pie came out on Ota for it. The guide I followed didn't have me disable encryption, which at the time wasn't a real big deal, with my only loss being the inability to do nandroid backups. But fast forward to now, when Resurrection Remix GSI came out, I was immediately interested as I think that rom could be a great experience.
So I decided to come here in this guide because I might as well disable encryption, right? So I flashed the new twrp and did get it to wipe and disable the encryption (in the option that has you type in yes) and proceeded to flash RR, it booted to the boot anima9and there it stayed for a good 30 minutes before I decided to try the older GSI image, maybe that one would work.
But nope, I immediately got the unable to mount /data bootloop and successfully flashed my stock rom and tried again, this time flashing the new twrp right off the bat. No avail. Now everytime i go into a freshly flashed twrp, i get no password prompt, and when i try to access the internal storage, it comes up as 0mb. Even my Linux complains that it couldn't mount my Internal storage as only the SD card shows up (weirdly enough I was able to successfully push dm verity and magisk to /temp no problem but they fail upon flashing)
Edit: gotta mention that after the first time I did the pull adb command to get the backups, the command refuses to work anymore. And also that I still have an old twrp backup stored (did that today before trying this)
Click to expand...
Click to collapse
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
Click to expand...
Click to collapse
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
blowingoff said:
well i also couldnt make the backups, fastboot just tells me the file doesnt exist. and for the internal storage: while you are encrypted, that is how it works.
---------- Post added at 11:58 AM ---------- Previous post was at 11:42 AM ----------
Edit: i can not mount data, twrp says argument invalid. followed your instructions anyway and my phone still gets me to a bootloop to a "running OpenRecoveryScript" again.
Click to expand...
Click to collapse
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Starkiller2 said:
Go into the wipe menu, advanced wipe, check data and hit change file system. change data back to f2fs. When you guys format and don't immediately reboot straight to recovery, data sets to Auto and freaks out
Click to expand...
Click to collapse
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Kuntitled said:
the multiple times i checked, the file system was always f2fs, but sometimes ext4
and also: Do you mean we should do that after we try to format with the format data (typing yes) option? If so, it doesn't work as the internal storage won't mount. Won't even show up on my computer
Click to expand...
Click to collapse
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Kuntitled said:
Alright, let me work through this.
I'm currently on a stock firmware and it's working fine.
Right now i have to:
1. boot into recovery twrp
2. change the filesystem of data
3. flash recovery and boot into it
4. format data(yes option)
5.check and change the file system again
6.reboot straight back into twrp recovery from recovery
7.flash dm verity zip
8.flash magisk
9.boot
Is this correct? and as for attempting to install a GSI image again, should i attempt to flash it before the verity zip and magisk? (i'll also be flashing micro gapps) or do i let it boot into system once and then i do it? (by wiping data/dalvik/cache/system)
Click to expand...
Click to collapse
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Starkiller2 said:
Let's simplify. If everything is working,
go to fastboot
Flash recovery (boot doesn't seem to be working here)
Fastboot flash recovery twrp image
Select recovery, when the decrypt menu comes up, hit cancel
Wipe menu,
Swipe to factory reset
Go back to wipe
format data, yes,
Reboot recovery
Flash disabler
Flash magisk
And yes. Boot system then GSI flash, then factory reset before magisk
---------- Post added at 01:44 PM ---------- Previous post was at 01:36 PM ----------
We'll get it figured out
Click to expand...
Click to collapse
Do i check the file system for data at any point?
Kuntitled said:
Do i check the file system for data at any point?
Click to expand...
Click to collapse
Only if it won't mount
Starkiller2 said:
Only if it won't mount
Click to expand...
Click to collapse
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Kuntitled said:
does it matter where i flash disabler, magisk and GSI from? I've been doing it from my SD card
Click to expand...
Click to collapse
No that's fine
Starkiller2 said:
If you change the file system, it'll format, even if it says it won't mount. Changing the file system will force it to format. Even if it says f2fs, hit change and select f2fs anyway.
If it doesn't, format from fastboot, boot system once then go to recovery
Click to expand...
Click to collapse
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues
Click to expand...
Click to collapse
But data won't work as ext4, hence the boot loop
Try going to fastboot and typing
Fastboot -w
Then boot to recovery
---------- Post added at 02:10 PM ---------- Previous post was at 02:07 PM ----------
Kuntitled said:
Data is set to emmc file system, won't mount and filesystem won't change at all and won't format
Edit: only happens when i try to change it to f2fs, changed it to ext4 with no issues and it mounts sucessfully with ext4 but won't let me format data
I get the mkfs.f2fs -t 0 /dev/block/mmcblk0p56 error 1, unable to mount data whenever i try to change to f2fs. Has my previous failed attempt at installing GSI **** with my filesys?
Click to expand...
Click to collapse
I honestly don't see how, especially if stock is working