This is just so i can learn for if this happens again in the future.
I have been running the cm9 nightly (26th) and today downloaded the 26th GT7 (based on cm9) using goo manager. After flashing the zip i was stuck at the Samsung boot screen and could not enter recovery. I have managed to get my tab back using download mode and restocking using the Overcome guide. the funny thing is, a similar thing happened last night whilst updating my sons Galaxy S.
Is this likely to be simply faulty downloads? Could I have done some thing less drastic to recover?
Cheer
have you checked if md5 hash of the rom you just downloaded is the same?
this problem happened to me once, after i successfully flashed a cm9 rom i was somewhat stucked on the boot animation. the difference is i can access recovery mode. but then i tried reflasing again, minutes haved passed on the boot animation and im close to calling it and reverting back to my nandroid backup but the unexpected happened and my boot up pursued.
lesson is: it pays to wait 5 or maybe 10 minutes before quitting the boot up process.
sorry if i cant provide you much useful information. taking long boot animation is rare(only happened to me once).
Deleted the originally downloaded files and didn't check the md5. Used the goo manager on tab to download so assumed it was fine.
Maybe waiting a little longer during boot would have solved it. I waited a couple of minutes.
Cheers for reply.
Sent from my GT-P1000 using Tapatalk 2
no problem sir! just keep me posted regarding this matter.
cheers!
Related
Hi there,
Have been using ICS on my galaxy s for a couple of months. However this is the second time out of the blue it's decided not to boot for me.
The first time I thought it was because I dropped it and reinstalled gingerbread through Odin, then went back to ICS which was a very lengthy process.
I haven't installed anything, and now after just using the phone as per normal and it's decided to stop working? Any tricks I can do?
Basically it boots up, gets to the loading screen and just does that forever. I can boot into recovery but not sure what I should be doing next.
You could try reflashing your rom from recovery .
I think it's necessary to know which ICS-rom, for example slim ICS 2.8 needs to flash kernel first and then the rom ...
Sent from my GT-I9000 using XDA
Thanks imgibby123, if that is the last resort I may as well try it.
I've actually forgotton which one it is, I flashed ages ago and was very stable it just literally broke itself (a number of apps where crashing this mornign (reader, gmail etcc), so I held down the power button, turned it off as per normal, now the phone won't get passed the loading boot animation).
It was cynogen something, team platypus - I feel stupid I can't recall the details. But the ROM is still on there so I'll try reflashing from recovery.
Edit: It's ICS 4.0.3 RC3.1, so obviously still a RC but still! It worked flawlessly for months before
Thanks for the help.
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.
I installed cyanogenmod 10.2 nightly 20130824 accidentally, thinking that it was another 10.1 update (which by then was pretty stable), and realized that i made a big mistake: tonnes of bugs (focal, screen elements blacking out, play store not working).
But when i tried to boot into recovery to restore my clockworkmod full back up (which i do almost everytime i update CM), the "Galaxy Note N7000" boot screen comes up, and then a black screen. I can still boot back into the normal boot, but the tonnes of bugs just annoys me sooo much.
(i've tried to boot into recovery many times, to no avail)
Then, i tried to update it. I figured a newer version should at least be slightly more stable.
But updating cyanogenmod requires the phone to boot into recovery.
soooo fk.
Also when i try to boot into download mode, a screen showing an android icon and Downloading Do Not Turn Off Target pops out.
So after some google searches which didnt help, i came here to xda devs hoping you smart people could help me with this predicament.
Please tell me, has anyone experienced this problem on any phone and do you have any idea what to do?
It's a known bug with cm10.2. Follow this thread, just install phillz kernel to give you recovery, then you can flash cm10.1.
http://forum.xda-developers.com/showthread.php?p=45041491
Sent from my GT-N7000 using XDA Premium 4 mobile app
So, to make a long story, short, for the past couple of days my phone has been soft-bricked... It first happened when I attempted to flash dmodv6 in CWM. Everything looked good throughout the installation, however, when I rebooted my device, I got stuck in a boot loop where It would say "Samsung Galaxy S III GT-I8190" for a few seconds, the screen would go black, then say the same thing again... over and over and over...
After a lot of trial and error because of NOT making a nandroid backup via CWM (stupid, I know - I had made one via Titanium Backup and thought that might be good enough), I finally was able to boot. Thanks to xXPR0T0TYPEXx, I was able to flash another rom by puting my external sd card into another phone, loading another rom onto it, and putting it back in my phone. I now had Cyanogenmod10 and was able to boot back up.
I attempted to restore the Titanium Backup I had made with this new rom (stupid again, I know) and it made almost every service on the phone stop working... I desperately wanted just to get back to square one - to install stock firmware and go from there. I followed tys0n's guide on flashing stock recovery then attempted to install stock firmware... All seemingly went well - I booted up, got past the initial "Samsung Galaxy S III GT-I8190" logo and finally got hung up at the "Samsung" logo. I left it one while I went to sleep, just to see if it would eventually work... I woke up and it was still the same. I tried flashing different version of the same stock firmware but it all ended in getting hung up at the "Samsung" logo.
A major problem is that I absolutely CANNOT flash a custom recovery via Odin - it just will NOT work. Everything looks good on Odin's end - I PASS, get the (succeed 1 / failed 0) thing but am sent to stock recovery every time I do the 3 button combination. I've tried many version of CWM and TWRP.... NOTHING. I've even unticked the "Auto-Reboot" button in Odin and pulled the usb cable and battery upon completion but, but nothing ever works. The only way I was ever able to get CWM on my phone in the first place was by an in-phone app... Rom Manager, maybe? I can't remember. But, as it is, that method is out of the question.
I've learned a lot about what I did wrong so that's the only good part of all of this. Now, all that's left is to fix the thing so I can go about it right. I'm completely out of ideas, have spent almost a full 24 hours searching solutions to this problem and I am at wits end...
I just want to get back to stock firmware... Any ideas, guys? Should I go about re-partitioning my device at this time?
I have the PIT file... but I'm not sure as to which firmware to choose. I imagine a firmware that is 4.1.1 like my phone was... but I'm not sure about the region. I live in the US and there is no US or North American region firmware version.Can anyone shed some light on which one I should choose?
My SSN underneath my battery say "GTI8190GSMH".
I'm sorry this is so long, I just wanted to explain what happened as best as I could. So, should I go about re-partitioning my device at this point? If so, what firmware would you recommend for my model? Are different region versions okay for a this method?
Or is there another way?
Thanks, guys. :silly:
Some additional details (if it will help): I can, indeed, boot into both recovery and download mode. I just can't seem to flash a stock rom that will boot past the "Samsung" logo.
I've even attempted to flash the param file after the rom flash but it didn't help.
AffectiveEffect said:
Some additional details (if it will help): I can, indeed, boot into both recovery and download mode. I just can't seem to flash a stock rom that will boot past the "Samsung" logo.
I've even attempted to flash the param file after the rom flash but it didn't help.
Click to expand...
Click to collapse
Do you have the stock recovery now instead CWM? If yes do (if you didn't try it) a factory/data reset and wipe cache but it will delete your pics, music etc on your internal storage too.
xXPR0T0TYPEXx said:
Do you have the stock recovery now instead CWM? If yes do (if you didn't try it) a factory/data reset and wipe cache but it will delete your pics, music etc on your internal storage too.
Click to expand...
Click to collapse
Yeah, I have stock recovery now and I have tried that many, many times... Even if I install something like CyanogenMod, it still gets hung up on the CyanogenMod boot screen... And if I boot a stock firmware, it gets hung up at the same place at the "Samsung" logo...
I have an idea that one of the only options left is a PIT re-partitioning... If so, how would I properly go about that? Load the PIT file and the stock firmware in odin? Or only the PIT as PDA? I've heard a couple of different things and am unsure.
AffectiveEffect said:
Yeah, I have stock recovery now and I have tried that many, many times... Even if I install something like CyanogenMod, it still gets hung up on the CyanogenMod boot screen... And if I boot a stock firmware, it gets hung up at the same place at the "Samsung" logo...
I have an idea that one of the only options left is a PIT re-partitioning... If so, how would I properly go about that? Load the PIT file and the stock firmware in odin? Or only the PIT as PDA? I've heard a couple of different things and am unsure.
Click to expand...
Click to collapse
I don't know about PIT files but some people got this message : "CUSTOM PIT BINARY" in recovery mode after flashed a PIT file (maybe they used a other PIT file that wasn't compatible). So make sure you use a PIT file that is GT-i8190 compatible.
I tried flashing the PIT file for the hell of it because I am completely out of ideas.... It failed repeatedly in Odin.
I have no clue on how to fix this... I've tried countless roms and they all get stuck on their respective boot screens. The only one that gave me a glimmer of hope was Cyanogenmod10.2.... It went as far as saying "Android is upgrading" and showed "starting apps" but it got hung up there.
I don't know what to do, guys. Someone help!!!
AffectiveEffect said:
I tried flashing the PIT file for the hell of it because I am completely out of ideas.... It failed repeatedly in Odin.
I have no clue on how to fix this... I've tried countless roms and they all get stuck on their respective boot screens. The only one that gave me a glimmer of hope was Cyanogenmod10.2.... It went as far as saying "Android is upgrading" and showed "starting apps" but it got hung up there.
I don't know what to do, guys. Someone help!!!
Click to expand...
Click to collapse
Use a custom ROM to see if it will fix the problem .Try to flash CyanogenMod 10.2 by NovaFusion via odin or if you flash CyanogenMod 11 then you will automatically get the TWRP recovery. NovaFusion Team Homepage : novafusion.pl. I know you want the stock ROM but try other ROMs to get a booting phone again
xXPR0T0TYPEXx said:
Use a custom ROM to see if it will fix the problem .Try to flash CyanogenMod 10.2 by NovaFusion via odin or if you flash CyanogenMod 11 then you will automatically get the TWRP recovery. NovaFusion Team Homepage : novafusion.pl. I know you want the stock ROM but try other ROMs to get a booting phone again
Click to expand...
Click to collapse
I have... I've tried numerous stock roms and numerous custom roms... all versions of Cyanogenmod, Chameleon, Carbon, Slim mod, etc... They all get stuck at their respective logos.
I even tried the Cyanogenmod with TWRP but, as I explained earlier, I absolutely CAN NOT flash a custom recovery unless I use what ever app I used.... It doesn't work with Odin or with a rom. I don't know why.
I wish someone had more info on repartitioning my phone and if it would help.
NEED HELP?
AffectiveEffect said:
So, to make a long story, short, for the past couple of days my phone has been soft-bricked... It first happened when I attempted to flash dmodv6 in CWM. Everything looked good throughout the installation, however, when I rebooted my device, I got stuck in a boot loop where It would say "Samsung Galaxy S III GT-I8190" for a few seconds, the screen would go black, then say the same thing again... over and over and over...
After a lot of trial and error because of NOT making a nandroid backup via CWM (stupid, I know - I had made one via Titanium Backup and thought that might be good enough), I finally was able to boot. Thanks to xXPR0T0TYPEXx, I was able to flash another rom by puting my external sd card into another phone, loading another rom onto it, and putting it back in my phone. I now had Cyanogenmod10 and was able to boot back up.
I attempted to restore the Titanium Backup I had made with this new rom (stupid again, I know) and it made almost every service on the phone stop working... I desperately wanted just to get back to square one - to install stock firmware and go from there. I followed tys0n's guide on flashing stock recovery then attempted to install stock firmware... All seemingly went well - I booted up, got past the initial "Samsung Galaxy S III GT-I8190" logo and finally got hung up at the "Samsung" logo. I left it one while I went to sleep, just to see if it would eventually work... I woke up and it was still the same. I tried flashing different version of the same stock firmware but it all ended in getting hung up at the "Samsung" logo.
A major problem is that I absolutely CANNOT flash a custom recovery via Odin - it just will NOT work. Everything looks good on Odin's end - I PASS, get the (succeed 1 / failed 0) thing but am sent to stock recovery every time I do the 3 button combination. I've tried many version of CWM and TWRP.... NOTHING. I've even unticked the "Auto-Reboot" button in Odin and pulled the usb cable and battery upon completion but, but nothing ever works. The only way I was ever able to get CWM on my phone in the first place was by an in-phone app... Rom Manager, maybe? I can't remember. But, as it is, that method is out of the question.
I've learned a lot about what I did wrong so that's the only good part of all of this. Now, all that's left is to fix the thing so I can go about it right. I'm completely out of ideas, have spent almost a full 24 hours searching solutions to this problem and I am at wits end...
I just want to get back to stock firmware... Any ideas, guys? Should I go about re-partitioning my device at this time?
I have the PIT file... but I'm not sure as to which firmware to choose. I imagine a firmware that is 4.1.1 like my phone was... but I'm not sure about the region. I live in the US and there is no US or North American region firmware version.Can anyone shed some light on which one I should choose?
My SSN underneath my battery say "GTI8190GSMH".
I'm sorry this is so long, I just wanted to explain what happened as best as I could. So, should I go about re-partitioning my device at this point? If so, what firmware would you recommend for my model? Are different region versions okay for a this method?
Or is there another way?
Thanks, guys. :silly:
Click to expand...
Click to collapse
i got same problem with you before im wayback dmod v6 before and stuck at samsung logo i just try hard reset
1. open your phone
2. remove battery and put the battery try and try til u get in recovery mode (CWM) maybe just tried almost 20x restarting in logo til u in CWM :victory:
3. re-Flash your dmod v6 this way for dirty rom like what i said (softbricks)
4. just flash another new rom whatever u like or dmod v6.
5. I HOPE IT HELPS DONT FORGET TO THANKS <3 :highfive:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
your phone partition got messed up you have to put TWRP back and then go in wipe and then you have to do file repairwhen you fix file then ran back the stock firmware which will fix bootloader
then go back install twrp and install custom rom with root
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
once you fix file then do the format within twrp
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
there is the list of stock firmware try them see which one works with twrp, you have to install twrp first so you can fix the problem using repair files in twrp
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910T/
also read this for installing twrp on 910t
https://forum.xda-developers.com/no...nt/tool-utility-twrp-2-8-1-0-teamwin-t2915588
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
Befour flashing twrp make sure you uncheck Auto reboot....when it's done flashing pull your battery, put it back in the phone but don't power on....you want to boot right into recovery......then twrp will stick