Hi all. I know there are quite a few posts with people having a similar problem to this, however none of the solutions mentioned have worked for me. Recently, I updated my phone to JB using Odin 1.85 (I8160XXNF1). All was working fine, and when i recieved a notification saying there was an update available, I updated to a new version, which was also JB 4.1.2 but it changed to I8160XXMG2. Everything still worked fine at this point, though there was still an update available. So, once again, I decided to update it although this time the phone never fully booted, it gets stuck on the boot screen every time (the one saying 'SAMSUNG galaxy Ace 2 GT-I8160' not the animation). I couldn't boot into recovery, only into download mode so I flashed the previous JB (I8160XXNF1) which worked, however this has not resolved the problem and the phone is still stuck on the same screen.
Okay, thanks for reading this, please help if you have any ideas on how to resolve this issue.
TiPEX360 said:
Hi all. I know there are quite a few posts with people having a similar problem to this, however none of the solutions mentioned have worked for me. Recently, I updated my phone to JB using Odin 1.85 (I8160XXNF1). All was working fine, and when i recieved a notification saying there was an update available, I updated to a new version, which was also JB 4.1.2 but it changed to I8160XXMG2. Everything still worked fine at this point, though there was still an update available. So, once again, I decided to update it although this time the phone never fully booted, it gets stuck on the boot screen every time (the one saying 'SAMSUNG galaxy Ace 2 GT-I8160' not the animation). I couldn't boot into recovery, only into download mode so I flashed the previous JB (I8160XXNF1) which worked, however this has not resolved the problem and the phone is still stuck on the same screen.
Okay, thanks for reading this, please help if you have any ideas on how to resolve this issue.
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
I saw you solved your problem so i'm gonna close this thread.
Regards
Related
Hello every one on this forum, I need your help regarding my Samsung Galaxy note GT N7000, I woke up yesterday to find out that my phone need some update and i press ok and I went to the bathroom to get ready for work and by the time i came back my phone as stop working completely and I tried to reboot it but to no avail, I need your help pls.
Thanks
were you on gingerbread and what about root? any custom rom? can you still get into recovery? Or did you have clockwork mod? i wonder if it was upgrading to ICS and your phone died? Just some things that might help narrow down a bit.
Galaxy Note not booting after firmware update
Hi,
The same thing happened to me today. My phone indicated that an update was required. When I proceeded to install, the phone is stuck at the SAMSUNG logo.
My phone is not rooted. About a few weeks ago I had upgraded from GB to ICS.
Any help would be much appreciated. Thanks!
Facing the same problem
Hi all,
I am facing the same problem since this morning. I have not rooted my phone. Recently I upgraded my Galaxy Note from Gingerbread to ICS 4.0.3. This morning, I upgraded the firmware, as I had done this in the past as well, I didn't think it may lead to any problem. But since then, the phone starts and shows Samsung prompt. Is it because of any bug in the latest update? Does anyone know what to do in this situation?
I am facing the same problem, the Samsung logo keeps glowing off and on after the boot chime plays.
Does any one have any clue about this? I think its happening to India users who got this update.
Edit: I am unable to go into the recovery screen as well. The green droid shows, some loading happens(tries to?) in the bar below and the screen turns off and if I keep holding the buttons the same cycle repeats. Leaving them at any point leads to the Samsung glowing logo and no boot!
Another one bites the dust
Faced the same problem yesterday...running around to get my contactsrescued...even the authorized service centres are only assuring flashing it -0 as if it is a big obligation
Need someone to access dram... jtag to a usb mode...going to try at heera panna & manish market tomoro - both in Mumbai
Lts c
If anyone can help - kindly upload post
Found the solution!!!
Hi Guys, I've found the solution.
Edit: Since, I received queries from many people, I would like to know from the advanced/experienced members if the solution I am suggesting is absolutely right or not, and if it could lead to any problem. My phone is working fine, I haven't lost any data.
The solution:
1. Download the stable ICS version released in May.
2. Install it manually using the ODIN settings.
Guys, please help us out, let us know your opinion.
add me to list
using just the stock rom
this update flashed on the notification and after installation doesnt go beyond the
boot screen
Note , India
Two days ago my Galaxy Note 10.1 gt-n8010 got stuck at the initial screen (Samsung Galaxy Note 10.1)
It was working normally, and it was last successfully upgraded to a custom rom and CWM 6.0.3.6 a month ago.
The custom rom was (to my best knowledge Android Revolution HD 11.2 - 4.1.2)
Booting into recovery and download modes works.
CWM recovery works partially. Erasing Cache en resetting to factory works, and sometimes results in getting to the second splash screen of the boot process where it again gets stuck (Samsung animation keeps glowing), but more it keeps getting stuck at he first boot screen.
Erasing Dalvic cache leads to immediate reboot.
CWM log files cant be opened / external sd card can't be reached/mounted.
So CWM is only working for a small part.
I've attached images of the CWM screens including a log-screen that shows that files and folders cannot be found.
Using ODIN, to flash a new CWM or custom/original ROM result in a FAIL message.
Tried different ODIN version, two original Samsung data cables and two computers. Alle the same result. FAIL.
I'm hesitant to continue now without some help. I might do more harm and destroy all chances there are to recover this tablet.
I've flashed all my phones and tablets before. I'm not an expert, but never had a mishap, because I triple read the instructions. The situation that arises now is not a result of a failed upgrade/flash, but suddenly appeared one morning.
On the last days i thought i had also broken my tablet and i had more or less the same problem. If i were you i would directly download an official 4.4.2 and flash it via odin. Then if you everything works i would try whatever you want to flash
Try changing recovery. Give TWRP a try. Had it happen with a phone and switching recoveries solved it.
Sent from my SM-N900T using XDA Free mobile app
Well I had the same problem due to toooo many consecutive reboots
I was on gnabo then wid twrp
then I reflashed 4.4.2 update via odin and everything was a breeze after that
and one more thing
be sure to change the recovery cause the same one might not work again
well at least it didn't do worth me
I use philz now
Can't flash anything
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Deadbeef said:
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Click to expand...
Click to collapse
are you sure you do not have a bad cable
I've used two different original Samsung cables. Same result.
Brick?
Change a Odin version like odin 3.07 http://forum.xda-developers.com/showthread.php?t=1837605?
your odin shows your device is Samsung I9505 Galaxy S4
Where does Odin show the device is a i9505? It's a n8010.
reCAPTCHA
I am having similar issues (Galaxy Note 10.1 N8010 Gnabo ROM) - stuck on the samsung logo (never managed to get past it though) boots into recovery but can't mount sd card OR internal storage. Can't flash anything using Odin, always gets a Complete(Write) operation failed. Any suggestions ?
Looks like we're both in the same sinking boat.
Sorry for late reply
Deadbeef said:
Where does Odin show the device is a i9505? It's a n8010.
Click to expand...
Click to collapse
Sorry for late reply
Your Odin Screen Shot Say i9505 as your device
Deadbeef said:
Looks like we're both in the same sinking boat.
Click to expand...
Click to collapse
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
georgesmh said:
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
Click to expand...
Click to collapse
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Agyar said:
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Click to expand...
Click to collapse
guys did any of you solve the problem??
georgesmh said:
guys did any of you solve the problem??
Click to expand...
Click to collapse
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Agyar said:
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Click to expand...
Click to collapse
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
georgesmh said:
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
Click to expand...
Click to collapse
I've seen few other occurrences of this on different roms on various forums, so probably not Gnabo issue. also, nobody nowhere had a fix for it
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
dmarchant said:
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
Click to expand...
Click to collapse
I don't think it was flash failure, at least not in my case, since device worked without any issue for quite a while after last flashing... what was different now is that my battery was drained out for the first time i quite a while...
Please pardon me for any faux pas as I am new here.
Mods please refer me to the appropriate thread and close this one, in case this one is a duplicate.
It seems my Moto G 1 Gen XT1033 is hardbricked. I had been running a CM 12 for falcon - nightly release since May 2015 and had had no problems so far. I had also upgraded my recovery to CWM Touch.
Two weeks ago, my phone got stuck in a boot loop (I now realise that that is called a softbrick), I managed to boot into recovery and updated my OS with the latest nightly release of CM 12 for my phone. I also tried to upgrade the recovery version with the same as that of the OS version but I don't think that it got upgraded. (I'm not sure what it said).
Anyway my phone was working fine for an hour or so until CM gave some errors on opening the themes configuration, so I thought rebooting my phone would solve the problem.
My phone never booted after that. It didn't even turn on or boot into the bootloader/recovery etc. I checked the battery etc. and it was fine. There was no issue with the hardware.
I then connected my phone to my laptop and it recognised it as qhsusb_bulk. I have spent a lot of time searching and trying various methods like:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076
Using the MotoTool All In One etc.
I cant seem to figure out the problem. I don't even know what my bootloader version was etc.
Is there a problem with my bootloader or recovery? I can't seem to understand.
Can someone please help me with this?
Thanks
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
motolollipop said:
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
Click to expand...
Click to collapse
Thanks man. But no help so far
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
CoolCrusader said:
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
Click to expand...
Click to collapse
That happened to me too, I think even the same image! It was a long time ago and I have now switched to a Oneplus One after using a Moto E which actually isn't that bad - I got it new super cheap. For me, Cyanogen restarted to update and after a LONG period of time stopped doing anything (I have upgraded before). I couldn't mount anything in CWM and I lost all data irrecoverably. The partition table got all messed up, and I had to flash a dual sim image as it was the only one that loaded - done through fastboot. I then flashed the original kitkat image and then massively messed up and updated, making my phone qhs_bulk.
Basically everyone who has had lollipop on their devices and have this are waiting for files to be leaked from Motorola so they can make their phones work. Not much is happening currently, you might as well get a new budget phone - some of the new ones are much better than the Moto G 1st gen! Or you could do what some people are doing which is ordering broken Moto Gs off eBay and replacing the board. Good luck!
---------- Post added at 01:49 AM ---------- Previous post was at 01:42 AM ----------
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
You may want to go the fastboot method to flash a stock lollipop image and CWM recovery - if you don't have a backup, you may want to try just flashing something like TWRP to see if you can get some files off your device, then completely flash over it.
hi, in the past I had a huawei y511 and because I had this problem I've changed my phone now, but I want to fix it. plz help me.
Previously I could root my phone easily using framaroot 1.8, and I tried to root my phone to do some things then after things got ok, I unrooted it and this was done several times, but the latest time I wanted to root, it didn't allow me and I installed framaroot 1.9 and rooted successfully. but the problem started from here, after a couple of days, constant force closes came and without any they started force closing, clicking ok and the next one was there! sometimes restarting could fix my problem but in some situations restarting the phone was not the solution and I was made to enter recovery mode to full wipe, then everything could get ok again! firstly I thought the problem is from updated gaps, so I tried keeping them outdated to see if it was relating to this, but no nothing changed, although no apps was updated, these errors came again! I even flashed my phone (but I hadn't unlocked it's bootloader) to the stock rom to see if it could fix but NO, even in this rom problem existed and already exists! I googled a lot but couldn't find any working solution so i ask my question here! I do not know that may either unlocking bootloader or just installing a custom rom fix my problem?!?!?! plz help me this is really annoying!
HUAWEI Y511-U30, BB118
PLZ PLZ PLZ SOMEONE HELP!
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