Asus Zenfone Selfie displaying wrong internal storage - Asus Zenfone Selfie Questions & Answers

After flashing LineageOS 15.1 (Z00T) successfully I realized that my 64gb selfie (Z00UD) is displaying 32gb instead of 64gb. Any knows how to fix this?
I have tried:
- reflashing ROM (stock and custom) even tried flashing raw images.
- Tried TWRP fix the partition
- fastboot displays 27 gb for userdata
- flash partition gpt_both0.bin and userdata.img

does a 64gb ver even exist? I remember this phone was 64gb, I need to check the box but I couldn't find it.

Related

Nexus 7 32GB: Only 6GB after flashing userdata

I have a isue with my Nexus 7 which is really annoying and I need it fixed asap, the issue is that only 6GB out of 32GB is displaying after I flashed the userdata from one of my compiled roms.
I have tried flashing factory images, bootloader and more, but nothing works, anyone know how to fix this?
devstaff said:
I have a isue with my Nexus 7 which is really annoying and I need it fixed asap, the issue is that only 6GB out of 32GB is displaying after I flashed the userdata from one of my compiled roms.
I have tried flashing factory images, bootloader and more, but nothing works, anyone know how to fix this?
Click to expand...
Click to collapse
Did you try already to do a
fastboot erase userdata
???
VERY common issue. A search would have given you a solution thread. All you need to do is boot into recovery and format /data. This NOT the same as a factory reset. You could also do it with the above fastboot command, but it's easier to use recovery and I'm pretty sure it's more successful.

Improper storage size. 128GB model only showing 24GB

I have the 128GB model and I was transferring 32GB worth of music over to my 6P and before it completed I was getting warnings that files couldn't be copied. I stopped it and then looked at the phone on my PC and it was saying it's size was 24.1 GB. It shows the same thing when I look at the storage on the phone. What happened?
If you flashed the factory image, it probably set the partition for userdata to the wrong size. One fix is to go into recovery and perform a factory reset from recovery and it will fix the size. I am not sure if there are other methods that can fix it without doing the reset. Another person may be able to offer a better alternative.
tkoreaper said:
I have the 128GB model and I was transferring 32GB worth of music over to my 6P and before it completed I was getting warnings that files couldn't be copied. I stopped it and then looked at the phone on my PC and it was saying it's size was 24.1 GB. It shows the same thing when I look at the storage on the phone. What happened?
Click to expand...
Click to collapse
Did you flash the userdata.img from the factory images at some point? Doing so always allocates the smallest of the available storage sizes, so it really shouldn't be used. You can fix it by issuing this fastboot command:
Code:
fastboot format userdata
This will wipe your userdata partition so make sure you back up anything important first.
Heisenberg said:
Did you flash the userdata.img from the factory images at some point? Doing so always allocates the smallest of the available storage sizes, so it really shouldn't be used. You can fix it by issuing this fastboot command:
Code:
fastboot format userdata
This will wipe your userdata partition so make sure you back up anything important first.
Click to expand...
Click to collapse
That explains it, thank you. I ended up just starting over so it's all good now.
Heisenberg said:
Did you flash the userdata.img from the factory images at some point? Doing so always allocates the smallest of the available storage sizes, so it really shouldn't be used. You can fix it by issuing this fastboot command:
Code:
fastboot format userdata
This will wipe your userdata partition so make sure you back up anything important first.
Click to expand...
Click to collapse
Hehe that's exactly what I just did (flahsed my own cooked up userdata.img, which cut my size in half), thanks Heisenberg

[Solved] Hard Brick Moto X Style XT1572 ( Qualcomm hs-usb qdloader 9008 )

