Ok was running Axura 2.3.1.0 tried to downgrade to Modem FWare KA7 [because KB1 was very slow with data] using ODIN 1.81
Couldnt or wouldnt load it, tried to get the phone outa DL mode and into recovery mode
Apparently, it turned off while in DL mode, and now the phone wont do anything except turn off, and when trying to get it to boot up, all I see now is a picture of a cell phone dot dot yellow triangle with exclamation character dot dot and picture of computer.
phone wont go into recovery mode, done a battery pull and all suggested methods, ODIN, BayWolf's program nothing will interact with it!
Is this a soft brick or a hard one, and is there a simple way or anyway to get it to go into boot mode and turn back on?
Haven't seen this scenario in any threads Ive search thru all morning, need this phone back up ASAP. thanks!
OK were up and running starting all over AGAIN!!
OK I guess my asking for help must not have been worthy enough for reply, However, the thread right above mine labeled "HELP seriously" Had the answer I needed, It enabled me to get linked USB wise NOT DL MODE though, With BayWolfs 2.5 ToolBox, and I did a restore back to Eclair 2.1.1 Phewww! thought the phone was hosed/bricked!! Anyway BayWolfs Program did the trick! Heimdall's or ODIN 1.81 wouldnt link or respond to the phone, If this program hadn't been available, with no answers from contributors, I might've been seriously lost! Anyway I got into this delimna by trying to downgrade the KB1 modem to KA6, I think Ill try mounting it to the ex SD and flash it from there! I did as whats been read with ODIN, installed the PIT file, selected the tar file labeled KA7 , phone was in DL mode, but that's where the confusion lays with me, cause I see two different Instructions [from threads including video tutorials] on where to mount the modem file for flashing, some say no pit just the phone bar, others say must use pit but mount the modem file to the PDA bar! WTF!! Why is there NO uniform Instructions for a sure fire method that works with 0 defects, irregardless of how buggy ODIN my be? Does any one know for certain exactly how and what to do step wise with ODIN which would apply to Heimdalls program as well? I had problems flashing to Axura using BayWolfs toolbox ironically , yet it saved my ass in getting my phone un-stuck otherwise!
Anyway I still want to try other modems other than the KB1 thats with Axura 2.3.1.0 and try different modems like KA6 which was fast with Froyo 2.2 or try KA7 and try to get the speed back up, as well as the improved reception telephony and GPS wise!
Related
I'm a total noob here and to Android...well to all of this really. I've searched the forums (I swear) to find an answer elsewhere, but found only solutions based on the EVO or Experia, and neither was exactly the issue I'm facing. Here's what I did:
1.) Had total stock phone that got sluggish and lagging after installing JI5 through Kies.
2.) Factory Reset and One Click Root. Phone was noticeably snappier still with the JI5 obviously, so the reset helped that.
3.) Used Rom Manager app to make a backup
4.) Using Titanium Backup removed some of the bloatware (got sick of Slacker Radio and TelNav randomly running when I never opened either once)
5.) Went about re-downloading apps lost in the factory reset and noticed the NY Times app isn't even in the market anymore? Read in another forum about it being copy protected (even though it's free!) and therefore wont show up in the market on a rooted phone. Ugh...
6.) Start reading and trying to learn about kernals and custom Roms, Odin, and flashing...and "holy crap, I'm in way over my head".
7.) Unrooted, and still no apps.
Now I just want to get back to where I was before Installing JI5, have access to the whole market, and be able to get the JI6 OTA update. I've read the "Easiest way back to stock" thread but not sure that's going to fix the copy protected apps problem, and I'm worried that's going to screw up my GPS again (though,to be fair, it isn't that good now), and not sure what that does to my ability to get to JI6.
Guys, I know these questions are long, probably annoying, and possibly redundant. I've learned my lesson, I wanna get back to the shallow end of the pool! Can anyone help get me there?
"all the Dude ever wanted was his rug back."
After more reading, would flashing Bionix 1.7 fix all of this?
first, check to make sure your phone can enter download mode by connecting the usb cable to the phone and computer and pressing all three buttons until it resets. release the power button when you see the vibrant logo.
if you see a little yellow robot shoveling **** you're in.
if it doesn't. search around the forums for info about Hardware locked phones.
if it does:
download Odin
download stock JFD
use odin to flash JFD with repartition checked and the 512 pit file.
then use odin to flash JI6 with repartition UNCHECKED and the 512 pit file.
then you should be at stock and everything should work as if you never touched it and just updated.
note this will erase your system and data (your settings and stuff).
more info by searching the forums for any of those items.
Worked perfect! Thanks for your help!
Hi I'm a new member,
I rooted my fascinate easily enough. Then searching and learning about ROMs and Kernels I decided to do use ODIN CWM Recovery to 'backup' or whatever most forums tell you to before installing a new ROM. Point is my phone is stuck in manual boot mode and I cannot undo it.
I have tried multiple times using ODIN plus the four stock files
Stock-i500-VZW-Kernel.tar.md5
Stock-i500-VZW-pit.pit
Stock-i500-VZW-Recovery.tar.md5
Stock-i500-VZW-System.tar.md5
(I always would try to implement them in order pit/system, pit/kernel, pit/recovery)
Unfortunately after the first one (pit/system) ODIN says the process fails, I go ahead with the other two and they both amount to nothing happening. My phone does not reset or do anything for this matter and I am forced to shut down ODIN and unplug my phone (upon which it dies with no battery).
Then I put back in the battery and Im back to before in manual boot mode with
Reboot system Now
Apply sdcard:update.zip
wipe data/factory rset
wipe cache partition
Btw wiped data and wiped cache and it didn't help me =(.
Please someone help me, I really don't want this new phone to be dead... Thanks in advance
Oh and when I press "apply sdcard:update.zip" I receive
E:Can't mount \dev\block\vold\179:9
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
I really don't care at all about keeping the phone rooted or not or whatever. I just want to be able to make calls again!
So it looks like you're stuck in blue recovery ... sounds like something that Odining a stock package should fix.
Here is a nice thread for getting back to stock (it's a sticky in the general section). The packages include system, recovery, kernel, and radio in a single file (I've actually never odin'd four separate files to get back to stock, or even ever flashed a system-only file), though no pit file.
So open up odin with your phone in download mode (with the battery out, otherwise there's a small chance of odin stalling at the end), and use:
- either the DI01 all-in-one, EB01 all-in-one, or this DL09 package in PDA
- the pit file in PIT (the link says DI01/EB01 but it also works with DL09)
- check "re-partition" if it isn't already checked
- run odin and hopefully in five minutes your phone will work again If for some reason it doesn't, that thread has instructions for using heimdall, although I've never had to resort to it.
So try this and see if it works! (For which package to use, I'd suggest trying DL09 first (since you'll need it to get to the official froyo build) and DI01 if that fails. If you're wondering whether DL09+pit actually works, I've used it to get out of a "stuck in blue recovery after odining stuff" situation myself so yes, it works.)
Thank you for the response! It's encouraging to hear any support and I think yours is promising.
So unfortunately I tried D101 and no go. Turns out this was before I realized this was for 2.1 and I'd prefer 2.2 for the upgrades. Although would you suggest 2.1 for the purpose of rooting/ROMing/Kerneling in the future? I ask because I'm slowly gaining confidence that after fixing this I might be willing to try this again...
Odin (1.7 -> I decided at your poster friend's advice to upgrade from 1.3) worked well said 'pass' and everything. Unfortunately when booting my phone it went straight to the boot screen as always.
Meanwhile I'm downloading the EB01 and your suggested DL09 to test those two.
Hopefully one of those will work but if not, I guess I'll try that heimdall technique the poster suggested in the other forum. Hopefully not tho b/c it looks a bit more complicated.
I'll let ya know if one of these others works.
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
mattjac1 said:
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
Click to expand...
Click to collapse
Definately stay away from rom manager cwm if you have the voodoo lagfix enabled, but since all the new fascinate roms are edify scripted, flashing through cwm in rom manager would be ok.
Sent from my Froyo'd Evil Fascinate full of PB&J
Problem: Whenever I boot my phone after the galaxy S logo dissapears the screen stays black, while the backlight on the touch sensitive buttons still come on.
So here is my background on what I have done with the phone
- It is on 2.1 Eclair
- Everything was fine. I had it rooted and running Bionix.
- When the problem started was when I was trying to install a matrix boot image, and a theme for Bionix.
- First symptons would it wouldnt get past the Vibrant (text) startup screen.
- In response I Restored to the Clockwork mod Restore which would have brang my phone back to normal.
- It did bring my phone back to normal except for one thing, there was a bug that said my cards were full and couldnt install any apps.
- So I went back into clockwork mod recovery and figured out quickly it didnt recognize my sd ext. But when my phone was on it did.
I understand that this problem is very out of now where and probably isnt very solveable with just a one click program. But I would be very thankful if anyone could give me any kind of information on this. Even if it is just saying "Its a problem with your Kernel". AlthoughI hope to see downloads and full instructions.
Thank for reading this.
CWM recovery is not supposed to be able to see your external sd, you are only supposed to be able to flash files from the internal sd.
Thanks given.
Do you know of any method I can do to fix this
You could Odin back to stock 2.1, but first turn off lag fix if there is one via voodoo app.
You want to ODIN using stock firmware and the 512 pit file. This will repartition your internal SD. You will (should) not lose personal data such as pictures, music, files.... You ended up trying to flash a theme or bootanimation that was not compatiable and when you restored traces of it have been left behind.
ODIN is the best method in these situations. Note that in rare cases it may be neccessary to do a full SD reformat.
The first thing you want to do is back everything up to your computer. All those pictures, music anything you want saved and then and only then try the odin with 512 pit.
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
shreddintyres said:
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Click to expand...
Click to collapse
Thanks for referring, I've also included the files in the guide just in case.
I certainly hope you aren't in a partitioning brick situation. I've seen this now twice and both were running Bionix 1.3.1 w/ Voodoo enabled and both somehow got certain bml partitions in an recognizable format by CWM and the Android OS. So far it hasn't been fixable with conventional flashing and PIT repartitioning. I will be trying a full JTAG re-write on one of the customer's phones tonight. I'll report back to this thread whether a JTAG session in which I fully re-write all addresses in the NAND block was able to fix this.
This marks the 3rd instance of what I'm referring to as partitioning bricking that was involved on a Vibrant that was running Bionix 1.3.1 at the time of the brick. I'm not blaming the ROM or the developer as I have used it with no issues and it's a great piece of work but perhaps the CWM packaged with it is allowing users to do things they don't intend to do causing this issue.
Thank you everyone very much for all the information and I was able to restore my phone back to stock 2.1 Eclair and then I flashed the rom bionix onto it.
I have given thanks to everyone that has posted from here on up ^^
Also if anyone is stuck in this situation also and Is reading this thing saying "what the heck I have no idea what to do". Just message me and I could full througho instructions.
Once again thank everyone and I have solved my problem. I am pretty sure it was the boot logo that made it happen.
okay i'll preface this by saying i read all the way through the Vibrick thread and any others i could find on this subject.
i was running NeroV3, decided to try CM7. made a dumb move (apparently?) by restoring back to my stock 2.2 backup via CWM, then flashing to CM7 and THEN trying to flash the Overstock kernel (these steps should be reversed?). i wiped the cache and dalvik cache, but then the kernel flash failed ("installation aborted"), so i rebooted, which went fine. i used ROM Manager to get back to recovery, tried flashing the kernel again, failed again, hit reboot, and then my phone got stuck on the Vibrant screen.
I tried every 3-button combo (also with battery pulls) to get to Download mode but nothing works. when i plug in the USB the spinny-working-hourglass thing pops up but freezes, the green charging bar does not come up, and it does not go to download mode.
when not plugged in, it just keeps returning to the Vibrant screen. i can't even get it to turn off without pulling the battery. i'm definitely not comfortable trying the solder method.
any help is appreciated - i'm not giving it long til i take it to t-mobile and play dumb, worst comes to worst i'll just get a cheapo replacement from the store and find another vibrant (or similar) used on craigslist.
thanks!
UPDATE:::
got the phone into download mode thanks to a thread by Dolphinwigs. had to do have odin open when replacing the battery/holding volume up/down.
waiting on the stock rom download now (internet is slow). hopefully all goes well from here...
The biggest issue I find is that people give up on ODIN to easily. Getting into download mode is not that hard but also not that easy eiither. This is why everyone should purchase a jig, never give up on ODIN try it a thousand times and then once more. Always have ODIN up and ready with the proper files on hand, and as soon as it connects to ODIN be ready to make shyt happen.
In your case an ODIN flash should get you where you need to be and after you root again flashing to CM7 should not be an issue. Keep in mind if you use the .tar in ODIN as well as the .pit you will lose everything on both internal/exteral SD. At this point unless you made a backup prior to your issue its really a lost cost.
Good luck!
i am now back up and running, i just didn't realize i needed Odin running when i tried to go to download mode. so simple, but so frustrating.
one thing though, the ROM i got is Eclair. do i need to update to FroYo before flashing CM7?
and also, so i do it right this time, do i flash the Overstock kernel BEFORE i flash CM7? or does it matter?
I flashed a few different ROMs, but suddenly the SIM card isn't capturing any signal. I tried the SIM card on an old phone and it works fine. Is there something I can do without buying a new SIM reader for it?
Hm, what different ROMs have you flashed? Have you tried going back to stock via ODIN?
I have a suspicion that you flashed a ROM build that has an issue with losing baseband/imei. Please list the ROM and build date that caused the issue.
Sent from my SGH-T959 using xda premium
If it is not an IMEI issue, try flashing a modem in recovery.
Here's the story. Some of the ROMs I flashed were ICS Passion, ICZen, and Doc’s Master ICS V12.1 (KB5) and I didn't like it so I flashed back to ICZen or Passion. One of them messed up the signal, but I don't remember which one. Anyway, I tried RemICS-JB after that, but it still did not have any signal, so I figured I flashed back to stock. However, after starting Odin it didn't progress for awhile so I exited the program. Then I resetted the phone and suddenly it was in a mode that that looked like this "Mobile .../ ! \...Computer" I found out that it was either soft-bricked or hard-bricked. Seeing as how I couldn't go into download mode with 3 buttons nor adb method, I decided that to have to make a jig. Then suddenly after trying this method for a bit,
http://forum.xda-developers.com/showthread.php?t=775911&highlight=usb+jig
I was able to start Odin and still have repartition ticked since I read that it would cause problems, but it didn't this time. The strange thing was that I was never in the original download mode(android with shovel). My screen still looked like this "Mobile .../ ! \...Computer" until I saw a blue dot at the bottom which happened to be the progress bar when I just clicked the START button on Odin after adding the PIT and PDA. On the other hand, I right-clicked and ran as administrator in Windows 7, so maybe that had something to do with it. Anyway, I'm glad it was able to flash it back to stock and the signal is back. I just have to root it again and flash ICZen or something. Let's hope it doesn't happen again haha.
FC3SRedSuns said:
Here's the story. Some of the ROMs I flashed were ICS Passion, ICZen, and Doc’s Master ICS V12.1 (KB5) and I didn't like it so I flashed back to ICZen or Passion. One of them messed up the signal, but I don't remember which one. Anyway, I tried RemICS-JB after that, but it still did not have any signal, so I figured I flashed back to stock. However, after starting Odin it didn't progress for awhile so I exited the program. Then I resetted the phone and suddenly it was in a mode that that looked like this "Mobile .../ ! \...Computer" I found out that it was either soft-bricked or hard-bricked. Seeing as how I couldn't go into download mode with 3 buttons nor adb method, I decided that to have to make a jig. Then suddenly after trying this method for a bit,
http://forum.xda-developers.com/showthread.php?t=775911&highlight=usb+jig
I was able to start Odin and still have repartition ticked since I read that it would cause problems, but it didn't this time. The strange thing was that I was never in the original download mode(android with shovel). My screen still looked like this "Mobile .../ ! \...Computer" until I saw a blue dot at the bottom which happened to be the progress bar when I just clicked the START button on Odin after adding the PIT and PDA. On the other hand, I right-clicked and ran as administrator in Windows 7, so maybe that had something to do with it. Anyway, I'm glad it was able to flash it back to stock and the signal is back. I just have to root it again and flash ICZen or something. Let's hope it doesn't happen again haha.
Click to expand...
Click to collapse
Always run Odin with administrator privileges. I'm not sure if that's what cause your troubles but it's always good practice.
Remics JB will cause loss of baseband. This has happened from time to time with some ROMs. If it happens again, just Odin back to stock to fix. You had a soft brick, good job on recovering it!
Sent from my SGH-T959 using xda premium