hey all
i found a galaxy s2 and i want to wipe it and use it as attempt's to find owner have failed here here is my problem
screen lock is enabled i can not remove it at all i have tried Full Flash via odin cwm firmwares a cmw backup of an other gs2 kernel flash nothing works
i flash phone and it lets me go through the setup .. the phone becomes unlocked but i cannot factory restore (to remove pin )as pin is required the and same gos
's for removing screenlock .. ive tried bricking the phone and recovering still no good ive searched for weeks for an answer and i cant find one
the phone is an Australia telstra branded gt-i9100t ... as far as firmware go's it have been flashed so many times iam not sure whats on it lol
if you need any more info let me know what u need n ill get it
pleas help
kjrol0 said:
i have tried Full Flash via odin cwm firmwares a cmw backup of an other gs2 kernel flash nothing works
Click to expand...
Click to collapse
While i've never been in this situation its hard to believe that flashing a new firmware won't remove the pin, did you do a full wipe/factory reset in recovery?
yes i have same thing ... phone set up then as soon as the screen turns off ...locked its really annoying
Try flashing the stock kernel and rom for i9100T from then on i believe u can root + cwm all in DL mode / odin
but it is very strange, if you've successfully wiped cache, wiped user data, all pw and pin should've been removed.. especially if u flash a new rom..
i would have thought so myself but for some reason apparently not i mean what other options do i have ..none really swap stickers n send it a way ... lol i mean what would they do .. nothing we cant its really starting to frustrate me ... like i installed gs1 firmware to brick it than re flashed it still nothing .. its bull
The pin is stored in the efs iirc... So wiping data won't help...
Did you try to flash cm, as it stores pin in regular place?
dogiefix
ok so i went thru the setup n had the phone temp unlocked so used Hc-kTool to backup efs file ok than u used an other gs2 efs back up to restore it ok re boot ..then boom unlocked ... both imei codes are different for som reason but i can make calls on both so pfft
however my imei code is 004990106.ect i think that is the imei code that needs repairing but i can fix that lol
my phone had a pin lock,the previous owner didnt tell the second hand store owner,so he wouldnt sell it till he re flashed the firmware to check its components etc, i could tell he did as it had odin after download mode, or is that normal?
Related
Hi all
Ok Ive just had my phone repaired by vodafone as the motherboard was dead and it came back with stock rom so i straight away set about rooting it but ive had multiple problems.
No matter how many roms i put on it with stock different kernels, super wipe, mega wipe and now even back to vodafones stock rom it keeps crashing and rebooting
I didnt run it long enough when it came back from repair so i dont know if it did it before root, does anyone think this is a issue before i started to root or something i've done?
Also now ive put stock rom on it when i try to do anthing that requires root access it says its not rooted and there is no little orange ! in the corner when booting up, so if i send this back to vodafone can they tell from this that ive attempted rooting etc, is there anyway for them to tell?
Thanks for your helps
not if you se the triangle away app in the playstore to reset your binary counter
Its not so simple as just TA.
Your status is modified and requires run TA flash stock rom then factory reset then check status in download mode and about phone in settings .
jje
ok so i've flashed the stock romj then do a factory reset in options in android? when do i do TA? also doesnt TA need root privledges? As its showing as not rooted?
Thanks
So is the process re root, run ta then reflash stock rom and factory reset?
Hey guys!
So once again I find my self asking for help.
So my phone decided to forget it's IMEI so I started following THIS guide.
The guide asked me to return to stock to somehow get the IMEI back.... so I followed THIS guide.
The problem is that after I flashed the phone I got stuck in the "Samsung Galaxy SII I9100" screen (where one gets the yellow triangle)
SO I thought to myself , meh it's a boot loop....so I followed some steps that had previously saved me.
But ever since the first flash I've not been able to access ANY sort of recovery, be it CWM or the normal android one.
I have access to download mode but that's it really....
Please help!
If you've got no recovery & the only option you've got is download mode, flash a stock rom. Then do a factory reset if you need to/assuming you get recovery back.
Then you can restore a backup/re-root your phone/flash whatever kernel or rom you want.
MistahBungle said:
If you've got no recovery & the only option you've got is download mode, flash a stock rom. Then do a factory reset if you need to/assuming you get recovery back.
Then you can restore a backup/re-root your phone/flash whatever kernel or rom you want.
Click to expand...
Click to collapse
Thank you for your quick reply.
Here's the thing. I got the stock rom from here and it's the first thing I flashed as a kernel yet it got stuck in the first screen.
I doubt i made a mistake here (because I checked with my phone´s "about" ) but Maybe I got the wrong version? (would it stop working if so?) .
Get one for your country/carrier from Samfirmware & try that (Be careful if it's 4.0.4 & don't do a wipe until after you've flashed a 'safe' kernel).
Success! I got recovery mode.....
(used Cf Root)
Now how do I go to stock?
If you've got CWM, try flashing whatever kernel you were using before you started having problems (You haven't been using Rom Manager by chance, have you ?). If you still don't have any joy, try flashing whatever rom you were using in CWM.
If we're talking stock recovery but the phone still won't boot normally, still flash a stock rom in Odin.
Nope, no ROM manager.... I had what seemed like a stock ROM , just with a different baseband to work in the UK (it's a mexican phone).
Anyways i'm back to square one..... I tried flashing the stock kernel that I looked for in Samfirmware (the mexican, just in case...) and it's still stuck in boot loop... and again I have no access to recovery...... tried flashing CF to no avail....
argh <.<
You need to try flashing the entire stock rom in that case.
MistahBungle said:
You need to try flashing the entire stock rom in that case.
Click to expand...
Click to collapse
So it will be the same? or is there a different place to get the ENTIRE stock rom?
I got the one you mentioned from sammobile... will this include the phone / csc/ things?
by the way..... will it get out of the boot loop?
thanks for your patience...
Go to Samfirmware & search for an entire stock rom (which will have kernel, modem & CSC) for your country if there's an unbranded one, or get one specific to your carrier if there isn't unbranded.
Will it get you out of bootloop ? You'd think so, but without knowing exactly what caused your phone to throw a wobbly in the first place, it's hard to say definitively. But at the moment, you don't really have any other option given your phone won't boot normally & all you have is DL mode.
Edit - I've checked Samfirmware, there's 3 for Telcel; 2.3.6, 4.0.3 & 4.1.2. You can probably skip the GB one & choose either of the other two
And you're welcome
MistahBungle said:
Go to Samfirmware & search for an entire stock rom (which will have kernel, modem & CSC) for your country if there's an unbranded one, or get one specific to your carrier if there isn't unbranded.
Will it get you out of bootloop ? You'd think so, but without knowing exactly what caused your phone to throw a wobbly in the first place, it's hard to say definitively. But at the moment, you don't really have any other option given your phone won't boot normally & all you have is DL mode.
Edit - I've checked Samfirmware, there's 3 for Telcel; 2.3.6, 4.0.3 & 4.1.2. You can probably skip the GB one & choose either of the other two
And you're welcome
Click to expand...
Click to collapse
Ok, finally finished the download.
I'm soon to flash and I have a dumb question....
should I unpackage the file or flash it to the kernel as is? (its a.zip)
if I extract it it contains the .tar.md5 and SS_Dl.dll
Extract the tar.md5, flash it in the PDA section of Odin. Delete the .dll
MistahBungle said:
Extract the tar.md5, flash it in the PDA section of Odin. Delete the .dll
Click to expand...
Click to collapse
Just before I break anything.... since this wasn't working just yet (and your explanation explains alot haha)
I got CWM again and I restored my previous mod /build whatever its called......
So I have a working device again. The question then is...... (and completely changing subject) IS there a way to resolve the no IMEI problem from this point?
I dail +#06# and get a blank imei thing.......
Any suggestions?
Forget the code. Check your IMEI in settings/about phone. If it's not 0049-----, then you're fine. If it is & you don't have an EFS backup, there are a bunch of threads on here which claim to be able recover your IMEI; you need to read them (No idea whether these methods work as I've never had to use them & never will because I make EFS backups). Either that or service centre who can fix the IMEI.
Edit -Also, I'm, rather confused. You claim you have nothing but download mode, yet all of a sudden have CWM working ? Sounds like you've left a lot of details/a lot of what you've been doing out. Bit of a waste of my time answering your posts in the end really.
MistahBungle said:
Forget the code. Check your IMEI in settings/about phone. If it's not 0049-----, then you're fine. If it is & you don't have an EFS backup, there are a bunch of threads on here which claim to be able recover your IMEI; you need to read them (No idea whether these methods work as I've never had to use them & never will because I make EFS backups). Either that or service centre who can fix the IMEI.
Click to expand...
Click to collapse
Lol I guess im screwed haha:
IMEI: Unknown
IMEI SV: unknown
Baseband Version Unknown:
--- Atleast I have the build numbers and kernel version info haha
Thank you for your help and patience! I'll see what I find!
I have a Samsung Galaxy s3 which I successfully rooted over a year ago though I never bothered with a custom rom. I have now purchased a note 3 so in preparation for selling the S3 I did a factory reset through Settings to clear out all my apps, data and personal information. That all went well and the device booted back into the normal system a couple of times (I didn't check to see if root had been maintained or not) This weekend I got it out to sell it only to find that it boots through the first part of the routine with the Samsung moving logo but then sticks on the static SAMSUNG screen and will not go further.
I am able to boot into TWRP so would I be able to download a stock rom from somewhere, insert a micro sd card with the stock rom on it and recover through TWRP? Alternatively I do have an old full back up stored on my computer - I could transfer this to the micro sd and restore this through twrp - I can see this was made through twrm as the openrecovery-twrp-2.3.1.0-i9300.tar.md5 is stored with it. Of course if this works I would still need to perform a reset to get rid of all the personal data etc so could end up in the same situation later.
What recommendations do you helpful guys have?
gbswales said:
I have a Samsung Galaxy s3 which I successfully rooted over a year ago though I never bothered with a custom rom. I have now purchased a note 3 so in preparation for selling the S3 I did a factory reset through Settings to clear out all my apps, data and personal information. That all went well and the device booted back into the normal system a couple of times (I didn't check to see if root had been maintained or not) This weekend I got it out to sell it only to find that it boots through the first part of the routine with the Samsung moving logo but then sticks on the static SAMSUNG screen and will not go further.
I am able to boot into TWRP so would I be able to download a stock rom from somewhere, insert a micro sd card with the stock rom on it and recover through TWRP? Alternatively I do have an old full back up stored on my computer - I could transfer this to the micro sd and restore this through twrp - I can see this was made through twrm as the openrecovery-twrp-2.3.1.0-i9300.tar.md5 is stored with it. Of course if this works I would still need to perform a reset to get rid of all the personal data etc so could end up in the same situation later.
What recommendations do you helpful guys have?
Click to expand...
Click to collapse
try to some firmware dude
u have usb jig? use it to reset u binary :good:
and flash again with odin
if u have backup in cwm u can restore so Do it :good:
As you are going to sell it then follow the guide in general forum, stickies to return to stock. Factory reset before you boot the fresh firmware.
further
VerlyAnanda said:
try to some firmware dude
u have usb jig? use it to reset u binary :good:
and flash again with odin
if u have backup in cwm u can restore so Do it :good:
Click to expand...
Click to collapse
I don't have a usb jig whatever that is
I have an old back up on my computer which I can copy to an external SD card to put in the phone
I can then try using TWRP (I have this not CWM) to try restore the back up
This may work I can only try it - however I will still be in the position of needing to do the reset to clear all my data and put the phone back into "new" state and am concerned this may cause the problem again
Is this the best plan? I suppose once I get it working I can use ODIN to flash a stock rom
The problem is I understood all this a year ago when I rooted it but its all a little vague to me now as I decided not to do more than root the phone so I could back it up
formatting cache solved the problem!
gbswales said:
I don't have a usb jig whatever that is
I have an old back up on my computer which I can copy to an external SD card to put in the phone
I can then try using TWRP (I have this not CWM) to try restore the back up
This may work I can only try it - however I will still be in the position of needing to do the reset to clear all my data and put the phone back into "new" state and am concerned this may cause the problem again
Is this the best plan? I suppose once I get it working I can use ODIN to flash a stock rom
The problem is I understood all this a year ago when I rooted it but its all a little vague to me now as I decided not to do more than root the phone so I could back it up
Click to expand...
Click to collapse
I read someone had the same problem and just cleared the cache - so went into Team Win wiped cache and it restarted - guess I was looking for a complicated solution to something simple!
Hi everybody,
hoping someone can help me as I am really frustrated now and have tried everything I can think of...
first a bit of info, I have an S6 edge, G925F and I was using a custom rom with no issues for a couple of months until all of a sudden I was having the same issue as others where I was getting "not registered on network" from damaged or corrupted /EFS, my imei had changed to 350000000000006 but I still had baseband version etc visible, just imei lost.
I have read on many threads that the answer is to change back to stock rom but no matter what rom i flash from sam mobile, it will not boot, when I go into recovery after booting it says "DM-Verity failed have to check DRK first", no matter what Rom I try but if I flash the odin flashable UNI Kernel after that then it will boot but then I have a rooted stock rom so not actually stock and an unstock kernel and still the not registered on network issue with same imei (350000000000006) .
so far I have tried flashing;
G925FXXS3COK5_G925FOXA3COK5_G925FXXS3COK5_HOME.tar.md5
G925FXXU3COI9_G925FBTU3COJ1_G925FXXU3COI9_HOME.tar.md5
and another one same as above but with XEU sales code as well as trying the EE (EVR) branded one with associated pit file and I've flashed every other pit file with each one as a last resort, to no avail...
nothing boots without flashing separate, non stock kernel, defeating the purpose of trying to return to stock.
p.S. Smart Switch doesn't work either as both it and kies say "SM-G925F does not support initialising, please contact support service"....
what can I do??
I've had 3 samsung phones now, s3, s4 and now s6, all rooted and have flashed countless roms on them and never had this issue and I also have no EFS back up as I have never selected it to back up in TWRP as I didn't know I should have and like I said, haven't had this problem before (kicking myself for not backing it up now...)
any help would be mucho appreciated as I am gutted to have broke my new phone and I am at my wits end with trying to fix it.... I thought I was quite good with tech and have done countless mods and rom flashes to various phones and solved many problems Ive encountered along the way but this is stumping me and I really need help..
Thanks in advance for your time and regards,
Elijah
anybody?
any ideas at all? anyone? how do I get the phone to rebuild or reset the EFS partition so that it refreshes it when I start it up with the sim card in it again? any ideas are more than welcome as I really can't accept Ive bricked my new phone, it's less than 3 months old and I know there must be a way to do it. any help would be appreciated, cheers in advance, Elijah
Elijah257 said:
any ideas at all? anyone? how do I get the phone to rebuild or reset the EFS partition so that it refreshes it when I start it up with the sim card in it again? any ideas are more than welcome as I really can't accept Ive bricked my new phone, it's less than 3 months old and I know there must be a way to do it. any help would be appreciated, cheers in advance, Elijah
Click to expand...
Click to collapse
I just managed to flash stock firmware on a SM-G925F (= model name in upper case) with Kies3.
It puts the phone on stock state (i.e. bootloader, efs partition, recovery, ... etc.)
but you have to be able to boot in Android in order to retrieve serial number in settings => about => state
Elijah257 said:
Hi everybody,
hoping someone can help me as I am really frustrated now and have tried everything I can think of...
first a bit of info, I have an S6 edge, G925F and I was using a custom rom with no issues for a couple of months until all of a sudden I was having the same issue as others where I was getting "not registered on network" from damaged or corrupted /EFS, my imei had changed to 350000000000006 but I still had baseband version etc visible, just imei lost.
I have read on many threads that the answer is to change back to stock rom but no matter what rom i flash from sam mobile, it will not boot, when I go into recovery after booting it says "DM-Verity failed have to check DRK first", no matter what Rom I try but if I flash the odin flashable UNI Kernel after that then it will boot but then I have a rooted stock rom so not actually stock and an unstock kernel and still the not registered on network issue with same imei (350000000000006) .
so far I have tried flashing;
G925FXXS3COK5_G925FOXA3COK5_G925FXXS3COK5_HOME.tar.md5
G925FXXU3COI9_G925FBTU3COJ1_G925FXXU3COI9_HOME.tar.md5
and another one same as above but with XEU sales code as well as trying the EE (EVR) branded one with associated pit file and I've flashed every other pit file with each one as a last resort, to no avail...
nothing boots without flashing separate, non stock kernel, defeating the purpose of trying to return to stock.
p.S. Smart Switch doesn't work either as both it and kies say "SM-G925F does not support initialising, please contact support service"....
what can I do??
I've had 3 samsung phones now, s3, s4 and now s6, all rooted and have flashed countless roms on them and never had this issue and I also have no EFS back up as I have never selected it to back up in TWRP as I didn't know I should have and like I said, haven't had this problem before (kicking myself for not backing it up now...)
any help would be mucho appreciated as I am gutted to have broke my new phone and I am at my wits end with trying to fix it.... I thought I was quite good with tech and have done countless mods and rom flashes to various phones and solved many problems Ive encountered along the way but this is stumping me and I really need help..
Thanks in advance for your time and regards,
Elijah
Click to expand...
Click to collapse
What happens when you just flash the stock FW, boot into recovery and make a factory reset from there? Cannot mount /EFS error???
AFAIK this IMEI is displayed when the EFS partition has been corrupted...
Some reported issues with param.bin (part of the BL file) in combination with EFS... and solved it by flashing the BL (which contains the param.bin) and the modem.bin
Try to flash a 4 part original FW, boot into recovery and make a factory reset...
Anyway if the EFS has lost data and you have not made a backup, you cannot fix / get back your original IMEI again.....
Check here: http://forum.xda-developers.com/galaxy-s6/help/help-restore-lost-imei-serial-sm-g920fd-t3239815
Hey,
My friend was running a flawless custom rom on his s3. Suddenly, it turns off by itself and the phone is then stuck on boot logo.
1. I tried to factory reset with no luck.
2. I tried to install stock 4.3 with no luck.
3. I tried to install 4.1.2. The phone booted but with no recovery. Then i noticed that imei changed to *0049 and i'm not registered on network (even though it was working well on the custom rom).
4. I tried to upgrade to 4.3, i got succeeded but recovery didnt install.
5. I tried to install the custom rom again but no luck.
6. I tried all patches of modems and kernels and ariza. All Failed.
7. I also tried EFS backup/restore and Failed.
My only concern is to know what made this issue appear all by itself ?? Because i guess we should take it to a mobile repair shop.
One last thing to say is that every time i try to install a software, available space gets low, and even if i delete some files from internal storage the storage wont free up.
Thank you !
get stock 4.3 fom and flash it via Odin (wipe everything before flash). Then flash recovery via odin. then backup efs. then flash custom roms.
downgrade from 4.3 to 4.1.x causes efs to become corrupted
Seems like a corrupt nand. Was it rooted previously when it died the first time?.
Going from 4.3 to 4.1.2 will cause the imei to be lost as the efs encryption changed at 4.3. You cannot go back.
If the phone has a custom rom on it try an official cwm recovery, if not or it doesn't work then proceed to the following:
If you can get the phone into download mode try flashing the stock firmware twice or thrice with a factory reset in between each flash. Do not allow the phone to boot into the os!!. If it attempts to boot to OS after the blue pass in odin then pull the battery out immediately and boot to recovery or download mode respective of what you are doing at the time, resetting or flashing.
If that fails you can then call it a dead phone.
Beamed in by telepathy.
Wow these are new solutions to me..
I really thank you guys and i'll look forward into trying them in any upcoming problems.
Thank you so much for sharing your knowledge
And just to mention, yes the phone was rooted when it went bricked suddenly.
I'd try to flash an official cwm and if it takes then flash back to stock twice with a reset, reroot and leave it as that. Custom roms aren't worth the paper they're written on.
In addition to downgrading from 4.3 to an earlier version, but forgot at the time of writing, you can downgrade but you need an efs backup from the time it was at 4.1.2, which has to be restored but I'm not sure of the process. I couldn't tell you if it has to be restored before flashing, after or both.
Not a lot of people have an efs backup from 4.1.2. I do, but then my phone hasn't acted wierd yet. Sods law.
Kies 2 (not kies 3) can restore the phone but only if it was in original condition. You can try the emergency recovery routine but don't hold your breath.
Beamed in by telepathy.
You're right.. Efs is the only part most of us miss !!
I wrote all of the steps you said in order.. So that if any problem occur ill deal with it based on your info.
Btw do you suggest using KK TW 4.4.4 by back-to-n00t ? Or this wont be considered as a kind of official firmware ?