Develop Bugs

[Q] Problem while flashing new ROM.

Okay, this is my third time flashing a new ROM to my android device. As always I entered Clockwork mod Recovery. I wiped data and cache, done a system backup and tried to flash Rootbox 4.2 for Galaxy SIII (Yeah I know I'm stupid, don't know if it'll work just was giving it a shot because Rootbox doesn't have support for Galaxy W I guess, or I missed it) It gave me a status 7 error and aborted the installation. I tried to reboot my phone but I couldn't open it. It can go into the phones recovery mod (not CWR) but I can't do anything in there too, it says "Downloading now" and just starts downloading something which takes forever.
I seriously have no idea what to do (Yeah, a total noob here) so anyone can please help me?
Edit: Okay I found that it's called ODIN mode and when I click volume up it starts downloading something but it takes long so I should wait.
Edit 2: I realized I need Odin downloader to flash firmware but I DON'T have any connection between my phone/laptop. And there's no slot to put my sd card in and transfer files so I can't transfer anything. I tried to open it up in safe mode and normally lots of times but no luck.​

Please help me.

You have to connect via usb cabel
And install Odin on your PC.
Then flash a Stockrom in it.
Sent from my potato

But I can't because usb debugging is not enabled and I can't boot the phone. The usb just doesn't work, it does not charge my phone or get recognized by my laptop.

Nemesis Xanity said:
But I can't because usb debugging is not enabled and I can't boot the phone. The usb just doesn't work, it does not charge my phone or get recognized by my laptop.
Click to expand...
Click to collapse
You have to boot the phone on download mode (volume down + home button) and connect it in your laptop. Then, use Odin's tutorial to flash stock rom.

you better install samsung USB driver first

Nemesis Xanity said:
Okay, this is my third time flashing a new ROM to my android device. As always I entered Clockwork mod Recovery. I wiped data and cache, done a system backup and tried to flash Rootbox 4.2 for Galaxy SIII (Yeah I know I'm stupid, don't know if it'll work just was giving it a shot because Rootbox doesn't have support for Galaxy W I guess, or I missed it) It gave me a status 7 error and aborted the installation. I tried to reboot my phone but I couldn't open it. It can go into the phones recovery mod (not CWR) but I can't do anything in there too, it says "Downloading now" and just starts downloading something which takes forever.
I seriously have no idea what to do (Yeah, a total noob here) so anyone can please help me?
Edit: Okay I found that it's called ODIN mode and when I click volume up it starts downloading something but it takes long so I should wait.
Edit 2: I realized I need Odin downloader to flash firmware but I DON'T have any connection between my phone/laptop. And there's no slot to put my sd card in and transfer files so I can't transfer anything. I tried to open it up in safe mode and normally lots of times but no luck.​
Click to expand...
Click to collapse
this might help

Samsung S3 (tmo) soft bricked, encrypted, USB debugging off

Hi,
Summary: Was running Cyanogenmod 10.2.0 and tried to update to 10.2.1. Phone won't boot. Using CWM recovery 6.0.4.3. Factory Reset reports that it can't mount / clear /data (due to encryption?). Can get phone into CWM recovery and Download mode. Haven't been able to successfully connect to PC (ADB or Odin) even though I have samsung drivers.
I do have an unencrypted SD card in the phone so my normal way of flashing is to connect SD card to PC, download, then in CWM recovery to install ZIP from SD card.
Looking to get into any good state - Cyanogenmod 10.2.1, or 10.2.0, or heck go back to stock.
**** I think the answer might be use ODIN and flash back to stock, I see some guides but haven't been able to get ODIN to "see" my phone *****
Details
I had downloaded Cyanogenmod update to phone using "About this phone" menu and when I tried to "Install it" from that window the machine booted into recovery, immediately failed, and rebooted. The phone is encrypted (work requires this) and I discovered Cyanogenmod saves the download to encrypted phone storage and CWM recovery doesn't support encryption.
Downloaded 10.2.1 to my SD card and flashed it. (no back-up, no wiping of cache). Installed successfully, reboot asked me for my encryption password, Android optimized apps, rebooted, encryption password, then blue spinner spins forever.
From here I started my troubleshooting:
- I flashed back to 10.2.0 then flashed Gapps again, no change.
- Reading about boot.img I installed ADB and SDK Manager and tried connecting and flashing boot.img. ADB devices shows up empty. I have installed Samsung drivers.
- Researching going back to Stock points me to installed Triangle to reset my custom ROM count - but I can't boot.
Thanks in advance.
Matt

