[Q] Stuck in a bootloop, think EFS is corrupt - anyone know of a fix? - Galaxy Note 3 Q&A, Help & Troubleshooting

[Q] Stuck in a bootloop, think EFS is corrupt - anyone know of a fix? - Galaxy Note 3 Q&A, Help & Troubleshooting

N900W8 - unlocked Canadian version
Long story short, phone's stuck in a bootloop.
I can get into Download/Recovery, but can't mount anything in recovery. I can connect via Odin, but Win7 doesn't see the phone (so I can't transfer files).
I have a feeling my EFS is ****ed, which is why it won't boot. Is there a way to fix this, considering my connectivity situation?
I'm coming from a GNEX, which is obviously much easier to deal with than the note 3.
Any help is (obviously) greatly appreciated.

In case anyone else has this problem, I figured out the solution.
1 - boot to custom recovery (TWRP).
2 - follow steps outlined here: http://forum.xda-developers.com/showthread.php?t=2471421
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command"
3. Hit "Select" (lower right corner)..Do not select any specific folder, just hit select..
4. keyboard will open, type in the following commands, make sure you put the spaces and / where they need to be, it needs to look exactly as outlined..
mke2fs /dev/block/mmcblk0p12
Hit Go - The command will run. Clear the box, type the following command
mkdir /efs
Hit Go - The command will run. Clear the box, type the following command
mount -t ext4 /dev/block/mmcblk0p12 /efs
Hit Go - The command will run.
Click to expand...
Click to collapse
3 - reboot to recovery
4 - follow the steps outlined here: http://forum.xda-developers.com/showthread.php?p=47530627#post47530627
Download latest MJ4 firmware from SamMobile for the N900W8
Boot into custom recovery wipe System, Data, Cache, Dalvik
Boot into download mode and flash MJ4 via Odin (brings you back to stock)
Click to expand...
Click to collapse

n900w8
hi I have a samsung galaxy note 3 SM-N900W8
I lose my efs folder
My phone gets the bootloop
I can get download mod and recovery mod but the phone always rebooted (bootloop)
I'm trying all solution like
-fix boot loop .zip
-terminal commanded with TWRP
-flash it with a stock ROM ........
But no way my phone always bootloop
I think the problem about my efs folder
Can you give me efs folder N9020W8??
Please help ….
I’m sorry about bad English & thxxxxxxxxxxxxxxxxxxxxxxxxx a lot

Anyone know where I can get twrp for SM-G390W?
I am having the same problem as you are efs folders won’t mount and phone is stuck in bootloop. If anyone can help with this problem it would be greatly appreciated thx.

TWRP is twrp.me
Or the forum for your phone .

Related

[GUIDE][ICS] Beginners Guide - Rooting, Flashing, Unbricking

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

[Q]LG G2 re-flashing or rooting stock 4.4.2 bad rom

Hi all,
First off I've tried now for a two days to solve this, reading as much as I could find on here and the rest of the internet.
I decided to root my LG D802 running 4.2 and install CWM recovery no problem. Next I flashed a stock 4.4.2 vodaphone img. All went well untill i tried to use the touch screen, which shows that when i press on one point on the screen it selects multiple points basically its unusable and unable to do almost anything with it, however i have managed to turn on ADB and connect to the phone. So now i have a stock recovery and an unusable ROM.
So next up I tried to rooting it since I had ADB shell working ok, using the IOROOT25. This appears to work as when it reboots and installs the kkroot.zip in the recovery it's saying it worked. Now when I reboot and open ADB shell then type SU to get root I can't press ok when superuser pops up to asking me to give it permission, because of the touch screen problem.
If i can get root in ADB then remount the files system then i will be able to DD a new recovery img??
After getting this far and loosing, I then found this: http://forum.xda-developers.com/showthread.php?t=2432476 on flashing to stock, but the program crashes every time it's about to flash, so i tried doing a fresh install of windows 7 and then tried windows 8 however the program still crashes every time and yes I have followed the instructions and tried the manual method and checking the 127.0.0.0. lgblahblah is there
So no I am turning to you guys for help.
phone details;
Model: D802 32GB
Firmware operator: VDF
sw version: D80220a
ro.build.fingerprint: lge/g2_vdf_com/g2:4.4.2/KOT49I.D80220a/D80220a.1392133741:user/release-keys
Recovery: <3e> KOT49I.D80220a test-keys

UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?

need help
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?

twon23 said:
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?
Click to expand...
Click to collapse
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??

Ok so your phone not longer boots, correct? Do you know what build/version plus any other details of the rom you flashed? or even a link so i can have a look at the rom you have installed. Can you get into recovery mode and is it still a stock recovery image? also what is your phone d802? 16gb 32gb?

Mustafa1 said:
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??
Click to expand...
Click to collapse
If you're running root.bat as an admin, try executing it without admin privileges. Dunno why, but it seemed to work for me.

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
---------- Post added at 06:18 PM ---------- Previous post was at 06:12 PM ----------
makgun said:
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
Click to expand...
Click to collapse
NOT CWM , it is TWRP
Are you from turkey?

twon23 said:
UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?
Click to expand...
Click to collapse
Hi! I've recently flashed an updated stock ROM and have the same Touchscreen issue as yourself! Can you tell me the steps you have done to fix it? I'm using windows 8.1 to flash etc, and using a stock ROM I can't seem to get it to work again

[HELP] Bricked Umi Zero

Hello. Sorry for my english. I want flash my phone via rootjoy to Arcatarc's MIUmIZERO and i only can see miui logo. next i want back to stock rom from needrom via sp flash tool, i followed instructions and i stop, when red status back not change for 20 minutes. and i can't charge my phone, can't conected to pc, can't turn on, looks like dead. How unbrick my phone? please help
problem solved

how did you solve it? please let me know as i am in the same boat

If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.

it is dead . the phone wont turn on . the pc wont recognise it anymore , it was fine ... untill i tried to flash stock through sp flash tool .
i was running antarcts emui,.... tried flashing using the method on umi digi forum : http://umidigi.com/forums/topic/how-to-restore-rom-version-3-03-2/ ... preloader was unticked, and when i tried firmware uopgrade option...nothing happened, and the phone was dead after that.

thepopos said:
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
Click to expand...
Click to collapse
I managed to make it boot.
The problem is I have twrp and some chinese recovery . And I cant go back to stock.
Fastboot cant flash recovery for some reason ... so I can go back to rootjoy.

use adb side load an try to flash a working rom, the original one from umi website or emui.

can you get in recovery mode? volume (+ or - try both) and power button for some seconds
if yes go adb side load, (check google) and transfer an original rom, then flash it again in the recovery

My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?

Pospa420 said:
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Click to expand...
Click to collapse
If the system is unstable with popups etc or with damaged partitions you can get past that with TWRP.
Boot into recovery Wipe/Advanced Wipe. Then after that is completed, without rebooting, Format Data. That should sort out your partitions.
Then Install ROM from the recovery. It will need to be on the device. If your new ROM is not already there plug in a USB lead and transfer the zip file from your pc.
If you want to re-install your backup, do that instead.
If that doesn't work Backup in TWRP, even though there is no system. Then copy your Nandroid backup (must have been made via TWRP) and paste into the same folder as the Backup you just made, overwriting if asked.
I have had to do all this myself!
Good luck

Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.

It looks like memory become write-protected...

YrP said:
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
Click to expand...
Click to collapse
Hi
Did you Advance Wipe and Format Data?
I found that worked.
Alternatively, you could use Rootjoy to put just about any ROM on. CM 12.1 works ok.
Once you have a stable installation, install a custom recovery like TWRP 2.8.7 from Needrom. I used Mobileuncle, an app from the Playstore. However, I looked just now and it doesn't seem to be available.
I have tried Rashr, but couldn't get it to work.
Once you have it all stable you can flash the ROM you really want via TWRP.
Good luck

Advance Wipe and Format Data or flashing new stable ROM via TWRP did not work for me. The same result- unable to mount /system.
Rootjoy and Mobileuncle could be used if phone is working. My phone works in recovery mode only.
I tried to flash different recoveries but did not find the way to do this. As I wrote, Sp Flash Tool, Fastboot and Adb Sideload did not make any changes to my recovery. I think, flash new recovery will help if I found the way)
Or if I discover the method to test and\or repair /system partition from PC
But thank you for answer)

