I wanna know if you can get bricked by the update if you have installed apk files.
Sent from my SGH-T959 using XDA App
No you can't. Unless you have a non stock ROM, lag fix, Voodoo kernel, OC'ed kernel etc applied to your phone. (Unless the update just randomly messed up) which would be very unlikely and in that case the device would/ should be replaced by your cell provider.
Related
I was under the impression that the typical custom ROM disables the OTA update feature. Is it safe to accept the update with Bionix + JAC's kernel installed, or is bricking a possibilty here? Can I flash it back to stock without "losing" the OTA update?
I'm very curious as to what it might be, because Fusion is based on JI6, which would imply that this update is newer than JI6...
I wouldnt recommend doing the upate, if stock gives you problems imagine a custom rom
Sent from my SGH-T959 using Tapatalk
I just received the same update also while running Fusion. I unrooted, deleted the update.zip then accepted it. It rebooted back into Fusion and didn't change anything. Apparently it's a Media Hub update.
Well i hear a lot of people say that they turned off there lag fix y if isn't it suppose to help them so y would they turn it off
Lag fix sometimes is turned off because of conflicts with other programs, at this point there are really only a handful that may have issues, Got to remember, it has only been 5-6 months from when everyone was using roms mostly written with the original RFS vs now we use ext4. (voodoo lagfix). ME ? I still disable lagfix before flashing a new rom......... just a habit and I never get any problems in flashing.......... but then, that is just me
I read that it slows it down when opening apps is that true?
Turn off before flashing Rome to avoid bricking your device
dcaples002 said:
Turn off before flashing Rome to avoid bricking your device
Click to expand...
Click to collapse
SOFT bricking. and mostly it doesn't even happen, if you going from a 2.2 rom to another 2.2 rom with voodoo enabled, nothing will happen, it'll just save you time from enabling it over again.
It's just a safety precaution, and i don't follow it.
Neither should most people, if they read the instructions and details of the rom their going to flash see if kernel is compatible etc.
If going from a voodoo kernel to another voodoo kernel there is no need to disable. Problems happen when mixing rfs and ext4, as in if u were to flash to a stock kernel over a voodoo one you may end up with misformatted partitions.
Sent from my SCH-I500 using XDA Premium App
I have an LG-P509 from T-Mobile. Recently, I flashed the Megatron ROM, but was not able to unlock my "new P500". (Calls and sms worked fine, but no 3G and the phone was no longer listed as a T-Mobile device.) I cannot be without 3G service, so I reflashed the Nand backup from my original stock setup without wiping anything. Expecting the LG splash I was surprised that my phone is still running Megatron and is still listed as "P500".
What specific files are responsible for identifying a phone to a specific 3G carrier? It seems that my phone is now a "mash" of two different ROM's. I am OC'd and running just fine even though I may not be running as efficiently as possible. Any ideas or suggestions would be greatly appreciated. I would like to isolate the files needed for my phone to stay on T-Mobile and copy them into custom ROMs for convenience (and the challenge).
Thank you!
Brian
I have the same phone as you, but Im running mik's cyanogen port and ive never had the problems your having. I've never ran megatron, but I've ran several others as well and always had 3g. Your carrier and stuff like that comes from your sim card, not any files on the phone. You should give miks cyanogen mod a shot.. just make sure to follow his instructions, and wipe everything first.
Sent from my LG-P500 using XDA Premium App
That is what I thought, but when I loaded Megaton my phone was locked. I'm going to try a few T-mobile Roms & see what happens. As long as I can learn without making a brick...
Sent from my LG-P500 using XDA App
Yes you can root with z4 root http://forum.xda-developers.com/showthread.php?t=833953 and i also suggest you install a custom recovery and ROM here http://tablet-crunch.blogspot.com/20...overy-rom.html I am overclocked using Setcpu at 806mhz on megatron ROM it is a safe way to root and put in custom ROM i dont know about your phone but even rooted with setcpu it wouldnt overclock past 600 the best kernal to use is this one http://forum.xda-developers.com/showthread.php?t=929941 its very fast and fixes the touch screen bug
I posted this for someone else but it will work for you I sugest using milsos Cyogen Mod 7 for your Rom here is the link please be sure to read all instructions and its not my fault if you **** your phone up http://forum.xda-developers.com/showthread.php?t=946354
My complete phone history is as follows:
Z4Root - Successful
Thundurg Recovery v1.2.1 - Successful
Nand Backup + .android secure - got the .img to prove it
Complete wipe & SDCard format
Flashed Megaton - Successful
Opening the T-mobile My Device app results in a locked phone message. Browser will not connect to the internet. Phone & SMS work correctly.
Restored the original Nand backup from adb shell.
Phone is still running Megaton & is listed as a P500. I can overclock to 806 with no problems.
There has to be a certain file or set of files that makes the words T-mobile display at the top of the notifications.
I'm going to flash a different Rom this afternoon to see what happens.
Sent from my LG-P500 using XDA App
Hi all, I don't think most Vibrant users worry about it (at least from what I've seen), but do you worry about losing your baseband/EFS partition/IMEI info when flashing?
For those of you who don't know or forgot, basically some flashes can result in a generic IMEI number and you SIM card would no longer be readable under any custom ROM. You would then have to ODIN to stock and stay there forever, as that is the only way your SIM would be readable.
I know this was a problem a while ago when CM7 or MIUI was flashed, but is it even worth worrying about anymore?
Hopefully someone can inform me and others about the issue. Thank you for your time!
I'm not cause I got my efs backed up. Plus AOSP ROMS are no longer tedious to flash..just flash like any other rom. Though odining back to stock is the only way to leave AOSP I don't really care.
Sent from my T959 using XDA App
Hey laylovj,
So we only have to ODIN to stock if we're going from an AOSP rom to some non-AOSP ROM? (How common are these?)
Also, I remember hearing that if we want to go from Gingerbread (specifically CM7) back to Froyo we'd have to ODIN. Not true?
Sent from my SGH-T959
awebster said:
Hey laylovj,
So we only have to ODIN to stock if we're going from an AOSP rom to some non-AOSP ROM? (How common are these?)
Also, I remember hearing that if we want to go from Gingerbread (specifically CM7) back to Froyo we'd have to ODIN. Not true?
Sent from my SGH-T959
Click to expand...
Click to collapse
Yea...there are three for us VIbrant Owners...
You need to Odin back to stock w/ repartition checked if you want to go back to Sammy based roms coming MIUI and any other CM7 based ROMs.
That's great to know, thanks so much for the info laylovj.
Anyone else?
I think i backed up my efs at some point but i dont worry about it too much... at one point, flashing kernels in gb, i lost.my baseband i had 'no imei' according to my phone... i odined to stock and now im back on cm7 texting 24/7 so idk
... itd prob be aa good idea to have a backup
Sent from a cell tower to the XDA server to you.
Why worry now? I could understand worrying when we were toying with fire--i.e. early voodoo, etc. But almost all roms now are easily flashed and provided you follow instructions to the tee, you will have no problems.
TheSneakerWhore said:
Why worry now? I could understand worrying when we were toying with fire--i.e. early voodoo, etc. But almost all roms now are easily flashed and provided you follow instructions to the tee, you will have no problems.
Click to expand...
Click to collapse
I couldn't stand it if I lost my IMEI and was stuck on a stock, Touchwiz ROM. That's the only reason I worry.
younix258, I do have a backup of my EFS folder, but I guess ODINing to stock will also fix the problem like it did for you. Good to know.
Sent from my SGH-T959
I lost my IMEI a long time ago while flashing an unlocker or maybe CM7. I have this generic IMEI that has been working every since though with all the ROMs. Even Tmobile can't identified what phone I am using but they haven't shut down my service probably because I am paying $200 a month on 3 lines,.
Hmm, I wonder how often that's the case though.
From http://forum.xda-developers.com/showthread.php?t=859914,
"In case you screwed your IMEI by playing with the nv_data.bin and you are experiencing issues like:
Fake IMEI (usually 004999010640000)
Unable to download apps from the market
Unable to unlock your SIM card using your PIN
Weird apps are downloading automatically from the market
Blinking SIM card icon on the top tray… ETC"
So I'd definitely like to avoid losing my IMEI, even if everything seems to be fine without it.
I bought a used GT-I9100M phone that looks new (locked to Bell Canada). But the wifi doesn't turn on.
I click the button to "Turn on Wifi" and the checkmark turns green. Then it scans, finds nothing, and the checkmark turns grey again.
I tried flashing the stock rom (no re-partition), and then doing a factory reset, but it still doesn't work.
Can someone help me?
My guess - Whatever kernel you have is not compatible with the system image. I know this was a problem with UCKK6 for the SGH-I777 - the initramfs of kernels had to be updated for compatibility. Did you flash the stock kernel when you flashed the stock ROM?
Entropy512 said:
My guess - Whatever kernel you have is not compatible with the system image. I know this was a problem with UCKK6 for the SGH-I777 - the initramfs of kernels had to be updated for compatibility. Did you flash the stock kernel when you flashed the stock ROM?
Click to expand...
Click to collapse
I thought I was already on the stock kernel. I will flash it now and update you in a minute.
Ok I flashed the stock kernel, and there is no change.
Any ideas for me? I'm desperate!
Check q&a section several threads about it.
You bought phone with damaged board due to moisture whether humidity, sweat, condensation or dropped in water. Now not sure which board controls wifi whether it's one connected to usb which is cheap and easy to replace, or motherboard which is basically your phone.
Warranty! Try directly samsung since bell will refuse since phone is not tied to your account even if you are bell customer.
Make sure you flash stock Bell kernel, modem and rom before sending for warranty.
Sent from my GT-I9100