Develop Bugs

[Q] 4.2 Upgrade Problems-- verizon gnex

My vzw nexus has been running mRom version x.x for sometime. I went to install the upgraded 4.2 rom via clockworkmod, (wipe cache and dalvik, flash over current rom) and it appeared to install successfully. However, when I rebooted I saw the lock screen for a split second and it just started to boot loop. I rebooted back into recovery and wiped all data and tried to reinstall the rom via through the new 0 partition, but I get the error symlink: some symlinks failed
E: Error in /sdcard/0/mRom_v3.0_JOP40C.zip (status 7)
I think that this may have something to do with the multiple users in 4.2, but don't quote me on it. I cannot get my computer to recognize my phone, when I go to mounts in cwm I can mount everything except the sdcard, although I think this problem was evident before I flashed. Any suggestions? I could try to restore to stock using galaxynexusrestore-- http://forum.xda-developers.com/showthread.php?t=1743939 but I have not tried it before so I cannot speak to weither it will work or not.
HELP!

Always always wipe data when changing an Android version. Unless it comes via OTA, which is specifically designed to fix all the little problems that will arise.
As to how to fix the problem, flashing a factory image
http://forum.xda-developers.com/showthread.php?t=1626895 will probably work. Just follow the rules for Toro. The toolkit you linked may work, but it's generally a better idea to not use them and actually familiarize yourself with how to fix things yourself, you'll be less likely to make mistakes in the future.

Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!

Misread OP.

ironerd said:
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Click to expand...
Click to collapse
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.

