Related
Tired, Frustrated and Helpless I am at the moment.
My A500 was running OK with a Jelly Bean Rom( I forgot which one) with Skrilax_CZ's bootloader V8 and CWM v5.5.0.4.
I decided to try a different Jelly Bean Rom. Forgot to keep a CWM backup and my misery started.
Any rom and gaps will install fine. But after reboot it will be stuck on Cyogenmod or Android LOGO. I have tried several ROM. Exact same result.
This happened a few months back and after trying numerous times I gave up for that time.
But I need to get the tablet back to working.
So, since yesterday I have been trying my best to get this one to work.
Started with "[A500 & A501] Android 4.4.4 (OmniROM unofficial)".
According the installation note for that rom, I installed CWM 6.0.4.5 on secboot following the "[Recovery]CWM 6.0.4.5[UPDATED WITH INSTRUCTIONS][25/12/2013]" process.
Same exact situation. ROM will install then after reboot it will be stuck on OS load.
Tried with a few other older rom such as CM10-FLEX_V6Supercharged_Rev3.4. Same issue.
I even, Installed TWRP recovery openrecovery-twrp-2.6.3.0-a500 on secboot. Same Issue.
Then, Updated Skrilax_CZ's bootloader V8 to Skrilax_CZ's bootloader V9. Same Issue.
Weird thing is now when I go to "CWM 6.0.4.5" from "Skrilax_CZ's bootloader V9", CWM doesn't really let me do any task. Any menu I enter on CWM 6.0.4.5 it freezes and then reboots the tablet. But initially when I first installed CWM 6.0.4.5 on secboot it worked for the first few times.
I am a noob in this. I do not want to try anything else myself as I think I will eventually brick the device and there will be no coming back.
I have searched on XDA for this issue. Many other people have similar issue with a500 but I couldn't find any situation same as mine.
Need help from you awesome people.
I do not want to give up on this tablet. But without your HELP I am lost.
Please HELP.
Need help on this please.
iamtapu said:
Need help on this please.
Click to expand...
Click to collapse
Have you tried wiping the device in fastboot mode? If not, try that!
The partitions to wipe are system, data and cache. The command is "fastboot erase cache".
HenrikE said:
Have you tried wiping the device in fastboot mode? If not, try that!
The partitions to wipe are system, data and cache. The command is "fastboot erase cache".
Click to expand...
Click to collapse
tried that. same issue.
it keeps circling on cyanogenMOD logo.
Apologies for reply late. I was not well and could not attend to you reply.
anything else i can try?
Please help.
Hey Bro,
I had exactly the same issue. What I did to solve it, was to delete all folders manually. Boot to recovery and choose "mounts and storage". Unmount everything and then format every folder. Then Wipe everything again. Reboot and flash the image with recovery. Then everything should work fine.
Same here
I have had exactly the same issue and haven't yet found a decent solution.
Mine was stuck on the Acer logo with the stock ICS ROM.
I found my CPUID and SBK, the linux way.
I tried everything you tried, managed to have bootloader V9 installed, TWRP as a recovery (Thor's version), CWM as secboot.
I was able to wipe and flash with no errors, but it would always stuck on the Acer logo. No custom ROM would ever boot.
I will definitely try Unimatrix-zero's solution and tell you guys if it worked for me.
So far, the only thing that worked for me was to use an EUUs package (GEN1) to get back to stock HC 3.01.
As you may guess, there are no more OTA updates via wifi in 2014.
So I downloaded several update packages and so far I only managed to update to HC 3.2. I haven't yet found a working package for stock ICS.
Anyway, if Unimatrix-zero's workaround actually works, a custom ICS ROM will do the trick for me.
Unimatrix-zero said:
Hey Bro,
I had exactly the same issue. What I did to solve it, was to delete all folders manually. Boot to recovery and choose "mounts and storage". Unmount everything and then format every folder. Then Wipe everything again. Reboot and flash the image with recovery. Then everything should work fine.
Click to expand...
Click to collapse
Significant result but did not resolve the issue.
As you have mentioned, I have wiped off everything that i can find in the recovery menu.
rebooted after that to recovery and for the first time I could go to TWRP 2.7.
tried to install a custom rom. but same issue. Either it reboots when I tried omni rom 4.4.4 on the "booting from primary" menu or the CM blue circle going on forever, when I tried with a CM 10.1 rom.
and just now after trying the cm 10.1 rom it went back to the way it was before. now the TWRP 2.7 will just keep on blinking on the screen .
Help bro...help....
You can try the following fastboot commands to wipe your device:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
And then flash the rom.
Unimatrix-zero said:
You can try the following fastboot commands to wipe your device:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
And then flash the rom.
Click to expand...
Click to collapse
you are a GOD SEND for me.:highfive::highfive::highfive::victory::victory::victory::victory::victory:
Did the following as you mentioned.
Code:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
boot recovery TWRP 2.7.
Installed OMNI 4.4 rom.
Installed GAPS.
NOW its booting to OMNI rom...
awesomeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
Hi everyone,
tonight I was trying to install the Stagefright OTA using this guide: http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
The only thing I got was an android with a red triangle on it. So I went back, did a total phone reset, reinstalled the TWRP (fastboot flash twrp.img) and restored my backup. Sadly, the phone keeps rebooting to the TWRP as if there's nothing on it except the TWRP.
I've got the eu model and I can't find any factory image (or image in general) to flash on the device.
EDIT:
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
jco23 said:
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
Click to expand...
Click to collapse
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
edmael said:
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
Click to expand...
Click to collapse
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
jco23 said:
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
Click to expand...
Click to collapse
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
edmael said:
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
Click to expand...
Click to collapse
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
mastarifla said:
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
Click to expand...
Click to collapse
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
edmael said:
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
Click to expand...
Click to collapse
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
another thing I have noticed is that my phone kept getting stuck on the boot image screen (failed to proceed to the boot animation screen). to resolve this, I made sure to flash SU via TWRP after flashing my ROM via TWRP (or restoring a nandroid).
mastarifla said:
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
Click to expand...
Click to collapse
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
you may need to wipe internal storage and mfastboot everything from scratch...
jco23 said:
you may need to wipe internal storage and mfastboot everything from scratch...
Click to expand...
Click to collapse
Already did that (the first time I didn't even tried booting with BT Tools, but the effects were the same), but nothing new happened.
edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
mastarifla said:
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
Click to expand...
Click to collapse
Yes, tried, but nothing happens (except that it boots when I go into BT Tools).
I think there's something wrong with my partition scheme because it always go straight to TWRP.
If I were on a GNU/Linux distro I'd check the grub config because it seems it boot from the wrong partition, but on Android I don't know if/how that's possible.
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
did you happend to type "mfastboot flash boot twrp.img"? that could be the issue, as the command should be "mfastboot flash recovery twrp.img, right?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
jco23 said:
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
Click to expand...
Click to collapse
Don't be sorry, you're helping me!
Also: I'm not much frustrated since I have a working phone right now, I just need do avoid rebooting it
I tried to flash the stock recovery (found here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628, used this: XT1052_GHOST_RETEU_5.1_LPA23.12-15_cid7_CFC.xml.zip) but if I'm not wrong (did that yesterday in the late night) it just booted to the Android with the red triangle on it (so, no booting for me).
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
edmael said:
Don't be sorry, you're helping me!
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
Click to expand...
Click to collapse
You can revert it by taking the boot.img from the 5.1 zip and flashing that using the command...
mfastboot flash boot boot.img
The partitioning you are mentioning is probably the gpt.bin, but that is typically done near the very beginning of the flashing process
here's what I would do:
boot into recovery
connect phone to PC, copy your nandroid and any other files from the SDcard to your PC
within recovery, wipe cache/dalvik/data/internal storage
reboot to bootloader
run the mfastboot commands as shown (but use the getvar-download....) in place of editing the xml zip file
after running the mfastboot commands, let the phone boot up to stock and establish itself
reboot to bootloader and flash TWRP
again, just a suggestion on what I would do - seems like @mastarifla is a great resource and is more knowledgeable than me, so maybe you'll get some confirmation.
good luck!
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
edmael said:
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
Click to expand...
Click to collapse
So your phone thinks that the bootloader is your recovery?
That is actually pretty strange, you could take a look at the Linux kernel on Motorola's GitHub and see if it has any info on the partitioning structure or what happens when a reboot-bootloader command is sent to the phone
It sounds as if the recovery and the bootloader swapped places, as the fastboot menu is considered a part of the bootloader, and if you are not seeing that on the hardware key bootup, then there is something definitely wrong, if you do reboot-recovery does it take you to the bootloader/fastboot menu?
Hello recently my phone battery went dead than after I charged it I got "optimizing apps" and it just couldn't finish. So then I did "flash stock and unroot" and now I'm stuck with bootloop. Wiping data with stock recovery didn't work, I've tried it many times.
Did you try using fastboot commands to erase userdata, flash userdata.img, and factory wipe before first booting the phone?
I think not, please tell me how to do that :$
Extract the userdata.img file from the stock Google ROM you are flashing.
Boot the phone into fastboot mode, connect the phone to the computer, type "fastboot erase userdata" and press enter. Then type "fastboot flash userdata userdata.img" and press enter. The userdata.img file should be in the same directory where you execute fastboot commands. When the flash has completed, use the volume and power button to go into recovery, wipe data, and reboot.
My PC doesn't even want to recognize my phone...
http://i.imgur.com/E7MYAKX.png
Is the phone in fastboot before it is connected to the computer?
Yeah, it is. Edit: I think I made a mistake because i wrote "adb devices" instead of "fastboot devices". Edit 2: Still stuck in bootloop. Somehow I managed to instal CM 12 but now I have infinite "starting apps".
It could be stuck because you need to flash the userdata.img file.
I have a similar issue here, Wiped, formatted, resized, reflashed bootloader, radio, recovery, system, userdata, cache. Tried stock lollipop, cm12, cm13, everytime each rom flashes successfully. However, upon loading the custom bootloader animation, it stucks there forever. This happens matters not that flash each partition individually, install the zip via TWRP, or ADB sideload. Is there a live boot/verbose option so I can see where it is hanging? I tried so many times it almost feel like it is a hardware issue.
After flashing each stock partition, including userdata.img, are you booting into stock recovery to perform a factory wipe before the first boot of the newly-flashed stock ROM?
audit13 said:
After flashing each stock partition, including userdata.img, are you booting into stock recovery to perform a factory wipe before the first boot of the newly-flashed stock ROM?
Click to expand...
Click to collapse
so I tried to enter recovery with stock 5.1, android with red ! pops up, but no "no command" line. I can't press volume up/power to enter recovery.. thought it is a fluke, I reflashed everything with 4.4.4 stock, same problem, cannot enter stock recovery. what am I missing here?
edit: dumb question, I held the button in wrong sequence, yes I factory wiped and still hangs on boot image
When you went into recovery, did you see an error line at the bottom that said something like invalid format or invalid argument? In recovery, did screen at the bottom say that the cache and data were formatted?
audit13 said:
When you went into recovery, did you see an error line at the bottom that said something like invalid format or invalid argument? In recovery, did screen at the bottom say that the cache and data were formatted?
Click to expand...
Click to collapse
enter recovery "fail to mount cache"
factory reset
"format system"
"format cache"
done
reboot----> hangs
That is what I was hoping to see but it's strange that the phone still hangs.
Maybe boot back into ft aboot be run the commands "fastboot erase cache", "fastboot erase userdata" and reboot.
audit13 said:
That is what I was hoping to see but it's strange that the phone still hangs.
Maybe boot back into ft aboot be run the commands "fastboot erase cache", "fastboot erase userdata" and reboot.
Click to expand...
Click to collapse
done, phone still hangs, do I just need go get another motherboard?
I'm out of ideas and another motherboard may be the only solution. You've done everything I would have done.
ddvche said:
done, phone still hangs, do I just need go get another motherboard?
Click to expand...
Click to collapse
FYI I took the unbootable motherboard out, swap it into a nexus with broken digitizer. Turned it on, and it booted.... so the fix wasn't replacing the motherboard... it was replacing everything else...... probably was a connection issue yes?
In post number 13, you formatted the system?
audit13 said:
In post number 13, you formatted the system?
Click to expand...
Click to collapse
Heh, I think I meant "internal storage"/"data" partition. If no OS it wouldn't hang, just reboot to recovery if I remember correctly.
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?
Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.
Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this
Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?
leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?
edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.
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?