I think I just bricked this phone. - Touch CDMA General

Posted this in the UPGRADING section but it may be better suited here, I'm not completely sure.
So I think I just bricked my dads vogue.
I followed the instructions in the HOW TO FLASH YOUR VOGUE thread as best as I could and now I'm in a rough position. He's been ranting about the WinMo OS almost since he got it and wanted to try Android so I tried to flash it.
What's going on:
Blank (black) screen
Backlight is on
Orange status(?) LED
Unresponsive to anything
Powering up yields a green status LED, one buzz of the vibration, call & end keys light up then it reverts to the above. Takes 1 or 2 seconds.
Plugging in the USB gives me "Found New Hardware: Data Interface" but I don't have the drivers or w/e is required to install it.
Any one able to help me? I figured this should be pretty straight forward but it's turning out to be a nightmare. :cries:

After you flash the android rom, you have to load a system image and data image into it. That may be normal.
Note, I have not flashed mine to Android, but it seemslike your missing the next step in the process.

This may help...
The bottom may help with the bricking and the top may help with android.
http://forum.xda-developers.com/showthread.php?t=603508

nope it isnt bricked just reflash windows and use android via haret...sounds kernel related

With advice from the other thread I'm in bootloader(?) mode
But that's as far as I got.
oh man I'm in trouble said:
So I've gotten back to red/green/blue/white striped screen but nothing will read the phone/let me flash anything to it.
Screen says:
VOGU100 MFG
SPL-2.31.CoKe
CPLD-3
USB
Click to expand...
Click to collapse

oh man I'm in trouble said:
With advice from the other thread I'm in bootloader(?) mode
But that's as far as I got.
Click to expand...
Click to collapse
Did you download your ROM you needed?

staud8469 said:
Did you download your ROM you needed?
Click to expand...
Click to collapse
What carrier do you use?

Yes, downloaded the stock rom.
Provider is Verizon

oh man I'm in trouble said:
Yes, downloaded the stock rom.
Provider is Verizon
Click to expand...
Click to collapse
Ok then...you will need to flash another rom. Verizon, is a pain.
Here is NFSFANS ROM windows 6.5
http://forum.xda-developers.com/showthread.php?t=432487
The files from this forum will contain a program called ROMUpdateUtility. Run that in boot mode. Then run NFSFANS verizon provisioning. all files are on that forum. Just remember...Your device is not bricked (as it sounds). You could brick it though. So be careful. You may wanna get advice from a Verizon User.

staud8469 said:
The files from this forum will contain a program called ROMUpdateUtility. Run that in boot mode. Then run NFSFANS verizon provisioning. all files are on that forum.
Click to expand...
Click to collapse
At this point, I'm throwing everything I think I know or understand out the window.
That said, can you walk me through the process starting at the bootload screen?

oh man I'm in trouble said:
At this point, I'm throwing everything I think I know or understand out the window.
That said, can you walk me through the process starting at the bootload screen?
Click to expand...
Click to collapse
Yes, from a Sprint stand point though.
-download NFSFANS ROM
-Extract all the files from NFSFANS ROM to a new folder.
-Enter BootLoader
-Once it loads up plug your phone into your computer
-In your new folder there should be like 10 files...one of which say ROMUpdateUtility. Click and run that.
-Follow all the instructions on it.
-When it finishes...your phone will auto reboot.
-Once loaded up, Download Verizons Provesioning from NFSFANS ROM (you will find the link of the download towards the bottom of the first post NFSFAN has posted)
-Connect your phone to ur pc and put the Verizon Provesioning Cab on your sd card and install it.
-Restart your phone.
That should work.

Thanks a ton, I'm 35% into the RUU.
I'll keep everyone updated.

oh man I'm in trouble said:
Thanks a ton, I'm 35% into the RUU.
I'll keep everyone updated.
Click to expand...
Click to collapse
Thats good progress. Now if/and when your phone boots up. Tell me if it gets stuck...and where at. If not then your good

Seems to be stuck at the Verizon logo. (First screen upon startup.)
EDIT:
Yeah, it's stuck.

oh man I'm in trouble said:
Seems to be stuck at the Verizon logo. (First screen upon startup.)
Click to expand...
Click to collapse
Does it say No radio?

oh man I'm in trouble said:
Seems to be stuck at the Verizon logo. (First screen upon startup.)
Click to expand...
Click to collapse
give it awhile to boot though.

staud8469 said:
Does it say No radio?
Click to expand...
Click to collapse
Nope.
M 03 PACAAAM4070
B 01 R 1.06.30
D3NFS
^That appears briefly under the Verizon logo which is normal but it still hangs after it disappears.
staud8469 said:
give it awhile to boot though.
Click to expand...
Click to collapse
5-8 minutes isn't enough?

oh man I'm in trouble said:
Nope.
M 03 PACAAAM4070
B 01 R 1.06.30
D3NFS
^That appears briefly under the Verizon logo which is normal but it still hangs after it disappears.
5-8 minutes isn't enough?
Click to expand...
Click to collapse
Well, I'm going to get a verizon guy to help you. Brb.

ok sounds no radio has been written
follow this wiki to the T and you my friend will have a working phone with GPS
mainly a working phone!!!
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS

How do you keep customization from running?

Related

Well crap...I think I bricked it :-(

I tried to unroot my phone via OCLF from the market. It went dark, then got the normal Vibrant screen, the the Galaxy S screen, then it went dark again. Now, it just sits. Black screen. All the buttons at the bottom are lit up. :-/
Anyone?
Silly question, I know. But did you have a nandroid backup, by any chance?
This is probably a last resort, but try boot into recovery and wipe everything. This fix the problem for me, the downside is you lose all you data.
Sent from my SGH-T959 using XDA App
If you are anything like me, recovery didn't work and using Odin and reflashing Stock with repartition didn't work either.
You'll need to use odin to flash Eugenes "Vibrant that doesn't brick" (NO REPARTITION), then use odin again to flash Stock (check repartition this time) and you'll be good to go.
You can try to flash the froyo rom with odin...... I had that same exact problem and this is what fixed it for me. Once froyo us flashed then you can flash whatever rom you want. Hth
Ok, I probably should have stated that I'm a complete newby and have no idea what I'm doing. I believe I do have nandroid, but other than that you all are speaking French to me.
Right now I'm in the recover mode (I think). It's hooked up to my computer and I'm in the "Downloading... Do not turn off target!!" mode. This is where I'm stuck...I have no idea where to go from here.
Please talk to me like I'm a 5 year old, because as far as this is concerned, I am!
Oh, and thank you so much for any help you can give me!
hospo said:
Ok, I probably should have stated that I'm a complete newby and have no idea what I'm doing. I believe I do have nandroid, but other than that you all are speaking French to me.
Right now I'm in the recover mode (I think). It's hooked up to my computer and I'm in the "Downloading... Do not turn off target!!" mode. This is where I'm stuck...I have no idea where to go from here.
Please talk to me like I'm a 5 year old, because as far as this is concerned, I am!
Oh, and thank you so much for any help you can give me!
Click to expand...
Click to collapse
Well, good news is... you didn't brick your phone, this is recoverable. Best idea would be to search the forums on how to ODIN back to Stock. Theres plenty of posts on how to do it. You should also be able to find this in the tips & tricks threads. Good Luck.
Thank you all for your help! I recovered it!! Seems as though I was just going about it the wrong way!! I got into the actual recovery mode and cleared it all out. Now it's as good as new!
Again, appreciate your help and patience with what I'm sure is the 120,000th post on this subject. ;-)
Kienz said:
Silly question, I know. But did you have a nandroid backup, by any chance?
Click to expand...
Click to collapse
Is it even possible to make a nandroid backup before rooting?
hospo said:
Thank you all for your help! I recovered it!! Seems as though I was just going about it the wrong way!! I got into the actual recovery mode and cleared it all out. Now it's as good as new!
Again, appreciate your help and patience with what I'm sure is the 120,000th post on this subject. ;-)
Click to expand...
Click to collapse
Hey - what does you doing? Please told me, I've the same problem:
If I start the phone with an USB cable and the battery symbol with the running point under this, the PC recognize that something is connected, but Windows found no driver....
How could you could flash the Stackfirmware back, if the recovery and download menu does not work ?
PLS help !!!
Check out this thread http://forum.xda-developers.com/newreply.php?do=newreply&p=8129898
Go to the section where it says "Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out."
And do fix #1 it is pretty easy and it wont take you more than 20 minutes.
Let us know if that works
And do fix #1 it is pretty easy and it wont take you more than 20 minutes.
Let us know if that works
Click to expand...
Click to collapse
If I following the link and the next one, I can read:
Caution!!! You Must be on STOCK Vibrant Rom & NEVER Have Already Flashed the JP3 Froyo Image
Click to expand...
Click to collapse
It isn't -> it's a Firmware for the normal Galaxy (3key)[I'm a idiot]
First,
You must already Have Odin installed & Know how to boot into Down-loader Mode!!
Click to expand...
Click to collapse
Thats also the problem as described in front : I have had no chance to received the DL Mode.. maybe I make something wrong? The phone is booting up till the "S" is there, after that, the screen is black, keys are lightning...
The recovery 3button are blocked from the beginning; the DL Menu - I did not have reached it successfully
The PC recognize, that is something on USB, but not what ... so Odin did not see the Mobile, too.

Unlocking Vibrant

Hi there,
I am pretty new with this stuff, as I just got this phone today. It came with Froyo2.2 so I unrooted it back to the original JFK.
It did not come with a sim card, so I do not have a sim inside the phone as of now. But I do have a bell sim that I will use after to put the unlock key in... Is that okay?
I Connected the vibrant through Mini Kies and the MTP application says its connected.
I just re rooted from J16 back to the original.
I have the 64 bit drivers installed.
When I try to run Generate Unlock Windows Script I get the following error message saying...
Copy nv_data.bin
*daemon not running. Starting it now *
*daemon started succesfully *
error: device not found
error unable to find file <.\nv_data.bin>
could not find C:\documents and settings\1\desktop\key\generateunlockwindows\nv_data.bin
Anyone know what this means?
Or know what to do in this situation?
I am not sure if I should try installing the 32bit drivers or what.
how did you downgrade the phone from android 2.2?
I just bought the phone through ebay with the OS already at 2.2, and the phone is locked to t-mobile. I've heard it is not possible to unlock it with the 2.2 update. Is that true?
molson24 said:
Hi there,
I am pretty new with this stuff, as I just got this phone today. It came with Froyo2.2 so I unrooted it back to the original JFK.
It did not come with a sim card, so I do not have a sim inside the phone as of now. But I do have a bell sim that I will use after to put the unlock key in... Is that okay?
I Connected the vibrant through Mini Kies and the MTP application says its connected.
I just re rooted from J16 back to the original.
I have the 64 bit drivers installed.
When I try to run Generate Unlock Windows Script I get the following error message saying...
Copy nv_data.bin
*daemon not running. Starting it now *
*daemon started succesfully *
error: device not found
error unable to find file <.\nv_data.bin>
could not find C:\documents and settings\1\desktop\key\generateunlockwindows\nv_data.bin
Anyone know what this means?
Or know what to do in this situation?
I am not sure if I should try installing the 32bit drivers or what.
Click to expand...
Click to collapse
Yup, having exact same problem. If you find a fix let me know.
Make sure your usb setting is on debug and you have all of the files for the unlock on your pc. You also need java installed.
That method worked for me from stock.
can someone answer my question?
mbison83 said:
how did you downgrade the phone from android 2.2?
I just bought the phone through ebay with the OS already at 2.2, and the phone is locked to t-mobile. I've heard it is not possible to unlock it with the 2.2 update. Is that true?
Click to expand...
Click to collapse
I don't know whether the unlock methods work with Froyo but you can download a 2.1 stock Odin in the forum.
pvspencer22 said:
I don't know whether the unlock methods work with Froyo but you can download a 2.1 stock Odin in the forum.
Click to expand...
Click to collapse
where can i get it at and how do i do the rollback?
mbison83 said:
can someone answer my question?
Click to expand...
Click to collapse
...... please?
koooba said:
...... please?
Click to expand...
Click to collapse
very funny.
mbison83 said:
very funny.
Click to expand...
Click to collapse
Wasn't meant to be. Usually please and thanks goes a long way when asking for something. Shows appreciation.
^ Hence the THANKS button.
koooba said:
Wasn't meant to be. Usually please and thanks goes a long way when asking for something. Shows appreciation.
Click to expand...
Click to collapse
it also shows sarcasm and in this case thats what is seems like.
Read the stickies in the forum. If you can't figure it out ill grab the links tonight.
For the unlock this worked for me.
pvspencer22 said:
The windows tool worked for me from stock.
It doesn't generate a code though you input one.
Edit: link
http://forum.xda-developers.com/showthread.php?t=822008&page=11
Scroll down for instructions.
Click to expand...
Click to collapse
For going to stock. (From the general stickie)
draikz said:
Fixing so-called "Bricks"/Odin Errors
This guide is open to contribution/editing/correcting
-----------------------------------------------------------------------------------------------------
BOOT CYCLE
This is where you get the annoying Samsung Screen/Galaxy S screen.
DOWNLOAD REQUIRED (CREDITS TO JUSTANOTHERCROWD):
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by following the steps below
*Turn off the phone until you get to the charging battery screen (keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
3. Open Odin (in Administrator if you're running W7 or Vista), try one of the ones I attached to this post, at least one of them is bound to work, some don't work for me, but works for others, some doesn't work for others, but works for me, whatever floats your boat
4. Load in the files into Odin that you have downloaded from above Just load in the files corresponding to the text field.
DO NOT CHECK REPARTITION.
5. Plug in your phone with the DL mode
6. Click start and wait for the magic
-----------------------------------------------------------------------------------------------------
NO-BOOT PHONES
This is where your phone does NOT turn on, no combo of buttons works and power button does nothing.
DO THIS ONLY WHEN YOU PLUG IN YOUR PHONE AND NOTHING SHOWS UP ON THE SCREEN!!! If else, follow the steps from above.
This method is basically same as above, EXCEPT the way you get into Download Mode as your phone is HARD BROKEN.
1. Download all the files required in the "BOOT CYCLE" section of this post.
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
8. Follow steps 4-8 from the "BOOT CYCLE" section.
Troubleshooting:
-Odin stuck at some random process?
*Switch to another odin
*Make sure you did NOT check repartition, if you did, just repeat all the steps over again, except for the downloading parts, obviously.
-Phone not responsive?
*Try "NO-BOOT PHONES"section of this guide
-Phone stuck at Galaxy S logo screen?
*Put it in to DL mode, and run Odin again, it's just a bad install.
-All three ODIN is nonfunctional, stuck or giving "FAILED" errors?
*DO NOT CLOSE ODIN ONCE IT HAS FAILED!
*Unplug your phone
*Replug in your phone, get it into DL mode
* Unplug once it is in DL mode
*Replug and ODIN should recognize your phone
*Leave all the settings the same, then click "Start" again.
-Cannot get into download mode using the method I listed? Use the method(s) below:
Soldering Method
More methods coming soon
-----------------------------------------------------------------------------------------------------
I know how much of a pain posting in the Q/A section can be and the wait time is pretty bad, so if you need help regarding UNBRICKING and ONLY UNBRICKING feel free to post in here.[/S​
Click to expand...
Click to collapse
I unlocked my phone w Galaxy_S unlock 2 days ago. It's in the market and I was running Bionix V when I did it.
draikz said:
^ Hence the THANKS button.
Click to expand...
Click to collapse
Pretty soon we'll have apps that'll say hi and thanks and apps in general will replace everything we say, so much for what our parents taught us huh?
koooba said:
Pretty soon we'll have apps that'll say hi and thanks and apps in general will replace everything we say, so much for what our parents taught us huh?
Click to expand...
Click to collapse
Technology > your parents.
Anyday.
Do you know any other way i could unlock my samsung vibriant .nothing on this site has worked for me,,,who do i pay get files to work on this site please help poor black boy
franjess said:
Do you know any other way i could unlock my samsung vibriant .nothing on this site has worked for me,,,who do i pay get files to work on this site please help poor black boy
Click to expand...
Click to collapse
Poor with a few hundred dollars worth of phone. Lol
Did you try the PRO SGS app?
franjess said:
Do you know any other way i could unlock my samsung vibriant .nothing on this site has worked for me,,,who do i pay get files to work on this site please help poor black boy
Click to expand...
Click to collapse
If you want help you are going to have to be a lot more specific. What have you actually tried?
Just a tip, people will not help you on these forums if you ask for help without showing you've tried to solve the problem and know how to search.
There are loads of unlock threads. Almost everyone get one method to work eventually.

[VIDEO] i9000 Boot Screen Replacement Tutorial

All links pulled due to XDA Request after an XDA member complained I was only out for profits to a moderator on a few products I have. Due to the fact I link to a product or two and a few other things in many videos, I was asked to pull any content relating to this.
I will still be offering all this great material at my website. Just go to google and search for MobileTechVideos.
Video will be fully live any minute...
very helpfull ...even drinking russian Vodka .. i was able to do it !!!
Added link to new boot screen page on my website. Check it out in the bottom of the original post!
Maybe you guys wanna use this one I just made? Looks great on our AMOLED screens
shishir95 said:
Maybe you guys wanna use this one I just made? Looks great on our AMOLED screens
Click to expand...
Click to collapse
Looks great. Care if I add it to my boot screen page on the site?
Go ahead!!
Added it...
Just attempted this and it went terribly wrong
everything was okay until it tried pushing the logo to my sdcard (which failed with "permission denied") - it then said it couldn't copy the file from sdcard because it didn't exist.
I proceeded to unmount the sdcard from the phone and try it again which seemed to work. I shut the phone down and when I attempted to turn it back on it just remained off... I was able to get into download mode with odin 1-click and flash to stock (thank God).
- Serendipity 5.7
- I9000 .rar package
- logo_ATNT.jpg < 20K
was it the unmounting that did the trick? and can I just manually move the file onto /mnt/sdcard/ and edit the .bat file to skip the push?
Worked perfectly for me I love the nexus boot screen with my nexus boot animation Thank you connexion
mdsannihilation said:
Just attempted this and it went terribly wrong
everything was okay until it tried pushing the logo to my sdcard (which failed with "permission denied") - it then said it couldn't copy the file from sdcard because it didn't exist.
I proceeded to unmount the sdcard from the phone and try it again which seemed to work. I shut the phone down and when I attempted to turn it back on it just remained off... I was able to get into download mode with odin 1-click and flash to stock (thank God).
- Serendipity 5.7
- I9000 .rar package
- logo_ATNT.jpg < 20K
was it the unmounting that did the trick? and can I just manually move the file onto /mnt/sdcard/ and edit the .bat file to skip the push?
Click to expand...
Click to collapse
I'm not sure but it sounds like you didn't make sure that busy box was installed. As for not turning back on, I'm surprised at that. I soft bricked a vibrant building the vibrant files and got out of it but that was my fault pulling the usb cable out accidentally before ODIN was done. The answer to your question is yes, you can just flash the param.lfs tar file, verify busy box apk is installed and so is busy box, then just manually move the file. The script is built for simplicity. I'm sorry you had trouble.
connexion2005 said:
I'm not sure but it sounds like you didn't make sure that busy box was installed. As for not turning back on, I'm surprised at that. I soft bricked a vibrant building the vibrant files and got out of it but that was my fault pulling the usb cable out accidentally before ODIN was done. The answer to your question is yes, you can just flash the param.lfs tar file, verify busy box apk is installed and so is busy box, then just manually move the file. The script is built for simplicity. I'm sorry you had trouble.
Click to expand...
Click to collapse
Also, you did let the phone try to boot for a sec right? In some cases when you don't have a boot screen after the flash you won't get a dirty pixel screen but it will be black for the 5-10 seconds it attempts to show you whats there. I just want to make sure you were not prematurely turning the phone off.
connexion2005 said:
Also, you did let the phone try to boot for a sec right? In some cases when you don't have a boot screen after the flash you won't get a dirty pixel screen but it will be black for the 5-10 seconds it attempts to show you whats there. I just want to make sure you were not prematurely turning the phone off.
Click to expand...
Click to collapse
yeah, i attempted to turn back on twice (hold power for about 3-4 seconds, wait about 10) after it seemingly succeeded - I pulled battery in between jic.
the .bat file said busybox install failed because it was already installed... how else can I verify that bb is installed?
I'm going to try again once I get another ROM back on my phone because I really want to get at&t off my phone
thanks for your hard work and responses
this was going to be my boot image if anyone wants to use
mdsannihilation said:
yeah, i attempted to turn back on twice (hold power for about 3-4 seconds, wait about 10) after it seemingly succeeded - I pulled battery in between jic.
the .bat file said busybox install failed because it was already installed... how else can I verify that bb is installed?
I'm going to try again once I get another ROM back on my phone because I really want to get at&t off my phone
thanks for your hard work and responses
Click to expand...
Click to collapse
That will install the application on the phone. But, before you finish the rest of the batch script, you must open the app on the phone and make sure it's installed. It will look and tell you. If it's not click install busybox. When it's done, continue with the batch script. I'd start fresh also btw. Reflash with ODIN on the tar package then launch the script.
AReynante said:
Worked perfectly for me I love the nexus boot screen with my nexus boot animation Thank you connexion
Click to expand...
Click to collapse
Do you mind posting the boot screen?
can you give me a txt document guide? I can open the related web because of internet accessing control, thanks!
TheBassman369 said:
Do you mind posting the boot screen?
Click to expand...
Click to collapse
Yeah, it is in the OP, but I'll post it too. Credit goes to connexion
http://www.mobiletechvideos.com/blog/?page_id=317
AReynante said:
Yeah, it is in the OP, but I'll post it too. Credit goes to connexion
http://www.mobiletechvideos.com/blog/?page_id=317
Click to expand...
Click to collapse
Thanks, but I remembered that AFTER I asked you. I had a slow moment. Lol
TheBassman369 said:
Thanks, but I remembered that AFTER I asked you. I had a slow moment. Lol
Click to expand...
Click to collapse
Hah, no problem, we all do

[STOCK ROM]Use for going back to stock before flashing a custom ROM with minimum risk

\\\\\\\\\\\\warning///////////
It seems that phones batch 1010 and newer dont like this method of going back to stock. If you're caught in a boot loop try flashing the official froyo for Captivate. One source can be found here
\\\\\\\\\\\\warning///////////
Disclaimer: Anything you do with the content found in this thread and the content that this thread links to, is your own choice and you are fully responsible for what happens to your phone.
This method is for ATT Captivate ONLY!
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
The purpose of this thread is to give flash addicts/custom ROMs users a more secure way to go back to stock - JF6 - without risking bricking their devices.
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
This package contains NO BOOTLOADERS and NO PARAM.LFS!
Download the package from here
Download Samsung Kies and install it. It will install the latest Samsung drivers.
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot in Download Mode (see below)
Run Odin3 v1.3.exe
Click on the button PDA
Choose JF6_secure.tar.md5
Click start.
Wait and do not unplug cable until it is finished
How to boot in download mode:
There are 3 methods:
Method 1: (ADB) - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons
Plug in the USB cable and continue holding both Volume buttons
Method 3: (JIG)
Link
If moderators believe this does not belong in development, I have nothing against to moving it to General. However, I think the community would appreciate if it would remain here.
Works fine
I used this to flash the latest Continuum 3.5 and everything worked fine. Thanks!
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered NO BOOTLOADERS! @@ YAY
Yep, updated, thanks!
Thanks for this and I appreciate all your work.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Success !!
Just used this to go back to stock prior to flashing another ROM. Worked with no problems and only took about 5 minutes. Will use this from now on to avoid the possible brick.
Again, really appreciate you providing this for us.
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
sircaper said:
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
Click to expand...
Click to collapse
Here you go again, is in the OP
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
Click to expand...
Click to collapse
on top of the read phail, i would add that you dont need to flash stock between roms, you only need to do it after a failed flash or a "no wipe" rom that depends on original files, **which they dont do anymore**. All the good full roms do a wipe before flashing. so there is no point going to stock! hope that clearifies!
icezar1 said:
Here you go again, is in the OP
Click to expand...
Click to collapse
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
sircaper said:
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
Click to expand...
Click to collapse
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
icezar1 said:
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
Click to expand...
Click to collapse
Makes sense. Is there ever an instance where those files need to be wiped, though?
sircaper said:
Makes sense. Is there ever an instance where those files need to be wiped, though?
Click to expand...
Click to collapse
Not really. Only if you flashed a boot loader from a different SGS model.
icezar1 said:
Not really. Only if you flashed a boot loader from a different SGS model.
Click to expand...
Click to collapse
Thanks. Appreciate you clearing things up for me.
Trusselo said:
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered
Click to expand...
Click to collapse
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
WickedNite said:
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
Click to expand...
Click to collapse
Yes, is OK
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
likiud said:
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Click to expand...
Click to collapse
take a look here
double RL said:
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
Click to expand...
Click to collapse
You dont have the 3 button fix?
EDIT: yes, is OK, I tested it. Make sure you run a md5 checksum after putting it on your sdcard

[Q] Verizon G2 Bricked Without Recovery, Stuck in Fastboot Mode?

Hey guys,
The inevitable has happened: I've finally bricked a device that I can't seem to find the solution to online. Here's what happened:
1. When I got the phone a little over a week ago, I accidentally "broke" the recovery by trying to install CWM through Rom Manager. Turns out that's not something you generally want to do. Oops.
2. I got lazy and put off restoring the stock recovery, instead choosing to deal with the stock launcher.
3. Today, while dealing with the 50th pop-up for the OTA update, I accidentally pressed "Install Now" instead of "Install Later"
Now, when it boots, it briefly shows the LG logo before displaying an all-black screen with small white text reading:
[730] Fastboot mode started
[780] udc_start()
I get a little bit more text when I plug it into my PC. I've been trying to fix it for the past three hours - I've tried countless solutions, but nothing seems to work.
Can anyone out there give me some advice? I'd greatly appreciate it.
Have you tried to use the lg flash tool?
tbishop91 said:
Have you tried to use the lg flash tool?
Click to expand...
Click to collapse
When I opened the Flash tool, it prompted me for a Username and Password, something I didn't have.
techee44 said:
When I opened the Flash tool, it prompted me for a Username and Password, something I didn't have.
Click to expand...
Click to collapse
there's a dll you have to download an replace the one that was installed, it should be on that same thread, but it takes away the username and password
datechnerd said:
there's a dll you have to download an replace the one that was installed, it should be on that same thread, but it takes away the username and password
Click to expand...
Click to collapse
Will this work even though I don't have a recovery? The instructions I found (these: http://forum.xda-developers.com/showthread.php?t=2448960 ) definitely sound as though they were created with a working phone, and some of the instructions linked still imply they have TWRP.
Thanks for any help, I really appreciate it. I feel like I can get this working, it's just going to take some time (something I don't have a lot of, as I'll be camping all weekend).
techee44 said:
Will this work even though I don't have a recovery? The instructions I found (these: http://forum.xda-developers.com/showthread.php?t=2448960 ) definitely sound as though they were created with a working phone, and some of the instructions linked still imply they have TWRP.
Thanks for any help, I really appreciate it. I feel like I can get this working, it's just going to take some time (something I don't have a lot of, as I'll be camping all weekend).
Click to expand...
Click to collapse
yes...
antawnm26 said:
yes...
Click to expand...
Click to collapse
Lol such a simple answer.
Alright I'm trying it. Will report back with results in case I need more help. Thanks everyone
techee44 said:
Lol such a simple answer.
Alright I'm trying it. Will report back with results in case I need more help. Thanks everyone
Click to expand...
Click to collapse
Lol.. Make sure you get that dll that was mentioned earlier because that's your crack to make the tool work.. If you get a fail but your phone boots up and go through settings don't worry about it it's good.. I know a lot of people were having the fail reset error
Sent from my LG-D802 using Tapatalk
antawnm26 said:
Lol.. Make sure you get that dll that was mentioned earlier because that's your crack to make the tool work.. If you get a fail but your phone boots up and go through settings don't worry about it it's good.. I know a lot of people were having the fail reset error
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
So... I followed the guide I posted earlier. It talks about entering download mode, which I'm not able to do, and my phone isn't seen in Device Manager as "LGE AndroidNet for VZW..." (Oddly, it's seen as a "SAMSUNG Android Phone," and under that is "USB Modem Phone ADB port").
When I unplugged and replugged the phone back in, trying to enter download mode even though I haven't been successful with that, nothing happened. LG Flash says it's ready, but nothing activated.
Help??
When it says it's ready unplug it while in download mode and plug it back in.. Make sure you have the ports set right
Sent from my LG-D802 using Tapatalk
antawnm26 said:
When it says it's ready unplug it while in download mode and plug it back in.. Make sure you have the ports set right
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
But I can't enter download mode. If I power off the phone it just brings me straight back to Fastboot.
techee44 said:
But I can't enter download mode. If I power off the phone it just brings me straight back to Fastboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2524482
antawnm26 said:
http://forum.xda-developers.com/showthread.php?t=2524482
Click to expand...
Click to collapse
After 6+ hours of work, I finally have my phone up and running again. Thank you so, so much antawnm. You're awesome for helping me through this. Though that link provided wasn't perfect (it was for the Korean model) it provided me with enough clues to combine it with everything else you sent me and some files I found in a directory (especially the recovery.img file for the VZW LG G2) to get back right to where I was.
The funniest part was, after the phone rebooted itself and I got back to my home screen, the phone informed me that my software update was unsuccessful. I genuinely laughed.
Thanks again.

Categories

Resources