Develop Bugs

Problems flashing, need help please!!!

Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions? Also, I didn't want to try this and mess things up further, but can I restore a backup I had done when I had the virtuous rom installed, or do I have to have the rom already working properly? Kind of a noob question, I know.

calamari85 said:
Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions?
Click to expand...
Click to collapse
Hmmm... Do you have any Nandroids from earlier roms? That'd be the easiest route.
If not, since you can't even get to a homescreen, you might try an RUU reset, but let's hope it won't come to that for now.
I get that too, but only when going into the menu for Dalvik Cache wiping, and it never actually gets in my way, it just pops up and then I can keep going on about my business.

1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum

If you can't get a nandroid backup to work, you may have to RUU back to stock.
Here's the older one that will still let you use unrevoked after. Just rename this PB31IMG.zip, load up H-boot, follow the prompts, and be patient. Then run unrevoked when it finishes and install rom manager to restore your backup. If the backup still won't work, try a fresh install of virtuous.

Sorry
g00s3y said:
1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum
Click to expand...
Click to collapse
My apologies, where should I have posted? And can I move the thread so it is in the correct place?

calamari85 said:
My apologies, where should I have posted? And can I move the thread so it is in the correct place?
Click to expand...
Click to collapse
Probably in the Q & A General Forum, but don't worry about it this time, just as long as it doesn't end up being a frequent thing.
But I don't know about being able to move the thread, I think that's a Moderator power.
Regarding your issue though, either use the RUU link posted above, or try Nandroid-ing back.

No go
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.

calamari85 said:
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.
Click to expand...
Click to collapse
It's cool.
Yes, you'll need it on the root of your SD-card (not in any folders), run it through hboot, and then you'll have to re-run the unrEVOked tool from your PC. I would also suggest running the S-Off tool afterwards, just to be safe. That has saved me once before.
Make sure you have at least 50% battery before you do the hboot flash. VERY IMPORTANT. If your phone dies or loses power while updating the radio files from the RUU, your phone is as good as bricked.
If you get stuck with the unrEVOked tool at waiting for root for more than fifteen minutes, post back here again and we'll continue from there.
EDIT: Actually, run the unrEVOked Forever S-Off tool through CWM recovery before doing this, as a pure precautionary measure.

I'm an idiot apparently
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.

calamari85 said:
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.
Click to expand...
Click to collapse
Hahaha! No worries, we all have our moments!

Glad you figured it out. Be sure to make a backup of your current rom on your new SD card right away haha.

[Q] [SOLVED] Is my radio bricked? device no longer sees ANY SIM

-I have true s-off, permaroot and superCID
-ENG hboot and CWM work fine
-can successfully load and run ROMs
Device no longer sees a SIM card, yet been testing various ROMs for over 6 months with this handset.
I've taken it apart , and SIM slot looks ok.
I've tried eft wipe, superwipe, all my working nandroids, updated radio (currently running cm9/aokp40) to no avail.
Can anyone point me to how I can determine whether this is a S/W or H/W issue?
I'm leaning towards downgrading to stock/s-on then repeating the unlock to re-set my unlocked status for lack of any other options.
While googling not finding much if anything on radio data, so thanks in advance.
IF this is S/W based and you can help to fix I've a working TP2 in box as a reward/incentive.

If I am not mistaken the newer Roms need a newer SIM card, i.e.: the older ones (I think like 3-5 years old) won't be recognized with say the new radio (*.19)
I'm not sure what the new # is, but mine has 39.01a on the side, and works with the latest radio and CM9, EliteMod ICS, etc.
EDIT: But that might only refer to T-Mobile, not sure how it is with Fido/Rogers.

kbeezie said:
If I am not mistaken the newer Roms need a newer SIM card, i.e.: the older ones (I think like 3-5 years old) won't be recognized with say the new radio (*.19)
I'm not sure what the new # is, but mine has 39.01a on the side, and works with the latest radio and CM9, EliteMod ICS, etc.
EDIT: But that might only refer to T-Mobile, not sure how it is with Fido/Rogers.
Click to expand...
Click to collapse
Food for thought thanks, the SIM stopped being recognized after having flashed the "no service fix" update to this ROM http://forum.xda-developers.com/showthread.php?t=1749445 and have asked in that thread whether anything in the fix file could've set something off on my device.
IT IS an older SIM that I'm using but up to now have used every ROM with it without a hitch. I'll downgrade the radio now as an option.