@YrP
Rootjoy works from your pc

Yes, Rootjoy- works)
But for establish connection phone must work too.
And not in recovery mode.

@YrP
I have already done all this with my daughter's Zero.
However, it's in bits at the moment while we wait for a part from China. So I can't go through the process with you live, step by step.
I am in the UK.
If you send the phone to me I will try and fix it for you.
PM me if you want to go ahead and I will let you have my address.

I am in Ukraine, it is too far from UK)
I will keep trying to find the way to fix it by myself.
But thank you very much for your attention and advices.

@YrP
I have got my daughter's phone back together and fixed (mostly).
Did you manage to get your Zero going?
Sent from my Nexus 4 using XDA-Developers mobile app

@goldbear
My UMI is still bricked(
It is flash memory problem, I think.
I am trying to find the tool to remap internal memory, to move SYSTEM part to other physical place. But did not find it yet.
What was your way?

Zero stutters, processes crash or the phone will not boot into System
Have you already tried a Factory Reset or re-installed the ROM?
What can you do?
You could try the following. However, if your phone blows up, orders a takeaway or elopes with your girl-friend, please don’t blame me.
1. Provided you already have TWRP custom recovery installed and your phone is powered down boot into Recovery: hold the volume down and power buttons until the Zero logo appears then let go
2. Select Wipe/Advanced and select Dalvik Cache, System, Cache and Data. Slide to execute
3. Select Format Data/ type yes and slide to execute
4. Reboot into Recovery without installing a new ROM
5. Select Backup, choose SD card rather than internal storage and give the file a memorable title like Blank Backup and date. Select Boot, Logo, Recovery and Uboot. Slide to execute
6. The next step requires you to have a Nandroid backup made via TWRP already made of a stable ROM. If it isn’t stable or you don’t have one I have attached a clean backup below. It’s derived from Cyanogen Mod 12.1. This is based on Lollipop 5.1, with Gapps and rooted. I have found this to work. As the title of the file suggests, it’s a factory reset, ie no personal data included. Download it to your pc unzip and save it.
7. Connect your phone to your pc via USB cable and open Windows Explorer
8. Find your stable backup or the one below and drill down until you see the folder with 15 files, starting with data.info and ending with uboot.emmc.win. Select all and Copy.
9. Open another window and find the TWRP folder on the SC card of your phone. Drill down to the same folder containing similar files as to step 8 above. Click in folder and Paste. When prompted select Copy and Replace, all and Ok
10. If your pc doesn’t show your phone and the SD card, in recovery select Mount and USB storage.
11. In Recovery select Restore and the Blank Backup (or whatever file name you gave it, now populated with usable ‘data’). Slide to execute
12. Give it time to load and boot up
13. You should be good to go!
If you don’t like CM 12.1 installing a new Launcher from the Playstore, like Cheetah will make it run smoother. Everything after that is down to you.
Of course, you could flash another ROM via TWRP
The backup below was made via TWRP 2.8.6. This is also attached below. You can install this via a previous version of TWRP as an image. Unzip it first.
Assuming this doesn’t wreck your phone and you like the guide please click Thanks below.
https://drive.google.com/file/d/0ByoLjFrSKxLwc01UUWZBZEQtbWs/view?usp=sharing
https://drive.google.com/file/d/0ByoLjFrSKxLweGhqNGJuVGV1a0U/view?usp=sharing

ZE550KL bricked ?

Hi,
I was at work Sunday night when the phone offers me an update, not wanting to lose my data I re-growth that has Tuesday morning during my last round (which takes me roughly 25/30 minutes ). So I run the update and go round when I come back I have the phone on the screen of blocked boot ...
Considering I'm looking since yesterday, I have already tried many tutorials that did not work.
I tried everything flashed like to start from zero but nothing worked. I have every time a message like: failed can't install image not signed OR dtb not found ...
I have access at fastboot and nothing else.
There's way to save this phone I for 3 months or it is good to wedge a table ?
Thx in advance
edit :
ok, i do this
http://www.asus-zenfone.com/2015/10/how-to-root-asus-zenfone-2-laser-ze500kl.html
and this
http://forum.xda-developers.com/showpost.php?p=66894780&postcount=5
and i have now acces to recovery mode
Edit 2 :
http://www.asuszenfoneblog.com/2015/04/how-to-flash-asus-zenfone-2-via-adb.html with the firware Version V13.10.7.1(Andriod M) https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
but after reboot i have the message : ERROR : Can't load invalid boot image !
i lose th recovery and i can't flash the boot ( remote dtb not found ) ...
edit 3 :
the phone has restarts with the original firmware but I have so manipulated that I do not know what I did
I remember using the following links : http://www.asus-zenfone.com/2015/09/how-to-flash-asus-zenfone-2-laser.html ans the stock rom for 550KL
when I reinstall the rom of origin, such would not boot and I had to boot the mod_boot.img picture (Flashtool boot mod_boot.img), which launches the phone and now more problem. It remains to remove the root which should be easier than the rest.

@Genux888 This link takes to ZE500KL's firmware downloads https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
Your phone model is ZE550KL but you first attempted to flash MM ROM of ZE500KL
Thats why you got error: invalid boot.img and you lost recovery.
I don't know where you got mod_boot.img from. Neverthless, here's the simplest fix-
1. Download ZE550KL's Stock_boot_recovery.zip
This zip contains stock signed recovery.img and boot.img. Extract it and copy both .img files to the folder where you have adb and fastboot files.
Download correct firmware for your ZE550KL of the correct SKU. You can find your SKU on your phone's box.
WW SKU : Download ZE550KL's firmware v1.17.40.1531 for WW SKU only
Let me know if your phone's SKU is not WW
Copy the firmware zip (UL-Z00L-WW-1.17.40.1531-user.zip) to your external sd card.
2. Connect your phone to computer and Reboot phone to fastboot mode.
3. Now run the following commands
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot oem reboot-recovery
3. Third command should reboot your phone to recovery mode.
Now, in recovery mode-
A) select "wipe cache partition" then select yes
B) select "apply update from sdcard" then select "UL-Z00L-WW-1.17.40.1531-user.zip" and finally select "yes"

