Ok, so I've been Resurrection_Remix_LP_v5.4.6-20150530-hlte.zip for quite some time now, probably since not long after it's release, and it pretty much liked it. Except for the occasional seemingly random "auto reset" of android/app settings and preference (such as forgetting all my saved wifi ssid) after a random crash/reboot.
Starting last week, the camera became problematic, often failing to start entirely (error message, "could not connect to to camera"), or could connect to the back camera, but freezes when i try to switch to front camera. I tried wiping data with TitBak and it worked again, but the problem comes back a while later. Is this a software or hardware problem?
Anyway, I finally decided to upgrade the the latest RR and wanted to upgrade TWRP from 2.8.5 as I go along. Since the existing version fits the requirement for TWRP install...
Code:
TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
... I went ahead and did it, with the standard 3 wipes (couple of times) and then the recovery flash. Turns out it didn't work and the phone just keeps freezing at the first screen with Note3 logo and the red/blue/yellow test at the top left saying booting to recovery. It never did!
I then tried to reflash the recovery using odin with the .tar file, it flashed fine and auto re-booted back into the launcher (everything's gone of course). But I still needed to go back into recovery mode to either flash a higher version of TWRP, or install the newer RR.
Still, it gets stuck and wont go to recovery no matter i used the hardware button method, or recovery button in the power menu, or adb reboot recovery.
What's wrong!?!??!
c'mon guys, give me something.
Later TWRP are know to give problems .
http://forum.xda-developers.com/showthread.php?t=2481255
I tried to Odin flash the old 2.8.5. .img file as well. Didn't work.
Related
So I flashed the new synergy to try out the multiwindow pinning, but had the intention of going back to my nandroid right after trying it out. After flashing it and booting it up, and trying it out, I tried going back to my recovery (TWRP). But when my phone showed the TWRP welcome screen, it just stuck there and flashed every couple of seconds (like every 5 seconds) instead of going up and revealing the recovery. So I pulled battery and tried the hardware keys for recovery. It did the same thing. So I tried booting back up to my system, but it kept trying to go into recovery, so I went to download mode and pressed the down button to reboot (this time successfully). I did this about three times, and it kept failing to go to recovery. So I decided the flash cwm. With cwm I was able to get to recovery and move around in the menus, but as soon as I try factory resetting to flash another rom I had on my sd card, it froze. So I rebooted back up to my system using the download mode again. So now I have a booting phone but my recoveries don't work. I have flashed roms numerous times without problems, I checked to make sure my bootloader is unlocked, and am rooted. Can anyone tell me how to get my recoveries to work?
Edit: I just tried goo manager and installed the latest twrp. It went to recovery. Ill edit if I have any other issues.
Hi guys,
I made the upgrade to CM10 last week from a stable CM9.
I made a full wipe and the install worked fine.
One thing I noticed after the install was that I couldn't restart in recovery.
I saved my apps with titanium backup beforehand (including ROM manager).
I think this might be why ROM manager didn't work properly as every time I lauched it, it would force close.
I then found the apk file and reinstalled ROM manager, hit the power button and I could reboot in recovery again, so I did straight away.
At the recovery menu I flashed an old CM9 .zip gapps file (silly me).
Now when I start my phone when I try to unlock I get the "setup wizard has stopped" error message over and over and I'm unable to access most menus because of this. I can still access some settings menus without too much hassle but I can't reinstall the apk like before and reboot in recovery.
I can access files via the USB also.
Any ideas on how to solve this problem? I just need to be able to get into recovery and flash the correct gapps again, at least that's what I gathered from other threads.
grossd said:
Hi guys,
I made the upgrade to CM10 last week from a stable CM9.
I made a full wipe and the install worked fine.
One thing I noticed after the install was that I couldn't restart in recovery.
I saved my apps with titanium backup beforehand (including ROM manager).
I think this might be why ROM manager didn't work properly as every time I lauched it, it would force close.
I then found the apk file and reinstalled ROM manager, hit the power button and I could reboot in recovery again, so I did straight away.
At the recovery menu I flashed an old CM9 .zip gapps file (silly me).
Now when I start my phone when I try to unlock I get the "setup wizard has stopped" error message over and over and I'm unable to access most menus because of this. I can still access some settings menus without too much hassle but I can't reinstall the apk like before and reboot in recovery.
I can access files via the USB also.
Any ideas on how to solve this problem? I just need to be able to get into recovery and flash the correct gapps again, at least that's what I gathered from other threads.
Click to expand...
Click to collapse
Turn off phone, press and hold the volume down key, home button, and power key till you boot into recovery.
Hi,
I have been following XDA since two years and this is the first time i am having to post something due to lack of a relevant thread.
My fastboot nightmare started a month ago, when i had tried to back up my ROM using ROM manager. I tried but failed to use the KDZ update since my phone would not get detected. I flashed a stock firmware using LGMDP to regain functionality of the phone.
On rerooting my phone this time, i think the CWM recovery was not installed properly. My phone used to hard reset every time I tried to reboot into recovery. I used LGMDP again to flash another image of CWM, which got it into the recovery mode but i cant seem to go beyond the main menu. Whenever i select an option on the menu, the screen goes blank, showing only the CWM logo in the background and does not go any further. I cant restart my phone through the menu either, and have to remove my battery and replace it to be able to exit the recovery menu in the first place. Also, my recovery mode shows "E:Bad boot message "recovery" " at the bottom of the screen, which i think used to come before the nightmare too, but i'm not really sure.
Even on updating the recovery through ROM manager, it takes time to flash but is never completed. I get the message saying "An error while flashing your recovery" and that's all.
Please help me out here. After a year of ICS and subsequently JB, i'm having to use GB with no workably way around so you can imagine my frustration.
What do i do?
P.S.:- as i post here, it just clicked me if i should try flashing a different recovery img file through LGMDP. I will let you know if that works. Till then, any and all replies are appreciated.
Alright, my work is done. Flashed AmonRa this time manually using the terminal emulator. I found the solution at:- http://forum.xda-developers.com/showthread.php?t=1146566
Thx anyways, guyz...
Is my stock recovery broken? Can't update through about device even with stock non CWM recovery.img. Even with factory restore files from the link below I was unable to get native recovery to work. I get a broken android.
I've been manually updating from the link below and I even tried the stock "recovery.img " on that official site doesnt seem to do the trick.
https://developer.nvidia.com/develop4shield
Below thread doesn't resolve issue.
http://forum.xda-developers.com/nvidia-shield/shield-qa/help-stock-recovery-shield-portable-t2850634
AFAIK the "broken android" screen is expected.
You just have to press the Power and Home buttons at the same time (this sometimes takes multiple tries) again to launch the recovery.
Go here and download this tool
http://forum.xda-developers.com/showthread.php?t=2661067
Once you have that grab the recovery file and the cwm file.
(Not at a computer right now if you need any files, let me know if you need them)
Turn off the Shield
Hold home, back and the Nvidia button all at once, your in fastboot now.
Here on command prompt type "fastboot flash recovery (location of your recovery image)"
Once you did that on the device go to recovery and you should have the android laying on his back, dead, poor little thing.
Hold home Nvidia button and back and once off boot normally.
One in the system update the system as normal once done turn the device back off
Go back in to fastboot and run on your computer "fastboot flash recovery (location of your cwm file)”
One you do that go back in to recovery and you should have cwm now. Reroot using the flash method "supersu has a flashable file you can use to root" one rooted your done till the next system update.
I have done this for the last 3 or 4 updates and works like a charm [emoji2]
Sent from my Amazon OtterX using Tapatalk
Doesnt work for me. I've tried it so many times and although it flashes everything back to (ota 56 I think) recovery stays broken. Then I went as far as replacing the stock recovery with the official one off nvidias development page still no luck. Tried to flash it bone stock (factory) and although the rom reflects the update/downgrade recovery always stays broken.
So ive tried this two times each end up the same.
Twrp recovery works once each time, then fails to boot into it again. the first time i booted into it just to test it flashed properly, then clicked reboot then system. then whenever i tried to reboot back into recovery it would ignore my inputs and just got straight to system again. the second time (reset os with odin) is extremely similar with me just installing a custom rom first.
any help? no clue what I'm doing wrong, I'm definitely doing the same button combination i was doing when i got into the first time.