Galaxy Core Restored With M-G360T1 Firmware - Samsung Galaxy Core

twrp for metro pcs core prime sort of ????
OK IN MY SEARCH FOR ROOT AND TWRP FOR OUR METRO PCS CORE PRIME I HAVE DISCOVERED A FEW THINGS
1 . IF YOU BRICK YOUR PHONE YOU CAN DOWNLOAD THE T MOBILE SM-G360T1 FIRWARE FROM SANMOBILE FLASH IT THROUGH ODIN AND RESTORE YOUR PHONE
2 AS OF NOW I FLASHED THROUGH ODIN THE TWRP-2.8.7.1-coreprimelte.img.tar
that was made for the sm-g360f and it boots into twrp but the only thing that works is the power button as a lock
also note that my phone with twrp installed also boots as normal into the o.s without issue if you want to test this just know that when you hold the button combo to get into recovery you have to keep holding it until you see twrp screen
so if some one can mess with this and get it fully fuctional
please help

If you want to restore device without losing data next time just flash my ODIN boot file here. Better than reflashing the whole firmware.
http://forum.xda-developers.com/showpost.php?p=62457159&postcount=42
There is a file to restore recovery there too if needed. TWRP wont work until someone ports it specifically for our device. Hope this helps!
Sent from my SM-G360T1 using Tapatalk

Related

p6200 Cant access recovery, bootloop on 3.2, stuck on samsung logo 4.0.4

Hi, sorry for my bad english. Im from Vietnam, and im having a p6200
last night i tried to flash an the galaxy hd, the modified stock rom, through cwm, and i forgot to put it on external sdcard, i put it on the internal sdcard, and it failed to flash when system is erased. I've lost all my backup, because it was on the internal sdcard, but i still have the cwm recovery at that time.
Then, i tried to flash the 4.0.4 stock firmware through Odin. Flashing was ok, Odin show PASS!, but my tab is stuck on the SAMSUNG logo forever. This time looks like i've lost my root and cwm. I cannot access CWM nor stock recovery.
Then, i tried to flash back the stock 3.2, flashing still ok, but my tab got bootloop on the Samsung galaxy tab screen. I've tried the Vietnam fw and the UK fw both. When flashing is done and it's about to reset, ive seen just in a flash that there were 1 or 2 red line say that cannot access data/recovery... something.
I tried the emergency recovery in KIES. Never worked.
Now im out of option. I got bootloop on stock 3.2, stuck on 4.0.4, and i cannot access the recovery. Even when i try to flash recovery through Heimdall, it wont work. I can only access the download mode. By the way, the phone is neither stuck or bootloop, but it still charging through AC very good.
Did i hard brick my tab? Do i have to send it to warranty? Is my warrant now void? What options left do i have?
Panicing
Any one? Just tell me how can i get the recovery mode back
lpvlinh07 said:
Any one? Just tell me how can i get the recovery mode back
Click to expand...
Click to collapse
Same Here 100%
Please we need help
You are not alone.I was running 4.0.4 on my p6200 and was experimenting with the permanent CWM recovery and the temporary touch one.One thing led to another and my tablet was stuck at the samsung bootanimation.After a couple of reboots it was stuck at the galaxy tab plus logo.Finally it wouldn't boot anymore and my tab is literally dead.It doesn't respond to USB connection although it gets warm when plugged into an AC socket.I've been reading about the solutions extensively. There seems to be two : 1. Get it exchanged under warranty or 2. Get it Jtag-ed if you are out of warranty.
farazlodhi007 said:
You are not alone.I was running 4.0.4 on my p6200 and was experimenting with the permanent CWM recovery and the temporary touch one.One thing led to another and my tablet was stuck at the samsung bootanimation.After a couple of reboots it was stuck at the galaxy tab plus logo.Finally it wouldn't boot anymore and my tab is literally dead.It doesn't respond to USB connection although it gets warm when plugged into an AC socket.I've been reading about the solutions extensively. There seems to be two : 1. Get it exchanged under warranty or 2. Get it Jtag-ed if you are out of warranty.
Click to expand...
Click to collapse
Just got the CWM work on it.
But getting error each time i try to install .zip roms
Problem also that i don't have CWM backup file.
Do you think if i got my friend Tab (Same model exactly) and done a CWM backup on it and ther restore to my Tab will work?
als500 said:
Just got the CWM work on it.
But getting error each time i try to install .zip roms
Problem also that i don't have CWM backup file.
Do you think if i got my friend Tab (Same model exactly) and done a CWM backup on it and ther restore to my Tab will work?
Click to expand...
Click to collapse
that would work, unless you have a hard brick. of course, you should try it, and see if you can recover from the bootloops.
Hey guys it seems i have found a solution. Just find a stock heimdall package rom and flash with heimdall. Somehow heimdall seem to be able to do what odin couldnt. Now my tab is running stock ics smoothly. Just use heimdall to flash. I hope this gonna help someone who in the situation like i was.
Sent from my MT11i using xda app-developers app
i'm glad to hear that, i have same problem know, bootloop , stuck on samsung logo, after flashing cm9 , and do the wipe from stock android recovery
halim8051 said:
i'm glad to hear that, i have same problem know, bootloop , stuck on samsung logo, after flashing cm9 , and do the wipe from stock android recovery
Click to expand...
Click to collapse
Halim,
try this, hope can help u,
1) reflash using odin 1.85.
2) Check repartion and select .pit
3) Get .pit in this link.
For save. Flash hc and wipe data (Your data will lost). Hope u already backup.
http://forum.xda-developers.com/showthread.php?p=31915442
for others, don't ever wipe on any temporary recovery mode (Touch version) or ics stock recovery. Only use for flash root.zip and flash permanent recovery(cwr6.0.1.0).
Sent from my GT-P6200

