Develop Bugs

ALL AOSP Roms FAIL, Help

I don't post here often, but I am on IRC all the time for those of you that do know me. I have been having serious issues with the AOSP Roms. Cyanogen, Ruby, and Incredible Does all either freeze on me or reboot sooner or later. I've went so far as to install nothing else except the Rom and it still freezes or reboots. I've done this test with all three, I even dialed down the processor while on them and still NO DICE. I'm not an Android expert, but I do have a bachelor's in IT so I feel I'm pretty tech savvy. I was told on IRC that others are having similar problems with all the AOSP roms. I'm trying to get a consensus of who else is experiencing this and some more suggestions on how to fix this.
I appreciate all the help
~Thanks , AnthonyKash

Yeah this is very odd. A couple of us in ##incredibleroms have been working with AnthonyKash to figure this out. So far we have had no luck at all. No Sense UI ROMs do this to him, it seems like it's only vanilla ROMs. Very strange............

anthonykash said:
I don't post here often, but I am on IRC all the time for those of you that do know me. I have been having serious issues with the AOSP Roms. Cyanogen, Ruby, and Incredible Does all either freeze on me or reboot sooner or later. I've went so far as to install nothing else except the Rom and it still freezes or reboots. I've done this test with all three, I even dialed down the processor while on them and still NO DICE. I'm not an Android expert, but I do have a bachelor's in IT so I feel I'm pretty tech savvy. I was told on IRC that others are having similar problems with all the AOSP roms. I'm trying to get a consensus of who else is experiencing this and some more suggestions on how to fix this.
I appreciate all the help
~Thanks , AnthonyKash
Click to expand...
Click to collapse
I know you posted this months ago but was wondering if you figured out what is causing this? I too can't use ANY aosp Rome because they all end up being unusable after a couple of hours. It's almost like the CPU slows down to a dramatic crawl. Only way to fix is to do a battery pull to reset. I have cleared cache, dalvik, uninstalled setcpu, all with no luck. Anyone have any insights?

Check integrity and space of SD card - maybe even remove, copy contents to PC, reformat to FAT32, copy a few nandroids back to SD and reinstall in device. Also make sure there is ample space on SD.
Absent that, have you tried a different SD card? AOSP ROMs interface w/ the SD considerably more than Sense ROMs.
Also, check radio version - recommend at least 2.15.xx
HBOOT version may come into play as well.

+1 to the above post. Seems like some sense files are bring left somewhere.
Sent from my ADR6300 using XDA App

smtom said:
Check integrity and space of SD card - maybe even remove, copy contents to PC, reformat to FAT32, copy a few nandroids back to SD and reinstall in device. Also make sure there is ample space on SD.
Absent that, have you tried a different SD card? AOSP ROMs interface w/ the SD considerably more than Sense ROMs.
Also, check radio version - recommend at least 2.15.xx
HBOOT version may come into play as well.
Click to expand...
Click to collapse
I don't think its my SD Card, I just got a new one a month ago and the same thing happened with my old SD Card. I have 4 gigs left empty of a 16 gig sd card. Would it make a difference if I installed from EMMC using RA recovery?
Hboot 0.92
Radio 2.15.00.09.01
Am on the latest versions of Hboot and radio right?

One thing I do find very weird is that even after doing full wipes of user data, cache and dalvik, when I boot up on CM7 my wifi settings still work. I would have expected I needed to reenter all of those settings. Or does this stuff get saved to the SD or internal storage...normal? If it is not, then why are data wipes in Recovery not cleanning up my files?

I've not had this problem.
Sent from my ADR6300 using XDA App

greatchief1 said:
I don't think its my SD Card, I just got a new one a month ago and the same thing happened with my old SD Card. I have 4 gigs left empty of a 16 gig sd card. Would it make a difference if I installed from EMMC using RA recovery?
Hboot 0.92
Radio 2.15.00.09.01
Am on the latest versions of Hboot and radio right?
Click to expand...
Click to collapse
Yep, those are the latest versions.
AOSP ROMs offer automatic reinstall of apps and data to Google when flashing, if that option is checked when flashed. That's where/how/why settings and/or apps still appear as before.
So, if Sense ROMs are not wonky, maybe it is an app you have installed on the AOSP ROM?
Long diagnostic road, (well understood by us IT folk ) but perhaps uninstall apps in reverse install date order of the app, reboot as you go thru, see which one may have been a culprit.
Absent that, perhaps factory reset in recovery, install an AOSP rom w/out choosing to reinstall apps.
Maybe try another different AOSP ROM?
I know the SD interacts quite a bit more with the SD compared to Sense ROMs - again, maybe copy SD card contents to PC, reformat SD to FAT32 either on the PC or in phone, maybe both - then d/l an AOSP ROM on a clean SD, see if it's still wonky.

smtom said:
Yep, those are the latest versions.
AOSP ROMs offer automatic reinstall of apps and data to Google when flashing, if that option is checked when flashed. That's where/how/why settings and/or apps still appear as before.
So, if Sense ROMs are wonky, maybe it is an app you have installed?
Long diagnostic road, (well understood by us IT folk ) but perhaps uninstall apps in reverse install date order of the app, reboot as you go thru, see which one may have been a culprit.
Absent that, perhaps factory reset in recovery, install an AOSP rom w/out choosing to reinstall apps.
Click to expand...
Click to collapse
Sense ROMS work great, its AOSP roms that are giving my phone fits lol. Well last night I tried something new.
-I changed my radio from 2.15.00.09.01 to 2.15.00.07.28 Official Froyo radio.
-Installed CM7 #14 from the EMMC versus SD CARD.
-"Hit Wipe All" in recovery about 10 times in a row before I flashed CM7
I hope changing the radio to "official" is what does it. Anyone running AOSP roms using the leaked radio 2.15.00.09.01 ?

Radio?
Yes, do let us know whether the xx.09 radio was the (a) culprit.
I run the older 2.15.xx.07.28 one, never had issues w/ AOSP ROMs.

