Develop Bugs

[Q] A100 won't mount emmc or SD Card

My a100, which was running Flex, froze up night before last and I powered down, thinking that would take care of it like it has before. Wrongo! Now all I can do is boot into recovery. Will not mount anything in the system. Any help to fix this would be greatly appreciated.

Try erasing CWM recovery (fastboot erase recovery), place the update.zip (of the official rom) on your external SD card (via card reader, etc.), then attempt to boot into recovery (it should flash the rom).

Theonew said:
Try erasing CWM recovery (fastboot erase recovery), place the update.zip (of the official rom) on your external SD card (via card reader, etc.), then attempt to boot into recovery (it should flash the rom).
Click to expand...
Click to collapse
That's the thing, I can't get it to mount anything including the external sd when I boot into recovery.

j.price said:
That's the thing, I can't get it to mount anything including the external sd when I boot into recovery.
Click to expand...
Click to collapse
CWM recovery will not be there to do that. Maybe the default will be able to.

Theonew said:
CWM recovery will not be there to do that. Maybe the default will be able to.
Click to expand...
Click to collapse
If you have adb pull the recovery log that will show any errors in the fileaystems. I woukd say dump it but if it cant mount external sd that wont work. You verified failed mounting in the mounts menu in recovery?
Tapatalked from my Galaxy S II.

That is correct. Will not mount anything other than the recovery partition.

j.price said:
That is correct. Will not mount anything other than the recovery partition.
Click to expand...
Click to collapse
And did you try adb? Try it from whatever pc you used to get cwm or twrp or whatever recovery on there. It's not really possible for it to only mount recovery or you wouldn't boot at all. In cwm go to mounts and make sure your internal sd and /data does or does not mount. And try to get that log it'll pretty much solve it without random flashing.
Tapatalked from my Galaxy S II.

Won't pull the logs, but I can show you pictures I took of the tablet in Recovery with the errors. Also, if I did what was suggested and tried to run a Stock Recovery what would happen if I did that and went back to full stock or atleast attempted to

j.price said:
Won't pull the logs, but I can show you pictures I took of the tablet in Recovery with the errors. Also, if I did what was suggested and tried to run a Stock Recovery what would happen if I did that and went back to full stock or atleast attempted to
Click to expand...
Click to collapse
I need to see the log not the error on screen, that just says error I need to see what causes it, in the log.
If you go back to full stock its like how Acer intended. You'll need to root and unlock the boot loader again and install cwm or twrp again, if you choose to. I'm not one to throw flashes at a device that isn't working correctly but sometimes that's the only fix. Still haven't mentioned if adb works. If you want to send pics I guess go into mounts and try to mount internal SD or external SD and take a pic of the error. Go ahead and post or send the pics of the error you took already, may explain things enough there.
Tapatalked from my Galaxy S II.

Unintentionally misspoke. Tablet is recognized by ADB in recovery but will not pull the log to my PC. That is why I offered the pictures. But as the log is better, could you just reconfirm first the commands needed to pull the logs via ADB> Maybe I am screwing something up. This is the first time I have had any major issues with Android.

j.price said:
Unintentionally misspoke. Tablet is recognized by ADB in recovery but will not pull the log to my PC. That is why I offered the pictures. But as the log is better, could you just reconfirm first the commands needed to pull the logs via ADB> Maybe I am screwing something up. This is the first time I have had any major issues with Android.
Click to expand...
Click to collapse
Ok if ADB is working then we can fix this. The command is
adb pull /cache/recovery/last_log > last_log
This will pull the log to whatever directory your ADB is launched from, if you have the SDK then it will be in your platform-tools folder. You can either post it here, or send it to me directly.
On your device, in recovery (of course at this point lol) attempt to mount each partition, cache, system, data, internal sd, external sd. Then run that command from your command prompt/terminal depending on what OS you use.
My email is [email protected], you can use this for gtalk if we need to start throwing commands at it, that will be the easier way vs posting and waiting. You can also email me that log directly if you choose. Once this is resolved you or I can post the fix back here for others should they need it.
Once this is done hit me up on gtalk if you can, usable through the gmail website as well, I have to make a phone call or 50 so I won't be checking here for a little bit.

adb gives me the error
C:\Program Files\Android\android-sdk\platform-tools>adb pull /cache/recovery/las
t_log > last_log
The system cannot find message text for message number 0x5 in the message file f
or System.
Click to expand...
Click to collapse
Now it is saying
remote object 'cache/revocery/last_log' does not exist
Click to expand...
Click to collapse

I'm also experiencing this issue where Relix rom froze on me and now recovery can't mound /sdcard/ Any ideas?

