I got into a bootloop after disabling the settings app from the terminal emulator, using the command pm disable, am rooted using magisk. Now it is telling me to enter safe mode, but the safe mode is completely unusable. Anyone can tell how to undo so it boots up normally, besides factory reset
Bummer. If nothing works you could go to recovery and wipe phone clean from there. You'll need to look up the button combo to go to recovery, don't recall myself.
Can't believe you decided to proceed even people told you your device will brick. Nothing you can do other than factory reset your device from recovery. You also can flash ROM via odin. Next time listen to others. Otherwise, don't even ask in the first place
twinh3ad said:
Can't believe you decided to proceed even people told you your device will brick. Nothing you can do other than factory reset your device from recovery. You also can flash ROM via odin. Next time listen to others. Otherwise, don't even ask in the first place
Click to expand...
Click to collapse
Actually my phone was working just fine while the app was disabled ,but I forgot to to enable it again before reebooting my phone , simple mistake
Related
Hello, all. I've had this problem for about a year, but I just kind of put the KF away once I got it replaced instead of fixing it.
Last year, I put my KF into a softbrick, factory reset bootloop. On boot, the KF warns:
Your Kindle has detected a problem and must clear App storage. The recovery process will erase some apps and data from your device.
Click to expand...
Click to collapse
The rest is the generic factory reset info. Press power to proceed. This looks like it goes through the process, restarts, and just boots back up into this message. Thus, bootloop. I've tried looking up others with the same problem, but no one has had the same one I mention. I don't have a custom bootloader or TWRP.
As for what caused this, if i can remember correctly I was having trouble with google apps permissions and changed a folder in /system/ to something else. The fire freaked out and I rebooted it. The above has happened ever since. So the only modification is being rooted. I've tried getting access to adb, but it hasn't listed the device. Maybe I installed the drivers wrong or something, but I didn't mess with it for long because I don't like being in Windows if I can help it.
Any help would be greatly appreciated. Not in too big of a hurry, though, as I have a Nexus 7 currently. ^.^
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Thepooch said:
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Click to expand...
Click to collapse
I knew about fastboot, I should have mentioned. I just don't have the money to spend on one currently. What do you mean by attempt to race it to factory reset and reset it?
Just what I said you have just a little time to race to settings and factory reset it before it fc`s and shuts down some people manage to pull it off.
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
fza99 said:
Ok. I foolishly enabled encryption on my i711 and after putting in the password, the volumes unlock and the system starts. The problem is that if the screen goes off for any reason, the phone reboots. Tried all sorts of things to correct and decided I no longer wanted the phone encrypted. There is no way back. Ok, so I thought I could do a factory reset... No dice. The phone reboots and all is still encrypted and there.
Next I tried clockworkmod but couldn't do ANYTHING there because the encrypted volumes aren't mountable. I couldn't factory reset, install a new rom, etc.
Next I went to ODIN and tried to repartition. No luck there either. I flashed clockworkmod again for good measure and even tried Nand Erase All.
After this I booted into the phone and tried to repartition... Now I have a phone that displays the lovely CM10 boot screen but never gets passed that. I can still get into recovery.
Any thoughts on how to undo the encryption and reflash a rom?
Click to expand...
Click to collapse
I have some very bad news for you.... Encryption is a one way street. Once encrypted the only way back is to flash stock via fastboot.
I can't even start to explain how to use fastboot as I have never been in a situation where I have needed it.
recoveries lose all access on encrypted devices so this is the only way.
Here is some links to get you started... Please do research before you begin the process and make sure you've obtained the appropriate files. I will take no responsibility for bricking your device.
Flashing via Fastboot:
http://forum.xda-developers.com/wik...id#Android_Flashing_Guide_.28with_fastboot.29
Installing Fastboot on Windows:
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Sent from my SGH-I747 using xda app-developers app
Okay my friends wife had an unlucky bad file flash and ended up hard bricking somehow.
And keep this in mind that she never flashed a Int. version.
She flashed the SlimRom 3.1.0-D2SPR then she flashed the custom kernel unlocker file
to use the K747 kernel for slimrom, but the thing was ( She has TWRP ) when she slid the bar to flash
the file, the screen went back to the TWRP home page she waited 5-10 minutes then she tried reflashing the file again
and it said failed. Rebooted and the phone's hard bricked after installing the kernel. ( No LED when USB plugged in for recharge,
No power or haptic feedback. )
Her husband used the same method to install slim rom and his phone is fine
but the screen never went to the TWRP home page, it went straight into installing it.
The thing that boggles my mind is that she flashed everything in order and it hard bricked.
Rom first, rebooted recovery, kernel unlock, cache and dalvik cleared. rebooted recovery
When she tried flashing the K747 AOSP Kernel, she said it never went to the page screen that would show
it install, it just went straight to the home page, retry flashing but failed. ( here's the weird part I've never experienced. )
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Spark91 said:
Is her devices bootloader corrupted? Because all I'm thinking is she's the one in a million of people that has a defective
device itself and a bad flash ( This is what I think ) hard brick her device.
But my suggested solution if correct would be force odin mode via USB Jig or send it in for jtag repairs if possible.
If there is no chance for the both of these solutions then a full blown replacement repair will be the last thing she'll do
because she doesn't have TEP or a warranty on the device.
Click to expand...
Click to collapse
So, I'm just going to rattle through my thought process on this, just to get things clear in my mind:
Her phone cannot turn on at all. Do a battery pull/replace and make sure that there's no going into recovery or download mode. If that's the case, then JTAG might be your only solution.
This happened when trying to flash a kernel. It seems unlikely that a kernel would screw up the bootloader. I was under the impression that only recovery zips touch the bootloader/recovery partition.
If the kernel or Rom zip was for an international GS3, then it would try to write to the bootloader partition. But since you said your buddy's phone flashed the same files just fine, it seems unlikely that they flashed the international zips.
I've had TWRP fail to flash a zip. Each time I tried to flash a zip, it would say it failed. All I had to do was reboot into recovery (even if I hadn't flashed a ROM, so I had no system file), and then I could flash the file. Sometimes TWRP had those issues for me. Her story reminded me exactly of when that happened to me, but if hers won't load into recovery (or download mode), that's a major difference.
After all that, I honestly have no clue how this happened. It sounds to me like the JTAG is the best bet. You can find them online for around $60. Sorry this happened, and I hope you find a good fix for your friend's wife.
Its possible that you can still fix this....
Couple questions. When you try to turn it on, what exactly happens? does it vibrate? what occurs?
There is a possiblity that you can bypass the idea of holding the power button and vol button, try to adb reboot recovery command. ive had this save me about 5 times now when flashing goes bad.
http://droidlessons.com/how-to-install-adb-on-a-windows-7-pc/
make sure adb is installed...
while the phone is trying to boot, keep typing or copy/pasting or in cmd pressing up and enter after you enter the command.
adb devices
if it gives you the UID of your phone you at least know that you might have the ability to fix it.
From here just type
adb reboot recovery and it will reboot into the recovery to allow you to flash a "good" kernel again.
Bit of advice.. I am always paranoid after going through this so many times of a bad flash. As a result i never stack flashes.. for instance.
if i want to flash a rom, kernel, modem, radio..
i wipe dalvik, flash rom, wipe dalvik, wipe system, wipe cache.
Reboot let android do its thing...
reboot into recovery.
wipe dalvik, flash kernel, wipe dalvik, wipe system, wipe cache.
reboot, let android fully boot up.
reboot into recovery
wipe dalvik, flash radio, wipe dalvik, wipe system, wipe cache.
reboot...you get the point.
Just precations i started doing because of issues ive had in the past. If you have a mac, the commands are a bit different so let me know...
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
topherk said:
This is interesting, Hamspiced.
I didn't know that flashing a kernal can "brick" your phone.
Do you happen to know why or how this happens? You allude to stacking flashes... I normally only stack gapps with the ROM, but I was wondering if it's important to reboot and go through the setup prior to flashing gapps.
Thanks for the info!
Click to expand...
Click to collapse
When i had my evo things flashed slightly different.
There were many issues in kernel flashing where if the kernel didnt download properly or you had a bad dl. it will what we called soft-brick. This would allow the phone to "act" like it was booting up but only display a black screen and never boot. Screen would flicker, phone was active but nothing would display and it will not boot loop. kind of just freeze.
We noticed that if we connect the phone to the computer we could actually use adb to access the phone. from there we noticed that we could push recoveries, and even push kernels and radios to the phone even though it wasnt displaying anything.
I figured the easiest way to get through this issue is to see if you can Reboot Recovery through adb if it allows you, and hopefully then you can restore functionality.
Help possibly?
Can you get it into download mode and just use Odin to flash it?
So this may be a stupid question (but it's my first post so go figure) but I've read a few forum posts and I still can't seem to find a resolution.
I'm using a Rogers SGH i3170 with Android 4.3. I used the cf auto root file to root my phone with ODIN and otherwise did not modify the original software I manually installed the SuperSu apk to get around KNOX.
I was going to sell the phone so I went into the backup & reset option to clear out all my information. the phone seemed to clear itself just fine but now it won't go back the 'samsung' boot screen.
It'll show the device name, do the boot animation and otherwise just sits there.
The battery is at 80-90%
My main issue is that I would flash the stock ROM but it also won't go into recovery mode. It just reboots without actually going there.
Did I just brick my phone?
**I'm fairly new to rooting, I've rooted my S4 and Nexus 5 and was able to reset them without issue through the menus without using CWM or TWRP. I'm familiar enough with the processes just need some direction I guess!
Try this: Vol down& power& home. That'll put you into download mode so you can use Odin to return to stock...
You can also try THIS
If that doesn't help then goHERE for more INFO:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk
LENT0N said:
So this may be a stupid question (but it's my first post so go figure) but I've read a few forum posts and I still can't seem to find a resolution.
I'm using a Rogers SGH i3170 with Android 4.3. I used the cf auto root file to root my phone with ODIN and otherwise did not modify the original software I manually installed the SuperSu apk to get around KNOX.
I was going to sell the phone so I went into the backup & reset option to clear out all my information. the phone seemed to clear itself just fine but now it won't go back the 'samsung' boot screen.
It'll show the device name, do the boot animation and otherwise just sits there.
The battery is at 80-90%
My main issue is that I would flash the stock ROM but it also won't go into recovery mode. It just reboots without actually going there.
Did I just brick my phone?
**I'm fairly new to rooting, I've rooted my S4 and Nexus 5 and was able to reset them without issue through the menus without using CWM or TWRP. I'm familiar enough with the processes just need some direction I guess!
Click to expand...
Click to collapse
My guess would be depending on what options you chose for wiping your data you probably wiped the root folder.
in which case there is nothing to boot to.
I have done that before in error and its a pain.
If you still have a recovery great you just need to flash a ROM.
Otherwise you might have to ODIN a recovery back on and then flash. Which is what I had to do.
I was running the latest version of TWRP and a rooted version of the LG G6 port. Everything was stable and worked fine. So I was ready to give it back to its owner who I had modded it for. I went into the settings menu of the phone and did a standard factory reset to remove my account that was logged in so I could test the phone out before giving it to the owner. well when it finished resetting and rebooted, its been stuck in a boot loop ever since.
Tried just clearing both Dalvik Cache and Cache, to no avail. Tried Reflashing the rom and starting over. Still nothing. Tried flashing a different rom. Still nothing.
So what else can I try? and also if its the only thing I can do, rest it all the way back to stock factory everything. How do I do that on this phone. What program do I need and what files. and whats the steps to complete the process.
Thank you in advance for all help that is given
i factory reset in twrp and turned on developers options after first boot then reflashed twrp i always forget backup lol or delete it or use kdz you flashed before anyway i can help i will if you still need
if you have tried to flash the same custom rom or another is still not working, flashes with the program "lg up", you will need a kdz file,and the corresponding drivers. if with that you can not watch this tutorial before doing anything.
if you have a backup made with twrp, it flashes again.
https://forum.xda-developers.com/g4/help/unbrick-lg-g4-brick-hs-usb-qdloader-t3542785
during this process you will have to disassemble the back of the phone, (plastic) you do not need to remove the motherboard completely from the phone, anyway if you can enter download mode try with lg up tool.
if you need help around here we are.
Well now in the process of trying to fix it. The phone bricked and will no longer turn on at all. Is there anyway to fix this ?
Silicon Knight said:
Well now in the process of trying to fix it. The phone bricked and will no longer turn on at all. Is there anyway to fix this ?
Click to expand...
Click to collapse
Can you get into download mode?
Also, it's possible you have been hit by the bootloop