Good morning, I'm new here on the forum. Sorry if English is bad because I'm using the automatic translator and I'm from Brazil.
I have the Moto X Style that died after updating via ota (the bootloader is unlocked and had downgrade) result = does not enter fastboot mode, recovery, nor loads, when it connects on the computer by usb it presents qualcomm hs-usb qdloader 9008, for those with the same problem, I was able to recover my device through a file shared by a colleague of google plus who made a dump of xt1572 that works 100% (loader.img)
File Link to Recovery
drive.google.com/file/d/0Bz770r9yW2iNU29JZkNPdkZmeG8/view
ROM link with bootloader version A0.52
androidfilehost.com/?fid=961840155545596639
MOTO X STYLE XT1572 UNBRICK GUIDE
Initial Reminders: This method has been tested on more than one XT1572 model successfully, but we can not guarantee the success of this guide in your case. NO ONE HERE IS RESPONSIBLE FOR WHAT YOU DO WITH YOUR APPLIANCE. If you have no skill / experience or do not feel confident following such guides, DO NOT GO!
Several members of this community together have come up with a solution to the "Hardbrick" problem of Style, a condition where it gives no sign of life and recognizes on the computer as "HS-USB DLoader 9008".
THINGS YOU WILL NEED BEFORE YOU BEGIN:
1 - A computer with Motorola drivers installed, fastboot files and the DiskImageRev2 program. Your Windows user needs to have administrator access.
2 - A USB cable of good quality and 100% functional.
3 - A USB microSD memory card reader.
4 - A microSD memory card. Recommendation: 16GB, class 10 and ORIGINAL!
5 - The complete ROM file.
Details of this ROM: Dual SIM. RETAIL. Region "LA" - the two simcards operate 100% in Brazil. Android 7.0. Security Patch August 1, 2017. Version Number NPHS25.200-15-3.
6 - The file "Loader.img".
7 - The battery of the unit must be charged so as to allow the unit to switch on in fastboot mode.
Each of the above may require additional steps. For this guide not to get too large these details were not included.
STEP BY STEP
Step 1 - Burn the "Loader.img" file to the microSD memory card using the DiskImageRev2 program.
Step 2 - Insert the memory card into the device and turn it on in fastboot mode. There are three possible options: (1) hold down the Power and Volume buttons for at least 10 seconds. (2) Hold the Volume minus button and connect the unit to the computer. (3) Connect the device to the computer, after it is recognized to hold the Power button until it "reboots" it automatically enters fastboot mode.
Step 3 - With the device in fastboot mode, write the ROM normally complete using the Windows command prompt.
.\fastboot oem fb_mode_set
.\fastboot flash partition gpt.bin
.\fastboot flash bootloader bootloader.img
.\fastboot flash logo logo.bin
.\fastboot flash boot boot.img
.\fastboot flash recovery recovery.img
.\fastboot flash system system.img_sparsechunk.0
.\fastboot flash system system.img_sparsechunk.1
.\fastboot flash system system.img_sparsechunk.2
.\fastboot flash system system.img_sparsechunk.3
.\fastboot flash system system.img_sparsechunk.4
.\fastboot flash system system.img_sparsechunk.5
.\fastboot flash system system.img_sparsechunk.6
.\fastboot flash system system.img_sparsechunk.7
.\fastboot flash system system.img_sparsechunk.8
.\fastboot flash system system.img_sparsechunk.9
.\fastboot flash system system.img_sparsechunk.10
.\fastboot flash modem NON-HLOS.bin
.\fastboot erase modemst1
.\fastboot erase modemst2
.\fastboot flash fsg fsg.mbn
.\fastboot flash bluetooth BTFM.bin
.\fastboot erase cache
.\fastboot erase userdata
.\fastboot erase customize
.\fastboot erase clogo
.\fastboot oem fb_mode_clear
.\fastboot reboot
This solution was the result of a joint effort of several people from the "Moto X Style BRASIL - Official" community on Google+
restores the dump into sd card, is this right ? or can you provide some instruction ?
This is for the XT1572 (not sure about other models), and yeah, you use DiskImageRev2 to write the loader.img to a sd card (32 gb card needed since it writes a 32gb partition)
After that you connect it to the computer, and press power button till it resets, it will start in fastboot mode.... then, just flash the rom you want (got mine back some hours ago with the same procedure)
@Danielo007
Good news.
Can you explain what/how did you unbrick MXP/S?
What to do with this file and after?
can confirm it works
Thank you very much
1. use Diskimage to write .img file on a 32gb card
2. put the card inside the slot
3. boot like you would boot to bootlooder (volume down + power) after some screen flash, it start in bootloader mode.
4. use fastboot to flash rom
Danielo007 said:
Good morning, I'm new here on the forum. Sorry if English is bad because I'm using the automatic translator and I'm from Brazil.
I have the x-style bike that died after the update via ota (the bootloader is unlocked and had downgrade) result did not connect in fastboot mode, recovery, did not load and when connecting on the computer it featured qualcomm usb qdloader 9008, for those who are with the same problem I was able to recover my device from a file shared by a colleague of google plus that made a dump from its xt1572 that works 100% o (loader.img)
File Link to Recovery
drive.google.com/drive/folders/0B9SXWV7BgmquVWZJTUp1NHJPb2M
Click to expand...
Click to collapse
Very nice! I've seen something like this work on other Snapdragon phones. Thankfully I've never had to try it on this one. There's something baked into the Qualcomm CPU that will fallback and read the bootloader from an SD card if the eMMC fails. Is that what's going on here?
Anyone tried it on an XT1575? I'm not sure if the bootloaders are interchangeable cross device or not.
I'd be happy to try and make an XT1575 debrick image if this one is XT1572 specific. Do you know if your colleague created it with a command something like this?
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1M count=165
update...
device boot only with flash card inserted
fdc77 said:
update...
device boot only with flash card inserted
Click to expand...
Click to collapse
Not really, you're using an older version of your rom, you need the same GPT.BIN file to be writen, or else your not "fixing" the bootloader, it will give " preflash validation failed" in it, with the latest rom it worked for me, i'm not using the "emulation sd card" and the phone boots as the first time
---------- Post added at 14:32 ---------- Previous post was at 14:30 ----------
See in here the file "Guia para UNBRICK em inglês.pdf" gives you the instruction needed
you are right......but i don't have stock nougat rom for xt1572 EU, anyway i was able to recover my phone, flashing a nougat flashfire backup that i had made when i install it first time.
Guys, I love you. I DO, REALLY!
Finally my bricked XT1572 is back from the dead, at least it booted into Fastboot mode. However, I don't have the full Nougat ROM for the XT1572-LATAM_DS, only the Marshmallow 6.0 ROM with December security patch. Thus, since the Loader.img is for a Nougat ROM, I can't flash the gpt.bin and bootloader.img from the MM ROM ("Preflash validation failed").
Can anyone share the full Nougat ROM (if it's available), or at least the gpt.bin and bootloader.img (then I can flash a custom ROM, for instance)?
THANKS!!!
EDIT: found it on the Google+ community, downloading now.
EDIT 2: solved!! The ROM worked with the instructions! THANKS TO ALL INVOLVED!!
Amazing... Moto staff hided this secret from people for years ))
Tried this on my xt1575 and it worked initially. Failed to flash gpt.bin and bootloader.img from the 24.49-18-8 full factory MM image. It did initially boot to the stitch screen then powered off and won't power on again. Tried letting it sit and reinstalled the sd card but it won't power on at all now. When I initially put the SD card in the white led lit up and I was able to get to recovery mode. Now nothing happens. So I wouldn't advise XT1575 users to try this loader.img
I hope this interchangeable with X1575. Or some one can create a loader.img for it. BTW you would have to fastboot the last image that was installed?
jason2678 said:
Very nice! I've seen something like this work on other Snapdragon phones. Thankfully I've never had to try it on this one. There's something baked into the Qualcomm CPU that will fallback and read the bootloader from an SD card if the eMMC fails. Is that what's going on here?
Anyone tried it on an XT1575? I'm not sure if the bootloaders are interchangeable cross device or not.
I'd be happy to try and make an XT1575 debrick image if this one is XT1572 specific. Do you know if your colleague created it with a command something like this?
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1M count=165
Click to expand...
Click to collapse
please make a debrick image of xt1575 USA Version If you can. I need it to debrick my X Pure .
Hi:
But finally when flash by fastboot, the destination is the internal memory or the sd card?
Regards
npatel555 said:
please make a debrick image of xt1575 USA Version If you can. I need it to debrick my X Pure .
Click to expand...
Click to collapse
On other Snapdragon phones I've seen this work with in the past it is kind of a fickle thing. I looked back over some old threads, and you needed an image specific to the firmware you were running at the time you bricked. I think my phone is too much of a Frankenphone right now to be a good candidate for pulling an image from. I'm pretty sure I'm on the bootloader from the MM Sept 2016 security update and the modem from the MM May 2016 security update. Currently not on a stock rom either. I could make you an image, but based on BuildUpNow's post above I think it would either not work or maybe leave you worse off than you are now.
I could get my phone back to fully Sept 2016 stock for the purpose of making an image, but that's it. The bootloader won't downgrade. The XT1575 packages haven't leaked for Dec 2016 or Nougat, and I'm not touching those OTA's as poorly as they seem to be going. I've never seen so many hard bricks reported on this device as I have in the last month or two.
Our lack of full firmware packages for XT1575 will really hinder this unless you happen to have been on older firmware. Unless you can get your hands on a firmware package same or newer than what you were running, you're going to get preflash validation failure on the bootloader and partition table, and based on the posts above it sounds like you'll still be stuck.
can you please provide loader.img for moto x play???
I think any user of bricked xt1575 can use the same loader.img, flash stock N LatAm, one reboot and flash modem/baseband from 6.0 US.
If it will not help - system boots but wrong working - can flash full 6.0 US without BL, GPT, OEM commands.
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
dzidexx said:
I think any user of bricked xt1575 can use the same loader.img, flash stock N LatAm, one reboot and flash modem/baseband from 6.0 US.
If it will not help - system boots but wrong working - can flash full 6.0 US without BL, GPT, OEM commands.
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
Click to expand...
Click to collapse
I tried that and it didn't work.
I actually got my phone to boot up now though. But the phone will only boot with the sd card it in. I tried wiping it and using it for storage and the phone refuses to boot. The img has to be written to it. I also can't enter recovery mode( pwr + vol dn buttons at all). So now I'm stuck with mm6.0 and I cannot enter recovery at all. Guess I'll have to try and load the sd card on linux and see what files are on the card and see if there's anything to be modified.
Oh my goodness, thank you so much for this quick and easy fix. My phone is back from the dead and it even worked on my Moto X PURE (XT1575). You made my day, honestly, I haven't been this happy for a long time