A100 won't mount emmc or SD Card
any solution to this??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I also had this problem, most forums say its a bad emmc. I chatted with an acer rep before sending it in, they received it yesterday, hopefully they wont give me problems because of the "unlocking"
UPDATEThey fixed it!! Only thing I can advise is to get on the site and chat with a rep to confirm that its a bad emmc, maybe they dont even boot it up once thats on the ticket

brick
sorry for my bad english, i have this problem im from venezuela and here the guarantee not cover me i send to acer venezuela and his say that is the logic card, why you fix you brick tablet? plsss i need help im trying to solve this brick since 4 month am i love mi tablet!!

etoxz said:
sorry for my bad english, i have this problem im from venezuela and here the guarantee not cover me i send to acer venezuela and his say that is the logic card, why you fix you brick tablet? plsss i need help im trying to solve this brick since 4 month am i love mi tablet!!
Click to expand...
Click to collapse
Its been verified there is a fault in the emmc. There is currently no way to repair it other then sending it to Acer, sorry to say. Acer locked us out of what we need to fix this.
Tapatalked from my Galaxy S II.

I had a similar issue it would load cwm or twrp but it would not load a recovery. it kept saying that files were missing i had to send it back for repair they replaced the main board it is an issue with the hardware not the software. Mine just froze then it died. sorry man. I can say mine was unlocked and they covered it under warranty.

