Develop Bugs

is my galaxy nexus bricked?

i have a big issue with my nexus, last night i leave the phone charging, this morning i turned it on and there was a message asking me for a password to decrypt the data (i never activated that ) :S, then i went to recovery mode, tried to do a factory reset , and install the stock rom again, it said it installed it but NO, i rebooted the phone and it came back to the same 4.2.2 version i had previously installed (with all my apps on it, it is like never installed the rom) this time android did not ask for decrypt password but i got "android.media process has stopped" error (something like that) and a few seconds after that the phone rebooted itself.. at this point i decided to try odin, and i flashed a 4.1 version , odin did everything right, not error messages at all.. then the phone rebooted after finishing the installation but it came back to the same OS 4.2.2 with all my apps installed and with the same issue of android.media process has stopped blablabla, and reboot..
ive tried nexus toolkit, odin, etc.. and nothing.. it looks like it flash the files normally but then it come back to the same OS (4.2.2) with troubles.
i dont know if im wrong but it is like 4.2.2 cannot be deleted with twrp 2.3.2.1 or odin... but thats weird.. when i wipe internal storage, system, etc from TWRP it said it wiped everything, but then i reboot the phone, go to TWRP again and if i look in "install" i can see all my files. i dont know whats going on.

I dont know why you're posting the same thing in two different sections.

Relock then unlock the boot loader again. If that doesn't wipe everything you're hosed.

I'm pretty sure every version of TWRP that has been released since 2.3.1.0 has been (somewhat)broken. At least from the multiple users confirming issues of every version since then in TWRP thread... Anyways Go to the main "Team Win Recovery Project" post in the Nexus Development section and click the link to their webpage to download an older version. I personally use 2.4.1.0 without issue.
If rolling back to an older recovery doesn't solve issues, try CWM recovery. If that doesn't work either, use fastboot commands to flash the stock Google images.
Check the forum stickies in ALL of the galaxy nexus sub-forums. Everything you will need is there. Please do not use toolkits! See? It tells you success! But it was not. And now you have NO idea why. At least using fastboot if something fails it will tell you what, when, where, and why and you can relay that info and we can actually help you out more.
But I think changing recoveries will solve your problem. If not report back I'd be glad to assist you further.

RoyJ said:
I'm pretty sure every version of TWRP that has been released since 2.3.1.0 has been (somewhat)broken. At least from the multiple users confirming issues of every version since then in TWRP thread... Anyways Go to the main "Team Win Recovery Project" post in the Nexus Development section and click the link to their webpage to download an older version. I personally use 2.4.1.0 without issue.
If rolling back to an older recovery doesn't solve issues, try CWM recovery. If that doesn't work either, use fastboot commands to flash the stock Google images.
Check the forum stickies in ALL of the galaxy nexus sub-forums. Everything you will need is there. Please do not use toolkits! See? It tells you success! But it was not. And now you have NO idea why. At least using fastboot if something fails it will tell you what, when, where, and why and you can relay that info and we can actually help you out more.
But I think changing recoveries will solve your problem. If not report back I'd be glad to assist you further.
Click to expand...
Click to collapse
thanks for your answer, ill try that!

jsgraphicart said:
I dont know why you're posting the same thing in two different sections.
Click to expand...
Click to collapse
maybe because this is my only phone, i dont have warranty, i dont have money to buy another, ive tried everything i know to try to fix it and it doesn't work so at this point im a little bit desperate?

i tried using fastboot commands, and it does everything ok, i first erased system and userdata, then flashed system and userdata again, it take a while to do it, and there is not a single error in the process, but then i reboot the phone and it goes back to that damn "bigxie deodexed 4.2.2" that i installed a week ago.. for some reason it seems everytime i reboot the phone that rom and all my old files are again in the phone. (it runs the OS but it last just a few seconds before i get the android.process.media error and then an ugly reboot)
for jesus, mother theresa, allah, buddha and ganesha, help me guys!!!!

rodmc123 said:
i tried using fastboot commands, and it does everything ok, i first erased system and userdata, then flashed system and userdata again, it take a while to do it, and there is not a single error in the process, but then i reboot the phone and it goes back to that damn "bigxie deodexed 4.2.2" that i installed a week ago.. for some reason it seems everytime i reboot the phone that rom and all my old files are again in the phone. (it runs the OS but it last just a few seconds before i get the android.process.media error and then an ugly reboot)
for jesus, mother theresa, allah, buddha and ganesha, help me guys!!!!
Click to expand...
Click to collapse
If you can not change ROMs or wipe anything isn't that the sign of a bad flash partition? Its rare but can happen
Toro | Atom v9 | AK Cylon 728