stuck at verifying update package

MITHI-N said:
stuck at verifying update package
Click to expand...
Click to collapse
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.

sziraqui said:
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
Click to expand...
Click to collapse
Hi can you put a link to OTA, I tried searching for it but could only get the full firmware from the asus website.

sziraqui said:
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
Click to expand...
Click to collapse
Removed, putback battery & followed all steps, successfully installed 1531 rom
Then upgraded to Asus Marshmellow, Everything working.
But when I try to clear data & cache from new recovery I get couple of errors stating unable to mount /asdf & few other things

MITHI-N said:
Removed, putback battery & followed all steps, successfully installed 1531 rom
Then upgraded to Asus Marshmellow, Everything working.
But when I try to clear data & cache from new recovery I get couple of errors stating unable to mount /asdf & few other things
Click to expand...
Click to collapse
I did the following-
Input: "Wipe cache partition"
Output: E: unable to mount /asdf (invalid argument)
Input : "mount /system"
Input: "wipe cache partition"
Output: Cache wipe complete
E: unable to mount /asdf
E: Can't open /asdf/recovery/last_log
This shows that I am able to wipe cache after mounting /system (though it doesnt make sense)
I didn't wipe data as I don't want to setup my device again. You may try if wiping data works after mounting /system. Alternatively, you can flash stock 1.15's recovery (download from post #2)
and flash in fastboot mode using
Code:
fastboot flash recovery recovery.img
(assuming you recovery.img file is present in the folder where you have fastboot files)
And, here on XDA, we hit "thanks" good button if a post was helpful to us.