same problem, stuck at JB logo
Marisa said:
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
Click to expand...
Click to collapse
I was running stock JRO03O with Clockwork Recovery Mod and decided to flash the JB 4.2 ROM from Grouper (http://forum.xda-developers.com/showthread.php?t=1993545 - I can't post there since I'm too new).
The update must have succeeded, because I can see the new 0/ partition on my phone, but it won't boot past the "X" logo. I can boot into CWM and try various things, but of course because of the data structure changes, I can't actually recover to my last save. When I'm home, I'm hoping I can get the CWM backup off my phone to restore later, but without a terminal in CWM, I can't try to fix the path.
It's nice to hear that CW is working on a fix - I hope it's retroactive (I mean, helpful to those of use who already screwed up). Also, I've never flashed anything but OTA, so I didn't realize I needed to wipe data before flashing something that's supposed to be almost stock. I guess it matters how different from stock the ROM actually is.
What's next? I'll try to interface with my PC at home. If others have this problem, I'd be happy to hear your success (or fail) stories. I'll share mine once I've tried it.

The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Koush
When trying to restore CWM backup move previous backups AND blobs folder to /data/media/clockworkmod if the folder does not exist simply create one or if unsure just go to recovery and make new backup, it will create necessary folders for you then move (or copy to be safe) files to location.... The blobs folder is what I was missing and why I kept getting error while trying to restore.
Click to expand...
Click to collapse
This should help your problem solving for the moment, if you're familiar enough with ADB to move the files that way it shouldn't take very long at all

thanks, and update of my status
Marisa said:
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Click to expand...
Click to collapse
Thanks for the extra insight. I wrestled with my phone all night and finally got it back to 4.1.1 (JRO030). Along the way I screwed up my adb or fastboot drivers, and for all my efforts I couldn't get any of my nexus toolkits to recognize the phone as in fastboot mode. Adb was fine, but fastboot was a no-go. I moved to a fresh computer after someone else had success with that, and read up on how to do a manual (adb command line) flash to factory image.
Now that that's done, I'm hoping I can restore from CWM to get back to where I was. If not, then yuck, but I'm optimistic.

Upgrade from 4.1.2 to 4.2.X Fail...

So I attempted to upgrade my girlfriend's Galaxy Nexus from 4.1.2 to 4.2.2 (this is on Verizon. Was using a Xenon HD version from last August and attempted to update to the newest version).
Well, since I'm an idiot, I didn't read up on the file system changes and now I can't figure out how to get everything working properly. I have the sdcard/0 now and haven't been able to move the files over from sdcard/0 to the sdcard.
All I want to do at this point is just restore a nandroid backup and start over from scratch. Any help would be greatly appreciated.... I'm also having driver issues, so if there's any way to do this without using ADB, that would help immensely.
Thanks in advance.

The SDcard/0 is supposed to exist. Take 10 minutes to do the tiniest bit of searching and all your problems will solve themselves.

can you boot into recovery? what do you mean you cant get things working properly

slimb9 said:
can you boot into recovery? what do you mean you cant get things working properly
Click to expand...
Click to collapse
Yeah I can get into recovery but when I try to restore nandroid it says there are no files, and I know there is a backup.

I did a half hour of searching, but thanks for the help. I must not be searching for the right thing....

so can the phone turn on? or can you only boot into recovery

slimb9 said:
so can the phone turn on? or can you only boot into recovery
Click to expand...
Click to collapse
Yeah I can turn it on. Gapps didn't install, though, so I don't have a keyboard and can't install goomanager from the play store to update recovery. I also can't move files in the file manager because it times out very time.

if you still have the old xenon rom .zip file on the phone you could just flash that after wiping/clearing everything. then from there boot into recovery and see if you can see your nandroid backup of the old xenon she was on. not sure if this will help but worth a try. looks like the new xenon rom required a full wipe so something may be messed up that you could fix by flashing an older version

Asterdroid said:
Well, since I'm an idiot, I didn't read up on the file system changes and now I can't figure out how to get everything working properly. I have the sdcard/0 now and haven't been able to move the files over from sdcard/0 to the sdcard.
Click to expand...
Click to collapse
063_XOBX said:
The SDcard/0 is supposed to exist. Take 10 minutes to do the tiniest bit of searching and all your problems will solve themselves.
Click to expand...
Click to collapse
As 063_XOBX said, sdcard/0 is supposed to exist. Considering your comment later in the thread about not being able to find old backups, it sounds like you have an outdated recovery that doesn't understand the new file structure. Update your recovery rather than screwing with Google's intended file structure.
Asterdroid said:
I'm also having driver issues, so if there's any way to do this without using ADB, that would help immensely.
Click to expand...
Click to collapse
What driver issues? You haven't been overly clear with the actual problems that you're having. You said you had a problem with Gapps. Why not download and flash a Gapps package?

i p.m. him without a response. im sure he figured out he was doing something wrong. it helps to read instructions

[Q] Kindle Fire won't flash stock ROM.

I got the stock ROM off of amazon. Converted it to update.zip, couldn't flash it cuz it said "blaze" as the codename in the updater script. Updated it to otter, still can't flash it. What am I doing wrong? Help is appreciated, thanks.

GalaxyExhibit said:
I got the stock ROM off of amazon. Converted it to update.zip, couldn't flash it cuz it said "blaze" as the codename in the updater script. Updated it to otter, still can't flash it. What am I doing wrong? Help is appreciated, thanks.
Click to expand...
Click to collapse
Revert to an earlier version of TWRP (preferably one before the different "otter" and "blaze" versions) or install COTR. I'd recommend COTR though.
Also, DON'T FORGET TO FACTORY RESET!!! Otherwise, you will need a factory cable to fix it.

soupmagnet said:
Revert to an earlier version of TWRP (preferably one before the different "otter" and "blaze" versions) or install COTR. I'd recommend COTR though.
Also, DON'T FORGET TO FACTORY RESET!!! Otherwise, you will need a factory cable to fix it.
Click to expand...
Click to collapse
Thanks, will do.

Ok, so here is what I did to fix the issue. Instead of installing TWRP (this is a smarter idea), I installed ubuntu as a side OS, after installed, downloaded stock firmware. After that, changed it to zip format and named it update.zip. After that, I changed the name from blaze to otter in the update-script. Guess what, it worked. Recommending this method to anyone who has either this issue, TWRP 2.6 installed, or just likes to play around with their KF.

LGHater said:
Ok, so here is what I did to fix the issue. Instead of installing TWRP (this is a smarter idea), I installed ubuntu as a side OS, after installed, downloaded stock firmware. After that, changed it to zip format and named it update.zip. After that, I changed the name from blaze to otter in the update-script. Guess what, it worked. Recommending this method to anyone who has either this issue, TWRP 2.6 installed, or just likes to play around with their KF.
Click to expand...
Click to collapse
Alright, I'm having the same issue, but I'm not sure how to do the things you've described here, being a complete noob. Could you provide a bit more of a detailed instruction, including what difference installing Ubuntu made and how one goes about changing the name from blaze to otter in the update-script? (Starting with where does one find the script.)
I'm currently running TWRP 2.6.0.0 and just want to go back to stock...which is now 6.3.2.
Thx.

bembley said:
Alright, I'm having the same issue, but I'm not sure how to do the things you've described here, being a complete noob. Could you provide a bit more of a detailed instruction, including what difference installing Ubuntu made and how one goes about changing the name from blaze to otter in the update-script? (Starting with where does one find the script.)
I'm currently running TWRP 2.6.0.0 and just want to go back to stock...which is now 6.3.2.
Thx.
Click to expand...
Click to collapse
Get a virtual machine, download ubuntu and select the ISO file in whatever VM software you use. When it's done installing, download the stock software and when it's done downloading, change the format from BIN (I think it's a bin I might be wrong) to ZIP. Then go into the ZIP file and go into Meta-Inf, and edit the update-script with the text software on ubuntu and change the code name from blaze to otter if you're having a status 7 error. And you're done. Get ready to flash the software by performing a factory reset. Then go back and install the update.zip. And you're done. If this didn't work, post on this thread again with any confusion or errors.

LGHater said:
Get a virtual machine, download ubuntu and select the ISO file in whatever VM software you use. When it's done installing, download the stock software and when it's done downloading, change the format from BIN (I think it's a bin I might be wrong) to ZIP. Then go into the ZIP file and go into Meta-Inf, and edit the update-script with the text software on ubuntu and change the code name from blaze to otter if you're having a status 7 error. And you're done. Get ready to flash the software by performing a factory reset. Then go back and install the update.zip. And you're done. If this didn't work, post on this thread again with any confusion or errors.
Click to expand...
Click to collapse
Worked marvelously...and confirmed my suspicion of hardware problems. The stock image loaded, but processes keep failing and it reboots itself over and over again...similar to what it was doing with the cyanogen mod I was using.
Anyway...Thanks for your help!!

bembley said:
Worked marvelously...and confirmed my suspicion of hardware problems. The stock image loaded, but processes keep failing and it reboots itself over and over again...similar to what it was doing with the cyanogen mod I was using.
Anyway...Thanks for your help!!
Click to expand...
Click to collapse
Well I'm glad things worked out for you and the error was gone. Enjoy stock, I guess. lol

Easy-to-flash backup of VUPMP.GPRO.sG3.Stable

UPDATE:
Flash using **CWM from Freegee**( I previously recommended Philz for the updated look and features but it is SUPER inconsistent and unfortunately unreliable, I do not mean any offense to its creator/developer, it is just too much hassle and this thread is meant for easy flashing and I was already posting the work around for the Philz bootloop issue which killed the purpose of easy flashing...)
Remember to make a nandroid/backup using CWM, if you forgot to make one, PM me to help you sideload a Rom using ADB. (will save you the hassle of going through stock and go directly to any custom rom of your preference)
Hello dear people with an E980:
I'm here to share a backup I made for my personal use to avoid the hassle of having to return to stock to flash the VUPMP stable rom and deleting the recovery folder inside the Rom, pretty much in other words it's just an "easy-to-flash" backup.
Rom comes from:
http://forum.xda-developers.com/opt...om-20140920-vupmp-gpro-sg3-stable-lg-t2902595
Here is the backup!, it is flashable so don't extract it, it includes a boot.img (kernel) so you can restore from any rom, no need to come from stock:
https://www.androidfilehost.com/?fid=95747613655048316
MD5: f50a74eb5ceb7600d0ea609192d5c258
On this particular backup, I applied the following fixes for E980:
-Volume restore fix
-Video recording fix
-Removed a system apk which seemed to be a calendar in viet (for the sake of clean and stock look).
It is highly recommended to wipe before flashing:
-Data (without wiping data/media, if you don’t know how to do this just ask in the Q&A section or PM me!!)
-Cache & Dalvik cache
-System
-Please, don't report bugs if doing a "dirty" flash.
Special thanks to:
@datphu2811 for developing such a cool ROM
@Chairizkuro for the video recording fix
anyone who contributed with this files linked above!
Remember:
Flash at your own risk!

Anyone try yet?
Anybody try this yet? Looks cool! Sounds easy.

DollarStrawz said:
Anybody try this yet? Looks cool! Sounds easy.
Click to expand...
Click to collapse
I did, I followed the instructions but got stuck in a boot loop and it didn't fix when I applied the aforementioned zip. I just went back to stock the normal way and everything worked out. That's just my experience though, you could have completely different results.

GreatCaesar said:
I did, I followed the instructions but got stuck in a boot loop and it didn't fix when I applied the aforementioned zip. I just went back to stock the normal way and everything worked out. That's just my experience though, you could have completely different results.
Click to expand...
Click to collapse
Man thanks!! I was just about to do it.

GreatCaesar said:
I did, I followed the instructions but got stuck in a boot loop and it didn't fix when I applied the aforementioned zip. I just went back to stock the normal way and everything worked out. That's just my experience though, you could have completely different results.
Click to expand...
Click to collapse
Can you describe your problem? What kind of bootloop did you get?
A) it kept booting to recovery (that's what the zero zip is for)
B) it kept stuck in the lg logo
If B)
Did you performed a full wipe of data (without data media), system and cache? Did the flash took an unexpected amount of time (2 seconds instead of 2 minutes)?
Additionally, why did you totted back? Didn't you made a backup first?, in case you made a backup, did the recovery rendered useless after flashing my backup?
Did you get any lokifying errors?
DollarStrawz said:
Man thanks!! I was just about to do it.
Click to expand...
Click to collapse
Please let the person answer those questions before walking away scares, I've tried my own backup several times and I assure you it works properly if following the instructions. Even further, it's common sense to do a backup even without being warned about it.

OK yeah thanks I will still try it. Thanks for making this. It looks super cool and easy.

DollarStrawz said:
OK yeah thanks I will still try it. Thanks for making this. It looks super cool and easy.
Click to expand...
Click to collapse
Please use CWM from Freegee, I have been getting reports from a few friends testing on how Philz touch is being inconsistent, I'm about to update main post.

Md5 Mismatch
I followed ever4ything I think. I extracted it on my desktop then copied that folder over to Clockworkmod/backup folder. After wipingt everything I went to restore and got Md5 Mismatch. What did I do wrong?

DollarStrawz said:
I followed ever4ything I think. I extracted it on my desktop then copied that folder over to Clockworkmod/backup folder. After wipingt everything I went to restore and got Md5 Mismatch. What did I do wrong?
Click to expand...
Click to collapse
Can you please manually check the MD5 sum of your downloaded file? Let me know if you don't know how to do it I can show an easy method.

Jose-MXL said:
Can you please manually check the MD5 sum of your downloaded file? Let me know if you don't know how to do it I can show an easy method.
Click to expand...
Click to collapse
I checked the re-downloaded one and they match. I used an Md5 checker?? So am I on the right track by extracting and copying that folder to clockwork backup? Then in CWM go to Mounts and Storage and format /data, format /system, format /cache and wipe dalvik. THEN restore the folder copied earlier. Just want to make sure I'm not missing anything. Thanks!!

DollarStrawz said:
I checked the re-downloaded one and they match. I used an Md5 checker?? So am I on the right track by extracting and copying that folder to clockwork backup? Then in CWM go to Mounts and Storage and format /data, format /system, format /cache and wipe dalvik. THEN restore the folder copied earlier. Just want to make sure I'm not missing anything. Thanks!!
Click to expand...
Click to collapse
Oh! OH! OH!!, I know what's going on, this is a flashable zip lol, you are not supposed to extract it, sorry if I provided misleading instructions so I can change them

AWESOME
Loving this ROM everything works great!!

Can't get LTE To Stick
Everything works great but the one thing bothering me is I can't seem to get Global + LTE to stick after following the steps:
- Input 5457#*988# from dial pad
- Find "Network Mode" set value "Global + LTE"
- Find "CDMA Subsciption" set value "USIM"
When I try to switch from NIV to USIM the phone instantly reboots and reverts the network back to WCDMA. Does anyone know how to fix this?

Jose-MXL said:
Oh! OH! OH!!, I know what's going on, this is a flashable zip lol, you are not supposed to extract it, sorry if I provided misleading instructions so I can change them
Click to expand...
Click to collapse
How is the flushable ROM running. Thinking about flashing. Any differences from other VROM

[Q] Flashing TWRP failing!

Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.

Vesten said:
Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.
Click to expand...
Click to collapse
what exact version of twrp?
Is the backup a system IMAGE backup?
are you entering TWRP in read-only mode?
When you try to restore now, what does the terminal output say?

TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...

Vesten said:
TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...
Click to expand...
Click to collapse
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads

jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
I'll have to check, but don't think it does.
I'll try that new version of TWRP and report back.
Many thanks for the help, greatly appreciated.

jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.

Vesten said:
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.
Click to expand...
Click to collapse
What happens when you restore your backup and reboot without installing supersu?

jollywhitefoot said:
What happens when you restore your backup and reboot without installing supersu?
Click to expand...
Click to collapse
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.

Vesten said:
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.
Click to expand...
Click to collapse
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version

jollywhitefoot said:
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version
Click to expand...
Click to collapse
Interesting. There's nothing saying it couldn't write anything..
Just tried opening SuperSU from my restored backup, and hits me with "There is no SuperSU binary installed!" This is a problem, blah, blah, etc.
Then tried check-boxing the 'system' box in the Mount section. Then tried flashing UPDATESuperSu.VsXX and just gave me the usual as said above. Crashed and reboots.
https://www.dropbox.com/s/cvkclw8xuzua4u3/2015-07-20 21.56.37.png?dl=0
Losing the will to live! Ha

What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?

Vesten said:
What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?
Click to expand...
Click to collapse
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.

jollywhitefoot said:
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.
Click to expand...
Click to collapse
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?

Vesten said:
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?
Click to expand...
Click to collapse
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?

jollywhitefoot said:
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?
Click to expand...
Click to collapse
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)

Vesten said:
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)
Click to expand...
Click to collapse
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401

jollywhitefoot said:
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401
Click to expand...
Click to collapse
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.

Vesten said:
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.
Click to expand...
Click to collapse
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698

jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Wow, thankyou! I've been Googling RUU's all night at work and found nothing like this. Think I'll do that and flash the RUU and start afresh!
Getting a killer 17.4 kbp/s though. 100mb connection wasted. Ha!

jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Yay it worked! Using a stock image from that link. Something must of been really screwed up. I'm now re-rooted! Many thanks for your help!