[Q] Can't enter recovery mode, can't access menus after wrong gapps installation - Verizon Samsung Galaxy S III

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.

Related

[Q] SOLVED Problem flashing CyanogenMod 9.1.0 Stable

I rooted my MT4GS a few months ago but stuck with the stock ROM. I decided I wanted to try out the CyanogenMod 9.1 ICS ROM. I followed the following steps:
1) Installed ROM Manager.
2) ROM Manager indicated a newer version of ClockworkMod Recovery and I installed it (5.0.2.7).
3) Using ROM Manager, did a full backup of the current ROM. All went well.
4) Using ROM Manager, downloaded and installed CyanogenMod 9.1.0 stable-doubleshot. I specified to wipe the data and cache partitions. The installation seemed to go normally.
When the phone rebooted, it was stuck at the logo screen. Had to remove the battery to turn it off. Tried a couple times, still the same.
Since I had the backup, I decided I would use CWM to restore the old ROM.
When I boot into recovery mode, it shows CWM 5.0.2.7, but whatever option I try to choose from the recovery menu, The screen just goes blank with the CWM logo in the middle and nothing else happens. Hitting the power button returns me to the menu, but no option works, even power down or reboot. It just goes back to the CWM logo again and I have to remove the battery to shut it down.
So, I thought I would try using fastboot to flash the ROM again. When I boot the phone into the boot loader and select fastboot, then plug the phone in via USB, nothing happens. Windows does not see the phone and ADB or fastboot don't see it either. It's not a driver issue, as the computer is still setup from when the computer was rooted and I connect the phone all the time with no problems.
When the phone is off and plugged into USB or the charger, I still get the charging light, though it goes off after about 10 seconds, then comes back on and cycles like that.
Is there anything I can try at this point, or is my phone bricked? It seems like I followed all the steps correctly. Is there an update.zip I can put in the root folder and see if it picks it up?
Any help would be appreciated.
brucehvn said:
I rooted my MT4GS a few months ago but stuck with the stock ROM. I decided I wanted to try out the CyanogenMod 9.1 ICS ROM. I followed the following steps
...
Click to expand...
Click to collapse
Ok, after rebooting Windows, I was able to get the USB connection to the phone to work in fastboot. It seems I missed the step described in this thread:
http://forum.xda-developers.com/showthread.php?t=1508556
which states with S-ON you must flash the boot.img separately. I did that via fastboot and the phone boots into cyanogenmod now.
However, I still seem to have the issue with clockwordmod recovery. As long as I do the recovery functions from rom manager, everything is fine, but when I manually boot into the recovery menu, I get the same behavior of any choice from the menu just blanks the screen except for the CWM logo and nothing happens. I tried reflashing the recovery image using fastboot, but still no go.
brucehvn said:
However, I still seem to have the issue with clockwordmod recovery. As long as I do the recovery functions from rom manager, everything is fine, but when I manually boot into the recovery menu, I get the same behavior of any choice from the menu just blanks the screen except for the CWM logo and nothing happens. I tried reflashing the recovery image using fastboot, but still no go.
Click to expand...
Click to collapse
This is solved also. Seems on the MT4GS, the trackball is the selection button. The power button appears to only be a back button.
What a thread! Two nicely phrased problem definitions, two well explained solutions, and all from the same guy. Sorry we weren't able to help directly, but you obviously found the answers you needed elsewhere in the forum. And you updated the title as well to show it was solved. Thanks.

[Q] CWM Recovery not working

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...

Ok, so I've been Resurrection_Remix_LP_v5.4.6-20150530-hlte.zip for quite some time n

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.

Phone loading into recovery menu after factory reset?