Sandman-007 said:
If you can not change ROMs or wipe anything isn't that the sign of a bad flash partition? Its rare but can happen
Toro | Atom v9 | AK Cylon 728
Click to expand...
Click to collapse
and how could that be solved?

Somehow change the flash chip housing your ROM?
Posted from a Unicorn powered Nexus 4 running XDA-premium.

Ponox said:
Somehow change the flash chip housing your ROM?
Posted from a Unicorn powered Nexus 4 running XDA-premium.
Click to expand...
Click to collapse
eeh, that is not an option.
nobody can help me?
i tried to repair and to format the partition /dev/block/mmcblk0p12 using mke2fs and e2fsck but it says is apparentely in use and will not make a filesystem there, with e2fsck -b (using backup superblock) it says it cannot put a flag on the superblock blablah...
i don't know what else to do.

rodmc123 said:
eeh, that is not an option.
nobody can help me?
i tried to repair and to format the partition /dev/block/mmcblk0p12 using mke2fs and e2fsck but it says is apparentely in use and will not make a filesystem there, with e2fsck -b (using backup superblock) it says it cannot put a flag on the superblock blablah...
i don't know what else to do.
Click to expand...
Click to collapse
What happens if you install an app and reboot. Is the app still there? If not you are screwed and need a new phone
Toro | Atom v9 | AK Cylon 734

Sandman-007 said:
What happens if you install an app and reboot. Is the app still there? If not you are screwed and need a new phone
Toro | Atom v9 | AK Cylon 734
Click to expand...
Click to collapse
i cant do that, when the OS loads, it last like 5 second before it reboot itself, so i dont have time to do anything.
all i can do now is from recovery, fastboot, adb, etc.. i cant do anything inside the OS.
i think the flash memory of the phone is dead or something.. thats why it comes back always to the same state after a reboot.
for example i used adb push to send a rom to the sd card, and inside the recovery, in "install" i saw the file i just passed but i rebooted the phone, went back to recovery and the file was gone... the same if i format data, it seems it works, but i reboot and everything is there again. All changes i do in the internal memory from fastboot, adb and recovery disappear after a reboot.

rodmc123 said:
i cant do that, when the OS loads, it last like 5 second before it reboot itself, so i dont have time to do anything.
all i can do now is from recovery, fastboot, adb, etc.. i cant do anything inside the OS.
i think the flash memory of the phone is dead or something.. thats why it comes back always to the same state after a reboot.
for example i used adb push to send a rom to the sd card, and inside the recovery, in "install" i saw the file i just passed but i rebooted the phone, went back to recovery and the file was gone... the same if i format data, it seems it works, but i reboot and everything is there again. All changes i do in the internal memory from fastboot, adb and recovery disappear after a reboot.
Click to expand...
Click to collapse
Yep flash memory is done
Toro | Atom v9 | AK Cylon 734

Jeesus , how many ROMs have you flashed that you wore out the ROM chip in your phone?! It takes like 1,000 writes to kill it!
Posted from a Xylon powered Nexus 4 running XDA-premium.

Ponox said:
Jeesus , how many ROMs have you flashed that you wore out the ROM chip in your phone?! It takes like 1,000 writes to kill it!
Posted from a Xylon powered Nexus 4 running XDA-premium.
Click to expand...
Click to collapse
thats the weird thing.. i flashed in total like.. 10-15 times?? i think is not that much , because there is people here flashing their phones atleast twice per day...
anyway the phone is not totally dead, i mean i can turn it on, go to fastboot, recovery, adb works... the thing is as soon as i reboot the phone, every change i did dissapear (like wiping data, system, etc) , and the phone has again the exact same files, rom, etc.. the worst thing is that i cant even use the rom that stil loads, becase it reboots like 2 seconds after i enter my pin.
i tried everything, fastboot formating and flashing, e2fsck, mke2fs, etc..
this kind of issue should requiere a mainboard replacement i guess? is there a way to force the flash memory to work again.. like giving it an electric shock lol! i miss my nexus :crying:
this is my phone now :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rodmc123 said:
thats the weird thing.. i flashed in total like.. 10-15 times?? i think is not that much , because there is people here flashing their phones atleast twice per day...
anyway the phone is not totally dead, i mean i can turn it on, go to fastboot, recovery, adb works... the thing is as soon as i reboot the phone, every change i did dissapear (like wiping data, system, etc) , and the phone has again the exact same files, rom, etc.. the worst thing is that i cant even use the rom that stil loads, becase it reboots like 2 seconds after i enter my pin.
i tried everything, fastboot formating and flashing, e2fsck, mke2fs, etc..
this kind of issue should requiere a mainboard replacement i guess? is there a way to force the flash memory to work again.. like giving it an electric shock lol! i miss my nexus :crying:
this is my phone now :crying:
Click to expand...
Click to collapse
Eh, its been a while since the last post, but when running e2fsck, did you make sure /data was unmounted before running terminal?

