whoops I flashed super wipe on a phone it wasn't intended for?
Sent from my SGH-T999 using xda premium
Sent from my SGH-T999 using xda premium
whoops I flashed super wipe on a phone it wasn't intended for?
Sent from my SGH-T999 using xda premium
whoops I flashed super wipe on a phone it wasn't intended for?
Sent from my SGH-T999 using xda premium
..
If you've never lost your IMEI before, I could see how you might blame stupidity.....
I rooted my phone via Odin. The non trip method, yet my phone says modified. I don't know if it was supposed to or not...and this is user error. I did not read fully, why, and that's most people's problems: not reading fully, skipping steps.
I guessed the basis of my point is why isn't it happening to everyone...
It's probably busybox. There's a service on the stock rom that periodically scans for "bad" things like /system/bin/busybox, then flags it modified. Uninstalling busybox and waiting for another rescan (or rebooting) will return the status to normal.
Because the variables are... variable. It'll eventually get narrowed down.
what is the cause(s) for losing the imei on these devices? if we had a common denominator across past devices, it could be a good starting point for determining what is going on here
what is the cause(s) for losing the imei on these devices? if we had a common denominator across past devices, it could be a good starting point for determining what is going on here
Everyone can read my previous posts on this and I am going to advise people NOT to flash cwm touch via Odin tar because I have had two phones now mine is working fine been on CM10 for 3 days installed cwm touch via adb. The other one yesterday sadly cwm touch was installed via Odin tar and after CM10 installed lost imei. You can check my signature I have owned and rooted almost every phone experience with Odin and cwm and both Samsung DL mode and HTC bootloaders.
I'm not saying this is the only cause but it was a cause on a brand new phone that is now headed to Samsung for repair!
Sent from my SGH-T999 using xda app-developers app
I wouldn't call it stupidity I would say its user error. 9x out ten it usually is.
It doesn't mean your stupid. Like forgetting to turn usb debugging, or disabling fastboot, or even Dl a corrupted file... yes these are considered user error, its not about fault.
Computers are computers are computers...even when they are a mobile device. A computer only does what you tell it to even when you inadvertently do so. Like people who mass-click links or commands when the computer is not responding.
I rooted my phone via Odin. The non trip method, yet my phone says modified. I don't know if it was supposed to or not...and this is user error. I did not read fully, why, and that's most people's problems: not reading fully, skipping steps.
I guessed the basis of my point is why isn't it happening to everyone...
Somehow somewhere there must be some kind of variable causing this.
If you take the imei off your box, you can't put it back manually ?
There has to be a work around for this.
Think I'm gonna hold of on the recovery flashing ....
Sent from my DROID X2 using Tapatalk 2
Everyone can read my previous posts on this and I am going to advise people NOT to flash cwm touch via Odin tar because I have had two phones now mine is working fine been on CM10 for 3 days installed cwm touch via adb. The other one yesterday sadly cwm touch was installed via Odin tar and after CM10 installed lost imei. You can check my signature I have owned and rooted almost every phone experience with Odin and cwm and both Samsung DL mode and HTC bootloaders.
I'm not saying this is the only cause but it was a cause on a brand new phone that is now headed to Samsung for repair!
Sent from my SGH-T999 using xda app-developers app
It's probably busybox. There's a service on the stock rom that periodically scans for "bad" things like /system/bin/busybox, then flags it modified. Uninstalling busybox and waiting for another rescan (or rebooting) will return the status to normal.
Because the variables are... variable. It'll eventually get narrowed down.
I have an off topic question for you. I know busy box performs a number of Linux commands and background processes, but why do we install it. I always install it, I'm not so much interested in all its functions because I know there are many, but the hy do we install it as soon as we root? I more or less do it blindly out of habit & I'm rather unclear on what it needs to be there for.
Maybe a Poll should be made...that way we can kind of keep track of How many people this has affected so far. Along with the recovery they used. Version number as well. And How long they've been using that recovery before the zap.
I wasn't even aware it was required for adb, shows how much I know, lol. That's reason enough to make it necessary Imo.We install it because quite a few root apps require, or just work more simply, when the extra powerful tools are there, so they don't have to reinvent the wheel in java.
That reason aside, *I* install it mainly because I use the adb shell all the time and can't live without many common utils like find, grep, wc, less, etc.
I'll concur, that command looks ok to me.. Don't really need to cd /sdcard though but it won't hurt anything.
zonly, good luck, and as usual, this is at your own risk but you already have a brick right
Assuming you can get back to a shell afterwards, you can (theoretically) re-dd the original img back to restore the original state.
has anyone tried restoring a complete dd backup after losing imei?
dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=/external_sd/efs_backup.img
dd if=/external_sd/efs_backup.img of=/dev/block/platform/msm_sdcc.1/by-name/efs_sdcc.1/by-name/efs