So, my kid was sitting on my lap and I was editing build.prop on my samsung galaxytab s2 (SM-T810). And for those of you that dont know, toddlers are the picture of sitting still and motionless.
I wasn't finished editing a line and the screen was hit, my tablet rebooted and I am in eternal boot land.
What I have tried.
Connected ADB. Cannot see device via USB
Connected via ODIN and flashed new rom and stock rom.
wiped data, cache, etc.
Factory reset.
I have TWRP installed and can get into recovery and most recently i tried the command
Code:
make_ext4fs /dev/block/mmcblk0p15
and it seemed to work but still will not boot. The only thing I can do to get into recovery every time is connect with ODIN and reinstall TWRP, then it returns to recovery.
It seems to me I need to somehow get my stock build.prop and upload it.
Do any of you Gods of Android have a suggestion?
If you can enter on TWRP you can try to install a custom ROM, if you can't copy the zip on the flash storage of your tablet you can try to copy it using sideload from the TWRP
Related
Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.
hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...
I followed what you suggested and got the phone back up and working. Thanks again.
Hi, I need help with a (possibly) soft bricked phone. It boots, yet it reboot itself once it tries to read the multimedia files in the internal storage. The owner is a co-worker so I really don't know how or what could possibly trigger this behavior (a virus perhaps?). The device is not rooted, even if I set usb debugging it just keep rebooting and losing all configuration. Uninstalled apps respawn again once it reboots. I tried to flash it with many Odin versions to a proper stock rom, but when the device reboots all the files remain the same, as if nothing were ever done. I tried wiping everything from recovery mode, didn't work either. Whenever I enter recovery mode it updates some files and says it can't gain access to CSC. I'm not an expert on repairing phones so I'm already out of options, any suggestion would be appreciated.
Edit: Android version is 2.3
Try this: http://forum.xda-developers.com/showthread.php?t=2100642
The guide is meant for Jelly Bean, but works even with Gingerbread and should repair the csc.
Cassiusss said:
Try this: http://forum.xda-developers.com/showthread.php?t=2100642
The guide is meant for Jelly Bean, but works even with Gingerbread and should repair the csc.
Click to expand...
Click to collapse
Didn't work either. All files are still there after rebooting. CSC still fails to load in recovery.
I saw some people with this issue in other android devices, it seems the problem is a corrupted internal memory (nothing can be erased or written). I may just give up
Try to perform this shell command:
mke2fs /dev/block/mmcblk0p3
It will force the format of system partition. You can do it with the Terminal included in TWRP recovery for Gingebread. Once done, you'll have to flash a firmware with Odin to rewrite the system partition.
Cassiusss said:
Try to perform this shell command:
mke2fs /dev/block/mmcblk0p3
It will force the format of system partition. You can do it with the Terminal included in TWRP recovery for Gingebread. Once done, you'll have to flash a firmware with Odin to rewrite the system partition.
Click to expand...
Click to collapse
I can't install custom recoveries, it doesn't recognize external storage and not even Odin can rewrite the recovery.
If you're sure that you can't install TWRP with Odin then I don't know how you could solve your problem, sorry. :/
@Cassiusss Hey Bro,
I have been using epirex cm13 builds
but later these days, i didnt used it much as i was flashing around on my 1+3.
Now, i cant boot in recovery and bootloader, whenever i reboot to recovery or bootloader it boots back to rom.
i try adb commands and flashing recoveries through app but didnt work.
Also I tried odin flash it but as it cant boot in bootloader, how can i revert back.
I am using 12 june build Cm13.
Please help.
Try to reboot to recovery or in download mode with this: https://play.google.com/store/apps/details?id=com.antaresone.quickreboot
Anyway, what error is shown when you try to flash a recovery?
Cassiusss said:
Try to reboot to recovery or in download mode with this: https://play.google.com/store/apps/details?id=com.antaresone.quickreboot
Anyway, what error is shown when you try to flash a recovery?
Click to expand...
Click to collapse
I tried ur mentioned app but it again takes 1-2 secs and boots to system.
I also extracted out boot.img from cm13 and flashed it through rashr but after flashing it again booted to system.
Also tried to factory reset from phone but surprisingly it again didnt show anything and booted to system.
Can You tell me any method to HARD RESET or format its system partition so i can odin it ezily.
I think that formatting system will not bring back recovery or download mode.
What's important is to gain access to download mode (because without it you can't use Odin).
Are you sure that booting your phone while pressing "Volume down" + "Home" + "Power ON" keys is ineffective?
Maybe you'll need an USB JIG to force the download mode...
I guess your device memory is broken. Because my friend's ace3 had the same problem with you, and the service center said that the emmc had been broken. So no hope at all
Hi,
so I was about to flash a new ROM to my Z3C, because I was having some trouble connecting the phone to pc (drivers etc are ALL installed and have beend reinstalled too).
Since my phone was already running on .291, I skipped flashing stock rom, went to recovery, did a wipe, flashed 3.1.1.0 TWRP FOTA Kernel, flashed ROM, booted ROM (fine), forgot to flash GApps, went back to reco... Wait? No more recovery? Hmm.. Let's try booting system. OK! Went to settings and did a wipe. It took me into an older version of TWRP (I don't know exactly, something like 3.0.2.8?!), where I did the wipe myself (Data, Cache, System). I did system wipe because I wanted to flash the 3.1.1.0 FOTA TWRP once again (since it seemed to be incorrectly installed) and then install the ROM freshly. So, after installing TWRP (which was "successful") I tried to restart recovery to install the OS. WHAT? Again no recovery? Damn.. Now there's no more system to boot from.
Then I tried to put the phone into Flash-/Fastboot mode, to install the stock rom and start over again. Trying to Hold Vol+/- while plugging in USB doesn't do sh*t. The green/blue LED pops up for a sec and then disappears instantly. Entering recovery with hardbutton method won't work either.
Now I'm stuck with a phone, that can't do anything.. Is there any way to recover the phone?
I appreciate any kind of help & thanks in advice,
furi
NVM! What 'r the chances of 3 different usb cables being broken? LOL. Sorry for being stupid ._________.
So I tried reinstalling LOS, but I got an error: failed to update system image. So I wiped EVERYTHING. the internal storage, data, cache, everything. Then I reinstalled it. Same error but it said success. So I tried rebooting to the system, NOPE, straight to TWRP. Now I was scared. Why is this happening?? So I tried reinstalling twrp, changing the rom, but nothing fixed it. Now, nothing will boot other than TWRP. I try the bootloader, straight to twrp. I try system, straight to twrp. I try fastboot, straight to twrp. Please help, I need to keep my snapchat streaks alive :crying::crying:
I would try to install lg stock rom and then root, unlock bootloader, twrp and finally lineageos.
I'm having a similar nightmare. I have a D415 running running LineageOS 14.1. I downloaded the February 24th update and clicked on it. That booted me into TWRP. I wasn't sure what to do next, so I tried to reboot into the system but it send me straight back to TWRP. Then I booted into recovery, I think, and figured out how to install the update. However, I still couldn't boot the system. Then, I tried to restore the system . Everything seemed to go fine, but TWRP just looped me back to TWRP.
Just to be clear, is the correct method of booting to the system to select "reboot", then "system"? Is there any other method?
On the main screen, there's a selection called "Mount". If I click on it, I see "Select Partitions to Mount" . The top selection, "System", is unticked. I tried ticking it and rebooting, but was still returned to TWRP.
I was in the same boat....
Hey everyone, I'm hoping this works for you like it did for me. I'm a avid fan of the Linage OS and TWRP-- I donate to them like they're a charity! Lol....
Any who, I constantly check weekly for my "nightly" fix; however dread the update due to the TWRP loop. So, I decided to download the update via my phone browser to the SD card, and update manually.
What do you know, no TWRP loop! I use to have to go thru a 4 line script I found online to boot up to the system. So basically, go to recovery and install the update manually. Don't let the updater do it for you. If you are using Linage SU and Xposed, remember to reinstall.
---------- Post added at 03:12 AM ---------- Previous post was at 02:58 AM ----------
I found the script on Reddit under Linage OS: "How to fix TWRP boot loop after OTA. The article says it's only for MAKO devices; however, due desperation I tried it and it worked.
Use the l90 repartion tool
If u have a custom recovery use LG optimus l90 Reparation tool . Pick the stock option. It'll reboot then start again to finish. When it's done you'll be in clockwork recovery. Don't worry if u had twrp. Mount system then flash a cm based rom plus apps. See if it works.
I got distracted by life, but this weekend I put in some hours working on the phone again. The phone is stuck in TWRP 3.1.1-0. After endless misery, it seems it had a corrupted SD card. I've got a new 32gb SDHC in FAT32. I put lineage-14.1-20181007-nightly-w7-signed.zip on the card and put the card in the phone. Then I browsed to "install" and selected "sdcard (29648mb)". However, the zip file doesn't appear. There's just a folder that says "(Up A Level)". If I click that, there's a ton of empty folders.
How come the zip file doesn't appear? How can I install Lineage?
Here's more stuff I've tried:
installed Java (necessary for ADB, I think) for Windows 7
Installed universal ADB drivers
Plugged in phone
Followed instructions on https://www.xda-developers.com/install-adb-windows-macos-linux/ "Microsoft Windows ADB Setup”
Opened ADB, typed "ADB Devices"
My phone not detected.
Windows sees it as "target_device=w7"
Tried installing LG drivers. No love.
Hello, I've been trying to bring back to life this old XT1068.
In the past years, I had installed several ROMs until one day the phone stopped working (probably I made some mistakes like flashing something not supposed to be flashed on this device, probably) and since that moment if I turn it on it remains stuck on the boot animation (the coloured google dots moving...).
I tried everything. I have TWRP 3.1 installed, I tried to wipe everything, I tried factory reset, I tried to erase the internal storage, I tried to install new ROM, including a stock ROM and the stock recovery. The result is always the same: no errors at all in TWRP, but it's like nothing changes. It does not boot and if I go to TWRP I can still see files that I put in the phone years ago, after I tried every possible wipe. Imagine that I still see the WhatsApp folder of years ago.
As I already mentioned, I also tried to flash a stock recovery: the process finishes without errors but if I reboot to recovery, I always end up in TWRP.
The only thing I can do is to reboot into recovery or fastboot.
The phone is recognized by the computer ("adb devices" / "fastboot devices").
Does anyone of you guys ever experienced something like this?
Thanks in advance.
I have exactly the same issue. Did you find a solution?
I never got that problem, is pretty strange, i think some zip you flashed before is still installed automatically, for example, there is some option on supersu called survival mode, if you enabled that, i think an supersu uninstaller zip could work, also you can try to install any rom, install supersu and check on supersu settings
---------- Post added at 07:15 PM ---------- Previous post was at 07:14 PM ----------
Also probably some partition got damaged or anything, i recommend to flash an stock rom that flashes many things except for nvdata and nvram partitions because it could make you can't get signal if those partitions are from another zone
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
eagledipesh said:
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
Click to expand...
Click to collapse
Hello!
I`ve done the process to install via mfastboot the stock IMG, no errors at all. When the phone reboots it goes into the previous installed rom boot animation and stays there at bootloop.
I even tryed to install an updated TWRP recovery (3.4) via fastboot. Is shows "OK" but when it loads it is still the previous version.
It looks like the phone is "write pretected".
Any further suggestion?
Thanks in advance.
Allisson
Same problem here. I can accces the fastboot menu via "VOLUME DOWN + POWER" but whatever I try, the red error message comes up. I can boot into twrp via USB/PC but i cannot install it. I cannot factory reset.
when I reboot from TWRP I come to lineageOS boot loop.
ANY IDEAS?