Related
Hi there,
I was trying to flash my Galaxy S i9000 with ROM-ODIN-2.3.6-Gingerbread Offical, but it did not work.
I tried several times but the operation failed .
There is a copy of the logs fromODIN3
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T959VUVKJ6-REV00-home-low-CL694130.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> Sbl.bin
<ID:0/016> NAND Write Start!!
<ID:0/016> cache.rfs
<ID:0/016> factoryfs.rfs
<ID:0/016> modem.bin
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After that my phone is not turning on and the only thing showed on screen is a exclamation mark between PC and Phone.
Please give me some advice on what should I do now!:crying:
Cheers,
Oscar_Barlop
First off, check that your ROM image is correct -- if you can get an md5sum for what it should be and use a tool like HashTab to check what you have. If that's not the problem...
I would suggest trying the "repartition" option in Odin. You'll need a .pit file to go with that though, so you'll have to try find one. I'm not sure where you got your ROM from, but I know you can get all of that from samfirmware . com (sorry, can't post links; too junior apparently)
davydm said:
First off, check that your ROM image is correct -- if you can get an md5sum for what it should be and use a tool like HashTab to check what you have. If that's not the problem...
I would suggest trying the "repartition" option in Odin. You'll need a .pit file to go with that though, so you'll have to try find one. I'm not sure where you got your ROM from, but I know you can get all of that from samfirmware . com (sorry, can't post links; too junior apparently)
Click to expand...
Click to collapse
Thank you for your reply,I resolved the issue downloading a previous ROM 2.3.3 which worked fine.
I will follow your advise and will verify in the future with hashtab the md5sum verification is correct before going ahead.
One more question, the .pit file is a generic one or it has variations from ROM to ROM?
Regards,
Oscar_barlop
oscar_barlop said:
Thank you for your reply,I resolved the issue downloading a previous ROM 2.3.3 which worked fine.
I will follow your advise and will verify in the future with hashtab the md5sum verification is correct before going ahead.
One more question, the .pit file is a generic one or it has variations from ROM to ROM?
Regards,
Oscar_barlop
Click to expand...
Click to collapse
AFAIK, each .pit file works for one or more ROMs. Again, I'm not 100% knowledgeable here, but it looks (to me) like the .pit file defines partitions for Odin to make on your device before flashing. I used to *always* make sure I had a .pit file to go with my ROM, then I found that I mostly didn't need one. If you're trying to resurrect your phone "from the dead", as it were, it's probably a good idea, but mostly, even though there are a couple of .pit files out there, there seems to be little variance between the ones I've come across. I would typically only use one if I can't seem to get a ROM on without out or if the package I got the ROM in recommended it.
As for your current ROM, I really recommend giving CyanogenMod another go -- it made a world of difference on my i9000 -- speed of device, battery, themes, usability. If you can get Clockwork Recovery on your phone, then it's easy to install. I also recommend checking out DarkyROM as they provide a really nice ROM for the S1 which installs Clockwork Recovery as part of its install process. Indeed, I would say that installing DarkyROM and then CM10 is the path of least resistance for getting CyanogenMod on an S1. Give it a go if you're up for it -- you won't regret it Just bear in mind that your very first boot (DarkyROM and CyanogenMod) may take a few minutes each -- try to be patient and just let the phone do its thing
davydm said:
AFAIK, each .pit file works for one or more ROMs. Again, I'm not 100% knowledgeable here, but it looks (to me) like the .pit file defines partitions for Odin to make on your device before flashing. I used to *always* make sure I had a .pit file to go with my ROM, then I found that I mostly didn't need one. If you're trying to resurrect your phone "from the dead", as it were, it's probably a good idea, but mostly, even though there are a couple of .pit files out there, there seems to be little variance between the ones I've come across. I would typically only use one if I can't seem to get a ROM on without out or if the package I got the ROM in recommended it.
As for your current ROM, I really recommend giving CyanogenMod another go -- it made a world of difference on my i9000 -- speed of device, battery, themes, usability. If you can get Clockwork Recovery on your phone, then it's easy to install. I also recommend checking out DarkyROM as they provide a really nice ROM for the S1 which installs Clockwork Recovery as part of its install process. Indeed, I would say that installing DarkyROM and then CM10 is the path of least resistance for getting CyanogenMod on an S1. Give it a go if you're up for it -- you won't regret it Just bear in mind that your very first boot (DarkyROM and CyanogenMod) may take a few minutes each -- try to be patient and just let the phone do its thing
Click to expand...
Click to collapse
I appreciate your reply and will give it a try next monday, I already have downloaded all the required files and I will let you know the outcome for sure.
Thank you again!!!
davydm said:
AFAIK, each .pit file works for one or more ROMs. Again, I'm not 100% knowledgeable here, but it looks (to me) like the .pit file defines partitions for Odin to make on your device before flashing. I used to *always* make sure I had a .pit file to go with my ROM, then I found that I mostly didn't need one. If you're trying to resurrect your phone "from the dead", as it were, it's probably a good idea, but mostly, even though there are a couple of .pit files out there, there seems to be little variance between the ones I've come across. I would typically only use one if I can't seem to get a ROM on without out or if the package I got the ROM in recommended it.
As for your current ROM, I really recommend giving CyanogenMod another go -- it made a world of difference on my i9000 -- speed of device, battery, themes, usability. If you can get Clockwork Recovery on your phone, then it's easy to install. I also recommend checking out DarkyROM as they provide a really nice ROM for the S1 which installs Clockwork Recovery as part of its install process. Indeed, I would say that installing DarkyROM and then CM10 is the path of least resistance for getting CyanogenMod on an S1. Give it a go if you're up for it -- you won't regret it Just bear in mind that your very first boot (DarkyROM and CyanogenMod) may take a few minutes each -- try to be patient and just let the phone do its thing
Click to expand...
Click to collapse
Hi Davidm,
I have follow your advise and I have installed DarkyRom but I went with CM9, it made a huge difference on my SGS, it is running very smooth and I have noticed as well that the size of the RAM increased as well from 329 to 389MB so there is no more lagging issues.
Thank you once again fro your advise.
Regards,
Oscar_barlop
I am really desperate here! I just spent $800 on the Note Edge Developer Edition (SM-N915V):
samsung dot com/us/mobile/cell-phones/SM-N915VMKEVZW
I am really hoping this isnt totally bricked because it was expensive and I only had it two days.
I tried to get root and found posts/pages on the net that said the Note 4 rom/tar file for odin could be used for all the "Note" linn devices. I turned on developer mode, booted into installation mode (home volume power) and followed these instructions
android dot gs/root-verizon-galaxy-note-4-developer-edition-using-odin-and-cf-auto-root/
Loading the tar file: CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5
Odin found the phone fine, then when I clicked start here is the log:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now when it boots up it just shows the error in the attached image "Software update failed". It still says odin in the tiny status text and odin "seems" to see it when I reconnect it, so I am hoping hoping it can be fixed with the right tar file.
Is there anyway to fix this???? I will do almost anything to get this working...
starfoxtj said:
I am really desperate here! I just spent $800 on the Note Edge Developer Edition (SM-N915V):
samsung dot com/us/mobile/cell-phones/SM-N915VMKEVZW
I am really hoping this isnt totally bricked because it was expensive and I only had it two days.
I tried to get root and found posts/pages on the net that said the Note 4 rom/tar file for odin could be used for all the "Note" linn devices. I turned on developer mode, booted into installation mode (home volume power) and followed these instructions
android dot gs/root-verizon-galaxy-note-4-developer-edition-using-odin-and-cf-auto-root/
Loading the tar file: CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5
Odin found the phone fine, then when I clicked start here is the log:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltevzw-trltevzw-smn910v.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now when it boots up it just shows the error in the attached image "Software update failed". It still says odin in the tiny status text and odin "seems" to see it when I reconnect it, so I am hoping hoping it can be fixed with the right tar file.
Is there anyway to fix this???? I will do almost anything to get this working...
Click to expand...
Click to collapse
Would suggest to flash STOCK 915V(edge)rom. Might fix problem.
Don't flash anything for other models unless you are 100% sure you can recover or it will work. It's a very expensive mistake to make...
I honestly thought it was a compatible rom. Do you have a link to the stock one I cant find anything? Its all for the SM-95F/G/etc and not the V. And will the stock rom blow away the developer/unlocked bootloader and revert it to retail?
And if it does work, is there anyway to get root on this one??
starfoxtj said:
I honestly thought it was a compatible rom. Do you have a link to the stock one I cant find anything? Its all for the SM-95F/G/etc and not the V. And will the stock rom blow away the developer/unlocked bootloader and revert it to retail?
And if it does work, is there anyway to get root on this one??
Click to expand...
Click to collapse
Your issue sounds exactly like what happened to sprint users when we first tried to root. The cf-auto-root root method for us failed every time giving that same message. See this thread: http://forum.xda-developers.com/note-edge/help/n915p-cf-auto-root-fails-t2944539
The issue with xposed will also apply to you (I'm 99.999999% sure of this), so read up on that if you're not already aware.
---------- Post added at 09:14 ---------- Previous post was at 09:12 ----------
Also, the ONLY Note 4 intended root-related tool I know of that's safe to run on the Edge is the Note 4 variant of TWRP. Set brightness all the way down and disable screen lock though. You'll see why if you run it.
use a 915G ROM and all will be well, i myself have went through this pen.
Ok hold on. What are we talking about here? The OP was all about CF auto root. Why are we all talking about flashing different roms now? The issue of CF auto root failing has been seen on both the Tmobile and Sprint variants, and both times it has been solved by flashing TWRP afterwards. I pasted a link to one of the (numerous) related threads above.
Thanks for the feedback.
jooniloh: There are a lot of various approaches that link off the link you provided, is the specific post below the one you were referring to? (Which is the first post in the thread)
http://forum.xda-developers.com/showpost.php?p=56834584&postcount=1
If so, step 6 says "UPDATE-SuperSU-v2.16.zip & External SD Card Fix". I have no clue how to do that...
I also dont even know what twp is, or ccd? (ccm?) I thought there was just one root mthod to use and now I dont know if I need to worry about twp and the other one or what.
starfoxtj said:
Thanks for the feedback.
jooniloh: There are a lot of various approaches that link off the link you provided, is the specific post below the one you were referring to? (Which is the first post in the thread)
http://forum.xda-developers.com/showpost.php?p=56834584&postcount=1
If so, step 6 says "UPDATE-SuperSU-v2.16.zip & External SD Card Fix". I have no clue how to do that...
I also dont even know what twp is, or ccd? (ccm?) I thought there was just one root mthod to use and now I dont know if I need to worry about twp and the other one or what.
Click to expand...
Click to collapse
If chain fire autoroot fails simply flash a compatible custom recovery for your device right after the failure. Twrp is an awesome custom recovery with a lot of great features built into it.
starfoxtj said:
Thanks for the feedback.
jooniloh: There are a lot of various approaches that link off the link you provided, is the specific post below the one you were referring to? (Which is the first post in the thread)
http://forum.xda-developers.com/showpost.php?p=56834584&postcount=1
If so, step 6 says "UPDATE-SuperSU-v2.16.zip & External SD Card Fix". I have no clue how to do that...
I also dont even know what twp is, or ccd? (ccm?) I thought there was just one root mthod to use and now I dont know if I need to worry about twp and the other one or what.
Click to expand...
Click to collapse
TWRP is a custom recovery that replaces the stock recovery. It lets to do MUCH more than the stock recovery, notably making Nandroid backups (full images of your system in its exact state that you can restore to if anything goes wrong). This is what you should do:
Download TWRP. The Note 4 variant is the only option here, but it works fine. Choose "twrp-2.8.6.0-trltevzw.img.tar" from here: http://dl.twrp.me/trltevzw/
You've already run CF auto root so just boot into download mode again, and connect the phone to your computer. Run odin and flash the file you just download in the PDA slot (for odin 3.07) or the AP slot (for odin 3.09).
once you've flashed that, see if you can reboot into recovery (Home, Power, vol UP). Once you're there, make sure you go into settings and turn the brightness all the way down and disable screen lock (the two white bars are because this was intended for the note 4 and will burn in your screen if you leave it on too long at full brightness. Unlocking the screen in TWRP also seems to be broken, but disabling screen lock works around that.).
Now you can reboot into the system, and from there you should be rooted. If SuperSU isn't already downloaded, just download it from the Play store.
If you're not rooted, try flashing CF auto root again, and then go through these steps again afterwards. Although next time, try this one: http://download.chainfire.eu/617/CF-Root/CF-Auto-Root/CF-Auto-Root-tbltespr-tbltespr-smn915p.zip It's for the sprint variant but should work.
jooniloh THAT WORKED!!! THANK YOU SO MUCH!!!!
I have SuperSU and titanium running perfectly!! I was sweating so bad at the thought of losing 1k....dude thank you so much I cannot tell you how happy I am!!!
I read about how I should backup the "aboot" partition incase it gets lost somehow. Do you recommend doing that and is this the guide to use?
http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
Or will a full backup in titanium backup include that as well? And is there anything else I should do before installing all my apps and loading my data?
Once I do a backup with titanium can I just do a normal factory reset to test that the restore works correctly? If so, how is that done on a rooted phone?
Reflash of the stock rom will 9 times out of ten fix any problem. I would suggest you find a stock rom so if anything does go wrong, you can restock.
Also, DON'T flash any other model; rom (no, a 915G rom is not the answer... you needs a 915V rom)... That will definitely cause bootloops or hanging at the Samsung logo...
starfoxtj said:
jooniloh THAT WORKED!!! THANK YOU SO MUCH!!!!
I have SuperSU and titanium running perfectly!! I was sweating so bad at the thought of losing 1k....dude thank you so much I cannot tell you how happy I am!!!
I read about how I should backup the "aboot" partition incase it gets lost somehow. Do you recommend doing that and is this the guide to use?
http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
Or will a full backup in titanium backup include that as well? And is there anything else I should do before installing all my apps and loading my data?
Once I do a backup with titanium can I just do a normal factory reset to test that the restore works correctly? If so, how is that done on a rooted phone?
Click to expand...
Click to collapse
What you want to do is make a Nandroid backup in TWRP. With a nandroid backup, if anything goes wrong with anything on your system, 99% of the time, you can restore the backup and your system will revert to EXACTLY how it was when you made the backup (root, apps, settings, EVERYTHING).
What I suggest you do is get a Micro SD card (you need one large enough. The Nandroid will be as large as however much is on your phone (NOT including your internal SD card). Ergo, if you have a 64GB phone filled to 50GB of application data, you'll need something with around 60GB (50GB + system, modem, efs, cache, boot, etc.) of space for the backup.), put the backup on that, and move them to a safe location (like your computer, or an external drive). To make a Nandroid, boot into recovery again, press "Backup", make sure all the partitions are selected, make sure storage is set to "Micro SDcard", then swipe.
Once the backup is done, turn off the phone, take out the SD card, and put it into your computer. Keep a safe copy of your backup (it'll be in TWRP/BACKUPS/<8-digit hex ID>/<your backup name>) somewhere and do this regularly. I suggest you also give your backups detailed names so you remember when you made each one, or what you did right after making that backup (like if you made a backup before flashing a certain file that you don't know if it'll work correctly). That way, if you need to go back to a backup, you can figure out which one to go back to easily.
Once they're on your computer, I wouldn't keep the backups on your Micro SD card because they're large and take a lot of space. IF you had the 128GB Micro SD, maybe keep the latest backup for convenience, but that's about it. Keep the rest on your computer. You can delete backups from your Micro SD by going to "Restore" in TWRP, selecting the backup, then pressing "Delete Backup".
An important thing to keep in mind is that Nandroids do not back up your data on the Internal or External SD cards. You can access both these locations through your computer though so make backups of them manually. Otherwise, you risk loosing downloaded files, photos, etc.
For less serious things, you can make a backup of apps and their corresponding data in Titanium Backup. This wont save you from corrupt systems files or other more serious issues, but if you switch to a new ROM and want to take your apps and data with you, Titanium is your friend. Titanium WON'T back up anything else besides apps and data. If you need a more comprehensive guide on Titanium, give a shout, and I'll see what I can do.
As for backing up aboot. Yes. Definitely do that. I'm reading through the guide posted there now. If you need any clarification or help with the steps, don't hesitate to ask. When in doubt, just ask. Some of the tools used could do some serious damage to your phone with even a slight error. Also, it's always a good idea to read all the instructions through once before doing anything so nothing surprises you as you're doing it.
The closest thing to a factory reset you can do quickly is the "Wipe" option in TWRP. Otherwise, to truly factory reset, you have to flash a stock rom. This will unroot AND remove TWRP.
ultramag69 said:
Reflash of the stock rom will 9 times out of ten fix any problem. I would suggest you find a stock rom so if anything does go wrong, you can restock.
Also, DON'T flash any other model; rom (no, a 915G rom is not the answer... you needs a 915V rom)... That will definitely cause bootloops or hanging at the Samsung logo...
Click to expand...
Click to collapse
Will the 915V ROM work for the dev edition? This was brought up before but never confirmed or denied as I remember.
The retail rom will not work on the dev edition. also for the dev edition you do not need cf autoroot. only flash twrp then use twrp to flash supersu update.zip reboot and done.
Also I have a full backup of full stock dev edition but when you flash it onbdefferent device it becomes super laggy. I'm currently trying to figure out how to make my backup into a flashable rom so that it goes through all the proper install steps instead of being a backup that can be restored on a different device at the cost of a $900 box of lag.
Sent from my SM-N915VMKE using XDA Free mobile app
NekoShinigami said:
The retail rom will not work on the dev edition. also for the dev edition you do not need cf autoroot. only flash twrp then use twrp to flash supersu update.zip reboot and done.
Also I have a full backup of full stock dev edition but when you flash it onbdefferent device it becomes super laggy. I'm currently trying to figure out how to make my backup into a flashable rom so that it goes through all the proper install steps instead of being a backup that can be restored on a different device at the cost of a $900 box of lag.
Sent from my SM-N915VMKE using XDA Free mobile app
Click to expand...
Click to collapse
Could you please post links to the proper tools for the Dev edition?
I don't know what version of Odin I would need, or where to find the proper twrp.zip.
Please help.
Again it's the Verizon Dev edition Note edge.
Thanks in advance.
Vorridor said:
Could you please post links to the proper tools for the Dev edition?
I don't know what version of Odin I would need, or where to find the proper twrp.zip.
Please help.
Again it's the Verizon Dev edition Note edge.
Thanks in advance.
Click to expand...
Click to collapse
I've already posted instructions for everything on the thread. Please read. Odin version doesn't matter; there's only two that are widely circulated anyways.
jooniloh said:
I've already posted instructions for everything on the thread. Please read. Odin version doesn't matter; there's only two that are widely circulated anyways.
Click to expand...
Click to collapse
Okay thank you. Will I need the extsdfix.zip? Also I have Odin 3.07 from working on my galaxy reverb will that work?
Vorridor said:
Okay thank you. Will I need the extsdfix.zip? Also I have Odin 3.07 from working on my galaxy reverb will that work?
Click to expand...
Click to collapse
The SD card fix is optional. Apply it if you want. Make sure you read the other posts before continuing. Use the latest version of TWRP for any Snapdragon Note 4 (TMO/ATT/VZW/SPR) downloaded from the TWRP site as the one in the T-Mobile Root thread is probably outdated. Use whatever version of Odin you already have.
jooniloh said:
The SD card fix is optional. Apply it if you want. Make sure you read the other posts before continuing. Use the latest version of TWRP for any Snapdragon Note 4 (TMO/ATT/VZW/SPR) downloaded from the TWRP site as the one in the T-Mobile Root thread is probably outdated. Use whatever version of Odin you already have.
Click to expand...
Click to collapse
Okay I downloaded the twrp mentioned in the posts on here, and got the Odin 3.09.
Now should I download the kies mini that's linked in the op?
I'm sorry for all the questions, I'm having trouble navigating the posts and links.
I do very much appreciate all your help and time! :good:
Also, can I flash the extsdfix.zip and SU update from twrp or do I need Odin for that also?
Vorridor said:
Okay I downloaded the twrp mentioned in the posts on here, and got the Odin 3.09.
Now should I download the kies mini that's linked in the op?
I'm sorry for all the questions, I'm having trouble navigating the posts and links.
I do very much appreciate all your help and time! :good:
Also, can I flash the extsdfix.zip and SU update from twrp or do I need Odin for that also?
Click to expand...
Click to collapse
Like I said, download the latest TWRP from its site. You don't need Kies unless you don't have Samsung device drivers on your computer. The SD card fix is flashed from TWRP. You don't need the SU update. As I said before, read the rest of my instructions on this thread first before continuing. All the steps after flashing CF-auto-root are listed here.
jooniloh said:
Like I said, download the latest TWRP from its site. You don't need Kies unless you don't have Samsung device drivers on your computer. The SD card fix is flashed from TWRP. You don't need the SU update. As I said before, read the rest of my instructions on this thread first before continuing. All the steps after flashing CF-auto-root are listed here.
Click to expand...
Click to collapse
Sorry again, I'm having trouble finding your post with instructions, so, if I have this right...
1st : open Odin, plug the phone in to pc, let Odin recognize the phone?
2nd : put the twrp in the ap slot then flash?
3rd : reboot phone in twrp, flash the extsdfix.zip?
And finally since it's dev edition, do I need to do the cf autoroot?
Ive got a sprint galaxy s5 that was running 5.0 fine. i tried installing a custom rom on it, as i've done before, and i'm stuck on the logo screen. i've read through a lot of stuff on here, and appreciate any feedback i can get. i've seen similar issues, but i was getting philz touch successfully loaded, but it wont boot past samsung logo after i've wiped everyting, in both standard recovery and on custom recovery.
i've now tried going to put a stock 5.0 rom back on in odin, and i'm failing odin. the only thing thats passed lately is putting on philz touch.
blazingoose503 said:
Ive got a sprint galaxy s5 that was running 5.0 fine. i tried installing a custom rom on it, as i've done before, and i'm stuck on the logo screen. i've read through a lot of stuff on here, and appreciate any feedback i can get. i've seen similar issues, but i was getting philz touch successfully loaded, but it wont boot past samsung logo after i've wiped everyting, in both standard recovery and on custom recovery.
i've now tried going to put a stock 5.0 rom back on in odin, and i'm failing odin. the only thing thats passed lately is putting on philz touch.
Click to expand...
Click to collapse
Which custom rom did you try installing? I'm sure you know, but Lollipop can be very temperamental the first time on a custom rom. Also, the first boot can take about 20 minutes the first time.
i was attempting to use MOAR v6.1 oa6
First, thanks for your reply.
so i had a rooted device with running moar initially. it was starting to get really laggy, so i decided to update it, flash this version. well i realized after that i wasn't on lollipop, got stuck in a bootloop then, and through this site, thankfully, was able to recover. then i did an OTA update to 5.0, so that was woriking fine, but now that ive been using my hotspot since i got this phone, im used to it and not having it blows!! so, after lollipop, (i backed up to kies 3 before attempting anything) i tried it again. philz worked fine, i put the super su in my phone's memory, and then went into super su to ignore knox or whatever, and it asked if i wanted to do it manually or normally. i think i did manual. but something didn't go right, i'm sure, and so now i don't even think i'm rooted, therefor need to go to stock, correct?
I'm new on here, well, posting, i use it a lot to figure **** out. like i mentioned earlier, the only thing that my phone will pass in odin is putting philz custom recovery on. it fails everything else, which all i've tried is to put stock 5.0 rom back on there. i will post my bootloader info as well as my odin script in hopes that someone will be able to help this dumbass(myself!) shouldnt have ****d with it after 5.0 was running fine, but it's like quitting a drug, once you root, i at least, don't wanna go back to stock.
i use my phone for work tho, so stock working is better than boot loop. any info/advice is greatly appreciated, i had to go buy a piece of **** prepaid phone just so i can work, and this thing is complete garbage!
my bootloader text
odin mode
product name: sm-g900p
current binary: custom
system status: custom
reactivation lock(kk): off
knox warranty void: 0x1 (2)
qualcomm secureboot: enable (csb)
rp swrev: s1, t2, r1, a2, p1
secure download: enable
udc start
kies was closed every time i've tried doing anyting in odin, fyi
my other question is can i use custom recovery to install a stock rom? prob dumb question, but like i said, i'm fairly new at this and anything helps. i just had no issues the first time i rooted, did a bunch of research, and clearly didn't do enough this time around to get it working properly.
blazingoose503 said:
my other question is can i use custom recovery to install a stock rom? prob dumb question, but like i said, i'm fairly new at this and anything helps. i just had no issues the first time i rooted, did a bunch of research, and clearly didn't do enough this time around to get it working properly.
Click to expand...
Click to collapse
Just so you know, if you quote the person, he'll get a flag. I didn't notice your post again until just now. IMO, your best bet is to follow the complete instructions from my post #2 It's important to follow it carefully, in your case, thread your phone like it was on Kitkat and don't take any corner. If you need help during that process, post in the Q&A that my link is in. To answer your question on this post, you can't use custom recovery for stock rom, you use Odin. All links to files needed are there too.
so im a little confused
Ramer said:
Just so you know, if you quote the person, he'll get a flag. I didn't notice your post again until just now. IMO, your best bet is to follow the complete instructions from my post #2 It's important to follow it carefully, in your case, thread your phone like it was on Kitkat and don't take any corner. If you need help during that process, post in the Q&A that my link is in. To answer your question on this post, you can't use custom recovery for stock rom, you use Odin. All links to files needed are there too.
Click to expand...
Click to collapse
are you telling me to put moar on, or flash a stock rom? and kitkat install should work even tho last time phone was working it was running 5.0?
im sorry im sure i sound retarded im just sort of at a loss, confused, and dont want to further damage my phone and make it unusable. so dont feel bad and you can explain to me as if i were a complete noob... i will donate for your help as well, id just really like to fix my phone. was gonna take it to a sprint store and have a tech look, but i know knox is tripped and theyll prob tell me to kick rocks
another thing
my phone wont get past samsung boot screen so i cant do anything on my phone itself, ive gotta do it all externally... im not worried about losing all data, i can get my stuff from other sources, so a fresh start isnt an issue for me
blazingoose503 said:
are you telling me to put moar on, or flash a stock rom? and kitkat install should work even tho last time phone was working it was running 5.0?
im sorry im sure i sound retarded im just sort of at a loss, confused, and dont want to further damage my phone and make it unusable. so dont feel bad and you can explain to me as if i were a complete noob... i will donate for your help as well, id just really like to fix my phone. was gonna take it to a sprint store and have a tech look, but i know knox is tripped and theyll prob tell me to kick rocks
Click to expand...
Click to collapse
The great thing about our phones is it's nearly impossible to truly brick it. As far as MOAR, of course I'm biased, but I'd highly recommend it. Because I can't really say for sure what state your phone is in. If you follow the instructions in the post I linked earlier, click on the "Click to Show Content" below the big red note and follow those instructions, I bet we can get you back on MOAR with Lollipop. Even though those instructions are written for someone who has never been on Lollipop they will still work, just takes longer to go through all the steps. Read it through a couple of times, download everything you'll need in advance and I bet you'll get up and running. If you run into any problem, PM me and I'll try to help.
really appreciate the help
Ramer said:
The great thing about our phones is it's nearly impossible to truly brick it. As far as MOAR, of course I'm biased, but I'd highly recommend it. Because I can't really say for sure what state your phone is in. If you follow the instructions in the post I linked earlier, click on the "Click to Show Content" below the big red note and follow those instructions, I bet we can get you back on MOAR with Lollipop. Even though those instructions are written for someone who has never been on Lollipop they will still work, just takes longer to go through all the steps. Read it through a couple of times, download everything you'll need in advance and I bet you'll get up and running. If you run into any problem, PM me and I'll try to help.
Click to expand...
Click to collapse
I'm getting all the files now, just deleted all i had got before and am starting with new downloads from #2, your instructions. do i have to do anything with super su and root before i can install MOAR? and there was no question of which rom to use, i just wasn't sure if your instructions for me were to get moar or stock, but i'm understanding now that i'm going to stock 5.0 then to moar, correct? does it matter which build of moar i use, i'm getting 6.2 as i figured the newer the better. if not let me know. i put money in my account so i can truly appreciate you help and i obviously cant do the steps where i back anything up in my phone, since it wont turn all the way on, so i'm hoping all of this will work without those steps as well. Like i wont be able to go and delete the android file. i hope that's not a deal breaker... i could just pull my sd card, or is that a bad idea? these are the things i'm worried about, but i guess i will learn one way or another!!
gonna throw another 10 your way
just really wanna figure this out, and i cant stress enough how thankful i am. if i had more money i'd be giving it to you, thanks dude!!
blazingoose503 said:
I'm getting all the files now, just deleted all i had got before and am starting with new downloads from #2, your instructions. do i have to do anything with super su and root before i can install MOAR? and there was no question of which rom to use, i just wasn't sure if your instructions for me were to get moar or stock, but i'm understanding now that i'm going to stock 5.0 then to moar, correct? does it matter which build of moar i use, i'm getting 6.2 as i figured the newer the better. if not let me know. i put money in my account so i can truly appreciate you help and i obviously cant do the steps where i back anything up in my phone, since it wont turn all the way on, so i'm hoping all of this will work without those steps as well. Like i wont be able to go and delete the android file. i hope that's not a deal breaker... i could just pull my sd card, or is that a bad idea? these are the things i'm worried about, but i guess i will learn one way or another!!
Click to expand...
Click to collapse
1. Don't need to do anything with SuperSu or root. MOAR is pre-rooted.
2. Yes, go to stock then MOAR. Make sure to set up your google and samsung accounts in stock rom per instructions.
3. You are correct, install the latest which is MOAR 6.2. Don't worry about it now, but once you're up and running, read through the FAQ. There's another update which is called New Stuff mods. Also, down the road you'll enjoy a theme for MOAR.
4. Correct, you can't backup your phone since you're in a bootloop now, so skip.
5. Do you have a card reader on your PC? If so, pull your SD card out now, delete the android folder and you'll need to copy the MOAR rom to your card to flash when you reach that step. If that's not possible you'll have to go through a more difficult route of copying the MOAR rom from your PC to your internal SD while you're in the stock rom. Keep in mind, while your in stock rom, you're not rooted, which is why you just want to get the initial sign-in done before doing a battery pull.
6. The android file on your SD may not be important anyway, since I believe you were on Lollipop at some point. It was just an issue for people going from Kitkat to Lollipop for the first time.
Good luck, I'll be around for the next two hours if you need more help, but if you're getting started now, you should be up and running in less than two hours. Just remember, the first boot in stock and in MOAR can take about 20 minutes, so be a bit patient.
---------- Post added at 07:19 PM ---------- Previous post was at 07:06 PM ----------
blazingoose503 said:
just really wanna figure this out, and i cant stress enough how thankful i am. if i had more money i'd be giving it to you, thanks dude!!
Click to expand...
Click to collapse
I'm always happy to help (well, almost always). I saw your edit, you don't have to un-check auto-reboot after odin'ing stock. Just where it's mentioned.
after putting moar zip on my sd, via computer...
Ramer said:
1. Don't need to do anything with SuperSu or root. MOAR is pre-rooted.
2. Yes, go to stock then MOAR. Make sure to set up your google and samsung accounts in stock rom per instructions.
3. You are correct, install the latest which is MOAR 6.2. Don't worry about it now, but once you're up and running, read through the FAQ. There's another update which is called New Stuff mods. Also, down the road you'll enjoy a theme for MOAR.
4. Correct, you can't backup your phone since you're in a bootloop now, so skip.
5. Do you have a card reader on your PC? If so, pull your SD card out now, delete the android folder and you'll need to copy the MOAR rom to your card to flash when you reach that step. If that's not possible you'll have to go through a more difficult route of copying the MOAR rom from your PC to your internal SD while you're in the stock rom. Keep in mind, while your in stock rom, you're not rooted, which is why you just want to get the initial sign-in done before doing a battery pull.
6. The android file on your SD may not be important anyway, since I believe you were on Lollipop at some point. It was just an issue for people going from Kitkat to Lollipop for the first time.
Good luck, I'll be around for the next two hours if you need more help, but if you're getting started now, you should be up and running in less than two hours. Just remember, the first boot in stock and in MOAR can take about 20 minutes, so be a bit patient.
---------- Post added at 07:19 PM ---------- Previous post was at 07:06 PM ----------
I'm always happy to help (well, almost always). I saw your edit, you don't have to un-check auto-reboot after odin'ing stock. Just where it's mentioned.
Click to expand...
Click to collapse
it said that i needed to insert the last disk of the multi-volume set and click ok to continue? i put the unzipped folder onto my sd card, that's how i'm supposed to do it right? i'm gonna try, hoping that message doesn't mean anything. and sorry to blow you up bro, i'm just stoked on getting my phone back, running MOAR, baby:silly:
lastly...
blazingoose503 said:
it said that i needed to insert the last disk of the multi-volume set and click ok to continue? i put the unzipped folder onto my sd card, that's how i'm supposed to do it right? i'm gonna try, hoping that message doesn't mean anything. and sorry to blow you up bro, i'm just stoked on getting my phone back, running MOAR, baby:silly:
Click to expand...
Click to collapse
do i put philz on before i odin to stock, i think step 3 is to wipe everything, and im on stock recovery, so do i odin philz, then wipe, then stock, then install moar from my sd card once i'm ready for that step? sorry again dude. i know you're trying your best, and unfortunately, so am i!! told you i'm (as you guys kindly refer to us as) a new user
blazingoose503 said:
do i put philz on before i odin to stock, i think step 3 is to wipe everything, and im on stock recovery, so do i odin philz, then wipe, then stock, then install moar from my sd card once i'm ready for that step? sorry again dude. i know you're trying your best, and unfortunately, so am i!! told you i'm (as you guys kindly refer to us as) a new user
Click to expand...
Click to collapse
You can odin Philz after you set up the stock rom. It sounds like your very familiar with Philz, I haven't used that for a long time. I think I read somewhere that he was retiring, so I've stayed with TWRP. But for now, use what you're comfortable with.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
blazingoose503 said:
it said that i needed to insert the last disk of the multi-volume set and click ok to continue? i put the unzipped folder onto my sd card, that's how i'm supposed to do it right? i'm gonna try, hoping that message doesn't mean anything. and sorry to blow you up bro, i'm just stoked on getting my phone back, running MOAR, baby:silly:
Click to expand...
Click to collapse
Whoa, stop there. Don't unzip MOAR, just copy it to your phone. Philz or TWRP, when you install a rom takes care of that.
this is what odin says when i try to go stock
using the dl from your tutorial
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
using odin 3.07
cuz that's what it said it was tested on somewhere in my reading. so i got that one, put the file in the pda box in odin, and it won't pass, just like my initial post!!
my bad, i didn't unzip
Ramer said:
You can odin Philz after you set up the stock rom. It sounds like your very familiar with Philz, I haven't used that for a long time. I think I read somewhere that he was retiring, so I've stayed with TWRP. But for now, use what you're comfortable with.
---------- Post added at 07:42 PM ---------- Previous post was at 07:40 PM ----------
Whoa, stop there. Don't unzip MOAR, just copy it to your phone. Philz or TWRP, when you install a rom takes care of that.
Click to expand...
Click to collapse
i put the zipped file onto sd card, dunno why i put that. i left it in zip format. my apologies. still can't odin stock rom tho...
blazingoose503 said:
using the dl from your tutorial
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You didn't download the stock that I linked to. Hold on a few minutes and let me find it...
i got it from the install instructions page
Ramer said:
You didn't download the stock that I linked to. Hold on a few minutes and let me find it...
Click to expand...
Click to collapse
but thank you, ill re dl from you. thanks again
Hi everyone,
Firstly, I'm sorry if this is posted in the wrong area but I'm in a state of despair at the moment!
Basically, I was manually backing up my girlfriend's phone to my PC (backing up pictures) - naturally clicking the folders to backup, ctrl+c and then ctrl+v in the relevant folder on my PC and voila. Backup done. Except, it didnt copy all of the files and now my girlfriend has deleted in excess of 400 pictures, most of which of our 6 month old baby that we desperately want back.
I have seen many ways to do this but all seem to need root access - I have tried rooting using many different unikernels (excuse my ignorance, this is the first time I've tried rooting a device!) but none seem to work...
Useful info: Android version: 5.1.1 (out of the box), model number: SM-G920F, Build number: LMY47X.G920FXXU3QOKN.
Any help or advice at all is greatly appreciated and I will forever be in your debt if you can successfully help get my files back. And I'm willing to purchase any payware needed!
EDIT: I have tried: Kingo Root, iRoot, One-click-root, Root Genius, Coolmusters recovery tool, wondershare's recovery tool... essentially all of the first 2 or 3 pages of any Google search remotely related to this.
Download odin 3.7 for windows. And google CF auto root instructions for your device and firmware.
So the links ensure you use the right CF auto root
That should work.
You shouldn't be finding it hard to root whilst on
Lollipop! !
kush2.0 said:
Download odin 3.7 for windows. And google CF auto root instructions for your device and firmware.
So the links ensure you use the right CF auto root
That should work.
You shouldn't be finding it hard to root whilst on
Lollipop! !
Click to expand...
Click to collapse
Thanks! Looks like DiskDigger (Free app on Play store) has recovered all my files and then some... Currently verifying this...
EDIT: DiskDigger recovered files but without being rooted, it only recovered low-res images. I'm still trying to figure out how to root this thing! Why so hard?!
So I've been following this, and all other tuts that I can find, www [dot] ndroidrootz [dot] com/2015/05/how-to-unroot-galaxy-s6-and-s6-edge.html
The phone is bricked and will only go between 2 screens. Download Mode and a screen that shows "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" - but this fails too!
Any way of fixing my girlfriends S6? I just keep getting FAIL in ODIN!
lemons55 said:
So I've been following this, and all other tuts that I can find, www [dot] ndroidrootz [dot] com/2015/05/how-to-unroot-galaxy-s6-and-s6-edge.html
The phone is bricked and will only go between 2 screens. Download Mode and a screen that shows "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" - but this fails too!
Any way of fixing my girlfriends S6? I just keep getting FAIL in ODIN!
Click to expand...
Click to collapse
the smart switch option is a nice way to clean up everything and try again, i know that sounds strange but even the usb cable can make the difference (hope u r using the original one) and odin 3.10 i think should help a bit with all these fail attempt..
in case via smart switch reinstall the drivers and.. let me know if it helped somehow
ps: sorry for bad english
lemons55 said:
So I've been following this, and all other tuts that I can find, www [dot] ndroidrootz [dot] com/2015/05/how-to-unroot-galaxy-s6-and-s6-edge.html
The phone is bricked and will only go between 2 screens. Download Mode and a screen that shows "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" - but this fails too!
Any way of fixing my girlfriends S6? I just keep getting FAIL in ODIN!
Click to expand...
Click to collapse
Jesus christ, what an old guide, no wonder you've ruined it in your desperation.
First, You need a newer version of Odin. (3.10.7)
http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361
Then your best bet is to find the exact firmware you were on prior to this mess to have the best chance of keeping your original files in tact if you haven't completely trashed them by now.
Not sure what region / provider your phone is from. Does this look correct?
The link you gave was linking to older versions of android then what you were on to start with.
http://samsung-updates.com/details/58161/Galaxy_S6/SM-G920F/VDI/G920FXXU3QOKN.html
If so download it and flash via odin making sure "nand erase" or "repartition" is not selected!
Hopefully that will get the phone running again.
Then Flash TWRP recovery via odin
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/arter97-recovery-g920fi-13.0-twrp_3.0.0-0.tar.md5
Finally, reboot into recovery and install supersu to get root.
http://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
self_slaughter said:
Jesus christ, what an old guide, no wonder you've ruined it in your desperation.
First, You need a newer version of Odin. (3.10.7)
http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361
Then your best bet is to find the exact firmware you were on prior to this mess to have the best chance of keeping your original files in tact if you haven't completely trashed them by now.
Not sure what region / provider your phone is from. Does this look correct?
The link you gave was linking to older versions of android then what you were on to start with.
http://samsung-updates.com/details/58161/Galaxy_S6/SM-G920F/VDI/G920FXXU3QOKN.html
If so download it and flash via odin making sure "nand erase" or "repartition" is not selected!
Hopefully that will get the phone running again.
Then Flash TWRP recovery via odin
http://arter97.com/browse/exynos7420/recovery/twrp/g920fi/arter97-recovery-g920fi-13.0-twrp_3.0.0-0.tar.md5
Finally, reboot into recovery and install supersu to get root.
http://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
Click to expand...
Click to collapse
Thanks man! Unfortunately, flashing the stock firmware using the link you provided above (I even paid for a faster download!) didn't work, got about 30% through then failed. I've PM'd you with the log but anyone else who can help, see it here below:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Odin 3.10.6 seems to work when others fail try that one bud.
Jimmy1life said:
Odin 3.10.6 seems to work when others fail try that one bud.
Click to expand...
Click to collapse
Thanks mate, tried that and it just fails as with all other attempts. Went a bought a new S6 (£400 later!) and that seems to be the end of it :/ Thanks to all for your advice though! I'll keep trying with the bricked S6!
Hey guys, I have a major problem on my Samsung Galaxy Note II (N7100), that is it slowly corrupts my applications, whether I install them or the system apps that are already installed. Now I used the word "corruption" because that's how I can compare it to a computer and corrupted hard drives, files go missing, or become unreadable. I also experience a lot of random reboots, I assume because the corruption messes with system files and it reboots to reset said files. After each reboot I have most likely something lost, whether it is just settings (notifications reset to default sound), or whole applications vanish from the apps tab but show in the app manager as the android symbol and can't be opened or uninstalled/reinstalled.
The device wears its original Kitkat, updated from ICS, the one and only major update this phone had, and is rooted with kingo one click root.
I already tried a reset to factory, worked fine for a few hours, then started presenting the same behavior again.
This is a screen cap (it won't let me post the link, so I removed three dots and replaced them with # - i1383#photobucket#com/albums/ah298/Jo_The_Veteran/Screenshot_2016-12-02-21-48-55_zpss697tn89#png -) before the factory reset that show what I'm experiencing, applications are there, but can't be accessed or deleted or anything and sometimes even looking at this view causes a reboot. At this moment I have 1 or 2 apps that present that behavior.
So I was thinking to reinstall the firmware, maybe the same again, or some other ROM if it's better. The thing is, I don't think that will fix the problem either. If it's flash corruption then this will happen again. So maybe there's a tool that can isolate those damaged sectors of the flash memory? Is there a tool that can search for damaged sectors for that matter? Let me make something clear, this isn't the extSDcard causing this, the extSD is a brand new card and I can have it removed at any time and the problems remain. The problem lies with the onboard 16GB flash.
So I provided all the info I could think, but if you have any questions feel free to ask.
So any ideas on what's going on?
Excellent replies!
Well today my phone crash and burned. I booted into recover and get messages all over the board, E:Can't mount/cache/recovery/last_log, E:failed to mount /cache (Block device required).... a bunch of others as well.
Tried a data reset and another batch of errors followed.
Is the phone memory dead? Can I do something? Anybody?
Jo The Veteran said:
Excellent replies! [emoji14]
Well today my phone crash and burned. I booted into recover and get messages all over the board, E:Can't mount/cache/recovery/last_log, E:failed to mount /cache (Block device required).... a bunch of others as well.
Tried a data reset and another batch of errors followed.
Is the phone memory dead? Can I do something? Anybody?
Click to expand...
Click to collapse
You can flash the stock firmware via Odin, then see if the problems remain.
Did you recently update the stock firmware? Such as with an OTA update?
Sent from my SCH-I535 using Tapatalk
Droidriven said:
You can flash the stock firmware via Odin, then see if the problems remain.
Did you recently update the stock firmware? Such as with an OTA update?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I had some OTA updates arrive almost immediately since I tried a factory reset, some Samsung security updates I believe.
I tried flashing with ODIN, I used Odin3-v3.07 because it has worked for this phone before.
So I went through this whole process : Volume Down + HOME + POWER, enter the custom OS programming menu, hit volume up, it is at the screen "downloading, don't turn off". Connect USB via ODIN, it shows <ID:0/006> Added!!, hit PDA button, load N7100XXUFND3_N7100OXAFND3_N7100XXUFND3_HOME.tar (I'm downloading another firmware as I write this, just to cross reference). Anyway it says :
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
then after a while
<OSM> N7100XXUFND3_N7100OXAFND3_N7100XXUFND3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
I hit start, it did some actions but then said fail almost immediately.
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Then I saw this post
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
but haven't tried it yet. I wanna try the other firmware first.
That's another subject altogether? Where can I find the official Samsung firmware? Currently I'm downloading from http://www.sammobile.com/ and the other one I tried that failed I downloaded from this post http://forum.xda-developers.com/showthread.php?t=2740496 (the first one).
Jo The Veteran said:
I had some OTA updates arrive almost immediately since I tried a factory reset, some Samsung security updates I believe.
Unfortunately I tried flashing with ODIN, went through this whole process : Volume UP + HOME + POWER, enter the programming menu, hit volume up again, it is at the screen "downloading, don't turn off". Connect USB via ODIN, it shows detected, hit PDA button, load N7100XXUFND3_N7100OXAFND3_N7100XXUFND3_HOME.tar (I'm downloading another firmware as I write this, just to cross reference). Anyway it said success (loading image), I hit start, it did some actions but then said fail almost immediately. I think it wrote "Nand Write Fail" something like that. Then I saw this post
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
but haven't tried it yet. I wanna try the other firmware first.
That's another subject altogether? Where can I find the official Samsung firmware? Currently I'm downloading from http://www.sammobile.com/ and the other one I tried that failed I downloaded from this post http://forum.xda-developers.com/showthread.php?t=2740496 (the first one).
Click to expand...
Click to collapse
Sammobile .com or samsung-updates .com are where you can get the official firmware, you just have to make sure its the most up to date version for your model number and that it is the correct firmware for your model number and carrier/region/country.
For troubleshooting why you got a failed Odin flash, you can try reading this thread also. The thread is from the S2 forum but the process is the same.
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Sammobile .com or samsung-updates .com are where you can get the official firmware, you just have to make sure its the most up to date version for your model number and that it is the correct firmware for your model number and carrier/region/country.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ok found it but I'm still downloading it (another 27 minutes or so left).
Did some edits in the second post, added more details. Please take a look if you will.
Droidriven said:
Sammobile .com or samsung-updates .com are where you can get the official firmware, you just have to make sure its the most up to date version for your model number and that it is the correct firmware for your model number and carrier/region/country.
For troubleshooting why you got a failed Odin flash, you can try reading this thread also. The thread is from the S2 forum but the process is the same.
forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Unfortunately the sammobile N7100XXUFNL1_N7100EURFNL1_EUR firmware didn't work either. Same errors. I'm downloading specifically the Italian firmware, since this is the country where I got this phone from, but I have little hope it will work. In my mind this problem sounds like a hardware fault, NAND Write Start!!<ID:0/006> FAIL. I do hope I'm wrong though. Replacing an eMMC looks like a serious pain in the ass. And although I own most of the tools for that job, I do want to avoid it and only try it as a last, last resort.
Tried a bunch of odins 3.07,09,10.6,11.1,12.3. None worked, same error.
Jo The Veteran said:
Unfortunately the sammobile N7100XXUFNL1_N7100EURFNL1_EUR firmware didn't work either. Same errors. I'm downloading specifically the Italian firmware, since this is the country where I got this phone from, but I have little hope it will work. In my mind this problem sounds like a hardware fault, NAND Write Start!!<ID:0/006> FAIL. I do hope I'm wrong though. Replacing an eMMC looks like a serious pain in the ass. And although I own most of the tools for that job, I do want to avoid it and only try it as a last, last resort.
Click to expand...
Click to collapse
I doubt it is the eMMC and I don't think it has anything to do with which version of Odin you are using. Have you read the thread for troubleshooting a failed Odin flash? There are options in Odin that do different things. Just don't use the NAND erase all option, that won't go very well for you, you nay can try finding the PIT file for your model number and try flashing the PIT along with the firmware but that should be a last ditch effort if nothing else works, that can go bad sometimes also. They can be finicky sometimes even when flashing the absolute correct files, sometimes it takes 3 or more flashes before it works.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
I doubt it is the eMMC and I don't think it has anything to do with which version of Odin you are using. Have you read the thread for troubleshooting a failed Odin flash? There are options in Odin that do different things. Just don't use the NAND erase all option, that won't go very well for you, you nay can try finding the PIT file for your model number and try flashing the PIT along with the firmware but that should be a last ditch effort if nothing else works, that can go bad sometimes also. They can be finicky sometimes even when flashing the absolute correct files, sometimes it takes 3 or more flashes before it works.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I didn't want to explore the PIT option, everyone says it's a bad idea. Btw I have tried EVERYTHING in the odin section troubleshooting. I'm even trying in another PC today with other USB 2/3 ports.
I also kinda cross referenced the eMMC must be ok since I see the product number in recovery, if I can it means it's fine (or so I read), so that's a definite relief.
What does PIT does anyway? Is it possible I loose even the firmware install option? Or is that hard coded into the device? I'm asking cause I managed once to enter recovery, I had a bunch of error messages in red "E:cannot mount... log file" stuff, I don't remember. A LOT of them. Would a new PIT fix that?
I tried to flash CF-Auto-Root-t03g-t03gxx-gtn7100.tar with odin as well. Same error. Nothing works. At this point I'm just trying out pretty much anything really.
I've tried this because I'm thinking how computers act in situations like that again. If the computer is stuck at boot, it's probably the bootloader and boot section at fault (if the disk is ok). So how can I go and fix that? How can I reinstall the stock bootloader? Does flashing a firmware do that as well? Or do I need that PIT thing? Or something else?
for sure your emmc is starting to get hardware failure, a reflow could fix temporary this issue
Jo The Veteran said:
I tried to flash CF-Auto-Root-t03g-t03gxx-gtn7100.tar with odin as well. Same error. Nothing works. At this point I'm just trying out pretty much anything really.
I've tried this because I'm thinking how computers act in situations like that again. If the computer is stuck at boot, it's probably the bootloader and boot section at fault (if the disk is ok). So how can I go and fix that? How can I reinstall the stock bootloader? Does flashing a firmware do that as well? Or do I need that PIT thing? Or something else?
Click to expand...
Click to collapse
Yes, the bootloader is included in the firmware. I get the feeling that your bootloader is corrupted also instead of it being an eMMC issue because you are getting the failure error when it tries to flash your boot.img.
Have you tried finding your firmware in a 4 part file? If you can find one, it is flashed by placing each part in its own slot in Odin instead of in the PDA/AP slot like you would with an all in one firmware file. You can try flashing just the bootloader by itself and then see if it boots or flash each other part individually, you can extract the boot.img from the firmware if needed by using Cygwin or a VM running a Linux distro if you have a Windows machine, or a Linux machine if you have one. I can get you a thread with instructions for extracting the firmware and making your own Odin flashable .tar if you need it. The bootloader and the kernel are both in the boot.img contained in your firmware. They both effect whether the device boots as it should.
In my time here I've rarely ever seen a device with eMMC issues out of the hundreds of different models of devices I've encountered so don't give up yet. Its possible that you are having memory failure but in my opinion it isn't likely, I could be wrong though.
To answer your earlier question about the PIT, it is basically your partitioning table.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Yes, the bootloader is included in the firmware. I get the feeling that your bootloader is corrupted also instead of it being an eMMC issue because you are getting the failure error when it tries to flash your boot.img.
Have you tried finding your firmware in a 4 part file? If you can find one, it is flashed by placing each part in its own slot in Odin instead of in the PDA/AP slot like you would with an all in one firmware file. You can try flashing just the bootloader by itself and then see if it boots or flash each other part individually, you can extract the boot.img from the firmware if needed by using Cygwin or a VM running a Linux distro if you have a Windows machine, or a Linux machine if you have one. I can get you a thread with instructions for extracting the firmware and making your own Odin flashable .tar if you need it. The bootloader and the kernel are both in the boot.img contained in your firmware. They both effect whether the device boots as it should.
In my time here I've rarely ever seen a device with eMMC issues out of the hundreds of different models of devices I've encountered so don't give up yet. Its possible that you are having memory failure but in my opinion it isn't likely, I could be wrong though.
To answer your earlier question about the PIT, it is basically your partitioning table.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
What had me going thus far was this post here
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
but this must be one of the most incomprehensible guide I've even seen online. The writer is definitely not versed in the English language. Still the whole concept got me going, I experience the same errors he describes, and he says there's a solution. Alas, I can't make heads or tails of his explanation though.
Still now you as well give me great hope, I've almost given up on it and was looking for replacement eMMC chips and soldering methods.
Please provide the links and I'll try that as well.
Also, is there a way to absolutely know if the eMMC is not busted? All I found was a mention that the device name must appear in recovery, and mine does, so that's definite? Are there any other tests? (other than failing every flash attempt and having a corrupted bootloader, which is kinda obvious)
Yeah I have no Linux vm, will parted magic work? I have a flash drive with a small linux environment, but I know next to nothing about linux, would be better if I could find the boot file directly.
Still I don't think that'll work either because, well wouldn't the boot file be the first that the firmware try to install? So maybe I need to remake the PIT, see if that helps. The things is, other than in a PC, I don't know how that works in android. There's a bunch of programs made for partition recovery or reconstruction, is there one for android?
And If I do try that and it ****s up, do I loose recovery as well? Or is that hard coded to an EPROM BIOS or somewhere?
Jo The Veteran said:
Yeah I have no Linux vm, will parted magic work? I have a flash drive with a small linux environment, but I know next to nothing about linux, would be better if I could find the boot file directly.
Still I don't think that'll work either because, well wouldn't the boot file be the first that the firmware try to install? So maybe I need to remake the PIT, see if that helps. The things is, other than in a PC, I don't know how that works in android. There's a bunch of programs made for partition recovery or reconstruction, is there one for android?
And If I do try that and it ****s up, do I loose recovery as well? Or is that hard coded to an EPROM BIOS or somewhere?
Click to expand...
Click to collapse
I'm not sure if a Linux USB or CD would work but you can try it.
I'll link you some threads to help explain what you're asking.
For extracting the boot.img, look here
forum.xda-developers.com/showthread.php?t=2138885
For how to create a Odin flashable .tar with what you extract, look here
forum.xda-developers.com/showthread.php?t=2154762
The PIT file for your model number might be available for download somewhere, just do a Google search for
"PIT for (your model number)"
I'm not sure about partition recovery programs for android, I'm not sure that's possible, I've never had to try it.
To explain the ins and outs of android firmware, look here
www.addictivetips.com/mobile/android-partitions-explained-boot-system-recovery-data-cache-misc
Recovery partition is not like PC, no EPROM or BIOS, android recovery is flashed on the eMMC either in its own partition on some devices, or in data partition on some, or its packaged along with your kernel(ZIMAGE) on some. Intel based android tablets have an actual BIOS but they also use a separate bootloader, android is a fickle thing and varies in structure from brand to brand or device to device, they're all different.
I'm trying to help you but I'm not making sense of what you have going even though I'm pretty experienced with Samsung. I'll keep trying to wrap my head around it, you have a software issue I'm pretty sure so there should be a solution SOMEWHERE.
Try reading through Q&A forums for the various Samsung devices here at XDA, there are many of them.
Here's a link to a list of all devices supported at XDA, read through some of the Samsung forums, you might find answers or solutions in their Q&A subforums.
forum.xda-developers.com/?nocache=1&z=8504840892273933
If the link isn't showing the supported list correctly, view the forum in a browser and look at the bottom of the page and you'll see a box to choose the XDA theme are viewing in, select that and change the theme to the 2013 theme, then at the top of the page you'll see a tab that says "COMPACT", select that and you'll see the list, find the list of Samsung devices and start looking through the forums for those, find the Q&A subforum in each of them and see if there are any threads that help you find answers solutions.
I'll let you know if I think of or find anything that might help. If you have more questions, feel free to ask and I'll see if I can answer them.
Sent from my SCH-I535 using Tapatalk
Thanks!
Droidriven said:
I'm not sure if a Linux USB or CD would work but you can try it.
I'll link you some threads to help explain what you're asking.
For extracting the boot.img, look here
forum.xda-developers.com/showthread.php?t=2138885
For how to create a Odin flashable .tar with what you extract, look here
forum.xda-developers.com/showthread.php?t=2154762
The PIT file for your model number might be available for download somewhere, just do a Google search for
"PIT for (your model number)"
I'm not sure about partition recovery programs for android, I'm not sure that's possible, I've never had to try it.
To explain the ins and outs of android firmware, look here
www.addictivetips.com/mobile/android-partitions-explained-boot-system-recovery-data-cache-misc
Recovery partition is not like PC, no EPROM or BIOS, android recovery is flashed on the eMMC either in its own partition on some devices, or in data partition on some, or its packaged along with your kernel(ZIMAGE) on some. Intel based android tablets have an actual BIOS but they also use a separate bootloader, android is a fickle thing and varies in structure from brand to brand or device to device, they're all different.
I'm trying to help you but I'm not making sense of what you have going even though I'm pretty experienced with Samsung. I'll keep trying to wrap my head around it, you have a software issue I'm pretty sure so there should be a solution SOMEWHERE.
Try reading through Q&A forums for the various Samsung devices here at XDA, there are many of them.
Here's a link to a list of all devices supported at XDA, read through some of the Samsung forums, you might find answers or solutions in their Q&A subforums.
forum.xda-developers.com/?nocache=1&z=8504840892273933
If the link isn't showing the supported list correctly, view the forum in a browser and look at the bottom of the page and you'll see a box to choose the XDA theme are viewing in, select that and change the theme to the 2013 theme, then at the top of the page you'll see a tab that says "COMPACT", select that and you'll see the list, find the list of Samsung devices and start looking through the forums for those, find the Q&A subforum in each of them and see if there are any threads that help you find answers solutions.
I'll let you know if I think of or find anything that might help. If you have more questions, feel free to ask and I'll see if I can answer them.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ok, I'll start digging around, see what I can find.
Thank you very much for all that info. I'll make sure to update this post if I accomplish anything, good or bad.
So I've followed this post. The writer seemed to know his stuff, so I've tried everything he told. Nothing worked.
I've even tried flashing the bootloader alone as a last resort like the guide creator stated, nothing.
This is what odin presents to me trying to do exactly that.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I also got a line of red letters in download mode reading SW REV. Invalid Magic String. exactly the moment I hit start when tried to flash the bootloader. Whatever that would mean?
Of course I also tried to recreate the PIT, which got stuck at
get pit for mapping
Click to expand...
Click to collapse
Which from what I can say is another classic error everyone gets.
Umm.. I don't know. There are like, millions of opinions out there, but no one who really know his stuff. I mean I read guides on "do this" and "that" but I don't read why should I. I mean, I think those people got there by experimentation, like "try this button, meh doesn't work, oooh try this now, works! Let's make a guide!"... this isn't right man... it just ain't.
Still trying though. My phone ain't totally dead. It has recovery and download mode yet. That ought to mean something... right???
I'm taking a break from all the flashing, it gets me a nasty headache. Will try again tomorrow. Would be cool if anyone had any ideas that could help.
Just a thought, can I use ADB commands to manually fdisk the partitions? I just noticed that apply update from ADB option in recovery. Could that work? Also again in recovery I noticed my firmware is the KOT49H.N7100XXUFNE1. None of the firmware I tried to restore has this code. Does that mean I did everything wrong all that time? I have
N7100XXUFND3_N7100OXAFND3_XEF
N7100XXUFNL1_N7100EURFNL1_EUR
N7100XXUFOE1_N7100ITVFOF1_ITV
and the
N7100XXDLJ2_OXA_FACTORY from that guide.
Could flashing that specific firmware fix it?
I haven't noticed all that before because I though recovery was dead because it takes a lot time to load. But it's there, and works as intended, it just gives a bunch of error messages not being able to mount the partitions, I assume the OS and CACHE.
Bah my head! Enough for today.
Ok I wanna ask something to make it crystal clear. Would a bad USB cable/port give me the
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
error?
Or would it give me an error prior to that? No one says for 100%, but if they get that NAND error everyone says change USB cable. I find that difficult to understand, what does a USB cable has to do with the inability of ODIN to copy data from one device to another? If it were a totally screwed cable it wouldn't find the phone at all, right? Anyway to make sure I used a USB to Micro USB adapter as well. No cable is included in that one, only the internal connections. Well that failed as well prompting that NAND fail message.
Let me put it in another way, does the original Samsung cable maybe have some chip in it, that is used in certain situations like that? Or is everyone who says change cable/use original when faced with the NAND write fail error just plain wrong?