I have an unlocked (but not rooted) ATT S4 active that I have been using on Cricket.
It now refuses to boot; just displays the ATT globe.
I can hold vol-down, power, and home and boot into a screen the warns me of the danger of booting a custom OS.
I can also hold vol-up, power, and home and, after a blue “recovery booting” appears, boot into a screen which at the top says
Android system recovery
LRX22C.I537UCUC0C7
And then the selection menu:
reboot system now
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery logs
Enable cp logging
Disable cp logging
I have tried wiping both the cache and the data (factory reset) to no avail.
Although it could be a hardware issue, I suspect it had to do with an app that started loading from a repo other than Google. I stopped it but it started generating errors; when I tried to reboot, it wouldn’t.
Since it is practically bricked, I see little downside to loading a later ROM, even with no ability to backup what was there. I have installed Android development and ADB on my Linux box but don’t see how to proceed. All of the help postings I see assumes that I can root the machine after the machine boots; I never get that far.
I have looked for help but haven’t seen anything. (I’ve tried to RTFM!) Can anyone point me in the right direction?
Thanks.
-Jack
Related
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
whitechameleon said:
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
Click to expand...
Click to collapse
i have now tried to flash the firmware while in download mode using a less than legitimately obtained lg R&D tool. however, i need V10F_00.kdz and i am facing a bit of censorship. any kind soul willing to host this file on dropbox or similar so i can download it?
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
J2270A said:
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
Click to expand...
Click to collapse
believe me i have. the only combo i can get to is download mode. there is a combo for a hard reset, but my touch buttons arent active during boot.
My Polaroid S10 tablet, build number AS10-20130827 is stuck at the boot screen so I cannot get to debug mode, and from what I can assess, this model cannot be forced to do a factory reset by pressing volume keys with the power switch. What I need to do is wipe the system cache area. Unable to do that, I have downloaded a new firmware image and installer from Southerntelecom, but since I am unable to get past boot screen, I cannot enter debug mode to establish a USB connection. The Phoenix suite loader *does* provide instructions for a procedure to try if the automatic update fails (the procedure is for a "manual update"), but try as I might, I cannot get out to work.
Does anyone know if disconnecting the battery will clear the system cache (if it is in static ram) or is system cache stored in flash ram? Ant advise will be appreciated!
Ok so, a bit of background, I'm on a Vodafone speed tab 6 (vf-1397) running on a root using kingoroot converted to super sume using the app, everything was running fine as such I decided to start looking for apps to use when rooted and ended up coming across jrummyapps boot animations As such I thought, "oh that looks cool let's get that" being naïve and not having any recovery boot loaders installed because I only found out about them after I got into a boot loop. So I proceeded to test a few and they all worked till I got to the third, it proceeded to lock it into a boot loop and now I have no clue what to do, is there anything that I can do, I've tried everything in the recovery menu and nothing. Any help would be highly appreciated I did do a factory reset so it's not currently rooted it's just stock with a custom boot animation that I can't seem to get rid of. Thank you. If all else fails I'll take it to a local Vodafone store when I get back from my holiday.
Another thing I should add currently from my device I can
-reboot system now
-wipe data/factory reset
-wipe cache partition
-power down
-enable adb
Update on current status.
I've found a stock rom for the device and now have the files however, i didn't have usb debugger turned on before it got stuck in a boot loop so, are there any alternative ways of saving it or have i completely messed up?
I know its grave digging at this point but ........
load in recovery and select start adb
then select restart
the device will now load with an unsecured adb connection active
Hello everyone,
I’m actually not an android developer but managed to maneuver myself in a quite tricky situation. I think I need some help from someone how has deep insights in the that topic.
Right now, I’ve got the problem that only TWRP would start if I press the power button of my Ulefone Armor 6. The Stock ROM won’t. My original goal was to restore pictures I deleted by using a recovery tool on my pc. For that reason, I tried to root the phone by using TWRP and Magisk. I performed the following steps:
- Unlocked the bootloader in the developer options and by using the command “fastboot oem unlock” on my pc.
- Installed TWRP 3.3.1 for my Phone by using the command “fastboot flash twrp.img”
- Rebooted the system in recovery mode. TWRP was installed and asking for a PW. Decryption didn’t work with the set PIN. I couldn’t find any files (installation file ) in the filesystem after clicking “Install”
- Restarted the phone in “normal mode”. The system was now in factory settings without performing anything like this on purpose. I couldn’t find any files like pictures. I thought: ****, I ****ed up! I made my situation even worse than before…
- Every time I booted the stock ROM, TWRP was gone afterwords. I could only open the stock recovery. For that reason, I installed TWRP a couple of times. When y restarted in recovery mode directly after installing TWRP it stayed.
- Then I removed the PIN in Android without any result. TWRP was still asking for a PW.
- I pressed Wipe and Format Data in TWRP. After that the PW request was gone.
- I installed Magisk V20.4 from my SD-Card by using the install button in TWRP. No error occurred.
- After rebooting, a pop up from TWRP appeared with something like: “corrupt data: you need to perform a factory reset” without any other options. So I did it.
- On the next normal reboot, no android appeared, but only TWRP by asking for a pw again.
- I pressed format data again. TWRP was not asking for the PW again.
- Now I did a backup with TWRP for the first time…
The current state is:
When I press the power button only TWRP starts. I can also use the fastboot mode. But I can not switch off the phone by pressing the power button or using the Power off command in TWRP. It will always restart.
Now my first goal is to restore a many files as I can by using any rooted ROM. Later I would like install the stock ROM again. In the process I would like not to brick my phone which is actually the one of my girlfriend… So please, what can I do?
Many thank for reading everything and for the help
If someone needs the logfile from TWRP, I can send it via PM I guess.
yo...
if your fone is like mine, and you cant take the battery out, you cant power off. you need to have the usb lead out of your machine in order to shut down, and that's in the os, if usb is plugged in, fone will reboot. By pressing power off switch, you only reset, because you are not in the os which has the turn off function. Hope this makes sense
After soft-reset, the usual splash screen (with unlocked bootloader message) appears, then it disappears, the phone makes a single vibration, the splash screen happens again and it loops from there. Model number is SM-A202F/DS. I can't pull log files using ADB.
Can anyone help me?
UPDATE: Tried flasihng the latest firmware from https://www.sammobile.com/samsung/galaxy-a20e/firmware/SM-A202F/XEO/download/A202FXXU3BTE2/344595/ and using the HOME_CSC file as oposed to normal CSC which would wipe /data. The flash was sucessful but instead of bootloop the phone entered recovery mode with "android cant be loaded" error. I've decided to wipe /data from there (most of stuff I have is either Google synced or stored on external memory anyway) and the phone boots normaly now. So now I have a new question - how can I integrate system app updates with factory versions without risking another bootloop?