Hello...
I'm new to all of this rooting, installing and so( used to do this years ago on my LG KP500 Cookie ), so I'm not sure what to look/search for when I'm in this "bad" spot.
I used my sony xperia SP, but I did not like the current version of android it was, as it was lagging, hanging and other weird stuff, so I've decided to try and install the "lollipop" version. Since the guide I followed was detailed, I got it all working perfectly fine, until I tried to install gapps. After installing them, my phone started crashing / hanging on booting, which kept kicking it back to "SONY" screen, and from there it's just an endless loop.
so I tried to wipe and use backup that I had saved, so I could try and reinstall the ROM. It ended up at where I can't do anything anymore. I start my phone - "SONY" screen and nothing else. Can't access the CWM recovery, it doesn't progress anywhere, just sits there.
I'm lost. I don't know what to do Please help ;~;
Digital Noodle said:
Hello...
I'm new to all of this rooting, installing and so( used to do this years ago on my LG KP500 Cookie ), so I'm not sure what to look/search for when I'm in this "bad" spot.
I used my sony xperia SP, but I did not like the current version of android it was, as it was lagging, hanging and other weird stuff, so I've decided to try and install the "lollipop" version. Since the guide I followed was detailed, I got it all working perfectly fine, until I tried to install gapps. After installing them, my phone started crashing / hanging on booting, which kept kicking it back to "SONY" screen, and from there it's just an endless loop.
so I tried to wipe and use backup that I had saved, so I could try and reinstall the ROM. It ended up at where I can't do anything anymore. I start my phone - "SONY" screen and nothing else. Can't access the CWM recovery, it doesn't progress anywhere, just sits there.
I'm lost. I don't know what to do Please help ;~;
Click to expand...
Click to collapse
it's ok...please try to flash t-kernel v2.2 twrp via fastboot mode ...thread link
need further help? ...quote this post and i'll replay ....but always do some searching then ask
good luck :good:
Related
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.
Everything worked fine for almost a whole year, then my tablet started acting strange last night. It got really bad this morning so i was trying to install a antivirus thinking that might help, but it wouldn't open. Reports of program failures were popping up like crazy, so i turned it off and back on about five minutes later. Now its been over an hour and its stuck in the cyanodenmod loading screen, its never taken this long.
Is there any program i can use on my laptop to wipe everything on my tablet and install another os? I'm not sure how it'd work seeing as how its stuck loading. Do i need to let the battery die? I really just want to plug it in and wipe the whole thing but i haven't a clue where to start.
Please help?
I took the back off and unhooked the colorful wire thing from it to turn it off, and put it back. It restarted fine and now I'm attempting to wipe everything on it. When i first pushed the erase all button it didn't do anything, then after trying a few more times it restarted to a "teamwin" something (have no idea what that is) and it restarted again, so far its back on the cyanogenmod loading loop again. (I'm a little amazed i even managed to root it in the first place, considering i didn't know what "os" stood for before that. I really need help with stuff like this.)
If i can get it back to the normal screen, is there any program i can use to reformat everything and like an alternative to cyanogenmod for the program?
Which CyanogenMod version are you running ? The teamwin that you saw when it booted up was the recovery you flashed to install custom ROMs like CyanogenMod. Make sure you have the latest recovery before anything . take a look here and let me know when your up to date and we can put you device back in working form
http://forum.xda-developers.com/showthread.php?t=2218796
So I recently tried updating MIUI v5 to MIUI v6. However, I stupidly opted for the FOTA update, rather than updating using recovery.
After running the update, my phone rebooted and it worked fine, MIUI v6 running great. However, because I'd updated using the in-built updater, my data and apps were still there from before. This was causing no-end of 'process stopped running' alerts, which drove me crazy after around 10 minutes.
Therefore, I decided to try and wipe my data. I went to the recovery menu and found that MIUI had installed its own Chinese recovery, my previous TeamWin one was gone. So I fumbled around and managed to find the 'Wipe data' etc. option, and chose it. I was presented with a couple more options which I didn't understand, and (stupidly) accepted both. This left me with a phone that would no longer boot past the 'Sony' logo. I was also unable to access the Chinese recovery menu.
Feeling a little worried at this point, I started to Google around for guides on how to flash a recovery back onto a phone stuck in a boot loop. After hours of searching, I decided it wasn't possible and instead follow a guide for fixing 'boot loops' through flashing an original Sony 'ftf' firmware using flashtool.
Now, the guide I was following was quite old, and provided a link to 'C6903_14.2.A.0.290_Global LTE' - so this is what I used to flash (which I'm now regretting). Before flashing, I was presented with some options, for which the guide I was following recommended I deselect the 'kernel' option. So I did this too.
After around 10-15 minutes and what seemed like a successful flash, I tried turning the phone on. This time, the Sony logo appears, then disappears to a black screen, and then the backlight turns off, followed by the Sony logo, then a black screen, then backlight turning off, etc. So slightly different behaviour to before, but still boot looping.
I think what may have happened is that MIUI includes an updated kernel, and through flashing the 14.2.A.0.290 firmware without a kernel, I've introduced some sort of incompatibility.
The problem I'm having now is getting another firmware onto the phone in order to resolve this. For some reason, despite flashtool recognising the phone being plugged in with flash mode, it refuses to load the firmware - I'm instead presented with the message:
"You must have the according fsc script to flash this device."
Does anyone know how I might be able to get around this? I admit to being a bit of a noob when it comes to flashing so have probably dug my own hole here, and seem to have left myself completely unable to work out what I need to do in order to get back out! Any help would be hugely appreciated.
Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!
langauld said:
Please see the attached screenshot of what I see when I try flashing with flashtool. The whole flash takes around 2 seconds, so it appears as though nothing's actually happening. However, it did flash successfully before, only without the kernel (which I think is what's causing my problems).
Please help!
Click to expand...
Click to collapse
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)
Just2Cause said:
This version of Flashtool you're using is known to require some files for your device to be able to work.
Try using the version before it.
Oh and NEVER:
- Wipe /system and /data using recovery with unlocked bootloader (it will remove everything and the phone will not be able to boot).
- Flash an ftf of a older android version (like flashing kitkat on top of lollipop) without including kernel because that will cause a bootloop. (not sure about flashing lollipop on top of kitkat but I think it's the same)
Click to expand...
Click to collapse
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.
langauld said:
You sir, are a god amongst men. I'd never have thought to try the previous version of FlashTool. From reading around, I knew some devices had issues with it, but because it lists the Z1 as being 'supported', I didn't think that would apply to me.
I flashed again without deselecting the kernel and it booted first time. Thank you again.
Click to expand...
Click to collapse
Glad I could help.
I wanted to try and hopefully learn little about rooting. Have been reading forumposts and tutorials for hours before I started.
Then I got this problem that I have been trying to solve for hours. But my conclusion is I need help solving it.
Tested on this phone that just were collecting dust.
Samsung Galaxy S5 Mini (SM-G800F) and I think it was running 4.4.2. (this is all I remember off the top of my head)
Problem / What happend (long version):
Rooted phone. Downloaded SuperSU and Flashify and installed TWRP 3.0.0 (http://forum.xda-developers.com/galaxy-s5-mini/orig-development/recovery-twrp-3-0-0-t3313775). I had no SD-card so I skipped doing a backup. Everything worked fine (for a normal user). Downladed a Root Uninstaller app also Debloater-setup-v3.90.exe (http://forum.xda-developers.com/devdb/project/dl/?id=12623). Did not freeze or uninstall anything before checking in this forum that it was OK. But after a while I could not access my homescreen it just turned up blank but I could still use other functions/apps. Rebooted the phone in order to get it to work but got stuck at the bootscreen. Tried to fix it via TWRP but the program freezes after a while or just reboots the phone back into Samsung bootscreen.
Problem / What happend (short version):
Rooted - got Flashify and SuperSU
TWRP 3.0.0 installed (no backup made)
Debloater-setup-v3.90.exe and some Root Uninstaller app used (searched on this forum before doing any changes)
Homescreen just blank, other functions/apps worked
Rebooted the phone and got stuck at Samsung bootscreen
TWRP access but the program freezes/reboot after short time
I did try "Factory reset". But the screen froze and the phone slowly started to heat up.
Later on I searched about it and it might have something to do with KNOX?
Any solution is fine since I don't have anything thats need to be saved. I can try any working stock/custom ROM (just not sure how to get it into the phone, yet).
Yes I am a novice so the simplest thing might even work.
Have you tried to flash stock ROM for your device using Odin? If it fails you may want to check this:
http://forum.xda-developers.com/galaxy-s5-mini/help/g800f-failed-odin-firmware-upgrade-fail-t3131782
If it doesn't fix your phone you may have a hardware problem.
Hello all before I describe my issue lemme tell you how I got there.
First of all, new phone, couldn't install pixelexperience and flashing stock android was being a pain with all methods (read not working), only managed to install stock android with pitch black recovery.
After a while it auto updated to android 9 and I started having wifi issues that people told me were android's fault so I waited for an update. Update came but android was unable to install it, giving errors after errors every time it downloaded the update.
My solution to all of this was to flash another rom, either stock or custom, and pray it works. It was scheduled to happen in 2 days, when I had free time.
Today, when trying to change the permission for a text file for an app from read only to write, some random process crashed, and it triggered a crashing cascade, including the settings app, homescreen launcher, etc until the phone restarted and got stuck in TWRP logo screen.
No key press, combination, resets, etc would fix it. So I got into fastboot and tried a few things with no luck. Flash stock rom again and phone seemed to be working.
Magisk manager couldn't install magisk and root the phone so I went into stock recovery/twrp and every time I did it I got a black screen message saying something like this:
"Your phone/system is corrupt and won't boot ever again *evil laugh*. Oh btw, go to this link in another device to cry more"
and the link redirects to a google page with some non-useful info.
So here I am, unable to root, unable to go into recovery, phone boots though. I force-stoped updates for a while, as android 9 wifi issues were terrible, and I don't know how to proceed.
Do I flash a stock image again, a custom one, try another rooting method?
I don't want to brick a 6month old phone, really sucks.
Btw, is there a reliable way to back up everything in the phone ?(not only google stuff, but app configs and files/folders) Long time ago I read something about Titanium backup but never looked into it further and now with this crash that lost me everything I wanna prepare for the future.
Thanks for all the help and for reading my boring story.
Even I am facing same problem.. In my case my phone is rooted and I cnt flash TWRP and I cnt get into fastboot mode.. I alwys endup with black screen..