I'm wondering if its possible to partition my sd card so that half of it can remain baked snack with everything I have set up then the other half to cm6 final then just flash the roms and kernels from the applicable side when I want to run it. So essentially I have 2 to choose from each with their own backups ext...
Possible?
Kinda like a dual boot box... Is there an app for that?
I don't really want an app for it. I think that would end up slowing the system down substantially. I just want to be to choose a partition flash the rom from that partition then do a nand restore for that rom(located on same partition) and have that side of my sd card already set for that particular rom.
cool idea. for now I just nand restore when I want to switch back and forth but it takes a bit of time. If it was as quick as rebooting to another partition that would be hot.
That's very possible. We dualboot our pc from Windows to Linux so should not be impossible. Someone just needs to make it work.
Sent from my PC36100 using XDA App
Maybe I'll suggest it in the Dev section someone in there will have the know how to get this done.
well the rom doesnt install to the sdcard. hence the reason you can format the sdcard and still have a working phone. it installs to the phones internal memory.
your best bet is to do what is stated above. do a nandriod of the roms you want, setup how you want and a titanium backup of each to restore your settings.
So I can't just partition it and have 2 different "sides" for each roms information like I can't tell Baked Snack to look at "A:" and CM6 to look at "B:"? are we sure about this? Maybe even partition the memory inside the phone to 2 different roms then choose 1 from boot loader? Think I'm going to try to post something in dev section and hope they won't get too angry at me.
You know, i think the main reason this hasn't been discussed before is that previous phones didn't have the nand capacity to hold multiple roms that you would switch between. Even at 512mb it is pushing it depending on how many apps you are going to have installed on the phone on each rom that aren't going to be insstalled to sd.
Well I have 270 free on the phone and I still haven't moved every app I can over to the SD cdard. I think Cyanogen is smaller then most other roms the Zip is only 70 mb compared to baked snack wich is 170, well over double. I think it would be pretty easy to have enough space. This may hinder performace if internal memory is completely maxed out though, not quite sure.
wy1d said:
cool idea. for now I just nand restore when I want to switch back and forth but it takes a bit of time. If it was as quick as rebooting to another partition that would be hot.
Click to expand...
Click to collapse
Yeah thats what I doo I have Fresh 3.1.0.2 and CM6 and I just restore depending on my mood.
I originally posted this in the Q/A section but no one seemed to have any reasonable answer.
Is it possible to partition my SD card so I can have baked snack on 1 half and CM6 on the other with all their user options ect.... saved to that respective side of the card? I'm not really wanting a true dual boot here but I would like to maybe nand backup my backed snack save it to backed snack's partition. Then flash cm6 and kernel ect.. and already have all my apps settings in place. Or maybe even partition the internal mem so we could have a true dual boot. Is it possible to partition the internal mem and perhaps mess around with the boot loader in order choose which partition you will be booting from?
crimeslunk said:
I originally posted this in the Q/A section but no one seemed to have any reasonable answer.
Is it possible to partition my SD card so I can have baked snack on 1 half and CM6 on the other with all their user options ect.... saved to that respective side of the card? I'm not really wanting a true dual boot here but I would like to maybe nand backup my backed snack save it to backed snack's partition. Then flash cm6 and kernel ect.. and already have all my apps settings in place. Or maybe even partition the internal mem so we could have a true dual boot. Is it possible to partition the internal mem and perhaps mess around with the boot loader in order choose which partition you will be booting from?
Click to expand...
Click to collapse
Did you try using both NAND and Titanium backups? If you make two backups, one for each ROM, you should be able to recover everything fairly easily when you want to go back and forth.
I suppose it would be possible. Stuff would load pretty slow though and you'd have to manually create such a setup. I haven't looked at the bootstrapping, but I can't think of any reason you couldn't mount the data heavy positions from the sdcard. Not easy by most people though.
Sent from my PC36100 using XDA App
i asked for this a few months back and was told to just use rom manager. make backups of both roms and just use that to go between them. dual booting isnt possible with our boot loader.
OP, without getting too "techy", what's being overlooked is the fact that you'd have to get into the BIOS itself end change where it loads the os from for it to work.
Also, in theory, with the os running from the SD card, things like mounting the phone as a disk drive would be impossible without turning the phone off, and that would just suck...
It's a cool idea, but I think having everything draw from.one source would make it lag like hell even, so I dunno.... I don't really get your reasoning behind switching between different roms on a constant basis, but I'd think about the cons too
All spelling errors thanks to xt9 on my Evo!
ricersniper said:
i asked for this a few months back and was told to just use rom manager. make backups of both roms and just use that to go between them. dual booting isnt possible with our boot loader.
Click to expand...
Click to collapse
Sure, but what if they shared the initrd and that was what promoted for the selection?
Sent from my PC36100 using XDA App
I did this with my tp2 had winnow and android on. Had Haret.exe worked great just used a explorer to SD card clicked and loaded up. Also had dual bootup at startup. Picked which rom I wanted to run. Was indeed nice.
Sent from my PC36100 using XDA App
Not to get off op topic but how do you get rid off the nand backups on the phone. Have a few on roms I don't use anymore.
Sent from my PC36100 using XDA App
you can get rid of backups a few ways if you use rom manager you can just go to manage and retore roms long clikc it and select delete. if you dont use rom manager youc an set your device to disck drive while hooked up tot he pc and manually navigate to the back up and delete it.
In reality, you could make as many NAND backups as you want, and restore any of of them from recovery whenever you want!
xHausx said:
Did you try using both NAND and Titanium backups? If you make two backups, one for each ROM, you should be able to recover everything fairly easily when you want to go back and forth.
Click to expand...
Click to collapse
Would you not need to constantly update the nand backups?
Also...if I were to do this with say CM6 and something else...would I have 4G issues from flipping back and forth? I know CM6 doesn't have 4G and want to make sure it's just missing, not that it messed with the radio.
Alrigh then I guess I'll just give up on this and do it the old fashion way with band and titanium back ups. Am I going to need the full version of titanium for this? Will it make the whole process alot quicker?
Hey there -
I have a GN2 and before I get myself into a big mess, I thought I'd ask here. I'm no stranger to CWM and installing new ROMS on my phones, but I am in a new situation here. Since I'm a big space user, I used the script method to change my internal SD and my external SD so I have more space for apps.
I am currently running rooted stock with the multi view update and it works with no problem. The next goal, however, is to install CWM and try out some different ROMS. I know that I may or may not be able to do the SD switch, and that's fine. What I am wondering, though, is if I use CWM to do backups/restores, since the script that changes my SD configuration runs on boot, what do I need to do? Do I need to ditch this setup if I'm planning on doing anything with ROMS?
The ideal situation is that I can get a good backup of my current setup with CWM (or some other method), play with some new ROMS, and be able to go back to my current setup if necessary with as little fuss as possible (and of course, avoiding a brick).
Thanks for the help and advice!
MM
mathman76 said:
Hey there -
M
The ideal situation is that I can get a good backup of my current setup with CWM (or some other method), play with some new ROMS, and be able to go back to my current setup if necessary with as little fuss as possible (and of course, avoiding a brick).
Thanks for the help and advice!
MM
Click to expand...
Click to collapse
Use twrp
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
So, I finally rooted this old phone after all these years with the hopes of deleting a lot of the bloatware. I did, but now I realize that this has only freed up space on my system partition. I have an extra 50mb here. I am assuming there is no way to move space from this partition to my /data partition - even though they are both on the nand.
I searched the forums for a good hour and did not find an answer to this question. Do people use custom roms to avoid having wasted space in their system partition? I'm running the latest stock, which I rooted using htc, and I installed anon ra.
Thanks
mherlihy said:
So, I finally rooted this old phone after all these years with the hopes of deleting a lot of the bloatware. I did, but now I realize that this has only freed up space on my system partition. I have an extra 50mb here. I am assuming there is no way to move space from this partition to my /data partition - even though they are both on the nand.
I searched the forums for a good hour and did not find an answer to this question. Do people use custom roms to avoid having wasted space in their system partition? I'm running the latest stock, which I rooted using htc, and I installed anon ra.
Thanks
Click to expand...
Click to collapse
Read this whole thread.... http://forum.xda-developers.com/showthread.php?t=1386911 ,then at the bottom of post 2 you will see some links,use the ones you need and yes you can free up space with DT's app2sd.
.. and to answer your specific question, a small amount of unused space in /system is normal and necessary. As you install more and more apps you may see this overhead decrease slightly. (Indeed, your OP indicates you have already observed this process in reverse.) You can get by with less than 10 megs. Because it is not available for any other use, anything much more than that is basically wasted space.
There was once a mod that attempted to realign partitions to reclaim this space. Search Google for "firerat".
The problem with this mod was that no scripts for flashing kernels or ROMs expect a non-standard alignment, which leads to disastrous results unless you remember to undo the mod every time you flash anything.
Note this mod is not much discussed anymore. This leads me to conclude that even if it still works, it's probably not worth the effort.
Sent from my PC36100 using xda app-developers app
Actually many of the long time users still use it. The problem is that the new sense roms eat most of the system partion up. Yet if you use an aosp rom you can get around an extra 100 meg depending on the setup. Also some of the newer scripts give you more space by using an extended sd partition.
I suggest if you are not comfortable flashing with fastboot not to use firerats mod. The mod wont really mess up anything but if you have forgotten you used it than you flash something else you could spend hours or days beating your head against the wall. Also if you change kernels then you have to flash a script to mod the new kernel to properly read the partitions.
To undo the mod you have to flash a new recovery through fastboot then erase partitions and reboot to recovery. Then flash new rom like normal.
Hope this helps you get an idea of what you are going into before you start.
Sent from my PC36100 using xda app-developers app
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