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

Need to flash my phone, but have a question...

So here's the scenario. Hopefully I don't leave anything pertinent out...
Galaxy S3 w/Sprint. Phone is rooted but has the stock ROM on it. The phone doesn't need to be rooted, but I figured something like wifi tether might come in handy at some point. I rooted it such a long time ago I honestly don't remember how I did it. However, the screenshots of the Odin program look somewhat familiar so I'm guessing it was something with that.
When I boot into recovery mode, it says CWM-based recovery v5.5.0.4 and has the standard CWM menu.
This, of course, means I can't get the OTA update that came out a few months back.
So, in order to get the stupid prompt to stop bugging me to update, I need to flash the phone with something. I'd be fine using an updated version of the Stock ROM, or would be happy to put something like CM10 on there. I don't want anything experimental so I'd go with the stable version.
This leads me to three questions.
1) What would you recommend as far as a ROM to flash when comparing stock vs CM vs whatever else. I'm fine with the stock feature set and stability is the top priority.
2) When I flash whatever ROM I flash, how much of the phone needs to be wiped? All the apps will have to be reinstalled, but does it also have to wipe things like photos and such?
3) How do I do the flash? All of the tutorials I see assume you're starting with an unrooted phone, which I'm not. Do I just copy the ROM Zip file over, do one of the wipes and then do the install from zip? I'm just looking for the basic steps to follow since I"m already rooted and have a recovery already there.
THANKS for any help so I can finally get this straightened out!!!

1.It depends on your likings. Play with different ROMs.
2.Just a wipe before to flash the ROM.No need to wipe photos and videos.
3.Yep.Put the ROM on your SD card,wipe your phone and then flash it.
Hope that helps
Sent from my GT-I9300 using xda app-developers app

kelemvor33 said:
This leads me to three questions.
1) What would you recommend as far as a ROM to flash when comparing stock vs CM vs whatever else. I'm fine with the stock feature set and stability is the top priority.
2) When I flash whatever ROM I flash, how much of the phone needs to be wiped? All the apps will have to be reinstalled, but does it also have to wipe things like photos and such?
3) How do I do the flash? All of the tutorials I see assume you're starting with an unrooted phone, which I'm not. Do I just copy the ROM Zip file over, do one of the wipes and then do the install from zip? I'm just looking for the basic steps to follow since I"m already rooted and have a recovery already there.
THANKS for any help so I can finally get this straightened out!!!
Click to expand...
Click to collapse
1) The standard answer is: try them all out and see if you like one or the other. But I'll be nice and also say that if you're looking for something stable, I'd recommend The People's ROM. It's a TW-based ROM with a lot of customization, but it's very stable and has a large user base. They're always willing to help someone out (as long as you search before asking).
2) It really depends what you're flashing. I always recommend what I call a "so fresh, so clean-clean flash," which means wiping /data, wiping /system, and cache and dalvik cache. You won't lose your photos, but you will lose all apps and their associated data (save games, etc). The reason I recommend wiping system (which others might not suggest), is that different ROMs have different mods associated with them, and as an end-user of the ROM, you have no idea if your previous ROM is leaving behind files in /system that won't play nicely with your new ROM. So I typically wipe system as well as data and the caches.
3) You're in luck. I have a previous post that explains #3 is pretty good detail. Since you have verified that you have CWM, you can skip the first section where I talk about that. I have quoted it below:
kay131108 said:
ok..can u pls be a little more specific..i if i press the three buttons with volume down is just an android in download mode..so what do i do next?...clockworkmodrecovery
Click to expand...
Click to collapse
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
And lastly, you don't have to lose all your apps. You can use Titanium Backup (TiBu) to restore your apps. You just have to be careful not to restore any system apps, as they tend to not play well between Roms. I have quoted my previous post about TiBu down below so you can review some features/warning about TiBu.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"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"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Click to expand...
Click to collapse