I had an issue with this using cm7 nightlies, and I WOULD post it there but the new, ~totally awesome~ rule they are implementing (can't post in the dev forum w/ less than 10 posts) prevents me from doing that (Which means I have to spam the other sub forums?).
ANYWAYS, I got a bigger sd card from a friend, and I went to erase it under the sd card settings. Then i got a low space notification, saying I had 9 mb free of 7 Terbytes. Rebooting the phone caused it to go into boot loop. If your situation sounds like mine then do this
Boot into CWM, and from there you can mount the SD card and format it, as well as copy any backups.
I did not have any luck with restoring the phone to a previous AOSP rom, even after wiping the cache/dalvik. Maybe there's another one that could be wiped that I didn't do. Anyways, I installed a Sense based rom, and from there I was able to install Cyanogen mod.
Good luck.

smtom said:
Yes, do let us know whether the xx.09 radio was the (a) culprit.
I run the older 2.15.xx.07.28 one, never had issues w/ AOSP ROMs.
Click to expand...
Click to collapse
Well it turns out that the radio version I was using was not the issue because the phone became unresponsive this morning when I tried to wake it up. To be specific, it does allow me to swipe to unlock but painfully in slow motion.
So that rules at the radio...which leaves me with its either the ROM/Kernel or some rogue app.
So this morning I wiped all user data in recovery and reinstalled CM7#14 but this time I did not log on to my google account during setup and have not installed any apps. So far no issues, but the true test is trying to wake the phone up tomorrow in the morning. If there are no issues, then that solves it (ITS A FREAKING APP).
If it is a rogue app that has been haunting me these past couple of weeks then who has the best way to identify which one is the offender? Why would a rogue app only affect me using AOSP roms and not Sense?
My suspicions are with..(Locale, Beautiful Widgets, ADW EX, Swype, CardioTrainer, Handcent) but I guess process of elimination is what its going to take.
Thanks to all for the help and recommendations.

cougar618 said:
I had an issue with this using cm7 nightlies, and I WOULD post it there but the new, ~totally awesome~ rule they are implementing (can't post in the dev forum w/ less than 10 posts) prevents me from doing that (Which means I have to spam the other sub forums?).
ANYWAYS, I got a bigger sd card from a friend, and I went to erase it under the sd card settings. Then i got a low space notification, saying I had 9 mb free of 7 Terbytes. Rebooting the phone caused it to go into boot loop. If your situation sounds like mine then do this
Boot into CWM, and from there you can mount the SD card and format it, as well as copy any backups.
I did not have any luck with restoring the phone to a previous AOSP rom, even after wiping the cache/dalvik. Maybe there's another one that could be wiped that I didn't do. Anyways, I installed a Sense based rom, and from there I was able to install Cyanogen mod.
Good luck.
Click to expand...
Click to collapse
Please tell me u meant 7gb not 7tb
If you have a SD card that huge I beg you to tell me where to get it
I've heard of a 2tb SD but they haven't released it
Sent from my Incredible using XDA App

just wanted to give an udate on my issue...as I suspected it was an app that was causing my phone to crash using aosp roms. The offending app is Locale, wierd that a it never gave me problems using Sense based roms.

greatchief1 said:
just wanted to give an udate on my issue...as I suspected it was an app that was causing my phone to crash using aosp roms. The offending app is Locale, wierd that a it never gave me problems using Sense based roms.
Click to expand...
Click to collapse
Good stuff. Glad to see it all finally worked out.

Gingerbread on Droid Pro with Unlocked Froyo Radio

So, as people know, the newest builds of CM7 or CM9 by JackpotClavin require it to be placed on top of a fully updated Gingerbread Droid Pro. However, those of us with a US Band unlocked radio can't do that without losing our unlocked radio since there is no unlocker for the gingerbread radio. Based on what Axl did for the Droid 2 Global, I've created a gingerbread kernel based on the Droid Pro to allow us to install gingerbread roms while maintaining our unlocked radios. I've also created a clockworkmod backup that can be used as is, or as a base for installing another gingerbread rom such as CM7. Thanks to JohnS and dettofatto, the kernels and clockworkmod backups were updated to 4.7.3. Below are the Resources and the Process.
Resources:
1) RDS Lite (http://forum.xda-developers.com/showpost.php?p=19390783&postcount=1)
2) SBF 2.26 (http://db.tt/5gKwCQwF)
3) TBH Radio Unlocker (http://goo.gl/6NuuG - http://www.mediafire.com/?9pfbk846tjb5a36)
4) Root (http://www.psouza4.com/Droid3/)
5) Droid 2 bootstrap (http://www.mediafire.com/?g8l7vy0futbc4g5)
6) Kernel (US http://www.mediafire.com/?swv4bl7wa47mpxg or EU http://www.mediafire.com/?w6963rmkvdqmro1)
7) ClockworkMod Backup (Verizon US http://www.mediafire.com/?yhr4b768qbnyote or European http://www.mediafire.com/?wn3pyy5fw3i1nr2)
8) Optional Roms - CM7 for Droid Pro (http://goo.gl/M6e4s) or Apex for Droid Pro (http://goo.gl/sTwSp)
Process:
1) Boot to Recovery & Wipe Data (R+M+Power)
2) Boot to Bootloader (Up+Down+Power) & SBF to 2.26 (Using RSD Lite & SBF file) - Usually I have to copy SBF File to root of Hard Drive & name it 2026.sbf or it may fail (ymmv)
3) Skip Activation (http://goo.gl/n2Zhw)
4) Settings->Applications, Set Unknown Sources and USB Debugging (in development)
5) Root
6) Install Bootstrap apk, open, press 'bootstrap recover'. then 'reboot recovery' to boot to recovery mode.
7) While in recovery mode, and without rebooting at all:
...a) Wipe Data
...b) Install Radio Unlock
...c) Install Kernel
...d) Restore Clockworkmod backup (you should have extracted the clockworkmod zip so the folder is located on your sdcard at [ie clockworkmod\backup\...] folder (with the system.img and other images under that folder))
8) Optional - Install cm7, apex or other rom you download
9) Reboot
Notes:
1) You can build your own Clockworkmod recovery file by following the JackpotClavin link below and then just backing up your build. It won't have signal while you're doing it (because of the locked radio), but after you restore it later using the above steps, it'll be fine.
2) Your SIM needs to be unlocked from verizon (i used sim-unlock.net) to work.
3) Info on an Argentinian 2.3.6 rom here
Credits:
JackpotClavin - CM7 for Droid Pro (http://goo.gl/M6e4s)
Axl - Created the Droid2 Kernel which allowed me to use the same method for the Droid Pro (http://goo.gl/ErLAR)
dettofatto - Clockworkmod backup and kernel for European 4.7.3
JohnS - Clockworkmod backup and kernel for Verizon US 4.7.3
Good Luck!

hey im from argentina, here we have Motorola Pro which is the same as droid pro but it doesnt use cdma, it uses gsm and hsdpa. Can i install this on my phone or will it turn to a nice brick?
now i have ANDROID 2.2.2 and it says that the phone is the xt610 same as the droid pro.
thanks
edit: i just followed your source (jackpotcalvin) and it says it should work with gsm but there are still issues

bveditz, thanks for your work.
i have a droid pro (unlocked, verizon branded).
right now i'm using android v2.2 because the TBH radio hack only works with this version. i didn't dare doing any updates because of that. lol. i have one questions.
my phone is already sim unlocked.
so with this new CM7 build, can i just flash and use it without doing the TBH radio hack all over again?

chagla said:
bveditz, thanks for your work.
i have a droid pro (unlocked, verizon branded).
right now i'm using android v2.2 because the TBH radio hack only works with this version. i didn't dare doing any updates because of that. lol. i have one questions.
my phone is already sim unlocked.
so with this new CM7 build, can i just flash and use it without doing the TBH radio hack all over again?
Click to expand...
Click to collapse
Yes, you don't need to unlock the radio, you can start from step 5 (or 6 if its already rooted) and just skip the part about running the radio unlock. Running the radio unlock again doesn't hurt anything either.
Just a word of note, I don't know how the froyo build is by default (i didn't use it), but the current CM7 build still has the issue with switching between mobile data and wifi data, and mobile data can also cut out at times. All that info is in the CM7 discussion, but it's worth noting that the Droid Pro CM7 Build isn't a final build and might not function with the same stability as the Froyo build did. This has nothing to do with this process, it's just the current state of the CM7 rom at the moment. Flashing APEX might produce better results with the radio, but you lose features of CM7, although it has a number of its own features.

installed it. i just started with step 7C. so far so good.
radio is working. sim is still unlocked.
so far i've found one thing, maybe i didn't see the setting yet. the keyboard back lights aren't working?

chagla said:
installed it. i just started with step 7C. so far so good.
radio is working. sim is still unlocked.
so far i've found one thing, maybe i didn't see the setting yet. the keyboard back lights aren't working?
Click to expand...
Click to collapse
No, with that issue and the wifi/radio issues (loosing connection and not being able to switch between the two) , I switched over to the APEX ROM, it's more stable. You don't get the features of CM7, but it has less bugs. Might want to try that. You don't need to do anything different, just put the apex file on your SD, reboot to clockwork mod and wipe data and reflash.

is it possible to use this in some way to have band unlock and normal ginerbread without cm7

Yes. You need to basically upgrade Gingerbread to the full release, root it and do a nandroid backup. Then, you follow the steps in the first post but instead of restoring the nandroid backup of CM7, you install the nandroid backup of regular gingerbread that you made yourself.

bveditz, thanks, that is along the lines of what i was thinking might work after reading the directions... Im already running tbh rooted gingerbread... Do i need to sbf and upgrade to a clean gingerbread, or can i nandroid backup what i already have and then retain all my settings and apps so i dont have to start over. Has anyone noticed any disadvantage to useing the older radio besides the obvious advantage of being able to use the band unlock?

Excellent tutorial!!
EXCELLENT TUTORIAL GUYS. Also, you should make sure to mention after installing bootstrap, press 'bootstrap recover'. then 'reboot recovery' option. I did that, installed the kernal and restored backup fine.
Only issue so far was a -20% battery decrease randomly. I had 100% with a brand new battery fully charged for the first time and when I finished installing cm7 I was already on 80%, then dropped to 70% on a reboot or two, its weird. Anyone else had this happen? I heard the apex 2.0 rom did it to someone else as well on another forum
Also, do you guys know how to get back the blur social network apps such as friendfeed, or whichever app it was that adds your friends social network updates to their contact numbers on your contacts? Most people don't like it, but I think its a pretty awesome built in feature

jxs714 said:
EXCELLENT TUTORIAL GUYS. Also, you should make sure to mention after installing bootstrap, press 'bootstrap recover'. then 'reboot recovery' option. I did that, installed the kernal and restored backup fine.
Only issue so far was a -20% battery decrease randomly. I had 100% with a brand new battery fully charged for the first time and when I finished installing cm7 I was already on 80%, then dropped to 70% on a reboot or two, its weird. Anyone else had this happen? I heard the apex 2.0 rom did it to someone else as well on another forum
Also, do you guys know how to get back the blur social network apps such as friendfeed, or whichever app it was that adds your friends social network updates to their contact numbers on your contacts? Most people don't like it, but I think its a pretty awesome built in feature
Click to expand...
Click to collapse
Thanks, made the note to the tutorial. I haven't noticed the issue with the battery, but I do know that this is one of those roms that seems to jump in increments of 10 for the battery which is kinda weird. That said, i only used it about a week on CM7 before switching over to the Apex rom (and haven't noticed that issue on the apex rom).
Don't know about blur, I didn't use the original OS at all. That said, you can do what the guy above did and wipe the phone, upgrade all the way to gingerbread, do a nandroid backup then follow the original instructions but use that backup to restore to, which should have the full motoblur functionality. Thats just a guess though, haven't tried it myself.

