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
Related
For reasons I won't go into (mainly because they're boring) I deleted Google talk.apk from Root Explorer (I was following instructions to update the app but those didn't work) and now I can't get it back. I've factory reset the phone to no avail. I have Google Voice installed, but can't seem to get talk back. If anyone could help, it would be greatly, greatly appreciated. Thanks!
BTW, I did a search before posing the ?, but the only solution I found was for a different phone, and when I ran those steps, when I tried to open Talk, it would just FC.
libracolo said:
For reasons I won't go into (mainly because they're boring) I deleted Google talk.apk from Root Explorer (I was following instructions to update the app but those didn't work) and now I can't get it back. I've factory reset the phone to no avail. I have Google Voice installed, but can't seem to get talk back. If anyone could help, it would be greatly, greatly appreciated. Thanks!
BTW, I did a search before posing the ?, but the only solution I found was for a different phone, and when I ran those steps, when I tried to open Talk, it would just FC.
Click to expand...
Click to collapse
Have you tried snagging the files from another Photon and installing? Can you post what steps you have already taken please?
Yes....factory reset won't restore system apps. You can flash Juggs update.zip and that will restore for you. Then would have to root again of course but is easy enough.
Just download a custom rom , unzip it and copy the required app to your device.
faria said:
Just download a custom rom , unzip it and copy the required app to your device.
Click to expand...
Click to collapse
+1
I should of said that instead of grabbing it from another phone. Thanks faria.
CCallahan said:
Have you tried snagging the files from another Photon and installing? Can you post what steps you have already taken please?
Yes....factory reset won't restore system apps. You can flash Juggs update.zip and that will restore for you. Then would have to root again of course but is easy enough.
Click to expand...
Click to collapse
Thanks for the info. If I flash Juggs update, will it hurt anything (since I already am on the latest OTA)?
faria said:
Just download a custom rom , unzip it and copy the required app to your device.
Click to expand...
Click to collapse
I will try that as well. When I did a search, I found where someone had posted the talk.apk.zip file which I copied to my sd card, unzipped and then copied to system/apps (through Root Explorer), but that is when I started getting FC's. I then installed it (from Root Explorer) even with the same result. It may be that it wasn't the right version maybe? So if I extract it from a Rom, do I just copy it to the System/Apps folder (using Root Explorer)? Sorry for the confusion, and thanks much for the help.
libracolo said:
I will try that as well. When I did a search, I found where someone had posted the talk.apk.zip file which I copied to my sd card, unzipped and then copied to system/apps (through Root Explorer), but that is when I started getting FC's. I then installed it (from Root Explorer) even with the same result. It may be that it wasn't the right version maybe? So if I extract it from a Rom, do I just copy it to the System/Apps folder (using Root Explorer)? Sorry for the confusion, and thanks much for the help.
Click to expand...
Click to collapse
you need to delete the talk.odex file from system apps othewize you get fcs.
faria said:
you need to delete the talk.odex file from system apps othewize you get fcs.
Click to expand...
Click to collapse
I don't (and didn't) have that file, only talk.apk (which of course was deleted). Isn't the odex like the cache? If so, would it have been removed when I ran App Cache Cleaner?
libracolo said:
I don't (and didn't) have that file, only talk.apk (which of course was deleted). Isn't the odex like the cache? If so, would it have been removed when I ran App Cache Cleaner?
Click to expand...
Click to collapse
Correct.
Well short of getting the apk from the very same rom version ,you will have to reflash he rom.
ps.
there the new google talk with video here in the forum, that probably would fix your problem.
Here
http://forum.xda-developers.com/showthread.php?t=773272
http://forum.xda-developers.com/showthread.php?t=716888
faria said:
Here
http://forum.xda-developers.com/showthread.php?t=773272
http://forum.xda-developers.com/showthread.php?t=716888
Click to expand...
Click to collapse
Hey faria, thanks! I did the top link last night (that was the one that I copied the talk.apk.zip (2.2) over to my SD card, extracted, and then copied to /system/apps/. I installed from there (btw, I did change to R/W first), but all I got was FC's on talk. I'm thinking I needed to reboot after installing, maybe? I'm not really sure why I would need to reboot though, but if that is all it takes, I'm happy. I will try that when I get home tonight (don't have a spare cable with me right now). Thank you sooo much for your help.
libracolo said:
Thanks for the info. If I flash Juggs update, will it hurt anything (since I already am on the latest OTA)?
Click to expand...
Click to collapse
If you still end up having problems.....
Juggs update.zip is just the latest OTA with a few minor modifications. So basically it will restore all to pretty close out of the box and restore any system apps.
However, you can also flash the sbf which is the actual newest OTA exactly like the one pushed from Motorola/Sprint. This requires using rsd and isn't quite as easy as the update.zip which can just be flashed via bootstrap recovery.
Any one of these methods will require you to root the phone again.
CCallahan said:
If you still end up having problems.....
Juggs update.zip is just the latest OTA with a few minor modifications. So basically it will restore all to pretty close out of the box and restore any system apps.
However, you can also flash the sbf which is the actual newest OTA exactly like the one pushed from Motorola/Sprint. This requires using rsd and isn't quite as easy as the update.zip which can just be flashed via bootstrap recovery.
Any one of these methods will require you to root the phone again.
Click to expand...
Click to collapse
Yeah, I'm gonna flash the sbf, I just downloaded it and installed the drivers and stuff, but I think I'm gonna wait until tomorrow night (only because it's been a really long day, started at 4 am MST just ending), so I think my brain is fried. Thanks for all your help today, I'll let ya know tomorrow how it goes. What a freakin pain in the arse this talk.apk has become....haha
Update: I flashed the sbf, re-rooted, and everything is great now, have Talk back. Thanks for all the help!
So i've upgraded my SGS2(uk device) to the european ICS LPQ i think.
and ive notice that i'm now unable to install apk's manually on the device.
i can install via ADB so not all lost,
has anyone else come across this problem?
also should i flash the UK ICS when it is available
ZonyX said:
So i've upgraded my SGS2(uk device) to the european ICS LPQ i think.
and ive notice that i'm now unable to install apk's manually on the device.
i can install via ADB so not all lost,
has anyone else come across this problem?
also should i flash the UK ICS when it is available
Click to expand...
Click to collapse
Might be a silly thought, but have you enabled the unknown sources option...?
Lee
yep thats been done,
under Security > Unknown Sources is ticked
doesnt seem to be anyother settings that i could've missed either.
Hmm. Odd bug then. I can't help (or confirm) yet as I'm doing a system dump before flashing (LPH to LPQ, full wipe + internal sd format). Copying everything from my internal sd to the pc takes a little while, it was nearly full...
You've tried the nasty shotgun approach of clearing caches and fixing permissions...?
Lee
edit
wrong thread
Working fine here. I did a wipe before install as it wouldn't work the first time I flashed.
Working fine here. I didn't wipe.
The only thing I noticed is that some apps, previously installed, didn't work. I uninstalled them and reinstalled them from the internal SD Card.
Do you have Root? Depending on how you flashed your phone, you may have lost root access and thus some apps that require root may not install.
i agree it is an odd "bug" not sure why it would do this.
when the install application screen comes up, only the cancel button is responsive.
also i can confirm i have root - i flashed CF_root strait after.
flash the stock XXLPQ kernel, and you will be able to install
try said:
flash the stock XXLPQ kernel, and you will be able to install
Click to expand...
Click to collapse
wont i then lose root?
Have you tried unmounting SD card and then mounting it, I had a few issues like that and that fixed it for me.
Sent from my GT-I9100 using XDA
richfreestone said:
Have you tried unmounting SD card and then mounting it, I had a few issues like that and that fixed it for me.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
yes i have tried this, and also did the fix permissions thing in CWM
Not too sure if your issue is related, but you can try the following trick.
http://forum.xda-developers.com/showpost.php?p=23907529&postcount=259
Hope this help.
in case you loose root
ZonyX said:
wont i then lose root?
Click to expand...
Click to collapse
Flashing back the stock kernel will actually solve the problem. For the case of rooting your phone, you can use:
http://forum.xda-developers.com/showthread.php?t=1501719
Got stock kernel on, and rooted my phone using that method. Everything works fine.
Credit goes to Rachmat3 for the guide.
I deleted my the Phone.apk file on my rooted Galaxy Player 4.0 (YP-G1CWY/XAA) running the stock rom awhile back to save on battery life.
I have done the same thing on my Nook Color, and figured that it wouldn't cause any problems, as the Player isnt a phone.
Recently tried to record some video, and found I was unable to do so. After doing some research I found out that deleting phone.apk causes the stock camera app, but not 3rd party camera apps, to stop functioning.
While I was sure to backup the file when I originally deleted the file, the backup has been lost in the intervening months.
Do I just need to find a specific phone.apk file for my device and return it to the correct directory?
I assume a factory reset will solve the problem, but I would rather not try that unless I have to.
Thanks!
a factory reset will not solve the problem, since it was a system .apk it will reset everything except for that particular apk.
heet1 said:
a factory reset will not solve the problem, since it was a system .apk it will reset everything except for that particular apk.
Click to expand...
Click to collapse
In which case do I need to track down a copy of that specific apk or will I need to download odin and perform a full recovery?
put back the phone.apk file back on your device. Go to a ROM(best if its that ROM you are using) Find the phone.apk, and take it out. Then transfer it into your device, and use Root Explorer or something and put back phone.apk.
i dont think that will work because i uninstalled the screencapture.apk from my 5.0 and i backed it up so i tried to reinstal and it would not let me... but try aznflawless' way first if not you may want to flash a stock based rom...
heet1 said:
i dont think that will work because i uninstalled the screencapture.apk from my 5.0 and i backed it up so i tried to reinstal and it would not let me... but try aznflawless' way first if not you may want to flash a stock based rom...
Click to expand...
Click to collapse
I put screencapture.apk from stock rom 2 chip rom because it was missing and worked normaly..just copy it 2 root/system/app ..dont install it.
Sent from my GT-I9000 using XDA
aznflawless said:
put back the phone.apk file back on your device. Go to a ROM(best if its that ROM you are using) Find the phone.apk, and take it out. Then transfer it into your device, and use Root Explorer or something and put back phone.apk.
Click to expand...
Click to collapse
This seemed to work for me!
I tried looking in various roms before, but they were all formatted for flashing with odin.
I should have just went straight for the cwm package. *slaps forehead*
Thanks so much!
i shall try that sir thanks
As others said... find the phone.apk... preferably from the same rom you are using... use RootExplorer and copy the phone.apk to the system/apps folder. Change the permissions to match the other apps in that folder... reboot and you are good to go.
For your future reference, it is not a good idea to delete system apps without knowing what they actually do... I think you made a real good guess since phone.apk should not be on a device that is actually not a phone by function. For example, the Android Market app is actually called phonesky.apk or vendor.apk... nothing like what you would normally guess it to be, such as market.apk or something to that matter. So if I were you and I wanted to keep using my device and not brick it, I would becareful what I delete out of /system and it's sub folders...
Good luck...
Try to reinstall your custom rom!!
OrglCe said:
Try to reinstall your custom rom!!
Click to expand...
Click to collapse
this is a thread from august of 2012. please dont go digging through old threads and posting on them
Can one of the experienced devs please tell me how I can rename the internal SD card back to Phone when mounted in a windows machine?
Currently when I connect via MTP it shows as "/mnt/mmc/Downloaded Data" instead.
I have searched and this is happening on a couple of ROMs and not just my home build.
The other option, what am I removing that is causing this?
I've the same problem. I'm on JB dragon's rom .
Can someone with the problem try this fix and see if it works for them.
Please back-up first and post back if it works or not.
Thanks for trying
Not working
Still Thank you for your working
I have the same problem. Was fixed when i flashed unrooted stock rom using pc, but changed again after flashing custom XXDLIB
Sent from my GT-I9300 using xda premium
---------- Post added at 05:28 PM ---------- Previous post was at 05:26 PM ----------
ManojKBanga said:
Not working
Still Thank you for your working
I have the same problem. Was fixed when i flashed unrooted stock rom using pc, but changed again after flashing custom XXDLIB
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
My english
*stock firmware
*for your work
Sent from my GT-I9300 using xda premium
I often get that it is rom/kernel change related .
But i just ignore it .
jje
JJEgan said:
I often get that it is rom/kernel change related .
But i just ignore it .
jje
Click to expand...
Click to collapse
I do too but my wife doesn't like it so I need to find the fix. I thought I had it, it's working here but there must be more to it. Will keep looking!
this solution it's ok ! I tried this and it's work !
http://forum.xda-developers.com/showpost.php?p=32434515&postcount=2026
I have the same problem with my Galaxy Note, this is really gonna be a problem, as I can't view all my files in PC... The files shown in PC are not complete. So if this is not solved, the only choice will be permenantly switch to Mass Storage Mode.
I got this issue after updating my own Rom from XXEMA2 to XXEMR2, the internal memory now appears as "mnt/mmc/Downloaded Data" instead of "Phone", and I doubt the solution is the storage, because restoring the EMA2 backup (with twrp) I get back the Phone label in MTP.
no other solutions out there?
Update:
after few restarts, and cleaning the MediaStorage, now it is back OK
question
mcbyte_it said:
I got this issue after updating my own Rom from XXEMA2 to XXEMR2, the internal memory now appears as "mnt/mmc/Downloaded Data" instead of "Phone", and I doubt the solution is the storage, because restoring the EMA2 backup (with twrp) I get back the Phone label in MTP.
no other solutions out there?
Update:
after few restarts, and cleaning the MediaStorage, now it is back OK
Click to expand...
Click to collapse
What do you mean with cleaning the media storage?
Kangburra said:
Can one of the experienced devs please tell me how I can rename the internal SD card back to Phone when mounted in a windows machine?
Currently when I connect via MTP it shows as "/mnt/mmc/Downloaded Data" instead.
I have searched and this is happening on a couple of ROMs and not just my home build.
The other option, what am I removing that is causing this?
Click to expand...
Click to collapse
I faced the same problem installing Phoenix rom on Samsung Galaxy Note2 and corrected this way:
1. wipe data factory reset on CWM
2. Wipe cash partition
3.format system, data on mount and storage
4. install rom through aroma installer selecting full wipe.
Hello! Wipe didn't help me in this situation, but I found another way. You need to copy the folder "kies"(system/etc) from the official firmware.
Need Some Help
zVeRoBoY said:
Hello! Wipe didn't help me in this situation, but I found another way. You need to copy the folder "kies"(system/etc) from the official firmware.
Click to expand...
Click to collapse
I am new to Android and recently bought a Tab2 10.1 (SCH-I915). It is rooted and I deleted the system/etc/kies folder thinking it was remnants of the stand alone Kies program that I found out is not compatible with my device after having installed it . Now I have the same problem with internal memory showing up as /mnt/mmc/Downloaded Data. when connected to PC. Can someone send me a copy of the system/etc/kies folder so I can replace it?
I looked for a stock firmware for this tablet and can not find one to extract the folder from. I tried the firmware for a SCH-I925 but the folder contains different files and does not correct the problem.
I also did a factory reset but that did not replace/re-install the folder. It needs to be from a SCH-I915 model I suppose, Please help, If you have a SCH-I915 and could copy the entire folder and send it as an email attachment or .zip/.rar or if someone has found a place to download the SCH-I915 firmware I can extract it myself......
I know this thread is a bit older but hoping someone has a solution as this is the only place I found with any information about this.
Thanks for your time
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