Database Develop

[Q] Stuck on ATT World Phone, Odin not working

Tried to replace the lock screen using the MOD from the 'JI6 MODS' thread,
and now my phone is stuck at the Att world phone screen.
I can reboot into recovery, but that doesn't help me. When I try to reinstall packages it says:
'E: failed to open /mnt/internal_sd/update.zip (no such file or directory)
E: signature verification failed.
Installation aborted. '
I tried to push the update.zip file it needs to my internal sd, but it said permission denied.
Sometimes I can access my phone via ADB but it's only for a few moments while its loading the 'ATT world phone' screen but not for very long. I tried to push the original odex file to /system/framework/ but got permission denied.
I can get into download mode but when in Odin it always fails during file analysis.
I thought for sure that Odin would be able to fix this, but no luck.
My phone was running
Froyo JI6 rooted, no lag fix or anything. The only MOD I was running was Fightspits circle battery MOD.
Does anyone know anything I could try? I'm at the point where i'd try just about anything..
Please and Thank you!

Wrong section. topost your question

Put your phone into download mode (open the ODIN one click to stock, remove battery, remove SIM, replace battery,hold down both volume buttons, plug phone into usb while still holding volume keys, wait for the pic of an android with shovel to appear on the phones screen, click start) this should put you back to stock.
Its seems though that you might a kernel issue. You might just want to put phone into download mode and using the standard ODIN flash xcalibers reoriented kernel with 2e recovery.
The message you are getting in recovery is because you have the standard froyo kernel wich does not support self-signed .zip files.
Hope this helps.
Sent from my GT-I9000 using XDA App

Thanks for the reply maginator!
I actually got home from work today and my roomate had it fixed.
He booted into recovery then cleared the cache and user data, and THEN
used odin to flash it back to stock 2.1
Very happy to have my cappy back!

Yeah i got the same problem but mine wont go into download mode i get the att world phone, then the att wold phone again and then it goes into recovery <2a>....any advice could really use it.

[Q] A challenging suspected brick case - request for help

Hello Guys
I have a challenging, near brick case.
I have an SGS I9000 I bought from a provider in Singapore. I had a row of misfortune with this device and it was DOA with receiver problem. It was sent twice to Samsung labs and eventually they replaced most of its internals.
When the device eventually returned from the labs it had a 2.1 ROM version of the local provider (IDEA) that was locked for the 3-button maneuver.
I have read all that was written about it, decided to get a decent JIG that work like magic and bring me easily back to DOWNLOAD mode. I decided to install an alternative ROM of my country that had a clear good installation instructions: PilotX 3.0. When this did not work I tired several others, all from ODIN only. In general what happens:
1) After the ODIN restarts the application the ROM goes up and gets stuck after the S opening screen. The device stays black with buttons light on and vibrates every few secs.
2) After the ODIN reset there are messages on the external environment that says E: cant mound /dev/block1st/st110 or 111 (invalid argument)
or: copy dbdata_media cant mound ... copy media content failed
3) I did manage to get to recovery mode despite the errors from the ODIN installation and managed to install from SD card ZIP files the PilotX ROM. It did not give any error messages but it got stuck the eventually the same way.
4) The only ROM I managed to install and actually get running was the local ORANGE ROM. This too did not recognize my SIM and did not solve the 3-button issue.
I am now with a semi bricked device, luckily returning to Download mode easily thanks to the JIG.
Any suggestions guys ?
Thanks
B

You need to flash a full rom in Odin (one with 3 files) and repartition checked. I normally use xxjpc for this purpose.
Sent from my GT-I9000 using XDA App

update
I managed to intall an ACLAIR 2.1 ROM with ODIN that actually works.
I think using a proper PIT did the trick. not sure.
Still:
1) I did get to see that when rebooting there was still a red error message saying something like: "can not access system syn ...."
2) I am still stuck with a phone that refuses to do the 3-button Recovery maneuver.
I guess I am back to square one, searching on the 3-button fix threads for a proper solution. Any good suggestions or boosts. I am after a sleepless night
Thanks

[Q] Difficult "soft" brick

Hey, guys, long time lurker and first time posting here.
So, I managed to screw up my S4 Active (i9295, international version) somehow and I am out of things to try now.
I have been testing lots of roms and have always been successful using Odin. Never had any problems with it, got quite familiar with the notions of it all.
So tonight I tried to go back to the original stock rom of my phone, and I got a FAIL error at Odin. After that, I just could not flash any other ROM on it for the life of me. I tried the ROM I had just before, fail. Tried a ROM I used some time ago, fail. It seems it fails to flash any rom to it, it always giver an error at the very end of the process.
I CAN:
- flash CWM to it - it works normal
- flash root to it - although i dont really see the point
- access "odin"/download mode
- access cwm recovery
I CAN'T:
- manage to flash stock rom to it
- it always fails at the very end, right after the modem.bin
- Complete(Write) Operation Failed
I already tried:
- changing usb ports
- 3 different stock roms downloaded from sammobile
- closing every single app remotely similar to kies on windows
- reinstalling the samsung android drivers
- removing sim card and external sd card
- wipe data/cache prior to flashing
I'm running out of ideas here. Anyone got any solution I might have skipped?
Thanks and sorry for the long post.

Oh, I also tried getting the firmware using KIES.
It doesn't recognize the phone (just says "Connecting") and it doesn't show on the list for the Emergency firmware recovery.
I also tried the "Firmware upgrade and initilazation" mode, which I have used in the past.
It downloads the firmware, goes to the next step, but when it gets to the part where it sould instruct me to put the phone in download mode, it just shows a warning completely in japanese (probably korean actually, considering... thanks, Samsung! :good: ) and it stops the whole thing.

