Hi
My unflashed Tab S suddenly started boot looping whilst I was using it. Since then I have downloaded the latest Odin V3.13 and instal different variations of firmware from old to new. It always passes on Odin but then reboots to the Samsung Galaxy Tab S logo the green Android man comes up saying installing, then erasing, it reboots back to the Tab S Logo, goes to the just Samsung logo and switches off. After that I've tried factory erasing data in recovery mode and clearing the cache but then keeps looping again. I can't use Samsung Kies as it does not recognise my tablet. Can anyone help me please?
Continuation of story
I finally managed to load the oldest version of firmware and the tablet booted to the start menu but kept rebooting until, after many attempts, I managed to turn wifi off. Unfortunately, after skipping everything in the menu it loaded and my battery died completely. I have since bought, installed and charged a new one and once again, after several attempts, it loaded the oldest firmware and installed the apps required in order for it to boot up. It still won't let me get past the wifi page without rebooting then goes into a boot loop again until I turn it off. However when I plug it in to the charger it load the Tab S screen, then the Saumsung logo and the shuts down without looping.
Can anyone help me fix my problem please
frimley86 said:
I finally managed to load the oldest version of firmware and the tablet booted to the start menu but kept rebooting until, after many attempts, I managed to turn wifi off. Unfortunately, after skipping everything in the menu it loaded and my battery died completely. I have since bought, installed and charged a new one and once again, after several attempts, it loaded the oldest firmware and installed the apps required in order for it to boot up. It still won't let me get past the wifi page without rebooting then goes into a boot loop again until I turn it off. However when I plug it in to the charger it load the Tab S screen, then the Saumsung logo and the shuts down without looping.
Can anyone help me fix my problem please
Click to expand...
Click to collapse
Seeing as you've no other option and this may be a hardware issue.
It's worth ticking nand erase and repartition in Odin when flashing the firmware.
ashyx said:
Seeing as you've no other option and this may be a hardware issue.
It's worth ticking nand erase and repartition in Odin when flashing the firmware.
Click to expand...
Click to collapse
Thanks for trying to help but it fails in ODIN and says <ID:0/006> Can't open the specified file. (Line: 1834)
Do you think it's a lost cause now then?
frimley86 said:
Thanks for trying to help but it fails in ODIN and says <ID:0/006> Can't open the specified file. (Line: 1834)
Do you think it's a lost cause now then?
Click to expand...
Click to collapse
Try it without repartition. You need the PIT file.
I would also use odin 3.10 not the latest version.
Thanks
ashyx said:
Try it without repartition. You need the PIT file.
I would also use odin 3.10 not the latest version.
Click to expand...
Click to collapse
Thanks for trying to help but unfortunately it did not work. I tried many different combinations and stock rom files but it still won't reboot. If you have any further suggestions they would be appreciated otherwise thanks for trying
frimley86 said:
Thanks for trying to help but unfortunately it did not work. I tried many different combinations and stock rom files but it still won't reboot. If you have any further suggestions they would be appreciated otherwise thanks for trying
Click to expand...
Click to collapse
Can you boot in safe mode?
Have you tried to FORMAT (not wipe!) the system and data partitions in TWRP?
Briefly
ashyx said:
Can you boot in safe mode?
Click to expand...
Click to collapse
I can boot into safe mode but it will not stay on, I believe it is something to do with the wifi as on previous attempts if I was fast enough to turn the wifi off it stayed on and went through the whole start up procedure, unfortunately the one time I managed it was when the battery died completely.
I did have TWRP on it at one point but it seems to have disappeared on my many attempts with ODIN. I will try again
frimley86 said:
I can boot into safe mode but it will not stay on, I believe it is something to do with the wifi as on previous attempts if I was fast enough to turn the wifi off it stayed on and went through the whole start up procedure, unfortunately the one time I managed it was when the battery died completely.
I did have TWRP on it at one point but it seems to have disappeared on my many attempts with ODIN. I will try again
Click to expand...
Click to collapse
You can disable wifi by renaming the wifi folder in etc.
Use TWRP and go to etc/wifi
Rename the wifi folder to wifi-off
Then reboot and wifi won't be able to activate.
ashyx said:
You can disable wifi by renaming the wifi folder in etc.
Use TWRP and go to etc/wifi
Rename the wifi folder to wifi-off
Then reboot and wifi won't be able to activate.
Click to expand...
Click to collapse
I found /etc under file manager in TWRP but cannot find wifi listed. Am I looking in the right place? I'm using v3.2.1-0
frimley86 said:
I found /etc under file manager in TWRP but cannot find wifi listed. Am I looking in the right place? I'm using v3.2.1-0
Click to expand...
Click to collapse
Sorry I should have said In the system/etc folder should be the /wifi folder.
ashyx said:
Sorry I should have said In the system/etc folder should be the /wifi folder.
Click to expand...
Click to collapse
Sorry I still can't find it. Is it in file manager / system? In mine it only shows /bin
frimley86 said:
Sorry I still can't find it. Is it in file manager / system? In mine it only shows /bin
Click to expand...
Click to collapse
You need to mount the system partition first under the mount options.
ashyx said:
You need to mount the system partition first under the mount options.
Click to expand...
Click to collapse
I've renamed it and it's saved but when I initially start it in either safe or normal mode it's turned off but quickly says turning on, turns on then reboots. Anymore thoughts? Appreciate the effort you're putting in the help
frimley86 said:
I've renamed it and it's saved but when I initially start it in either safe or normal mode it's turned off but quickly says turning on, turns on then reboots. Anymore thoughts? Appreciate the effort you're putting in the help
Click to expand...
Click to collapse
Are you sure it took? Have you rebooted to recovery and checked?
Shouldn't be possible for wifi to enable without those files in the wifi folder.
ashyx said:
Are you sure it took? Have you rebooted to recovery and checked?
Shouldn't be possible for wifi to enable without those files in the wifi folder.
Click to expand...
Click to collapse
If definitely took the wifi-off but seems to be trying to turn on. On one occasion I waited on the wifi screen and it turned on (the tab went from unclear to green as if it was turning on) then the tablet died.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I actually managed to get through all the initial load screens at one point so when it does boot (in safe or normal mode) it goes directly to the home screen, but then crashes again with a few seconds. I'm assuming it's a wifi problem but not certain
(I've tried uploading photos but not sure if it's worked)
frimley86 said:
If definitely took the wifi-off but seems to be trying to turn on. On one occasion I waited on the wifi screen and it turned on (the tab went from unclear to green as if it was turning on) then the tablet died.
I actually managed to get through all the initial load screens at one point so when it does boot (in safe or normal mode) it goes directly to the home screen, but then crashes again with a few seconds. I'm assuming it's a wifi problem but not certain
(I've tried uploading photos but not sure if it's worked)
Click to expand...
Click to collapse
Can't see any pics.
Seems that even though the wifi can't enable the hardware is still attempting to activate.
The other way is to either disable it in the kernel or the init.rc.
Have you tried to quickly enable airplane mode as soon the device boots. This will switch off wifi completely.
ashyx said:
Can't see any pics.
Seems that even though the wifi can't enable the hardware is still attempting to activate.
The other way is to either disable it in the kernel or the init.rc.
Have you tried to quickly enable airplane mode as soon the device boots. This will switch off wifi completely.
Click to expand...
Click to collapse
Thanks so much for trying to help but I wiped the cache again and now can't get through the start up pages to even try and turn on airplane mode before it loops or shuts down.
It's even shut down whilst in TWRP if I leave it on too long so I'm guessing it must be a hardware issue and not the wifi as I thought.
Being the knowledgeable person you obviously are you are getting far to technical for me so I think I have to give up and save for a new one.
Thanks again for trying to help
P.s I've managed to get it in inflight mode finally and it still loops so not the wifi
frimley86 said:
Thanks so much for trying to help but I wiped the cache again and now can't get through the start up pages to even try and turn on airplane mode before it loops or shuts down.
It's even shut down whilst in TWRP if I leave it on too long so I'm guessing it must be a hardware issue and not the wifi as I thought.
Being the knowledgeable person you obviously are you are getting far to technical for me so I think I have to give up and save for a new one.
Thanks again for trying to help
P.s I've managed to get it in inflight mode finally and it still loops so not the wifi
Click to expand...
Click to collapse
Tbh I think you've suffered emmc failure. Not the first time and your symptoms are typical.
Related
Hi everyone,
I bought my HTC One X today and was told to install Cyanogen Mod 10 on it to get the best out of it. I have followed a couple of guides but i have completely screwed this up!! After following the instructions (well thought i did anyway) i have gotten to the point where my phone is stuck in the boot loop (spinning circle thing).
I have tried following guides everywhere but i'm getting completely lost and getting more and more frustrated because i dont understand anything that is being explained.
So is there any way of getting my phone back to normal or some form of working condition because i would hate to have broken something i just bought within 7 hours of having it
Any help is much appreciated.
FXhnd77 said:
Hi everyone,
I bought my HTC One X today and was told to install Cyanogen Mod 10 on it to get the best out of it. I have followed a couple of guides but i have completely screwed this up!! After following the instructions (well thought i did anyway) i have gotten to the point where my phone is stuck in the boot loop (spinning circle thing).
I have tried following guides everywhere but i'm getting completely lost and getting more and more frustrated because i dont understand anything that is being explained.
So is there any way of getting my phone back to normal or some form of working condition because i would hate to have broken something i just bought within 7 hours of having it
Any help is much appreciated.
Click to expand...
Click to collapse
I guess you dint flash the boot.img..When you open the CM 10 zip file you will find the boot.img there...just extract it to a known location and flash the boot.img file and then install the rom as you did b4...that will solve the problem
Dont worry, nothing bad has happened to your phone and its just a extra step to be followed till v get s-off
:good:
kskendsup said:
I guess you dint flash the boot.img..When you open the CM 10 zip file you will find the boot.img there...just extract it to a known location and flash the boot.img file and then install the rom as you did b4...that will solve the problem
Dont worry, nothing bad has happened to your phone and its just a extra step to be followed till v get s-off
:good:
Click to expand...
Click to collapse
Do this 1st fast boot erase cache then flash the boot.IMG
Sent from my Xoom using xda app-developers app
---------- Post added at 10:36 PM ---------- Previous post was at 10:31 PM ----------
Just thought I'd share this what I copied from a good source what helped me when I started flashing my hox but I use Linux so I don't have a clue about any window issues
.) Open the .zip file and copy 'boot.img' to your fastboot folder. Or the folder you use
.) Turn off your phone and enter the bootloader (Hold the Volume Down and Power Keys while off).
) Select 'Fastboot' by pushing the Power Key.
.) Plug your phone into your computer using a USB cable.
.)Now go to your computer and open a command window inside the fastboot folder (Hold SHIFT + Right Click on any white-space).
.) Type 'fastboot devices.'
) Type 'fastboot erase cache' and push enter. This can fix problems with bootloops or bootfailures.
.) Type 'fastboot flash boot boot.img' and push enter. It should say 'OKAY' if successful.
.) On your phone, select 'HBOOT' using the Power Key and scroll down to 'Recovery' using the Volume Down Key. Push to Power Key again to select it.
Once in recovery you can navigate by tapping the screen or by using the Power and Volume Up/Down Keys.
.) Select 'wipe data/factory reset' and accept the warning screen.
) Now select 'advanced' and select 'wipe dalvik cache.'
) Select 'mounts and storage' and then 'mount USB storage.'
.) Copy the .zip file you downloaded (Don't unzip it!) onto the SD card of your phone.
.) Unmount USB Storage on your phone and navigate back to the Recovery Homescreen.
.) Now select 'install zip from sdcard' followed by 'choose zip from sdcard.'
.) Select the .zip file and let it install.
Sent from my Xoom using xda app-developers app
I actually love the both of you!!! My phone is working again
REALLY appreciate it! :laugh:
Thank you
Stuck in CM Boot Loop - please help!!
Hi guys,
I too am a bit of a noob in this. I had similar problems and then followed the instructions listed above. I saved the following files to my SD Card:
cm-10.2.0-RC1-endeavoru.zip
gapps-jb-20130813-signed.zip
First time round, after I rebooted the device, I managed to get through and set up my WiFi, log into my Google Account, but just as my Google account was registering and beginning to restore my apps, my phones screen suddenly reverted to the boot loop (spinning circle thing). Furthermore, the LED indicator is now steadily flashing in Red!
I am completely stuck here and any assistance this forum can provide will be much appreciated.
Thanks in advance!
someshj1577 said:
Hi guys,
I too am a bit of a noob in this. I had similar problems and then followed the instructions listed above. I saved the following files to my SD Card:
cm-10.2.0-RC1-endeavoru.zip
gapps-jb-20130813-signed.zip
First time round, after I rebooted the device, I managed to get through and set up my WiFi, log into my Google Account, but just as my Google account was registering and beginning to restore my apps, my phones screen suddenly reverted to the boot loop (spinning circle thing). Furthermore, the LED indicator is now steadily flashing in Red!
I am completely stuck here and any assistance this forum can provide will be much appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Flash the boot.img!!!!
Thant said:
Flash the boot.img!!!!
Click to expand...
Click to collapse
Thanks Thant!
Just so you know, I first flashed the boot.img file (extracted it from the ROM package), then followed the steps in the post above.
This time round, the phone started up and I went through the initial set-up steps. Logged in to my Google account, everything seemed to work fine until I went to Play Store to check my apps. I briefly saw that my backed-up apps were downloading, then suddenly the phone went back to the CM boot screen (circular thing). That's how the phone has stayed.
What further do you guys advise?
Thanks.
someshj1577 said:
Thanks Thant!
Just so you know, I first flashed the boot.img file (extracted it from the ROM package), then followed the steps in the post above.
This time round, the phone started up and I went through the initial set-up steps. Logged in to my Google account, everything seemed to work fine until I went to Play Store to check my apps. I briefly saw that my backed-up apps were downloading, then suddenly the phone went back to the CM boot screen (circular thing). That's how the phone has stayed.
What further do you guys advise?
Thanks.
Click to expand...
Click to collapse
INSTRUCTIONS
First time installing CyanogenMod 10.2 to your HTC One X (GSM), or coming from another ROM:
Read the official wiki
Unlock your device via http://www.htcdev.com
Flash the latest official ClockworkMod-Recovery via Fastboot
Copy GApps and CM10.2 ZIPs to your SDCard
Boot into Recovery
Flash CM10.2 zip from SDCard
Flash GApps zip from SDCard
Flash the boot.img included in the CM10.2 zip via Fastboot
DO A DATA WIPE / FACTORY RESET
Reboot
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Thant said:
INSTRUCTIONS
First time installing CyanogenMod 10.2 to your HTC One X (GSM), or coming from another ROM:
Read the official wiki
Unlock your device via http://www.htcdev.com
Flash the latest official ClockworkMod-Recovery via Fastboot
Copy GApps and CM10.2 ZIPs to your SDCard
Boot into Recovery
Flash CM10.2 zip from SDCard
Flash GApps zip from SDCard
Flash the boot.img included in the CM10.2 zip via Fastboot
DO A DATA WIPE / FACTORY RESET
Reboot
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Click to expand...
Click to collapse
Thanks again, Thant! Your help is much appreciated.
Got the phone working with CM10.2, I played around with it for about 5 minutes, but not it has become unresponsive again. Pressing the power button to unlock the phone doesn't wake the screen, only the three soft buttons at the bottom light up, then nothing. If I leave the phone alone for a few minutes, it will wake up. I have since tried restarting the phone and it is working for the moment. I will report back if the screen hangs again.
Thanks again for your help.
someshj1577 said:
Thanks again, Thant! Your help is much appreciated.
Got the phone working with CM10.2, I played around with it for about 5 minutes, but not it has become unresponsive again. Pressing the power button to unlock the phone doesn't wake the screen, only the three soft buttons at the bottom light up, then nothing. If I leave the phone alone for a few minutes, it will wake up. I have since tried restarting the phone and it is working for the moment. I will report back if the screen hangs again.
Thanks again for your help.
Click to expand...
Click to collapse
Please try something for me.Turn on the screen and do a pressure between the right down side on main camera and display and see if the display flickering or do something strange.
Thant said:
Please try something for me.Turn on the screen and do a pressure between the right down side on main camera and display and see if the display flickering or do something strange.
Click to expand...
Click to collapse
Nope. Nothing. Although, I have noticed that the screen is taking a long time to wake up. When I press the pwer button, the screen should wake immediately, on the lock screen, but it is taking up to 2-3 minutes to wake. I have just now also noticed that when moving between screens or pulling the notification and app drawer, the display gets garbled and pixelated and screen flickers. It then sorts itself out.
I will try and capture a video of it happening and post it back here, if it helps.
someshj1577 said:
Nope. Nothing. Although, I have noticed that the screen is taking a long time to wake up. When I press the pwer button, the screen should wake immediately, on the lock screen, but it is taking up to 2-3 minutes to wake. I have just now also noticed that when moving between screens or pulling the notification and app drawer, the display gets garbled and pixelated and screen flickers. It then sorts itself out.
I will try and capture a video of it happening and post it back here, if it helps.
Click to expand...
Click to collapse
It is something like this
Thant said:
It is something like this
Click to expand...
Click to collapse
Yes, that's exactly what's going on. Although, I've been working with the device for a few hours now and I haven't seen the pixelated screen, but I have seen a delay in the screen waking to the lock screen.
Hardware..
Sent from my HTC One X using xda app-developers app
someshj1577 said:
Yes, that's exactly what's going on. Although, I've been working with the device for a few hours now and I haven't seen the pixelated screen, but I have seen a delay in the screen waking to the lock screen.
Click to expand...
Click to collapse
You have Black Screen of Dead sorry my friend you must to change the mainboard on the phone if you have warranty go back to full stock(stock rom and stock recovery), RELOCK the bootloader and send it for repair and hope they will repair free of charge if no warranty changing the mainboard will cost you some monеy. And I am right if you turn on the screen and you do pressure in the my point in previous post you will see the flickering and all the thing in this video. Sorry again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
imhotap said:
Hardware..
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Right you are!
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
Thant said:
You have Black Screen of Dead sorry my friend you must to change the mainboard on the phone if you have warranty go back to full stock(stock rom and stock recovery), RELOCK the bootloader and send it for repair and hope they will repair free of charge if no warranty changing the mainboard will cost you some monеy. And I am right if you turn on the screen and you do pressure in the my point in previous post you will see the flickering and all the thing in this video. Sorry again
Click to expand...
Click to collapse
Thank for your help! Glad to know guys like you are around!!
My phone's out of warranty, I'm afraid. I will carry on using it until it completely dies on me!!
is there any other option fo me to do, i have restore my phone many times but i cant get pass the boot screen because FRP is locked. i remember i turned off oem unlocking and i restored my phone and now i cant get past the boot screen. i looked online and i couldnt find anything, i even went back to stock rom and nothing. losing my mind for stupid thing i did
G925T 5.1.1.
Did you able to get it unlock yet ?
http://forum.xda-developers.com/show...php?p=61531848
madrrio said:
http://forum.xda-developers.com/show...php?p=61531848
Click to expand...
Click to collapse
The link does not work... Can you please re-post it... I'm stuck in the same situation so I desperately need help as well.
biddle said:
The link does not work... Can you please re-post it... I'm stuck in the same situation so I desperately need help as well.
Click to expand...
Click to collapse
i managed to boot up by flashing the attached file in odin BUT I GUET this green text
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/tmo...o-to-5-0-2-t3142946/post61531848#post61531848
elmy2424 said:
i managed to boot up by flashing the attached file in odin BUT I GUET this green text
Click to expand...
Click to collapse
I'll bet your fingerprint scanner dosen't work either. You have the a modified sboot.tar file. Should be able to Odin back to stock and start over now. Or leave it........
Svo86 said:
I'll bet your fingerprint scanner dosen't work either. You have the a modified sboot.tar file. Should be able to Odin back to stock and start over now. Or leave it........
Click to expand...
Click to collapse
managed to fix it just removed the cache partition from the stock tar and phone boots normally and fully works, but imei was 3500000006,,, no problem for me because i have a box and i wrote the imei again:good::good:
also i get a message saying "phone has been flashed with unauthorized firmware please reboot" , every time phone boots up but it disappear after some secounds:good::good:
maybe i damaged the imei when i was random flashing the 3 lastest firmwares
i have the sasme problem
How to fix this please
elmy2424 said:
managed to fix it just removed the cache partition from the stock tar and phone boots normally and fully works, but imei was 3500000006,,, no problem for me because i have a box and i wrote the imei again:good::good:
also i get a message saying "phone has been flashed with unauthorized firmware please reboot" , every time phone boots up but it disappear after some secounds:good::good:
maybe i damaged the imei when i was random flashing the 3 lastest firmwares
Click to expand...
Click to collapse
I need help I forgot to turn off my FRP and wenever I turn on my phone a yellow triangle pops up
my phone is j5
hello...my mobile is j5
i want to know how to fix...as my devloper option is not on.i have boot loop now.so cant able to use odin as it keep saying fail due to that reason.so how i gonna fix.is there any other way to start devloper option from pc.as my mobile is not starting only showing error. custom binary locker by frp.its frustrating.
elmy2424 said:
managed to fix it just removed the cache partition from the stock tar and phone boots normally and fully works, but imei was 3500000006,,, no problem for me because i have a box and i wrote the imei again:good::good:
also i get a message saying "phone has been flashed with unauthorized firmware please reboot" , every time phone boots up but it disappear after some secounds:good::good:
maybe i damaged the imei when i was random flashing the 3 lastest firmwares
Click to expand...
Click to collapse
s6 edge+
hi, do you have this file for the s6 edge plus?? or does it not matter??
am stuck on the boot, it boots up (show the frp lock) then turns it self off automatically.
sanu2015 said:
hello...my mobile is j5
i want to know how to fix...as my devloper option is not on.i have boot loop now.so cant able to use odin as it keep saying fail due to that reason.so how i gonna fix.is there any other way to start devloper option from pc.as my mobile is not starting only showing error. custom binary locker by frp.its frustrating.
Click to expand...
Click to collapse
@powerful111 @turkleman @elmy2424 @biddle @ikram11 @butterfan214
If I were you guys I would reset my phone with Smart Switch. I described how Here.
yaaaaa
yaa I downloaded my drivers what u have to do: ok soo go to Samsung live chat I asked them for the real drivers download it worked. the drivers were on my phone. then I went into odin on my phone and pc and mine finally recognized my phone. and my phones running just as new. NOTE:never root your phone. I was stuck myself in frp mode. thank goodd
wway19 said:
yaa I downloaded my drivers what u have to do: ok soo go to Samsung live chat I asked them for the real drivers download it worked. the drivers were on my phone. then I went into odin on my phone and pc and mine finally recognized my phone. and my phones running just as new. NOTE:never root your phone. I was stuck myself in frp mode. thank goodd
Click to expand...
Click to collapse
Actually there is nothing wrong with rooting your device. You just need to enable developer options when you get your device. As a small time developer I always do this first to see what was added or removed from there. Then you would have noticed the boot loader switch.
Samsung Galaxy FRP Locked
madrrio said:
http://forum.xda-developers.com/tmo...o-to-5-0-2-t3142946/post61531848#post61531848
Click to expand...
Click to collapse
I tried that lik to download from that mirror to unlock the frp but its no longer available. any other sites you kn?
DEFMAN219 said:
I tried that lik to download from that mirror to unlock the frp but its no longer available. any other sites you kn?
Click to expand...
Click to collapse
Anything that worked before the last update ( Nov 2015 ) doesn't work anymore, FRP has stumped a lot of users, developers, flashing geeks you name it, but if you find a solution come and post/share what worked for you.
Samsung doesn't want you messing with the phone, even if you paid for it.
Pp.
stuck in FRP LOCK
any help please
Failing to into a new firmware in my j1(sm-j110H)
sanu2015 said:
hello...my mobile is j5
i want to know how to fix...as my devloper option is not on.i have boot loop now.so cant able to use odin as it keep saying fail due to that reason.so how i gonna fix.is there any other way to start devloper option from pc.as my mobile is not starting only showing error. custom binary locker by frp.its frustrating.
Click to expand...
Click to collapse
oem unlocking is off and debuging mode off too and i am faiking to install a new firmware in my cellphone
What do I do? please help
First download a firmware that suitable to your mobile
And go to factory reset mode.do the factory reset
And flash the downloaded firmware if Samsung mobile flash with odin.and the mobile will boot normally after that use same Google Id that used before.ita done njoy
G925T 5.1.1.[/QUOTE]
Would someone mind helping me out, I cant use my phone any more. The last thing I did was install Emotion OS and then I installed the Emotion Kernel, upon reboot the phone was stuck on the emotion boot screen after restarting the phone Im not sure how it happened however the phone went from TWRP to some recovery that looks like the lineageos logo, I cant install any updates from this recovery and my phone via USB in download mode or ADB is not detected by any computer I have tried 3 computers in my house. I have never seen this recovery screen and I do not know what to do. I downloaded a stock MM firmware and converted it to a zip file from a tutorial on here however I keep getting an error message from this recovery. I really need my phone back up and running Im not sure what the heck happened.
Continued from other posts
Quote:
Originally Posted by shadeau
Do you have any options in recovery? Even if you could perform a "factory reset" with lineage OS you'd at least be able to enable ADB and reinstall TWRP. Also, when you say that the phone isn't recognized by the computer does that mean ADB, ODIN, and your OS don't recognize the phone?
So I do have options in this Lineage Recover but I cant get anything to work, Here are my options Reboot System Now, Apply Update, Factory Reset, Advanced. I have already tried factory reset however I may have deleted the OS all together with the Wipe Data Option. When I reboot the phone it stays on the the Samsung Galaxy Note 4 Screen with the little padlock that shows my bootloader is unlocked. I was messing around with flashing betwen several roms, I went from CM 14.1 to Lineage to Emotion OS, I then flashed the emotion kernel. If I select Apply update it gives me these several options, Apply from ADB choose from emulated (no typo) choose from sdcard1. I have tried to sideload via adb shell and my pc ( have tried multiple computers) does not detect the device. I even went to the extent of reinstalling windows and all Samsung USB and ADB drivers. Selecting choose from sdcard1 I can see the various zip files on my sd card however when it goes to install any roms it fails and just says error. There is a error log however it will not let me view these. My phone before this stopped connecting to any pc's I could plug the phone in via usb and it would charge but I would not get any notifications from windows! I will seriously send money to who ever can hlep me out I do not want to shell out for a new phone. Placing the phone in download mode still works however odin will not detect the phone either lol what the heck is going on here. I do have a micro sd card reader for the mc so i can place files on the phones card but I dont know what kind of file this recovery is looking for. I do not know how this recovery even got on here as I have been using TWRP from the very beginning. Please help me
I have never seen this recovery it has the lineage os logo and just says RECOVERY. I wish I could take a picture of the screen.
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
ziggsta2 said:
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
Click to expand...
Click to collapse
Are you using the Samsung OEM USB cord?
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
good questions will try another usb cable all I have is 1 for right now
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
quinciebee said:
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
Click to expand...
Click to collapse
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
ziggsta2 said:
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
Click to expand...
Click to collapse
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
quinciebee said:
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
Click to expand...
Click to collapse
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
ziggsta2 said:
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
Click to expand...
Click to collapse
CHECK THIS OUT People are having the same issues
https://forum.xda-developers.com/android/help/phone-stuck-bootloop-t3510266
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ziggsta2 said:
Click to expand...
Click to collapse
In the advanced menu is there an option to "mount system" or something? Also see if there's a setting in there for chmod
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
ziggsta2 said:
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
Click to expand...
Click to collapse
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
shadeau said:
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
Click to expand...
Click to collapse
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
ziggsta2 said:
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
Click to expand...
Click to collapse
Well, good luck! Send me a PM if you have trouble finding the links to unlocking and rooting.
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
mojoswagger1980 said:
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
Click to expand...
Click to collapse
Ouch ! I kinda failed to take into account the very real possibility the ROM you wished to flash might not be on your device and you may have no means to get it there.....in which case flash twrp then you need (if you don't want relock bootloader) to flash a system only image . vague I know I'm thinking .....bottom line is whatever you flash cannot contain aboot image or you will relock boot loader. If on 6.0.1 boot loader there is a safeupgrade to the most recent firmware that won't relock if on 5.1.1 (bpa1 ) idk if there is one . I think there is . in fact I'm sure there is hsbrad made Odin flashable IMG for all Verizon note 4 firmware broth dev and retail . look under his profile on XDA should link you to it
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
weard1212 said:
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
Click to expand...
Click to collapse
Yeah ty I went ahead and tried last night cause I was bored ....meh lack luster . oh and I did it intentionally and just restored recovery with flashify and I just realized this probably wasn't directed at me but yep lineage
Hi All,
I managed to brick my Fire TV 2 by flashing Magisk 12 whilst under the influence.
The unit now boots to the white Amazon logo, the power light goes from white to orange and then it restarts (bootloop).
I have tried various fixes covered on the AFTV site to get back in to recovery but to no avail.
Attempted to re-root the unit which fails with the message "error: source file is larger than target file!"
During the re-root process, It does load the preloader and the power light pulses white until I remove the power lead. Is there anything I can do from here?
Details: sloane-5.2.4.0-rooted_r1 rom with TWRP recovery v3.0.0-5
Thanks.
Reflash the pre rooted rom from recovery
m1steron said:
Hi All,
I managed to brick my Fire TV 2 by flashing Magisk 12 whilst under the influence.
The unit now boots to the white Amazon logo, the power light goes from white to orange and then it restarts (bootloop).
I have tried various fixes covered on the AFTV site to get back in to recovery but to no avail.
Attempted to re-root the unit which fails with the message "error: source file is larger than target file!"
During the re-root process, It does load the preloader and the power light pulses white until I remove the power lead. Is there anything I can do from here?
Details: sloane-5.2.4.0-rooted_r1 rom with TWRP recovery v3.0.0-5
Thanks.
Click to expand...
Click to collapse
The 2nd main requisite for Magisk is a fully unlocked bootloader. And only a small % of FTV1's have this done. If you can still go into TWRP. Then just flash the same PreRooted ROM you had installed before.
Y314K said:
The 2nd main requisite for Magisk is a fully unlocked bootloader. And only a small % of FTV1's have this done. If you can still go into TWRP. Then just flash the same PreRooted ROM you had installed before.
Click to expand...
Click to collapse
Sorry but it's a Fire TV 2 and the problem is that I can't get in to the TWRP recovery. I have tried multiple methods including the remote button presses and keyboard combinations.
The device isn't recognised over a network or USB adb. Before I bricked it, both USB and ADB debugging were enabled.
Have you tried the unbrick method?.
https://forum.xda-developers.com/newreply.php?do=newreply&p=65281865
I unbricked mine this morning
CFKod said:
Have you tried the unbrick method?.
https://forum.xda-developers.com/newreply.php?do=newreply&p=65281865
I unbricked mine this morning
Click to expand...
Click to collapse
Yes I have tried this but receive the following error:
error: source file is larger than target file!
I have tried using different versions of recovery and installer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Your links didn't work properly. Wasn't until I looked at it again that I saw the bit about an unbrick image. Trying it now, fingers crossed...
OK, I have tried using both unbrick methods (unbrick.img and unbrick+ramdisk.img) they completed successfully but didn't resolve the issue (white Amazon logo, pulsing orange light bootloop).
Presently I am trying to inject the prerooted rom's boot.img using the "mediatek_inject firetv2 COM4 boot.img /boot -" command. At 4% so far...
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Thanks have wondered about magisk as more apps check root. Obviously a no no
Sent from my SM-G955F using Tapatalk
m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Just think you did some Magisk v12 on non-Unlocked Bootloader FTV test. I am just glad you at least got your device back to a normal state. Took one for the modding scene. Thanks drunken M1steron. I know sober M1steron would not have approved.
Hello m1steron,
Thxs for sharing your experience.
Krgds
m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Trying to flash boot.img the forth time using mediatek inject command... It stucks at around 50% each time. Should i try it again and again or leave it?
Servet83 said:
Trying to flash boot.img the forth time using mediatek inject command... It stucks at around 50% each time. Should i try it again and again or leave it?
Click to expand...
Click to collapse
Did it finish? I left mine flashing for most of the day so I don't know if it paused at 50% or not.
m1steron said:
Did it finish? I left mine flashing for most of the day so I don't know if it paused at 50% or not.
Click to expand...
Click to collapse
No, it didn't finish. Yesterday it stopped at 67%. Don't know what to do alternatively...is it cause im using a windows pc?
Servet83 said:
No, it didn't finish. Yesterday it stopped at 67%. Don't know what to do alternatively...is it cause im using a windows pc?
Click to expand...
Click to collapse
I used Windows 10 on an old works laptop. Could you describe all the steps you are taking?
m1steron said:
I used Windows 10 on an old works laptop. Could you describe all the steps you are taking?
Click to expand...
Click to collapse
1. Connect to FTV using a2a usb cable
2. start handshake
3. Power on Box (handshake complete)
4. Start mediatek inject command (continue with 'y')
5. Wait writing filesystem...
Here are 2 Screenshots. One for the install_firetv2_recovery process and the other dor mediatek inject process.
Servet83 said:
1. Connect to FTV using a2a usb cable
2. start handshake
3. Power on Box (handshake complete)
4. Start mediatek inject command (continue with 'y')
5. Wait writing filesystem...
Here are 2 Screenshots. One for the install_firetv2_recovery process and the other dor mediatek inject process.
Click to expand...
Click to collapse
Thanks, are you using the extracted boot.img from the same pre-rooted rom that is installed on your device?
Also, this is where I got the information from: https://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349/page3
rbox should be able to help.
m1steron said:
Thanks, are you using the extracted boot.img from the same pre-rooted rom that is installed on your device?
Also, this is where I got the information from: https://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349/page3
rbox should be able to help.
Click to expand...
Click to collapse
Yes, i am using the same boot.img (5.2.1.1).
How did u solve the error "source file larger target file" while running the install recovery batch?
Trying to get in touch with rbox. Thank u so far!
Servet83 said:
Yes, i am using the same boot.img (5.2.1.1).
How did u solve the error "source file larger target file" while running the install recovery batch?
Trying to get in touch with rbox. Thank u so far!
Click to expand...
Click to collapse
I didn't so I tried the below:
m1steron said:
OK, I have tried using both unbrick methods (unbrick.img and unbrick+ramdisk.img) they completed successfully but didn't resolve the issue (white Amazon logo, pulsing orange light bootloop).
Presently I am trying to inject the prerooted rom's boot.img using the "mediatek_inject firetv2 COM4 boot.img /boot -" command. At 4% so far...
Click to expand...
Click to collapse
m1steron said:
I didn't so I tried the below:
Click to expand...
Click to collapse
Didn't work for me i remember that usb debugging was turned of before bricking the device and maybe thats the issue now...
I recently got a used Samsung Galaxy S9 (G960F/DS) with a broken screen (shattered glass and a black spot on the LCD). I was preparing to replace its screen, however, I'm currently not getting the device to boot.
When connected to power, the phone turns on automatically and ends up stuck on the "Samsung Galaxy S9 Secured by Knox Powered by android" screen. When disconnecting power, it turns off after 1-2 seconds.
By pressing power + bixby + volume down, the device enters download mode. When trying to flash stock firmware (BL + AP + CP + CSC) downloaded through Frija (SM-G960F_2_20211021052205_oql3mv17br_fac) the process fails and the phone shows "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". However, I was able to flash the four parts separately by rebooting in between.
This doesn't change anything about the booting problem though. Holding power + bixby + volume up doesn't boot recovery either.
I'd be happy to hear any suggestions. If any more information is required, I'm happy to send you everything I know.
Jogius said:
I recently got a used Samsung Galaxy S9 (G960F/DS) with a broken screen (shattered glass and a black spot on the LCD). I was preparing to replace its screen, however, I'm currently not getting the device to boot.
When connected to power, the phone turns on automatically and ends up stuck on the "Samsung Galaxy S9 Secured by Knox Powered by android" screen. When disconnecting power, it turns off after 1-2 seconds.
By pressing power + bixby + volume down, the device enters download mode. When trying to flash stock firmware (BL + AP + CP + CSC) downloaded through Frija (SM-G960F_2_20211021052205_oql3mv17br_fac) the process fails and the phone shows "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". However, I was able to flash the four parts separately by rebooting in between.
This doesn't change anything about the booting problem though. Holding power + bixby + volume up doesn't boot recovery either.
I'd be happy to hear any suggestions. If any more information is required, I'm happy to send you everything I know.
Click to expand...
Click to collapse
May I'm wrong, but the first impression seems that not only the screen is defective, keep in mind that a device with that broken screen had to receive a severe shock (or various of them), to this can happen, in the incident -of course- other hardware could be damaged.
But taking apart the hardware thing, did you try to format data through stock recovery? Or could you see in the recovery screen (if something is visible) the current build number, so you can flash the right firmware instead of a lower version or the first you found out there?
SubwayChamp said:
May I'm wrong, but the first impression seems that not only the screen is defective, keep in mind that a device with that broken screen had to receive a severe shock (or various of them), to this can happen, in the incident -of course- other hardware could be damaged.
But taking apart the hardware thing, did you try to format data through stock recovery? Or could you see in the recovery screen (if something is visible) the current build number, so you can flash the right firmware instead of a lower version or the first you found out there?
Click to expand...
Click to collapse
I feel like the phone might have another hardware defect, but I'd still like to try my best to fix it.
Unfortunately, the previous owner already tinkered with the device aswell, when I received it, it was not booting stock recovery. However, I only tried flashing the newest update of the firmware - was that the wrong approach? How (and where) can I find a lower version without knowing the exact version details?
Thank you for the input!
Jogius said:
I feel like the phone might have another hardware defect, but I'd still like to try my best to fix it.
Unfortunately, the previous owner already tinkered with the device aswell, when I received it, it was not booting stock recovery. However, I only tried flashing the newest update of the firmware - was that the wrong approach? How (and where) can I find a lower version without knowing the exact version details?
Thank you for the input!
Click to expand...
Click to collapse
Not sure if as the screen is broken you can see something through it, in the recovery screen you'll find the build number version for your device.
Flashing the latest update is always the best bet to not fail. Flashing lower version is not a good idea. You also have to check what is the input in the download screen, if something like KG prenormal warning is there, then you can't flash something in this state.
Also, as the previous owner seems to be not so careful with this device, it is probable that the latest Google account is still there that will trigger the FRP protection.
SubwayChamp said:
Not sure if as the screen is broken you can see something through it, in the recovery screen you'll find the build number version for your device.
Flashing the latest update is always the best bet to not fail. Flashing lower version is not a good idea. You also have to check what is the input in the download screen, if something like KG prenormal warning is there, then you can't flash something in this state.
Also, as the previous owner seems to be not so careful with this device, it is probable that the latest Google account is still there that will trigger the FRP protection.
Click to expand...
Click to collapse
I attached an image of what information download mode has. The second image shows what happens when I try to boot recovery (or anything except download mode for that matter).
You are right that the FRP ist still turned on. Does that mean there is no way to go around this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Jogius said:
I attached an image of what information download mode has. The second image shows what happens when I try to boot recovery (or anything except download mode for that matter).
You are right that the FRP ist still turned on. Does that mean there is no way to go around this?
View attachment 5478243View attachment 5478245
Click to expand...
Click to collapse
Yes, I suspected that, FRP is active, try to find the guy that sold to you this device, and ask him to log out from his Google account. Also the FRP trigger can be a false positive in the instance that you can enable OEM unlock toggle (what it is not actually enabled), and if Odin allow you to flash something on it and from there you could set it up your device normally.
SubwayChamp said:
Yes, I suspected that, FRP is active, try to find the guy that sold to you this device, and ask him to log out from his Google account. Also the FRP trigger can be a false positive in the instance that you can enable OEM unlock toggle (what it is not actually enabled), and if Odin allow you to flash something on it and from there you could set it up your device normally.
Click to expand...
Click to collapse
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Jogius said:
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Click to expand...
Click to collapse
frp still allows you to boot, it just will ask for your google account when setting the phone up
Jogius said:
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Click to expand...
Click to collapse
FRP works mainly in two ways, when you didn't enable OEM unlock and of course USB debugging then FRP detects an unofficial attempt to inject some custom binary rejecting to boot to system, (What would be the purpose of FRP if you could flash a custom binary, rooting it and then pulling all the data you want?) sometimes this is bypassed by formatting data either booting to recovery (that you say you can't do at this time) or flashing the CSC different from the CSC_HOME, this will wipe/format all your data. And the second instance where FRP can be trigger is when the device was black listed (plus the Samsung account if the last owner didn't log out). The first thing you have to do when buying a Samsung device is logging into the two accounts, then formatting data, and from there you can do what you want.