Related
Hello friends.
I installed Xposed (http://forum.xda-developers.com/showthread.php?t=1574401) and now my shiny new S4 won't boot (stuck at Samsung logo).
According to the docs, I need only copy /system/bin/app_process.orig back to /system/bin/app_process but alas I cannot because my stock recovery is not letting me adb shell, reporting the device is offline. Note that adb devices shows the device as connected but offline.
Since there's no working TWRP or CWM (yet!!) I think I'm stuck.
If someone else can unlock me in the mean time. I'll buy you a beer or TWENTY. That's a promise.
Don't know whether it still works, but other SS phones have a save mode boot.
To enter it, you have to power off your phone first. Next, turn it on while holding the menu button and keep menu pressed until you see your homescreen.
hope it works.
Thanks for the reply! Nope. Tried the home button and the menu button. No cigar.
can you enter download mode?
Try and find something like the nexus root tool kit.....maybe there is one like it for Galaxy phones.
Its a great tool for such a thing, it helps you root, un root, lock, unlock, flash and re flash stock, it aslo lets you pick if phone is working as normal or is it soft bricked., and thats what saved my nexus 7 and 10 lol was stuck with bootloops and not able to get into recovery mode.
Anyway have a look see if there is something like that but for Samsung Galaxy.
Have a look at this, used it to flash s3 in the past, unsure what it can do s4 way though. http://forum.xda-developers.com/showthread.php?t=1703488
Thanks for replies.
Yes! I can get into download mode.
There is an S4 toolkit but it's early days and apparently doesn't actually work. I figure with time, a custom recovery will emerge and that will save the day. I'm sure I don't need to explain that I would like this fixed NOW without waiting tho!
bonstio said:
Hello friends.
I installed Xposed (http://forum.xda-developers.com/showthread.php?t=1574401) and now my shiny new S4 won't boot (stuck at Samsung logo).
According to the docs, I need only copy /system/bin/app_process.orig back to /system/bin/app_process but alas I cannot because my stock recovery is not letting me adb shell, reporting the device is offline. Note that adb devices shows the device as connected but offline.
Since there's no working TWRP or CWM (yet!!) I think I'm stuck.
If someone else can unlock me in the mean time. I'll buy you a beer or TWENTY. That's a promise.
Click to expand...
Click to collapse
Download firmware for Odin from Samsung-Updates or use Pre-Rooted OFFICIAL Rom from here
Turn OFF your phone, press&hold POWER+HOME+VOL_DOWN to enter Odin/Download Mode.
Connect your phone to the computer, use Odin3 v3.04 , load firmware as PDA, make sure that ONLY AutoReboot&F.Reset Time is ticked and click START.
After 5 minutes, all done, it should be back to life...
enjoY
Just flash a Official stock firmware and you will boot normally again.
Download a stock firmware
Download odin
Enter download mode in you unit by pressing power and volume down and home button.
Connect the device to your pc, wait for drivers to install.
Select your unzipped firmware (yeah the .md5 file) in the PDA section
Now start flashing and wait...your phone should boot as normal.
That is about it
no donation required btw...
download mode is great news. now get odin + stock firmware and flash your s4 back to life be aware, that all your data is most likely to be lost in the process.
a small price to pay if you ask me.
As others said, if you can get to download mode then be ready to have babies and fall in love with Odin, another life saver.
voodoochild2008 said:
As others said, if you can get to download mode then be ready to have babies and fall in love with Odin, another life saver.
Click to expand...
Click to collapse
Thanks guys. On the download. Server seems slow. Great to know that it's recoverable. I'll update when I'm up and running again.
djembey said:
Download firmware for Odin from Samsung-Updates or use Pre-Rooted OFFICIAL Rom from here
Turn OFF your phone, press&hold POWER+HOME+VOL_DOWN to enter Odin/Download Mode.
Connect your phone to the computer, use Odin3 v3.04 , load firmware as PDA, make sure that ONLY AutoReboot&F.Reset Time is ticked and click START.
After 5 minutes, all done, it should be back to life...
enjoY
Click to expand...
Click to collapse
SORTED. Thanks to everyone for jumping on board! djembey, mail me your PayPal for your reward or alternatively a shipping address and what color your S4 is. Which ever you prefer.
Thanks again.
bonstio said:
SORTED. Thanks to everyone for jumping on board! djembey, mail me your PayPal for your reward or alternatively a shipping address and what color your S4 is. Which ever you prefer.
Thanks again.
Click to expand...
Click to collapse
I'm happy for you! Next time be more careful with your new Baby
I've got white i9505 and love it to the bits (my first white phone...)
Under my avatar you'll see "DONATE TO ME" ..... if you want to....
Did you try my Pre-Rooted Rom?? If not, you should
djembey said:
I'm happy for you! Next time be more careful with your new Baby
I've got white i9505 and love it to the bits (my first white phone...)
Under my avatar you'll see "DONATE TO ME" ..... if you want to....
Did you try my Pre-Rooted Rom?? If not, you should
Click to expand...
Click to collapse
You just got a donation my friend!
Didn't try the prerooted... didn't see it for I9505XXUAMDF. Still, I'm used Chainfire's root and I'm back in business. No apps or data were wiped after the flash either, much to my surprise.
Waiting now for a working recovery and a decent ROM, like a Paranoid Android or CM10.1 port. In the mean time, I'm putting up with the TouchWiz jank + 320 DPI in spite of the odd scaling of some apps.
Cheers.
bonstio said:
You just got a donation my friend!
Didn't try the prerooted... didn't see it for I9505XXUAMDF. Still, I'm used Chainfire's root and I'm back in business. No apps or data were wiped after the flash either, much to my surprise.
Waiting now for a working recovery and a decent ROM, like a Paranoid Android or CM10.1 port. In the mean time, I'm putting up with the TouchWiz jank + 320 DPI in spite of the odd scaling of some apps.
Cheers.
Click to expand...
Click to collapse
Thanks a LoT! ) Appreciated
There's XXUAMDF on the list but it will give you just basic root permissions, no access to the system... In your case better use CF as it will give you full access..
Anyway, be more careful in future and enjoy it
S4 i9500 (I9500XXUAMDK with root) has soft brick
Dear friends. I would like your help, if possible! Please!
I did the actualization on my S4 i9500 (I9500XXUAMDK, with root) and after this, I was trying to put more space in sdcard (editing vold fstab files to try to change extSdCard into sdcard).
During this process, appeared a message on the phone about one error there is in sdcard and it suggested me to unmount the sdcard to try solve the problem. So, when I click yes, the phone froze and then I turned it off, but it stock now in Sangung Logo and go to recovery mode. In recovery mode I tryed to clear/mount/unmount any file, but it returns with error to mount any directories.
I think the phone has the files or some partition corrupted!!! . I can access it through ODIN and adb shell as well. There is (in adb commands) a command to fix the partition? How can I do?
With ODIN, I tried to re-install the original FW. It did well (complete the re-install perfectly), but the phone cant finish the instalation after this, because it cant mount anything, and goes to recovery mode with many messages about that it cant mount directories (list a vary directories that wasnt mounted correct).
Everything I try to do, the phones (in recovery mode) returns "cant mount... or error to mount something". I cant too clear cache, format /sdcard or other directory, or reset it to the factory data as well (because I think, the system cant mount any directories).
Somebody had this problem? or could help me to solve it, please!!!
Tks in advance!
Barros
Hello
My S4 (XUBMGA) wont boot, it kept crashing so i used Odin to fresh install the OS, but it wouldnt let me enter recovery mode after so then I googled and found this website which gave me steps to recover my OS via Odin and also re-partion the recovery mode via a PIT File.
Now my S4 wont boot (stays stuck on the Samsung 9505 logo) and when i try enter recovery the blue text 'Recovery Boot' or something stays there but it wont enter. The phone doesnt boot up but I can still enter download mode?
What can i do! Also im a newb at this so simple please
Thanks in advance!
Get a stock rom from Samfirmware, flash it with Odin. That's the only way you're fixing it. How ? Search.
MistahBungle said:
Get a stock rom from Samfirmware, flash it with Odin. That's the only way you're fixing it. How ? Search.
Click to expand...
Click to collapse
I did i downloaded the BTU United Kingdom Version but im not 100% sure which one to download? I bought the phone unlocked over eBay so im not sure which firmware to download exactly? I cant turn the phone on and go to about device as it wont boot to check all the numbers. Im sure it ended in MGA though
Any help?
BUMP
1) You absolutely do not bump threads after 25 minutes. This isn't your personal technical support hotline :-|
2) It makes no difference which firmware you use, as long as you use one for your specific model, tho I personally would use the latest one my carrier has released (if there was more than one). You may prefer to use an unbranded one for your country if there is one (I have no idea if there is/isn't one of these for the UK).
If you want to fix this, it's going to take a bit of effort on your part, we can't do it for you.
Edit - You really need to learn 'the basics' (people need to do this before they start messing with their phones, not after they bork them). Once you've fixed it, read the Stickies before you bork it permanently.
MistahBungle said:
1) You absolutely do not bump threads after 25 minutes. This isn't your personal technical support hotline :-|
2) It makes no difference which firmware you use, as long as you use one for your specific model, tho I personally would use the latest one my carrier has released (if there was more than one). You may prefer to use an unbranded one for your country if there is one (I have no idea if there is/isn't one of these for the UK).
If you want to fix this, it's going to take a bit of effort on your part, we can't do it for you.
Edit - You really need to learn 'the basics' (people need to do this before they start messing with their phones, not after they bork them). Once you've fixed it, read the Stickies before you bork it permanently.
Click to expand...
Click to collapse
I have and am trying. Im new to Samsung, just moved after years of iPhone, hence though rooting would be similar to jailbreaking the iPhone.
Ive tried multiple ROMs now using Odin 3.07, it says it passes etc but the phone stays on the Samsung Galaxy S4 logo, it doesnt still let me enter recovery mode, but allowss me to get into download mode.
Any advice? Thanks
Download the last Twrp recovery(tar format) for your phone from their website flash it with odin 3.07
Noticeut your tar file with PDA
uncheck the reboot box.let only the reset box checked.
Don't check for any reason the partition case.
GO to download mode with your phone:hold down volume+power+home
After volume +button to continue
You are now on the download mode.connect your phone to your computer
If the box in the left corner become blue .it ok
If in the message box you see "added".it ok
Now press the start (the button to begin the process)
Wait till you will see PASSED in the left upper case.(take around 2min)
Unplung your phone,remove the battery.
Reput the battery and swicht on your phone :hold hight volume+home+power
2nd notice:when you see the samsung logo appear for the first time and going,remove your hand and you will see the beautiful twrp interface.
By the way,you should already have download SuperSu 1.51 and put that somewhere In your extsd card.
Go to install(always in the twrp recovery)
And select the Super su 1.51 or 1.41,cause they are stable)(you know the path where you will put the SuperSu app)
Installation succefull.touch the reboot button on the interface .your phone will reboot and you will see this mesage "Android upgrading"
Ok.i think you have understood.
Sent from my GT-I9500 using xda app-developers app
Minou32 said:
Download the last Twrp recovery(tar format) for your phone from their website flash it with odin 3.07
Noticeut your tar file with PDA
uncheck the reboot box.let only the reset box checked.
Don't check for any reason the partition case.
GO to download mode with your phone:hold down volume+power+home
After volume +button to continue
You are now on the download mode.connect your phone to your computer
If the box in the left corner become blue .it ok
If in the message box you see "added".it ok
Now press the start (the button to begin the process)
Wait till you will see PASSED in the left upper case.(take around 2min)
Unplung your phone,remove the battery.
Reput the battery and swicht on your phone :hold hight volume+home+power
2nd notice:when you see the samsung logo appear for the first time and going,remove your hand and you will see the beautiful twrp interface.
By the way,you should already have download SuperSu 1.51 and put that somewhere In your extsd card.
Go to install(always in the twrp recovery)
And select the Super su 1.51 or 1.41,cause they are stable)(you know the path where you will put the SuperSu app)
Installation succefull.touch the reboot button on the interface .your phone will reboot and you will see this mesage "Android upgrading"
Ok.i think you have understood.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply.
I followed your steps and also a youtube video but when my phone reboots and you have to enter recovery mode (to get to TWRP) it doesnt go beyond the blue font at the top left and the samsung logo. It stays there
Any advice mate
Thanks
bump - im desperate to get this sorted
hus2k7 said:
bump - im desperate to get this sorted
Click to expand...
Click to collapse
Bump
I think you 1.didn't check the reboot box
2.you removed the batterie after seing the passed message
3.and you removed your hand (all)after the samsung logo disapear
4.you download the last twrp for you model.
What is your phone model in fact?
If you want to see that go to 1.setting
2.more
3.about device
Mine is gt-i9500 simply
No at
No lce or others ones
Sent from my GT-I9500 using xda app-developers app
I get model mismatch every single time, I have downloaded the right firmware.. Downloaded the one said to do 5 DIFFERENT ONES that are all essentially the same, I rooted succesffully, then tried to flash xposed and failed obv.
.."Stock-S7-EDGE-ATT_G935AATT2APG1.zip"
"AP_G935AUCS2APF2_CL7617530_QB9897831_REV02_user_low_ship_MULTI_CERT.tar.md5"
Etc. Idk what to do anymore, stuck in download or recovery mode.
"Downloaded the one said to do 5 DIFFERENT ONES that are essentially the same," what does that mean? You downloaded the firmware zip file that had 5 seperate files in it, and they're all essentially the same? See how you quoted one of the files inside? Notice how it starts with "AP"? In odin, you click the AP button, then add that file in that AP slot. Then the one that starts with "BL" in the BL slot, and so on and so forth, until you have all 5 files in their respective slots. THEN you start the flashing process. Did you do that? If that didn't work, did you make sure the md5 number listed at the download screen match after you downloaded the zip file? Do you have an md5 checksum program on your computer? You can easily find a free one by doing a quick google search. You could also maybe try downloading and flashing a different/newer stock AT&T firmware.
As for xposed, you first need to download and install this version of the xposed apk from the xposed website: XposedInstaller_3.0_alpha4.apk
Then, if/when rooted find and flash this version of xposed framework in flashfire:
xposed-v85.1-sdk23-arm64-custom-build-by-wanam-20160530.zip
If you're not having any luck, and your phone is still stuck in download or recovery mode, you can still power it off for the time being using the following steps:
If it's in recovery mode, you'll have options listed, like "reboot system now," and, "power off device." You can toggle through each choice using the volume up and down buttons, and once you highlight the one you want, hit the power button to select it. You can go to "power off device" in recovery mode and turn your phone off for now if you don't want to have to worry about it. If your phone is in download mode, it'll either be at the warning screen where you can hit volume up to continue, or volume down to cancel and restart the phone. If it is all the way in download mode, it'll say "downloading... do not turn off target !!" If it is on the warning screen, just continue into into download mode. If it is in download mode already, or you just continued into download mode, and you want to turn the phone off, press and hold volume up, volume down, power, and home button and hold them all down at the same time until the phone shuts off. Immediately after, let go of all the buttons, and then press and hold the volume up, home, and power buttons until the phone comes back on, and in the top left corner, in blue, it'll say "Recovery booting." It is then that you let go of all the buttons. You will enter recovery there and be able to power the device off.
Anyway, I hope you already got it fixed, and if not, I hope this information helped. I'm not trying to be mean, but you really need to search through all of the forums, read everything, read people's comments for information on how to do these sort of things properly, and how to fix the problems. Rooting, installing custom roms and xposed is a little different on newer devices now. Mistakes can be much more costly now than they used to be, so unless you've read thoroughly on such processes, and/or have found a youtube video that helps and you're feeling confident about it, you might want to reconsider attempting to apply these kinds of changes to your phone. If you have any friends that are good at this stuff, maybe that would be another way as well. Anyway, best of luck to you.
Try Odin 3.12.3 or PrinceComsy version It work for me. My case was that I upgrade to the firmware 935u version bootloader v4 and I wanted go back to PH1 that the bootloader is v2. Make sure to do factory reset before do any flash with odin (I don't know if that matter but works for me). Hope this work for you.
xjimmy said:
"Downloaded the one said to do 5 DIFFERENT ONES that are essentially the same," what does that mean? You downloaded the firmware zip file that had 5 seperate files in it, and they're all essentially the same? See how you quoted one of the files inside? Notice how it starts with "AP"? In odin, you click the AP button, then add that file in that AP slot. Then the one that starts with "BL" in the BL slot, and so on and so forth, until you have all 5 files in their respective slots. THEN you start the flashing process. Did you do that? If that didn't work, did you make sure the md5 number listed at the download screen match after you downloaded the zip file? Do you have an md5 checksum program on your computer? You can easily find a free one by doing a quick google search. You could also maybe try downloading and flashing a different/newer stock AT&T firmware.
As for xposed, you first need to download and install this version of the xposed apk from the xposed website: XposedInstaller_3.0_alpha4.apk
Then, if/when rooted find and flash this version of xposed framework in flashfire:
xposed-v85.1-sdk23-arm64-custom-build-by-wanam-20160530.zip
If you're not having any luck, and your phone is still stuck in download or recovery mode, you can still power it off for the time being using the following steps:
If it's in recovery mode, you'll have options listed, like "reboot system now," and, "power off device." You can toggle through each choice using the volume up and down buttons, and once you highlight the one you want, hit the power button to select it. You can go to "power off device" in recovery mode and turn your phone off for now if you don't want to have to worry about it. If your phone is in download mode, it'll either be at the warning screen where you can hit volume up to continue, or volume down to cancel and restart the phone. If it is all the way in download mode, it'll say "downloading... do not turn off target !!" If it is on the warning screen, just continue into into download mode. If it is in download mode already, or you just continued into download mode, and you want to turn the phone off, press and hold volume up, volume down, power, and home button and hold them all down at the same time until the phone shuts off. Immediately after, let go of all the buttons, and then press and hold the volume up, home, and power buttons until the phone comes back on, and in the top left corner, in blue, it'll say "Recovery booting." It is then that you let go of all the buttons. You will enter recovery there and be able to power the device off.
Anyway, I hope you already got it fixed, and if not, I hope this information helped. I'm not trying to be mean, but you really need to search through all of the forums, read everything, read people's comments for information on how to do these sort of things properly, and how to fix the problems. Rooting, installing custom roms and xposed is a little different on newer devices now. Mistakes can be much more costly now than they used to be, so unless you've read thoroughly on such processes, and/or have found a youtube video that helps and you're feeling confident about it, you might want to reconsider attempting to apply these kinds of changes to your phone. If you have any friends that are good at this stuff, maybe that would be another way as well. Anyway, best of luck to you.
Click to expand...
Click to collapse
I did all of this, except for the check md5thing, will try this today.
Yeah so im pretty sure my phone is done for good, I have literally tried to flash every stock firmware, blah blah there is. ik to put Bl with bl ap with ap etc. lol it used to be so easy...
brandonjames1212 said:
Yeah so im pretty sure my phone is done for good, I have literally tried to flash every stock firmware, blah blah there is. ik to put Bl with bl ap with ap etc. lol it used to be so easy...
Click to expand...
Click to collapse
What are you flashing FROM? From what you listed in the OP, you are trying to flash to APG1? What the device is on now could be on a newer firmware
kangi26 said:
What are you flashing FROM? From what you listed in the OP, you are trying to flash to APG1? What the device is on now could be on a newer firmware
Click to expand...
Click to collapse
I honestly dnt knnow what the phone originally was, I forgot, but i have tried pg1 Pf2 pb4.. atleast those are some of the files i have tried.. cant find any others.. currently about to try ph1
Ph1 failed too.
idk if this helps anything, but Here is exactly what it says on my download mode
"ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FAP LOCK: ON
WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE
AP SWREV: B4(2,1,1,1,1) K1 S3
SECURE DOWNLOAD: ENABLE
brandonjames1212 said:
I honestly dnt knnow what the phone originally was, I forgot, but i have tried pg1 Pf2 pb4.. atleast those are some of the files i have tried.. cant find any others.. currently about to try ph1
Ph1 failed too.
idk if this helps anything, but Here is exactly what it says on my download mode
"ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FAP LOCK: ON
WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE
AP SWREV: B4(2,1,1,1,1) K1 S3
SECURE DOWNLOAD: ENABLE
Click to expand...
Click to collapse
If you are trying to flash the stock ROM and you are on different bootloaders you are going to run into issues. I THINK (and could be wrong), you may be on version 4 (based off of the "AP SWREV: B4(2,1,1,1,1) K1 S3") again, I'm not positive on my assumption here, but, if that's the case you need to flash a stock ROM that is on version 4 of the bootloaders, something like G935AUCS4API2 (BL4)
kangi26 said:
If you are trying to flash the stock ROM and you are on different bootloaders you are going to run into issues. I THINK (and could be wrong), you may be on version 4 (based off of the "AP SWREV: B4(2,1,1,1,1) K1 S3") again, I'm not positive on my assumption here, but, if that's the case you need to flash a stock ROM that is on version 4 of the bootloaders, something like G935AUCS4API2 (BL4)
Click to expand...
Click to collapse
Thank you for responding, but I did download that one yesterday and tried that one too.. got the same error sadly ;/
brandonjames1212 said:
Thank you for responding, but I did download that one yesterday and tried that one too.. got the same error sadly ;/
Click to expand...
Click to collapse
If you go into Recovery Mode, you should be able to see what ROM you are on. From there, I'd do a system wipe like xjimmy suggested, power off, boot to Download mode, and try to flash the ROM that has matching bootloader
kangi26 said:
If you go into Recovery Mode, you should be able to see what ROM you are on. From there, I'd do a system wipe like xjimmy suggested, power off, boot to Download mode, and try to flash the ROM that has matching bootloader
Click to expand...
Click to collapse
Android recovery
MMB29M.G935AUCS4API2
samsung/hero2qlteuc/hero2qlteatt
6.0.1/MMB29M/G935AUCS4API2
I factory reset, But can you refer me to what i should download for the above.. tired of downloading wrong file and all.. lol have downloaded over 13gb worth of files.. dnt wanna fail again
Lol i see pi2... ive already done that one tho, but as he said before, i reset this time and gonna try again.. already have files for that one.. so about to try
brandonjames1212 said:
Android recovery
MMB29M.G935AUCS4API2
samsung/hero2qlteuc/hero2qlteatt
6.0.1/MMB29M/G935AUCS4API2
I factory reset, But can you refer me to what i should download for the above.. tired of downloading wrong file and all.. lol have downloaded over 13gb worth of files.. dnt wanna fail again
Click to expand...
Click to collapse
So you are on V4 Bootloaders, and API2, which is the current stock release.
I would
Download the stock API2 ROM from HERE and put them all on your desktop
Open Odin
In Recovery mode, wipe the device
Restart the phone in Download Mode then plug the phone into the PC
Put the downloaded files to their slots in Odin, and hit start
kangi26 said:
So you are on V4 Bootloaders, and API2, which is the current stock release.
I would
Download the stock API2 ROM from HERE and put them all on your desktop
Open Odin
In Recovery mode, wipe the device
Restart the phone in Download Mode then plug the phone into the PC
Put the downloaded files to their slots in Odin, and hit start
Click to expand...
Click to collapse
That is the exactly files i have currently trying again now that i reset phone.
OMG thank you guys so much, after a thousand tries.. it ended up being the files you linked (Which were the original files i used the very first time) I just never did the factory reset!!! after doing the reset and trying again!! its currently started actually through the process, instead of saying model mismatch ! hopefully it does the entire thing with no errrors!! THANK YOU GUYS SO MUCH...
brandonjames1212 said:
OMG thank you guys so much, after a thousand tries.. it ended up being the files you linked (Which were the original files i used the very first time) I just never did the factory reset!!! after doing the reset and trying again!! its currently started actually through the process, instead of saying model mismatch ! hopefully it does the entire thing with no errrors!! THANK YOU GUYS SO MUCH...
Click to expand...
Click to collapse
Excellent!
kangi26 said:
If you are trying to flash the stock ROM and you are on different bootloaders you are going to run into issues. I THINK (and could be wrong), you may be on version 4 (based off of the "AP SWREV: B4(2,1,1,1,1) K1 S3") again, I'm not positive on my assumption here, but, if that's the case you need to flash a stock ROM that is on version 4 of the bootloaders, something like G935AUCS4API2 (BL4)
Click to expand...
Click to collapse
Yes I'm trying to flash the stock firmware but I flashed the rooted bootloader in Odin I think, lol so that may be why I'm having issues. Cause mine fails every single time for the att version and it's driving me nuts and I can't find any video tutorial on it at all, and smart switch won't work with the att one lol Dicks
kshansen7692 said:
Yes I'm trying to flash the stock firmware but I flashed the rooted bootloader in Odin I think, lol so that may be why I'm having issues. Cause mine fails every single time for the att version and it's driving me nuts and I can't find any video tutorial on it at all, and smart switch won't work with the att one lol Dicks
Click to expand...
Click to collapse
Did you do a Factory Reset in Recovery first?
kangi26 said:
Did you do a Factory Reset in Recovery first?
Click to expand...
Click to collapse
No I haven't I'm about to and I'll let you know what happens
kangi26 said:
Did you do a Factory Reset in Recovery first?
Click to expand...
Click to collapse
OK did a reset wiped her out set it up and wallllllaaaa it's fixed golden!! You sir helped a bunch thanks again this thread saved my nuggets
kshansen7692 said:
OK did a reset wiped her out set it up and wallllllaaaa it's fixed golden!! You sir helped a bunch thanks again this thread saved my nuggets
Click to expand...
Click to collapse
Sorry to come back to the party so late. Things have been hectic here. I'm glad these guys were able to get you all fixed up.
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
bothambhai said:
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Click to expand...
Click to collapse
just checking... are you using the edited princecomsy odin? http://d-h.st/gsDA or use the link here https://forum.xda-developers.com/att-s7-edge/help/princes-odin-t3545104
find the correct rom here https://forum.xda-developers.com/sprint-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3569834
just use files from one rom at a time. get good at that first. maybe you are careful but it really looks like you were guessing what goes where at the end of your post.
i just have tips on what helped me. passing along the info and the link.
epikroms said:
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
Click to expand...
Click to collapse
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
bothambhai said:
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
Click to expand...
Click to collapse
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
epikroms said:
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
Click to expand...
Click to collapse
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
bothambhai said:
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
Click to expand...
Click to collapse
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
epikroms said:
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
Click to expand...
Click to collapse
Thanks for your reply. If it is not too much can you please break down the steps a bit more because I don't want to guess and mess it up again and also if you could please kindly point me to the other thread as well so I can download the appropriate stuff from there and read a bit more about it. I am right now unable to use the phone with the sprint firmware on it on TMo, it's super annoying.
Thanks in advance.
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Did you get it sorted out? Hopefully you are on the rom and haven't bricked your device. I attached a picture so you could see that I am on what I say I am on.
epikroms said:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Click to expand...
Click to collapse
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
bothambhai said:
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
Click to expand...
Click to collapse
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
thats pretty interesting being on the binary 5 baseband and binary 4 rom. to clarify, you were on the binary 5 rom and reverted? or were you on the baseband 4 and upgraded just the baseband? thanks for the info.
epikroms said:
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
Click to expand...
Click to collapse
I odined the AP_Nougat_S7_Edge_EngBoot.tar.md5 then ran the root.bat file from Nougat_S7_Root_2_82_All_Carriers_V2 , I chose the options to install the fingerprint fix and install the root without any gpu tweaks. I watched the whole process complete and the cmd prompt close, my phone never asked my permission to ALLOW anything, everything was on the computer. I ran the root.bat from cmd as an administrator and the program ran evidently because it asked me about the fingerprint fix and root with or without tweaks etc. I noticed the phone reboot and there was a notification, the phone was rooted but no SU and flashwire says no root access. I tried it back from square one a couple of tries more right back from flashing stock sprint firmware and trying the whole rooting process again, same results except the next two times the phone doesn't reboot after running the root.bat file. I notice now when the phone boots up there is a sign saying "CUSTOM" beneath the samsung logo on the screen. I don't know where I am going wrong in the process though. I don't know if it is because I am on the binary 5 however I also read somewhere that people have been successful in rooting their binary 5 sprint S7 edges. I have rooted many devices before and installed roms etc, this has been, by far, the most perplexing phone in every which way.
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
epikroms said:
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
Click to expand...
Click to collapse
Bummer about your phone. On a glad note I managed to root and flash my phone and everything works great now. I was taking the hard nerdy way to do it by running cmd as an administrator and having that run the root.bat file. I read somewhere else you could just double click the file and it worked for me . From there on the aroma part was pretty straightforward. I am grateful to you for pointing me in this direction and breaking it down for me, I seriously doubted me being able to achieve this on my binary 5 phone but it turned out to be smooth.
I do wish you the best and thanks once again.
SM-N9005 with stock Lollipop
Using Odin 3.09 to flash N9005 (with working, stock Lollipop ) with TWRP 3.3.1.0 (hlte) - get success message however on reboot after message "set warranty bit : recovery" the device boots to Lollipop. No boot loop however on subsequent reboots I still have stock recovery with Odin mode then reporting custom install (previously stock). So it appears to be installing OK but just not defeating the stock recovery reversion. Tried also removing battery after install message on Odin before reboot however same issue.
Subsequently tried multiple variations of Odin 3.12, TWRP 2.8.7 and a different, known clean Windows OS on a different device - no change. . Same issue with reflashing stock ROM although it does appear to be installing stock Lollipop on finishing the install on the device it just reboots to the existing install. Odin mode still reports install as custom.
Any thoughts ?
There's a file on /system named "recovery-from-boot.p", it reverts stock recovery back whenever it checks a non-stock recovery installed.
Removing that file should fix your problem.
It won't harm you.
Mohamedkam000 said:
There's a file on /system named "recovery-from-boot.p", it reverts stock recovery back whenever it checks a non-stock recovery installed.
Removing that file should fix your problem.
It won't harm you.
Click to expand...
Click to collapse
Thanks - found it via adb however since I don't have root access I can't get further forward.
Can anyone suggest a way forward please ?
I have got a stock BT firmware from Sammobile and will reflash to stock.
Next step will be to try installing TWRP again.
mrwibble3bw said:
Thanks - found it via adb however since I don't have root access I can't get further forward.
Can anyone suggest a way forward please ?
Click to expand...
Click to collapse
Easy, falsh twrp, boot into twrp recovery, mount system, go to file manager and browse to that file, and remove it.
Or use adb from recovery maybe.
mrwibble3bw said:
I have got a stock BT firmware from Sammobile and will reflash to stock.
Next step will be to try installing TWRP again.
Click to expand...
Click to collapse
Update : Managed to get back to official status via Sammobile stock firmware, used Odin 3.09 to reflash twrp however same result - no twrp installed. Recovery boot signals "Set Warranty Bit : recovery" and then reboots to Lollipop.
I can adb into the phone afterwards and see it has a read-only file structure so can't rename recovery-from-boot.p. Bootloader version is N9005XXSGBRI2.
Rebooting into recovery again gives the same results - no stock recovery or twrp.
Not sure where to go now.
Multiple post on this Failed TWRP problem .
Unable to flash on some phones for unknown reason .
Look in the TWRP thread and search q&A .
You may have tried this but . . .
Flash TWRP 2.8.7 via Odin.
Then you have to be quick . . .As soon as the phone tries to reboot hold and press Volume Up + Home button + Power button (Entry to recovery button combination).
I tried it a couple of times and finally got TWRP installed.
grwalker said:
You may have tried this but . . .
Flash TWRP 2.8.7 via Odin.
Then you have to be quick . . .As soon as the phone tries to reboot hold and press Volume Up + Home button + Power button (Entry to recovery button combination).
I tried it a couple of times and finally got TWRP installed.
Click to expand...
Click to collapse
Bingo ! Worked first time with 2.8.7 !!!!
Now I am on the road to Pie ...
Thanks
mrwibble3bw said:
Bingo ! Worked first time with 2.8.7 !!!!
Now I am on the road to Pie ...
Thanks
Click to expand...
Click to collapse
I would be very interested to hear if you have success with flashing a version of TWRP greater than 2.8.7, which you need to be able to flasha Pie ROM. (using the same method you did for 2.8.7)
I found that whilst Odin reports a successful flash of a version of TWRP greater than 2.8.7, the phone goes into a bootloop. I was only able to flash 2.8.7, nothing higher, no matter what i did. (I have the hlte). That meant i couldn't flash a ROM greater than 7.0
grwalker said:
I would be very interested to hear if you have success with flashing a version of TWRP greater than 2.8.7, which you need to be able to flasha Pie ROM. (using the same method you did for 2.8.7)
I found that whilst Odin reports a successful flash of a version of TWRP greater than 2.8.7, the phone goes into a bootloop. I was only able to flash 2.8.7, nothing higher, no matter what i did. (I have the hlte). That meant i couldn't flash a ROM greater than 7.0
Click to expand...
Click to collapse
Finally found why I can't flash - I replaced a defective screen with one from a non N9005 Note 3. See https://forum.xda-developers.com/showpost.php?p=80756445&postcount=522 for further info.
I replaced my screen (or rather the whole upper unit including the display) about a year ago with one from a non N9005 Note 3 - think it was a US unit - after I got water on it at the beach. These replacement units are very competitively priced - assume they are from Chinese recycling of old units around the world - but they don't let you choose the Note 3 model. It has worked fine with stock so the issue was hidden until I tried flashing TWRP.
Sadly it looks like I am restricted to 7.1 until / unless I source an N9005 upper unit. Very frustrating.
mrwibble3bw said:
Finally found why I can't flash - I replaced a defective screen with one from a non N9005 Note 3. See https://forum.xda-developers.com/showpost.php?p=80756445&postcount=522 for further info.
I replaced my screen (or rather the whole upper unit including the display) about a year ago with one from a non N9005 Note 3 - think it was a US unit - after I got water on it at the beach. These replacement units are very competitively priced - assume they are from Chinese recycling of old units around the world - but they don't let you choose the Note 3 model. It has worked fine with stock so the issue was hidden until I tried flashing TWRP.
Sadly it looks like I am restricted to 7.1 until / unless I source an N9005 upper unit. Very frustrating.
Click to expand...
Click to collapse
Thanks for the info. I did the same thing about a year ago. Bought a replacement LCD on ebay from UK reseller. Info was that it was a 9005 unit, but i guess not. Would be interesting to know the difference between a "fake" LCD and an original and how to tell.
grwalker said:
Thanks for the info. I did the same thing about a year ago. Bought a replacement LCD on ebay from UK reseller. Info was that it was a 9005 unit, but i guess not. Would be interesting to know the difference between a "fake" LCD and an original and how to tell.
Click to expand...
Click to collapse
I'm fairly certain that my old one had "LTE" moulded into the frame on the reverse whereas the current one had something else. It worked fine in stock which was all it needed to do. I would imagine phones sent in for recycling are split in China and it would be pot luck which one you get. I know that I raised it with the eBay vendor (also in UK) and he could not guarantee the model.
If you look at current eBay UK listings they all have images with LTE prominently displayed on the frame reverse so I am mulling another swap.
mrwibble3bw said:
I'm fairly certain that my old one had "LTE" moulded into the frame on the reverse whereas the current one had something else. It worked fine in stock which was all it needed to do. I would imagine phones sent in for recycling are split in China and it would be pot luck which one you get. I know that I raised it with the eBay vendor (also in UK) and he could not guarantee the model.
If you look at current eBay UK listings they all have images with LTE prominently displayed on the frame reverse so I am mulling another swap.
Click to expand...
Click to collapse
Thanks
I checked mine. the original screen had LTE moulded in to the case. And so did the replacement.
grwalker said:
Thanks
I checked mine. the original screen had LTE moulded in to the case. And so did the replacement.
Click to expand...
Click to collapse
Sorry I can't add much to that - I got Nougat working well - a few minor issues with the Playstore notwithstanding and now resolved. This meets my use case for the phone which was to allow Life 360 app (my wife uses it for family tracking) from the Playstore (nothing before 6 supported by developers). Now my teen son can be tracked on his way home from school on days he needs to be somewhere ("Where are you ?", "Errrrr ... by a building", etc etc).
Many thanks to all who helped me btw