desktopfusion said:
Eh, its been a while since the last post, but when running e2fsck, did you make sure /data was unmounted before running terminal?
Click to expand...
Click to collapse
yep

Try this:
http://forum.xda-developers.com/showthread.php?p=25775981
Sent from my Galaxy Nexus using xda app-developers app

[ROM][4.3.1][December 3] Slim Bean jfltetmo [stable 2.2]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
The Real Dark Slim
Notification drawer & lockscreen Shortcuts
SlimPIE
Customizable NavBar
QuickSettings custom Shortcuts
Full hardware key rebinding!
SlimCenter
..and much more!
Need to find a feature? Want to see screenshots? Check out SlimBean's features!
Changelog
Find our latest Changelog go here
Chat with the slim team and other slim users
IRC: #slimusers @ freenode
New to IRC? Don't have a native app? Try the Freenode web client [link] or the Firefox extension Chatzilla [link]
Google+ [link]
Twitter [link]
Facebook [Link]
Installation instructions
For Most Users
Please keep in mind if a special instruction is needed it will be noted in the Changelog
Download the latest build from [here]
Gapps ( if you don't have it already) from [here]
!Recommended! Full wipe, and manual format /system
Flash ROM and the gapps you want, reboot
FAQ
Check out out FAQ before posting! Keeps more common questions answered in one place!
To get root working go to Settings/Developer options/
Then change the option "root access" to "apps and adb".
Help us out!
If you want to help us by translating slim to your language check out Crowdin.net and submite your translations.
Or consider a donation.
Thanks!
You can find the full list of credits here
Source
Please visit here for the rom source code.
Kernel source can be found here
XDA:DevDB Information
Slim Bean jfltetmo [stable 2.2], a ROM for the T-Mobile Samsung Galaxy S 4
Contributors
blk_jack
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2013-12-03
Created 2013-08-18
Last Updated 2013-12-08

SlimBean 4.3 stable 2.2
Stable 2.2 is live! Please read the Changelog for more details including proper upgrade/installation methods, as well as notes on activating root and restoring with Titanium Backup.
Changes, Features & Fixes:
Changelog for stable 2.2
SuperUser security fixes
Several BT fixes
Selinux security ehancements
LID control fix
some translation upstrem
nearly all device got device and kernel updates

Please note these builds are under heavy development!
Known issues
Headset in-call mic uses phone
HDR Camera mode may need improvements, but should at least work
4.3 mini-FAQ
Q) I'm stuck at the boot logo and/or a boot loop!
A) Make sure you use TWRP 2.5.0.2. TWRP 2.6 and other recoveries can cause boot loops & hangups
Q) Root doesn't work!
A) From a clean build you need to enable root access for Superuser itself. This is different from 4.2.2 in which Superuser by default had root access on a new install. To do this, go to Settings -> Developer options -> Root access. If an app attempts to request root access before Superuser itself has access, it may cause problems with that app in the future where root requests are silently denied.
Q) Titanium Backup isn't restoring apps!
A) Change the backups folder to storage/emulated/legacy.
If you use Philz recovery 5.10.0 you must upgrade to 5.11.0 or you will lose radio!
Since the SGS4 is so new, development is happening very rapidly. This should be taken into consideration when flashing any 4.3 AOSP-based builds on the device. Known issues will be listed here.

I can't seem to get past the bootloop. rebooting repeatedly doesn't seem to do anything. if I go back to recovery, it won't even let me wipe. can't mount data. I have to go back and factory reset, then reboot into recovery to get wiping to work again. then I can get back to the o.s.

