Related
I'm getting a Not Registered On Network error on my phone since I tried the official Jelly Bean update.
The IMEI seems to ave changed too and I've a serial number of 00000000
I had a look at other threads but this only happen after I did the flash - I've tried going back to stock but it seems to be there too
Theres an official jellybean update for this device? *headscratch*
I'm going to assume you flashed the update for the international variant on your d2vzw. Odin back to stock.
Tearaway said:
I'm getting a Not Registered On Network error on my phone since I tried the official Jelly Bean update.
The IMEI seems to ave changed too and I've a serial number of 00000000
I had a look at other threads but this only happen after I did the flash - I've tried going back to stock but it seems to be there too
Click to expand...
Click to collapse
In the dev section there is a tutorial on how to backup and restore your IMEI. I still *knock on wood* haven't run into that issue yet.
Sent from my SCH-I535 using xda app-developers app
Tearaway said:
I'm getting a Not Registered On Network error on my phone since I tried the official Jelly Bean update.
The IMEI seems to ave changed too and I've a serial number of 00000000
I had a look at other threads but this only happen after I did the flash - I've tried going back to stock but it seems to be there too
Click to expand...
Click to collapse
Did you properly backup your IMEI as described in several threads in the development section? If so, restoring your IMEI is simple.
apacseven said:
Theres an official jellybean update for this device? *headscratch*
I'm going to assume you flashed the update for the international variant on your d2vzw. Odin back to stock.
Click to expand...
Click to collapse
No, there are several unofficial Jellybean roms for our phone. They are based on the T-Mobile leak from a while back. We're a ways away from an official jellybean OTA. The OP wouldn't be able to boot their phone and discover their IMEI changed/phone number reset had they flashed an international rom.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
No, there are several unofficial Jellybean roms for our phone. They are based on the T-Mobile leak from a while back. We're a ways away from an official jellybean OTA. The OP wouldn't be able to boot their phone and discover their IMEI changed/phone number reset had they flashed an international rom.
Click to expand...
Click to collapse
Right, but if you read his post he said official, not unofficial.
apacseven said:
Right, but if you read his post he said official, not unofficial.
Click to expand...
Click to collapse
Idk how I missed that smh. Well, we'll see soon enough what exactly they flashed.
OP, could you post where you got this official update from? Link? Cuz there are definitely no official Jellybean anything for our phones as of yet.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Idk how I missed that smh. Well, we'll see soon enough what exactly they flashed.
OP, could you post where you got this official update from? Link? Cuz there are definitely no official Jellybean anything for our phones as of yet.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I'm getting that sinking feeling...
I tried posting the link but as I'm a new user I'm not allowed - it's the Polish update - google will lead you to it
Tearaway said:
I'm getting that sinking feeling...
I tried posting the link but as I'm a new user I'm not allowed - it's the Polish update - google will lead you to it
Click to expand...
Click to collapse
Sadly you flashed an international rom. Sorry. I thought this would be a hard brick. But since you can boot you can odin back to stock.
http://forum.xda-developers.com/showthread.php?t=1762709
Sent from my SCH-I535 using xda app-developers app
Its not a hard brick since he is able to boot up, but beyond that IDK. OP, when you said you tried stock and still no go, did you mean that you used Odin to flash a stock image? If not, that is your best bet.
As long as you can odin back to stock and you have a Verizon device, there is a tool in the dev sections stickies that can restore your IMEI even without a backup.
Now that u r back to stock do a search for IMEI restore on xda to restore your phone.
For future reference note that there are several GS3 variants and u can only flash the one specific to your carrier if u want to have a functional device. The international version doesn't even have the same processor.
Sent from my SCH-I535 using xda app-developers app
sololhj said:
Now that u r back to stock do a search for EMIE restore on xda to restore your phone.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
*IMEI.....just want to be precise.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
*IMEI.....just want to be precise.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You are correct, but I think you mean more accurate not precise
THanks for all the pointers - I'm a bit confused though and possibly I haven't given enough info...
The S3 was originally running on AP i9300xxalef CP i9300xxlef CSC 19300OJVALEC and it was rooted - I'm in Ireland so it appears to be an international phone.
I can't get a product code because when I try it gives me NOt Registered On Network
Previously when ever I tried to update it via Keis I never could and it always showed the serial as 000000000 I also think the IMEI as different.
I did try to flash it previously and it failed I but it kept working - So I wonder could the IMEI switch have come from that - as I do seem to remember the 000000000 from before I tried Jelly Bean.
If I put it back on the same AP CP and CSC would it work again - and how would I go about it?
Thnaks
Brought it back to the original firmware - and getting a no signal icon now!
I don't know of any tool for the international model's Exynos that is like the tool for the Qualcomm processor.
Everything I've seen, says in order to restore it on the Exynos processor, you need to have backed up your EFS folder. There are a couple threads in the International GS2 forum (not the GS3 forum) detailing how to repair it, but that entails you having have backed up your EFS folder.
Not sure if there is a way to fix the problem if you are able to get the IMEI number from your box or behind the battery.
Edit: I just did some googling and found there is some kind of Samsung tool for repairing it. There are a couple youtube videos that I found as well. Some tec site is claiming that once you restore to stock, you get a new EFS folder on your phone and although the information will be incorrect inside of it, you may be able to edit it. :shrug: You would have better luck in the international forums though if you have an international phone.
Tearaway said:
THanks for all the pointers - I'm a bit confused though and possibly I haven't given enough info...
The S3 was originally running on AP i9300xxalef CP i9300xxlef CSC 19300OJVALEC and it was rooted - I'm in Ireland so it appears to be an international phone.
I can't get a product code because when I try it gives me NOt Registered On Network
Previously when ever I tried to update it via Keis I never could and it always showed the serial as 000000000 I also think the IMEI as different.
I did try to flash it previously and it failed I but it kept working - So I wonder could the IMEI switch have come from that - as I do seem to remember the 000000000 from before I tried Jelly Bean.
If I put it back on the same AP CP and CSC would it work again - and how would I go about it?
Thnaks
Click to expand...
Click to collapse
Maybe you should post this NOT in the Verizon section to avoid confusion.
Sent from my SCH-I535 using xda app-developers app
Thanks
voodoomanx said:
Maybe you should post this NOT in the Verizon section to avoid confusion.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
mia culpa
I'm new here :cyclops:
Thanks for all your help - I'll post it on the international forum - now that Ive gotten used o the idea that I've a very pretty paper weight I can pay abit more attention to what I'm doing :laugh:
S3 serial changed
I updated to stock firmware
I lost imei n I got unknown imei
N also signal lost. No network
Plz tell me
Is it possible to restore a backup of one phone to another phone that is the same model? Thanks in advance!
Sent from my X9017 using xda app-developers app
musmos said:
Is it possible to restore a backup of one phone to another phone that is the same model? Thanks in advance!
Click to expand...
Click to collapse
Why, oh why, can people not search? This has been asked many times before.
Yes it is possible but it may not work properly as even the same phone model can have different components and there can be other factors that tie some parts of the software to an exact phone.
SINGAPOREAN said:
Hi,
I don't understand why would the SAME phone model not be able to use the SAME ROM?
If there were to be different components, then it would not be the same model, would it?
ie. our recent Samsung Galaxy Note II. There is the LTE and non LTE variations, thus they are two different models. ie. LTE ones are N7105 and non-LTE ones are N7100
Click to expand...
Click to collapse
Prime example being the HTC Desire S. During production the panel changed from Hitachi to Sony which causes problems with a lot of the newer kernels. During any production run components are changed based on price and availability. Standard manufacturing principles.
Why do I lose backups every time I flash a new ROM?
krob8768 said:
Why do I lose backups every time I flash a new ROM?
Click to expand...
Click to collapse
Please don't jump into a thread that has absolutely nothing to do with your post. It is a good way to guarantee getting no response at all.
This is an APK that uses the ExynosAbuse exploit (by alephzain) to be able to do various things on your Exynos4 based device.
Features for non-rooters:
- Securely patch the exploit
Features for rooters:
- Root the device (SuperSU v0.99)
- Enable/disable the exploit at will
- Enable/disable patching the exploit at boot
- Unroot and cleanup (optionally leaving the exploit patch at boot in place)
Please note that patching the exploit may break camera functionality, depending on device and firmware. Also note that if use the patch method without rooting, or keep patching the exploit at boot enabled when unrooting, you need an alternate method to re-root the device to disable this feature (like CF-Auto-Root) - you cannot use ExynosAbuse to do this since it patched the exploit. Unlike other patch authors, I do not believe in keeping an invisible rooted process running in the background while pretending you aren't rooted, to be able to unpatch this way.
While the exploit patches work (aside from possibly disabling your camera), these are more work-around than actual fixes. A proper patch would be a kernel fix, either from a third party or Samsung themselves (hopefully one day...)
My method vs Supercurio, RyanZA
Mine is the only one that is secure. Both Supercurio's and RyanZA's method leave you with easily exploitable holes any serious malware author will abuse. More details http://forum.xda-developers.com/showthread.php?t=2053824
Exploit
For more details on the exploit itself, see this thread: http://forum.xda-developers.com/showthread.php?t=2048511. The exploit is used by this APK in unmodified form. You should be very afraid of this exploit - any app can use it to gain root without asking and without any permissions on a vulnerable device. Let's hope for some fixes ASAP !
Camera
If your camera keeps working depends on your device/firmware combination. Affected are mostly the SGS3, but there is good news too, there is a potential fix here: http://forum.xda-developers.com/showthread.php?t=2052675 SGS3 I9300 ONLY. It seems to work for a number of people. It replaces some system libraries with libraries from a different firmware version that does not rely on /dev/exynos-mem. Do not attempt this unless your camera actually breaks due to the exploit, and beware it may cause you to have to reflash your firmware. Also beware that even though this change will not prevent OTAs from downloading, it can possibly prevent OTAs from flashing succesfully.
Device status
Using this patch may turn your device status into modified. There's not really a proper solution to that at the moment, but you can restore status by removing the patch (and SuperSU) again and rebooting your phone. This will however leave you unprotected again. Doing all sorts of weird stuff (like for example wiping data) to get rid of this modified status while you're still have the patch applied at boot or keep SuperSU around, is an exercise in futility. If you want to go ahead and do that, that is fine, but do not litter my thread with your comments. Because eventually, the modified status is likely to return
Compatibility:
(If your device isn't listed it could still be both compatible with the exploit as well as this fix !)
Samsung Galaxy S2 GT-I9100
Samsung Galaxy S3 GT-I9300
Samsung Galaxy S3 LTE GT-I9305
Samsung Galaxy Note GT-N7000
Samsung Galaxy Note 2 GT-N7100
Samsung Galaxy Note 2 LTE GT-N7105
AT&T Galaxy Note 2 SGH-I317
Verizon Galaxy Note 2 SCH-I605 both locked and unlocked bootloaders work
Samsung Galaxy Camera EK-GC100
Samsung Galaxy Tab Plus GT-P6210
Samsung Galaxy Note 10.1 GT-N8000, GT-N8010, GT-N8013, GT-N8020
Google Nexus 10 not compatible, Exynos5
Post in this thread if you have a device to add.
Notes
I'm not sure if this APK will work right on Android 2.x devices (not tested yet), doesn't mean the exploit doesn't work. So if you're on Android 2.x and this APK doesn't work for you, try doing the exploit manually.
Download
Please do not redistribute, link to this thread instead
v1.40 hashes:
MD5: be4a373ff2848a16bfb948d7e1d1f7d2
SHA1: 79670ab10da59ea58df222e94ad9e8ed83c791a9
(v1.00: 3786; v1.10: 6397; v1.20: 12004; v1.30: 14480)
Changelogs
2012.12.19 - v1.40
- Added check for updates functionality
- Added "current status" display
- Split into sections for non-rooters and rooters
- Added "One-click secure exploit patch" for those who just want to patch their device and forget about
- Added ability to unroot and clean up the leftovers (optionally leaving the patch code in place)
2012.12.18 - v1.30
- Adjusted many things in the shell code, the app will now properly detect an install SuperSU/Superuser with the wrong permissions as NOT having root
- Added a startup notification telling you your device/firmware is not susceptible to this exploit, if it isn't
2012.12.17 - v1.20
- Gingerbread-related fixes - note that not all Gingerbread firmwares of affected devices are vulnerable (for example, I know several SGS2 GB firmwares are not exploitable)
- Added some spam (view my apps on Play, follow me on Twitter, that sort of BS)
- Added icon
2012.12.16 - v1.10
- Added ability to disable and re-enable the exploit (which may break camera)
- Added ability to disable exploit at boot (before any Play-installed app runs, other solutions run later which means they are still vulnerable)
- Both above features require being rooted
2012.12.16 - v1.00
- Initial release
--- reserved as well ---
Nice, fast work. Thanks.
Wow that was quick. Good work Chainfire!
Confirmed working on Samsung Galaxy S2 GT-I9100
Sent from my GT-I9100 using xda premium
Will this root the Sprint/Boost mobile version of the Galaxy S2? Thank you in advance.
Confirmed working on the Verizon Galaxy Note 2 (SCH-I605)
imnuts said:
Confirmed working on the Verizon Galaxy Note 2 (SCH-I605)
Click to expand...
Click to collapse
Locked or unlocked bootloader ?
Chainfire said:
Locked or unlocked bootloader ?
Click to expand...
Click to collapse
Still locked and fully stock.
Works as expected under note 10.1 n8010 4.1.1 stock.
Sent from my GT-N8010 using xda app-developers app
This is a amazing apk app. Right from my phone rooted my phone. Wow! It's unbelievable.
How do you unroot?
SupperDroid said:
How do you unroot?
Click to expand...
Click to collapse
SuperSU --> Settings --> Full unroot
SupperDroid said:
How do you unroot?
Click to expand...
Click to collapse
If you've got SuperSU installed, open it, go to Settings and scroll down and you'll see it says unroot.
Sent from my Nexus 7 using xda premium
benzmar said:
This is a amazing apk app. Right from my phone rooted my phone. Wow! It's unbelievable.
Click to expand...
Click to collapse
as pointed out by Chainfire, this is dangerous too, so beware. :angel:
drraptor said:
as pointed out by Chainfire, this is dangerous too, so beware. :angel:
Click to expand...
Click to collapse
The danger is inherited from the stock kernel and not an outcome by the use of CF's app.
The app just exploits the kernel's security hole.
Does anyone know if this will work on an S2 i777? It too is running an exynos processor.
Sent from my Nexus 4 using Tapatalk 2
Worked flawlessly on my Boost Mobile Galaxy S2! Thank you sir.
Works also with Galaxy S3 Lte
Hi all
Just got a question regarding the version software my note is running,
I understand there are a number of different versions getting around, I'm unclear as to what is the latest version for my particular model
Currently it is running 4.0.4, yet I know there are much newer versions getting around, yet when I try to run an update it says there are no updates for my device
Can anyone clarify for me if what I have is the newest version for my note
Cheers
I havent got a 8010 i have the optus delivered 4g version 8020 and im on 4.1.2 i think.plug yours into a pc and fire up samsung kies...let it do its thing and check for a update.you should have one available.
Sent from my GT-N7000 using xda premium
Ricbec said:
Hi all
Just got a question regarding the version software my note is running,
I understand there are a number of different versions getting around, I'm unclear as to what is the latest version for my particular model
Currently it is running 4.0.4, yet I know there are much newer versions getting around, yet when I try to run an update it says there are no updates for my device
Can anyone clarify for me if what I have is the newest version for my note
Cheers
Click to expand...
Click to collapse
You can flash you device throught Odin:
Use BTU or NZC firmware.
h**p://samsung-updates.com/device/?id=GT-N8010
Well believe it or not kies says it is the most current version, guess we must just miss out here in Aus
This is why I use other country roms...
I dont think I'd ever have the courage to do something like that on my own device, sounds a little complicated to the novice modder, I'd be too scared to brick it!!
You shouldn't be. It's a piece of cake.
http://techmell.com/android-tips/how-to-install-galaxy-note-10-1-n8010-zccma4-android-4-1-2-jelly-bean-official-firmware/
Is it possible however that I may lose some functionality by doing this? It does sound simple enough, I can build computers so I should be able to do it
Ohh, and I lose all software installed correct?, hence the extra special need to backup prior?
I didnt lose any apps or settings but I went from 4.1.1 to 4.1.2 updated without a hitch.it will sudgest a backup but I didnt have time or my pc to backup too.i was at work.but a backup is good while you are waiting for the file to download.not sure what the go is nowdays but I use to use titanium backup the paid version.you need a rooted tab tho....not a big deal....google exynos abuse and grab the apk and install that.its made by a dev called chainfire (very trustworthy)it can root your tab in about 30 secs.once rooted you can backup you apps and settings if needed.i somtimes had probs with the settings part, but no probs with the just apps. Once backup is done flash the new firmware, reboot and play for a few mins....then reboot again....root tab again with exynos abuse as it should loose root rights with the new firmware....then re install titanium and load your backup and or your sammy kies backup too. Clear as mud eh?
Sent from my GT-N8020 using XDA Premium HD app
Ricbec said:
Ohh, and I lose all software installed correct?, hence the extra special need to backup prior?
Click to expand...
Click to collapse
No, you don't loose apps, but it's recommended to factory reset your device. I went through 4.0.3 -> 4.1.1 -> 4.1.2 without wiping. But finally I did a factory reset to be sure
Okay, thanks for the info
Finally, what are the improvements, additions and removals for the device between 4.0.4 and 4.1.2
Cheers
I believe the jelly bean update is now available for GT-N8010 Australian model
Multi window manager is nice....there nice a app that enables it for every app you have installed too.
Sent from my GT-N7000 using xda premium
I just noticed when sniffing the new 9500UBUAMDK kernel is that they activated a new "feature" / CONFIG_SEC_RESTRICT_SETUID in the kernel.
This means no more rooting is possible, at least not anymore in the usual methods. Your SuperUser will tell you it will have granted access, but it's neutered on the kernel level.
There is the exception of allowing /system/bin/pppd to gain root access so somebody will want to maybe replace that somehow to gain it as an entry-point. Somebody will want to check that.
This doesn't apply to custom compiled kernels which disable this config option.
Omg.......hope somebody can bypass that one.......sad news for me.....XXUAMDL now....arghhhh
Sent from my GT-I9500 using xda premium
This makes sense cause I flashed MDM for I9505, I used djembey's modfied stock root and apparantley it works, well yeh it works but that because it reverted my kernel back to an older version it didn't actually root the current kernel it reverted back to the older kernel. Because my rom was dated 12th April after i updated the firmware it was 25th april. Then I used the Modified root that is meant to work on all firmwares, I checked the date of the kernel after i rooted and I am now back to the 12th.
AndreiLux said:
I just noticed when sniffing the new 9500UBUAMDK kernel is that they activated a new "feature" / CONFIG_SEC_RESTRICT_SETUID in the kernel.
This means no more rooting is possible, at least not anymore in the usual methods. Your SuperUser will tell you it will have granted access, but it's neutered on the kernel level.
There is the exception of allowing /system/bin/pppd to gain root access so somebody will want to maybe replace that somehow to gain it as an entry-point. Somebody will want to check that.
This doesn't apply to custom compiled kernels which disable this config option.
Click to expand...
Click to collapse
CORRECT!!
I've tested it and it's true.... I9505 STOCK Kernel for new builds MDM/MDN has been LOCKED as well....
My solution is to use Kernel from builds up to MDF and include it into CF-AutoRoot package and it WORKS like charm... (Future proof..)
BTW, they have changed something in system.img.ext4 as well!! Checksum added or something like this, if you re-build it, whole integrity is broken... SYSTEM IS LOCKED!!
CSC is impossible to apply usual way, I've implanted it into system and modified to achieve HD Voice support on all networks.. NOTHING can be added to it afterwards..
Ahhh, this is why I'm getting the following error, damnit!
"BusyBox works but the "su" command does not elevate to root. There's something wrong with your "su" binary and/or "Superuser" app."
I am sure other methods will be found soon. u know u can count on the good folks here at xda.
Sent from my GT-I9500 using xda premium
removed
WOW
great work Samsung :crying::silly:
AndreiLux said:
I just noticed when sniffing the new 9500UBUAMDK kernel is that they activated a new "feature" / CONFIG_SEC_RESTRICT_SETUID in the kernel.
This means no more rooting is possible, at least not anymore in the usual methods. Your SuperUser will tell you it will have granted access, but it's neutered on the kernel level.
There is the exception of allowing /system/bin/pppd to gain root access so somebody will want to maybe replace that somehow to gain it as an entry-point. Somebody will want to check that.
This doesn't apply to custom compiled kernels which disable this config option.
Click to expand...
Click to collapse
Damn!.. I updated my GS4 from UBUAMDE to UBUAMDK and was just now planning to root it when i saw this post.. *sigh*... Nonetheless,thank you for the information and insight kind sir, and I hope there will be a workaround soon for root access *fingers crossed*
Well can we just flash a rooted rom from recovery?
Sent from my GT-I9500 using xda premium
samomamo said:
Well can we just flash a rooted rom from recovery?
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
no u need kernel that disable CONFIG_SEC_RESTRICT_SETUID to get the SU binary working
> kernel that disable CONFIG_SEC_RESTRICT_SETUID
patch one byte in kernel file?
yahyoh said:
no u need kernel that disable CONFIG_SEC_RESTRICT_SETUID to get the SU binary working
Click to expand...
Click to collapse
Well then we can flash a kernel.
Sent from my GT-I9500 using xda premium
AndreiLux said:
I just noticed when sniffing the new 9500UBUAMDK kernel is that they activated a new "feature" / CONFIG_SEC_RESTRICT_SETUID in the kernel.
Click to expand...
Click to collapse
I'm afraid you are right. I did a source code review a few days ago in a German forum and came to the same conclusion: We need a Stock Kernel with deactivated Root Restriction Feature or a custom kernel without these features.
I'm not sure, if we can build something around the pppd issue. Some "rename pppd temporarily if root is needed special hacking service". But sounds somehow crazy, and I'm not sure, if it is worth a try. You have to modify the systemfs, and I think, a Custom Kernel is easier.
Do you think there are dependencies in the rest of the firmware to the Root Restriction Feature? In other words: Will disabling this feature cause trouble, e.g. with Knox?
And since we have kernel sources can't we recompile our own kernel with this option disabled? I don't think this as a deadlock state. It is pretty much possible to bypass.
I think, this will be possible. At least it will be my first try as soon as I have my own S4 in my hands. Building a stock kernel from source without Root Restriction.
BTW: In the actual Samsung source code the feature is disabled in the default configuration. Hmmm ...
AndreiLux said:
I just noticed when sniffing the new 9500UBUAMDK kernel is that they activated a new "feature" / CONFIG_SEC_RESTRICT_SETUID in the kernel.
This means no more rooting is possible, at least not anymore in the usual methods. Your SuperUser will tell you it will have granted access, but it's neutered on the kernel level.
There is the exception of allowing /system/bin/pppd to gain root access so somebody will want to maybe replace that somehow to gain it as an entry-point. Somebody will want to check that.
This doesn't apply to custom compiled kernels which disable this config option.
Click to expand...
Click to collapse
Could they possibly be getting some kernels ready for military purpose devices?
Sent from my GT-I9300 using xda app-developers app
RiverSource said:
BTW: In the actual Samsung source code the feature is disabled in the default configuration. Hmmm ...
Click to expand...
Click to collapse
They enabled it in the last sources.
Anyway the problem with a compiled kernel is to get exFat working; I can load exfat_core now but exfat_fs is giving me kernel page faults.
thats because latest exynos exploit story, so now u dont have to worry about holes in os. its unrootable
Aaaaaaaaaannnddd im returning my s4. Not gonna keep dealing with this s*** every time that there's updates.