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 ?
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.
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
zhuang281 said:
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
Click to expand...
Click to collapse
Did you try to put the update on the external sd card? Not sure if that would make a difference but i remember i used to put it there...
You could also flash a custom recovery and flash the update that way. You can find more info in this thread:
http://forum.xda-developers.com/showthread.php?t=2636093
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
To unlock with Asus unlock tool make sure Google 2 Step verification is disabled.
Then I used fastboot to flash CWM recovery from a computer. I think you flash with fastboot from the newly unlocked bootloader. Power + Vol DOWN.
After you have flash recovery then you can enter it. No scary man lying down.
YayYouFixedIt said:
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
Click to expand...
Click to collapse
I forgot to mention one thing at the start. I don't actually have on hand a external microSD card. Which I think might be why placing the zip file in the root of the internal storage did not work.
Should it work? Is there any way to get around it? I've been trying to use sideload with cwm (finally got cwm working), but it comes up with "failed to write data protocol fault no status"
EDIT: Through cwm, I chose "choose zip from /sdcard" then select the "0" file directory then i found my zip at the location. I selected it and confirmed install. However, it then comes up with "Error in data/media/0/(name of update here).zip status 6"
Thanks for the help so far but anyone have an idea about this?
Not sure. After googling I see this
http://forum.xda-developers.com/showthread.php?t=1535546
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
You can put the zips anywhere when your recovery is installed.
Okay so I finally managed to get the custom rom installed and working. However, this did not fix my problem with the touchscreen. I think it is because it only changed the firmware but not the android version (still 4.3).
Is there any place I could find android 4.2.2 rom? This was the one the tablet was on before the update that screwed everything up. If I could downgrade to that version, it may work again.
Thanks
I gave up and just put on the android 4.3 ota from droidbasement. Now the tablet randomly restarts and is stick in reboot loop. It wont even allow me to boot into cwm recovery to delete the cache. But i accept that I now have a $600 piece of **** on my hands. Going to bed. Night.
Ya i dont like the whole void your warranty for "using it" idea. If it responds to fastboot you might be ok.
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Alta1r said:
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Click to expand...
Click to collapse
I tried that before but it stated "update aborted" immediately after i pressed confirm, in CWM.
But all that is in the past now. I am pretty sure that the tablet is hard bricked since it no longer even opens bootloader. I accidentally pressed the wipe data option and I read that irreversibly damages the tablet. When I hold pwr+vl down, nothing happens anymore, it keeps on its reboot loop.
So since I didn't read anything of xposed being "BAD" for the new CM beta, i figured i'd give it a shot.
The current gist is this:
Powers on, can't get into TWRP, if I get into the Download Mode and go to "Send_Command.exe \\.\COM4" and do "#id" it just comes back with "#" or it may take a long time, then it'll just come back with "#". Fastboot devices, shows nothing. ADB Devices same thing. I'd love to do a HardReset, or anything that could be done, but the only button config that works is Pressing Up when plugging the phone in.
Any ideas?
Yes I've seen others are having bootloops, noone seems to be having them due to what I've done (xposed + CM).
UPDATE: Problem solved. http://forum.xda-developers.com/showpost.php?p=63674157&postcount=3
Got a bit further thanks (i'll probably regret that word) to the LG Flash Tool.
Followed the instructions, flashed the KDZ, then I guess the flash tool error'd out because the Download Mode still showed 0% but the tool had a **** ton of ????? ??????
Needless to say, TWRP is booting up now!....but "unable to mount '/system'.
Attempted the H81110N Bootstack and Image, but that didn't work. due to the /system.
Retrying again with the LGTool, this time choosing English -_-
Looks like im at 52%, that error message i received i guess should have ben ignored.
\
Edit: wasn't looking good with LGTool crashing. but I've successfully gotten the phone back to stock it looks like. Just going through some reboots. I did get a glimpse of the LG setup screen
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page1
You are booting into recovery. I think when the android is laying down you hold power and press the volume up key. You will probably have to restore the backup of the file you changed (you did back it up right?).
If that doesn't work, you will most likely have to flash your system partition with the stock one and root again.
Red_81 said:
You are booting into recovery. I think when the android is laying down you hold power and press the volume up key. You will probably have to restore the backup of the file you changed (you did back it up right?).
If that doesn't work, you will most likely have to flash your system partition with the stock one and root again.
Click to expand...
Click to collapse
Ill try flashing the stock one, see if it works, thank you
Dear friends , I will be as accurate as I can.
I rooted my Hisense C20 with Kingoroot. When I tried to erase the apps that came with it I noticed that I couldn't get rid of Kinguser app.......or so I thought I could.....
I downloaded then SuperSume Pro , and while it was running and saying that it was deleting Kingroot artifacts, it stopped working. When I tried to reboot the phone so the app could run again , the phone remained frozen on the logo screen without giving me access to any order, not even power off.
1. I managed to access recovery menu by pressing power key-volume down,
2. I tried ''wipe data-factory reset'' and ''wipe cache partition'' ,
3. reboot system, but nothing happened.
4. Taking a shot , I pressed ok button to ''apply update from ADB'' choise and it answered ''now send the package you want to apply with adb sideload''....
I have read so many new for me articles the last two days and I value a great respect for all those to make them work!!!
My phone is Hisense C20 with Android 5.1.1 and product no. C20FE-1 and it was? rooted. It has an Alcatel ADB Interface. I downloaded on my PC the Alcatel ADB Interface , Adroid SDK and Hisense C20FE_1 official (it said..) ROM.
Could PLEASE so much and respectfully someone tell me if there is a proper and detailed way to bring back my phone using what I have , or anything else more proper for the job?? Am I in the right way? It is the first time I even read about these procedures....
I would respect so much if someone who is sure about it would take his time to give me an advice or even better a detailed and in his simplest English path step-by-step to the solution.
Except the ''paint it blue and drop it in the sea'' one...... :laugh:
THANK YOU all in advance. Yannis