quickquest88 said:
I can't seem to get past the bootloop. rebooting repeatedly doesn't seem to do anything. if I go back to recovery, it won't even let me wipe. can't mount data. I have to go back and factory reset, then reboot into recovery to get wiping to work again. then I can get back to the o.s.
Click to expand...
Click to collapse
Something is definitely wrong on your end. You're gonna have to give me more info, like your recovery and what steps you did to install the ROM.
If it's stuck at the boot logo, try wiping dalvik cache.
Sent from my SGH-I337M using Tapatalk 4

I guess wasn't as clear as I thought. i can get the system to boot once, but trying a reboot, it will bootloop.
I'm using the latest twrp, wipe everything but extsd, format system, install 4.3 and 4.3 gapps. I can get it to boot and everything looks good from there. however, if I reboot, it gets stuck in the bootloop. pulling battery or long press power to turn off and boot again doesn't help. I can get to recovery, but if I try to wipe cache and dalvik, it says something about cant mount /data and says it failed. then I have to go back to format system. after I do that, the text on screen says I may have to reboot recovery to access /data. then I can get it to boot again. of course I have to reinstall all of my apps again.
if I do anything that requires a reboot, it will start to bootloop again, and I have to format system to get /data to mount.

quickquest88 said:
I guess wasn't as clear as I thought. i can get the system to boot once, but trying a reboot, it will bootloop.
I'm using the latest twrp, wipe everything but extsd, format system, install 4.3 and 4.3 gapps. I can get it to boot and everything looks good from there. however, if I reboot, it gets stuck in the bootloop. pulling battery or long press power to turn off and boot again doesn't help. I can get to recovery, but if I try to wipe cache and dalvik, it says something about cant mount /data and says it failed. then I have to go back to format system. after I do that, the text on screen says I may have to reboot recovery to access /data. then I can get it to boot again. of course I have to reinstall all of my apps again.
if I do anything that requires a reboot, it will start to bootloop again, and I have to format system to get /data to mount.
Click to expand...
Click to collapse
The lack of /data in recovery worries me the most. That's definitely not good and I'm not sure how that would be happening.
Are you doing all this w/ your device plugged in? Can you try not plugging it in if that's the case?
EDIT: I've had an issue where sometimes on reboot w/ my device plugged in I need to wipe dalvik to continue booting. I'm not sure why this is at the moment but it's always fixed if I reboot to recovery and wipe dalvik cache.

i started not plugged in at 75% batt. I installed, activated, and installed all apps. ran titanium backup, and it said something about restoring android I'd. clicked yes, and at reboot it started to loop. tried wiping everything but system, didn't want to reinstall apps. tried to reflash zip, but failed because it couldnt mount /data.format system worked. reinstalled all apps. I thought maybe titanium backup hosed it somehow so i stayed away from it. wanted to change font with ifont. reboot looped again. wiping gave /data error again. format system worked without reflashing zip. got it running, oddly enough with the changed font.
the second format was plugged in, as at that point I was down to about 45% batt. As long as I don't reboot, everything seems good. hesitant to reboot again in case it loops.

quickquest88 said:
i started not plugged in at 75% batt. I installed, activated, and installed all apps. ran titanium backup, and it said something about restoring android I'd. clicked yes, and at reboot it started to loop. tried wiping everything but system, didn't want to reinstall apps. tried to reflash zip, but failed because it couldnt mount /data.format system worked. reinstalled all apps. I thought maybe titanium backup hosed it somehow so i stayed away from it. wanted to change font with ifont. reboot looped again. wiping gave /data error again. format system worked without reflashing zip. got it running, oddly enough with the changed font.
the second format was plugged in, as at that point I was down to about 45% batt. As long as I don't reboot, everything seems good. hesitant to reboot again in case it loops.
Click to expand...
Click to collapse
From what I'm reading there are issues w/ TWRP 2.6. Downgrade to TWRP 2.5 and your issues should go away.

I couldn't find twerp 2.5, so I installed cwm 6. now i can't get past the bootloop no matter what. I'm not getting an error about /data, but nothing, not even a format system will get the damn thing to boot to o.s.
I went through and formatted everything in the mounts menu one by one. still nothing.
I spoke too soon. now I'm getting an error when trying to format system that says cwm can't mount /data or /android.secure and /sdcard
now I seem to be soft bricked. I can't get it to go past the Samsung galaxy s4 screen. can't format.

