Hello guys, so basically you are my last hope since I cannot find a solution for my problem (at least with my level of knowledge).
Lets start from the beginning: I (someone with no experience in this topic) decided to try out a new OS on my old Samsung Galaxy S3 since a lot of apps stopped working on Android 4.3. I tried a tutorial on youtube on how to install a new custom ROM. I installed TWRP (3.5.2_9-0-i9300) and later with the help of TWRP Lineage OS 17.1 (an unoffical version for my type of phone) and everything worked perfect.
I started to download all apps I need and to customise my OS. In the end when everything was set up I decided to do a full backup using TWRP and thats where the problem started. In the development section I checked the function, that when you press the power button you can directly boot your phone into recovery mode. So my phone rebooted and ended up in a constant boot loop where at first the Samsung Galaxy logo appears (first picture) and then TWRP appears (second picture) and this process goes on and on...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sadly there is no way to get into recovery mode since this loop just continues. If tried it many times also with taking out the battery and putting it back in. The only thing I have access to is the download mode.
So my question to you: is there anything I could do in the download mode to solve this problem? I saved the important data before so a full wipe wouldnt be a problem. Maybe I can do something with odin?
I really hope you can give me some ideas to try out. Every help is appreciated. Thanks!
Try reflashing a stock ROM first of all.
Then reflash TWRP. Make a TWRP backup (especially the EFS ! That is a "must-do first and foremost" !) of your working system and progress from there.
And in the future, instead of reinstalling all your apps piecemeal I strongly recommend you use Titanium backup (paid version. The free version is very limited), that is a wise invesment for the small sum it'll cost you
@Snakeforhire reflashing stock ROM worked, thank you so much.
I will take a closer look on Titanium backup. Used it in the past but with root access. On the new Lineage OS I dont have root although it shouldnt be hard to get from what I read.
Related
Hi All,
I've been reading this forum for a good few days now as I am trying to get my Kyros functioning the way I need it to. However, I've run into a few problems and am not 100% sure as to what to do. Before I go on, I'm not very techy, so I would be very greatful if replies could be as straight forward as possible, without much jargon as that really loses me
First off, we've just managed to install the windows and ADB drives. I'm following all the instructions from here: http://forum.xda-developers.com/showthread.php?t=858952. That took some hacks our side, but is now working.
I'm pretty stuck on the clockwork reboot though. Again, followed the instructions from the link above. When it initially rebooted, it went straight into the Android System Recovery mode (the robot with the triangle opening screen.) I've tried it over and over, following the directions exactly as explained in the link, but all I'm getting is the generic Androis system recov.
The Recovery zip file is on my SD card. Do I need to unzip it to get the recovery.img to show? Is that something that I'm doing wrong? I also updated the OS (I guess) from the coby site before I started working on these other changes.
So basically, this is the issue right now. Trying to get the clockwork to run and all I'm getting is the android system...and that's when it doesn't just reboot back to the home screen directly.
Any advice would be great. Thanks
And out of the blue, after an hour of angry TV watching, it's now worked. I can't tell you what I did differently as I followed all the same steps as before. Must just have been lucky I guess.
I am having the same issue, and i tried to unzip the update.zip but i boot back to the recovery mode, can someone assist me with this, i have a galaxy s (Vibrant).
thanks
Try going to your sd folder and delete the clockwork recovery folder then uninstall rom manager and redownload it from the market after it installs open up rom manager and click on flash clockworkmod recovery and let it download the update.zip file and your done
Sent from my SGH-T959 using XDA App
Oh yeah after all those steps and you still get back into the stock recovery system click on reinstall package and it should boot into cwm I hope that helps
Sent from my SGH-T959 using XDA App
ASR
baalcat said:
Trying to get the clockwork to run and all I'm getting is the android system
Click to expand...
Click to collapse
like this ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just recently followed the manual way of flashing each .img individually like I usually do. Every fastboot flash was successful I followed instructions to a T and tried it several times. The phone boots and goes through the android is-upgrading its apps then after that I get a black screen with only the time, battery ad signal in the status bar and the back arrow in the navigation aarea, ant ideas what i grg wgon"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
======
Sent from my Tablet
@Jonnyredcorn Did you restore from a backup? If so try from a new device
Why nt make a clean flash and see if it persists or not?
I had this exact same problem, and assuming that you did a dirty flash (did not erase your data), this is why it's being caused
After flashing Android L onto your device it is attempting to run the "First installation" screen but is in conflict with booting up normally as you have already completed the setup.
To confirm this = Try "unlocking and locking" your phone with the power button, you should see the install menu flash up briefly, for a second or less, if that's the case then you're in the exact same situation I was in
There was an old fix for this, but isn't very reliable now, it's worth a shot anyway
"adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity"
This will force the installation overlay on top of the black screen allowing you to "setup" your phone again despite already doing it.
If this fails then your only hope is a fresh reinstall
I don't believe I did a dirty flash. I was under the understanding if I flash the factory images it did to clean white I didn't do a clean wipe and recovery prior to booting into the bootloader and flashing the factory images. I did not restore from a backup this is my first time going from KitKat to lollipop I do not see the installation screen pop up when unlocking and locking my phone
Sent from my Nexus 7
Ah okay then,
I'd suggest attempting a reinstall
If you modify the flash-all.bat removing the "-w" command, which wipes your phone, you'll be able to retain any data currently on the phone.
But as you've said you think you've wiped over it anyway, just complete another wipe over the device and flash it again, better yet download a fresh ROM first
OK so my issue was I forgot to flash the userdata.img which caused me to dirty flash. I just redid the whole thing and it's working it's working perfectly now thanks for all your help guys
Sent from my Nexus 5 running lollipop!
Today i flashed the latest CyanogenMod13 on my Galaxy Tab 2 3G, the zip name was cm-13.0-20160517-1925-UNOFFICIAL-espresso3g.zip. I have followed the instruction of official developer Android-Andi to flash the ROM precisely. I was also flashed Mini Google Apps from Open GApps the ARM version and for Android 6.0. And i flashed too an Android Keyboard for M.
The flashing was success, but not 100% success. At the 'welcome' menu, suddenly all Google Apps were crashing at the same time and lagging my Tab.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also i found that all Google Apps icon turned to unknown or android icons. And some application like File Manager ceases to open and said that 'Package Installer has stopped working.' And some time ago i bluetoothed an Android games called 'Beat the Boss 4' but when i want to install it says 'There's no app to handle this type of files'.
Can someone help me?
Yopu can try different gapps.
On OpenGapps also make sure to not to setup your google account before giving all permissions!
Hello, I've got the same problem on P 5110 and I've tried lots of sources of GAaps. Help please
I'm having exact same issue on my P3110, tried flashing for many times with different Gapps still persist, subscribing to this threat.
Same problem on p5100, cm13 with openapps 6.0 pico. also tried with gapps-600-base version, and a-gapps 6.0.1 one .
tried going to cm 12.1, and same problem there (with 5.1 apps ). what is going on?
E: tried some more- does not matter if i clean the internal memory. does not matter if i flash rom+gapps, or rom-reboot-gapps. Is this ****ery something to do with TWRP? i flashed the newest one, 2.8.5.0. I have not seen something this bad on no other device (have flashed nexus 7, SE arc s, xperia sp, lg g2 several times...)
E2: Got my gapps to work, atleast with CM12.1, wont try to install CM13 as dont need it for this tab. But might work in 13 aswell. Be sure to update your recovery, newest recoveries from http://forum.xda-developers.com/showthread.php?t=2676180 . I had 2.8.5.0, which according to this twrp site was the one available. But the thread I linked has 3.0 something. I used this queue zip flashing with rom+gapps, and now its working. Worth a try if you havent.
hello
if first install
hard wipe
to go back to twrp 2.8.50
put old recovery.img in twrp 3 (andi gave this solution)
regards
Hello guys,
I'm new here, I've read a lot about your different topics and I'm admirative for some level god members with their answers :good: :laugh:
Indeed I'm a dev, but for websites so it's a bit different with phones for me, and I will try to explain as detailed as I can.
I have a samsung SM G965F, bought in Poland (I work here for the moment); And indeed tried to root it for private purposes.
I followed a tutorial; I was on Pie 9 (****tiest ever update for me); from there OEM in DEV tools was activated, and the TWRP was installed.
the phone wasn't root, but I had the TWRP options (when push Volume up+bixby+lock) so thought I'm on the good way, but only after, and there is my mistake, I understood by reading something that I should make faster an operation when enabled the OEM (before it start to delete all my infos) that I should switch to recovery mode (or installation) and if not there was a story with 7 days to wait.
So the phone was just reseted with only memory card datas not deleted, and the phone was working, just the OEM always disabled, and when you select to enable it it says "ok we reboot the phone you will loose all your files etcc..." and anyway after many attempts, it says always the same after the reboots, and never is enabled after. So I tried to install a new rom, and then I thought I had a problem, in the installation it was written "Secure Check Fail : PIT".
So I tried to found the right rom, with the number "6" inside as per this screen :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then the Secure Check Fail : PIT dissapeared and now its just Fail in Odin.
Also, I tried to reboot normally but it says that there was an error and I need to reinstall with smart view or smart touch, I don't really remember, so I just reinstalled the first TWRP and now the screen of my phone is looping on Samsung, and rebooting.
I'm lost, I spent from 3pm to 4 am yesterday in the internet to found a solution, so my final option is write to ask your help guys.
Hope you can help me, thank you in advance
PS: Sorry for the big picture, there is no acceptance unfortunately for resizing codes, or maybe I just still don't have access to this option cuz I have less than 10 messages, if need delete it or explain me if you need pictures, I did it 10 min ago, even if there is not a lot to do because i'm limited with my phone now
Hi Everyone Thans for having me Im stuck
My s7 froze and wouldnt do anything I managed to turn it off ,then it wouldnt boot ,after clearing the cashe and rebooting system it almost started but kept going to the android falling over ,
I read the options to sort this and tried to flash twrp recovery I seemed to go ok but when the phone rebooted it went to the An error has occured while updating the device software screen ,
I have tried smart switch but it does not see /connect the phone ,I can with a bit of messing with the buttons get from the An error /use the emergency recovery function screen to the ODIN Mode screen and the phone connects to odin But when i try to re flash the boot loader it flashes to the end then fails .
Am I right thinking Its the boot loader I need to get on 1st to get any further ?
Can anyone point me in the right direction ?
If ive posted in the wrong place please can you move
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sounds to me, like part of the storage may have suddenly failed or been damaged, causing your device to lock up and after a reboot, triggering this unusual state. Part of the bootloader is likely not getting read or written to properly, so installing fails only after partially writing to the device, and it refuses to boot. You could try a repartition and complete installation - that might also make it worse though. I've seen the blue screen of mild annoyance many times - not sure about the falling android, was there any text? If so, what did it say? The firmware does contain screens for various diffrent panic states, resembling the one you mentioned. I would encourage you to do some more research on those and look for patterns in the way it fails - or doesn't - when flashing other parts of the firmware package. Don't even bother with SmartSwitch - in my experience, it fails at anything the errors tell you to use it for. Also, simple issues like a faulty cable or the wrong firmware can often be overlooked - so make sure those are fine before starting to experiment.