igor45 said:
Food for thought thanks, the SIM stopped being recognized after having flashed the "no service fix" update to this ROM http://forum.xda-developers.com/showthread.php?t=1749445 and have asked in that thread whether anything in the fix file could've set something off on my device.
IT IS an older SIM that I'm using but up to now have used every ROM with it without a hitch. I'll downgrade the radio now as an option.
Click to expand...
Click to collapse
I noticed that it said "only for 2.7.13", though that seems to be specifically for a version of MUIU.
though when I unpack the fix :
Code:
assert(getprop("ro.product.device") == "vision" || getprop("ro.build.product") == "vision");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
unmount("/system");
Which basically only verifies that the phone is a HTC Vision (as per existing build.prop), mounts the /system partition, then extracts the package's content of /system to your rom
in this case a single file:
/system/framework/framework-res.apk
So from just that, I can't really see the fix having a prolong effect on all your other roms, unless you failed to do a full wipe (factory reset and wipe cache/dalvik cache in recovery before flashing a brand new rom).

This is the only thing I've changed in framework-res.apk:
Code:
<bool name="skip_restoring_network_selection">false</bool>

v1r0x said:
This is the only thing I've changed in framework-res.apk:
Code:
<bool name="skip_restoring_network_selection">false</bool>
Click to expand...
Click to collapse
right but even that change would be completely wiped out if he wiped/changed roms, so would have to be another factor that caused it.

kbeezie said:
right but even that change would be completely wiped out if he wiped/changed roms, so would have to be another factor that caused it.
Click to expand...
Click to collapse
Yes. Maybe it's just coincidence..
But I hope there is a fix for that problem.

Sounding like my SIM slot at this point then. But I didn't just flash the fix on its own. I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Sent from my HTC Vision using xda app-developers app

igor45 said:
Sounding like my SIM slot at this point then. But I didn't just flash the fix on its own. I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Maybe nothing to do with this but was using Elitemod/CM9/AOKP before flashing and "su" reported that it needed to close. I'D been experiencing few FCs with that ROM installed.
Didnt thing this would affect it once rebooted to CWM.

igor45 said:
I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Click to expand...
Click to collapse
which file do you mean with that?

igor45 said:
Maybe nothing to do with this but was using Elitemod/CM9/AOKP before flashing and "su" reported that it needed to close. I'D been experiencing few FCs with that ROM installed.
Didnt thing this would affect it once rebooted to CWM.
Click to expand...
Click to collapse
Can you be more specific on the EliteMod part, are you simply talking bout the EliteMod ICS rom, or putting EliteKernel on top of a CM9 or AOKP port? (if just the rom, I'm not aware of a 'fix' that was meant for EliteMod).

v1r0x said:
which file do you mean with that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28906048&postcount=74
... maybe something in yozgats file?

igor45 said:
http://forum.xda-developers.com/showpost.php?p=28906048&postcount=74
though I see it doesn't include the fix... maybe something in yozgats file?
Click to expand...
Click to collapse
Are you saying you used a fix from one rom (light) with another rom (elitemod)? I'm not getting very clear information from you just bits and pieces.

to clarify
kbeezie said:
Are you saying you used a fix from one rom (light) with another rom (elitemod)? I'm not getting very clear information from you just bits and pieces.
Click to expand...
Click to collapse
LOL - bit of a noob here though not that bad, so no I didn't mix fixes/ROMs :highfive:
I was on latest Elitemod/CM9/AOKP
To be clear,
1 - I first flashed the file from post 74 in the thread that included the bugfixes and few enhancements to the original.
(So wondering whether there's something in that file, and yes it does include the fix)
----this is where "no sim inserted" occurs---
2 - when ROM came up good but no SIM, i reverted to my nandroids, trying each one of them.
3 - then tried full wipes with fresh ROM flashes
4 - then tried superwipe/efs wipe AND updated radio and tried each nandroid/fresh installs again
5 - now downgraded radio to what I had (minus the rils) and living with WIFI only connection til I can fix the SIM issue

btw "Elitemod/CM9/AOKP" are three different roms If you just mean EliteMod ICS just say that , helps reduce the confusion. (since some people do separately install AOKP or CM9 by itself, and then flash EliteKernel on top of those).
k, as for #1 when I originally read about the 'fix', that was for a completely different rom than EliteMod and course probably wouldn't work anyways.
Secondly with EliteMod ICS, I've found that I had to be on the .19 radio (note my signature) in order to boot up with it and manage both data and wifi connection, there was no need to 'patch' anything because nik3r already included the proper ril/data for the newest radio in the rom/kernel itself. And it doesn't matter if you're on either the G2 hboot (0.76.0000 I think) or the DZ hboot like I have, since it's not a sense rom or a rom of that size.
If you are on a functional phone right now (outside of the non-Wifi data connection of course), I would recommend upgrading your recovery to 4EXT recovery first (something like the 4EXT Touch Recovery 1.0.0.5 RC5 that can be installed from the app, the app itself is found in google play and can install the recovery for you, there is a free version of the app that I have if you simply want the installer but I Recommend the paid version since you can control most of it's preferences from the app before rebooting into recovery).
From there (assuming you have everything you need backed up to the computer including say any titanium backup files):
Just to knock out a number of possibilities will just act like we're going to do a 'full' setup, assuming that 1) You are already using an ENG S-OFF hboot and 2) have already upgraded the radio to the latest .19 version
1) re-partition the SD card via 4EXT (I recommend a 2GB sd-ext, skipping the sd-ext2 and skipping swap), so that's freshly setup [that and if you chose to use the dataswap mod for EliteMod the 2GB sd-ext is needed to compliment it, never make a sd-ext less than ~1.5GB in size]
2) once you got that re-partitioned toggle the USB storage so you can copy back all the files you need including the rom files etc etc.
3) "Wipe/Format" menu to do
a) Factory Reset/Wipe
b) wipe cache+dalvik
c) Battery stats (cuz why the hell not, it *could* help lol)
4) No need to do an EFS wipe since the EliteMod rom zip does this for you upon installation, so Flashing the EliteMod Rom, then any optionals (Gtalk, google gallery, T-mobile wifi calling, DataSwap mod) on top of that.
PS: if you like to multitask active apps quite a bit (i.e.: background notifications etc), I would recommend the 64MB Dataswap mod at the very least, especially with all that free space you'll have on /data partition from the use of an sd-ext partition.
5) Reboot, once fully booted, reboot again
6) check connectivity for both SIM/Wifi/Etc.
If you're *still* having problems, even after physically pulling the sim out, blowing some dust out, or whatever you can and putting it back in, I'd start to wonder if 1) the sim is too old for whatever reason [ie: with whatever update], 2) the sim got damaged [maybe via some kind of sim update?], or 3) the sim slot is maybe damaged? 4) or the universe just hates you right now.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
PS: I highly recommend Titanium Backup, it's been very useful in flashing a fresh clean rom, but then being able to restore most of my applications with their settings/data intact.