[Q] on 4.3 but dont have a knox counter. HELP!

So I have a Sprint Galaxy Note II... I'm all jumbled up, i did a load of work on it way back and just now read about the knox counter... i got a lil worried and checked to see what mine was... there was NO COUNTER and both of my entries said CUSTOM and my flash count is 4...
I'm Confused cause i cant get my wifi to turn on ATALL and my white back has paint cracks, so i was gonna take it in to sprint... how am i supposed to do that? i have the knox apps on my phone, but no knox counter in odin mode. i know i can root my phone and reset my flash counter and set my phone back up to stock roms and settings... I've attached a picture and odin details to depict this problem. if someone could give me the best solution here, should i take my phone in or keep it seeing as it does not have knox... also, as far as i know i don't have root accesses atm. but every time i boot my phone it says SU permissions has stopped working. when i updated it did it through the sprint network so it was an official rom. i didn't get a choice it just happened one night when i was sleeping. i had 4.2 rooted with custom recovery (e3) and i still have that custom recovery. please help me XDA Forum users.. your my only hope.
{
"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"
}
--------------------------------------------------------------------
ODIN MODE
CUSTOM BINARY DOWNLOAD: (4 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
---------------------------------------------------------------------
these are the only listings in odin mode.

Well first of all DO NOT take your phone to the Sprint store the way it is. It's pretty obvious that somehow your phone was able to download and install an OTA on top of your already rooted phone. It sounds like you're gonna have to put your phone back to factory ROM no matter what because you're phone is now pretty messed up and you want to take it in to get it swapped. I see no other choice but to odin your phone back to stock.

Install and flash billards back to stock un root, with counter reset, you won't have any issues..

It's not broken, just flaws to its pretty white look. I would never take it in the way it is. I DO NOT WANT A KNOX COUNTER IF AT ALL POSSIBLE! I just need my wifi working. Can I flash back to 4.2? If so could I get a link to a step by step tutorial? Thanks for the reply guys.
Sent from my SPH-L900 using xda app-developers app

supermth2 said:
It's not broken, just flaws to its pretty white look. I would never take it in the way it is. I DO NOT WANT A KNOX COUNTER IF AT ALL POSSIBLE! I just need my wifi working. Can I flash back to 4.2? If so could I get a link to a step by step tutorial? Thanks for the reply guys.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
What you posted is not a knox counter. That is standard for any platform.. I'm currently back to mc2 stock and mine says the same thing.. Knox counter you will have a warranty void entry at the bottom..

supermth2 said:
It's not broken, just flaws to its pretty white look. I would never take it in the way it is. I DO NOT WANT A KNOX COUNTER IF AT ALL POSSIBLE! I just need my wifi working. Can I flash back to 4.2? If so could I get a link to a step by step tutorial? Thanks for the reply guys.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Here you go. http://forum.xda-developers.com/showthread.php?t=2086769
download MC2 and put it on your external sd card, then wipe everything EXCEPT your external sd card and flash. it takes just a few minutes and your phone will be like it come out of the box. Once it's done you can then take it to the sprint store for whatever reason.

Reply
one last question. how can i use titanium backup it my root sevices wont work? all i get is "superSU has unfortunetly stoped working." i need all my contacts backed up.

supermth2 said:
one last question. how can i use titanium backup it my root sevices wont work? all i get is "superSU has unfortunetly stoped working." i need all my contacts backed up.
Click to expand...
Click to collapse
Back your contacts up to google, not the phone.. When you flash a new rom,then set it up google will install all of your contacts from your google account.. I do not use titanium for anything other than un-installing things I do not want..

UPDATE!
I ran the zip andit seemed to load up fine. I got a "digital sigiture varifacation" error, my phone reset and booted up like it was all puked out, froze trying to acsses settings. I reset it and its all good but i got nowhere... still on the same custom rom that isnt even custom, still dont have root... wifi still not working. what next guys? i appriciate the help btw. thanks.

supermth2 said:
I ran the zip andit seemed to load up fine. I got a "digital sigiture varifacation" error, my phone reset and booted up like it was all puked out, froze trying to acsses settings. I reset it and its all good but i got nowhere... still on the same custom rom that isnt even custom, still dont have root... wifi still not working. what next guys? i appriciate the help btw. thanks.
Click to expand...
Click to collapse
What steps are you doing? Post and I will see what your issue is and try to get you back on track.

I put the zip in the root of my sd card, backed up my photos, shut down my phone, boot into recovery, and apply update from sd card, select my zip, it begins to load up reading
"install/update from sd..." the next thing I see is "digital signature verification failed" it runs a few lines so quick I can't read them and reboots all messed up, I restart, and I'm right where I began.
That's exactly what I'm doing. Idk what recovery I have, it just says "recovery menu (e3)" with a blue backdrop. Dose this help?
Sent from my SPH-L900 using xda app-developers app

supermth2 said:
I put the zip in the root of my sd card, backed up my photos, shut down my phone, boot into recovery, and apply update from sd card, select my zip, it begins to load up reading
"install/update from sd..." the next thing I see is "digital signature verification failed" it runs a few lines so quick I can't read them and reboots all messed up, I restart, and I'm right where I began.
That's exactly what I'm doing. Idk what recovery I have, it just says "recovery menu (e3)" with a blue backdrop. Dose this help?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Are you on a custom rom now? or are you stock? I need to know so I can get a better idea of how to move you into the right direction once and for all.

See that's the thing. Odin says I'm on custom everything with a count of 4. But my phone updated through the sprint network while I was sleeping one day so It used an official rom, but I never got a Knox counter, and my recover and everything never went back to stock.
Sorry if the problem is innoying, if you want I could make a video showing the problem and link you to it.
Sent from my SPH-L900 using xda app-developers app

supermth2 said:
See that's the thing. Odin says I'm on custom everything with a count of 4. But my phone updated through the sprint network while I was sleeping one day so It used an official rom, but I never got a Knox counter, and my recover and everything never went back to stock.
Sorry if the problem is innoying, if you want I could make a video showing the problem and link you to it.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Everytime to flash a rom, you will have a flash count. With the knox thing that is a prart of the MK4 update, but it can be ridden with no problem.
Flash back to 100% pure stock unrooted with stock recovery.. When you are done, and you go back to download mode,you will not see the knox count, only the normal one you would see if flashing a none MK4 rom.. If your phone is out of warranty, then do not worry about the knox counter.. If it is still under warranty, when you need to go to the Sprint store, by flashing back to unroooted stock MC2, the knox counter will not show, and everything will show normal instead of custom..
So follow these steps once again.
1)Put (if you have not already) Billards Stock MC2 unrooted with counter reset on your external Sdcard.
2) If you do not already have one, install a custom recovery.
3)Boot to your custom recovery and do a complete wipe cache, delvik cache, data, system..
4) once done install the zip
5) Once the zip starts billards version of TWRP will start. when it does do a complete wipe again.
6) Go to install and choose the billards zip again and run it
7) When it is done it choose reboot, but it will reboot into a special feature included, but you have to do nothing else. Once it is done it will boot let it do its thing, and when done you should be back to 100% MC2 stock..
When it is all done, set up your phone like you would normally do.. At some point sprint will tell you about a system update.. Let it run on its own and you should be at MK4. Yes you will have the know counter, but that is no real big deal,as I mentioned earlier.

