hello i recently rooted and installed cm11 on my FP, i just did a clean system partition flash, then flashed pa_gapps. now screen is stuck at black screen with amazon logo. what should i do? i did get the phone to connect to the pc, i got it working using the stock usb cord phone came with. now the phone not connecting to pc anymore.
what can i do to return the phone to factory setting? or at least to get the cm11 running.
azheng said:
hello i recently rooted and installed cm11 on my FP, i just did a clean system partition flash, then flashed pa_gapps. now screen is stuck at black screen with amazon logo. what should i do? i did get the phone to connect to the pc, i got it working using the stock usb cord phone came with. now the phone not connecting to pc anymore.
what can i do to return the phone to factory setting? or at least to get the cm11 running.
Click to expand...
Click to collapse
You mentioned clean partition flash and pa gapps but you didn't say you flash the cm11 zip. I assume you did? If not there's no os. Twrp will notify if the os isn't there but not sure about safestrap. I'd assume you need to flash it in fastboot now unless there's a button combo that can be utilized.
I'd take this to the cm11 thread. ggow might be able to assist.
KLit75 said:
You mentioned clean partition flash and pa gapps but you didn't say you flash the cm11 zip. I assume you did? If not there's no os. Twrp will notify if the os isn't there but not sure about safestrap. I'd assume you need to flash it in fastboot now unless there's a button combo that can be utilized.
I'd take this to the cm11 thread. ggow might be able to assist.
Click to expand...
Click to collapse
well problem is i cant even get into safestrap recovery right now. when i hard reset the phone, try to boot it. its stuck at amazon screen. good thing right now is when i plug the phone in the pc, it makes connection. maybe i can sideload a os using the pc?
azheng said:
well problem is i cant even get into safestrap recovery right now. when i hard reset the phone, try to boot it. its stuck at amazon screen. good thing right now is when i plug the phone in the pc, it makes connection. maybe i can sideload a os using the pc?
Click to expand...
Click to collapse
That probably IS a good thing. But if there's no OS installed I'd think it would automatically boot to recovery? I've only owned this phone a short time and before last week never used safestrap. Normally I'd either try to boot recovery with a button combo (haven't needed to on this phone.) Or connect via adb and use the command "adb reboot recovery".
I'd say you have a better chance or at least a quicker response if you head over to ggow's thread. Good luck
KLit75 said:
That probably IS a good thing. But if there's no OS installed I'd think it would automatically boot to recovery? I've only owned this phone a short time and before last week never used safestrap. Normally I'd either try to boot recovery with a button combo (haven't needed to on this phone.) Or connect via adb and use the command "adb reboot recovery".
I'd say you have a better chance or at least a quicker response if you head over to ggow's thread. Good luck
Click to expand...
Click to collapse
thanks for the help, i think recovery went bye bye along with the OS lol
Hi,
any update on this thread? I've been stuck also. I had safestrap. I supposed to flash a cleamsystempartion but I accidentally restart it without flashing new rom and now i am stuck in Fire Phone Logo. I still can access the stock recovery tho. Please help :crying::crying::crying:
try to flash your phone back to stock rom
any solution to this problem? I am stuck with same problem.
siddharth_bhal said:
any solution to this problem? I am stuck with same problem.
Click to expand...
Click to collapse
same problem here: can't start safe stripe and stuck at Amazon. tried to start the phone pressing volume up and power button, see if you can get into the build-in recovery. if it works, you can wipe the data and then use ADB sideload to flash in official rom (should be a bin file, i tried 4.6.1 version) and bring back your phone .
fire phone keep rebooting
my fire phone is keep rebooting with amazon logo up to 5 minutes and suddenly turned of i want to know the problem and how to fix it so please help me.
Have any of you guys tried the instructions in this thread: https://forum.xda-developers.com/fire-phone/general/reverting-fire-phone-to-stock-t3288890
I have bricked Fire phone quite a few times and everytime I followed his instructions and the lifehacker instructions that he linked to install adb and ADB sideloaded 4.6.6.1. without any problems.
My fire keeps rebooting and gets stuck with the amazon logo on it pls i need ur help urgently
Bahdtyga said:
My fire keeps rebooting and gets stuck with the amazon logo on it pls i need ur help urgently
Click to expand...
Click to collapse
U need a new fire phone, talk with amazon from your country or region or the seller from where you got fire phone!
Related
I think my 1st gen KF is stuck trying to boot to recovery. I was trying to restore back to stock from CM10.1. Downloaded the Amazon update 6.2.1 bin file, renamed it to update.zip, booted into TWRP recovery, tried to flash and it failed (several times). After some research, I found that the fix for this was to downgrade TWRP to v2.2.2.1 (I was on 2.6.0.0 or something like that). I tried several methods for doing that and it wouldn't take, even though it looked like flashing the TWRP v2.2.2.1 finished successfully. So finally I found a method (thanks to XDA's wonderful developers) to install CWM. Finally was able to get it to boot into CWM recovery, tried flashing the update.zip again, and all went through successfully. However, when I rebooted it was stuck at the Kindle Fire logo screen. Tried rebooting several times...nothing. AFter more research, found that the bootmode was incorrectly set so I tried to change the bootmode to recovery (which failed miserably)...now I'm stuck on the Kindle Fire logo screen. Seems like it is trying to boot to stock recovery but can't get there. Now none of my computers will recognize it at all. Is there anything I can do to unbrick this? I've tried just about every method I can get my hands on but without the computer recognizing it, not sure what else I can do.
Any help would be GREATLY appreciated. This is my 8-year old son's Kindle!
Thanks,
caseym
caseym said:
I think my 1st gen KF is stuck trying to boot to recovery. I was trying to restore back to stock from CM10.1. Downloaded the Amazon update 6.2.1 bin file, renamed it to update.zip, booted into TWRP recovery, tried to flash and it failed (several times). After some research, I found that the fix for this was to downgrade TWRP to v2.2.2.1 (I was on 2.6.0.0 or something like that). I tried several methods for doing that and it wouldn't take, even though it looked like flashing the TWRP v2.2.2.1 finished successfully. So finally I found a method (thanks to XDA's wonderful developers) to install CWM. Finally was able to get it to boot into CWM recovery, tried flashing the update.zip again, and all went through successfully. However, when I rebooted it was stuck at the Kindle Fire logo screen. Tried rebooting several times...nothing. AFter more research, found that the bootmode was incorrectly set so I tried to change the bootmode to recovery (which failed miserably)...now I'm stuck on the Kindle Fire logo screen. Seems like it is trying to boot to stock recovery but can't get there. Now none of my computers will recognize it at all. Is there anything I can do to unbrick this? I've tried just about every method I can get my hands on but without the computer recognizing it, not sure what else I can do.
Any help would be GREATLY appreciated. This is my 8-year old son's Kindle!
Thanks,
caseym
Click to expand...
Click to collapse
I'm having exactly the same issue on my Kindle Fire. I just recently got it from a friend; it seemed to be bricked, but the friend stated that he had never tried modifying the stock OS. I was able to use KFU to install the most up-to-date version of TWRP, but not FFF; I wanted to get it to stock before doing any additional hacking. That version of TWRP booted without any issues.
As OP mentioned, the most up-to-date version of TWRP has issues with installing the current version of the Amazon software. So, I tried downloading a copy of TWRP 2.2.2.1 (attached) and used KFU to install it, by extracting recovery.img, renaming it to twrp.img, and dropping it in KFU's /recovery/ folder.
Since then, I've seen the same symptoms as OP. The Fire boots to the Kindle Fire bootscreen, with no animation. It's not detected at all by any computer I attach it to. Windows doesn't chime or show it in Device Manager and KFU and adb don't see it. I also tried setting up FireKit, but none of the tools in that package are able to see it.
I'm going to test to see if this persists after depleting the battery for a while. I do not have a fastboot cable to test with, but I'm open to opening the case if you guys think that'll help get it back up and running.
Update; I was able to use the shorting trick to put it into OMAP boot mode and install FFF and TWRP, as well as reset the boot mode using Firekit. Firekit also installs TWRP 2.0, which is able to restore the stock Kindle Fire firmware.
haikuginger said:
Update; I was able to use the shorting trick to put it into OMAP boot mode and install FFF and TWRP, as well as reset the boot mode using Firekit. Firekit also installs TWRP 2.0, which is able to restore the stock Kindle Fire firmware.
Click to expand...
Click to collapse
OK...can you explain what you mean by the "shorting trick"? The battery on mine has been dead for about a day and a half. I had the case open the other day but didn't really do anything. What do I need to do?
Thanks,
caseym
caseym said:
OK...can you explain what you mean by the "shorting trick"? The battery on mine has been dead for about a day and a half. I had the case open the other day but didn't really do anything. What do I need to do?
Thanks,
caseym
Click to expand...
Click to collapse
First, get the Kindle charged. Then, boot to Ubuntu and set up FireKit (link above). Then, with the back cover off, hook the Kindle up to the computer. It'll power up, but hold down the power button to shut it off immediately.
Once you've done that, run the "usb_install_fff_twrp" script from Terminal. It'll say that its waiting for an OMAP device. Here's where the shorting comes in. Short the pad circled in the picture in this post to the metal frame around the CPU:
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
Then, keeping it shorted, press the power button.
Firekit should see the device over USB now, and write the appropriate settings. Once booted to TWRP, you should be able to install the stock firmware from /sdcard/.
It might take a couple tries, but keep trying. I used a continuity tester with an LED in it to make sure I had shorted that pad correctly.
haikuginger said:
First, get the Kindle charged. Then, boot to Ubuntu and set up FireKit (link above). Then, with the back cover off, hook the Kindle up to the computer. It'll power up, but hold down the power button to shut it off immediately.
Once you've done that, run the "usb_install_fff_twrp" script from Terminal. It'll say that its waiting for an OMAP device. Here's where the shorting comes in. Short the pad circled in the picture in this post to the metal frame around the CPU:
http://forum.xda-developers.com/showpost.php?p=19762674&postcount=51
Then, keeping it shorted, press the power button.
Firekit should see the device over USB now, and write the appropriate settings. Once booted to TWRP, you should be able to install the stock firmware from /sdcard/.
It might take a couple tries, but keep trying. I used a continuity tester with an LED in it to make sure I had shorted that pad correctly.
Click to expand...
Click to collapse
Well it worked the first time. I was able to get it to boot and the FireKit utility installed TWRP and I was able to flash the stock rom. After doing that, I disconnected the USB cable and the KIndle immediately shut off and I can't get it to turn back on. What did I do wrong?! Is it fried or something?
--
caseym
caseym said:
Well it worked the first time. I was able to get it to boot and the FireKit utility installed TWRP and I was able to flash the stock rom. After doing that, I disconnected the USB cable and the KIndle immediately shut off and I can't get it to turn back on. What did I do wrong?! Is it fried or something?
--
caseym
Click to expand...
Click to collapse
I'm afraid I've got nothing for you at this point. Hopefully someone more knowledgeable than I can sound off.
Hi, i successfully rooted my Galaxy tab s 8.4 with the root method discussed on the development
section. I am using a stock rom. the tablet runs fine with the OS. I decided to try a custom rom.
I have tried everything to get into bootloader, the power button with the volume keys gets me to
the "downloading target the android guy logo. I do not get the screen that gives me the options
to select recovery, bootloader or reboot screen. I have all the drivers installed. fast boot fails.
I dont know what else to. I have tried loading thru TWRPa rom and i get a sig verification.
i have heard what an ADB sodeload but not sure if that will help. Any recommendations would
be appreciated.
thanks!
noob2112 said:
Hi, i successfully rooted my Galaxy tab s 8.4 with the root method discussed on the development
section. I am using a stock rom. the tablet runs fine with the OS. I decided to try a custom rom.
I have tried everything to get into bootloader, the power button with the volume keys gets me to
the "downloading target the android guy logo. I do not get the screen that gives me the options
to select recovery, bootloader or reboot screen. I have all the drivers installed. fast boot fails.
I dont know what else to. I have tried loading thru TWRPa rom and i get a sig verification.
i have heard what an ADB sodeload but not sure if that will help. Any recommendations would
be appreciated.
thanks!
Click to expand...
Click to collapse
Have you tried this? It's worked for me twice on soft bricks.
HTH
skeeterpro said:
Have you tried this? It's worked for me twice on soft bricks.
HTH
Click to expand...
Click to collapse
I tried that. thank you for offering. I an not stuck in a bootloop. I can get right to the OS and it runs fine. But I have
no access at all to the bootloader. I have no clue what to do.
noob2112 said:
I tried that. thank you for offering. I an not stuck in a bootloop. I can get right to the OS and it runs fine. But I have
no access at all to the bootloader. I have no clue what to do.
Click to expand...
Click to collapse
tried this yet?
Code:
adb reboot bootloader
I have the same problem, I'm trying to simply get fastboot access to install CWM instead of TWRP. bootloader command in adb does absolutely nothing, just reboots into the OS. Also, running quickboot with root permission does the same thing. The bootloader just seems to be gone, but the tablet works flawlessly.
Same problem with mine.
My Galaxy Tab S 8.4 was bought from HK.
Same here. Sadly there is no option to use fastboot with this device. The only solution is to flash via Odin.
Cheers
reboot download * NOT * reboot bootloader
first timer here,
so I had my fire tv for a week it was rootable so I had it rooted and running on 51.1.4.1_514013920
fixed, for some reason i decide to install boot menu, so I could just update once the 51.1.4.2 comes out
and now it would not boot kernel. every time i try it just loops back I could still boot in to recovery
but i already have the rom removed from the device
I just wanna ask if there's anyway i could load the rom back into the firetv with recovery mode
and install it from there? Or could i remove the boot menu in anyway?
thank you so much for your help
gk83916 said:
first timer here,
so I had my fire tv for a week it was rootable so I had it rooted and running on 51.1.4.1_514013920
fixed, for some reason i decide to install boot menu, so I could just update once the 51.1.4.2 comes out
and now it would not boot kernel. every time i try it just loops back I could still boot in to recovery
but i already have the rom removed from the device
I just wanna ask if there's anyway i could load the rom back into the firetv with recovery mode
and install it from there? Or could i remove the boot menu in anyway?
thank you so much for your help
Click to expand...
Click to collapse
If you can boot in recovery install 51.1.4.0_514006420-rooted+updated, this is the last firmware that does not required a boot menu. As far as I know 51.1.4.1 requires it so not sure how did you manage to run this rev without the boot menu. Let me guess, did you try installing boot menu using Firetv Utility s/w? After reverting back to 51.1.4.0 follow the guide from AFTnews and install boot menu manual sending one commend at the time.
Thank you for the reply
But how do I install the frimware in recovery?
Because u had it deleted from the firetv
Is there any way I could load it back in the within recovery?
gk83916 said:
Thank you for the reply
But how do I install the frimware in recovery?
Because u had it deleted from the firetv
Is there any way I could load it back in the within recovery?
Click to expand...
Click to collapse
I've always used adb push but if that's not an option (because you can't connect) I'm pretty sure you can copy the update to a usb drive then insert in aftv and get it from there. Actually I've read that's the preferred method for lots of people.
But it doesn't hurt to re-read Rbox's threads and/or aftvnews guides.
KLit75 said:
I've always used adb push but if that's not an option (because you can't connect) I'm pretty sure you can copy the update to a usb drive then insert in aftv and get it from there. Actually I've read that's the preferred method for lots of people.
But it doesn't hurt to re-read Rbox's threads and/or aftvnews guides.
Click to expand...
Click to collapse
So I could just plug a USB drive in there and it would work?!
Thank you so much I will give it a try tonight
alright this is what happened I finial took care of this boot loop thing
the reason is i install boot menu twice so once the first boot menu try
to boot into kernel it goes to the second boot menu and that's how the
boot loop started
luckily i could still get into recovery so from there I tried everything
finally i find the think called advanced putty
from there I was able to load 5140 and removed both menus
reroot busybox did everything and now got a fire tv fully working
rooted and all good
Thank everybody for helping out
good luck
Updated my rooted Amazon Fire TV to 51.1.5.0_515020820. Now I'm stuck on "Amazon Fire TV" logo. Clockwork recover is installed. I cannot ADB to a network connection to issue Adb Reboot Recovery. If I connect a USB keyboard Control-Alt-Delete will reboot Amazon Fire TV. I did try Alt-PrintScrn-i to get to the default recovery screen but I think that is disabled when you install Clockwork mod. Any ideas?
Wow.. Exactly same result doing exactly same thing!!
Don't have a USB keyboard so haven't tried that yet. Also while searching I came across a method which involve connecting FTV with computer using a A to A type USB cable while power is unplugged and then putting the power cable back on triggers fastboot mode, did you try that?
i am too, now i can not connect:crying:
Unbricked.. Yay!!
omega99 said:
Updated my rooted Amazon Fire TV to 51.1.5.0_515020820. Now I'm stuck on "Amazon Fire TV" logo. Clockwork recover is installed. I cannot ADB to a network connection to issue Adb Reboot Recovery. If I connect a USB keyboard Control-Alt-Delete will reboot Amazon Fire TV. I did try Alt-PrintScrn-i to get to the default recovery screen but I think that is disabled when you install Clockwork mod. Any ideas?
Click to expand...
Click to collapse
vn_soft said:
i am too, now i can not connect:crying:
Click to expand...
Click to collapse
So I was able to unbrick my AFTV with the same Alt+Prt Scr+i keyboard method already posted before. It took sometime and AFTV rebooted 3-4 times before finally going to recovery, since I had cwm recovery installed, it directly went to cwm.
OP, I dont know why this method didn't work for you.. As i mentioned above, it didn't go to stock recovery but directly to cwm. I guess you should try again.
To anyone who does the same mistake again, I had the soft brick because I missed flashing the FTV boot menu by rbox. I was coming from older version ( 51.1.3.0_513011820), and while I did install the rbox's prerooted stock 51.1.4.0_514006420+updated before flashing the latest update, I missed flashing the boot menu (I did know about it and even moved the .img file to FTV with all other files, somehow just forgot to flash it inbetween the 2 updates).
I have the same issue but managed to get clockwork mod to be displayed. What option did you choose? Install from zip? Clear partions?
jainanshal said:
So I was able to unbrick my AFTV with the same Alt+Prt Scr+i keyboard method already posted before. It took sometime and AFTV rebooted 3-4 times before finally going to recovery, since I had cwm recovery installed, it directly went to cwm.
OP, I dont know why this method didn't work for you.. As i mentioned above, it didn't go to stock recovery but directly to cwm. I guess you should try again.
To anyone who does the same mistake again, I had the soft brick because I missed flashing the FTV boot menu by rbox. I was coming from older version ( 51.1.3.0_513011820), and while I did install the rbox's prerooted stock 51.1.4.0_514006420+updated before flashing the latest update, I missed flashing the boot menu (I did know about it and even moved the .img file to FTV with all other files, somehow just forgot to flash it inbetween the 2 updates).
Click to expand...
Click to collapse
i' ve solved this problem, my AFTV stuck in white logo, after i use "Alt+Prt Scr+i " it came into color logo, then I use "Alt+Prt Scr+i " several time, finally it boot in CMW recovery. I've installed an older rom, it is OK now.
I thinks the newest Rom have problems, so plz wait until the author fix it. TKS for all:good:
vn_soft said:
i' ve solved this problem, my AFTV stuck in white logo, after i use "Alt+Prt Scr+i " it came into color logo, then I use "Alt+Prt Scr+i " several time, finally it boot in CMW recovery. I've installed an older rom, it is OK now.
I thinks the newest Rom have problems, so plz wait until the author fix it. TKS for all:good:
Click to expand...
Click to collapse
Ok I'm at the cwm recovery screen but how can I load up an older firmware? I tried adb to connect to the IP address of the box and it says it cannot connect
Berrybare said:
Ok I'm at the cwm recovery screen but how can I load up an older firmware? I tried adb to connect to the IP address of the box and it says it cannot connect
Click to expand...
Click to collapse
If you in cam recovery screen, you can see your fire tv box's ip at the low left screen. You can not connect cause of your ip has changed (in my ip changes from 192.168.1.103 to 192.168.1.110).
Then you can use adb push to copy rom image to your fire tv and install it. Good luck
vn_soft said:
If you in cam recovery screen, you can see your fire tv box's ip at the low left screen. You can not connect cause of your ip has changed (in my ip changes from 192.168.1.103 to 192.168.1.110).
Then you can use adb push to copy rom image to your fire tv and install it. Good luck
Click to expand...
Click to collapse
Thanks. So I should connect adb using the IP address found on the bottom left of cwm screen?
I have same problem too.
omega99 said:
Updated my rooted Amazon Fire TV to 51.1.5.0_515020820. Now I'm stuck on "Amazon Fire TV" logo. Clockwork recover is installed. I cannot ADB to a network connection to issue Adb Reboot Recovery. If I connect a USB keyboard Control-Alt-Delete will reboot Amazon Fire TV. I did try Alt-PrintScrn-i to get to the default recovery screen but I think that is disabled when you install Clockwork mod. Any ideas?
Click to expand...
Click to collapse
I have same problem too. Any solution ???
Berrybare said:
Thanks. So I should connect adb using the IP address found on the bottom left of cwm screen?
Click to expand...
Click to collapse
Yes.
1.you can use command adb connect 192.168.xxx.xxx
2. Adb push (your path rom file)
Or use tool http://forum.xda-developers.com/showthread.php?t=2786505
Good luck
I had the same issue with the latest custom firmware soft bricking my device. I managed to get back to recovery screen, then reloaded previous firmware and everything was back as it was.
Can anyone advise on what steps are best to get the newest custom firmware on my device ?
I have read things about re-flashing rbox recovery screen, etc ?
If you are on 51.1.5.0 and you are stuck on the amazon logo and never saw bootmenu, that means you didn't follow the instructions for flashing 51.1.5.0 which say you must have bootmenu.
I just updated last night and it works great--painless process. And I was coming from 51.1.4.0 which on this particular aftv meant unlocking bootloader, installing boot menu, then pushing the rom.zip.
A lot of steps but I thought it was really easy. I followed the guide aftvnews meticulously put together and don't think I strayed from it at all.
*Obviously this post is for people reading about issues other users are reporting and it might give them pause to install it. I don't think it should because its not hard. Take the time to check all md5 sums! It might be worth it...make certain ALL prerequisites are met.
rbox said:
If you are on 51.1.5.0 and you are stuck on the amazon logo and never saw bootmenu, that means you didn't follow the instructions for flashing 51.1.5.0 which say you must have bootmenu.
Click to expand...
Click to collapse
This is where I went wrong. I have 4 fire tv's, and I have always updated them together with no problem. I mistook "boot menu" to think that was a reference to CWM menu. I always thought of that as the "boot menu", when in fact that was my mistake and the cause for bricking the two devices. In this scenario there is no way to unbrick that I can find. The keyboard alt i print screen is a no go, fastboot is a no go, I have tried everything but unless there is something I am missing, I made a mistake and it cost me two firetvs.
crayneogeo said:
This is where I went wrong. I have 4 fire tv's, and I have always updated them together with no problem. I mistook "boot menu" to think that was a reference to CWM menu. I always thought of that as the "boot menu", when in fact that was my mistake and the cause for bricking the two devices. In this scenario there is no way to unbrick that I can find. The keyboard alt i print screen is a no go, fastboot is a no go, I have tried everything but unless there is something I am missing, I made a mistake and it cost me two firetvs.
Click to expand...
Click to collapse
Well that is why the post for the prerooted images links to the boot menu post... but fastboot will only work if you did the full unlock. If you're not fully unlocked and sysrq doesnt work, then you are stuck.
vn_soft said:
Yes.
1.you can use command adb connect 192.168.xxx.xxx
2. Adb push (your path rom file)
Or use tool http://forum.xda-developers.com/showthread.php?t=2786505
Good luck
Click to expand...
Click to collapse
Thank you so much!! just a little heads up, you will need to connect the Fire TV with the LAN cable so this could work, then you could use ADB from your computer to push the correct rom, my mistake was that I installed Boot Menu before updating to 51.1.4.0 and then I updated to 51.1.5.0, big mistake! you need to install Boot Menu before updating to 51.1.5.0 and to fix my problem I just downgraded to 51.1.4.0 from ClockworkMod Recovery
Cheers!!
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 ?