To start, I was using I9000XXJP2 firmware on an unlocked samsung I9000 from Bell. I installed a lagfix a few days ago and everything was working fine. The phone was really slow and freezing a lot today so I decided to restart. Ever since then, the phone is stuck on the Samsung S screen (not the one with the triangle). I can get into download mode just fine and i tried reflashing XXJP2 using odin back onto the phone. Odin does everything fine up until i see a blue 'reset' on odin and the phone is in recover mode with the options asking for me to restart the system etc. I restored to factory settings from there and even cleared the cache and restarted but it is still stuck on that "S" screen at startup. Odin only says "pass" once the phone is disconnected. So as of yet I haven't been able to flash a working ROM back on the phone. If you have any ideas as to which ROM i should try, if you could place a link with that, I would be very grateful.
I've had this problem myself a couple of times (just happened today in fact).
Boot into recovery mode (vol-up, home & power). Do you see any error messages in yellow under the menu?
I was unsuccessful at reflashing any of the Froyo firmwares so I reverted back to the last official 2.1 firmware from Bell JH2. Since I was coming from a 512 pit firmware, I didn't repartition or specify a pit file. This ended up working for me. I've since flashed to JK3 and am about to go back to JPU.
Reply:
I actually do see an error message E:can't mount /dev/block/mmcblk0p1, Can't mount SD card.
I should mention that Im using the unlocked bell phone on fido. Will i lose the unlock if i downgrade? Also, if you could point me to the site where i can download bell firmware, that would be awesome. I went to samfirmware.com and they dont have canadian versions there.
Unless one of the pros comes by and says otherwise, I understand that's the error indicating internal sdcard issues.
However... if the thing is dead, you can't hurt it more by trying some fixes
You can get the official and unofficial Bell firmwares from samfirmware.com, you just have to look in the US section. You want the firmwares starting with "i9000UG". Here's direct download links for you:
JH2 (official 2.1)
http://www.multiupload.com/ZNBT2RY5Y0
JK3 (unofficial 2.2)
http://www.multiupload.com/WTZGSKJGPF
JK4 (official 2.2)
I've heard people flashing this via CWM but I haven't see the files.
Also, I've seen references to people saying their phones begin working again after this error msg after they've left the battery hour for hours.
Let us know how things go.
Reply:
No go. When i flash to 2.1, it just shows the "S" screen and turns off. When i flash to 2.2, does the same thing as my first post. I still can get to the download screen through all of this so I hope its not messed up too bad.
I tried several times this afternoon before it worked including clearing data/cache.
Although, I had a different error message so you might be SOL in the end.
called samsung
So I called samsung this morning and they basically said they won't repair it because Bell handles repairs. Since I dont have a bell account, I can't get it repaired. I keep reading on forums that if you can get into the download mode, if you see the battery icon when you plug the phone in, its not totally bricked so i still have hope yet everything I've tried doesn't work. I tried to adb into the phone in recovery mode and it detects it but says I dont have permissions to push files onto the phone. If anyone can tell me what possibly went wrong and if it is fixable, how, that'd be awesome because right now this is a very expensive paperweight.
Hey all i apologize in advance im really new to all this stuff. I have a d950 it was rooted (cwm kept saying root was lost) and im using the stock ROM. The other day i got an update notification on my phone i kept ignoring it for a few days and one day i turn my phone over and its in CWM. I tried to use the restores that i had created with no luck and somehow ended up erasing my phone as in all the restores and anything else is gone. I have been lurking here for about a week trying different things the phone wont boot to any mode except CWM. First the drivers would not work with the phone ended up having to modify the google usb drivers since the lg ones would not work. I was then able to push stock firmware that i found into the phone but when i try to install it says installation aborted after about a second. I have read that its more then likely because it isnt compatible with my phone but it said it was for the d950. I then tried to enter fastboot with no luck just still cycling between the LG logo or CWM. At this point any help would be appreciated before i give up and have to get another phone.
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
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.
My friend had this i9000 and he said that at one point it just wouldn't boot, just kept doing a boot loop. He has pictures on there he wanted to recover. I flashed CWM and managed to mount it and copy everything off the device. Now I want to try and get it working for him but for some reason, flashing the phone just isn't working. I've also tried flashing with 3 different pit files, but there's just no success. All I can say is the device is was using the official ROM and is locked to the UK T-Mobile carrier.
Is anyone able to help?
Former Samsung user who just jumped ship....
Earlier today I unlocked my P20 Pro CLT-L04 (Canada) and installed TWRP, everything seemed fine, but when I rebooted it just keeps going back into TWRP?! I can't boot my phone into the rom.
I've tried re-locking my phone and unlocking, which the phone tries to factory reset EMUI, but it never works, it just keeps failing. I've tried downloading the stock image with EMUI recovery on my phone, but that keeps failing.
My phone won't connect to any PC to transfer files, my internal memory doesn't seem to mount and I've never pushed files over adb.
Can anyone please help?!