quickquest88 said:
I couldn't find twerp 2.5, so I installed cwm 6. now i can't get past the bootloop no matter what. I'm not getting an error about /data, but nothing, not even a format system will get the damn thing to boot to o.s.
I went through and formatted everything in the mounts menu one by one. still nothing.
Click to expand...
Click to collapse
You sure you don't have a bad build?? None of my testers are having these issues. Grab it here & flash it w/ goomanager or odin/hemidall http://goo.im/devs/OpenRecovery/jfltetmo

thanks fro the link. twrp 2502 got me out of the softbrick. with cwm, nothing seemed to work to get it past the samsung screen.
twrp got me to the point that i can at least get it running again, however, not even 2502 fixes the original issue of being unable to reboot. this time after getting 4.3 installed, i rebooted at the screen asking what language. it didnt get past the samsung screen. went back into recovery and wipe/format data/yes and then reboot. that got me back into the o.s.
this is really strange, i wish i knew more about developing. as long as i dont reboot, im ok. good thing this isnt windows, or id be in trouble, hah!!

I had no problems installing with the latest regular version of CWM from ROM Manager. Got root working just by tinkering around in superuser in settings... Not sure what I did but root works. Overall very very nice for a beta release!
I have one inane question(hope I didn't miss it somewhere): is the setting for lock screen rotation removed? It seemed to me to be buggy on cm10.2 anyway. Also can't remember if the phone app rotated to landscape in 4.2.2 build, but I think it did. Again, meaningless issues really, just wondering.
Thanks for the hard and awesome work!

Loving the beta build! It's almost fully stable! All convenient features are working as should!

I wants to say Great job! Got it all set up to find the camera won't work. Give error "Can't connect to camera". I thought OK, I'll try focal. Did the same thing initially then soft bricked the phone. Had to start from scratch.
I did notice as I scrolled through app list in TB that it didn't list a camera app at all.

Bowmanspeer said:
I wants to say Great job! Got it all set up to find the camera won't work. Give error "Can't connect to camera". I thought OK, I'll try focal. Did the same thing initially then soft bricked the phone. Had to start from scratch.
I did notice as I scrolled through app list in TB that it didn't list a camera app at all.
Click to expand...
Click to collapse
It'll be under Gallery2
Sent from my SGH-I337M using Tapatalk 4

Flashed 8/20/13 using TWRP 2.5.0.2. No problem, other than some freezing apps here and there. Cleared caches, fixed permissions, and all seem fine now.
Will now run it through my battery tests, etc.
Thank you blk_jack!

I'm not sure what happened to my phone. Apparently twrp 2.6 caused some weird issue that wasn't fixed by reflashing with another recovery.
I had to Odin back to stock (freaked me out cause first Odin attempt failed, second passed, then I had to go back and format system again), and upgrade from there. Now it works like it should, rebooting and everything with oudhs.
Sent from my SGH-M919 using xda app-developers app

quickquest88 said:
I'm not sure what happened to my phone. Apparently twrp 2.6 caused some weird issue that wasn't fixed by reflashing with another recovery.
I had to Odin back to stock (freaked me out cause first Odin attempt failed, second passed, then I had to go back and format system again), and upgrade from there. Now it works like it should, rebooting and everything with oudhs.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
This is a notice for others on TWRP 2.6. Please read the OP (post 3 specifically). It has been updated to contain a mini-FAQ for 4.3 that should solve 99% of the issues I'm seeing on XDA.

Any way to get stock DPI?
Sent from my Nexus 7 using Tapatalk 4

[ROM] [Lollipop 5.0] Stock AOSP

This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!JdYCnSxZ!fn82nMs3mA0VdDBTYuguT9OXHjQtt7P9jnZUyndrtZA
if someone wants to host mirrors let me know.

Does this have the Wifi fix in it? or has Google not published that yet?

Can't wait to install this and try it. I was going to wait it out for the official release but I've broke I have to try it.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
I don't think it will be as Google haven't released the version with the patch yet as that will be the OTA or factory image versions.

ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
most likely not have not tested for any wifi bugs atm

Thank you I'm really excited about it. But I have a question. Can I have use my flash drives in this ROM without stickmount?

ROM
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??

I seem to be unable to install on my Nexus 10. I've followed the stages, but when I get to flashing the AOSP rom it stays on it forever!
I've updated my TWRP to v2.8.1.0 but it does the same thing.
Sorted the problem I think, some how the download I had on my Nexus was not a happy one haha. just on the boot logo now :3

Thank you, booted up and running. One question, I couldn't install Google+. It cannot be found on Play Store and installing from APK doesn't work neither.

Great work, thanks. Flashed about an hour ago, flawless so far!

seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.

gabegom said:
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
Click to expand...
Click to collapse
Same question here. Can we flash after any ROM or do we have to flash stock .imgs first then this?

Is anyone having problems with Wifi? I have flashed this twice and I cannot get Wifi to connect. It sees networks but won't connect to any of them.

ChaosMinionX said:
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
Click to expand...
Click to collapse
internal storage is working here

Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?

chowynatt said:
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
Click to expand...
Click to collapse
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.

tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Did you manage to install Google+?

kejar31 said:
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!lVYHAAjI!-478q0a5v6QAL9-6bDNzo7utJ1AXZD539CpTP6R63w8
if someone wants to host mirrors let me know.
Click to expand...
Click to collapse
So far so good! I'm in the setup... it's taking a long time checking my wifi connection.
edit:changing to 5ghz did the trick
edit2: after passing setup, changing back to 2.4ghz works just fine.

tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Yeah all working now, took forever to boot, went black a few times and then started working.

Now the $64,000 Question: will it root?
because I've had my fun with it. And without root, I can't keep it. I doubt it can be, but I have to hope.

Flashed yesterday. My experience was as follow:
1) Dirty flash from PA, system erase command did t seem to work. After flashing it booted up all apps were there, 4.4 gapps were force closing.
2) Twrp advance factory reset and erase. normal flash afterwards with gapps 5.0. Setup wizard crash. Couldn't get past that error.
3) Factory 4.4 image. Complete erase, and flash to L, boot up and then TWRP and gapps flash. Tablet booted correctly and works since then.
Regarding the WiFi battery drain bug:
No issue here. Battery drain when idle is a flat line. No misc group with excessive battery is listed in the battery stats.
Further more performance is great, basic apps seem to work correctly. Haven't gotten much into detail.
Regarding the G+ question. It works fine.

