Develop Bugs

Can't decrypt Galaxy Nexus after OTA

Just applied the 4.0.2 OTA update to my GSM Galaxy Nexus and after the reboot, even though i type in the correct password, my phone wont decrypt.
I read on android forums people with the 4.0.3 OTA having the same problems.
How can i reset my phone? How does Odin work? Somehow i am stuck at the screen with the android and his open chest

ok i got odin workin, needed to install the android sdk, wiping my phone now

Please note: YOU WILL LOSE ALL DATA
everything seems ok, i got into odin mode like this:
-connect your GN with usb to your computer
-start with power + volume down
-use volume up / down to select recovery mode
-confirm by pressing power
-you will see an android with a triangle
-press power and volume
-select factory reset
-confirm with power
-reboot
this worked for me only after i installed the android sdk, before that somehow i was stuck at the android with his chest open and couldnt select anything because somehow my device wasnt recognized
hope this helps

This also caught me out. Not happy.
Method I used (posted on OTA thread) worked without installing SDK:
Power off
Hold Volume + , volume - and power
You should get a green android image with the body opened with "Start" on the screen
Press Down till you get to recovery mode
Press power
Phone will reboot
You will then get same image of android (smaller) with red warning triangle
Wait a minute or two and then press volume + and power (not sure exactly what I did for this maybe it's just waiting)
Use volume down to select wipe data/factory reset and hit power
Select Yes - delete all user data and hit power
Once done select reboot system now and hit power
You are now back to zero and can start again.

Hi I have roote, and installed cwm, I the applied the encryption proces, now I want to flash a ROM (revert to stock) thru cwm, it says can't mount SD card. I try do a factory reset through cwm but also says can't mount....
Any tips on how to remove the encryption?

tc4101 said:
Hi I have roote, and installed cwm, I the applied the encryption proces, now I want to flash a ROM (revert to stock) thru cwm, it says can't mount SD card. I try do a factory reset through cwm but also says can't mount....
Any tips on how to remove the encryption?
Click to expand...
Click to collapse
Have you tried using fastboot to wipe userdata and system and then to flash the stock image?

andrewNY said:
Have you tried using fastboot to wipe userdata and system and then to flash the stock image?
Click to expand...
Click to collapse
how do I do that? is that thru cwm?

tc4101 said:
how do I do that? is that thru cwm?
Click to expand...
Click to collapse
The only way to decrypt an encrypted phone is using fastboot. Fastboot is a developer tool that runs on your computer. You need to download the full Google factory image or a full rom, and flash all of the files to your phone using fastboot.
CWM and other recovery software will not be able to factory reset the device.

Sienna Hanon said:
The only way to decrypt an encrypted phone is using fastboot. Fastboot is a developer tool that runs on your computer. You need to download the full Google factory image or a full rom, and flash all of the files to your phone using fastboot.
CWM and other recovery software will not be able to factory reset the device.
Click to expand...
Click to collapse
can u give us a link on how to use "fastboot" ? every tutorial i seen seems to use CWM....

tc4101 said:
can u give us a link on how to use "fastboot" ? every tutorial i seen seems to use CWM....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895

Sienna Hanon said:
[snip]
The only way to decrypt an encrypted phone is using fastboot.
Click to expand...
Click to collapse
This is not entirely true. You should be able to use TWRP 2.2.0. As well, have a look through this thread.

andrewNY said:
Have you tried using fastboot to wipe userdata and system and then to flash the stock image?
Click to expand...
Click to collapse
What is the command you have to type in prompt to do this?
I am also having trouble decrypting my phone. Factory reset it a couple of times and it is still encrypted.

TWRP and FFF Installed; Cannot Boot Fully

Thanks in advance for the help. Like many others I have searched for something similar to what I am experiencing but have not had luck finding it. So here goes my "special" situation:
Background:
-I use a PC with Windows 7 installed
-I downloaded KFU (v. 0.9.6) and ran install_drivers
-Connected KF and ran "run"
-Selected Option 2 for a Permanent Root with Superuser
-I am not sure if this step fully worked because during the root it seemed like my PC and KF disconnected from each other and my PC flashed a message about "smartphone no attached" that I didn't catch the exact verbiage of
-I restarted my KF and found myself in the TWRP (v. 2.2.0) interface
-Followed directions from another post and selected "reboot" and then "system"
-This worked and it loaded the familiar KF home screen
-From here I again ran the "run" file from KFU
-This time I selected Option 6 for extras, then Option 1 for Google Apps / Go Launcher Ex
-The ADB Status was Online and away the install went
-Here I am not totally sure what happened, but I believe a similar problem happened as before with m PC and KF losing connection during install
-Either way, I landed on the KF boot screen (blue Fire, which implies I have FFF installed v. 1.4);
-It was stuck here so I tried the Unbrick Utility and several other suggestions from posts and was once again able to get back to the TWRP interface
-Here, I thought I had everything figured out and again navigated to "reboot" and then "system"
-This time however, I did not go back to the KF home screen and instead got right back to the TWRP interface
-It almost seemed like it tried to load the home screen (yellow word "fire"); but quickly restarted again and went back to the blue fire and then the TWRP interface
-From here, I have tried several different approached to no avail, but here is the state I am in to the best of my knowledge:
1. It appears I have FFF and TWRP installed
2. I may or may not have the Google Aps installed
3. My drivers are all still installed, but the only time my computer recognizes it is the split second when the yellow word "fire" comes up on a system reboot.
I think I am close, but maybe not. Any help is greatly appreciated and let me know if I need to provide more information. Tried to be thorough but this is my first crack at this.

hold the power button down for 20 seconds then power on when you see the white kindle blue fire press your power button to get boot menu
then select recovery from the boot menu with the power button
Download this rom http://forum.xda-developers.com/showthread.php?t=1439916
select mount in twrp transfer this rom zip to your sd card but dont place it in a folder
then select unmount
go to install make sure you can find it
then hit the home button select wipe
wipe factory reset
wipe cache
wipe dalvik
wipe system
then go home again
select install again tap on rom zip flash it let it finish
then select reboot
enjoy your lovely rooted kindle fire
this is just rooted stock with playstore if you wish to try other roms use the same method with the exception of making a backup first

Thepooch said:
select mount in twrp transfer this rom zip to your sd card but dont place it in a folder
then select unmount
go to install make sure you can find it
Click to expand...
Click to collapse
Thanks for the help! I have the ROM downloaded but am still cannot get my KF to be recognized on my PC to transfer files. Any suggestions on how to get the two to communicate?

Linux LiveUSB plus this:
http://forum.xda-developers.com/showpost.php?p=30629067
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
...or you could just pay attention to the directions Thepooch gave you. Just a thought.

soupmagnet said:
Linux LiveUSB plus this:
http://forum.xda-developers.com/showpost.php?p=30629067
...or you could just pay attention to the directions Thepooch gave you. Just a thought.
Click to expand...
Click to collapse
Thanks for getting back to me once more. I did try the directions Thepooch gave me exactly and no connection. Mounting did not allow my KF to connect. I also went into Linux and tried your code to get my KF to connect to my PC. I am no pro, but it seemed your first script just displayed a string and was rather frustrating. Inside one of the folders appeared to be a more complete script (with options 1 and 2) that your "READ ME" instructions hinted at (install_it file). I must be missing something. Would you be willing to provide more guidance on the Linux connection?
I appreciate all the help.

Yeah double click on runit then run in terminal.... Hit selection number 1 hit enter when it prompts for password... let it finish. ...Then hit selection number 2.... Then enter a y hit enter it will reboot.. Then try adb devices in a terminal..

SOLVED!
Thepooch said:
Yeah double click on runit then run in terminal.... Hit selection number 1 hit enter when it prompts for password... let it finish. ...Then hit selection number 2.... Then enter a y hit enter it will reboot.. Then try adb devices in a terminal..
Click to expand...
Click to collapse
Thanks to both of you for all the help! These little added details helped me through the home stretch. I still did not use the ""run_it.sh" script in terminal. I went straight to the "install_it.sh" file. I then followed your directions and had no troubles. The only change I had to do was manually toggle by booting selection after it kept rebooting to TWRP.

noobathon said:
Thanks to both of you for all the help! These little added details helped me through the home stretch. I still did not use the ""run_it.sh" script in terminal. I went straight to the "install_it.sh" file. I then followed your directions and had no troubles. The only change I had to do was manually toggle by booting selection after it kept rebooting to TWRP.
Click to expand...
Click to collapse
I think I'm going to have to change the title of that thread. I really did have faith in people.
There are instructions in that thread and in the README, and nowhere does it say to run any script other than "run_it.sh". There are separate sets of scripts for good reason.
If you had paid attention to the OP, you would have found what to do in your particular situation.

[Q] cant install root file from internal storage?

Hey guys im trying to root my device so i can install some lightweight custom roms. Ive been following this guide i found online
http://androidcritics.com/how-to-root-and-install-clockworkmod-recovery-on-galaxy-s3-i747/
I basically did this
Installing Clockwork Recovery Mod
Find the recovery image file which is clockworkmod.tar
On your Samsung Galaxy S3 I747, press and hold down the volume down, power, and home buttons
Once your at the warning screen, press volume up to accept
Launch the Odin program from your computer
In Odin, find the PDA tab and click it
Find the clockworkmod.tar.md5 file in the unzipped recovery image file
Press start to begin flashing the recovery mod
BE PATIENT! and wait until your device reboots
Once your device has fully rebooted, you can start installing root
It loaded on the phone fine. I then did this
Installing Root
Transfer the root.zip file onto your phone from your computer
Make sure you connect your s3 to your computer and find the root zip file and put it in your downloads folder.
Enter clockwork recover mod by holding down the volume up, power, and home buttons
Navigate by using the volume buttons to Install Zip > Choose Zip from Internal SD card > Navigate to the downloads folder> Select
Be Patient! and wait until your device is finished
Once the process is finished, you can select Reboot
Once your device has rebooted, launch the Google Play Store app
Search “SuperuserSU” and select the first app that shows in the search results
Install this app
Once it has finished installing, your done!
The only problem is I cant navigate to the option "install zip from internal sd card" I simply dont have though's options here is what I have when hold volume up reset and home
"reboot system now
apply update from ADB
apply update from external storage (which i dont have)
wipe data/factory reset
wipe cache partition
apply update from cache
When i hit apply update from ADB it says "now send the package you want to apply to the device with "adb sideload <filename>"...
Im wondering if the original flash didnt go thru? Why dont I have the options that I should?
Any help would mean the world trying to get this puppy up asap!
regards,
Eddy

eddyg519 said:
Hey guys im trying to root my device so i can install some lightweight custom roms. Ive been following this guide i found online
http://androidcritics.com/how-to-root-and-install-clockworkmod-recovery-on-galaxy-s3-i747/
I basically did this
Installing Clockwork Recovery Mod
Find the recovery image file which is clockworkmod.tar
On your Samsung Galaxy S3 I747, press and hold down the volume down, power, and home buttons
Once your at the warning screen, press volume up to accept
Launch the Odin program from your computer
In Odin, find the PDA tab and click it
Find the clockworkmod.tar.md5 file in the unzipped recovery image file
Press start to begin flashing the recovery mod
BE PATIENT! and wait until your device reboots
Once your device has fully rebooted, you can start installing root
It loaded on the phone fine. I then did this
Installing Root
Transfer the root.zip file onto your phone from your computer
Make sure you connect your s3 to your computer and find the root zip file and put it in your downloads folder.
Enter clockwork recover mod by holding down the volume up, power, and home buttons
Navigate by using the volume buttons to Install Zip > Choose Zip from Internal SD card > Navigate to the downloads folder> Select
Be Patient! and wait until your device is finished
Once the process is finished, you can select Reboot
Once your device has rebooted, launch the Google Play Store app
Search “SuperuserSU” and select the first app that shows in the search results
Install this app
Once it has finished installing, your done!
The only problem is I cant navigate to the option "install zip from internal sd card" I simply dont have though's options here is what I have when hold volume up reset and home
"reboot system now
apply update from ADB
apply update from external storage (which i dont have)
wipe data/factory reset
wipe cache partition
apply update from cache
When i hit apply update from ADB it says "now send the package you want to apply to the device with "adb sideload <filename>"...
Im wondering if the original flash didnt go thru? Why dont I have the options that I should?
Any help would mean the world trying to get this puppy up asap!
regards,
Eddy
Click to expand...
Click to collapse
Sounds like the root method you are using is just way to complicated. Follow this one here http://forum.xda-developers.com/showthread.php?t=1739426 it has prerooted firmwares that you just install with odin and you are done (cwm included). Just make sure you grab the right firmware for your carrier.
If I have helped you out, slap that thanks button.

aeppacher said:
Sounds like the root method you are using is just way to complicated. Follow this one here http://forum.xda-developers.com/showthread.php?t=1739426 it has prerooted firmwares that you just install with odin and you are done (cwm included). Just make sure you grab the right firmware for your carrier.
If I have helped you out, slap that thanks button.
Click to expand...
Click to collapse
Beauty I think its flashing the rogers rom to my phone from there Im good to load other roms using this odin tool? (or is it rom manager?)
also what is this clockwork mod ? I might as well go into play store and get both rom manager and clockwork?
- eddy

So After I flashed the new rom to my phone i left it plugged in and it restarted. Android loader popped on and now it says android is upgrading... starting apps. Its been like this for over a half an hour... what do i do??? helpppp dont really want to reset it but it is bricked? or do i have to reload ?
update:
held the restart button down it restarted bit is still stuck on starting apps.
update two:
held vol down home and reset tried to reload the rogers rom onto the phone and now it stops at samsung load screen. Do i have to reload the carrier that came with the phone? I cant quite remember what the original carrier was.
UPDATE THREE:
I as able to boot back into the phone but...nothing changed? i ended up wiping the phones data in settings because its too full as it is. I downloaded root checker and it said access was denied ? That makes its not rooted after all... I followed the directions seems that they didnt take? Any clues?
eddy

eddyg519 said:
So After I flashed the new rom to my phone i left it plugged in and it restarted. Android loader popped on and now it says android is upgrading... starting apps. Its been like this for over a half an hour... what do i do??? helpppp dont really want to reset it but it is bricked? or do i have to reload ?
update:
held the restart button down it restarted bit is still stuck on starting apps.
update two:
held vol down home and reset tried to reload the rogers rom onto the phone and now it stops at samsung load screen. Do i have to reload the carrier that came with the phone? I cant quite remember what the original carrier was.
UPDATE THREE:
I as able to boot back into the phone but...nothing changed? i ended up wiping the phones data in settings because its too full as it is. I downloaded root checker and it said access was denied ? That makes its not rooted after all... I followed the directions seems that they didnt take? Any clues?
eddy
Click to expand...
Click to collapse
Okay buddy looks like you need to learn some basic android 101
You are definitely not ready to root or do anything til you learn this stuff...
Okay, so first is recoveries. Basically recoveries are a bit of software that let's you flash ROMs, kernels, and whatever else to your phone. When you hold volume up and power when your phone is off, you boot to recovery. Now basically recoveries are necessary because when you are flashing a new ROM it essentially deletes the android system from your phone first so this is a way of your phone still working between flashes.
Clockworkmod is a custom recovery with a lot of features meant for flashing ROMs. There are competitors such as TWRP (team win recovery project) but clockworkmod is a great starter. Use videos or tutorials on how to use it before you flash your first ROM. I can not stress how often you need to read read and read some more.
Okay so rooting your phone. Basically there is a "root" directory of your phone. Its where all the system files are stored and it let's you do a lot of stuff, but it also means you can screw a lot of stuff up to (like really screw it up). On default you are locked out of here by the maker of your phone for various reasons. Rooting means that someone found an exploit to gain access to this folder. Usually what you then do is you find a way to inject superuser (a little app that gives root access to other apps later on). You use Odin in this case to install a stock Samsung rom (with superuser already put in the root directory of that modified ROM its installing) essentially this means you have root. Root allows you to install recoveries like clockworkmod (which you need to flash ROMs later.
Okay so that was my quick run through. At your point you need to go to YouTube and Google how to root the sgs3 and hopefully they should have one for your specific carrier. The process should be the same minus the files you flash. Essentially you should be looking for stock ROM (for your specific device) with superuser or supersu already installed. Then you should be finding a way to install clockworkmod once you have root. (You may be able to find a file or tutorial that does this in one go). I cannot emphasise enough about reading. You wouldn't be here had you read first and in the flashing business, if you don't want a sgs3 paper weight you should read first.
Oh and ROMmanager from the marketplace installs clockworkmod for you (ONCE YOU HAVE ROOT) its simple. Just download it from the play story. Click flash recovery. It will load a bit and your done. Then you can reboot into it. ROM manager (the paid version is unnecessary) it just adds extra features you don't yet need. Look at it once you have flashed your first few ROMs.
Best of luck. Let me know and slap that thanks button. I wrote this on my phone.
READ READ READ

eddyg519 said:
Hey guys im trying to root my device so i can install some lightweight custom roms. Ive been following this guide i found online
http://androidcritics.com/how-to-root-and-install-clockworkmod-recovery-on-galaxy-s3-i747/
I basically did this
Installing Clockwork Recovery Mod
Find the recovery image file which is clockworkmod.tar
On your Samsung Galaxy S3 I747, press and hold down the volume down, power, and home buttons
Once your at the warning screen, press volume up to accept
Launch the Odin program from your computer
In Odin, find the PDA tab and click it
Find the clockworkmod.tar.md5 file in the unzipped recovery image file
Press start to begin flashing the recovery mod
BE PATIENT! and wait until your device reboots
Once your device has fully rebooted, you can start installing root
It loaded on the phone fine. I then did this
Installing Root
Transfer the root.zip file onto your phone from your computer
Make sure you connect your s3 to your computer and find the root zip file and put it in your downloads folder.
Enter clockwork recover mod by holding down the volume up, power, and home buttons
Navigate by using the volume buttons to Install Zip > Choose Zip from Internal SD card > Navigate to the downloads folder> Select
Be Patient! and wait until your device is finished
Once the process is finished, you can select Reboot
Once your device has rebooted, launch the Google Play Store app
Search “SuperuserSU” and select the first app that shows in the search results
Install this app
Once it has finished installing, your done!
The only problem is I cant navigate to the option "install zip from internal sd card" I simply dont have though's options here is what I have when hold volume up reset and home
"reboot system now
apply update from ADB
apply update from external storage (which i dont have)
wipe data/factory reset
wipe cache partition
apply update from cache
When i hit apply update from ADB it says "now send the package you want to apply to the device with "adb sideload <filename>"...
Im wondering if the original flash didnt go thru? Why dont I have the options that I should?
Any help would mean the world trying to get this puppy up asap!
regards,
Eddy
Click to expand...
Click to collapse
Hi eddy,
It sounds like you didn't get CWM to stick after your flash with ODIN. You need to uncheck the reboot option in odin and then after the flash is done pull the battery and go directly into CWM loader by booting with the volume up + power + home button method. This will give you cwm rather than the stock loader you seem to be trying to use. You're almost there!

sxorpyon said:
Hi eddy,
It sounds like you didn't get CWM to stick after your flash with ODIN. You need to uncheck the reboot option in odin and then after the flash is done pull the battery and go directly into CWM loader by booting with the volume up + power + home button method. This will give you cwm rather than the stock loader you seem to be trying to use. You're almost there!
Click to expand...
Click to collapse
He also said root wasn't sticking. He needs that before he can cwm to stick

aeppacher said:
He also said root wasn't sticking. He needs that before he can cwm to stick
Click to expand...
Click to collapse
I think he can't install the superuser.zip from cwm after boot because he's allowing the stock rom to overwrite his cwm flash ... he's gotta pull his battery after the odin flash to get root in. That's what worked for me. once he's got root he can use rom manager to upgrade to cwm 6.x

sxorpyon said:
I think he can't install the superuser.zip from cwm after boot because he's allowing the stock rom to overwrite his cwm flash ... he's gotta pull his battery after the odin flash to get root in. That's what worked for me. once he's got root he can use rom manager to upgrade to cwm 6.x
Click to expand...
Click to collapse
He shouldn't need cwm to install. If flashes a firmware with root already injected he can then just use rom manager to install clockworkmod for the first time since rom manager just needs root which he will have. You can root and keep the stock recovery on at the same time
I think his biggest issue is root not sticking. Til he does that cwm wont install

[Q] Root Help Please SM T210R

I have CWM installed on my Tab 7 and when I go to install the universal root that I copied and pasted into the external SD I get two messages saying in red
"failed to verify whole file signature"
and one saying in red
"failed file signature"
I downloaded the universal zipped root file twice and its the same thing over and over. I have USB de bugging on too. Any help would be greatly appreciated. I have been up all night and been at it for hours trying to fix this issue.

PMK19 said:
I have CWM installed on my Tab 7 and when I go to install the universal root that I copied and pasted into the external SD I get two messages saying in red
"failed to verify whole file signature"
and one saying in red
"failed file signature"
I downloaded the universal zipped root file twice and its the same thing over and over. I have USB de bugging on too. Any help would be greatly appreciated. I have been up all night and been at it for hours trying to fix this issue.
Click to expand...
Click to collapse
When you select Install zip in CWM, select Toggle signature Verification, then choose your zip.

Not an option
gr8nole said:
When you select Install zip in CWM, select Toggle signature Verification, then choose your zip.
Click to expand...
Click to collapse
Thank you for the timely response. Unfortunately I just noticed in the background in CWM that my droid man has a red triangle with ! point inside him. The options given to me are as follows...
Reboot system now
Apply update from ADB
Apply uopdate from Ext. Storage
Wipe data/factory reset
Wipe cache partition
Apply update from cache
Which of these options should I use if any and or should I flash CWM again on Odin in order to get the screen you are speaking about?
If I do need to flash again what are the correct steps to clear what CWM is already in place? Thank you again for all of your help. I am a noob that rooted my SIII a while back and obviously it is a little different with the Tab 7.0.

PMK19 said:
Thank you for the timely response. Unfortunately I just noticed in the background in CWM that my droid man has a red triangle with ! point inside him. The options given to me are as follows...
Reboot system now
Apply update from ADB
Apply uopdate from Ext. Storage
Wipe data/factory reset
Wipe cache partition
Apply update from cache
Which of these options should I use if any and or should I flash CWM again on Odin in order to get the screen you are speaking about?
If I do need to flash again what are the correct steps to clear what CWM is already in place? Thank you again for all of your help. I am a noob that rooted my SIII a while back and obviously it is a little different with the Tab 7.0.
Click to expand...
Click to collapse
Just try flashing CWM again and uncheck auto reboot in Odin.

gr8nole said:
Just try flashing CWM again and uncheck auto reboot in Odin.
Click to expand...
Click to collapse
Ok I did that and got a pass on Odin. Now my screen is still in Odin mode with a green droid in the middle and under that it says in white letters Downloading....Under that it says Do not turn off target!! in green letters. How do I properly restart? In CWM as normal? (Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen). Thanks...

PMK19 said:
Ok I did that and got a pass on Odin. Now my screen is still in Odin mode with a green droid in the middle and under that it says in white letters Downloading....Under that it says Do not turn off target!! in green letters. How do I properly restart? In CWM as normal? (Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen). Thanks...
Click to expand...
Click to collapse
Update...Just re read this
--Auto Reboot can be un-checked if CWM doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
Trying now fingers crossed!!!

PMK19 said:
Update...Just re read this
--Auto Reboot can be un-checked if CWM doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 10).
Trying now fingers crossed!!!
Click to expand...
Click to collapse
Update....ROOTED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!:good: Thanks for all of your help as well as the rest of the build team.

