TLDR: My phone is softbricked, I've tried ODIN flashing Stock, I've tried flashing ROMS I've used before in TWRP... Nothin' workin'
fI was using Task's AOKP with no issues. Yesterday my phone was taking way longer to boot, but eventually made it, but my battery was draining like crazy... I rebooted my phone and it was stuck in boot loop. I tried reflashing the ROM/GAPPS but got an error during the GAPPS install that told me that system/build.prop was missing. I figured I should just try to revert to stock through ODIN and start from scratch. Here's what ODIN gives me when I try to flash the latest Samsung firmware:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? Are all soft-bricks eventually recoverable? I'm a phone addict...
Uggo said:
TLDR: My phone is softbricked, I've tried ODIN flashing Stock, I've tried flashing ROMS I've used before in TWRP... Nothin' workin'
fI was using Task's AOKP with no issues. Yesterday my phone was taking way longer to boot, but eventually made it, but my battery was draining like crazy... I rebooted my phone and it was stuck in boot loop. I tried reflashing the ROM/GAPPS but got an error during the GAPPS install that told me that system/build.prop was missing. I figured I should just try to revert to stock through ODIN and start from scratch. Here's what ODIN gives me when I try to flash the latest Samsung firmware:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? Are all soft-bricks eventually recoverable? I'm a phone addict...
Click to expand...
Click to collapse
The exact error I get when I try to flash GAPPS is:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error executing updater binary in zip '/external_sd/pa_gapps-stock-4.4.4-20140916-signed.zip
Error flashing zip '/external_sd/pa_gapps-stock
Updating partition details...
It's also worth noting that flashing the ROM (I'm going with the latest CM nightly) takes way too short of a time to complete
Sounds like your recovery may not like the binary used by the package.
For Odin though, do you have kids on your computer? If so uninstall it, reboot and try again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Sounds like your recovery may not like the binary used by the package.
For Odin though, do you have kids on your computer? If so uninstall it, reboot and try again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks, but it didn't help. I'm still getting the same problems.
Try a different version of twrp, or try cwm or philz recoveries too.
For that Odin flash, how big is the firmware you're trying to flash? I just noticed the "single download" line. Also, which version of Odin are you using and where are you putting the firmware? Looks like you might be putting it in the bootloader slot?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Try a different version of twrp, or try cwm or philz recoveries too.
For that Odin flash, how big is the firmware you're trying to flash? I just noticed the "single download" line. Also, which version of Odin are you using and where are you putting the firmware? Looks like you might be putting it in the bootloader slot?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks for all the help. I'm not sure what the issue was, but I ended up solving it by using the latest CWM recovery to install a flashable version of stock. I'm not a huge fan of stock, but I'm up for an upgrade in January so I'm going to just have to cool it on the ROM front to ensure I have a working phone.
Related
Hello, I recently acquired a note 2 n7100 and I have been trying to restore it. However, every time I try using odin, it gives me the that I the frimware upgrade encountered an issue error. I used the pit, but now it goes to the splash screen but nothing after that... Just a black screen. What should I do? I have been at this for hours and I am losing my mind!
Anyone have a solution? I am dying here!
EDIT: I got to the screen with the android on it and the little spinning ball in him, but then it just keeps booting to the android figure with the spinning globe. Any ideas?
You ll need to be more specific with your problem. Did you aquire the phone in working state? What were you trying to do. What did you do to achieve that? What was the results. What did you do to compansate that ? Etc....
Sent from my GT-N7100 using xda app-developers app
Try rebooting recovery (vol up+home+power)
wipe cache and data
if not works, input full details with complete odin log
and which ROM and pit file you have used
dr.ketan said:
Try rebooting recovery (vol up+home+power)
wipe cache and data
if not works, input full details with complete odin log
and which ROM and pit file you have used
Click to expand...
Click to collapse
Hello doc! I used the n7100 16gb pit you made and I am using the united arab stock rom, that is the only one that allows me to get to the android screen instead of a black screen. I tried the recovery button combo but that did not let me get into recovery.
I can update with my odin log when I get home. It all passes, nothing fails... So I guess I really dont know what is wrong with it.
Ok, try flashing stock recovery (get from here )
if you can flash it correctly then try rebooting in recovery and wipe cache and data.
otherwise post log of odin
dr.ketan said:
Ok, try flashing stock recovery (get from here )
if you can flash it correctly then try rebooting in recovery and wipe cache and data.
otherwise post log of odin
Click to expand...
Click to collapse
Thank you! Where do I find the log? Also if I can get this working I will definitely donate!
minnieman said:
Thank you! Where do I find the log? Also if I can get this working I will definitely donate!
Click to expand...
Click to collapse
The area which shows getting pit for mapping in odin application and all.
Sent from my GT-N7100
Ok, I tried flashing the recovery but that didn't work. I tried flashing the stock rom via odin again and it came up with the connect to kies error until I put the 16gn pit in and now it is back to the android figure with the spinning orb... Enclosed is the log, any other ideas? I am at a loss for words here.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB5_N7100OJVDMB1_N7100XXDLK7_HOME.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> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB5_N7100OJVDMB1_N7100XXDLK7_HOME.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
UPDATE: nevermind, it officially bricked so I am sending it in to be resurrected. Thanks for the help anyways doc!
Well it is flashing normally. Find a rom that will factory reset your phone.
Sent from my GT-N7100
I updated my i317M (Telus) via OTA and the next day it rebooted and went into boot loop.
I've tried flashing the phone with 4 different stock roms (from 4.1.2 to 4.4.2) but they all fail.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLBMA3_I317MOYABMA3_I317MVLBMA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried flashing Philz Touch recovery but that fails as well.
I've tried to boot it into recovery mode but it shows a dead Android with error logs like "E:failed to mount"
Help?
goyagoyago said:
I updated my i317M (Telus) via OTA and the next day it rebooted and went into boot loop.
I've tried flashing the phone with 4 different stock roms (from 4.1.2 to 4.4.2) but they all fail.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLBMA3_I317MOYABMA3_I317MVLBMA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried flashing Philz Touch recovery but that fails as well.
I've tried to boot it into recovery mode but it shows a dead Android with error logs like "E:failed to mount"
Help?
Click to expand...
Click to collapse
Try flashing with odin again but before flashing open the tar and remove the bootloader out of it.
Hi, thanks for the reply cnote.
Would the bootloader be sboot.bin or boot.img or both?
thanks again
edit: or rather, how do you remove the bootloader and remake the tar file?
goyagoyago said:
Hi, thanks for the reply cnote.
Would the bootloader be sboot.bin or boot.img or both?
thanks again
edit: or rather, how do you remove the bootloader and remake the tar file?
Click to expand...
Click to collapse
I believe it;s both. Just retrieve the tar file only.
sboot is the bootloader boot.img is the kernel .Have you tried the latest NH2 for your phone also maybe try using a pit file
The nh2 you will have to get from sammobile and the pit file can be found here http://forum.xda-developers.com/showthread.php?t=2609871
Also after odin is finished go into factory recovery and do a factory reset or its just going to sit at the boot screen
flashing pit file also gives an error :S
Was unable to turn on Note 2 (stuck at samsung note 2 loading screen)
Went to flash, got the below message.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105XXUFNG4_N7105OLBFNG1_N7105XXUFND3_HOME.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> tz.img
<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)
anyone? All I have been doing is reflash the boot.tar.md5, and then try flashing another older firmware 1 by 1...
Lobaba said:
anyone? All I have been doing is reflash the boot.tar.md5, and then try flashing another older firmware 1 by 1...
Click to expand...
Click to collapse
Have you tried flashing this file before? It maybe a corrupted download. Please check.
erljayp said:
Have you tried flashing this file before? It maybe a corrupted download. Please check.
Click to expand...
Click to collapse
I have been downloading newer and older firmwares from samfirmware. tried up to 4 firmwares so far
Lobaba said:
tried up to 4 firmwares so far
Click to expand...
Click to collapse
I had flashing issues before only to know that my download is corrupted or when I extracted my stock rom, it didn't finish properly.
You can try reinstalling samsung drivers. What odin version are you using?
i tried version 3.10
So, I have the SM-G920P. I was encrypting it when it failed. Well that sucks. Fired up Odin, set my phone into download mode, loaded the only version of the stock rom I have (5.0.2). It was running the newest version of the firmware, 5.1.1 with the stage fright fix. I'm using Odin 3.10.6 and when ever I try to flash it, Odin just says this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How do I get it to pass?
Edit: I've tried different USB cables, different USB ports, everything.
ovil101 said:
So, I have the SM-G920P. I was encrypting it when it failed. Well that sucks. Fired up Odin, set my phone into download mode, loaded the only version of the stock rom I have (5.0.2). It was running the newest version of the firmware, 5.1.1 with the stage fright fix. I'm using Odin 3.10.6 and when ever I try to flash it, Odin just says this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How do I get it to pass?
Edit: I've tried different USB cables, different USB ports, everything.
Click to expand...
Click to collapse
From all I have read you can't Odin back to a previous version once on 5.1.1.
Try this: http://forum.xda-developers.com/showthread.php?p=62274187
Sent from my SM-G920P using Tapatalk
correct, you cannot go back after you're on 5.1.1, that's why it's not working, you need to Odin a 5.1.1 tar
sent from my S6 using tapatalk
I am having the same error messages in ODIN as the OP. EverYthing I flash through ODIN fails. Even flashing stock 5.1.1 OF7 fails. I believe it's because I was on OGA so I have to wait until the tarball for that comes out I guess.
was a solution to this ever found?
Orion9k0 said:
was a solution to this ever found?
Click to expand...
Click to collapse
Yes. Use the latest version of Odin (3.10.7 or 3.10.6, both can be found here: http://www.samsungodindownload.com/) and use the latest stock TAR from: http://forum.xda-developers.com/showpost.php?p=63956192&postcount=226
Check the md5 on your TAR download to make sure that it matches. In my experience getting a bad or incomplete download is the number one cause of errors.
And be aware that you CANNOT DOWNGRADE. If you flash to the latest stock and firmware, you can't go back.
my s6 dosen't want to be fomated by givng me msg of cant open the serial(COM)port,and when am removing it in the pc it is turning off,
Boot loop after factory reset on GT-N5110
I tried to reset the device using Settings>Back up and reset>Factory data reset>Delete all.
Rebooted into a black screen with an Android with a hatch open and a blue spinning thing. It's been stuck in a endless loop of the startup screen with the name and model, which then goes to the Android with open hatch.
I pried the rear cover off and discovered that I don't have any screwdrivers small enough to remove the battery. So I'm wondering if there is any software based fix that I can try.
Holding down Power+Volume Down interrupts the loop and brings up this screen - blogyourearth.com/wp-content/uploads/2012/02/Samsung-Galaxy-S2-Warning-Custom-rom-installation.jpg
I've had the tablet for 2 years, so the warranty is long gone. I'd be open to flashing a Custom Rom/Kernel, as long as I'm able to go back to the default TouchWiz 4.1.2.
Bump/Update
Update/bump.
Tried flashing the stock 4.1.2. firmware from sammobile.com with Odin v3.07. - Doesn't seem to work, here are the status messages from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> boot.img -----Status was frozen on boot.img for 3 hours.
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any idea what's wrong? Should I try a different version of Odin, different firmware or what?
emc_2 said:
Update/bump.
Tried flashing the stock 4.1.2. firmware from sammobile.com with Odin v3.07. - Doesn't seem to work, here are the status messages from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> boot.img -----Status was frozen on boot.img for 3 hours.
<ID:0/004> __Xmit Write fail
<ID:0/004> XmitData Fail..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyone have any idea what's wrong? Should I try a different version of Odin, different firmware or what?
Click to expand...
Click to collapse
Are you able to enter download mode without issues?
pvsgh said:
Are you able to enter download mode without issues?
Click to expand...
Click to collapse
Yes, no issues at all.
emc_2 said:
Yes, no issues at all.
Click to expand...
Click to collapse
Try flashing TWRP recovery, take a backup of your current ROM, and then try installing one of custom ROM .
pvsgh said:
Try flashing TWRP recovery, take a backup of your current ROM, and then try installing one of custom ROM .
Click to expand...
Click to collapse
Have no idea on how to do any of the above, but I'm googling now. Are there any guides/articles on how to do this, that You could point me in the direction of? Since I'm soft-bricked, is there any point in trying to back-up my presumably borked ROM? I've already downloaded my country specific, stock 4.1.2. ROM.
Many thanks for taking the time to help me and I apologize for the noob questions. I know my way around Windows, but when it comes to Android - I'm hopeless
I flashed TWRP successfully, I think...
Stumbled across the ODIN troubleshooting thread and one of the steps was to try different cables. The 10 foot cable I've been using for the past 8 months would only end up with a failure, stock cable... didn't even register. 8 inch cable I bought for my external battery had a successful flash in 10 seconds!
<ID:0/004> Added!!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i.imgur.com/HPziH0E.png
emc_2 said:
I flashed TWRP successfully, I think...
Stumbled across the ODIN troubleshooting thread and one of the steps was to try different cables. The 10 foot cable I've been using for the past 8 months would only end up with a failure, stock cable... didn't even register. 8 inch cable I bought for my external battery had a successful flash in 10 seconds!
<ID:0/004> Added!!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i.imgur.com/HPziH0E.png
Click to expand...
Click to collapse
OK so now you have a working TWRP recoveryand you also know what was causing ODIN to fail.
Next step would be to install a custom ROM, check the development section.
if you prefer stock then you ODIN your stock tar file which you downloaded.
Using TWRP, I backed up; EFS, Boot, Cache, System and Data. After the backup completed I followed the prompt to reboot and it booted into Android *happy dance*.
looks like all the user preferences are gone. No more password or background pictures and all apps have been removed from their folders. Basically looks like all the apps that I installed are there and any data associated. But all my preferences and set options are gone.
Going through the apps, I remembered that I had rooted using Framaroot. Do you think that may have been the cause for the soft-brick? Should I un-root and then try the factory reset again or just flash the stock ROM that I downloaded?
EDIT: didn't see your reply when I started typing this out. Since TWRP is flashed. Does that mean it has replaced whatever recovery Samsung had in place? If so; does having it installed/flashed increase the chance of a fairly stress free recovery in case of future problems?
So, it turns out pvsgh is pretty awesome!
It worked! Thank you so much. You rock!
Had to use another cable though. I think I need a new USB/Charge port
After flashing the stock ROM I had quite a bit of left over data like app folders and pictures/screenshots. Went into the stock recovery and did a factory reset from there, which wiped the internal storage back to factory state.
Should I flash TWRP again and use it to backup everything, now that everything seems to be working normal. Or just leave it as is?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
i.imgur.com/j9neU0B.png
emc_2 said:
It worked! Thank you so much. You rock!
Had to use another cable though. I think I need a new USB/Charge port
After flashing the stock ROM I had quite a bit of left over data like app folders and pictures/screenshots. Went into the stock recovery and did a factory reset from there, which wiped the internal storage back to factory state.
Should I flash TWRP again and use it to backup everything, now that everything seems to be working normal. Or just leave it as is?
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N5110XXBMC9_N5110XACBMC9_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
recovery.img
system.img
cache.img
hidden.img
RQT_CLOSE !!
RES OK !!
Removed!!
Remain Port .... 0
All threads completed. (succeed 1 / failed 0)
Added!!
Removed!!
i.imgur.com/j9neU0B.png
Click to expand...
Click to collapse
You can take a backup that you can use to restore your tablet if you ever get issues again.
Or just follow the same procedure again.
Taking backup is completely a user choice whether he want it or not.