pio_masaki said:
Its been verified there is a fault in the emmc. There is currently no way to repair it other then sending it to Acer, sorry to say. Acer locked us out of what we need to fix this.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
So, has anyone experienced this emmc fault outside of the Relix rom? I'm just curious--I had my tablet for 10 months and this rom for 1 week, and this happened. I loved the rom, but will definitely stay away from it if it's breaking emmc. (I'm a total noob -- not sure if the issue with emmc is hardware vs. software).

eatnosenuggets said:
So, has anyone experienced this emmc fault outside of the Relix rom? I'm just curious--I had my tablet for 10 months and this rom for 1 week, and this happened. I loved the rom, but will definitely stay away from it if it's breaking emmc. (I'm a total noob -- not sure if the issue with emmc is hardware vs. software).
Click to expand...
Click to collapse
Mine happened on a personal build of CM10, other's on CM9, etc. Its a fault with the emmc firmware, not ROM or Kernel dependant.

Messed up kernel install

I wanted to try Merruk's kernel so I download the 4 files that are to be used. I flashed KernelUpdate.zip first and rebooted twice. A friends required urgent help so i didnt continue the process. After waking up in the morning, I decided to continue the process. I flashed the next file i was supposed to after formatting /cache and Dalvik cache.
Now i cant boot. The phone stay stuck at the galaxy y splsh screen. I can boot into recovery. It says /cache/recovery/log cant be open. Also, it cant mount /cache/recovery/last_log
Cant open /cache/recovery/last_log
I have ADB but it seems I didnt enable the USB debuggin option. If that was possible, I could have flashed a stock kernel and tried again.

Are you sure you cant enter download mode (HOLD power+home+volume DOWN)? Remove backcase if you have, remove the battery , keep aside for 5 min, then put it back and hold the download mode combination

DiGtal said:
I wanted to try Merruk's kernel so I download the 4 files that are to be used. I flashed KernelUpdate.zip first and rebooted twice. A friends required urgent help so i didnt continue the process. After waking up in the morning, I decided to continue the process. I flashed the next file i was supposed to after formatting /cache and Dalvik cache.
Now i cant boot. The phone stay stuck at the galaxy y splsh screen. I can boot into recovery. It says /cache/recovery/log cant be open. Also, it cant mount /cache/recovery/last_log
Cant open /cache/recovery/last_log
I have ADB but it seems I didnt enable the USB debuggin option. If that was possible, I could have flashed a stock kernel and tried again.
Click to expand...
Click to collapse
just flash back to stock via odin
i advise you not to use the "ext4.zip"
use only the system 1.0.8 zip <-- extract to sdcard

hitme987 said:
Are you sure you cant enter download mode (HOLD power+home+volume DOWN)? Remove backcase if you have, remove the battery , keep aside for 5 min, then put it back and hold the download mode combination
Click to expand...
Click to collapse
So THATS how you enter download mode
leodasal2 said:
just flash back to stock via odin
i advise you not to use the "ext4.zip"
use only the system 1.0.8 zip <-- extract to sdcard
Click to expand...
Click to collapse
Well, I flashed my backup and it rebuilt the /cache. All is fine. Thank you.
A new problem has risen. I was trying to flash Creed v4.0.
I had Merruk's Kernel.
I did a reset and tried flashing the ROM. It started wiping the /system partition and came across with an error in /boot(Error 7). Im guessing its due to the kernel. It aborted.
I tied again by doing a data reset again thinking that there might have be a random error in the wiping process.
It started cleaning /data. The progress bar never moved. I waited for 15 mins and did a battery pull. When i try to boot into the recovery mode, it stays at the Galaxy Y logo.
Dowload mode works. Adb doesnt detect my device though. I wonder why.

DiGtal said:
So THATS how you enter download mode
Well, I flashed my backup and it rebuilt the /cache. All is fine. Thank you.
A new problem has risen. I was trying to flash Creed v4.0.
I had Merruk's Kernel.
I did a reset and tried flashing the ROM. It started wiping the /system partition and came across with an error in /boot(Error 7). Im guessing its due to the kernel. It aborted.
I tied again by doing a data reset again thinking that there might have be a random error in the wiping process.
It started cleaning /data. The progress bar never moved. I waited for 15 mins and did a battery pull. When i try to boot into the recovery mode, it stays at the Galaxy Y logo.
Dowload mode works. Adb doesnt detect my device though. I wonder why.
Click to expand...
Click to collapse
There is no Creed 4 for galaxy y...re flash to stock and flash Creed 3.5

I cant boot into recovery. How do I use the download mode to do so?
Edit: I installed the correct drivers for my phone while it was trying to restart(it didnt ofcourse). I booted into download mode and connected odin. Odin is not showing any signs of it connecting to the phone.
Edit2: Got it working(v1.85). I need bootloader, CSC, Modem and phone tar balls. i downloaded 2 rar files but they dont have Phone and bootloader tar balls

DiGtal said:
I cant boot into recovery. How do I use the download mode to do so?
Edit: I installed the correct drivers for my phone while it was trying to restart(it didnt ofcourse). I booted into download mode and connected odin. Odin is not showing any signs of it connecting to the phone.
Edit2: Got it working(v1.85). I need bootloader, CSC, Modem and phone tar balls. i downloaded 2 rar files but they dont have Phone and bootloader tar balls
Click to expand...
Click to collapse
Hi. Make sure you have the the drivers installed correctly. Try the one from this thread. http://forum.xda-developers.com/showthread.php?t=961956 credits to SamHaLeKe. if you have an existing driver uninstall if first, reboot your pc then install the new one. you can download stock ROMS from this thread and its complete. http://forum.xda-developers.com/showthread.php?t=1465800 credits to Doky73. If everything is ok when your phone is in download mode ODIN should be able to detect it.

Thank you all!
You have been of great help.
My phone is running fine now.
Just waiting for Merruk's kernel to get overcloking capability.

DiGtal said:
Thank you all!
You have been of great help.
My phone is running fine now.
Just waiting for Merruk's kernel to get overcloking capability.
Click to expand...
Click to collapse
Nope. There is no stable overclocking capability yet and merruk is outdated. I recommend to use kuros kernel or savies rev 73

Phone Not booting
hitme987 said:
Nope. There is no stable overclocking capability yet and merruk is outdated. I recommend to use kuros kernel or savies rev 73
Click to expand...
Click to collapse
Hello,
I have same problem,When I want to Install Stock ROM with ODIN error shows ""
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
""
and when I go to "Android System Recovery" (vol up + home bot + power bot) and choose Wipe data/factory reset OR wipe cache partition, Error Show "Failed to mount /Cache (invalid argument) " & "Can't mount /cache/recovery/lastlog"
What should I do?

[ROM][TMO][ODEXED/DEODEXED][4.4.2][HTC 1.57 OTA] Stock+ 5/20/2014

Stock+
The mission of this ROM is to keep fairly close to the stock experience while unlocking certain features and limitations.
Furthermore my plan is to remove useless or intrusive customizations done by the manufacturer or carrier.
The kernel will have few commits, but those that are there will be for stability, battery life.
Click to expand...
Click to collapse
FEATURES
Prerooted.
Deodexed.
APNs are unlocked.
Preload data is restored.
Zipaligned.
CarrierIQ removed
**Stock kernel until I get time to pull the latest source.**
wp_mod for stock kernel thanks to @flar2
Insecure ADB (Always runs as root).
Tether Enabled
Click to expand...
Click to collapse
INSTALL
Data wipe is not required if you are coming from stock, BUT if you do wipe data do it BEFORE flashing the ROM.
Wipe /data/... or not.
Flash with TWRP.
Go into APNs and change the Default from IPV6 to IPV4.
Click to expand...
Click to collapse
Again, Thanks to @flar2 for his wp_mod.
DOWNLOAD
Latest:
HTC 1.57 OTA
OLD:
Stock+v1.01 SHA1: bc39bda6f656e323ea725f77dca0c4a3212d1044
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please do not PM me with images of farm equipment.

CHANGELOG:
1.01 -> 1.1 (unreleased)
Added init.d support.
Full write perms to external SD.
Rebuilt framework-res with the APN changes cooked in.
Email without exchange policy enforcement. (This will probably be a flashable option.)
1.0 -> 1.01
Fixed an issue with a symlink breaking wifi. Thanks to @Andromorphone for sitting on IRC for testing the fix for this with me.
1.0
Initial release.

Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse

Thank you so much for this!!
EDIT: Are the links broken?
EDIT 2: Downloading now. Thanks again!
Sent from my HTC One M8

VolcanicSkunk said:
Thank you so much for this!!
EDIT: Are the links broken?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
They were indeed. It's fixed now.
Annnd It's back to bed for me. I'll repost the mega mirror in the morning.

EDIT 2: This issue was solved. Did not brick my phone. Didn't want this post to scare anyone away from a great ROM.
Think I just bricked my phone flashing this. Downloaded, confirmed hash sum, flashed via TWRP 2.7.0.2. Now phone is stuck at HTC splash screen. No amount of holding the power button will turn it off.
EDIT: Got a tip that said to hold the power and volume down buttons under a light source to try to get it to boot to bootloader. No luck.

VolcanicSkunk said:
Think I just bricked my phone flashing this. Downloaded, confirmed hash sum, flashed via TWRP 2.7.0.2. Now phone is stuck at HTC splash screen. No amount of holding the power button will turn it off.
EDIT: Got a tip that said to hold the power and volume down buttons under a light source to try to get it to boot to bootloader. No luck.
Click to expand...
Click to collapse
Hold power button and volume up, untill the phone shuts off

LIL_ROOKIE said:
Hold power button and volume up, untill the phone shuts off
Click to expand...
Click to collapse
Got pretty much the same advice in a thread I made in Q&A. Thanks for the tip though. That's exactly what I had to do. Don't know if the light source makes a difference though.
Finally got it to work. I had to hold volume up + power under a light source to get the phone to reboot. When the screen turned black I changed to the volume down while still holding the power button. This booted me to HBOOT. Then I was able to select recovery and boot there just fine. I am now restoring to my stock backup.

VolcanicSkunk said:
Got pretty much the same advice in a thread I made in Q&A. Thanks for the tip though. That's exactly what I had to do. Don't know if the light source makes a difference though.
Finally got it to work. I had to hold volume up + power under a light source to get the phone to reboot. When the screen turned black I changed to the volume down while still holding the power button. This booted me to HBOOT. Then I was able to select recovery and boot there just fine. I am now restoring to my stock backup.
Click to expand...
Click to collapse
Well, that certainly should not have happened, I am downloading from the link right now. I'll see if I can reproduce the error.
*EDIT*
So, I just did both a dirty flash, and a flash with a /data/ wipe. (A FULL data wipe, sadly.)
Phone booted fine in both cases.
Are you flashing over from a completely stock ROM?
What is your s-off satatus?
If you didn't flash from a fullty stock ROM, and did not wipe /data/ then the system was probably choking on a different SQLite schema. Doing a /data/ wipe before flashing the zip should do the trick.

Fenny said:
Well, that certainly should not have happened, I am downloading from the link right now. I'll see if I can reproduce the error.
*EDIT*
So, I just did both a dirty flash, and a flash with a /data/ wipe. (A FULL data wipe, sadly.)
Phone booted fine in both cases.
Are you flashing over from a completely stock ROM?
What is your s-off satatus?
If you didn't flash from a fullty stock ROM, and did not wipe /data/ then the system was probably choking on a different SQLite schema. Doing a /data/ wipe before flashing the zip should do the trick.
Click to expand...
Click to collapse
Hmmm.... That's strange.
I am coming from the stock operating system. I haven't restored the preload data yet. That was one of the reasons I was flashing this (so I didn't have to restore it manually). I am S-Off using Dev Unlock, TWRP + SuperSU & Root, then Firewater.
Here is my flash process:
Download from link in OP with phone to internal storage (/storage/emulated/legacy/download/)
Confirm hash using Hash Droid from Play Store
Reboot to Recovery using Quick Boot from Play Store (TWRP 2.7.0.2)
Select Wipe
Select Advanced
Checked options for system, data, Dalvik cache, cache
Slid to wipe
Repeated wipe with same options
Pressed home button
Selected Install
Chose internal memory
Navigated to /download/
Installed ROM
Since I'm at work I stopped paying attention to the screen after that since last night I had successfully flashed ViperOneM8. I didn't like the UI changes to ViperOneM8, so I restored my stock TWRP backup.

VolcanicSkunk said:
Hmmm.... That's strange.
I am coming from the stock operating system. I haven't restored the preload data yet. That was one of the reasons I was flashing this (so I didn't have to restore it manually). I am S-Off using Dev Unlock, TWRP + SuperSU & Root, then Firewater.
Here is my flash process:
Download from link in OP with phone to internal storage (/storage/emulated/legacy/download/)
Confirm hash using Hash Droid from Play Store
Reboot to Recovery using Quick Boot from Play Store (TWRP 2.7.0.2)
Select Wipe
Select Advanced
Checked options for system, data, Dalvik cache, cache
Slid to wipe
Repeated wipe with same options
Pressed home button
Selected Install
Chose internal memory
Navigated to /download/
Installed ROM
Since I'm at work I stopped paying attention to the screen after that since last night I had successfully flashed ViperOneM8. I didn't like the UI changes to ViperOneM8, so I restored my stock TWRP backup.
Click to expand...
Click to collapse
I'll try again following your process precisely. Perhaps dexopt is cowardly refusing to build the dalvik cache when /cache/ has been wiped. (This happens from time to time if there was a bad deodex.) I'll let you know how it goes.