Stuck on Asus load screen

After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.

Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?

bratski said:
Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?
Click to expand...
Click to collapse
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.

jerk48 said:
After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.
Click to expand...
Click to collapse
by asus screen, did you mean the ASUS Setup Wizard?

sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
my problem right now is my pc wont detect my phone. Ive already installed the drivers.

Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me

sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
where do i get the stock image?

bratski said:
where do i get the stock image?
Click to expand...
Click to collapse
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.

sooty84 said:
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.
Click to expand...
Click to collapse
ive read about the temp cmw method and i cant figure out how to go about it. it says on the instruction that you need to turn on phone before running the cai_dat_CWM. how am i going to do this as my phone will only boot to the asus logo? thanks

just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?

bratski said:
just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?
Click to expand...
Click to collapse
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please

Ninjakura said:
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please
Click to expand...
Click to collapse
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..

cangcan said:
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..
Click to expand...
Click to collapse
thanks. problem solved after i followed instructions from this thread, http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835

bratski said:
my problem right now is my pc wont detect my phone. Ive already installed the drivers.
Click to expand...
Click to collapse
me too, any idea on how to fix it?

sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
I have same prolem as OP's got.
I've got stuck on Asus Loading screen after install OTA update on rooted device.
I'm gonna try your method.
Thanks

downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
how did u do that? can u give me step by step instruction please?
ty

Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!

SAN_MARINO said:
Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!
Click to expand...
Click to collapse
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.

k576 said:
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.
Click to expand...
Click to collapse
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.

SAN_MARINO said:
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.
Click to expand...
Click to collapse
I will try to tell you step by step:
1. Press Power Button + Volume Button
You enter into Recovery Fastboot Option, then Choose Recovery menu using Volume Key (3 Option mostly shown)
then press Power Button (From Recovery Mode), it restart.
2. Then after Restart it shows you (Mostly) Sleeping Android Screen with Error text, then Press First Volume Up Button, and Press Power Button (Power button for a second or two then leave it, IF YOU PRESS MORE TIME, IT WILL RESTART THE PHONE).
3. You can now see the Recovery Menu with Normally appear in other phones also - Reset, Restart, Etc Option.
Hope you will now able to reset your phone...
----------------------------------------------------------
PRESS THANKS BUTTON IF I AM HELPED YOU
----------------------------------------------------------