[Solved] This is for anyone who happens to read this wondering if their phone is screwed. Relax! If you can get into Download mode and Odin can see your phone, you'll be o.k.
Turns out the machine and cable you use do matter. I tried for days connecting using my MAC running Windows 7 Virtual Machine. Once I switched to my Win7 laptop and used the original Samsung cable things starting working out more smoothly.
Steps:
1) Get Odin (mine was 3.09) and run as admin. If you see an error in Korean it's because you have to unzip the entire Odin folder.
2) Get stock firmware for t-mobile. There's only 1 firmware file, I didn't need a PIT nor a specific recovery step. The t-mobile firmware includes everything I needed. Flashing failed in Odin saying Complete Write failure. This had me stumped for hours and hours. When I switched to stock cable and Win7 laptop it succeeded. I never had to check Nand erase all or repartitian (almost did in desparation though). Flash took about 10 minutes but eventually PASSED.
3) However, when it rebooted it asked for encryption key and my old one didn't work. Turns out their are more steps. This scared me.
4) Reboot into recovery (up, home, power) which gave a bunch of scary error messages. Actually those listed at the bottom in http://forum.xda-developers.com/showthread.php?t=1840030.
5) Factory Reset then Wipe Cache
6) Reboot
Now I'm back at stock and breathing a sigh of relief. Unclear if I'll ROM back to Cyanogenmod.
I spent hours and hours reading discussions and going down one dead end after another. I'd say it was like looking for a needle in a haystack but it was the complete opposite. It was like looking for a specific needle in a sea of needles. Every search query yielding tantilizing results and a plethora of step by step guides that ultimately didn't work. A very frustrating experience all around. Good luck to anyone who reads this.

Hi Matt
Similar thing happened to me last night. I am/was using Omni-Nightly build. I plugged it in to the charger before bed, and it rebooted, saying upon reboot - "Encryption Failed" and saying the only way to recover would be to wipe the machine and start again, it then rebooted and all I get is the Samsung boot screen.
Tried rebooting, wiping, everything, Odin, Android Toolkit, nothing works. It shows up on my Linux PCs but not accessible, but not windows at all.

note 2 not connecting with odin

I have a note 2 its not rooted one day my phone just stops working i change the battery but now the software is stuck on the samsung logo or when in charger stuck on a battery icon, i managed to get it in download mode but odin now doesnt recognize it.
im not sure if there is certain version of odin i should use with my note 2 n7100.
summing it up i want odin to recognize my phone so that i would flash kitkat on it.

ento bdan :cyclops:

Try more version of Odin and another USB port

Try Odin v3.09 https://mega.co.nz/#!UdRRyCAT!H4FyVxYynNWvXqRNmnpMGQRCP-dG3uykgP2pT4rh8Ek

I always using Odin v3.07 for my note 2 but it doesn't make any change.
First of all, does the pc recognise your device?
When you plug in your device, dies the pc make a sound?
Does it say something like installing drivers csc, serial, and many other things?
If one of this anwsers is yes; try this:
I tink there's a problem with your drivers.
1. Instal Samsung kies 3 when your note is on android 4.3 or higher, else just Kies
2. Open kies (3)
3. Search in the dropdown menus somewhere above the screen for "(re)install drivers" (I think it was in one of the last menus)
4. Reinstall the drivers
5. Close Samsung Kies
6. Open Odin
7. Put your Galaxy Note 2 in download mode and then connect to the pc
8. Choose in the tab "PDA" what you want to flash with Odin
9. Wait a while, a bleu box will appear with COM and some numbers. When this appears your device is recognised and you can start flashing
If this doesn't work This will help too, BUT YOU WILL LOSE ALL YOUR DATA.
1. Go to recovery mode by holding volume key up + home + power.
2. Choose factory reset. (It will wipe all your data)
3. After the factory reset, connect your phone to the pc and see if it works
4. If It still won't connect redo my first steps (those with Kies)
If it still doesn't work, I can't help you

Galaxy Note II (GT-N7100) Resuscitation