kbeezie said:
btw "Elitemod/CM9/AOKP" are three different roms If you just mean EliteMod ICS just say that , helps reduce the confusion. (since some people do separately install AOKP or CM9 by itself, and then flash EliteKernel on top of those).
k, as for #1 when I originally read about the 'fix', that was for a completely different rom than EliteMod and course probably wouldn't work anyways.
Secondly with EliteMod ICS, I've found that I had to be on the .19 radio (note my signature) in order to boot up with it and manage both data and wifi connection, there was no need to 'patch' anything because nik3r already included the proper ril/data for the newest radio in the rom/kernel itself. And it doesn't matter if you're on either the G2 hboot (0.76.0000 I think) or the DZ hboot like I have, since it's not a sense rom or a rom of that size.
If you are on a functional phone right now (outside of the non-Wifi data connection of course), I would recommend upgrading your recovery to 4EXT recovery first (something like the 4EXT Touch Recovery 1.0.0.5 RC5 that can be installed from the app, the app itself is found in google play and can install the recovery for you, there is a free version of the app that I have if you simply want the installer but I Recommend the paid version since you can control most of it's preferences from the app before rebooting into recovery).
From there (assuming you have everything you need backed up to the computer including say any titanium backup files):
Just to knock out a number of possibilities will just act like we're going to do a 'full' setup, assuming that 1) You are already using an ENG S-OFF hboot and 2) have already upgraded the radio to the latest .19 version
1) re-partition the SD card via 4EXT (I recommend a 2GB sd-ext, skipping the sd-ext2 and skipping swap), so that's freshly setup [that and if you chose to use the dataswap mod for EliteMod the 2GB sd-ext is needed to compliment it, never make a sd-ext less than ~1.5GB in size]
2) once you got that re-partitioned toggle the USB storage so you can copy back all the files you need including the rom files etc etc.
3) "Wipe/Format" menu to do
a) Factory Reset/Wipe
b) wipe cache+dalvik
c) Battery stats (cuz why the hell not, it *could* help lol)
4) No need to do an EFS wipe since the EliteMod rom zip does this for you upon installation, so Flashing the EliteMod Rom, then any optionals (Gtalk, google gallery, T-mobile wifi calling, DataSwap mod) on top of that.
PS: if you like to multitask active apps quite a bit (i.e.: background notifications etc), I would recommend the 64MB Dataswap mod at the very least, especially with all that free space you'll have on /data partition from the use of an sd-ext partition.
5) Reboot, once fully booted, reboot again
6) check connectivity for both SIM/Wifi/Etc.
If you're *still* having problems, even after physically pulling the sim out, blowing some dust out, or whatever you can and putting it back in, I'd start to wonder if 1) the sim is too old for whatever reason [ie: with whatever update], 2) the sim got damaged [maybe via some kind of sim update?], or 3) the sim slot is maybe damaged? 4) or the universe just hates you right now.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
PS: I highly recommend Titanium Backup, it's been very useful in flashing a fresh clean rom, but then being able to restore most of my applications with their settings/data intact.
Click to expand...
Click to collapse
Yes understood that the "fix" was a trivial patch and that it pplies only to the MIUI multilang version in question - trust me I would not have mixed those two up. I opted to first flash the version from the later post since it included app/framework enhancements WITH the "no service fix"
Yes I was on Elitemod ICS (AOKP base) with modified CM9 kernel. Sorry for that confusion.
I'd previously used Elitemod AND AOKPs with my old radio with no issues whatsoever. never had to tweak a thing.
FWIW I'm on hboot .84.2000 ENG s-off and yes using clockworkmod recovery
I'd like to try 4ext - looking into it now.
Appreciate the help.
Maybe I'll put this on hold til I get a new sim from FIDO...