Can't Boot Recovery Philz Touch - Root Lost

I was running Alliance rom and decided I wanted to try a couple different roms. I had previously installed Philz touch recovery 6.48.4 and had no issues with it. So I went into recovery and did the 'clean to install new rom' option and then I installed the Beanstalk 4.4.285 rom and checked it out and then was going to wipe it and try out Paranoid Android 4.45 so I rebooted to recovery again using the script in Rom Toolbox which is how I had been rebooting in to recovery since having installed Philz Touch because it's just simpler than holding the hardware keys. I had never tried booting in to Philz recovery using hardware keys. So anyways once in recovery again I once again do the 'clean to install new rom' option and then I went to flash Paranoid Android and I get a message about (can't remember exactly what it said) root being lost and was asked If I want to (again not sure exactly what it said) push su back to system/xbin and I said yes at which point the phone rebooted and now I can not reenter Philz recovery. I have tried numerous key combos including V+,home, power ; V+,power : V-,Power : V-,home,power ; V-,V+,power, V-,V+,home,power and nothing. It just boots to the Samsung Galaxy SIII screen and sits there. When I tried the V-,Home,power combo I get a screen that reads something like "Warning a custom os can cause critical problems in phone and installed applications. If you want to download a custom OS press the volume up key...." I think that is download mode but not sure. How can I get back in to Philz and or regain root if lost and reflash back to Alliance? Hope I didn't brick it.
DuhCiphered said:
I was running Alliance rom and decided I wanted to try a couple different roms. I had previously installed Philz touch recovery 6.48.4 and had no issues with it. So I went into recovery and did the 'clean to install new rom' option and then I installed the Beanstalk 4.4.285 rom and checked it out and then was going to wipe it and try out Paranoid Android 4.45 so I rebooted to recovery again using the script in Rom Toolbox which is how I had been rebooting in to recovery since having installed Philz Touch because it's just simpler than holding the hardware keys. I had never tried booting in to Philz recovery using hardware keys. So anyways once in recovery again I once again do the 'clean to install new rom' option and then I went to flash Paranoid Android and I get a message about (can't remember exactly what it said) root being lost and was asked If I want to (again not sure exactly what it said) push su back to system/xbin and I said yes at which point the phone rebooted and now I can not reenter Philz recovery. I have tried numerous key combos including V+,home, power ; V+,power : V-,Power : V-,home,power ; V-,V+,power, V-,V+,home,power and nothing. It just boots to the Samsung Galaxy SIII screen and sits there. When I tried the V-,Home,power combo I get a screen that reads something like "Warning a custom os can cause critical problems in phone and installed applications. If you want to download a custom OS press the volume up key...." I think that is download mode but not sure. How can I get back in to Philz and or regain root if lost and reflash back to Alliance? Hope I didn't brick it.
Click to expand...
Click to collapse
I've used philz but only on my tablet. I prefer using terminal emulator to reboot if I need to. And the last part yes that is download mode. You can always try Odin
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
ShapesBlue said:
I've used philz but only on my tablet. I prefer using terminal emulator to reboot if I need to. And the last part yes that is download mode. You can always try Odin
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I figured it out. I feel stupid though. I was really freaking out hoping I didn't brick my phone, couldn't you just hear the panic in my post. The first key combo I used to boot recovery was correct I just wasn't doing it right. I was pressing V+,home,power and waiting for the samsung logo before letting go and that's why it wasn't working. But I found out the correct method is to hold down V+ and home then hold down power also and wait for the phone to vibarate then let go of the power button but continue to hold down V+ and home until recovery boots.
I was about ready to try reflashing recovery via odin but I was a bit concerned about a few things when it comes to that. If I do need to use odin in the future is there a specific version I should use for the S3. I downloaded Odin3 v3.07 and also have 1.85. I know your phone needs to be in download mode to use it, so now I know how to boot to download mode at least. My bootloader is unlocked and I was wondering if using odin would lock it or affect that in anyway or have any other type of ill effect on my phone?
DuhCiphered said:
I figured it out. I feel stupid though. I was really freaking out hoping I didn't brick my phone, couldn't you just hear the panic in my post. The first key combo I used to boot recovery was correct I just wasn't doing it right. I was pressing V+,home,power and waiting for the samsung logo before letting go and that's why it wasn't working. But I found out the correct method is to hold down V+ and home then hold down power also and wait for the phone to vibarate then let go of the power button but continue to hold down V+ and home until recovery boots.
I was about ready to try reflashing recovery via odin but I was a bit concerned about a few things when it comes to that. If I do need to use odin in the future is there a specific version I should use for the S3. I downloaded Odin3 v3.07 and also have 1.85. I know your phone needs to be in download mode to use it, so now I know how to boot to download mode at least. My bootloader is unlocked and I was wondering if using odin would lock it or affect that in anyway or have any other type of ill effect on my phone?
Click to expand...
Click to collapse
No Odin has nothing to do with the bootloader.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

