Looking for second opinion before I replace the board.[GT-N8013] - Galaxy Note 10.1 Q&A, Help & Troubleshooting

I have the GT-N8013 note 10.1. It was rooted, running Omni 4.4.4 rom from about a year or two ago, using TWRP custom recovery. I mainly use it for Plex movie streaming and Pandora while I work. Yesterday I noticed it was sitting at the Samsung Galaxy Note 10.1 splash screen, and it doesn't seem to want to boot anymore. At this point, it will only allow me to get into download mode and ODIN does recognize it. When I try to boot into the custom recovery, it will show the TWRP splash screen for about a second or two, then reboot and go back to the Galaxy note 10.1 splash screen. Below is a list of everything I've tried to fix it.
Through ODIN on pc:
-Flashed stock 4.1.2 rom from Sammobile, It "passes"
-Flashed stock recovery, It "passes"
-Flashed Philz recovery, It "passes"
-Tried having ODIN erase the NAND, but it always fails
Disassembled tablet and pulled battery for about 5 minutes and reconnected.
After all that, it still does the same thing. Turns on, and stays at the Samsung Galaxy Note 10.1 splash screen and doesn't boot. From my searching around, I've found that the N8000 models(I would assume all models) seem to over time have faulty NAND Flash modules. It seems like that model has a modular NAND flash, however the 8013 doesn't.
Does anyone else know of anything else I can try before I replace the mainboard? Thanks in advanced for any info.

Same problem
My wife's N8013 is in the same condition. It had gotten slower and slower and I planned to reset it. Somehow it seemed to lose Root awhile back. She said it behaved weird then did the hang at Sammy screen. Odin flash said pass but we know how it ends. Where do we go from here, I have been researching this Nand problem for most of the day and what people say works for their tablet is not fixing mine. Is it even repairable? She is considering Iphone and Ipads after this and problems with her locked bootloader GS5. Not happy with samsung lately.
xxcrashxx said:
I have the GT-N8013 note 10.1. It was rooted, running Omni 4.4.4 rom from about a year or two ago, using TWRP custom recovery. I mainly use it for Plex movie streaming and Pandora while I work. Yesterday I noticed it was sitting at the Samsung Galaxy Note 10.1 splash screen, and it doesn't seem to want to boot anymore. At this point, it will only allow me to get into download mode and ODIN does recognize it. When I try to boot into the custom recovery, it will show the TWRP splash screen for about a second or two, then reboot and go back to the Galaxy note 10.1 splash screen. Below is a list of everything I've tried to fix it.
Through ODIN on pc:
-Flashed stock 4.1.2 rom from Sammobile, It "passes"
-Flashed stock recovery, It "passes"
-Flashed Philz recovery, It "passes"
-Tried having ODIN erase the NAND, but it always fails
Disassembled tablet and pulled battery for about 5 minutes and reconnected.
After all that, it still does the same thing. Turns on, and stays at the Samsung Galaxy Note 10.1 splash screen and doesn't boot. From my searching around, I've found that the N8000 models(I would assume all models) seem to over time have faulty NAND Flash modules. It seems like that model has a modular NAND flash, however the 8013 doesn't.
Does anyone else know of anything else I can try before I replace the mainboard? Thanks in advanced for any info.
Click to expand...
Click to collapse