Sorry to reply so late but I managed to unlock my phone has put version 5.0, the update to 6.0, UNLOCK the boot, root the phone and install the TWRP may close 2 or 3 hours after my last post.
thank you.

i really like it when people post all the steps taken and links in their problem posts.
this is great.
(no, that is NOT sarcasm)

The best solution out there for zoold 550kl
This is the best answer for the rooted asus zenfone 2 550kl for upgrading to marshmellow stock .Thank you...

Help
@sziraqui My phone is in a bootloop and I honestly know pretty much nothing as to how to fix it.. I know it's the ZE551KL, but that's pretty much it. Is there any way youcan help me out? thanks in advance

Stock recovery for MM?
Anyone have stock recovery for MM upgrade from LP?

Problem Not Solved
I am Also facing same type of problem but the difference is :
- I am only able to enter fastboot mode only when i am connecting my phone to pc via datacable.
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..

I've seen you've tried a lot.
I'd suggest you try this... As long as you can send your phone to fastboot and can pc/add your way through you'll be able to unbrick it. This takes a bit of time as you'll be dealing with two huge downloads (system.img and stock rom) but it should do the trick.
Follow the guide here:
https://www.asus.com/zentalk/thread-80274-1-1.html
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
utkarshdev20 said:
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
Click to expand...
Click to collapse
The guide at https://www.asus.com/zentalk/thread-80274-1-1.html talks about flashing boot.img first then a huge (1.7GB) system.img second then recovery.img last.
So it could mean the boot.img and system.img needs to be dealt with first before you have any chances of getting your recovery to work.
Follow the steps closely, I've been able to fix a brick with it twice.

NO way to boot into Recovery or Fastboot!!!!!!!!!!!!!
Phone got bricked!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
When connected to PC(Windows), I only get 8 local disk partitons (ext4) asking to format!!!!!!!!!!!
And one with image partition(BOOT)
What to do now to regain access to either fastboot or to recovery!!!!!!!!!!!!!!!!!
PLEASE Reply!!!!!!!!!!!!!!!!!!

utkarshdev20 said:
I am Also facing same type of problem but the difference is :
- I am only able to enter fastboot mode only when i am connecting my phone to pc via datacable.
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
Click to expand...
Click to collapse
I can help you but first i neef some info about your phone..how it got bricked?was your phone rooted?

[guide] [root] [oreo&pie] [jeter/aljeter] [twrp, decrypt, magisk] [stock firmware]

* 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

Database Users

welcome