igor45 said:
Maybe I'll put this on hold til I get a new sim from FIDO...
Click to expand...
Click to collapse
Yea the issue in general sounds just weird overall, hopefully it'll get resolved one way or another.

kbeezie said:
Yea the issue in general sounds just weird overall, hopefully it'll get resolved one way or another.
Click to expand...
Click to collapse
Indeed - still hoping that there's someone that can offer a method of testing to see whether its a H/W issue. Must be somethng in adb and/or bootlogs? Perhaps in the bootloader for Radio.

well reading over this thread have you tried another sim? your sim in another phone? you can run some very simple tests in the diagnostics menu. go to dialer and type *#*#4636#*#*
go into phone info and play around with turning radio on and off and gsm only etc to see if anything appears ok. the best ways to test software/firmware or hardware faliure you seem to have tried, wipe fully, flash new rom, new radio...
I guess you can always try to unroot? if it still won't work then my guess is hardware
Sent from my HTC Vision using xda premium

demkantor said:
well reading over this thread have you tried another sim? your sim in another phone? you can run some very simple tests in the diagnostics menu. go to dialer and type *#*#4636#*#*
go into phone info and play around with turning radio on and off and gsm only etc to see if anything appears ok. the best ways to test software/firmware or hardware faliure you seem to have tried, wipe fully, flash new rom, new radio...
I guess you can always try to unroot? if it still won't work then my guess is hardware
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
thx for the suggestions
Have my sim working in my backup phone and works in every other phone I've tried. Yes have also tried airplane mode on/off data on/off - etc...
Did try to unroot yesterday but ran out of time, had to run off to work.
Want to do it right so will try again today as I've a bit more time.
playing with diagnostics menu now thanks.

Flashing a ROM that's already been flashed on your phone

Title pretty much says it all but i have a question..Let's say i was to flash a ROM onto my phone that i had already flashed before but then decided to flash a different one but i also kept the .ZIP file on my phone. If i was to flash back to that old ROM would i keep certain things like the WIFI codes and the wallpaper i had before i went to a new ROM?Because this seems to be a problem for me. Also Would this problem be fixed if i downloaded a fresh ROM copy from the internet or off my Laptop?

Seshin said:
Title pretty much says it all but i have a question..Let's say i was to flash a ROM onto my phone that i had already flashed before but then decided to flash a different one but i also kept the .ZIP file on my phone. If i was to flash back to that old ROM would i keep certain things like the WIFI codes and the wallpaper i had before i went to a new ROM?Because this seems to be a problem for me. Also Would this problem be fixed if i downloaded a fresh ROM copy from the internet or off my Laptop?
Click to expand...
Click to collapse
Flashing the exact same ROM over your current ROM will tend to cause no issues, but no guarantee. Flashing to a different ROM, now thast a whole new can of worms. Its HIGHLY ADVISED to wipe all data and cache then flash. Use TDJ superwipe in CWM to do this, or you can use TWRP and do a factory reset. Now, depending on the ROM, you either flash gapps, or sign in into google. Either way, you have to sign in. If you would to chose to google to back up your phone, which is the default settings, then your wifi and wallpaper will be restored. You might have to restart to get the wallpaper back. Having the ZIP on your phone makes no difference in the way the ROM installs. The zip is no different then any other piece of data on your phone. You can find all the resources ive mentioned the development thread.

LoopDoGG79 said:
Flashing the exact same ROM over your current ROM will tend to cause no issues, but no guarantee. Flashing to a different ROM, now thast a whole new can of worms. Its HIGHLY ADVISED to wipe all data and cache then flash. Use TDJ superwipe in CWM to do this, or you can use TWRP and do a factory reset. Now, depending on the ROM, you either flash gapps, or sign in into google. Either way, you have to sign in. If you would to chose to google to back up your phone, which is the default settings, then your wifi and wallpaper will be restored. You might have to restart to get the wallpaper back. Having the ZIP on your phone makes no difference in the way the ROM installs. The zip is no different then any other piece of data on your phone. You can find all the resources ive mentioned the development thread.
Click to expand...
Click to collapse
P.S Don't be afraid to wipe all your system data. It won't touch your SD card. Your pics and files will be safe. Only your ROM and programs with its data will be deleted. Use titanium backup or ROM toolbox to back up your data. SMS backup is a good program to backup your SMS.
Sent from the pink Unicorn from the Darkside.