Fenny said:
I'll try again following your process precisely. Perhaps dexopt is cowardly refusing to build the dalvik cache when /cache/ has been wiped. (This happens from time to time if there was a bad deodex.) I'll let you know how it goes.
Click to expand...
Click to collapse
Thanks so much for checking into it! I'll try it again tomorrow when I've got a lot more time on my hands. I'm just too used to flashing on the fly.

VolcanicSkunk said:
Thanks so much for checking into it! I'll try it again tomorrow when I've got a lot more time on my hands. I'm just too used to flashing on the fly.
Click to expand...
Click to collapse
Well, I did exactly the same thing as you did. I even went and downloaded the same rebooter app. The phone booted with no issue.
@Andromorphone Come back me up here. I KNOW you got it booting as well.

Whelp, I really must have done something screwy. Lol. Like I said, I'll try it again tomorrow (or late tonight if I get a chance). I'm just glad that everything works! I was hoping that no one else had the same problems I did. When I try it again I'll post back with my results. Hopefully it goes well without any hitches.

VolcanicSkunk said:
Whelp, I really must have done something screwy. Lol. Like I said, I'll try it again tomorrow (or late tonight if I get a chance). I'm just glad that everything works! I was hoping that no one else had the same problems I did. When I try it again I'll post back with my results. Hopefully it goes well without any hitches.
Click to expand...
Click to collapse
Ha! Figured it out. Disable zip signature verification. It looks like it didn't sign right but as long as the sha1 matches you should be fine.
*EDIT*
The link in the OP has a valid signature again.

