Hello, So I am having a very strange issue with this phone (Samsung Galaxy S5). For the pass 3 days I have been trying to diagnose this problem and I can't seem to figure it out. I was wondering if someone could help me or guide me to the right path.
I went from stock 5.1 lollipop that came with the phone. Used ODIN to flash TWRP and flashed CM 12.1. Then I flashed GApps then everything was fine booted into it. Then the welcome screen came up and immediately noticed "google play service has stop" and this would happen every 1 min or so. I just kept ignoring it. With every reboot a variety of crashes would happen. For example most of the google apps would crash along side with some simple apps like facebook. For every reboot the crashes would be more or less the same. The crashes are native and the stack trace are some what different but don't really tell much of a story.
So I went from CM 12.1 to CM 13 with the same results. I clean flashed it, installed gapps ( The recommend opengapps ) and the same results. Varitey of google apps crashing again and again and again. So I tried different roms that were not based on CM and the same thing. I flashed back to stock and same thing. Which was very werid, so at this point I was stuck I didn't know what else to think of. I tried every method to ensure that all the cache was clear on google play services and other apps that were crashing. The interesting thing is that sometimes when download an app I get a variety of errors unable to download or install ranging from error code 902, 960, -2 so I used adb debugger to see what the heck was going on. I noticed that the md5 hash from installing apps (From google play store) weren't matching. So I assume okay perhaps corrupt wireless card but I used my mobile data same thing and still doesn't fix the constant google apps crashing. These issues that I have described are the exactly same thing for all the different roms I have tried from stock > CM12.1 > CM13 > Blisspop > OmegaRom > Stock (Again)> (Stock kitkat 4.4.2) so this issues doesn't seem like a software issue as the same results happen every time. I was wonder if anyone could shed some light into this issue its a strange issues and I am speculating it is a hardware issue. Thank you very much
Flash this PIT file along with the stock ROM (At the same time / together)
http://forum.xda-developers.com/attachment.php?attachmentid=2800218&d=1402859206
Extract it to .pit, add to PIT section in ODIN 3.10.7, flash both stock ROM in AP or PDA section, and PIT file in PIT section
--
For the custom ROMs, are you sure you 100% wiped everything and formatted in TWRP before flashing the ROMs? (Including DATA?)
*Detection* said:
Flash this PIT file along with the stock ROM (At the same time / together)
http://forum.xda-developers.com/attachment.php?attachmentid=2800218&d=1402859206
Extract it to .pit, add to PIT section in ODIN 3.10.7, flash both stock ROM in AP or PDA section, and PIT file in PIT section
--
For the custom ROMs, are you sure you 100% wiped everything and formatted in TWRP before flashing the ROMs? (Including DATA?)
Click to expand...
Click to collapse
Yes and I will proceed to flash the pit. I actually I was a thread about flashing the pit with the stock before I posted ill try it out and flash it with stock to see the results and yes I formatted everything including data
Ok so I reflashing it along side with the pit file you gave me. I think I did it wrong as I unticked the "Re-Partion" because it was giving me error "Re-Partition operation failed" and on the phone it says "Secure check fail : PIT" the device is fine on stock same crashing results. I know the pit didn't flash at all I am assuming lol
If you unchecked repartition, then the PIT was useless as that is what it is for
Which provider is the phone with? Some have locked bootloaders and might not allow the PIT to be flashed
*Detection* said:
If you unchecked repartition, then the PIT was useless as that is what it is for
Which provider is the phone with? Some have locked bootloaders and might not allow the PIT to be flashed
Click to expand...
Click to collapse
I am with Fido, and download the stock ROM under "Fido" on sammoblie and on one of the links on the fourm. And yes I figured unchecking it wouldn't do anything I just thought I would try it out lol.
Just realised you already flashed TWRP and custom with ODIN, so your bootloader is not locked
You can try flashing just the PIT file on it's own, and then the Stock ROM again on its own after that
Make sure you run ODIN as Administrator (Right click > run as admin)
And use ODIN 3.10.7
You can try any stock ROM, as long as it's for your model S5, doesn't have to be FIDO
Double check in download mode, that it does say G900W8
*Detection* said:
Just realised you already flashed TWRP and custom with ODIN, so your bootloader is not locked
You can try flashing just the PIT file on it's own, and then the Stock ROM again on its own after that
Make sure you run ODIN as Administrator (Right click > run as admin)
And use ODIN 3.10.7
You can try any stock ROM, as long as it's for your model S5, doesn't have to be FIDO
Double check in download mode, that it does say G900W8
Click to expand...
Click to collapse
I have tried that and it fails ODIN saying " Re-Partition operation failed " phone saying " secure check fail : PIT"
100% it says G900W8 in download mode
You're using a native PC?
Phone is definitely in Download mode, and not recovery?
Feel like I've seen others with a similar problem in this forum, have a read through some threads, see if you can find any - I`ll post back if I come across them
Until then, hopefully someone who has seen this error before can chip in
EDIT - Hidden partition rings a bell..
*Detection* said:
100% it says G900W8 in download mode
You're using a native PC?
Phone is definitely in Download mode, and not recovery?
Feel like I've seen others with a similar problem in this forum, have a read through some threads, see if you can find any - I`ll post back if I come across them
Until then, hopefully someone who has seen this error before can chip in
EDIT - Hidden partition rings a bell..
Click to expand...
Click to collapse
Yes 100 percent download mode with the combos vol down + home + power. I also tried using link2sd to actually move all apps to my external SD card and same results constant random google apps crashes with other apps. Along with that issue I also have random "unable to download" issues on google play store using adb to capture the logs and verified that the issues were occurring because of a MD5 hash not being match to the source which leaves me to believe that it can either be a storage issues corrupted the data as it is being written to or the wireless nic in the phone itself. Thank you very much ill also look into it on the threads to see if anyone has a similar issues. Its a very strange issue, if anything I will be doing more debugging to see of I can for sure verify it is a issues of the internal storage of the device. Also I would like to mention that I used TWRP "Repair" partion on all directory from /system to /data
Also yes I am using a native PC Windows 10 Pro
If we can figure out the PIT issue, I feel it would probably solve it, I'm thinking that TWRP has done something to the files system / partition table
I know with my TF101 tab, G Play will error out if the storage is not formatted with a specific TWRP version prior to flashing the ROM
I've had problems with apps crashing on my S5 when I tried clearing the caches using stock recovery, nothing would fix it until I flashed the same stock ROM over the top, then flashed TWRP 2.8.7.0 with ODIN, and cleared caches with TWRP instead
Seems the stock recovery is buggy
*Detection* said:
If we can figure out the PIT issue, I feel it would probably solve it, I'm thinking that TWRP has done something to the files system / partition table
I know with my TF101 tab, G Play will error out if the storage is not formatted with a specific TWRP version prior to flashing the ROM
I've had problems with apps crashing on my S5 when I tried clearing the caches using stock recovery, nothing would fix it until I flashed the same stock ROM over the top, then flashed TWRP 2.8.7.0 with ODIN, and cleared caches with TWRP instead
Seems the stock recovery is buggy
Click to expand...
Click to collapse
Alright, sounds good, ill look into the PIT issue see if there is some way to flash it. After that I will flash stock then install TWRP with ODIN.
Franco093 said:
Alright, sounds good, ill look into the PIT issue see if there is some way to flash it. After that I will flash stock then install TWRP with ODIN.
Click to expand...
Click to collapse
Found a thread with the same issue for the S3, and the guy used a HEX Editor to remove that hidden partition section in the PIT file
Don't ask me how, Hex editors are confusing
*Detection* said:
Found a thread with the same issue for the S3, and the guy used a HEX Editor to remove that hidden partition section in the PIT file
Don't ask me how, Hex editors are confusing
Click to expand...
Click to collapse
I JUST saw the same thread doing it right now!
Good luck
Remember though, the PIT file wipes and recreates all the partitions on your phone, so if you get it wrong, and the original will not flash, you could end up with a brick
*Detection* said:
Good luck
Remember though, the PIT file wipes and recreates all the partitions on your phone, so if you get it wrong, and the original will not flash, you could end up with a brick
Click to expand...
Click to collapse
Well good news I MANGE TO DO IT! I removed the padding and flashed the PIT! Thank you! Ill keep you updated going to install PIT with stock at the same time then install TWRP!
Franco093 said:
Well good news I MANGE TO DO IT! I removed the padding and flashed the PIT! Thank you! Ill keep you updated going to install PIT with stock at the same time then install TWRP!
Click to expand...
Click to collapse
I installed the pit file with stock rom again same crashes occured. So I flashed TWRP then formated everything then installed PIT first then stock and same crashes. I am going to install cm 12.1 and try again.
Franco093 said:
I installed the pit file with stock rom again same crashes occured. So I flashed TWRP then formated everything then installed PIT first then stock and same crashes. I am going to install cm 12.1 and try again.
Click to expand...
Click to collapse
And you are not doing anything else other than flashing stock?
You're not letting Google backup restore your apps or anything? Just 100% stock?
If it's still doing it after flashing the PIT (Nice job btw )it's either a buggy stock ROM, but if it was doing it with custom too, that rules that out,
Or a hardware issue
Have you tried creating a new Google account to test, in case something with your account is messing with settings/apps (Unlikely, but only thing I can think of atm)
Have you tried formatting or just removing your MicroSD card, and then factory resetting stock again, so you have 100% just the phone, purely with stock ROM, with a new Google account - to remove any traces of anything you've done since buying it
I do not have a microsd card connected to it. And I tried a custom ROM and same crashes google services and google app constantly crashing, I also get random download errors.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I notice also that one of the google service crash was a memory violation error. Maybe the ram is corrupted
It is sounding more and more like a hardware fault, we've done just about all that can be done to rule out firmware (ROM)
KNOX will be tripped from you flashing custom too, so I'd say your only option is to pay for it to be fixed, or sell it as faulty and buy another one unfortunately, unless any other Android gurus have any ideas
Good luck
EDIT - One last thought, when you flashed the modded PIT on it's own, did you check to see if it had actually wiped the phone clean before flashing stock again? (Did it hang on the logo / black screen?)
Just wondering if the PIT did actually do it's job or not, after being modded
Related
I am reaching out to the XDA community because with my Vibrant I received so much help, knowledge, experience you name it everyone has been so awesome. I have really hit a brick wall here with this new Epic and I have to say working on an Epic is 10x harder than a vibrant. I had the syndicatefrozen rom running and all of a sudden I rebooted the phone and it would not go past custom boot. So i did what I always do in the case of reflashing in cwm doesnt work... I used odin to flash the 512 pit and DI18 stock software but it fails every time. Now I have read every post I can find that suggests using a different usb cable, a different computer, try 512 pit, victory pit, tried the tar.md5 or the .tar., try redownloading the files, everything Now trust me when I say with my vibrant I NEVER encounter problems flashing with ODIN. If someone could please take some time to go back and forth with me on troubleshooting I would be so grateful. I have been trying so hard that all the troubleshooting processes have started to run together in my head and I'm really frustrated. Can anyone help?
The very first time I flashed my epic it bricked. It turned out I needed to redownload the Rom in my case. If that didnt work for me, my next step was to get a new cable.
but because it bricked I needed to reflash to a stock rom (which in your case I would re download (FROM A TRUSTED SITE)
Just to make sure... to Odin you need to be in "download mode". You can get into it by hold the #1 key on the qwerty keyboard and holding power. By doing that odin will see your phone.
If you need help, I made a bunch of how to youtube videos. There is a sticky in the general section... check it out.
Sent from my SPH-D700 using XDA App
stevenmcneal83 said:
I am reaching out to the XDA community because with my Vibrant I received so much help, knowledge, experience you name it everyone has been so awesome. I have really hit a brick wall here with this new Epic and I have to say working on an Epic is 10x harder than a vibrant. I had the syndicatefrozen rom running and all of a sudden I rebooted the phone and it would not go past custom boot. So i did what I always do in the case of reflashing in cwm doesnt work... I used odin to flash the 512 pit and DI18 stock software but it fails every time. Now I have read every post I can find that suggests using a different usb cable, a different computer, try 512 pit, victory pit, tried the tar.md5 or the .tar., try redownloading the files, everything Now trust me when I say with my vibrant I NEVER encounter problems flashing with ODIN. If someone could please take some time to go back and forth with me on troubleshooting I would be so grateful. I have been trying so hard that all the troubleshooting processes have started to run together in my head and I'm really frustrated. Can anyone help?
Click to expand...
Click to collapse
do not use the pit, it contains partition mapping, if you use the wrong one it can BRICK your phone. but yea stock samsung cable sucks, if i were you id try heimdall
I have a good bit of experience with ODIN. I've read that you have a better chance of permanently bricking using heimdall. Is that true? Also, how does heimdall work? Basically extract the zip files and load them individually?
First off, I'm not going to tell you one rom is better than another.....they're all good. However, I have become very fond of midNIGHT roms because the developer is very precise in walking you through the flashing process. He has download links for everything that you need to flash his roms in the op, including the stock D18 files from Sprint. I would try downloading the D18 files FROM HIS SITE and use them to ODIN back to stock. By the way, make sure that ur using ODIN 1.61, that version seems to give people the best results. Don't worry, you can download that from the midNIGHT op also. Make sure that all of the Epic's drivers were successfully installed on your PC. You can also get those from midNIGHT's op. Once you've downloaded the files you need, make sure before you ODIN, that you completely shut the phone down for at least 30 sec. Then open your keyboard and press and HOLD 1 and then the POWER button until you see the android robot with the shovel pop up. That's the Epic's downloading mode. Before plugging the phone into your PC, go ahead and open up ODIN, make sure that you only have reboot checked. Then put the victory.pit file in the pit spot and the stock D18 file in the pda spot. Now you can plug your phone in, if ODIN recognizes the phone you'll see a comm:0 in the top left side of ODIN highlighted in yellow. If not, then you need to reinstall the Epic's drivers. If you do see a comm:0 in yellow, then all is good.....go ahead and click on START and wait for it to finish. When done, ODIN will automatically reset your phone. Wait for it to boot up, then continue to flash according to the rom developer's instructions.......I know this is confusing, but I can guarentee that if you explicitaly follow the directions on midNIGHT's op, you'll be enjoying a new rom in no time. Hope this helped to some degree.....Good Luck......Happy Flashing
shabbypenguin said:
do not use the pit, it contains partition mapping, if you use the wrong one it can brick your phone. But yea stock samsung cable sucks, if i were you id try heimdall
Click to expand...
Click to collapse
if you use the .pit file that is included with the stock d18 file on midnight's op, i guarentee that it will work.......just used it a couple days ago. Sounds like you used the wrong .pit file the first time
My bad, I just double checked my downloads from midNIGHT's op and the correct .pit file he includes with the ODIN 1.61 download. Just download ODIN from midNIGHT's page and you'll have all the correct files for ur Epic
Where the hell did u get the 512 .pit file?
stevenmcneal83 said:
I am reaching out to the XDA community because with my Vibrant I received so much help, knowledge, experience you name it everyone has been so awesome. I have really hit a brick wall here with this new Epic and I have to say working on an Epic is 10x harder than a vibrant. I had the syndicatefrozen rom running and all of a sudden I rebooted the phone and it would not go past custom boot. So i did what I always do in the case of reflashing in cwm doesnt work... I used odin to flash the 512 pit and DI18 stock software but it fails every time. Now I have read every post I can find that suggests using a different usb cable, a different computer, try 512 pit, victory pit, tried the tar.md5 or the .tar., try redownloading the files, everything Now trust me when I say with my vibrant I NEVER encounter problems flashing with ODIN. If someone could please take some time to go back and forth with me on troubleshooting I would be so grateful. I have been trying so hard that all the troubleshooting processes have started to run together in my head and I'm really frustrated. Can anyone help?
Click to expand...
Click to collapse
\
Take the tar.md5 and erase the md5 off the end, just to have .zip. Put this in the PDA box and check marked. This worked for me numerous times when I downloaded the DI18 file. Make sure you just have Auto Reboot checked and no others, and make sure COM port is showing up with the appropriate drivers installed, which are the same for the Vibrant I believe. So shouldn't be the problem. Dont worry bout the pit file, it is a mapping source for the md5 that isn't really needed. If that fails, try a different port on the computer on the back and another USB cable.
stevenmcneal83 said:
I have a good bit of experience with ODIN. I've read that you have a better chance of permanently bricking using heimdall. Is that true?
Click to expand...
Click to collapse
No, however based user reports, the opposite could most certainly be argued.
However in the end it just comes down to personal preference. Just use whatever you're more comfortable with.
Leeboy said:
if you use the .pit file that is included with the stock d18 file on midnight's op, i guarentee that it will work.......just used it a couple days ago. Sounds like you used the wrong .pit file the first time
Click to expand...
Click to collapse
i didnt use a wrong pit, but just fore warning as he said he did. also you do not need to use the pit. it will pull it from the phone for just flashing
Thank you for all of the responses. I think only one person suggested something that I have not yet tried. The person that said to remove "md5" from the ".tar". But now my device will not be recognized by the computer. I have uninstalled and reinstalled the drivers numerous times. tried 3 different computers. tried no battery. tried leaving the battery out for a while and putting it back in. Ive tried a different cable. Does anyone know a guaranteed way to get my pc to recognize the phone? I mean once I get past this I can finally actually work on fixing the device. Thanks again everybody that gave their input. I'm going to destroy this phone soon if something doesnt give lol (also, the phone will go into download mode so there is still hope, i think)
Ok. somehow the computer all of a sudden recognized the device. I used heimdall to flash the stock software. The flash was completely successful, the phone rebooted and showed the sprint boot animation with sound, after that the screen is just blank. Any ides? I'm so close I can feel it
i can feel it too.
stevenmcneal83 said:
Ok. somehow the computer all of a sudden recognized the device. I used heimdall to flash the stock software. The flash was completely successful, the phone rebooted and showed the sprint boot animation with sound, after that the screen is just blank. Any ides? I'm so close I can feel it
Click to expand...
Click to collapse
If you flashed the stock software and it said successful I can only imagine you need to wait longer for it to boot. I have never used heimdall, due to always having success with Odin, so I can't give any real advice past this point except to try again. If you do get Odin to work, then please try the remove .md5 at the end and flash the DI18 file WITHOUT pit and I"m pretty sure that will work.
Use this utility in Windows I've uploaded and hit Description to organize the folders. Once that is complete, scroll down to the drivers that are named "Samsung SPH-D700 Card" and others. You will see many of them. Right click on the target and Uninstall them and all and reboot your computer. Then proceed to reinstall the drivers normally. This should make your computer recognize your phone again.
Once it does, Open ODIN, untick F. Reset Time, Tick the PDA and select the file in which you removed the .md5 ( should just be .tar file) and hit start.
Here is the program to remove drivers:
http://www.multiupload.com/3PC2BBAFSO
The problem now is not getting the phone to recognize. It all of a sudden started working. When I use ODIN it fails EVERY time. I know I'm using ODIN correctly because I have flashed back to stock about 4 times previously with this phone. When I flashed with Heimdall it said it was successful and the sprint boot screen came on which is further than I have been able to get in a week so it leads me to believe I'm very close to fixing it. After the bootup animation I left the phone for 10 minutes and the screen just stays blank with the capacitive buttons lit as well as led indicator light. I've tried mulitple flashes and still nothing. Any ideas?
I think most here have good experience with Odin, not Heimdall. Either try Heimdall again, or try Odin. I also agree with Leeboy - look at the instructions on www(dot)lostandtired(dot)com/android-development (new user - can't post links yet)
There's a video tutorial on how to Odin just the modem (and a note on where/how to Odin EC05).
Hmm,Maybe try it out on a different computer.Follow the procedure which is given Here, It will definitely work. I have done it over 5-6 times in my epic without a problem even once.
odin fails eveytime i try to flash the DI18 stock. The last item to show on the odin progress box is recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It all started with the plan to root the device Samsung Galaxy Note 3
I had rooted the device using Kingo Android root. This had gone successfully. Then I tried to install some apps which needs root access. I tried an app called EFS, I though I would back up EFS and NV_ *, When I clicked on backup NV_* (cant remember the whole name), thats when the problem started. It had been 2 days since I had been trying different things to recover the device.
I went into recovery mode and tried
Clear cache
Then Back up my data and did factory reset
Between boot loops I had the opportunity to uninstalled the EFS app
Then installed twrp and tried this blog http://forum.xda-developers.com/showthread.php?t=2471421
eventually, I thought of letting go of my data, so did the format of data
used ODIN to and flashed this ROM from this blog http://forum.xda-developers.com/showthread.php?t=2540822
Despite all these steps I cannot get it working.
Current phone behaviour
The phone keeps booting again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding"
I am willing to try anything to get the device functional, if it means to build it from scratch. This is my first time venturing into this side of the world, I would be thankful if you can guide me with the steps to perform a build from scratch, or direct me to a blog where I can do this?
eagle909 said:
It all started with the plan to root the device Samsung Galaxy Note 3
I had rooted the device using Kingo Android root. This had gone successfully. Then I tried to install some apps which needs root access. I tried an app called EFS, I though I would back up EFS and NV_ *, When I clicked on backup NV_* (cant remember the whole name), thats when the problem started. It had been 2 days since I had been trying different things to recover the device.
I went into recovery mode and tried
Clear cache
Then Back up my data and did factory reset
Between boot loops I had the opportunity to uninstalled the EFS app
Then installed twrp and tried this blog http://forum.xda-developers.com/showthread.php?t=2471421
eventually, I thought of letting go of my data, so did the format of data
used ODIN to and flashed this ROM from this blog http://forum.xda-developers.com/showthread.php?t=2540822
Despite all these steps I cannot get it working.
Current phone behaviour
The phone keeps booting again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding"
I am willing to try anything to get the device functional, if it means to build it from scratch. This is my first time venturing into this side of the world, I would be thankful if you can guide me with the steps to perform a build from scratch, or direct me to a blog where I can do this?
Click to expand...
Click to collapse
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
radicalisto said:
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
Click to expand...
Click to collapse
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
eagle909 said:
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
Click to expand...
Click to collapse
Ahh, you will need to find an ext SD card, then you'll have to transfer it across via your PC then insert into phone, boot into Recovery and flash it.
Not flashable via Odin atm I'm afraid
eagle909 said:
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
Click to expand...
Click to collapse
Yes it does comes with an ext SD card slot... Beside ur sim card slot. Put that file into it then put into ur phone. Boot into custom recovery and flash it.
Sent from my proudly temaseked +Yankied note 3.
Yeah SD Card slot is above the sim card slot, -- I read it wrong, thought you said -- "it doesn't come with an EXT SD Card"
radicalisto said:
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
Click to expand...
Click to collapse
radicalisto said:
Yeah SD Card slot is above the sim card slot, -- I read it wrong, thought you said -- "it doesn't come with an EXT SD Card"
Click to expand...
Click to collapse
I never knew there was a slot of SD card, else I would have backed up my data thanks!
But this solution didnt work for me. After the install of this script through twrp the phone behavior is unchanged.
Try flashing the stock rom for your phone. Then you can go back and root again....
99% of the time this will fix things...
eagle909 said:
I never knew there was a slot of SD card, else I would have backed up my data thanks!
But this solution didnt work for me. After the install of this script through twrp the phone behavior is unchanged.
Click to expand...
Click to collapse
The screenshot of the install. I suspect if there is something wrong with the install?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
eagle909 said:
The screenshot of the install. I suspect if there is something wrong with the install?
sorry too big of the picture
Click to expand...
Click to collapse
ultramag69 said:
Try flashing the stock rom for your phone. Then you can go back and root again....
99% of the time this will fix things...
Click to expand...
Click to collapse
downloading this Rooted Stock ROMs for Note 3 SM-N9005
http://galaxynote3root.com/rooted-stock-roms/
That screenshot looks OK to me. The Mount error is standard in TWRP. Reboot your device and see.. or as posted re flash stock as it pretty much fixes everything
Sent from my SM-N9005 using XDA Premium 4 mobile app
eagle909 said:
downloading this Rooted Stock ROMs for Note 3 SM-N9005
http://galaxynote3root.com/rooted-stock-roms/
Click to expand...
Click to collapse
I have just flashed this ROM and reran the fix, but with out any luck?
The phone keeps rebooting
eagle909 said:
I have just flashed this ROM and reran the fix, but with out any luck?
The phone keeps rebooting
Click to expand...
Click to collapse
You haven't flashed a stock rom... That is rooted and so is no longer a stock rom. Go to Sammobile.com to get a pure stock rom...
Just a note for you, whether it says stock is solely reliant on it being NOT tampered with. Rooting a stock rom no longer makes it stock, it is just a description that means no tweaks were applied or bloatware removed...
Remember that the bootloader must match the stock rom. If you are trying to flash a lower version rom onto an MJ3 or higher bootloader you will get bootloops.
The same applies if you have updated to Kitkat rom.
If you haven't updated to 4.4.2, then you should check this[first post]
http://forum.xda-developers.com/showthread.php?t=2540822
But this will trip your Knox counter
Sent from my SM-N9005 using Tapatalk
I checkout this post and did exactly as described. but the phone rebooting doesnot stop. Also when the phone is turned on I am not able to open Phone option and under settings I am not able to launch status option under about device? Could my EFS is lost/corrupted?
Dahdoul said:
If you haven't updated to 4.4.2, then you should check this[first post]
http://forum.xda-developers.com/showthread.php?t=2540822
But this will trip your Knox counter
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
eagle909 said:
I checkout this post and did exactly as described. but the phone rebooting doesnot stop. Also when the phone is turned on I am not able to open Phone option and under settings I am not able to launch status option under about device? Could my EFS is lost/corrupted?
Click to expand...
Click to collapse
Use This It'll fix it. - You have to install a custom recovery via Odin then flash that fix and you'll be alright, you EFS is warped is all.
I had already tried that fix, but with no luck. I flashed that fix with a lot of combinations like with fresh install of stock rom, with rooted rom etc. No luck
radicalisto said:
Use This It'll fix it. - You have to install a custom recovery via Odin then flash that fix and you'll be alright, you EFS is warped is all.
Click to expand...
Click to collapse
eagle909 said:
I had already tried that fix, but with no luck. I flashed that fix with a lot of combinations like with fresh install of stock rom, with rooted rom etc. No luck
Click to expand...
Click to collapse
Is the phone bootlooping constantly ? and crashing after around 1minute?
rtanceF seize
radicalisto said:
Is the phone bootlooping constantly ? and crashing after around 1minute?
Click to expand...
Click to collapse
When you mean "install a custom recovery via Odin", you meant to install something like TWRP to install the zip using recovery mode?
The phone keeps booting again and again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding" before the phone restarts.
Heyo, lets get started ruining this device even more! See if we can't brick it ey?
Anyways first off the battery is draining like a madman, 1% every 30 seconds or so. The thing is not getting the performance in games that it should be, using other devices with lower end hardware as a reference(1.1ghz quad core, adreno 305, 2gb ram one touch, and 1.2ghz quad core, adreno 306, 1.3gb ram kyocera), it keeps micro-stuttering while browsing chrome and doing basic actions with the UI, also when the battery is draining too(funny, sometimes while I have the charger plugged in and do basic activies such as chrome, youtube, read books, mess with menu settings the battery actually charges instead of deplete, but sometimes, seemingly always now, it depletes just as fast as though it was unplugged).
Anyways I have decided to try and customize the device with the plethora of information on here and all over the web for this device(after doing a lot more "research" of course and laying everything out for myself step by step to try to minimize failure.
First question is how much of a chance is there to brick the device installing TWRP alone? Really want to get that on there before doing anything, then install SuperSU from there with zip flash. And does it matter if I use a .tar or .img version of TWRP to flash with odin? The latest version of TWRP is in .img format and the tutorials I read say to use a .tar.
After that witch should I do try first, custom rom or custom kernel? What custom rom would be best at this point in time(5/13/2016) for this device, 100% compatible and fully tested. Also a kernel(unless overclocking can be unlocked within the custom rom, in witch case less chance of me ****ing up yet another android device).
One last thing, I really hope that even I am successful in doing all of this without ****ing up the phone that it does not turn out to be a fruitless effort, how much performance gains can I expect from all of this, custom rom, debloat after root, set sd as default storage after root(package does not belong to 2000 afterall), and then maybe a slight overclock on the cpu and gpu.
And thats all assuming that one day after getting all of this to work that one day I don't wake up and for no apparent reason boot up the phone and find its bootlooped or something without ever changing anything once all of this is done, I mean if I get the thing working as I would like it to work theres no more reason for me **** with it is there? Also I guess no reason to even have the thing if it aint gonna function how I need it to function right?
Thanks for the help though anyways, if anybody even decides to help me this time in a manner that they are not just "helping" just because the end result ****s me over.
Thanks again.
Oh one other problem I am having with the phone I was hoping a custom rom might fix, my Apps will not register as the correct size in Application manager. A 2gb game is showing up as 50mb total data, and when using "Move to SD Card" it only shows only like 200kb of data on the sd card, it does with with every single app on the phone. I know should not be like this because the last 2 phones I had were able to move every single byte of data from every one of the same exact apps to the SD card without an issue. Plus the application manager not registering the correct app size is just bugging me.
phenom2955 said:
Heyo, lets get started ruining this device even more! See if we can't brick it ey?
Anyways first off the battery is draining like a madman, 1% every 30 seconds or so. The thing is not getting the performance in games that it should be, using other devices with lower end hardware as a reference(1.1ghz quad core, adreno 305, 2gb ram one touch, and 1.2ghz quad core, adreno 306, 1.3gb ram kyocera), it keeps micro-stuttering while browsing chrome and doing basic actions with the UI, also when the battery is draining too(funny, sometimes while I have the charger plugged in and do basic activies such as chrome, youtube, read books, mess with menu settings the battery actually charges instead of deplete, but sometimes, seemingly always now, it depletes just as fast as though it was unplugged).
Anyways I have decided to try and customize the device with the plethora of information on here and all over the web for this device(after doing a lot more "research" of course and laying everything out for myself step by step to try to minimize failure.
First question is how much of a chance is there to brick the device installing TWRP alone? Really want to get that on there before doing anything, then install SuperSU from there with zip flash. And does it matter if I use a .tar or .img version of TWRP to flash with odin? The latest version of TWRP is in .img format and the tutorials I read say to use a .tar.
After that witch should I do try first, custom rom or custom kernel? What custom rom would be best at this point in time(5/13/2016) for this device, 100% compatible and fully tested. Also a kernel(unless overclocking can be unlocked within the custom rom, in witch case less chance of me ****ing up yet another android device).
One last thing, I really hope that even I am successful in doing all of this without ****ing up the phone that it does not turn out to be a fruitless effort, how much performance gains can I expect from all of this, custom rom, debloat after root, set sd as default storage after root(package does not belong to 2000 afterall), and then maybe a slight overclock on the cpu and gpu.
And thats all assuming that one day after getting all of this to work that one day I don't wake up and for no apparent reason boot up the phone and find its bootlooped or something without ever changing anything once all of this is done, I mean if I get the thing working as I would like it to work theres no more reason for me **** with it is there? Also I guess no reason to even have the thing if it aint gonna function how I need it to function right?
Thanks for the help though anyways, if anybody even decides to help me this time in a manner that they are not just "helping" just because the end result ****s me over.
Thanks again.
Click to expand...
Click to collapse
Well first it sounds like you need a new battery, I suggest having a couple and an external charger (it's great for gaming, just pop in a new fully charged battery). To install TWRP with Odin you need the tar file. The chance of Helicon with TWRP is almost zero, recovery is always overwritten when you flash a stock tar in Odin. So if something is messed up, just flash the stock tar and you are back to stock, grab it at www.sammobile.com . When you Odin TWRP make sure that you uncheck Auto Reboot in Odin. I would suggest my ROM as it is still being updated every few months, but I am biased. I use my S4 for gaming and this thing can handle PSP emulation when it is tweaked right.
Wicked X is my ROM and it's located here - http://forum.xda-developers.com/showthread.php?t=3115583
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok thanks, a little reluctant to install an OS with the name "Wicked" though.
Any ideas why the stock Application Manager is being wacky, done several factory resets. For instance I have installed Fifa 16 about 5 times now just to see if it would fix the data readout in App manager, the Game is at least 1.5gb total data, app manager shows it as about 50-70mb, when using "Move to SD Card" it shows about 700kb of data on sd card.
Whats the deal?
Also before flashing TWRP with odin I have to unlock bootloader or something?
phenom2955 said:
Ok thanks, a little reluctant to install an OS with the name "Wicked" though.
Any ideas why the stock Application Manager is being wacky, done several factory resets. For instance I have installed Fifa 16 about 5 times now just to see if it would fix the data readout in App manager, the Game is at least 1.5gb total data, app manager shows it as about 50-70mb, when using "Move to SD Card" it shows about 700kb of data on sd card.
Whats the deal?
Also before flashing TWRP with odin I have to unlock bootloader or something?
Click to expand...
Click to collapse
No, bootloader is already unlocked. I can't tell you on the other without more information. What ROM are you on? Have you done any modifications? Have you Odined a full stock tar?
I bought this phone used on cl. Fully stock not a single mod on it as far as I am aware. The only thing I have done is factory reset.
It seems half the time as well when I Uninstall apps the data stays in misc section of storage manager. I have to go into recovery and clear cache and I get my space back. And misc section of storage manager will be back down to its normal size.
@ your comment about loader. You absolutely certain and no bs that if I attempt to flash something (even just twrp) it ain't gonna fail and go tit's up because I didn't unlock bootloader or something?
Just lost 2 phones already simply from uninstslling gltools after it failed to produce my desired results. Install went fine, but uninstslling rebooted the phones and got one caught in boot loop other just sits on manufacur er logo.
If asked why I was stupid enough to try it a second time I'll say I wasn't 100% sure it was absolutely gltools as the culprit.
Anyways this is the first device I have had with so much support with custom recoveries. Roms and kernels and even access to stock rom files. Would love to successfully apply some good stable/safe/and better running mods than the stock stuff though since I am convinced this hardware should be running better than it currently is!! But not trying anything for a while though till I've read as much as I can at least and have at least a few options for recovery should somehring go wrong.
Don't like being stuck with thumb up my ass stacking bricks, I am no mason.
Nickvanexel said:
I bought this phone used on cl. Fully stock not a single mod on it as far as I am aware. The only thing I have done is factory reset.
It seems half the time as well when I Uninstall apps the data stays in misc section of storage manager. I have to go into recovery and clear cache and I get my space back. And misc section of storage manager will be back down to its normal size.
@ your comment about loader. You absolutely certain and no bs that if I attempt to flash something (even just twrp) it ain't gonna fail and go tit's up because I didn't unlock bootloader or something?
Just lost 2 phones already simply from uninstslling gltools after it failed to produce my desired results. Install went fine, but uninstslling rebooted the phones and got one caught in boot loop other just sits on manufacur er logo.
If asked why I was stupid enough to try it a second time I'll say I wasn't 100% sure it was absolutely gltools as the culprit.
Anyways this is the first device I have had with so much support with custom recoveries. Roms and kernels and even access to stock rom files. Would love to successfully apply some good stable/safe/and better running mods than the stock stuff though since I am convinced this hardware should be running better than it currently is!! But not trying anything for a while though till I've read as much as I can at least and have at least a few options for recovery should somehring go wrong.
Don't like being stuck with thumb up my ass stacking bricks, I am no mason.
Click to expand...
Click to collapse
100%, Sprint doesn't lock bootloaders (though Samsung has started to). You may have to turn off the an option in Settings/Security, I think it's called Write Protection, it won't let you Odin anything if it is on.
I have a sprint sph-720T
I installed TWRP using ODIN
then reboot in recovery, put OCTOS-M on to internal memory and wipe the cache davik
install the OCTOS-M from zip file then install GAPPS from zip.
BOOOM! you have a rooted android 6.0.1 ! longer battery life.
EDIT: if you need direct links to the files, just ask.
Mangodreads said:
I have a sprint sph-720T
I installed TWRP using ODIN
then reboot in recovery, put OCTOS-M on to internal memory and wipe the cache davik
install the OCTOS-M from zip file then install GAPPS from zip.
BOOOM! you have a rooted android 6.0.1 ! longer battery life.
EDIT: if you need direct links to the files, just ask.
Click to expand...
Click to collapse
Have you had any issues flashing the s4 to 6.0? It would be great if you added direct links. Thanks.
ABERBER1986 said:
Have you had any issues flashing the s4 to 6.0? It would be great if you added direct links. Thanks.
Click to expand...
Click to collapse
1. Put the Custom Rom Zip and the GAPPS zip on the phones memory card and then turn off the phone
2. Put the phone in download mode, connect to the computer via usb and run ODIN
Select AP and the select the TWRP recovery file. - Click Start - Once its finished
3. Put the phone in recovery mode - go to wipe, clear cache/davik a few times
go to install and select the Custom Rom Octos 6.0.1 that you put on the phones memory.
install it and then install GAPPS zip right afterwards
once those are installed reboot the phone and you are good.
These links are for user with Sprints galaxy s4 sph-720T ONLY
This is the TWRP recovery
https://dl.twrp.me/jfltespr
This link is to 6.0.1 Custom Rom by OCTOS
https://www.teamoctos.com/download/M_release/jfltespr/OCT-M-R1-6.0.1-20160319-jfltespr.zip
This is a link for GAPPS (google apps, playstore etc) - select the "variant" you want
http://opengapps.org/?arch=arm&api=6.0&variant=micro
Mangodreads said:
1. Put the Custom Rom Zip and the GAPPS zip on the phones memory card and then turn off the phone
2. Put the phone in download mode, connect to the computer via usb and run ODIN
Select AP and the select the TWRP recovery file. - Click Start - Once its finished
3. Put the phone in recovery mode - go to wipe, clear cache/davik a few times
go to install and select the Custom Rom Octos 6.0.1 that you put on the phones memory.
install it and then install GAPPS zip right afterwards
once those are installed reboot the phone and you are good.
These links are for user with Sprints galaxy s4 sph-720T ONLY
This is the TWRP recovery
https://dl.twrp.me/jfltespr
This link is to 6.0.1 Custom Rom by OCTOS
https://www.teamoctos.com/download/M_release/jfltespr/OCT-M-R1-6.0.1-20160319-jfltespr.zip
This is a link for GAPPS (google apps, playstore etc) - select the "variant" you want
http://opengapps.org/?arch=arm&api=6.0&variant=micro
Click to expand...
Click to collapse
Please advice which version of twrp you used. Because I am unable to flash thru through odin
bump........
earthworm82 said:
Please advice which version of twrp you used. Because I am unable to flash thru through odin
Click to expand...
Click to collapse
The link for teamoctos doesn't seem to work.
vikingjerr said:
The link for teamoctos doesn't seem to work.
Click to expand...
Click to collapse
You could just go their thread in the Android Development section[emoji6]
Wicked 10.9
bilgerryan said:
You could just go their thread in the Android Development section[emoji6]
Click to expand...
Click to collapse
I just downloaded Wicked 10.9 but am not sure I have all the files needed. In the first page it mentions to load the 720t conversion file and a kernal file.
Later I saw that the kernal file was include. I don't know if I should flash one, two or three files.
vikingjerr said:
I just downloaded Wicked 10.9 but am not sure I have all the files needed. In the first page it mentions to load the 720t conversion file and a kernal file.
Later I saw that the kernal file was include. I don't know if I should flash one, two or three files.
Click to expand...
Click to collapse
Three, the v11.0 update last.
Hello folks,
I have Galaxy S4, Play Edition, GT-I9505G, currently running SlimROM 7.1.2 build 1.17 (dated 20180115) and baseband version I9505GUEUDNL3.
Last stock I had on this phone was Android 5.0. If there was any OTA after that, I didn't install it.
(Sam Mobile does not list this device, hence no way of knowing firmwares, but https://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4/GT-I9505G lists mine as the last firmware.)
I have been trying to install Lineage 15/Oreo ROMs and with every ROM I am getting Error 7, which is supposedly Recovery error but every time I have used the recovery recommended by the ROM administrator. So its definitely not a recovery issue in my case.
I was wondering, those with same device, managed to install Oreo ROM, what is your baseband version? Most likely, this is the culprit, but to be sure, I would like to know at least one person with same device and different baseband version that managed to install Oreo ROM.
This page (https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624) list a lot of stock ROMs. Mine is half way through. Hence, I would like to see someone with newer baseband running Oreo ROM.
Many thanks in advance.
Did you check the updater script to ensure the phone's model # is included?
audit13 said:
Did you check the updater script to ensure the phone's model # is included?
Click to expand...
Click to collapse
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
fuzzychicken said:
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
Click to expand...
Click to collapse
Maybe you need to add the gt-i9505g to the list rather than removing it.
audit13 said:
Maybe you need to add the gt-i9505g to the list rather than removing it.
Click to expand...
Click to collapse
It was already there, so the ROMs were compatible but I removed just in case, thought if it is not working with the model number in it, maybe I can try without it, as recommended on some other blog posts on the web.
I guess the only other thing would be to try different versions of TWRP.
audit13 said:
I guess the only other thing would be to try different versions of TWRP.
Click to expand...
Click to collapse
I am sorry, thats what I said in the OP. I have tried every possible version of TWRP that was recommended for those ROMs and the error keep showing up. That indicates that its not recovery that is causing the problem.
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
audit13 said:
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
Click to expand...
Click to collapse
That is what I am thinking but I am not too sure which is the latest stock ROM.
https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 On this page, there are loads of stocks. Mine is half way through. Its I9505GUEUDNL3_FULL. Assuming that the list goes down as newer stocks, esp looking at the last 3 alpha-numerics, should I be flashing I9505GUEUDPF1_FULL?
If I flash, I9505GUEUDPF1_FULL will it write new bootloader and baseband? If yes, do I have to go through whole unlock bootloader thing? or just flash twrp via Odin and go ahead with newer ROM? This is the most sticky part as I don't remember how I did it in the past. I just don't touch something I am not very clear understanding on, but this time I would like to update to Oreo, primarily for security purpose and the cash is tight so if I brick this, I wouldn't be very happy to buy another device. Hence trying to dot all i's and cross all t's.
Thanks for all help in advance.
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
audit13 said:
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
Click to expand...
Click to collapse
Thank you.
Let me put it in steps, pls correct me if I am wrong.
1. Flash I9505GUEUDPF1_FULL using Odin. Once rebooted, confirm if newer baseband is present. Check if the calls and data works.
2. Flash TWRP recovery using Odin (it will revert to stock recovery, right?) If not, alls good as it is.
3. Install ROM of choice.
There is no data on the phone, I reflashed SlimROM after all attempts of Oreo failed.
Anything tricky stuff in between?
Thanks in advance.
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
audit13 said:
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
Click to expand...
Click to collapse
I am very sorry to be a PITA, mate, but I really need help here.
As per the suggestions, I tried flashing various images. In every image I flashed, the calling and wifi worked but cell data didn't work in any of those versions. Still I tried flashing Oreo with them but the error persisted. So probably, its something beyond I can do it with my little knowledge.
So finally, to give up I tried going to back to where I was before all this, to baseband version, I9505GUEUDNL3. I flashed NL3 image linked in the post https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 through Odin. While the OS shown in about phone is 5.0, the baseband version is stuck at OJ1, where the data does not work.
Any idea how I can go back to NL3 where data worked flawlessly?
Many thanks in advance.
Edit: I flashed NL3 modem from https://forum.xda-developers.com/showthread.php?t=2452034 but still the issue persists. I have nandroid backups from the very first time when I flashed another ROM. If I use that to restore, will it restore all the issues?
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
audit13 said:
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
Click to expand...
Click to collapse
Thank you.
Can you pls take a look at this thread? https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 Supposedly, these are factory images. I tried these images and my best guess is, they have right bootloader and modem. None of the sites you suggested carry stock images for GT-I9505G (Play Edition). They have GT-I9505 though.
What I tried so far.
- Flashed images linked above. Didn't work
(at one point, I even got OTA, when I was on OE1 baseband, it updated to OJ1. So in theory, in this OTA, it should fix this mismatch bootloader and modem, right?) When things didn't change after this update. I tried to flash NL3 image.
- Flashed NL3 image which I had. The baseband remained at OJ1. This was odd to me. So flashed NL3 modem. The issue persisted.
- I had taken nandroid backup before I started flashing custom ROMs. I tried to restore that back up through a custom recovery, TWRP. No help.
Screenshot of that backup, if it tells you anything
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- I have EFS Backups, but I don't quite remember how I took that backup.
Screenshot attached. Any idea if this can be used to restore everything in one shot. I don't know if EFS contains bootloader as well.
You mentioned I should flash stock ROM. Assuming that ROM images linked on the XDA thread above are untouched, shouldn't that fix the issue? If not, is there any possibility one can find bootloader images (if such thing exists) because modem images are available in another thread. One can pick and choose a combination to flash. I am just speculating. I have no idea if such a thing can be done.
Thank you so much. Really appreciate you sticking around to share the ideas.
P.S. - Is there any option where you can delete both bootloader and modem just before flashing the stock ROM via Odin or TWRP?
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
audit13 said:
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
Click to expand...
Click to collapse
So I flashed PF1 stock ROM, both bootloaders and modems are PF1. Made sure over the full day yesterday, there is no update and the problem persists. Can't flash Oreo and no cell phone data. Now, my interest in Oreo has pretty much died and only hoping to find a tweak to fix cell phone data. Fixed APN, made a factory reset just to be sure that its not the issue, tried SIM card in the different phone and other SIM in my phone that its not the SIM or the network thats the cause. So far I have not managed to find out what made the phone lose cell phone data.
Buff99 said:
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
Click to expand...
Click to collapse
Dang man, your comment came a little late after I managed to fcuk up my phone very well trying to install Oreo. It will be great if you folks can make this comment in OP of the respective ROMs so that next I9505G user won't mess it up royally the way I did. If I remember correctly, I read both the threads start to the end and I didn't find any comment on this issue of I9505G.
Thanks both of you for chiming in and trying to help. If there is any idea to fix the loss of cell phone data, that will be of great help.
Had this N4 for years. Flashed countless times. No emmc faults. Rock-solid reliable, until now.
The past week, it started stalling badly or rebooting. Mostly stalling, 1 in 10 bringing a reboot. Just freezes randomly for a few seconds. No common denominator. Clean-flashed another ROM with the same effects. Freezing and occasionally rebooting. This means it's dying, right?
Hello.
I never had the "emmc_read" fault either, but I had the same problems as you.
When you clean flash, you only wipe /data /cache /system ... But some essentials partitions are untouched like /EFS.
Let suppose (as an example) that you have a corrupted block somewhere in /EFS (/dev/block/mmcblk...) Any ROM you'll use will read your IMEI, and if the corrupted block is there, any ROM you'll flash will try to read your IMEI, get stuck, and will result the same problem : reboot, hang, etc.
Now my 1 cent advice : Make a backup from your partitions using EFS Professional : https://forum.xda-developers.com/ga...ol-updated-09-06-14-efs-professional-t1308546
And also using TWRP (better be safe than sorry)
(You'll need a specific version of BusyBox for EFS Pro)
And then, try to simply flash a stock rom using Odin, but with .PIT file for your model : https://forum.xda-developers.com/no...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
Flash a 1 file rom + pit and select "nand erase", and then a 4 files roms using the .pit and select "nand erase".
The whole nand is not really erased, you'll still have flashmode and your EFS safe.
It will repartition your device.
It may relocate the corrupted block somewhere else on the 32Gb internal storage.
It has fixed the issue for me... Hope it will fix yours as well.
Good luck.
PasSlert said:
Flash a 1 file rom + pit and select "nand erase", and then a 4 files roms using the .pit and select "nand erase".
Good luck.
Click to expand...
Click to collapse
I'll try this! Thank you! One question. What does the second half of this mean?
First half, simple enough. Flash a ROM and PIT, with Nand Erase checked. Got it. What does "then a 4 files roms using the .pit" mean?
ETA: Did not work.
Odin: "FAIL! Re-Partition operation failed."
Phone in Download mode: "SECURE CHECK FAIL : PIT"
O's said:
I'll try this! Thank you! One question. What does the second half of this mean?
First half, simple enough. Flash a ROM and PIT, with Nand Erase checked. Got it. What does "then a 4 files roms using the .pit" mean?
ETA: Did not work.
Odin: "FAIL! Re-Partition operation failed."
Phone in Download mode: "SECURE CHECK FAIL : PIT"
Click to expand...
Click to collapse
An official ROM can come in 2 ways :
4 files (+pit) : BL, AP, CP, CSC
1 file (+pit) : HOME
If you had a problem while flashing 1 file ROM + PIT, then try 4 files + pit.
You can find everything you need here : https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Your Odin screen should look like this while flashing the ROM :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You should be able to complete the "SECURE CHECK FAIL : PIT" using this method.
If not, you can still grab the PIT from your phone, but that's not the goal.
GL.
Thank you again! But I don't see a PIT file in the example image, or checks for Re-Partition and Nand Erase. What of those?
ETA: Thank you again, but I'm spending hours chasing dead links and bad leads. Do you have a working link to a 4-files ROM? That thread has only dead links for N910T files. A post says to use a program on a different thread to use phone info to find newest firmware on Samsung servers. Installed program. Won't read phone info. Thread suggests to install Qualcomm drivers. Installed. Program still won't read phone info. Inputting phone info manually requires specs I can only find with Phone INFO app from Play Store. That requires a working ROM. I somehow flashed MagMa even though TWRP said it couldn't mount anything. (Still doing stall/reboot issue.) Logged into Play Store, downloaded Phone INFO. Entered info from app. Firmware program kept saying "Could not send BinaryInform. Status code 200/401."
Edit 2: I found the EQI2 BL and CP. Still need the CSC. Got a stock EQI2 .tar. Got Odin 3.09 per screenshot (was on 3.13.3). Tried to flash with those 3 + PIT. Still "Re-Partition operation failed." It just immediately rejects the PIT file every time. Losing hope here. Can't even flash stock, let alone check the stall issue.
Edit 3: Progress! Tried 3 different N910T PIT files before one worked. Odin PASS! with BL/CP/AP/PIT (no CSC). Initial boot now.
Edit 5,000: Worse than before.
At first, it seemed great. Stock booted OK, randomly rebooted once, and then seemed fine. I stress-tested it with all the usual steps that froze it up before on N7 port ROMs, and stock did fine. So I thought it moved a bad sector as you said. Clean-flashed a reliable favorite N7 ROM, and it turned off during the flash. Tried again, and it flashed but didn't reach ROM boot animation; Samsung logo then black for a half-hour. Pulled the battery, tried to reboot, same thing: Samsung logo then endless black. Attempted to restore an old backup to see if still acted up in regular use. Didn't even get there: Stayed on the gears "Android is starting" screen a half-hour. Wiped cache/dalvik, same outcome. Not sure what to do with it at all now.
Thinking it's time to put this phone out to pasture, unless you have other observations or ideas. Thank you again for the help.
Hello,
So you've flashed stock ROM.
If repartition succeded it went into bootloop on Stock ROM, if you did not went into bootloop : repartition didn't work.
(Bootloop can be 'fixed' by entering stock recovery and wipe data/factory reset.)
If flashing stock succeeded, you had to re-flash TWRP 3.3.1 using Odin : https://forum.xda-developers.com/note-4/snapdragon-dev/recovery-twrp-3-3-1-0-t3933427
(1) From TWRP, you can select wipe (top right) a select every partition (make backup of your internal memory) but don't select sdcard and OTG.
Then reboot > recovery.
Then install > zip > your note 7 ROM, but check md5 value because your N910T turning off while flashing is a problem.
The 'kernel' from TWRP doesn't handle temp really well, sometimes the phone can become really hot... Or the flashing tried to use the bad sector again. And as it's randomly moved while repartitionning, there's not a lot of solution : flash stock rom 4 files with pit.
To isolate the problem, I suggest you to let your phone be cool before flashing N7 ROM. If while cold, the flash of the same N7 ROM (assuming md5 is correct) makes the phone turn off, then I'd say bad sector.
Edit : beside phone turning off while flashing, being stuck on 'android is starting' could be solved by a factory reset from TWRP (wipe > swipe to factory reset) after a flash of custom ROM. It's sometimes recommended. Mainly if you get stuck on optimising android.
Also Odin version doesn't matter, some says 3.07 is better for a specific android version, 3.09 is better for others (source https://www.**********.com/odin-version-samsung-device-compatibility-list/) ... Use at least 2 different ones, just to be sure to eliminate every possibility. Same for 4 files rom, try to find a 4.4.4. and a 5.0.1 for example. You never know.
If you have hard times finding on xda, google give a lot of 4 files rom while searching for "4 files n910t".
Edit2 : you had a hard time with Qualcomm drivers because your phone is not bricked. As long as you have a working flashmode to communicate with your phone using Odin : you don't need Qualcomm drivers. This driver is only when your download mode is not even accessible, and the APQ8084 is the only way to communicate with your device.
Edit3 : sometimes, a pit file can be inside the CSC file. You can open the CSC.tar.md5 using 7zip or WinRar. Try to "4 files + pit" method, and if doesn't work the "within the CSC.tar.md5 pit file" method, in both cases repartition should be checked in Odin tool.
Hope you'll fix it.
PasSlert said:
Hello,
So you've flashed stock ROM.
Click to expand...
Click to collapse
Hello,
Wiped everything but sdcard and OTG x3. N7 ROM installed successfully this time, but the phone turned off by itself while I let it sit at the Welcome screen.
Thank you again.
ETA: I used a different battery that time just to rule that out, too.
I also started having this issue where phone will reboot while in use.
I did used this emmc bug app and it said I am fine
One thing i noticed when my phone would reboot is that the middle right side of screen was warm
When it does reboot like that , it goes into bootloop.... Right after Samsung logo.
The only way to get out of bootloop was to take the battery out and let the phone cool down. After that the phone boots successfully without any issue.
So I am assuming that warming up of phone somehow loosens flash chip solder point leading to reboots and bootloop. Cuz if phone can reboot fine on cooling down maybe that bad solder point would hardens just enough for good connections to be made with motherboard... Just my theory that's it's due to poor quality control or chip balling.
However the last time it happened, I couldn't boot my phone no matter what. So had to flash stock firmware ( 1 file method) but as OP mentioned the phone got into bootloop at welcome screen.. Again i noticed that phone was warm at right top/ middle point of screen.
What I did was to take back cover off and put the phone screen down on cold floor or marble counter top to let the heat dissipate. Only then the phone boots fine.
Maybe try that or get the motherboard changed ( with one with good emmc chip)
It's a wakelock.....not mmc
trinilu27 said:
It's a wakelock.....not mmc
Click to expand...
Click to collapse
Sorry?
Search XDA article is on here somewhere you have to go to the Play Store and download a certain wakelock detector... it magically fixes the phone and I'm not even kidding... I've owned probably 30 no fours and all of them I thought emmc was crashing and I follow the instructions in the article and it worked every time
trinilu27 said:
Search XDA article is on here somewhere you have to go to the Play Store and download a certain wakelock detector... it magically fixes the phone and I'm not even kidding... I've owned probably 30 no fours and all of them I thought emmc was crashing and I follow the instructions in the article and it worked every time
Click to expand...
Click to collapse
That's app keeps the cpu and memory engaged hence the name wake lock
And yes it works with some minor battery drain
But let the phone get hot/very warm from use and it will crash nonetheless with or without this app.
Even those who have custom kernel and have changed the governors and such still experience this problem... Meaning it's hardware level issue
And this wake lock app is like a bandaid to that problem
eMMc problems are not that bad. I had it, ordered a board from Alibaba for ~$25, installed it, and all was well again.
ghostwheel said:
eMMc problems are not that bad. I had it, ordered a board from Alibaba for ~$25, installed it, and all was well again.
Click to expand...
Click to collapse
What garentee you have that the said board will be good?
fizzingbees said:
What garentee you have that the said board will be good?
Click to expand...
Click to collapse
None.
Mine was good, and several years later, still working.
O's said:
Had this N4 for years. Flashed countless times. No emmc faults. Rock-solid reliable, until now.
The past week, it started stalling badly or rebooting. Mostly stalling, 1 in 10 bringing a reboot. Just freezes randomly for a few seconds. No common denominator. Clean-flashed another ROM with the same effects. Freezing and occasionally rebooting. This means it's dying, right?
Click to expand...
Click to collapse
There is a way to see if it is a emmc fail.
Start up the device to the bootloader (home + start + volume down, then volume up), and in the upper left side of the screen there are some system messages. If emmc chip is faulty there will be corresponding message there (se Picture, second row. Altho i can't remember android logo looking like that.. LOL).
Certain faults i have personally experienced gave exactly the same symtoms like a busted emmc chip:
A bad battery - but you say that you already tried replacing it?
Firmware - i went back to original stock from sammobile and that solved it.
There are some fixes for the bad emmc chip, but in my experience they are all temporary. The only thing that worked permanently was to replace motherboard. I ordered from aliexpress, didn't choose the cheapest nor the most expensive ones. A bit tricky, but doable. I replaced a few so far, they all worked and are holding on almost a year after.
prkfsz said:
There is a way to see if it is a emmc fail.
Start up the device to the bootloader (home + start + volume down, then volume up), and in the upper left side of the screen there are some system messages. If emmc chip is faulty there will be corresponding message there (se Picture, second row. Altho i can't remember android logo looking like that.. LOL).
Certain faults i have personally experienced gave exactly the same symtoms like a busted emmc chip:
A bad battery - but you say that you already tried replacing it?
Firmware - i went back to original stock from sammobile and that solved it.
There are some fixes for the bad emmc chip, but in my experience they are all temporary. The only thing that worked permanently was to replace motherboard. I ordered from aliexpress, didn't choose the cheapest nor the most expensive ones. A bit tricky, but doable. I replaced a few so far, they all worked and are holding on almost a year after.
Click to expand...
Click to collapse
Would you consider sharing the link.
I have snapdragon varient.
Regarding this error mmc_read fail... This only appears when emmc chip is beyond use.
If e.g you have a loose solder that cause transient problems, then this message wouldn't appear.
If it does that means your chips is goner or going to be goner soon.
The signs of emmmc chip fail should be recognized at the earliest and data backup up along with replacing motherboard when wallet and time allows