xxcrashxx said:
I have the GT-N8013 note 10.1. It was rooted, running Omni 4.4.4 rom from about a year or two ago, using TWRP custom recovery. I mainly use it for Plex movie streaming and Pandora while I work. Yesterday I noticed it was sitting at the Samsung Galaxy Note 10.1 splash screen, and it doesn't seem to want to boot anymore. At this point, it will only allow me to get into download mode and ODIN does recognize it. When I try to boot into the custom recovery, it will show the TWRP splash screen for about a second or two, then reboot and go back to the Galaxy note 10.1 splash screen. Below is a list of everything I've tried to fix it.
Through ODIN on pc:
-Flashed stock 4.1.2 rom from Sammobile, It "passes"
-Flashed stock recovery, It "passes"
-Flashed Philz recovery, It "passes"
-Tried having ODIN erase the NAND, but it always fails
Disassembled tablet and pulled battery for about 5 minutes and reconnected.
After all that, it still does the same thing. Turns on, and stays at the Samsung Galaxy Note 10.1 splash screen and doesn't boot. From my searching around, I've found that the N8000 models(I would assume all models) seem to over time have faulty NAND Flash modules. It seems like that model has a modular NAND flash, however the 8013 doesn't.
Does anyone else know of anything else I can try before I replace the mainboard? Thanks in advanced for any info.
Click to expand...
Click to collapse
My personal N8000 issue is somewhat like this.... Im noticing this is quite common for this device, also still waiting for a reply on my thread, but will be keeping close watch on this thread as well.

Which NAND module?
I'm ready to pull the trigger and order either a new motherboard or NAND chip but for the life of me I cannot pull up the right part number for the NAND. I want the part in hand before I tear it completely down. Mine is the;
GTN8013EAYXAR
Anybody able to help? the chip is on the underside of the board and I have the case open but want to see if part is even available first.
Kultabashi said:
My personal N8000 issue is somewhat like this.... Im noticing this is quite common for this device, also still waiting for a reply on my thread, but will be keeping close watch on this thread as well.
Click to expand...
Click to collapse

turbo23 said:
I'm ready to pull the trigger and order either a new motherboard or NAND chip but for the life of me I cannot pull up the right part number for the NAND. I want the part in hand before I tear it completely down. Mine is the;
GTN8013EAYXAR
Anybody able to help? the chip is on the underside of the board and I have the case open but want to see if part is even available first.
Click to expand...
Click to collapse
Unfortunately for the n8013, the nand chip is soldered to the board and surrounded by glue. It's possible to replace it for a skilled technician with the right tools [IR or dark IR reflow station]. Similar to replacing the xbox 360 gpu's, but these and solder beads are much smaller. The board would need to be replaced. I managed to find a couple on ebay that were pulled from working systems, but you really don't know how long it will last since this seems to be an issue that is starting to pop up more and more.
I'm planning on ditching the tablet and probably most Samsung devices and either build a small pc, buy a raspberry pi, or other "open" android device.
Here's the teardown guide from ifixit. https://www.ifixit.com/Teardown/Samsung+Galaxy+Note+10.1+Teardown/10144 You can see the NAND chip in step 14.

Replaced the entire tablet, nm
I picked another one off eBay. Sofar sogood. Wife is happy. No need to root it. Finished with sammy devices. Upgraded from my S5 phone to a Motorola X pure, never looking back. No crapware or locked BL hassles. Peace.
xxcrashxx said:
Unfortunately for the n8013, the nand chip is soldered to the board and surrounded by glue. It's possible to replace it for a skilled technician with the right tools [IR or dark IR reflow station]. Similar to replacing the xbox 360 gpu's, but these and solder beads are much smaller. The board would need to be replaced. I managed to find a couple on ebay that were pulled from working systems, but you really don't know how long it will last since this seems to be an issue that is starting to pop up more and more.
I'm planning on ditching the tablet and probably most Samsung devices and either build a small pc, buy a raspberry pi, or other "open" android device.
Here's the teardown guide from ifixit. https://www.ifixit.com/Teardown/Samsung+Galaxy+Note+10.1+Teardown/10144 You can see the NAND chip in step 14.
Click to expand...
Click to collapse

I didn't even bother replacing the board in mine. I'm just not using a tablet anymore. I too am done with Samsung devices. Upgraded my phone from the S4 to a Oneplus One. It's an awesome phone, everything I was looking for and then some.

Related

Note 10.1 s pen not working at all

