Related
[SOLVED -- Read my last post]
Posting on forum was my last resource, but I've tried literately almost everything I can possible find.
I already bricked my phone and had to unbrick, do everything (update firmware etc) all over again.
I am at a point where I am afraid to do something new to my phone now without knowing what they are...
Please bare with me, I am not familiar with exactly what flashing is or whatnot, I just followed the instructions and got where I am....
K, recently I decided to wipe my phone CLEAN and update to new CyanogenMod 9 from factory mode.
So, I have Captivate, I897. It was ECLARE with 2.1 firmware.
I have updated to 2.3.5 (Gingerbread [I897UCKJ2]), Rooted.
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
I installed Clockwork mod (Free version).
My goal is to install CyanogenMod 9, and part of the process requires me to enter the CMW Recovery Mod.
I dont even know what this looks like, but all I know is whenever I boot my phone, after the AT&T logo animation it seems to go into this "messed up" screen, where as if my phone is broken. Stays there for 3 seconds and then continues to boot back to its OS.
In ROM manager, it says Flash ClockworkMod Recovery (You must have the clockworkmod recovery installed to flash and restore ROMs!)
Another option within ROM manager is, Reboot into Recovery (Boot into Recovery mode for manual management.), which if I do access it, it takes me back to that AT&T logo animation and that "messed up" screen again, but this time it stays there. Where all kinds of colored pixels are on my screen as if my screen is broken. It will only continue to boot back to my OS if I press power button or some sort.
Im guessing that's my Recovery Mod, which my phone for some reason cannot see?
So I tried "Download ROM (Upgrade to ROM Manager (premium) to access the full list of ROMs!", hoping this may cure that messed up screen effect, which I think is the Recovery Mod for all I know... When I click to install, it gives me Confirm Phone Models. None are my phone model for me to install.. (It only gives me Google Nexus S / Google Nexus S 4G / Samsung Epic4G / Samsung GalaxyS i9000).
Earlier, I was looking at this, http://forum.xda-developers.com/showthread.php?t=1127578
which is a way to fix recovery mod(?) But I have NO idea how to even install those files... Maybe not the .tar file but the other one.
Please help? Am I the only one experiencing this kind of problem? Couldnt find anywhere else on youtube / google / forum..
Thank you VERY much in advance, really appreciate it..
-Dan.
danroh said:
I had to Flash BACK to KK4_stock_kernel.tar for me to use WIFI again because I had issue after Rooting my phone, I couldnt access the WIFI.
-Dan.
Click to expand...
Click to collapse
This is your likely problem right here. The Kernel that is installed during the rooting process and typically when you install custom roms is what is responsible for installing and therefor you being able to access the CWM recovery. Flashing back to the stock kernel likely messed things up for you.
http://forum.xda-developers.com/showthread.php?t=1300843
Now if you follow that link it will take you to several one click options for flashing your phone to stock gingerbread but with a kernel containing CWM. Also keep in mind that it is possible you could have wifi issues if you've had them in the past, but if your goal is to get to CM9 just ignore the wifi for the time it shouldn't be an isuse in the end.
Hey OP,
See this.... TRusselo's Flashing Guide
Sent from my SAMSUNG-SGH-I897 using xda premium
You need Gingerbread bootloaders.
Thanks guys! I figured out the problem and solved it!
Like you guys said, I didnt have the bootloader. The gingerbread I installed was the no bootloader version. After reinstalling to the one with bootloader, I was able to access the recovery mod and that "rainbow screen" glitch was no more.
Thank you!
Ok, I am new to these forms and kind of a noob android user so please make it as simple as possible.
So, I rooted my phone but i never have messed with roms or kernels or anything (mostly because i dont understand them) so everything is stock (gingerbread 2.6 i believe). I was following an online guide to change the boot animation via root explorer and now my phone only shows the word "android" with the shine going through it. The weird thing is, I can turn on the phone and get to the homescreen, but I am not able to see anything except the boot screen. For example, when i turn it on, I am able to turn it off by pressing power then blindly searching for the turn off button on-screen.
I have searched long and hard for a solution, but they were all caused by uploading a CWM roms that went bad, but I didnt do that. I did have it at one point just to backup my rom because everyone said that it was important. So I do have a CWM backup, but no CWM app on my phone. I am able to get to recovery mode.
Please help thanks.
Hello,
I am a noob trying to install a rom with aroma installer. But now it has been stuck at the page where it says: The installation wizard has successfully installed *********. Press next to exit.
What do i do? Power off?
Is it definitely stuck? Aroma doesn't always recognise touch events very accurately, and I usually have to tap the "next" button a few times before it registers. Failing that, if it's finished installing whatever you flashed, you should be fine to reboot manually anyway.
Yes,i have tried to push the next button many times but nothing happens. It has been like this for 30 minutes now. The successfully installed text appeared very fast, a second or two maybe after the previous screen. So if it has installed the rom, it was def a fast install.
Anyway, is it safe to try to reboot, even if it was in the middle of the install? Rebot to recovery and try again?
Well, there certainly isn't anything else to be done besides rebooting. I don't know what you were trying to install - if it was a several-hundred-MB ROM, as most things that use Aroma are, you would expect it to take a while. Smaller things can be flashed very quickly. If it _did_ go wrong somewhere, there are a few things:
1. What recovery, and what version thereof, are you using?
2. Did you wipe data before using the installer?
3. Most of all, what were you trying to install? There might be some known issue with certain configurations.
I wouldn't necessarily expect a working OS when you reboot, depending on what you were trying to install and how badly things went wrong, but you should be able to get back into recovery easily enough.
Thank you for your quick reply.
1. I use the CWM recovery in this http://forum.xda-developers.com/showthread.php?t=1914394 thread, not the newest, but 5.5 something i believe.
2. Yes, wiped all data + dalvik.
3. I was trying to install rXTREME on my SGS III lte i9305.
I've rebooted now, and everything works perfect as the phone was before i tried to do the install. No brick. I also tried to flash it one more time, but stuck at the same place again. Rebooted fine at stock rom again. Maybe i should take this as a hint that someone else should be put at the steering wheel.. :laugh:
EDIT: forgot link above
Found out what the problem was.
In Aroma Installer i selected EFS backup both times. The third time i tried i did not do this. And everything went fine. Runs smooth.
my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?
jehad.drarjeh said:
my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?
Click to expand...
Click to collapse
This is I9305 forum is this your phone ??
This thread is about Aroma installer is that your problem ???
Suggest you read the basic faqs and guides first looks like from your post you are either flashing wrong rom to your phone or have hijacked a thread in the wrong forum ./
jje
Q&A for Computerfreek274_Turbo_lollipop_1.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Computerfreek274_Turbo_lollipop_1.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks!
I appreciate all your hard work to make it possible for the Turbo community to enjoy root and lillipop!
Flashing android symbol after 1.0 image.
Ive been using your images since day 1, followed the instructions and I cannot get into recovery to clear cache or do a wipe.
Ive done everything twice including running all the fastboot commands prior.
CF.lumen
First of all, thank you very much for the 5.1 image! So far everything seems to be working perfectly.
Now on to my question:
Would it be possible at all to get full CF.lumen functionality?
Installing the drivers requires write access so it can't be done the normal way, but I wonder if it's possible to (manually) install the drivers in a custom image before flashing.
I don't have any experience with making custom images but I am willing to figure out how to do it if that's what it takes to get CF.lumen.
I just want to know if it's possible or not. (though a version of your image with CF.lumen installed would be even better of course)
Cheers
I am able to get to the recovery menu, but it says "no command" on it. Thought it might have been a bad recovery flash, so I redid it in fastboot. Same thing happened. Should I mofo back to 4.4.4? Can I do this without a seperate recovery.img?
drizzzzzz said:
I am able to get to the recovery menu, but it says "no command" on it. Thought it might have been a bad recovery flash, so I redid it in fastboot. Same thing happened. Should I mofo back to 4.4.4? Can I do this without a seperate recovery.img?
Click to expand...
Click to collapse
At the android logo, enter recovery menu by holding power and pressing volume up.
Before it was hold volume up for 10 seconds then press power.
Oh crap.
I RSD'd to stock to prep for a fresh install of this and accidentally selected the 5.1 file instead of kitkat. FAIL.
Well, I hope there is a new exploit :/
Mobile Hotspot
Will the Mobile Hotspot be enabled with this image?
I did a full wipe before flashing and advanced calling still won't enable, just force closes every time. Is there any known solution to this that I haven't seen?
Need help
So I followed install to a T - got the flashing Android in Recovery so I could not get into Wipe Cache so I started and phone got stuck on Android logo - I got back into recovery mode and got to wiping cache and it says wiping cache. . . Formating /cache . . . how long should take? If I cannot get phone to boot do I do a clean wipe and start over?
Bluetooth connectivity issues with Smartlock on ChromeOS
So I am currently partially rooted with mofo and running Computerfreek274_Turbo_lollipop_1.0. Among the computers I own, I have a chromebook pixel, in which I love the fast booting portion. In the settings on the laptop, there is an option to turn on SmartLock (phone unlocks computer when nearby), but it requires a phone with Lollipop 5.0 or above installed. Knowing I installed the lollipop build as mentioned above, I tried to connect my phone to the SmartLock function. I kept getting the message stating the computer could see my phone, but it needed to be Android 5.0 or above. First question I have is aren't we supposedly on 5.1, since I loaded the lollipop build above? Or did part of the installation process get missed, since we only fastboot loaded specific portions of the new build? According to the about phone section in settings, we are on 5.1.
In addition to this, I opted to see if I could just connect the phone straight to the computer bluetooth signal. Again, both devices could see each other fine, but when going to pair the two together, the process failed everytime. I have not been able to connect the phone to my computer yet. So the main question I have is if the bluetooth functionality has been broken in this build or if it is not working right. I did clear all of the data/cache for the bluetooth application before trying the second time, but that didn't help. Does anyone else have issues connecting to a computer, connecting to the smartlock feature, or troubles with bluetooth in general?
Thanks ahead of time.
Does it work in the Brazilian Maxx is taking installing the modem command line?
excuse my bad english hehe
Can't get past the android with the red triangle
Every time I flash the .img file with mofo, I keep getting a android with a red triangle. What am I doing wrong?
I have wiped and trying to upgrade to B from 1.0, it has completely stopped a few times, goes right back to C prompt. Highest it's gone has been 45%. Any suggestions? 1.0 was running fine before.
Sent from my Nexus 7 using Tapatalk
Need help loading computerfreek274 turbo lollipop.
I'm having problem loading computerfrek274turbo image using mofo, everytime I load the image on my phone it fails to boot, I keep getting the android with the red triangle, can someone please tell what i'm doing wrong? Thanks
Stuck on Motorola boot logo
I cleared my cache and tried to flash back to 4.4, I cant get past the M at boot. I tried to flash back to 5.1 and it still wont boot.
I'm on 1.0 and trying to replace the stock Google emojis with the Apple ones. In Kit Kat, this was relatively easy by either replacing NotoColorEmoji.ttf in /system/fonts/ with the Apple Emojis, or modifying the fallback_fonts.xml file in /system/etc/. I'm trying to use the same Apple emoji file (found here) or the updated Apple Emojis (from here) and I get black boxes instead of emojis. I have verified that permissions are correct.
Is there anything else that needs to be changed to make those alternate emojis work? I know the first Apple emoji file works because I used it in the Computerfreek274 KK ROM. Has something changed with how 5.1 handles fonts?
Moto Display
I can't seem to get the moto display fix to work for the 493 DPI version. I got the xposed update (version 65), downloaded app settings, changed it to 640 DPI, hit save, but it still doesn't work. Then, when I go back into app settings and look at moto display, it's been reset to 0.
Not sure what to do from here. I'm also having a hard time getting adaway to stick. The ad blocking that was in computerfreek's kitkat root worked amazing, but now I'm not able to get this working. I've tried adblock plus, adaway, and unbelovedhosts and none of them seem to be working.
It doesn't seem to be a problem with xposed, because amplify is working fine and xposed isn't giving any errors on the framework page.
Any ideas?
computerfreek274 said:
I was off xda for only a few hours and there like 2 or 3 pages added on here
One more time on recovery and I just tested it.
When you see the dead Android guy! Stop and hold on for 10 seconds or so. Then hold VOL up keep holding it then just tap power key as you are still holding the power key! Do all this very as low between steps like hold VOL up for 3 or so seconds the tap power. I do this and get into recovery every time and always the 1st time. There is no other ways we all have the same recovery after you flash the new one.
Please even if you have already updated you phone and it is all set please go test this way out. If it works please hit thanks on this post. I have 12 pm's asking hot to do this. I am getting burned out guys and as most of you know I am also sick. So please I am sorry I can not respond to all the post in the last hours. I hope you guys that where having trouble I hope you guys got it working. I have updated 6 phones my self 1st time on each phone and and my phone has been flashed so many times I lost count after 30.
Thank you guys for all your support. I am very grateful to all of you.
Click to expand...
Click to collapse
I don't know if or how this varies between other people's Turbos, but I too was having trouble getting into recovery, and I found that what worked for me is when I have the android logo with "No Command", I first press and hold POWER and then press VOL UP while still holding POWER. I only press POWER for less than a second before pressing VOL UP.
I don't know if this has already been mentioned, but it looked like all of the guides and answers I've read suggest pressing VOL UP first then POWER. Pressing POWER first then VOL UP is the only way it has worked for me, and so far it works every time. I hope that helps.
home button lollipop problem
Thanks for your hard working .. But now after I update to Lollipop 1.0B >> the home button is not working its only vibrating when I press it without redirecting to the main home menu >> I tried to flash many times but the same error >> is this common ?? any help or suggestion please ?
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..