Database Info

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] New Note Pro?

Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900

So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk

Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)

muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?

I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .

48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.

Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.

Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.

It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".

Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069

You are a much braver sole than I. Hope all goes smoothly.

I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk

treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!

Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.

Sweet Deal singhsta! I'm glad my efforts were a help!

i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.

Unable to restore/mount/flash in TWRP and unable to achieve dl mode in LG Flashtool

Here's to hoping someone can help me out. My phone details before I messed up: LG G3 D850, rooted, TWRP 3.0, running Fulmics 5.2 for about 1 1/2 weeks
I noticed that I was not seeing the LTE indicator on my phone. I checked the HUB and saw the BootD850-30012016 data patch and figured that I just needed to install. So I flashed it and my phone wouldn't start. I was able to boot into recovery, so I figured I would do a clean install of the ROM so I did a full wipe, accidentally wiping EVERYTHING except for my external SD.
Result was that I can access TWRP but am unable to flash any of my backups or zips from my external SD, or OTG. I can see the files, but don't have the option to "swipe". I also am unable to 'mount' or 'install'.
At this point, I noticed that AT&T has finally released the OTA for Marshmallow, so I figured I would just use LG FlashTool and totally un-root and give the update a try. (BTW, I have used the flash tool many times with no problems/issues on both my phone and my son's D855).
Unfortunately, I am getting the dreaded "unable to change to download mode" after 15 seconds. I have uninstalled and re-installed Flash Tool, the LG Drivers and all files and used every port on both of my computers (Windows 10 btw) but can't get past the download error.
So...after many hours of digging, I took a leap of faith and was able to sideload Fulmics 5.1 successfully and install the 5.2 update from the HUB. I made backup of the ROM but TWRP still won't allow me to "swipe" and install/restore. I reinstalled TWRP using Flashify and it installed version 2.8 but still no go on flashing from recovery.
I realize that I'm lucky to have been able to figure out how to get the phone back using the sideload function in TWRP, but I really do want to go back to stock and it bugs me that I am unable to use my backups.
Sorry for the novel, but I wanted to be sure to include everything I did....if anyone can help me out I would be much obliged. My 11 year old is anxiously waiting on me to figure this out before she gets this phone (I'm moving up to the HTC 10 in a couple of weeks!). She still thinks I'm 'SuperMommy' so if I can fix this I get to keep my swagger!

I was also running fulmics 5.1 and updated to 5.2 in my phone but now i was having pretty good laggs and i finally realised that the update provided by the phone was corruped so i went on the official site and downloaded the same 5.2 OTAs from there and flashed it into TWRP recovery to finally get the latest version 5.3..know that is it always advisable to flash zip file when in recovery mode using TWRP recovery...The big mistake was cleaning also the internal memory of your phone.this caused the malfunction of twrp.

The issue is that most often i have seen cases of lagg in those updating to fulmics 5.2 from the Hub .sometimes in twrp recovery the update files will not successfully wipe and then reboot system with 5.2 installed but with many lagg the file downloaded there may be corrupted and not give you permission to swipe..if you really like fulmics and still update to the latest..Try this it may help you solve your problem:1 reinstall the fulmics 5.1 go to xdadevelopers.com/fulmics follow the link given by xpirit to www.fulmics.com and download the OTA 5.2(file size maybe 46 mb).. 2.reboot your phone now in twrp recovery it should now be able swipe and install..(if not then install Twrp 3.0 and try) 3-search the files in your internal memory or wherever you have downloaded it and flash it ..4.reboot system.That should be done!! In case you want to come back to stock and cant install from Twrp then the problem is with Twrp just download the latest version that goes with your phone.

Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.

dcli23 said:
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
Click to expand...
Click to collapse
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk

SofaSpud said:
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Hey there....you can access the Hub after you flash the Fulmics ROM. It's where you can get your tweaks, downloads, mods, etc. You'll find it in your app drawer.

[S6] Crashed and stuck in bootloop, please help!

Hi guys!
I have a Galaxy S6 for 1,5 years now. I was on Whatsapp, and the phone got into the boot loop randomly. Everything is still original, not rooted or a custom firmware. Most important thing for me is to get my data back. The data is more important than the phone for me.
This is what I already tried to do:
-Got the battery replaced in a shop (they replaced it 3 weeks ago, so they did it again just to be sure...)
-Samsung Premium Service hooked it up to a service device, that would bypass the battery and supply it's own power. Still the same, and the guy told me the voltage was fine.
-Another shop reflashed the firmware part with Chimera, he said that won't delete the data on the phone. Flashing was done, but still the same problem.
-I flashed the phone with Odin and the original firmware. First 5.1, but that gave me an error. Then I flashed the firmware parts separately, only sboot.bin and cm.bin gave me an error.
-Later I flashed the phone with Odin and the newest 6.0.1 Samsung firmware. I think the shop before flashed it also with Android 6, that's the reason why 5.1 gave me an error. Anyway, flashing to 6.0.1 with Odin was successful, but the phone still has the same problem.
I can only enter Downloading mode on the phone. Recovery mode doesn't work. USB debugging is not enabled.
Any suggestions or ideas? Any help would be very much appreciated. The data on the phone is really important to me.
Thanks a lot!

MTS0 said:
Hi guys!
I have a Galaxy S6 for 1,5 years now. I was on Whatsapp, and the phone got into the boot loop randomly. Everything is still original, not rooted or a custom firmware. Most important thing for me is to get my data back. The data is more important than the phone for me.
This is what I already tried to do:
-Got the battery replaced in a shop (they replaced it 3 weeks ago, so they did it again just to be sure...)
-Samsung Premium Service hooked it up to a service device, that would bypass the battery and supply it's own power. Still the same, and the guy told me the voltage was fine.
-Another shop reflashed the firmware part with Chimera, he said that won't delete the data on the phone. Flashing was done, but still the same problem.
-I flashed the phone with Odin and the original firmware. First 5.1, but that gave me an error. Then I flashed the firmware parts separately, only sboot.bin and cm.bin gave me an error.
-Later I flashed the phone with Odin and the newest 6.0.1 Samsung firmware. I think the shop before flashed it also with Android 6, that's the reason why 5.1 gave me an error. Anyway, flashing to 6.0.1 with Odin was successful, but the phone still has the same problem.
I can only enter Downloading mode on the phone. Recovery mode doesn't work. USB debugging is not enabled.
Any suggestions or ideas? Any help would be very much appreciated. The data on the phone is really important to me.
Thanks a lot!
Click to expand...
Click to collapse
Try this thread linked below, try the instructions in post #6. Don't use any files that are linked in the thread, they are not for your device. Make CERTAIN that you use the files for your device but try those steps and instructions, they should work the same for your device.
If the instructions in post #6 don't work, try reading further in the thread , there may be more solutions discussed.
https://forum.xda-developers.com/showthread.php?t=2302144
@MTS0, I forgot to add the link, sorry, hope it helps.
Sent from my SM-S903VL using Tapatalk

Thanks for your reply, but I can't go into recovery mode. Boot loop and download mode is the only thing it still does. I can't even turn the device off, need to wait for the battery to empty.
I was checking out that thread, they are talking about flashing the PIT and param. Do I have any chance with that? I just need to acces my data....
Thanks

GT-N8010 - Firmware Upgrade

Hey there!
Just ran into some troubles with my GT-N8010. I had been using stock on it for quite awhile, but have been noticing that many of the newer apps do not work with JB. I had rooted and used my Asus Transformer before, figured that it was probably about time to get some more life out of the Note 10.1.
My first option was to upgrade from JB to KitKat. Unfortunately there is not an official update in Canada, but using Odin I should have been able to upgrade it. This is where the issues came. First, it failed twice. I restarted the computer, and tried it once more. Success! It was downloading. It took a few moments, but eventually it failed as well. The download stopped and I was left looking at my tablet having 3/4 of the install complete. I left it for awhile, hoping that it would restart itself or reload. Nothing happened, and I had to restart the tablet.
Situation now: I am stuck at the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
First thing I tried was getting to the download screen, so I have that. I figured I could just flash it back to the offical JB from Canada, but now it's like the computer won't recognize the device. Even unplugging and plugging the USB back in does not even give me the PC Recognizing sound. I moved to a laptop, and it could read the device, but once I installed Samsung USB and Keis, it stopped. Odin doesn't recognize it and I am not sure where to go from here.
Is using the SD card an option? Can I somehow force the computer to read the tablet?
I have looked through the forums, but didn't really see much in the way of help.
I hope to hear from you guys! Thanks in advanced! If I need to provide more information, please ask.

Is using the SD card an option>>> NOT for stock custom rom only .

I don't mind installing a custom rom at this point. If it is still an option at this point the I don't mind at all. If there is anyway you could point me towards that option, I will definitely give it a shot.

The development threads.
You will need to flash a custom recovery tar through Odin .
https://forum.xda-developers.com/showthread.php?t=2490954

Part of the problem is that the Odin, even my PC, are not recognizing the the Tablet is connected through my USB. So I cannot flash anything right now.

I figured it out. It was all because of my cord. I went out and got a new one, flashed 4.4.2 easily. Hope that helps everyone who has issues as I did.

elevenstewart said:
I figured it out. It was all because of my cord. I went out and got a new one, flashed 4.4.2 easily. Hope that helps everyone who has issues as I did.
Click to expand...
Click to collapse
Hi, I've read your posts. Helpful.
I'm in the situation of having tried to flash a custom recovery, to then flash a custom ROM.
Started Odin, began to flash, then Odin showed failed.
Now the n8000 no longer starts, just hangs after the Samsung logo/music.
I do have two different cords, so will try that later.
Question, did you end up flashing a custom ROM later, and if so, which one?
Thanks.
Sent from my SM-N920C using Tapatalk

I have a Samsung Galaxy GT-N8010 (UK version), Android 4.1..2 - i need to get this up to KitKat 4.4.2 as BT Sport app won't run on below v4 - help?

Search this forum its well answered.
Or
Sammobile.
Updato.
Two firmware site