Hey guys, been a long time lurker here and just encountered my first issue, so made an account to hopefully get some advice.
I received the note 10.1 8010 (UK) as a gift for Christmas. I was disappointed to see it was running 4.0, when devices like the Nexus 7 are already on 4.2. And Germany had the 4.1 update for over a month. Samsung as always refuse to give a solid answer.
I followed a guide to install the German 4.1.1 update. I first installed the German version of ICS via Odin. I then applied the update.zip from here:
HTML:
d-h.st/lLB
Prior to this, I rooted the device, but I believe the above process removed the root anyway.
After my device rebooted, the S Pen isn't working at all. It recognises when I take the pen out, but I cannot use it. It doesn't do a thing. I've read about 1,000 forum threads and cannot find an answer, as to how I can get it working again.
I tried deleting cache and user data, then reapplying the update.zip to no avail.
When I boot up in to recovery mode, it does come up with a message about CSC and then the little drop falls over and I have the usual options.
Any idea what I need to do, to get my S Pen working again? Or what I've done wrong?
Many thanks
This is how I rooted the device.
HTML:
rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
I have a feeling this is the "root" of the issue. I'm not sure how to remove it.
I know previously I wasn't able to change my CSC via CSC switcher, but I am now.
So I guess installing the German ICS and then update.zip, hasn't completely undone whatever rooting it above did.
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Tehkseven said:
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Click to expand...
Click to collapse
This a pretty bummer situation. Sorry you're dealing with it.
I find this interesting, as I followed the exact same procedure to root as you. I haven't experienced any pen issues though.
Could it be the 4.1 you flashed?
This is one of my fears too, so I really hope this can be solved.
I finally managed it.
I downloaded a different German ICS from a different guide and this time it worked no problems.
The one that worked, had a file name: N8010XXALI3_N8010OXAALI3_DBT
Update.zip worked first time after I installed the above ICS.
Hope that helps.

[Q] Reinstalled stock rom, can't get upgrades

Hi, I'm sorry if this has been asked before, basically a few weeks ago I was having problems with my Tab 2 p3110, it just wasn't running right. At around the same time I ordered an EZCAST hdmi device for my tv.
Well, I used Odin and cwm and taught myself how to upgrade to kitkat withCM11 nightlies, great stuff, fixed the issues I was having.
Then my tv dongle arrived, the one feature I wanted to use more than anything was screen mirror/AirPlay. No you can imagine my dismay when I couldn't even find the option in cm11, I found cast screen but it wouldn't work.
So, having tried several nightlies hoping the problem would be fixed I settled on reinstalling the stock 4.2.2 rom following the instructions on here. It bricked my tab 2 but I managed to get it going again and reinstalled the stock rom after several days of trying.
All this to find the screen mirror option was not available on the stock rom!! I can't figure out why but thought, maybe, an upgrade was needed, so I headed to the update tab to be told that my device was modified, updates are not available!
To be honest I'm ready to throw it in the lake behind my house I'm that frustrated, does anyone have any suggestions on getting screen mirroring working?
http://live.samsung-updates.com/index.php?device=GT-P3110
Here... get the clean firmware here. It will give a pure system that won't trip the modification check.
It will also give you the factory recovery system.
Look up the p311x PIT file and when in odin pick the size that matches your tablet.
If it hangs at boot try doing a factory reset from recovery.
That's what worked for me to allow me to check updates.
I can't say that this will fix screen mirror, since I've never used it or seen the option on my p3113
Sent from my SGH-T999 using Tapatalk
Thanks for that. I can't find my model number on the list, The british one is close and as thats where I live i think i'll give that a go.
Thanks again for your help
Didn't work, still saying that the device has been modified and in download mode shows "count 1"
Any other ideas?
Triangle away?
Sent from my SGH-T999 using Tapatalk
Hey, I use my tablet with the Samsung Smart View ap.
You must have the right samsung tv for it to work and it's not perfect, but it is a nice feature. I stopped updating my tab because this is the most important feature for me.
I rooted my device and have the same issue as you, that's how I came across this thread.