Its been a long time since I booted my Galaxy Note-II (GT-N7100) as I use an iPhone and Nexus 5 as my daily drivers.
The phone wont boot past the Samsung Galaxy Note II GT-N7100 logo. I am able to access the recovery and download mode as well, and I have flashed the latest stock rom from Sammobile using the Odin. The flashing was successful. however the phone doesn't boot past the logo. Also the phone will not power up unless connected to a PC, it wont power up even when connected to a charger and will immediately shut down when the USB cable is disconnected from the PC. I flashed TWRP 3.0.2 Custom Recovery using the Odin and tried installing CM 13 based Rom through the mem card, however the log reads patching image unconditionally and also that "Failed to mount /system" (invalid argument). The phone when restarted into recovery can no longer mount the /system partition. However on flashing the stock rom using Odin, the /system partition is available for mounting. The recovery log also shows MTP enabled, but my PC doesn't detect the phone when in recovery, it only detects the phone in Download mode. I have the Samsung drivers installed. Since the phone is not being detected in recovery I am unable to use the adb.
I am out of ideas and request your suggestions other than approaching a service centre.
If I can somehow access the phone via ADB, I might be able to check the memory partitions for corrupt units, and possibly create a custom PIT file to repartition and suit the available memory units.

Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?

audit13 said:
Try this: open Odin, uncheck everything except f.reset time. Connect phone and flash stock ROM. When you see the word reset in the status window, remove USB cable, remove battery for a few seconds, replace battery, immediately boot the phone into recovery mode, factory wipe, and boot the phone.
Could the battery be defective or dead?
Click to expand...
Click to collapse
Thanks a lot.
Tried your method and finally the phone has booted into the OS.
Had to replace the battery with another spare one in the process.
However the phone is still not being detected by the PC unless it's in Fastboot/ Download mode.

When connected to a computer, does anything appear on the phone screen? If you're using Windows, nothing new appears in device manager?

sorry to jump in this thread but i am having a similar problem
my completely stock tmobile note 2 is stuck on the samsung logo
i have never flashed it or done anything to it
my phone was working really slow, freezing up and battery draining fast
so i did a hard reset and it fixed the problem of running slow and freezing up for a week or so but battery drained fast
so i bought a replacement battery from ebay and installed it and the next day i restarted my phone and it froze on the samsung logo
i tried turning it off and on and still the same thing
any suggestions or should i start a new thread?
fyi i am a noob

Samsung GT-N5110 - Stuck in Boot Loop, Can't flash Due To "Write Error!!"

I have a Samsung Note 8 GT-N5110 (WiFi only) that is stuck at the Samsung logo.
This started after there was an attempt to flash a non-stock firmware and the device powered off before it was done.
When I attempt to enter Recovery Mode (Volume Up + Home + Power) it displays "Write Fail!" in upper left of the screen.
I am able to enter "Download Mode", so I've tried flashing a stock firmware using Odin.
I've tried both a One-Click recovery based on ODIN3 v1.81 and also tried Odin3 v3.12.10.
Each time, Odin fails, with a message:
write fail!!
SW REV. CHECK FAIL. DEVICE:2, BINARY:1
I've tried various versions of firmware, and nothing seems to work.
I've tried disconnecting the battery for a minute or so, and it still fails.
Any ideas what else I can try?
I have screen shots and detailed logs of what I've been getting, if that helps.
Thanks!

Believe it or not, I still have this device, and have not been able to get it to work!
So, I'll just revive this zombie post more than 2 years later, and see if anyone has any idea on what to do.
I'm in the fourth (fifth? sixth?) week of corona-quarrantine, so plenty of time to look into this!

The tablet needs more power than the computer's USB port can deliver. Thus, it will slowly drain the battery while connected to the computer and working via ADB, Odin or Heimdall. Seems like that has been the case in your earlier attempt, resulting in a corrupt flash memory. I can't tell if it's really defective or just corrupt and in need of formatting.
I'd try to:
1) Charge the battery
2) Copy LineageOS to the MicroSD card
3) Boot into download mode and install TWRP only via Odin or Heimdall. If this works,
4) Boot into Recovery (TWRP, not the stock one!), connect the charger to keep it powered and go from there (wipe and repair the internal flash, install LineageOS)
If this doesn't work, try if you can find any service functions in Odin or Heimdall to wipe and repair the internal flash.
Good Luck!
Ektus.

Hi Ektus,
Thanks for your help!
I will try as you suggested, and see what happens.
I'll let you know how I do.
Thanks!

I had similar problem. What I did is just change the USB cable to new.