Seshin said:
Title pretty much says it all but i have a question..Let's say i was to flash a ROM onto my phone that i had already flashed before but then decided to flash a different one but i also kept the .ZIP file on my phone. If i was to flash back to that old ROM would i keep certain things like the WIFI codes and the wallpaper i had before i went to a new ROM?Because this seems to be a problem for me. Also Would this problem be fixed if i downloaded a fresh ROM copy from the internet or off my Laptop?
Click to expand...
Click to collapse
Strictly answering your specific question... "If i was to flash back to that old ROM (ed: after flashing a different one) would i keep certain things like the WIFI codes and wallpaper i had before i went to a new ROM?"
Simple answer: NO. When you flash a ROM, generally whatever was on the phone will be lost. Generally, it's like installing a new copy of Windows on a hard drive that has been partitioned into more than one partition. Whatever was in the partition the new Windows was installed to will be overwritten (<< note key word). Stuff that got overwritten will be lost. Stuff that doesn't MAY still be accessible assuming you didn't format the partition first. While stuff that is in the other partition will likely still be there, but may not be useable due to various reasons. In the PC example: installing Windows on a formerly Linux pc and retain the other linux partitions. The data's still there, but Windows (without massive driver/software support) will not be able to read the other partition and will ask you to format before using, which WILL then destroy all data there.
Stuff like wallpaper, it depends. If it's a wallpaper that was a file saved on your SD card or one of the stock wallpaper that came with the ROM, you can reuse it, however, you WILL need to reselect it (unless the stock wallpaper was the default one, which sounds like it was not, in your case).
Stuff like WiFi codes, all bets are off, and I wouldn't put any $ down as chances are VERY good that that information will have been erased. That's why you are supposed to keep backup of that information, preferably in a location away from the device.
Only data stored on the SD card and whatever partition that was not specifically erased/overwritten by the installation process will remain, and if you follow generally good practices, you should have had erased the various partitions and caches on top of the installation to ensure maximum reliability of the ROM. Thus only what you have on the SD is the only thing that would be retained after a ROM installation.
---------- Post added at 12:27 AM ---------- Previous post was at 12:12 AM ----------
LoopDoGG79 said:
P.S Don't be afraid to wipe all your system data. It won't touch your SD card. Your pics and files will be safe. Only your ROM and programs with its data will be deleted. Use titanium backup or ROM toolbox to back up your data. SMS backup is a good program to backup your SMS.
Click to expand...
Click to collapse
I agree, I too use Titanium. If you're really concerned about saving data (like that WiFi codes), then you will need something like Titanium and a SD card. Just remember to restore that data.
Please be aware that this assumes that you are using the saved data from the original ROM and, after trying a different ROM, you are going back to the first one.
If you are trying to migrate data (like the WiFi Code), for example, from the second ROM to the first ROM, this will only work IF both ROMs used the same software to handle WiFi and data are stored/used the same way in both ROMs.
That's why it's a good idea to keep a hard copy of the account and password information backed up separately from the application that's using the information. At the very least, in a text file stored on the SD card. I prefer using Dropbox and store it OFF the phone itself.

[Q] Wifi not turning on! Please Help.

Hello, Im new to all of this so please understand. Okay, I have a Sprint GS3, I rooted it using the toolbox thing it worked but I decided that I didnt want the root anymore. I loaded stock software and booted it up normal. The only problem now is my wifi isnt turning on. Ive searched page after page on google, ask and bing. I dont know what to do anymore. Im just about to just say screw it and give up. Any help will be much appreciated.

You Odin'd back to Stock, and now your WiFi is not working correctly ? Are you certain your connecting to your Router ? Did you check the Router to make sure it's working correctly ? Did you try to connect to the Router with another Device ?

If you still have a custom recovery installed, I'd say to just flash another rom. The toolbox kills your WiFi fir sine reason, which can only be fixed by flashing another kernel, and roms have the kernels built in so, you might as well kill two birds with one stone
You could just flash stock rooted though, no need to go full out custom

Wifi not turning on
What I mean is my phone's wifi wont turn on at all. How do I get everything back to normal like before I rooted it?

Brblank44 said:
What I mean is my phone's wifi wont turn on at all. How do I get everything back to normal like before I rooted it?
Click to expand...
Click to collapse
Ok, this method should work and do exactly what you wanted, but you'll still have root access.
Below, I have quoted a post I made a while back when trying to help someone out.
Down below I link to Freeza's stock Rom, which is what you want if you want the stock phone with root. The one you want to download is the DeOdex MD4 one:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMD4 | Mirror
MD5: 77262D9D6CF1A6AF30A8981A95A75D57
Click to expand...
Click to collapse
In step #4, the wipe system is very important. It's most likely that something in your /system folder is messing up your wifi. Just flashing a new Rom over might not fix it. I'd also wipe /data, 'cause a fresh wipe is much less likely to have issues.
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to the rooting guide and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse

Brblank44 said:
What I mean is my phone's wifi wont turn on at all. How do I get everything back to normal like before I rooted it?
Click to expand...
Click to collapse
Yes. The toolbox kills your WiFi completely and you have to flash another rom to fix it. Flash stock rooted from freezas thread and you should be good to go.

CNexus said:
If you still have a custom recovery installed, I'd say to just flash another rom. The toolbox kills your WiFi fir sine reason, which can only be fixed by flashing another kernel, and roms have the kernels built in so, you might as well kill two birds with one stone
You could just flash stock rooted though, no need to go full out custom
Click to expand...
Click to collapse
Why do people use a toolbox on a phone that's so easy to root without it?

flastnoles11 said:
Why do people use a toolbox on a phone that's so easy to root without it?
Click to expand...
Click to collapse
When I first rooted my phone (back pre LJ7 days), I used it because I came from the EVO 4G, which was notoriously difficult to root (and which needed a toolkit). So when I came to the GS3, I figured it'd be the same way. Fortunately, the toolkit worked better back then and I didn't have an issue. Now that I've helped others use Odin (and have used it myself a number of times), I don't point to the toolkit anymore.
But my point is, sometimes people assume it's difficult, see a toolkit that is meant to make it easier and decide that's the way to go.

topherk said:
Ok, this method should work and do exactly what you wanted, but you'll still have root access.
Below, I have quoted a post I made a while back when trying to help someone out.
Down below I link to Freeza's stock Rom, which is what you want if you want the stock phone with root. The one you want to download is the DeOdex MD4 one:
In step #4, the wipe system is very important. It's most likely that something in your /system folder is messing up your wifi. Just flashing a new Rom over might not fix it. I'd also wipe /data, 'cause a fresh wipe is much less likely to have issues.
Click to expand...
Click to collapse
Thank you very much. I will try this as soon as I can.

topherk said:
When I first rooted my phone (back pre LJ7 days), I used it because I came from the EVO 4G, which was notoriously difficult to root (and which needed a toolkit). So when I came to the GS3, I figured it'd be the same way. Fortunately, the toolkit worked better back then and I didn't have an issue. Now that I've helped others use Odin (and have used it myself a number of times), I don't point to the toolkit anymore.
But my point is, sometimes people assume it's difficult, see a toolkit that is meant to make it easier and decide that's the way to go.
Click to expand...
Click to collapse
I get that, but just a tiny bit of reading around well show you the toolkit is actually the harder way to root this phone in my opinion... Just saying

flastnoles11 said:
I get that, but just a tiny bit of reading around well show you the toolkit is actually the harder way to root this phone in my opinion... Just saying
Click to expand...
Click to collapse
I totally agree that the toolkit is much more complicated and a bit of a "black box." Hence why I don't recommend it anymore.
But back then, even though I read a whole lot, I decided to go with the toolkit because it felt safer. Heck, I eevn donated so I could get the "pro" features! And for people who aren't that comfortable "hacking" things, it's tempting to use something that'll do the "hard work" for you, even if the normal way of doing it is relatively simple.
That's why I always try to spell things out very clearly for people (I do like numbered lists, don't I?). If someone responds to a thread with "just wipe data and flash a new rom," most "noobs" will hesitate because while they may know those terms, they don't know the procedure and will be afraid of messing it up. With the numbered list of instructions, they typically feel much more comfortable with doing it themselves.
Just my two cents.

Yeah, very true (@topherk). The first time I rooted my firdt phone, I saw all the guides and stuff, but settled on a toolkit sort of program to do it for me...subsequent phones I've always rooted by hand. For me it kinda sucks that there's no way to root the S3 manually (as in like, push this to.the phone, reboot, run this command then flash recovery)
Having come from 2 HTC devices (evo and evo shift), I kinda feel like ODIN is a "cheating" way to root lol. But that's just me.

Whats a md5? It says no md5 file and gives me an error.

Brblank44 said:
Whats a md5? It says no md5 file and gives me an error.
Click to expand...
Click to collapse
Thats normal,.the great majority of flashable zips do not include an md5 file.
What that is referring to is a hashing function, called the md5sum, that can be used to verify the integrity of a file. Most devs will provide this (in number format) so that you can check the md5sum of your local copy/download against what they provide. If anything goes wrong in a download or file transfer, the md5sum of your copy will not match the expected value, confirming that it was a bad download or that something went wrong along the way.
For your case, TWRP always checks to see if the flashable zip includes an md5sum check file that it can check your file against as an added precaution that you're not flashing something corrupted.

Brblank44 said:
Whats a md5? It says no md5 file and gives me an error.
Click to expand...
Click to collapse
Don't do the md5 verification in the Recovery. That typically fails, even if the md5 is correct.
I typically do it in Windows (I use this program, works great). If it's a really large file or I don't feel confident about the cable I'm using, I'll also check the md5sum in ES Explorer on the phone after I transfer it.