Ive broken my Note 2 (ROM upgrade gone wrong).

Hi Everyone,
I come to you for a bit of help. I have spent a long time trying to fix this and come for help from you guys.
So I got a little bored with standard Samsung Android on my Note 2 (GT-N7100). Having used Cyanogen before, I decided to try it on the note.
I rooted the device and installed CWM on it no problems. I then loaded CM from a micro usb.
On reboot it just gets what i'd call the "Spinning blue screen of death" where it just has the big blue circle going round until it runs out of battery. After some research I used CWM to clean out the caches etc but it still didn't appear to work. This was using the stable version for my Note 2. I then went on to try other versions and got the same issues. Alas, trying to do a restore didn't work either, as it didn't seem to have all the files.
At this point I am happy to go back to stock Android or indeed CM. I'd just like a phone that works!
My device details:
Model GT-N7100
SSN: -N7100GSMH
Network Provider Virgin UK
Any help appreciated.

Issue since cm11,4.4.4, es manager and usb not recognized

My 959V is rooted, had plenty of roms,ect over the last 3 years decided to do Gremlin remover and update it...,
Couple days ago upgraded to the "909" download of CM11,4.4.4, but every site I get it from gives me 908 (even though they all say 909) (last 3 digits of download version). The 908 will not recognize on my Win 7 laptop, but was fine up to now with previous cm11 same phone..
I have used the same cable for the last year for both my Galaxy and 2 Sidekicks phones, data and charging, now the Galaxy only charges, Windows detects but wont recognize, does on the sk4g's
Also (908) will not allow me to paste into sys/media with a " read only issue", although up to now swapped 15 different bootani without problems. Tried 3 different root file managers,same outcome.
Is the driver for the phone firmware windows looks for(on the phone itself) replaceable from sdcard? Im guessing its a bootloader issue and the 908 is the one not to of put on my phone.
Whats the probability I am getting the 909 but the 908 will not allow it to surpass it. Goes through the whole flash and on reboot I have to reenter emails,playstore apps,ect, but on 908 still in settings.
I can/ have been able to swap 1 rom via twrp and sdcard on 908 ( to slimkat4.4.4 and back to 909, but comes up 908) any other roms error before flash(and slimkat does not recognize on usb either).
is it a Kernel fix, and can it be flashed via sdcard? Bootloader via sdcard? Bad usb port? Does charge, and the drivers/ cable verified.
Thank you for any help, been 3 days now, redone my laptops (2) from scratch, everything ,c++,java,netframework,samsung,zadig 2.0, and more.
DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.
FBis251 said:
DId you do a clean upgrade (did a factory reset) before you installed CM11? If you didn't, go into TWRP and do a full backup (/system, /data) and do a factory reset, then boot up the phone and see if your computer will recognize it.
Click to expand...
Click to collapse
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
I didnt do a backup, if thats an issue , can I backup 2nd motherboard and apply to the first?
Floridasun said:
Yes, cashe,factory and davlik, before and after flash. I also have a 2nd motherboard,swapped them out and seen that it also is the 908 download but does recognize and allows me to ES Explorer swap boot animation. Im guessing I somehow erased the driver from the phone itself.
Ive done some Iphone jailbreaking unlocking for friends and found that a certain baseband (if I remember right 5.13.xx or 5.16.xx) would basically lock the phone unable to downgrade or upgrade and was to be avoided. Wondered if this a similar issue. (screwing up my bootloader)
What does windows look for via usb in the phone, adb,? Is it in the kernel and reflashable via sd?
I read also that the mini usb port can get bent over time and needs centering, tried that, cord fits better but not the issue.
Tried to zagdig the 2nd motherboard (worked) for drivers, but the 1st one still has error,device malfunctioned and cant be recognized by windows (7).
If i can get the Anton basic with a twist (no rom just the cm,I have it for Oden but wonder if Its possible cm flash)., Im good I believe,thats how I first rooted and got 4.3 cm,then 4.4.4, 908. Dunno,willing to try anything, not worried about it as I have a 2nd motherboard.
The rom is awesome, with no isuues except the battery stats vary. It says 3 hrs left then dies 10 min later, tried to erase the battery cashe in recovery but doesnt change anything. (related via usb?)
Thank you.
Click to expand...
Click to collapse
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?
FBis251 said:
You can flash new kernels via recovery but it sounds like your issues are bigger than that. The fact that the 2nd motherboard is recognized via USB but not the 1st suggests that there's some kind of hardware issue. The drivers on your computer are working fine since the 2nd mobo is recognized, and so is your USB cable.
Why not just keep using your 2nd mobo? Is there something wrong with the 1st?
Click to expand...
Click to collapse
O.K., so Ive been playing with the second mobo just to test different angles.
1) E.S. File manager is the culprit, swapped out for a paid app Ive used with Sidekick 4g, Root Explorer, and boot ani. goes fine, on both mobos.
2) The latest gapps (cm 11 w/ gaps 4.4.x) was giving me a "Google servers cannot be reached" error on both mobos, used the gapps for cm 10.1 (jb 4.3) and all is working, both mobos.
3) Was reading that possibly the adb driver is in the kernel, and thats what windows is looking for? Ive tried but can only sd card flash at this point so, giving up. I can bluetooth,wifi share or email files to myself if need be. Im guessing its a hardware issue beings that the 2nd mobo was reflashed identical to to the first. (with exception of one click 2.3.6,and w/a twist oc/uv on the 2nd),1st one will not downgrade at all below 4.4.4 by sd, I was trying to ics a rom guessing the foundation might overwrite any missing stuff then upgrade back to 4.4.4.
One post mentioned that the mtd/bml cross flash is a no-no, could that mess up usb driver identity on the phones side?
Not a big deal, both phones/ roms are working great and have no issues (except 1 doesnt connect to a computer for file transfer). Thank you for your help.
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Also, the phone was working fine up to about a month ago, it was recognized by the computer, only difference I made was trying apps, off playstore, five fingers for ebay,different weather apps for widgets,silver/gold prices apps. Thats when it started not recognizing.
I was getting the same error about the google servers, then I tried a earlier version of gapps. Connects now.
Floridasun said:
Little early to ask but are you going to be in this forum long enough for lollipop to be ported? I would send you this phone for devving if you think you can get it to transfer files. Also need to get a lcd/digitizer, i have the rest of the phone.
Click to expand...
Click to collapse
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
As far as the phone itself goes, the phone should be recognized even if there is no driver for it installed on your computer. You can use this software to verify that
http://www.nirsoft.net/utils/usb_devices_view.html
I don't believe you can even edit anything on the phone to make the USB device not be recognized when plugged in short of bricking your phone, so if there isn't even a USB connection being made, as I mentioned before, it looks like a hardware issue is causing your problems.
In that case, it'll be hard to flash anything without going through a lot of hassle since all the reliable recovery methods we have need that you are able to use your USB port on the phone.
EDIT
If you do still have TWRP available on the phone, flashing any ROM will reflash a kernel, but be careful because the recovery is tied to the kernel and some ROMs have a non-working recovery, so if you happen to flash some of these you'll be stuck with a nice paperweight . The latest CM11 I have posted does have a working kernel/recovery but I still don't think it'll fix your issue.
FBis251 said:
I have no plans to try a Lollipop port, this phone is almost 4 years old now. You might be better off sending the phone to @bhundven since I recently got two dev phones donated to me.
Click to expand...
Click to collapse
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.
bhundven said:
I'm currently looking into it, as well as fixing some issues with cm11. I have an SGS4G, so no need to send a phone.
Not just is it a 4 year old phone, but I am not sure how many people even use this as a daily driver anymore.
Click to expand...
Click to collapse
I still use two of them. Great little phones really. I see no need or use for 5.0 I think running this CM11 from you guys is about the end of the road for these phones. A great ride indeed. Ill be sticking around regardless just to see what happens. Thanks guys☺