------------------

Could you re-up just the Kernel file? I've followed your instructions to the T and every time it seems that I have a problem at that step.
I've gotten to Flashing the Kernel VIA CWM, and when I try to restore the backup of CM7 via \clockworkmod\restore\ folder - it will say MD5 mismatch.
Also, if I skip the restore portion of CM7 and just try to reboot the phone after flashing the Kernel, I will be stuck at the red M.
I've tried rebooting the phone right after applying the band unlock (all after SBF + Wipe data), and the phone will boot up just fine if I skip flashing the Kernel (again I leave it in zip form and install it via CWM).
I’ve already unlock my SIM via code provided by VZW (I am a VZW customer in good standing)
While stuck at the red M, I’ve done a battery pull and tried to enter Recovery mode by pressing M+R+Power, and the recovery screen that is booted up doesn’t look like it’s compatible with the phone. I can almost describe it as a bunch of white horizontal lines of what the menu should be, and all the menus and the green android are skewed diagonally to the right/and also looks like it’s double or triple vision.
I know a very similar process works for the D2G, because I have successfully performed and tested it on the D2G on one of my other lines.
Any help is greatly appreciated. I can stick with Froyo, but I’d like to have GB.

Try redownloading the CM7 backup, it might be a corrupted download. If that doesn't work, try the APEX file. But, yes, you cannot reboot without restoring a gingerbread backup or you'll have to start over again (there's ways to get back to the cwm but i'm not sure how, I did it accidently a few times).

Thanks I am a complete noob
So it turns out the problem is when I unzipped the Backup that it created sub folders "\nandroid\restore\xxxx\xxx\backup\restore\"
Just to save everyone headaches, make sure the when you unzip the file into your backup folder that the name of the next folder down is the series of numbers that represent the name & number i.e.
Should NOT be
\clockworkmod\backup\clockworkmod\clockworkmod\backup\2011-11-27.09.52.03\
but instead SHOULD BE
\clockworkmod\backup\2011-11-27.09.52.03\
My 7zip by default created all those sub directories, which caused the CWM restore not to find the back up files.
On another note, I am having issues with GSM Wifi and 3G.
With a fresh flash & WiFI on - if I connect WIFI first I cannot later add the APN and access Cellular Data
Inversely, If I add the APN first (again after a fresh SBF flash, kernel update, and Backup restore), and connect to cellular data, none of the WIFI connects I make can access WIFI Data
I am going to try WIFI fixer in one of the older threads to see if this resolves the problem.

DROID PRO
Please upload the file in other downloads bc megaupload is temp down

agni said:
Please upload the file in other downloads bc megaupload is temp down
Click to expand...
Click to collapse
If you're talking about the two multiupload files I put up, use one of the other links below megaupload. I just tried the bottom one (wupload) and it worked. If you're talking about RSD Lite and SBF files, I'll see if I can find another link to them, but you can easily find them by searching the forums or google.
**Edit** Edited first post with non-megaupload links.

jraskal said:
On another note, I am having issues with GSM Wifi and 3G.
With a fresh flash & WiFI on - if I connect WIFI first I cannot later add the APN and access Cellular Data
Inversely, If I add the APN first (again after a fresh SBF flash, kernel update, and Backup restore), and connect to cellular data, none of the WIFI connects I make can access WIFI Data
I am going to try WIFI fixer in one of the older threads to see if this resolves the problem.
Click to expand...
Click to collapse
Let me know how that worked out. I stopped using CM7 and switched to Apex because of the Wifi/Cellular switching issues of the november cm7 rom.

bveditz said:
Let me know how that worked out. I stopped using CM7 and switched to Apex because of the Wifi/Cellular switching issues of the november cm7 rom.
Click to expand...
Click to collapse
Can you provide a link to the Apex rom you're using?

aaevann said:
Can you provide a link to the Apex rom you're using?
Click to expand...
Click to collapse
Theres an apex thread on xda that links to the rom http://forum.xda-developers.com/showthread.php?t=1292506

Wildfire Bootlooping When Mobile Data Turned On

Hi guys,
I've done a fair share of searching but it seems nobody is having the same issues
Basically, I thought i'd try out these new tweaks I found, the V6 Supercharger and the 3G Turbocharger from zeppelinrox - The V6 installed fine and was running smoothly but when i installed the faster version of the 3G turbocharger sent my phone into a bootloop (it eventually came back on to my relief). My HTC Wildfire is now thrown into a bootloop every time i enable mobile data. WIFI works fine.
I have reflashed my ROM, wiped data and dalvik cache, but when i flash the G_apps, the phone goes into the boot loop - and thats after a full wipe and reboot (i have now restored a backup - but the issue is still apparant)
Another thing worth mentioning is my local.prop file is empty and i'm not sure if this should contain any script.
Any help appreciated. Phone Spec below.
Thanks
Phone Model: HTC Wildfire Buzz
Android Version : 2.3.7
Rom: Cyangoen Mod-7.1.0.1-Buzz
Kernal: 2.6.35.14-nFinity [email protected] #1
Radio: 3.35.15.31
Baseband: 13.45.55.24U_3.35.15.31
Hboot: 6.01.1002
S-OFF
V6 Supercharger - Unsupercharged
3G Turbo Charger - Uncharged

This was caused by the 3G / V6 Script:
http://forum.xda-developers.com/showthread.php?t=1015532&page=200
Read Post #1998 onwards (The next 2 Pages as well). You have to clean wipe and install another ROM (Not restoring anything from your existing setup), and if it still doesn't work, use an RUU to go back to the Stock ROM and then come back to whichever ROM you are using.

