Showing posts with label think. Show all posts
Showing posts with label think. Show all posts

Thursday, 15 October 2015

Think my M7 is about to bite the dust



Yesterday I noticed my phone hot and noticed the screen was bulging trying to separate from the phone body. I placed in my apt AC vent and most of the swelling went down. So figure time for a new phone but not going with HTC this time. I have had HTC since the droid incredible and figure time for a change.

My question to you is go for the galaxy S6 edge or the Verizon nexus 6. I am looking for a good camera and sorry HTC has let me down on many of the previous phones I owned. I will keep my old M7 as still workable but that just in case as don't want to be without a phone. This had been a great community with many great ROMs except that darn Google one that my phone seemed to not like as it would only send one text and no more lol.

So guess this is kinda farewell but never posted much in here lol. So let's see what all you guys and gals suggest. Not looking for a note as it has to fit in my works shirt pocket lol. Less chance of breaking there than in my pants pockets.

Sent from my Nexus 9 using XDA Free mobile app



Saturday, 10 October 2015

Soft Bricked I think after trying to update Roms.



I was on Color OS 2.1.3

Decided I wanted to try a 5.1.1 custom rom.

Ununified back to default. Installed TWRP and created a backup.

Wiped installed Paranoid Android 5.1.1 this seemed to be working fine untill.
Couldn't copy new files onto the SD card (So could not add Gapps)
Got the 'Could not connect to camera' error.

So then I tried to install Omni 5.1.1 Although no I can't

Copy Files.
Restore the backed up Coloros

I do have color os 1.2.7 and 2.1.3 on external SD although then I use TWRP to install these I starts up and then just gets stuck in a reboot loop.

Anyone got a suggestion of how I can hard rest my phone back to color os?

Thanks!



I think my phone is bricked(kinda?)



I have a HTC One M8 Unlocked and I haven't been able to use the phone for a couple days because I think I bricked it. First I unlocked my bootloader (successful) and then I rooted my phone (I assume it went successful) and after that I ran the ViperOneM8 4.6.1 rom. I was in a hurry so I did not read that you were supposed to update your firmware before installing the rom. I ****ed up and installed the rom and I was left with a phone that couldn't connect to wifi. I tried to fix the problem but I think I just made it worse and now I don't know what to do. Any help/links would be greatly appreciated thank you!

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA4****06572
(bootloader) imei: 35871*****09708
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0



Friday, 9 October 2015

I think bootloader is not working



I have HTC Inspire 4G rooted. I rooted it with this method that first I moved the following zip file in root of sd card and then I turn off phone. By pressing Power button + Volume down, hboot (S-OFF) was shown and it automatically updated the stock bootloader and recovery. This is link to the zip file. The recovery is ClockworkMod v5.8.1.5 (with touch)...
and currently this ROM is installed

Yesterday my phone got little wet from the back side as I accidentally placed it on water. The water hardly get inside it. I picked it and cleaned it with tissue. The phone then turned off and from that time, I'm having this problem.
1. When I press power button, the phone vibrates 3 times and the orange notification light starts blinking but no display.
2. When I try to boot the bootloader by pressing Power + Volume down buttons, the phone vibrates 5 times and the yellow notification light is constantly shown (No blinking)

When I first updated bootloader and recovery, I noticed that when I turn off my phone and connect it to charger, CWM recovery is booted. So I tried this method and now I can boot into recovery. I had the custom xperia ROM zip file in sd card that my phone was using, I first backed up current ROM and data from recovery, wiped Dalvik cache and Battery stats, formated /system, /data and /cache,,,, and installed the ROM again. Same problem with bootloader.
I then wiped Dalvik cache and Battery stats, formated /system, /data and /cache and tried booting bootloader and ROM, same problem...



I don't know what to think about lags