Need Asus Ze550kl ZOOL EMMc Raw File

Hello,
My Asus ze550kl m8916
Snapdragon 410 2gb/16gb model
is hardbrick
It is still in locked state
However, I have used QFIL using Test Point and managed to reach Fastboot Mode
When I flashed TWRP it always Reboot
I can flash all the firmwares files even in locked state using
Emmc RAW tool
But ai need the Working Dump flash file
Can anyone help me?
Download the EMMC Raw Tool
Boot into Download mode Q9006 mode) and dump the Firmware Only
this include
1.ASDF, SEC, sbl1, hyp, tz, aboot, adf, Asusfw, asusgpt1, 2, Asuskey, asuakey2, 3,4,5, boot, cache, config, ddr, devinfo, factory, fsc, gaps#1, keystorre, mbr-gpt-other, misc, modem, modemstr1, modrmstr2, oem, presist, persistent, recovery, splash, ssd,
You can dump all these files using emmc raw tool while in Q9006 Mode..
To be in q9006 mode just flash the wrong emmc_aboot to your phone
you'll be in q9006 mode
to get back on track install the correct emmc_aboot.mbn file again
OR
you can dump your Firmware using root
adb shell command
dd if=/dev/........ of=/sdcard
if u need help in How to dump these files to your memory card or internal storage, Reply I'll help u how to dump
Please send me the files after you're dump
Contact me on what app +918974796939 if u r willing to help me
Let's learn things together
Can anyone help me. with this?.?
Thanks a lot in advance
Just take it to service centre I think you got a flash lock on your partition (just assuming). I have a custom ROM so if you want I can send you the dump files.
Hello.
What are the test points you connected?

