Related
I upgraded my Note 4 OTA yesterday and it appears to be working fine. But there is one thing I would like to find out if others have experienced. Since the update, when I boot into recovery mode I get the following message; "installing system update." This stays on the screen for about 15 seconds and then disappears and is replaced by "No command". Then I am presented with the usual recovery mode menu. Does anyone else get these results when booting into recovery mode since doing the update? Does anyone know how to make it stop this behavior? It doesn't appear to be causing any practical problems as I can still access everything you normally could in recovery mode, I just have to wait a little longer to get in. Any info is appreciated. Phone is not rooted.
--Burbank Jim
Same thing happening to me. I'm sure it's nothing.
Hello everyone,
first of all thanks for your amazing work and all the stuff you provide. I was a silent reader for a long time, but now my phone is trolling that much, I cannot fix it on my own/with the guides I found here.
I do have an HTC One M7, rooted (superuser) and S-OFF (revone) with Androidd Revolution HD 71.1. I used to update my ROM every month, but I got stuck after the last update. My recovery was TWRP as CWM did not work properly when I rooted my phone.
My issues as a list:
- cannot enter recovery anymore
- cannot connect via USB (tried every port)
- screen turning randomly black on homescreen and sometimes in apps (but they usually work), screen does work, but i cannot see a thing
- since today graphical issues after a reboot (flickering screen, parts of the screen get duplicated)
Since the last update I cannot enter recovery anymore. Getting in bootloader is no problem but i get stuck in the "entering recovery...." screen. It does not move, tested it for some hours. I tried updating the recovery (-), trying to flash stock recovery and reflashing custom (-), trying cwm (-).
After I tried cwm i noticed that it didnt overwrite the recovery but i got both. cwm and twrp, but i cannot delete one of them (didn' work before either). I can start TWRP oder CWM on a booted phone, but updating both bugs and I can't enter recovery with these tools too.
Today I wanted to try again on my own, but my phone won't connect on USB. Tried every port on my computer with and without USB-Debugging. I will try on a other computer, but I could not do this until now. Additionaly I want to wait for some ideas of fixing, as I think "my" trys are not going to work suddenly .
Screen started to turn black a few days ago. Dont know why but I think it could be a software issue. but i cannot update (see above ). When i try to turn my screen on it often just turns instantly black. soft keys are enlightend and it does work (more or less). if i success in sliding down the service bar on the top, i can start my alarm clock app and from there use the soft keys to get in other started apps. From there it works most of the time. Sometimes i need a couple of trys, sometimes it just works as its intended without turning black and sometimes i need several minutes to succeed.
Cannot say more as I did to the graphical issues. Just had them once until I started an app (screen worked). could not reproduce this error.
I would prefer a solution without wiping, but if necessary i will ofc.
Thanks in advance for your help, as I am rather helpless right now.
I attached a photo of the bootloader.
Yours Laexxi
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 ?
Hi, I've recently bought a Samsung Note 9, secondhand, yet still new condition. Courier dropped the delivery and I was impressed with what I received, unboxing through to switching it on. Awesome display, features, speed, etc.. unfortunately, it didn't last long. Went through the initial setup, google acc, personal preferences, up to the point where security features needed to be activated. As I wanted to enroll fingerprints, it asked for passkey before biometrics could be recorded. I entered a 5 digit code, again to confirm, and then it was set. Then the trouble started. Phone locked by pressing the power button then refused to unlock with the passcode that I've just saved. After a while of trying to enter the key I've used, as well as some alternative combinations for in case I've made a mistake (twice?), I've resorted to boot into recovery mode by switching off the device and pressing bixby+vol up+pwr. Booted into recovery, chose factory reset and let it run.
It finished in less than a second, before I chose to reboot device. Only to see the screen stay dark with red words top left corner of screen: Only official firmware to be installed something something. And that's what I kept on getting, did abovementioned step again, same issue, tried formatting cache, same issue, tried lacking storage boot, same issue, tried flashing custom rom via Odin, same issue, tried to find official firmware and installed that same issue. I've noticed that none of the packages I try to install works due to an error stating that Signature Verification Failed. Every time, whether I try sideloading via adb, updating via sdcard or flashing with Odin, I get the same result. Last try was flashing the bootloader with an recovery zip I found somewhere and now it just bootloops the Samsung Galaxy Note 9 startup screen, vibrates, restarts and same screen again. Even if I let it loop, it keeps on forever. I can still access bootloader, recovery and Download mode with pressing the button combinations, but nothing I try of the options available resolves the problem.
I'm really at a point where I don't know what to do or try, please advise. Here's some additional info that might help:
Samsung Galaxy Note 9 SM-N960F Crownlte.
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSI3
After a few of my flashing attempts, abovementioned line now reads:
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSF9
Its the Exynos version of the Note 9. Any direction or help will be much appreciated.
Thanx
Sdejager2 said:
Hi, I've recently bought a Samsung Note 9, secondhand, yet still new condition. Courier dropped the delivery and I was impressed with what I received, unboxing through to switching it on. Awesome display, features, speed, etc.. unfortunately, it didn't last long. Went through the initial setup, google acc, personal preferences, up to the point where security features needed to be activated. As I wanted to enroll fingerprints, it asked for passkey before biometrics could be recorded. I entered a 5 digit code, again to confirm, and then it was set. Then the trouble started. Phone locked by pressing the power button then refused to unlock with the passcode that I've just saved. After a while of trying to enter the key I've used, as well as some alternative combinations for in case I've made a mistake (twice?), I've resorted to boot into recovery mode by switching off the device and pressing bixby+vol up+pwr. Booted into recovery, chose factory reset and let it run.
It finished in less than a second, before I chose to reboot device. Only to see the screen stay dark with red words top left corner of screen: Only official firmware to be installed something something. And that's what I kept on getting, did abovementioned step again, same issue, tried formatting cache, same issue, tried lacking storage boot, same issue, tried flashing custom rom via Odin, same issue, tried to find official firmware and installed that same issue. I've noticed that none of the packages I try to install works due to an error stating that Signature Verification Failed. Every time, whether I try sideloading via adb, updating via sdcard or flashing with Odin, I get the same result. Last try was flashing the bootloader with an recovery zip I found somewhere and now it just bootloops the Samsung Galaxy Note 9 startup screen, vibrates, restarts and same screen again. Even if I let it loop, it keeps on forever. I can still access bootloader, recovery and Download mode with pressing the button combinations, but nothing I try of the options available resolves the problem.
I'm really at a point where I don't know what to do or try, please advise. Here's some additional info that might help:
Samsung Galaxy Note 9 SM-N960F Crownlte.
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSI3
After a few of my flashing attempts, abovementioned line now reads:
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSF9
Its the Exynos version of the Note 9. Any direction or help will be much appreciated.
Thanx
Click to expand...
Click to collapse
1. Install official stock rom from sammobile from this link (doesn't matter which you download):
https://www.sammobile.com/samsung/galaxy-note9/firmware/#SM-N960F
2. Load up Odin, put corresponding files to their slots, AP to AP, BL to BL, etc..
3. Boot into download mode (phone powered off, press and hol volume down + bixby button and insert cable to computer)
4. Flash it, wait for it to boot up.
Ok, I'll try that today and hopefully my next reply will be me posting from the Note. Let's hold thumbs.
Thanx
How did you solve the problem.. Same here.. Stuck at bootloop
Am unable enter in to download mode.. Tried hundreds of times
Minzlife said:
Am unable enter in to download mode.. Tried hundreds of times
Click to expand...
Click to collapse
try this
Plug your phone to pc
Hold power button + volume down for a few seconds
Then right before the phone logo shows, bixby + volume down
Now download mode shows. Flash stock rom
I upgraded my Moto X4 from LineageOS 16 to the latest 18.1 build by following these instructions. When I rebooted, the phone was stuck on the boot screen with the green circles. I installed the latest version of TWRP and reinstalled the 18.1 image. Sometimes the phone stay in the loop, but usually it was get the the home screen.
However, it still doesn't work. Sometimes the phone reboots shortly after arriving on the home screen. Sometimes it has WiFi turned off and is on airplane mode. In that case, it seems stable until I turn either of those on, and then it reboots. Running an app might also cause it to reboot. The touchpad buttons at the bottom of the phone also become unresponsive.
I tried installing the latest LineageOS 17.1 build, and that just stays in the boot loop too.
Like a first rate noob, I didn't make a backup of the v16 installation before the upgrade. I have a backup of the OEM rom that I made in 2019, when I first put LineageOS on the phone, but I'm worried about erasing my data.
I appreciate all suggestions. One thing I considered doing, but have not figured out how to do, is to look through the logs to find out what is making the phone reboot from the home screen. "adb logcat" might be the answer.
Another question I have: Does each "slot" have its own recovery? I think that's the case, and I think I have the newest TWRP in both slots.
kalbfled said:
I upgraded my Moto X4 from LineageOS 16 to the latest 18.1 build by following these instructions. When I rebooted, the phone was stuck on the boot screen with the green circles. I installed the latest version of TWRP and reinstalled the 18.1 image. Sometimes the phone stay in the loop, but usually it was get the the home screen.
However, it still doesn't work. Sometimes the phone reboots shortly after arriving on the home screen. Sometimes it has WiFi turned off and is on airplane mode. In that case, it seems stable until I turn either of those on, and then it reboots. Running an app might also cause it to reboot. The touchpad buttons at the bottom of the phone also become unresponsive.
I tried installing the latest LineageOS 17.1 build, and that just stays in the boot loop too.
Like a first rate noob, I didn't make a backup of the v16 installation before the upgrade. I have a backup of the OEM rom that I made in 2019, when I first put LineageOS on the phone, but I'm worried about erasing my data.
I appreciate all suggestions. One thing I considered doing, but have not figured out how to do, is to look through the logs to find out what is making the phone reboot from the home screen. "adb logcat" might be the answer.
Another question I have: Does each "slot" have its own recovery? I think that's the case, and I think I have the newest TWRP in both slots.
Click to expand...
Click to collapse
Hello,
I have come here from.
Actually upgrading from an older Android to newer Android is almost never very smooth, and hence should be avoided if possible, but if you have done so and currently experiencing boot or device operation problems, then:
1: Open TWRP, and go to 'Wipe'.
2: check ONLY 'cache' and "Dalvik / ART Cache", and uncheck the rest, then proceed by swiping the trigger which reads "Swipe to Wipe".
3: Wait for 3 seconds.
4: Reboot to system.
5: If the system boots now, then reply with written "Solved", else the issue.
Thank you...
Thank you very much for replying. I followed your instructions for both slots on my phone, but neither shows any improvement. The 18.1 slot continues to get to the home screen and then reboot as soon as I try to do anything (or randomly before that); the 17.1 slot continues not to get past the green circles screen.
Although the Lineage website no longer hosts builds for v16, I was able to download the last signed v16 nightly build from Archive.org and to verify the signature using these instructions. I booted to TWRP sideload mode and ran `adb sideload <v16 build>`. Now that isn't working either! It seems to loop at the circles screen for a while. Then it gives me a message about being unable to boot and asks if I want to do a factory reset. I did not try a factor reset because I think that erases my data.
I resolved the issue by following the full installation instruction for Moto X4. I tried it with versions 18 and 17 first, but the rebooting problem continued. Fortunately, it worked this time when I put version 16 on the phone again.
I have version 16 on mine and I don't have the will to try to update. Migrating from version 15 to 16 the first time gave me issues and troubleshooting woes and I don't wish to repeat that process. Pie works good enough for me, F it. Just wish it would receive security updates still, but the devs are done with it.