Develop Bugs

[Q] Is it possible to run RUU from recovery?

I'd like to run an RUU on my Evo, since I am in some kind of limbo mode between root and non root. Problem is, I am in a reboot loop / can't get into the OS. Only RA recovery works. Can I run the RUU against the phone in another mode? (Fastboot?)

Menotti said:
I'd like to run an RUU on my Evo, since I am in some kind of limbo mode between root and non root. Problem is, I am in a reboot loop / can't get into the OS. Only RA recovery works. Can I run the RUU against the phone in another mode? (Fastboot?)
Click to expand...
Click to collapse
Answering my own question by trying it...seems to work from Fastboot mode. Let's see how this goes...

I think I know what the issue is. I seem to be in limbo between root and non root. after some research, it seems I need to RUU the device. S-ON seems to be back.
Problem is, I'm getting bootloader version errors when trying to do the RUU.

bootloader version errors when trying to do RUU. Any ideas?

In order to help, more info is needed. What were you doing when you got stuck? Attempting Root? if so, which method? What hardware version is your Evo? What hboot version? Software? You most likely need to load a stock image pc36100.zip to your sd card and flash from bootloader. You just need to make sure you have to correct file for your phone, and the above info would help. I've never been stuck in your position, but reading through here all the time, I've seen it happen to others, and what I suggested usually seems to work. But more info is definitely needed.

Thanks for the help.
I was able to successfully use an RUU. (RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444_signed)
However, I'm back into reboot loops again. I'm starting to wonder if there is a HW issue at play.
I need to go to bed, I will revisit this in the morning. Been going at it for about 6 hours now.

Menotti said:
Thanks for the help.
I was able to successfully use an RUU. (RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444_signed)
However, I'm back into reboot loops again. I'm starting to wonder if there is a HW issue at play.
I need to go to bed, I will revisit this in the morning. Been going at it for about 6 hours now.
Click to expand...
Click to collapse
This RUU is supposedly stock Froyo, btw.

Ok so I tried flashing the image in step 1 of this post and I'm getting the same results. Gets to the OS, sits there a sec, then reboots.

Bricked phone

I attempted to install recovery on my phone and everything seem to be going ok untill after saying yeah and now mu phone Is bricked.
I may rebooted it too early assuming it was done. How I can recover the phone? Or I just have to go to sprint store ?
I can put my phone in download mode

tritron777 said:
I attempted to install recovery on my phone and everything seem to be going ok untill after saying yeah and now mu phone Is bricked.
I may rebooted it too early assuming it was done. How I can recover the phone? Or I just have to go to sprint store ?
I can put my phone in download mode
Click to expand...
Click to collapse
I just went through a similar issue. Don't worry, if you can get to download mode, your phone should be recoverable.
The first thing you want to try is to flash your phone's original firmware. All of the instructions and downloads you need are located on the IRC server our developers use. Check out the link below for instructions on getting into IRC. You can use LGNPST to flash recovery (search forum for teenybin), or you can also just flash the unlocked stock firmware if you so choose. The guys in IRC are very helpful.
http://forum.xda-developers.com/showthread.php?t=1984620
If your phone still does not boot after using LGNPST, and you cannot get into recovery, let me know, you may need a battery pull.

Thank you for pointing me in right direction and thank you for the tip. I have my phone working and unlocked and rooted with custom firmware in less than 30 minutes.

[Q] Help! - Rooted Zenfone 2 (ZE551ML) bricked after OTA accidently

followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?

Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?

If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.

joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...

I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps

Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse

xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.

This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse

xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.

actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.

dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.

5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?

Stuck in boot loop and can't get into fastboot mode to use adb, need help

I followed this tutorial: http://forum.xda-developers.com/g4/general/unlock-bootloader-install-twrp-root-t3128241
Here's what I did:
Unlocked bootloader
Booted into TWRP (version 3.0) (didn't install, just booted into)
Flashed SuperSU
Rebooted into system
Now whenever I boot the device I'm stuck in a boot loop.
So I can't boot the device up or get into fastboot mode (what should fastboot mode look like? I got into download mode at some point), not sure what to do?

I had same problem once, managed to handle it with LGUP and refubrish full stock rom

ashensii said:
I had same problem once, managed to handle it with LGUP and refubrish full stock rom
Click to expand...
Click to collapse
I tried LGUP but it says the Model is "unknown" so when I select my phone it says "You have to select a known model, please." Can someone help?

I also tried flashing a stock kdz using LG flash tool but I got an error. Does anyone know what I can do? I can get my phone into download mode but don't know what to do on my computer.
I'll give someone $20 if they can help fix my phone for me

Paul397 said:
I also tried flashing a stock kdz using LG flash tool but I got an error. Does anyone know what I can do? I can get my phone into download mode but don't know what to do on my computer.
I'll give someone $20 if they can help fix my phone for me
Click to expand...
Click to collapse
With LG up if it comes up with device unknow with usb cable still pluged in pull battery out then put it back.

Paul397 said:
I also tried flashing a stock kdz using LG flash tool but I got an error. Does anyone know what I can do? I can get my phone into download mode but don't know what to do on my computer.
I'll give someone $20 if they can help fix my phone for me
Click to expand...
Click to collapse
I had the same problem.
If you can get your phone in the download mode, than try this.
1: Install LGBridge,
2: Boot your phone in download mode & start LGBridge,
3: Than on Software Update tab, on the bottom right corner, you will see an option saying "Update Error Recovery"
4: Click on it and your phone will be flashed to latest firmware. Make sure you are connected to net as it will need to download it.
Once the update it complete, Your phone should reboot normally.
Give it a try and let me know how it goes.

Edut;Deleted OS and all zips are marked as corrupted.

First, let me start off by saying I'm an idiot; my phone was stuck in a bootloop and out of panic I tried to fix the problem and only made it worse. Now I'm left with no OS installed and I'm stuck at my custom recovery.
I am using twrp as my custom recovery and I'm able to use my mac to send files successfully to my phone. The problem arises when I try to flash the zip and I am prompted with the message that says that the file is corrupted. I tried installing multiple zip files onto my phone and when returning it to stock did not work I even tried to flash Cyanogen Mod. Each time I was greeted with the same message.
This sucks because I just bought my nexus 5x and I don't want to lose it to a stupid mistake. If anyone could help in anyway that would be amazing. If not I will still accept prayers for my potentially dead phone.
-Carlos
Edit: problem solved. I did what you guys said and returned to stock and didn't panic. Thanks so much.

you mean the unlocked bootloader message? thats nothing
or maybe the md5 message, which also is normal?
to me sounds like you are panicking for no reason, but anyway, search for nexus root toolkit, install it, and choose the option to revert stock + unroot

Giorgos Chatziioannou said:
you mean the unlocked bootloader message? thats nothing
or maybe the md5 message, which also is normal?
to me sounds like you are panicking for no reason, but anyway, search for nexus root toolkit, install it, and choose the option to revert stock + unroot
Click to expand...
Click to collapse
Yeah as said above there is no need for panic.
Even if your recovery wont flash the zips you can flash the stock factory images via fastboot manually (i dont now if its available on mac if not boot a linux live disk).
And if your bootloader is still locked unlock it reboot to bootloader and then flash the images.
By the way you should provide more information such as os details twrp version bootloader state and so on...:fingers-crossed: