Have I bricked my N7000 / bootloop / COM port failure? - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hi Guys,
Decided to finally update my Samsung Note 1 N7000 as the 4.0.3 stock ROM was struggling with Google Maps and I use this as an in- car GPS. I read about a thousand different how to guides on the net and tried as best I could to back everything up and proceed carefully but I think I have stuffed the phone regardless.
I tried installing a custom recovery (tried both CM and CWM custom recoveries) before installing the latest CM11 ROM. I tried Heimdall and I installed SuperSU and Busybox. Everything I tried seems to either fail or crash half way through and so many of the guides were vague on what to do or their instructions didn't quite match what I saw on the screen. In the end I tried resetting the phone and wiping the cache and now I am stuck. Yes, I probably did too many things but all the guides were contradictory and it is darned confusing for a beginner!
TLDR:
Phone is now in bootloop mode (seems to still be Samsung factory recovery installed) and can't get it out using any of the usual methods
Can put phone into download mode and connect to Odin (phone connection inside Odin is recognised) but Odin eventually gives error message when trying to upload a clean stock Samsung N7000 ROM image of "serial (COM) failure". Have tried connecting to another phone (Note 3) and hardware appears OK but swapped USB ports and cables to make sure.
Is the phone stuffed or am I missing something here?
Cheers

...and the answer is NO! It wasn't bricked...
Tried again today, installed Philz recovery (PhilZ-cwm6-XXLT4-OXA-4.93.6-signed.zip) by copying the .zip file directly onto the SD Card via a USB adapter and executing that .zip through the stock recovery mode.
Rebooted and at last had something different as PhilZ recovery mode now working. Couldn't install anything directly off the SD card and the bootloop was still happening though.
...but...
Now Odin worked. Loaded stock ROM (N7000XXLT6_N7000XSALS8_XSA - 4.1.2) via Odin 3.10.6 (opened ROM in the AP field) and this time it loaded and flashed perfectly. I now have a fully functioning 4.1.2 phone again.
Phew.

Related

[Q] Stuck at Samsung Logo... Repartition phone?

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:

Strange problem with CWM

Hey folks,
I have very strange problem with CWM. I installed CWM clean without ROM via All-in-one toolkit. So, when i turn up the phone, it boots directly into the CWM, of course. Then mounts and storage --> USB mount (or something like that) and I transferred Cyanogen 10. It doesnt shows any error any time i install rom. But when i restart the phone, it stays around 1 minute at the LG logo and then...CWM again...
I tried many times to do this with different roms, but without success. No matter of the ROM, it just boots CWM directly.
Please, help. I will very appreciate it.
Flash twrp with aio and download a rom that fits your bootloader

[Q] i897 Internal SD card unmountable and flashing ineffective