How to install cyanogenmod on HTC One M8?

Hi,
I searched online for 2 hours but I see a lot of mixed, outdated articles, videos. For example Hasoon's app link doesn't work, or the cyanogenmod installer link for your phone is giving me 404.
I don't want to do something stupid so can someone tell me or show me a guide on how to install this?
My phone is from Rogers (contract ended). I just want a fast and light weight android without bloatware and nice features.
Will I have to find a cyanogenmod release from someone who use Rogers, or can you use the same build on that's built for M8 regardless of your phone company?
Thanks a lot.

Have you done anything to the phone yet (unlock bootloader, s-off, root, etc.) or still just fully stock?
Is the phone currently on Lollipop? You'll want updated hboot to run current CM12.1.
Don't bother with toolkits and the like. The toolkits haven't been updated in over a year, contain obsolete files, and that will cause you more problems than anything. The steps are not that hard to do "manually", and that is a much better learning process. The toolkits shortcut that learning process; putting you in a position to get into a jam, with no knowledge of how to get out of it.

Thanks a lot for replying. I unlocked the bootloader, s is off, but I don't know how to root. I think it's superSU right? If so, I assume I will do this by installing this zip after I flash the cyan mod?
I downloaded these to my phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I assume I just have to format/adv format everything and install these zip files using TWRP, right? If so, that wasn't hard
But I have another problem. I don't have an SD card or OTG cable to store these zip files outside the phone. I have usb flash memory/stick, HDDs but AFAIK I need OTG cable to use them with my phone.
Also another thing that concerns me is the new Android version is coming next week, right? So should I wait for it and use that cyan mod?
Are you able to get OTA updates with cyan as easily without having to flash your phone every time?
Thanks again