Okay I flashed it and I have the same problem. Wifi not turning on. The detox whatever its called didn't work. So I took it to sprint today after having flashed it and everything and they did a hard reset. I lost everything. Sprint couldn't swap the phone out for a new one. I am thinking about sending it back to samsung. So they can fix it. Any other ideas guys? Also thank you for your understanding and helping me.

Brblank44 said:
Okay I flashed it and I have the same problem. Wifi not turning on. The detox whatever its called didn't work. So I took it to sprint today after having flashed it and everything and they did a hard reset. I lost everything. Sprint couldn't swap the phone out for a new one. I am thinking about sending it back to samsung. So they can fix it. Any other ideas guys? Also thank you for your understanding and helping me.
Click to expand...
Click to collapse
Brblank,
Try this easy method to return to stock everything including recovery, flash count reset and device status normal. It worked perfectly for me.
Before flashing wipe Cache and Dalvik and factory reset.Then flash the file. Make sure you choose the correct file (16gb or 32gb version).
Even if it doesn't fix your WiFi issue it will put your phone in the proper state to send to Samsung.
You can place the file on your internal or external card.
Return to Stock Link
With much thanks to billard412
Hope this helps you.

Flashing ROMs question

I want to flash a custom rom, had one before pie came out, is there a way to keep all my shiz on the phone? Like music etc, and flash factory image and then a custom rom? Basically, if i wipe data and cache is that going to take my music, pics etc out? I know it's a dumb question, but with no external storage it's quite the ordeal to put all the music back on! And flashing isn't like it used to be, way more complicated these days haha.

Zooandbio4me said:
I want to flash a custom rom, had one before pie came out, is there a way to keep all my shiz on the phone? Like music etc, and flash factory image and then a custom rom? Basically, if i wipe data and cache is that going to take my music, pics etc out? I know it's a dumb question, but with no external storage it's quite the ordeal to put all the music back on! And flashing isn't like it used to be, way more complicated these days haha.
Click to expand...
Click to collapse
Short answer, yes. Doing a twrp factory reset doesn't wipe your internal storage before you flash a rom. You can fastboot the factory image with the -w removed from the flash-all.bat script, which also doesn't wipe data. So, you should be fine. However, always backup all your "shiz" on your pc before you start. Just in case ya know!

Zooandbio4me said:
I want to flash a custom rom, had one before pie came out, is there a way to keep all my shiz on the phone? Like music etc, and flash factory image and then a custom rom? Basically, if i wipe data and cache is that going to take my music, pics etc out? I know it's a dumb question, but with no external storage it's quite the ordeal to put all the music back on! And flashing isn't like it used to be, way more complicated these days haha.
Click to expand...
Click to collapse
short answer, no, but I wished there was a way. I remember the days when smartphones had external sd cards where I could store my personal files in the sd card while flashing the rom into the internal 'sd card.'
Even though you can remove the -w when flashing, I've noticed many times from personal experience that there will be problem ... either the rom won't boot up or the apps will constantly crash or other issues. The only time you can remove -w when flashing (based on my experience) is when you are dirty flashing a version upgrade of the same rom ...

Anyone else care to weigh in?

Do exactly what Badger50 says. EXACTLY!

https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761 Use the script from the link to flash any stock rom without wiping internal. This is much easier than editing in -w. This is in my opinion the safest way to flash stock firmware. After that just root and flash your rom through twrp. I'm shocked nobody mentioned the script already. It is a God send for this device. It can even recover the phone from a bricked state with internal data in tact. If ever you run into a non bootable state when flashing roms(mainly due to firmware date vs rom date) just flash stock again using the script.

Zooandbio4me said:
Anyone else care to weigh in?
Click to expand...
Click to collapse
Why couldn't you make a nandroid TWRP backup, move the backup files to an external source (flashdrive or computer/external hdd), wipe everything, install custom ROM, then move backup files back to Pixel 2 XL (keeping in mind TWRP's folder structure; /sdcard/TWRP/BACKUPS/serial#/backupcreationdate/), and run the TWRP Restore option (only the "Data" partition need be restored)???
Word of warning, TWRP normally doesn't backup the internal sd files (where your pictures and music files reside); but there is a convoluted way to include those files in the backup -- it'll just take a couple extra steps at the backup phase and restore phase. Let me know and I'll lay the directions out for you (and/or refer you to where I learned of the method...).

Badger50 said:
Short answer, yes. Doing a twrp factory reset doesn't wipe your internal storage before you flash a rom. You can fastboot the factory image with the -w removed from the flash-all.bat script, which also doesn't wipe data. So, you should be fine. However, always backup all your "shiz" on your pc before you start. Just in case ya know!
Click to expand...
Click to collapse
I can't agree more with the advice to back up... Badger50 knows first hand as well as many of us that even the simplest procedure can go sideways in the blink of an eye. Both him and I for instance had failures while upgrading to Pie while others never missed a beat.
I personally keep a zipped up copy of my TIBU folder on my pc along with a backup of my sms, call log, calendars, Nova data, photos, music, downloads dir.
All in all its about 30 gigs that I periodical back up overnight when needed. Yes it's an overkill but I can basically reproduce my setup if it goes south. That and I'm a lunatic that has pretty much had the same setup and desktop for the last 4 phones. Lol