Fenny said:
Well, I did exactly the same thing as you did. I even went and downloaded the same rebooter app. The phone booted with no issue.
@Andromorphone Come back me up here. I KNOW you got it booting as well.
Click to expand...
Click to collapse
indeed, flashed the initial v1.0 and subsequent version 1.01 and never had any issues booting. in fact it's working great, and very happy to be rid of carrierIQ and to have working tether.
Sent from my HTC One_M8 using Tapatalk

I am able to replicate this freeze several times.
Steps:
Downloaded ROM onto PC
Powered phone off
Ejected MicroSD card
Plugged MicroSD card into computer (USB 2.0)
Checked SHA1 hash via MD5 & SHA Checksum Utility 2.1
- Returned "SHA-1 Hash matched."
Transferred ROM to root of MicroSD card
Checked SHA1 hash again
- Returned "SHA-1 Hash matched."
Properly ejected MicroSD from PC
Reinserted MicroSD card into my M8
Booted phone and waited for it to settle
Connected phone to PC via stock USB
Confirmed Connection using "adb devices"
Rebooted phone to recovery using "adb reboot recovery"
In recovery performed the same wipe process outlined earlier
- Checked: Dalvik Cache, System, Cache, Data
- Repeated
Installed ROM from MicroSD card
Pressed Wipe Dalvik/Cache button
Phone rebooted to splash. Hung for 2+ minutes.
Rebooted to recovery via HBOOT.
Wiped again. This time included internal memory.
Installed ROM from MicroSD card
Received an Install Successful message
Pressed Reboot System
Received a warning there was no OS installed
Accidentally pressed reboot anyway
Prompted to install SuperSU since it wasn't detected (lol)
At hanging splash screen rebooted to HBOOT then recovery again
Performed single wipe
Installed from MicroSD card (again)
Install process took significantly longer than prior
Received Install Successful message
Pressed Reboot System
Screen froze while Reboot System button was highlighted
Phone booted through splash to boot animation
I am now sitting at the Welcome screen
I'm not sure if the fact that I was wiping a second time was causing some issue, but this was just a weird process. lol. After the first or second hang (I don't remember which) I exported the recovery log to the MicroSD card. I attached it to the post so hopefully it might shed some light as to what was going on.
Everything seems to have worked though. I'll go through the setup process and get back with you if there are or aren't any issues.
Thanks again for going through the same process I went through so I knew it was probably a fluke. Hopefully this is an isolated incident.
Anyway... :highfive:

