i have intex cloud y3 with serial no as ABCDEF123456789 I WANT to get serial no back i have tried changing init.rc deafault.prop and even init.usb.rc in boot.img but no success could you please help me out changing my serial no. i think it is is in init.c but dont know how to edit . i even use sp imei flash tool to flash serial no.
IMEI Chaning is against the Law and is prohibited per XDA rules.
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
Thread closed.
Related
Is anybody working on an iMEI changer?
What does jockyw's security unlocker mean in regards to this?
Will the security unlock plus a radio dumper allow this? (I assume the radio dumper would dump the portions of radio memory not updated during a radio firmware update)
I've been reading and reading, and can't answer these questions...
why do you need one? these tools just encourage phones to be stolen.
Remember in most parts of the world it's illegal to change the IMEI of the phone.
The-Kevster said:
Remember in most parts of the world it's illegal to change the IMEI of the phone.
Click to expand...
Click to collapse
Not all.
I think I'll refer you to this thread: http://forum.xda-developers.com/showthread.php?t=274860
There are legitimate reasons for wanting to do so.
Okay, so I was wondering, if we flash a rom, and the service provider's name on the phone changes, is that a problem? will they be able to trace back to me and see that I have modified my phone? Originally I was using Fido, but afterwords it says Rogers. Although fido does "borrow" Rogers network, would it be a problem?
Btw i apologize in advance if i posted int he wrong area because this is my first post and im new to everything! thx
it wont affect buddy... since yur network changes name, dat means its from tha network!!!
#Dont panic brov..... yu dont have any problem!
Your provider can't read your phone infos. Unless he has some programs instaled on your phone that would do that form them.
Just make sure you have a way to revert back to stock rom, in case you need to warranty your phone. Rooting will automatically void the warranty.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Not perfectly related but the knowledge of the "hidden" Carrier IQ software should be interesting if you own a smartphone. http://en.wikipedia.org/wiki/Carrier_IQ
A carrier can read your phone info, and they do when you call in with a problem. The information they read is from your build.prop, if I remember correctly, so you could just change that file to reflect what looks like stock. Don't make any changes without first doing a backup and knowing what you're doing. If you don't know what to change, don't mess with it.
Every thread to do with rooting says that rooting voids your warranty. Your warranty is done unless you completely revert to stock and unroot. Your service is not affected. They cannot kick you off for rooting your phone, but they can deny you (warranty) service on the rooted phone.
Supersonic Evo 4G | MIUI | Tapatalk
hi.
I have root note 3 and flag knox varanty 0x1 now I have problem becous I found in my device some factory errors like crash nfc is not work for me. If I tray send in such a state of the phone warranty I lose it (service not respect devices who have knox 0x1).
And now my question is how to brick this device?
cookie^Monster said:
hi.
I have root note 3 and flag knox varanty 0x1 now I have problem becous I found in my device some factory errors like crash nfc is not work for me. If I tray send in such a state of the phone warranty I lose it (service not respect devices who have knox 0x1).
And now my question is how to brick this device?
Click to expand...
Click to collapse
Doing this is obviously highly illegal as you are purposely destroying your product to fraudulently claim on your warranty. If you read around enough you will find out how to do it. I'm afraid I won't tell you how to do so.
edit: also this should have been posted here. But I'd expect this thread to be closed as it is technically breaking the rules.
Mod Edit
Seriously?
This site is called XDA DEVELOPERS
Do you really think that asking how to destroy something is part of that?
Thread closed
malybru
Forum Moderator
we talk about bricked phones .
there will be a no. of people who brick their phones today.
this mainly happens due to wrong bootloader or preloader in mtk.
my question is-
* Why can't we write boatloader after bricking by any method - if i am right manufacturers of phone parts(board or processors) don't write bootloader files, mobile phones companies do it after assembling phones . so there may be a way of writing it again as if they can do it ,why can't we?
they cannot be better than a senior developer(ofcourse i am not talking about me).
gursewak.10 said:
we talk about bricked phones .
there will be a no. of people who brick their phones today.
this mainly happens due to wrong bootloader or preloader in mtk.
my question is-
* Why can't we write boatloader after bricking by any method - if i am right manufacturers of phone parts(board or processors) don't write bootloader files, mobile phones companies do it after assembling phones . so there may be a way of writing it again as if they can do it ,why can't we?
they cannot be better than a senior developer(ofcourse i am not talking about me).
Click to expand...
Click to collapse
Its possible to repair bricked phones. All you need is a e.g. a RIFFBOX for JTAG repair
for nearly every device there are diy to unbrick the phone
It depends on the design. When bootloader allows you to flash important parts of system (e.g., kernel image and /system partition), you can't completely brick you phone by flashing anything but the bootloader. That is, when you "brick" you the phone by flashing something (except the bootloader), you can easily unbrick it by flashing the correct firmware.
(A notable exception is flashing a software that actually destroys the hardware. But this is rare, I think.)
I am not sure if there is a bootloader that does not allow flashing the important parts of the system. I am sure my phone allows it (I flashed bad boot.img many times and recovered then ) and my tablet probably also allows it.
When you, however, do some mistake when flashing a bootloader (either you flash a bad binary or the flashing process is interrupted by a bad cable or power outage in a critical moment), it is hard to recover from it. (As noted, you can use JTAG or something similar, but you can't usually boot the bootloader.) There might be some "dual-bootloader" phones, like there are some dual-BIOS computers, but I am not aware of them. Such phone would have two distinct areas for bootloader. One of them is used, the other is for flashing a new bootloader. When you successfully flash the new bootloader, these areas are effectively swapped. While this would prevent you from some type of issues (e.g. power outage), it does not necessarily prevent you from some others (e.g. accidental flashing a bad file).
gursewak.10 said:
we talk about bricked phones .
there will be a no. of people who brick their phones today.
this mainly happens due to wrong bootloader or preloader in mtk.
my question is-
* Why can't we write boatloader after bricking by any method - if i am right manufacturers of phone parts(board or processors) don't write bootloader files, mobile phones companies do it after assembling phones . so there may be a way of writing it again as if they can do it ,why can't we?
they cannot be better than a senior developer(ofcourse i am not talking about me).
Click to expand...
Click to collapse
Bootloaders are flashed through an IC writer like JTAGGING (RIFFBOX maybe?) (I have seen IC's being written fiest time, like BIOS etc.) ... Thy are not easily erasable (I tried it! Full format through sp flash tool 3 times didn't erase my preloader/bootloader), which if corrupted has to be rewritten by JTAG tool because it is inaccessible .. A senior member or any member can write a bootloader but it needs correct tools. Which vendor has. I have seen this writing process very closely. I have seen hard bricked phones bring repaired (my dad is an electronic engg and has tools at home. I have written my bootloader (OF LGE975) myself after a hard brick it is so easy if you have tools
Instead of thanking me by posting, HIT Thanks if you like my post or if I helped you in any way!
-------------------------------------------
My work:
[TOOL]Kernel/Boot.img (un)packer
My S8+ sm-g955FD got Custom Binary Lock by FRP how I do fix this please?
-edit-
Also it seems that my mistake was that I turned off the OEM unlock afterward... I guess that's the problem...
you need to flash the stock ORIGINAL Samsung firmware!
All datat will be lost!
Flash AP, BL, CP and CSC_ don´t flash with the HOME_CSC.
after that you can enable OEM unlock and root or whatever you want.
BUT NEVER disable OEM Unlock if you are not on an unmodified, unrooted, stock Samsung firmware and recovery!
maik005 said:
you need to flash the stock ORIGINAL Samsung firmware!
All datat will be lost!
Flash AP, BL, CP and CSC_ don´t flash with the HOME_CSC.
after that you can enable OEM unlock and root or whatever you want.
BUT NEVER disable OEM Unlock if you are not on an unmodified, unrooted, stock Samsung firmware and recovery!
Click to expand...
Click to collapse
Thank you for your reply. I only tried Flashing with HOME_CSC from the zip and never tried the rest.
I took my phone to unofficial repair shop and paid to have the phone fixed. I will remember this if the problem occurred again.
You said you disabled OEM Unlock.
THAT was you problem.
If you do that without having the stock orignal Samsung firmware + recovery then your phone wont boot anymore.
The only solution to fix this would be to reflash the full firmware.
AP, BL, CP, CSC.
If you still have your box or know your serial number. Your can plug it into smart switch and select emergency recovery. It will restore the firmware and get you functional again.
I did the exact same thing, i disabled the oem unlock after i rooted, and ended up bricked after several failed odin firmware flashes trying to get it back, i could no longer get into download mode.
sakohunter said:
If you still have your box or know your serial number. Your can plug it into smart switch and select emergency recovery. It will restore the firmware and get you functional again.
I did the exact same thing, i disabled the oem unlock after i rooted, and ended up bricked after several failed odin firmware flashes trying to get it back, i could no longer get into download mode.
Click to expand...
Click to collapse
I tried that but I didn't know how to start and what to put in where.
In the Emergency Software Recovery and Initialization screen, there are two tabs Emergency Software Recovery and Device Initialization. Which tab did you put the serial number in?
- The Emergency Software Recovery asked for Recovery Code from previous PC.
- The Device Initialization tab for Model Name.
kefrayba said:
I tried that but I didn't know how to start and what to put in where.
In the Emergency Software Recovery and Initialization screen, there are two tabs Emergency Software Recovery and Device Initialization. Which tab did you put the serial number in?
- The Emergency Software Recovery asked for Recovery Code from previous PC.
- The Device Initialization tab for Model Name.
Click to expand...
Click to collapse
Device initialization. Enter model name and s/n
sakohunter said:
Device initialization. Enter model name and s/n
Click to expand...
Click to collapse
And by recovery mode it seems to mean the Download mode right? The screen that you also do to use Odin.
Yes you need capital letters in the model or it wont recognize lol.
Mine couldn't boot into download mode. I bricked it. So I don't think it's necessary but I could be wrong. As long as it recognizes your device after you enter the s/n you should be good to procede.
sakohunter said:
Yes you need capital letters in the model or it wont recognize lol.
Mine couldn't boot into download mode. I bricked it. So I don't think it's necessary but I could be wrong. As long as it recognizes your device after you enter the s/n you should be good to procede.
Click to expand...
Click to collapse
Aha. It looks like it. Mine is currently working and I am too scared to try again for now. With these safety net I think I will try again in a few weeks. So Thank You for info.
The issue with small letters aside, the Smart Switch software is quite a decent backup/restore software.
Thread cleaned up.
Lucky patcher is considered as Warez and discussion related to Warez is strictly prohibited here at XDA.
The Forum Rulesforum.xda-developers.com/announcement.php?a=81 clearly state
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
Click to expand...
Click to collapse
I'll be keeping an eye on this thread so please don't discuss about warez any further.
Regards
Vatsal,
Forum Moderator.
Vatsal said:
Thread cleaned up.
Lucky patcher is considered as Warez and discussion related to Warez is strictly prohibited here at XDA.
The Forum Rulesforum.xda-developers.com/announcement.php?a=81 clearly state
I'll be keeping an eye on this thread so please don't discuss about warez any further.
Regards
Vatsal,
Forum Moderator.
Click to expand...
Click to collapse
I was about to type the reply to that. Thank you mod for the cleaned up. If there are any further discussion, it will most likely be about how to fix the FRP lock from unchecking OEM Unlock.