My Unlocked, rooted,TWRP'd XT1575 received notification of an update, which I proceeded to accept/download. Now my phone keeps rebooting to recovery (TWRP) and I have no idea where to find this file so I can install it.
I also don't know how to stop the phone from trying to run this update and continuously rebooting. Can anyone tell me how to address this problem? Many Thanks!
SteveHebe said:
My Unlocked, rooted,TWRP'd XT1575 received notification of an update, which I proceeded to accept/download. Now my phone keeps rebooting to recovery (TWRP) and I have no idea where to find this file so I can install it.
I also don't know how to stop the phone from trying to run this update and continuously rebooting. Can anyone tell me how to address this problem? Many Thanks!
Click to expand...
Click to collapse
Wipe cache in TWRP. That should delete the OTA file and break the bootloop.
Update file will be named Blur*.zip and located in cache.
Related
I just did the 4.2.2 update for my phone and now when I try to turn it on all I get is the X logo... it's been stuck that way for a while now... anything I can do?
hey, try rebooting into recovery and wiping cache, and factory reset if that doesn't work. PM me for more help. cheers
This is really bizzarre.... I wiped the cache and turned it on... it showed the lock screen (without the unlock slider) and I got an SMS... then it went back the X logo and is stuck again...
out of curiousity OP did you do the update via the OTA or did you sideload it?
uploder said:
out of curiousity OP did you do the update via the OTA or did you sideload it?
Click to expand...
Click to collapse
OTA, now i downloaded the factory image and am trying to flash it with the .bat file included
FYI, I found an archived jop40d image, flashed that, still hung at the X. Wiped data, wiped cache, and now it has started and is working (4.2.1). I'll try the 4.2.2 OTA later
Update 2: Tried the OTA again, won't boot again. Flashing jdq39 now...
Update 3: Flashed jop40d (4.2.1), phone is working okay now, i guess I'll have to avoid the update for now
Ok do I did search first but can't find anyone with the same problem.
Started with stock 4.3 rooted, unlocked,TWRP.
Got the update notification, told it to update. It auto rebooted to TWRP and applied the update with no error. When it was done (assuming it was done progress bar finished) it went to the main TWRP menu. I told it to reboot and it just sits at the new 4.3 splash screen animation. I assumed it may take a bit so I let it sit for about 20min with no change. Rebooted it a couple times, also tried applying the update again via twrp (errors out as i woukd expect). Wiped dalvik and cache. Didn't do a factory wipe because I'd like to avoid that but still no change.
Any suggestions? Should I manually load the full 4.4 package via TWRP?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Same exact setup... Say exact issue... Oh and before rebooting I wiped Dalvik and Cache as "Sandard Operating Proceedure" ... I'm going to just do a clean flash at this point....
Tracy
Hi
I have the same problem. had a rooted 4.3, and after the update the screens remains on the splash thing. restarted a couple of times, did wipe data, factory reset, and it still remains stuck at the boot. What should i do. pls help
step944 said:
I have the same problem. had a rooted 4.3, and after the update the screens remains on the splash thing. restarted a couple of times, did wipe data, factory reset, and it still remains stuck at the boot. What should i do. pls help
Click to expand...
Click to collapse
Prior to the installation of the OTA it is safer to re-install stock recovery. Root is lost but re-installing a custom recovery and SuperSu bring back root.
gunner1937 said:
Prior to the installation of the OTA it is safer to re-install stock recovery. Root is lost but re-installing a custom recovery and SuperSu bring back root.
Click to expand...
Click to collapse
How can i install stock recovery?
You *could* unzip the factory image and then fastboot the recovery.img file. A lot easier is to download the wugfresh nexus root toolkit and use that:
http://www.wugfresh.com/
ty, but do u think it works, because i cant open my nexus 10 memory from the pc, since it is stuck at start up
Wug's toolkit has an option to restore to stock from a bricked system. All you need to be able to do is to get to the bootloader (press the power button while holding down both volume buttons -- you should get a dead android with a red triangle on chest).
Hey, so I rooted my D802 a while ago, and installed TWRP using autorec, and all was going well.
today I received an ota, and against my better judgment , I clicked install, so of course it booted into TWRP and not stock recovery, and it couldn't flash the update, I rebooted the phone and it still booted back in TWRP!!, formatted, system, data, dalvik, and cache, then reboot, same thing, the phone keeps going back to recovery, apparently the command to update (boot into recovery) has been issued to the bootloader, and I have no idea how to cancel it, any ideas?
does anyone know where to find the temporary downloaded file from OTA? maybe flashing it manually through TWRP will fix the issue
thanks
this page helped, I typed the code and viola ,it works, thanks guys
http://forum.xda-developers.com/showthread.php?t=2694530
Hopefully someone can help. There was an update on Google Play today for the Chainfire SuperSU. I ran the update, clicked the message that I needed to update the binary, chose TWRP (I'm on 2.8.7.0), and the phone rebooted. After booting, it went into recovery, tried to run something (I wish I had written it down), and rebooted again. It did this again and again, looping about 10 times before I finally held the power button. At that point, the phone tried to boot normally, but never went past the boot animation (waited about 30 minutes).
I can still get into recovery, luckily... I just don't know what I should do at this point. I am running the stock MM, just debloated.
From which SuperSU version did you run the update?
Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
I was able to fix the issue by booting into recovery, copying the latest supersu zip to internal storage via MTP, and installing the zip manually. Once that was done, the phone finally booted all the way.
andry23jsv said:
From which SuperSU version did you run the update?
Click to expand...
Click to collapse
The update was from the newest one in the store. It came up just like any other app update does. The funny thing is, when I went back to look at the latest version in Play, it was definitely older. I wonder if it was pulled.
jason2678 said:
Before you do anything else, try wiping cache and dalvik from TWRP. Sometimes you get lucky and that's all it takes to stop a bootloop.
Click to expand...
Click to collapse
I had tried all that. It's usually the first thing I do when I have issues like that.
Hey, i am using a note 4 . Currently my phone is in recovery mode and is boot looping. It would boot for 2 secs then reboot again. i cant exit the recovery mode at all the clear any cache or stuff. I may have misclicked the normal boot and clicked the TWRP after updating supersu. Is there a fix for it?
Did you try manually copying the latest SuperSU zip file to your internal storage (via MTP, or adb), then installing it from recovery?
Flapjack said:
Did you try manually copying the latest SuperSU zip file to your internal storage (via MTP, or adb), then installing it from recovery?
Click to expand...
Click to collapse
hi the problem is that i cant get pass the recovery mode. its there for about 2 secs then gone
I guess I'm not sure what you mean. You can't get "past" recovery mode? When you reboot (without button intervention), what happens? Does it try to load the OS partition, then reboot? Can you press whatever button combo the Note 4 has to get into recovery (as opposed to booting the phone normally?
Not sure how much help I can be, as I've never had a Note. I got off the Samsung train after the S4. I've had enough of locked bootloaders, bloatware, and crappy UIs. It's a shame, too.... as I really like their hardware.
Flapjack said:
I guess I'm not sure what you mean. You can't get "past" recovery mode? When you reboot (without button intervention), what happens? Does it try to load the OS partition, then reboot? Can you press whatever button combo the Note 4 has to get into recovery (as opposed to booting the phone normally?
Not sure how much help I can be, as I've never had a Note. I got off the Samsung train after the S4. I've had enough of locked bootloaders, bloatware, and crappy UIs. It's a shame, too.... as I really like their hardware.
Click to expand...
Click to collapse
Hey man tks for replying so promptly though. I think i know what went wrong. Just that i don't know how to fix it. My phone is now recovery booting through TWRP. But i don't remember having TWRP. Is there a way to change the boot to normal?
I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.
khushboop said:
I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.
Click to expand...
Click to collapse
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.
sk.shehbaz said:
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.
Click to expand...
Click to collapse
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.
khushboop said:
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.
Click to expand...
Click to collapse
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.
khushboop said:
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.
Click to expand...
Click to collapse
I still have no idea why it got bricked. So after searching on google and youtube I came across this: https://androidmtk.com/download-yu-stock-rom-for-all-models . I followed the steps and now KitKat is running except launcher is not working, instead play store open's every time I try to go to home screen. So tried the nova launcher but that still doesn't work with home button, have to open through playstore->my apps, every time. But rest is working.
sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
dude!! i tried the above method and thankfully my phone is working now the only major problem now is whatsapp is not opening...when clicked opens for 0.01 sec and returns back to previous screen (flashes) ....please somebody help me with this. Anybody can help me, Thanks in Advance.