VolcanicSkunk said:
*snip*
In recovery performed the same wipe process outlined earlier
- Checked: Dalvik Cache, System, Cache, Data
- Repeated
Installed ROM from MicroSD card
Pressed Wipe Dalvik/Cache button
Phone rebooted to splash. Hung for 2+ minutes.
Rebooted to recovery via HBOOT.
Wiped again. This time included internal memory.
Installed ROM from MicroSD card
Received an Install Successful message
Pressed Reboot System
Received a warning there was no OS installed
*snip*
Click to expand...
Click to collapse
Okay, I think there may be some sort of problem with TWRP and mounts/storage.
This tells me that your system partition was completely blank upon the last boot reboot:
/system | /dev/block/mmcblk0p45 | Size: 2641MB Used: 42MB Free: 2599MB Backup Size: 42MB
I have two working theories at the moment. The first is that IO was hanging when reading from your ext-sd, and then the system locked up IRQ style.
The second I think is more likely and involves the /system/ mount point. I wonder if after the second wipe, the /system/ partition was not actually mounted. It would mean that the script would flash to the tmpfs that is created for the root partition, and the files would go precisely nowhere.
The second could be proven by looking at the /data/preloads folder right after a non-booting scenario. If it exists and there are files there, then the data partiton mounted just fine, while the system partition did not.
*EDIT*
Battery is looking gooood.

Anyone not able to send or receive mms when apn switched to ip4/ip6?
Sent from my HTC One_M8 using Tapatalk

Same here
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Dead Device

I have an issue that I cannot for the life of me fix. Last night my wife’s phone received the OTA update and her phone would not restart after that. Total B.S. move on ASUS’s part not to pull that update knowing the issues people were having. But anyways, here’s the rundown. I can boot into bootloader mode but I cannot get into stock recovery. I can, through a certain method get into CWM recovery and I can see the external SD, but I get errors when I try to flash an update or another entire OS. I’ve tried to bypass signature verification also and still cannot get anything to install. ADB will not sideload because it does not find my device, but the method of getting into CWM recovery is done through ADB so I’m confused there. Never have I had such a tough time restoring a bricked device. Samsung, no problem. Huawei, no problem. This POS I’m about ready to throw in the pool and call it a day. Does anyone have any suggestions?

Try flashing CN version and dont forget to disable zip signature and format everything before flashing
Sent from my ASUS_Z00AD using Tapatalk

LiRi2000 said:
Try flashing CN version and dont forget to disable zip signature and format everything before flashing
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7

MikeyLee said:
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
Click to expand...
Click to collapse
Open ROM archive with app (for example WinRAR),
navigate to META-INF\com\google\android
unpack updater-script
open unpacked updater-script with any text editor (I use Notepad++)
remove first line with "(!less_than_int..."
save file
put unpacked file back in archive overwriting it
put rom package on sdcard
flash it via recovery
btw, Updating IFWI takes a 10 or more minutes so wait and don't panic

I'll try that when I get home

MikeyLee said:
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
Click to expand...
Click to collapse
Try and install twrp recovery through adb you can find how in the forum....if you can install it it will be much easier to flash a room.
Sent from my ASUS_Z00AD using Tapatalk

LiRi2000 said:
Try and install twrp recovery through adb you can find how in the forum....if you can install it it will be much easier to flash a room.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Nothing will flash through adb

meciu99 said:
Open ROM archive with app (for example WinRAR),
navigate to META-INF\com\google\android
unpack updater-script
open unpacked updater-script with any text editor (I use Notepad++)
remove first line with "(!less_than_int..."
save file
put unpacked file back in archive overwriting it
put rom package on sdcard
flash it via recovery
btw, Updating IFWI takes a 10 or more minutes so wait and don't panic
Click to expand...
Click to collapse
Still doesnt work. E: error in external sd blah blah blah, same as everything else.

@MikeyLee I had the same problem this morning, i spent a lot of time to fix this, i couldn't access the recovery, i tried to flash thetered recovery and do factory reset, flash again the rom, but nothing.
To fix the bootloop i just rebooted in fastboot mode, launced the adb from pc and format cache partition, thats all.
And the strange thing is that i didn't loose the data, Although I did the factory reset, that's mean maybe a corrupted cache partition that maked impossible to flash anything or do factory reset.
Sent from my ASUS_Z00AD using Tapatalk

