So let's start the story. I rooted my phone with KingRoot, all was good. Replaced it through the "Terminal Emulator for Android" app to SuperSU (The SuperSume app didn't work for me because "Your system is incompatible with this version"), all was good. Wanted to install Lineage OS. Installed it without GApps (I forgot it...), all was good. Downloaded the stock GApps for my phone, and flashed with Lineage OS through TWRP. It was working, but the Google app and Google Play Services were crashing every second. I searched that up and I found an article that said that I should just flash the GApps again (with no wipe needed), tried it but still no help. So i thought to download the mini GApps package. I wiped everything that was needed (Dalvik cache, Cache, System, Data) and flashed them both. since then, it never booted up. It showed the LineageOS boot animation, and that's it. waited and hour, but still nothing. tried to shut it down by pressing the power button for long time, and then turn it on again, but it doesn't help. Problem is, for some reason I can't get to the recovery! I press the power,home and volume up, and it just boots up normally, but that wasn't working also before flashing lineageOS. When i go to download mode, (which i can, but can't to the recovery) and connect it to Windows pc and Odin, it says "USB wasn't recognized" and doesn't work. i also tried another pc, but no luck. Of course USB Debugging is disabled, because i never had a chance to turn it on. I do have a Nandroid backup from TWRP, but i can't get to the recovery, so that's not helping. Can someone help me fix it?
Info about the phone:
Samsung Galaxy S3 i9300
Original android 4.3
Russian firmware (It had a problem with the GPS, so we fixed it there when we been there, and they replaced the motheboard with a russian one)
Running TWRP custom recovery
If any more info needed, tell me and i'll add.
Thanks for helping me.
R3t0nix7 said:
So let's start the story. I rooted my phone with KingRoot, all was good. Replaced it through the "Terminal Emulator for Android" app to SuperSU (The SuperSume app didn't work for me because "Your system is incompatible with this version"), all was good. Wanted to install Lineage OS. Installed it without GApps (I forgot it...), all was good. Downloaded the stock GApps for my phone, and flashed with Lineage OS through TWRP. It was working, but the Google app and Google Play Services were crashing every second. I searched that up and I found an article that said that I should just flash the GApps again (with no wipe needed), tried it but still no help. So i thought to download the mini GApps package. I wiped everything that was needed (Dalvik cache, Cache, System, Data) and flashed them both. since then, it never booted up. It showed the LineageOS boot animation, and that's it. waited and hour, but still nothing. tried to shut it down by pressing the power button for long time, and then turn it on again, but it doesn't help. Problem is, for some reason I can't get to the recovery! I press the power,home and volume up, and it just boots up normally, but that wasn't working also before flashing lineageOS. When i go to download mode, (which i can, but can't to the recovery) and connect it to Windows pc and Odin, it says "USB wasn't recognized" and doesn't work. i also tried another pc, but no luck. Of course USB Debugging is disabled, because i never had a chance to turn it on. I do have a Nandroid backup from TWRP, but i can't get to the recovery, so that's not helping. Can someone help me fix it?
Info about the phone:
Samsung Galaxy S3 i9300
Original android 4.3
Russian firmware (It had a problem with the GPS, so we fixed it there when we been there, and they replaced the motheboard with a russian one)
Running TWRP custom recovery
If any more info needed, tell me and i'll add.
Thanks for helping me.
Click to expand...
Click to collapse
Greetings and welcome to assist. Does kies/smartswitch recognise your phone in download mode ? You could use the emergency firmware recovery option or you can try and use adb to reboot the phone into recovery
Good Luck
Sawdoctor
Nope, not working
Related
Hello everyone, I need help with my Galaxy Tab p5100.
Few days ago, I switched from CM 10.3, to SlimKat. To do so, I had to install the CWM 6.0.4.5. I did this through recovery mode (I had an earlier version and flashed the new version through the older one) and it worked just fine.
I unlocked the root feature, installed some apps, including the Xposed Module, Greenify and BootManager.
Everything was working just fine til yesterday. Before sleeping, I turned off the tab.
Today, and all of a sudden, as soon as I turned the tab on, it keept on rebooting every two minutes for no apparent reason. It just starts, boots into Slimkat, then it reboots.
At first I thought it might be a malfunctioning app, so I booted into safe mode, it stayed a little longer than 2 mins without a reboot, then it rebooted again. Tried that more than once.
I did a factory reset, wiped cache, cleared Dalvik and formatted system from the mount and storage section. Still the problem was there, and surprisingly all my apps and personal data was still there!!
Tried the back up and reset option from the ROM itself, while on safe mode, and still nothing happened.
I tried to flash CM 10.3 back via the CWM, it tells me that it succeeded, then I reboot and SlimKat is still there!
I tried to install the TWRP via Odin, and the Odin said PASS. Then when I rebooted into recovery I found that CWM 6.0.4.5 still there!!
I tried to flash the TWRP via the existing CWM, and again it says operation is successful but when I reboot into recovery I find that CWM is still taking over.
I even tried to flash the official JB 4.2.2 ROM via Odin, and it FAILED. (the P5100XXDMH1.tar file)
I feel pretty helpless and I don't know what to do. Any help would be appreciated.
Thanks in advance!
Update 1: I can delete an app or two before the tab restarts, and when I did and the tab restarted, the apps were restored!
Hi. Just got a Note2 which was running 4.4.2
I downloaded Odin3-v3.07 and got root access. I then used a checker to confirm.
From there, I used the TWRP Manager to install 2.8.7.0.
I think this is where things went wrong. I know I selected the correct phone model, but it gave me an error saying something went wrong ( I think it said something about me having the latest TWRP) . Then my phone rebooted and took me into TWRP.
I made a backup and tried to flash the CM12 rom for sgh-i317m.
That's when I noticed I couldn't get out of TWRP. Rebooting or pulling the battery has no effect. Phone keeps booting into TWRP. I tried wiping delvic cache, cache and other things, but no matter what I do I can't boot into the OS. I tried restoring and it says it was successful, but again am stuck in TWRP. I've now spent the last hour searching for a way to get out and still can't find a solution. Any help would be greatly appreciated.
Notes:
Not sure if this has anything to do with it, but I had forgotten to enable USB debugging when I was in my OS.
Another thing I noticed is when I open the terminal command, there's a running boot script error: E:/sbin/runatboot.sh process ended with ERROR=1
Problem resolved: I booted into download mode and used Odin to root again. That seem to overwrite whatever was causing the Note 2 to be stuck booting into TWRP.
I enabled USB debugging and installed TWRP again. Got the same error but this time chose not to reboot into recovery. Then I rebooted manually, and the phone boots into the OS. I powered down and held Vol up + power + menu and released power button at Samsung logo, and was successful in booting into TWRP. Exited and rebooted took me back to the OS. So I'm not quite sure what it was the first time around that got me stuck into booting TWRP everytime.
Glad you got it fixed! :good:
I'll close this thread.
Hello, I got problem with my standard Galaxy S6 (G920F), i can open recovery and download mode, but phone still reseting on Samsung logo, even after flash newest 5.1.1 rom via Odin. Some suggestions?
EDIT: ADB Sideload every time stuck on 12%
Recovery and download:
http://imgur.com/J1JTWwi
http://imgur.com/DBmP7TB
vangoor said:
Hello, I got problem with my standard Galaxy S6 (G920F), i can open recovery and download mode, but phone still reseting on Samsung logo, even after flash newest 5.1.1 rom via Odin. Some suggestions?
EDIT: ADB Sideload every time stuck on 12%
Recovery and download:
http://imgur.com/J1JTWwi
http://imgur.com/DBmP7TB
Click to expand...
Click to collapse
5.1.1 means your phone has a sytem write protection, so it tried to reboot into recovery itself after auto-reboot => bootloop.
Do you have TWRP installed?
If not, flash Unikernel (you need a custom kernel with this bootloader) and TWRP, then use TWRP to wipe/factory reset and flash any ROM.
Relevant:
http://forum.xda-developers.com/show....php?t=3216658
http://forum.xda-developers.com/gala...3#post63049203
http://forum.xda-developers.com/gala...flash-t3211402
http://forum.xda-developers.com/gala...-root-t3197764
This is one of several how-tos, there are more in above links.
Man, You are awesome! My phone alive! Thanks a lot!
Bad news... new problem Now I got IMEI 350000000000006, phone not logged in network, of course I don't have EFS backup, what now?
vangoor said:
Bad news... new problem Now I got IMEI 350000000000006, phone not logged in network, of course I don't have EFS backup, what now?
Click to expand...
Click to collapse
Use TWRP to wipe cache/dalvik and do a factory reset-
did you check the ROM you used was for your special device, and checked its md5-sum?
I personally would try downloading another one and flash again; once it works, do a backup in TWRP; very easy and done in 3mins.
Maybe you should try to manually log on to your network to see if this works first, in "network settings" tap the line to automatically choose your provider; should be it.
I used 4-file G920FXXU2COI1, after reboot phone not started so I flash Unikernel via Odin, now phone is turned on, but sometimes touchwiz was stopped, maps was stopped etc, phone find my network, but I can't logged
After wipe in TWRP phone stuck on Samsung logo
Hi,
My friend has an Xperia L with cyanognemod 11 running on it. Tried to flash resurrection remix ROM and ended up bad. These are the steps I followed:
1. cwrp recovery was already installed and bootloader was already unlocked.
2. I copied the resurrection remix zip file into sd card
3. Went to recovery, wiped cache partition. (Did not do a factory reset. My mistake).
4. Installed the zip
5. Installed the WRONG version of Gapps. Installed gapps for 4.4 instead of 5.1.
6. Device successfully booted to resurrection remix. However, the wallpaper and apps that were already there is still there! It was like I upgraded the phone to lolippop. However, it is not possible to use the phone because com.android.phone keeps crashing and everything is very sluggish. I was hoping for a fresh install.
7. Now the problem - I can't access the bootloader. If I do adb reboot bootloader or select bootloader from recovery, it just gives me a blue charging light and that's it. But I can access recovery and boot to os still. Also, cwrp recovery is now replaced by cyangenmod recovery and I can't factory reset/wipe cache from it. It fails with 'cannot load volume /misc' when I try to flash the same ROM again.
8. I can't even do a factory reset after booting into resurection remix. I press 'reset factory settings' and nothing happens.
So any ideas? The really bad thing is that I can't access the bootloader and hence cannot use fastboot.
lonesword said:
Hi,
My friend has an Xperia L with cyanognemod 11 running on it. Tried to flash resurrection remix ROM and ended up bad. These are the steps I followed:
1. cwrp recovery was already installed and bootloader was already unlocked.
2. I copied the resurrection remix zip file into sd card
3. Went to recovery, wiped cache partition. (Did not do a factory reset. My mistake).
4. Installed the zip
5. Installed the WRONG version of Gapps. Installed gapps for 4.4 instead of 5.1.
6. Device successfully booted to resurrection remix. However, the wallpaper and apps that were already there is still there! It was like I upgraded the phone to lolippop. However, it is not possible to use the phone because com.android.phone keeps crashing and everything is very sluggish. I was hoping for a fresh install.
7. Now the problem - I can't access the bootloader. If I do adb reboot bootloader or select bootloader from recovery, it just gives me a blue charging light and that's it. But I can access recovery and boot to os still. Also, cwrp recovery is now replaced by cyangenmod recovery and I can't factory reset/wipe cache from it. It fails with 'cannot load volume /misc' when I try to flash the same ROM again.
8. I can't even do a factory reset after booting into resurection remix. I press 'reset factory settings' and nothing happens.
So any ideas? The really bad thing is that I can't access the bootloader and hence cannot use fastboot.
Click to expand...
Click to collapse
There are many ways to get out of this. Nothing is really messed up. If you get a blue led, it means you're in the bootloader. Try reinstalling your fastboot drivers. Firstly, get a fota recovery. If you can boot into android, install this app, [APP][RECOVERY][ROOT]Recoveries and Recovery Installer for Taoshan , allow root access (Enable under developer options), and install Twrp. Boot into twrp, and you can wipe system, data, cache and reinstall your rom without gapps.
The app is hardly recommended by me in this case ( okok i know xD )
After reboot bootloader you get blue led... THAT is fastbootmode
And btw you cant load volumen /misc because our device have no so thats not a error (you can ignore it )
Sent from my mint using XDA Free mobile app
Thanks agent_fabulous and barbarossa, but when the blue light was on 'fastboot devices' did not list any devices. Also, unplugging the device from my pc seemed to turn it off. So I thought it was some sort of charging mode rather than fastboot. Thanks for the information, I will try them and get back to you. This community rocks!
Solved!
Using that app to install twrp worked. Wiped everything and flashed the ROM again. Working like a charm. Thanks a lot
Ok. I have a Samsung S4 mini. Yesterday I installed CM13. Dumb thing to do.
It was an automatic update from CMUpdater, so not through the Recovery menu.
For my surprise, I noticed that this update also updated the ClockWorkMod Recovery to the latest version available.
The CM13 installation went well actually .The phone booted fine. Then of course I needed the new Gapps installed. I downloaded the correct Gapps. Boot into CWM recovery. Choose the Gapps ZIP file. And... Error! I went back to phone to enable root acess (ADB & Apps), and enabled USB debugging also. And...Error! No way to install Gapps with CWM recovery.
After some search I realize that the new Gapps for CM13 is somehow not compatible with the CWM recovery that was instaled. So I downloaded ROM MANAGER to change the recovery to TWRP, which everybody said would perfectly flash the Gapps smoothly. Nothing happened. No TWPR. Only CWM still on. Then I downloaded Flashify and went back and forth on installing and unistalling TWPR and CWM. On and On.
Conclusion: somewhere along the process not only I couldn´t install TWRP recovery, but also have wrecked the CWM recovery. Now, no matter what I do, I cannot enter recovery mode at all, hence i cannot neither install Gapps or Reinstall another ROM to "start from scratch"....
I can boot the phone normally.
I can boot into donwload mode normally.
I tried installing TWRP .tar with ODIN3 but it keeps saying "cant open USB port", so it fails.
I have also installed KIES. It sucessfully install drivers, but fails to connect with my device.
Is there anyway to install a Recovery or a fresh new ROM without having to boot recovery?!
Some help? Please.
Hello,
Welcome to XDA.
Do you have USB debugging enabled in system settings to allow flashing via Odin? You may not even need to use Odin.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s4-mini/help
The experts there may be able to help.
Register an XDA account to post and reply in the forums. Good luck.