When I try to add my Gmail to sign in to the play store it says couldn't sign in there was a problem communicating with google play servers. I have found the correct google play services apk and reinstalled it. Still no luck. Anyone else have this problem?
HollowKyo said:
When I try to add my Gmail to sign in to the play store it says couldn't sign in there was a problem communicating with google play servers. I have found the correct google play services apk and reinstalled it. Still no luck. Anyone else have this problem?
Click to expand...
Click to collapse
I'm thinking about factory reset. Would I lose root and unlocked bootloader or brick possibly? But I've also seen factory reset doesn't help in most cases. I've fixed this before by downloading the correct apk on my note 2. And I'm 100 percent certain I have the right one this time. I've also cleared the caches and things. I'm a techy person. I've tried all the things.
Edit:
Actually I've been looking for a performance increasing rom without losing too many features. There's a lot I don't care about. Anyone know of a good one for this dev converted retail verizon one yet?
HollowKyo said:
I'm thinking about factory reset. Would I lose root and unlocked bootloader or brick possibly? But I've also seen factory reset doesn't help in most cases. I've fixed this before by downloading the correct apk on my note 2. And I'm 100 percent certain I have the right one this time. I've also cleared the caches and things. I'm a techy person. I've tried all the things.
Edit:
Actually I've been looking for a performance increasing rom without losing too many features. There's a lot I don't care about. Anyone know of a good one for this dev converted retail verizon one yet?
Click to expand...
Click to collapse
Are the date & time & timezone correct on your phone? Can you get to google.com from the phone's browser?
If the date & time settings are correct, try just uninstalling all updates and clearing data for Google Play Services, Google Play Store, and Google Services Framework. Make sure nothing Google related has been disabled or uninstalled.
Factory reset is safe, you won't lose dev status that way. Flashing factory firmware that contains an aboot.mbn will lose your dev status, and you'll have to go through the conversion again.
blindmanpb said:
Are the date & time & timezone correct on your phone? Can you get to google.com from the phone's browser?
If the date & time settings are correct, try just uninstalling all updates and clearing data for Google Play Services, Google Play Store, and Google Services Framework. Make sure nothing Google related has been disabled or uninstalled.
Factory reset is safe, you won't lose dev status that way. Flashing factory firmware that contains an aboot.mbn will lose your dev status, and you'll have to go through the conversion again.
Click to expand...
Click to collapse
The phone does connect to the internet. I've done all the things in the list aside from factory reset. Would you retain root? And nothing google has been disabled.
If you can retain root after a reboot, you should retain root after a factory reset. If a factory reset doesn't work, you can try flashing one of the safe upgrade packages in Odin and re-rooting.
blindmanpb said:
If you can retain root after a reboot, you should retain root after a factory reset. If a factory reset doesn't work, you can try flashing one of the safe upgrade packages in Odin and re-rooting.
Click to expand...
Click to collapse
Edit: double posted for some reason
blindmanpb said:
If you can retain root after a reboot, you should retain root after a factory reset. If a factory reset doesn't work, you can try flashing one of the safe upgrade packages in Odin and re-rooting.
Click to expand...
Click to collapse
Factory reset did nothing. Now it doesn't even let me try to sign in. Just straight to the can't connect error.
I found a Google Apps package that has all the Google Apps in it but when I tried to flash the zip it said I had the wrong one. Could someone point me in the right direction? Would reinstalling the gapps package even do anything? Any help is greatly appreciated. Until I fix this my phone is practically unusable.
The gapps package said it couldn't install when I tried the zip from twrp. I'm really in need of some help. I can't use my phone at all since I've factory reset it and the play store won't work.
Edit: I tried wiping the cache and dalvik cache in twrp and now my phone is boot looping. Yay
HollowKyo said:
The gapps package said it couldn't install when I tried the zip from twrp. I'm really in need of some help. I can't use my phone at all since I've factory reset it and the play store won't work.
Edit: I tried wiping the cache and dalvik cache in twrp and now my phone is boot looping. Yay
Click to expand...
Click to collapse
Is this a custom rom that you're on or official build, and if so, which build are you on? If you're on the latest official build 5.1.1 (BPA1), then like someone else suggested above, I'd suggest making sure that you have Samsung USB drivers installed on your PC, putting your phone in Downlode Mode, connecting it to the PC and using Odin to flash hsbadr's N910VVZW2BPA1 Stock Restore (Incremented) (your unlocked bootloader will be preserved) and twrp-2.8.5.0-trltevzw.img.tar, then using recovery to flash a permissive kernel such as MultiSystem kernel for TouchWiz 5.1.1. and then BETA-SuperSU-v2.71-20160331103524.zip to reroot. That should at least get your device booted up and working again.
livinxtreme2114 said:
Is this a custom rom that you're on or official build, and if so, which build are you on? If you're on the latest official build 5.1.1 (BPA1), then like someone else suggested above, I'd suggest making sure that you have Samsung USB drivers installed on your PC, putting your phone in Downlode Mode, connecting it to the PC and using Odin to flash hsbadr's N910VVZW2BPA1 Stock Restore (Incremented) (your unlocked bootloader will be preserved) and twrp-2.8.5.0-trltevzw.img.tar, then using recovery to flash a permissive kernel such as MultiSystem kernel for TouchWiz 5.1.1. and then BETA-SuperSU-v2.71-20160331103524.zip to reroot. That should at least get your device booted up and working again.
Click to expand...
Click to collapse
Thanks. I'll try this now.
I had that problem when i installed jasmine rom, what i did was boot in to recovery,wipe data and cache and install jasmine rom again and now is fine.
livinxtreme2114 said:
Is this a custom rom that you're on or official build, and if so, which build are you on? If you're on the latest official build 5.1.1 (BPA1), then like someone else suggested above, I'd suggest making sure that you have Samsung USB drivers installed on your PC, putting your phone in Downlode Mode, connecting it to the PC and using Odin to flash hsbadr's N910VVZW2BPA1 Stock Restore (Incremented) (your unlocked bootloader will be preserved) and twrp-2.8.5.0-trltevzw.img.tar, then using recovery to flash a permissive kernel such as MultiSystem kernel for TouchWiz 5.1.1. and then BETA-SuperSU-v2.71-20160331103524.zip to reroot. That should at least get your device booted up and working again.
Click to expand...
Click to collapse
When I try I get,
SW REV CHECK FAIL : [tz]Fused 2 > Binary 1
On my phone and,
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910VVRU2BPA1_StockRestore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> NON-HLOS.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> cache.img.ext4
<ID:0/008> modem.bin
<ID:0/008> recovery.img
<ID:0/008> rpm.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> sdi.mbn
<ID:0/008> system.img.ext4
<ID:0/008> tz.mbn
<ID:0/008> RQT_CLOSE !!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In odin.
HollowKyo said:
When I try I get,
SW REV CHECK FAIL : [tz]Fused 2 > Binary 1
Click to expand...
Click to collapse
Then your bootloader version most likely doesn't match the file you're flashing. Do you know the last official build that you were on, and which file that I linked you to did you attempt to Odin flash just now, the Stock Restore one or the Stock Restore Incremented? If you at any point accepted the official OTA to Lollipop, then your bootloader has been incremented, meaning you'll need to flash the Stock Restore Incremented file. However, if you stayed on Kit Kat, then flash the plain Stock Restore file.
livinxtreme2114 said:
Then your bootloader version most likely doesn't match the file you're flashing. Do you know the last official build that you were on, and which file that I linked you to did you attempt to Odin flash just now, the Stock Restore one or the Stock Restore Incremented? If you at any point accepted the official OTA to Lollipop, then your bootloader has been incremented, meaning you'll need to flash the Stock Restore Incremented file. However, if you stayed on Kit Kat, then flash the plain Stock Restore file.
Click to expand...
Click to collapse
I did take the ota. Now it boots straight to odin mode and says to use verizon software repair assistant.
I was on 5.1.1 I see what I need. I'll try this right now.
HollowKyo said:
I did take the ota. Any chance you could link me the download I need? Now it boots straight to odin mode and says to use verizon software repair assistant.
Click to expand...
Click to collapse
That's okay, it'll do that when ever there has been a flash fail. We can fix it. If you accepted the official OTA to Lollipop then your bootloader has been incremented, meaning you'll need to flash the N910VVRU2BPA1_StockRestore_Incremented.tar.md5.7z file. Be sure and visit the original post and give hsbadr thanks for his restore file though.
livinxtreme2114 said:
That's okay, it'll do that when ever there has been a flash fail. We can fix it. If you accepted the official OTA to Lollipop then your bootloader has been incremented, meaning you'll need to flash the N910VVRU2BPA1_StockRestore_Incremented.tar.md5.7z file. Be sure and visit the original post and give hsbadr thanks for his restore file though.
Click to expand...
Click to collapse
Followed your instructions. I am now back up and running at 100% and rooted. Thank you so much.
HollowKyo said:
Followed your instructions. I am now back up and running at 100% and rooted. Thank you so much.
Click to expand...
Click to collapse
That's awesome. Glad I could help you out, brother.
livinxtreme2114 said:
That's awesome. Glad I could help you out, brother.
Click to expand...
Click to collapse
That was some fantastic assistance you gave there. way to represent the community well :good::good::good:
sudermatt said:
That was some fantastic assistance you gave there. way to represent the community well :good::good::good:
Click to expand...
Click to collapse
I really appreciate that!
Related
I tried to get help through reddit to no avail. My GS3 can only start up in download mode and nothing else works. I have the proper drivers installed on my computer, yet every time I try to flash a stock rom (which I've made sure are for the T-999 model) Odin fails at the NAND write start! part. I tried using the GS3 Toolkit to flash a stock rom but it says I need USB debugging enabled, which I can't enable because my phone doesn't start up in anything but download mode. What do I do?
Pakarido said:
I tried to get help through reddit to no avail. My GS3 can only start up in download mode and nothing else works. I have the proper drivers installed on my computer, yet every time I try to flash a stock rom (which I've made sure are for the T-999 model) Odin fails at the NAND write start! part. I tried using the GS3 Toolkit to flash a stock rom but it says I need USB debugging enabled, which I can't enable because my phone doesn't start up in anything but download mode. What do I do?
Click to expand...
Click to collapse
What was the last thing you did before this happened? Any idea what caused it to not be able to boot normally? How about recovery? Can you get that?
Are you using the USB cable that came with the phone? Try other cables?
DocHoliday77 said:
What was the last thing you did before this happened? Any idea what caused it to not be able to boot normally? How about recovery? Can you get that?
Are you using the USB cable that came with the phone? Try other cables?
Click to expand...
Click to collapse
I have this problem after unrick phone by JTag, can not flash stock rom on T999 after repair boot vby Jtag.
Odin Log:
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Set PIT file..
<ID:0/017> DO NOT TURN OFF TARGET!!
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> aboot.mbn
<ID:0/017> NAND Write Start!!
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
DocHoliday77 said:
What was the last thing you did before this happened? Any idea what caused it to not be able to boot normally? How about recovery? Can you get that?
Are you using the USB cable that came with the phone? Try other cables?
Click to expand...
Click to collapse
I was trying to get CWM on the phone but it didn't work, and I was stuck with only being able to boot in download mode. I have tried other cables and other computers, no luck. I can't get into recovery mode, only download.
How did you attempt to install cwm? Try flashing only recovery in Odin.
Sent from my SGH-T999L using XDA Premium 4 mobile app
DocHoliday77 said:
How did you attempt to install cwm? Try flashing only recovery in Odin.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My phone is T999 hard bricked but after repair boot loader by jtag phone able to boot up into Download mode only.
Not able boot into recovery, i tried Flash stock firmware with pit file, it is fail the Odin log said like that.
I tried to flash TWRP succeed but still can not go into TWRP to flash custom rom.
I tried to flash stock kernel and stock recovery after succeed with Odin phone still like that.
Only Boot into Download mode. can not go into recovery or TWRP or OS.
T-Mobile lock bootloader T999 via OTA update like I337 with OTA MF3 update ?
Thanks for help.
DocHoliday77 said:
How did you attempt to install cwm? Try flashing only recovery in Odin.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Forgive me, I'm new but what do you mean flash only recovery? Please specify.
nguyento1986 said:
My phone is T999 hard bricked but after repair boot loader by jtag phone able to boot up into Download mode only.
Not able boot into recovery, i tried Flash stock firmware with pit file, it is fail the Odin log said like that.
I tried to flash TWRP succeed but still can not go into TWRP to flash custom rom.
I tried to flash stock kernel and stock recovery after succeed with Odin phone still like that.
Only Boot into Download mode. can not go into recovery or TWRP or OS.
T-Mobile lock bootloader T999 via OTA update like I337 with OTA MF3 update ?
Thanks for help.
Click to expand...
Click to collapse
Please just post in the thread you created. No need to post the same thing here too.
Pakarido said:
Forgive me, I'm new but what do you mean flash only recovery? Please specify.
Click to expand...
Click to collapse
You said you tried to install cwm. Cwm is a custom recovery. How did you try installing it? I suggested trying to flash it in Odin by itself.
First, please tell me where you got the cwm recovery, and how exactly did you try to install it?
If your inability to boot normally started after trying to get cwm, ill need to know where you got it and how you tried installing it if I am going to be able to help. Please include a link to the file and any instructions you used.
Sent from my SGH-T999L using XDA Premium 4 mobile app
DocHoliday77 said:
Please just post in the thread you created. No need to post the same thing here too.
You said you tried to install cwm. Cwm is a custom recovery. How did you try installing it? I suggested trying to flash it in Odin by itself.
First, please tell me where you got the cwm recovery, and how exactly did you try to install it?
If your inability to boot normally started after trying to get cwm, ill need to know where you got it and how you tried installing it if I am going to be able to help. Please include a link to the file and any instructions you used.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried to flash it in Odin, and then it broke. I cant link because I'm a new user but if you copy paste this into Google "CF-Root 6.4 — It’s the New Samsung Galaxy S3 Root Package, Includes CWM 5.5, SuperSU and CWM Manager App" it's the first result, the website is theandroidsoul.com.
Pakarido said:
I tried to flash it in Odin, and then it broke. I cant link because I'm a new user but if you copy paste this into Google "CF-Root 6.4 — It’s the New Samsung Galaxy S3 Root Package, Includes CWM 5.5, SuperSU and CWM Manager App" it's the first result, the website is theandroidsoul.com.
Click to expand...
Click to collapse
Ohh boy!
Did you not read the entire page there? This is mentioned in the main body and also in large italic letters immediately following the article,
"This hack and the guide below are compatible only and only with Galaxy S3, model number i9300. It’s not compatible with other devices. Check your device’s model number in: Settings » About phone."
That is the international model. Ours is not an I9300. Ours is SGH-T999. Flash anything for the I9300/I9305 and you are destined for a hard brick. Yours, while not a total brick due to the fact you can get into download mode, is pretty much in the same boat as the other guy who posted in this thread and started his own. Basically, you probably flashed cwm recovery to a non-recovery partition, and system apps to a non-system partition. The trick is figuring out what partitions you overwrote. Probably ones that are not included in the stock firmware.
You need to find out what partitions hold the System and Recovery on the I9300. (ex. on our phones, System is on mmcblk0p14 and recovery is on mmcblk0p18). if their system is on p7, for example, then you would have flashed apps to our boot/kernel partition. If their Recovery is on p2, then you would have flashed CWM to our SBL1 partition which is not available in the stock firmware. It is possible to also mess up the partion layout this way as well.
If I get the time tonight, I will try to look up some of this for you and the other guy, but I may not be able to help much with this as I've never had to actually perform this kind of fix. I know what needs to be done, just not positive I know how to go about it. I can make very educated guesses, but with stuff like this, if I guess wrong, it could end up a little worse!
I suggest you take the info I just gave to you and do a lot of research. If you want guaranteed results, go to www.mobiletechvideos.com and see what they offer. They are the only ones I have ever seen anyone on this forum report using, and everyone who did was always very happy with their service. There are other shops you can find online that do this type of work, but Ive not seen any others mentioned around here. Not sure about prices either, so its up to you to research all of that type stuff.
In all honesty, I would look into a repair service to see what they can offer price-wise. If its cheap enough, I would seriously consider using them.
Good Luck man! If I can come up with anything, Ill let you know. And if you want me to try to help with actually fixing it after we have more info, I can do my best, but keep in mind you may have to wait until I am freed up enough to focus on it and I will not promise any kind of positive results! Others may reply with more info during the day tomorrow too, so you may also want to wait to see if anyone else has anything to add.
DocHoliday77 said:
Ohh boy!
Did you not read the entire page there? This is mentioned in the main body and also in large italic letters immediately following the article,
"This hack and the guide below are compatible only and only with Galaxy S3, model number i9300. It’s not compatible with other devices. Check your device’s model number in: Settings » About phone."
That is the international model. Ours is not an I9300. Ours is SGH-T999. Flash anything for the I9300/I9305 and you are destined for a hard brick. Yours, while not a total brick due to the fact you can get into download mode, is pretty much in the same boat as the other guy who posted in this thread and started his own. Basically, you probably flashed cwm recovery to a non-recovery partition, and system apps to a non-system partition. The trick is figuring out what partitions you overwrote. Probably ones that are not included in the stock firmware.
You need to find out what partitions hold the System and Recovery on the I9300. (ex. on our phones, System is on mmcblk0p14 and recovery is on mmcblk0p18). if their system is on p7, for example, then you would have flashed apps to our boot/kernel partition. If their Recovery is on p2, then you would have flashed CWM to our SBL1 partition which is not available in the stock firmware. It is possible to also mess up the partion layout this way as well.
Click to expand...
Click to collapse
Jesus I'm lost. I have no idea how to even start going about this. I would greatly appreciate if you can offer any help in your free time, and thank you very much for what you've given me already. Please don't forget about me :crying:
Hello everyone.
Phone Samsung Galaxy note 2 gt n7105 T mobile UK
So this morning my phone was working fine and while i was playing a game my phone literally just went dead, black screen and then stuck on galaxy note II screen.
So booted into recovery which is Philz touch 4 (had it on there for a few months so cant be more specific)
And i figured i would just do a wipe and reinstall.
But now i cant wipe cache just get error formatting /cache!
So i thought i would try just reinstalling a rom, i was using Jedi x2 rom previously so i went to try installing that, and it started to install then goes blank and reboots back to galaxy note II screen.
rebooted into recovery to check log and i get this.
I : Checking for extendedcommand & OpenRecveryScript..
I ; Skiping execution of extendedcommand. file not found
I : Using /data/media for /sdcard
w : Failed to mount /dev/block/mmcblk0p16 )invalid argument)
I :Skipping execution of OpenRecoveryScript, file not found
E : Cant't open /Cache/recovery/log
E : Cant't open /Cache/recovery/log
E : Cant't open /Cache/recovery/last_lo
E : Cant't open /Cache/recovery/log
So i thought i would just try and install stock rom via odin which failed
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
So now i dont know what to do, is my phone dead?
Please help, i tried to find info on the forums which lead me to try a few of the steps i have tried already and now im really stuck
Was your phone on updated bootloader ?
I notice your phone is N7105 what stock rom did you try to flash ?
Sent from my SGH-T889 using xda app-developers app
Can you attach screenshot with device reboot in download mod?
Sent from my SM-N900 using xda premium
dr.ketan said:
Can you attach screenshot with device reboot in download mod?
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
I have no way of taking a screen shot but ill type what it says there.
ODIN MODE
Product name : GT-N7105
Custom binary download: yes (17 counts)
Current binary: custom
System status : custom
(next 2 lines are in dark grey)
Knox warrenty void: 1
RP SWREV: A2
ciphercodes said:
Was your phone on updated bootloader ?
I notice your phone is N7105 what stock rom did you try to flash ?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Bootloader i think was fairly new, i dont know how often they update them (thats if you mean the philz touch thing?)
As for the rom, i got the lastest from SamMobile but they are classed as EE and not Tmobile ones so its possible thats why i have an issue?
Im a bit of a noob with the way Samsung and roms work. Was no problems with my old HTC.
You will have to download the exact firmware for your device N7105 and flash it using odin.
Sent from my SGH-T889 using xda app-developers app
ciphercodes said:
You will have to download the exact firmware for your device N7105 and flash it using odin.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Well i thought i already had what i needed, and since then i have tried a couple older versions too.
Unless im not even getting the correct roms/firmware.
I just get
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In odin.
nollington said:
Well i thought i already had what i needed, and since then i have tried a couple older versions too.
Unless im not even getting the correct roms/firmware.
I just get
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
In odin.
Click to expand...
Click to collapse
Your phone is on the 4.3 bootloader, do not try to flash older 4.1.x firmwares they are going to fail.
Did you try emergency recovery using KIES ?
You can also try to flash the using ODIN v 1.85.
I see that stock ROMS for N7105 on sammobile are region specific, I am not sure if flashing a ROM of incorrect region with fail but try to download the one for your region.
ciphercodes said:
Your phone is on the 4.3 bootloader, do not try to flash older 4.1.x firmwares they are going to fail.
Did you try emergency recovery using KIES ?
Try ODIN v 1.85.
I see that stock ROMS for N7105 on sammobile are region specific, I am not sure if flashing a ROM of incorrect region with fail but try to download the one for your region.
Click to expand...
Click to collapse
I dont know anything about KIES to be honest.
Ill look for a download of an older odin and try that.
As for the Roms on sammobile, i have been using the UK ones but the ones for EE since EE took over t mobile / orange. It seems thay are the only ones available
So i just found this thread on Kies
http://forum.xda-developers.com/showthread.php?t=2261153
Is this what i should try? i dont want to try it without knowing its what i should be doing.
nollington said:
So i just found this thread on Kies
http://forum.xda-developers.com/showthread.php?t=2261153
Is this what i should try? i dont want to try it without knowing its what i should be doing.
Click to expand...
Click to collapse
Yes.
Remember if your phone can go in to download mode then it can still be recovered, just need to find the right firmware.
ciphercodes said:
Yes.
Remember if your phone can go in to download mode then it can still be recovered, just need to find the right firmware.
Click to expand...
Click to collapse
Ok well so far i cant get odin to install anything. I either get an error after NAND as mentioned previously, or it gets stuck on set up connection.
Possibly a ROM/Firmware issue? but i have tried 3 different ones from sammobile all for EE UK as i cant find specific tmobile anymore.
As for what my phone can do at the moment.
It can boot into Philz touch but will reboot if you do anything like format cache/system/factory reset etc.
And can also put it into download mode with menu + volume down + power.
So i guess ill try that KIES thing and then see what happens.
If you have any other advice for me i would appreciate it.
And also thank you for your help so far
nollington said:
Ok well so far i cant get odin to install anything. I either get an error after NAND as mentioned previously, or it gets stuck on set up connection.
Possibly a ROM/Firmware issue? but i have tried 3 different ones from sammobile all for EE UK as i cant find specific tmobile anymore.
As for what my phone can do at the moment.
It can boot into Philz touch but will reboot if you do anything like format cache/system/factory reset etc.
And can also put it into download mode with menu + volume down + power.
So i guess ill try that KIES thing and then see what happens.
If you have any other advice for me i would appreciate it.
And also thank you for your help so far
Click to expand...
Click to collapse
Since you were using Philz recovery did you take a full back up ? If yes, can you try to restore it ?
If Philz is not responding as it should then try flashing Philz via ODIN.
ciphercodes said:
Since you were using Philz recovery did you take a full back up ? If yes, can you try to restore it ?
If Philz is not responding as it should then try flashing Philz via ODIN.
Click to expand...
Click to collapse
I had made a back up previously (a few months ago) and tried to install that via philz but it wouldnt even read the file.
Also tried to reflash philz via odin and it fails.
And currenctly im having issues with KIES finding my device. It just doesnt seem to want to connect to it.
So i also just saw this while trying to get a backup to work.
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p13
Error formatting /system!
Im guessing something is pretty corrupt since i cant format cache or system
nollington said:
I had made a back up previously (a few months ago) and tried to install that via philz but it wouldnt even read the file.
Also tried to reflash philz via odin and it fails.
And currenctly im having issues with KIES finding my device. It just doesnt seem to want to connect to it.
Click to expand...
Click to collapse
ok if your trying to install via the KIES software you need to be i download mode not recovery . once your in recovery mode should start seeing your device and start installing drivers or drivers might already be installed and it will ask you for device model number and serial number and will download the current OS and install . i had the same issue as you did and recover my phone via KIES hope this helps
MERK77 said:
ok if your trying to install via the KIES software you need to be i download mode not recovery . once your in recovery mode should start seeing your device and start installing drivers or drivers might already be installed and it will ask you for device model number and serial number and will download the current OS and install . i had the same issue as you did and recover my phone via KIES hope this helps
Click to expand...
Click to collapse
I have been in download mode but KIES wont connect to my phone it just sits on connecting to device for about 10 mins and then says to reboot the device. And then does the same again.
Even tried a different cable and that didnt make any difference.
ciphercodes said:
Your phone is on the 4.3 bootloader, do not try to flash older 4.1.x firmwares they are going to fail.
Did you try emergency recovery using KIES ?
You can also try to flash the using ODIN v 1.85.
I see that stock ROMS for N7105 on sammobile are region specific, I am not sure if flashing a ROM of incorrect region with fail but try to download the one for your region.
Click to expand...
Click to collapse
I flashed an EE firmware 4.3 over H3G 4.1.2 using old Odin. Works fine but you lose all internal data
Sent from my GT-I9100 using XDA Premium HD app
Im thinking it is a storage problem.
Since im having issues with cache,storage,data formatting.
I read on a thread somewhere i could have to install some .PIT?
Is there anyway to do a kind of full wipe with odin or anything? and then be able to reinstall everything such as partitions?
Those could be really noob things to ask, but im not really much of a "pro" with the phone side of things, just thinking along the lines of regular storage systems being corrupt.
nollington said:
Im thinking it is a storage problem.
Since im having issues with cache,storage,data formatting.
I read on a thread somewhere i could have to install some .PIT?
Is there anyway to do a kind of full wipe with odin or anything? and then be able to reinstall everything such as partitions?
Those could be really noob things to ask, but im not really much of a "pro" with the phone side of things, just thinking along the lines of regular storage systems being corrupt.
Click to expand...
Click to collapse
The last ODIN log you posted shows that it failed while flashing sboot.bin which is the bootloader. I think that was when you tried to flash the older firmwares.
Here is the PIT file for N7105 but I cannot assure if it work or not as I have a different phone SGH-T889.
http://forum.xda-developers.com/showthread.php?t=2137008
I do not think the partition table is messed. I still think flashing the correct firmware via ODIN should get this fixed.
Few other things to try:
You can also flash CF-Autoroot for N7105, it comes with stock recovery and then you can wipe data and perform a factory reset from there.
http://download.chainfire.eu/255/CF-Root/CF-Auto-Root/CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip
You can try flashing TWRP or CWM via ODIN and use then wipe the cache.
My girlfriend installed an OTA update and after install, it got past the Samsung screens then goes black and seemingly turns off. I have tried flashing several stock and rooted roms from XDA verified developers. I tried initially flashing CF-Auto-Root, it flashed successfully but no change in symptoms. The other stock ones I've tried same up as invalid or failed the flash. Any other ideas on this? Any help is appreciated.
Are you running the latest TWRP or CWM? What errors are you getting when the custom ROM fails?
I had two galaxy s3's AT&T both got an update
yesterday both got stuck in ATT logo boot loop
saying updating then failed but, recovery is unable
to launch the only thing usable was odin mode.
There is no stock firmware to fix it. I would bet
its the same issue.
audit13 said:
Are you running the latest TWRP or CWM? What errors are you getting when the custom ROM fails?
Click to expand...
Click to collapse
When trying to flash the rooted version, I'm getting this
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Should I check the 'Nand Erase All' option within Odin?
nightsbird said:
I had two galaxy s3's AT&T both got an update
yesterday both got stuck in ATT logo boot loop
saying updating then failed but, recovery is unable
to launch the only thing usable was odin mode.
There is no stock firmware to fix it. I would bet
its the same issue.
Click to expand...
Click to collapse
Sounds like AT&T goofed their update
***UPDATE***
After a lot of work, I not got it to boot, but now it's saying there's no sim card in it. Is this a modem issue?
What rom did you install? The aboot.mbn error tells me you were flashing a rom in Odin that was trying to downgrade the bootloader which cannot be done.
What modem and bootloader are on your phone?
audit13 said:
What rom did you install? The aboot.mbn error tells me you were flashing a rom in Odin that was trying to downgrade the bootloader which cannot be done.
What modem and bootloader are on your phone?
Click to expand...
Click to collapse
Honestly, I'm unsure on either. Is there a way I can figure out what bootloader I have? If I can figure that out I think I can get it from there.
I just got same problem todat. I have been using stock 4.3 room rooted. Now I can't pass samsung animation . I can enter only to download mod. I'm gonna try install another room by odin.
---------- Post added at 07:06 PM ---------- Previous post was at 06:16 PM ----------
So right now I can't even stand in download mod Deveci keep restarting him self even in the download mod. If there is anyone who got deal with it before please help us.
***UPDATE***
After a lot of work, I not got it to boot, but now it's saying there's no sim card in it. Is this a modem issue?
What did you do to get it to boot?
Dante411 said:
Honestly, I'm unsure on either. Is there a way I can figure out what bootloader I have? If I can figure that out I think I can get it from there.
Click to expand...
Click to collapse
I would install the latest philz for the d2lte and cm10.2 to see if the sim
is detected.
audit13 said:
I would install the latest philz for the d2lte and cm10.2 to see if the sim
is detected.
Click to expand...
Click to collapse
I'll see what I can find. Link?
I still can't pass the animation. it's restrarting even in download mod so I can't try anything by odin, what should I do guys?
Dante411 said:
I'll see what I can find. Link?
Click to expand...
Click to collapse
Link to Philz: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
CM11: https://download.cyanogenmod.org/?device=d2lte
audit13 said:
Link to Philz: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
CM11: https://download.cyanogenmod.org/?device=d2lte
Click to expand...
Click to collapse
The Philz link didn't work. Also that cyanogenmod link, is that supposed to be a custom recovery or is that just the mod?
EDIT: Just kidding, the link worked now
***UPDATE***
While trying to install the cm-11-20141120-NIGHTLY-d2lte.zip
Finding update package....
Opening Update Package....
Installing update....
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E:Error in /storage/sdcard1/cm-11-20141120-NIGHTLY-d2lte.zip
Any ideas on what that 'incompatible data' would be?
*******UPDATE*******
Nevermind, just wiped cache and it worked. Booting..
While installing CyanogenMod it came up with 'Insert SIM card'. This SIM has been tested in another phone and is working in another phone. Note that it does not explicitly tell me that I am not on a wireless network or that SIM is missing other than the initial setup. Does CyanogenMod flash a modem with it's package?
dcr4m said:
I still can't pass the animation. it's restrarting even in download mod so I can't try anything by odin, what should I do guys?
Click to expand...
Click to collapse
I would try flashing the two things he recommended. that seems like it would get you past boot. However it sounds like your phone may be in a slightly different situation since mine is not rebooting in recovery/download mode.
Cm11 does not flash a modem or bootloader.
What bootloader is on your phone?
audit13 said:
Cm11 does not flash a modem or bootloader.
What bootloader is on your phone?
Click to expand...
Click to collapse
I've been asked this before and I'm not sure how to figure that out. If you tell me how I'll certainly figure it out.
Can you boot into cm11 or any rom? If you can and your rom is rooted, download and install the samsung info app from the play store, run it, and make note of the modem and bootloader.
audit13 said:
Can you boot into cm11 or any rom? If you can and your rom is rooted, download and install the samsung info app from the play store, run it, and make note of the modem and bootloader.
Click to expand...
Click to collapse
I'm having issues downloading anything in Cyanogenmod. Doesn't have the google play store installed.
Hey XDA,
I just got my hands on Samsung Galaxy S6 Edge T-Mobile , its really an awesome phone. I am on Android 5.1.1 with baseband version G95TUVU3DOI1. I tried searching for couple of days to find a way to root the phone but was not successful. Is there a way to root S6 Edge, if not how to get back to older version of 5.1.1 android.
I have already tried to get back to older version of 5.1.1 with OH6 but had lots of errors like Enhanced feature stopped, Gapps has stopped and all kinds of other errors.
I hope anyone has the solution to root or downgrade the device.
Thank you
Right now it's impossible to downgrade, but if you don't care about KNOX, you can flash a custom kernel that has auto-root included (most do). I used UniKernel v8 over in the unified development section to obtain root, but again, THIS WILL TRIP KNOX AND BREAK SAMSUNG PAY. Worth it in my opinion, though.
is it possible to flash TWRP and run custom roms?
tehsu said:
is it possible to flash TWRP and run custom roms?
Click to expand...
Click to collapse
Yes. you should be able to flash TWPR before the kernel, and then just flash the kernel through TWRP, but I flashed the kernel first through ODIN, then ODIN flashed TWRP, so I can confirm that it works in that order. Once you've got TWRP, you can use that to flash whatever ROM you like, as long as it's compatilbe, of course.
EDIT: I'm currently running XtreStoLite 2.4 right now. Great for battery life with the included UniKernel v9, however some people are having issues with v9 so you may want to check out v8 instead. v9 works fine for me though.
Thanks, works great. For reference, I flashed unikernel then twrp then installed xtrestolite through twrp, this does void knox.
tehsu said:
Thanks, works great. For reference, I flashed unikernel then twrp then installed xtrestolite through twrp, this does void knox.
Click to expand...
Click to collapse
Awesome. Enjoy.
I'm in the same boat here. Bought a used S6 Edge and the KNOX was already tripped. However for the life of me I can't find a tutorial that could root the phone. Can anyone just provide the link for this exact version? (OI1). Also, did anyone noticed that phone is lagging a bit from time to time?
EDIT: ENABLE OEM UNLOCKING IN DEVELOPER OPTIONS
All the things I used on my OI1
Download everything, last one is the ROM if you want to flash it, its 10000x better than stock.
Put the kernel into AP and flash then put twrp into AP and flash and then flash the rom through TWRP
ODIN 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
UniKernel v8-0002 ODIN
https://www.androidfilehost.com/?fid=24052804347808101
TWRP
https://dl.twrp.me/zeroltetmo/twrp-2.8.7.1-zeroltetmo.img.tar
XtreStoLite
http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
The only reason I want the stock rom is pretty much the reason I got the phone: WiFi calling, TV remote, side night clock, etc. I managed to root the phone after bricking it this morning after flashing twrp, then flashing stock again and rooting it again. For now I'll manage without twrp since I'm not flashing roms anytime soon.
tehsu said:
All the things I used on my OI1
Download everything, last one is the ROM if you want to flash it, its 10000x better than stock.
Put the kernel into AP and flash then put twrp into AP and flash and then flash the rom through TWRP
ODIN 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
UniKernel v8-0002 ODIN
https://www.androidfilehost.com/?fid=24052804347808101
TWRP
https://dl.twrp.me/zeroltetmo/twrp-2.8.7.1-zeroltetmo.img.tar
XtreStoLite
http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
Click to expand...
Click to collapse
Thanx man it worked like a charm!!. but before doing those steps make sure you enable OEM Unlocking in developer settings.
Hello ,
i cannot get it to work,
Odin Failed to flash the kernel ... i get error on phone screen (Blocked by FRP Lock)
<ID:0/027> Added!!
<ID:0/027> Odin engine v(ID:3.1100)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> SingleDownload.
<ID:0/027> boot.img
<ID:0/027> NAND Write Start!!
<ID:0/027> FAIL!
<ID:0/027>
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Edit: Solved the problem by turning FRP lock OFF from my Developer Optiones by turning ON OEM UNLOCKING .Thanks
tehsu said:
All the things I used on my OI1
Download everything, last one is the ROM if you want to flash it, its 10000x better than stock.
Put the kernel into AP and flash then put twrp into AP and flash and then flash the rom through TWRP
ODIN 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
UniKernel v8-0002 ODIN
https://www.androidfilehost.com/?fid=24052804347808101
TWRP
https://dl.twrp.me/zeroltetmo/twrp-2.8.7.1-zeroltetmo.img.tar
XtreStoLite
http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
Click to expand...
Click to collapse
Sobaro said:
Hello ,
i cannot get it to work,
Odin Failed to flash the kernel ... i get error on phone screen (Blocked by FRP Lock)
Edit: Solved the problem by turning FRP lock OFF from my Developer Optiones by turning ON OEM UNLOCKING .Thanks
Click to expand...
Click to collapse
Thats what i mentioned in my earlier post, got to your developer settings (if you havent enable it, enable it buy tapping 7 or more times on your build number in about phone) and enable OEM Unlocking in developer settings and keep it Enable. It should work.
One last question Please, Does the rom u provided support Arabic Language not only writing but also Menus ?
Thanx in advance!
flashing TWRP
HI,
I am self teaching myself all this and I just bought a locked 925t edge I just need to know the last part how do I "flash the rom through TWRP, it's right through the phone on final reboot after ap flashing the first 2??
tehsu said:
All the things I used on my OI1
Download everything, last one is the ROM if you want to flash it, its 10000x better than stock.
Put the kernel into AP and flash then put twrp into AP and flash and then flash the rom through TWRP
ODIN 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
UniKernel v8-0002 ODIN
https://www.androidfilehost.com/?fid=24052804347808101
TWRP
https://dl.twrp.me/zeroltetmo/twrp-2.8.7.1-zeroltetmo.img.tar
XtreStoLite
http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
Click to expand...
Click to collapse
Mannon said:
HI,
I am self teaching myself all this and I just bought a locked 925t edge I just need to know the last part how do I "flash the rom through TWRP, it's right through the phone on final reboot after ap flashing the first 2??
Click to expand...
Click to collapse
Have you flashed the TWRP? If so, copy the ROM zip file to phone's internal memory, enter TWRP, then go to WIPE and do a factory reset, or manually wipe cache, system, data. After that, go to INSTALL, find your ROM zip and flash it. Then reboot the phone.
copying TWRP to phone
sorry if I seem stupid, but i am confused on the flashing of TWRP, when I flash the first 2 that would put TWRP in the phone? if not then I just need to copy it to the phones internal memory utilizing smartswitch type app??
xxhaimbondxx said:
Have you flashed the TWRP? If so, copy the ROM zip file to phone's internal memory, enter TWRP, then go to WIPE and do a factory reset, or manually wipe cache, system, data. After that, go to INSTALL, find your ROM zip and flash it. Then reboot the phone.
Click to expand...
Click to collapse
If you flashed the TWRP with ODIN successfully, then you just need to enter recovery with combination of keys: Turn off your phone. HOLD power + home + volume up keys at the same time. It will ask you to confirm and you would push Vol up again and then enter TWRP recovery.
Personally, my phone bricked after flashing TWRP and I decided not to try it again. The stock ROM is excellent and has tons of features that integrate the phone's design. All I needed is to root it.
cant see files
there is a problem I can see the files I extracted the rom image and twrp, but when I open Odin and put the phone download mode and select AP those files dont show, they are supposed to show as MD5 tar files correct. maybe I have the wrong versions for this phone model SM-G925T baseband G925TUVU2COF8 ON 5.1.1..... MY BOOTLOADER IS LOCKED SO i AM TRYING TO ROOT TO UNLOCK THE BOOTLOADER BY FLASHING A CUSTOM ROM...i AM DEF DOING SOMETHING WRONG...
xxhaimbondxx said:
If you flashed the TWRP with ODIN successfully, then you just need to enter recovery with combination of keys: Turn off your phone. HOLD power + home + volume up keys at the same time. It will ask you to confirm and you would push Vol up again and then enter TWRP recovery.
Personally, my phone bricked after flashing TWRP and I decided not to try it again. The stock ROM is excellent and has tons of features that integrate the phone's design. All I needed is to root it.
Click to expand...
Click to collapse
When add the files you will be flashing in ODIN, you should see something like this:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
Then you click START and wait for the success/fail message.
Correct files dont show to flash
YES i UNDERSTAND ALL THAT BUT i CAN CHOOSE THE FILES NEEDED TO FLASH BECAUSE THEY SHOW IN THE FOLDER SEARCH BUT NOT WHEN CONNECTED TO ODIN AND i CLICK AP, THERE THEY DONT SHOW IN ORDER TO FLASH THE PHONE...I GIVE UP...
xxhaimbondxx said:
When add the files you will be flashing in ODIN, you should see something like this:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
Then you click START and wait for the success/fail message.
Click to expand...
Click to collapse
I got my S3 from my brother since my Nexus 5 is currently broken, and with the S3 he installed CyanogenMod though it doesn't have root. So I decided to try and root it, but probably messed something up and now I'm stuck on the Cyanogen loadup screen, been waiting there for a solid 3 hours, and finally decided to try to fix it. I've tried using Odin3 3.0.7, trying to flash stock rom but I'm currently getting this error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Does anyone know what to do at this point? I've tried multiple different stock roms in case one of the stock roms had a problem. However, I flashed TWRP no problem, and I have that working for my recovery. What should I do at this point to get my phone back to Stock ROM?
Do you know what bootloader it is running? After 4.3 you cannot downgrade. Use the terminal emulator in TWRP and enter this if you're not sure:
getprop ro.bootloader
If it returns a 4.3 build number you can only flash the same or newer builds. Look for enewman17's threads in the General section for how to return to stock on those builds.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Do you know what bootloader it is running? After 4.3 you cannot downgrade. Use the terminal emulator in TWRP and enter this if you're not sure:
getprop ro.bootloader
If it returns a 4.3 build number you can only flash the same or newer builds. Look for enewman17's threads in the General section for how to return to stock on those builds.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I can't access the terminal emulator since I get stuck on the Samsung logo when trying to boot my phone.
The error happens when trying to flash aboot.mbn because, as @DocHoliday77 noted, LK3 cannot be flashed if the phone is running a 4.3 or newer bootloader.
I advise flashing TWRP and a custom ROM. This will allow you to boot the phone and determine the phone's bootloader version.
Flinze said:
I can't access the terminal emulator since I get stuck on the Samsung logo when trying to boot my phone.
Click to expand...
Click to collapse
I thought you said you had TWRP installed and working? Are you able to boot recovery at all?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
I thought you said you had TWRP installed and working? Are you able to boot recovery at all?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yes, I am able to access recovery with TWRP working, I just don't know where the terminal emulator is. (sorry i'm not very experienced w/ TWRP)
Also one thing to note, I can't install any sort of ROMS or can't flash anything through TWRM for some reason. When I swipe to flash a rom, what happens is that it just automatically goes back to the TeamWin logo page thing, and then I'm back on the home screen of TWRM (which shows all the buttons like install, wipe, backup, restore, mount, etc.) So I can't flash through TWRM, and if possible can someone link me a custom rom that supports md5, .tar, with those file extensions since the roms I've tried all are zips of .img files. (unless there is a way to convert it to md5, .tar, etc. extentions so that I can use ODIN on my computer to flash it)
edit: what I mean by md5, .tar is a PDA file so that I can use ODIN. if possible I just want my phone to run again w/ any roms... I've been phoneless for a few days now
You can find the terminal through twrp's advanced menu. Select the root folder and go from there.
Look in enewman17's NJ2 thread. He has a recovery flashable stock recovery. Try flashing that, then factory resetting from the stock recovery.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
You can find the terminal through twrp's advanced menu. Select the root folder and go from there.
Look in enewman17's NJ2 thread. He has a recovery flashable stock recovery. Try flashing that, then factory resetting from the stock recovery.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Okay, when I typed the command getprop ro.bootloader what is get is:
I747MVLDLK4
I've tried flashing the stock recovery through TWRP, but it just again doesn't work as I explained in the previous post. So I tried using ODIN to flash it after converting it into a md5 file so that ODIN can read it and now when I try to enter recovery my screen is just black.
Looks like an i747m bootloader, not i747.
http://www.sammobile.com/firmwares/download/15321/I747MVLDLK4_I747MOYADLK4_MTA/
audit13 said:
Looks like an i747m bootloader, not i747.
http://www.sammobile.com/firmwares/download/15321/I747MVLDLK4_I747MOYADLK4_MTA/
Click to expand...
Click to collapse
Oh my gosh! Thank you!!! I just followed the instructions after the download and this recovery worked! It looks like I thought my phone was i747, but it was actually i717M, thanks!!!
Glad you got your phone back.
I can't take the credit because @DocHoliday77 helped you determine the phone's bootloader.
Flinze said:
Oh my gosh! Thank you!!! I just followed the instructions after the download and this recovery worked! It looks like I thought my phone was i747, but it was actually i717M, thanks!!!
Click to expand...
Click to collapse
Glad to hear you got it going!
audit13 said:
Glad you got your phone back.
I can't take the credit because @DocHoliday77 helped you determine the phone's bootloader.
Click to expand...
Click to collapse
Don't even worry about cred on this stuff man! You do plenty enough to be just as deserving! @dawgdoc too!
And tbh, I'm really glad you chimed in on that one! Since I'm not as familiar with which variant has which build number for the I747/I747M, (and since I'm usually used to just glancing at the last 3 characters), it probably would've taken me another 2 or 3 posts to have realized that was the problem. I Definately didn't catch it that first time!
So in the spirit of giving credit where it's due, you do deserve it here and in many, many other threads! Thanks!
Sent from my SGH-T999 using Tapatalk