Develop Bugs

Looking for some help...

Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point

garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.

OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager

Older Recovery versions are available on "dougpiston.com" just follow the directions.

www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.

Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip

Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.

Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium

pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?

[Q] Cyanogen 10.1 mod gone wrong.

AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.

chazbot7 said:
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
Click to expand...
Click to collapse
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).

Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.

BWolf56 said:
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Click to expand...
Click to collapse
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.

chazbot7 said:
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
Click to expand...
Click to collapse
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.

BWolf56 said:
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
Click to expand...
Click to collapse
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?

chazbot7 said:
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
Click to expand...
Click to collapse
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app

BWolf56 said:
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.

chazbot7 said:
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
Click to expand...
Click to collapse
No need to apologize. Glad you got it back up! And it was mostly to keep you from making similar mistakes in the future
Sent from my SGH-I747 using xda app-developers app

also one thing you need to know
First boot after you flash will always take longer than normal. After that, it's fine

[HELP] Stuck on nexus 'X' loading screen after simply trying to flash new radio!

Hello, I need some urgent help as I currently don't have a phone! Keep in mind I'm not too good with all of this modding stuff, I've generally played it safe and did small things here and there.
I was running a rooted stock-based ROM of JB 4.3 on my Galaxy Nexus. Completely stock without a few g-apps.
The radio was XXLH1.
I simply wanted to update the radio, so I downloaded 2 of the newest radios. I put the zips in /sdcard whereas I usually put them in sdcard/0/0/0 (don't ask, never really understood or took care of that mess). Didn't think it'd make a difference where the zip files were. I have 3 other radios I already switched to and from to test in that latter folder, and was switching between them perfectly fine days ago.
I go to flash the newest radio UGLL1.
First I cleared cache, cleared dalvik, made a nandroid, flashed the radio zip - it said it worked. Went to reboot, stuck at the nexus logo loading screen.
So I take out the battery, put it back in, boot into CWM Recovery, and select the nandroid I just made hoping to undo the horror. Says MD5 mismatch! I don't know what that is, just read a bit about it but none of the common issues related to me (like renaming the nandroid?).
I select an earlier nandroid I made a week or so back, this one says it restored successfully. I reboot, stuck at nexus logo loading screen again.
Remove battery, reboot into recovery. I see on the CWM screen the radio is still UGLL1. Oh right, the radio didn't change, that's firmware or whatever...?
So I tried to use some logic and from CWM flashed the zip of the radio I had before, XXLH1. Says it installed. So now I should have the original radio I had plus the restored image of my phone a week or so ago.
Hit reboot, stuck at loading screen.
What could have went wrong? And how can I fix this?
Again, please understand I don't know much beyond these simple tasks, so clear explanations would help a ton.
Other random info:
- I have CWM Recovery 5.8.0.2
- My computer doesn't read my phone when it's at that 'X' logo screen. In Recovery it picks it up but I never figured out how to make it recognize again on my new computer. Never needed to.

BryMerc said:
Hello, I need some urgent help as I currently don't have a phone! Keep in mind I'm not too good with all of this modding stuff, I've generally played it safe and did small things here and there.
I was running a rooted stock-based ROM of JB 4.3 on my Galaxy Nexus. Completely stock without a few g-apps.
The radio was XXLH1.
I simply wanted to update the radio, so I downloaded 2 of the newest radios. I put the zips in /sdcard whereas I usually put them in sdcard/0/0/0 (don't ask, never really understood or took care of that mess). Didn't think it'd make a difference where the zip files were. I have 3 other radios I already switched to and from to test in that latter folder, and was switching between them perfectly fine days ago.
I go to flash the newest radio UGLL1.
First I cleared cache, cleared dalvik, made a nandroid, flashed the radio zip - it said it worked. Went to reboot, stuck at the nexus logo loading screen.
So I take out the battery, put it back in, boot into CWM Recovery, and select the nandroid I just made hoping to undo the horror. Says MD5 mismatch! I don't know what that is, just read a bit about it but none of the common issues related to me (like renaming the nandroid?).
I select an earlier nandroid I made a week or so back, this one says it restored successfully. I reboot, stuck at nexus logo loading screen again.
Remove battery, reboot into recovery. I see on the CWM screen the radio is still UGLL1. Oh right, the radio didn't change, that's firmware or whatever...?
So I tried to use some logic and from CWM flashed the zip of the radio I had before, XXLH1. Says it installed. So now I should have the original radio I had plus the restored image of my phone a week or so ago.
Hit reboot, stuck at loading screen.
What could have went wrong? And how can I fix this?
Again, please understand I don't know much beyond these simple tasks, so clear explanations would help a ton.
Other random info:
- I have CWM Recovery 5.8.0.2
- My computer doesn't read my phone when it's at that 'X' logo screen. In Recovery it picks it up but I never figured out how to make it recognize again on my new computer. Never needed to.
Click to expand...
Click to collapse
xxlh1 is a galaxy s3 radio and also a modem firmware update And a maguro variant ...
ugll1 is a maguro radio...
i might recommend
http://forum.xda-developers.com/gal...dios-verizon-galaxy-nexus-radios-3-5-t1890585

arigr said:
xxlh1 is a galaxy s3 radio not a gnex...
ugll1 is a maguro radio...
i might recommend
http://forum.xda-developers.com/gal...dios-verizon-galaxy-nexus-radios-3-5-t1890585
Click to expand...
Click to collapse
This is incorrect. HERE is the thread for the maguro radios, and there is definitely an XXLH1 variant. However, OP did not state which Galaxy Nexus variant he has. Do you have the GSM, Verizon, or Sprint versions? I'm guessing GSM, but please confirm.
Assuming you have the GSM variant, I would recommend that you try to use flastboot to flash XXLH1 again. Download at the thread I linked above, then connect your phone to your PC while in fastboot mode. Flash using
Code:
fastboot flash radio [file name].img

FredFS456 said:
This is incorrect. HERE is the thread for the maguro radios, and there is definitely an XXLH1 variant. However, OP did not state which Galaxy Nexus variant he has. Do you have the GSM, Verizon, or Sprint versions? I'm guessing GSM, but please confirm.
Assuming you have the GSM variant, I would recommend that you try to use flastboot to flash XXLH1 again. Download at the thread I linked above, then connect your phone to your PC while in fastboot mode. Flash using
Code:
fastboot flash radio [file name].img
Click to expand...
Click to collapse
i stand corrected.. sorry for any confusion..have edited reply

FredFS456 said:
This is incorrect. HERE is the thread for the maguro radios, and there is definitely an XXLH1 variant. However, OP did not state which Galaxy Nexus variant he has. Do you have the GSM, Verizon, or Sprint versions? I'm guessing GSM, but please confirm.
Assuming you have the GSM variant, I would recommend that you try to use flastboot to flash XXLH1 again. Download at the thread I linked above, then connect your phone to your PC while in fastboot mode. Flash using
Code:
fastboot flash radio [file name].img
Click to expand...
Click to collapse
I appreciate the replies! I have a GSM Galaxy Nexus and yes those radios I listed were compatible.
I ended up just starting all over again. I had the dreaded sdcard/0/0/0/0 issue and felt that MAY have been causing the problem, and ended up doing a factory reset to clean it up anyway. After doing that, all the radios were flashed fine.
Another thing was, I was suddenly really low on space even though I didn't have many things in my sdcard, but it seems because of all the duplicate file paths I was killing my space. So there's a very slim chance the radio was simply too big, even though it's only like 4mb, but perhaps I was that low on space.
Thanks for the help anyway. I was lucky to have recent backups, it was merely time consuming. But now I have a cleaner sdcard.

[q] frequent frustrating data drops on htc one m7

Hello All,
Due to my endless frustrations, this might be a long one so please bear with me!
So I purchased a Verizon Global HTC ONE M7 from the States, I am currently in Nigeria and the only thing that makes me sadder and more frustrated than the state of my phone right now is the incessant terror attacks in the country! Initially, almost everything worked fine when i popped in my new Etisalat sim card into the phone, except for the mobile hotspot (which just conveniently turns out to be the one of the top 3 most important features in a phone for me - probably the feature I use the most) this message kept popping up about how hotspot couldn't be used without a VZW sim, etc (also with the non-verizon sim warning when the phone boots up). I tried all I could, eventually deciding to flash a new ROM to clear out everything Verizon and start fresh.
Enter Viperone 6.2.0 - everything worked initially, but after a few weeks i noticed if I did anything like watch a youtube video or download something over a few MBs 90% of the time the data drops (no visible signs like changes from E to H or 3g or the likes, everything looks the same, just that the data stops), toggle mobile data on/off and data connection is back. It worsened and became more frequent over time. Upgraded to Viperone 6.2.1, no difference, so i figured its probably the viperone rom.
Enter Cyanogenmod - http://forum.xda-developers.com/ver...-oneplus-one-stock-rom-cm11s-verizon-t2857425 - and its the same exact issue from the beginning, so im guessing its not to do with the ROM at all (though there are one or two niggling issues with the ROM - cant change BBM display pic, etc)?! I've really tried to comb through the forum and see what makes sense that i could try without bugging y'all - I did a factory reset, wiped everything completely and its the same thing.
I've seen suggestions to similar issues like: flash stock recovery, update radio/firmware/kernel, flash back to custom recovery and some other things which are beginning to sound quite dangerous in my ignorance!! I did believe updating the firmware made sense but after digging deeper, i must honestly say i'm quite confused on what to do. what radio/firmware/kernel works with what software version, etc- most firmware that i've seen are 4.4.3 compatible, while this ROM is 4.4.4., some of them seem to be for stock ROMs only and a lot of other confusions.
So, I'm not gonna be a hero and brick my phone from trying to do what i do not understand, instead here i am, hat in hand, crying out for help after suffering for 3 months! Its really frustrating as, downloads break causing me to lose data, skype or MSLync calls always break and im beginning to look unprofessional to people! This is why I have decided to put up a post of my own specific to my case so i don't medicate for someone else's ailments. So please........ WHAT EXACTLY DO I DO??
PHONE DETAILS (typing it out as i've just realized on this ROM i can't take screenshots with Power+Home button combo anymore and can't be bothered at this point!!!)
ANDROID VERSION: 4.4.4
BASEBAND VERSION: 1.12.41.1112_2
KERNEL VERSION: 3.4.82-gfe09065; [email protected] #1; Wed oct 8 01:36:03 PDT 2014
BUILD DATE: SUN AUG 3 23:00:51 PDT 2014
BUILD NUMBER: CYANOGENMOD 11S v5 (Verizon)
SELinux status: Enforcing
Thanks

Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.

Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).

Uzephi said:
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Click to expand...
Click to collapse
Thanks for the responses folks, i'll try out your suggestions and revert..

8100
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:

Mr HaRR said:
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Click to expand...
Click to collapse
FALSE ALARM FOLKS!!! I decided to attempt flashing the CM11 rom i just uninstalled and it worked. Turns out its a known issue with the .zip file for that rom - i am now re-downloading from another mirror. Meanwhile the Fastboot thing was just a driver issue - though i'm surprised because i had all the drivers installed on the system and have used fastboot successfully - anyway i reinstalled the drivers and all was well with fastboot again.
NB: Don't get tired of me just yet please!

brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?

Mr HaRR said:
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Click to expand...
Click to collapse
If doing factory reset from stock recovery doesn't fix it, it is most likely a burned SIM. It has happened to me. (Average 150+ GB a month in data, so I burn em easily)
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.

ccarr313 said:
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
Click to expand...
Click to collapse
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!

Mr HaRR said:
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Click to expand...
Click to collapse
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.

dottat said:
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
Click to expand...
Click to collapse
HA! and now i feel :silly: !!
Bless your soul! i'll give it a go shortly...

n00b here, Google isn't helping [SOLVED]

So I think I just bricked my phone... I tried to update my phone by reinstalling the stock recovery as per this video:
https://www.youtube.com/watch?v=PPPT5J8xG6w
After updating, the phone got stuck on the error screen. I was able to go back into recovery and go back to the home screen. After some googling, I found this:
http://forum.xda-developers.com/htc-one-m8/help/ota-lollipop-update-fails-red-triangle-t3015597
So I followed the steps and unrooted my phone and tried again. After the update, my phone won't go past the splash screen. I tried going into recovery and wiping the phone and rebooting, but it never gets past the splash screen. Help please!

CID-ROGER001
HBOOT-3.19.0.0000
RADIO-1.25.21331147A1.06G
OpenSDP-v48.2.2-00564-M8974_FO.1211
OS-4.20.631.3
eMMC-boot 2048MB

If you can flash an ruu then I would suggest flashing a stock latest Rogers ruu and starting from there

danial.aw said:
If you can flash an ruu then I would suggest flashing a stock latest Rogers ruu and starting from there
Click to expand...
Click to collapse
How would I flash and RUU? And where can I find a Rogers RUU? I can only find US/Europe RUUs. Please bear with me, I'm new to all this, but I'm trying to read as much as I can.

Bump
I'm trying method 2 as per SneakyGhost's FUU guide, but my computer is not detecting my phone despite it showing up in the "Safety Remove Hardware and Eject Media" tab (Android 1.0). In addition, the phone is showing FASTBOOT USB when connected. Stuck at a standstill right now.

Just an update on the situation, maybe this will help someone in the future - Progress so far - I was able to flash TWRP 2.8.7.0 as instructed a guide on the Android forums (I wish I could post links!).
Working on getting a rom to flash onto it now... I think I'm getting close...

ChickenOmelette said:
Just an update on the situation, maybe this will help someone in the future - Progress so far - I was able to flash TWRP 2.8.7.0 as instructed a guide on the Android forums (I wish I could post links!).
Working on getting a rom to flash onto it now... I think I'm getting close...
Click to expand...
Click to collapse
Same issue as you right now. Attempting to download a nandroid backup and then push it to my phone via fastboot and restore using TWRP and see if that works. Let me know how you make out.

essteekay said:
Same issue as you right now. Attempting to download a nandroid backup and then push it to my phone via fastboot and restore using TWRP and see if that works. Let me know how you make out.
Click to expand...
Click to collapse
Unfortunately, I didn't even have a backup - I'm having enough trouble getting the damn thing to boot!

ChickenOmelette said:
Unfortunately, I didn't even have a backup - I'm having enough trouble getting the damn thing to boot!
Click to expand...
Click to collapse
I managed to get a nandroid 4.4 backup onto my device and restored it. Worked and now my phone is back up and running and going through the rigmarole of updating apps and restoring my media/data backups.

essteekay said:
I managed to get a nandroid 4.4 backup onto my device and restored it. Worked and now my phone is back up and running and going through the rigmarole of updating apps and restoring my media/data backups.
Click to expand...
Click to collapse
Who is your carrier? And where did you get this Nandroid backup?

ChickenOmelette said:
Who is your carrier? And where did you get this Nandroid backup?
Click to expand...
Click to collapse
Fido, but my CID is Rogers001 (same network, probably that's why).
I used this thread as reference.
Downloaded the 3.34.631.4 - TWRP Recovery Nandroid from the CID Rogers001 part. Here's a direct link to the Nandroid backup.
From there, I unzipped the file and then transferred it to my M8 using my SD card (you can also push it straight to the device if using fastboot). I used the file manager in TWRP to move it into my backup folder (TWRP > Backup > Serial Number) in TWRP and then restored it.
Let me know if you've got any other questions. Seems to be working for me right now.

essteekay said:
Fido, but my CID is Rogers001 (same network, probably that's why).
I used this thread as reference.
Downloaded the 3.34.631.4 - TWRP Recovery Nandroid from the CID Rogers001 part. Here's a direct link to the Nandroid backup.
From there, I unzipped the file and then transferred it to my M8 using my SD card (you can also push it straight to the device if using fastboot). I used the file manager in TWRP to move it into my backup folder (TWRP > Backup > Serial Number) in TWRP and then restored it.
Let me know if you've got any other questions. Seems to be working for me right now.
Click to expand...
Click to collapse
Seems like amazing news. Hopefully this works. Apparently after this is done the OTA has to be applied? Is that your next step? Will you be flashing a rom after your firmware is updated?

ChickenOmelette said:
Seems like amazing news. Hopefully this works. Apparently after this is done the OTA has to be applied? Is that your next step? Will you be flashing a rom after your firmware is updated?
Click to expand...
Click to collapse
Right now, just going to keep things as is. I'm in a location with pretty spotty internet, so downloading 1+ GB ROMs isn't that easy. Probably just keep it so that I can use my device and then tinker on it when I'm back at home. I was notified that the Android 5.0.1 update is available for download, but right now I'm holding off doing anything else.
I'm just glad I got it back to working order now.

Here's what I got told to do:
If you want to properly update your firmware via FUU, you have to get to a stock rooted rom, stock recovery, s-off using Sunshine, apply the SuperCID mod, and then update your firmware. After that, reinstall TWRP and whatever modern rom.
Click to expand...
Click to collapse
After doing all this, I tried updating the phone from the Rogers pushed update. Unfortunately, that pushed me back to step 1, where the phone wouldn't boot up, so I had to start from scratch. Now that I have SuperCID, I'm going to try to apply a stock OTA from another carrier. Wish me luck!

So I started from scratch and the Rogers update just doesn't want to work. Every time it updates, it would show the red HTC error icon. I ended up taking the update off the phone's internal memory, as it could still boot, and pushing it via Method 2 seen in this guide as a reference. After pushing flashing (it took two times), the update finally installed, BUT it STILL GOT STUCK AT THE DAMN BOOT SCREEN.
At this point, I got frustrated and went straight to flashing a custom ROM as per the instructions given here. After long moments of waiting, it finally started installing. Very important to note, but I got stuck at the AROMA installer at the "Please Wait" screen. After pressing the power button and vol up, the got out of that screen and continued to install. Now I have a custom ROM, updated firmware and SENSE 7.0! Amazing. I hope that this post helps you in what you'll have to do next!
I blame Rogers for pushing out s***ty updates. But consider this problem SOLVED.