Hey guys, I have TWRP 3.0.2-0 was running 4.4 (i think) got an system update earlier today, and the phone asked to restart to install, (absent minded) I pressed yes.... The phone rebooted into recovery and thats as far as it went. I have all my stuff backed up ( did that last week) since I had intentions of going with a custom rom.
restoring the system didn't work, so i wiped everything and installed RR with gapps. Successfully wiped and installed both however, phone still boots back into recovery, not system.
How can i get it back to boot into system?
I found a fix which worked for me at
http://forum.xda-developers.com/tmob...puter-t2873386
Related
First off I am on mdk and rooted and up until today have been running hd 10.2. I had been having some weird things happen with twrp 2502 so I went into goo and tried to update to the newest version of twrp. it downloaded and went through with everything and I rebooted into recovery. once I got into recovery it was showing I was still on 2502, but it was asking for a password which I had never seen before. I backed out and tried to boot into my rom again and it got stuck on the samsung custom screen. pulled the battery a few times and still kept getting stuck. went back into recovery and tried to restore a known good backup that I had restored before, but it keeps failing. I had rls12 on my phone so I tried installing it dirty since I cant wipe anything due to the whole password thing in twrp which said it was succesful but still gets stuck on the samsung custom screen. it sits there for about 10 seconds and loops. I tried about 10 more times to get my backup restored and it finally finished and booted into the rom. I left it this way for an hour or so and did some stuff with my phone, tried to update twrp again which did the same thing again and still shows 2502. after the reboot I am back to the same problem of not being able to do anything in twrp except restore or dirty flash, I cant get the usb to mount in twrp so I cant try putting another rom on the phone unless I go and buy a micro sd adapter.
I am in the process of downloading a stock mdk rom to try and flash in odin, but is there anything I can try before I go through with this, or is it pretty much my only option.
after some more research I think I figured out what caused all this. I wiped the data partition with the old version of twrp which screwed it up pretty bad. Apparently the older versions of twrp were known to have this problem. I kept trying to restore, but trying to restore kept failing on the data partition. After about 25 attempts of trying to restore just the data partition I was able to get it to work finally, and then I restored the the others and got it to boot back into the rom. like an idiot I rebooted the phone back into recovery after it finished and had the same problem again. another couple hours wasted trying to restore the data partition and it worked again and this time i was able to get twrp to update and then went back to recovery and formated the data partition again and it seems to have fixed the problem. Now to figure out why hd rls 12 wont install.
What fixed it for me:
I had made a backup through TWRP 2.6.3.0, but then upgraded to 2.3.6.1 after. Not sure why it didn't work on 3.1, I flashed back to 2.6.3.0, flashed my backup, and everything works again.
So, I've been having one hell of a battle trying to get MJ9 and ROMs based off it to work in the last couple days. In the end, I have decided to go back to my Liquid ROM that I have a backup of yesterday morning in TWRP. This backup, until now, has served me well and has gotten my phone back to how it was.
Until now.
I wiped everything through TWRP and tried to recover my ROM image... Now when I boot, it's stuck at Samsung Galaxy Note 2 screen, and stays there indefinitely. I can boot to recovery if I pull the battery. How does this happen? I was recovering back to this backup just fine until now.
I've deleted system/cache/internal storage, flashed, then deleted cache, no luck.
I flashed Beans stock deodexed 4.3 image. That booted ok, but when I go back to recovery, my Liquid backup still will just hang at the Note 2 screen.
What can I do from here to get it working? Do I need to ODIN a pit file? I'm at a loss.
I rooted my device a few days ago in order to stop the 4.1 ota update, I am currently on 4.0.4 and the device is an xt912.
Today I decided to install safestrap and after installing the recovery and booting into it, I backed up the stock rom.
After backing it up, I clicked on reboot to system.
The device then jumped into a bootloop.
So I cleared cache, dalvik cache, and even factory reset but it won't pass the DROID eye.
So I created a new slot and restored my early backup and to my suprise, it booted up.
I then rebooted back to recovery and cleared system, data,cache and dalvik cache of stock slot and restored the same back up there and rebooted, and it booted up nicely. But after that the recovery kind of disappeared. So I installed safestrap apk again and rebooted to recovery to make sure it flashed.
I was able to boot into the recovery but as I tried to boot back into the rom, I got stuck in a boot loop again.
My problem is if I reinstall the recovery, the device gets stuck in a bootloop, unless I wipe everything and restore my backup.
Also when turn off the phone and connect it to wall charger, the battery sign doesn't show up again.
Can u guys help me out??
Doesn't matter if I loose my stuff.
I just want a working 4.0.4 with root and to be able to charge the device when it's off.
(BTW my version of safestrap is 3.3.0 I think. Its 3 point something.)
I need help ASAP.
Sent from my DROID RAZR using XDA Free mobile app
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Its my daughters bog standard, cheap chinese MTK6580 phone (uhappy up580 if it matters)
It came with stock 5.0 a few years back so I flashed TWRP, rooted it, ported a CRdroid 5.1 rom for it and was working fine. Yesterday on boot every app refused to start, or stopped, or froze including stock launcher and settings so I couldnt do anything at all. Booted to TWRP and wiped cache and dalvik but although TWRP said completed, it hadnt.
So decided to wipe EVERYTHING including data and again TWRP said it had but upon reboot the faulty rom was still there, not working.
Tried to flash a backup that ended in tar error, fixed that and it flashed the backup fine, rebooted but it hadnt.
Tried to TWRP flash a new rom, said it had but it hadnt,
Used SPFlash tools to flash the stock 5.0 rom, THAT said it completed after the usual time and procedure, rebooted but it hadnt
Used SPFlash tools to completely format and wipe the phone which also said it had completed but it hadnt.
I CANNOT wipe this phone using any method I know of! or install or flash anything! Just this same custom rom that was fine for years and just went wrong. Does ANYONE know how I can somehow wipe this phone or flash a new rom? Tried flashing a TWRP with SP tools AND a TWRP .img and they all said completed but obviously, nothing did.... I've accidently bricked phones easier than I can deliberately wipe this one
Any help greatly appreciated.
emmc is weared out. therefore it is read only
aIecxs said:
emmc is weared out. therefore it is read only
Click to expand...
Click to collapse
Gah... exactly what I suspected but hoped not
cheers