Hank87 said:
@MikeyLee I had the same problem this morning, i spent a lot of time to fix this, i couldn't access the recovery, i tried to flash thetered recovery and do factory reset, flash again the rom, but nothing.
To fix the bootloop i just rebooted in fastboot mode, launced the adb from pc and format cache partition, thats all.
And the strange thing is that i didn't loose the data, Although I did the factory reset, that's mean maybe a corrupted cache partition that maked impossible to flash anything or do factory reset.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I've wiped cache multiple times. What steps did you go through?

Use the adb fastboot, command "fastboot erase cache"
Sent from my ASUS_Z00AD using Tapatalk

You need the stock recovery as the same version of the firmware you're sideloading, flash the recovery through fastboot.

I was finally able to restore everything. Stock recovery, OS etc… Here’s what I did.
Using ADB and following the procedures here http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556 and using fastboot, flashed the recovery.img, boot.img and droidboot.img in that order. That gave me stock recovery back. Then I sideloaded with ADB the latest FULL firmware from here https://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
It was the only version that did not error out in some form or another. Everything is back to normal.

Root issues in Oreo

I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.

jfk999 said:
I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535

Baseminge said:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
Tried that too , same issue still.
It seems that data partition gets corrupted whenever i boot into twrp everytime.
No way out

jfk999 said:
I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
Click to expand...
Click to collapse
have you wiped data(TWRP/wipe data/type YES in the keyboard)?
and use superuser for root cause magisk can t mount data at the moment.

broky said:
have you wiped data(TWRP/wipe data/type YES in the keyboard)?
and use superuser for root cause magisk can t mount data at the moment.
Click to expand...
Click to collapse
As soon as i boot in twrp, data is not mountable. So I then go to
wipe-->adv wipe-->(select data partition)repair or change partition-->change partition format-->fat
TWRP then wipes it to fat filesytem,then i change it to ext4 (which is readable by OS)
then only data partition is mounted.
Afterwards I flash no-verity-no-encryption_ashyx and RMM patch
Boots normal to OS
Again boot to twrp i get error unable to mount /data
I had this issue in nougat but it used to happen only once.After flashing patch i used to not get this error repeated

jfk999 said:
As soon as i boot in twrp, data is not mountable. So I then go to
wipe-->adv wipe-->(select data partition)repair or change partition-->change partition format-->fat
TWRP then wipes it to fat filesytem,then i change it to ext4 (which is readable by OS)
then only data partition is mounted.
Afterwards I flash no-verity-no-encryption_ashyx and RMM patch
Boots normal to OS
Again boot to twrp i get error unable to mount /data
I had this issue in nougat but it used to happen only once.After flashing patch i used to not get this error repeated
Click to expand...
Click to collapse
Twrp/above factory reset on right side there is an option format data.
Press on this option and a keyboard rises.type YES and select format data.
After this check data partition,should be mounted.
After this flash SU zip and last Ashyx s patch.
Idonel this many times never had a problem even in Orsi.
Hope it works I can t think of something else.

broky said:
Twrp/above factory reset on right side there is an option format data.
Press on this option and a keyboard rises.type YES and select format data.
After this check data partition,should be mounted.
After this flash SU zip and last Ashyx s patch.
Idonel this many times never had a problem even in Orsi.
Hope it works I can t think of something else.
Click to expand...
Click to collapse
Which twrp version are you using?

Try...
The universal "no verity opt encrypt".
Magisk for the above, or safetynet evasion.
Backing up snapchat in /data/data/ and /sdcard/Android/data/, and load the backup. By PC or external sdcard, or load the backup later.

jfk999 said:
Which twrp version are you using?
Click to expand...
Click to collapse
look in 1:13
this is the step i mean:
format data/type:yes
https://www.youtube.com/watch?v=iOjnmGQ14fc&t=41s

broky said:
look in 1:13
this is the step i mean:
format data/type:yes
https://www.youtube.com/watch?v=iOjnmGQ14fc&t=41s
Click to expand...
Click to collapse
Tried it but still same issue.

Bryan48765 said:
Try...
The universal "no verity opt encrypt".
Magisk for the above, or safetynet evasion.
Backing up snapchat in /data/data/ and /sdcard/Android/data/, and load the backup. By PC or external sdcard, or load the backup later.
Click to expand...
Click to collapse
Tried the universal version for samsung and applied RMM patch, unfortunately same issue again.

I think that this has to do with SEpolicy. In nougat i used to get a small red warning at the edge of screen while booting to twrp. That time i did not face this
issue. Now I dont get any warning..boots into twrp with data partition corrupted.
I dont know, ive tried everything possible but no luck.

This is how I did and it works on my A320FL:
1. I installed Ashyx's version of TWRP via odin.
2. Boot into TWRP and "Format Data" from "Wipe" menu.
3. Flash SuperSu.
4. Flash Ashyx's patch.
5. Reboot phone(into recovery again).
6. Update TWRP with McFy's version.

