Unrooting Eris without trackball scrolling up/down


Last Updated:

  1. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    Had a couple of unsuccessful attempts at flashing kaosfroyo-v31.zip that I got from the xda forum. Thought I would try flashing v30 first, then flashing v31 on top of that, but when I got to the amon bootloader, my trackball would not scroll down.:mad:

    I want to call Verizon and get my second replacement phone sent out, but I'm afraid of sending this phone in and they hitting me with a $300 bill because of it being rooted. Anyone have any ideas on how to unroot without using the trackball?

    Seems like a lot of people are having trackball issues with the Eris. I've had to get my wife's Eris replaced because of trackball issues. Wish they would send me an Incredible or something else other than this Eris. I only rooted to get what they had in the first place.

    :(:confused: Help!?
     

    Advertisement
  2. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    After doing some more searching, I found this post and will try it first. I think it is done by connecting the phone to the computer and letting the program do it without any input from the phone.

    Will let you know how it goes.
     
  3. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    Did not work. Got unknown error when trying to reboot phone to bootloader. Maybe that's because the bootloader is the amon)recovery_tool instead of the stock bootloader.

    Will continue to search, but the results I've found require trackball usage.
     
  4. da man

    da man Well-Known Member

    Joined:
    May 11, 2010
    Messages:
    215
    Likes Received:
    22
    Have you tried to fix your trackball by using the method on the youtube video of the blackberry. It has been floating around the forum for a while. My trackball wasn't working and I tried it, worked like a charm.

    I'll find the video for you if you would like.
     
  5. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    No. That didn't work. As a matter of fact, it sunk my trackball into the phone a bit. The other directions work, it just will not scroll down.

    If I can use the android sdk to do it, please just give me the steps. I can follow directions and am not afraid of the technical part of it. I just need to return phone back to stock. I should have never rooted it in the first place.:(
     
  6. da man

    da man Well-Known Member

    Joined:
    May 11, 2010
    Messages:
    215
    Likes Received:
    22
    I'd help if I knew, but have never looked into how to unroot. I've liked root since day one, well, maybe since like day three when I found the ROM I liked.
     
  7. doogald

    doogald Guides Guide

    Joined:
    Jan 7, 2010
    Messages:
    6,622
    Likes Received:
    1,896
    Eddie,

    I have never tried it myself, but this may help: HowTo: Flash Any Ruu - xda-developers

    It should let you then RUU the stock build.

    [edit] There is also this thread: http://androidforums.com/eris-all-t...ot-thread-apps-roms-updated-05-06-2010-a.html

    Again, I have never unrooted myself. I'm thinking, though, that I should download these files and instructions in case I ever need to...
     
  8. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    I liked it too untill I needed to unroot because of a known hardware problem on more than just my eris.

    If I could have a recovery console that does not require the use of the trackball, I would still love the world of rooting. It's just that I can not operate the rooted features because of the trackball.
     
  9. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    eddieb1983,

    If your trackball is not working, then you obviously can not use jcase's "flash any Ruu" method - it uses Amon_RA.

    The "RUU" installer fails when folks use it on a dev ROM for at least one reason: the failure of the devs to install a HTC stock "reboot" command that understands what a "oem-78" reboot is.

    That is the first thing the RUU utility tries to do: force the phone from a normally booted state to a special bootloader mode called "RUU"; it does this by running the command

    reboot oem-78

    on the phone.

    So, that's why you got the message you did - not because of the custom recovery.


    If you are trying to re-flash a phone back to factory state, and you have a trackball problem, there are several different approaches, but the first one I would try would be to use the HBOOT+PB00IMG.ZIP approach using the Leak V3 ROM.

    That's the easiest, and if that doesn't work, there are several other methods of increasing levels of difficulty.


    I see you are posting all over the board with this same problem. I'm going to limit my responses to this thread, rather than chase you all over the board. Let me know what your attempts with the Leak-V3 PB00IMG.ZIP method get you.

    eu1
     
  10. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    Thank you for your response eu1. I will try those things again and get back to you on this thread. It was more of a panic, thinking that my phone was stuck the way it was and I couldn't do anything about it. Got a little impatient. But I'm good now and will follow your directions to the "t" and get back to you.
     
  11. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    Ok. The file named PB00IMG.zip (zero zero) is in the /sdcard/ folder and after the phone goes through figures 1 and 2 of the PB00IMG.zip method, it never makes it to figure 3. It shows the following:

    HBOOT

    <SEND> FastBoot Mode
    <VOL UP> Recovery

    Do I have the file in the correct folder? I tried using eStrongs file manager to move it to /, but it said the file could not be moved.
     
  12. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    It should be located in the /sdcard folder.

    Quote from that other mentioned thread:
    So, do you actually see the phone reporting "Checking... [PB00IMG.ZIP]" for at least a full minute?

    Please, Please be precise in describing what you see.


    eu1
     
  13. doogald

    doogald Guides Guide

    Joined:
    Jan 7, 2010
    Messages:
    6,622
    Likes Received:
    1,896
    Just to put it out there, Windows has this default thing where they hide the extension of known file types, so make sure that the file is not actually named PB00IMG.zip.zip. It seems unlikely in this case, but I just wanted to mention it ...

    You say that you have eStrongs, so check with that.
     
  14. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    eStrongs says the path is /sdcard and the filename is PB00IMG.zip. In windows, the filename is just PB00IMG with no file extension shown. (They are hidden by default)

    What I see is precisely what is in figures 1 and 2 of the other thread. When the screen stops at figure 1, the bar in the upper right corner slowly fills up, then the phone moves on to what is shown in figure 2. Following that, I get what I showed in the previous posts:

    PB00100 XC SHIP S-ON
    HBOOT-1.49.0000 (PB0010000)
    MICROP-0111
    TOUCH PANEL-SYN0104
    RADIO-2.42.01.04.27
    Feb 8 2010,00:08:56

    HBOOT
    (Shown at the top the entire time)

    Then:

    <SEND> FastBoot Mode
    <VOL UP> Recovery



    Three androids on skateboards at the bottom.
     
  15. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    Checking..[PB00IMG.ZIP]
    stays on the screen for 26 seconds
     
  16. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    eddie,

    Thanks for the additional detail. That clearly indicates that the phone is finding the file (but 26 seconds seems too short).

    If you do not see an error message such as "Main Version is Older", then that result strongly suggests that the file you put on the SD card got corrupted when you transferred it.

    The Leak-V3 PB00IMG.ZIP ROM file is 109,946,224 bytes long (exactly - not one byte less nor one byte more).

    It has a "md5sum" checksum of: 1c0b0182356242a9d673a661e7458587

    There is no need to run a MD5 checksum if the file length is wrong.

    If you can verify that the file is the correct size (using Estrongs - long press and then select Properties), the file is probably not corrupted.

    If you transferred the file to your phone from a PC, make sure that you are using the "Safely Remove Hardware" control in the System Tray to disconnect the E: (F:, G:, whatever) drive after copying the file BEFORE you turn off "Disk Drive Mode" on the phone.


    eu1
     
  17. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    The file length is right on the money.

    The md5 checksum is d7bb9bcccc05398226bc8d1f7cb9fa70 which means it is a bad file. Could it be corrupted from not clicking safely remove hardware before unmounting the sd card from the pc? I will try that. I had to hunt for the file I got because a lot of the posts have dead links.
     
  18. doogald

    doogald Guides Guide

    Joined:
    Jan 7, 2010
    Messages:
    6,622
    Likes Received:
    1,896
    Never mind...
     
  19. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    You need to check the file length ON THE PHONE using a file manager - not the length of the file on the PC.

    If you do not use that "Safely Remove Hardware" control, there is a very good chance that you corrupted it on the SD card. The reason for this is that Windows uses write file caching: the "Copy" operation on the PC side appears to complete because the file data got copied into RAM - but has not yet successfully been copied to the slow SD card. You MUST use the "Safely Remove Hardware" feature before you turn off "Disk Drive Mode" - and wait for the little balloon to pop up saying "Safe to remove" or similar

    (Sometimes you can get away with not using "Safely Remove Hardware" when you copied small files because they get flushed quickly - but it is always dangerous to disconnect USB hard drives and flash drives without doing that)

    I strongly suspect you truncated the file because of your "26 seconds" report.

    eu1
     
  20. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
  21. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    I checked the file length and checksum on the phone using ScaryAlienWare Checksum Utility v1.0.

    I copied the same file to the phone again, and this time I waited a while after it finished, then used the safely remove hardware, and I got the same file length, 109946224, but this time I got a different checksum: eb982e7893ea34924380c0254d545366. Isn't that strange? I'm going to the link you posted to download it again and will try again.
     
  22. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    That is indeed strange. That is starting to sound like a bad SD card - especially since the file length is correct. If you are downloading the ROM file to your PC first, you could also check the file length and md5sum on the PC as well (to eliminate the possibility that it is the downloading process which is somehow corrupting the .zip file). But, let's make absolutely sure of something (I'm not trying to be insulting, just trying to be sure of things you didn't mention) : you are checking the length of the file after the file has finished transferring using a file manager on the phone, correct?

    Note that many (but not all) rooted (dev) ROMs have a version of busybox on them which can perform md5sum. Using either adb (from the pc) or a terminal emulator app, you could also do a

    md5sum /sdcard/PB00IMG.ZIP
    and
    ls -l /sdcard/PB00IMG.ZIP

    on the phone.

    eu1
     
  23. doogald

    doogald Guides Guide

    Joined:
    Jan 7, 2010
    Messages:
    6,622
    Likes Received:
    1,896
    The file explorer app Astro Explorer will also calculate MD5 checksums. Long-press on a file and choose Details from the pop-up menu and it will give size info, as well as the MD5 checksum (after a few seconds, depending on the size of the file.)
     
  24. scary alien

    scary alien not really so scary Moderator

    Joined:
    Mar 5, 2010
    Messages:
    21,684
    Likes Received:
    22,041
    doogald,

    What, don't you like or trust my app? :eek: Just kidding, of course (Astro is much easier and handy to use at the moment).

    I've been monitoring this thread and just wanted to verify that my app that eddie used was correctly calculating the MD5 checksum. I transferred my copy of the 2.1v3 leak to my Droid X and re-calculated with both my app and with Astro. MD5 sums and file sizes were as they should be (and matched the known/published values and the same value that I re-calculated on my PC just now too). I also verified that the values that Eddie was reporting were not the SHA1 checksums just in case (since my app has that option via a radio button).

    I think his /sdcard has poltergeists. Hope you figure this out, eddie. You've got great folks guiding you.

    Good luck!
     
  25. eddieb1983

    eddieb1983 Well-Known Member This Topic's Starter

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    :DFINALLY!!!!!!!!!!!!!!

    EU1, once again you saved another Eris user from throwing his phone across the room. The file I was downloading was corrupted. Once I downloaded the one you linked here in this thread, everything worked as beautifully as you said in the other threads.

    Thank you everyone on Android Forums!!!!! Especially erisuser1!

    My phone is now applying the July OTA update. When I get my replacement phone, I will be rooting it because I now have the tools to return it to stock if need be, and I have the great support of the people on this forum.

    I will probably be downloading the update.zip file to install the July update again if after I root the next phone, the trackball stops working again and I need to unroot it but the July update is no longer on the servers.

    Thanks again!!!!!
     

Share This Page

Loading...