Note - Sorry everyone; I've been so busy with work the past few days, and it doesn't seem to be letting up any time soon. I'll try to check in as much as possible.
This thread is mainly for rooting development / techniques and updates on the SGH-I927[R]; If you're looking for the latest (detailed) instructions, please see CarpeNoctem's guide here:
http://forum.xda-developers.com/showthread.php?t=1378082
If you want to participate in ongoing rooting/dev work, keep reading!
----
Success! The SGH-I927R was rooted on Dec 5, after a great team effort. We finally have the powerful device the Captivate Glide was meant to be! Special thanks to:
ardatdat, boog, CarpeNoctem, and everyone that helped keep this thread alive.
You've now got a couple options. If you don't mind the annoying little yellow triangle on boot-up (I think it looks kinda hackerish ), you can simply flash my insecure STOCK Rogers boot image (ro.secure = 0), attached to this message. I've never tested this against an AT&T ROM, so if you do, please report back how it goes!
Simply load this .tar up in the PDA section (same as procedure below), flash, and you should be able to adb in as root. Then, install your mode 6755 su binary into /system/xbin, and superuser.apk.
Note that you can always flash back to the stock kernel (also attached), when you're done rooting your device. This will restore the normal boot logo.
Alternatively, here are two pre-rooted ROMs:
Rogers Canada (SGH-I927R): https://rapidshare.com/files/1741701072/SGH-I927RUXKJ5_STOCK_ROOTED.tar.bz2
AT&T (SGH-I927): https://rapidshare.com/files/3058304268/I927UCKI3_STOCK_ROOTED.tar.bz2
1. Unpack the tarball, which will dump out a single tar file.
2. Put phone into download mode.
3. Launch ODIN, and select the file from the PDA flash option.
4. Don't touch anything else!
5. Flash the image.
Now, this goes without saying, but:
This is highly experimental! It could permanently brick your device! It worked for me, but I cannot accept any responsibility if something goes wrong!
At this point, it seems kernels and roms are interchangeable. I highly recommend the Rogers kernel, as it's not infected with CarrierIQ.
PS - Thank you Rogers, for doing the right thing!
The CL652095 is part of their build number, and modules from a different build won't work if that 'version magic' doesn't match.
So, if you try to build a kernel from other source (and the initramfs from your kernel) you will need to
Code:
export LOCALVERSION="-I927RUXKJ5-CL652095"
that way it will load the prebuilt modules properly.
But, if you can pull the zimage from the phone, it might be easier to just unpack, add su (or cwm, then you could flash root from cwm) and repack.
boog said:
The CL652095 is part of their build number, and modules from a different build won't work if that 'version magic' doesn't match.
So, if you try to build a kernel from other source (and the initramfs from your kernel) you will need to
Code:
export LOCALVERSION="-I927RUXKJ5-CL652095"
that way it will load the prebuilt modules properly.
But, if you can pull the zimage from the phone, it might be easier to just unpack, add su (or cwm, then you could flash root from cwm) and repack.
Click to expand...
Click to collapse
Yeah, assuming they're only using that to stamp the kernel and not to reflect their own (critical) patchset they've applied to the stock source.
I sent yet another request to Samsung support, and they're playing dumb. Their support guys claim to "not have the source" and be "not affiliated with the Samsung open source release center" (no joke).
I also filled out a request on their web form on the OSRC; I'll see what they say.
Honestly if there were a way to extract the kernel, we'd be golden. Unfortunately all mmcblk* devices are 007 masked or worse. Wonder if these devices have some undocumented "upload" mode.
Does anyone know if kies is able to force-recover a device with the emergency firmware recovery utility? Does the recovery mode use the main kernel that gets flashed by ODIN, or some separate kernel? ie. if I flash a bad kernel, is it lights out, or will recovery mode still work?
I know adam has been able to use UART to root devices and pull software.
Im pretty sure you need some hardware. But if anyone can find a way its adam.
Well, I'll be damned!
I made a request to the Samsung Open Source Release Center for the source, and they delivered!
I'm downloading right now and will report back shortly!
If anyone else is interested in checking it out, here's the link they gave me:
https://opensource.samsung.com/reception/receptionSub.do?method=downLoad&attach_id=1842
Go Samsung!
I'm not trying to make too much of a tangent but with an upgrade due in a few months I've been considering this device. would you recommend it? If the hardware is worthy I will definitely root& rom and contribute to the community when I have the time.
How would you compare it to to original captivate?
BigArea said:
I'm not trying to make too much of a tangent but with an upgrade due in a few months I've been considering this device. would you recommend it? If the hardware is worthy I will definitely root& rom and contribute to the community when I have the time.
How would you compare it to to original captivate?
Click to expand...
Click to collapse
Honestly, my only issue is the lack of rootability (which hopefully will be solved soon).
Now, I'm coming from a 2+ year old n900, so take my opinion with a grain of salt, but I have to say that the phone itself is spectacular. If it wasn't, I'd have returned it the day I realized it couldn't be easily rooted. It was good enough to make me hold out.
The display is gorgeous, form factor perfect, keyboard is decent enough (not as good as the n900's, but it was way above average), and the performance is, for me, mind blowing.
BigArea said:
I'm not trying to make too much of a tangent but with an upgrade due in a few months I've been considering this device. would you recommend it? If the hardware is worthy I will definitely root& rom and contribute to the community when I have the time.
How would you compare it to to original captivate?
Click to expand...
Click to collapse
slide-out keyboard, stock gingerbread, front-facing camera... in line for an official ICS upgrade (maybe????)... dual core CPU... faster HSPA+ downloads...
Ok, I successfully built a kernel for our device! Time to roll the dice.
...fires up ODIN...
Wish me luck!
Does anyone know offhand how to make a kernel insecure?
Try telling it that it needs to lose some weight. That should make it really insecure.
lol rof ! +10
I am going to request from the moderator to create a captivate glide dev subforum and Q&A.
Well, that got ugly.
ODIN failed to flash the new kernel, giving this error:
Code:
...
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now it's complaining I need to do a firmware recovery. Ugh.
I hope this is reversible.
Any ODIN experts monitoring this thread?
Also, does anyone know how to use KIES to perform an emergency recovery? The device isn't showing up in the list.
EDIT
Ok, this is bizarre. Out of desperation, I booted into 3e recovery mode, rebooted, and suddenly my device came back to life. Running fine. As if nothing happened. I checked the kernel timestamp (from /proc/version) and it's still the stock kernel, so the NAND update failed. I guess it must have flagged a failure, and that flag was reset by recovery mode!
lambgx02 said:
Ok, I successfully built a kernel for our device! Time to roll the dice.
...fires up ODIN...
Wish me luck!
Does anyone know offhand how to make a kernel insecure?
Click to expand...
Click to collapse
How did you build a kernel without the source being released??
jmtheiss said:
Try telling it that it needs to lose some weight. That should make it really insecure.
Click to expand...
Click to collapse
LMAO....+1
CarpeNoctem said:
How did you build a kernel without the source being released??
Click to expand...
Click to collapse
see post #5
lambgx02 said:
Well, that got ugly.
ODIN failed to flash the new kernel, giving this error:
Code:
...
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now it's complaining I need to do a firmware recovery. Ugh.
I hope this is reversible.
Any ODIN experts monitoring this thread?
Also, does anyone know how to use KIES to perform an emergency recovery? The device isn't showing up in the list.
EDIT
Ok, this is bizarre. Out of desperation, I booted into 3e recovery mode, rebooted, and suddenly my device came back to life. Running fine. As if nothing happened. I checked the kernel timestamp (from /proc/version) and it's still the stock kernel, so the NAND update failed. I guess it must have flagged a failure, and that flag was reset by recovery mode!
Click to expand...
Click to collapse
I have had issues with samsung's source. We have been playing with their kh2 source, and I get builds that seem to build successfully, but never boot. Had a few that wouldn't flash (using heimdall), for some mysterious reason that seem similar to what you got.
I would say you still need a backup zimage before trying to flash an unknown kernel. You could be stuck with a non booting phone without it.
Did anybody tried this kernel, same tegra2 same os and version: http://forum.xda-developers.com/showthread.php?t=1348857
when I compare the source from samsung there are some difference (ATT reference in the i927 one) but they are 99.99% similar
hi .. everyone here. I am the kernel developer for i9103.
Firstly, I do not get the Captivate Glide. But, could I do anything for the GLIDE? If I try to compile a kernel, I could not test in using my machine.
And I think you all know how to use Odin3 thru PDA to flash ROM & kernels?
ardatdat said:
hi .. everyone here. I am the kernel developer for i9103.
Firstly, I do not get the Captivate Glide. But, could I do anything for the GLIDE? If I try to compile a kernel, I could not test in using my machine.
And I think you all know how to use Odin3 thru PDA to flash ROM & kernels?
Click to expand...
Click to collapse
Honestly if you can compile the kernel with root and CWM that would be HEAVEN!!
I install your other kernel (curiosity I had to try) and bricked my phone
Also, do anyone get the original kernel (boot.img) for that phone? It will help me and be the most important part to have the compiled kernel working on the phone.
So, please, if anyone get the boot.img, please keep it, upload it and tell me. Thanks.
Related
Bay_wolf's AIO I9000 Toolbox 3.0
If this program has helped you, please consider donating.
Video Removed because connexion2005 felt that selling USB Jigs on my site was taking away from his sales of USB Jigs and his video was promoting the sales of mine. I'll be adding a short guide on how to use it to make up for the lose of the video.
Disclaimer: I'm distributing this program as-is and no guarantee that it will not hurt your phone. So, use at your own risk and don't blame me for bricking your phone. I am to not be held liable for any outcome of the use of this program.
Description: To help automate flashing custom ROMs onto the Samsung Vibrant. This is primarily designed for beginners but will help advanced users flash custom ROMs quicker.
READ BEFORE DOWNLOADING.
BEFORE EACH STEP: You must not mount the phone but have it plugged in with USB Debugging enabled.
This program doesn't come with a stock ROM. You must download it yourself. Here's a good place (Section B): LINK
The custom ROM you select must MUST NOT have spaces in the file name or else it won't copy correctly.
The program will act like it's not responding during the flash custom ROM step. Just let it do its thing (normally takes about 5-10 minutes).
First time you run it you must download the latest Titanium Backup if you intend to install it. From there on in, you have the option to download the latest or keep the version you downloaded.
Restore PRO License Key for Titanium Backup copies your Titanium Backup Pro License (TitaniumBackup_license.txt) that you should have gotten when you bought the program.
You do not need to root the phone in order to install a custom ROM (reason rooting was moved to the advanced section).
Programs/Files included:
ODIN 1.7
ClockWorkMod Recovery
Root Files
Android Debugging Bridge
Drivers
You need .NET 4 installed and the Microsoft Visual C++ Redistributable. Download .NET | Visual C++ 32bit & 64bit.
Download
Just in case anyone wanted them. Here are the drivers in a smaller and automated installer that I created. It's the same that's used in my program so if you have my program installed you don't need to worry about these. -32 bit -64bit
Donations are appreciated if you found this program helpful:
Changelog:
2.5 - Intial Release (Don't ask about version numbers haha)
Planned Features:
Smaller Download Size.
Smaller Install Size.
Fully Automated Backup and Restore.
Thanks for donations from:
connexion2005
FishDoc
qynt
novagator
Oxicottin
konazxiii
For2ndtwin
kvenubabu
meohman1
Hellrod87
movrshakr
this is immensely helpful, thank you! looking forward to seeing this one take shape keenly!
Bay_Wolf,
Just downloaded your AIO tool and tested it on my i9000.
It all worked, smooth and quick. Will try to get some more of the gang at Rom Kitchen to stress test it and give you feedback/suggestions. But a very nice first experience with it!
Will also point all of our noobs over here ... big time saver.
Many thanks!
this makes life much easier for sure
Yes, this is a real time-saver for people who keep flashing ROMs like me.
Very very nice application.
Thanks! I'm glad it's helping people out. Now we just need it to be a sticky so more new users see it. *hint hint*
-Bay_wolf.
Gonna try it out later today, but it is looking really good.
Excellent. Good work fella!
Shame its been buried in the apps section though......
Sent from my GT-I9000 using XDA App
Muy interesante.
Es posible en spanish ????
En caso negativo, si nos facilitarn el Xml, para poder traducir, y lo devolvemos para su inclusion.
Puede ser ?????
Gracias por todo
Very interesting.
It is possible in Spanish??
If not, if we facilitarn the xml, so translated, and return it for inclusion.
It can be ?????
Thanks for everything
Bay_wolf
Great little programme. I can't flash to stock though, odin gives me this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> PDA.tar.md5 is invalid.
<OSM> End...
Have I got a corrupt download or something? I have downloaded it twice and I get the same thing.
Just thought you may want to know.
Why JM9 was chosen as stock?
I heard, but don't have all the knowledge, that JM5 i sby far a better starting point, especially the version without bootloader. Some also say that JPC is a good start point. It was said that it is due to the fact these ROMS have some extra files I don't remember exactly...
I used to have JM5 as a starting point for a clean phone, so really not tempted to move to JM9 unless confirmed
jonny_ftm said:
Why JM9 was chosen as stock?
I heard, but don't have all the knowledge, that JM5 i sby far a better starting point, especially the version without bootloader. Some also say that JPC is a good start point. It was said that it is due to the fact these ROMS have some extra files I don't remember exactly...
I used to have JM5 as a starting point for a clean phone, so really not tempted to move to JM9 unless confirmed
Click to expand...
Click to collapse
I can confirm JM9 as a working alternative to JM5. JM8 is another ROM that works for cleaning your phone/starting a fresh. And AFAIK JM9 is not a low level package, meaning it doesn't flash your bootloader. So it is very safe. This guide also recommends JM9 http://forum.xda-developers.com/showthread.php?t=926399
Mothatt said:
I can confirm JM9 as a working alternative to JM5. JM8 is another ROM that works for cleaning your phone/starting a fresh. And AFAIK JM9 is not a low level package, meaning it doesn't flash your bootloader. So it is very safe. This guide also recommends JM9 http://forum.xda-developers.com/showthread.php?t=926399
Click to expand...
Click to collapse
Just trying to undesrstand. JM5 with no bootloader version was said to be the best as it contains dbdata.rfs files.
So, JM9 and JM8 also conatin these files? If yes, I personally prefere a start from JM9 as it won't default to serbian or russan language.
Sad to say that such a great program could not be downloaded by 1.3 billion people in China as multiupload is not accessible (thanks to the freaking stupid GFW).
Bay wolf, any possibility for a mirror?
P.S. I have clicked on the ads in your official site, but d/l link still points to multiupload.
Rdgs
Jamalsid said:
Bay_wolf
Great little programme. I can't flash to stock though, odin gives me this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> PDA.tar.md5 is invalid.
<OSM> End...
Have I got a corrupt download or something? I have downloaded it twice and I get the same thing.
Just thought you may want to know.
Click to expand...
Click to collapse
That should have been fixed with the latest version as the md5 at the end of the file was causing some issues. If it still doesn't work for you then just keep an eye out for version 3.0 which will make everything more automated and use Heimdall to flash.
buyaoxiao said:
Sad to say that such a great program could not be downloaded by 1.3 billion people in China as multiupload is not accessible (thanks to the freaking stupid GFW).
Bay wolf, any possibility for a mirror?
P.S. I have clicked on the ads in your official site, but d/l link still points to multiupload.
Rdgs
Click to expand...
Click to collapse
If there is a filesharing site that you can use then let me know and I'll upload it to that. If not then do torrents work for you? As I can create a torrent,
I'm not sure if heimdall would be such a great idea considering you can't repartition without flashing the boot loaders (risky) and you have to reserve a usb slot for it
Sent from my GT-I9000 using XDA App
Bay wolf- I think a torrent would be a great addition.
Sent from my GT-I9000 using XDA App
Mothatt said:
I'm not sure if heimdall would be such a great idea considering you can't repartition without flashing the boot loaders (risky) and you have to reserve a usb slot for it
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I've talked with the developer of Heimdall and he said that repartitioning isn't required to go back to stock (ODIN 1.0 & 1.3 don't do it) and I've verified this on my captivate. I've made a 3.0 version using Heimdall for the Captivate and it has been tested on my device multiple times. The feedback of the Captivate version will be the true test and if it works I'll make the Vibrant and I9000 editions use Heimdall.
js8 said:
Bay wolf- I think a torrent would be a great addition.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Will try to make one sometime. If you want you can make one and PM me the link and I'll add it to the download page.
Hi all, I’m having some trouble with my SGS2. I’ve searched for the better part of several days and read a lot of threads with similar but slightly different issues and I haven’t seen any definite solutions so I want to ask the experts before I do something stupid. Sorry for the long post but I want to include as many details as I can so no one has to use their crystal ball to figure out what is going on.
The other day my Sprint (really it is through Ting but it is branded as Sprint) SGS2 would not wake up from sleep after charging all night. It was running a GB27 rooted, full restore stock ROM I flashed through Odin (downloaded via rwilco’s very nice site). The flashing was done over a month ago and I didn’t have any troubles until this. Pressing and holding the power button did nothing, so I removed the battery to restart the phone. It was stuck in a boot loop at the “Samsung Galaxy S2” boot screen. Removed the battery for over an hour, tried again, same thing. I can boot into Odin download mode by using power+vol down. I don’t have CWM so I can’t try any other recovery options.
I tried using Odin to reflash the same ROM--GB27, rooted, full restore. This is Odin v1.81 one-click from rwilco’s site. I made sure all Kies processes were killed and started the reflash process and it got stuck trying to write cache.img. I left it for well over an hour and it never progressed past this point. Usually I’d see the blue progress bar on the phone during the flash process but it never appeared. This is the log from odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> cache.img
The log stopped here and after an hour, I unplugged the phone. I can still get to odin download mode, but instead of the “Samsung Galaxy SII” boot screen, I just get the “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.” I gather that a flag is set during the flash process, then is removed once the flash process completes successfully. Tried to flash again many times with different USB cable/port etc, but no luck.
The next step, I read through the FAQ on this forum and decided to try flashing EL29 via odin one-click (downloaded from here: http://www.rwilco12.com/downloads.p...-D710)/Stock ROMs/GB/EL29/Full Restore/Rooted). This used Odin v1.85. I left all options as the default and selected the PDA file but got these messages:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.bin
<ID:0/003> NAND Write Start!!
However, it never seems to progress from here even after an hour. I never see any blue progress bar. Also tried again using different USB cable and port, but no luck.
My phone isn’t viewable from Kies.
I’m at a loss for what to do next. I’d try to flash more versions, but I don’t know enough about this emmc bug and don’t want to trigger it. Reading around, I see suggestions about repartitioning and flashing PIT files, but this seems risky. I am also looking if there is any danger flashing from jellybean to non-jellybean builds.
I read about flashing just the kernel, modem and ROM separately but which files should I use? I also read about flashing a CWM kernel so I can get into recovery mode but I’m still not certain which files I should be using. I will also admit I don’t know how to flash only a kernel through odin. It looks like you use the PDA box like what I did above, but I thought that was for full ROMs? Do you use the PDA box for both kernels and ROMs?
I did find this thread http://forum.xda-developers.com/showthread.php?t=2289007 which is very similar to my issue, but I’m not sure if I messed something up by trying to reflash the same ROM.
What should I try next?
Sorry for the simple questions but I want to learn! Thanks for the help!
Very interesting. Seems like there is some nastiness going around with jellybean and our phones. The emmc bug was initially ICS, don't know if it carried over, but due to the high number of phones crashing, there must be some form of corruption going on.
Sent from my SPH-D710 using xda premium
noobtoob said:
Very interesting. Seems like there is some nastiness going around with jellybean and our phones. The emmc bug was initially ICS, don't know if it carried over, but due to the high number of phones crashing, there must be some form of corruption going on.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Agreed. The fact that it happens unprovoked is particularly worrisome.
This is the exact type issue I tried moving and helping the other day. I an now at quite a loss. We could have you just try and Odin flash a kernel. Yes, you would just use the PDA button to select your .tar file. Put a ROM in your SD card, and clean/flash this way, but that proved unsuccessful least time as well.
Sent from my SPH-D710 using xda premium
noobtoob said:
This is the exact type issue I tried moving and helping the other day. I an now at quite a loss. We could have you just try and Odin flash a kernel. Yes, you would just use the PDA button to select your .tar file. Put a ROM in your SD card, and clean/flash this way, but that proved unsuccessful least time as well.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks. I did find your post here on a similar thread and it was what made me post this... I wasn't sure if I could salvage it before getting to the point where I couldn't get into odin mode.
So you think flashing EL26 with CWM recovery would be my best option? I'm curious if when I tried to flash EL29 it didn't do anything since the previous flash had stalled... so maybe I avoided the scenario mentioned in your post above. From the log it still looks like it flashed recovery.bin though, so I don't know.
tanminivan said:
Thanks. I did find your post here on a similar thread and it was what made me post this... I wasn't sure if I could salvage it before getting to the point where I couldn't get into odin mode.
So you think flashing EL26 with CWM recovery would be my best option? I'm curious if when I tried to flash EL29 it didn't do anything since the previous flash had stalled... so maybe I avoided the scenario mentioned in your post above. From the log it still looks like it flashed recovery.bin though, so I don't know.
Click to expand...
Click to collapse
Well, at this point I don't know. I see this happening a lot now. I have been flashing exclusively through mobile Odin and roms that I had on my SD card except the other day when I tried the pit and tar files from that post. Seems more and more people are running into bricking all of a sudden a lot right now. I think sprint or Samsung need to get involved and do some phone replacement. I would take a poll and see how many people have bricked using just a stock ROM. It could have something to do with the hardware version of something in your phones. I am not anywhere smart enough to figure that stuff out, I can just offer advice and test things I know (or knew) to be safe ATM.
Sent from my SPH-D710 using xda premium
Are you able to flash a one-click ICS or GB ROM? Specifically FL24. My phone didn't like GB27 either (thankfully no bricking). I was able to flash EL26 with CWM by using the one-click twice. The first flash never seemed to work the first time, even though it said it was successful. Flashed several AOSP ROMs from there without issue.
bigj231 said:
Are you able to flash a one-click ICS or GB ROM? Specifically FL24. My phone didn't like GB27 either (thankfully no bricking). I was able to flash EL26 with CWM by using the one-click twice. The first flash never seemed to work the first time, even though it said it was successful. Flashed several AOSP ROMs from there without issue.
Click to expand...
Click to collapse
Flashing with one-click twice? Wouldn't that be a double-click?
I've tried using Odin non-one-click to flash EL26 w/ CWM but Odin just stalls at "NAND Write Start." But interestingly, it is incrementing the flash counter and "current binary" now reads "custom" where before it read "Samsung Official." So at least it's doing something. Time to search on how to get past these stalled flashes... from this thread it doesn't look particularly promising...
Just to provide an update to anyone who comes across this thread and has the same issue. I tried pretty much everything I could think of. I tried flashing all of the odin one-clicks I could get a hold of (GB/ICS/JB). I tried flashing tars. I tried flashing just kernels (GB/ICS/JB). I tried all kinds of recovery kernels, EL26 CWM etc. Of course I used all different versions of odin, different computers, different cables, different USB ports, etc.
I read the repartitioning thread (well at least quite a bit before people started asking the same questions over and over again). I downloaded the 92 different PIT files for the E4GT and tried flashing all of the different kinds of pit files... ones that moved the system partition, ones that moved data, ones that moved factoryFS, ones that shrank the UMS partition. Of each of those I tried different shift amounts...1GB, 3GB, 8GB, etc. I tried flashing with "repartition" unchecked (not sure what it really would do but it was suggested somewhere so I tried it).
Nothing worked. It'd always stall trying to write to the device. For flashing PIT files odin would start with "SET PARTITION" and just hang for over an hour and never progress. Still very strange that I could get into odin and usually on each attempted flash it would increase the flash counter. And strange as well that I was running rooted stock and this seemed to happen on its own.
The best I can figure is I'm really unlucky and have some bad blocks in memory at just the wrong spot to prevent the flashing process from completing.
Thanks for the update tan. Someone else has this very same issue. Looks like as of now there's no solution. That really sucks.
Sent from my SPH-D710 using xda premium
jdsingle76 said:
Thanks for the update tan. Someone else has this very same issue. Looks like as of now there's no solution. That really sucks.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I woke up this morning with the same issue. My phone was fine when I put it on the charger last night. This morning it was off, when I turned it on just samsung logo boot loop. I could not boot to recovery. I've tried to Odin a new recovery and a once-click full ROM. Odin stalls at recovery.bin either way.
wraith404 said:
I woke up this morning with the same issue. My phone was fine when I put it on the charger last night. This morning it was off, when I turned it on just samsung logo boot loop. I could not boot to recovery. I've tried to Odin a new recovery and a once-click full ROM. Odin stalls at recovery.bin either way.
Click to expand...
Click to collapse
Sorry to hear you have the same issue. You may read up on repartitioning and try that---you might have better luck than I did.
tanminivan said:
Sorry to hear you have the same issue. You may read up on repartitioning and try that---you might have better luck than I did.
Click to expand...
Click to collapse
I couldn't perform any of the standard repartitioning methods because recovery was not accessible (couldn't run the bad sector scan), nor was Odin working with any sort of TAR. I also reviewed the various PIT files, but based on your review of the same 100 odd files I was reviewing and finding that none of them seemed to relocate recovery addresses (we are stalling on recovery not sys or user), I threw in the towel and took it into a local Sprint repair store. The tech confirmed the issue, he was unable to factory flash it at all. His diagnosis was "something is seriously corrupted", but was very nice about it. He didn't even mention my dozen or so flash count showing in odin mode from my recovery attempts. Oh, and I told him flat out that I had tried to recover it via odin. I had the Insurion coverage, (drop/break/wet), not full TEP, but they were still able to order a replacement for $53. If you have TEP it might be a no charge replacement. He also noted aside that hes seen this a couple other times lately, not to read to much into that but it may be that the lemon memory modules Samsung pawned off on this device might be starting to just up and die instead of waiting to be overwritten wrong. I only say that because I haven't flashed a thing in months by Odin or recovery, and when mine died it was (or should have been) sleeping.
Thanks for the posts, they saved me the frustration of further investigating the PIT files, and got me into the repair shop quickly. I have a 5 day wait for the replacement, and my pregnant wife is due any time. I can't afford to be without a phone for long. I could have procrastinated for days without finding this research.
I'm up for upgrade in just like 2 weeks now, and this has me wondering if I should even chance another Samsung product. The HTC One is looking better and better, even though I'm not sure I can part with having an SD card and replaceable battery. Time to start looking around to see if the SG3 and Note2 have had all these EMMC issues. I want the SG4 but not if this is a running problem.
Note 2 doesnt.
Sent from my SPH-L900 using Tapatalk 2
wraith404 said:
Thanks for the posts, they saved me the frustration of further investigating the PIT files, and got me into the repair shop quickly. I have a 5 day wait for the replacement, and my pregnant wife is due any time. I can't afford to be without a phone for long. I could have procrastinated for days without finding this research.
I'm up for upgrade in just like 2 weeks now, and this has me wondering if I should even chance another Samsung product. The HTC One is looking better and better, even though I'm not sure I can part with having an SD card and replaceable battery. Time to start looking around to see if the SG3 and Note2 have had all these EMMC issues. I want the SG4 but not if this is a running problem.
Click to expand...
Click to collapse
Thank you, not a problem. Congrats on your upcoming baby!
Unfortunately I'm with Ting, so not am I only out of warranty and official repair options, but the full $500 unsubsidized cost of the phone as well. I'm optimistic, however. I purchased a Sprint SGS2 with a broken screen on ebay for around $50 and swapped the motherboard. Unfortunately it turns out the ESN had been flashed to another carrier so I'm trying to figure out how to flash it back...
I have the same feelings on whether my next phone will be a Samsung device as well. I guess time will tell how good the S4 is.
I posted my problem on androidcentral earlier today, I'm not progressing anywhere with my situation, I've copied my original posts with some edits here. If you need more information for helping me to resolve this dilemma, ask right away.
I'm in deep****. It started when i tried changing the fonts on my galaxy s3, simple install and reboot. Now when it rebooted it got stuck on the Metro PCS logo screen, I turned it off and turned it on again, and same problem. Then I tried flashing my g3 with odin it said pass, but now my model number has disappeared from the samsung boot screen and it still has the same problem prior; before it said Samsung Galaxy S3 SGH-T999N, but now it just shows Samsung Galaxy S3. Prior to all this my phone was already rooted. I'm a noob and I need help. All the details I remember about my phone is that the carrier is Metro PCS, the model is SGH-T999N (a t-mobile variant) and the OS was Jellybean 4.1.2.
Thankyou for reading, please reply soon its urgent.
*Extra notes, I tried booting it up into recovery mode it shows splash screen for a brief moment and then completely turns off. It is still able to go in to download mode, also when the phone is completely off and charged in, the battery charging animation is still normal/unchanged before all this happened.
-I've also tried using GS3 Toolkit, but I really don't know which build to use for my predicament, I've tried using the t-mobile SGH-T999 builds but theyre not working at all, just adding to my flashcount.
*Additional notes, when in download mode the information at the top left corner reads as:
ODIN MODE
PRODUCT NAME: SGH-T999N
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CUSTOM BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
tookutz said:
It failed to flash, I tried 3 times, here is the log of the 3rd/last attempt with that .tar file.
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
What else can I try? I doubt I'll be able to replace it with the warranty by now.
Click to expand...
Click to collapse
tookutz said:
Isn't that only on verizon's variants? I don't remember anything having to do with the bootloader, but I did successfully root my phone, so maybe I did, I'm not completely sure.
*Edit, Could you also give me a detailed guide as to how I could reset it with Kies? I'm not sure if it will work or not, because in my first postt, if it wasn't clear, I think I used the wrong .tar which made the model number under the samsung boot screen, disappear.
Click to expand...
Click to collapse
tookutz said:
I'm still stuck on the KIES method, I removed my sd card and found that my titaniumbackup update.zip, also I found the folder where my KIES backup files are that I made on kies a few days ago. Please continue helping me.
*Edit, okay I found my IMEI through the google dashboard, it was also the same number on the sticker under the battery. FML. Okay so when doing the Kies method it asks me for the model name, I enter SGH-T999N, now it prompts to ask me for the s/n, I copy and paste in the IMEI, but it says that it is incorrect. PLEASE HELP
Click to expand...
Click to collapse
If you are still able to get into Download mode, flash back to stock using @DocHoliday77 guide here: http://forum.xda-developers.com/showthread.php?t=2308514
No, sorry man but I'm pretty sure you bricked it. There us no firmware available for the T999N yet. You flashed T999 firmware.
In the future, if you get stuck during boot, factory reset will almost always fix it.
I have an image that I've got to pass to KAsp3rd that he can hopefully use to create a debrick method for the T999N. I'll send it to him in a few min. But once he's got it ready, it should fix you up....hopefully! I've also just received the files I need to create a stock Rom and Odin firmware for it. I'll try to get it all together and will let you know.
In the meantime check his thread, it's stickied in development.
Sent from my SGH-T999L using Tapatalk 4
Actually, @KAsp3rd already has the T999N image. Mustve forgot or missed it or something! Anyway, he may already have the other partitions that were flashed, and if so he should already have everything you need to get working again. If not, I'll have to look, but I might have a copy of all the ones you will need.
@tookutz if you can jump over http://forum.xda-developers.com/showthread.php?t=2439367 and see if we can give you a hand. There is a link to the irc channel that I'm usually in as well in the OP of that thread..
KAsp3rd said:
@tookutz if you can jump over http://forum.xda-developers.com/showthread.php?t=2439367 and see if we can give you a hand. There is a link to the irc channel that I'm usually in as well in the OP of that thread..
Click to expand...
Click to collapse
I feel like this this morning is christmas lol, I wake up and find such helpful replies, I'll give it a look thankyou so much everyone
*Edit, for the list of requirements do I need both the Linux Live Disc and the Linux Virtual Machine? Or is it either or? Also I have an 8gb Micro SD would that suffice? or does it absolutely have to be 16gb+?
tookutz said:
I feel like this this morning is christmas lol, I wake up and find such helpful replies, I'll give it a look thankyou so much everyone
*Edit, for the list of requirements do I need both the Linux Live Disc and the Linux Virtual Machine? Or is it either or? Also I have an 8gb Micro SD would that suffice? or does it absolutely have to be 16gb+?
Click to expand...
Click to collapse
It is either or on the Linux and it has to be 16G or greater. We have tested on 4 and 8gb and they both failed
KAsp3rd said:
It is either or on the Linux and it has to be 16G or greater. We have tested on 4 and 8gb and they both failed
Click to expand...
Click to collapse
Okay so just to be clear, cause I always jump to conclusions and get confused x.x, I can run a Linux Virtual Machine on my Windows 7 laptop? And I'll stop by staples later today and get a new micro sd.
tookutz said:
Okay so just to be clear, cause I always jump to conclusions and get confused x.x, I can run a Linux Virtual Machine on my Windows 7 laptop? And I'll stop by staples later today and get a new micro sd.
Click to expand...
Click to collapse
You can run a VM or boot to a "Live" version that has a Persistence mode on a USB Stick. UNETBootin or LiLi (LinuxLive USB) both work great for this making the Live USB images of major distros, such as Ubuntu (and variants).
tookutz said:
Okay so just to be clear, cause I always jump to conclusions and get confused x.x, I can run a Linux Virtual Machine on my Windows 7 laptop? And I'll stop by staples later today and get a new micro sd.
Click to expand...
Click to collapse
Yes that is correct. If you watch the video in my thread I did the linux portion in a VM. There apparently are windows tools out there for properly managing .img files however I've not used any so therefore cannot recommend any.
KAsp3rd said:
Yes that is correct. If you watch the video in my thread I did the linux portion in a VM. There apparently are windows tools out there for properly managing .img files however I've not used any so therefore cannot recommend any.
Click to expand...
Click to collapse
I'm in class right now, so all I can do is read and re-read this thread lol, can't wait to give it a try x-x
tookutz said:
I'm in class right now, so all I can do is read and re-read this thread lol, can't wait to give it a try x-x
Click to expand...
Click to collapse
If you need any help with it you can join me in IRC or ask in the thread with the walkthrough (if you have more then 10 posts) and if not me someone else should be able to help you
KAsp3rd said:
If you need any help with it you can join me in IRC or ask in the thread with the walkthrough (if you have more then 10 posts) and if not me someone else should be able to help you
Click to expand...
Click to collapse
KK, this will be my 10th post lol, I joined your IRC I think. Im in the #teambuild
Ok, I guess I might be jumping in between conversations but I guess I need help with almost the same thing that happened with OP.
http://forum.xda-developers.com/showthread.php?t=2467692
I didn't try to root it yet, though i would love to, and I am new to a few jargon here.
Please help me out guys.. @KAsp3rd: you mentioned you had a forum to debrick or unbrick the phone. I am not sure whether I bricked my phone or not, but I would like to give it a read at least. Can you please mention the link here. Thanks.
Also, I trying the recovery mode (Home+volume up+power) but it doesn't come up. It just vibrates and the screen remains blank.
I try the download mode (Home+volume down+power) and it shows up with the option to continue to cancel.
I think I will add this info in my original post as well.
Please see if any of you could help me with it.
Thanks.
shanxthechashmich said:
Ok, I guess I might be jumping in between conversations but I guess I need help with almost the same thing that happened with OP.
http://forum.xda-developers.com/showthread.php?t=2467692
I didn't try to root it yet, though i would love to, and I am new to a few jargon here.
Please help me out guys.. @KAsp3rd: you mentioned you had a forum to debrick or unbrick the phone. I am not sure whether I bricked my phone or not, but I would like to give it a read at least. Can you please mention the link here. Thanks.
Also, I trying the recovery mode (Home+volume up+power) but it doesn't come up. It just vibrates and the screen remains blank.
I try the download mode (Home+volume down+power) and it shows up with the option to continue to cancel.
I think I will add this info in my original post as well.
Please see if any of you could help me with it.
Thanks.
Click to expand...
Click to collapse
Can you post exactly the link that you flashed on your phone? Sounds like you might have done the same thing that the OP did and flashed a bad kernel
t999N
Ive apparently flashed T999L firmware to my gfs T999N I just got her and am reduced to edge, everything else is working great but I've hit a wall here and want to either flash back to stock or fix the issue. Carrier is Metro.
I used root66 method for the T999L described in this thread
http://forum.xda-developers.com/showthread.php?p=43772039&highlight=t999n#post43772039
and flashed this file
http://sourceforge.net/projects/d2ltetmo/files/Use In Odin/MB7system.tar.md5.7z/download
From what I now gather I shouldn't have done this and now cannot find a way to get back to stock.
I found this in my searches but I don't know how / if I can use the files to restore,
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-T999N
Please excuse my noobness. Any help would be uber appreciated.
Thanks.
mrrexsocks said:
Ive apparently flashed T999L firmware to my gfs T999N I just got her and am reduced to edge, everything else is working great but I've hit a wall here and want to either flash back to stock or fix the issue. Carrier is Metro.
I used root66 method for the T999L described in this thread
http://forum.xda-developers.com/showthread.php?p=43772039&highlight=t999n#post43772039
and flashed this file
http://sourceforge.net/projects/d2ltetmo/files/Use In Odin/MB7system.tar.md5.7z/download
From what I now gather I shouldn't have done this and now cannot find a way to get back to stock.
I found this in my searches but I don't know how / if I can use the files to restore,
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SGH-T999N
Please excuse my noobness. Any help would be uber appreciated.
Thanks.
Click to expand...
Click to collapse
Quick bit of advice....only post in one thread. When people repost their issue in multiple threads it makes it difficult to keep up with what's been done, what's been asked/answered, etc.
And The last link you posted is just the kernel source, nothing more. It won't help.
Sent from my SGH-T999V using Tapatalk 4
KAsp3rd said:
Yes that is correct. If you watch the video in my thread I did the linux portion in a VM. There apparently are windows tools out there for properly managing .img files however I've not used any so therefore cannot recommend any.
Click to expand...
Click to collapse
Can you please send me galaxy s3 T999N image
Phone Stats
Sprint Galaxy S3 (SPH-L710)
Cyanogenmod 10.2 (Stable)
Last ROM update flash was months ago, no issues
TWRP latest
Can not get into recovery
Can get into download mode (using HOME+VOL-DOWN+POWER)
Using Odin 3 (1.85)
Phone was sitting on table, just started boot looping.
Tried to flash (everything) - stock Sprint image, CM ROM, etc.
Odin fails when it gets to reading the PIT information.
I looked everywhere for a Sprint GS3 PIT file, only found one, but it was labeled "i710" (probably by accident) and did not work.
If anyone has or can dump an image of their partition information (PIT) I would be extremely grateful, and willing to compensate you, because I'm an Android developer and kinda need my phone =)
More information:
Yes drivers are all installed and working. Phone is recognized as usual on three different laptops.
Yes phone was charged at least over 80% when trying anything.
Yes, tried multiple cables and USB ports (esp. powered ones) - phone connects fine.
Brought it to Sprint - they actually tried to flash it for me (nice guys!) but the software denied b/c of the custom binary.
Yes, I read every post here/elsewhere containing the keywords "PIT", "S3", and "brick" - many solutions would work, except for the fact that Odin won't get past reading the PIT.
No, I didn't do anything dumb like flashing GSM, international, custom crap, or by checking "repartition" or anything like that.
Not using any custom kernel or anything else - only the recovery (TWRP) and ROM (CM10) are custom.
Even more information (yes, I'm desperate!):
I tried all methods I could find - literally days worth of searching - including reinstalling the drivers, installing drivers while in download mode, connecting from Windows 7, Windows 8, Windows 8.1, and Linux (Ubuntu - Mint).
Tried flashing stock recovery.
Tried flashing stock Sprint/Samsung image.
Tried flashing various PIT files claiming to be Sprint SGS3.
I basically gave in and was going to buy a new phone, but the dude at Sprint even said "this is fixable - you just need that PIT file", so I'd like to give it one last try before calling it. The phone really has been good to me, otherwise.
Any help is greatly appreciated! If you read all of this, you're a saint =)
Adding Odin output
CorporalMaxSterling said:
Adding Odin output
Click to expand...
Click to collapse
Relevant thread for anyone following:
http://forum.xda-developers.com/showthread.php?p=48376031#post48376031
DELETE: I see you have another thread about this already
sent from my GS3
joeyhdownsouth said:
DELETE: I see you have another thread about this already
sent from my GS3
Click to expand...
Click to collapse
Thanks. That's real helpful. It's not my thread, it's a related one I found after I posted, and this info is still relevant.
How do i get a rom on my note 4 i have sprint running N910PVPS4DPE
peterogg said:
How do i get a rom on my note 4 i have sprint running N910PVPS4DPE
Click to expand...
Click to collapse
Did you try Samsung Kies on. PC?
jimmbomb said:
Did you try Samsung Kies on. PC?
Click to expand...
Click to collapse
Hey I always use TWRP to flash Supersu to root but I was wondering cause Ive been asked several times what easiest way to root. My question is = Does CF Auto Root still work for our device or is it just for older firmware? Thanks in advance!
What's the best way to update to the latest OTA on a rooted phone without losing data or root?
Sent from my SM-N910P using XDA-Developers mobile app
skanndelus said:
What's the best way to update to the latest OTA on a rooted phone without losing data or root?
Sent from my SM-N910P using XDA-Developers mobile app
Click to expand...
Click to collapse
With systemless root can't we just flash back stock kernel and recovery, to accept ota. Or does phone still not pass system check for ota. I've never tried myself so I was wondering.
My phone is on PD1 via OTA update.
Unrooted and stock as bones in a bag.
Yet, Now it refuses to check for updates anymore.
Manually or auto update checks via wifi.
Im locked out of latest updates.
Any ideas?
Even keis says up to date, even though the PE1 has been out for a while.
Any id
Thanks.
peterogg said:
How do i get a rom on my note 4 i have sprint running N910PVPS4DPE
Click to expand...
Click to collapse
First step is to use Odin to flash twrp or cwm ( I use twrp)
After that boot to twrp and create a back up (always do a back up)
Then go to wipe, advanced wipe and wipe dalvik, system,data, and cache.
From there go to install and select the rom you want to install and swipe to to install. Make sure your phone is on the correct baseband and firmware version to run the rom otherwise you will have issue like WiFi not turning on and camera not focusing! Reading the OP of the rom is very important. Being on PE1 you would probably have to downgrade to OK1 or PC1/PD1 for majority of roms for now. Freeze has a page where he has all the firmwares and their baseband, you can just dl them and flash them through Odin. Let me know if you need anything explained. If you mean how to literally get the rom onto the phone, I usually will just download or put the SD card into my computer. Another good option is samsung side sync/android file transfer
---------- Post added at 12:23 AM ---------- Previous post was at 12:21 AM ----------
jimmbomb said:
My phone is on PD1 via OTA update.
Unrooted and stock as bones in a bag.
Yet, Now it refuses to check for updates anymore.
Manually or auto update checks via wifi.
Im locked out of latest updates.
Any ideas?
Even keis says up to date, even though the PE1 has been out for a while.
Any id
Thanks.
Click to expand...
Click to collapse
Did you manually unroot? Or did you flash back to a stock? You need to completely flash a stock firmware to take an OTA.
---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------
aaron74 said:
Hey I always use TWRP to flash Supersu to root but I was wondering cause Ive been asked several times what easiest way to root. My question is = Does CF Auto Root still work for our device or is it just for older firmware? Thanks in advance!
Click to expand...
Click to collapse
I would say go with manually flashing root. CF auto root hasn't worked for me in a long time. Besides majority if roms you'll find are prerooted anyway so there's no reason to really have to flash a root. Unless of course you're rooting stock.
I have never rooted. Always bone stock since new and always have OTA the updates. 3 maybe so far.
Still cant OTA anymore
hi every one
i have a question
i just bought a sprint galaxy note 4 and im living outside USA and my problem is that i have this annoying message of handsfree activation and i cant also select cdma or lte i just can use gsm
my android version is marshmallow 6.0.1
and my device isnt rooted
so please help me to unlock my phone and what is the best way to root it safely
Hi, mine it's the same situation, anybody can help us with that because the gsm speed is to slow for navigate, thanks in advance.
I don't know if this thread is still active.
Okay,
So I have a Sprint 32gb model Note 4 SM-N910P UD, I was experiencing the random reboot issue so I removed the sim card, thought it was fixed and tried to install a sprint pushed update via the phones normal process. It power cycled in the update and now it's pretty bricked, I can't do a factory reset or clear cash. If I turn it on it goes straight into the "Firmware upgrade encountered an issue screen"
Now I try to be pretty self sufficient so I did some reading and downloaded two versions of Kies (both of which don't recognize my device) I downloaded three versions of Odin and have been attempting to restore with stock platforms. This is where I ran into my problem, I know nothing about this stuff and I am completely lost. I tried to go to Best Buy and their Samsung techs couldn't help me.
I've tried searching the site, but all the links people provide are to multiple versions of TWRS and basebands, but I don't know what those are or which ones I am supposed to download or what slot or order they are supposed to go into in Odin to re-flash this device, I keep getting "need PIT file" or other errors.
So I am throwing myself at the mercy of the court, is there an idiots guide to how I get this phone back up and running in a basic configuration? I don't need the latest update, or to even save the data that was on it before, I just need it to run like normal and I'll never download an update again. If you can link me to the thread of just tell me "look dummy download this files and install them in this order" I will be forever in your debt.
The_Malhavoc said:
Okay,
So I have a Sprint 32gb model Note 4 SM-N910P UD, I was experiencing the random reboot issue so I removed the sim card, thought it was fixed and tried to install a sprint pushed update via the phones normal process. It power cycled in the update and now it's pretty bricked, I can't do a factory reset or clear cash. If I turn it on it goes straight into the "Firmware upgrade encountered an issue screen"
Now I try to be pretty self sufficient so I did some reading and downloaded two versions of Kies (both of which don't recognize my device) I downloaded three versions of Odin and have been attempting to restore with stock platforms. This is where I ran into my problem, I know nothing about this stuff and I am completely lost. I tried to go to Best Buy and their Samsung techs couldn't help me.
I've tried searching the site, but all the links people provide are to multiple versions of TWRS and basebands, but I don't know what those are or which ones I am supposed to download or what slot or order they are supposed to go into in Odin to re-flash this device, I keep getting "need PIT file" or other errors.
So I am throwing myself at the mercy of the court, is there an idiots guide to how I get this phone back up and running in a basic configuration? I don't need the latest update, or to even save the data that was on it before, I just need it to run like normal and I'll never download an update again. If you can link me to the thread of just tell me "look dummy download this files and install them in this order" I will be forever in your debt.
Click to expand...
Click to collapse
Sounds like you need the 4 file repair firmware. At least this is where i would start. I'll try to find you the links and guide. Give me some time and I'll get back to you.
aaron74 said:
Sounds like you need the 4 file repair firmware. At least this is where i would start. I'll try to find you the links and guide. Give me some time and I'll get back to you.
Click to expand...
Click to collapse
I really appreciate it, take as much time as you need I'm just happy to have help from someone more experienced than me.
@The_Malhavoc
Ok, so this is what i would try first, since you said Odin gives Pit file error.
To start, uninstall all Samsung software (like kies) from your pc. Also uninstall Odin. I guess Odin don't install, but use the one in this post.
Download and install Samsung drivers from here to your pc.
Now download Odin 3.11.1 from here!
Unzip odin to your desktop.
Download the N910P repair firmware here! You'll need to unzip this. See below.
Ok now I provided all the files here. But now continue to this post and read carefully and follow directions!
https://forum.xda-developers.com/showpost.php?p=68854735&postcount=1
I hope this helps and all you have is a software issue!
---------- Post added at 08:35 PM ---------- Previous post was at 08:26 PM ----------
The_Malhavoc said:
I really appreciate it, take as much time as you need I'm just happy to have help from someone more experienced than me.
Click to expand...
Click to collapse
Fyi, i can't guarantee this will work. I personally have never needed to use it, or try it. But i know it has the pit file in this. So i figured it'd might help.
---------- Post added at 08:40 PM ---------- Previous post was at 08:35 PM ----------
@The_Malhavoc
Before you try this, respond back to me. So i know You didn't start yet. I'm trying to find you another solution.
aaron74 said:
@The_Malhavoc
Ok, so this is what i would try first, since you said Odin gives Pit file error.
To start, uninstall all Samsung software (like kies) from your pc. Also uninstall Odin. I guess Odin don't install, but use the one in this post.
Download and install Samsung drivers from here to your pc.
Now download Odin 3.11.1 from here!
Unzip odin to your desktop.
Download the N910P repair firmware here! You'll need to unzip this. See below.
Ok now I provided all the files here. But now continue to this post and read carefully and follow directions!
https://forum.xda-developers.com/showpost.php?p=68854735&postcount=1
I hope this helps and all you have is a software issue!
---------- Post added at 08:35 PM ---------- Previous post was at 08:26 PM ----------
Fyi, i can't guarantee this will work. I personally have never needed to use it, or try it. But i know it has the pit file in this. So i figured it'd might help.
Click to expand...
Click to collapse
I understand completely about no guarantee it'll work, but its more than I had so I'll give it a go. I wasn't expecting a reply so quickly and left my stuff at the office. Ill get it a shot tomorrow and report back, thank you so much for taking the time to help out a lost newbie have a great day!
The_Malhavoc said:
I understand completely about no guarantee it'll work, but its more than I had so I'll give it a go. I wasn't expecting a reply so quickly and left my stuff at the office. Ill get it a shot tomorrow and report back, thank you so much for taking the time to help out a lost newbie have a great day!
Click to expand...
Click to collapse
Ok great. Cause I'm trying to find you an easier firmware to try first. So don't try that just yet. I'll post back shortly.
Edit. What's your current firmware?
The_Malhavoc said:
I understand completely about no guarantee it'll work, but its more than I had so I'll give it a go. I wasn't expecting a reply so quickly and left my stuff at the office. Ill get it a shot tomorrow and report back, thank you so much for taking the time to help out a lost newbie have a great day!
Click to expand...
Click to collapse
Ok Im back. Before You do what I first told you. I want you to follow this guide. It will download you a firmware with a pit file. I actually have the file but it will take 8 hours for me to upload. so just do this.
First, All these links are from this post here. Its an old program "SamFirm" but it still works.
But Im providing shortcuts here for you. To simplify this process.
1. Download Samfirm0.3.6.zip Here!
2. It requires .NET Framework 3.5 (Microsoft Visual C++ 2008 Redistributable Package (x86) and Microsoft Visual C++ 2010 Redistributable Package (x86) installed)
3. So Download and Install above Links!
4. Unzip samfirm into its own directory.
5. Open it up and run as an Admin!
Now in Samfirm put in following info: (check pics)
Model== SM-N910P
Region== XAS (or if you want sprint default logo at boot then use SPR)
Check the box== Auto
and also box== Binary Nature
Then Click Check Update
It should show it found firmware SM-N910P/XAS/N910PVPS4DPK1/N910PSPT4DPK1/N910PVPS4DPK1/N910PVPS4DPK1
Make sure both boxes == Check CSC && Decrypt are both selected and Click Download!!!
IT'LL Download and Decrypt a special binary firmware, that will contain a PIT file. When you flash this file with Odin, It will completely wipe your device.
When its done just unzip the file. And then you will have a TAR.MD5 file to use with Odin!!
In Odin, Load this file to AP slot. Only select 'F.Reset Time' & 'AutoReboot' the first time, just like a normal flash.
Hope This Helps Ya!!! If This file doesnt solve your problem, you could try that other file from previous post, if you wish!
But just try this and let me know what happens!!
Good Luck!!
No luck,
I downloaded ALL_SPT_N910PVPS4DPK1_N910PSPT4DPK1_CL9120850_QB11420407_REV00_user_low_ship_MULTI_CERT.tar .md5 from Samfirm then extracted it.
Downloaded and installed odin 3.11.1 from the above link and ran as administrator.
Checked the AP box and linked it to the extraced md5 file, made sure autoreboot and f. reset time were the only things checked.
Started phone in download mode using vol down + home + power, then pressed up to enter download mode and plugged the usb into the computer.
Once Odin registered my phone with the "added" notification I clicked start.
Odin read:
<id:0/003> Odin engine v(ID:3.1101)...
<id:0/003> File analysis..
<id:0/003> SetupConnection..
<id:0/003> Initialization..
<id:0/003> Set PIT file..
<id:0/003> DO NOT TURN OFF TARGET!!
<id:0/003> FAIL!
<id:0/003>
<id:0/003> Re-Partition operation failed.
<OSM> ALl threads completed. (succed 0/ failed 1)
Meanwhile my Note read:
ddi: mmc_read failed
ODIN MODE (High Speed)
etc. etc.
Secure download: enable
UDC Start
ODIN: flash read failure
Error: There is no pit binary.
so barring any failure on my part (which I'll be the first to admit is very likely) I may have to try again using the first message you suggested. I'll hold off for now just to see if I did anything wrong, considering I've heard that if I manually try flashing a PIT I could hard brick my phone permanently and it should only be as a last resort.
In any case no matter how it works out, thanks again Aaron for taking the time to help me out. I just saw how to add thanks to the posts, so I'll be doing that now.
The_Malhavoc said:
No luck,
I downloaded .
Click to expand...
Click to collapse
Ok, well it definitely sounds like you got the emmc problem that i see floating around here.
I don't have any experience with it. But a couple more suggestions.
1. Try this file again. But in Odin select 'F.Reset' & 'Re- partition'. And don't select ' auto reboot '. Let it flash, and if successful, when done pull battery and reboot to recovery then wipe and reset.
2. If that is no go. Try the first solution i pointed you to.
If neither these work. Then its beyond me. Sorry.
Hope you get one of these to work for you. :fingers-crossed:
Edit. I should have mentioned, if your phone has twrp and you can boot to it. You should make a complete backup especially the efs. And copy and save it off phone.
Edit 2. You could try posting your question to that first thread i mentioned to you.
Why my SM-N910P the FRP couldn't activated.
I did a lot of factory resets but that FRP didn't activated at all.
I am on 6.0.1 PJ1 and bought it as a second hand device not new.
Why this happened... Could somebody explain this weird thing to me?