jfk999 said:
Tried it but still same issue.[/QUO
I think I have the same issue.
May was your phone branded when you bought it?
Click to expand...
Click to collapse

Baseminge said:
jfk999 said:
Tried it but still same issue.[/QUO
I think I have the same issue.
May was your phone branded when you bought it?
Click to expand...
Click to collapse
I bought it from official store..Also i bought it jus few months after launch..
Which carrier are you using?
Click to expand...
Click to collapse

jfk999 said:
Baseminge said:
I bought it from official store..Also i bought it jus few months after launch..
Which carrier are you using?
Click to expand...
Click to collapse
So I think is something concerning the MM firmware that was not fixed with the N and O updates, 'cause I bought it very close to his launch too. I solved it by flashing a custom rom, so I think the problem was in official MM firmware or something went wrong in the OTA updates
Click to expand...
Click to collapse

Baseminge said:
jfk999 said:
So I think is something concerning the MM firmware that was not fixed with the N and O updates, 'cause I bought it very close to his launch too. I solved it by flashing a custom rom, so I think the problem was in official MM firmware or something went wrong in the OTA updates
Click to expand...
Click to collapse
Well ya..from MM to N, I did Odin update but from N to O i did ota update..since then im facing this issue..
But i still dont get it..i did a clean install and downloaded firmware from sammobile..yet this issue persist
Click to expand...
Click to collapse

jfk999 said:
Baseminge said:
Well ya..from MM to N, I did Odin update but from N to O i did ota update..since then im facing this issue..
But i still dont get it..i did a clean install and downloaded firmware from sammobile..yet this issue persist
Click to expand...
Click to collapse
At this point the only advice I can give you is to do a full wipe including "Internal Storage" (if you didn't) before flashing with Odin.
I really don't guess it will solve the problem on an official firmware, but there's no harm in trying
Click to expand...
Click to collapse

Still no luck...
At this point i have lost hopes

jfk999 said:
Still no luck...
At this point i have lost hopes
Click to expand...
Click to collapse
No matter what you try at this point you're data will always encrypt and will need to be formatted. TWRP will always reset.
This requires a whole different route and needs you to edit system files.
I'll get back to you with details.
---------- Post added at 11:25 PM ---------- Previous post was at 10:39 PM ----------
jfk999 said:
I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
Click to expand...
Click to collapse
This method requires intermediate knowledge of Windows and CMD commands....I've tried to simplify it and hope it is easy enough to go through
The files that need editing are the ramdisk fstab files.
Basically you are going to unpack boot.img, edit the files and repack it.
Here's how you do it:
In windows...From the firmware, open the AP file with WinRAR. Extract boot.img.lz4 and save it to your desktop
Go here https://github.com/lz4/lz4/releases/download/v1.8.2/lz4_v1_8_2_win64.zip
Extract it then just place your boot.img.lz4 to directory of lz4
Next open up cmd as admin and cd to the location where lz4.exe is located
In cmd type lz4.exe boot.img.lz4
This will unpack the lz4 file.
Now download http://www.mediafire.com/file/93a3f4bikaxh6tj/MTK_Extractor_V2.6.3.zip
Just open exe go to boot tab select the unpacked boot.img
This will extract the files you need and it will create folder called "initrd" and it will contain the contents of boot.img.
Make sure you have Notepad++ installed to edit the files.
Go to the MTK folder where your files have been extracted
Right click Fatah.goldfish and select open with Notepad++
Next find the phrase ",encryptable=userdata"
Delete it
Close the tab in Notepad++ and click to save
Back to MTK folder and right click fstab.ranchu. Open with Notepad++
Find the phrase ",quota,forceencrypt=/dev/block/vdd"
Delete it
Find the phrase ",encryptable=userdata"
Delete it
Close the tab in Notepad++ and click to save
Back to MTK folder and right click fstab.samsungexynos7880. Open with Notepad++
Find the phrase ",verify"
Delete it
Find the phrase ",forceencrypt=footer,quota"
Delete it.
Close the tab in Notepad++ and click to save
Next, go back to the MTK program and press the repack button
This will create your new boot.img file
Go back to the MTK folder. You should see your old boot.img file saved as "boot-old.img" and your new file as "boot.img"
Install 7-zip
Back to MTK right click your new boot.img. select 7-zip then select "add to archive"
This will open up another window. Simply select "tar" from the dropdown menu for "Archive format"
Press OK
This will create a new file "boot.tar"
Flash this via Odin with phone in Download mode
The boot will now be patched and you can set up TWRP as you need.
This whole process will need repeating if a new AP is flashed