Urgent help needed please, Bricked device ?

URGENT HELP NEEDED PLEASE;
Can you please help my buddy Tyler, he just got the T-Mobile Note 5, and he rooted it, and installed TWRP Recovery, and flashed a ROM for the first time, but he's afraid he may have bricked his device ?
Here's the thread I have been coaching him at. Any opinions ?
http://hardforum.com/showthread.php?t=1869279&page=23
Thank you.
As long as he knows what he's doing and has a unlock bootloader he should be fine
airam0931 said:
As long as he knows what he's doing and has a unlock bootloader he should be fine
Click to expand...
Click to collapse
He did get the whole root thing figured out, and his phone does have SuperSU installed, he then installed TWRP Recovery through Odin, and is running the latest Modem COI5.
He downloaded a T-Mobile ROM, and Arty97 Kernel, flashed the ROM + Kernel, and he said been stuck on the boot screen for 25 minutes, and can't get back into Recovery.
Suggestions ?
Actually never mind after reading that whole thread I would reccomend download the stock rom and then flashing it . This happened to me when I flashed the wrong framework for my device. It got stuck on the same screen . I flashed in with my stock rom and it went back to normal and I didn't lose anything.
Tyler made this comment, can't seem to even power off the phone.
amn, you really are trying to help. That's awesome. Sadly however, the thing won't turn off no matter how long I hold the power button.
I saw one thread on reddit that suggested downloading a stock ROM and flashing through Odin. But, I can't find a stock ROM and I don't think you can flash ROMs through Odin.
He did manage to get this after trying to power down./
[/QUOTE]
Now what he asked ?
Tell him to put it into download mode then flash his stock rom . I Googled it and found it super easily and even found instructions
This is Tyler, the guy Zorachus has tried so hard t help. I've been googling for stoc ROMs but haven't found any to download. Can I flash a ROM through Odin?
I'm iPhone jailbreaker guy, so all this Android stuff is new t me.
I want to post the link I found but I can't because this site has a 10 post rule to post links and I haven't done 10 posts and don't worry this is my first Android phone . I've been jailbreaking since 4.1.2 so the switch was weird for me too haha but yes you can flash flash a rom through Odin
Here:
http://www.sammobile.com/firmwares/download/56127/N920TUVU2COI5_N920TTMB2COI5_TMB/
Make sure it is the correct model and follow the instructions.
Don't worry, you should be fine.
If he got stuck again, hold down volume up and down and power at the same time and it reboots
Sent from my SM-N920T using Tapatalk
Get back to download mode by holding home power and volume down at same time and Odin right stock rom for n920t and should be fine you can find all you need in the n5 t-mobile forum on xda-developers most everyone in forum are very helpful
Sent from my SM-N920T using Tapatalk
matteosaeed said:
If he got stuck again, hold down volume up and down and power at the same time and it reboots
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Just the volume down and power does the trick ?
Sent from my SM-N920T using Tapatalk
I had this same issue, I found out that TWRP did not actually flash the rom so the phone sat on the boot logo with no OS to load, then read up on arter97's kernel and he recommends switching to PhilZ touch recovery instead of TWRP. He provides a download to this recovery on his thread I do believe. Luckily I had downloaded the recovery and simply flashed it via TWRP (Hint: while I was stuck on the boot up logo, the only thing that worked for me is holding Vol-, home and power, then as soon as the screen goes dark, switch from holding Vol- and hold Vol+ instead, wait a bit and recovery should boot).
Once I got Philz touch installed, I rebooted the recovery and voila, no more TWRP. I simply flashed the ROM through it and rebooted again, back in business.
So to conclude, I get the feeling you're experiencing the same problem, where you went wrong is using TWRP with the arter97 kernel.
EDIT: You're in luck! Go here: http://arter97.com/browse/exynos7420/kernel/5.0/n920tw8/
Grab the tar.md5 file and flash with Odin with the phone in download mode, then reboot to new recovery and flash your rom again
micfinn said:
I had this same issue, I found out that TWRP did not actually flash the rom so the phone sat on the boot logo with no OS to load, then read up on arter97's kernel and he recommends switching to PhilZ touch recovery instead of TWRP. He provides a download to this recovery on his thread I do believe. Luckily I had downloaded the recovery and simply flashed it via TWRP (Hint: while I was stuck on the boot up logo, the only thing that worked for me is holding Vol-, home and power, then as soon as the screen goes dark, switch from holding Vol- and hold Vol+ instead, wait a bit and recovery should boot).
Once I got Philz touch installed, I rebooted the recovery and voila, no more TWRP. I simply flashed the ROM through it and rebooted again, back in business.
So to conclude, I get the feeling you're experiencing the same problem, where you went wrong is using TWRP with the arter97 kernel.
EDIT: You're in luck! Go here: http://arter97.com/browse/exynos7420/kernel/5.0/n920tw8/
Grab the tar.md5 file and flash with Odin with the phone in download mode, then reboot to new recovery and flash your rom again
Click to expand...
Click to collapse
Hey thanks!!!! You saved my a$$ I have been dealing with this for 6+ hours now & couldn't get past the boot logo & your suggestion worked! I <3 you! Lol
Thank **** I found your post mate, I was stuck in a never ending boot loop with no way to get into recovery either.
The trick about holding down Vol-, home and power, and then switching to vol+ at blackscreen but keeping the others down, that thing worked and I was able to make it into my recovery!
Sadly however I made the most foolish mistake of all in my hurry and went for a factory reset.
On top of that I don't think that Titanium Backup was set to auto sync on my new phone so I might possibly have lost everything I have. Let's find out.

