Page 2 of 2 FirstFirst 12
Results 26 to 48 of 48
  1. #26  
    MrSmith317's Avatar
    Mr Fix-It

    Posts
    2,187 Posts
    ROM
    Stock Rooted

    Default

    Quote Originally Posted by -Droid- View Post
    Also do you think Verizon would check that it's relocked or could I take it under warranty? And if so could they fine me $650 for the refurbished one that they send me if they see it's relocked?
    Don't worry about that. You really shouldn't need to go that far either. Try to follow my how-to on flashing an ruu. If you continue to get the mainver error there's a fix for that on xda. It sets your mainver back to 1.0. When I get to a PC I'll update this post with links.

    Sent from my Paranoid Android Galaxy Nexus
    “Around here, however, we don't look backwards for very long.
    We keep moving forward, opening up new doors and doing new things,
    because we're curious...and curiosity keeps leading us down new paths.”

    -Walt Disney
  2. Thread Author  Thread Author    #27  

    Default Re: ***Please Help*** Urgent! May have bricked

    Finally fixed it by resetting the mainver to 1.XXX in the 4th post of this link
    The used the application that wanda and pizzadude showed me to get back to 2.XXX.
    After that it no longer recognized the sim card so I went into Verizon, got a new one, and I'm good to go now.
    Anyway, just wanted to help anyone else that may have this problem. Once again thanks to all of you, I got my phone working again, but I think I'll just wait until the OTA ICS comes out now!!!
  3. #28  
    Wanda's Avatar

    Posts
    1,439 Posts
    ROM
    Venom 1.0.3

    Default Re: ***Please Help*** Urgent! May have bricked

    Quote Originally Posted by -Droid- View Post
    Finally fixed it by resetting the mainver to 1.XXX in the 4th post of this link
    The used the application that wanda and pizzadude showed me to get back to 2.XXX.
    After that it no longer recognized the sim card so I went into Verizon, got a new one, and I'm good to go now.
    Anyway, just wanted to help anyone else that may have this problem. Once again thanks to all of you, I got my phone working again, but I think I'll just wait until the OTA ICS comes out now!!!
    I completely understand your reservations about rooting and ROMing considering you're experience. I would point out though that some good reading and homework could have prevented much of your troubles and when done in the proper order rooting and installing ROMs is very easy and painless (minus setting up your phone again).

    If you get the itch to get your ICS on give us a shout and we'll be here if you need help.

    If you're going to wait for the OTA...well, get comfortable...it could be a while
    "I drank what?" -Socrates
  4. #29  

    Default Re: ***Please Help*** Urgent! May have bricked

    Ok...I am in the same boat. However my problem is this...I have no custom recovery, when I hit recovery it just goes to a black screen and then nothing happens. Second problem is this....if I try doing adb commands, it says device not found.
  5. #30  
    MrSmith317's Avatar
    Mr Fix-It

    Posts
    2,187 Posts
    ROM
    Stock Rooted

    Default Re: ***Please Help*** Urgent! May have bricked

    Quote Originally Posted by JTAC View Post
    Ok...I am in the same boat. However my problem is this...I have no custom recovery, when I hit recovery it just goes to a black screen and then nothing happens. Second problem is this....if I try doing adb commands, it says device not found.
    If you're in HBOOT, ADB doesn't work, fastboot does. If you're in the normal phone mode, make sure USB debugging is enabled. Take a look at my guide for unlocking and loading a custom recovery.
    “Around here, however, we don't look backwards for very long.
    We keep moving forward, opening up new doors and doing new things,
    because we're curious...and curiosity keeps leading us down new paths.”

    -Walt Disney
  6. #31  

    Default Re: ***Please Help*** Urgent! May have bricked

    Quote Originally Posted by MrSmith317 View Post
    If you're in HBOOT, ADB doesn't work, fastboot does. If you're in the normal phone mode, make sure USB debugging is enabled. Take a look at my guide for unlocking and loading a custom recovery.
    That's the thing I had USB Debugging enabled. I cannot get into normal phone mode at all. Stuck at HBOOT or a black screen.
  7. #32  
    MrSmith317's Avatar
    Mr Fix-It

    Posts
    2,187 Posts
    ROM
    Stock Rooted

    Default Re: ***Please Help*** Urgent! May have bricked

    Quote Originally Posted by JTAC View Post
    That's the thing I had USB Debugging enabled. I cannot get into normal phone mode at all. Stuck at HBOOT or a black screen.
    In HBOOT, you can use fastboot commands, not ADB commands. Fastboot commands are more limited but if you have the AmonRa .img file you can flash it there. "fastboot flash recovery <insert amon ra img file here>"
    “Around here, however, we don't look backwards for very long.
    We keep moving forward, opening up new doors and doing new things,
    because we're curious...and curiosity keeps leading us down new paths.”

    -Walt Disney
  8. #33  

    Default Re: ***Please Help*** Urgent! May have bricked

    Smith...thanks for helping me out....but anytime I do a fastboot command it hangs on waiting for device. Any tips? So used to being spoiled with easy root like Droid and Nexus.
  9. #34  
    MrSmith317's Avatar
    Mr Fix-It

    Posts
    2,187 Posts
    ROM
    Stock Rooted

    Default Re: ***Please Help*** Urgent! May have bricked

    Quote Originally Posted by JTAC View Post
    Smith...thanks for helping me out....but anytime I do a fastboot command it hangs on waiting for device. Any tips? So used to being spoiled with easy root like Droid and Nexus.
    You should be sitting in HBOOT with the message "Fastboot USB" staring at you. That's the one and only time that fastboot will work.
    “Around here, however, we don't look backwards for very long.
    We keep moving forward, opening up new doors and doing new things,
    because we're curious...and curiosity keeps leading us down new paths.”

    -Walt Disney
  10. #35  

    Default Re: ***Please Help*** Urgent! May have bricked

    Then just put the recovery img in the folder on desktop? Correct? Rather ask 5 times and do it once.
  11. #36  
    MrSmith317's Avatar
    Mr Fix-It

    Posts
    2,187 Posts
    ROM
    Stock Rooted

    Default Re: ***Please Help*** Urgent! May have bricked

    Quote Originally Posted by JTAC View Post
    Then just put the recovery img in the folder on desktop? Correct? Rather ask 5 times and do it once.
    Copy it to wherever you like, but the same directory as fastboot is the easiest. I'll show you why.

    If I used c:\androidsdk(and copied the img there) , here's the command I'd use:
    "cd \androidsdk"
    "fastboot flash recovery recovery.img"

    If I did the same but copied the img to desktop:
    "cd \androidsdk"
    "fastboot flash recovery c:\users\myusername\desktop\recovery.img"

    So it's up to you. Hopefully you see the potential pitfall.
    “Around here, however, we don't look backwards for very long.
    We keep moving forward, opening up new doors and doing new things,
    because we're curious...and curiosity keeps leading us down new paths.”

    -Walt Disney
  12. #37  

    Default Re: ***Please Help*** Urgent! May have bricked

    New error message. Cannot load the recovery image.
  13. #38  
    MrSmith317's Avatar
    Mr Fix-It

    Posts
    2,187 Posts
    ROM
    Stock Rooted

    Default Re: ***Please Help*** Urgent! May have bricked

    You are unlocked right? As long as you're unlocked you may just have a bad download.
    “Around here, however, we don't look backwards for very long.
    We keep moving forward, opening up new doors and doing new things,
    because we're curious...and curiosity keeps leading us down new paths.”

    -Walt Disney
  14. #39  

    Default Re: ***Please Help*** Urgent! May have bricked

    Ok. Here is what I did with success. Downloaded Amon Ra 3.14. Changed the name to recovery.img. Put that in C:\Program Files\Android\android-sdk\platform tools. Then once the prompt was changed to the above...type, fastboot flash recovery recovery.img

    All I got to do now is finish rooting.
  15. #40  

    Default Re: ***Please Help*** Urgent! May have bricked

    Ok. This phone is killing me. Flashed the recovery.img and then went to recovery, developer menu and installed super user. Rebooted device after that completed, it powered on, saw HTC screen and now is stuck on a black screen.
  16. #41  
    Wanda's Avatar

    Posts
    1,439 Posts
    ROM
    Venom 1.0.3

    Default Re: ***Please Help*** Urgent! May have bricked

    Quote Originally Posted by JTAC View Post
    Ok. This phone is killing me. Flashed the recovery.img and then went to recovery, developer menu and installed super user. Rebooted device after that completed, it powered on, saw HTC screen and now is stuck on a black screen.
    Which ROM did you try to fire up?
    "I drank what?" -Socrates
  17. #42  

    Default Re: ***Please Help*** Urgent! May have bricked

    I am on the stock Rom. Is there a particular Rom to install so I can get the phone working?
  18. #43  
    Wanda's Avatar

    Posts
    1,439 Posts
    ROM
    Venom 1.0.3

    Default Re: ***Please Help*** Urgent! May have bricked

    Maybe try one of Scotts Clean ROMs for S-On. It has a script that allows the kernel to pretty much auto install...after you flash it, the phone should automatically reboot to Hboot and ask if you want to flash the kernel...accept the update and you should be good to go. If nothing else you'll at least be able to use the phone again until you get a ROM you really want. Scott's ROMs are usually very close to stock but with improvments and minus the stuff many of us consider bloatware.
    "I drank what?" -Socrates
  19. #44  

    Default Re: ***Please Help*** Urgent! May have bricked

    I tried flashing many of Scott's GB ROMs. That works fine, but when it auto installs the kernel, I get "main version is older, power to reboot".
  20. #45  
    MrSmith317's Avatar
    Mr Fix-It

    Posts
    2,187 Posts
    ROM
    Stock Rooted

    Default Re: ***Please Help*** Urgent! May have bricked

    Use the tool in post #27 to change your mainver back to 1.000
    “Around here, however, we don't look backwards for very long.
    We keep moving forward, opening up new doors and doing new things,
    because we're curious...and curiosity keeps leading us down new paths.”

    -Walt Disney
    Thanked by:
    JTAC 
  21. #46  
    Wanda's Avatar

    Posts
    1,439 Posts
    ROM
    Venom 1.0.3

    Default Re: ***Please Help*** Urgent! May have bricked

    Quote Originally Posted by JTAC View Post
    I tried flashing many of Scott's GB ROMs. That works fine, but when it auto installs the kernel, I get "main version is older, power to reboot".
    Quote Originally Posted by MrSmith317 View Post
    Use the tool in post #27 to change your mainver back to 1.000
    Yep, what Mr. Smith said. In the 4th post of that link to "the other forum" is a zip file. Grab that zip file, put it on the root of you SD. Do all your data wipes, flash the ROM but after it flashes go back to the "flash from zip" menu and flash the mainver zip file...then let it go to Hboot for the kernel install.

    I'm pretty sure thats the order...if it automatically takes you to Hboot after the ROM install then flash the mainver zip before you flash the ROM.

    I keep a copy of this file on my SD card for just such cases...only had to use it once so far though.
    "I drank what?" -Socrates
    Thanked by:
    JTAC 
  22. #47  

    Default Re: ***Please Help*** Urgent! May have bricked

    Mr. Smith/Wanda. Thanks that worked. I got to turn in my other Rezound to warranty. Now I get to deal with the fun of going back to S-On and locking my device.
  23. #48  

    Default Re: ***Please Help*** Urgent! May have bricked

    Hello,
    Is there any other link where you could get the exe RUU other than FileFactory?
Page 2 of 2 FirstFirst 12

Posting Permissions