CyberpodS2 said:
...
I personally keep a zipped up copy of my TIBU folder on my pc along with a backup of my sms, call log, calendars, Nova data, photos, music, downloads dir.
...
Click to expand...
Click to collapse
The SMS, call log, calendars, and photos, aren't they included in the automatic Google backup?

CyberpodS2 said:
I can't agree more with the advice to back up... Badger50 knows first hand as well as many of us that even the simplest procedure can go sideways in the blink of an eye. Both him and I for instance had failures while upgrading to Pie while others never missed a beat.
I personally keep a zipped up copy of my TIBU folder on my pc along with a backup of my sms, call log, calendars, Nova data, photos, music, downloads dir.
All in all its about 30 gigs that I periodical back up overnight when needed. Yes it's an overkill but I can basically reproduce my setup if it goes south. That and I'm a lunatic that has pretty much had the same setup and desktop for the last 4 phones. Lol
Click to expand...
Click to collapse
Yes! +1 on this post!
Since I update the monthly security updates by flashing the Full Factory images and have to connect the phone to a computer anyways, I make sure to create a nandroid TWRP backup (a special method that will also include the internal sd folders/files as well as the /data partition), and after -- while the phone is connected to the computer to run the fastboot, adb, and flash-all commands -- I copy the TWRP backup folder to the computer while at things. I also make sure to not delete the previous 3 months; just in case. So, that's two TWRP backups at any given time; one, residing in the phone, just in case it is direly needed and I can't get home and access the computer soon enough, and then another copy safe in an external location. I would do a whole TB backup, compressed, and zipped folder or an adb backup method, but I find that the nandroid backups perfectly do the trick; and, in certain cases, TB can access certain nandroid data as well. I used to do this with FlashFire and my S5 as well...
Seriously, -- especially, as I've found with this device -- you can't be too careful! It is a lot safer with the "bootloader" now -- I recall long in the past that any type of flashing and the words "stock image" was last resort rescue -- but one can't get too complacent and develop a false sense of security (speaking from experience of unintentionally but manually formatting all partitions including the bootloader which caused a pure-brick experience and had no way of accessing the phone's internals at that point).
TL;DR Make backups...NOW! If you don't have at least two currently, then RIGHT NOW! Google has given us so many "outs" and rescue potential with the bootloader access, we only have ourselves to blame by not going about it as smart as possible and neglecting to make enough backups -- especially when doing things like "flashing" or modifying any partition -- for recovery, custom ROMS, theme or launcher type modifications, or any other modifications. Being able to revert back to the stock state with minimal hassle is a "Godsend"!
*note: as you can tell, I don't think it's overkill...

Nikos2k said:
The SMS, call log, calendars, and photos, aren't they included in the automatic Google backup?
Click to expand...
Click to collapse
I use an app called Super Backup Pro. It uploads the backups to gmail or Drive. Either way it's much faster to restore stuff than waiting on the Google stuff. Also, I never let google restore apps. I know what I can and can't restore data on with TIBU. 90% I can. The other stuff mostly doesn't need local data anyway.
That and my internet blows chunks out here in the boonies...

CyberpodS2 said:
I use an app called Super Backup Pro. It uploads the backups to gmail or Drive. Either way it's much faster to restore stuff than waiting on the Google stuff. Also, I never let google restore apps. I know what I can and can't restore data on with TIBU. 90% I can. The other stuff mostly doesn't need local data anyway.
That and my internet blows chunks out here in the boonies...
Click to expand...
Click to collapse
Damn chunk blowing internet! I hate them things! :laugh:

Ok so I think I've got it, nandroid/twrp backup, flash Ota then rom of choice. Any 9.0 roms that have the active edge feature? Seems like they're all based off aosp which I understand does not have this and most other features.

Zooandbio4me said:
Ok so I think I've got it, nandroid/twrp backup, flash Ota then rom of choice. Any 9.0 roms that have the active edge feature? Seems like they're all based off aosp which I understand does not have this and most other features.
Click to expand...
Click to collapse
Active edge is indeed not implemented in custom roms, as it is not part of aosp
(however it is said that DU team managed to reverse engineer it so maybe we will see it in future versions of custom roms)
All other features of stock rom (and numerous other features that stock rom lacks) are included

Zooandbio4me said:
Ok so I think I've got it, nandroid/twrp backup, flash Ota then rom of choice. Any 9.0 roms that have the active edge feature? Seems like they're all based off aosp which I understand does not have this and most other features.
Click to expand...
Click to collapse
DUs latest RC has active edge working. You can set it to trigger things like flashlight, camera, assistant etc.