Related
I tried 5 different roms and i feel cyanogenmod 6 rc2 version is stable. but i am worrying if i try one more custom rom then will it break my phone?. Please tell me how many time we can install roms in the phone.
Will it create a bad sector on my phone.
dlcsboop said:
I tried 5 different roms and i feel cyanogenmod 6 rc2 version is stable. but i am worrying if i try one more custom rom then will it break my phone?. Please tell me how many time we can install roms in the phone.
Will it create a bad sector on my phone.
Click to expand...
Click to collapse
Well as long as you're wiping between different ROMs you should be fine. And even if you are there won't be any permanent damage. The only way you can brick your phone is by installing a bad/old radio.
Even if there's a limited number of "flashing" the phone you won't reach it before you get a new phone.
Likely in the millions of times.
Don't worry about it.
Its the same question like "how many times can you write data on a sd card", you already got a new one when you reach that number
Flash memory has a certain number of read write times until it fails. But that number is so high that it will be years from now.
how can i know if i have a bad sector??
Amritttt said:
how can i know if i have a bad sector??
Click to expand...
Click to collapse
You have to wipe/install a new rom and copy logs to sd card from either other or advanced menu, havent used amon_ra recovery in forever
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
androidcues said:
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
Click to expand...
Click to collapse
Lol, I may be able to tell you soon, flashing nightlies every day
How many stars are there in the Galaxy?
Flippy125 said:
Lol, I may be able to tell you soon, flashing nightlies every day
Click to expand...
Click to collapse
EVERY DAY ISN'T ENOUGH!!!!!!!1111oneeleven
Flippy125 said:
Lol, I may be able to tell you soon, flashing nightlies every day
Click to expand...
Click to collapse
Hey, I am a total newbie but I would like to flash the nightlies as well. I usually backup all my apps and settings using Titanium Backup, do a Nandroid backup, wipe and then flash the new ROM. However, backing up all apps and settings using Titanium Backup and restoring them after flashing the nightly is quite time consuming. Even worse is arranging the application short cuts / widgets on the desktops after a fresh install.
Nandroid will allow me to go back to backed up version after I have played around with the nightly for a few hours. But then I lose all the features of the nightly once I am back to my old ROM. As I am carrying only a single phone, it becomes mandatory for me to restored the Contacts, Messages, Applications and Settings after flashing a new ROM.
It may sound stupid but is there a better and faster way of doing things without having to restore all applications/settings from the backup so that I also could try out the nightlies? How do you manage this?
For the most part, you can flash nightlies without a wipe, if you're going from CM to CM. If you see weird behavior after flashing, then go back and wipe, and if that doesn't work do a complete wipe and flash.
If you're on another ROM, then I would definately wipe...
Sent from my Nexus One using XDA App
Exactly 6.3 times. That is all. But nobody mentions it.
danger-rat said:
For the most part, you can flash nightlies without a wipe, if you're going from CM to CM. If you see weird behavior after flashing, then go back and wipe, and if that doesn't work do a complete wipe and flash.
If you're on another ROM, then I would definately wipe...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks, danger-rat! I'll give it a shot
meechto said:
Thanks, danger-rat! I'll give it a shot
Click to expand...
Click to collapse
I strongly suggest wiping cache and dalvik-cache prior to flashing a new nightly, it prevents **** and doesn't affect your settings/files
Haven't been on CM for awhile, but if you use Launcher Pro or ADW they have Homescreen backups. Have had good luck with MyBackUpPro too.
Ken
3 times. 1...2...crunch...3. Haven't you all seen the tootsie pop commercial?
androidcues said:
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
Click to expand...
Click to collapse
How many licks does it take to get to the Tootsie Roll center of a Tootsie Pop? LMAO, that's what I WANNA KNOW!
Had my Hero for a little over a year now. Been rooted for most of that time. Currently running Aosp from 02-10-11. I also have 2.6.29.6 Aosp Kernel. Not sure if any other info needed. I have normal coverage where I live and mostly everywhere else except where I work. I drop calls all the time, lose data, etc. I called Sprint and was told its my Hero, not the network. They said they have a new tool that tells them what is causing the problem, so its def my phone. I also have terrible battery life, and my phone is laggy as hell. I just want to know what my best option would be. Should I go to the Sprint store and have them replace my phone? Should I start from scratch (rooting wise) and take it from there? Or should I just wait for the Evo 3D to come out and suck it up? Just not sure which road to take. Any help is GREATLY appreciated. And sorry if this has been asked previously, I did some searches and couldnt find much info.
To see if it's on your end, do a fresh install of your favorite ROM on its latest release. Preferable latest aosp or cyanogen stable. If it's still laggy, hardware. If not, then your hero is good. For the network, after you install a ROM, run a speed test. Then update to the latest prl. Run again. If it gets better, than great. If not, then proceed to update a Verizon prl. If good, than it's not your hardware. If it is, think about getting a replacement.
Great advice. Dont think I ever updated my PRL. How do I go about doing so and where do I get them? Fresh install is what I was leaning towards.
DozeBeatS said:
Great advice. Dont think I ever updated my PRL. How do I go about doing so and where do I get them? Fresh install is what I was leaning towards.
Click to expand...
Click to collapse
please go here and read the thread, if it's been a while you'll want to do the update manually, the most recent PRL is 01115.
http://forum.xda-developers.com/showthread.php?t=1046899
Lol Big duce is on the ball baby! Hooah!
Ok Im sold. Gonna update the PRL following the instructions in that thread. After that its a fresh install of either cm7 or aosp. Last question...Does a fresh install consist of wiping the data/factory reset and thats it? Or am I missing something? Again, TY so much. Quick response as well.
You on clockwork? You should if you aren't.
And a fresh install to me is wiping the dalvike, boot, cache, system, and data. Then installing the ROM.
I see everything except for boot, and system. And Im on Clockwork 2.5.0.7
I'm on 3.0.2.4, but in that version it's in the mount section.
Gotcha! Heres goes nothing.
DozeBeatS said:
I see everything except for boot, and system. And Im on Clockwork 2.5.0.7
Click to expand...
Click to collapse
my personal recommendation is aospCMod 4/21, for correct install instructions go to the wiki www.romrepo.info/wiki
il Duce said:
my personal recommendation is aospCMod 4/21, for correct install instructions go to the wiki www.romrepo.info/wiki
Click to expand...
Click to collapse
Will definitely take your advice.
Is it smart to use the google backup and restore feature?
DozeBeatS said:
Is it smart to use the google backup and restore feature?
Click to expand...
Click to collapse
Are you talking about the market app restore?
I guess thats what it was. So far everything is looking good. Will have to wait till I go to work tomorrow to see if the signal is any better. Thanks again!
When should you do a full wipe when installing a custom rom and when is it ok to dirty flash? Can someone please explain?
Sent from my HTC One using xda app-developers app
If you're changing bases it's always good to wipe. And if you're changing roms you should always wipe. But if you're just applying an update you might get away with a dirty flash. Save a backup first and you don't risk much with a dirty flash.
Sent from my HTC One using xda app-developers app
lampel said:
If you're changing bases it's always good to wipe. And if you're changing roms you should always wipe. But if you're just applying an update you might get away with a dirty flash. Save a backup first and you don't risk much with a dirty flash.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I apologize if this is a stupid question. When you say change base what exactly do you mean? Is this from one rom to another or a version change on the same rom like 5.0 to 6.0? Or is it a kernal change? If it is a version change would 5.1 to 5.6 be considered changing base?
Thank you very much. Again, I apologize if this is a dumb question. I have read around a little and did not quite get an answer I was comfortable with.
easyrabbit said:
I apologize if this is a stupid question. When you say change base what exactly do you mean? Is this from one rom to another or a version change on the same rom like 5.0 to 6.0? Or is it a kernal change? If it is a version change would 5.1 to 5.6 be considered changing base?
Thank you very much. Again, I apologize if this is a dumb question. I have read around a little and did not quite get an answer I was comfortable with.
Click to expand...
Click to collapse
What rom are you using?
CYNiCAL2KX said:
What rom are you using?
Click to expand...
Click to collapse
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------
easyrabbit said:
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
Click to expand...
Click to collapse
Sorry I meant ViperOne...
easyrabbit said:
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------
Sorry I meant ViperOne...
Click to expand...
Click to collapse
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
CYNiCAL2KX said:
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
Click to expand...
Click to collapse
Thank you very much for the info. So now I understand what the base is. Aside from time or laziness I would think that doing a full wipe is the way to go. Maybe I am wrong but I would rather not take chances.
Right now Iam currently having some issues. I basically did a dirty flash of the same version I am on to clear the theme and it went wrong. It never came back up after an hour in the "starting applications" state. After that I got back in to recovery (TWRP) and did full wipes and installs. They seem to go OK but then the android setup crashes right after the "name your device" part and the launcher wont start (chose Nova). Everything just hangs. I reboot but then it just hangs. I just did my nandroid restore and I am back up and running but not sure what is going wrong. I tried the install a few times with different options but everytime the setup part crashes. So my simple question is now another full blown issue haha.
I love this board tho, everyone is so helpful. One day I hope to be the one giving the advice.
CYNiCAL2KX said:
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
Click to expand...
Click to collapse
May I ask, is restoring the data folder similar to adb backup/restore or even titanium? With titanium I could just restore messages or whatever. Doing the whole data folder could put back something I dont want or something I want to get rid of. With my current situation I think this might solve my issue with setup but I really wanted to start from scratch and retweak everything.
Regarding the base, I cant seem to find where I can check that on the device. It is not in settings-about where I would expect to find it.
I am finally working my nerve up to try this again and figure out why the initial android setup is crashing. I am getting more comfortable now especially since I know my nandroid restore works. Good fun but scares the hell out of me at the same time when things go wrong haha....
easyrabbit said:
May I ask, is restoring the data folder similar to adb backup/restore or even titanium? With titanium I could just restore messages or whatever. Doing the whole data folder could put back something I dont want or something I want to get rid of. With my current situation I think this might solve my issue with setup but I really wanted to start from scratch and retweak everything.
Regarding the base, I cant seem to find where I can check that on the device. It is not in settings-about where I would expect to find it.
I am finally working my nerve up to try this again and figure out why the initial android setup is crashing. I am getting more comfortable now especially since I know my nandroid restore works. Good fun but scares the hell out of me at the same time when things go wrong haha....
Click to expand...
Click to collapse
Ususally most issues regarding cross flashed bases are problems derived from the system partition, however i'm not saying it doesn't happen, but I've never really had many issues restoring data. Also, once you back up data , you can install a Nandroid manager app where you can restore certain things from nand backups. This is what I chose to use over things like titanium as it's just another thing to do
CYNiCAL2KX said:
Ususally most issues regarding cross flashed bases are problems derived from the system partition, however i'm not saying it doesn't happen, but I've never really had many issues restoring data. Also, once you back up data , you can install a Nandroid manager app where you can restore certain things from nand backups. This is what I chose to use over things like titanium as it's just another thing to do
Click to expand...
Click to collapse
Thank you very much. I have heard back and forth on wiping the system but had never done it till now. I am still not sure what was happening. in my initial installs I allways removed sense and used Nova. The last time I left Sense and most off the apps. I also 're-downloaded the zip. it worked like a charm. soon I will start investigating kernals and updating firmwae and antennas. Will play with the basics for a while first tho. eventually I would like to try my own. However the bar is set high with venomone.
I am now dealing with sense which is ok bit for me Nova is as close to perfect a launcher for me. still investigating battery lifevetc but will probably do another flash removing sense. venomone fixed everything I didnt like about it for the most part but I love to be able to swipe up or down anywhere to get quickbar and app drawer... still testing tho, I have a full life but definitely want to contribute here... my new obsession.
Running Beanstalk.
Have been having intermittent issues with mobile data, so I'm sadly familiar with toggling Airplane mode, changing the CMDA subscription, rebooting, etc. in order to jog mobile data into working again. Lately have been having a weird, sporadic problem with people I call only hearing static on my end, so I chatted with Sprint, got to the point where they suggest typing the code to reset/update PRLs into the dialer, and bailed.
Then, in my infinite wisdom decided to try flashing a Sense ROM, proceeding with the manual PRL update/reset, and then wiping and restoring my Beanstalk nandroid.
Now I can't make or receive calls or texts at all, no matter what I do. Have tried all the old toggles. Have tried a complete reflash of Beanstalk. I'm beginning to worry I seriously borked something up.
Is anyone familiar with this kind of situation? Did I screw up, and if so, how bad? Any solutions anyone can think of? I'd be most grateful for any and all help. Thanks guys.
Reinstalling ROM from scratch and if that doesn't work then running ARU.
EPayne123 said:
Reinstalling ROM from scratch and if that doesn't work then running ARU.
Click to expand...
Click to collapse
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.
thedodus said:
What's ARU? I did try reinstalling the ROM from scratch and it didn't fix it.
Click to expand...
Click to collapse
Okay here is what you can do, there is an app floating around these forums that can allow you to manually write the prl, find that, and then use a stock prl for sprint. I believe this post will help:
http://forum.xda-developers.com/showthread.php?t=2296167
Let me know if that helps.
Oh and also yeah flashing a different rom wouldnt help because they do not contain any of that information, in fact i think all the carrier information is stored in a different partition for this exact reason -so they cant be easily overwritten.
I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS
BMP7777 said:
I build the Beanstalk here and haven't come across that issue yet. Do you have a backup of your original stock ROM? You need to get back to straight stock, like out of the box stock. From there, you can update your prls or anything else OTA-style, check your functionality, then redownload the Beanstalk ROM from here, do a full wipe(no internal data), install the fresh DL, Gapps, fix permissions(PhilzTouch 6.0.3.3 only), and reboot. Should be good to go and should only need to toggle airplane for reboots and occasionally for the wifi. Let me know how it goes, either here, on the BS thread or by PM. Good luck....
If you have no original back up(after getting back to straight stock, MAKE ONE), then use Bigdaddy619s threads on getting back to stock. After that, then follow the steps above.
You should always make an original back up of stock directly after rooting and unlocking. ALWAYS
Click to expand...
Click to collapse
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.
Yes, it should as long as everything worked then. Driving right now. Try it and let me know. When I get home I'll help however I can.
Sent from my One using XDA Premium 4 mobile app
thedodus said:
Thanks, both of you.
BMP - Beanstalk rules - it's definitely my fault. If I have a back-up made just after getting S-OFF, would that work?
matinm90 - thanks for the info...that explains exactly what the problem I'm having is.
I'll try these solutions out and post back. Thanks again guys.
Click to expand...
Click to collapse
Your welcome and yeah it should defintely work, just make sure you use the right prl
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
More than welcome. Glad you're up and running.:highfive:
thedodus said:
Worked!
I think what I'd originally goofed was not immediately rebooting after the prl update, since the Sprint lady didn't mention that step (or maybe I didn't hear her). This time I immediately rebooted and data came back, and then I was able to flash BeanStalk and stay functional.
Many thanks to both of you!
Click to expand...
Click to collapse
Your welcome glad you got everything straightened out
Sent from my HTCONE using Tapatalk
Hi all. I could use some help with this issue I've been having. Basically, about a week ago, I went on a trip to Colorado and at the same time had an issue with my data through VM. After talking to them, I had to change my service plan. Since then I haven't been able to maintain any kind of connection with VM; it reads no service a lot, even in places I've never had an issue (home, school, practically everywhere...). Before I deal with VMs customer service yet again, I wanted to see if there is any issues with my phone/rom/kernel and any updates to either I could use.
http://forum.xda-developers.com/desire-510/help/how-to-treat-sd-internal-storage-t3029186
I used this guide to root my phone and install all that stuff in order to use my sd card as my internal storage. So, could there be some issue with that wHich could cause me to not be able to get any service? Is there anything I could do on my side to determine if the problem is with my phone?
If the issue lies with VMs network, are there any updates to the kernel or roms with newer versions of Android that I could use and still use my sd card as my main storage? Side question: on any rooted device, could you do the ad card as main memory thing with the apps, Apparted and Link2sd?
Thanks anyone who can help me out.
Edit: I'm running Android 4.4.2
Kernel version
3.4.0-Missed-Kernel-v2.6.1
[email protected] #4
SMP PREEMPT
Build number
1.48.652.2 CL373881 release-keys
Umm, can think what else I should add. Thanks
Cypher5235 said:
Hi all. I could use some help with this issue I've been having. Basically, about a week ago, I went on a trip to Colorado and at the same time had an issue with my data through VM. After talking to them, I had to change my service plan. Since then I haven't been able to maintain any kind of connection with VM; it reads no service a lot, even in places I've never had an issue (home, school, practically everywhere...). Before I deal with VMs customer service yet again, I wanted to see if there is any issues with my phone/rom/kernel and any updates to either I could use.
http://forum.xda-developers.com/desire-510/help/how-to-treat-sd-internal-storage-t3029186
I used this guide to root my phone and install all that stuff in order to use my sd card as my internal storage. So, could there be some issue with that wHich could cause me to not be able to get any service? Is there anything I could do on my side to determine if the problem is with my phone?
If the issue lies with VMs network, are there any updates to the kernel or roms with newer versions of Android that I could use and still use my sd card as my main storage? Side question: on any rooted device, could you do the ad card as main memory thing with the apps, Apparted and Link2sd?
Thanks anyone who can help me out.
Edit: I'm running Android 4.4.2
Kernel version
3.4.0-Missed-Kernel-v2.6.1
[email protected] #4
SMP PREEMPT
Build number
1.48.652.2 CL373881 release-keys
Umm, can think what else I should add. Thanks
Click to expand...
Click to collapse
Tap settings and then scroll to the bottom and look for either software update or about phone and then look for the option to select PRL update, do that and then go back and do a profile update in the same spot as the PRL update and then reboot the phone.
MrMike2182 said:
Tap settings and then scroll to the bottom and look for either software update or about phone and then look for the option to select PRL update, do that and then go back and do a profile update in the same spot as the PRL update and then reboot the phone.
Click to expand...
Click to collapse
Yep, I've tried that one. But for the sake of thoroughness, I tried it twice more to no avail. Any other tips/tricks?
Cypher5235 said:
Yep, I've tried that one. But for the sake of thoroughness, I tried it twice more to no avail. Any other tips/tricks?
Click to expand...
Click to collapse
Flash this via twrp and let me know if it works.. After you flash this wipe the cache and dalvic cache too then reboot.
Edit: Are you running the stock rom or something else?
MrMike2182 said:
Flash this via twrp and let me know if it works.. After you flash this wipe the cache and dalvic cache too then reboot.
Edit: Are you running the stock rom or something else?
Click to expand...
Click to collapse
Alright, tried that, too, now. Still a no-go.
I'm not sure if I have a custom rom, but I don't think so. I just followed that guide, and I believe it only needed me to install a custom kernel. This thing acts weird. I'll pick it up and unlock it, and it will have 5 bars, but then quickly jump down to 1 then no service. As I'm driving to class, I'll have 4-5 bars but when I get to school, it's gone. It feels like whenever there are WiFi signals, I lose my service connection, if that helps.
Thank you so much, btw.
Cypher5235 said:
Alright, tried that, too, now. Still a no-go.
I'm not sure if I have a custom rom, but I don't think so. I just followed that guide, and I believe it only needed me to install a custom kernel. This thing acts weird. I'll pick it up and unlock it, and it will have 5 bars, but then quickly jump down to 1 then no service. As I'm driving to class, I'll have 4-5 bars but when I get to school, it's gone. It feels like whenever there are WiFi signals, I lose my service connection, if that helps.
Thank you so much, btw.
Click to expand...
Click to collapse
Install this and see what happens but first create a backup of your current system in recovery... http://forum.xda-developers.com/desire-510/orig-development/modded-cm11-32-bit-t3245291/post63749189
MrMike2182 said:
Install this and see what happens but first create a backup of your current system in recovery... http://forum.xda-developers.com/desire-510/orig-development/modded-cm11-32-bit-t3245291/post63749189
Click to expand...
Click to collapse
Hmm, definitely going to try this tonight. I've now tried to revert to my stock image, and things just haven't gone well since then. So, since I've already removed or backed up all data, should I just wipe everything (data, system, boot, cache, dalvik, etc), flash root, flash custom kernel, then restore this rom? That way, everything is fresh with no chance of interferences?
Cypher5235 said:
Hmm, definitely going to try this tonight. I've now tried to revert to my stock image, and things just haven't gone well since then. So, since I've already removed or backed up all data, should I just wipe everything (data, system, boot, cache, dalvik, etc), flash root, flash custom kernel, then restore this rom? That way, everything is fresh with no chance of interferences?
Click to expand...
Click to collapse
No flashing anything the boot/kernel is already in the folder just wipe and restore no using custom kernels there's already a custom kernel in it. It already has root access you do not even need a computer to do this just download extract and move the modded folder to twrps backup folder and restore. This is a full custom modified CyanogenMod 11.. Not stock rom at all.
MrMike2182 said:
No flashing anything the boot/kernel is already in the folder just wipe and restore no using custom kernels there's already a custom kernel in it. It already has root access you do not even need a computer to do this just download extract and move the modded folder to twrps backup folder and restore. This is a full custom modified CyanogenMod 11.. Not stock rom at all.
Click to expand...
Click to collapse
Okay, wow. I really like this, man. It's really slick. But, sadly, I'm still SOL. Sometimes there is a connection with VM, but it goes away quickly. I've really appreciated your help, but the problem seems to lay on VMs side, or there is a physical problem in my phone preventing it from maintaining a connection.
Im going to try to deal with their customer service and see if they can do anything. In the end, the phone only cost me $50, I guess. If I get it worked out, I'll post what it was about so you may be able to help the next guy with the issue, lol.
Cypher5235 said:
Okay, wow. I really like this, man. It's really slick. But, sadly, I'm still SOL. Sometimes there is a connection with VM, but it goes away quickly. I've really appreciated your help, but the problem seems to lay on VMs side, or there is a physical problem in my phone preventing it from maintaining a connection.
Im going to try to deal with their customer service and see if they can do anything. In the end, the phone only cost me $50, I guess. If I get it worked out, I'll post what it was about so you may be able to help the next guy with the issue, lol.
Click to expand...
Click to collapse
Lol that's definitely gotta be VM's side then.. I'm on VM to but let me ask you a question... Is that a pay as you go, like 1 monthly payment or is it prepaid? If it's the monthly payment then ask VM to reprovision the phone but restore back to your stock backup before calling.
MrMike2182 said:
Lol that's definitely gotta be VM's side then.. I'm on VM to but let me ask you a question... Is that a pay as you go, like 1 monthly payment or is it prepaid? If it's the monthly payment then ask VM to reprovision the phone but restore back to your stock backup before calling.
Click to expand...
Click to collapse
It's their $35/month unlimited plan. I just got off the phone with them after 1.5 hours, so not that long, lol. They claim there is a cell tower being worked on, and everything should clear up in 48-72 hours....and yet I can't get a stable signal 20 miles away at school, so it sounds like a rote answer when they have no clue. On the other hand, my wife's S2 barely gets a signal, too.
They are going to comp my for the 2 weeks it's been down, tho. If after this weekend there isn't any improvment....wwell, I'll figure something out, I guess.
Cypher5235 said:
It's their $35/month unlimited plan. I just got off the phone with them after 1.5 hours, so not that long, lol. They claim there is a cell tower being worked on, and everything should clear up in 48-72 hours....and yet I can't get a stable signal 20 miles away at school, so it sounds like a rote answer when they have no clue. On the other hand, my wife's S2 barely gets a signal, too.
They are going to comp my for the 2 weeks it's been down, tho. If after this weekend there isn't any improvment....wwell, I'll figure something out, I guess.
Click to expand...
Click to collapse
The "Cell tower being worked on" is just an incompetent fools answer because they in fact have no idea what the problem really is. What carrier does your wife have, VM to?
MrMike2182 said:
The "Cell tower being worked on" is just an incompetent fools answer because they in fact have no idea what the problem really is. What carrier does your wife have, VM to?
Click to expand...
Click to collapse
Lol, I've figured that one out when they told me that a couple months ago, I called back the next day and asked about the tower and they told me there was no record of any tower problems. Yeah, she's on VM also, with a Samsung S2, completely stock. When I check her signal, she has a connection, but it's low, around -100 to -120 dba.
Cypher5235 said:
Lol, I've figured that one out when they told me that a couple months ago, I called back the next day and asked about the tower and they told me there was no record of any tower problems. Yeah, she's on VM also, with a Samsung S2, completely stock. When I check her signal, she has a connection, but it's low, around -100 to -120 dba.
Click to expand...
Click to collapse
If it's both phones doing it then it's certainly not on your side.
MrMike2182 said:
If it's both phones doing it then it's certainly not on your side.
Click to expand...
Click to collapse
Hey Mike. I hate to bother you again, especially since I've been reading how much you've been dealing with other people, so I think I know how to do this, I just would like to run this by you to make sure I have it right.
I'm going to try to have VM replace my phone, so I need it back to looking clean.
1) So, I need to relock the bootloader first. I first "fastboot oem lock" in cmd, then.
2) I DL the RUU from HTC's site, specifically the VM 1.49.652.3 file.
3) While still in fastboot usb, I run the RUU repeatedly till it completes
4) Go back to hboot and do a factory reset.
Thanks man. I've tried to read things through, but I want to make sure it'll be clean if they do replace it.
Edit: Wait, I just saw someone said to input "fastboot oem rebootRUU" then run the RUU.
Cypher5235 said:
Hey Mike. I hate to bother you again, especially since I've been reading how much you've been dealing with other people, so I think I know how to do this, I just would like to run this by you to make sure I have it right.
I'm going to try to have VM replace my phone, so I need it back to looking clean.
1) So, I need to relock the bootloader first. I first "fastboot oem lock" in cmd, then.
2) I DL the RUU from HTC's site, specifically the VM 1.49.652.3 file.
3) While still in fastboot usb, I run the RUU repeatedly till it completes
4) Go back to hboot and do a factory reset.
Thanks man. I've tried to read things through, but I want to make sure it'll be clean if they do replace it.
Edit: Wait, I just saw someone said to input "fastboot oem rebootRUU" then run the RUU.
Click to expand...
Click to collapse
Just relock the bootloader then flash the stock recovery and then run the RUU from the PC but you don't need to factory reset after that because the RUU is the reset.