Dear all.
First of all, thanks for your attention, I really appreciate.
I have a GNote 10.1 Wi-Fi version (N8013) with stock Android 4.1.
My S-Pen was getting me crazy, because I was not able to use it correctly on the edges of the device. I tried an app that supposed to reset the alignment, but I did not work, so I googled and found that the only way to fix it was "factory reseting" the tablet.
So, I installed the TeamWin recovery and backed up my data. After that I hit the button "reboot". But before rebooting, the recovery screen "told me" that I was not rooted and "asked" if I would like to install SuperSU to get root access. I checked YES and rebooted.
After that I got stucked at the "Samsung Galaxy Note" screen (see attached file).
I've tried to switch off the note, but the screen goes off for one second and it lights up again at the same screen.
If I plug the USB cable and try to switch it off, the note goes to the battery charging screen. If I remove the USB and push the power button again, the tablet gets back to the "Samsung Galaxy Note" screen.
Odin seems to "connect" with the tablet.
I can enter both the download mode and the recovery mode (not the teamwin recovery).
Attached pictures of what I get.
Any sugestions?
Thanks!!!
Everything is ok now
Dear all,
Hope I can help you if you have a problem similar to mine.
I remembered that a PC with no OS stops on some screen, but everything else works, just as what was happening with my note.
I tought that I might have wiped more things than I should, so, the only thing I had to do was to restore the backup that I had.
To do this I should reinstall the TWRP and the only way was via Odin.
Solved the problem this way:
1. Downloaded the Odin (http://techbeasts.com/2013/08/08/download-odin-pc-latest-version-v-3-07/)
2. Downloaded the TWRP file (http://techerrata.com/get/twrp2/p4noterf/openrecovery-twrp-2.6.1.0-p4notewifi.tar)
3. Connected the Galaxy Note to my PC using the USB cable
4. Entered the "download mode"
5. Loaded the file from step 2 into the tablet using Odin
6. Rebooted the tablet
7. Entered the recovery mode (TWRP was working)
8. Restored the backup that I had
9. Rebooted again
Did the dance of victory!!!
I am so glad to have my device back.
Regards
how to access recovery mode? mine can't access recovery mode with power+volume up :crying:
rizalabd said:
how to access recovery mode? mine can't access recovery mode with power+volume up :crying:
Click to expand...
Click to collapse
Hi all
mine neither.. followed your steps with odin but still stuck in start screen (Samsung Galaxy Note 10.1). By the way mine is the 8010. I tried almost everything. Cant even load the recovery mode!.... And Have no backup either.
PLease someone help me...
Thank you in advance
I have an SM-P600
My Note 10.1 2014 Edition is stuck on the tablet title screen, not sure if its in reboot mode it returns to this screen if I try to shut it off... basically Its frozen, and when I try to shut it off it goes away a few seconds and comes back. This happened after I rooted with KingRoot, and tried to Flash a ROM, Im a complete Noob and should have done my homework... but I didnt. I see everyone suggesting odin and going into download mode... I can get to download mode but I am using a macbook pro, and there are very little options to use odin, I tried Jodin3... and Heimdall... no luck...
PLEASE HELP !
HELP stuck on Samsung screen
I didn't any root or install a different firmware to mine.
But after charging it I removed the cable and it rebooted and got stuck on the Samsung screen. I can only access to Download mode. I didn't have any Recovery mode installed, and now I can't install one successfully via Odin...
I tried to install a new firmware... a recovery mode... nothing is working...
Please I need HELP...
@ agelcer: Was your tablet rooted?
Hello. I havea similar problem with my note 2 phone. It will not get past the
samsung screen. My cpu knowledge is very limited. Are you open to accepting payment for attempting to fix my cell phone? All I want is the pictures off of it if that is all you can do to it. Pleass email me at [email protected] if you or anyone you know can help. Thanks....Jay
Same thing is happening to mine. I tried Odin but after the download the srceen goes black and then comes back to the Samsung Galaxy Note 10.1 screen.
Hello folks.
Same problem here with a n8000.
It had the stock unrooted rom probably JellyBean.
Can only access Download Mode, nothing else.
I get connection to Odin, tried to flash original firmware, 4 file firmware, re-partition with pit file, flash a custom recovery, all seem to pass through but nothing changes, still stuck on 'Samsung Galaxy Note 10.1' screen, never moves on to boot animation and still can't access Recovery Mode.
However, something else I triy with Odin and it FAILS is ticking 'Nand Erase All'. It won't let me erase nand.
Could this mean some kind of memory corruption?
Does it have anything to do with EMMC?
If it does, is there a possible way to fix without replacing the hardware?
What else can I try before giving up?
It would be nice if other users who report this problem attempt to Nand Erase All and see if it also FAILS..
Thanks alot and sorry for the long post.
Edit: after posting I found this which is PROBABLY THE SOLUTION for me.
And here is another topic on this issue.
did you find the solution?
giba_fernando said:
Hello folks.
Same problem here with a n8000.
It had the stock unrooted rom probably JellyBean.
Can only access Download Mode, nothing else.
I get connection to Odin, tried to flash original firmware, 4 file firmware, re-partition with pit file, flash a custom recovery, all seem to pass through but nothing changes, still stuck on 'Samsung Galaxy Note 10.1' screen, never moves on to boot animation and still can't access Recovery Mode.
However, something else I triy with Odin and it FAILS is ticking 'Nand Erase All'. It won't let me erase nand.
Could this mean some kind of memory corruption?
Does it have anything to do with EMMC?
If it does, is there a possible way to fix without replacing the hardware?
What else can I try before giving up?
It would be nice if other users who report this problem attempt to Nand Erase All and see if it also FAILS..
Thanks alot and sorry for the long post.
Edit: after posting I found this which is PROBABLY THE SOLUTION for me.
And here is another topic on this issue.
Click to expand...
Click to collapse
i am looking for any solution since two years without any benefit. did you find any?
chozex said:
i am looking for any solution since two years without any benefit. did you find any?
Click to expand...
Click to collapse
I assumed from my searches the solution would be JTAG or replace the EMMC.
Since I don't have the resources for any of those, I just abandoned it to the dust and rust..
bootloader
Is this after the boot loader is updated?
osirisx69 said:
Is this after the boot loader is updated?
Click to expand...
Click to collapse
I'm not very clear about bootloader upgrading, but I guess it was included in the 4 file firmware I tried flashing and it said 'success' but nothing changed..
I think it ain't just a softbrick since I can't erase nand..
What's your background, osirisx69?
This happened to ours as well just today. Unplugged it rebooted it and it's stuck. Can only access the Odin mode.
Sent from my XT1254 using Tapatalk
i got same issue at last 4 months
just try reset then got same issue.
Same problem for 3 months. Guys have anyone tried jtag flashing firmware as in this post which was provided earlier?
So a while ago, I rooted my nexus 6 phone and along with it TWRP. So, today, I tried unrooting it, and in the process of doing this, I didn't notice something failed and after this, I locked the OEM, so now I can't unlock it. After doing this, my phone starts to boot, and the image for TeamWin Just keeps flashing, and when I try to go to recovery mode from the fastboot, it just tries to go to teamwin and the image for it just keep flashing as well. I have no idea what to do and I am really panicking. Could anyone please direct me to something that could fix this? I am limited in my knowledge involving fastboot and flashing custom ROM's so I need specific steps as to what to do. I really need help.
*Also, when I mean the image for teamwin keeps flashing, I mean the literal picture of the teamwin bootup keeps flashing on screen and nothing happens.
If you didn't select the lock bootloader option in Developer Options, then you should still be able to do the fastboot oem unlock. If you have, then I think you are out of luck...
So my friend was trying to get some stupid game to work on my phone that my phone didn't support, so he tried replacing the build.prop for my Pantech Flex with one for the Galaxy s3. Which needless to say bricked it.
I can start up the phone, and I assume it starts up normally and goes to the lock screen. But everything after the pantech logo is black screen.
Here is what I've tried:
1. Pulling my current build.prop and editing it, then pushing it back with ADB. Pulling it works, but when I push it, nothing seems to happen. It says "Success" but when rebooting the device, my phone is still ****ed up. And when I pull the build.prop back again, it's the one for the Galaxy s3 and not the one I just pushed.
I read that the reason this is happening is because ADB doesn't have root permissions. Not sure if thats true though, as I obviously have rooted my phone.
2. Booting the device into recovery. For a while now, trying to boot into recovery leaves me stuck on the Pantech logo. I think this may be due to me flashing a recovery that wasn't for my device a while back. So I can't get into my recovery to factory reset it.
3. Booting into fastboot mode. The Flex is a strange creature, so there is no standard bootloader apparently so when using "adb reboot bootloader" it reboots into fastboot instead of a bootloader. Meaning on the screen is just white text saying "FAST BOOT mode" and adb disconnects, and fastboot devices sees the device now.
Trouble here is, I have the stock recovery for the Flex. But when I use Fastboot boot recovery.img or Fastboot flash recovery recovery.img or fastboot wipe data or anything in fastboot really, I get a "Not support!!" error. Which I assume means my phone is a piece of **** and can't be used with fastboot.
So now I'm at my wits end and don't know what else to do. I am dead broke and need my phone for work.
Is there anyway I can fix the build.prop or factory reset my phone?
Fukesh said:
So my friend was trying to get some stupid game to work on my phone that my phone didn't support, so he tried replacing the build.prop for my Pantech Flex with one for the Galaxy s3. Which needless to say bricked it.
I can start up the phone, and I assume it starts up normally and goes to the lock screen. But everything after the pantech logo is black screen.
Here is what I've tried:
1. Pulling my current build.prop and editing it, then pushing it back with ADB. Pulling it works, but when I push it, nothing seems to happen. It says "Success" but when rebooting the device, my phone is still ****ed up. And when I pull the build.prop back again, it's the one for the Galaxy s3 and not the one I just pushed.
I read that the reason this is happening is because ADB doesn't have root permissions. Not sure if thats true though, as I obviously have rooted my phone.
2. Booting the device into recovery. For a while now, trying to boot into recovery leaves me stuck on the Pantech logo. I think this may be due to me flashing a recovery that wasn't for my device a while back. So I can't get into my recovery to factory reset it.
3. Booting into fastboot mode. The Flex is a strange creature, so there is no standard bootloader apparently so when using "adb reboot bootloader" it reboots into fastboot instead of a bootloader. Meaning on the screen is just white text saying "FAST BOOT mode" and adb disconnects, and fastboot devices sees the device now.
Trouble here is, I have the stock recovery for the Flex. But when I use Fastboot boot recovery.img or Fastboot flash recovery recovery.img or fastboot wipe data or anything in fastboot really, I get a "Not support!!" error. Which I assume means my phone is a piece of **** and can't be used with fastboot.
So now I'm at my wits end and don't know what else to do. I am dead broke and need my phone for work.
Is there anyway I can fix the build.prop or factory reset my phone?
Click to expand...
Click to collapse
Also, maybe there is a way to set up a VNC server of some sort to use the phone from the computer??
So I recently got a Nexus 9. I think it was affected by the battery issues with android nougat. I rooted and used greenify and got much better battery life but decided I wanted to unroot and see if over a couple days the battery life would have gotten better. So I connected to my computer and stupidly sent the "fastboot flashing lock" command and now my Nexus is stuck in a boot loop because of TWRP. I knew that locking the bootloader would initiate a factory reset but didn't take into account that TWRP may affect that so now I can not use my Nexus. The device says it is a developer edition and not intended for personal use and I don't I know what to try. Just letting everyone know I only tried to sideloading and flash. I appreciate everyone who takes the time to read this and try to help.
Have you tried following instructions from google to flash a factory image ?
https://developers.google.com/android/images
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
AUSTIZ1997 said:
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
Click to expand...
Click to collapse
Did you try booting your nexus to fast boot and execute fastboot oem unlock?
I have​, it just send me an error message
Update, I was able to finally get into the custom recovery and tried to flash the stock recovery and now it just boots into fastboot mode but I got rid of the custom recovery (as far as I know) and the boot screen that said the tablet was a developer device
Same problem here in May 2017, the OTA update prompted by Google sent the device into a bootloop. As the Bootloader was locked and there was no way to change to USB debugging mode it wasn't possible to use Recovery mode or to flash an OTA. Wiped data cache, tried all options in HBoot menu, tried flashing OTAs and full block OTA didn't work either. Just stuck in bootloop.
Repair shop encountered same problems so they then suspected the logic board. They heated it up to reflow the solder and success! Logic board may fail again through dry joint but I believe this risk can't be avoided by switching manufacturer as they all use the same component-to-board soldering practice.
Hi All,
I am currently in the phone repair business. Well i buy as much as i can fix and sell on. Its all fun. I have a very nice one currently and looking to see if anyone has ideas. All i want to do is boot to recovery that is my current goal.
So phone clearly has corrupt installation, likely a flash Rom or update gone wrong. It boots to Huawei logo then reboots and that's all it does. Tried de-powering and all sorts including removing battery cable but to no luck.
There is no recovery mode
No download mode
Can get to fastboot but unable to run commands it seems due to FRP lock. I am not worried about FRP lock at this time, i only want recovery back.
Tried:-
All flash commands and all fail
Any attempt to get to receovery or download mode fails
All three buttons to force SD card boot fails
Currently trying to boot using SD card but seems i need to change boot devices from within recovery. Well it has no recovery mode so no luck there.
So it is pretty much a brick at this point and could be a write off but before I give up does anyone have any other ideas? maybe a FB command i can run with FRP lock and bootloader lock on?
Thanks
Karl