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
Related
Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob
Hi there,
Today I received my Xperia Tablet Z and sure enough, the first thing I did was flash a custom Rom
But my device wouldn't boot up anymore...
Basically I unlocked the bootloader via Sony's key, flashed a boot.img via fastboot and then flashed the Rom via the recovery.
All I got was a bootloop - regardless of which custom Rom I used (AOKP, Cyanogen stable, Cyanogen nightly, Cyanogen unofficial, ...)
I tried doing a factory reset but to no avail.
I manually checked for each delete / wipe option in the recovery, but the device simply would not boot further than the boot animation.
However, after some time I stumbled across a Rom that contained the TWRP recovery instead of CWM.
And this one asked me for a password when I booted.
"A password? What for?!"
Well, simply cancelling the request works.
But it seems that my whole problem had to do with that password request
As it turns out, the data partition was encrypted would not let me access it.
For some reason unknown to me, it was not wiped in CWM (some error popped up when trying to format /data).
TWRP allows for doing a format on this one ("full wipe" if my memory does not fool me) and voila - the tablet would boot!
So to sum it up:
After unlocking the tablet, there might still be an encrypted /data that can't be accessed by any custom Rom.
Wiping this /data solves the problem - and can be done via TWRP.
I just banged my head on that issue for 5 straight hours - downloading new custom roms, looking for similar bootloops, ...
Maybe this information will help someone
FrozenLord said:
Hi there,
Today I received my Xperia Tablet Z and sure enough, the first thing I did was flash a custom Rom
But my device wouldn't boot up anymore...
Basically I unlocked the bootloader via Sony's key, flashed a boot.img via fastboot and then flashed the Rom via the recovery.
All I got was a bootloop - regardless of which custom Rom I used (AOKP, Cyanogen stable, Cyanogen nightly, Cyanogen unofficial, ...)
I tried doing a factory reset but to no avail.
I manually checked for each delete / wipe option in the recovery, but the device simply would not boot further than the boot animation.
However, after some time I stumbled across a Rom that contained the TWRP recovery instead of CWM.
And this one asked me for a password when I booted.
"A password? What for?!"
Well, simply cancelling the request works.
But it seems that my whole problem had to do with that password request
As it turns out, the data partition was encrypted would not let me access it.
For some reason unknown to me, it was not wiped in CWM (some error popped up when trying to format /data).
TWRP allows for doing a format on this one ("full wipe" if my memory does not fool me) and voila - the tablet would boot!
So to sum it up:
After unlocking the tablet, there might still be an encrypted /data that can't be accessed by any custom Rom.
Wiping this /data solves the problem - and can be done via TWRP.
I just banged my head on that issue for 5 straight hours - downloading new custom roms, looking for similar bootloops, ...
Maybe this information will help someone
Click to expand...
Click to collapse
I usually just hit the thanks tab but feel I have to than you personally for this post. After hours of messing about I found this post, flashed the TWRP recovery, wiped data and was able to flash and boot my xperia..
Thank you for sharing this info..
For others searching you can get the twrp recovery in this rom http://forum.xda-developers.com/showthread.php?t=2383800
I was using the Blekota Note 4(based on Kitkat) on my i9300 when it one day suddenly it restarted on its own and went into a bootloop and heated up. So I took out the battery and tried starting it again by clearing cache and dalvik cache. But it was still stuck at bootloop. After about 3 hours, somehow it came back on its own, but all the data and settings were lost. The downloaded apps were present, but their settings were lost.
Since I would have to again set up all apps, I wanted to try a new rom, Lollipop based. I downloaded the latest RESURRECTION REMIX (5.5.7) apps and downloaded the OpenGapps micro package. But after trying a clean install, the boot loop problem was still there. I tried with a different Gapp package, from OmniRom thread (all were for Android 5.1) but still no help. Even flashing the ROM alone would be of no help. I remembered I had a similar problem after flashing Boeffla kernel and the solution in that case was flashing a new version of the kernal. I tried that also. But no help.
I changed my recovery from CWM to TWRP as someone in some thread mentioned that it could help. But still No avail. In doing a clean rom, I tried almost 3 roms, cleaned cache, system, dalvik cache and even the internal storage and tried all other combinations. BUT THE SAME BOOT LOOP PROBLEM REMAINED.
As a last resort I had to flash the original 4.3 JellyBean firmware hoping that performing a clean install from that would help. But even after that the boot loop remains. Someone please help me flash a Lollipop based rom. This thing is driving me crazy now.
There's still 1 basic procedure: flash a 3part firmware with PIT-file for repartition.
Pit files should only be considered as a last resort.
Clear data and reflash stock rom and repeat once more. I have had cases where the rom didnt fully clear on a normal single flash.
Dont let it boot to rom. Do the two data wipes from recovery only.
I wish I stole my HTC M9.
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
Hi
A couple of months ago i decided to change my battery because it was draining for nothing, before that i tried to downgrade to miui 9 and 10, and it didn't change anything, so i thought that the battery was the problem.
But even after changing the battery, i still had this drain issue, so i thought " Miui 11 and kernel?" , so i downgraded again, flashed the optimusdrunk kernel and nothing !
So this morning i decided to tried another rom, the pixel experience, i didn't wanted to do that in the first place because i wanted to keep features such as native call recorder or screen recorder. But i've rather loose thoses features if that can help with my battery issues.
I follow the steps of this tutorial : https://forum.xda-developers.com/poco-f1/development/rom-pixel-experience-t3967593
And after i wiped dalvik, cache, system, data in TWRP, flashed the rom then factory reset, the rom was succesfully installed, i booted the phone, google logo appeared quite fast, then gave me this " Enable Encryption, please wait a while blablabla" , so i wait, at least 15min , so i figured something was wrong right?
So i rebooted the phone after flashing the twrp recovery again (it always dissapeared when i flash a rom i don't know why..), boot into TWRP and i wanted to see if i did something wrong, but i realized that my sd card didn't show up, and all of my roms was not there anymore , and TWRP says that there is no space available (0mb) (because of the factory reset), so i plug my phone into my computer, but i can't transfer anything to it!!
Now i'm stuck with a phone with no system, and no ability to transfer a simple zip file to flash another rom/firmware
Is there any other way to transfer files or flash a rom with adb command ?
Does that have to do with the encyption thing ?
Cheers