Fix for bootloop after 3g turbocharger script install
FIX:
Ran an RUU for wildfire.
- Downloaded (RUU_Buzz_HTC_WWE_1.14.405.2_R_C_Radio_13.45.55.24_ 3.35.15.19_release_141106_signed) from android forums.
- Connected phone to PC and ran RUU
- This downgraded phone OS to eclair (android 2.1)
- Let it do the bizniss
- Had to re-root with unrevoked 3
- Re-Flashed CM7 and gApps
All ok
I'll say one thing, CM7 doesnt need a v6 or a 3G super/turbocharger. It works fine without them. The minfree values are set at an ok level and I always have HSDPA signal. Its not worth the effort.

Yeah after carefully tweaking this and that - all one change after the other and testing a lot before going on - I've been pretty much satisfied with my old buzz. Until I decided to give that 3G Supercharger a try (because of 3G didn't ever work really good - the only thing I was not completely satisfied with)...
It turned out that there hasn't been any improvement from my perspective so I just reverted the settings and went on.
It took me 2 weeks to find out where the bootloops suddenly came from (1 day to narrow down the prob had to do with switching on data and at least 10 days for the 2g/3g part).
Is there anybody who can explain more specific a) what causes this behaviour and b) what would be necessary to eliminate the cause (and probably avoid it in the future)
I won't get misunderstood but just "do an RUU update" sounds a bit like the standard no.1 suggestion "format and re-install" in all those amateur winsucks forums...
3xeno said:
This was caused by the 3G / V6 Script:
http://forum.xda-developers.com/showthread.php?t=1015532&page=200
Read Post #1998 onwards (The next 2 Pages as well). You have to clean wipe and install another ROM (Not restoring anything from your existing setup), and if it still doesn't work, use an RUU to go back to the Stock ROM and then come back to whichever ROM you are using.
Click to expand...
Click to collapse
Thanks for the hint but even after reading all the related posts several times I don't feel enlighted somehow (besides the information that I don't need any super charge scripts with CM - which I'm half the way to be convinced of )