When I turn my phone on, it reboots over and over again, HELP PLEASE!

So I used my galaxy note edge SM-N915F for 6 months with no problem, but I did the Marshmallow 6.0.1 update and now it doesn't work. As I said in the title when I try to start it reboots over and over again.
Any suggestions?? It opens only downloading mode and I flashed a rom(official russian Marshmallow 6.0.1 rom) with Odin and it didn't work.
Please help me! Thanks in advanced!
gazeL_ said:
So I used my galaxy note edge SM-N915F for 6 months with no problem, but I did the Marshmallow 6.0.1 update and now it doesn't work. As I said in the title when I try to start it reboots over and over again.
Any suggestions?? It opens only downloading mode and I flashed a rom(official russian Marshmallow 6.0.1 rom) with Odin and it didn't work.
Please help me! Thanks in advanced!
Click to expand...
Click to collapse
When using the correct button combination are you able to enter recovery or does it continue to bootloop? Power, Home and Volume Up is used to enter recovery. When you attempted to flash the stock firmware through Odin, where did you download the stock firmware from?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
When using the correct button combination are you able to enter recovery or does it continue to bootloop? Power, Home and Volume Up is used to enter recovery. When you attempted to flash the stock firmware through Odin, where did you download the stock firmware from?
Click to expand...
Click to collapse
Yes, it continue to bootloop even when I try to open in recovery mode. I succesfully entered recovery mode only one time and was able to full wipe, full cache the phone. This is after the flashing. I flashed the stock firmware a week ago and I actually don't remember where I downloaded it from. Thanks for your interest.
gazeL_ said:
Yes, it continue to bootloop even when I try to open in recovery mode. I succesfully entered recovery mode only one time and was able to full wipe, full cache the phone. This is after the flashing. I flashed the stock firmware a week ago and I actually don't remember where I downloaded it from. Thanks for your interest.
Click to expand...
Click to collapse
Most firmwares are available from sammobile.com. Which version of Odin are you using? Also, when you performed the flash through Odin, did Odin show the flash to be successful on the progress window? Was your Note Edge rooted or did you have a custom recovery installed before the bootloop issue started?
fast69mopar said:
Most firmwares are available from sammobile.com. Which version of Odin are you using? Also, when you performed the flash through Odin, did Odin show the flash to be successful on the progress window? Was your Note Edge rooted or did you have a custom recovery installed before the bootloop issue started?
Click to expand...
Click to collapse
I used Odin3. Yes, Odin showed me the flash to be successful. My Edge didn't rooted before and I didn't have a custom recovery. I had an official software. I actually want to add an screenshot but XDA doesn't let me.
gazeL_ said:
I used Odin3. Yes, Odin showed me the flash to be successful. My Edge didn't rooted before and I didn't have a custom recovery. I had an official software. I actually want to add an screenshot but XDA doesn't let me.
Click to expand...
Click to collapse
Have you tried a different version of Odin to perform the flash? I have 3.07 and 3.10 and sometimes one version will work perfectly and the other will show a successful flash but the device will still bootloop. Check which version you have and then download a different one to test with. That may be your issue.
Also, can you enter recovery at all anymore? If you try to enter recovery several times in a row during the bootloop process you may be able to access it after a few attempts. If you can enter recovery, wipe data/factory reset for me. Then attempt to boot. If it loops again, download the official firmware from sammobile.com and flash it with your original version of Odin. If it still loops, then flash it again with the different version of Odin. Lemme know how it goes. I'll do what I can to help.
fast69mopar said:
Have you tried a different version of Odin to perform the flash? I have 3.07 and 3.10 and sometimes one version will work perfectly and the other will show a successful flash but the device will still bootloop. Check which version you have and then download a different one to test with. That may be your issue.
Also, can you enter recovery at all anymore? If you try to enter recovery several times in a row during the bootloop process you may be able to access it after a few attempts. If you can enter recovery, wipe data/factory reset for me. Then attempt to boot. If it loops again, download the official firmware from sammobile.com and flash it with your original version of Odin. If it still loops, then flash it again with the different version of Odin. Lemme know how it goes. I'll do what I can to help.
Click to expand...
Click to collapse
I tried different Odin versions but it didn't work. I can flash rom succesfully but after the flashing it doesn't open in recovery mode. It bootloops. Once, it opened in recovery mode and I did wipe data/factory reset after first flashing and it didn't work. Now, it still doesn't open anyway except Downloading Mode.
gazeL_ said:
I tried different Odin versions but it didn't work. I can flash rom succesfully but after the flashing it doesn't open in recovery mode. It bootloops. Once, it opened in recovery mode and I did wipe data/factory reset after first flashing and it didn't work. Now, it still doesn't open anyway except Downloading Mode.
Click to expand...
Click to collapse
Are you flashing the exact same ROM version you were using before this problem started? We're you using 5.1.1 before you accepted the MM OTA?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Are you flashing the exact same ROM version you were using before this problem started? We're you using 5.1.1 before you accepted the MM OTA?
Click to expand...
Click to collapse
I used 5.1.1 to before I accepted the MM OTA and I didn't have any p roblem with 5.1.1. I tried to flash different type of 6.0.1 after the problem. Just, problem started with the MM OTA. I will try to flash 5.1.1. So, I guess I need to enter recovery to wipe data/factory reset before flashing 5.1.1 but I can not because it still bootloop. How can I do wipe data/factory reset?
Edit1: And I readed somewhere, they said that it is about the kernel? Is it possible?
Edit2: A few minutes ago, I succeeded to enter recovery mode, I did factory reset and phone still bootloop. It doesn't open. Now, I am downloading the 5.1.1. I will try to flash 5.1.1.
Edit3: I tried a lot of times but it is still same. I flashed the 5.1.1 with different versions of Odin. I successful with flashed it but phone wants to enter in recovery mode after flashing and it bootloops. It is trying to enter recovery mode all time but it doesn't work. Sometimes, on charge, it close to enter the recovery mode. I said in edit2 I succeeded to enter recovery mode, but I didn't say that it was on charge because I discover this now. So, I don't know what I have to do, I am waiting for your suggestions.
gazeL_ said:
I used 5.1.1 to before I accepted the MM OTA and I didn't have any p roblem with 5.1.1. I tried to flash different type of 6.0.1 after the problem. Just, problem started with the MM OTA. I will try to flash 5.1.1. So, I guess I need to enter recovery to wipe data/factory reset before flashing 5.1.1 but I can not because it still bootloop. How can I do wipe data/factory reset?
Edit1: And I readed somewhere, they said that it is about the kernel? Is it possible?
Edit2: A few minutes ago, I succeeded to enter recovery mode, I did factory reset and phone still bootloop. It doesn't open. Now, I am downloading the 5.1.1. I will try to flash 5.1.1.
Edit3: I tried a lot of times but it is still same. I flashed the 5.1.1 with different versions of Odin. I successful with flashed it but phone wants to enter in recovery mode after flashing and it bootloops. It is trying to enter recovery mode all time but it doesn't work. Sometimes, on charge, it close to enter the recovery mode. I said in edit2 I succeeded to enter recovery mode, but I didn't say that it was on charge because I discover this now. So, I don't know what I have to do, I am waiting for your suggestions.
Click to expand...
Click to collapse
Let's see if we can get your Note Edge into safe mode without bootlooping. Use these steps:
Turn on safe mode
Turn the device off.
Press and hold the Power and Volume down key.
Continue to hold the Volume down key until the device finishes restarting.
Safe mode will display in the bottom left corner of the screen.
Release the Volume down key when you see Safe Mode.
I have read a few forums and notes about booting into safe mode can stop the bootloop. Once it's successfully booted into safe mode we can attempt to boot normally. Give it a shot and I'll keep researching. Good luck.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Let's see if we can get your Note Edge into safe mode without bootlooping. Use these steps:
Turn on safe mode
Turn the device off.
Press and hold the Power and Volume down key.
Continue to hold the Volume down key until the device finishes restarting.
Safe mode will display in the bottom left corner of the screen.
Release the Volume down key when you see Safe Mode.
I have read a few forums and notes about booting into safe mode can stop the bootloop. Once it's successfully booted into safe mode we can attempt to boot normally. Give it a shot and I'll keep researching. Good luck.
Click to expand...
Click to collapse
I tried a lot of times but it didn't work. I tried on charge, without charge, with different cables but still bootloop. It is just like a joke.
I tried with Kies but Kies didn't see my edge. It didn't connect. On the Kies window, it said "connecting..." so I waited about 2 hours and it didn't connect. Then, I tried to emergency firmware recovery, it didn't see my edge again.
Download Samsung Smart Switch and see if it recognizes your device.
Sent from my Nexus 6 using XDA-Developers mobile app
I have the same problem with my friend's phone (SM-N915F) , I tried all the suggested solutions to no avail.
Qaseeh said:
I have the same problem with my friend's phone (SM-N915F) , I tried all the suggested solutions to no avail.
Click to expand...
Click to collapse
Do you have your friends device with you and a PC to use? Was your friend trying to root the device or install a custom recovery or a custom ROM when this happened?
Or, did your friend accept the OTA for 6.0.1 MM and then ended up in a bootloop after installing the OTA?
fast69mopar said:
Do you have your friends device with you and a PC to use? Was your friend trying to root the device or install a custom recovery or a custom ROM when this happened?
Or, did your friend accept the OTA for 6.0.1 MM and then ended up in a bootloop after installing the OTA?
Click to expand...
Click to collapse
Yes i still have my friend's phone with me and I have a PC .. he wasn't trying to root it or anything .. he said that the phone was too slow then it rebooted by itself then the bootloops started. i have tried several time to get to the recovery but I couldn't I can only put it on download mode that's where I tried to flash a 6.0.1 MM stock rom using odin and didn't succeed
Qaseeh said:
Yes i still have my friend's phone with me and I have a PC .. he wasn't trying to root it or anything .. he said that the phone was too slow then it rebooted by itself then the bootloops started. i have tried several time to get to the recovery but I couldn't I can only put it on download mode that's where I tried to flash a 6.0.1 MM stock rom using odin and didn't succeed
Click to expand...
Click to collapse
What version of Odin are you using to flash the factory firmware? Try to flash the firmware with a different version of Odin.
Also, you said the flash was unsuccessful using Odin. Was there an error message in Odin at the bottom left corner of the screen? If so, what was the error? I have had several flashes fail using one version of Odin but pass with a different version.
Also, what version of Android was your friends device using before you tried to flash the 6.0.1 firmware? If the device was running 5.1.1, have you tried to flash a 5.1.1 firmware with Odin?
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
What version of Odin are you using to flash the factory firmware? Try to flash the firmware with a different version of Odin.
Also, you said the flash was unsuccessful using Odin. Was there an error message in Odin at the bottom left corner of the screen? If so, what was the error? I have had several flashes fail using one version of Odin but pass with a different version.
Also, what version of Android was your friends device using before you tried to flash the 6.0.1 firmware? If the device was running 5.1.1, have you tried to flash a 5.1.1 firmware with Odin?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have used Odin version 1.85 then tried with Odin v3.11.1 , the flash succeeded no errors but the phone stayed as is .. Actually, he doesn't know the android version of his phone before it bricked. Are u suggesting that I should try to flash a 5.1.1?
Qaseeh said:
I have used Odin version 1.85 then tried with Odin v3.11.1 , the flash succeeded no errors but the phone stayed as is .. Actually, he doesn't know the android version of his phone before it bricked. Are u suggesting that I should try to flash a 5.1.1?
Click to expand...
Click to collapse
Search for Odin 3.07 and 3.10. I use both of these versions. When all else fails for me I use 3.07 and it always seems to work for me. Also, I'm betting it was running 5.1.1 because 6.0.1 hasn't been out that long for the Saudi Arabian Note Edge. I would flash the 5.1.1 stock firmware using Odin 3.07 and see if it will allow you to boot normally. Let me know how it goes. Good luck.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Search for Odin 3.07 and 3.10. I use both of these versions. When all else fails for me I use 3.07 and it always seems to work for me. Also, I'm betting it was running 5.1.1 because 6.0.1 hasn't been out that long for the Saudi Arabian Note Edge. I would flash the 5.1.1 stock firmware using Odin 3.07 and see if it will allow you to boot normally. Let me know how it goes. Good luck.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried flashing android stock rom 5.1.1 like u suggested using Odin 3.07 and 3.10 but still nothing changed ... I think it's totally bricked.
Thank you fast69mopar I appreciate your inputs :good:
Qaseeh said:
I tried flashing android stock rom 5.1.1 like u suggested using Odin 3.07 and 3.10 but still nothing changed ... I think it's totally bricked.
Thank you fast69mopar I appreciate your inputs :good:
Click to expand...
Click to collapse
Dammit man. Ill keep looking through my Samsung stuff and see what I can find. I sent my cousin an email yesterday who works for Samsung in their Tier 3 Technical Support/Case Management Group and asked her for some help. I'm really curious as to what she has to say on the subject. When it comes to a Samsung Galaxy or Note device she is a PRO. When I run into an issue with any of my Samsung devices that I can't fix, I call or email her. Keep working on it and we will find a solution.

