Hi, I have a rooted s4 sgh m919. I am running twrp custom recovery. So I just flashed cm 13 nightly build for the s4 and it worked and ran through boot up and everything. Then I realized that I had stupidly forgotten to backup my apps(I though I had but it was a twrp backup). So I returned to recovery mode using adb because my up volume buttons dont work(biggest problem for me now) and used twrp restore of a backup I made before the new rom. Now I know that my twrp backups work because I have successfully restored before but that was using the same rom, this is the first time flashing a new rom. Since I am a noob, I didn't know that I have to factory reset and delvik cache wipe before I restored my backup since they were different roms. Now after booting up and getting past the boot animations it goes straight to a black screen with a bunch of "Unfortunately ______has stopped" for just about every single app I have including system apps and UI. I can boot into the download mode prompt(where it says volume up to download mode, down to reboot) but since my volume up button doesn't I cant boot into recovery or download and do a factory reset. I can boot into safe mode but I still get the same black screen with a bunch of "Unfortunately ______has stopped". I also can't do it through adb since I have no access to phone settings and when I connect to the computer, the computer make a sound recognizing something was plugged in but won't show my phone in the libraries and when I use "adb devices" my phone isn't there. I stored my backup onto my ext sd card if that helps. Is there anyway to get into recovery mode or even just do a factory reset without using volume buttons or the computer? And has anyone else had this problem and if so what is it called(hard brick, soft brick, bootloop.....). Thanks!
You need to fix your up-vol button.
There is also a special micro USB loopback plug which I think can make the device boot into a special firmware loader mode. Then you would use heimdall/odin to replace the firmware, but I have never done that.
As for what to call the problem, I say "dumb user with broken hardware". You knew that your up-vol button was broken and what would happen if you could not get into recovery. Now that it has happened you want a magical fix instead of doing what you already know you need to do. Sorry for honesty.
1st- buy a usb jigg, they go for less than $5 amazon, eBay etc.
2nd - while phone is powered off use the USB jigg to put it into download mode
3rd- use Odin to flash the latest ok3 firmware.
4th - use Odin again to flash cf auto root. (No need to check if it has root the recovery you flash should be able to root it)
5th- use Odin again to flash Philz touch cwm recovery.twrp causes lots of problems when flashing. Philz recovery has been flawless.
6th- flash any rom of your choice. If you can't get into recovery theres an app called quickboot that can put you in recovery as long as you're rooted.
Related
I am not new to the concept of rooting and loading a custom rom. This is the 3rd android phone that I have bothered with. However it is the first one I have had to use Odin to root or push files to.
I have used CarpeNoctem's writeup on how to root and utkanos' CWMR port writeup. Ofter verifying I had root, I decided I would try out Carpe's OsiMood. No problem right? Here is where I am wondering what if anything went wrong on the previous steps.
I made a back up ofter finally getting it to recovery mode, and when I tried flashing the new rom, it would not complete the process.
As it sits, when I choose recovery from CWM it reboots to the android with triangle screen(see attached video). What concerns me is the lack of fluidity into the recovery, the fact that it loads in only after the battery is removed and the phone is turned back on and lastly that I cannot flash a new rom.
It appears as though I need more posts to add my link for youtube.
Please add standard youtube weblink before this to watch the video.
/watch?v=qpQyQB1aozs
What would you recommend my first action be?
Thanks,
Steve
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Thanks for your insight. I tried volume down and power before but when I saw the samsung logo pop up I figured it wouldn't work.
I will try flashing again and report back. Thanks again.
-Steve
Tried flashing again, worked great. If only the glide had more support. Lol.
Currently running OsiMood.
Sent from my SAMSUNG-SGH-I927R using Tapatalk
gabby131 said:
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Click to expand...
Click to collapse
My glide does not boot. I can get into Download Mode. I can NOT get into de recovery mode. I think my NAND is corrupted.
How can I mount the /system partition? Because I flashed too many roms with ODIN, but nothing, still not booting, I get stuck in the samsung logo.
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Kodiack99 said:
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Click to expand...
Click to collapse
I've already flashed the stock recovery, the CWM, a lot of kernels, even I tried to flash the kernel and bootloader of the Galaxy S II, but nothing.
I'm starting to think that maybe is a hardware problem. Hope not, but I'm not moving foward.
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
I had a boot loop once ,had me stumped and it turned out to be my sd card was poached and caused the loop.
Kodiack99 said:
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
Click to expand...
Click to collapse
Exactly... It goes all over the process bar, says succesfull, the phone turns off, and nothing. The phone not even restart itself, I have to remove the battery, put it back again, and then it turns on, but just to show me the samsung logo.
I've used the ODIN version 1.85 and the new one 3.04. But nothing. This is so frustating.
---------- Post added at 04:23 AM ---------- Previous post was at 04:04 AM ----------
I've opened a thread with all the symptoms of my bricked phone:
http://forum.xda-developers.com/showthread.php?t=2035742
Please, tell me there is a solution...
There are one alternative to boot
1. Shut down and then restart phone in recovery mode. For the Samsung Captivate Glide, this required pressing the power, volume down and home keys all at the same time.
2. The initial screen which appears gives you a choice of loading a replacement OS (volume up) or entering recovery mode (volume down). Note you have to hold the volume down key for several seconds before the recovery mode menu appears.
I am soft-bricked (I hope). A boot jig does nothing for me, but I am able to get into twrp recovery. It won't let me flash my current rom though (Mijjz). What should I do? (I am able to access odin through the twrp recovery right now though, and the computer does recognize it.) I am not able to boot directly into it. When attempting to flash in twrp it can't verify the partition size. I believe this is emmc?
Edit: This helped, but... http://forum.xda-developers.com/showpost.php?p=27852689&postcount=435
So this got my phone to boot again (yay) and now it can go into download mode and such, but my phone appears to be in a boot loop of the sprint logo, turning on and off. =( now what?
Edit #2: I am posting how I got this running for future visitors with my issue to see that there is hope of getting there device back online . So after I was able to get into download mode, I was able to go and flash the El26CWM and then do a Wipe on everything. I then was able to flash my favorite ICS rom, and get on my way. Unfortunately somewhere along the way my Modem got wiped out so I had to go back into download mode to flash it, and I found a new issue. For some reason, my phone still refuses to enter download mode without a jig. So I put my jig in, and downloaded the modem. All is working now (except I still can´t figure out why I need a jig to enter download mode, and the recovery wont boot for me either. It just goes and boots up normally. Its like until the Rom is loaded, it doesn´t take any imput from the buttons. I´m now running an FF18 kernel, so I find this to be odd, but at least I have a working device. Now I´m off to buy myself a nice memory card to compensate for the lost 8 gigs. The only thing that I can think of that may be causing the no download mode issue (although I can´t see why or how) is that I had a custom splash screen (not boot animation, splash screen) before I corrupted my emmc. Throughout the whole process of restoring, it displayed my custom one, except when I put on EL26, it went back to the Normal Boot screen. (the only time since the emmc screwed up that my buttons responded) But when I flashed back up, the custom one came back, and my controls to get into recovery and download mode stopped working again.
So I bought 2 broken Galaxy Tab 3 7.0 from a friend knowing that the screens were cracked and that there were pass codes but I just figured I could replace the screens and then wipe them. Fast forward to today and I got one fixed but it won't go into recovery or download mode. I do the right button sequences for each one and but it just boots up as normal. All the buttons function and I tested them with the device on but no matter what I do it just starts up as normal. Does anyone have any suggestions on what I can do?
Just replaced the actual volume buttons and still no luck. Any one have any idea?
Rooted ?
Options:
If you can get into system ( normal bootup ) try enable USB debugging and install ADB on PC then run adb reboot boot loader or adb reboot recovery
or
If you are rooted, install Rom Toolbox and use reboot option
or
Use a usbjig, its small and cheap XD once you plugged in you can reboot into boodloader
Sorry to bump this so late but I just started trying to fix these again and still can't figure out what to do with this one. New buttons are installed and they work when the tablet is on but whenever I try to boot into recovery or download mode it just boots normal. At a lost here any suggestions?
Ok ordered a USB jig and got it into download mode. Loaded stock from odin and it still popped up with password so I flashed stock again with odin but erased NAND and now I'm just stuck at the final samsung screen and it won't boot. Tried 2 different stock roms with no luck no idea what to do
Hi guys, I rooted a friends s3 to enable aws on it and it was working , yesterday she calls me and tells me that it is not working anymore. So I check it and notice there is no root access.
I try to install it using CFRoot . odin flashes fine , I see it running on the phone but once you boot in Supersu states it is not rooted.
Next tried a slew of programs, towelroot apk but nothing works.
Next tried to factory reset, boot in to twrp and I get asked for a password, hit cancel and I get in to the menu. I try to mount the sd card and it fails, trying to install zip from sd fails, factory reset seems to work, wipe data fails and ask for a decrypt code.
I also tried using CWM recovery with basically the same results.
THe last thing I tried was downloading the same firmware 4.4.2 and flashing with odin, it says successful but after rebooting, the phone is exactly the same, nothing changed , it has the same apps, same wallpaper.
I am wondering if my friend let her son play with the phone and turned on some kind of encryption or security that is stopping it from getting wiped back to stock.
Try flashing stock ROM again but uncheck everything except f reset time. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait 3 seconds, replace battery, use button combination to boot into recovery, factory wipe, reboot.
To root, flash twrp, then flash supersu.zip from recovery.
Download the latest tar version of TWRP from here: https://dl.twrp.me/d2att/
Download supersu from here: http://forum.xda-developers.com/showthread.php?t=1538053
Save supersu to the phone's internal or memory.
When flashing TWRP in Odin, uncheck everything except f reset time. When you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait 3 seconds, replace battery, use button combination to boot into recovery, flash supersu.zip, reboot.
Long story short installed substratum and it was working fine, had a navbar theme already running and installed another one. Few hours later rebooted phone and when it booted back up systemui crashed and it went into bootlooping into that over and over again. Now it bootloops a few times and goes into a recovery menu that only gives me the options to try rebooting again or a factory data reset.
The phone boots into bootloader/fastboot just fine and I can get into recovery but the only options I have are 'try again' and 'factory data reset' I know that FDR is basically my only option and so be it. BUT IF POSSIBLE I want to try and backup the internal data or at least as much of it as possible.
So, is it possible to backup any internal data with only having access to bootloader/fastboot.
I've spent over an hour searching to this answer but either I was searching wrong or simply was not able to find the answer. Pixel XL is 100% stock. Never modded, never rooted, stock recovery, stock latest official Oreo from OTA update.
So again. Absolutely no access to the OS. Only access bootloader/fastboot and a form of the recovery menu and I would like to somehow backup the internal data. I don't care about apps or any app data, specifically just the user data if at all possible. If not well then I'm screwed and that's that.
Hello,
Happened to me also something like this. The phone rebooted and the only option were those presented to you also. But, I pressed the "Try again". If this still doesn't work, when the device is rebooting, and the white screen appears, try and hold on to the power button until the moving dots appear.
Also, this didn't wipe anything on my device.
Hope this is useful to you.
moraritza1 said:
Hello,
Happened to me also something like this. The phone rebooted and the only option were those presented to you also. But, I pressed the "Try again". If this still doesn't work, when the device is rebooting, and the white screen appears, try and hold on to the power button until the moving dots appear.
Also, this didn't wipe anything on my device.
Hope this is useful to you.
Click to expand...
Click to collapse
Does nothing. Just reboots back into recovery. I've tried Try Again probably 100 times and nothing ever changes. Even safe mode does not work. The SystemUI is completely dead.
I'm 90% sure there is no way to fix the phone other than factory data reset and I'm fine with that. I just want to know if I can backup anything from bootloader/fastboot before I do that.
Have you tried using ADB to boot ( not flash ) a custom recovery, and from there to backup the phone, and after if it's possible, to use the USB-OTG to copy that backup to an USB memory stick?
Looking at the Substratum FAQ in the app it says that if you experience a bootloop you should be able to flash /storage/emulated/0/substratum/SubstratumRescue.zip in recovery and it should fix the boot loop.
matt0720 said:
Looking at the Substratum FAQ in the app it says that if you experience a bootloop you should be able to flash /storage/emulated/0/substratum/SubstratumRescue.zip in recovery and it should fix the boot loop.
Click to expand...
Click to collapse
As Matt already mentioned, there's a rescue zip file which comes by default with substratum. It's purpose is to remove all overlays which you've currently installed.
In case you don't have a custom recovery installed you can simply boot into twrp via adb (without having flash the recovery)
Android-xp said:
As Matt already mentioned, there's a rescue zip file which comes by default with substratum. It's purpose is to remove all overlays which you've currently installed.
In case you don't have a custom recovery installed you can simply boot into twrp via adb (without having flash the recovery)
Click to expand...
Click to collapse
What if you're bootloader locked? Is there a way to recover from a bad overlay?
You could try to flash the factory image if you've unlocked the BL, just remove the -w from the flash all script
bobby janow said:
What if you're bootloader locked? Is there a way to recover from a bad overlay?
Click to expand...
Click to collapse
If you have checked the option to potentially allow unlocking your bootloader in dev-settings you can use fastboot to unlock your bootloader and boot into the bootable recovery image