Yesssss! - update
I got knox disbled and got clockworkmod recovery going. got the zip installed after wipeing my cache and then got stuck in the wonderful boot loop.
got into stock recovery, wiped cache again, factory reset the device....... AND BAMN!!!! just like new thanks for your help guys. so happy to be able to take my phone in and get it replaced.

Congtats see it is not all that complicated.
Sent from my SPH-L900 using Tapatalk

[Q] Is it possible to flash the Android Lollipop Dev Preview without formatting?

I cant wait til the ota comes out to try out lollipop. I've read some articles that it can be flashed via the "official" way a.k.a. the fastboot way but i need to wipe all data. I already have a unlocked boot loader so maybe theres a way to skip the formatting? I found an article that i can edit the fastboot flash script to not wipe my device but its noted that its not guaranteed to work. Have anyone tried this yet? Maybe just like updating roms that dont need wiping the device?
The androidpolice webpage http://www.androidpolice.com/2014/1...ilable-for-the-2013-wifi-nexus-7-and-nexus-5/
And
http://www.howtogeek.com/176284/how...-without-waiting-by-flashing-a-factory-image/

Just did the update to Lollipop dev preview from the last "L" preview without wipe (via editing out the -w from the script). Haven't had a problem doing this before, aside from having to unfreeze stock Chrome (I use Chrome Beta) and uninstalling CF.Lumen drivers. So far, it's working fine for me. However, the boot animation stayed on quite a bit longer than usual before it reached the "Android is upgrading" screen. It was on the boot animation for a good 3-5 minutes, so don't consider hard resetting it so soon.
Update: I ended up having to do the "SetupWizard" fix to restore notification pull-down functions, and possibly Google syncing related features.
http://www.androidpolice.com/2014/0...at-refuses-to-pull-down-after-android-update/
Good luck with the upgrade without wipe.