Hi guys,
just got my moto x play here, and after one day I'm confused about lags I'm experiencing. Until 2 days ago I was thinking that if a phone lags, it lags in everything it does (at least if it's a heavy thing), but this phone is...strange! I have lags in feedly (just a simply rss feed app), but no in heavy games like asphalt. I really don't know what to think. Same thing on the launcher side: no lags on nova or google launcher, lags on action launcher 3.
It seems like an app-related problem, but these apps run smoothly on my older phone..is this a bad system optimization by Motorola..? I think that it's not a chipset related problem, cause many heavy apps runs smooth and many others, less heavier, not. Correct me if I'm wrong.
Anyone can help me to understand this..? I'm trying to understand if in future upgrades Motorola will be able to fix this or if it's hardware related and I have to live with it.

side note: feedly really has heavy lags (expecially in the side menu). Anyone else that uses feedly can confirm this..?



Installing update stuck in a loop - I think



Morning all.

I got an OTA update available notification on my wife's phone and started the update. Its been well over 1.5 hours and it seems to keep repeating the "installing update" step in a loop.

I thought I check here for suggestions before I rebooted the phone. Anyone faced similar situation? Note the phone is unrooted.

A Google search didn't find anything similar.



Thursday, 8 October 2015

M919 "might" be getting official 5.1.1 according to this site. What do you guy think?



I've been searching around for news about M919 and lollipop. This website some time ago mentioned it being possible but nothing remotely concrete. Now, however, it has given some more promising details.

http://www.vcpost.com/articles/96721...-galaxy-s4.htm

What do you guys think? Or has anyone else found something more reliable?



I think I may have "killed" my HTC (Specifics in the thread)



Ok, so I'm very new to using bootloading and fast boot and all of the other developer tools, and I seemed to have killed my HTC.

I downloaded the rashr flash tool with the hope of being able to install the CyanogenMod rom to my HTC One X. Using the rashr flash app, I selected the option that allows you to flash a kernel on your phone, and I selected the img file that I downloaded which was the latest nightly img. Afterward I went into the command prompt and typed in adb reboot bootloader. From there I haven't gotten any response from my phone at all. The screen doesn't turn on, the small light indicator hasn't lit up at all, and I know the batter is close to fully charged, but there's nothing happening. Did I kill my phone? Can anyone help me out with this problem?

Not entirely sure if the phone is brand new, but my uncle bought it for me, he said it was unlocked, though I'm assuming he meant SIM unlocked because when I was able to get to the boot menu, it showed that it was still locked at the top. It had all of the packaging contents and the screen protector - so it's "like new"

The only clue I have to there still being some sort of "life" in this phone is this weird device that shows up in the device manager under "Other Devices". It says "QHSUSB_DLOAD", but no information can be pulled up about it

I hope my story is detailed enough, I can elaborate more if need be. Please go easy on me, I'm a nub but I want to learn this stuff xD.



Wednesday, 7 October 2015

HELP - Think ive bricked my Nexus 6



I had a stock Nexus 6 onto which I loaded the MarshMallow previews.
I then decided to go back to 5.1.1 on the basis of the final release using the following:

fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img

Once I had entered the final fastboot command I also stupidly entered the command to lock the bootloader prior to rebooting

Some thing went wrong and now the phone sits on the google (while letters on black background) screen on bootup.

What are my options? I can access the bootloader, but its not showing up as a device on the on "adb devices"

Any assistance would be appreciated.



I do not think the V1 chromecast is updateable thru the HTTP Post request.



I tried it and it's not picking up any updates.



Freak i think i bricked my N6



I don't know much when it comes to this stuff but my phone was acting up and i went into recovery and went to wipe cache partation. When i did that the wipe cache failed. i rebooted my phone and its been on the boot animation the 4 little dots floating around for the last 30 mins.

and this shows up for the log

E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_kmsg
E:Can't open /cache/recovery/last_kmsg

I'm not sure what to do or how to fix this but i do know there is a way to do it on here.



Do you think Devs can make Nexus 6P and 5X Quick charge 2.0 compatible?



They have the right chips. I read the actual quick charge 2.0 will charge faster than the fast charge the phones come with. But then I thought, since the chips are there, would some simple mods make this work?