Related
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
kabell4 said:
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
Click to expand...
Click to collapse
Regarding your nightly question, they are full ROMs...the difference between them is the code that was committed within the previous 24 hours. Of course that also means that, in theory, some of the nightlies could be 100% the same...anyway, the nightlies can be a beautiful thing or a disasterous thing...usually if there's an issue with a nightly it is quickly found by those who flash each nightly and it is brought up around 3.2 million times and it is typically fixed by the next nightly.
Partitioning usually does mean a wipe of data on the SD. Careful!
When I upgraded to a 32GB flash from the stock 2GB from my Aria, I backed up the entire contents and restored on the new one. Apparently there is volume information stored somewhere (not sure where) and the phone couldn't recognize the card and asked me to partition it.
Because I had a backup, I decided to do so, but instead of partitioning for the entire size of the chip, it partitioned only 2GB!
So I had to stick it into a reader and repartition it manually and then selectively restore music, etc back on the card.
After that it worked just fine. So short version: yes it does.
kabell4 said:
I tried flashing the Rom yesterday and was successful. The issues I had revolve around restoring my apps. I used My Backup Root for stock to Froyo, but this time it seemed as though the apps were on the phone and the card, which cause an error stating that I didn't have enough memory. What should I have done to restore the apps to preserve the memory? I also received force close error for SetCPU, SlideIt (which I love), and a few others.
Also, what is the benefit of partitioning my sd card and does doing so erase it's current contents?
Lastly, are the nightlies a full rom or just part that needs to be flashed? If found some on CMs website, but not here.?
Yes, I'm a NOOB.
Click to expand...
Click to collapse
You will need to creaate an sd-ext partition to fix the issue of installing (larger) apps with CM7.
The best way would be through ROM Manager.
wifi
Installed the RC2 and can't connect to a hidden SSID wifi network.
That is a known issue with the wifi driver on cm7 thus far. Not sure if it will be corrected though. Anyone else know if it is in the works?
"Do you mind if I turn up the AC?"
I believe if you flash to nightly 14 all will be good, not 100% sure though.
TheFurnace said:
That is a known issue with the wifi driver on cm7 thus far. Not sure if it will be corrected though. Anyone else know if it is in the works?
"Do you mind if I turn up the AC?"
Click to expand...
Click to collapse
As far as I know there are no plans to change it. But then again we weren't supposed to get fm radio working either...
Sent from my cm7 Aria using XDA App
Too true. Never know what is coming down the pipeline!
"Do you mind if I turn up the AC?"
stellarhopper said:
You will need to creaate an sd-ext partition to fix the issue of installing (larger) apps with CM7.
The best way would be through ROM Manager.
Click to expand...
Click to collapse
Great input from everyone. Thanks! Following up on the sd-card partitioning... I have a new 8g card and want to more to CM7. If I partition it, what happens when I restore the backed up app using My Backup Root? And, what is the best partition configuration, why, and what info get store in each section (ext)?
Thanks...
kabell4 said:
Great input from everyone. Thanks! Following up on the sd-card partitioning... I have a new 8g card and want to more to CM7. If I partition it, what happens when I restore the backed up app using My Backup Root? And, what is the best partition configuration, why, and what info get store in each section (ext)?
Thanks...
Click to expand...
Click to collapse
The easiest way to partition is using your ROM manager.
Just select the max size for SD-EXT (I think it would got to 512MB), and none for swap.
I'm not sure if this would have any effect on your backup - I myself started out from scratch and got my apps from the market even though I had made an Astro backup...
You will store all your stuff - music, pictures etc in the normal partition. The SD-EXT will be automatically handled by the phone.
Tried flashing Nightly 22 on my Aria from 17. I spent a lot of time customizing 17. Is there a way to keep all of the old home screens? Also, GPS lock isn't working for me. Using MyBackup Root for Apps, but it seems to duplicate the apps?
kabell4 said:
Tried flashing Nightly 22 on my Aria from 17. I spent a lot of time customizing 17. Is there a way to keep all of the old home screens? Also, GPS lock isn't working for me. Using MyBackup Root for Apps, but it seems to duplicate the apps?
Click to expand...
Click to collapse
You should be able to flash each new nightly without losing any of your settings/customizations/homescreens and apps.
While upgrading from ROM manager, just check the backup option, don't check wipe data and cache.
I can confirm this works transitioning from 14 to 22 because I just did it yesterday night
As for the GPS problem, thats a known issue - the workaround is to make a nandroid backup of your current cm7, then do a complete phone reset, then do a nandroid restore of cm6 or 6.1 (hope you have one), do another factory reset, and restore your cm7 from the backup you took in the 1st step
stellarhopper said:
You should be able to flash each new nightly without losing any of your settings/customizations/homescreens and apps.
While upgrading from ROM manager, just check the backup option, don't check wipe data and cache.
I can confirm this works transitioning from 14 to 22 because I just did it yesterday night
As for the GPS problem, thats a known issue - the workaround is to make a nandroid backup of your current cm7, then do a complete phone reset, then do a nandroid restore of cm6 or 6.1 (hope you have one), do another factory reset, and restore your cm7 from the backup you took in the 1st step
Click to expand...
Click to collapse
first of all, i would never suggest using rom manager for things such as that. historically it has only caused problems and has been more of an inconvenience than anything. second of all, when you boot into CWM and do it the right way, don't wipe data, it's suggested but not necessary that you wipe cache and dalvik, then flash the rom and you'll be good.
Thanks to both of you. Big help and not deleting the data did the trick. Looks like I'm good to go and GPS is working well again. Is there a way to ensure I don't have duplicate apps taking up space on the card and phone? I'm getting errors on moving some apps to the sd card.
kabell4 said:
Thanks to both of you. Big help and not deleting the data did the trick. Looks like I'm good to go and GPS is working well again. Is there a way to ensure I don't have duplicate apps taking up space on the card and phone? I'm getting errors on moving some apps to the sd card.
Click to expand...
Click to collapse
Not all apps can be moved to the FAT32 partition on the SD card. Widgets also, won't work properly if moved to the SD FAT32.
If you need more memory, look into (read up) partitioning your sd card with a ext3 partition and installing S2E or Dark Tremor a2sd (DT a2sd).
zervic said:
first of all, i would never suggest using rom manager for things such as that. historically it has only caused problems and has been more of an inconvenience than anything. second of all, when you boot into CWM and do it the right way, don't wipe data, it's suggested but not necessary that you wipe cache and dalvik, then flash the rom and you'll be good.
Click to expand...
Click to collapse
Oh, I had no idea about that, thanks for the info.
I've been using ROM manager without any problems so far, apart from one lately, that when I reboot to recovery, I always get an error screen - exclamation mark in triangle...but I just pull the battery and reboot into recovery manually and it starts whatever command I had given it (backup/new rom) automatically...
Ok so i was having some laggy issues w the x2 and all the sudden i started getting process not working for things like nova laucher and such. SO i went into BSR to wipe cache and fix the permissions. Did that and now the phone sits on the Big M boot screen. Why wont it boot up. I didnt wipe dat or try to flash anything. Any way to get the phone up and runnig again w/ o SBF'g
jeff5347 said:
Ok so i was having some laggy issues w the x2 and all the sudden i started getting process not working for things like nova laucher and such. SO i went into BSR to wipe cache and fix the permissions. Did that and now the phone sits on the Big M boot screen. Why wont it boot up. I didnt wipe dat or try to flash anything. Any way to get the phone up and runnig again w/ o SBF'g
Click to expand...
Click to collapse
Well what ROM are you using for starters.
that might be important right.. .sorry.. its aokp 6
Ok. Well if you can get back into BSR, try and wipe the dalvik cache in the advance settings. I never use the fix permissions option. Maybe that did something to your device.
did that too. Still on the boot logo. is a sbf in order
jeff5347 said:
did that too. Still on the boot logo. is a sbf in order
Click to expand...
Click to collapse
Well I wouldnt see why it would do that if you just wiped cache and fixed permissions. Did you have any other mods on there? Were you using the patched CM7 BSR and not the original one?
i was using the motodx2_bootstrap_signed.apk. Not sure if the cm7 or not. Ive used this on eclipse and aokp
jeff5347 said:
i was using the motodx2_bootstrap_signed.apk. Not sure if the cm7 or not. Ive used this on eclipse and aokp
Click to expand...
Click to collapse
That one is fine to use on Eclipse. But pretty much any other ROM we have (CM7, CM9, CM10, AOKP, Paranoid Android and I think even MIUI), you need to use the CM7 BSR named "MOTODX2_Bootstrap-CM7-signed.apk" which is found in the CM7 thread. That may have been the problem.
really... damn. i dl'd it so when i flash cm10 but did not install it for thw aokp. Just off your thoughts is the cm10 stable enough now to install. i have no prob putting aokp back on but im nott looking for stability problems. If cm10 isnt stable yet i van wait
jeff5347 said:
really... damn. i dl'd it so when i flash cm10 but did not install it for thw aokp. Just off your thoughts is the cm10 stable enough now to install. i have no prob putting aokp back on but im nott looking for stability problems. If cm10 isnt stable yet i van wait
Click to expand...
Click to collapse
I think CM10 is more stable than any of the ICS ROMs. But with the stability, there comes other small issues that the ICS ROMs dont have. Its a trade off. Main issues of CM10:
1. Messing with bluetooth may cause phone to crash durring calls. Reboot fixes it until bluetooth is messed with again. (Might be fixed with an update)
2. Storage is in a different location. Not really an issue but its also swapped back to the original 4gigs for the internal. All your files will be flipped after using other ROMs for so long. (not a huge deal)
3. Due to the storage being moved around, apps that are stored on the SD card will disappear after reboot. (will probably be fixed in the future)
4. Flashing ROMs in recovery wont work. If any update comes out, you have to either SBF and update or nandroid back to ICS and update. (again, not a huge issue)
Other than that, I cant really think of any bad stuff. Its faster and I have no random reboots. I recommend it if you can live with the issues I mentioned which are honestly not bad.
Also, with the BSR files, in case you dont know already. When you are on stock 2.3.4, you first use the original BSR. Then when you flash CM10, you install the CM7 BSR.
Thanks JS
1. I never use blue tooth so then i should be all set then.. correct?
2. didnt aokp have that. I know the eclipse rom had the flip flop in it to read right but aokp i had to move my music and such so wouldnt i still be in the same boat or is it different than oakp?
3. i have some apps.. such as thems i have downloaded off of xda. So once installed they will work but rebooting will make them dissapear? is there a way to put these on the phone memory? Also curious i have google drive and have some of these installed on the drive. Will they still work or do they just dl to the sd and still not work?
4 i dont have a problem sbf'g but wondering if i nandroid the a2, will i be able to sbf, install root, a3 ect and do a data restore to get my info back?
also i will take the cm7 bsr and remeber that. Thanks
jeff5347 said:
Thanks JS
1. I never use blue tooth so then i should be all set then.. correct?
2. didnt aokp have that. I know the eclipse rom had the flip flop in it to read right but aokp i had to move my music and such so wouldnt i still be in the same boat or is it different than oakp?
3. i have some apps.. such as thems i have downloaded off of xda. So once installed they will work but rebooting will make them dissapear? is there a way to put these on the phone memory? Also curious i have google drive and have some of these installed on the drive. Will they still work or do they just dl to the sd and still not work?
4 i dont have a problem sbf'g but wondering if i nandroid the a2, will i be able to sbf, install root, a3 ect and do a data restore to get my info back?
also i will take the cm7 bsr and remeber that. Thanks
Click to expand...
Click to collapse
1. I use bluetooth every now and then but I never turn it off. It seems that toggling the bluetooth on and off or visa versa triggers the issue and a reboot fixes it again.
2. I forget what Eclipse had. Its been so long. But ever since CM7, the flip flop mod has been included in all the ROMs which meant you got your SD card (which the droid X2 comes with 8GB) as internal storage and the actual 4GB internal storage was turned into the "external storage." CM10 reverted back to the original 4GB internal and 8GB external.
3. Everything you download and install on your phone will usually be installed on the internal storage. I think if you have apps over a certain size (which isnt very many. Mostly games), they are installed on your SD card. Those are the ones the system has a problem reading after a reboot. the actual files you have downloaded from XDA will still be there. Just installed apps might disappear.
4. Not really sure what you are asking here. But if you get A2 installed and up and running and A3 comes out, You will pretty much need to start over. But for me, thats fine. I use Titanium Backup and restore everything after a wipe anyway. What data are you referring to?
ok so this is the gapps md5
MD5sum: f62cfe4a827202899919fd932d5246d7
and gapps-jb-20120726-signed.zip
is this correct
jeff5347 said:
ok so this is the gapps md5
MD5sum: f62cfe4a827202899919fd932d5246d7
and gapps-jb-20120726-signed.zip
is this correct
Click to expand...
Click to collapse
Honestly, I dont even know what MD5sum means. I'm not that tech smart. lol. I know thats the right file name though. And if you got it from here: http://goo.im/gapps you should be fine.
hahaha neither do i lol yea thats where i got it.. again thank you
No problem. If you have any other issues, just reply here and I'll help out.
one last th. sbf'd. trying t oroot with petes like i always have but it wont recognize the phone i enables debugging and unknown sources. Am i forgetting something. havent done this in a bit
jeff5347 said:
one last th. sbf'd. trying t oroot with petes like i always have but it wont recognize the phone i enables debugging and unknown sources. Am i forgetting something. havent done this in a bit
Click to expand...
Click to collapse
Pete's can be a PITA... If usb debug is enabled and unkown sources is checked just keep trying. I've had to "one click" 5 or 6 times before it works right. Close the program between tries. Also make sure your phone isn't in PC charge mode or anything.
Sorry for not updating this. After trying for 2 hrs I started trying everything. It turned out I had to use the cable that came w the dx2. No other cables worked
Sent from my MB870 using xda premium
Ah, my bad I should have read the time stamp. Anyway yea, the cable is a big deal (even though that sounds crazy.)
---------- Post added at 10:54 PM ---------- Previous post was at 10:43 PM ----------
Lol oh and btw MD5 checksums are
"The MD5 checksum for a file is a 128-bit value, something like a fingerprint of the file. There is a very small possibility of getting two identical checksums of two different files. This feature can be useful both for comparing the files and their integrity control."
I've tried several times to install the custom ICS ( [ROM] CM9 / LiquidSmooth / AOKP / Random ICS ), but WiFi is not coming on.
Any ideas how to resolve this?
Better yet, I am trying to flash the latest ICS ROM to my thunderbolt that is stable.
Seems most have some sort of reboot problem
So far I have tried all the Liquid Smooth - very nice ROMs but get random reboot
PS
From about phone, I see the following
Mode version: liquid mecha.mr3.100212
Build number: Liquid ICS v1.5MR3-JMOD
Radio: 2.00.00.0308, 0.02.00.0312r
brochild said:
Better yet, I am trying to flash the latest ICS ROM to my thunderbolt that is stable.
Seems most have some sort of reboot problem
So far I have tried all the Liquid Smooth - very nice ROMs but get random reboot
PS
From about phone, I see the following
Mode version: liquid mecha.mr3.100212
Build number: Liquid ICS v1.5MR3-JMOD
Radio: 2.00.00.0308, 0.02.00.0312r
Click to expand...
Click to collapse
Maybe THIS helps?
I just stumbled unto that site by accident (I love it)
I have registered and downloaded the nusense ROM (Beta v10.8) and will report my findings.
Thanks for the great work(on your ROM) and for the quick reply.
brochild said:
I just stumbled unto that site by accident (I love it)
I have registered and downloaded the nusense ROM and will report my findings.
Thanks for the great work(on your ROM) and for the quick reply.
Click to expand...
Click to collapse
No problem, hope you enjoy.
There's also a DeSensed version, called UnSense, which you likely saw as well.
See ya around that way.
Yes, I saw it and am trying to learn the differences between these 2 ROMs - so far better battery life stands out
Looks like I will be spending a lot more time there.
By the way, I was looking at your ext4 instructions (re-printed below for clarity - hope you don't mind)
Select Wipe/Format Menu Option
Wipe cache and dalvik
In the same Wipe/Format Menu: Wipe all partitions except SD
Now back in 4ext main menu: Select Tools
Select Format ext3 option I chose ext4 instead of ext3
Format Cache
Format Data
Format System
Now go back to the main menu and select the rom .zip to install
I chose ext4 instead of ext3 - could this be the cause of my random reboots using Liquid Smooth ICS ROM?
When I flash your ROM, I will choose to format ext3 - just to be sure (heh heh heh):laugh:
brochild said:
By the way, I was looking at your ext4 instructions (re-printed below for clarity - hope you don't mind)
Select Wipe/Format Menu Option
Wipe cache and dalvik
In the same Wipe/Format Menu: Wipe all partitions except SD
Now back in 4ext main menu: Select Tools
Select Format ext3 option I chose ext4 instead of ext3
Format Cache
Format Data
Format System
Now go back to the main menu and select the rom .zip to install
I chose ext4 instead of ext3 - could this be the cause of my random reboots using Liquid Smooth ICS ROM?
When I flash your ROM, I will choose to format ext3 - just to be sure (heh heh heh):laugh:
Click to expand...
Click to collapse
You can't use ext4 file system with nusense or unsense yet because the kernel doesn't support it. The random reboots with twisted ics could be related but I can't be sure since I haven't used it in a while.
Sent from my ADR6400L using Tapatalk 2
I tried the nusense ROM and formatted using ext3
Am still getting WiFi to drop randomly
At times it turns itself off - when it does that I see "out of range'.
Google Market changed to "Google Play", and most of the times that process stops working and prevent me from installing my apps
WiFi turns off and prevent update from Google Play as well - since I have it setup to update over WiFi
Also, am getting lots of process is not responding messages like "process.com.android.phone is not responding"
I get these messages very frequently.
I may go back to using LiquidSmooth ICS8 mr3v1
Are you sure you formatted all the partitions in ext3? The only way I get those messages are when I don't format properly. Also, maybe try clearing cache and data in the phone app and as for the market trying clearing data and cache. It may not hurt to run a fix permissions in the recovery. Does you wifi problem only happen with ics roms?
Sent from my ADR6400L using Tapatalk 2
If you do not format all partitions in ext3 format, you will have issues.
If you are not waiting until after the initial setup to sign into the market, that is likely an issue.
You need to wait until the home screen has set up and the device settles.
Then reboot, wait a minute and then sign into the market.
In my FAQ, you will see, the Market is the Play Store, no difference, just themed.
It has updated since the rom's last update and will do so when you sign in.
It's just an incremental update, but the theme goes away that I included for it an so does the custom icon and "Market" name.
If you do the above and still have issues, clearing the market (Play Store) app data and cache should sort you out.
If you are restoring data from another rom, then that is why you are also having force closes or wifi issues.
You cannot restore wifi data from an AOSP based rom that uses a GB kernel and expect that the same config will work well with the ICS rom and kernel.
disconnecktie said:
Are you sure you formatted all the partitions in ext3? The only way I get those messages are when I don't format properly. Also, maybe try clearing cache and data in the phone app and as for the market trying clearing data and cache. It may not hurt to run a fix permissions in the recovery. Does you wifi problem only happen with ics roms?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Yes, I am sure I formatted the partition in ext3
I cleared data, davlik factory reset etc
The only thing I did not do was "fix permission"
After installing all my apps, I booted to recovery and did the swipe thing again
Yes, my WiFi issue is only with ICS ROM, specifically this one (during and after setup)
So far the LiquidSmooth ICS 1.5 MR3 is working the best for me.
No WiFi issues at all, but I still do get occasional reboots.
Did you wipe boot and system partitions before flashing the rom?
Sent from my ADR6400L using Tapatalk 2
santod040 said:
If you do not format all partitions in ext3 format, you will have issues.
Click to expand...
Click to collapse
Yep, I did that
santod040 said:
If you are not waiting until after the initial setup to sign into the market, that is likely an issue.
You need to wait until the home screen has set up and the device settles.
Then reboot, wait a minute and then sign into the market.
Click to expand...
Click to collapse
I waited as instructed
santod040 said:
In my FAQ, you will see, the Market is the Play Store, no difference, just themed.
It has updated since the rom's last update and will do so when you sign in.
It's just an incremental update, but the theme goes away that I included for it an so does the custom icon and "Market" name.
If you do the above and still have issues, clearing the market (Play Store) app data and cache should sort you out.
Click to expand...
Click to collapse
I followed your instructions to the letter
santod040 said:
If you are restoring data from another rom, then that is why you are also having force closes or wifi issues.
You cannot restore wifi data from an AOSP based rom that uses a GB kernel and expect that the same config will work well with the ICS rom and kernel.
Click to expand...
Click to collapse
I am starting WiFi from scratch by turning it on, wait for it to scan and locate available networks.
Then I select my SSID and enter my keys to activate it.
At times I am downloading from Google Play, and will loose WiFi intermittently.
At times, I am viewing email messages, and will loose WiFi intermittently.
I was tempted to downgrade my RADIOS -but decided to go back to LiquidSmooth ICS 1.5 MR3
disconnecktie said:
Did you wipe boot and system partitions before flashing the rom?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Yes Sir, I did all that
I really appreciate all your efforts and your replies both to you and to Santod, I really, really do!
At this time, I resign myself to the fact that some of these ICS ROMs are not yet in their final stages and will wait patiently.
A huge Thanks for the great work to all developers, busting their humps to get this done.
I'm back baby
A funny thing happened to me yesterday, and I'm still laughing
Previously, I mentioned that I was tempted to downgrade my radio, but decided to go back to Liquid ICS v1.5MR3V1
So far I was still getting random reboots - way too many for my taste.
After reading numerous posting, I decided to roll back my radio from 2.00.00.0308, 0.02.00.0312r to 1.49.00.0406w_1,0.01.79.0331w_1.
But, in doing so, I accidentally installed the leaked ICS ROM instead (2.11.605.19).
So I thought I was downgrading my radio, but ended up installing the leaked ROM :laugh:
Incidentally, I also un-rooted my T-bolt - Thanks to the new tool I was able to quickly root it back.
Luckily, I also backed up the previous ROM, and was able to restore it.
All in the sudden, my T-bolt is back - everything is working fine and no more reboots :victory:
To Recap, after downgrading my radio to the leaked radio 1.49, all is well again .
My T-bolt is running so good that I am hesitant to load the latest ROMs.
My choices are the nuSense beta 17.2 or AOSP 4.0.4 ICS [Multi-Source]
Is it a wise decision to upgrade or should I stay put
That updated nusense is amazing but I wouldn't run it with the full leaked radios. I use the combo of the. 19/leaked radios and they work great.
Sent from my ADR6400L using Tapatalk 2
Why should I try NuSense ROM by Santod
disconnecktie said:
That updated nusense is amazing but I wouldn't run it with the full leaked radios. I use the combo of the. 19/leaked radios and they work great.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Thank you sir, for your prompt reply!
Sounds like I need to give the NuSenseROM a try, but ....
1) what's so amazing about it, and how does it differ from what I'm currently using (where can I get screenshots)
a) I know its been reworked - but that's over my head (for now)
2) I am not entirely sure what the combo 19/leaked radio is, is it this ".19 cdma and the ICS LTE radio" posted by Santod?
Thanking you in advance.
1) Basically everything works the way it was intended to. Camcorder included. Only drawback is battery is slightly worse than Twisted's build.
A) He rebased the rom using the official Droid Incredible 2 ota which is a better base since the original base was from the leak that sucked balls big time.
2) Yes
Sent from my ADR6400L using Tapatalk 2
I now have the NuSenseROM installed - so far so good.
No reboots yet and I am still using the 1.49.00.0406w_1,0.01.79.0331w_1 radio
The ROM is nearly flawless, but I wish it had the phone dialer interface, and the people interface of the Liquid Smooth ROM
I love the fact the camcorder works, but I wish it also had the ICS camera (But I can download it).
I am using Go SMS Pro, and this ROM is not linking my accounts pictures there (bummer)
The Liquid Smooth ROM showed my accounts picture on that app.
I am using and synchronizing my Google, Verizon, Facebook, and Voxer accounts
Flashed My wife and I's OG's with CM 10.2. She was coming from stock 4.0.1 I was coming from 4.1.2
My has no problems. Hers wouldnt connect to wifi even though it could pick up the signals.
Last night her Kernel crashed. I figured maybe I didnt fully wipe her files clean so I rebooted her into recovery and did a factory wipe,
cleaning Dalvik, etc. and reinstalled.
Still no wifi connectivity.
Is this a driver, antennae, modem issue? Please help, I've run out of ideas.
Did you flash the correct radio?
Sent from my Optimus G using Tapatalk 4
Hmmmmm
Dr0!dFreek said:
Did you flash the correct radio?
Sent from my Optimus G using Tapatalk 4
Click to expand...
Click to collapse
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.1.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
brionbey said:
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
Click to expand...
Click to collapse
Roms for the OG don't contain modems, your wife's phone would still have ICS modem. If you had the ota to 4.1 on your phone it will have jb modem.
brionbey said:
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
Click to expand...
Click to collapse
Yes, given that you avoided bricking your phone not having the rpm/tz partitions from the ota update, she would also have the ics modem, which hopefully is the only thing wrong, and is an easy fix.
matter of fact I'm not aware of anyone trying the ics modem on 4.3, or using 4.3 without the updated partitions
Still, (as a purely personal preference) I would restore the backup from before you flashed her to CM 10.2, then call up AT&T and make them push the OTA update, then backup again and reflash CWM.
-edit- this is of course, if you are on AT&T
also, you can probably make a nandroid of CM 10.2, restore to stock, get the OTA, and restore CM 10.2 and you wouldn't lose anything, since it only restores kernel,system,data,cache, etc it would be unaffected by the OTA.
technically this remains true for the LGNPST/teenybin route, but i haven't used lgnpst, i prefer forcing at&t to provide the OTA update since if it bricks then, they owe you a phone
[r.]GimP said:
Yes, given that you avoided bricking your phone not having the rpm/tz partitions from the ota update, she would also have the ics modem, which hopefully is the only thing wrong, and is an easy fix.
matter of fact I'm not aware of anyone trying the ics modem on 4.3, or using 4.3 without the updated partitions
Still, (as a purely personal preference) I would restore the backup from before you flashed her to CM 10.2, then call up AT&T and make them push the OTA update, then backup again and reflash CWM.
-edit- this is of course, if you are on AT&T
also, you can probably make a nandroid of CM 10.2, restore to stock, get the OTA, and restore CM 10.2 and you wouldn't lose anything, since it only restores kernel,system,data,cache, etc it would be unaffected by the OTA.
technically this remains true for the LGNPST/teenybin route, but i haven't used lgnpst, i prefer forcing at&t to provide the OTA update since if it bricks then, they owe you a phone
Click to expand...
Click to collapse
Just like to pass on a little info I learned recently, both Shellnutt2's cm10.2 and dvhexer's "alternate" cm10.2 use an e975 kernel.and can be flashed to phones without updating partitions.
adfurgerson said:
Just like to pass on a little info I learned recently, both Shellnutt2's cm10.2 and dvhexer's "alternate" cm10.2 use an e975 kernel.and can be flashed to phones without updating partitions.
Click to expand...
Click to collapse
Yeah I considered that, still terrifying to me though, but it would explain still having the ics modem.
How does this sound?
[r.]GimP said:
Yeah I considered that, still terrifying to me though, but it would explain still having the ics modem.
Click to expand...
Click to collapse
Ok, Just got back from work.
Today, Device crashed twice. Once a kernel error, once something about watchdog.
The kernel crash occurred when using the CM 10.4 camera. The same thing happened to my wifes device.
What I'd like to do it flash the Stock Rom Back with Stock modems to both phones.
Unfortunately, my backup didnt take because of lack of space or something, so I need to find the stock 4.1.2 rom.
I need action steps if possible.
I'm assuming I need:
4.1.2 Stock Rom for my device.w/ google apps
4.0.1 Stock for my wifes's./w google apps
I'm also assuming that I'd follow the same steps:
factory reset, flash the rom + apps reboot.
I'm using TWRP
If all that goes well I'd attempt to have at&t push the update to my wife's phone ( would I need to reset her bootloader?)
Then Reflash CM 10.2 with appropriate modems, and google apps.
Please catch any errors in this logic. Also Links to stock Rom's would be appreciated.
If anyone has any suggestions to a better custom rom then CM 10.2 I'm open to suggestions. I have not found it to be as stable as I would of liked...
FYI to make things worse, now my pc won't recognize that my device is attached.... trying not to panic.
brionbey said:
Ok, Just got back from work.
Today, Device crashed twice. Once a kernel error, once something about watchdog.
The kernel crash occurred when using the CM 10.4 camera. The same thing happened to my wifes device.
What I'd like to do it flash the Stock Rom Back with Stock modems to both phones.
Unfortunately, my backup didnt take because of lack of space or something, so I need to find the stock 4.1.2 rom.
I need action steps if possible.
I'm assuming I need:
4.1.2 Stock Rom for my device.w/ google apps
4.0.1 Stock for my wifes's./w google apps
I'm also assuming that I'd follow the same steps:
factory reset, flash the rom + apps reboot.
I'm using TWRP
If all that goes well I'd attempt to have at&t push the update to my wife's phone ( would I need to reset her bootloader?)
Then Reflash CM 10.2 with appropriate modems, and google apps.
Please catch any errors in this logic. Also Links to stock Rom's would be appreciated.
If anyone has any suggestions to a better custom rom then CM 10.2 I'm open to suggestions. I have not found it to be as stable as I would of liked...
FYI to make things worse, now my pc won't recognize that my device is attached.... trying not to panic.
Click to expand...
Click to collapse
Don't panic, you can always load onto the SD card externally, with a microsd to SD adapter or through TWRP/CWM with "mount usb storage" mode. Failing both of those things I'm fairly certain one of your two phones will be enough to load the SD card for the other phone if needed.
I'm thinking everything you need is going to be the LGNPST route now anyway, and that being said you may as well just flash them both to stock 4.1.2 in that case. First things first, you definitely want to backup before anything gets out of hand, if twrp isn't getting it then pull with adb. Quick breakdown of that below.
The universal drivers straight off the LG site work just fine, but in my experience to get the adb part happy you need to click on your devices, and find your phone, whether it says LG/Nexus4/MTP, doesn't matter. Open it and click on the hardware tab, it should list 3 devices.
unknown (or adb if you're lucky)
Your phone
USB Composite Device
If the top isnt some variation with ADB in the name, double click it, then change settings, it may say drivers not loaded, so on the driver tab we're going to give it one.
Update driver, and it will ask how, the option on the bottom is "browse my comp for driver software" and after that the bottom option again is "let me pick from a list..." I think then it shows a split list, the device type should be ADB something, and if you installed the LG universal drivers then near the bottom you will have "LGE Mobile Sooner Single ADB Interface" windows will complain because it couldn't figure out that its the right driver, confirm you want to use it and it will then show "this device is working properly" go ahead and close all those windows and it will update on the first one with the three devices listed the next time you open it.
At this point you need the adb application itself, I usually just download the whole android SDK personally, but where you get it from doesn't matter. If you're booted in android, make sure adb has root access in developer settings, and debugging is enabled.
open a command promt, for the sake of easy navigate to the folder where you put adb, in windows, or in the SDK example, /android/sdk/platform-tools/ hold shift and right-click on an empty space and select "open command window here"
If android is running, type "adb root" without quotes
and adb will inform you its restarting, if in twrp you will already be root.
Type "adb devices" and as long as its not blank you should be good
again, for the sake of easy "adb backup -shared -all"
and let it do its thing, it should start creating a default file named "backup.ab" it's bound to take awhile as -shared should grab all the sd card contents just to be safe.
Disaster recovery aside, I would use a combination of Titanium backup root, and "backup your mobile" - especially add the second option in addition to titanium, thats one of the only free backup apps that can get MMS as well as SMS, and restore them.
Again, if you're having issue with the computer normally seeing the device, these are still good tools, save to external sd card, remove card and transfer manually to your computer.
ok.. now that all your stuff is *hopefully* now redundantly backed up, depending on the stock image you find, you can either push it via fastboot commands or flash with lgnpst. I know the images are in our forum, most likely in the lgnpst thread. just follow through that and read well ahead before performing each step, you'll be ok.
I believe fastboot can relock your bootloader in all off one command, i don't have the answer if its necessary or not to receive the OTA, but having skimmed the lgnpst thread in the past, I'm positive people have done the flash and then had the OTA pushed from AT&T so they could get up to 4.1.2 for the official JB and partitions. Like I said in the beginning, your call if you want to skip that and just lgnpst to 4.1.2 since you're there anyway. Also, keep an eye out for one of the recent restore to stock / RPM/TZ partition threads, I think shellnutt making a cwm/twrp flashable zip to do the same thing lgnpst teeny bin would without even needing lgnpst.
So, barring a complete hardware failure, dont be scared. Get your data for now, then on to the next step.
Best xda technical support post I have seen in a long time. Thanks, gimp.
Sent from my Optimus G using XDA Premium 4 mobile app
DeathmonkeyGTX said:
Best xda technical support post I have seen in a long time. Thanks, gimp.
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Agreed.
Sent from my Optimus G using Tapatalk 4
I agree also! feels great to have some help with this. attempting fixes I'll report back.
Sent from my LG-E970 using XDA Premium 4 mobile app
I got stuck on the adb driver part. Through searching I found the backup I made for her. Can I restore her backup. Flash the jellybean rom to it, creating the neccessary. Partitions in the process, along with the correct radio, and then reflash Cm? My main concern is getting her wifi up. She's racked up 6gigs in 2 days herself! Were on the 4.gig shared plan. Or possibly just flash the radio...
Sent from my LG-E970 using XDA Premium 4 mobile app
brionbey said:
I got stuck on the adb driver part. Through searching I found the backup I made for her. Can I restore her backup. Flash the jellybean rom to it, creating the neccessary. Partitions in the process, along with the correct radio, and then reflash Cm? My main concern is getting her wifi up. She's racked up 6gigs in 2 days herself! Were on the 4.gig shared plan. Or possibly just flash the radio...
Sent from my LG-E970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes that sounds fine, in that case I would just make the apps and messages backups with titanium/backup your mobile
I'm not 100% if the lgnpst flash to JB wipes user data or not, but after that you can flash pretty much ANY rom for our device, then just download titanium/backup your mobile from the app store and point it to the directories on the sd card, and restore selectively.
For the most part you can move everything from /sdcard to /external_sd and move it back over when you're done, I think the JB radio (or modem, both terms apply) works very well for everything I've used (and yes they play a significant part in wifi and gps also), and I was a pretty hardcore flash-a-holic for a really good while, still haven't tried the hybrid modems and people rave about how well they work. Sounds like a good plan you got going, once you're up with the partitions and the JB modem from 4.1.2 you really should have no issues, and once you have that freedom, and she will as well to try out all manner of ROM's, you'll find you get really good at backup/restore out of necessity. Happy flashing.
If you need any specifics, aside from the step by steps of the other threads I'm glad to lend advice, just let me know
-edit- you can make multiple backups with each program by the way, titanium and backup your mobile.
Titanium free says only one backup per app, but in reality just hit the batch button on the top right, looks like a check mark, have it get all apps and system settings, then just move the whole folder you set for titanium off of the device for safe keeping. This way you can backup everything running right now, then if you want to restore the other one, you could even do it again, if you just wanted to cherry pick some stuff, then flash, etc. Titanium free wont let you make multiple copies of the same app, but it also WONT delete extras if you already have them, so if you dump a few titanium folders into eachother and merge them, you can then choose any of the backup files or data or both from each date.
The reason I use both programs is as I said earlier, backup your mobile handles SMS/MMS very efficiently, and occasionally I'll let it grab a few user apps, and system apps, because when it restores them, it restores for example, flash player from LG stock rom, as a user app, and it continues to work flawlessly. Titanium can't get over it being a system app, and sucks at restoring flash.
However, titanium is GREAT for also saving user data, not just the program itself. ie.. savegame states for any app you have that doesnt explicitly sync online, or the login data for facebook, or adfree with the most current hosts so you dont have to redownload or even type your logins, very convenient.
My personal order of operations before I flash a new rom, or even upgrade to a new version with a clean flash instead of a "dirty" is to fully backup all apps/system data with titanium, then hit ByM for contacts/sms/mms/bookmarks/user dictionary/apps
then a nandroid backup, since it is basically a perfect snapshot itself, just like turning the phone off, and back on.
after rom flash / gapps, I boot, setup google real quick, goto app store and cancel the 5 million downloads, except for titanium/ByM
after those download I roll my messages/user dictionary/contacts/ selective apps I know i'll use, and the same with a few from titanium.
This way I'm less bloated with crap I probably don't use everyday, and if i need it, its a few taps away. It's a very painless process and a lot of peace of mind having everything safe, and allows you to try alot of unstable crap knowing how easy you can always roll your CWM/TWRP backup over to the device like you never left.
Sorry, I'm a fan of ranting. Pics for adb driver steps explained in previous post, and the backup part, for reference if you ever need them.
View attachment 2263477
View attachment 2263478
Ok, I'm keepin cool but it seems to be one thing after another
I made the backup before the original flash.
I see it in the folder. When I restored it, it is the same rom that I'm on CM 10.2
I'm not sure how that happened.
Thanks for the images, that really helped unstuck me.
Question: I've checked the threads looking for the stock [ROM] 4.1.2 and Gapps for E970 and can't find them anywhere.
At this point I just need a doOver. I have to get my wife her phone back, ASAP and if I brick by some chance, I'll never hear the end of it.
EVER.
Or how about just flashing the radio? Can I do that to at least get her Wifi?
Here is the flashable jellybean radio by g33k3r.
http://forum.xda-developers.com/showthread.php?t=2220048
I recommend still updating her to the jellybean partition layout when you get a chance, but this should get you working WiFi at the very least.
Sent from my LG-E970 using xda app-developers app
Flash the Radio
Thanks SnowLeopard.
So all I need to do is just boot into recovery using TWRP and Install the radio, or should I factor reset and install the radio at the same time as the rom?
Thanks Again Guys. (or gals)
Lgnpst doesn't touch the /data partition.
Sent from my Optimus G using XDA Premium 4 mobile app
the modem work great.
Sent from my LG-E970 using XDA Premium 4 mobile app
At gimp, followed instructions exactly, computer recognize device, only thing left to do is run teeny bit, but getting error path not found
Sent from my LG-E970 using XDA Premium 4 mobile app
Hi all,
This is the first time I've tried installing a custom ROM on my VZW S4 (i545) (MDK firmware. Yes, I held out on the OTA since May). I've got a few thoughts and a couple of questions I was hoping could be addressed. I consider myself familiar with flashing ROM's and whatnot, so I won't need hand-holding steps in answer to my questions.
Some info:
VZW S4
MDK Firmware
Recovery: OUDhs CWM Touch Req0very v1.0.3.5
I haven't taken any OTA since I got the phone back in May. This leads me to believe (correct me if I'm wrong) that I'm on Android 4.2.2?
Current ROM: AOKP Nightly Build for 10/31/2013 (MR2)
Thoughts: Holy hell, this ROM is BLAZING fast. I am missing a few features, but none I use regularly (I don't use any of the TouchWiz "smart" features. Damn battery hogs). I was able to flash this over and install GAPPS without any problems. Loading time is incredible, and I love how clean the interface is.
Questions:
Can anyone help me figure out why I cannot install CM10.2? Not sure if that's because I downloaded the wrong version or something, but after flashing it, the screen stays stuck at the Galaxy S4 logo and doesn't move. Maybe I didn't wait long enough, but it surely didn't move in any reasonably expected time (AOKP, by comparison, loaded probably <1 minute). Any thoughts on why this might be? I really want to try CM10.2, so perhaps I should try a different build?
Another question/concern: I downloaded a few different ROMs last night -- CM10.2, AOKP and st0ckdr0id. AOKP installed fine, CM10.2 froze up, but when I installed st0ckdr0id (after wiping out, of course), I got what I think is referred to as a kernel panic. The message was similar to "This phone has software installed on it that Verizon Wireless has determined to be unsafe. Please power off the phone and take to the nearest Verizon Wireless store for help". In the top-left corner, it had in bold RED letters "Kernel secure: FAIL" (or similar wording). I fixed this by booting back into recovery, wiping out, and then installing AOKP again. Can anyone help me understand why this happened?
Why is only ~10GB of space still available when I -thought- I wiped out everything?
What I'm really searching for is an AOSP ROM that is very clean and light, but has SOME of the TouchWiz features. Any recommendations?
My phone only shows me as having a 3G connection, where normally I have 4G LTE. Anything I can do to fix this? Is this an issue with the ROM not detecting the right kind of radio? Bug report, perhaps?
I can't mount my external_sd in my CWM anymore. Yes, I used to be able to do it at one point, because I've done an external nandroid backup to it from within CWM in the past (as of October 29th, if the date on the backups is correct). I've read in other Google searches that it has something to do with the formatting of the SD card, but I haven't removed that SD card from my phone in a few months to have adjusted anything to do with formatting. I plugged the memory card into my Linux laptop this morning while diagnosing this and got an error about an unknown exfat partition. Any advice would be greatly appreciated.
Stupid question: Is there a way to -completely- wipe my internal SD card clean of all my current files? I know when I "wipe" /data I can still see all of my files from the previous installation, and I'm not ballsy enough to wipe /sdcard. I guess the question that then coincides with this is if I were able to completely wipe the phone, I assume that would wipe the recovery as well?
Sorry for some of the novice questions -- I have no problem messing with my old TF300T tablet (because NVFlash will save the day), but this is my only phone, only line of communication and SOLE way for me to answer calls for work (24/7 rotating on-call), so it is VERY important to me to ask questions and not go down for more than 1 hour.
Thanks for all help guys, its much appreciated. I hope to be able to test ROMs regularly and maybe start posting video reviews or something, who knows?
Thanks,
Opethfan89
opethfan89 said:
Hi all,
This is the first time I've tried installing a custom ROM on my VZW S4 (i545) (MDK firmware. Yes, I held out on the OTA since May). I've got a few thoughts and a couple of questions I was hoping could be addressed. I consider myself familiar with flashing ROM's and whatnot, so I won't need hand-holding steps in answer to my questions.
Some info:
VZW S4
MDK Firmware
Recovery: OUDhs CWM Touch Req0very v1.0.3.5
I haven't taken any OTA since I got the phone back in May. This leads me to believe (correct me if I'm wrong) that I'm on Android 4.2.2?
Current ROM: AOKP Nightly Build for 10/31/2013 (MR2)
Thoughts: Holy hell, this ROM is BLAZING fast. I am missing a few features, but none I use regularly (I don't use any of the TouchWiz "smart" features. Damn battery hogs). I was able to flash this over and install GAPPS without any problems. Loading time is incredible, and I love how clean the interface is.
Questions:
Can anyone help me figure out why I cannot install CM10.2? Not sure if that's because I downloaded the wrong version or something, but after flashing it, the screen stays stuck at the Galaxy S4 logo and doesn't move. Maybe I didn't wait long enough, but it surely didn't move in any reasonably expected time (AOKP, by comparison, loaded probably <1 minute). Any thoughts on why this might be? I really want to try CM10.2, so perhaps I should try a different build?
Another question/concern: I downloaded a few different ROMs last night -- CM10.2, AOKP and st0ckdr0id. AOKP installed fine, CM10.2 froze up, but when I installed st0ckdr0id (after wiping out, of course), I got what I think is referred to as a kernel panic. The message was similar to "This phone has software installed on it that Verizon Wireless has determined to be unsafe. Please power off the phone and take to the nearest Verizon Wireless store for help". In the top-left corner, it had in bold RED letters "Kernel secure: FAIL" (or similar wording). I fixed this by booting back into recovery, wiping out, and then installing AOKP again. Can anyone help me understand why this happened?
Why is only ~10GB of space still available when I -thought- I wiped out everything?
What I'm really searching for is an AOSP ROM that is very clean and light, but has SOME of the TouchWiz features. Any recommendations?
My phone only shows me as having a 3G connection, where normally I have 4G LTE. Anything I can do to fix this? Is this an issue with the ROM not detecting the right kind of radio? Bug report, perhaps?
I can't mount my external_sd in my CWM anymore. Yes, I used to be able to do it at one point, because I've done an external nandroid backup to it from within CWM in the past (as of October 29th, if the date on the backups is correct). I've read in other Google searches that it has something to do with the formatting of the SD card, but I haven't removed that SD card from my phone in a few months to have adjusted anything to do with formatting. I plugged the memory card into my Linux laptop this morning while diagnosing this and got an error about an unknown exfat partition. Any advice would be greatly appreciated.
Stupid question: Is there a way to -completely- wipe my internal SD card clean of all my current files? I know when I "wipe" /data I can still see all of my files from the previous installation, and I'm not ballsy enough to wipe /sdcard. I guess the question that then coincides with this is if I were able to completely wipe the phone, I assume that would wipe the recovery as well?
Sorry for some of the novice questions -- I have no problem messing with my old TF300T tablet (because NVFlash will save the day), but this is my only phone, only line of communication and SOLE way for me to answer calls for work (24/7 rotating on-call), so it is VERY important to me to ask questions and not go down for more than 1 hour.
Thanks for all help guys, its much appreciated. I hope to be able to test ROMs regularly and maybe start posting video reviews or something, who knows?
Thanks,
Opethfan89
Click to expand...
Click to collapse
Wow that's a lot. Let's see if we can get you answers.
1. Switch recoveries to twrp 2.5.0.2. I can't stress the importance of the particular version enough. There are others. This is absolutely the most stable. It's what the devs use. I think then your cm issue will be resolved.
Correct way to wipe with twrp.
1.wipe - >factory reset.
2. Advanced wipe - >check system, data, davlik, cache then wipe.
3. The go back to main screen and install rom.
2. Answered by answer one. Lots of people have lots of opinions about the various recoveries. All I can tell you is this is what all the devs use for their recovery. Can't argue with that.
3. Reserved space. It might say you have 16 gigs but a good size chunk is taking merely by formatting. Then the ROM and programs you have installed of course.
4. Honestly they are all freaking great. The aosp roms. You do the answer to number one and you can find out. DU is my fav @ this moment. Followed by beanstalk.
5. Go to mobile networks make sure your network mode is set to cdma +lte/evdo.
6. Answer 1.
7. You don't really want to wipe the entire internal SD card. Sounds good when you think it might screw you if you did it.
Sent from my Nexus 7 using xda app-developers app
Mightycaptain said:
Wow that's a lot. Let's see if we can get you answers.
1. Switch recoveries to twrp 2.5.0.2. I can't stress the importance of the particular version enough. There are others. This is absolutely the most stable. It's what the devs use. I think then your cm issue will be resolved.
Correct way to wipe with twrp.
1.wipe - >factory reset.
2. Advanced wipe - >check system, data, davlik, cache then wipe.
3. The go back to main screen and install rom.
2. Answered by answer one. Lots of people have lots of opinions about the various recoveries. All I can tell you is this is what all the devs use for their recovery. Can't argue with that.
3. Reserved space. It might say you have 16 gigs but a good size chunk is taking merely by formatting. Then the ROM and programs you have installed of course.
4. Honestly they are all freaking great. The aosp roms. You do the answer to number one and you can find out. DU is my fav @ this moment. Followed by beanstalk.
5. Go to mobile networks make sure your network mode is set to cdma +lte/evdo.
6. Answer 1.
7. You don't really want to wipe the entire internal SD card. Sounds good when you think it might screw you if you did it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response Mightycaptain! I used CWM as my first ever recovery and am kinda pressed on it, which is why I use it, but I have no issues going to TWRP if that means fixing my issues. Can you elaborate on how to install TWRP in place of my current CWM? I'll do some Googling in the meantime to try to find the answer myself. (I haven't done any flashing or rooting stuff since I got the phone in May!!)
Thanks for your answer in #5. Fixed the issue I was having.
My reason for wanting to wipe the entire internal SD card is there are still files, folders, logs and backups from when I had my previous ROM. I'm having issues restoring my nandroid backup from the night of the 7th so is it at all possible for me to salvage some of my settings, apps and file backups from those existing files? Once I fix my nandroid, I'm going to keep the nandroid backup in a safe place and I ideally want to have a completely clean phone to start from: That means getting rid of all those old files and other nonsense from before. Is this a possibility?
I'm going to spend my time today trying to extract data from my nandroid backups using ROM Toolbox Pro. If that doesn't work, I have a nandroid backup from the 31st that has 99% of the stuff I need so I'll try to restore that. If THAT doesn't work, then I'm going to cry myself to sleep while trying to remember all of my contacts
Wish me luck, and hopefully I can get some answers to my last few questions!
Thanks,
Opethfan89
opethfan89 said:
Thanks for your response Mightycaptain! I used CWM as my first ever recovery and am kinda pressed on it, which is why I use it, but I have no issues going to TWRP if that means fixing my issues. Can you elaborate on how to install TWRP in place of my current CWM? I'll do some Googling in the meantime to try to find the answer myself. (I haven't done any flashing or rooting stuff since I got the phone in May!!)
Thanks for your answer in #5. Fixed the issue I was having.
My reason for wanting to wipe the entire internal SD card is there are still files, folders, logs and backups from when I had my previous ROM. I'm having issues restoring my nandroid backup from the night of the 7th so is it at all possible for me to salvage some of my settings, apps and file backups from those existing files? Once I fix my nandroid, I'm going to keep the nandroid backup in a safe place and I ideally want to have a completely clean phone to start from: That means getting rid of all those old files and other nonsense from before. Is this a possibility?
I'm going to spend my time today trying to extract data from my nandroid backups using ROM Toolbox Pro. If that doesn't work, I have a nandroid backup from the 31st that has 99% of the stuff I need so I'll try to restore that. If THAT doesn't work, then I'm going to cry myself to sleep while trying to remember all of my contacts
Wish me luck, and hopefully I can get some answers to my last few questions!
Thanks,
Opethfan89
Click to expand...
Click to collapse
Check my post here for twrp 2.5.0.2.
http://forum.xda-developers.com/showthread.php?p=47275165
You can flash it in your current recovery. It overwrites CWM. I would make sure you have a flashable for CWM just in case you need to go back for some reason. Also the backups between those 2 recoveries are not compatible. But I would nandroid with CWM before flashing twrp. I would also change were you recovery is pointing to for storage to the external SD if you haven't already. After you have cut your current backup and past it there. You can use rom toolbox pro to back up your contacts and restore it once you flash a new ROM.
Now as good advice going forward I would add your contacts to your Google account. That way when you flash new stuff or drop your phone in the toilet as soon as you add your Google account to the phone all those contacts will automatically download. But it is always a good idea to use tibu or rom toolbox pro to back up all your apps and seeing and use that after flashing roms to restore apps and settings.
But honestly I'd nandroid, move my contacts to Google, make app backups. Flash twrp. Then start flashing roms. You could be doing it in an hour. After you flash twrp make another nandroid so you have a twrp compatible backup. Then in a day or so of you are happy with everything delete the CWM backups for space.
Edit: as to extracting things from your current nandroid. Not sure if that is possible for one thing it is compressed not sure how that would work unless you are doing a full restore.
Also for future reference with TWRP. When restoring nandroid wipe like your flashing a new rom before restoring.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Check my post here for twrp 2.5.0.2.
http://forum.xda-developers.com/showthread.php?p=47275165
You can flash it in your current recovery. It overwrites CWM. I would make sure you have a flashable for CWM just in case you need to go back for some reason. Also the backups between those 2 recoveries are not compatible. But I would nandroid with CWM before flashing twrp. I would also change were you recovery is pointing to for storage to the external SD if you haven't already. After you have cut your current backup and past it there. You can use rom toolbox pro to back up your contacts and restore it once you flash a new ROM.
Now as good advice going forward I would add your contacts to your Google account. That way when you flash new stuff or drop your phone in the toilet as soon as you add your Google account to the phone all those contacts will automatically download. But it is always a good idea to use tibu or rom toolbox pro to back up all your apps and seeing and use that after flashing roms to restore apps and settings.
But honestly I'd nandroid, move my contacts to Google, make app backups. Flash twrp. Then start flashing roms. You could be doing it in an hour. After you flash twrp make another nandroid so you have a twrp compatible backup. Then in a day or so of you are happy with everything delete the CWM backups for space.
Edit: as to extracting things from your current nandroid. Not sure if that is possible for one thing it is compressed not sure how that would work unless you are doing a full restore.
Also for future reference with TWRP. When restoring nandroid wipe like your flashing a new rom before restoring.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks again for your quick response!! I'm glad I checked this first, because I'm in my ROM Toolbox app atm and it has an option to let me install TWRP 2.5.0.2 from within the app itself. Should I do it this way?
I will be adding all contacts to Google from now on. Unfortunately I saved all my stuff to my Verizon backup assistant so I just need one last shot at my phone to save all those contacts (manually, if I must) and be able to enter them onto the new ROM.
By "flash it in your current recovery" I assume you mean download the .zip, place it on my internal /sdcard, and then "flash" it just like I would flash a ROM, right?
I'm sure I have a "flashable" for CWM somewhere but like I said, I haven't done any of this stuff on this phone since I first bought it, and things have changed so much with everyone having OTA's and being locked out that I'm not sure what process is the same or what has changed. I can't afford to lose this phone so I'm hesitant to go balls to the wall to try things.
I will try the things you've listed here. Seems like a nandroid + TiBu + Google Contacts is my best bet to get up and running each time I decide to try a new ROM.
Thanks again!
opethfan89 said:
Hey thanks again for your quick response!! I'm glad I checked this first, because I'm in my ROM Toolbox app atm and it has an option to let me install TWRP 2.5.0.2 from within the app itself. Should I do it this way?
I will be adding all contacts to Google from now on. Unfortunately I saved all my stuff to my Verizon backup assistant so I just need one last shot at my phone to save all those contacts (manually, if I must) and be able to enter them onto the new ROM.
By "flash it in your current recovery" I assume you mean download the .zip, place it on my internal /sdcard, and then "flash" it just like I would flash a ROM, right?
I'm sure I have a "flashable" for CWM somewhere but like I said, I haven't done any of this stuff on this phone since I first bought it, and things have changed so much with everyone having OTA's and being locked out that I'm not sure what process is the same or what has changed. I can't afford to lose this phone so I'm hesitant to go balls to the wall to try things.
I will try the things you've listed here. Seems like a nandroid + TiBu + Google Contacts is my best bet to get up and running each time I decide to try a new ROM.
Thanks again!
Click to expand...
Click to collapse
Understand the hesitancy completely. But with nodding comes risk. It is always about whether you can accept the worst possible outcome.
Rom toolbox pro flashing recovery? I don't know never tried it.
Yes I would download the recovery. Leave it on SD card reboot to recovery and flash like a rom.
Yes nandroid tibu and saving your contacts to Google is the quickest way to get up and running again.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Understand the hesitancy completely. But with nodding comes risk. It is always about whether you can accept the worst possible outcome.
Rom toolbox pro flashing recovery? I don't know never tried it.
Yes I would download the recovery. Leave it on SD card reboot to recovery and flash like a rom.
Yes nandroid tibu and saving your contacts to Google is the quickest way to get up and running again.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Mighty, just wanted to report that flashing TWRP 2.5.0.2 from within ROM Toolbox Pro worked like a charm. I'm on TWRP as we speak.
Thank you so much for your responses. If anyone else has anything to add, or a different response to my questions, please do so! In the meantime, I'm going to try to figure out how to get my nandroid backup working...
Cheers!
*EDIT* Made a backup with TWRP (whose interface is bloody phenomenal, btw), flashed CWM and its working like a charm!! Going to try the st0ckdr0id one as well. Still working on getting that nandroid working so I can recover my stuff and get to customizing!