[Q] What type of brick is my Galaxy note 10.1 gt n8010 stuck?

Two days ago my Galaxy Note 10.1 gt-n8010 got stuck at the initial screen (Samsung Galaxy Note 10.1)
It was working normally, and it was last successfully upgraded to a custom rom and CWM 6.0.3.6 a month ago.
The custom rom was (to my best knowledge Android Revolution HD 11.2 - 4.1.2)
Booting into recovery and download modes works.
CWM recovery works partially. Erasing Cache en resetting to factory works, and sometimes results in getting to the second splash screen of the boot process where it again gets stuck (Samsung animation keeps glowing), but more it keeps getting stuck at he first boot screen.
Erasing Dalvic cache leads to immediate reboot.
CWM log files cant be opened / external sd card can't be reached/mounted.
So CWM is only working for a small part.
I've attached images of the CWM screens including a log-screen that shows that files and folders cannot be found.
Using ODIN, to flash a new CWM or custom/original ROM result in a FAIL message.
Tried different ODIN version, two original Samsung data cables and two computers. Alle the same result. FAIL.
I'm hesitant to continue now without some help. I might do more harm and destroy all chances there are to recover this tablet.
I've flashed all my phones and tablets before. I'm not an expert, but never had a mishap, because I triple read the instructions. The situation that arises now is not a result of a failed upgrade/flash, but suddenly appeared one morning.
On the last days i thought i had also broken my tablet and i had more or less the same problem. If i were you i would directly download an official 4.4.2 and flash it via odin. Then if you everything works i would try whatever you want to flash
Try changing recovery. Give TWRP a try. Had it happen with a phone and switching recoveries solved it.
Sent from my SM-N900T using XDA Free mobile app
Well I had the same problem due to toooo many consecutive reboots
I was on gnabo then wid twrp
then I reflashed 4.4.2 update via odin and everything was a breeze after that
and one more thing
be sure to change the recovery cause the same one might not work again
well at least it didn't do worth me
I use philz now
Can't flash anything
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Deadbeef said:
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Click to expand...
Click to collapse
are you sure you do not have a bad cable
I've used two different original Samsung cables. Same result.
Brick?
Change a Odin version like odin 3.07 http://forum.xda-developers.com/showthread.php?t=1837605?
your odin shows your device is Samsung I9505 Galaxy S4
Where does Odin show the device is a i9505? It's a n8010.
reCAPTCHA
I am having similar issues (Galaxy Note 10.1 N8010 Gnabo ROM) - stuck on the samsung logo (never managed to get past it though) boots into recovery but can't mount sd card OR internal storage. Can't flash anything using Odin, always gets a Complete(Write) operation failed. Any suggestions ?
Looks like we're both in the same sinking boat.
Sorry for late reply
Deadbeef said:
Where does Odin show the device is a i9505? It's a n8010.
Click to expand...
Click to collapse
Sorry for late reply
Your Odin Screen Shot Say i9505 as your device
Deadbeef said:
Looks like we're both in the same sinking boat.
Click to expand...
Click to collapse
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
georgesmh said:
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
Click to expand...
Click to collapse
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Agyar said:
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Click to expand...
Click to collapse
guys did any of you solve the problem??
georgesmh said:
guys did any of you solve the problem??
Click to expand...
Click to collapse
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Agyar said:
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Click to expand...
Click to collapse
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
georgesmh said:
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
Click to expand...
Click to collapse
I've seen few other occurrences of this on different roms on various forums, so probably not Gnabo issue. also, nobody nowhere had a fix for it
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
dmarchant said:
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
Click to expand...
Click to collapse
I don't think it was flash failure, at least not in my case, since device worked without any issue for quite a while after last flashing... what was different now is that my battery was drained out for the first time i quite a while...

Categories

Resources