lachdanan said:
Thanks a lot for replying. I unlocked the bootloader, s is off, but I don't know how to root. I think it's superSU right? If so, I assume I will do this by installing this zip after I flash the cyan mod?
Click to expand...
Click to collapse
No need to flash SuperSU to root after flashing CM.
Go into Developer's Options in phone's settings (may need to tap version number 7 times to make Dev Options appear) then turn on root there.
lachdanan said:
I assume I just have to format/adv format everything and install these zip files using TWRP, right? If so, that wasn't hard
Click to expand...
Click to collapse
Before doing anything, make a TWRP backup of your current (presumably stock Sense) ROM.
Then backup any user data you want to keep, by method of your choice (Titanium Backup, cloud, copy to PC, etc).
Then do a wipe. I would only recommend the default Wipe option (user data, cache and Dalvik) in TWRP. Right in TWRP, it says "most of the time, this is the only wipe you will need" (or words close to that effect) and it says that for good reason.
You certainly don't want to wipe "everything". If you wipe internal storage, you will lose the TWRP backup I just told you to make. Plus you will wipe the ROM and gapps zips you are going to flash, if you put them on internal storage.
Some folks swear by wiping system when flashing ROMs. I don't like this, since if for some reason the ROM fails to flash, you are then stuck with no OS (although you will have a TWRP backup, that I just told you to make). If you run into problems, you can always wipe system later and flash again. But honestly, after many ROM flashes on several different devices, and I've never once had to wipe system, that I recall. Unless of course the ROM instructions require to wipe system. If that is the case, follow the instructions.
After default wipe, flash the ROM, and flash gapps. Then reboot.
lachdanan said:
But I have another problem. I don't have an SD card or OTG cable to store these zip files outside the phone. I have usb flash memory/stick, HDDs but AFAIK I need OTG cable to use them with my phone.
Click to expand...
Click to collapse
I don't follow what the problem is. It looks like you have the files on a PC. Just connect your phone by USB, then copy and past the files to the phone's internal storage.
Don't know why you want to store the files "outside the phone" (and not on the PC) unless you are talking about wiping internal storage. Again, it isn't necessary to do that.
lachdanan said:
Also another thing that concerns me is the new Android version is coming next week, right? So should I wait for it and use that cyan mod?
Click to expand...
Click to collapse
It usually takes a bit of time for a new Android version to be ported over to a respective device. Than a bit more time, for it to be fairly stable. So its up to you, but I say why wait. You can always flash again when CM13 (or whatever its going to be called) is released on the M8.
One of the things about flashing ROMs, is it can be addictive. So if you have the urge and time to do it now, just do it!
lachdanan said:
Are you able to get OTA updates with cyan as easily without having to flash your phone every time?
Click to expand...
Click to collapse
I actually don't use CM on the M8, so check the CM thread for any discussion on this.
Even if OTA updates aren't functional (no idea if they are or not), you can often download and "dirty flash" new updates (like nightlies). Dirty flash, means you just wipe cache and Dalvik and flash the ROM, keeping user data. Its very fast, since you don't need to setup the phone again.
Although, sometimes a dirty flash won't work, and you need to do a full flash. When CM13 comes out, you will probably need to do a full wipe before flashing it. And likewise, you probably won't want to do an OTA update to CM13 either.

Thanks a lot man, you cleared many of my questions. Regarding the storage, sorry they are already on my phone, so the phone has internal storage and another separate storage? I thought HTC One M8 had a single storage inside so if you delete things, everything is deleted.
But since you said don't delete system, then this is not an issue?
Also by system, does it mean actual stock android system files? Won't these files conflict with CM's own system files? Or if they are bloated with time, usage etc, then this will leave these unnecessary files behind?
Thanks again

