Does the T-Mobile Galaxy S5 have the dreaded Knox efuse?
just wanna know before i even try to root?
Yep, it does.
I don't think it's a fuse, but a script run after writing something not of a specific md5 on a sensitive partition (recovery, radio, system etc.) that alters some hidden phone partition. The same case in at&t S2 or S3. If some smart dev can find out that partition and backup and restore it, it could end KNOX tyranny lol
Related
Hi,
following a recent reboot, my Samsung Galaxy S2 (UK version) is mounting the /data partition as read only, causing many FC's and the phone to be unusable. It is not rooted or customised, but I had enabled debugging for development purposes.
Due to Gingerbread's limited backup capabilities (without root), there are items in various applications that I need to recover, if possible.
Can someone please advise on the most straightforward way of getting fsck and enough priviledges on the S2 to fix the disk (assuming there's no hardware fault)?
Is there a version of adb that can give me root access without flashing the device, or is there any way to get the device to fix the disk itself, without doing a factory reset?
For the last week I've been searching with regards to rooting, updating kernels/firmware etc, but there seem to be so many options, that I'm not sure which would be the one that requires the smallest change to the system and therefore the lowest risk. (At thist stage it appears that loading ClockWorkMod using Odin is the way to go, but I may only have one chance not to mess this up, so want to be sure! Are there any critical do's and don'ts? How does Heimdall compare to Odin? What do the manufacturers use?) Also, how will I be able to tell if the Bootloader is locked? How do I unlock it and relock it once I'm done?
I never upgraded the Firmware/OS since I had it and would like to return it to stock when (hopefully) the system is recovered (following which I'll bring the OS up to date). The version is 2.6.35.7-I9100BUKE5-CL227058 [email protected] #2 .
If ClockWorkMod is the best way, can I just change the kernel, or is it best to replace the entire firmware? How do I backup the current factory firmware / kernel before I make changes? Is it possible to do all of this without incrementing the flash counter? Does incrementing the flash counter matter?
During my searches, I've also become aware of the emmc brick bug on the S2. Is this likely to be a problem during the kernal change or whatever may be required to fix the disk format? (I.e. not flashing a kernel that has MC_CAP_ERASE=1.)
If it's not possible to fix the disk, can I use the inbuilt dd command to make a sector backup of the disk and then mount as a partition under LINUX to retrieve the files / databases?
I've used Linux/UNIX for many years, but am quite new to Android and flashing etc. , but I've done similar things with other devices.
Can someone please advise?
Thanks.
Andy.
Hello all.
Yesterday i was trying to install the last version of Paranoidandroid but when phone booted, i noticed that it had no data connection.
So i tried to make a call, but when you compose a number and press the phone button i get the error "not registered on the net" (hope the translation is good as i get the message in my language Italian).
Reading here and there i was able to undestand that the problem is the IMEI: my IMEI is changed and it displays a general one.
The big problem is that i pluged in into my PC the Hard disc that i used to backup my data and it doesn't work.... nothing...All the data are lost...
Am i able to recover my original IMEI (i found some guide around the web to get back IMEIs for AT&T and Verizon S3s with no backup, but not International GT-I9300) without a efs backup or do i need to send it back to Samsung (already resetted counters and restored original stock rom)? If i need to send it back, will they fix it in warranty (i'm still warranty covered) or will they ask me for moneys?
thanks in advance.
Hi,
First, you must try to install the latest stock firmware corresponding to your country and do a wipe data/cache. In some cases, the true IMEI will be back.
After that, if it doesn't work and if you haven't an EFS folder backup, there are no solution to fix your problem. As you said, we can get back IMEI for Qualcomm based Galaxy S3 (corresponding to USA Market) but Exynos' Galaxy S3 used EFS folder containing nv_data.bin that packaged the IMEI number and cannot be write without proprietary software.
If you cannot retreive your IMEI with the first method, send your Galaxy S3 to Samsung After Sale Services. Be sure that your custom flash counter is set to 0 and the firmware is a stock one before try a warranty fixing. In some case, it's covered by warranty (if there are no flashing watermark) but they can demand you some money to do that if they think you have flash/root the device.
lelinuxien52 said:
Hi,
First, you must try to install the latest stock firmware corresponding to your country and do a wipe data/cache. In some cases, the true IMEI will be back.
After that, if it doesn't work and if you haven't an EFS folder backup, there are no solution to fix your problem. As you said, we can get back IMEI for Qualcomm based Galaxy S3 (corresponding to USA Market) but Exynos' Galaxy S3 used EFS folder containing nv_data.bin that packaged the IMEI number and cannot be write without proprietary software.
If you cannot retreive your IMEI with the first method, send your Galaxy S3 to Samsung After Sale Services. Be sure that your custom flash counter is set to 0 and the firmware is a stock one before try a warranty fixing. In some case, it's covered by warranty (if there are no flashing watermark) but they can demand you some money to do that if they think you have flash/root the device.
Click to expand...
Click to collapse
Thank you, i really appreciate your reply.
Already flashed the latest stock rom for my country and operator and resetted all the counters, guess my last resort is Samsung after sales service... let's hope they will not ask for money.
Like @lelinuxien52 said, we can't restore those devices. Next time you should make several backups of your /EFS partition and them put them to an online storage facility, like DropBox, Google Drive or SkyDrive.
Would have loved to help, but you'll have to:
A: Beg that you have an old dusty backup on your PC or SD card somewhere,
B: flash a new Sammy stock ROM (Download here: http://sammobile.com/firmware) and hope that that works,
or
C: Send it to your carrier and hope they can fix it. They'll probably send you a new device, but if you're lucky they have some kind of program which can generate an EFS paritition with the data from the stickers on your phone or box.
Agree with @familyguy59 : DropBox or Google Drive (why not Mega instead of SkyDrive !) is your best friend against EFS folder problem. Do not forget to save it when you receive your new/fix smartphone.
C: Send it to your carrier and hope they can fix it. They'll probably send you a new device, but if you're lucky they have some kind of program which can generate an EFS paritition with the data from the stickers on your phone or box.
Click to expand...
Click to collapse
It would be nice if the software could be available here (but available only for user with bricked /efs folder, not for thieves !).
familyguy59 said:
Like @lelinuxien52 said, we can't restore those devices. Next time you should make several backups of your /EFS partition and them put them to an online storage facility, like DropBox, Google Drive or SkyDrive.
Would have loved to help, but you'll have to:
A: Beg that you have an old dusty backup on your PC or SD card somewhere,
B: flash a new Sammy stock ROM (Download here: http://sammobile.com/firmware) and hope that that works,
or
C: Send it to your carrier and hope they can fix it. They'll probably send you a new device, but if you're lucky they have some kind of program which can generate an EFS paritition with the data from the stickers on your phone or box.
Click to expand...
Click to collapse
To be honests the only lesson i learned here is: Keep that device as stock and stop messing around with it lol
It'a already wonderfull as stock, i had really no need to flash custom ROMs... it's just that i'm a flash-addicted user since my first android phone (Acer Liquid) but well... i deserved it i think ^^
Thanks anyone for the replies
ash1684 said:
To be honests the only lesson i learned here is: Keep that device as stock and stop messing around with it lol
It'a already wonderfull as stock, i had really no need to flash custom ROMs... it's just that i'm a flash-addicted user since my first android phone (Acer Liquid) but well... i deserved it i think ^^
Thanks anyone for the replies
Click to expand...
Click to collapse
Well then you missed something... You can and should mess around with it. Just be more careful.
(Check my description) I have created a universal Android tool kit which, in the next update, hopefully, will be able to back up the GS III's /EFS partition. Check it out, some time.
familyguy59 said:
Well then you missed something... You can and should mess around with it. Just be more careful.
(Check my description) I have created a universal Android tool kit which, in the next update, hopefully, will be able to back up the GS III's /EFS partition. Check it out, some time.
Click to expand...
Click to collapse
ok, thank you ^^
ash1684 said:
ok, thank you ^^
Click to expand...
Click to collapse
click the button to thank him
Glebun said:
click the button to thank him
Click to expand...
Click to collapse
Click the button and say it
Greetings XDA Assist,
I have read a bit about Samsung locking up 8GB of the 16GB internal memory.
My used phone, just purchased, is already rooted, with unlocked MDK bootloader (the original one, so it allows full root control).
It reports 9.55GB total (both used & available). The previous owner installed a stock VZW NC2 ROM, which may explain the slightly larger available space than the 8.xGB reported on the web.
My previous phone, a Samsung S3 VZW i535 reported 11.95GB total. It didn't achieve 16GB either, but at least it only lost a quarter instead of half!
Since my phone is fully rooted, is there any way to regain some of the lost potential?
I know a bit about bloatware removers (NoBloat, Jumobile's System App Remover) but have not used any yet. Would using these actually increase the total available internal memory space?
Is there a hidden partition at work? Can root users do something about it?
A portion of your space is taken up by Bloatware included by Samsung and Verizon. you may wish to review
KitKat Bloatware || Safe-To-Remove System Apps of 4.4.2
Typically that would free up a lot of space. Only on a few occasions, your phone's partition table would get messed up. If that happens, you'd need to reflash stock firmware. Please review and post in [Q&A] [ODIN][TAR] I545VRUFNC5 Factory and No-Wipe Odin tars if you suspect such to be a case.
More questions...
Perseus said:
A portion of your space is taken up by Bloatware included by Samsung and Verizon. you may wish to review
KitKat Bloatware || Safe-To-Remove System Apps of 4.4.2
Typically that would free up a lot of space. Only on a few occasions, your phone's partition table would get messed up. If that happens, you'd need to reflash stock firmware. Please review and post in [Q&A] [ODIN][TAR] I545VRUFNC5 Factory and No-Wipe Odin tars if you suspect such to be a case.
Click to expand...
Click to collapse
Thanks for the links, Perseus. I happened upon the Kitkat Bloatware page already. I used it to run a predictive scenario with Jumobile's System App Remover, and it came up with a figure of half a gig.
My "Storage" applet in Settings reports 6.43GB in Miscellaneous files, but when I look inside it lists just about 5MB of specific items in the list. Is the rest of this somehow locked up in the ROM?
In any event, half a gig is far short of the 6.43GB figure. How much more of the remaining 6GB or so can I reclaim? And why doesn't the full 16GB report when I'm looking at the "Phone" partition on a Windows 8.1 PC when the phone is connected to it via USB? No matter how much is used for whatever reason, the full space (or something fairly close, like 14-15GB) ought to report in Windows File Explorer. That suggests a hidden partition is at work. Can I make this visible on a fully rooted S4 with an MDK loader?
The used phone I just got reports having a stock NC2 build and an NG6 baseband (modem). Would that somewhat odd combination account for so much space being locked up even on a rooted phone?
EDIT: Seems like the best way to deal with Samsung & VZW bloatware is simply to install a custom ROM. However, I usually stick pretty close to stock. The previous owner of my S4 i545 reported his power button became unreliable when he installed a custom ROM. On the other hand...
I've heard that it can be dangerous to load stock ROMs on an i545 S4 because you can lose your precious original MDK bootloader, the only one that can be unlocked via the Loki process. (I didn't do the original unlocking and rooting myself; the previous owner did it.) Do the "no-wipe" ODIN ROMs in the other link you provided deal with this issue?
EDIT: Just viewed the second link, and it specifically warns against using if you want to keep custom recovery, which I most definitely do! Are there ways of proceeding with returning to stock that do NOT put custom recovery and MDK bootloader with Loki Exploit at risk?
I've heard that Samsung's ODIN can be problematical. Some recommend an open-source alternative called Heimdall with a front-end app called Heimdall One-Click. Any opinions about that?
EDIT: Or can the whole ODIN/Heimdall thing be bypassed using a custom recovery front end such as ROM Manager, which I have long used?
I would like to be able to use ROM Manager app to select and install ROMs like I did on my previous smartphones (HTC Droid Incredible, Samsung S3 i535). Now that ROM Manager supports TeamWin Recovery Project (TWRP -- v2..71 is currently installed on the used phone) will I be able to safely use that to change ROMs on my S4 i545?
Thanks for all answers from you or other certified RPs on XDA Assist! :fingers-crossed:
EDIT: RP moved me to Q&A, so goodbye XDA Assist! Anyone who can help provide answers is welcome to respond.
Cheers,
Kirk
The best debloater I've found is Kevs.Tweaks.v.2.1.0 and it has a nice Aroma interface to select what to uninstall. Of course it has to be ran from Safestrap or your recovery...
I have Verizon Samsung Galaxy S4 (SCH-i545) with the MDK bootloader. It is rooted, ROMed (GPE 4.4.4), has a custom kernel and custom recovery (PhilZ). I am using a Windows 7 PC (a 32 bit version.) I have nandroid backups and Titanium Backups, and now I want to do a backup to my computer to safeguard the nandroids, titaniums and also stuff like my pictures, other data, and frankly, I want as much of my phone on my computer (and browseable) as possible.
Essentially, I want a backup of my full internal sdcard (aka the built-in storage) and the microSD card. If it's easy I'd also like to backup stuff like the lowest level stuff (you know, the stuff that requires root access to modify when using a file explorer,) however that's secondary.
I am not sure what method will make the most thorough backup, but I know that dragging and dropping isn't the answer. If possible, I'd also like the backup to be broweable on Windows.
At first I was thinking just an adb pull (as detailed here), but I'm not sure if that'll capture everything that I need. Apparently Motorola blocks this method from getting everything, and I'm not sure if Samsung does too.
Then I found the natural backup function of adb, but I've heard mixed reviews, AND I'm not even sure it works if your phone has a locked bootloader (the MDK bootloader is locked; there's a workaround named loki for flashing stuff, but I doubt that matters in this case.)
This way looks like it might be very thorough, but it's a bit on the complex side, so if there's another way, I'd certainly prefer it.
Can someone please shed some light on how I could/should do this?
So I recently rooted my device, but forgot to remove KNOX's data beforehand. Now, KNOX warranty-void status has been activated, and I can't figure out how to remove KNOX itself. Uninstalling the app from the system itself just removes the launcher...
...but not the 9.6 gb of useless, unrecoverable data.
If anybody could point out a way to remove this useless data that is eating more than half of my phone's memory, that would be much much appreciated.
EDIT: My phone is a Samsung s5 g900w8
Are you really rooted? Your question seems irreal.. you uninstall knox as any other sys app.
Sent from my SM-N910F using Tapatalk
I am sure I am rooted. I can run superuser commands, and superSU returns that it is definitely rooted. I suppose that I could try again...
EDIT: uninstalled again, KNOX size went up 300 mb (...?)
Confusing, but uninstalling does not remove the 9.9 gb of data...
Late reply on my effort
So after following hundreds of online tutorials of how to remove My Knox data, none of them worked. My theory is that this is because of the way My Knox works. My Knox is treated as a seperate user, so simply uninstalling it would not work as it would require Knox to be unlocked, which would never be able to happen due to the Knox Warranty Void.
I ended up just backing all of my data up, and doing a factory reset, then just rerooting it. Was much quicker than attempting to find information about a lost cause; especially when nobody seems to actively want to help.