i upgraded my note N8000 via odin mobile pro with success and everything was smooth and the root was not intact
I tried to flash a theme via mobile odin but was not success, but note was still ok
then 2 days later I tried to enter the recovery mode , i found the note stuck on samsung boot screen and dose not reboot, I can enter download mode but can not enter recovery mode to reflash even the stock rom
what to do?
should i reflash the CWM as 1st time? then reflash the root if i found it is gone?
or i have to reflash the stock rom first via odin desk top since i can not reboot the note? problem is the stock rom is on the note and do not have it on PC
the note now is on Samsung boot screen, how to turn it off since note can not remove the battery?
EDIT 1::good:
Flashed a stock recovery via odin desk top, and rebooted
Note is back alive , no wipes, every thing still there, root still here
Rebooted once again with success
rebooted into recovery (stock since I lost my CWM) with success
EDIT 2
Flashed CWM and my note is back for my modifications
:fingers-crossed:
Stock Recovery File?
thermax04 said:
i upgraded my note N8000 via odin mobile pro with success and everything was smooth and the root was not intact
I tried to flash a theme via mobile odin but was not success, but note was still ok
then 2 days later I tried to enter the recovery mode , i found the note stuck on samsung boot screen and dose not reboot, I can enter download mode but can not enter recovery mode to reflash even the stock rom
what to do?
should i reflash the CWM as 1st time? then reflash the root if i found it is gone?
or i have to reflash the stock rom first via odin desk top since i can not reboot the note? problem is the stock rom is on the note and do not have it on PC
the note now is on Samsung boot screen, how to turn it off since note can not remove the battery?
EDIT 1::good:
Flashed a stock recovery via odin desk top, and rebooted
Note is back alive , no wipes, every thing still there, root still here
Rebooted once again with success
rebooted into recovery (stock since I lost my CWM) with success
EDIT 2
Flashed CWM and my note is back for my modifications
:fingers-crossed:
Click to expand...
Click to collapse
Do you have a link to where you found the stock recovery rom/image? And how did you flash it? I am having a similar problem right now.
kyleschepis said:
Do you have a link to where you found the stock recovery rom/image? And how did you flash it? I am having a similar problem right now.
Click to expand...
Click to collapse
do u mean the stock rom? I got it from samobile.com
or u mean u want the stock recovery?
try this
http://mirror21.downloadandroidrom....e10.1/recovery/N8000_StockRecovery.tar?token=
Will reflashing the tablet to stock, delete all of my files off of it? Is there a way to retrieve the files through download mode somehow?
kyleschepis said:
Will reflashing the tablet to stock, delete all of my files off of it? Is there a way to retrieve the files through download mode somehow?
Click to expand...
Click to collapse
in my post i wrote that reflashing the stock rom did not wipe (delete) any thing, u will find all your stuff undeleted
thermax04 said:
in my post i wrote that reflashing the stock rom did not wipe (delete) any thing, u will find all your stuff undeleted
Click to expand...
Click to collapse
It says you flashed a stock recovery. Is it the same case for a stock ROM?
kyleschepis said:
It says you flashed a stock recovery. Is it the same case for a stock ROM?
Click to expand...
Click to collapse
sorry, my mistake, flashing the stock rom will not delete your stuff, just be sure to flash the same rom or higher, not lower one
So, I tried flashing the stock recovery and that did not work. And then I tried flashing the stock rom (multiple times with different roms) and that did not work either. My tablet is still stuck on the screen that says "Samsung Galaxy Note 10.1". Do you have any other suggestions?
can u write some details about what was before and reason for problem, to think together about a solution
thermax04 said:
can u write some details about what was before and reason for problem, to think together about a solution
Click to expand...
Click to collapse
My Note 10.1 N8013 was rooted, had TWRP, and Cyanogenmod 10.2 Nightly on it. I hadn't touched it in two days and went to turn it on. It wouldn't turn on, so I assumed it was dead. I charge it overnight and try to turn it on in the morning, but it just goes into a boot loop. The tablet says "Samsung Galaxy Note 10.1" and stays that way until it dies. If I boot into recovery mode, the Teamwin (TWRP) title screen pops up and then immediately disappears. The tablet then shows the battery loading icon if it is plugged in. The icon shows up, then disappears and the shows up again and repeats this a few times. I could only boot into download mode successfully.
I have tried flashing different stock roms and recoveries through odin, including the one that you have linked on here. None of them have worked. I have also tried repartitioning the tablet, which passed on Odin, but did not solve the problem.
Other forums say that I should do a factory reset or wipe the data, but I do not know how to do this without being able to boot into recovery or the OS itself.
Thanks
P.S. I also brought it to Best Buy to see if the Samsung guy could reflash the stock rom, but his rom did not work either. They are all passing on Odin, so it isn't an error in that case.
I read that a lot of people got problems with Cyano roms. I did not like it and never used it, sorry can not help you
thermax04 said:
I read that a lot of people got problems with Cyano roms. I did not like it and never used it, sorry can not help you
Click to expand...
Click to collapse
Could it be because of the Cyanogen rom? I didn't update recently... I probably updated it a week before it died. Would you happen to know how to do a factory reset / wipe the data from the tablet, if I can't get into recovery mode or the OS?
I don't think that there is any other way, sorry about that.
try to put your problem in the Cyano rom thread, may others had the same and solved it
Ok thank you
Let me know if you get it fixed
Hi kyleschepis,
Let me know if you find a solution. I have a very similar issue . . . the difference is, I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started about 5 days ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But 5 days ago, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I am able to get into the Odin download mode but cannot get into recovery mode no matter what I do/
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. But the power + volume up combination does not get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for 5 days now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
robb-x said:
Hi kyleschepis,
Let me know if you find a solution. I have a very similar issue . . . the difference is, I am not using a custom ROM. I have the stock ROM that came with the GT-N8013.
My issue started about 5 days ago. My Galaxy Note had been having occasional issues with the external SD card. A warning would appear saying that the SD card had been removed, and a couple of seconds later it would re-mount and every thing was fine.
But 5 days ago, I picked up my note and turned the screen on (it was already started) and noticed the warning message while the screen was still locked. Then, as the second message was still being displayed letting me know that the SD card had been mounted, I swipe the screen to unlock. But instead of unlocking, my Note completely rebooted. It got as far as the logo screen (displaying "Samsung Galaxy Note 10.1"), but would go no further.
I am able to get into the Odin download mode but cannot get into recovery mode no matter what I do/
I have tried re-flashing the stock ROM ("KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_user_low_ship.tar.md5") several times, as well as trying to install customer recovery modes like CWM and TWRP, as well as the stock recovery. But the power + volume up combination does not get me into recovery mode. Even if, as many have suggested, I continue holding the button combination until the logo screen displays a second or a third time.
I have been without my Note for 5 days now, and I use it for everything. So, any help I can get would be appreciated.
Thanks,
Rob
Click to expand...
Click to collapse
Did you try removing the sd card and reboot again ?
DId you fix your tablet
kyleschepis said:
Ok thank you
Click to expand...
Click to collapse
Hi Kysleschepis,
Were you able to fix the problem with your phone.
I have exact same problem....my Gt-n8000 tablet is stuck on "Samsung Galaxy Note 10.1" logo. And i cant access the recovery mode.
Let me know if you found a solution to this problem.
Thanks.
same here but didn't work
i have same problem with my Note 10.1 N8000 stuck in bootloop problem but i didn't do anything like upgrading or install new app ... its stuck by him self and i tried the following and all not working :
1, Hard Reset with software menu (not working)"only if the device is working".
2, Hard Reset with Dial secret code key(not working) "only if the device is working".
3, Hard Reset with Hardware Key Button(Factory recovery screen not working).
4, installing recovery philz_touch_6.07.9-n8000.tar with Odin (passed installed successfully but still not working).
5, installing recovery openrecovery-twrp-2.4.1.0-p4notewifi_3 with Odin (passed installed successfully but still not working).
6, installing recovery CF-Auto-Root-p4noterf-p4noterfxx-gtn8000.tar with Odin (passed installed successfully but still not working).
7, installing recovery twrp-2.6.3.1-n8000.tar with Odin (passed installed successfully but still not working).
8, installing recovery Samsung_N8000_Hard_Reset_File_JB in "CSC" field with Odin (passed installed successfully but still not working).
9, installing "N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar" full new Android OS with Odin (passed installed successfully but still not working).
Finlay there is No Samsung Service Center in my country, i need to send it by mail to nearest country have Samsung Service Center and will cost me a lot .. what i have to do
Weeshi said:
i have same problem with my Note 10.1 N8000 stuck in bootloop problem but i didn't do anything like upgrading or install new app ... its stuck by him self and i tried the following and all not working :
1, Hard Reset with software menu (not working)"only if the device is working".
2, Hard Reset with Dial secret code key(not working) "only if the device is working".
3, Hard Reset with Hardware Key Button(Factory recovery screen not working).
4, installing recovery philz_touch_6.07.9-n8000.tar with Odin (passed installed successfully but still not working).
5, installing recovery openrecovery-twrp-2.4.1.0-p4notewifi_3 with Odin (passed installed successfully but still not working).
6, installing recovery CF-Auto-Root-p4noterf-p4noterfxx-gtn8000.tar with Odin (passed installed successfully but still not working).
7, installing recovery twrp-2.6.3.1-n8000.tar with Odin (passed installed successfully but still not working).
8, installing recovery Samsung_N8000_Hard_Reset_File_JB in "CSC" field with Odin (passed installed successfully but still not working).
9, installing "N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar" full new Android OS with Odin (passed installed successfully but still not working).
Finlay there is No Samsung Service Center in my country, i need to send it by mail to nearest country have Samsung Service Center and will cost me a lot .. what i have to do
Click to expand...
Click to collapse
I have the same problem. I was just playing a game when it suddenly turned off and went to the boot screen. Also tried installing N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar.md5 (success but also didn't work). Still stuck at the "Samsung Galaxy Note 10.1" screen.
Also can't access recovery, or do a wipe before installing firmware (I think USB debugging isn't turned on).
Did you find any solutions yet?
Thanks.
el_roi said:
I have the same problem. I was just playing a game when it suddenly turned off and went to the boot screen. Also tried installing N8000XXUDNE5_N8000OLBDNE3_N8000DXUDND1_HOME.tar.md5 (success but also didn't work). Still stuck at the "Samsung Galaxy Note 10.1" screen.
Also can't access recovery, or do a wipe before installing firmware (I think USB debugging isn't turned on).
Did you find any solutions yet?
Thanks.
Click to expand...
Click to collapse
Sorry till now no solutions ... If you have warranty on the device go to the samsung maintenance center i think its wrong factory made
Just wanting some advice (if any) to a white line issue I'm having with this tablet. I bought this tablet with Lollipop 5.0.1 already installed. I managed to get it downgraded, rooted, and currently have TWRP installed as well as CM12.1 nightly. The problem I have is that as soon as I install ANY custom recovery (TWRP or CWM recovery) it boots normally at first giving me the LG logo. Then, instead of getting the AT&T logo (or the CM custom boot animation), it gives me a series of white lines spamming from top to bottom of the screen. I know for a fact it has to be software related as when I return to stock KK everything boots fine, giving me the LG logo followed by the AT&T logo. I did NOT use the ADB method. Instead I downgraded using the LG Flash Tool, and a test KDZ file, which allowed me to install Flashify, then TWRP. My problem ONLY begins once I install ANY custom recovery. This process did not unlock my bootloader, however. Could this be my culprit, or would it be something else? Any help is greatly appreciated, and thanks in advance for any help/tips. More information is completely available upon request.
P.S. The white lines eventually disappear when the screen goes to sleep on it's own. I can then press the power button to wake the device which gives me the lock screen as normal. I just want to know if I can get the boot animation working. Everything else works fine.
You found cwm?
I recently replaced my nexus 5 display and frame, flashed the latest marshmallow stock images (through flash-all.sh from an early MM preview). From there I flashed TWRP hammerheadcaf and cm13 hammerheadcaf, and my power button would not power the device. I could get to bootloader with pwr+voldown, but the device wouldn't start from there (black screen).
Standard CM13 and AICP hammerhead builds boot and run great, hammerheadcaf builds just cause the device to stop powering. I even tried modifying a hammerheadcaf updater script to flash on the hammerhead TWRP, but the device still wouldn't power with the power button.
I remember hammerheadcaf (in cm12/12.1 days) as being light on battery and awesome in general. I'm open to any ideas or testing. Thank you in advance.
Bump
Same here
Same thing happened to me today:
My Nexus 5 was working well on cm 13 hammerheadcaf.
I changed my screen, and it was stuck on google logo when i tried to reboot it.
Tried to reinstall cm-13.0-20160129-UNOFFICIAL-hammerheadcaf (noticed that it is not longer officially supported btw..) but my phone wouldn't boot after the install (black screen, not responding to power button). I also tried an older hammerheadcaf one, without success.
When back to stock Android, it worked.
Tried cm-13.0-20160130-NIGHTLY-hammerhead, it worked too.
I suppose a problem with cm-13.0-20160129-UNOFFICIAL-hammerheadcaf bootloader, but couldn't find what..
I noticed that bootloader images are present in the cm-13.0-20160130-NIGHTLY-hammerhead zip file, while they are not in the hammerheadcaf one.
Running cm-13.0-20160130-NIGHTLY-hammerhead right now, awaiting for more informations about hammerheadcaf..
Numerinico said:
Same thing happened to me today:
My Nexus 5 was working well on cm 13 hammerheadcaf.
I changed my screen, and it was stuck on google logo when i tried to reboot it.
Tried to reinstall cm-13.0-20160129-UNOFFICIAL-hammerheadcaf (noticed that it is not longer officially supported btw..) but my phone wouldn't boot after the install (black screen, not responding to power button). I also tried an older hammerheadcaf one, without success.
When back to stock Android, it worked.
Tried cm-13.0-20160130-NIGHTLY-hammerhead, it worked too.
I suppose a problem with cm-13.0-20160129-UNOFFICIAL-hammerheadcaf bootloader, but couldn't find what..
I noticed that bootloader images are present in the cm-13.0-20160130-NIGHTLY-hammerhead zip file, while they are not in the hammerheadcaf one.
Running cm-13.0-20160130-NIGHTLY-hammerhead right now, awaiting for more informations about hammerheadcaf..
Click to expand...
Click to collapse
Please keep me updated Numerinico. I never ran cm13 hammerheadcaf on this device, only 12.1. But I do wonder if there's an issue with (potentially) non-OEM hardware that's supported by stock kernel but not hammerheadcaf kernel.
I decided to try a new build of hammerheadcaf with the new twrp 3 caf recovery. The recovery fails to start, and sits at a black screen (like when I try the ROM). The author notes that the build is based on the current caf branches.
bump
I did not tried anything else for the moment, I ll keep you in touch.
By the way, I did not noticed any big difference between CAF and not CAF after a month of usage.
After installing blisspop (or I don't really remember), I realized that WiFi wasn't working and neither was bluetooth so I decided to flash Extended Stock Kernel kernel, first with flashing the boot, then flashing the zip from recovery mode and even after that, the result was the same. It didn't work. Later on I went to the Phantom kernel's page and flashed that without checking that the kernel was meant for 4.4 and it bricked my device. Now, whenever the phone starts, it shows the Phantom kernel boot at start with its logo without any led light appearing below and due to that I'm unable to go into either flashmode or fastboot. It keeps restarting the Phantom boot at start and doesn't go any further. Please help!
EDIT: A more detailed version that I wrote a few months ago to the kernel's developer.
-
Previously I had my Xperia L reset on stock ftp then flashed the Extended Stock Kernel on it. Since the wifi wasn't working, I tried to download R17 and flashed it through CWM and now the phone keeps restarting on the Phantom Logo. It shows the logo, waits for about 10 seconds then restarts and the same keeps repeating. I saw it was for Kitkat but then too I insisted on installing. I can't access neither bootloader nor recovery mode. The light which comes when the Phantom Logo pops doesn't appear either. Can you help me please? Anything would be greatly appreciated. I know I did a stupid thing but I really don't want to give up on this device.
-
Xephor_EX said:
After installing blisspop (or I don't really remember), I realized that WiFi wasn't working and neither was bluetooth so I decided to flash Extended Stock Kernel kernel, first with flashing the boot, then flashing the zip from recovery mode and even after that, the result was the same. It didn't work. Later on I went to the Phantom kernel's page and flashed that without checking that the kernel was meant for 4.4 and it bricked my device. Now, whenever the phone starts, it shows the Phantom kernel boot at start with its logo without any led light appearing below and due to that I'm unable to go into either flashmode or fastboot. It keeps restarting the Phantom boot at start and doesn't go any further. Please help!
EDIT: A more detailed version that I wrote a few months ago to the kernel's developer.
-
Previously I had my Xperia L reset on stock ftp then flashed the Extended Stock Kernel on it. Since the wifi wasn't working, I tried to download R17 and flashed it through CWM and now the phone keeps restarting on the Phantom Logo. It shows the logo, waits for about 10 seconds then restarts and the same keeps repeating. I saw it was for Kitkat but then too I insisted on installing. I can't access neither bootloader nor recovery mode. The light which comes when the Phantom Logo pops doesn't appear either. Can you help me please? Anything would be greatly appreciated. I know I did a stupid thing but I really don't want to give up on this device.
-
Click to expand...
Click to collapse
yea.... output battery... reinput it.... DONT TOUCH POWERBUTTON.... holf vol - and connevt to pc
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
yea.... output battery... reinput it.... DONT TOUCH POWERBUTTON.... holf vol - and connevt to pc
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
-
It worked, I flashed the generic ftf and everything's okay. Thank you so much!
-
Hello everyone,
i have a problem with a Honor 6 from a friend. The phone has an Unlocked bootloader and was rooted.
Then my friend received an Update Notification on the phone and he has done that update. I have said before, that this won't work and it will brick your phone. But i don't know why, he made the Update.
Since then the Phone stucks on bootloader with the "Honor" Logo" AND the LED Notification is blinking first 1 x Red and then 3x in Green. This blinking is repeating 2 or 3 times then only the Honor Logo stays on the screen.
The Phone can access fastboot mode, but not the recovery mode (Volume Up + Power) or the 3-Finger-Mode, to install a stock rom from the sd-card. We have flashed a lot of Roms with the Multitool in the Unbrick Mode, but nothing works, still the same.
Our Problem is:
- We don't know on which version the Phone was before the Update. We know only that it was Kitkat with 4.4.2 and Emui 3.0 --> Maybe this is important for downgrade?
- After the update, he couldn't turn off the phone. So, the phone stayed on until it turned off by itself.
-> When we wanted to enter recovery mode one day later, the screen showed up an Icon with red flash, like the battery was empty.
--> the battery was completely empty because of not turning off -> We charged the battery by connecting the empty battery to another Honor 6 mainboard. After that the icon didn't show up but we still can't enter recovery mode or 3-Finger-Mode.
What can we do now? Every solution would be appreciated.
Thanks in advance
Same problem here. Any hint?
medusa_gorgona said:
Same problem here. Any hint?
Click to expand...
Click to collapse
Until now, i haven't found a solution
works only while charging
seems same is the case with me after updating , it only works when its being charged else only the honor screen and shutting down
me to have same problem
I forgot to say i have an L12.
The only thing that has worked for I have tried is to flashing TWR for emui4.0 from Multitool.
But ROMs and OTAs at this thread are not prepared to be installed via recovery.
I guess I could use an L12 backup to be restored at TWR, if someone can tell me where can I download it.
I want to try everything with stock roms before I try with custom ones.
P.D.: sorry for my bad english.
Finally, I managed to work again.
The steps I followed (keep in mind i have an L12):
Using Multitool -> Unbrick, I extracted the imgs from the B535 ROM
At Stock recovery, I made a factory and cache reset.
I flashed USERDATA from Fastboot
This worked for me.
I hope it helps
i am using l04 and i'm have same problem bro..