lachdanan said:
Regarding the storage, sorry they are already on my phone, so the phone has internal storage and another separate storage? I thought HTC One M8 had a single storage inside so if you delete things, everything is deleted.
Click to expand...
Click to collapse
Nope, the storage is actually partitioned into something like 41 separate partitions: system, hboot, recovery, radio, data, boot, and (of course) many more.
So when you say you want to wipe "everything" I said you don't want to do this, and I really mean it.
Plus, one of the Advanced wipe options in TWRP is the removable SD, which most folks will not want wiped, most of the time.
So again, use the default wipe option in TWRP. Only pick the Advanced options, if you know exactly what you are doing, and fully understand the result of wiping that selection.
The "default" TWRP wipe just wipes user data, cache and Dalvik. Internal storage (which is data/media) is actually not touched, and that is most likely where you placed the ROM and gapps files (plus its the default location for TWRP backups, Titanium Backup and some other things).
lachdanan said:
But since you said don't delete system, then this is not an issue?
Click to expand...
Click to collapse
Correct.
lachdanan said:
Also by system, does it mean actual stock android system files?
Click to expand...
Click to collapse
If you are still on the stock ROM (haven't flashed any ROM yet, was I assume is the case) then YES, system partition is where the actual stock ROM (stock Android system files) are currently located.
lachdanan said:
Won't these files conflict with CM's own system files? Or if they are bloated with time, usage etc, then this will leave these unnecessary files behind?
Click to expand...
Click to collapse
Nope, when a ROM is successfully flashed, it will wipe system, then install the new ROM on the system partition.
This is another reason why I say its not necessary to manually wipe system in TWRP. It will happen anyway when you flash the ROM. But if for some reason the ROM fails to flash (not unheard of, for various reasons), you will still have have a working phone if you didn't wipe system.

Thanks. I made a stupid mistake before reading your last post, now it seems like my phone's data storage is completely empty I restarted into bootloader and added TWRP to it again using Windows. But then I chose restart on that bootloader menu and now the phone screen is stuck in HTC android boot screen. I couldn't turn the phone off or restart. Do you know how to fix this?

I managed to fix it and now I am in cyan Looks really good, I will be customizing it now but it feels snappy
Thanks again man

sd card and gapps6 problem on cm13

i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?

Linx78 said:
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Click to expand...
Click to collapse
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.

dladz said:
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
Click to expand...
Click to collapse
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.

Linx78 said:
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Click to expand...
Click to collapse
Ask in the forum mate, where u got the rom from.

dladz said:
Ask in the forum mate, where u got the rom from.
Click to expand...
Click to collapse
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...

Linx78 said:
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Click to expand...
Click to collapse
You will have to have downloaded the rom from xda surely? The Rom you downloaded initially I assume was cm 12.1, then you updated to cm 13, that thread is in the original android development section, I'm sure you can find your way there as you've been there before. The thread is now called cm13 I believe..
Also make sure you're on the latest TWRP recovery, I'm guessing you are but it'd be nice to be sure.
Might also be worth downloading G apps from the cm13 thread then rebooting to recovery, flashing the rom again and installing gapps whilst once complete, don't allow a reboot.
Wiping cache and dalvic will be fine, don't perform a full wipe just incase you can't install the rom again.
If you get stuck, you can push files to your phone using recovery and the push command..
Not 100% but I think storage works via TWRP, could be wrong about that and I've not tested it with cm13.
Either way you have a way back..
---------- Post added at 06:55 PM ---------- Previous post was at 06:55 PM ----------
Install from your internal memory not your SD card. Get the necessary files on your internal memory instead.

thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted

Linx78 said:
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Click to expand...
Click to collapse
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...

Linx78 said:
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Click to expand...
Click to collapse
No it'a not bricked..
Are you installing from internal or external memory?
Connect your phone to your computer and go to recovery, then mount storage in recovery, copy G apps to internal memory.
Make more posts in here, i think you need ten

I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.

Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.

dladz said:
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
Click to expand...
Click to collapse
sorry, i did copy everything onto internall memory, still no luck...
also the cm13 updated the recovery aswell, and i can't even do a factory reset...
please is there a way to go back to cm12.1?
once again i can't install anything in recovery mode.

Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.

dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
that wasn't my post, some else posted here too...
i'm stuck, adb won't install anything too

LLegion said:
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Click to expand...
Click to collapse
i wanted to ask how to go back to cm12.1 from cm13?
i don't have any backups, nor my recovery is allowing to install anything as per post above...
adb method is not working either, just says waiting for the device when rebooted to download and nothing else.
also my firmware is 2.10..... is that an issue?

dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens

Linx78 said:
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Click to expand...
Click to collapse
Nah i'm on 2.10 that's fine.
At this point it appear to be an issue with CM13 rather than anything else, I'm not up to speed with Android 6.0 so I think it would be best if you asked in the thread, you've made over 10 posts now so i'm assuming you can post there.
See what they say, let them know what you've done so far, someone will have either been through it or will know what to do.
Sorry i can't be of more help mate.
PS: Just thought of something, if you have connectivity to your computer / laptop, update your recovery if you haven't already, chances are it's an issue with cm13 but might be worth a try.

I had similar problem - Google Services crashing after unintentional update to CM13.
I realized that I need to install new GApps to fix the issue but GApps installation in recovery was constantly failing.
I used to have some recovery there, I even don't know which one, but during update to CM13 the recovery has been changed to some kind of CM recovery.
After installing TPRW recovery (ir forked for me from the TPRW Manager App from play store) I was able to install Nano GApps.
It solved the issue with Google Services crashing, now I got some Wizard crashing. The issue with crashing wizard is solved by going to privacy setting and allowing the wizard all rights. Later I realized that many other applications were crashing on start as well. I solved it for each of them by uninstalling and installing from Play Store again.