Watch My Video
[How-To] Revert from OtterX Project to Stock Kindle Fire Partitions
and
Flashing TWRP in FFF bootloader For Kindle Fire 1
Recommend using update-kindle-prerooted.6.3.3.v1.zip rather than update-kindle-6.3.3_D01E_4112920.bin
Install kindle Fire DriversDownload Kindle Fire Utility extract file from zip, run install.drivers.bat
Download Files Links in 2nd post
TWRP 2.2.2.1: for Stock Rom, custom Gindgerbread(CM7), ICS(CM9), and Jellybean (CM10) roms
TWRP 2.2.2.1 - 2.6.1.0: ICS(CM9), and Jellybean (CM10) roms
TWRP 2.6.3.0 or better: For KitKat(CM11) Roms
Bootloader: Otter X Bootloader 2.05 seems to work fine with Otter/Blaze TWRP 2.7.x.x, Doesn't work well with TWRP 2.2.2.1, use FFF 1.4a/1.5
ADB Files
Rom: Stock or Custom/GApps
Change Partitions from Otter X[ to Amazon
Reboot Kindle Fire, When you see bootloader, press power button once to open boot menu, select Advanced
Open the bootloader menu by pressing [POWER]
Use 1-2 SHORT presses of [POWER] to highlight "ADVANCED -->"
Use a LONG press of [POWER] to select ADVANCED MENU
Use 5 SHORT presses of [POWER] to highlight "PARTITION MODE: OTTERX" (if this is Amazon you can skip step 3)
LONG press [POWER] to open "PARTITION MODE MENU"
Use 4 SHORT presses of [POWER] to highlight "[CONFIRM] SET MODE: Amazon"
WARNING THIS WILL ERASE THE CONTENTS OF YOUR "SDCARD" and USERDATA!!!! Before doing this step you should have backed up ANYTHING IMPORTANT and pulled it off of your Kindle!
LONG press will select this option and your system, cache, userdata will be changed to the Amazon layout (and ERASED)
Now use short [POWER] presses to navigate BACK and then to "RECOVERY"
STEP 4: WIPE PARTITIONS IN RECOVERY
[Main Menu] Wipe -> Advanced -> check "Cache" and Swipe
[Main Menu] Reboot -> Recovery (wait for it to come back into TWRP)
[Main Menu] Wipe -> "Format Data", type "yes" and hit enter
[Main Menu] Wipe -> Advanced -> check "System" and Swipe
Custom Bootloader and Recovery for Amazon Partitions
Two options Push/ Install in TWRP, or Flash in Bootloader
a. Push/Install
Code:
adb push fff-u-boot_v1.4a.zip /sdcard
Code:
adb pushzip-openrecovery-twrp-2.7.1.0-otter.zip /sdcard
and select install fff-u-boot_v1.4a.zip, when install is finished reboot, select recovery in bootmenu
install zip-openrecovery-twrp-2.7.1.0-otter.zip, when install is finished reboot, select recovery in bootmenu
then install zip-otter-twrp-2.2.2.1-blaze.zip if you are installing CM7 or stock rom
if you can't enter recovery after a reboot, you will need to flash recovery in Bootloader/Fastboot Mode
b. Flash in Bootloader
power off kindle, open command prompt on PC, enter a command, press enter, and Power on Kindle
for Bootloader
Code:
fastboot flash bootloader fff-u-boot_v1.5.bin
For Recovery
Code:
fastboot flash recovery openrecovery-twrp-2.2.2.1-blaze.img
For Reboot
Code:
fastboot reboot
if you get a
device needs formatted
Click to expand...
Click to collapse
or unable to select SD Card in mount options see
Mounting SD Card and Formating SD Card
Files - Links
Verify md5 checksum for all Files see Using Hash Checksums
.
Recovery
Flash in Bootloader:openrecovery-twrp-2.2.2.1-blaze.img
Install in TWRP: Flashable TWRP zips XDA--
Bootloader
Flash in Bootloader:fff-u-boot_v1.4a.bin
Install in TWRP: fff-u-boot_v1.4a.zip
Stock Rom
update-kindle-6.3.3_D01E_4112920.bin
204 MB (214,586,505 bytes) MD5: 89A4DEF015289F2291BF502E09A70554
Official--DevHost--Mega--XDA
Prerooted 6.3.3 stock--update-kindle-prerooted.6.3.3.v1.zip
ADB and Fastboot
ADB-Fastboot.zip--XDA--
Troubleshooting and Links
I recommend using my update-kindle-prerooted.6.3.3.v1.zip first Even if you want pure stock
The Full stock will flash the stock Bootloader, and stock recovery, even if the partitions are not right.
If the Pre-rooted zip boots fine, then you can try the update-kindle-6.3.3_D01E_4112920.zip
if the Pre-root does not boot, you still have TWRP/FFF, and it is easier to fix.
Links
Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
Kindle Fire Flashable Recoveries/FFF TWRP/COTR/CWM[2014]
Stock Amazon Partitions
When Amazon partitions are selected.
Verify that Partition Sizes and File Systems are correct
System: Size: 503 mb | File System: ext4 | Screenshot
Data: Size: 5119 MB | File System: vfat | screenshot
Cache: Size:251 MB | File System: ext4 | Screenshot
Note: Other File system may work, depends on the rom installed.
Required: an OtterX Twrp like otterx-twrp-2.7.1.0-recovery
In TWRP Select Wipe> Advanced Wipe>
Check Data Partition Box>Repair or Change File System> compared details Circled in Red
repeat with Cache and System Partitions
if Size is different try repair option, if File System is different use change File System.
Note: After using Repair Option or Changing File System, reboot and verify that Partitions are correct
If those option do not fix the partitions try change to OtterX Partitions with OtterX 2.04 or 2.05 Bootloader.
Wipe>Advanced Wipe>check Cache>reboot
Wipe>Advanced Wipe>check Cache, System, Data>Swipe to Wipe>reboot
In bootloader> select Amazon partitions
in Twrp>Wipe>Advanced>check Cache>swipe to Wipe>Reboot
Wipe>Advanced>Check Cache, System, Data>Swipe to Wipe>reboot
if you get any errors on any steps, go back a step or 2 and try again.
Note: Do not worry about Not rooted or no system install errors, at this time, just select an option and continue
Once Partitions are correct, retry installing the Twrp required for the Rom you want, Reboot, install rom.
In TWRP 2.7.1.0, I am unable to flash TWRP 2.2.2.1 or TWRP 2.6.1 ... Error message is: "This package is for blaze/otter devices; this is a "otterx".
Is there a workaround?
Mounting SD Card in Twrp and Formating SD Card from PC
In Twrp
Select Mount
Check SD Card box
Select Mount USB Storage
When you are done Eject SD Card in Windows.
Then select Unmount in Twrp
If you are unable to select SD Card in Mount options,
check System box,
Select Mount USB Storage
Formating SD Card from PC
Your computer will probably respond that the volume/device needs formatted before using it. This will erase everything left on the sdcard, as will anything else you attempt in this thread.
* Choose a quick format (if possible) and format it as "fat32", block size "4096".
If you don't get the "volume/device needs formatted before using it" warning
you can format by, selecting SD Card in Computer Folder>right click>select Format...>
Choose a quick format (if possible) and format it as "fat32", block size "4096".
also TWRP 2.2.2.1 does not work with oterx 2.05 bootloader, so you need to flash FFF 1.4 or 1.5 first.
sd_shadow said:
also TWRP 2.2.2.1 does not work with oterx 2.05 bootloader, so you need to flash FFF 1.4 or 1.5 first.
Click to expand...
Click to collapse
I was already on v1.04a bootloader so flashing TWRP 2.8 turned out not to work as it could not mount storage. So I went back to OtterX and will try again tomorrow. Thanks for your help; I will post here my results.
ttakacs said:
I was already on v1.04a bootloader so flashing TWRP 2.8 turned out not to work as it could not mount storage. So I went back to OtterX and will try again tomorrow. Thanks for your help; I will post here my results.
Click to expand...
Click to collapse
you used zip-openrecovery-twrp-2.8.0.1-blaze.zip ?
sd_shadow said:
you used zip-openrecovery-twrp-2.8.0.1-blaze.zip ?
Click to expand...
Click to collapse
I did. I was not able to flash anything in TWRP 2.8.0.1. To reinstall OtterX, I used fastboot to install FFF2.05 and TWRP 2.7.1.
Do you recommend I flash 2.8.0.1 before attempting to revert to Amazon partition mode? I don't want to revert to stock but want to go back to CM10.2, which gives me significantly better battery life.
ttakacs said:
I did. I was not able to flash anything in TWRP 2.8.0.1. To reinstall OtterX, I used fastboot to install FFF2.05 and TWRP 2.7.1.
Do you recommend I flash 2.8.0.1 before attempting to revert to Amazon partition mode? I don't want to revert to stock but want to go back to CM10.2, which gives me significantly better battery life.
Click to expand...
Click to collapse
Just flash 2.2.2.1 IMG in bootloader
Sent from my DROIDX using Tapatalk
Did you watch my Video?
sd_shadow said:
Just flash 2.2.2.1 IMG in bootloader
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
I'm stuck.
Here are the steps I took:
1. Rebooted to v2.05 bootloader and changed the partition mode from OtterX to Amazon.
2. Powered the Kindle off.
3. In fastboot, flashed the v1.5 bootloader and 2.2.2.1 TWRP.
4. Rebooted into TWRP 2.2.2.1 recovery.
5. Wipe > Cache = Success. Reboot to recovery.
6. Wipe > Factory Reset (there is no "Format Data" menu item in 2.2.2.1) = Success.
7. Wipe > System = Success.
8. Pushed CM10.2 and JB gapps to the Kindle's sdcard folder.
9. Attempted to flash.
"E:failed to mount /sdcard
"E:Can't mount /sdcard/CM-10.2.zip...."
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
sd_shadow said:
Did you watch my Video?
Click to expand...
Click to collapse
I will have, two minutes from now.
ttakacs said:
I'm stuck.
Here are the steps I took:
1. Rebooted to v2.05 bootloader and changed the partition mode from OtterX to Amazon.
2. Powered the Kindle off.
3. In fastboot, flashed the v1.5 bootloader and 2.2.2.1 TWRP.
4. Rebooted into TWRP 2.2.2.1 recovery.
5. Wipe > Cache = Success. Reboot to recovery.
6. Wipe > Factory Reset (there is no "Format Data" menu item in 2.2.2.1) = Success.
7. Wipe > System = Success.
8. Pushed CM10.2 and JB gapps to the Kindle's sdcard folder.
9. Attempted to flash.
"E:failed to mount /sdcard
"E:Can't mount /sdcard/CM-10.2.zip...."
Click to expand...
Click to collapse
may need to reformat sd card
reboot twrp, mount>check sd card> if you get a" need to format" popup in window
in Windows Choose a quick format (if possible) and format it as "fat32", block size "4096".
sd_shadow said:
may need to reformat sd card
reboot twrp, mount>check sd card> if you get a" need to format" popup in window
in Windows Choose a quick format (if possible) and format it as "fat32", block size "4096".
Click to expand...
Click to collapse
Reformatting successful, pushing ROM and gapps now to the Kindle....
... TWRP installing ROM and gapps now....
... Rebooting into CM10.2....
.... Success!
Thanks so much!
ttakacs said:
Reformatting successful, pushing ROM and gapps now to the Kindle....
Click to expand...
Click to collapse
I can't remember if I said in video, files may not be in sd card, but in system folder, and may need to reboot kindle before you can see the files.
check the sd card first though
Thank you for the guide, sd_shadow. I was really looking forward to Project OtterX but with Hashcode gone, I will revert back to stock Amazon.
@sd_shadow, thanks for this guide. I tested some OtterX roms but the Kindle is with my wife most of the time and for the sake of simplicity and battery consumption I'm gonna go back to non-otterx roms.
Instead of flashing the stock Rom, is there any way to revert to one of the non-otterx CM11 roms?
Thanks in advance!
inarush said:
@sd_shadow, thanks for this guide. I tested some OtterX roms but the Kindle is with my wife most of the time and for the sake of simplicity and battery consumption I'm gonna go back to non-otterx roms.
Instead of flashing the stock Rom, is there any way to revert to one of the non-otterx CM11 roms?
Thanks in advance!
Click to expand...
Click to collapse
yes instead of installing twrp 2.2.2.1 use 2.7.1.0 and flash cm7
sd_shadow said:
yes instead of installing twrp 2.2.2.1 use 2.7.1.0 and flash cm7
Click to expand...
Click to collapse
Thanks a lot, I have it running otter CM11 already!
I guess I speak for everyone in this community when I say that I love you!
Related
I wiped everything in TWRP on accident. the only thing on the phone is TWRP, no backups, nothing. i was wondering if there was a way to get all the system files and such back?
it can not unzip files.
the only thing it can do is run twrp. that's it.
TWRP can only restore backups it's made. Unless you copied them off the device before you wiped it.. you are out of luck on doing a restore.
You should be able to reload a Rom though.
If he were to try and flash a stock.zip, how would he get it onto /sdcard?
Mount USB in TWRP
1. once you are in twrp click the mount button from the recovery
2. mount sdcard - it should show up on your computer
3. download http://www.mediafire.com/?gtxrohbc4gmu4m8
4. copy the downloaded file to sdcard
5. in twrp tap install, select the file, clear the small button with "X md5" or something like that(if you don't do this the kf will not install the rom) and install it - ignore failures about volume /misc - the kf don't have a volume /misc
6. on the screen where you return after installation tap clear dalvik/cache (in the lower left)
7. go to you command prompt and issue "adb shell idme bootmode 4000" and "adb reboot"
8. be patient - the first boot takes long time
9. enjoy !
you don't have to root it because this rom is a prerooted stock rom
What would this forum do without b63? Thank you.
Post 1: Rooting, Flashing:
- To install an ICS or JB rom you NEED skrilax_cz unlocked bootloader
- Flashing the skrilax_cz bootloader and custom recovery
- Updating or Flashing a different recovery
- ics root methods
Post 2: How to use an update.zip Method
- Fix "Stuck on Acer Logo"
- Revert to stock
Post 3:How to unbrick your Tab...nvFlash Method
- Fix "nvFlash partition errors" with "babsector.rar"
- timmydeans EUU root tool- Repairing "Stuck in apx mode"
- Running nvFlash from the command line
- Archived nvFlash files and original threads
- How to use fastboot
Please read carefully and thoroughly all the steps before you start...if something is not clear then feel free to ask...its easy to softbrick your tab and not as easy to unbrick it...
You will need your CPUID - this cannot be said enough!!! Please do not attempt any flashing until you have a copy of it stored safely!!!
Bear in mind - installing custom roms and a recovery IS NOT DONE the same way as on your phone or other android device!!!
You must install the "skrilax_cz unlocked v8 bootloader" to install a custom rom/recovery
There is alot that can go wrong and you will need to follow the directions to the letter.
If you are stuck with the acer logo on boot or faced with a dead android or a recovery verified failed, when booting to recovery
then you have not followed the correct procedure and at the very best will need to do this all over again.
Before you go any further and while you can still boot into your tab - please retrieve your CPUID - see my guide here
Summary of Steps to flashing the skrilax_cz unlocked bootloader and custom recovery using nvFlash
Step 1. Install the Acer Drivers here and the USB drivers from the Android SDK here
Step 2. Retrieve your CPUID
then head to blackthund3rs site to generate your sbk
dibb_nz said:
How To Retrieve Your CPUID
Gersma's AfterOTA Lite retrieves all your ID's and saves them to a text file get it here
From a working system in /sys/firmware/fuse/acer_cpuid
Click to expand...
Click to collapse
Step 3. If you are running factory stock - you will need to rename or delete "the boot.p file" in /system to prevent your custom recovery being overwritten
- Use blackthund3rs ICSRoot here which will rename "the boot.p file" for you
- Have your Custom Rom downloaded and copied to your External SD Card ready to install immediatelyafter flashing skrilax's patched bootloader
- You are now ready to proceed with the "installation" you will also be asked to choose a Custom Recovery (CWM, TWRP,or Public)
Step 4. There are a couple of ways of doing this, manually or with one of the Auto Tools
- civato's manual nvFlash download and Guide and a walkthrough here
- Download gersma's afterOTA Tool if you have OTA'ed to ICS
- Download blackthund3rs apxFlash Tool and a walkthrough here
Step 5.To Manually Enter APX Mode
To get into APX mode, power off the tab.
Then, press the reset button (use a paper clip).
While still holding reset, hold power for 3 seconds.
Then, release power. Release reset after 1 more second.
The screen will be blank, but you are in APX mode (the power light should be on).
Click to expand...
Click to collapse
Once the flash is complete, boot directly to Recovery, Do a Wipe and Format and install your Rom!!
Moscow Desire said:
When you boot to CWM Recovery, you have a menu item "Wipes"
In Wipes;
1. Data/Factory Reset (don't worry, it skips your photos and such)
2. Cache
3. Dalvik Cache
Wait, you're not finished.
Go back to the previous menu, and select "Mounts and Storage".
1. Format System
2. Format Flexrom
Click to expand...
Click to collapse
NOTE: You may need to do a FULL WIPE AND FORMAT - to do this, enter recovery
Click to expand...
Click to collapse
In CWM select "Backup and Restore"
click on "Toggle backup and restore of internal storage (/data/media)"
should say enabled....
from the main menu select "Mounts and Storage" and "format /data"
this will REALLY format data and all your data and settings will be lost.
Click to expand...
Click to collapse
I have the unlocked bootloader: how do I update or change my recovery?
Only a few custom recovery's are compatable with ICS Custom roms, I've attached these to this post and they need to flashed via fastboot
Via Recovery:
There are some flashable zips around so copy the zip to your external sd or flash drive
boot to recovery and choose:
Install from zip option
Navigate to the zip and flash!!
Via fastboot see Post 3 for using fastboot
Use Acer Recovery Installer from the playstore
Please note again this is only possible with the unlocked bootloader
I'm on a stock rom, How do I root, I don't want a custom rom or recovery?
If you're happy with Acers Stock Rom?? and just want root, there are a couple of options:
blackthund3rs icsRoot.zip in Step 3 above - extract and run the .exe...Done
Original thread [ROOT] Stock ICS Leak One-Click Root Tool
For those wanting to root manually ZeroNull's method Full root for A50x ICS 4.0.3[LEAK]. Simple method.
_______________________________________________________________________________________________
if links arent working or you think something needs to be added or changed
please pm me...
if you're having troubles feel free to ask, I'll do my best to help
...thanx all
When Things Go Bad....How to unbrick
Download Links to Unbrick your Tab
1. update.zip method using HC 3.1_Full_Update.zip
Notes on use:
- rename the zip to "update.zip" and flash either using cwm or "pwr/volume down"
- you can flash the v8 bootloader from HC 3.1 if you want to ---
- You can restore a nandroid backup or flash an HC rom from here too, first you need to rootby installing iconiaroot then flash a custom recovery using Acer Recovery Installer
- oh how easy it all was on HC 3.1
- es File Explorer download here
Use this update.zip for any of the following:
- You do not have your cpuid
- You are stuck on the "Acer" Logo
- Your tab boots past the Acer Logo but then boot loops at the boot animation
- You are on the old HC bootloader /ICS Rom combination
- You wish to return to factory stock, and OTA all the way to Stock ICS
You CANNOT use the update.zip method if:
- You are stuck in apx mode
- You have unsuccessfully nvflashed skrilax_cz unlocked bootloader or timmydeans root tool-tdv4
- You have boot verified failed error
(Please see the EUU/nvFlash Method below to repair these issues)
HC 3.1 FULL_update.zip
************************************************************
2. nvFlash/apx/EUU method
you MUST use this if:
- the update.zip has not worked for you
- you do not have an external sd_card
- flashing the unlocked bootloader has failed
- your partitions are screwed up
timmydeans root tool -tdv4- will reset partitions, and downgrades you to a pre-rooted HC3.2.1 with cwm 1.7
To Downgrade using tdv4:
1. Do not connect your tab to your pc
2. Run the tool till you see the window telling you to put yr tab in apxmode
3. Put your tab in MANUAL apx mode using the button combo
4. Connect your tab to your pc now
5. Let the tool continue - you should see the big white PASS when its done!
***********************
BABSECTOR.RAR
***********************
***********************
babsector.rar download here - will reset partitions when tdv4 will not work for some reason
How to use babsector -
Turn your tab off and put it in apx mode manually. Press and hold reset button, hold power for 3 secs after the light comes on and release it, after another second release the reset button. Your screen is black and the power light is on.
On your PC:
Download and extract the .rar to a folder on your PC
Connect your tab to your PC
Navigate to the babsector folder and click on 501 A.bat
On your tab:
Reboot into recovery power/volume DOWN - (closest end to the power button)
Go to Mounts and Storage Menu and
Format - System, Data, Flexrom, Cache
Then flash your ICS/JB rom, power off.
Go back into apx mode and run 501 B.bat
Reboot into recovery and do the wipes
Reboot!!!
Click to expand...
Click to collapse
Official Acer a500 EUU 3.0.1 EUUs_SBK_Acer_A500_1.016.05_COM_GEN1.rar
3. Stuck with Black Screen and Power LED Light is on
This can happen "just like that" for no particular reason or after an OTA - if this is the case, its more than likely caused by a faulty memory chip on the motherboard - the ONLY fix for this is a replacement m/b from Acer..
Most likely though it happens by trying to flash a recovery or bootloader via Custom Recovery or a Rom Manager or Acer Recovery Installer - the first time bootloader flash must be done using nvFlash - OR if you've tried to flash BEFORE your tab has entered "Acer Download Mode" as displayed on your tabs screen
If you are using one of the auto flash tools and the tool seems to get somewhere - do not carry on -
1. use "safely remove hardware" icon in the PC system tray to eject the "APX Device"
1a. if there is no apx device listed here - then you need to install the drivers correctly then try the flash again...
2. next close the tool down and disconnect the usb cable
3. reboot both tab and PC
4. Once you;re back in windows connect your usb cable to your tab
5 Check the Acer-Picasso boot/recovery driver has installed
6. Proceed with the flash again
Getting out of APX Mode
If worse comes to worse and you are definitely stuck in APX Mode then download the archived file nvFlash.zip which will only flash the v2 unlocked bootloader - to flash a recovery image you'll need to download one and copy it to the nvflash folder.
1) extract "nvFlash" to C:\nvflash
2) pwr your tab OFF and ensure the Pwr LED lite is off
3) Manually put your tab in APX Mode
4) Connect your micro usb cable to your PC
5) Ensure your PC lists an "apx device"
6) Open a command prompt on C:\nvflash
7) Follow the steps below from vache:
vache said:
launch this to load bootloader :
Code:
nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk [B]MYSKB[/B] --sync
Of course, change MYSBK with yours.
Next, flash the bootloader :
Code:
nvflash -r --format_partition 4
nvflash -r --download 4 bootloader.bin
If you want to flash a recovery :
Code:
nvflash -r --format_partition 6
nvflash -r --download 6 myrecovery.img
or a new boot :
Code:
nvflash -r --format_partition 7
nvflash -r --download 6 myboot.img
To leave APX mode :
Code:
nvflash -r --go
Click to expand...
Click to collapse
Archived Files:
These files are the ones civato packaged for the "v8 unlocked bootlader.zip"
Original nvFlash zip files from "vache" and
"strra's" original batch file with the v2 bootloader from "skrilax_cz" & cwm 1.7.2 -
and the original nvFlash guide from jm77 from this thread
How to use fastboot
Fastboot works the same as adb by issuing commands from your PC
1. Put your tab in Fastboot Mode - Hold down the Volume UP button and press power button until your tab vibrates
2. Choose fastboot mode from the menu
3. Hook your tab to your PC
4. On your PC navigate to the folder where fastboot.exe/adb.exe are located
5. Open a command prompt on this folder
Run the following commands
Code:
fastboot devices
it should return a ?
To perform a Hard Reset or FULL WIPE your device
then type in:
Code:
fastboot erase userdata
fastboot erase cache
fastboot reboot
To flash a "recovery.img"
You'll need an actual recovery.img for this one, I've attached a couple to this post
These can be found in the unlocked bootloader packages
Copy "name_of_your_new_recovery.img" to your fastboot/adb folder
Hook up your PC and on your tab enter fastboot mode
Issue these commands"
Code:
fastboot devices
it should return a ?
Code:
fastboot flash recovery name_of_your_new_recovery.img
should say Done
Code:
fastboot reboot
quickly hold in the volume down button while it reboots - if you time it right it should boot to recovery...otherwise just power it down then try again
Thanks go to civato, blackthund3r, skrilax_cz, gersma, vache, strra, sp3dev
Hi
I have my A500 rooted. I DO have my CPUID and SBK
When I tried to flash unlocked bootloader with Blackthund3rs' program, it stucked on Stage 2.
I think I did the Babsector
Run a501 A.bat, but unable to Run a501 B. (unable to get in to APX mode for some reason)
then I used afterOTA (standard method)
Somehow I got the CWM Recovery 1.7.3 on the tab, some Error message when I am in the Recovery.
When I do the wipe and format following this: (from TegraOwner site)
"here's how to:
go to in recovery enter "Backup and Restore" and click on "Toggle backup and restore of internal storage (/data/media)"
should say enabled....
then go into "Mounts and Storage" and "format /data"
I get this:
Backup and Restore /data/media: Enabled
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
Error formating /data!
I am unable to flash the V170, or any other ICS ROM (encryption unsuccessful...)
Able to flash the JB V20, but only with about 60 MB left on the internal storage (I have the 8GB unit), unable to install any apps, only thing I can do is surfing internet.
The Storage under Setting shows:
Internal Storage: total space 0.00B
Micro SD CARD: total space 29.71GB
But when I press the Gallery or camera, it says No Storage, No external storage available.
Do you have any idea about what's going on with my tab? What should I do next?
Thanks
---------- Post added at 02:23 PM ---------- Previous post was at 01:50 PM ----------
Hi
I have my A500 rooted. I DO have my CPUID and SBK
When I tried to flash unlocked bootloader with Blackthund3rs' program, it stucked on Stage 2.
I think I did the Babsector
Run a501 A.bat, but unable to Run a501 B.bat (unable to get in to APX mode for some reason)
then I used afterOTA (standard method)
Somehow I got the CWM Recovery 1.7.3 on the tab, some Error message when I am in the Recovery.
When I do the wipe and format following this: (from TegraOwner site)
"here's how to:
go to in recovery enter "Backup and Restore" and click on "Toggle backup and restore of internal storage (/data/media)"
should say enabled....
then go into "Mounts and Storage" and "format /data"
I get this:
Backup and Restore /data/media: Enabled
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
Error formating /data!
I am unable to flash the V170, or any other ICS ROM (encryption unsuccessful...)
Able to flash the JB V20, but only with about 60 MB left on the internal storage (I have the 8GB unit), unable to install any apps, only thing I can do is surfing internet.
The Storage under Setting shows:
Internal Storage: total space 0.00B
Micro SD CARD: total space 29.71GB
But when I press the Gallery or camera, it says No Storage, No external storage available.
Do you have any idea about what's going on with my tab? What should I do next?
Thanks
appple said:
Hi
I have my A500 rooted. I DO have my CPUID and SBK
Click to expand...
Click to collapse
good:good::good:
When I tried to flash unlocked bootloader with Blackthund3rs' program, it stucked on Stage 2.
Click to expand...
Click to collapse
theres a couple of different errors you can get at "stage 2" uploading image, ebt, bct or partitioning - did u see which one?
I think I did the Babsector Run a501 A.bat, but unable to Run a501 B. (unable to get in to APX mode for some reason)
Click to expand...
Click to collapse
you could have tried putting yr tab in apx mode manually and to check an "apx device" is listed...if its not its a driver issue
then I used afterOTA (standard method)
Click to expand...
Click to collapse
I assume you were running stock OTA ICS??
Somehow I got the CWM Recovery 1.7.3 on the tab, some Error message when I am in the Recovery
Click to expand...
Click to collapse
thats weird - didnt think afterOTA came with 1.7.3 - i may be wrong tho'
When I do the wipe and format following this: (from TegraOwner site)
"here's how to:
go to in recovery enter "Backup and Restore" and click on "Toggle backup and restore of internal storage (/data/media)"
should say enabled....
then go into "Mounts and Storage" and "format /data"
I get this:
Backup and Restore /data/media: Enabled
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p8
Error formating /data!
Click to expand...
Click to collapse
eewwww thats ugly!!!
Do you still have the unlocked bootloader???
You may need to boot into fastboot mode (pwr-vol+) and
Code:
fastboot erase /cache
fastboot erase /userdata
fastboot reboot
I am unable to flash the V170, or any other ICS ROM (encryption unsuccessful...)Able to flash the JB V20, but only with about 60 MB left on the internal storage (I have the 8GB unit), unable to install any apps, only thing I can do is surfing internet.
Click to expand...
Click to collapse
Not sure I can help with tegra-owners JB rom - I know it doesnt require the unlocked BL - but there've been a few folks on here that have had issues with it (myself included) not sure why and didn't spend alot of time trying to figure it out - I just reflashed the CM10 JB rom of civato's
The Storage under Setting shows:
Internal Storage: total space 0.00B
Micro SD CARD: total space 29.71GB
But when I press the Gallery or camera, it says No Storage, No external storage available.
Do you have any idea about what's going on with my tab? What should I do next?
Thanks
Click to expand...
Click to collapse
The main thing is to get everything fastboot erased first and see how that goes...its looking like a partitioning error at this point....
and be helpful to know what rom etc you had on there in the first place!
rgds
dibb
theres a couple of different errors you can get at "stage 2" uploading image, ebt, bct or partitioning - did u see which one?
Click to expand...
Click to collapse
Here is what I wrote a while ago on the TO site:
I am trying to use you APX Flash tool to patch the Bootloader. (using Civato's guide on the Xda forum)
It hung at "Flashing Bootloader (EBT) stage two - uploading image..." and the other black command prompt window shows : Nvflash started [resume mode]
I, then, re-booted the A500, re-installed the Acer USB driver (used Acer link from A500 Manager)
Same as above.
Now I tried use the manual flash following Civato's guide, I got:
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command execution failed cmd 13, error 0x120002 Failed!
Command failure: format partition failed <bad command>
bootloader status: unknown operation <code: 1> message: flags: 0
Nvflash started
[resume mode]
you could have tried putting yr tab in apx mode manually and to check an "apx device" is listed...if its not its a driver issue
Click to expand...
Click to collapse
I was using apxFlash tool, could not get it into the apex mode when I tried to run a501 B. Should I try to run it with the manual method now?
I assume you were running stock OTA ICS?
Click to expand...
Click to collapse
?
Yes, rooted, was trying to get unlocked boot loader, thought I need that to flash custom ROM
theres a couple of different errors you can get at "stage 2" uploading image, ebt, bct or partitioning - did u see which one
thats weird - didnt think afterOTA came with 1.7.3 - i may be wrong tho
Click to expand...
Click to collapse
'
I probably got it after I ran the a501 A.
eewwww thats ugly!!!
Do you still have the unlocked bootloader???
You may need to boot into fastboot mode (pwr-vol+) and
Code:
fastboot erase /cache
fastboot erase /userdata
fastboot reboot
Click to expand...
Click to collapse
Yes, I was wondering what is that fast boot mode does
The main thing is to get everything fastboot erased first and see how that goes...its looking like a partitioning error at this point....
and be helpful to know what rom etc you had on there in the first place!
Click to expand...
Click to collapse
Any step guide on how to do this (used the adb thing before to get the SDK, I think, but forgot how now)
I had ICS OTA before, started messing with the tab few months ago, on and off, sorry I could not remember exactly how I got here.
I am not newbie totally, just know enough to be dangerous
Dibb, thank very much for your help
What I have done so far:
Step 1: Did this and my computer can detect my Acer
Step 2: I installed AfterOTA from the link provided and extracted CPUID and SBK (my question: will I be using this anywhere in my flashing process as I dont see it, if so why did I take this?)
Step 3: Since I was nervous to delete that boot.p file right away I moved that into my SD card as backup and used blackthund3rs ICSRoot to root the tablet and succeeded.
- I haven't downloaded the ROM yet as I was looking for the best in the forum, so left this step for last
- I used afterOTA to "install the unlocked bootloader" which will also "flash a Custom Recovery" as advised by you in the email (Bootloader ICS v3.14.8 + Recover Thor v1.7.3)
My big question now is on flashing the custom ROM - am I going straight away from here to recovery mode and do the below as in your thread?
------------------------------------------------------------------------------------------------
When you boot to CWM Recovery, you have a menu item "Wipes"
In Wipes;
1. Data/Factory Reset (don't worry, it skips your photos and such)
2. Cache
3. Dalvik Cache
Wait, you're not finished.
Go back to the previous menu, and select "Mounts and Storage".
1. Format System
2. Format Flexrom
------------------------------------------------------------------------------------------------
thanks and cheers
Sany
How to use fastboot
@appple
1. K go up to Step 1 and d/l the android sdk drivers - (its not the whole sdk just the adb and fastboot drivers) and extract them to your C:\ drive...
2. With your tab powered off - hold the vol+ button down and press down pwr
2a. If you have the v8 bootloader your tab should display the fastboot menu
2b. Enter Fastboot Mode
3. Connect your tab to your pc with the micro usb cable
4. Open a command prompt from the folder that contains "fastboot.exe"
5. Type fastboot devices
6. It should return a "?" this is fine!
Now just enter the commands I posted earlier
7. fastboot erase userdate
8. fastboot erase cache
After you enter each command - the prompt should say 'Done'
9. fastboot reboot
sany said:
What I have done so far:
Step 1: Did this and my computer can detect my Acer
Step 2: I installed AfterOTA from the link provided and extracted CPUID and SBK (my question: will I be using this anywhere in my flashing process as I dont see it, if so why did I take this?)
Click to expand...
Click to collapse
afterOTA will do this behind the scenes
if u use apxFlash or nvFlash then yes you will need to enter yr sbk manually
if u need to use a rollback rom or official EUU Tool - you will need to enter your cpuid
Step 3: Since I was nervous to delete that boot.p file right away I moved that into my SD card as backup and used blackthund3rs ICSRoot to root the tablet and succeeded.
Click to expand...
Click to collapse
being nervous is ok - you normally need root before you move it as its a system file...so just go back and check /system again...you can rename it "....boot.p.old" if that makes u less nervous
- I haven't downloaded the ROM yet as I was looking for the best in the forum, so left this step for last
- I used afterOTA to "install the unlocked bootloader" which will also "flash a Custom Recovery" as advised by you in the email (Bootloader ICS v3.14.8 + Recover Thor v1.7.3)
My big question now is on flashing the custom ROM - am I going straight away from here to recovery mode and do the below as in your thread?
Click to expand...
Click to collapse
yes but I advise a Backup before you do....if anything goes awry at least you'll have that!!!
then flash your rom and reboot
As far as roms go - I've only ever used civato's ones so I'm not much help there, sorry - and I spend so much time 'bricking and unbricking' (research purposes of course!!) I don't really get alot of time just 'playing', lol...but I will say this - most of the custom roms on here are pretty damn good, they're well supported and stable....just check the last couple of pages of the rom thread itself...if theres any user issues at all, you'll find them there....oh and in the OP itself
best of luck m8!!!
dibb_nz said:
being nervous is ok - you normally need root before you move it as its a system file...so just go back and check /system again...you can rename it "....boot.p.old" if that makes u less nervous
Click to expand...
Click to collapse
Do you think I need to go and do this, as I have already rooted, and completed unlocked bootloader and recover via afterOTA, I might be renaming the one that came with the modified bootloader?
dibb_nz said:
yes but I advise a Backup before you do....if anything goes awry at least you'll have that!!!
Click to expand...
Click to collapse
How will I do this? sorry for pestering
sany said:
Do you think I need to go and do this, as I have already rooted, and completed unlocked bootloader and recover via afterOTA, I might be renaming the one that came with the modified bootloader?
Click to expand...
Click to collapse
its only required if you are flashing a Stock Rom - all of the custom roms are pr-rooted and this file has already been deleted...
If the file is in /system it will remove your newly flashed custom recovery and put back the Acer Stock Recovery {i.e. dead android on its back} if this happens you just need to flash the recovery again
How will I do this? sorry for pesteringhttp://forum.xda-developers.com/showthread.php?p=35675823#post35675823
Click to expand...
Click to collapse
thats ok, we were all new to this stuff at some stage
in the recovery menu you will see an option "backup and restore"
select it and then you will see another menu - select "Full Backup" and let it do its thing...
once its done go back to the main menu and select "Flash Zip from SD Card" then choose the zip of the rom.
Just a note:
In recovery menu your SD Card refers to your external sd card
Your Internal Memory of the Tab itself is called Internal Storage
dibb
heres a pic - its an older version of cwm but gives the general layout
I gotta get some sleep - will check back in the morning...dibb
dibb_nz said:
1. K go up to Step 1 and d/l the android sdk drivers - (its not the whole sdk just the adb and fastboot drivers) and extract them to your C:\ drive...
2. With your tab powered off - hold the vol+ button down and press down pwr
2a. If you have the v8 bootloader your tab should display the fastboot menu
2b. Enter Fastboot Mode
3. Connect your tab to your pc with the micro usb cable
4. Open a command prompt from the folder that contains "fastboot.exe"
5. Type fastboot devices
6. It should return a "?" this is fine!
Now just enter the commands I posted earlier
7. fastboot erase userdate
8. fastboot erase cache
After you enter each command - the prompt should say 'Done'
9. fastboot reboot
Click to expand...
Click to collapse
Hope you had good rest yesterday.
I will try to do this in next few days.
Do you know what the a500 B of Babsector do? Just wondering
appple said:
Do you know what the a500 B of Babsector do? Just wondering
Click to expand...
Click to collapse
sorry i'm not too familiar with this tool - I've never had to use it as timmydeans v4 has always worked for me...
From what I can gather, running the 1st bat files uses a different partition to flash cwm 1.7.3 so you can enter recovery and perform a format of /system.
In other words it seems 'resetting the partitions' (like timmydeans tool does) is not enough - you must then do a format of the system partition thru cwm and then run the b.bat to put the original partition table back on yr tab....
You will need to flash a rom directly after using it....formatting system will leave you without an OS but this is not mentioned in anything I've read - you can read more about it here
EDIT: found a good thread for you to read here explains how to use babsector
BTW i'm working the next 3 days so may not be around as much as i'd like....
will check in when i can
rgds dibb
Merry Christmas dibb
From what I can gather, running the 1st bat files uses a different partition to flash cwm 1.7.3 so you can enter recovery and perform a format of /system.
In other words it seems 'resetting the partitions' (like timmydeans tool does) is not enough - you must then do a format of the system partition thru cwm and then run the b.bat to put the original partition table back on yr tab....
You will need to flash a rom directly after using it....formatting system will leave you without an OS but this is not mentioned in anything I've read - you can read more about it here
Click to expand...
Click to collapse
You are right about this little tool, (I was the last poster in that thread when I got stuck before the A500 B zip)
EDIT: found a good thread for you to read here explains how to use babsector
Click to expand...
Click to collapse
I was almost ready to try the Fastboot thing you showed me earlier, then after I read this thread, I decided to give the Babsector one more try, using the manual method to get in APX mode per your guide (last time I used the blackthund3's tool), VOILA, it WORKED!! I flashed Civato's Flex-Resurrection_Rev1
and it's rocking (I stayed with 4.0.4 because I want to swap my internal(8GB) with an external (32GB)
h??p://forum.xda-developers.com/showthread.php?t=1445720 ), now going to do this, hope it will go smoothly.
BTW i'm working the next 3 days so may not be around as much as i'd like....
will check in when i can
Click to expand...
Click to collapse
Hope you did not have to work too hard, and enjoying your Christmas now.
Thanks again for your help.
@appple great news glad it worked
Sent from my GT-I9300 using Tapatalk 2
N00b trying to upgrade to ICS.
I have a acer iconia a501, There is no ics update here in Canada I believe. It currently has unrooted HC 3.2 kernal 2.6.36.3+ with a build number of Acer_A501_4.452.01_PA_ROG. some of the guides seem pretty long to me. I have tried to install android sdk, however it does not seem to function under windows 8. is there another way to do this?
Go to the bottom of this post and download adb_fast.zip - this is a mini sdk kit with just the drivers - you do have the acer drivers as well, yes?
there have been a couple of issues reported using win8, so try a different micro usb cable and a different usb port on your pc...the acer is very picky when it comes to cables...
If you have access to a linux machine you'll have no probs at all flashing the v8 bootloader
Thank you
Thank you Dibb for responding to me in the other thread. I've got the update downloaded from your post 2 and I have an external SD card to load it onto. Am I correct in thinking there's no connection required between my computer and tablet? I rename the file to update.zip, load it onto the SD card, put that in the tablet and use the power/volume- buttons correct?
Yeh u got it....I think the update.zip is good to go just copy it to yr ext sd. Best to do full wipe too m8 via Android settings...you'll be back to full stock so no custom anything....If it's the 3.1 zip u can take the ota to ics or flash the v8 unlocked bootloader from there, to get cwm...and a custom rom
Sent from my GT-I9300 using Tapatalk 2
Hey,
For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read.
I have a google nexus 4, and i managed to format the whole phone while i was installing a new rom. Now i can boot into bootloader and CWM but there is no files on the /sdcard/ there so that i can flash the phone
I tried to use the feature "adb push", but it´s not permited as i cannot enable the USB debugging...
I tried these guidelines: http://forum.xda-developers.com/showthread.php?t=1754018 but they didn´t help.
My phone info is:
Fastboot Mode
Product_Name: mako
HW Version: rev_11
Bootloader_version: makoz101
Signing - Production
Secure boot - enabled
Look state: Unlocked
Any ideas or suggestions are welcome.
Thank You
Boot it to fastboot and flash factory image and you're good to go. You can find instructions in the General section.
andr0idfreak said:
Boot it to fastboot and flash factory image and you're good to go. You can find instructions in the General section.
Click to expand...
Click to collapse
Fastboot = Bootloader?
Flash Recovery image, this is what i´m unable to do.
I have tried many methods from the general section, any particular thread do you think is most helpful?
I really appreciate your answer.
You could connect the phone to a PC and use CWM to mount the SD card. Copy a CWM flashable rom (99% of custom roms) to the SD card, disconnect from the PC and use CWM to flash. Job done
madgibbon said:
You could connect the phone to a PC and use CWM to mount the SD card. Copy a CWM flashable rom (99% of custom roms) to the SD card, disconnect from the PC and use CWM to flash. Job done
Click to expand...
Click to collapse
In CWM i go to "Mounts and Storage" i see the list:
mount /system
unmount /data
mount /sdcard
format.....
If i press mount /sdcard the screen flashes and nothing happens still says the same "mount /sdcard/"
Any thoughts?
arifagic said:
In CWM i go to "Mounts and Storage" i see the list:
mount /system
unmount /data
mount /sdcard
format.....
If i press mount /sdcard the screen flashes and nothing happens still says the same "mount /sdcard/"
Any thoughts?
Click to expand...
Click to collapse
You cannot currently mount SD from recovery. Use adb to push the files you want to flash to your SD, then flash them in recovery.
adb push romname.zip /sdcard/
arifagic said:
Fastboot = Bootloader?
Flash Recovery image, this is what i´m unable to do.
I have tried many methods from the general section, any particular thread do you think is most helpful?
I really appreciate your answer.
Click to expand...
Click to collapse
Fatboot = Bootloader, yup! I would read this thread for detailed information.
http://forum.xda-developers.com/showthread.php?t=2010312
If you are not so comfortable with about, you can try out Wug's Nexus Root Toolkit (a bit riskier though) that I have used a couple of times to restore factory images, works fine.
madgibbon said:
You could connect the phone to a PC and use CWM to mount the SD card. Copy a CWM flashable rom (99% of custom roms) to the SD card, disconnect from the PC and use CWM to flash. Job done
Click to expand...
Click to collapse
This is the most simple way if you have CWM recovery.
Fixed!
Had the same problem just now and it scared the heck out of me.
Solved it by doing the following (Did this using ClockWorkMod Recovery 6.0.2.3 so some steps may be different from yours)
Boot to recovery
Connect your device to PC
Download and extract this - http://forum.xda-developers.com/showthread.php?t=1996051
Go to device manager and see that your device has the ! sign
Install the drivers you just downloaded to your device
Rename your rom to update.zip and copy it to where your adb is located
Your device should now be detected by adb so type this - adb push update.zip /sdcard/
In your device, go to install from SD card > apply /sdcard/update.zip
DONE!
Thanks man
I just tried this in boot loader, then i got this error:
http://awesomescreenshot.com/0a3ydrw8d
(Device not found)
---
Then i booted into CWM v6.0.1.9 and then the device was found, and it seems like it successfully transfered the file.
http://awesomescreenshot.com/03cydsr1c < which is great, but when i go to "install zip from sdcard" -> "choose zip from sdcard" the screen blinks and at the bottom it says:
- No files found
----
I then formated the sdcard from the advanced menu and retried transfering the files and it worked
Fantastic!!! Jusdavis i can´t thank you enough.
Flashing for Dummies
In this guide we'll go over how to flash custom ROMs with root and TWRP in addition to updating
this guide will always be updated
Read the ENTIRE guide before you start
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
things to keep in mind:
1- when you flash a ROM through TWRP, it will flash to your inactive slot, that's why you need to switch slot after flashing it and then flash everything else, think of it like an OTA update except you need to switch active slot yourself
2- when you change your active slot in TWRP, it will only change after you reboot, your active slot will always be the one you're currently booted on
3- the order of flashing anything that modifies boot is
1) TWRP
2) custom kernel
3) noverity
4)Magisk
if you're not sure, flash stock boot of your rom and do it again, flashing TWRP will break Magisk, flashing a custom kernel will break magisk, flashing TWRP after flashing a custom kernel will most likely get you a bootloop
Before you begin
you need to unlock your bootloader first https://forum.xda-developers.com/mi-a2/how-to/unlock-bootloader-n-root-magisk-easy-t3856800
It is no longer required to be on stock Oreo before flashing, but I currently still recommend you do so as there might be some minor bugs on some custom roms, but otherwise everything will work just fine.
get latest platform-tools if you haven't already, using an older one WILL result in errors
platform-tools
extract it and open the folder
hold shift then right click on an empty space then click "open command window here"
if you're on windows 10, doing that will open power shell instead, inside power shell, type "cmd" and press enter, use cmd for everything below
if you're coming from stock, you need to do this first
type the following command (data and files will be wiped)
Code:
fastboot -w
fastboot set_active b
Notes:
Pixel Experience includes Gapps, do not flash them after the rom
many roms include TWRP, such as Havoc, AICP and many others, check ROM thread first, if it includes it then don't flash TWRP.
Flashing custom ROMs and other stuff
download latest TWRP img and zip from https://twrp.me/xiaomi/xiaomimia2.html and place it in the same folder you extracted platform-tools to
NOTE: if you are on stock then use TWRP 3.2.3 img, not 3.3
note: if you're having issues with official TWRP, I've built an unofficial one with F2FS support which you can try here
be careful if you switch to F2FS, it will only work with a recovery that supports it and a ROM that supports it, no stock.
rename the img to twrp.img
in cmd, type
Code:
fastboot boot twrp.img
if you get a bootloop, force shutdown (power + volume down) and try again
using MTP copy the files needed to flash to your phone
if MTP doesn't work, you have the following options
1) wipe data from TWRP, try again
2) advanced > file manager, go to /data/media , if there is nothing in there, create a new folder called 0 there by going to Advanced > Terminal and typing the following commands
Code:
cd /data/media
mkdir 0
then reboot to bootloader and try again
3) try using PBRP for MTP, then go back to TWRP PBRP
4) use adb sideload:
in TWRP, go to Advanced > adb sideload, then on PC
Code:
adb sideload file.zip
do that for each thing you want to flash
(you can type adb sideload then drag and drop the file you want to flash onto cmd, make sure there's a space between sideload and the file you want to flash)
5) use adb push. follow methode 2 to create the folder, then in cmd, type this command
Code:
adb push file.zip /data/media/0/
do that for each file you need
after you got the files on your phone, it's time to flash
remember that when flashing a ROM, it will flash to your inactive slot, in this guide I'll assume your active slot is B, use "fastboot set_active b" in fastboot if you'd like to follow along
First go to wipe > advanced and select System and Data then wipe, then you can start flashing
1- flash the ROM zip
2- flash TWRP zip, so you can boot to TWRP without the need of a PC (ONLY if the ROM doesn't include it already)
3- switch your active slot (to A if you are on B and to B if you were on A)
4- reboot recovery
5- flash Gapps if required by the ROM you're flashing, Opengapps nano is recommended, you can get it here http://Opengapps.org
6- (optional) flash a custom kernel if desired/needed
7- (optional) flash DM-VERITY & FORCEENCRYPT DISABLER zip , this will disable DM verity and encryption in vendor, this is not required by most custom ROMs as they will disable encryption anyway, it is most useful on stock, and in the possibility that the ROM you're flashing does not disable encryption
8- flash Magisk
9- reboot to system
IMPORTANT, if you get an error while flashing ROM zip, do the following
use latest official TWRP, if you're already using it, then the ROM you're flashing is one of the older ROMs
previously, ROMs and TWRP used Jasmine as a codename for our device, while the real codename is Jasmine_sprout, this caused some issues, newer ROMs and TWRP now use the correct codename, but that means new TWRP can not flash older ROMs, and so you will need some simple modifications to the ROM zip:
1- open the ZIP using WinRAR on PC or X-plore on phone
2- go to META-INF/com/android/metadata and open it as text
3- on the last line, edit 'pre-device=jasmine' to 'pre-device=jasmine_sprout'
4- save it and try flashing again
Switching between custom ROMs
follow the same flashing instructions, you can boot directly to TWRP by holding power + volume up, wipe data and system first then flash ROM and the rest.
Updating Custom ROMs
For OFFICIAL ROMs which support A/B OTA it's very easy
1- once you get a notification that an update is available, download and install with the system updater but don't reboot (If the ROM includes TWRP then don't do any of the following steps, just reboot)
2- go to Magisk, Downloads, search for "TWRP A/B Retention Script" and install it
3- on the main Magisk page, click install > install > Install to Inactive Slot (After OTA)
4- once Magisk finishes, reboot, you will now be on the opposite slot with both Magisk and TWRP installed.
for Unofficial ROMs with no OTA or Official ROMs that don't support A/B OTA, you'll need to use TWRP, do not wipe anything:
1- boot to TWRP
2- flash the ROM zip
3- flash TWRP zip (ONLY IF the ROM doesn't include TWRP)
4- switch your active slot (to A if you are on B and to B if you were on A)
5- reboot recovery
6- flash Gapps if required by the ROM you're flashing, Opengapps nano is recommended, you can get it here http://Opengapps.org
7- (optional) flash a custom kernel if desired/needed
8- (optional) flash DM-VERITY & FORCEENCRYPT DISABLER zip , this will disable DM verity and encryption in vendor, this is not required by most custom ROMs as they will disable encryption anyway, it is most useful on stock, and in the possibility that the ROM you're flashing does not disable encryption
9- flash Magisk
10- reboot to system
Very good and very well detailed guide. This guide will be useful to those who are not so familiar with Flashing ROMs especially in our device with partitions.
Thank you for making this, as many users were asking this thing. Keep it up!
does rebooting to twrp gets stuck on twrp logo after flashing twrp zip?
its been an issue on stock or maybe i have been doing to wrong...
after wipe commands and setting active slot b,
i reboot into fastboot boot twrp.img and flash the rom and Im getting mount failed /system
is that normal?
Edit: NVM, it is normal. I successfully flashed Carbon ROM in my device. Thanks for this awesome guide.
This is great thank you. Going to try it once I get bored of stock rom.
@AxL said:
after wipe commands and setting active slot b,
i reboot into fastboot boot twrp.img and flash the rom and Im getting mount failed /system
is that normal?
Edit: NVM, it is normal. I successfully flashed Carbon ROM in my device. Thanks for this awesome guide.
Click to expand...
Click to collapse
Yes it's normal because you wiped system
levai_spencer said:
does rebooting to twrp gets stuck on twrp logo after flashing twrp zip?
its been an issue on stock or maybe i have been doing to wrong...
Click to expand...
Click to collapse
twrp.zip has a bootloop for TWRP when it is flash
Candy_Pineapple said:
twrp.zip has a bootloop for TWRP when it is flash
Click to expand...
Click to collapse
No, if you follow the instructions it works
coming from stock to pE I followed exacty the steps.
then flash CR. Here what Ive done
i-wipe cache,data,system for both partition using twrp
ii- set partition to B in twrp and flash zip
iii- set partition to A in twrp and reboot into bootloop
iv- set partition to B in twrp and reboot successfully
so what partition is my CR now?
which partition should i install gapps,kernel and magisk?
Thanks.
notJimz said:
coming from stock to pE I followed exacty the steps.
then flash CR. Here what Ive done
i-wipe cache,data,system for both partition using twrp
ii- set partition to B in twrp and flash zip
iii- set partition to A in twrp and reboot into bootloop
iv- set partition to B in twrp and reboot successfully
so what partition is my CR now?
which partition should i install gapps,kernel and magisk?
Thanks.
Click to expand...
Click to collapse
It's in B, because you didn't reboot after switching slot initially in twrp, stay in B and boot recovery then flash Gapps and the rest
Nebrassy said:
It's in B, because you didn't reboot after switching slot initially in twrp, stay in B and boot recovery then flash Gapps and the rest
Click to expand...
Click to collapse
You are right. I miss the first bl reboot.
I follow the step back and reboot after switch partition.
Only now i got the concept for A/B flashing. And my os in A now.
Thanks for the guide. Really helpful.
notJimz said:
You are right. I miss the first bl reboot.
I follow the step back and reboot after switch partition.
Only now i got the concept for A/B flashing. And my os in A now.
Thanks for the guide. Really helpful.
Click to expand...
Click to collapse
No prob, keep connected and click the tx button
Matteo (AIO Project Founder)
Hello,
after make adb push file.zip /data/media/0
I receive the next message
adb: error: failed to get feature set: no devices/emulators found
Please advice.
Thanks
Roviva said:
Hello,
after make adb push file.zip /data/media/0
I receive the next message
adb: error: failed to get feature set: no devices/emulators found
Please advice.
Thanks
Click to expand...
Click to collapse
What's the output of adb devices?
Nebrassy said:
What's the output of adb devices?
Click to expand...
Click to collapse
I entered in fastboot mode,:
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>.\adb devices
List of devices attached
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>
If I enter the command "adb devices" in normal mode (no fastboot) appear:
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>adb devices
List of devices attached
a341410 device
Roviva said:
I entered in fastboot mode,:
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>.\adb devices
List of devices attached
C:\Users\DELL\AppData\Local\Android\Sdk\platform-tools>
Click to expand...
Click to collapse
Adb devices
While in twrp, adb won't work while in fastboot, follow the guide carefully
Nebrassy said:
Adb devices
While in twrp, adb won't work while in fastboot, follow the guide carefully
Click to expand...
Click to collapse
Hello,
In your guide I dont understand the next part:
using MTP copy the files needed to flash to your phone
if MTP doesn't work, you have the following options
1) wipe data from TWRP, try again
If I made the step 1 above: I enter in the TWRP, select wipe, then, select wipe, advance wipe, select data and then swipe to wipe. After this reboot system, the telephone start but in normal mode, like restored.
2) advanced > file manager, go to /data/media , if there is nothing in there, create a new folder called 0 there by going to Advanced > Terminal and typing the following commands
I follow the step 2, in data/media appear a folder TWRP then i dont created a folder called 0
Then I go to advanced >> adb sideload and in the pc i wrote "adb sideload twrp.zip.
You write file.zip, I dont understand what is this file?
I dont understand what do you mean in the step 3: "try using PBRP for MTP, then go back to TWRP PBRP"
Code:
cd /data/media
mkdir 0
then reboot to bootloader and try again
3) try using PBRP for MTP, then go back to TWRP PBRP
4) use adb sideload:
in TWRP, go to Advanced > adb sideload, then on PC
Code:
adb sideload file.zip
do that for each thing you want to flash
(you can type adb sideload then drag and drop the file you want to flash onto cmd, make sure there's a space between sideload and the file you want to flash)
5) use adb push. follow methode 2 to create the folder, then in cmd, type this command
Code:
adb push file.zip /data/media/0/
do that for each file you need
Roviva said:
Hello,
In your guide I dont understand the next part:
using MTP copy the files needed to flash to your phone
if MTP doesn't work, you have the following options
1) wipe data from TWRP, try again
2) advanced > file manager, go to /data/media , if there is nothing in there, create a new folder called 0 there by going to Advanced > Terminal and typing the following commands
I follow the step 2, in data/media appear a folder TWRP then i dont created a folder called 0
Then I go to advanced >> adb sideload and in the pc i wrote "adb sideload twrp.zip.
You write file.zip, I dont understand what is this file?
I dont understand what do you mean in the step 3: "try using PBRP for MTP, then go back to TWRP PBRP"
Code:
cd /data/media
mkdir 0
then reboot to bootloader and try again
3) try using PBRP for MTP, then go back to TWRP PBRP
4) use adb sideload:
in TWRP, go to Advanced > adb sideload, then on PC
Code:
adb sideload file.zip
do that for each thing you want to flash
(you can type adb sideload then drag and drop the file you want to flash onto cmd, make sure there's a space between sideload and the file you want to flash)
5) use adb push. follow methode 2 to create the folder, then in cmd, type this command
Code:
adb push file.zip /data/media/0/
do that for each file you need
Click to expand...
Click to collapse
File.zip, as in the file you want to copy, you change that to the name of the file you want to copy
PBRP is another recovery, you can try booting it if twrp doesn't work to copy
Nebrassy said:
File.zip, as in the file you want to copy, you change that to the name of the file you want to copy
PBRP is another recovery, you can try booting it if twrp doesn't work to copy
Click to expand...
Click to collapse
hello,
I dont know how to follow:
flash the ROM zip
2- flash TWRP zip, so you can boot to TWRP without the need of a PC
3- switch your active slot (to A if you are on B and to B if you were on A)
4- reboot recovery
I wiped data and storage then I press back.
I flashed the PBRP that I pushed to data/media/TWRP
After flash I returned to the menu of PBRP
I switched to A
When I reboot, a warning message that "NO OS SYSTEM IS INSTALLED" appear.
I reboot to recovery but after this, the telephone does not restart. the screen "androidone" appear and dont advance...
How can I install the PBRP and magisk?
I succesfull push the files to the telephone but when flash the PBRP I cannot follow......
Roviva said:
hello,
I dont know how to follow:
flash the ROM zip
2- flash TWRP zip, so you can boot to TWRP without the need of a PC
3- switch your active slot (to A if you are on B and to B if you were on A)
4- reboot recovery
I wiped data and storage then I press back.
I flashed the PBRP that I pushed to data/media/TWRP
After flash I returned to the menu of PBRP
I switched to A
When I reboot, a warning message that "NO OS SYSTEM IS INSTALLED" appear.
I reboot to recovery but after this, the telephone does not restart. the screen "androidone" appear and dont advance...
How can I install the PBRP and magisk?
I succesfull push the files to the telephone but when flash the PBRP I cannot follow......
Click to expand...
Click to collapse
You didn't flash a rom, obviously it won't boot
* 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