divadkha said:
Just did the update to Lollipop dev preview from the last "L" preview without wipe (via editing out the -w from the script). Havent had a problem doing this before, aside from having to unfreeze stock Chrome (I use Chrome Beta) and uninstalling CF.Lumen drivers. So far, its working fine for me. However, the boot animation stayed on quite a bit longer than usual before it reached the "Android is upgrading" screen. It was on the boot animation for a good 3-5 minutes, so dont consider hard resetting it so soon.
Update: I ended up having to do the "SetupWizard" fix to restore notification pull-down functions, and possibly Google syncing related features.
http://www.androidpolice.com/2014/08/07/how-to-fix-missing-home-and-recents-buttons-and-notification-shade-that-refuses-to-pull-down-after-android-update/
Good luck with the upgrade without wipe.
Click to expand...
Click to collapse
Thank you for your information. But in your case its android l to android l which is not quite a huge jump. But I'm from kitkat to lollipop. Will that be any difference?

ImjuzCY said:
Thank you for your information. But in your case its android l to android l which is not quite a huge jump. But I'm from kitkat to lollipop. Will that be any difference?
Click to expand...
Click to collapse
You don't HAVE to wipe data before updating to a new OS version but from my personal experience I very strongly believe that wiping the data will give a more reliable update in the long term and have less chance of buggy user installed apps. One thing to think about is the fact that an OTA will NOT ever wipe data. With "minor" updates (like 4.4.3 to 4.4.4) I just fastboot flash the system image and whatever else is necessary which will keep all of the user apps installed and all the settings intact. With "major" OS updates I sometimes but not always do a factory reset from inside TWRP which will not wipe the storage then use TWRP to go into the bootloader and flash whatever from there. With the flash_all batch file modified you could flash the factory image (L preview) and have a clean install and not have your storage wiped. If you instead fastboot flash the bootloader, boot and system images separately instead of using the flash_all batch file you don't replace the custom recovery (TWRP) with the stock recovery. If you don't have a custom recovery installed and want a clean install you have no choice but to wipe everything. Save what you want from your storage to your computer. If you do have a custom recovery make a backup (nandroid) first. But... my personal opinion is that an OTA will not be as reliable as a clean install, again, not that I always do a clean install. Another thing to think about is how important is a clean install now anyway, the official 5.0 update isn't too far down the road. Do what feels comfortable for you, you have multiple choices.