how to resize recovery partition...please help

hell guys
First my phone is : Moto G5 Plus
Product/Variant : potter XT1685 32GB P3B
i made mistake guys and flash wrong gpt.bin and bootloader.img
after some research i find that the gpt.bin changed the size of all partitions i have
i flash TRWP and use this guide iwf1.com/how-to-re-partition-your-android-tablet-or-smartphone-all-options-included-change-size-fs-type-etc/2
i use adb and i can't delete userdatra and system partition to resize them
i can delete oem partition and recreate it and when i try to resize recovery partition it can't allow me
but i can delete and recreate it but phone going dead , then i use blankflash to back to life
and in singleimage.bin i try edit gpt.bin by the original gpt.bin and it is going will in flashing
but here is the problem when i back to TRWP to see the size of partition it back as same , i need 21MB in recovery but i find it all time 16MB :crying::crying::crying:
i have problem on my recovery partition
i can't flash the recovery.img of this Roms
POTTER_RETAIL_7.0_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
recovery.img required 20 MB :crying: and my recovery partition have 16 MB :crying:
i try Debloated ROM ... i know it works fine but i need this issue to fix
if someone know please help me :crying::crying:
i need to resize recovery partition
What error are you getting when trying to flash the Motorola stock recovery? Is your bootloader locked?
Which GPT/bootloader did you flash that caused this to happen?

Categories

Resources