Hello,
I've managed to get my build.prop in a state where I can't update (I assume it's the build prop). I've tried the backups I have, but none of them are working. I'm currently on 4.1.1 and I was hoping someone has backup.
Thanks in advance!
for clarity: Verizon Galaxy Note II 4.1.1 Stock ROM, Stock Recovery, Rooted
The Failing update is update_SCH-I605_LL4_to_MC3 which fails with code 402
Download the stock ROM in Development and pull it from there
Sent from my SCH-I605 using xda app-developers app
Bfitz26 said:
Download the stock ROM in Development and pull it from there
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Trevski13 said:
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Click to expand...
Click to collapse
Download the recovery flashable stock rom, the zip file, and extract it from that using 7zip.
Sent from my SCH-I605 using XDA Premium HD app
Trevski13 said:
I Downloaded the image and extracted it, now I have a "system.img" file which I assume contains the files but what do I do with it? I tried mounting/extracting and nothing worked.
Click to expand...
Click to collapse
Using ES File explorer. Setup up your root explorer. and change permissions by using tools to System R/W.
Use ES File explorer to open the stock download and navigate to system/build.prop Copy it. Go back to your system and Rename the one there to build.bak. Then paste the new one there. This way you have the original saved if it turns out not to be the build.prop. My guess is. If you are on a rooted, stock rom like you said. The build.prop's are going to be identical. Thinking the culprit might be whatever you are trying to Odin is bad.
dragonstalker said:
Using ES File explorer. Setup up your root explorer. and change permissions by using tools to System R/W.
Use ES File explorer to open the stock download and navigate to system/build.prop Copy it. Go back to your system and Rename the one there to build.bak. Then paste the new one there. This way you have the original saved if it turns out not to be the build.prop. My guess is. If you are on a rooted, stock rom like you said. The build.prop's are going to be identical. Thinking the culprit might be whatever you are trying to Odin is bad.
Click to expand...
Click to collapse
I didn't know you could explore .img files with a root explorer, of course I have never tried either.
Sent from my SCH-I605 using XDA Premium HD app
So I pulled the build.prop from a stock image, but it turned out it perfectly matched one of my backups. (I had three backups, factory, factory that I played with, and OTA Stock). So in the end that didn't solve my core issue. At this point should I make a new thread with a more appropriate title or just continue this one?
shangrila500 said:
I didn't know you could explore .img files with a root explorer, of course I have never tried either.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Actually you can't... I ended up using "Android ICS JB EXT4 imagefile unpacker" for windows, which worked nicely.
Trevski13 said:
The Failing update is update_SCH-I605_LL4_to_MC3 which fails with code 402
Click to expand...
Click to collapse
I would say just continue this thread.
I just re-read your original post. Are you trying to update from 4.1.1 to 4.1.2 via the OTA? If so, build.prop isn't your issue.
jcollier said:
I would say just continue this thread.
I just re-read your original post. Are you trying to update from 4.1.1 to 4.1.2 via the OTA? If so, build.prop isn't your issue.
Click to expand...
Click to collapse
alright, detail time!
I'm currently on 4.1.1 (I've applied one update after I bought it on release day)
I have an ota update (to what I assume is 4.1.2)
stock everything, locked boot-loader, but rooted (used Exynos Abuse)
using SuperSU
my phone lists update_SCH-I605_LL4_to_MC3 which fails to install with error code 402
my device status IS "modified" but it appears to be related to the SD card as it is "normal" when I remove it (apparently a known issue)
normally when I get an update I do the following:
1. restore build.prop
2. remove busybox
3. remove/disable any other apps that may have played with files that I think could cause issues
4. double check my root backup (Voodoo)
5. temp unroot
6. update
7. restore root
8. enjoy
this method usually works without issues :/
and the reason I suspected build.prop in the first place is that restoring it allowed me to update on another device.
I'd really rather not have to flash it back to stock, but if it's my only option, I will. So any ideas that don't involve wiping everything would be wonderful!
Trevski13 said:
alright, detail time!
I'm currently on 4.1.1 (I've applied one update after I bought it on release day)
I have an ota update (to what I assume is 4.1.2)
stock everything, locked boot-loader, but rooted (used Exynos Abuse)
using SuperSU
my phone lists update_SCH-I605_LL4_to_MC3 which fails to install with error code 402
my device status IS "modified" but it appears to be related to the SD card as it is "normal" when I remove it (apparently a known issue)
normally when I get an update I do the following:
1. restore build.prop
2. remove busybox
3. remove/disable any other apps that may have played with files that I think could cause issues
4. double check my root backup (Voodoo)
5. temp unroot
6. update
7. restore root
8. enjoy
this method usually works without issues :/
and the reason I suspected build.prop in the first place is that restoring it allowed me to update on another device.
I'd really rather not have to flash it back to stock, but if it's my only option, I will. So any ideas that don't involve wiping everything would be wonderful!
Click to expand...
Click to collapse
Really the only thing I have seen to update is to go completely back to stock.
But why do you want to do this so badly? Why not just unlock and flash the new update rom Beans provided? Thats certainly the easiest way to do it in my opinion, since you're having all these issues, and it leaves you unlocked in case you don't like one of the future updates or if you want to test out AOSP.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Really the only thing I have seen to update is to go completely back to stock.
But why do you want to do this so badly? Why not just unlock and flash the new update rom Beans provided? Thats certainly the easiest way to do it in my opinion, since you're having all these issues, and it leaves you unlocked in case you don't like one of the future updates or if you want to test out AOSP.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I rely on my phone a lot and so even the short amount of time it would take me to fix a soft brick, or reconfigure a wiped device would be a problem. I'm not worried about bricking it, I'm worried about the time it takes to fix it. I soft bricked my old X2, and it was a real inconvenience (granted that was the first time I'd ever had to fix something like that) and I had to restore my Transformer Infinity back to stock to fix lag and glitching issues. (which lead to a whole partial root fiasco). So It's not that I can't fix the problems, it's that it takes time I don't have, and disrupts my life. If I had another 4g phone (because switching between 3g and 4g is a pain on Verizon) that I could switch to if I messed up and didn't have time to fix it, I'd totally start messing with custom roms, unlocking, and all that fun stuff, but I don't
Trevski13 said:
I rely on my phone a lot and so even the short amount of time it would take me to fix a soft brick, or reconfigure a wiped device would be a problem. I'm not worried about bricking it, I'm worried about the time it takes to fix it. I soft bricked my old X2, and it was a real inconvenience (granted that was the first time I'd ever had to fix something like that) and I had to restore my Transformer Infinity back to stock to fix lag and glitching issues. (which lead to a whole partial root fiasco). So It's not that I can't fix the problems, it's that it takes time I don't have, and disrupts my life. If I had another 4g phone (because switching between 3g and 4g is a pain on Verizon) that I could switch to if I messed up and didn't have time to fix it, I'd totally start messing with custom roms, unlocking, and all that fun stuff, but I don't
Click to expand...
Click to collapse
Well unlocking would let you go ahead and update and until you wanted to flash roms you wouldnt have to except for that first flash of the new update, which is what a stock update does.
The reason I say this is some people have had this problem and when they finally do get the update to work it soft bricks them. This is rare but it has happened. In the end for me it is just easier to unlock so I can play around when I want to and when I dont I can stay on stock.
Sent from my SCH-I605 using XDA Premium HD app
Related
OK, I'm a noob and made the noob mistake of deleting (rather than freezing) some system apps after rooting. Won't make that mistake again.
I do not have backups nor am I completely sure which apps are missing. As a result of these missing apps I cannot complete the latest OTA update.
I downloaded a system dump and noted a few apk files in it that were not on my system though I believe that there are other apk files missing which are not in the system dump (MyLibrary, WebStorage etc) so I am not sure the particular system dump I got is up to date.
Copying the apk files to my system\app folder did not help, the update still fails.
I seem to recall seeing instructions somewhere for manual installation via power/down volume which would allow you to see a text dump of the update with reports of missing files or mismatched CRC's. I cannot find this again but such a thing would help me determine what is missing so that I can then attempt to find replacement apk files.
Sorry for being such a noob. Can anyone help?
Thanks
Made the same mistake when upgrading to ICS from Honeycomb...
If you get the previous update (the one your running now) from the Asus website, extract the update file and place it in one of the folders on the tablet, (I forgot which folder, sorry...) reboot and the tab will recognize it and prompt you to update. Once that update is finished installing, you should have all your bloat back. Delete the update file from the tab since you don't need it anymore, and then try to update to the most recent OTA Update.
Just do a search in the TFP forums and you should find complete instructions on how to do this.
I'm just assuming this will work for ICS to ICS... because it worked for me when I updated to ICS to Honeycomb...
Hope this method works for you.
I had the same issue.
Download:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/US_epaduser9_4_2_11UpdateLauncher.zip
Once downloaded, extract the contents of the zip file (yes, its another zip file of the same name inside) to your MICRO SD. put your micro SD in your TF201 (or eject and re-insert if you copied via cable)
Once the card is mounted you will see a triangle with an "!" in the notification area. Touch the notification and it will open a dialogue to install the manual update.
You will lose root, even with OTA Rootkeeper.
Re-root your device. Install OTA Rootkeeper if you have not already. Run Voodoo OTA Rootkeeper. Protect your su.
Check for updates. Install .13 OTA.
$$$
Should be a lesson learned. Stop messing with system apps. Always causes problems one way or another. The apps included are nothing to even be considered bloat. I still have everything installed n prime super fast. If anything just freeze the apps, never delete them unless u always want to have failed OTA.
demandarin said:
Should be a lesson learned. Stop messing with system apps. Always causes problems one way or another. The apps included are nothing to even be considered bloat. I still have everything installed n prime super fast. If anything just freeze the apps, never delete them unless u always want to have failed OTA.
Click to expand...
Click to collapse
I agree completely, and my lesson is learned. But why on earth would a freaking E-reader app be a system app?
That was my hangup. AsusReader a/k/a the My Library app.
And mine was backed up with Titanium, which obviously bungled it since it would not restore.
phree1 said:
I agree completely, and my lesson is learned. But why on earth would a freaking E-reader app be a system app?
That was my hangup. AsusReader a/k/a the My Library app.
And mine was backed up with Titanium, which obviously bungled it since it would not restore.
Click to expand...
Click to collapse
I went through the same thing on my Atrix phone. Rooted n went messing around deleting at&t bloatware. It killed my OTA updating. That's why now I'm still on froyo on it. Never bothered to manually update it. Still works great on froyo though. But I learned my lesson from that.
demandarin said:
I went through the same thing on my Atrix phone. Rooted n went messing around deleting at&t bloatware. It killed my OTA updating. That's why now I'm still on froyo on it. Never bothered to manually update it. Still works great on froyo though. But I learned my lesson from that.
Click to expand...
Click to collapse
Your still on froyo... why not just flash a sbf file to return to stock? Or better yet, unlock the boot loader and get yourself CM7 already.
Messing with system files isn't a big deal, as long as you have a backup.
Sent from my Transformer Prime TF201 using xda premium
Yep, this did the trick. Thanks very much.
Lesson learned, don't mess with the system apps.
Is it possible to root the Fascinate without deleting data, or at least a temporary root?
Chase716 said:
Is it possible to root the Fascinate without deleting data, or at least a temporary root?
Click to expand...
Click to collapse
Absolutely. You'd have to search/dig through older posts, but the general idea is this:
> Get a recovery .zip file that will install Superuser and put it onto the SDCARD
> Flash a custom recovery (typically ClockworkMod) using ODIN
> Reboot into recovery and install the .zip file
Basically for the Fascinate, all you really need to do is get the proper version of the Superuser application and it's corresponding su binary installed. The Samsung ODIN tool allows you to replace the stock recovery with a custom one, and that custom recovery will allow you to install Superuser/root the device. This only modifies the SYSTEM volume and does not affect any of your data at all. It's obviously more complicated, but essentially behaves as if you could just root by installing something from the Google Play Store.
There should be a TON of resources/threads out here and on other sites with how to actually accomplish this and provide the necessary files for the Fascinate, but as long as you pick a process that generally has the steps listed above, your data *should* be 100% safe.
... so get Googling and root that thing! lol :victory:
djp952 said:
Absolutely. You'd have to search/dig through older posts, but the general idea is this:
> Get a recovery .zip file that will install Superuser and put it onto the SDCARD
> Flash a custom recovery (typically ClockworkMod) using ODIN
> Reboot into recovery and install the .zip file
Basically for the Fascinate, all you really need to do is get the proper version of the Superuser application and it's corresponding su binary installed. The Samsung ODIN tool allows you to replace the stock recovery with a custom one, and that custom recovery will allow you to install Superuser/root the device. This only modifies the SYSTEM volume and does not affect any of your data at all. It's obviously more complicated, but essentially behaves as if you could just root by installing something from the Google Play Store.
There should be a TON of resources/threads out here and on other sites with how to actually accomplish this and provide the necessary files for the Fascinate, but as long as you pick a process that generally has the steps listed above, your data *should* be 100% safe.
... so get Googling and root that thing! lol :victory:
Click to expand...
Click to collapse
Well the only thing is, that I'm not supposed to root it, and I only want a temporary root to remove bloatware. Superoneclick's shell root didn't work, and neither did z4root.
Chase716 said:
Well the only thing is, that I'm not supposed to root it, and I only want a temporary root to remove bloatware. Superoneclick's shell root didn't work, and neither did z4root.
Click to expand...
Click to collapse
Well if you get more interested I suggest you try a 4.2.2 ROM you won't be disappointed
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Well if you get more interested I suggest you try a 4.2.2 ROM you won't be disappointed
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Well that does sound really nice, especially since i enjoyed CyanogenMod on my Incredible 2, but I can not flash any ROMs, I cannot completely root, and I cannot even flash a new recovery. And if I did flash a ROM, I think it would have to be manually activated since it does not have a SIM Card, leading him to find out I rooted. I just want a temp root to remove the bloatware I do not use.
Chase716 said:
Well that does sound really nice, especially since i enjoyed CyanogenMod on my Incredible 2, but I can not flash any ROMs, I cannot completely root, and I cannot even flash a new recovery. And if I did flash a ROM, I think it would have to be manually activated since it does not have a SIM Card, leading him to find out I rooted. I just want a temp root to remove the bloatware I do not use.
Click to expand...
Click to collapse
I don't think there are any temp-root solutions out there for the Gingerbread Fascinate, as the community was well beyond using exploits by that time Could be wrong, but I looked around and didn't really find anything. It might be worth looking around for a generic Linux 2.6.35-based exploit that somebody has compiled for the ARM processor.
Question ... what would prevent you from temporarily flashing a custom recovery to make the edits you want? If you don't change anything else, it would be overwritten with the stock recovery on the next boot, thus covering your tracks (and we can get the stock recovery back on there for ya if for some reason it doesn't). Many (most?) recoveries will allow ADB access when active, so you can mount system and do what you need to do without actually rooting the stock ROM.
Also, don't worry too much about the CDMA activation status, unless you check a certain box in the Samsung ODIN tool there is almost no way to screw that information up doing what you're looking to do. The CDMA keys are stored in a super double secret location that you ordinarily can't get to. The option is called "EFS Clear", don't go anywhere near it.
If you do find a solution that fits your needs, I also recommend you have a plan to restore the SYSTEM volume back to stock in case you make a mistake, like deleting a critical file. We can help with that as well if you are ultimately willing to use the ODIN tool. I just want to make sure you're prepared for that possibility as it sounds like if you temporarily break this device you'll be in big trouble
djp952 said:
If you do find a solution that fits your needs, I also recommend you have a plan to restore the SYSTEM volume back to stock in case you make a mistake, like deleting a critical file. We can help with that as well if you are ultimately willing to use the ODIN tool. I just want to make sure you're prepared for that possibility as it sounds like if you temporarily break this device you'll be in big trouble
Click to expand...
Click to collapse
Yeah, but two more things: first, can someone give me a very detailed tutorial on ODIN for my device, and could someone also give me the files i may need in order to delete the bloatware, no flashing, no data wipes or anything like that? Because the bloatware is what I think slows my phone down. And what if something does not go right?
Sent from my Galaxy S Fascinate SCH-I500
You should be able to unroot via SuperOneClick after you've fully rooted and debloated the thing. Whoever's keeping an eye on that Fassy hopefully won't notice!
Chase716 said:
Yeah, but two more things: first, can someone give me a very detailed tutorial on ODIN for my device, and could someone also give me the files i may need in order to delete the bloatware, no flashing, no data wipes or anything like that? Because the bloatware is what I think slows my phone down. And what if something does not go right?
Sent from my Galaxy S Fascinate SCH-I500
Click to expand...
Click to collapse
Does the person you're hiding this from even know the difference between what GB and JB looks like? What's to say if you have an AOSP or CM-based JB rom that they'd even know it's not stock?
Anyway, if you buy Nova Launcher prime I know you can hide apps from your drawer, so if you wanted to say hide TiBu or Superuser you could do that and throw someone off if they're just taking a quick look at your app drawer. Nova doesn't work on GB though I think, so you might have to look for a different launcher to do that if you want to stay on stock.
For a detailed guide on pretty much anything related to rooting/flashing just check droidstyle's guide here: http://forum.xda-developers.com/showthread.php?t=1238070
For freezing or removing bloat I highly recommend buying Titanium Backup, but there are some free apps that will do that sorta stuff. Titanium will give you way more options down the road though...
Crawshayi said:
Anyway, if you buy Nova Launcher prime I know you can hide apps from your drawer, so if you wanted to say hide TiBu or Superuser you could do that and throw someone off if they're just taking a quick look at your app drawer. Nova doesn't work on GB though I think, so you might have to look for a different launcher to do that if you want to stay on stock.
Click to expand...
Click to collapse
I believe he does, since when I rooted my Incredible 2 he noticed it was completely different and not HTC Sense skinned, and I'd explained to him the Android operating system. And I use ADW EX as my default launcher, only because I can't use the TwLauncher due to lag issues. So I've hidden my bloat apps, but things still stay open in the background.
This might be a long shot, but have you ever tried to explain to him that rooting is actually more secure than having an unrooted phone? Try to get him to understand that with a rooted device you can actually make FULL backups of your device in case anything goes wrong, unlike the half-assed backups that non-rooted devices have to use. Also, rooted devices allow you to install the latest (secure) versions of android unlike non-rooted which force you to wait for updates that may never come.
Anyway, if that fails, I would recommend to root and freeze/remove with Titanium
Crawshayi said:
This might be a long shot, but have you ever tried to explain to him that rooting is actually more secure than having an unrooted phone? Try to get him to understand that with a rooted device you can actually make FULL backups of your device in case anything goes wrong, unlike the half-assed backups that non-rooted devices have to use. Also, rooted devices allow you to install the latest (secure) versions of android unlike non-rooted which force you to wait for updates that may never come.
Anyway, if that fails, I would recommend to root and freeze/remove with Titanium
Click to expand...
Click to collapse
I wish. He won't listen, and he'll just say that it's bad, I don't need to root my phone,and that I'll break it, like my old one ( NOT MY FAULT!). That is why I wanted to do it secretly, temporarily, or something like that. I know it's good, and that there are risks. So is there any way I can root (no flashing) and keep it hidden? Also, I went into the bootloader, and saw an option that said update.zip. Would that be useful, to maybe flash the EH09 Fascinate rom?
UPDATE: Thanks for the help everyone, but I'm most likely going to ditch the Fascinate for a Galaxy SIII. So maybe sometime I'll find the time to experiment with ROMS on my Fascinate sometime.
Hi All -
Flashed LSS (NEE) firmware yesterday on my S2, after this my WIFI is dead.:crying:
Tried with previous (LSN) and also re-flashed LSS but nothings working. Is this any hardware issue
Any solution for this, after selecting wifi the switch goes back to off position in seconds.
Was it working on ICS?
If yes, it's not hardware.
If no, flash jb leak.
Sent from the little guy
gastonw said:
Was it working on ICS?
If yes, it's not hardware.
If no, flash jb leak.
Sent from the little guy
Click to expand...
Click to collapse
Yes, it was working on ICS as well in previous jb LSN.
Another issue i forgot to update. From past few days vibrator is not working properly, have order online & awaiting delivery. Is this vibrator issue is anything related to Wifi?
Make a full wipe?
mar10o said:
Make a full wipe?
Click to expand...
Click to collapse
Already did twice...no use
sunnyhot said:
Already did twice...no use
Click to expand...
Click to collapse
Try to run ROM nuke script,then flash again the LSN(or ICS,or whatever ROM where it was working.)Let me know that this helped you or not.
GamingDj said:
Try to run ROM nuke script,then flash again the LSN(or ICS,or whatever ROM where it was working.)Let me know that this helped you or not.
Click to expand...
Click to collapse
Sorry for nobe question.
Does ROM nuke script wipes all the data on internal SD card? just like formatting from storage option?
Don't nuke it, re-flash and factory reset.
If you're rooted flash via mobile odin.
Sent from the little guy
gastonw said:
Don't nuke it, re-flash and factory reset.
If you're rooted flash via mobile odin.
Sent from the little guy
Click to expand...
Click to collapse
^^nothings working.
Just few minutes back re-flashed the firmware through mobile odin and had selected wipe data & cache/Dalvik cache.
I think now the only option is to clear everything?
what you mean "nothing's working"?
Sent from the little guy
gastonw said:
what you mean "nothing's working"?
Sent from the little guy
Click to expand...
Click to collapse
Wifi option still not working even after re-flash
Hum....use M.O to flash JB leak.
Everything works on JB leak.
Sent from the little guy
Ok let me try this final option. Have to search my system for leaked firmware if not need to download again.
I will get back with the updated details once this is done.
Thanks.
You can also flash....what was it...LSN? The jb ROM where wifi actually worked.
Sent from the little guy
I had same wifi issue after upgrade from official stock ICS to official stock JB. Home wifi was dead after upgrade. On ICS wifi worked. So I read tens of similar issue threads, not only i9100 related. I tried to change every simple option on my router, reboots, wipes .... And finaly someone (HTC owner I guess) mention that replace binary files in /system/etc/wifi/*.bin from older 4.1.1 helped him.
Before upgrade, I had Supernexus ROM as secondary, and there were no wifi issue.
So solution which helped me is simple extract /system/etc/wifi/*.bin binaries from my previous supernexus nandroid backup and replace related files on updated stock JB. It was also necessary to rename them ie bcm_mfg.bin(supernexus) to bcmdhd_mfg.bin(stock) and so on. And everything works now!
Not simple, bit dangerous but helped me.
PS: don't forget backup!
russline said:
I had same wifi issue after upgrade from official stock ICS to official stock JB. Home wifi was dead after upgrade. On ICS wifi worked. So I read tens of similar issue threads, not only i9100 related. I tried to change every simple option on my router, reboots, wipes .... And finaly someone (HTC owner I guess) mention that replace binary files in /system/etc/wifi/*.bin from older 4.1.1 helped him.
Before upgrade, I had Supernexus ROM as secondary, and there were no wifi issue.
So solution which helped me is simple extract /system/etc/wifi/*.bin binaries from my previous supernexus nandroid backup and replace related files on updated stock JB. It was also necessary to rename them ie bcm_mfg.bin(supernexus) to bcmdhd_mfg.bin(stock) and so on. And everything works now!
Not simple, bit dangerous but helped me.
PS: don't forget backup!
Click to expand...
Click to collapse
Hi -
I see 4 bin files in path. Do i need to replace only 'mfg.bin' file?
I replaced all of them. 4
Sent from my GT-I9100 using xda app-developers app
russline said:
I replaced all of them. 4
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
My friend S2 running on CM 10.1. If i copy and replace bin files from his mobile will thats gonna work?since i do not have any backup from old firmware
And also do i need to delete old files and then paste or override the old files? sorry for too many questions.
keep gsterac
CM10.1 is JB4.1 AOSP based ROM similar as supernexus, perhaps it should work. BTW yours friend phone can connect to your wifi? If not, its useless.
I have no idea about your linux/android experience. Most of work I made through adb shell. If you are familiar with it you probably known what to do. If not, I recommend to read some threads about android filesystem, file permissions, adb... If you are courageous you can technically to use for example ES File explorer for all changes.
But again IF YOU DON'T UNDERSTAND WHAT YOU ARE DOING IT IS HIGH POSSIBILITY OF SERIOUS DAMAGE OF YOUR PHONE!!
I thing following steps should work fully from GUI. But I didn't tried it this way.
- !!!1st make backup of original files!!!! In ES File Explorer copy original files somewhere at least to sdcard(external one better).
Also please note original files owner, group and file permissions:
-rw-r--r-- 1 root root 183072 May 29 21:46 bcmdhd_apsta.bin
-rw-r--r-- 1 root root 202480 May 29 21:46 bcmdhd_mfg.bin
-rw-r--r-- 1 root root 204186 May 29 21:46 bcmdhd_p2p.bin
-rw-r--r-- 1 root root 196765 May 29 21:46 bcmdhd_sta.bin
It is very important to preserve this attributes. For example if you are going to copy files to your phone through sdcard, the permissions will be changed. It is necessary to change them back as above.
- turn off wifi. I also used airplane mode just in case...
- in ES File Explorer push Menu->Tools->Root Explorer->Mount R/W-> /system select RW
- delete old binary files.
- copy the new ones and rename them if necessary
- set file permissions through ES FIle Explorer - long press the file->(more)Properties->Change -> Make sure only all read checkboxess are selected and only the first one(User) Write permissions is selected. Repeat it for all 4 changed files.
- - in ES File Explorer push Menu->Tools->Root Explorer->Mount R/W-> /system select RO
-check the wifi, if it works reboot just in case. If not......I have no idea.
And also it has one impact I noticed. OTA updates doesn't work anymore.
russline said:
CM10.1 is JB4.1 AOSP based ROM similar as supernexus, perhaps it should work. BTW yours friend phone can connect to your wifi?
- in ES File Explorer push Menu->Tools->Root Explorer->Mount R/W-> /system select RW
- delete old binary files.
- copy the new ones and rename them if necessary
- set file permissions through ES FIle Explorer - long press the file->(more)Properties->Change -> Make sure only all read checkboxess are selected and only the first one(User) Write permissions is selected. Repeat it for all 4 changed files.
- - in ES File Explorer push Menu->Tools->Root Explorer->Mount R/W-> /system select RO
-check the wifi, if it works reboot just in case. If not......I have no idea.
And also it has one impact I noticed. OTA updates doesn't work anymore.
Click to expand...
Click to collapse
Now I think u might be confused about the issue. Im not facing wifi connectivity issue. Wifi option in my mobile is not at all switching on.
I have attached the screenshot for reference.
The switch comes back to 'O' position in seconds but message shows wifi turning on.
Portable wifi hotspot show error message.
Think aft seeing screen u got my problem.
Sent from my GT-I9100 using Tapatalk 2
So, I've had quite a long night trying to accomplish what seems to be such an easy task for every one else. My main goal for tonight was to root my HTC One and install a custom ROM, preferably ARHD 4.3. This was unfortunately not the case. This is my first time handling anything along the lines of rooting a phone or doing anything like that.
I started off by unlocking the bootloader and then moving on to install TRWP as my custom recovery image. Once I rooted my device after that, I started looking up custom ROM's only to find out that I would need to install firmwares before I installed the ROM's, which required me to pretty much re-do every thing above.
Here's where the problems began to happen. I had to try and get my S-On to go to S-Off and I got errors everywhere. Either I got an error trying to do one guide via terminal command inside of an app on the device, or my model number didn't show up on available methods. I don't even know, all I know is I never got to actually succeed with getting my thing to S-Off, therefore I never could do any firmware installs.
I then read that the Google Edition 4.3 only needed the radio to be installed via firmware so I thought hey, I bet this ROM is perfect for me. But, then I read that you still need the firmware upgrade to be stable.
My actual question because I'm just overall sick of this and it's beginning to scare me that I've ruined my phone and I'll never get it to how it used to be;
I just want to go back to how my phone was. Factory settings across the board. However, I have no idea how to do this and the 2 backups I had in TRWP aren't showing in the recovery, however they are showing in the ES file manager within the Google Edition 4.3 ROM.
Please help, this is starting to freak me out. I had to pay $600 for this phone off contract and I made a dumb ass decision tonight.:crying:
You don't have to install firmware for any custom rom and you may never have to.
Sent from my HTC One using Tapatalk 4
Nick281051 said:
You don't have to install firmware for any custom rom and you may never have to.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Really? What exactly is firmware and why is it not needed? On the ARHD custom ROM threads, it says at the bottom that it is not needed, but recommended. I also read people's comments saying if the firmwares aren't installed, then you lose stability for your custom ROM's. Is that true and if so how?
I currently have the Google Edition 4.3 ROM and it seems to be workng fine without the Radio firmware. I just don't know what is needed and what isn't. But, my device has the bootloader unlocked, TRWP installed, fully rooted and Google Edition ROM 4.3 installed.
Am I okay?
Leather Sock said:
Really? What exactly is firmware and why is it not needed? On the ARHD custom ROM threads, it says at the bottom that it is not needed, but recommended. I also read people's comments saying if the firmwares aren't installed, then you lose stability for your custom ROM's. Is that true and if so how?
I currently have the Google Edition 4.3 ROM and it seems to be workng fine without the Radio firmware. I just don't know what is needed and what isn't. But, my device has the bootloader unlocked, TRWP installed, fully rooted and Google Edition ROM 4.3 installed.
Am I okay?
Click to expand...
Click to collapse
You are FINE, that's the same set up I have basically. Unlocked BL, Root, TWRP and sinless GE rom from the International forums. I have never touched s-off or any firmwares/radios.
I've run nearly every sense and GE rom in the One forum and never had an issue.
In theory I suppose the upgraded firmware could be better but I haven't heard of any real benefits of doing it. And have had no issues without it so it seems kinda pointless.
Sent from my HTC One using xda app-developers app
FanDroid09 said:
You are FINE, that's the same set up I have basically. Unlocked BL, Root, TWRP and sinless GE rom from the International forums. I have never touched s-off or any firmwares/radios.
I've run nearly every sense and GE rom in the One forum and never had an issue.
In theory I suppose the upgraded firmware could be better but I haven't heard of any real benefits of doing it. And have had no issues without it so it seems kinda pointless.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh wow, thanks a ton for the reply. That made me feel a ton better. I've been panicking about this.
Leather Sock said:
Oh wow, thanks a ton for the reply. That made me feel a ton better. I've been panicking about this.
Click to expand...
Click to collapse
No problem... I was worried to when the firmware update came out and devs started putting little disclaimers in their posts about recommending it. I'd be willing to bet that there are more people in these forums with s-on and stock firmware flashing away without issues.
Sent from my HTC One using xda app-developers app
FanDroid09 said:
No problem... I was worried to when the firmware update came out and devs started putting little disclaimers in their posts about recommending it. I'd be willing to bet that there are more people in these forums with s-on and stock firmware flashing away without issues.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
My only concern right now is that I have a tad bit lower free space now that I've made backups and flashed my ROM and such. The stock HTC One comes with 32GB but you get about 27GB~ to use. Before I did anything I'm fairly certain I had roughly 25-26GB of free space. Now I have 20GB. Could this be from the backups taking up a lot of space? I have 3.
Leather Sock said:
My only concern right now is that I have a tad bit lower free space now that I've made backups and flashed my ROM and such. The stock HTC One comes with 32GB but you get about 27GB~ to use. Before I did anything I'm fairly certain I had roughly 25-26GB of free space. Now I have 20GB. Could this be from the backups taking up a lot of space? I have 3.
Click to expand...
Click to collapse
ummmm... yes if the backups are stored on phone
backups backup everything on the phone... so you saved 5gb in copies 3 times...you're lucky they are compressed
You should really have just one copy saved on a safe pc or flash drive
ghostlogic said:
ummmm... yes if the backups are stored on phone
backups backup everything on the phone... so you saved 5gb in copies 3 times...you're lucky they are compressed
You should really have just one copy saved on a safe pc or flash drive
Click to expand...
Click to collapse
Well, when I tried to put the backups on my phone by copying and pasting them, it only pasted some of the stuff inside of it and not all of it. It was weird but it didn't let me paste all of the inside contents onto my computer.
Leather Sock said:
Well, when I tried to put the backups on my phone by copying and pasting them, it only pasted some of the stuff inside of it and not all of it. It was weird but it didn't let me paste all of the inside contents onto my computer.
Click to expand...
Click to collapse
That's strange I've transfered backups before without issue. I would try again, it may have just been an anomaly.
I would recommend keeping at least a stock as possible backup on your phone to be safe.
Personally I keep 3 backups: a stock AT&T one, an InsertCoin Sense edition, and a SinlessROM Google edition.
The resulting space is enough for me, if your worried about space your only option is to keep the other two on your PC, not really a way around it.
Sent from my HTC One using xda app-developers app
FanDroid09 said:
That's strange I've transfered backups before without issue. I would try again, it may have just been an anomaly.
I would recommend keeping at least a stock as possible backup on your phone to be safe.
Personally I keep 3 backups: a stock AT&T one, an InsertCoin Sense edition, and a SinlessROM Google edition.
The resulting space is enough for me, if your worried about space your only option is to keep the other two on your PC, not really a way around it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Well, I have a backup that is only an unlocked bootloader + root with the stock AT&T ROM, however I don't see any possible way of putting it onto my computer since I can't access the file from my computer. Originally the backups were in the TRWM folder in the internal storage on my computer, but then they stopped showing up in the backups through TRWP so I had to move them to /data/media/TRWP instead of 0/data/media/TRWP or whatever.
I'm not sure if that makes sense because it barely does to me either.
Leather Sock said:
Well, I have a backup that is only an unlocked bootloader + root with the stock AT&T ROM, however I don't see any possible way of putting it onto my computer since I can't access the file from my computer. Originally the backups were in the TRWM folder in the internal storage on my computer, but then they stopped showing up in the backups through TRWP so I had to move them to /data/media/TRWP instead of 0/data/media/TRWP or whatever.
I'm not sure if that makes sense because it barely does to me either.
Click to expand...
Click to collapse
Ya I know there are issues with storage going from 4.1 to 4.2. I'd recommend getting a good file explorer from the play store (I recommend es file explorer) use that to find your backups... Just search "backup" using the search function if you need to. Then copy the backups somewhere you can see them with your computer like to the root of your storage. From there copy to your computer.
Sent from my HTC One using xda app-developers app
Just like fandroid I have a copy of a Stock GPe 4.3 and an Stock AT&T version backup on a usb drive that i keep safe and as for the firmware and s-off/s-on at first i had a little trouble with getting s-off but i tried it 3 or so more times then on the the 2nd or 3rd time (I can't remember) it worked and i got the new firmware and it has been all good for me.
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