wantabe said:
With "major" OS updates I sometimes but not always do a factory reset from inside TWRP which will not wipe the storage then use TWRP to go into the bootloader and flash whatever from there.
Click to expand...
Click to collapse
Thanks for your detailed explanation. But I have a question. You said you sometimes do a factory reset from TWRP *which will not wipe storage*. But according to TWRP's website, factory reset means wiping everything. Isn't it? Or you mean the sdcard partition?

ImjuzCY said:
Thanks for your detailed explanation. But I have a question. You said you sometimes do a factory reset from TWRP *which will not wipe storage*. But according to TWRP's website, factory reset means wiping everything. Isn't it? Or you mean the sdcard partition?
Click to expand...
Click to collapse
Yes and no! Doing a factory reset from your device settings "Settings/Backup & reset" will absolutely wipe Everything on your device. If you do a factory reset from inside TWRP it will Not wipe your device storage. When you open TWRP and tap on "Wipe" the screenshot shows what you will see. Excuse the screenshot, it's hard to get the camera to focus on a shiny screen. The only way to do a factory reset/wipe data that I know of without wiping the storage is with a custom recovery.

wantabe said:
Yes and no! Doing a factory reset from your device settings "Settings/Backup & reset" will absolutely wipe Everything on your device. If you do a factory reset from inside TWRP it will Not wipe your device storage. When you open TWRP and tap on "Wipe" the screenshot shows what you will see. Excuse the screenshot, its hard to get the camera to focus on a shiny screen. The only way to do a factory reset/wipe data that I know of without wiping the storage is with a custom recovery.
Click to expand...
Click to collapse
Oh! Thank you very much for the explanation. Wiping data partition means clearing all user installed apps right? If its true then I rather wait for the ota. I don't wanna waste too much time on backing up and restoring apps. Thanks anyway

ImjuzCY said:
Oh! Thank you very much for the explanation. Wiping data partition means clearing all user installed apps right? If its true then I rather wait for the ota. I don't wanna waste too much time on backing up and restoring apps. Thanks anyway
Click to expand...
Click to collapse
Correct! Wiping the data will always remove the user installed apps. Wiping from inside your device settings or from inside TWRP will determine if your storage gets wiped. Don't forget... there is more than one way to flash a factory image, in this case the Android L preview, without wiping any data.
1. Modify the flash_all.bat that is inside the factory image with a text editor (notepad) removing the text -w. Takes like 5 seconds to modify the text.
fastboot flash bootloader bootloader-flo-flo-04.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-lpx13d.zip
fastboot flash bootloader bootloader-flo-flo-04.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-razor-lpx13d.zip
2. Fastboot flash the bootloader, boot and system images.
Either way it takes longer for android L to boot up the first time than it does to flash the images. Just saying!

Backup it all! (Before execution of some operations that can cause data loss)
You just need to download this tool.
If your bootloader is really unlocked, then they'll be no problems out there!
Make sure your Nexus Device is connected to your Computer with a MicroUSB-Cable!
But do never use a slack joint cable! They'll cause many problems there!
Launch the Toolkit and it should detect your Tablet!
Go to the Installation-Guide on the Main-Menu and then install the GoogleADB-Driver.
That's the 1st(2nd?) ever time i'm using the USB-Icon on a Post!
{
"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"
}
Click to expand...
Click to collapse
Go to the BackUp-Menu and execute a full-Android ADB-Backup
Make sure your device is connected to the Computer!
And after the backup then make sure the BackupFile is there to make sure that to avoid a Blank 0B-File or no file at all!
If you've got any questions left then ask me anytime! Anytime you ever want!
All the best!
❤Hannah(❤❤❤!)
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
Hannah Stern said:
Go to the BackUp-Menu and execute a full-Android ADB-Backup
Click to expand...
Click to collapse
Sorry! What i mean is the Full N'Android /W/ Backup!
All the best,
Hannah:laugh:

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