Related
I got a note7000 offer at a bargain price; half the price of the original... the idea is that the guy is selling it as fault emmc bug. He told me that wiping the data - factory reset caused the problem.
The phone works from times to times he said, is still partially functional, thus he still asks for the price of SII for it, which he wants to replace with.
My question is:
Is the emmc bug permanent? I want to buy it cause is such a awesome screen\phone and i cant afford one from retails at full price. My plan is to downgrade from ics to gb with safe kernels and hope it wont brick with odin as unsafe as it is already.
Don't buy it. He is selling a bricked device for half the price (I wouldn't pay that for a used but fully functional right now).
And you will always get problems with it in many different situations.
Its risky for me, but also rewarding. If you'd seen this particular phone, is almost brand new. He told me it wasn't used much and that is visible on the over all aspect. And god, i love amoled screens, even if pentile is infamous.
Could you describe what you mean by being bricked? -> the phone boots and installs stuffs, but from time to times has the flaw of getting stuck -> require reset.
Its on the way
ps. I trust that if i had this stuff happen to me, coming from a samsung product, i would be able to get it fixed somehow.
Congrats: you just bought a bricked device. I guess he used the repartition workaround which reduces available capacity.
He didn't do the only real fix: replace motherboard in Samsung Service Center.
If you read here more before buying you would understand my "do not buy". Now you will learn later.
And he didn't lie to you - he told everything about the condition.
If you want to learn now while waiting for it, start to read about bricked devices here, about hg42's repartition thread etc. You might need it
Well, wish me luck. I'm gonna follow the steps from around the topics here.
I just hope i can watch movies, and pictures, and browse the mail... then he can get stuck but just a little.
I got an ace on my sleeves though. I can test it before i buy it... any advices, maybe doesn't even have the bug, how i notice
that ?
I'm gonna try these steps on the clip from rootgalaxynote:
youtube - hDtTNDVcTF4
If it doesn't work, i'm screwed cause i do not have a replace phone atm.
Following those steps will only mean that you won't brick it again... and anyway that is really outdated... When you've had enough of constant freezes then you will probably want to try a slim rom such as Slim Bean 4.2.2
I just purchased a n7000 from a guy on eBay for $350.00. It has the Ultimate rom installed in the screenshots. This means that it should be fine, right? I should receive it this week sometime. I bricked my i9100 back when the brick bug first appeared so I'm kind of worried about this.
Sent from my Nexus 4 using xda premium
Thanks for replies. I dunno what to expect. It is worrying, but probably i'll return it back cause is not worth the money if you put it this way "unusable".
He said to me to add a new sd card,,, i guess here is where he was just too honest. This confirms that there is actually a permanent damage to the hardware, especially the hefty 16 GB of memory.
My friend has the bug and he did the workaround , The phone freezes when you turn on bluetooth or wifi , And also the internal memory is low , but good luck with your's btw "restarting it from time to time" seems suspicious though
Sent from my GT-N7000 using xda app-developers app
KayKrate said:
My friend has the bug and he did the workaround , The phone freezes when you turn on bluetooth or wifi , And also the internal memory is low , but good luck with your's btw "restarting it from time to time" seems suspicious though
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Apparently that was a slight misleading. On itself doesn't restart. I got the phone right now. Is so huge even an elephant could use it.
Only freezes when i try write something thru usb cable. The ram is smaller, only 5 gb.
neier24 said:
Apparently that was a slight misleading. On itself doesn't restart. I got the phone right now. Is so huge even an elephant could use it.
Only freezes when i try write something thru usb cable. The ram is smaller, only 5 gb.
Click to expand...
Click to collapse
Really? Then it might be double-bricked and double "workarounded". Each time lossing about 3 GB...
When I close my eyes I see the grinning of this a--h-le who sold it for real money.
That sucks...
Now I want to see if is only a memory problem of the storage sd, or is as well as for the last 'bastion' of my phone, 2GB rom... cause then i can install slimbean like i've been adviced here.
neier24 said:
That sucks...
Click to expand...
Click to collapse
Why? You knew from the first day about the condition and bought it nevertheless.
ThaiDai said:
Why? You knew from the first day about the condition and bought it nevertheless.
Click to expand...
Click to collapse
First off, i'm in a bit of trouble right now. As you can guess, i can do something about it, cause beyond this is the morality of getting into a mess on someone's fault. Now that has to be decided, as long as is not mine.
This guy told me it is partially usable, add a card, try fix it yourself. At 190$ i expect to be better then a S1 or nexus s which might easly outmatch this phone. If is a matter of pride. Just keep it to yourself.
Either i give this guy a bad review as is a site as amazon, where user feedback is noted, or i return it back myself. Is not the holly grail, is just a phone.
He told me is not permanent damage.
LE: I got some good news and bad new:
I cannot add videos, it simply doesn't write. It doesn't freeze my phone anymore, this time i'm using samsung kies. Good news, i can write photos and songs.
I'm half way there in trusting this guy that with a sd card, the phone will work just okay in installing stuff.
On the other hand, i dunno if the internal storage is damaged; can i install jelly bean? or change the culprit kernel? or should i live with it as it is.
the seller has a no return policy. so ur actually screwed. you think the seller is a noob and that he didnt know about the fix. sometimes being too wise makes u feel and idiot in the end.
Sent from my GT-N7000 using xda app-developers app
Do you guys want to help, or keep ranting?
qazibasit learn some english.
How i change camera setting to save all its files on external microsd card?
neier24 said:
Do you guys want to help, or keep ranting?
qazibasit learn some english.
How i change camera setting to save all its files on external microsd card?
Click to expand...
Click to collapse
And now you are starting to get arrogant?
Even if I do not always follow qazis messages I do understand him very well - because Oxford english isn't a prerequisite here.
Members here can't help you: Why? Because you bought a brick device even when warned about it.
ThaiDai said:
And now you are starting to get arrogant?
Even if I do not always follow qazis messages I do understand him very well - because Oxford english isn't a prerequisite here.
Members here can't help you: Why? Because you bought a brick device even when warned about it.
Click to expand...
Click to collapse
How was his random ranting relevant to this topic?
So what do you think... flashing a new kernel and formating the sdcard do any good?
I may have a different term for bricking: When used in reference to consumer electronics, a "brick" describes an electronic device such as a smart phone, game console, router, or tablet computer that owing to a serious misconfiguration, corrupted firmware or a hardware problem, can no longer function. The term derives from the vaguely cuboid shape of many electronic devices (and their detachable power supplies) and the suggestion that the device can only function as a large, heavy object.
As far as i see, this device has stuff installed on it, and i can't figure how he did it.
recommend me a memory error checking app if u know, please!
Flash a safe kernel and flash a new ROM.. Try that and if all works good we´ll continue..
Didn't see this anywhere, so I thought I would try and hopefully save at least one person some time/frustration. I, like many people on this site own multiple devices and swap my Sprint service back and forth between them. I normally do this through Sprint.com. I just got my GS4 and spent hours testing what launcher would be the fastest with this SOC, and setting everything up exactly the way I wanted it.(I always keep things stock for the return period so I had no real way of making a backup) After I got everything the way I wanted, I activated this beauty...but upon doing this, I didn't see the fine print that the profile update triggers a factory data wipe.. **POOF** and all my app/prefs/etc. were gone. Needless to say, I was LIVID. I waited until I was calmed down to call customer care. The rep I spoke to advised that they changed it to require a factory data wipe when switching service online and you need to call customer care to attempt a manual IMEI/DEC/HEX swap.
glassjosh said:
Didn't see this anywhere, so I thought I would try and hopefully save at least one person some time/frustration. I, like many people on this site own multiple devices and swap my Sprint service back and forth between them. I normally do this through Sprint.com. I just got my GS4 and spent hours testing what launcher would be the fastest with this SOC, and setting everything up exactly the way I wanted it.(I always keep things stock for the return period so I had no real way of making a backup) After I got everything the way I wanted, I activated this beauty...but upon doing this, I didn't see the fine print that the profile update triggers a factory data wipe.. **POOF** and all my app/prefs/etc. were gone. Needless to say, I was LIVID. I waited until I was calmed down to call customer care. The rep I spoke to advised that they changed it to require a factory data wipe when switching service online and you need to call customer care to attempt a manual IMEI/DEC/HEX swap.
Click to expand...
Click to collapse
TiBu is your friend
rawintellect said:
TiBu is your friend
Click to expand...
Click to collapse
Word.
Sent from my SPH-L720 using xda app-developers app
glassjosh said:
Didn't see this anywhere, so I thought I would try and hopefully save at least one person some time/frustration. I, like many people on this site own multiple devices and swap my Sprint service back and forth between them. I normally do this through Sprint.com. I just got my GS4 and spent hours testing what launcher would be the fastest with this SOC, and setting everything up exactly the way I wanted it.(I always keep things stock for the return period so I had no real way of making a backup) After I got everything the way I wanted, I activated this beauty...but upon doing this, I didn't see the fine print that the profile update triggers a factory data wipe.. **POOF** and all my app/prefs/etc. were gone. Needless to say, I was LIVID. I waited until I was calmed down to call customer care. The rep I spoke to advised that they changed it to require a factory data wipe when switching service online and you need to call customer care to attempt a manual IMEI/DEC/HEX swap.
Click to expand...
Click to collapse
Had you already activated the device at least once before you attempted the online activation that resulted in the factory reset?
So I can confirm that this is indeed the desired behavior of chameleon. Whenever activation info is changed through HFA, then the device is now supposed to hard reset.
While this is certainly inconvenient if you didn't know it would happen (as us here in the store didn't know this was going to be the behavior going forward either), the reasoning behind it is sound: chameleon is put in place so that identical models of phones that are different sprint channels (sprint post paid, prepaid, boost, etc.) can run the same firmware; chameleon handles the bloatware payload for each channel. In other words, sprint no longer has to have different software packages for the same phone just because one gets sprint zone etc. and the other gets boost stuff etc.
Now, hopefully we get to a point to where chameleon is smart enough to recognize the current payload and decide whether a hard reset is necessary, but...baby steps I suppose.
EDIT: also, profile updates on their own don't require a reset. It's part of the whole HFA process that does it.
Sent from my SPH-L720 using xda premium
Nope, it was a new device I wanted to set up and play with on wifi before activating it. Now I just have to call CC and have them swap the devices manually.
rawintellect said:
TiBu is your friend
Click to expand...
Click to collapse
It's only your friend if you're rooted, I always keep stock FW for the return period of a device since you never know. I have always had mixed experiences with restoring app data as well.
glassjosh said:
It's only your friend if you're rooted, I always keep stock FW for the return period of a device since you never know. I have always had mixed experiences with restoring app data as well.
Click to expand...
Click to collapse
I've never had ONE bad experience with TiBu. Ever. If you know what you're doing it's fine. And why wouldn't you root? You can always unroot at any given time. And yes the counter can be reset.
The debate for rooting belongs elsewhere, I'm well aware you can reset counters, unroot, however, it's not worth the time when the risk of returning is high IMHO. You don't have to know what you're doing in TiBu, that's the beauty, but you still have a better chance of stability when using new app data, and it only takes 1 bad experience with some things..
glassjosh said:
The debate for rooting belongs elsewhere, I'm well aware you can reset counters, unroot, however, it's not worth the time when the risk of returning is high IMHO. You don't have to know what you're doing in TiBu, that's the beauty, but you still have a better chance of stability when using new app data, and it only takes 1 bad experience with some things..
Click to expand...
Click to collapse
LOL! You're not going to change my mind. I'm not going to change yours. I know from my own personal experience of MANY years of tinkering with android devices that you DO have to know what you're doing in TiBu or you're screwed. If you backup the wrong thing (say a system app from a different release of android) and restore it to an entirely new system you've just borked your device and are on a one way trip to bootloop city, population: YOU. And you'll have a full restore in your future.
As for "debating" on rooting? I'm not. Why even come on to XDA if you won't root? If you want stock apps stick to Google Play and sprint community forums. But don't come on to XDA and tell me or anyone else that rooting your phone is inferior to not rooting it. It just isn't. Period.
Stability is only as good as the person that coded it. That INCLUDES stock OEM ROMS or updates. I can count on two hands updates from manufacturers that have gone terribly wrong and been fixed by the devs in the XDA community LONG before they were fixed by the manufacturer. So your point about "new app data" is wrong as well.
And finally the "risk" isn't high. At all. Stop scaring folks. If your phone boots into the bootloader it's recoverable. Period. Even if it DOESN'T boot into the bootloader you can still recover it. I've had 8 HARD bricks. All of them recovered. Some even required EMMC_RECOVER to rewrite the bootloader. Don't know what that is? I'm not suprised. Let me google that for you. The WORST EVER required JTAG (again let me google that for you) to fix. But it WAS fixed.
I'm all done with this back and forth and I'll just place you on ignore and hope people see that you really have no clue what you're talking about.
Enjoy.
rawintellect said:
LOL! You're not going to change my mind. I'm not going to change yours. I know from my own personal experience of MANY years of tinkering with android devices that you DO have to know what you're doing in TiBu or you're screwed. If you backup the wrong thing (say a system app from a different release of android) and restore it to an entirely new system you've just borked your device and are on a one way trip to bootloop city, population: YOU. And you'll have a full restore in your future.
As for "debating" on rooting? I'm not. Why even come on to XDA if you won't root? If you want stock apps stick to Google Play and sprint community forums. But don't come on to XDA and tell me or anyone else that rooting your phone is inferior to not rooting it. It just isn't. Period.
Stability is only as good as the person that coded it. That INCLUDES stock OEM ROMS or updates. I can count on two hands updates from manufacturers that have gone terribly wrong and been fixed by the devs in the XDA community LONG before they were fixed by the manufacturer. So your point about "new app data" is wrong as well.
And finally the "risk" isn't high. At all. Stop scaring folks. If your phone boots into the bootloader it's recoverable. Period. Even if it DOESN'T boot into the bootloader you can still recover it. I've had 8 HARD bricks. All of them recovered. Some even required EMMC_RECOVER to rewrite the bootloader. Don't know what that is? I'm not suprised. Let me google that for you. The WORST EVER required JTAG (again let me google that for you) to fix. But it WAS fixed.
I'm all done with this back and forth and I'll just place you on ignore and hope people see that you really have no clue what you're talking about.
Enjoy.
Click to expand...
Click to collapse
I'm not trying to change anyone's mind, only warn others to possibly help someone out; which is the whole purpose of this site. I certainly don't have time to troll anyone's posts. Before you get more butt-hurt, read what I said. I know from my "MANY YEARS" of android tinkering and development, that you only need time to read, not to truly know what you're doing. Apparently we have different ideas of what that means. Never did I state that rooting was inferior, that's absurd. And how would you know the risk of me returning the phone in the return period? You obviously don't read or comprehend well. As stated before, I'm well familiar with the process for tweaking android devices, especially Samsung since I have 6 of them. I'm so super impressed with your vast knowledge though..
Wow. That escalated quickly for no reason. You ignores someone for having an opinion about not rooting a phone in the first seven days of owning it. I'm sure there are plenty of people on here that don't root in that first week, that includes me as one of them.
Sent from my SPH-L720 using xda premium
rawintellect said:
LOL! You're not going to change my mind. I'm not going to change yours. I know from my own personal experience of MANY years of tinkering with android devices that you DO have to know what you're doing in TiBu or you're screwed. If you backup the wrong thing (say a system app from a different release of android) and restore it to an entirely new system you've just borked your device and are on a one way trip to bootloop city, population: YOU. And you'll have a full restore in your future.
As for "debating" on rooting? I'm not. Why even come on to XDA if you won't root? If you want stock apps stick to Google Play and sprint community forums. But don't come on to XDA and tell me or anyone else that rooting your phone is inferior to not rooting it. It just isn't. Period.
Stability is only as good as the person that coded it. That INCLUDES stock OEM ROMS or updates. I can count on two hands updates from manufacturers that have gone terribly wrong and been fixed by the devs in the XDA community LONG before they were fixed by the manufacturer. So your point about "new app data" is wrong as well.
And finally the "risk" isn't high. At all. Stop scaring folks. If your phone boots into the bootloader it's recoverable. Period. Even if it DOESN'T boot into the bootloader you can still recover it. I've had 8 HARD bricks. All of them recovered. Some even required EMMC_RECOVER to rewrite the bootloader. Don't know what that is? I'm not suprised. Let me google that for you. The WORST EVER required JTAG (again let me google that for you) to fix. But it WAS fixed.
I'm all done with this back and forth and I'll just place you on ignore and hope people see that you really have no clue what you're talking about.
Enjoy.
Click to expand...
Click to collapse
Please don't feed the trolls...
Sent from my SPH-L900 using xda app-developers app
Hi All,
I'm about to change my Z to another.
Is it possible to restore an "old" nand backup to this new phone without any issue?
Thanks a lot
If the backup taken is of the same version of jelly bean and also the firmware,only then it can be restored without any probs..the other cases,well..I dunno about them..Cheers
Hit thanks if I helped u in any way.Sent from my Killer Xperia Z(C6602) using xda premium.
GeoSpaceKing said:
If the backup taken is of the same version of jelly bean and also the firmware,only then it can be restored without any probs..the other cases,well..I dunno about them..Cheers
Hit thanks if I helped u in any way.Sent from my Killer Xperia Z(C6602) using xda premium.
Click to expand...
Click to collapse
Why would Android version and ROM matter? I would be more worried about possibly restoring unique phone data like MAC addresses or IMEI. (Neither of which should happen on the Z anyway)
The imei and Mac addresses are unique for each device as far as I know..they don't change whatever we do..maybe we can put fake ones in their place but the original ones will still be the same..
Sent from my Killer Xperia Z(C6602) using xda premium.
GeoSpaceKing said:
The imei and Mac addresses are unique for each device as far as I know..they don't change whatever we do..maybe we can put fake ones in their place but the original ones will still be the same..
Sent from my Killer Xperia Z(C6602) using xda premium.
Click to expand...
Click to collapse
Say that to a Samsung phone... Honstly I used to take that for granted as well, until I soft-bricked my old SGS3's modem by wiping a partition which contained IMEI and MAC addresses (something that, in my opinion, shouldn't be possible on a production device).
Rekoil said:
Say that to a Samsung phone... Honstly I used to take that for granted as well, until I soft-bricked my old SGS3's modem by wiping a partition which contained IMEI and MAC addresses (something that, in my opinion, shouldn't be possible on a production device).
Click to expand...
Click to collapse
Woh..that is some serious mess..were u able to recover ur s3 back to life?where the hell did u delete those things from..I read somewhere that the device Mac and imei are related to the device's hardware..I'm not sure about that now cuz I read ur post lol
Sent from my Killer Xperia Z(C6602) using xda premium.
Such stuff should be in a read only memory... Or maybe this stuff is in the TA partition?
Yes they are unique to each phone. MAC is for the Ethernet (internet protocol layer) and IMEI is the phone unique identifier but don't know more about.
But if there are the same and the other isn't used, ( never) it can work. It will for internet at least.
"I know that my English isn't perfect, but I still hope it's comprehensible." Send over the cool Xperia Z
GeoSpaceKing said:
Woh..that is some serious mess..were u able to recover ur s3 back to life?where the hell did u delete those things from..I read somewhere that the device Mac and imei are related to the device's hardware..I'm not sure about that now cuz I read ur post lol
Sent from my Killer Xperia Z(C6602) using xda premium.
Click to expand...
Click to collapse
You are not supposed to be able to easily delete those things, like naphets8 said, yes, the XZs TA partition is roughly what I am talking about, on the S3 this partition is called the EFS partition. I figured, hey, why not wipe the phone properly and just execute "rm -rf /" before installing CyanogenMod... turns out that's a bad idea on a Samsung device, because this special partition, which shouldn't even have been mounted in the first place on a production device, is actually also writeable on a rooted device...
Yeah I did eventually get it semi-back-to-life, but I didn't care at that point because I was fed up with the lack of developer support on the International S3 and ended up just selling it for a low price to a friend (didn't feel right selling it to some random on the internet, even if I could have gotten more money, as I wanted the device to be near me so I could help take care of it when it has its moments... as only I really know exactly what is going on with that particular device seeing as I constructed the workaround for the missing data).
For the record, keeping this kind of stuff (IMEI, MAC addresses, other unique calibration data) in a mounted file system is wrong. You keep it on a NAND, yes, but not the NAND that stores the operating system, and you certainly do not mount it through the kernel, you access it through other means like the way NVRAM is accessed for example. How a huge technology company like Samsung (arguably one of the biggest electronics manufacturers in the world) could get this wrong on a flagship device like the S3 I will never understand, as there are literally thousands of engineers on a project like that who should have put a stop to it.
But yeah, depending on how the recovery partition makes backups, the EFS partition could have ended up in one of them, at least if you used "adb backup" on the S3. Then transferring that backup to another S3 could have potentially been fatal depending on if it was the same model or even how it is set up.
Moral of the story: No, I cannot recommend low-level backups like those produced by CMW-like recoveries to be transferred between devices even of the same model, unless you know exactly what you are doing or at least check it up with someone who does first.
Rekoil said:
You are not supposed to be able to easily delete those things, like naphets8 said, yes, the XZs TA partition is roughly what I am talking about, on the S3 this partition is called the EFS partition. I figured, hey, why not wipe the phone properly and just execute "rm -rf /" before installing CyanogenMod... turns out that's a bad idea on a Samsung device, because this special partition, which shouldn't even have been mounted in the first place on a production device, is actually also writeable on a rooted device...
Yeah I did eventually get it semi-back-to-life, but I didn't care at that point because I was fed up with the lack of developer support on the International S3 and ended up just selling it for a low price to a friend (didn't feel right selling it to some random on the internet, even if I could have gotten more money, as I wanted the device to be near me so I could help take care of it when it has its moments... as only I really know exactly what is going on with that particular device seeing as I constructed the workaround for the missing data).
For the record, keeping this kind of stuff (IMEI, MAC addresses, other unique calibration data) in a mounted file system is wrong. You keep it on a NAND, yes, but not the NAND that stores the operating system, and you certainly do not mount it through the kernel, you access it through other means like the way NVRAM is accessed for example. How a huge technology company like Samsung (arguably one of the biggest electronics manufacturers in the world) could get this wrong on a flagship device like the S3 I will never understand, as there are literally thousands of engineers on a project like that who should have put a stop to it.
But yeah, depending on how the recovery partition makes backups, the EFS partition could have ended up in one of them, at least if you used "adb backup" on the S3. Then transferring that backup to another S3 could have potentially been fatal depending on if it was the same model or even how it is set up.
Moral of the story: No, I cannot recommend low-level backups like those produced by CMW-like recoveries to be transferred between devices even of the same model, unless you know exactly what you are doing or at least check it up with someone who does first.
Click to expand...
Click to collapse
U sound like a person who really has an attachment to your tech.. Nice moral too... And about Samsung being cheeky is only maybe cuz they WANT people to meddle with the really dangerous stuff in their devices,no offence..I like Samsung products too...anyways this was really an intense detail u have given,thumbs up for that :thumbup:
Sent from my Killer Xperia Z(C6602) using xda premium.
GeoSpaceKing said:
U sound like a person who really has an attachment to your tech.. Nice moral too... And about Samsung being cheeky is only maybe cuz they WANT people to meddle with the really dangerous stuff in their devices,no offence..I like Samsung products too...anyways this was really an intense detail u have given,thumbs up for that :thumbup:
Sent from my Killer Xperia Z(C6602) using xda premium.
Click to expand...
Click to collapse
There's allowing developers proper access to the device, and then there's just being reckless (which is what I consider Samsungs solution to be). Kernel, recovery, data and system (and associated partitions like lib) should be accessible by developers. But unrestricted access (as in no signature checks on what I am flashing) to device config, bootloaders, NFC and radio partitions? That is just reckless behaviour. Honestly, on the S3 there was nothing stopping me from flashing a picture of a cat to my devices bootloader... and no I don't mean a modded bootloader with a picture of a cat instead of the Samsung logo, I mean a JPG... how do you think the device would have reacted to that? I would have bricked it.
Barring obscure projects like dual-booting (which can be done in userspace or kernel anyway, even if it is easier from a modded bootloader) there is really no need to give people that kind of access, and all that happens is that some idiot goes and ruins his device when it is completely unnecessary.
ROM manager creator and CM developer @Koush said it well when speaking about S-OFF on HTC devices. While on the subject, I'd like to credit HTC for finally getting this right on the One. There, mission critical partitions are locked down (signed images can be written freely, but not unsigned), and kernel, recovery, data and system partitions are accessible to developers through the HTCdev program.
Hi Guys,
A friend of a friend has the Samsung Note 1 (N7000) and they said it crashed the other day, it was apparently attempting to do an OTA upgrade. From what I understand, it didnt boot/come back on... Which makes me think its the eMMC bug.
She took it to her network (Vodafone) and they blamed it on the phone having to many Apps, and that her son (she doesnt have a son) had attempted to Jailbreak it... (which I told her, the shop was using the wrong terminology, so clearly the shop didnt know what they were talking about. However, she said she only has 633Mb left on her main storage.
https://fbcdn-sphotos-d-a.akamaihd....720x720/998536_4343286319716_1946491477_n.jpg
https://fbcdn-sphotos-f-a.akamaihd....20x720/1005339_4343299680050_2090572114_n.jpg
She said the shop just removed some Apps, and it suddenly started working again. However when she runs a couple of Apps now, the screen goes blank....
Does those pics sound about for a normal used N7000... Or does it look like there is storage space missing, due to a corrupt eMMC chip?
Thanks, Lister
Lister Of Smeg said:
Hi Guys,
A friend of a friend has the Samsung Note 1 (N7000) and they said it crashed the other day, it was apparently attempting to do an OTA upgrade. From what I understand, it didnt boot/come back on... Which makes me think its the eMMC bug.
She took it to her network (Vodafone) and they blamed it on the phone having to many Apps, and that her son (she doesnt have a son) had attempted to Jailbreak it... (which I told her, the shop was using the wrong terminology, so clearly the shop didnt know what they were talking about. However, she said she only has 633Mb left on her main storage.
https://fbcdn-sphotos-d-a.akamaihd....720x720/998536_4343286319716_1946491477_n.jpg
https://fbcdn-sphotos-f-a.akamaihd....20x720/1005339_4343299680050_2090572114_n.jpg
She said the shop just removed some Apps, and it suddenly started working again. However when she runs a couple of Apps now, the screen goes blank....
Does those pics sound about for a normal used N7000... Or does it look like there is storage space missing, due to a corrupt eMMC chip?
Thanks, Lister
Click to expand...
Click to collapse
does not seem bricked. Flash philz kernel, do all wipes and flash stock rom using pc odin. For guide and stock rom :
http://forum.xda-developers.com/showthread.php?t=1424997
for philz kernel:
http://forum.xda-developers.com/showthread.php?t=1901191
Whats wrong with 632mb on root folder? I got less than that. Apk do takes up space.
Sent from my GT-N7000
Hi treacherous_hawk,
Thanks for your prompt answer, and re-assuring me... I shall pass this news onto my friend (well, as said earlier... She's a friend of a friend, dont really know her other than online.. lol). But basically the way she described her initial fault with phone, sounded like she bricked due to OTA update. She then took it to the shops, and they told her she had been Jailbreaking (that only happens on iPhones, surely?? lol) plus she wouldnt know how to do that anyway... They blamed it all onto her, and said she had to many Apps installed... lol
Anyway, she gets it back... and I ask about it... (as I am planning to buy this off her when the contract runs out). And she tells me they just uninstalled some Apps and it started working again. However she told me it was a 16Gb Note, and that she only has 633Mb left of available space, and that she has only used 1.4Gb..... So I wondered where the other 14Gb went....?? She tells me she has a SD Card in it too... And so not having seen or used a Note yet, it sounded a bit odd why she only had 633Mb left....??
I'd love to get Philz kernel on it, purely so I know it will always be safe.. But never met the lady yet, plus the phone isnt mine yet.. lol
I really wonna get and use this phone, due to the size and spec of it... But just been reading some more posts, and now Im all scared of bricking, locking, or yellow triangle'ing the darn thing...
My ZTE Blade is old, and slow... But you could chuck anything at it, without fear of bricking it...
Hi Devll,
I've never seen or used a N7000 yet... However when she told me she only had 633Mb left, summit didnt sound right.. As I was expecting to see more GB's left. I didnt know the N7000 kinda partitions storage off for ROM and data. Whilst my ZTE Blade does use partitions too, what you see is what you get... ie: You get the full amount as advertised on the box... (which is a mere 240Mb... pitiful...) So when she said she had only used 1.4Gb, and only has 633Mb left... I wondered where the heck the other GB's had gone too...?? lol
Re: the Note..... I am now super worried and now debating whether I should actually attempt to purchase it off her...
1) Its from Vodafone UK, so dont know whether its SIM locked or not? I've heard all contract phones from Vodafone UK are factory UNlocked, but dont know for certain????
2) I'm ok at flashing the Philz Kernel... that bit doesnt scare me... However its the ROMs that do.
3) When I get it, I want to upgrade the rom to the latest Android (4.2.2, as like my ZTE Blade) and will no doubt go with PAC Rom or if they do a RootBox.... However I am hoping these are eMMC safe once flashed, as in there is no way/chance of me bricking it under that OS.
4) If I do get that PAC Rom on there, will my Yellow Triangle appear as its non stock. And heard that Triangle away only works on ICS??
So I'm starting to think, or look else where at a safer phone... or am I over scaring myself as to how faulty these are??
Thanks, Lister
Don't get paranoid mate its very easy to root and install custom rom on Note provided you read before doing it. Read the stickies in the development and other forum, read carefully the instructions given in the topic of the rom you are planning to install and you will be safe.
I too was worried a bit when I got my Note but trust me those who can read won't face any trouble but those who can't.... well they can always pray
Best Regards
Sent from my GT-N7000 using xda app-developers app
Lister Of Smeg said:
Hi treacherous_hawk,
Thanks for your prompt answer, and re-assuring me... I shall pass this news onto my friend (well, as said earlier... She's a friend of a friend, dont really know her other than online.. lol). But basically the way she described her initial fault with phone, sounded like she bricked due to OTA update. She then took it to the shops, and they told her she had been Jailbreaking (that only happens on iPhones, surely?? lol) plus she wouldnt know how to do that anyway... They blamed it all onto her, and said she had to many Apps installed... lol
Anyway, she gets it back... and I ask about it... (as I am planning to buy this off her when the contract runs out). And she tells me they just uninstalled some Apps and it started working again. However she told me it was a 16Gb Note, and that she only has 633Mb left of available space, and that she has only used 1.4Gb..... So I wondered where the other 14Gb went....?? She tells me she has a SD Card in it too... And so not having seen or used a Note yet, it sounded a bit odd why she only had 633Mb left....??
I'd love to get Philz kernel on it, purely so I know it will always be safe.. But never met the lady yet, plus the phone isnt mine yet.. lol
I really wonna get and use this phone, due to the size and spec of it... But just been reading some more posts, and now Im all scared of bricking, locking, or yellow triangle'ing the darn thing...
My ZTE Blade is old, and slow... But you could chuck anything at it, without fear of bricking it...
Hi Devll,
I've never seen or used a N7000 yet... However when she told me she only had 633Mb left, summit didnt sound right.. As I was expecting to see more GB's left. I didnt know the N7000 kinda partitions storage off for ROM and data. Whilst my ZTE Blade does use partitions too, what you see is what you get... ie: You get the full amount as advertised on the box... (which is a mere 240Mb... pitiful...) So when she said she had only used 1.4Gb, and only has 633Mb left... I wondered where the heck the other GB's had gone too...?? lol
Re: the Note..... I am now super worried and now debating whether I should actually attempt to purchase it off her...
1) Its from Vodafone UK, so dont know whether its SIM locked or not? I've heard all contract phones from Vodafone UK are factory UNlocked, but dont know for certain????
2) I'm ok at flashing the Philz Kernel... that bit doesnt scare me... However its the ROMs that do.
3) When I get it, I want to upgrade the rom to the latest Android (4.2.2, as like my ZTE Blade) and will no doubt go with PAC Rom or if they do a RootBox.... However I am hoping these are eMMC safe once flashed, as in there is no way/chance of me bricking it under that OS.
4) If I do get that PAC Rom on there, will my Yellow Triangle appear as its non stock. And heard that Triangle away only works on ICS??
So I'm starting to think, or look else where at a safer phone... or am I over scaring myself as to how faulty these are??
Thanks, Lister
Click to expand...
Click to collapse
Dont worry about the availabilty of space... Might be some virus that creates shortcuts and hides the original folders... try exploring the drive with winrar... It will show all the folders that are hidden too
Yelloe triangle is nothing to worry about... There are many methoda to bypass thebyellow triangle and even if u get one u can easily remove it
What is it? And for that matter, is it dangerous to mess with? I don't mess with it, but these are questions for knowledge mostly. What does it do and what is stored in there? If it got corrupted, is that fixable at all? Thanks! Might be a noob question, but I've always modded my stuff without ever touching it or even knowing what it is! I always choose to back it up with my TWRP backups an then restore the EFS with my backups.
As far as I know EFS partition contains some vital info of your phone's IMEI, serial number, radio info and other similar information. It's good to have a backup of your EFS partition all the time, because if it becomes corrupted you can quite easily render your phone useless (at least cell part of it). I learned my lesson with my old Nexus S ...
If it gets corrupted, and you don't have a backup then you lose your IMEI number and with that the ability to connect to any cellular network. So yes, back it up and keep it in a secure place.
As above.
Back it up once, forget about it. I've never seen any EFS related issues on the Nexus 5 or 6. Samsung on the other hand, every day,
EFS usually only get wiped when your doing something in the grey area... Such as *ahem* swapping IMEI's and other device identifiers to circumvent carrier/network blacklisted devices which we don't discuss on XDA, buy is common practice in the local phone shops you may find on craigslist. If you're good now and plan to stay that way, leave it alone. Backing up is a good practice when flashing ROMS, radios, system IMG., etc. You never know what may go wrong.
---------- Post added at 11:02 AM ---------- Previous post was at 10:53 AM ----------
Really, the loss of an IMEI isn't even the worst scenario. It's the authentication certificates that are almost impossible to replace on a GSM network, and on CDMA it's the AAA password and HA KEY that are unique to each device. Anyways, point being, back up--and store on external drive somewhere
Alright! Thanks guys for all your answers! So in short, if I were to lose that data and not have a backup, the device is fubar? No cellular data ever again?
Sent from my Nexus 6
No cellular anything.
Yeah, I owned mine that I broke. I was trying to get that galaxy nexus from Sprint flashed to pageplus/Verizon. No backup=no data for me. I never tried the donor thing, but I learned how to do all of it right here on XDA. @autoprime had a great thread about it back in the day. That phone is still awesome running OMNI ROM, but with a crappy camera... I like this nexus 6 only somewhat better, actually. Gnex was one of the greatest nexus devices ever, in part, I think at least, because Samsung was the manufacturer. Great model... Wish they made this nexus or the newest 6p, but I digress.
jbeezley said:
Yeah, I owned mine that I broke. I was trying to get that galaxy nexus from Sprint flashed to pageplus/Verizon. No backup=no data for me. I never tried the donor thing, but I learned how to do all of it right here on XDA. @autoprime had a great thread about it back in the day. That phone is still awesome running OMNI ROM, but with a crappy camera... I like this nexus 6 only somewhat better, actually. Gnex was one of the greatest nexus devices ever, in part, I think at least, because Samsung was the manufacturer. Great model... Wish they made this nexus or the newest 6p, but I digress.
Click to expand...
Click to collapse
I never had the Galaxy Nexus, did Samsung do a good job with it? My personal preference here has to be this Motorola Nexus 6! Motorola made an impressive build in my opinion and the device is sturdy, big, and all around amazing to me! I could say that they should have taken more consideration in the speakers, they work great and provide superb sound! But that hissing crackling sound when the battery is low........ Only complaint!
This Huawei 6P on the other hand............... Hahahaha
Sent from my Nexus 6
Ok guys. Lets clearify something real fast. The reason that XDA frowns on editing the IMEI is due to the fact that it is illegal in many countries to mess with it at all.
With that being said. The EFS partition should always be backed up when you can. Samsung and other OEM have a habit of making the partition to be erasible and once erased without a backup you are hosed.
zelendel said:
Ok guys. Lets clearify something real fast. The reason that XDA frowns on editing the IMEI is due to the fact that it is illegal in many countries to mess with it at all.
With that being said. The EFS partition should always be backed up when you can. Samsung and other OEM have a habit of making the partition to be erasible and once erased without a backup you are hosed.
Click to expand...
Click to collapse
What would be the best way to back it up? With TWRP or is there a more ideal solution than that? And I own this device, I'm definitely not asking about illegal stuff in here. Lol
Sent from my Nexus 6
H4X0R46 said:
What would be the best way to back it up? With TWRP or is there a more ideal solution than that? And I own this device, I'm definitely not asking about illegal stuff in here. Lol
Sent from my Nexus 6
Click to expand...
Click to collapse
I was say using an ADB command to back it up to your pc.
As for owning it that really doesn't apply. Even the owner is not legally allowed to mess with the IMEI numbers.
zelendel said:
I was say using an ADB command to back it up to your pc.
As for owning it that really doesn't apply. Even the owner is not legally allowed to mess with the IMEI numbers.
Click to expand...
Click to collapse
What would be the command to use? I'm not great with adb. I have used it but I'm not great with it lol
Sent from my Nexus 6
If you are most comfortable with TWRP, just use that to create the backup. Connect to your computer in MTP, find it in the TWRP folder and copy the file over to your computer.
---------- Post added at 02:52 AM ---------- Previous post was at 02:47 AM ----------
And yes, the galaxy nexus was a fantastic build that really helped to put the nexus phones on the map. First phone to use NFC, IIRC. The device performance overall was to notch, especially with custom ROMS. Had a lot of features that made it an exceptional phone for the starting price. Only true downfall of the device was a crappy camera.
H4X0R46 said:
What would be the command to use? I'm not great with adb. I have used it but I'm not great with it lol
Sent from my Nexus 6
Click to expand...
Click to collapse
No worries, To be honest I am not sure of the mounting points for this device or where the efs is stored on this device. If twrp works as stated then I would just use that and copy it some where safe.
zelendel said:
No worries, To be honest I am not sure of the mounting points for this device or where the efs is stored on this device. If twrp works as stated then I would just use that and copy it some where safe.
Click to expand...
Click to collapse
Thanks guys! You all are awesome! Always helpful here on XDA!
Sent from my Nexus 6