I factory reseted my galaxy s5 snapdragon g900p (sprint version) from stock recovery and after that phone is asking to my samsung account mail id and password. I gave that but it is not connecting to samsung network. Wifi is turned on. Is there any way to bypass it or install twrp or a custom rom? I guess it has no root access.I aldready tried odin and fastboot but unfortunately that didn't work. Can anyone help me? Please
If it is stolen, then return it. If not, boot into download mode, use CF AutoRoot then install TWRP.
西村大一 said:
If it is stolen, then return it. If not, boot into download mode, use CF AutoRoot then install TWRP.
Click to expand...
Click to collapse
I tried it already but showing failed
Related
I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
I bricked my s4 (i337 Canadian, bell) the day I bought it, TWRP 2.6.0.0 was what bricked my phone (I think, or improper use of TWRP) and it wouldn't boot whatsoever (even my recovery was bricked), I managed to fix it by flashing stock firmware from ODIN 1.85 on PC to the phone (couldn't access recovery, so I flashed from PC) , make sure you download a stock firmware that is .tar to use with the PC version of ODIN, the second thing I had to do was flash CF Auto Root again using ODIN 1.85 from PC to phone, since I still couldn't boot my phone or recovery (other root flashing methods wouldn't unbrick my phone, but CF Auto Root did, download the MF3 version of CF auto root).
after all this crap I installed TWRP 2.5.0.0 as my recovery and haven't had any issues since :victory:
this was done on a I337MVLUAMG1 which I believe is the bell equivalent of the MF3 (update that blocked rooting by most methods like motochopper ect)
Thanks
Amb669 said:
I bricked my s4 (i337 Canadian, bell) the day I bought it, TWRP 2.6.0.0 was what bricked my phone (I think, or improper use of TWRP) and it wouldn't boot whatsoever (even my recovery was bricked), I managed to fix it by flashing stock firmware from ODIN 1.85 on PC to the phone (couldn't access recovery, so I flashed from PC) , make sure you download a stock firmware that is .tar to use with the PC version of ODIN, the second thing I had to do was flash CF Auto Root again (other root flashing methods wouldn't unbrick my phone, but CF Auto Root did, download the MF3 version of CF auto root).
after all this crap I installed TWRP 2.5.0.0 as my recovery and haven't had any issues since :victory:
this was done on a I337MVLUAMG1 which I believe is the bell equivalent of the MF3 (update that blocked rooting by most methods like motochopper ect)
Click to expand...
Click to collapse
Thanks for your reply.
I have the same problem as this guy
http://forum.xda-developers.com/showthread.php?t=2407950
Any Idea how to fix it?
jerryhuanginusa said:
I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
Click to expand...
Click to collapse
Dont thinknthere is antthing you can do. We have no return to stock method at this point in time. This is why it is important to follow forum rules and read and search before doing something youll regret, im nkt saying this to be mean...but there has been at least 5 people these past few days who have done the exact same thing as you and have gone in here looking for help...
My best advice, throw in some money for the bootloader unlock bounty and hope somethung happens soomer than later
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
jerryhuanginusa said:
I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
Click to expand...
Click to collapse
If you read through the threads it specifically stated that the MF3 boot loader is locked and you cannot install twrp or custom ROMS on it. I have seen so many posts regarding this it makes me sick. It's kies seeing the device? But is falling to recover? Or is it not seeing it?
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
http://forum.xda-developers.com/showpost.php?p=44570305&postcount=366
Fail to recover
Tylorw1 said:
If you read through the threads it specifically stated that the MF3 boot loader is locked and you cannot install twrp or custom ROMS on it. I have seen so many posts regarding this it makes me sick. It's kies seeing the device? But is falling to recover? Or is it not seeing it?
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
the Kies can detect the phone buy it fail to recover it. the progress bar runs a little and stopped. error message pop out on PC screen says "Emergency recovery failed, Please contact Samsung Customer Service"
Good afternoon guys,
i have a big issue with my galaxy s5 SM-G900S (korean version). I bought it as a refurbished device. Knox was on 0x1 so something may have been modified.
It came with the stock (?!) android 4.4.2 from march14. I tried to update but it returned a registration error. Probably because knox is 0x1
In any case, I activated usb debugging and tried to root the phone using cfautoroot and the corresponding root file: CF-Auto-Root-klteskt-klteskt-smg900s.zip which I still assume to be the correct one.
I used odin for flashing. The device was properly connected (blue).
Everything seemed to go smooth until the phone restart when it said "recovery is not seandroid enforcing". I tried several times with both odin 3.07 and 3.09 but i cannot pass this step. I also tried the method to untick auto reboot, shut the phone down manually and boot into recovery mode but it failed.
This means I am now stuck in the bootloop. I can access download mode, but i cannot reach recovery mode. Also the phone is not recognized by the computer if i try to connect it to adb, kies etc. Odin seems to connect properly still.
Alright how should i proceed now?? My actual target is to flash a custom rom. I will need to go for a dirty flash now correct? Should I flash a stock rom with odin? If yes, which one?
Please support me a bit, I am very frustrated on this topic, especially cause I still dont realize my mistake......
Merry Christmas and greets from Bavaria, Germany.
cheeet
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
toxious651 said:
Flash the stock firmware to get out of boot loop. After flashing the stock firmware, everything should be working fine and booting again. Instead of using CF auto root, flash a custom recovery like TWRP and then use it to flash the SuperSU zip.
Click to expand...
Click to collapse
Alright, Im back to stock android 4.4.2 now. Works perfect, aside from registration. If I click on "update now" it shows: SKT-USIM required.
Can someone link a detailed guide for flashing cm13? I checked the web but i still dont entirely understand.
In any case I do not want to risk going into a tricky situation once more.....
Thanks in advance.
Greets, cheet
SORRY ABOUT MY BAD ENGLISH
I am writing this tread because i recently unlocked the frp lock on my bricked ROOTED samsung galaxy note 5 (SM-N920C). I faced problem in flashing stock firmware as my phone lost drk. And hence i do research and it took about a month to find a solution. I am sharing it here.
Tools i used.
1. Samsung tool pro( cracked version)
2. SM-N920C Combination file:
http://shell.boxwares.com/default.aspx?DeviceModel=SM-N920C&Type=All#fh5co-table
Because i am on nougat firmware the Samsung tool pro doesn't work and at the same time i am not able to down grade the firmware due to frp lock.
3. TWRP RECOVERY
https://twrp.me/samsung/samsunggalaxynote5.html
PROCEDURE:
1. Flash the combination file in download mode. And wait for the phone to boot. In my case the phone doesn't boot.
Then go to download mode agian and remove frp lock with samsung tool.
2. Flash TWRP.
3. Flash any custome rom from TWRP. :good:
simply go to download mode and flash official firmware
after phone starts go to settings>>developer mode>>enable oem unlock toggle
that's all no frp lock anymore. i wonder why it took you 1 month to figure this out.
tucking fypo said:
simply go to download mode and flash official firmware
after phone starts go to settings>>developer mode>>enable oem unlock toggle
that's all no frp lock anymore. i wonder why it took you 1 month to figure this out.
Click to expand...
Click to collapse
Actually, when the phone is under the frp lock. Flashing stock firmware under odin will not work. At least it happened to my n920g. I used the emergency restore through the samsung smart switch app.
Sent from my SM-N920G using XDA-Developers Legacy app
loppv said:
Actually, when the phone is under the frp lock. Flashing stock firmware under odin will not work. At least it happened to my n920g. I used the emergency restore through the samsung smart switch app.
Sent from my SM-N920G using XDA-Developers Legacy app
Click to expand...
Click to collapse
but i could easily go to download mode even with frp lock on. only i could not restart my phone and not enter twrp. but download mode worked fine forme
Since i lost Drk i can't able to boot after repair with smart switch. And thats why i tried this method.
rahulkr0507 said:
Since i lost Drk i can't able to boot after repair with smart switch. And thats why i tried this method.
Click to expand...
Click to collapse
It's simple flash twrp with odin and flash magisk or supersu with twrp and voila...the phone is booted with stock rooted kernel
ebusuhejbi said:
It's simple flash twrp with odin and flash magisk or supersu with twrp and voila...the phone is booted with stock rooted kernel
Click to expand...
Click to collapse
We can't able to flash custom recovery in this case. The phone will not allow it.
ebusuhejbi said:
It's simple flash twrp with odin and flash magisk or supersu with twrp and voila...the phone is booted with stock rooted kernel
Click to expand...
Click to collapse
flashing any custom recovery wont work on frp locked. it will fail in odin.
If flash stock boot the phone and check oem unlock
Drk matters
ebusuhejbi said:
If flash stock boot the phone and check oem unlock
Click to expand...
Click to collapse
If there is no drk in the phone it won't boot. I lost drk and not able to flash the stock rom.
rahulkr0507 said:
If there is no drk in the phone it won't boot. I lost drk and not able to flash the stock rom.
Click to expand...
Click to collapse
And I lost drk but seems i checked the oem unlock on when rooted the phone and when I flash stock firmware the phone is booted without drk but I can flash twrp with odin and reroot the phone again
ebusuhejbi said:
And I lost drk but seems i checked the oem unlock on when rooted the phone and when I flash stock firmware the phone is booted without drk but I can flash twrp with odin and reroot the phone again
Click to expand...
Click to collapse
Yes its possible but in my case the oem unlock git disabled i dont know how its happened. After that i can't do anything other than the above procedures to make the device working.
Could you change the destination of SM-N920C Combination file, because I can`t download it from your link. Thank you.
Try to rename firmware .tar.md5 to .tar (remove.md5).and flash it via odin .it work
lawong said:
flashing any custom recovery wont work on frp locked. it will fail in odin.
Click to expand...
Click to collapse
try rename firmware original samsung from .tar.md5 to .tar only(remove.md5).and flash it via odin again.it work for me
tassotti said:
Could you change the destination of SM-N920C Combination file, because I can`t download it from your link. Thank you.
Click to expand...
Click to collapse
Its not my link i just given the link from i downloaded the files.
I just checked the link and its working.
rahulkr0507 said:
Its not my link i just given the link from i downloaded the files.
I just checked the link and its working.
Click to expand...
Click to collapse
I found this file on another place. Thank you.
Sent from my SM-N920C using Tapatalk
Help with FRP Locked
I need help with this. I have tried several methods, 2 different ODIN versions, several different firmwares...I cannot get out of FRP lock. Please, Please help me.
Please explain the problem in detail. Whats shown in phone about the failure?
lonewolf5557 said:
I need help with this. I have tried several methods, 2 different ODIN versions, several different firmwares...I cannot get out of FRP lock. Please, Please help me.
Click to expand...
Click to collapse
Flashing firmwares will not undo FRP. No matter how many you flash. Solving the FRP problem lies elsewhere. And to another comment some FRp locked sammys will flash in odin under lock,Others will not. FRP lock is contained in a Partition in the device that is not touched by odin. If flashing orig stock firmware does not boot due to DRK problem then that has to be addressed first. I have not had a Note 5 in a while but This much I do know.
TheMadScientist said:
Flashing firmwares will not undo FRP. No matter how many you flash. Solving the FRP problem lies elsewhere. And to another comment some FRp locked sammys will flash in odin under lock,Others will not. FRP lock is contained in a Partition in the device that is not touched by odin. If flashing orig stock firmware does not boot due to DRK problem then that has to be addressed first. I have not had a Note 5 in a while but This much I do know.
Click to expand...
Click to collapse
Where do I start then, please. Thank you.
Hi guys... i need help... i recently purchased tab A 2017 (SM T385). I want to root it...i tried rooting with magisk manager but it failed. I tried twrp twice but both times my tab didnt start after flashing twrp. Thanks to samsung i got it replaced from company. Please provide cf autoroot file for this model. I searched firmware.mobi it has cf autoroot package for this model but that was also not working. Everytime it gives error and odin flash failed. Please someone provide me cf autoroot of this model...
I am also using c9 pro... also its cf autoroot package which is available on firmware.mobi is not working.... i had to download from here xda forums.... so please please help and provide cf autoroot files for tab A (SM T385)
drvish said:
Hi guys... i need help... i recently purchased tab A 2017 (SM T385). I want to root it...i tried rooting with magisk manager but it failed. I tried twrp twice but both times my tab didnt start after flashing twrp. Thanks to samsung i got it replaced from company. Please provide cf autoroot file for this model. I searched firmware.mobi it has cf autoroot package for this model but that was also not working. Everytime it gives error and odin flash failed. Please someone provide me cf autoroot of this model...
I am also using c9 pro... also its cf autoroot package which is available on firmware.mobi is not working.... i had to download from here xda forums.... so please please help and provide cf autoroot files for tab A (SM T385)
Click to expand...
Click to collapse
Then you flashed the wrong TWRP and even if you did it was perfectly recoverable without resorting to replacing the device.
https://forum.xda-developers.com/showpost.php?p=75213132&postcount=17
.
ashyx said:
Then you flashed the wrong TWRP and even if you did it was perfectly recoverable without resorting to replacing the device.
https://forum.xda-developers.com/showpost.php?p=75213132&postcount=17
.
Click to expand...
Click to collapse
you are right. i had flashed wrong twrp. but as u said it will be recoverable. that does not happen in my case. my tab was stuck at samsung logo and keep on rebooting. not entering recovery mode or download mode so that i can flash stock firmware.... not even detected in adb. thats why i had no other option to replace it.... i go through the link you mentioned but frankly speaking. now i dont want to flash twrp anymore. i will wait till cf autoroot for this device become available. anyway thanks for your reply
drvish said:
you are right. i had flashed wrong twrp. but as u said it will be recoverable. that does not happen in my case. my tab was stuck at samsung logo and keep on rebooting. not entering recovery mode or download mode so that i can flash stock firmware.... not even detected in adb. thats why i had no other option to replace it.... i go through the link you mentioned but frankly speaking. now i dont want to flash twrp anymore. i will wait till cf autoroot for this device become available. anyway thanks for your reply
Click to expand...
Click to collapse
I guarantee it WAS recoverable regardless of whether it was boot looping or not.
All you had to do was hold POWER + HOME + VOL DOWN for a short while, whilst it was boot looping and it would have entered download mode.
I'm also not sure why you seem to have a preference of flashing CFautoroot over TWRP they are both custom recoveries?
ashyx said:
I guarantee it WAS recoverable regardless of whether it was boot looping or not.
All you had to do was hold POWER + HOME + VOL DOWN for a short while, whilst it was boot looping and it would have entered download mode.
I'm also not sure why you seem to have a preference of flashing CFautoroot over TWRP they are both custom recoveries?
Click to expand...
Click to collapse
no buddy it wasn't.... i tried for atleast 50 times holding power key, volume down and home key to enter download mode... but it wasn't.... it just keep rebooting... i waited whole night so that its battery would drain and then i try to boot. but failed.... even at service centre they were not able to enter download mode.... i prefer cf autoroot because i used that on my c9 pro... its quite simple and safe
drvish said:
no buddy it wasn't.... i tried for atleast 50 times holding power key, volume down and home key to enter download mode... but it wasn't.... it just keep rebooting... i waited whole night so that its battery would drain and then i try to boot. but failed.... even at service centre they were not able to enter download mode.... i prefer cf autoroot because i used that on my c9 pro... its quite simple and safe
Click to expand...
Click to collapse
I've never known a flash of twrp right or wrong to permanently brick a device and I've accidentally and purposely bricked many a device countless times.
It's pretty much almost impossible to brick a Samsung device simply by flashing the wrong boot or recovery image.
Yours is an unlikely one off.
As for cf_autoroot, no safer to flash than twrp. They are both using modified recoveries.
Hi, xda dev forums,
I initially wanted to root my phone to recover my lost files since I accidentally factory reset. I followed this tutorial /watch?v=s2Xp-lQg1xs
and now after the Odin process, which I believe I messed up the Odin process and bricked it., I am stuck at the boot with a message saying that The phone is not running Samsung's official software. You may have problems with features or security. and you won't be able to install software updates. My phone is a Singapore import to the UK and I used the UK firmware associated with my current sim carrier to root. How do I resolve this problem? My Samsung S10+ won't boot to download or recovery mode only is able to reset onto this boot. Any solutions?
SM-G975F
Put it in download mode and reflash the firmeare in odin
Player04 said:
Put it in download mode and reflash the firmeare in odin
Click to expand...
Click to collapse
When I try it flashes goes back on that screen or I get something about bootloader being unlocked and cannot verify integrity etc press power to continue, which then is on the same screen.
edit: I managed to boot to it
Player04 said:
Put it in download mode and reflash the firmeare in odin
Click to expand...
Click to collapse
Hey, I managed to save it and reflash. I want to recover my previously deleted files do you or anyone know of a free software that's able to do this?
U didnt back ir up on samsung cloud or google?