Very happy XT1575 user (rooted on TruPure 2.4). Cruising along without issue for months and then it suddenly froze and started bootlooping. Sometimes it gets all the way to the lock screen but that's it.
Steps taken:
-Restored a nandroid backup but no dice.
-Next did a factory reset- also not successful.
-I did the Return To Stock method at this thread but it still bootloops.
Am I out of options? Is this a hardware issue?
Thanks for any suggestions. I really hate to give this phone up!
trptcom said:
Very happy XT1575 user (rooted on TruPure 2.4). Cruising along without issue for months and then it suddenly froze and started bootlooping. Sometimes it gets all the way to the lock screen but that's it.
Steps taken:
-Restored a nandroid backup but no dice.
-Next did a factory reset- also not successful.
-I did the Return To Stock method at this thread but it still bootloops.
Am I out of options? Is this a hardware issue?
Thanks for any suggestions. I really hate to give this phone up!
Click to expand...
Click to collapse
Did you lock bootloader? What is status code in BL screen?
No, I did not re-lock the bootloader when I returned to stock. That shouldn't matter?
Yes. After re lock you cannot do anything.
Flash stock again without bootloader & gpt. All sparsechunks you have in zip file, from 0 to last. Each command should end with "ok".
Don't lock BL.
Problem is - you are flashing the older version than you have on phone.
Post here results(screenshots from pc maybe too). @trptcom
---------- Post added at 07:32 AM ---------- Previous post was at 07:28 AM ----------
Of course it could be hardware problem(eMmc), you can check with twrp:
"fastboot boot twrp3xxx.img"
Into twrp: format data and after it check what sizes(MB) of backup are showing.
@dzidexx - Even though I returned to stock I never did relock the bootloader. Since then I...
--Reflashed TWRP and reinstalled my ROM after a complete wipe and data reformat. Bootloops after getting to the setup screen.
--Tried again to return to stock and omitted the bootloader and gpt commands, as you suggested. Still bootloops at the setup screen.
One FAILED result this time during fastboot, however..
fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.328s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.344s
Getting frustrated. Any suggestions welcome!
Maybe it is eMmc issue. Try & check:
fastboot boot twrp.img (3.+)
In twrp do:
Format data/factory reset,
Advanced wipe - all,
Go to backup section and check what are sizes of partitions.
System should be 0MB, data too. @trptcom
---------- Post added at 08:45 PM ---------- Previous post was at 08:44 PM ----------
Maybe it is eMmc issue. Try & check:
fastboot boot twrp.img (3.+)
In twrp do:
Format data/factory reset,
Advanced wipe - all,
Go to backup section and check what are sizes of partitions.
System should be 0MB, data too.
@trptcom
Thanks @dzidexx, I did that. Data is 0MB but system is 7MB (Boot shows 40MB).
Also I get this error when wipe and format commands are entered:
flash_image /dev/block/bootdevice/by-name/metedata /dev/zero process ended with ERROR: 255
Error sometimes is present - 1st should be done format data, than adv.wipe.
Emmc looks ok, check also partitions file system - adv.wipe - repair.
Should be: Cache, system ext4, data f2fs.
I think you should flash twrp and last good custom - you had tru pure?
Try another(not last) version.
Twrp - I think twrp 3.0.2 works the best. @trptcom
Okay, thanks again @dzidexx.. I did all that and reinstalled my last good ROM. Same result- phone starts up, gets to the welcome screen and starts bootlooping.
trptcom said:
Okay, thanks again @dzidexx.. I did all that and reinstalled my last good ROM. Same result- phone starts up, gets to the welcome screen and starts bootlooping.
Click to expand...
Click to collapse
Check sizes & file system in backup/adv.wipe sections with twrp. Post here.
Wiped everything.
Cache and system partitions are ext4, data partition is f2fs.
System has 7MB, Data has 0MB
Installed ROM
Cache and system are ext4, data is f2fs.
System now has 1140MB, Data has 0MB
Still bootlooping
Sorry, I don't know what is going on. You have to try flashing stock rom. @trptcom
Since this all started I have flashed stock several times now using fastboot from the "restore to stock' thread . Gets up to the Welcome screen and then goes into bootlooping.
Reflashed my last good Rom with the same result... gets up to the Welcome screen and then goes into bootlooping.
This all started out of the blue... phone had been humming along fine for many months. I had it all set up how I liked it and never updated anything. Then just the other day I tried to answer a phone call and the phone locked up. Started rebooting/bootlooping right after.
I'm so bummed....
Maybe you can try one more trick(only with newest twrp - 3.1.x):
Adv.wipe - change file system for data to ext4, wipe all, reboot recovery, change FS to f2fs and flash tru pure. @trptcom
@dzidexx, was excited to try your last tip. So I rebooted to bootloader from my existing TWRP to get to fastboot mode to flash the newer 3.1x TWRP and the phone completely died. Won't power on, nothing.
I guess that's what you call bricked?
Update: I was able to power the phone on. Installed the updated 3.1x TWRP, executed the file system trick, and installed the ROM. Still bootlooping. And actually it's bootlooping TWRP!
Thanks for all your tips but I'm out of luck I think..
I think you need new/used mainboard to fix it.
You can also try more wipe options.
Boot twrp with fastboot: "fastboot boot twrp3_1_1.img", repair/change file system to f2fs. Check if it done.
Erase all partitions with fastboot:
"fastboot erase boot", recovery, system, userdata, cache.
Flash the newest stock rom without bootloader & gpt.
If not helped, erase one more time & flash again with gpt.
Nothing more you can do. @trptcom
Install twrp-3.1.0-0-clark using fastboot. Then change to ext4 data and system and STAY THERE. Do not switch to f2fs. Wipe and reinstall your rom. Should work...let us know.
@dzidexx - tried the options in your last post (#17)... each time I got a couple of screens past the Android welcome screen before rebooting commenced.
@Kutty - thanks for your suggestion (actually used twrp-3.1.1-0-clark) but with that method my Rom wouldn't even finish installing before bootlooping commenced.
Thanks for all the assistance but I reckon that by now I've spent entirely too much time on this. I'm resigning myself to chalk it up to hardware failure. (The phone had been starting to act up in the week before it froze- I was getting prompted to reauthorize permissions when I started up apps. I didn't know what to make of that..)
Sorry to hear that bud, hope you get up and running soon.
Related
Hi guys,
I'm experiencing a very big problem with a friend of mine's nexus 4. I've done the same thing in the same order with my phone (nexus 4 too) five minutes before and it worked.
We installed 4.4 stock rom downloaded from official google website via fastboot and all went well on my device. The problem was that we repeated the same identical procedure on my friend's nexus 4 and it went well except for the fact that the phone only had 5gbs available after the flash, so we red on the internet that we had to repeat the procedure using "fastboot -w update" instead of flashing every single file contained in the zip folder.
So it's now that borns the real problem. We've erased all partitions (fastboot erase cache, userdata, system, bla bla) and reflashed all. But from this point it stucks on android 4.4 loading logo.
We've tryied to repeat the operation and we've noticed that "fastboot erase bootloader" command answers with "Failed (remote: bootloader partition does not exist)". So we tryied to install cwm recovery and flash from sideload, it works and loads cyanogenmod logo but stucks on it again, tryied to flash everything possible and it works but after don't start.
The strange thing is that the bootloader appears to not exist but if i do the command: fastboot flash bootloader C:\...\bootloader.img it works and says "writing... OK" so i really don't know what could be the problem.
Please guys help us, my friend is on the point to sell his phone but we both are SURE that if it still can enter on recovery and on bootloader it could be restored!!! But we don't know why! Tryied every possible solution on the web, and nothing worked for now...
Thanks to all in advance!
Install the latest twrp recovery, enter it and go to the wipe menu, chose the format data option. Then give a rom a try.
meangreenie said:
Install the latest twrp recovery, enter it and go to the wipe menu, chose the format data option. Then give a rom a try.
Click to expand...
Click to collapse
Hi, thanks for the answer. Fortunately i've just resolved the problem. It worked after I wiped data from the STOCK recovery (it was the first thing i've done with the cwm several times but unsuccessfully). Now it works perfectly. Thanks again :victory:
fdm91xda said:
Hi, thanks for the answer. Fortunately i've just resolved the problem. It worked after I wiped data from the STOCK recovery (it was the first thing i've done with the cwm several times but unsuccessfully). Now it works perfectly. Thanks again :victory:
Click to expand...
Click to collapse
For future references. Most likely the reason why your phone didn't boot up is because you 'erase' a partition and left it unformatted. The 'erase' command wipe out the partition so no data is there and it can't access it. If you erase userdata, then there would be no accessible internal storage and the phone cannot boot.
Which is why after you erase it, you need to either flash something over it or format the partition to make it blank: fastboot format userdata (this is what Format DATA option in TWRP is).
I have a few ideas as to why the certain devices are getting, seemingly, hard-bricked. I won't put the info out there yet, I'd like to get more data first.
Can everyone do me a favour and fill this out? I want to try to find the exact issue at hand so we can better fight against it.
FORM:This info is found in the bootloader
Bootloader -
Baseband -
Variant -
CPU -
EMMC -
DRAM -
Console -
Qfuse status -
Download Mode -
This is found in bootloader - barcodes
Manufacture date -
Brief description of where the bootlooping started - Ex. "I was pushing system files via adb, and cmoding them. I ran SELinux fix in TWRP 3.0.2-0. Upon restoring my backup, I got bootloops"
I was able to fix the bootloop with these EXACT steps - OR*
*I have not been able to fix my device*
I have tried methods - *METHODS WILL BE IN POST #2*
My device is
Bootloader - 3.58
Baseband - 3.72
Variant - VN2
CPU - 0x20001
eMMC: 32GB Samsung
DRAM: 3072 HYNIX LPDDR4
Console - NULL
Qfuse status - Enabled
Download Mode - Disabled
Manufacture data - 11-13-2015
Methods tried - 1-21
*TWRP #IRC*
Boot phone into TWRP, run these commands. You may have to flash factory images one more time if you get stuck at the splash screen (rather than looping)
Enter adb shell then copy and paste these two lines, separately.
dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix bootloops for most. TWRP 3.2.1-1 causes a fatal error. The above shell commands should get 'most' running.
-----------------------------------------------------------------------
All methods below are MTC20F unless otherwise stated.
If you notice a method that worked, that I haven't listed please share with me with the source so I can have a full list.
Method 1
Followed instructions on flashing full firmware, found on g.co/ABH
Method 2
Followed instructions for OTA, found on g.co/ABH
Method 3
Followed @Heisenberg instructions in the HOWTO for manually flashing firmware via fastboot
Method 4
Flashed stock firmware, then wiped data/cache in stock recovery
Method 5
Flashed stock firmware, then wiped data/cache in TWRP 3.0.2-0
Method 6
Flashed stock firmware, then wiped data/cache in TWRP 3.0.2-1
Method 7
Flashed firmware via fastboot, then flashed full stock firmware through twrp (specify which version)
Method 8
Flashed firmware via fastboot, then flashed OTA firmware through twrp (specify which version)
Method 9
Utilized Wugs tool to flash full firmware
Method 10
Flashed firmware via fastboot, then sideload OTA via adb
Method 11
Flashed firmware, then flash your own TWRP backup
Method 12
@Eric214 says
Advanced wipe - System, Data, Cache and Dalvik.
Flash vendor image MTC20F.
Flash PureNexus, Gapps, SuperSu 2.76.
Reboot.
Method 13
Factory reset, flash TWRP, resize and repair all partitions, flash stock again via fastboot
Method 14
Factory reset, flash TWRP, resize and repair all partitions, flash stock again via update.zip
Method 15
@shiftr182 method
Fastboot firmware, flash twrp, repair and resize, flash nougat bootloader, flash nougat update from HERE
Method 16
@neaznc021 method
"I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked"
Method 17
Fastboot stock, flash backup, flash MM ROM
Method 18
@rbouza1 method
"Fastboot format user data partition
Run factory image
Fastboot bootloader radio vendor
Flash twrp
Try and boot if not flash stock rom /any mm rom boot into twrp and try a restore. Those were my steps and it worked"
Method 19
@FragmentsOfLife method
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Method 20 @avivasaf
"Got backup from my friend, you need this!
Format userdata
Flash twrp
Make any backup
Move the good backup to the file backup
Restore it
Flash any Mm rom(i flashed cm13)
Fastboot flash mm bootloader, radio, vendor
And you got it!!!!"
Method 21 @Azhar05 method
flash developer preview 5 and flash latest twrp and then copy mtc 20f vendor image to twrp folder and then in twrp install image mtc 20f
Method 22
Let me know if you have more!
reserve 2
tr4nqui1i7y said:
I have a few ideas as to why the certain devices are getting, seemingly, hard-bricked. I won't put the info out there yet, I'd like to get more data first.
Can everyone do me a favour and fill this out? I want to try to find the exact issue at hand so we can better fight against it.
FORM:This info is found in the bootloader
Bootloader -
Baseband -
Variant -
CPU -
EMMC -
DRAM -
Console -
Qfuse status -
Download Mode -
This is found in bootloader - barcodes
Manufacture date -
Brief description of where the bootlooping started - Ex. "I was pushing system files via adb, and cmoding them. I ran SELinux fix in TWRP 3.0.2-0. Upon restoring my backup, I got bootloops"
I was able to fix the bootloop with these EXACT steps - OR*
*I have not been able to fix my device*
I have tried methods - *METHODS WILL BE IN POST #2*
My device is
Bootloader - 3.58
Baseband - 3.72
Variant - VN2
CPU - 0x20001
eMMC: 32GB Samsung
DRAM: 3072 HYNIX LPDDR4
Console - NULL
Qfuse status - Enabled
Download Mode - Disabled
Manufacture data - 11-13-2015
Click to expand...
Click to collapse
I don't have this problem but I have noticed that it appears that a lot of people with bootloop problems have either explicitly stated that they are "on TWRP 3.0.2-1" or say "I updated to latest TWRP". I've seen it mentioned enough times that I'm almost starting to wonder if there is an issue with TWRP 3.0.2-1. Just throwing this out, don't know if it helps or if you would also wish to collect TWRP version.
I would also like to see this issue resolved just for my own personal satisfaction. Good luck.
Edit - well hell you ninja'd me. I swear post #2 was reserved when I typed this.
sixgunmojo said:
[/HIDE]
I don't have this problem but I have noticed that it appears that a lot of people with bootloop problems have either explicitly stated that they are "on TWRP 3.0.2-1" or say "I updated to latest TWRP". I've seen it mentioned enough times that I'm almost starting to wonder if there is an issue with TWRP 3.0.2-1. Just throwing this out, don't know if it helps or if you would also wish to collect TWRP version.
I would also like to see this issue resolved just for my own personal satisfaction. Good luck.
Edit - well hell you ninja'd me. I swear post #2 was reserved when I typed this.
Click to expand...
Click to collapse
Thanks, that would be useful. I'm thinking of how to incorporate that in a simple enough way that people don't accidentally provide incorrect information.
FORM:This info is found in the bootloader
Bootloader - angler-03.54
Baseband - angler-03.61
Variant - ANGLER-VN2
CPU - MSM8994 0x20001
EMMC - 64GB Samsung
DRAM - 3072MB HYNIX LPDDR4
Console - NULL
Device : Locked
Qfuse status - Enabled
Download Mode - Disabled
Manufacture date - 10/20/2015
Brief description of where the bootlooping started -
Stock, locked bootloader. Attempted OTA Friday night. It downloaded, then prompted to install. After some time I checked the phone, it had rebooted, but still in 6.0.1. It said Update failed, please try again. The OTA update came back up and asked me to download again. I decided to worry it about it later cause I needed to use the phone at that time.
On Sunday, phone locked up for 10 seconds while browsing CHrome, then restarted itself. Bootloop, showing the white google logo for 10 seconds, then black screen for 2 seconds, then back to google, infinite looping.
I can access the bootloader screen. From there, choosing any option besides Power Off results in the same bootloop with white google logo. Can't access recovery.
Contacted Google Support, they're sending me a new device. Very bizarre. It's crazy. After the failed OTA, I backed up some things from my device. I was going to research and finally unlock bootloader and root, and then phone crapped out before I had the chance.
I have tried methods - can't do anything except see the bootloader screen or the barcodes screen. Anything else results in white google logo
busbeepbeep said:
FORM:This info is found in the bootloader
Bootloader - angler-03.54
Baseband - angler-03.61
Variant - ANGLER-VN2
CPU - MSM8994 0x20001
EMMC - 64GB Samsung
DRAM - 3072MB HYNIX LPDDR4
Console - NULL
Device : Locked
Qfuse status - Enabled
Download Mode - Disabled
Manufacture date - 10/20/2015
Brief description of where the bootlooping started -
Stock, locked bootloader. Attempted OTA Friday night. It downloaded, then prompted to install. After some time I checked the phone, it had rebooted, but still in 6.0.1. It said Update failed, please try again. The OTA update came back up and asked me to download again. I decided to worry it about it later cause I needed to use the phone at that time.
On Sunday, phone locked up for 10 seconds while browsing CHrome, then restarted itself. Bootloop, showing the white google logo for 10 seconds, then black screen for 2 seconds, then back to google, infinite looping.
I can access the bootloader screen. From there, choosing any option besides Power Off results in the same bootloop with white google logo. Can't access recovery.
Contacted Google Support, they're sending me a new device. Very bizarre. It's crazy. After the failed OTA, I backed up some things from my device. I was going to research and finally unlock bootloader and root, and then phone crapped out before I had the chance.
I have tried methods - can't do anything except see the bootloader screen or the barcodes screen. Anything else results in white google logo
Click to expand...
Click to collapse
Your device isn't recognized by adb/fastboot?
tr4nqui1i7y said:
Your device isn't recognized by adb/fastboot?
Click to expand...
Click to collapse
Let me know if there are others commands I can try. At any rate, my replacement device is arriving Wednesday.
This is what I get:
adb devices: reports blank
fastboot devices: report serial #
adb reboot bootloader: reboots bootloader
adb reboot recovery: error: no devices/emulators found
fastboot flashing unlock: FAILED (remote: oem unlock is not allow)finished. total time: 0.014s
fastboot reboot: reboots and goes into white logo loop
busbeepbeep said:
Let me know if there are others commands I can try. At any rate, my replacement device is arriving Wednesday.
This is what I get:
adb devices: reports blank
fastboot devices: report serial #
adb reboot bootloader: reboots bootloader
adb reboot recovery: error: no devices/emulators found
fastboot flashing unlock: FAILED (remote: oem unlock is not allow)finished. total time: 0.014s
fastboot reboot: reboots and goes into white logo loop
Click to expand...
Click to collapse
Try this tool to make things a little easier, and more automated for now. Wugs
I've tried that tool to "temporarily boot stock recovery" but nothing happened on the device.
busbeepbeep said:
I've tried that tool to "temporarily boot stock recovery" but nothing happened on the device.
Click to expand...
Click to collapse
Boot into bootloader manually then try to run something
Well I was able to update normally by flashing stock images and taking the OTA Thru the Phone. I did have an issue 2 days ago where I decided to wipe my phone and restore stock backup 7.0 At this point I started getting the boot loop nothing seemed to work so I'm assuming the newest version of TWRP has an issue with restoring backups on Nougat. Trying everything didn't work but what I had was my original EFS backups and the original stock back up from my phone which I believe was 29 Q I installed pure Nexus August 21st build restored my stock ROM and restored my EFS partition backup. Phone booted perfectly.
So now I'm wondering if the issue may lie in the efs partition.
Eric214 said:
Well I was able to update normally by flashing stock images and taking the OTA Thru the Phone. I did have an issue 2 days ago where I decided to wipe my phone and restore stock backup 7.0 At this point I started getting the boot loop nothing seemed to work so I'm assuming the newest version of TWRP has an issue with restoring backups on Nougat. Trying everything didn't work but what I had was my original EFS backups and the original stock back up from my phone which I believe was 29 Q I installed pure Nexus August 21st build restored my stock ROM and restored my EFS partition backup. Phone booted perfectly.
So now I'm wondering if the issue may lie in the efs partition.
Click to expand...
Click to collapse
What eMMC is your device using, if you don't mind?
tr4nqui1i7y said:
What eMMC is your device using, if you don't mind?
Click to expand...
Click to collapse
64GB Toshiba
Eric214 said:
64GB Toshiba
Click to expand...
Click to collapse
Just to clarify, you were able to get your device to boot?
Stock MTC20F ->adb sideload OTA -> Successfully booted and used N today. Factory Reset ->ensured OEM Unlock was still enabled -> flashed latest twrp -> performed full wipe including formatting data -> flashed MTC20F Vendor -> ran Flash-all script from factory image of MTC20F -> Running full stock MTC20F
Jammol said:
Stock MTC20F ->adb sideload OTA -> Successfully booted and used N today. Factory Reset ->ensured OEM Unlock was still enabled -> flashed latest twrp -> performed full wipe including formatting data -> flashed MTC20F Vendor -> ran Flash-all script from factory image of MTC20F -> Running full stock MTC20F
Click to expand...
Click to collapse
To clarify, this is for users to upgrade to N, then downgrade back to MM safely. This is not to correct the bootloop, correct?
tr4nqui1i7y said:
Just to clarify, you were able to get your device to boot?
Click to expand...
Click to collapse
Originally i had no issues I flashed factory images from Pure Nexus June build Via Fastboot. Rebooted the phone and took the OTA through the phone and then flashed TWRP 3.0.2-1 (the Newest one) and through TWRP flashed SuperSU 2.76 then FDR the phone before setting it up. All was fine and perfect. I made a backup and then factory data reset my phone Saturday and then restrored the backup. No go, Bootloop city. Got home did most of what was mentioned and nothing happened. Flashed PN through TWRP 3.0.2-1 and flashed my stock rom that came with the phone in Feb (29Q) and restored my EFS (I backup my EFS after any Android version change). The phone booted perfectly. no issues since. Took me about 2 hours total once i got home and was able to start using ADB and Fastboot commands.
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
Also i forgot to add my info....
BL: 03.58
Baseband: 3.72
Varient: Angler-VN2
CPU: 0x20001
eMMC: 64GB Toshiba
DRAM: 3072MB Samsung LDDR4
UNLOCKED
Qfuse status: ENABLED
Off-mode-charge: Enabled
Download Mode: DISABLED
I also forgot, I was enrolled in the beta program obviously since i took the OTA through the phone.
tr4nqui1i7y said:
To clarify, this is for users to upgrade to N, then downgrade back to MM safely. This is not to correct the bootloop, correct?
Click to expand...
Click to collapse
Correct, this is just what I have done. Did not bootloop. Used N successfully for the first time today all day and then came back to MM.
Jammol said:
Correct, this is just what I have done. Did not bootloop. Used N successfully for the first time today all day and then came back to MM.
Click to expand...
Click to collapse
Alright, thanks for clarifying. Didn't want to accidentally add something to the second post haha.
Hi everybody, i would like to remove the devices encription under Security-Encryption
Under Encrypt device i've got Encrypted.
I've tried to restore to factory default, from recovery, from fastboot using format userdata, but, no way.
How i can remove the encryption?
My device is ZE552KL
Thanks
swet90 said:
Hi everybody, i would like to remove the devices encription under Security-Encryption
Under Encrypt device i've got Encrypted.
I've tried to restore to factory default, from recovery, from fastboot using format userdata, but, no way.
How i can remove the encryption?
My device is ZE552KL
Thanks
Click to expand...
Click to collapse
I had a same issue with this device, but I had some experiment.
If your device is unlocked, you can flash TWRP, boot to recovery, wipe, format data.
Backup your data first! It will erase all of your data (Very noob answer)
Totally careful, don't do this if you didn't want a unexpected things. Or something...
The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM.
sensi277 said:
The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM.
Click to expand...
Click to collapse
Thanks!
TWRP isn't allowing me to Mount my Storage because it's asking for a password I don't know.
ZeldaLinkAaron said:
TWRP isn't allowing me to Mount my Storage because it's asking for a password I don't know.
Click to expand...
Click to collapse
I'm having the same issue. I just got my daughter this phone (the 552KL?), downloaded the official Asus bootloader unlocker APK and ran it, then rebooted to the bootloader to flash TWRP.
TWRP installed, but wants a password to unlock it. Before the bootloader unlock, I did put her Google account on the phone, but the tool said it would completely wipe the phone. Either way, I tried her google account password, but it just says wrong password. Same thing when I tried to boot to system.
Any tips?
@Flapjack
Format through twrp
wang1chung said:
@Flapjack
Format through twrp
Click to expand...
Click to collapse
That's what I ended up doing. I got some help on another thread. The problem I'm having now is that I can't format /cache. It's really weird. If I do a full wipe on the phone, it says it can't format it. I even tried formatting it through fastboot ("fastboot erase cache" then "fastboot format cache"), which says "OKAY finished", but doesn't fix the issue when trying to wipe cache inside of TWRP.
This phone is flat out weird compared to other phones. I don't get the bootloader unlock screen. It doesn't seem to want to boot system... it just keeps going to TWRP. On the few times I have gotten to boot into system (after flashing Carbon 6.1 unofficial), it ends up hanging on a blank screen. Windows makes a sound that a new device is connected, so I'm guessing it's connecting in EDL mode or something (no devices show with a "fastboot devices" or a "adb devices").
I really don't know where to go from here. I'm used to working with Axons, Motorolas, and OnePlus phones. They just work.
@Flapjack
The cache issue is a glitch with the build of twrp, it's not a big deal. There's a workaround posted somewhere, can't remember. Just use the file browser and delete the files on it. I think there's only one file that isn't 0 bytes.
Have you flashed magisk?
Sometimes a full wipe (system/data) and then flashing the raw firmware helps. Try magisk first.
wang1chung said:
@Flapjack
The cache issue is a glitch with the build of twrp, it's not a big deal. There's a workaround posted somewhere, can't remember. Just use the file browser and delete the files on it. I think there's only one file that isn't 0 bytes.
Click to expand...
Click to collapse
So you're saying it doesn't need to be actually wiped, I just need to go into cache and delete all the files in there? How about getting it to boot to system? It just keeps booting to recovery. Not sure when it started that, as after the first time I flashed the ROM, I was able to get it to boot to system by pressing the power button when the "bootloader unlocked" screen came up. That isn't working now.
Have you flashed magisk?
Sometimes a full wipe (system/data) and then flashing the raw firmware helps. Try magisk first.
Click to expand...
Click to collapse
For my first non-stock ROM flash, I flashed the Oreo modem, Carbon 6.1 unofficial ROM, ARM64 Gapps nano, and Magisk 16.0... all at once. I tried booting and it looked like it was setting up... but as I mentioned, it just went to a blank screen. After trying a full wipe and seeing the "couldn't wipe cache" message, I figured that was why.
How will flashing Magisk help me with wiping the cache partition or getting the thing to boot right? Sorry for my ignorance.
Flapjack said:
So you're saying it doesn't need to be actually wiped, I just need to go into cache and delete all the files in there?
Click to expand...
Click to collapse
wiping/formatting cache is the same as deleting all the files. Wiping is easier but as I said, doesn't work at the moment.
Flapjack said:
How will flashing Magisk help me with wiping the cache partition or getting the thing to boot right? Sorry for my ignorance.
Click to expand...
Click to collapse
magisk won't help with cache, but it will remove the verity flag that is tripped from having twrp. From my experience, if I don't flash magisk, it'll bootloop.
Yeah.... absolutely nothing I do will get it to boot to system now. I've flashed the ROM and Magisk, but no matter what, it keeps booting to recovery.
There were two folders under /cache... "Lost&Found" and "recovery". I deleted both, but that didn't help.
---------- Post added 5th July 2018 at 12:40 AM ---------- Previous post was 4th July 2018 at 11:44 PM ----------
wang1chung said:
wiping/formatting cache is the same as deleting all the files. Wiping is easier but as I said, doesn't work at the moment.
Click to expand...
Click to collapse
So I take it I did it right? I would say it's "pretty much" the same. Formatting a partition is different than deleting files/folders in an existing partition. Still, if deleting the files/folders is good enough, then that rules out why the system wouldn't boot after the first ROM install attempt. It would also explain why "fastboot erase cache" seems to work, but TWRP still throws an error. Fastboot erase is probably working just fine.
magisk won't help with cache, but it will remove the verity flag that is tripped from having twrp. From my experience, if I don't flash magisk, it'll bootloop.
Click to expand...
Click to collapse
Is there a custom version of Magisk for this phone? I'm just installing the usual magisk 16.0 zip file you can get on their site, but it doesn't seem to be helping with the phone continuously booting into recovery. Is there a way to remove that verity flag via adb?
@Flapjack
Magisk modifies one of the partitions to get around the flag (I believe), not doable through adb.
Standard magisk off their site is fine
Try this:
Format system/data
Flash custom Rom
Flash magisk
"Wipe" cache and davlik
Reboot
OR
Flash the raw firmware
Flash twrp
Flash whichever custom Rom & gapps where needed
Flash magisk
Factory reset and "Wipe" cache and dalvik
Reboot
wang1chung said:
@Flapjack
Magisk modifies one of the partitions to get around the flag (I believe), not doable through adb.
Standard magisk off their site is fine
Try this:
Format system/data
Flash custom Rom
Flash magisk
"Wipe" cache and davlik
Reboot
Click to expand...
Click to collapse
No go. Still just boots into recovery. Here's what the boot screen looks like (then the Asus logo pops up, then recovery loads)
Code:
< More information :
Dm-Verity in EIO mode
Your device software can't be
checked for corruption. Please
lock the bootloader.
Visit this link on another device:
g.co/ABHg.co/placeholder
Your device will shutdown in 10 seconds
I can press the power button to boot immediately, or wait the 10 seconds... which just boots anyway (doesn't shut down). If I press the volume buttons, I get the following options menu:
Power off
Restart
Recovery
Fastboot
Back to previous page
Flash the raw firmware
Flash twrp
Flash whichever custom Rom & gapps where needed
Flash magisk
Factory reset and "Wipe" cache and dalvik
Reboot
Click to expand...
Click to collapse
I haven't tried this yet. Would this be the best guide to follow?
HOW-TO: Go back to Stock Rom on ZE552KL/ZE520KL
https://forum.xda-developers.com/zenfone-3/how-to/how-to-to-stock-rom-recovery-zenfone-3-t3666223
@Flapjack
That is the correct screen for an unlocked bootloader.
Try this guide for the raw firmware instead, and verify it boots to the OS. Then flash twrp and the rom again.
wang1chung said:
@Flapjack
That is the correct screen for an unlocked bootloader.
Try this guide for the raw firmware instead, and verify it boots to the OS. Then flash twrp and the rom again.
Click to expand...
Click to collapse
Grrr... no matter what I do, it won't flash. The guide says to put it in fastboot mode, but the flash tool won't detect it (even though "fastboot devices" shows it just fine). If I boot it to recovery, it'll show up in the tool, but never actually flashes (see screenshot).
Flapjack said:
Grrr... no matter what I do, it won't flash. The guide says to put it in fastboot mode, but the flash tool won't detect it (even though "fastboot devices" shows it just fine). If I boot it to recovery, it'll show up in the tool, but never actually flashes (see screenshot).
Click to expand...
Click to collapse
This is why I stopped using Windows. Maybe try disabling "driver signature verification"? Swap USB ports? My computer has some high power and low power USB ports, certain devices won't work properly in the low power ones. A couple of guides mentioned unplugging and re-plugging the USB.
wang1chung said:
This is why I stopped using Windows. Maybe try disabling "driver signature verification"? Swap USB ports? My computer has some high power and low power USB ports, certain devices won't work properly in the low power ones. A couple of guides mentioned unplugging and re-plugging the USB.
Click to expand...
Click to collapse
That's a good idea. I'm going through a powered hub right now, but who knows...
I'll try that as soon as I get home.
Ok, different computer. This is my laptop I normally use to flash.
This time, I can get it it to start to flash, but with a second or two, it throws an error (see attached).
Flapjack said:
Ok, different computer. This is my laptop I normally use to flash.
This time, I can get it it to start to flash, but with a second or two, it throws an error (see attached).
Click to expand...
Click to collapse
are you running ASUS flash tool with admin privileges?
While I was on vacation my N6P (Android 6.01 MTC20L) decided it was time to give me the bootloop of death - talk about timing!
I have a recent backup I made via Flashfire saved on my PC but I need to get my phone booted - at least temporarily.
As I said my phone is on 6.01, but the fix offered by @XCnathan32 (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) is for Nougat and above. So what are my options?
- Should I use fastboot to upgrade to Nougat or Oreo then apply the fix?
- How do I dirty flash N or O without losing my data?
- Any ideas on the heating notion? Some people have had their phones working using a blow/hair dryer..is it dangerous to heat the phone? Will any parts get damaged?
Any response would be useful to me, thanks!
boeder9 said:
While I was on vacation my N6P (Android 6.01 MTC20L) decided it was time to give me the bootloop of death - talk about timing!
I have a recent backup I made via Flashfire saved on my PC but I need to get my phone booted - at least temporarily.
As I said my phone is on 6.01, but the fix offered by @XCnathan32 (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) is for Nougat and above. So what are my options?
- Should I use fastboot to upgrade to Nougat or Oreo then apply the fix?
- How do I dirty flash N or O without losing my data?
- Any ideas on the heating notion? Some people have had their phones working using a blow/hair dryer..is it dangerous to heat the phone? Will any parts get damaged? Any response would be useful to me, thanks!
Click to expand...
Click to collapse
More information would be useful to determine whether you really have BLOD or just bootlooping. What were you doing when it bootlooped? Was it just spontaneous? Are you able to access stock recovery or TWRP? Do you have a stable fastboot mode? If so, two options to try would be to use ADB to update using a newer version full OTA (eg. 7.0.0 (NRD90T)) or flash a full image (not OTA) with flash-all.bat, removing the -w (wipe) switch. Both of these methods will leave your data intact. If you don't have access to recovery mode (bootloops on selecting) or an unstable fastboot mode, then you are pretty much left with the hairdryer.
v12xke said:
More information would be useful to determine whether you really have BLOD or just bootlooping. What were you doing when it bootlooped? Was it just spontaneous? Are you able to access stock recovery or TWRP? Do you have a stable fastboot mode? If so, two options to try would be to use ADB to update using a newer version full OTA (eg. 7.0.0 (NRD90T)) or flash a full image (not OTA) with flash-all.bat, removing the -w (wipe) switch. Both of these methods will leave your data intact. If you don't have access to recovery mode (bootloops on selecting) or an unstable fastboot mode, then you are pretty much left with the hairdryer.
Click to expand...
Click to collapse
Thanks for the response.
- Phone was idle for a few moments thats when the bootlooping started.
- I was rooted (bootloader unlocked) with TWRP, I am unable to access it, takes me to the bootloop again
- What do you mean by stable fastboot. I can get to the fastboot mode by power button, volume down, remains there (if that's what you mean?)
boeder9 said:
Thanks for the response.
- Phone was idle for a few moments thats when the bootlooping started.
- I was rooted (bootloader unlocked) with TWRP, I am unable to access it, takes me to the bootloop again
- What do you mean by stable fastboot. I can get to the fastboot mode by power button, volume down, remains there (if that's what you mean?)
Click to expand...
Click to collapse
No access to Recovery mode is one hallmark of the BLOD. Without Recovery you have no ADB, even if it was enabled previously. Stable fastboot mode means you can actually flash something successfully and it completes before bootlooping again. Many people who are unlocked can start flashing, but it won't finish -or- flashing completes successfully, but the phone never boots up. Try the following: fastboot format your system, userdata, and cache and observe for errors. Do these 3 complete successfully? Next, fastboot FLASH the latest TWRP to your recovery partition.... errors? Try fastboot BOOT the same in an effort to get a working Recovery where you have some additional tools. If these fail, you are looking at either RMA if eligible or replacing the phone.
fastboot format system
fastboot format userdata
fastboot format cache
v12xke said:
No access to Recovery mode is one hallmark of the BLOD. Without Recovery you have no ADB, even if it was enabled previously. Stable fastboot mode means you can actually flash something successfully and it completes before bootlooping again. Many people who are unlocked can start flashing, but it won't finish -or- flashing completes successfully, but the phone never boots up. Try the following: fastboot format your system, userdata, and cache and observe for errors. Do these 3 complete successfully? Next, fastboot FLASH the latest TWRP to your recovery partition.... errors? Try fastboot BOOT the same in an effort to get a working Recovery where you have some additional tools. If these fail, you are looking at either RMA if eligible or replacing the phone.
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
Do these commands (espec system and userdata) erase my data and app data/personal files?
Ill try these and get back
boeder9 said:
Do these commands (espec system and userdata) erase my data and app data/personal files? Ill try these and get back
Click to expand...
Click to collapse
Formatting userdata will, but you won't be saving anything if you can't access recovery. If you like, try formatting system and cache first. Look for errors. Then try fastboot flashing or fastboot booting TWRP. The action of formatting each partition will tell you if there is a problem with the internal memory, and correct it (if possible).
v12xke said:
Formatting userdata will, but you won't be saving anything if you can't access recovery. If you like, try formatting system and cache first. Look for errors. Then try fastboot flashing or fastboot booting TWRP. The action of formatting each partition will tell you if there is a problem with the internal memory, and correct it (if possible).
Click to expand...
Click to collapse
OK so I did fastboot format cache, finished fine (see attached)
Haven't done format system, is it safe? what will the system formatting erase?
As for TWRP do you mean fastboot flash recovery twrp.img?
EDIT: after the cache format I'm getting 1-2 red LED flashes before each bootloop, is this the battery being down? If I turn off the device, hook up the charger it shows a full battery with electricity charge sign and phone boots again to bootloop.
boeder9 said:
OK so I did fastboot format cache, finished fine (see attached)
Haven't done format system, is it safe? what will the system formatting erase?
As for TWRP do you mean fastboot flash recovery twrp.img?
EDIT: after the cache format I'm getting 1-2 red LED flashes before each bootloop, is this the battery being down? If I turn off the device, hook up the charger it shows a full battery with electricity charge sign and phone boots again to bootloop.
Click to expand...
Click to collapse
System is a read only partition. Formatting it will not cause any data loss of yours, but will temporarily render the phone not bootable... BUT It can easily be restored via fastboot from any factory image. You just extract and flash the system image back to the system partition. Userdata is your personal data. When you format that partition your personal data will be gone. You did mention you had a FF backup so I'm guessing that was on the backup.
Yes on flashing TWRP. If after FLASHING twrp you cannot access Recovery, then try BOOTING recovery- fastboot boot recovery twrp.img
If you get to a point where nothing is working and you decide to format system and userdata and they complete successfully, you can flash a full Google image using flash-all.bat
Not sure about the LED's but just make sure your battery is close to fully charged. You didn't ever mention an battery issue, so there shouldn't be one. If in doubt hook the charger up and let it sit before proceeding.
@v12xke
Thank you for all your help. I left the phone on charge and let it bootloop for a good period of time and went out, came back and it was booted. I disabled the big clusters as suggested by @nicotinic in ElementalX and the device appears to be working fine aside from a little lag. I can live with that
Currently doing a little ADB pull, then will clear some space for a full nandroid backup!
Thanks a bunch to you both.
Hey guys, I already tried reddit but I figured I would ask here before I bite the bullet and factory reset my phone.
The problem I keep having is that when I boot my phone, I get to the home screen and immediately get the error "System UI has stopped". The screen then goes black and I can't interact with anything except for my camera and music player using the second screen.
I am not rooted, but I do have USB debugging enabled.
Things I have tried:
1. Rebooting into recovery and wiping cache
-I get to recovery and it gives me "No Command". I have no way to get to the actual recovery to wipe the cache. I have tried holding Vol Up, Vol Down, Power+Up, and Power+Down for 30s ea
2. Reinstalling the SystemUI.apk
-Denied due to no root
3. Restarting the SystemUI.apk
-I can force-stop and enable the com.android.systemui and com.lge.provider.systemui packages, but nothing happens
4. Using adb to perform a full backup so I don't lose any data
-Failed because I can't confirm the backup using my phone. The window to set a password and begin the backup never appears
5. Using Vysor to control my phone from my pc
-It just shows the dead black screen
6. Using the LG Backup tool
-Can't connect, says that I need to enable MTP on the phone
7. Enabling MTP using adb
-Can't figure out how to do this without root and editing files
I feel like I'm all out of options, but I feel like my phone isn't even that ****ed up. I can still use the quick apps and everything loads fine. It's just this System UI that eats ****. Is there a way to reset system apps using adb? I'm really at a loss here but I don't want to give up quite yet.
Thanks
paulmcgranite said:
Hey guys, I already tried reddit but I figured I would ask here before I bite the bullet and factory reset my phone.
The problem I keep having is that when I boot my phone, I get to the home screen and immediately get the error "System UI has stopped". The screen then goes black and I can't interact with anything except for my camera and music player using the second screen.
I am not rooted, but I do have USB debugging enabled.
Things I have tried:
1. Rebooting into recovery and wiping cache
-I get to recovery and it gives me "No Command". I have no way to get to the actual recovery to wipe the cache. I have tried holding Vol Up, Vol Down, Power+Up, and Power+Down for 30s ea
2. Reinstalling the SystemUI.apk
-Denied due to no root
3. Restarting the SystemUI.apk
-I can force-stop and enable the com.android.systemui and com.lge.provider.systemui packages, but nothing happens
4. Using adb to perform a full backup so I don't lose any data
-Failed because I can't confirm the backup using my phone. The window to set a password and begin the backup never appears
5. Using Vysor to control my phone from my pc
-It just shows the dead black screen
6. Using the LG Backup tool
-Can't connect, says that I need to enable MTP on the phone
7. Enabling MTP using adb
-Can't figure out how to do this without root and editing files
I feel like I'm all out of options, but I feel like my phone isn't even that ****ed up. I can still use the quick apps and everything loads fine. It's just this System UI that eats ****. Is there a way to reset system apps using adb? I'm really at a loss here but I don't want to give up quite yet.
Thanks
Click to expand...
Click to collapse
https://rongi.github.io/kotlin-blog/adb/android/2017/06/30/adb-clear-application-cache.html
Or possibly-
ADB command: fastboot erase cache
Mysticblaze347 said:
https://rongi.github.io/kotlin-blog/adb/android/2017/06/30/adb-clear-application-cache.html
Or possibly-
ADB command: fastboot erase cache
Click to expand...
Click to collapse
Hi, thanks for the response. I can use all the help I can get.
I tried doing fastboot erase cache, but I get this error:
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' FAILED (remote: 'unknown command')
Finished. Total time: 0.043s
I think I ****ed it up by having Secure Start Up enabled.
As for the link, I've tried wiping the cache for both the com.android.systemui and the com.lge.provider.system but neither have done anything after a reboot even though I get a "success" from adb.
I feel like theres gotta be a fix here somewhere, the phone loads everything fine including my icons and then just crashes on that stupid systemui.
paulmcgranite said:
Hi, thanks for the response. I can use all the help I can get.
I tried doing fastboot erase cache, but I get this error:
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' FAILED (remote: 'unknown command')
Finished. Total time: 0.043s
I think I ****ed it up by having Secure Start Up enabled.
As for the link, I've tried wiping the cache for both the com.android.systemui and the com.lge.provider.system but neither have done anything after a reboot even though I get a "success" from adb.
I feel like theres gotta be a fix here somewhere, the phone loads everything fine including my icons and then just crashes on that stupid systemui.
Click to expand...
Click to collapse
..do not format unless you want all gone. If all fails...sadly a factory reset may be in store. I recommend rooting if possible of restore an LG backup if u have one.
---------- Post added at 08:23 PM ---------- Previous post was at 08:22 PM ----------
paulmcgranite said:
Hi, thanks for the response. I can use all the help I can get.
I tried doing fastboot erase cache, but I get this error:
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' FAILED (remote: 'unknown command')
Finished. Total time: 0.043s
I think I ****ed it up by having Secure Start Up enabled.
As for the link, I've tried wiping the cache for both the com.android.systemui and the com.lge.provider.system but neither have done anything after a reboot even though I get a "success" from adb.
I feel like theres gotta be a fix here somewhere, the phone loads everything fine including my icons and then just crashes on that stupid systemui.
Click to expand...
Click to collapse
..do not format unless you want all gone. If all fails...sadly a factory reset may be in store. I recommend rooting if possible or restore an LG backup if u have one.
Mysticblaze347 said:
..do not format unless you want all gone. If all fails...sadly a factory reset may be in store. I recommend rooting if possible of restore an LG backup if u have one.
---------- Post added at 08:23 PM ---------- Previous post was at 08:22 PM ----------
..do not format unless you want all gone. If all fails...sadly a factory reset may be in store. I recommend rooting if possible or restore an LG backup if u have one.
Click to expand...
Click to collapse
Yeah, I exhausted my options and I needed my phone to be useable for work, so I bit the bullet and factory reset. I lost some data, but I definitely learned to backup often...
i95swervin said:
H918 has limited fastboot commands.
You didnt specify which android version your on or rom but what you need to do is either reflash the rom or replace the systemui. Your phone isnt bricked.
Click to expand...
Click to collapse
Hey thanks for the reply. I ended up factory resetting due to time constraints but to answer your questions:
I was on stock Oreo, unrooted. So realistically there was no way for me to reflash or replace the systemui without root, which would require factory resetting my phone anyway (correct me if I'm wrong).
paulmcgranite said:
Hey thanks for the reply. I ended up factory resetting due to time constraints but to answer your questions:
I was on stock Oreo, unrooted. So realistically there was no way for me to reflash or replace the systemui without root, which would require factory resetting my phone anyway (correct me if I'm wrong).
Click to expand...
Click to collapse
System ui cant be replaced without root access