Hey, I rooted my S6 edge (I believe just using the CF autoroot ROM, if my terminology is correct, I'm not too well versed here) and installed a custom recovery menu (TWRP 3.0) a few months ago and everything was working fine.
Today I decided that I wanted to wipe my phone, and I quickly googled to see if a factory reset from the settings app would play well with a rooted phone, and it said it would, it lied. Now my phone is rebooting only into the TWRP menu. I don't know what to do to fix it.
I've tried reloading the back up I made when I installed TWRP, it restores successfully but when rebooting it crashes. I have to reboot using Power+VolDown+Home. I also tried to just reinstall the ROM (assuming that going to Reboot - Download would be the same as using the stock recovery menu) but it also crashes so I don't think ODIN can detect it, the phone does however get recognised by my computer
I'm completely lost on what to do now, as I'm rather new to this, so any help would be appreciated!
thefomaster said:
Hey, I rooted my S6 edge (I believe just using the CF autoroot ROM, if my terminology is correct, I'm not too well versed here) and installed a custom recovery menu (TWRP 3.0) a few months ago and everything was working fine.
Today I decided that I wanted to wipe my phone, and I quickly googled to see if a factory reset from the settings app would play well with a rooted phone, and it said it would, it lied. Now my phone is rebooting only into the TWRP menu. I don't know what to do to fix it.
I've tried reloading the back up I made when I installed TWRP, it restores successfully but when rebooting it crashes. I have to reboot using Power+VolDown+Home. I also tried to just reinstall the ROM (assuming that going to Reboot - Download would be the same as using the stock recovery menu) but it also crashes so I don't think ODIN can detect it, the phone does however get recognised by my computer
I'm completely lost on what to do now, as I'm rather new to this, so any help would be appreciated!
Click to expand...
Click to collapse
Probably need to reflash stock firmware. Then reflash twrp if you want to.
Sent from my SM-G925F
Press volume down and power button after so 10 sec it will not reboot in first time try and try
If this dont work jst copy super su file and update it in trwp it will auto reboot. Try this hope this will work if works thn hit thanks button
Rosli59564 said:
Probably need to reflash stock firmware. Then reflash twrp if you want to.
Sent from my SM-G925F
Click to expand...
Click to collapse
yash_.shah said:
Press volume down and power button after so 10 sec it will not reboot in first time try and try
If this dont work jst copy super su file and update it in trwp it will auto reboot. Try this hope this will work if works thn hit thanks button
Click to expand...
Click to collapse
Thank you both for replying. I couldn't get it too turn off, however I did manage to install a custom ROM through TWRP itself. I think I've just installed TWRP wrong, so thats why it was crashing, so I'll update and reinstall when I'm next at home to see if that stops it crashing. Everything seems to be working now though, so thanks!

Nexus 5 Rom

I have been having issues with my power button, because it kept powering my phone on and off on a loop. So I installed an app that let me use the volume button to wake my phone, but the app started to drain my battery. I realized that I could flash my phone with a ROM that could let me control what the buttons do. So I downloaded all the packages I needed such as ADB tools and the Nameless ROM. I also installed TWRP recovery package and set it up on the phone. I backed up my phone, but I think I accidently deleted the back up, because it wasn't showing up on the backed up list. By the time I figured this, I had wiped my phone. At this point, everytime I try to boot my phone, I get a message in the TWRP saying that I have no OS and if I would like to install SuperSU. I tried this option, the first time, my phone got stuck on the boot animation with 4 dots for a couple of hours. I switched the phone off, went to fastboot, wiped everything, and tried to the SuperSU again, this time, the phone is stuck on a Google screen. I do not know what to do. I tried to google this problem, but I couldn't find anything helpful. Is there anything I could do?
Thank You for your help
You don't have an system on your phone, so it wont boot. You need to boot into twrp, plug your phone into a computer, download any rom,
(
here is a link to paranoid android:
https://forum.xda-developers.com/go.../paranoid-android-7-2-1-aospa-google-t3639696
)
download gapps,
(
http://opengapps.org/
)
start adb on your computer
do adb devices
(your device should show up)
adb push path/to/paranoidandroid.zip /sdcard/
(change the path to the path of the file)
adb push path/to/gappsfile.zip
disconnect your phone
hit install
click/ navigate to and then click on the paranoidandroid(or other rom) zip file, click add more zips, click on gapps, hit install, wait and finally reboot.

Categories

Resources