I've never used a forum before, but I'm having a very tough time with my i897 captivate. Its previous owner left it in a box while software updates passed it by. When I came in possession of it, I used rooting, custom ROMs, and flashing to update it to more useful firmwares. I mainly stuck to CM 7, 9, and 10. Eventually I fell victim to that "ICS Encryption Unsuccessful" error and clicked reset, triggering a period of bootloop. I've since fixed the bootloop issue but I still can't get my phone to boot to any firmware. Over the past year, I've been trying all sorts of things to get my phone to work again and I don't know if I've made the problem worse or not. I can get my phone to boot the At&t screen, download mode, and whatever recovery kernel I'm on at the time, but nothing more. I don't even think I have a ROM installed anymore.
What I've tried:
several Odin One-clicks
Heimdall One-click unbrick
Partitioning my external sd card to act as an internal one
ADB sideload
ADB push and install zip from sd card
The errors I run into the most are the "can't mount sd card" ones when I'm trying to flash a custom ROM in recovery. I guess my internal sd is corrupted somehow? Is there a way for me to fix this mess?
asertap said:
I've never used a forum before, but I'm having a very tough time with my i897 captivate. Its previous owner left it in a box while software updates passed it by. When I came in possession of it, I used rooting, custom ROMs, and flashing to update it to more useful firmwares. I mainly stuck to CM 7, 9, and 10. Eventually I fell victim to that "ICS Encryption Unsuccessful" error and clicked reset, triggering a period of bootloop. I've since fixed the bootloop issue but I still can't get my phone to boot to any firmware. Over the past year, I've been trying all sorts of things to get my phone to work again and I don't know if I've made the problem worse or not. I can get my phone to boot the At&t screen, download mode, and whatever recovery kernel I'm on at the time, but nothing more. I don't even think I have a ROM installed anymore.
What I've tried:
several Odin One-clicks
Heimdall One-click unbrick
Partitioning my external sd card to act as an internal one
ADB sideload
ADB push and install zip from sd card
The errors I run into the most are the "can't mount sd card" ones when I'm trying to flash a custom ROM in recovery. I guess my internal sd is corrupted somehow? Is there a way for me to fix this mess?
Click to expand...
Click to collapse
sd card issues are usually due to kernel, have you tried flashing a custom one to boot in recovery?
If your internal is dying, partitioning an external sd should work but since it's still not fully booting, I feel like that's not the issue. I had that happen to mine, tried many Odin and Heimdall, when finally one Heimdall worked (after like 10-15 different attempts). Shortly after my internal died though.
So I would start by flashing a kernel with Odin 1.7, see if you can boot in recovery (always took me a few attempts to get it). From there you can flash a custom ROM (I always suggest GamerzROM for the cappy but really it's personal preference). Otherwise, your 2nd option is bashing your head on Odin/Heimdall one-clicks lol
PS.: Just came across this if all else fails: http://forum.xda-developers.com/showpost.php?p=61479845&postcount=58
I have this exact same issue... Thank god I'm not alone! I wondered what that stupid "encryption failed' message was all about.
So I've done just about everything the above has done, except the problem is I continue to get a boot loop. The ODIN one-clicks all boot loop. Ive been able to install a custom kernel and CWM, and surprisingly my internal storage is still accessible, but when I try to install the CM9 that's on there it freezes at "opening update package".
So, stuck between a rock and a hard place. I can't put any other ROM's on the internal storage because I have no way of accessing it. Therefore I have to rely on a ODIN one-click. All of which boot loop or just fail outright. Is there a way to access the internal storage without fully booting android?

Infinite bootloop on Cyanogen modded S3 Mini... help!

I'm a complete newbie to android phone modding, and I was really proud of myself when I was able to install the Cyanogen 12.1 and Google Apps onto my Samsung S3 Mini. However, I made the mistake of trying to put my work email on it, which requires that my phone be encrypted. Well, I guess the encryption and rooted phone didn't want to play nice together, so I got the error message that my phone would be factory reset. Boo! Well, it got worse. Instead of a factory reset, my rooted phone now is stuck in what I have now learned is called a bootloop. Basically I turn my phone on, and the Cyanogen start screen (with the text "TEAMWIN") just infinitely flashes on the screen until I pull the battery.
I have tried using Odin 3.07 and cm12.1_golden.nova.20160210.ODIN_TWRP.tar.md5. I do the three button system boot, connect the usb, run Odin, get the phone recognized, and then install the .md5 in the PDA section of Odin. It tells me that it succeeded, but when I restart my phone it's still the same bootloop. I also tried swearing, but that didn't help either.
Has anyone else out there had experience with Cyanogen and this particular error? I would love to get this phone working again... preferably with either a Lollipop version of android or back to Cyanogen 12.1.
Any info would be greatly appreciated! Thanks everyone.
So I've got an update if anyone's interested... I can't call it progress, but it's a different problem now.
I was able to download and use Odin to do what was shown on this link: http://forum.xda-developers.com/showthread.php?t=2122548&highlight=root
Everything worked in Odin, the phone rebooted, and went to the Team Win Recovery Project diagnostics screen, rebooted again, and then to the samsung logo. However, it immediately goes to the "Encryption Failed" error screen, and the only option is to 'reset device'. Of course, doing this just reboots the phone and it then has the Team Win loading screen, Team Win Recovery Project diags screen, Samsung logo, and back to the 'Encryption Failed' screen again. So now I have a new infinite loop to solve. *sigh*
any thoughts?
Have you been able to get into TWRP? If you are, maybe you could wipe everything from there and flash the recovery version of your ROM.
I was able to put the stock bootloader onto the phone using Odin, download the original tar from here: http://live.samsung-updates.com/index.php?device=GT-I8190, then used the stock bootloader to install it from the sd card. Everything went fine, but now when I boot the phone it just hangs on the Samsung Galaxy S3 mini GT-i18190 start screen indefinitely. Is this progress, or have I created a new problem now?
You're playing around with heavy stuff. I won't recommend using an upgrade flash (CM over Odin) as an full flash. Please try flashing a stock image.
If you did something wrong to the partitioning, then it's likely to not allow you to do a successfull factory reset. Maybe you can try re-flashing a stock Odin image with PIT repartitioning.
Remember to try to backup the EFS folder, doing that kind of flash might wipe it.

Should I continue to try unbrick (soft brick) my phone (GT-S5570; Galaxy Mini)??

Galaxy Mini; GT-S5570
2.3.5
Gingerbread.XWKS7
While trying to flash an android mod via SD I managed to soft-brick my phone. I skipped a step or two (ROM backup and data wipe) and ended up with a phone stuck in a bootloop. I managed to flash CWM recovery v6.0.4.6. Since then I have tried to flash any and all ROMS I can find that have been developed for the GTS5570. Some of the ROMs have installed okay, some have failed or aborted. The only difference now is that the phone boots straight into recovery.
Tried to do this via laptop (using Linux Mint and Windows 10) and the phone was not recognised via usb, even with drivers.
I don't want to just give up, but I reckon I've come to that point. That is unless there is something I have overlooked.
Any and all advice welcome.
Thanks in advanced.

Categories

Resources