Need serious help with a zte blade l2 - General Questions and Answers

I Had CM12.1 installed on it and everything went fine until it ran out of battery. Then So far it started by having random resets and freezing up until it basically started freezing and turning off and on without going further than the ZTE logo the weird freeze ups affected it even on recovery mode so it wasnt soemthing from the ROM only.
I've had a terrible pain with it, i tried flashing different roms, tried wiping data, chache, dalvik. etc. I've format flashed the stock rom with sp flash tools so many times and even managed to get my sd formatted (thank god i had all backed up) and still no use. Recovery mode isn't affected anymore by the wierd freeze ups, but i can't enter the OS at all. I have CWM on it right now.
It's still doing the same thing, tried using a backup i made before all of this happen and still no go.
Anyone can help me out with this? THanks in advance.

Related

Please help: unusual bootloop/CWM error

Hi
I installed Thiaz ROM and the ICS theme which there is a link to on his V2.4 page. All was running fine and dandy for a day. I installed all of my programs, apps, etc, and used App2SD to move some of them to the SD. Each time I did this, it said 'failed' the first time and then allowed them to be moved on the next. I rebooted the phone a couple of times and never had any problems. After I had got things set up as I wanted them, I rebooted into CWM and did a new backup. I then rebooted and went into bootloop.
Cleared data, dalvik and even battery stats. Tried fixing permissions. Nothing worked at all, still boot loop. Did a factory reset and restored the backup and still bootloops.
If I restore to the original backup from when I first put on the ROM (no ICS theme), it works OK. Then after a few hours and after I have turned on and off successfully a few times, I get the old bootloop again. I have not messed around with any system files, etc. One time it was after I moved a file with File Expert but I uninstalled that programme and haven't used since.
Any help or suggestions would be very gratefully received as I don't really want to go back to the stock V21a but I can't be doing with setting up everything on my phone from scratch every day either!
I hope someone can help me.

[Q] CM10 Reboot leads to Stuck on Boot

I've seen a few other threads from people with similar issues, however most of them this happened after flashing CM10 or similar.
My phones been running perfectly fine on the 1/7 CM10 nightly with Rohan's B7 kernel. Actually haven't flashed anything in a fair while. Tonight I was about to go to sleep so I plugged my phone in since it was around 15%, then went to reboot it like I usually do. However it got stuck on the CM10 spinning boot screen. Now I think I might've had this happen a few days ago, but I recall that I rebooted into TWRP (bootloader and recovery both load fine), wiped both caches and it booted normally. This time however I tried such and still got stuck. I tried a couple more times, as well as tried to reflash the CyanDelta CM10 file and kernel (no wiping except caches), all with the same result.
Any ideas? I figure a factory reset will probably fix things, but I would REALLY like to save data if at all possible (stupid me for not doing backups in a bit). Also what could be causing this? As far as I know my phone's been running great and I haven't even flashed in awhile. Any help is greatly appreciated, thanks.

[Q] Bricked for no apparent reason

I rooted my phone back in December and have been using it without problems since then. I've rebooted it tons of time, haven't installed anything unusual or tried to modify anything. I just followed the normal instructions for rooting and flashing a custom rom. Today, I rebooted my phone and now it's hanging at the Galaxy SIII logo screen. Taking out the battery didn't help. I have no idea why it would do this out of the blue. What are my options for fixing this? Can I recover my data?
blueintegral said:
I rooted my phone back in December and have been using it without problems since then. I've rebooted it tons of time, haven't installed anything unusual or tried to modify anything. I just followed the normal instructions for rooting and flashing a custom rom. Today, I rebooted my phone and now it's hanging at the Galaxy SIII logo screen. Taking out the battery didn't help. I have no idea why it would do this out of the blue. What are my options for fixing this? Can I recover my data?
Click to expand...
Click to collapse
Should be easy to fix. Common issue.
Try booting into recovery. If you can then clear cache and dalvik. Try rebooting then.
If that doesn't work try re flashing the rom,
If you can't reboot into recovery but can get into download mode then you can easily fix it at the cost of losing all your data.
Let me know how it turns out.
At this point, my phone is just one big tweak.
Wiping the caches didn't work, so I ended up having to reflash the rom. Everything seems to be back to normal now though, thanks!

Stuck in a loop, need help

Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden
Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app
I know I should, but I didnt. Is it still fixable ?
*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.
Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app
Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden

Stuck in the bootloop :(

I noticed One+ was a bit slow so I decided first to switch from power save to balanced and it was still going slow so I decided to do a reboot. After the reboot the phone got stuck at the boot animation. I can get into recovery tried a factory reset didnt help. Im wondering if i try flashing the OS if that would work. Plus what would be the best way to do so.
What ROM, Kernel are you using?
Switching from Power Save to Balanced shouldn't cause your phone to be stuck in a boot loop. Something else caused it.
Everything is stock, it was really weird I was considering maybe using adb to flash a stock img (although i have little experience doing that). I tried rebooting again to potentially start this process (this is after a good 5 or 6 reboots and a factory reset) and it started up to the welcome screen. Another side issue it seems like the factory resets for this device only wipe the apps + user data. I know if I was rooted i wouldnt expect the media to be wiped but its stock with the stock rom. I bought it off ebay and when i went to load my stuff i did a factory reset and noticed the previous owners data including call/text logs and contacts were all on the device
mrfantastic said:
Everything is stock, it was really weird I was considering maybe using adb to flash a stock img (although i have little experience doing that). I tried rebooting again to potentially start this process (this is after a good 5 or 6 reboots and a factory reset) and it started up to the welcome screen. Another side issue it seems like the factory resets for this device only wipe the apps + user data. I know if I was rooted i wouldnt expect the media to be wiped but its stock with the stock rom. I bought it off ebay and when i went to load my stuff i did a factory reset and noticed the previous owners data including call/text logs and contacts were all on the device
Click to expand...
Click to collapse
If you were to flash a stock image, it would be done in fastboot mode and not adb mode. So is your phone booting yet?
You can always adb sideload a custom ROM and flash that to get your phone to a bootable state again.
The phone booted up after a good 3 hours a factory reset and multiple reboots

Categories

Resources