TWRP on samsung tab a GT-P5110

Hi there,
I am trying to install an unofficial LineageOS V 13.0 to this tablet
I got some issues with TWRP, i followed some instruction videos.
I downloaded TWRP for the tablet : https://twrp.me/samsung/samsunggalaxytab2wifiunified.html
I opened odin and i went to the odin screen on the tablet ( power + vol - ) I Selected the .tar file at the AP section of Odin.
The installation was succesfull.
Now for entering the TWRP , ihave to press power + volume + buttom right? If i do that i get the boot screen from the tablet and i enter the android recovery ( the android on hes back, belly open with a red ! inside ) But it won't boot TWRP.
Any suggestions?
solvathus said:
Any suggestions?
Click to expand...
Click to collapse
You've got to boot into recovery after flashing twrp. If you dont, stock recovery get rewritten.
champ1919 said:
You've got to boot into recovery after flashing twrp. If you dont, stock recovery get rewritten.
Click to expand...
Click to collapse
I tried that. I also disabled the auto reboot in odin. Now i get the TWRP.
Thanks for your responce !
Bricked it???
Ok, so I installed the twrp311-20180416-BIGSYS.zip onto my Samsung Galaxy Tab 2 10.1 P5110. Since reboot back into recovery, the tablet has effectively bricked completely... doesn't turn on at all. It had 70+% power at time of install but nothing doing. It doesn't even register that it's plugged into the charger (ie no charging indicators). Have I truly bricked this old bad boy???
Any direction or help towards a fix greatly appreciated.
Thanks
Bigsys.zip?
You sure you used the right recovery for your variant?
If not you might have bricked your tablet... Some other devices have a different partition layout (e.g recovery partition where we have our efs partition) which could brick a device if it's not made for that device.
For p31xx and p51xx you can get twrp also as .tar.md5 for Odin here: http://andi34.github.io/recoveries_tab2.html

Categories

Resources