Database Develop

Have I bricked my N7000 / bootloop / COM port failure?

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.

BRICKED? when changing from N920G back to N920i

Hi all
I think I may have completely effed my n920i.
Backstory :
Few months back i updated my phone from N920i 5.1.1 to N920G 6.0.1 using the 4 files from the MEGA link.
Everything was working good for the past few months, all the regular OTA updates went smoothly.
Over the last couple of weeks I noticed my mobile data was having issues (dropping out, only connecting 3g etc) so I decided it was time to switch back to N920i 6.0.1 since it has now been released in Australia.
I followed these instructions: http://forum.xda-developers.com/note5/general/flash-to-n920i-n920g-bl-modem-reverting-t3367903 using Odin3 v3.10.7
However i did not wipe cache, factory reset, etc and during the first attempt it failed. I was still able to restart the phone at that point. i rebooted into download mode and tried again. This time it failed but now I cannot reboot into recovery, flash any other ROMs using Odin as it keeps failing or turn it off.
The only options are to enter download mode or the blue screen saying something happened during the update and to use emergency smart switch. I can't even turn the phone off.
I have tried emergency smart switch using my model and SN and it still does not work. It'll download and when it goes to install it fails.
I've tried flashing the 4 file N920i 5.1.1 firmware with no luck as well.
Sorry for the long read but I wanted to cover the steps I took. Any guidance would be greatly appreciated.

bump.

Okay so the plan here is to install a recovery and wipe everything, then try flashing an original ROM in Odin
1. Flash TWRP Recovery and don't let the phone restart, immediately hold buttons for restart recovery
2. If this doesn't work, hold the buttons for restart in Download Mode. Once in DL mode, power off and quickly hold buttons for recovery. You may have to reflash TWRP if this doesn't work
3. Once in TWRP click on Wipe, Advanced and wipe Dalvik, System, Cache.
4. Reboot into Download Mode and try flashing ROM with Odin

thanks for providing the instructions however the moment i try to flash TWRP Recovery it fails in odin and this is what it says on my phone's screen.

Galaxy Tab S2 8.0 Stuck In Bootloop

Hello,
Been given a couple of ex retail demo tablets to flash, both of them Tab S2's. First one went fine and dandy and is updated now with latest samsung OS with no knox issues.
The second however updated fine but wouldn't reset due to MDM (Brilliant.... knox being a tw##). So after a couple of resets an kicking knox into life it has now put the device into a starting screen bootloop. Trying to reflash using odin hasn't worked and all I can access is odin mode and the reboot/factory reset screen.
Factory reset won't work as it's coming up saying MDM not allowed blah blah.
Help would be greatly appreciated on this one.
Thanks
X

Ok managed to fix my own problem. Flashed over TWRP and used auto root using odin.
Once in there I used TWRP to format the device removing the encryption, then rebooted. Low and behold samsung welcome screen.
Once I knew the device was fine went back into odin and reflashed the OEM firmware back on and factory reset the device.
Don't understand why 3 out of the 4 devices I was given reset out of retail demo mode fine with odin but this one was a c##t.
Thanks
X

SM-A305G Boot Loop, trying to flash stock firmware

I made the mistake of flashing the wrong version of TWRP using Heimdall, causing the device to get caught in a boot loop. Initially, I couldn't enter recovery or download mode to re-flash the firmware, but after disconnecting the battery to shutdown I was able to get back into download mode and flash a stock ROM (downloaded from SamFirm).
After flashing the ROM (now using Odin) and auto rebooting, I get the installing software update screen with a loading symbol (for a few seconds), followed by a boot loop (Samsung screen -> Knox warning -> reboot -> repeat).
- Power cycling the device boots back into recovery mode.
- "Reboot device" option from recovery mode enters the boot loop.
- "Reboot to bootloader" option reboots into download mode (I'm not sure why)
- Wiping the cache / factory reset between reboots seems to have no result
The phone is an unlocked SM-A305G/DS from Amazon, so I'm not confident I have the carrier version correct. The only record of the CSC version I had before was the .pit file I extracted through Heimdall before flashing the wrong firmware. It contained the string "TPA", so that's my current best guess. I have tried firmwares for TPA, CHE, and CHO but with the same results.
Any ideas what might be wrong? I imagine the device isn't hard bricked, so I don't know what else could have went wrong. Kind of a newbie when it comes to android firmware, but I have some technical background, so let me know if there's some more things I can try or if more information might be needed to debug this issue.
Some more specific questions:
1. Does the carrier code matching the device matter? If so, is there a way to find the original CSC from IMEI on an unlocked/no warranty phone? The few websites I tried don't appear to be able to get that info.
2. Is there any way to access the logs from the last normal boot attempt? (Recovery mode only appears to keep logs for itself, not normal boot)
3. Could tripping Knox somehow be the problem? I didn't think it had any repercussions except voiding the warranty (which the device didn't come with)....
4. Can Samsung support somehow help me find my CSC/correct firmware even if I don't have a warranty?

Solved
Posting solution here just in case someone makes the same mistake,
I realized that I neglected to post the information displayed in download mode, most importantly:
`KG State: Prenormal`
Googling that, I found that this might be caused because of a mismatch between my SIM card region and the installed firmware region. So I removed my SIM card, re-flashed the latest stock firmware again, and it booted :laugh:
Also, download mode displayed the correct CSC code regardless of installed firmware (I installed CHE firmware and it still displayed TPA), though I'm not sure if that's consistent across devices.

Note 10 lite ldu bootloop

hello i wanted to install a stock rom on my note 10 lite live demo unit (ldu), once the flash ended via odin is displayed (pass) but when i restart the phone i get stuck on the samsung logo, i have already tried to reset and clear the cache it does not change anything, I flash the region of my region (XEF) in January and March but nothing works. Help me please

Hihi. said:
hello i wanted to install a stock rom on my note 10 lite live demo unit (ldu), once the flash ended via odin is displayed (pass) but when i restart the phone i get stuck on the samsung logo, i have already tried to reset and clear the cache it does not change anything, I flash the region of my region (XEF) in January and March but nothing works. Help me please
Click to expand...
Click to collapse
I'm note sure if any of this will work, but this is what I would try:
Redownload the correct stock ROM, making sure it matches the specific hardware (Samsung Exynos vs Qualcomm). Additionally, check the checksum to make sure the download wasn't corrupted.
Flash everything again using Odin, making sure to include all partitions (BL, AP, CRC, etc.) in their correct slots.
If that doesn't work, clear data and reboot.
If that doesn't work, retry with only the AP (somehow does things differently with the partition table).
If that doesn't work, then I'm out of ideas. Maybe some of the more advanced features of Odin could help, but I'm not sure how those work, and you can really mess up your device with them.
Note that the first boot after a full wipe will take significantly longer than normal, as a lot of preparations need to be done. If it passed the bootloader to the second Samsung logo, give it around 10-15 minutes to be sure it's not just taking long.