Related
i tried rooting my tab (GT-P3110) and in Odin it didn't showed pass, my tab rebooted and it showed an error saying "Firmware Upgrade encountered an issue..." i tried putting it in download mode to flash a new rom but it's stuck in that screen, i also tried putting it in recovery mode but it doesn't work either, is my tab totally bricked? can it still be fixed? i can't enter download mode or recovery mode, every time i turn it off it just goes back to the same screen and when i put the charger in, it still shows the same screen, help me please...thank you!
dhrexler said:
i tried rooting my tab (GT-P3110) and in Odin it didn't showed pass, my tab rebooted and it showed an error saying "Firmware Upgrade encountered an issue..." i tried putting it in download mode to flash a new rom but it's stuck in that screen, i also tried putting it in recovery mode but it doesn't work either, is my tab totally bricked? can it still be fixed? i can't enter download mode or recovery mode, every time i turn it off it just goes back to the same screen and when i put the charger in, it still shows the same screen, help me please...thank you!
Click to expand...
Click to collapse
I have the same problem, can some1 help?
I try using kies to fix the problem but the gt-p3110 is not supported when u go to Firmware upgrade and initilazation, put in the serial number from the back of your battery, then the tablet model and when u click ok is telling you that your model is not supported.
Can some1 tell me how to do it using Odin , even with complete wipe, or stock ROM.
Thx and please reply
"Firmware Upgrade encountered an issue..." = that´s the black screen of death. Download mode is enabled in this situation automaticly, no need to boot into downloadmode.
Uninstall Kies first! Maybe that´s why Odin failed! Maybe some Kies prozess running in the background.
Start Odin as Administrator,
Connect your tabelt to your PC (yes, with black screen of death!) - Odin will show "Added"
Now flash a Stockrom for your device
Safed your Tab
i did that with odin, untill it show'd pass but when i turn it on is the same
i loaded the file in the pda section,auto reboot and f.reset time boxes were checked
i used this http://www.hotfile.com/dl/182607797/b61e3af/P3110XXCLK7_P3110OXACLK7_BTU.zip.html from here http://forum.xda-developers.com/showthread.php?p=35095146 , the uk link
if u have a working method can you please tell me and live a link and how to do it?
thanks and please reply
maybe bad download? redownload a rom for your deivce e.g. from www.samsung-updates.com
Just did that , but is the same, I use Odin 3.07
Any more ideas?
Thanks
I notice this thread has been dead for some time. However, I am also in search of a possible solution to this as a colleague of mine passed one of these tablets on to me in the hope I could get some use out of it. It is in the same state as the previous posters claim, 'firmware encountered a problem.....'. Obviously I'm in a different situation as I did not buy this thing with my own money, not will I lose out if it is beyond repair. But I'm interested to solve this problem none the less.
So, so far I have attempted to flash a philztouch recovery using Odin which was unsuccessful and I have also tried to flash several compatible ROMs. All of which have failed, Odin confirming each time that the attempts were unsuccessful. I have read that the tablet in this state auto unlocks the bootloader, so I have ruled out that as a sticking point. I have read that flashing ROMs potentially won't work either as the corruption of the firmware is seated too deeply for this to have any effect. I know a possible solution is to try flash a new kernel as this goes a lot deeper, but this can be risky, however, like I mentioned above is not an issue for me as I have nothing to lose. Does anyone have any pointers on how to flash a new kernel? Surely there is a way to remove the corrupted firmware completely? I have to admit this is beyond the realm of anything I have used Odin for in the past. Also, I am more than aware some of my understanding may be incorrect so feel free to correct me. Any help would be greatly appreciated, even if it's just to point me in the right direction or towards some reference material which could shed some light on this particular problem.
Thanks in advance.
Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.
I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:
heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img
However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.
Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.
I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?
Thanks for any help you can advise on ....
vax1170 said:
Hello all,
Short story, wife had the 4.3 OTA nag popup, accidentally hit 'ok' and pulled battery before unit booted.
I thought maybe I could avoid the 4.3 OTA by flashing CWM via heimdall. I followed the CM directions for d2vzw at wiki.cyanogenmod.org/w/Install_CM_for_d2vzw, basically I did the following:
heimdall flash --ABOOT aboot.mbn --no-reboot
heimdall flash --BOOT boot.img --no-reboot
heimdall flash --RECOVERY recovery-clockwork-6.0.4.5-d2vzw.img
However when I try to boot into recovery mode, I get the android character with spinning globe. I only saw the picture long enough to pull the battery.
Any suggestions on this on? It looks like the confirmation for OTA sets something, and it appears that whatever I did above either was wrong, didn't happen properly, or is ignored at this point. If I boot back into download mode I still see custom binary no, and current/system binary official.
I would like to get this to CWM and CM 10.2, but suspect it is too late ... can anyone tell me how to work around this, or should I just bite the bullet and reboot to see if the OTA updates at this point?
Thanks for any help you can advise on ....
Click to expand...
Click to collapse
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
buhohitr said:
Boot into download mode (vol down + Home + power button). Do you see this? If you see the last 2 lines you are on 4.3
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
Click to expand...
Click to collapse
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:
ODIN MODE
product name: SCH-I535
custom binary download: no
current binary: Samsung official
System status: Official
QUALCOMM secureboot ENABLE
And nothing else after that (just the green antroid graphic and 'downlaoding....')
Thank you for the fast response
vax1170 said:
No not quite. I don't see the last few lines. My eyes are a bit old but what I see is only:
ODIN MODE
product name: SCH-I535
custom binary download: no
current binary: Samsung official
System status: Official
QUALCOMM secureboot ENABLE
And nothing else after that (just the green antroid graphic and 'downlaoding....')
Thank you for the fast response
Click to expand...
Click to collapse
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.
buhohitr said:
Seems like the 4.3 didn't make it. You can boot up the phone and re check..Once phone is up just turn off wifi and 4g to prevent the OTA.
Click to expand...
Click to collapse
Sorry I wasn't clear ....
I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.
It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.
After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.
If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.
Let me know what you think .... thanks!
vax1170 said:
Sorry I wasn't clear ....
I believe the phone already had the OTA software downloaded and staged for install. It was popping up that nag screen that asks to run the update. My wife pressed 'OK' on that and as the phone shutdown and brought up the 'samsung' splash screen, the battery was pulled.
It was after this that I attempted to follow the CM directions to flash the older bootloader and CWM. However I don't think it was successful.
After running the procedure, I attempt to boot into recovery. I am expecting to see the usual CWM menu, however I don't. I get the android with the spinning globe in the belly. I am thinking, the flash with CWM didn't take, and the OTA is now attempting to install.
If possible I would like to flash CWM and then load up CM 10.2 from an internal SD card I've prepared.
Let me know what you think .... thanks!
Click to expand...
Click to collapse
It's possible that the 4.3 bootloader already flashed and it's in the process of flashing the rom when you pulled the battery. In any case, if the software is half done you phone won't boot, and if you attempt to flash the old rom, you will brick your phone if the bootloader already locked. So you need to turn it on to see where you at or you can take a chance and try to Odin old stock rom, again if the bootloader already locked you will brick your phone and if not then you will be back to the older version. I would turn it on and see.
Thanks.
Is there anyway to tell for sure if the bootloader is the new one?
Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.
Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there? I already did a print-pit on all 3 phones, but from what little I know it seems like the only differences are likely due to the memory sizes. 32 vs 16.
If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,
vax1170 said:
Thanks.
Is there anyway to tell for sure if the bootloader is the new one?
Fortunately I have 2 other S3's I can compare against. One is a 32g S3 with OTA 4.3. The other is a 32g S3 I picked up preinstalled with CWM/CM10. The hosed up phone is a 16g S3.
Can I pull something down from these phones with heimdall to check/compare if the 4.3 bootloader is there?
If there is no way to tell, then perhaps I'll reboot it and see..... thanks for the help,
Click to expand...
Click to collapse
If you don't see the last 2 lines like I mentioned above, it should be the old bootloader...since the timing you pull the battery, no one really know what state it's in unless you boot it up.
Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?
The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.
Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....
vax1170 said:
Am I correct in assuming that the 3 heimdall statements I executed above should have resulted in CWM coming up when I do the up-home-power?
The CM instructions for d2vzw are not clear if you really need to let heimdall reboot the phone between each step. I was trying to avoid a full reboot as I expected the OTA to take over if I did.
Perhaps I should reboot it; if it boots up into anything, at least I can sell it ....
Click to expand...
Click to collapse
Yes, you can boot up now and see what's going on...
So it looks like it is bricked to some degree. What might you advise to undo this?
When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.
If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.
If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.
What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.
Thanks
vax1170 said:
So it looks like it is bricked to some degree. What might you advise to undo this?
When I power the phone up I see the usual Samsung galaxy logo, then the screen goes black with pulsing blue LED.
If I boot into recovery, I see the android with spinning globe for about 60sec, then the dead android with red triangle, and phone resets.
If I boot into download mode, it still comes up with the same messages I indicated above. It looks like the boot loader is not new. I can connect with heimdall and print-pit, so something is still alive here.
What is your best advice here? At this point, I don't think I care if it is put back to stock 4.1.2 or upgraded; booting and working with anything is fine.
Thanks
Click to expand...
Click to collapse
I would try to use Odin and flash MF1 full firmware here http://www.androidfilehost.com/?fid=23134718111254196
Thanks for confirming ... I was poking around the forums and figured I should probably try the procedure to completely reflash my device back to stock. I'll try that later tonight. Thanks again ... crossing my fingers
[RESOLVED]
Looks like flashing the 4.1.2 stock image worked, device boots now!
There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.
On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.
Some summary details to anyone who is interested:
- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.
- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.
- On reboot, the phone has pulsing blue LED; bricked
- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.
If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.
Thanks for the help!
vax1170 said:
Looks like flashing the 4.1.2 stock image worked, device boots now!
There was somewhat unexpected behavior however, I don’t know if this is interesting or not. I followed the usual directions to use Odin to flash the full MF1 stock rom; this took about 8-10 min to complete.
On reboot, I saw the tiny blue message at top, and the phone appeared to start in recovery mode, at which point the android graphic with spinning belly globe came up. The progress bar went the full length (no error) and phone rebooted. Phone seemed to reboot fine with typical Samsung and LTE logos. When the phone came up, I was surprised. After unlocking the screen, I got a pop-up indicating that the phone update failed. I then found that all my old data was still available; wi-fi passwords, apps, account syncing, etc. everything. I was expecting the device to be wiped clean with the flash - but maybe I misunderstood. Download mode still seems to report the same messages as before (so it looks like it hasn’t been locked). Needless to say, I hit airplane mode and disabled WiFi, and the phone is not activated, so there is no ability for it to pull the OTA again. If it makes any difference, when I flashed this phone it had no SIM card, and it also had a new 1gb SD card I left in there which was populated with CWM and CM images.
Some summary details to anyone who is interested:
- Phone was running stock 4.1.2 MF1, it received the 4.3 OTA package and was popping up the request to update. Accidentally hit ‘ok’ and phone started reboot sequence to apply update. On phone startup, battery was pulled to prevent update.
- Attempted to run the CM 10.2 d2vzw procedure to flash older bootloader and CWM using heimdall. Transferred just fine, but this didn’t appear to work. Upon entering recovery mode, the android graphic comes up and attempts to do something, but fails.
- On reboot, the phone has pulsing blue LED; bricked
- ODIN’ed the stock 4.1.2 image back, and phone is un-bricked, pops up message on failed update, and all previous data is retained.
If there is any other information from this that could be useful to developers let me know. The phone will not be put back into service for some time, and I can transfer off or adb anything someone might find interesting. Just let me know and I'll try to retried and post here.
Thanks for the help!
Click to expand...
Click to collapse
You're a lucky son of .....lol.
OK, Ive been without my note for a whole day and been researching wht to do nonstop
What happened to me was that, since i had updated to official kitkat, i soon developed a taste for lollipop, and went on to try out different ROMs and finally settled on to crDroid
So it was one of those days where everything was going well until the note stopped opening apps for like a minute then showd a black screen and then all of a sudden restarted
Since this was a Sammy i thought it would get back up again.... But no, even a 5 minute didnt wake this beast up, it remained stuck at the boot logo, i.e, Samasung Galaxy Note 10.1
Im like ok ill go on do a factory reset and wipe cache and all, upon trying to accesss the recovery after the boot logo the recovery kinda opens then gets back at boot logo, a black screen shows up then turns on to be a full brightness black screen for a sec then goes back
I can access the download mode and can odin things but they fail every single time.
I have tried to odin a recovery and a stock recovery so far and they show a nand write error
i also have tried to PIT but they get stuck at get PIT for mapping
I have also tried all versions of odin tried changing a USB Port and the wire with no success
So is there any hope for my NOTE??
Please i need help its urgent
Osama Abedin said:
OK, Ive been without my note for a whole day and been researching wht to do nonstop
What happened to me was that, since i had updated to official kitkat, i soon developed a taste for lollipop, and went on to try out different ROMs and finally settled on to crDroid
So it was one of those days where everything was going well until the note stopped opening apps for like a minute then showd a black screen and then all of a sudden restarted
Since this was a Sammy i thought it would get back up again.... But no, even a 5 minute didnt wake this beast up, it remained stuck at the boot logo, i.e, Samasung Galaxy Note 10.1
Im like ok ill go on do a factory reset and wipe cache and all, upon trying to accesss the recovery after the boot logo the recovery kinda opens then gets back at boot logo, a black screen shows up then turns on to be a full brightness black screen for a sec then goes back
I can access the download mode and can odin things but they fail every single time.
I have tried to odin a recovery and a stock recovery so far and they show a nand write error
i also have tried to PIT but they get stuck at get PIT for mapping
I have also tried all versions of odin tried changing a USB Port and the wire with no success
So is there any hope for my NOTE??
Please i need help its urgent
Click to expand...
Click to collapse
is it rooted ?
i have the same problem from 2 months and i am finally got that i must replace the motherboard
Sounds like its written its last, flash is dead.
Since you are able to enter in download mode there is hope. Trying to flash recovery which doesn't match the firmware version will always fail. So, try flashing some of the base firmwares which will return everything to stock. I was in your situation few months ago and managed to flash Android Revolution HD 4.4.2 after first flashing stock firmware via odin. I got my 4.4.2 base firmware from "sammobile.com", firmware section (sorry i don't have enough posts for using links).
I remember i tried flashing TWRP for GT N8000 and i also tried Philz then CWM all for GT N8000
I also tried flashing base rom but it gives NAND write fail
Nand write fail can mean damaged PIT or the actual nand memory is damaged and needs a new motherboard .
flash with pit file
found these pit files for the device.
you can flash the pit file for GT-N8000 in odin
don't forget to repartition, it's a very delicate situation, you don't want to mess it up, before going to this, you should confirm if the size are same. you wont like to flash a 16gb to 32gb partition.
http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
good luck and please share your fix if its done
billysam said:
found these pit files for the device.
you can flash the pit file for GT-N8000 in odin
don't forget to repartition, it's a very delicate situation, you don't want to mess it up, before going to this, you should confirm if the size are same. you wont like to flash a 16gb to 32gb partition.
http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
good luck and please share your fix if its done
Click to expand...
Click to collapse
thx for telling me... im trying out a new wire so will try it out nxt week
Sorry for the late reply tho
Osama Abedin said:
thx for telling me... im trying out a new wire so will try it out nxt week
Sorry for the late reply tho
Click to expand...
Click to collapse
same problem for me, this did not work, still write error
I have a similar problem. Everything is stuck. I am tryingo to go back to stock, but if I try to connect (via Odin, Heimdall, fastbot or adb sideload) i can't.
Is there any advice?
Thanks
nope not yet
I'm early ???
So it turned out that my AMAZING tablet had its storage device corrupted... I. E I exceeded the read write count
Similar problem Bricked N8005
I bought my N8005 (variant of N8000 but phone is disabled just data 3G is available) in 2012. I rooted it once and used custom rom for a while but last year installed official stock ROM again. Yesterday I started a game called "zombidle" (possibly this is an unnecessary info) and tablet restarted itself but stuck on "samsung" logo.
I tried to enter recovery mode but it always restarted and cannot enter recovery mode.
Tried to install different versions of CWM, Philz and TWRP recovery using odin but it always FAILed when NANDwrite started. Tried odin 1.85, 1.87, 3.07, 3.09, 3.12 but all same.
I tried to install same stock ROM but always FAILed.
Then I tried to install a custom rom but it failed too.
I read about bad pit files. Searched internet and found some pit files but nothing changed, FAILed at same point.
Did I finished all solutions?
Should I take it to the doctor?
Any sugesstions?
Thanks in advance.
Edit: Today I took it to the Samsung doctors. They said that; this is a mainboard issue and mainboard needs to be changed. That will be over 400TL (TL=Turkish Lira). Device is still in markets and new N8005 is 1300TL (i think this is also expensive. Because new Samsung Galaxy Tab S2 T817 32GB 9.7" is 1900TL in my country).
Does it worth to fix? Any opinions? Can I fix it myself somehow?
Nand write fail probable defunct memory.
Hi all..or anyone out there
I have had the seemingly strange bootloop problem on my stock note N8010...which stuck on the dreaded "samsung galaxy note 10.1" and only has odin feature working. (and no factory reset options because I think the poor old tab is crammed to bursting with apps, files and cache and so had a meltdown) poor thing.
so anyway I check these sites of techie wonder and wisdom and followed every logical option..starting with the simple ones
first ran power down and tried to boot up (x3) with no joy, then take apart the tablet to disconnect / reconnect the battery and boot up (x3) still no change.
So went and got the firmware from samwares (both jelly bean and kitkat) to then flash through odin....tried and failed first because of dodgy cable, but the then got a new one...and joy of joys (at first) odin recognised my tab and the firmware flashed across with pass..but then auto rebooted straight back into the dreaded samsung 10.1 again....so tried different versions of odins... and tried other global n8010 firmware...but funnily and frustratingly then all fully download and pass in odin (and the andoid logo and green download status bar on the tablet seems to shown that downloading is and has fully taken place.... but the darn thing still wont boot up past the samsung galaxy note 10.1
Sadly coming to the ends of my tether (of so many nearly there false hopes, high and lows) and very little cash to send it to the Sami tech bods doesnt help matter....I then read and tried the (supposed) last resort pit file/firmware option...first with kitkat (as apparently that worked for someone somewhere) and then tried with jelly bean..again each time itAlways passes in odin.... but auto reboots into the dreaded bootloop logo .... to haunt and torment me.. Aaaaagh!!!!.....I would not mind if it said action failed (for once) like some others seem to experiencet...but it always passes in ODIN????
So.....have come to the semi ignorant conclusion it is either the bootloader section of the tablet or the original software that is messed up or some internal hardware component has a fault.
but was wondering if there is anthing left to try...or would it potentially be possible or worth trying to root a tablet in this condition?
As although I have not ventured into the wild worlds of rooting.....I am now pretty confident of messing with this tablets mind..and have little to lose...so any further ideas and help would be great.
Exact same here. Never flashed, totally stock N8010. My wife hadn't used it for a couple of weeks. So she grabs it again and it was off. booted to nothing but the boot logo. Nothing worked except Download mode.
Flashing stock roms has Odin reporting success, but it still won't boot up. Trying re-Partition does give a fail as soon as I press start.
And we aren't alone. It appears there are quite a few of these cases. I have no idea how to solve this.
I have done a bit of rom flashing on my old galaxy S (the first one) and bootloaders and such usually were included in a ROM. Rooting was done with Recovery or an app and I think it was also possible with adb, IIRC (it's been a while).
It's my wife's Note and she's starting to scope out mini iPads...
Same problem with GT-N8010
I am also having the same problem.
I tried to upload a new ROM via ODIN. All was successful from the ODIN app (PASSED). but stuck on the boot screen. Power and Vol up does not work (it appears to but then crashes out to the boot screen again) so no way to do a hard factory reset.
Volume down/power does work and allows you to get to Odin mode. but as above, uploading a new ROM does not seem to work.
This is an un-rooted GT-N8010 with the stock ROM when I purchased it back in 2013 I believe.
Come on guys, give us some ideas.
Thanks
Gene
Sounds like wrong model firmware flashed as that's the usual bootloop problem .
Try Odin firmware flash wait to passed then remove battery for a short while and replace and try recovery mode .
In my case there is no incompatible firmware issue... The tablet just stopped working one morning and that was that.
Can't comment on the other posters though.
Sent from my GT-I9305 using XDA Free mobile app
Gene_uk said:
In my case there is no incompatible firmware issue... The tablet just stopped working one morning and that was that.
Can't comment on the other posters though.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
My wife's the same. Never done anything to it. No idea how to remove the battery. I let the battery run down once, then recharged it, made no difference.
That was before trying to flash the new firmware. My Note says N8010 on the back, it says so in the download mode. I got a firmware from SamMobile for the N8010. Don't know what else I can do.
Widdly said:
My wife's the same. Never done anything to it. No idea how to remove the battery. I let the battery run down once, then recharged it, made no difference.
That was before trying to flash the new firmware. My Note says N8010 on the back, it says so in the download mode. I got a firmware from SamMobile for the N8010. Don't know what else I can do.
Click to expand...
Click to collapse
Having same problem here ... tried flashing different firmwares along with PIT file - still no luck ..
stuck on samsung galaxy note screen .. cannot get recovery mode
Any help guys?
Hi there, I'm pretty frustrated because all of the sudden my S6 (G920F) got a bootloop and I already spend too many hours in research to get this fixed without getting any further. The phone just worked fine before and I didn't change anything (stuck rom and kernel) so I don't know how this could happen. Now it just shows the Samsung boot logo until the battery dies. If I plug in the power cord it shows the charging logo but doesn't show any progress in charging. Now the extra challenge is that the home button doesn't work to get in recovery mode. So I ordered a USB-jig. Now I get into download mode. Via odin I successfully flashed a new stock rom from sammobile. Still the same problem. I tried to flash twrp via odin but still didn't change anything, I still can't get into recovery.
Since I didn't enable developer mode I can't get an adb connection running with my PC.
Now I heard that maybe the kernel needs to be fixed. So after some research I found this UniKernel that can be flashed via odin but they say it only works on Lollipop. I was so frustrated that I just tried to install it anyway but still. Nothing changed.
So now I'm kind of exhausted because I don't even know if I'm going in the right direction. Can anyone give me some advice what to try next? Why can't I get into recovery? Where can I get a kernel to flash via odin? I would appreciate any advice! Thanks in advance for taking your time!