ROM Manager WILL brick your admire.


Last Updated:

  1. nasstyrome

    nasstyrome Well-Known Member

    [​IMG]

    THIS APP'S ROM FLASHING OR CWM FLASHING IS UNSUPPORTED, INCOMPATIBLE AND UNSAFE FOR THE ADMIRE.

    What happens if you do hit those options:
    Samsung usually has arm-boot on 8 and recovery on 10.
    You flashed recovery on arm-boot and you get a brick since it is a bootloader partition looking for a bootloader but getting a recovery.
    You confused the heck out of your cute little admire..
    Now it's a cute little paperweight, doorstop, anti theft device (draw an angry face on it and leave it outside your front door for burgulars) [also the best way to get rid of it when youre done not using it anymore.]​

    ROM Manager is not compatible on all devices and/or does not check or does not know how to check for the proper recovery partition for this particular device and a few others and will overwrite the boot partitions with CWM.
    recovery.


    Ive just installed ROM Manager just to list the items NOT to touch in it.​


    let this be a warning to you if you do choose to install it:
    [​IMG]

    everything in green is safe to use.
    everything in red is NOT safe to use.
    if its not colored, it was covered in a previous image.


    [​IMG]
    [​IMG]
    [​IMG]


    If you happen to touch and use any of the red items, this is what will happen:

    [​IMG]

    At this point, you should feel that drop in the bottom of your stomach when your phone stops responding and doesn't turn back on.
    You've officially been bricked.

    I know of one other app similar to ROM Manager that has the same options i wouldnt touch, ROM toolbox. same rules apply for that app aswell. if it says flash rom, flash recovery or manage/restore/backup rom (*), don't touch it.
    *- not entirely sure what would happen if these items are selected, i believe itll do the same as flashing a ROM, it only makes sense.


    Images Updated 7/23/12 12:00

    Advertisement
  2. qandres12

    qandres12 Well-Known Member

    Right!!! If people took the time to read the stickies they would clearly see a forum on how rom manager isnt compatible. I may have bricked my own phone 1 1/2 times already but not because of rom manager. I actually took the time to read as much as i need to know, i wasnt gonna completely screw up my first android phone but i did and because of the good people here and all the time they took for these forums i was able to get it working. People should really take the time to read stuff out or at least ask questions. At this point in time there shouldnt be any post about how rom manager bricked their phones but surprisingly there are quite a few.....

    +1 sticky
    InFiD3ViL likes this.
  3. SacredBloodlin

    SacredBloodlin Well-Known Member

    You're absolutely right. I never read the other thread about Rom Manager because I have been toying with the Admire since it got CWM pushed with Odin and since those times people always told others not to use Rom Manager, so I never did. But there are a LOT more people with the Admire now and like you said, this thread should be stickied so that it doesn't get pushed to the bottom and no one sees the warning.

    +1 for sticky :)
  4. qandres12

    qandres12 Well-Known Member

    this is true a lot more people has the admire now. ive seen lots of people with the phone but anyone that downloaded CWM via Odin should already know the effect of ROM manager :/
  5. nuttmeg

    nuttmeg Well-Known Member

    +1

    great post OP.
    nasstyrome likes this.
  6. AntimonyER

    AntimonyER AF Addict VIP Member

    Per popular request, thread stickied. :)
  7. PlayfulGod

    PlayfulGod Well-Known Member Developer

    Let me clear something up here, ROM Manager isnt suppose to check for jack shyt. CWM when ported to any device has to be done properly and then submitted to koush to get officially built with ROM Manager support. If and when a device is available thru ROM Manager it is listed in the list of available devices. If your device isnt listed, it isnt supported thus you shouldnt be trying to flash recovery thru it, and if you did, and well, put bluntly, you were stupid in doing so, it isnt/wasnt ROM Managers fault you bricked your device but your own!!!!!

    I really wish people would take responsibility for their own mistakes and stop blaming a app, dev, etc.

    ;)
    puyow18 and aboatright like this.
  8. nasstyrome

    nasstyrome Well-Known Member

    woohoo, i got a sticky :D

    /feelinspecialsssss

    as far as dev blaming, i wasnt pointing fingers, that text block was a bit reworded by me but it was someone elses explanation from here as i couldnt explain it any better
    nuttmeg likes this.
  9. PlayfulGod

    PlayfulGod Well-Known Member Developer

    no clue on that info as why I didnt dispute it ;)

    But RM looks for a file in the ramdisk aka rootfs thats been set in the ROMManagerManifest.xml which contains the list of supported devices on koush's server. Device not in that xml, it doesnt get listed in RM n thus not supported. And one really shouldn't attempt to flash a recovery for a defferent device unless its Dev expressively states it works on such n such. ;)
  10. gbiggie

    gbiggie La patience et le pardon VIP Member

    Was there a picture below this:confused:
    Don't see any images at all:(
  11. Shabbypenguin

    Shabbypenguin Well-Known Member Developer

    You are a little off, samsung has been changing how they do things so much its ridiculous trying to keep up.
    old old phones used MTD and yaffs2 (like htc phones) then they decided to switch to their own stuff with bmls/stls and using RFS. they also used a non-standard android kernel, where the initramfs is actually compiled into the zImage instead of packed on after like with boot.img format.

    most prominently is the sgs1 series where boot kernel was bml7 and recovery was bml8. then on the indulge they jumped up +1 to each partition (bml8 and bml9 with boot and recovery respectively). then on the admire/prevail/precedant/repp/vitality/replenish they jumped up yet another bml to be bml9/10 (recovery comes later than boot)
  12. nasstyrome

    nasstyrome Well-Known Member

    reuploaded to a different file host. sorry about that.
  13. Jake Altman

    Jake Altman Active Member

    I wish I had seen this thread 5 mins sooner, I just bricked my admire, haha. Curious though, would it be possible to fix it by taking it apart? It doesn't matter if it breaks more since it's as good as a brick right now.

    Irony being that its a red bricked admire
  14. qandres12

    qandres12 Well-Known Member

    sorry jake, im afraid there is nothing that can be done now except find a replacement phone and throw that piece of junk into the phone drawer, make a video of you destroying it, use it as a paperweight or to prank your friends ;)
    Jake Altman likes this.
  15. nasstyrome

    nasstyrome Well-Known Member

    there's some usb jig you can build to unbrick it i believe, search around for it.
    Jake Altman likes this.
  16. qandres12

    qandres12 Well-Known Member

    most people report that a jig doesnt work on the admire though
  17. ThatBlackWolf

    ThatBlackWolf Well-Known Member

    Lulz. Good fight man. Always do you research on apps like that. You must make sure you're phone is compatible with em. Or you'll be where you are now... Let me not lecture you more though... The thread says it all already lol.
  18. Jake Altman

    Jake Altman Active Member

    Out of curiosity, some phones when you plug them into the computer via USB and take out the batter and hold the power button and another button, usually volume down, it goes into a downloading screen, it's different from rebooting into recovery, is there a way I can do something from there? I haven't tried it yet because I'm a little worried something might transfer over and mess up my computer. anyone ever hear of such a thing being possible?
  19. qandres12

    qandres12 Well-Known Member

    it wouldnt transfer anything to the computer jake. and no im sorry but that wont work for you since you used rom manager. rom manager literally takes incompatible phone's souls and takes them to the eternal abyss where cord phones rule the land(not literally but you get the idea) there is no way to bring it back to life. the steps of getting into download mode is to press down and hold the camera button and then plugging in the usb cable into the phone but again this wont work for you. essentially that is what a jig does, tricks the phone into download mode but they also dont seem to work on the admire. i understand you wanting to fix your phone but trust me when i say this my friend, all you have is a permanent brick and its best to move on
    Jake Altman likes this.
  20. Shabbypenguin

    Shabbypenguin Well-Known Member Developer

    if you can get into download mode yoiu can prolly fix it. id suggest doing the odin back to stock guide. normal rom manager bricks result in a lit up screen and nothing else
  21. qandres12

    qandres12 Well-Known Member

    once you use rom manager you arent able to get into download mode though. lots of users have reported this
  22. Shabbypenguin

    Shabbypenguin Well-Known Member Developer

    apologies the way he worded it i had misread that and assumed he was able to get into download mode still.

    and im aware the risks of using rom manager. i was teh one whom first warned admire owners when cwm was made :p

Share This Page