How I un-soft bricked my Samsung SGH-T679 and restored recovery mode

By soft bricked, in my situation, I mean that the only mode I could successfully enter on my SGH-T679 was ODIN download. Recovery and normal boot both locked up no matter how long the phone was allowed to run. Or it reported that firmware failed and to use Kies but Kies failed to recognize the phone.
How I bricked it
I was given one of those fitness wrist bands for Xmas, but it's from a startup company and their app only works in 4.3 or higher. So I got adventurous and tried CM 10.2. I got CM to run but couldn't get Google services to work. I finally gave up and started to revert to stock. When I had my first problem at 2am, I should have gone to bed and finished after a good night's sleep because I soft bricked it. At first, I was running flashes from my internal SD card and could only get it to flip between stock recovery and CWM recovery, it wouldn't take full stock flash. Finally, one CWM recovery flash failed and my recovery mode got stuck so it only showed the hat and gear icon and at the bottom of the screen it said "CWM 6.etc..." and never went further. But I could still get to ODIN download mode.
And that's when I got really stupid. I messed with things I didn't understand in ODIN. Did you know that if you try to run ODIN Multidownloader 4.43 using the "Debug Only" and "MD5 Ram Check" options that you can fully soft brick a T679? If allowed to run for a while (10-20 minutes is sufficient), then after forcing the phone to restart, it will result in the screen about firmware failed please use Kies for recovery (but then Kies can't see the phone because the recovery is bricked).
Long story short, after hours of trying this and that, I finally found a webpage that said you can download the CWM recovery via ODIN. That would have worked if I hadn't gotten the wrong version (resulting in lots of screen flickering), but it proved to me that I might be able to fix the recovery using ODIN.
Here's the walk thru of how I restored my stock recovery and ultimately got back to stock ROM:
Software required:
A zip software that can handle TAR files (I used PeaZip)
Go to this wiki http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G and scroll down to "Flash to stock via ODIN", you need the software discussed and read thru the "STEPS" section just below that
You can first try using ODIN as described in the wiki. But if that doesn't work, you can try what I did...
Restoring stock recovery
If you haven't already, unzip the uvlg3.odin.zip file that you got via the wiki link above
From the .tar file that was in the zip, extract recovery.img and then put it inside a new TAR file (call it something easy like recovery.tar) (depending on your zip program, use "add", do not use "convert", you need the .img file inside the .tar file)
Refer to the wiki link above for more help on ODIN but basic steps are:
- Run ODIN as admin (not sure if it matters if you disable auto-protect on your antivirus software but I followed that recommendation)
- Using "OPS" button, select the Ancora.ops file that you extracted from the zip file
- You may have to recheck the "One Package" box to be able to then select your recovery.tar using "One Package" button
- Press "Start" and cross your fingers
You hopefully have now restored the stock recovery to your phone.
Further steps
I went a step further. I extracted the entire .tar file (not just the recovery image) and put each item into its own new .tar file. I used ODIN to individually load each item. I did first try to load the full file but I now think mine was failing to load system (which is pretty critical, especially if you followed directions that included "format /system"). (Note, the preload file might not work, didn't for me ; I found several posts about it and the general answer was to ignore it.) One trick to this is to watch and push the Vol Down and Home buttons when ODIN reboots the phone so you go back into download mode. Oh, and change the reset time to 30 seconds (I tried 1 but ODIN changed it to 30) so you don't wait as long on "reset". I'm not sure if it would have made my first normal boot go faster if I'd gone to recovery mode between ODIN downloads. I do know it took my phone several minutes on the first normal boot. I'm sure those of you who have bricked phones can appreciate the feeling of waiting for the stupid startup jingle and the relief when it actually plays.
Oh, and save yourself some bother by rebooting 2 or 3 times before you try to do much w/ your phone once you get back to stock ROM (or some other ROM). I was a little freaked because my wifi didn't work but after some googling, I learned Android can require a couple reboots before all services (especially wifi) load properly (which makes me wonder if I should try CM 10.2 again with more reboots... am I a glutton for punishment enough to try???).

[Q/A] phone soft bricked / can't flash with odin either

Hi everyone, I was using this forum for a long time but this is the first post I've ever written.
Let me explain my problem:
I was rooting my SM-M215F/DSN and Odin gone mad for some reason and bricked the phone. Now phone is on a loop with screen sayin "An error has occurred while updating the device software. Use the emergency recovery function." Usually I can fix this kind of situations but this time I cannot fix this and hope someone can help me with it. This was not my first ROOT but for this phone it was.
These are the things I've already tried:
1) Tried to reboot phone to download mode. After pressing Volume (-) & Power it don't let me do anything and goes back to that warning screen directly.
2) Drained all battery power to kill phone, but when I connect it to grid it goes back to that screen again.
3) Used emergency recovery with Smart Switch but get an error "SM-M215F does not support initializing"
4) Odin cannot connect to phone in this mode so it cannot turn back to stock firmware
5) Someone has told in this forum that it's another kind of download mode and use Heimdall. I've tried it and it detects the device but while downloading .pit file it gives "ERROR: Failed to access device. libusb error: -12". I am a little bit n00b on Heimdall so I gave up.
So if anyone can help I will be really appreciated. Thanks in advance.

After a real struggle I've found my own solution so need to share with community.
Tenoshare ReiBoot for Android free version let me exit from download mode.
Hope this helps.