noone? I just want to find out what exactly is the problem (to avoid it in the future) and I'm really curious why a complete wipe doesn't help. The Supercharger scripts just tweak values in config files (correct me if I'm wrong) - so if the problem is caused by the script(s): why can't it be solved by simply revert those changes (or replace the files by the default ones)?

Fix for bootloop after 3g turbocharger script install
eventcom
Did you find anything more about this problem?
I have the boot loop after using 3g/4g optimizer from the market, but I can get partial network use if I enable only 2g and not 3g. Better than nothing while I see if it can be fixed without a RUU.
Just wondering if a RADIO flash may solve the problem.
Regards.
Phone Model: HTC Wildfire Buzz
Android Version : 2.2.1
Rom: Stock
Kernel: [email protected] #1
Radio: 3.35.20.10
Baseband: 13.55.55.24U_3.35.20.10
Hboot: 6.01.1002
S-OFF

st3v3droid said:
Did you find anything more about this problem?
Click to expand...
Click to collapse
nope unfortunately not, but it seems, that the problem still occurs - see in this thread or here in that one - I've given it another try to flash radio again - with no help. The information about changed values in build.prop isn't new to me (as I did expect something like that) - what I don't know is which values exactly and how to overwrite them (if too many) when flashing a new rom...

So I went a bit deeper into the build.prop and made a simple diff against the build.prop of October 2011 (has been an earlier nightly and that problem definitely didn't occur at that time).
The only differences were those:
This looks like a simple addition for identification
Code:
+++ ro.cm.device=buzz
Perhaps that's a better guess (looks like this had been added sort of randomly anyway? - qualifies):
Code:
+++ # For PDP overlap problem
+++ ro.ril.avoid.pdp.overlap=1
That shouldn't harm anything:
Code:
+++ # update the acoustic table for Buzz NEL lab testing
+++ ro.ril.update.acoustic.table=1
My own changes which didn't cause any trouble before:
Code:
--- dalvik.vm.heapsize=24m
+++ dalvik.vm.heapsize=32m
+++ ro.compcache.default=0
That shouldn't have to do with the problem, too:
Code:
+++ persist.sys.rotationanimation=false
+++ persist.sys.scrollingcache=2
but that one probably?:
Code:
+++ # Lock dirty_ratio to 20 when USB is mounted for improved transfer speed
+++ ro.vold.umsdirtyratio=20
So I simply commented out the stuff I guessed to be responsible (no. 2 and 6) and restarted - no success. Reboots again when turning on 3G

I get the same problem, Had CM7 running fine with no problems but started to get bootloops upon upgrading to CM9.
Found a temp fix by reflashing radio but the problem seems to come back sporadically using any cm mod (haven't tried stock yet)
Any ideas?

Doddster said:
I get the same problem, Had CM7 running fine with no problems but started to get bootloops upon upgrading to CM9.
Found a temp fix by reflashing radio but the problem seems to come back sporadically using any cm mod (haven't tried stock yet)
Any ideas?
Click to expand...
Click to collapse
that sounds exactly like LucidSomnia's report in the thread I've used to continue with my experiences. I can't tell if my solution (if it was any and not by accident) will help you but it shouldn't hurt to give it a try...

Tried pretty much everything, flashed several different versions of Buzz Radio, tried factory resets, data wipes.
I would guess it as a kernel or firmware error and it *must* be fixable, just like the camera.
P.S The camera works occasionally, I get viewfinder but no way of taking picture and if I install the 3rd party app Line camera I can take pictures with no viewfinder.

Doddster said:
Tried pretty much everything, flashed several different versions of Buzz Radio, tried factory resets, data wipes.
I would guess it as a kernel or firmware error and it *must* be fixable, just like the camera.
Click to expand...
Click to collapse
As you can see in my posts (in three threads) I've done a lot of stuff, too, what did the trick in the end (if it was not just by accident) was
Total/full/mega wipe (except SD card)
mounts & storage / boot, cache, system, data, sd-ext
advanced / dalvik-cache
main menu / wipe all (factory reset)
flash a fresh ROM
flash a different radio (older one in my case)
Boot
after that just the same procedure
mounts & storage / boot, cache, system, data, sd-ext
advanced / dalvik-cache
main menu / wipe all (factory reset)
flash a fresh ROM
flash a different radio (newest in my case)
It might be possible, that it would have worked to just flash the older radio / wipe caches / boot / flash the newer radio - no idea, but the actions in the exact order above have been successful for me (after trying a lot of things).
But just to make sure (because you're talking about CM9 I guess): my problem has been that the phone did bootloops every time and immediately when I turned on 3G data. No exceptions, nothing occasionally or random. With different Versions of CM7 (older nightly, RC, stable and newer nightly). And just 3G. Everything else did work like a charm.
If that's the case with you I'd give my method a try and if that doesn't work I'd do an RUU (the safe flash variant first of course).

eventcom said:
It might be possible, that it would have worked to just flash the older radio / wipe caches / boot / flash the newer radio - no idea, but the actions in the exact order above have been successful for me (after trying a lot of things).
But just to make sure (because you're talking about CM9 I guess): my problem has been that the phone did bootloops every time and immediately when I turned on 3G data. No exceptions, nothing occasionally or random. With different Versions of CM7 (older nightly, RC, stable and newer nightly). And just 3G. Everything else did work like a charm.
Click to expand...
Click to collapse
Yes mate! So far so good! No bootloop when enabling mobile data, even after reboots (with mobile data left on)
Steps followed:
(In recovery)
Wipe Cache,
Factory Reset.
Flashed CM7
Flashed Radio (3.35.19.25) using CMrecovery 2.5.0.7
Thanks eventcom
**Dunno if I'm gonna have the balls to install CM9 again after all this

Doddster said:
Yes mate! So far so good! No bootloop when enabling mobile data, even after reboots (with mobile data left on)
Click to expand...
Click to collapse
glad to hear that it helped
**Dunno if I'm gonna have the balls to install CM9 again after all this
Click to expand...
Click to collapse
I'm not really sure about what exactly caused the problem (at my side at least) - but even if CM9 on the Wildfire is highly experimental this particular problem doesn't look to me that it has to do with the ROM. I slightly remember a few people having this problem after flashing a different ROM but in most cases this could be solved by a simple restore. Did you also use some tweaks - like a different kernel, RAM scripts or something similar?

nope, nothing different from what was included on the CM7 and CM9 builds. :/
It's frustrating as ICS actually runs ok on the wildfire, it's only till it hits the radio or camera hurdles it lets itself down lol
I'm getting another phone soon so I will be using my Wildfire for development and I'll put all my effort into helping us wildfire'ers run ICS with no hassle.

Im gonna stick my neck out here, all the incidents ive come across regarding the issues raised have involved one, some or all 3 aspects
1.overclocking too high.
2. V6 supercharger scripts.
3. Cm9
Could be coincidence or could be the reason!
Forum fishing.... Who's biting!

CM9 in my case, it's defo something to do with the radio.
I have no probs running max clock on CPU and I haven't touched other scripts

Doddster said:
CM9 in my case, it's defo something to do with the radio.
I have no probs running max clock on CPU and I haven't touched other scripts
Click to expand...
Click to collapse
Have you ever had the problem with the radio outside of cm9?
Ive never tried cm9 nor had issue with any of my radios but have had bootloops when i tried the v6 scripts back in my early days.
Forum fishing.... Who's biting!

slymobi said:
all the incidents ive come across regarding the issues raised have involved one, some or all 3 aspects
1.overclocking too high.
2. V6 supercharger scripts.
3. Cm9
Click to expand...
Click to collapse
Yes, on the other hand overclocking can be the reason for almost every problem LOL - same goes with the highly experimental stuff. I'm not following the CM9 and ICS threads explicitly but I stumble over them here and there. I mean I appreciate that some people (I mean users not devs) are willing to flash and test a ROM where 25% of the hardware can't be used almost reliable - because in the end there might be a useful port (e.g. of CM9) for our GPU-less Wildfire. But I use my phone on a daily basis and don't have the time to flash it twice a day (+/- 5 LOL) and to hunt for errors.
Regarding the V6SC: That's why I would like to have an (Android/CM) expert look into it. I suspect there might either be a conflict of the script with important system stuff, an unknown trigger of something technically harmful or simply a hidden bug which doesn't affect many users - but that's just one more theory. Maybe there's something happening deeper in the hardware which is triggered by a combination of situations (e.g. could have to do with the s-off-ing or rooting process).

]Yes, on the other hand overclocking can be the reason for almost every problem LOL - same goes with the highly experimental stuff. I'm not following the CM9 and ICS threads explicitly but I stumble over them here and there. I mean I appreciate that some people (I mean users not devs) are willing to flash and test a ROM where 25% of the hardware can't be used almost reliable - because in the end there might be a useful port (e.g. of CM9) for our GPU-less Wildfire. But I use my phone on a daily basis and don't have the time to flash it twice a day (+/- 5 LOL) and to hunt for errors.
Regarding the V6SC: That's why I would like to have an (Android/CM) expert look into it. I suspect there might either be a conflict of the script with important system stuff, an unknown trigger of something technically harmful or simply a hidden bug which doesn't affect many users - but that's just one more theory. Maybe there's something happening deeper in the hardware which is triggered by a combination of situations (e.g. could have to do with the s-off-ing or rooting process).
Click to expand...
Click to collapse
I try to follow all threads here in wildfire as well as a handful outside and like i said the main 3 factors mentioned above are nearly always present or come to be eventually
I dont think it will ever be pinpointed or whittled down to just one reason due to there being so many possible causes/possible triggers. I can however say from my own experiences that ive not had a single bootlooping issue since the day i removed and never again used any v6/juuwes enhancing scripts. I keep my processor at 633 max,264 min ondemand/smartass, my readahead sd speed never over 1024(516 is my preference, to limit sd errors) set on any rom i use.
I always unzip the rom and study within to edit, mod, remove certain elements i desire/dont need or want prior to flashing it.
This way i have the setup i want and need for my own personal liking.
Regards slym.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse

[Q] Need help w/ Runnymede AIO install

This is my first post, otherwise I would have posted in the Runnymede AIO dev forum. It actually is two parts.
1. I have searched many threads and still can't find a fix for my problem. I tried to install Runnymede AIO four times yesterday. My phone is S-off, rooted, etc. I have what the installer says is a stock HBOOT, but it has the "Revolutionary" banner on the bootloader screen. Every time I installed and rebooted it would hang on the white "HTC" screen. I wiped the phone every time I reinstalled as well. I have the EXT4 Recovery. I tried the reboot into recovery, then reboot from there trick, and it still got stuck. I really want to use this ROM, but I can't get it to install correctly. Anybody have any suggestions?
2. I tried to change by HBOOT from the Revolutionary HBOOT to the CM7/r2 HBOOT from AlphaRev using Fastboot Commander yesterday. When I did that, it soft bricked my phone so I couldn't see the screen (I am assuming I have a SCLED model). I finally got it fixed and ended up finally just restoring my Nandroid backup. Do I need to use the downgrader before trying to flash a new HBOOT, or would something else cause that?

Well, I found the superb troubleshooting guide from bortak (and thanked as well!) and tried flashing CyanogenMod. It went without a hitch. I tried Runnymede AIO again. Stuck on boot. So, I thought I would try Runny Rom. Same thing. Why would it be that I can get CM to flash but not a Sense ROM?

grillheadxl said:
Well, I found the superb troubleshooting guide from bortak (and thanked as well!) and tried flashing CyanogenMod. It went without a hitch. I tried Runnymede AIO again. Stuck on boot. So, I thought I would try Runny Rom. Same thing. Why would it be that I can get CM to flash but not a Sense ROM?
Click to expand...
Click to collapse
have you tried post#4 from Runnymede AIO thread, the detailed FAQ and installation guides in PDF format?
my immediate guess it that you don't have an ext partition set up on sd card, as i don't think you've mentioned one. CM does not require one to boot, but Runnymede AIO does.
well done for solving one of the problems yourself, many ppl can't find that troubleshooting guide for some reason...

What exactly are you Doing. Don't get clumsy write down step by Step what procedure your followed.

tehTerminator said:
What exactly are you Doing. Don't get clumsy write down step by Step what procedure your followed.
Click to expand...
Click to collapse
For the Runnymede AIO install, I followed the 4EXT Recovery and Runnymede AIO installation sheets to the T. I did every step that was shown in them, including making a 1024mb EXT4 partition on the SD card, which showed when I checked the partition tables. I did a complete install from those sheets at least twice and it still would not move past the white screen. I let it set for 1 1/2 hours and it didn't move on.
For the HBOOT flashes I used Fastboot Commander as well as tried flashing from fastboot in the SDK. I was wanting to flash the CM7/r2 HBOOT so I could get the AD2SDX function.

My guess would be the ext partition of the sd card is acting up. When you format it using 4ext recovery did you pick the option to save your fat32 partition? If that was the case, backup your sd card contents to a computer and use 4ext to format the entire card this time including the fat32 partition. Pnce complete put your files back in the card and flash again.
via xda app

stankyou said:
My guess would be the ext partition of the sd card is acting up. When you format it using 4ext recovery did you pick the option to save your fat32 partition? If that was the case, backup your sd card contents to a computer and use 4ext to format the entire card this time including the fat32 partition. Pnce complete put your files back in the card and flash again.
via xda app
Click to expand...
Click to collapse
The first time I formatted and flashed, I backed up to the computer, formatted the entire sd card, and transferred everything back. After that I have done it both ways when trying to flash again, with the same result.

I don't know if this makes a difference or not, but I thought I'd throw out there that I have a CDMA Desire (US Cellular).

After digging around, I think I have found that the CDMA is most likely what my issue is. I found this post ( http://forum.xda-developers.com/showthread.php?t=1476469 ) that says Runnymede AIO is GSM. If that's what the problem is, that really stinks because that ROM looks awesome! I don't remember the threads about the ROM saying if it was compatible with CDMA or not (in fact I only remember one mentioning it with a patch, and I've read that the patches don't even work). So, is there a list or something that I've missed that tells what works with CDMA?

Runny from seb is pure gsm, have look at runny from coolexe he is/was doing CDMA patch, both have same base
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App

kotag82 said:
Runny from seb is pure gsm, have look at runny from coolexe he is/was doing CDMA patch, both have same base
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App
Click to expand...
Click to collapse
I may give it a try. I think the Sense ROMS look really really nice is the main reason I am trying to hard to get this to work.

grillheadxl said:
I don't know if this makes a difference or not, but I thought I'd throw out there that I have a CDMA Desire (US Cellular).
Click to expand...
Click to collapse
grillheadxl said:
After digging around, I think I have found that the CDMA is most likely what my issue is. I found this post ( http://forum.xda-developers.com/showthread.php?t=1476469 ) that says Runnymede AIO is GSM. If that's what the problem is, that really stinks because that ROM looks awesome! I don't remember the threads about the ROM saying if it was compatible with CDMA or not (in fact I only remember one mentioning it with a patch, and I've read that the patches don't even work). So, is there a list or something that I've missed that tells what works with CDMA?
Click to expand...
Click to collapse
Ahh, yes, you'll often find such minor details left out of your OP to be the ones that are the biggest problem.
Sorry, you cannot use Runnymede with CDMA. There are actually only a very few ROMs made for CDMA devices, but if you search "CDMA" in the Dev section, you will definitely find something you can use.
PS, you may like to know that yes, Runnymede is an awesome ROM!!

Well, I installed Cool3d Runny v7 last night in CDMA mode. Still ended up stuck on the white screen. Guess I'll try Runnymede007 with the patch next...

Did you full wipe before install??
Also, occasionally, you might get a bad download, so might be worth dl'ing again, just to be sure...

Yep, did full wipe. I forget what the error was it showed. I'll try dl'ing it again. I just finished trying to work with RunnymedeMod007. I can't get the script edited for the CDMA patch. Needless to say, I am getting very frustrated.

unfortunately I've found that some of the CDMA patches don't work like they say they do
(in fact I've found one and that was the ics bcm)
make sure you have the right partition sizes that they want for the rom to work
use cMTD to change partition sizes:
http://forum.cyanogenmod.com/topic/23984-guide-to-installing-cmtd/
DONT USE ANOTHER HBOOT
if that didn't work check with the dev and see if the patch actually includes a bravoc kernel. if not it has a very very slim chance of working
if it doesn't work after that i have no answers
if resolved and working please post what you did so others may do the same

I'll see what I can do. For RunnymedeMod007 it says to delete a line from the script. I unzip the file, edit in Wordpad, zip the file, and save to SD. When I try to run it ai get an error. The zip has a root folder inside of it. Any idea what I'm doing wrong, or how else to edit the wcript and see if the patch works?

Edit script with Notepad++
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App

Tried using Notepad++ to edit and it took out the script, but I can't get it to save back into the zip file. Tried zipping the entire file and ended up with the "file-in-file" problem again.

Ok, I redownloaded RunnymedeMod007, verified the MD5, unzipped it, edited out the line as he said to do, zipped the file, signed it with AndroidSigner, moved to SD, and, it failed. Whenever I zip the file, it makes the "Runnymede etc" zip file, then if I open it, there is another file inside with the same name, and if i open it, then all the info is there. I can't get it to zip without that extra folder inside, and I think that's the problem with this installation.
Also, I tried downloading Cool 3D Runny and doing a CDMA install with it again. I got it installed, but it hung at the white HTC screen again. I gave up after it was that way for an hour and did a battery pull.
The HBOOT partitions are all set to stock sizes, EXT4 partition set at 1024mb and aligned.

Help.... I ran a root tweak app... Phone won't boot. I need a solution...

I had an app installed called Android Tweaker Pro (or something like that). It was a legitimate Play Store App [although it was later removed along with many other apps as Google wanted to eliminate apps that had "Android" in the app name.] However, the real problem is that it was a root app and it was originally designed for Kit Kat.
I had not really touched it since I upgraded to Lollipop, and when I was running Kit Kat, it worked great... it has numerous tweaks (mainly to build.prop), however, in the past, I typically used an option in the app called "auto tweaker" which changed a certain set of variables. It was a safe route, as it clearly warned you up front not to enable all of the tweaks.
Well, I opened it tonight, and changed a few settings... I believe I changed/increased the video fps, and I think I optimized the LED flash, and I also enabled the "Power Supply", which the app explained reduced battery use if it was turned on.. But I don't think any of those things were really that big of a deal.
However, there are two more things I did that may be the cause of my problems:
ONE: I foolishly set the Dalvik Heap SIze to 0K. (I think it had a max of 512K). I don't know why I did that exactly... I think I assumed Dalvik wasn't being used in Lollipop, so I thought it would free up memory.... it was a total clueless move I realize, and of course feel like an idiot.
SECOND: I zipaligned all of my apps. I didn't think to look up if zipaligning apps was necessary anymore... which was also foolish I realize.,
Anyway, after it finished zipaligning my apps, I rebooted. The splash screen and then the T-Mobile animation ran but then froze at the HTC ONE screen. I powered it off a few times and tried to restart again—but there was no change... My phone was just frozen at that boot screen after the animation.
I booted into recovery, and the only thing I did was rename the Android Tweaker "base.apk" to "base.apk.bak", but I didn't really think that would help. I also tried to find the build.prop file to see if by chance the tweaker app made an automatic backup so I could restore it....but had no luck finding it the build.prop file at all... It doesn't seem to be where it used to be prior to Android 5.
So what I am hoping to do is find out where Lollipop keeps its build.prop file (or whatever it's equivalent is now)...and see if there was a backup made and restore it. IF not, then I am looking for suggestions.
On the other hand, if this is because I zipaligned all of my apps.... then I have no idea what to do.... Please offer suggestions. I will be eternally grateful!!!
Note: I think I can do a factory restore, but I cannot lose what is on my extended storage, so unless I can backup extended storage using adb (which I would think doubtful given I cannot boot into the phone), I really, really do not want to do a factory reset.
My sincere appreciation in advance for any help suggested!!!!!!!!
EDIT: If it helps at all, I am currently S-Off (with an unlocked bootloader), and I have an old nandroid backup. It is pre-Lollipop upgrade. SO...absolute worst case scenario (aside from losing my phone altogether), is to restore Kit Kat, and then do the OTA again...restore all my apps, etc. But I cannot imagine there is just some file I could delete using TWRP recovery that would be regenerated upon boot.
If I had to restore the KIT Kat nandroid and do the OTA, it would just take several hours...And it is 5:00am where I am and I need to use my phone by 8am.... SO, I hope someone has some alternative. I would settle for a way to back up my extended storage, and then somehow push a rooted nandroid of lollipop on the the storage and restore that with TWRP....
Any other ideas are appreciate of course!!!!!!!!!!!!!!!

syntropic said:
I had an app installed called Android Tweaker Pro (or something like that). It was a legitimate Play Store App [although it was later removed along with many other apps as Google wanted to eliminate apps that had "Android" in the app name.] However, the real problem is that it was a root app and it was originally designed for Kit Kat.
I had not really touched it since I upgraded to Lollipop, and when I was running Kit Kat, it worked great... it has numerous tweaks (mainly to build.prop), however, in the past, I typically used an option in the app called "auto tweaker" which changed a certain set of variables. It was a safe route, as it clearly warned you up front not to enable all of the tweaks.
Well, I opened it tonight, and changed a few settings... I believe I changed/increased the video fps, and I think I optimized the LED flash, and I also enabled the "Power Supply", which the app explained reduced battery use if it was turned on.. But I don't think any of those things were really that big of a deal.
However, there are two more things I did that may be the cause of my problems:
ONE: I foolishly set the Dalvik Heap SIze to 0K. (I think it had a max of 512K). I don't know why I did that exactly... I think I assumed Dalvik wasn't being used in Lollipop, so I thought it would free up memory.... it was a total clueless move I realize, and of course feel like an idiot.
SECOND: I zipaligned all of my apps. I didn't think to look up if zipaligning apps was necessary anymore... which was also foolish I realize.,
Anyway, after it finished zipaligning my apps, I rebooted. The splash screen and then the T-Mobile animation ran but then froze at the HTC ONE screen. I powered it off a few times and tried to restart again—but there was no change... My phone was just frozen at that boot screen after the animation.
I booted into recovery, and the only thing I did was rename the Android Tweaker "base.apk" to "base.apk.bak", but I didn't really think that would help. I also tried to find the build.prop file to see if by chance the tweaker app made an automatic backup so I could restore it....but had no luck finding it the build.prop file at all... It doesn't seem to be where it used to be prior to Android 5.
So what I am hoping to do is find out where Lollipop keeps its build.prop file (or whatever it's equivalent is now)...and see if there was a backup made and restore it. IF not, then I am looking for suggestions.
On the other hand, if this is because I zipaligned all of my apps.... then I have no idea what to do.... Please offer suggestions. I will be eternally grateful!!!
Note: I think I can do a factory restore, but I cannot lose what is on my extended storage, so unless I can backup extended storage using adb (which I would think doubtful given I cannot boot into the phone), I really, really do not want to do a factory reset.
My sincere appreciation in advance for any help suggested!!!!!!!!
Click to expand...
Click to collapse
By extended storage do you mean SD card?? If so just take it out and do the factory reset.

3484jacks said:
By extended storage do you mean SD card?? If so just take it out and do the factory reset.
Click to expand...
Click to collapse
No... Extended storage is not a separate SD card, it is a partition for storage. The HTC One (m8) has a 32 GB extended storage partition (I think it is a partition anyway). It is not however, a physical SD card (although one can be purchased to expand the storage).

So you're S-OFF and rooted but running a fully stock ROM? I would just download the full version of whatever ROM you're using and dirty flash it over everything, it should at least fix your build.prop and any other tweaks that might be lingering. Obviously a full wipe and reinstall would be the safest way to go.

Ok mate. If your rooted use titanium back up or my back up pro to back up the contents of your phone storage then do the factory reset or restore a stock nandroid from the stock back up thread.

thebobmannh said:
So you're S-OFF and rooted but running a fully stock ROM? I would just download the full version of whatever ROM you're using and dirty flash it over everything, it should at least fix your build.prop and any other tweaks that might be lingering. Obviously a full wipe and reinstall would be the safest way to go.
Click to expand...
Click to collapse
This is what I would suggest. All tweaks seem to be to the ROM, so dirty flashing the ROM should fix it.
OP should have made a nandroid before doing any tweaks of this nature. Not sure why so many folks skip this step. It takes about 5 minutes and saves a lot of headaches.

thebobmannh said:
So you're S-OFF and rooted but running a fully stock ROM? I would just download the full version of whatever ROM you're using and dirty flash it over everything, it should at least fix your build.prop and any other tweaks that might be lingering. Obviously a full wipe and reinstall would be the safest way to go.
Click to expand...
Click to collapse
redpoint73 said:
This is what I would suggest. All tweaks seem to be to the ROM, so dirty flashing the ROM should fix it.
OP should have made a nandroid before doing any tweaks of this nature. Not sure why so many folks skip this step. It takes about 5 minutes and saves a lot of headaches.
Click to expand...
Click to collapse
YES YES... I am regretting this... I have been rooting Androids since 2010, and I know better!!! But this app has been so familiar to me, plus i just spaced out on the backup....
OK to both of you (two previous replies)... BUT I CANNOT BOOT INTO THE OS... I AM LIMITED TO TWRP only!
How do I get a nandroid on extended internal storage... I tried to connect via ADB while in fastboot mode... no luck.

syntropic said:
No... Extended storage is not a separate SD card, it is a partition for storage. The HTC One (m8) has a 32 GB extended storage partition (I think it is a partition anyway). It is not however, a physical SD card (although one can be purchased to expand the storage).
Click to expand...
Click to collapse
I've never heard of internal storage referred to as extended storage. In fact ExtSD refers to the removable MicroSD card.
I would suggest calling it internal storage to avoid confusion.
---------- Post added at 11:01 AM ---------- Previous post was at 11:00 AM ----------
syntropic said:
YES YES... I am regretting this... I have been rooting Androids since 2010, and I know better!!! But this app has been so familiar to me, plus i just spaced out on the backup....
OK to both of you (two previous replies)... BUT I CANNOT BOOT INTO THE OS... I AM LIMITED TO TWRP only!
How do I get a nandroid on extended storage... I tried to connect via ADB while in fastboot mode... no luck.
Click to expand...
Click to collapse
Try adb in TWRP. adb won't work in fastboot or hboot by definition. It normally works within OS or in recovery.
Alternately, you can use a removable SD card and a USB card reader connected to your computer, put the ROM on the card. Then insert into the phone and flash in recovery.

redpoint73 said:
I've never heard of internal storage referred to as extended storage. In fact ExtSD refers to the removable MicroSD card.
I would suggest calling it internal storage to avoid confusion.
---------- Post added at 11:01 AM ---------- Previous post was at 11:00 AM ----------
Try adb in TWRP. adb won't work in fastboot or hboot by definition. It normally works within OS or in recovery.
Alternately, you can use a removable SD card and a USB card reader connected to your computer, put the ROM on the card. Then insert into the phone and flash in recovery.
Click to expand...
Click to collapse
OK, so if I use adb in TWRP, I should get my device to show up when I enter:
adb devices
?
Then I push the nandroid to internal storage? And to what directory exactly??? I apologize, I just have never had to do this before...
The HTC ONE m8 has the capacity to purchase an additional external SD card (which I don't have).... But I suppose I could get one if that would make it easier...

syntropic said:
OK to both of you (two previous replies)... BUT I CANNOT BOOT INTO THE OS... I AM LIMITED TO TWRP only!
How do I get a nandroid on extended storage... I tried to connect via ADB while in fastboot mode... no luck.
Click to expand...
Click to collapse
ADB won't work in fastboot mode, fastboot will though (ie "fastboot devices" should show your device). If you boot into TWRP, however, you should see your device in ADB.
Then you can push either your NANDROID if you want to go all the way back to that, or a ROM that you downloaded to your PCif you want to do what we suggested.
Can you not see your device via ADB when you're in TWRP?
EDIT : Sorry, slow on the draw. Push teh file to wherever you want, you just have to browse to it via TWRP when you try to install.
> adb push filename.bin /sdcard/
would be the way I'd go. Then wehn you try to "install" in TWRP you don't have to look too far

thebobmannh said:
So you're S-OFF and rooted but running a fully stock ROM? I would just download the full version of whatever ROM you're using and dirty flash it over everything, it should at least fix your build.prop and any other tweaks that might be lingering. Obviously a full wipe and reinstall would be the safest way to go.
Click to expand...
Click to collapse
Also... to add another reply to this... I wouldn't mind so much if I had to do a full wipe and reinstall.... BUT this would wipe my internal storage... If I could back this up, then I might do that.. I will try to connect via ADB with TWRP running.

syntropic said:
I wouldn't mind so much if I had to do a full wipe and reinstall.... BUT this would wipe my internal storage... If I could back this up, then I might do that..
Click to expand...
Click to collapse
Try a dirty flash first (just wipe Dalvik and cache). If you still run into issues, full wipe and flash.

redpoint73 said:
Try a dirty flash first (just wipe Dalvik and cache). If you still run into issues, full wipe and flash.
Click to expand...
Click to collapse
OK... Last Question before the dirty flash... This is on my Bootloader screen
MB_UL PVT SHIP S-OFF
CID-T-MOB010
HBOOT-3.19.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4
eMMC-BOOT 2048MB
Feb 2 2015, 19:07:09.0
I never did SuperCID, so do I need to get a stock firmware download from the TMO M8 forum? And also, why is the stock ROM better than a stock nandroid? Just curious.
I am trying to do this fast as I need my phone now to make an important call... so my thinking isn't very lucid and fluid.

thebobmannh said:
Can you not see your device via ADB when you're in TWRP?
EDIT : Sorry, slow on the draw. Push teh file to wherever you want, you just have to browse to it via TWRP when you try to install.
> adb push filename.bin /sdcard/
would be the way I'd go. Then wehn you try to "install" in TWRP you don't have to look too far
Click to expand...
Click to collapse
Yes, I'd suggest the "top" directory of your internal storage as well, when you adb push the ROM. The ROM can go anywhere on internal storage, you just need to navigate to the proper location in TWRP. So putting it in the top means less typing for the adb path (and therefore less chances for error), and less taps in TWRP to navigate to the ROM.
Another option is adb sideload. Which in theory is less steps (pushes the ROM and flashes it with a single adb command): http://teamw.in/ADBSideload
But in my experience, adb push is more reliable then sideload. I've had (and seen others with the same) sideload fail for no apparent reason, while adb push works fine.
---------- Post added at 11:28 AM ---------- Previous post was at 11:23 AM ----------
syntropic said:
And also, why is the stock ROM better than a stock nandroid? Just curious.
Click to expand...
Click to collapse
Stock ROM can be placed anywhere on internal storage. Nandroid has to be pushed to an exact location in the TWRP backup folder (which includes your serial number). Otherwise TWRP won't see it when you select "Restore". You can navigate to the proper zip when you select "Install" (flash a ROM), which you can't do for "Restore" (nandroid).
Getting the exact path right (for adb push) for the nandroid is more complicated. I've seen lots of folks here who have had trouble with this.

syntropic said:
OK... Last Question before the dirty flash... This is on my Bootloader screen
MB_UL PVT SHIP S-OFF
CID-T-MOB010
HBOOT-3.19.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4
eMMC-BOOT 2048MB
Feb 2 2015, 19:07:09.0
I never did SuperCID, so do I need to get a stock firmware download from the TMO M8 forum? And also, why is the stock ROM better than a stock nandroid? Just curious.
I am trying to do this fast as I need my phone now to make an important call... so my thinking isn't very lucid and fluid.
Click to expand...
Click to collapse
Installing a stock ROM will just install the OS, while a stock nandroid may blow away your apps (I'm not entirely positive on that). If the ROM matches the ROM you were using before you shouldn't have to worry about updating firmware or anything.

thebobmannh said:
Installing a stock ROM will just install the OS, while a stock nandroid may blow away your apps (I'm not entirely positive on that). If the ROM matches the ROM you were using before you shouldn't have to worry about updating firmware or anything.
Click to expand...
Click to collapse
OH yeah... of course... Nandroid backs up all of the apps.... OK.. Well I am all for flashing a stock ROM.
Now... my only problem is that I cannot find one. [Very sorry to ask all these questions... if I wasn't in such a hurry, I would leisurely research this stuff on my own]. But as said, since I am still a TMOB CID, I cannot use a generic ROM from the regular HTC One (M8) forum, correct???
And when I go to the HTC One (M8) T-Mobile forum, I see RUUs, Nandroids, radios, boot.imgs.... but no Stock ROMs.... I posted a question about where they might be in a thread I thought was appropriate at the T-Mobile M8 forum, but do you (or anyone reading this), know where I might find a 4.20.531 Stock Rom for TMO???
Again, my sincerest apologies for asking for all this spoon-feeding.... I would never ask these things if it wasn't bordering on an emergency (a job issue)....
EDIT: OK I found what I think is a TMO stock ROM... but this is a nomenclature issue, and I am not very adept at it... IS AN RUU the same as the STOCK FIRMWARE/ROM? I ask because the only time I ever used an RUU was when it was an exe windows file, and it wiped/reset my entire device....

syntropic said:
OH yeah... of course... Nandroid backs up all of the apps.... OK.. Well I am all for flashing a stock ROM.
Now... my only problem is that I cannot find one. [Very sorry to ask all these questions... if I wasn't in such a hurry, I would leisurely research this stuff on my own]. But as said, since I am still a TMOB CID, I cannot use a generic ROM from the regular HTC One (M8) forum, correct???
And when I go to the HTC One (M8) T-Mobile forum, I see RUUs, Nandroids, radios, boot.imgs.... but no Stock ROMs.... I posted a question about where they might be in a thread I thought was appropriate at the T-Mobile M8 forum, but do you (or anyone reading this), know where I might find a 4.20.531 Stock Rom for TMO???
Again, my sincerest apologies for asking for all this spoon-feeding.... I would never ask these things if it wasn't bordering on an emergency (a job issue)....
P
Click to expand...
Click to collapse
ROM shouldn't care about your CID, tha'ts for firmware and all that. Any ROM that works on GSM will likely work for T-Mo.
An RUU will wipe your entire device.
---------- Post added at 11:50 AM ---------- Previous post was at 11:46 AM ----------
By the way I know you're in a rush, but rushing is how you make bigger mistakes. I'd try and borrow someone's phone for your important call so you can carefully do what you need to do and not brick your phone or lose all your data.

thebobmannh said:
Installing a stock ROM will just install the OS, while a stock nandroid may blow away your apps (I'm not entirely positive on that).
Click to expand...
Click to collapse
When you restore a nandroid, you can select which partitions you do or don't want to restore, by checking or unchecking the boxes as desired. You can restore /system without restoring /data. Not sure, but I also believe the nandroids in the stock collection do not include /data partition backups.
Really, the main difference is getting the adb push path correct for a nandroid is a bit more complicated (but not impossible by any means) than a stock ROM.

thebobmannh said:
ROM shouldn't care about your CID, tha'ts for firmware and all that. Any ROM that works on GSM will likely work for T-Mo.
An RUU will wipe your entire device.
---------- Post added at 11:50 AM ---------- Previous post was at 11:46 AM ----------
By the way I know you're in a rush, but rushing is how you make bigger mistakes. I'd try and borrow someone's phone for your important call so you can carefully do what you need to do and not brick your phone or lose all your data.
Click to expand...
Click to collapse
Yes...wise words... But, I am really in an usual situation. Kinda of isolated at the moment.... but I will slow down nonetheless.
OK... In this HTC One (M8) generic forum, there is this thread/post...
http://forum.xda-developers.com/showpost.php?p=51836733&postcount=4
It says it is a stock ROM zip for MAC users? What??? Why would there be a difference between a stock ROM for macintosh and windows??? This is really confusing me more than I ever anticipated.....

If you want to save your internal storage data, the simplest way that I can see :
a) Install latest TWRP 2.8.5.0 where you can mount the Internal storage in MTP mode
b) Download the stock nandroid backup here : https://mega.co.nz/#!7JgQ2DJL!Ko33MVU49EyS__r7BqS3qYWFF02faKab19VkBYhI-F0
c) Transfer the extracted nandroid backup to your TWRP.BACKUP/SerialNo/folder
d) you can try to restore only partition part first or together with boot, so you have your data ... just do wipe dalvik & cache after restore system and restart