can i have a hard brick like in the android devices or some thing like it
mashkuov said:
can i have a hard brick like in the android devices or some thing like it
Click to expand...
Click to collapse
I don't understand the question.
mashkuov said:
can i have a hard brick like in the android devices or some thing like it
Click to expand...
Click to collapse
Bricks are generally hard
As far as I know, its hard to actually brick a TP, but I've yet to even have to use webOS doctor, so I'm not 100% sure
I am Z.
chicle_11 said:
I don't understand the question.
Click to expand...
Click to collapse
do you use any android device ?
zanderman112 said:
Bricks are generally hard
As far as I know, its hard to actually brick a TP, but I've yet to even have to use webOS doctor, so I'm not 100% sure
I am Z.
Click to expand...
Click to collapse
i don't know what is the TP
i understand from you that it's can happend but Rarely ؟؟ and you are not sure ?
mashkuov said:
do you use any android device ?
Yes. A touchpad running CM9 A 2, and an HTC Wildfire S on sense 2.1 (based on gingerbread 2.3.4)
i don't know what is the TP
i understand from you that it's can happend but Rarely ؟؟ and you are not sure ?
Click to expand...
Click to collapse
TP = Touchpad. They're hard to brick, probably because you have webos to fall back on.
You can brick pretty much any electronic device, not just Android devices. However I find it pretty hard to brick the Touchpad with WebOS doctor and all.
The only times I have seen anything close to a hard brick on a Touchpad were partition issues that messed up the low level of booting. As long as you can get to the USB connection part WebOS Doctor will bring you back to life.
Even in that case I believe it is fixable, it just requires some specialized utilities.
mashkuov said:
can i have a hard brick like in the android devices or some thing like it
Click to expand...
Click to collapse
I think hard brick in android devices happens mainly because of the bootloader messing up. I bricked my Samsung Captivate because I was flashing a new bootloader.....
So in case of Touchpad, as we r still using webOS bootloader its difficult to brick it. Also if anything gets messed up in Android, we always have WeboS to go back too..
heh mess around /boot and see what happens...
but seriously until someone is able to boot a boot image using qcom recovery the best way to recover is hardware flashing (that or warranty..)...
that which there is no tutorial and would be pretty hard to do not to mention you would need a flash backup...
Thanks gyz that was really helpfull
Related
I've been looking at loads of comments from people about using Dutty's ROM and am very tempted to try it but I'd like to know what the odds are like of bricking my HD in the process?
I'm a little paranoid because with my Omnia I did a ROM change successfully but a lot of people brick them and it seems a bit random, so I was wondering if it's the same with the HD, or if they are much 'safer' somehow to update?
Cheers!
Jim
Cret said:
I've been looking at loads of comments from people about using Dutty's ROM and am very tempted to try it but I'd like to know what the odds are like of bricking my HD in the process?
I'm a little paranoid because with my Omnia I did a ROM change successfully but a lot of people brick them and it seems a bit random, so I was wondering if it's the same with the HD, or if they are much 'safer' somehow to update?
Cheers!
Jim
Click to expand...
Click to collapse
You can use SD method to flash, it's safety. Or if you use CustomRUU it's safety too, becouse it doesn't format the bootloader... and it changes only the OS, so if the process will be interrupted you will have only to reflash the device.
You can find it in this section in the sticky threads.
Very helpful mate, thanks
The risk isn't much. Think of it as Flashing your BIOS on your PC. if you lose power or something goes wrong u can brick your PC the same way. The risk and reasons are about the same. Make sure you have a full charge, its best to be plugged in on power, flashing from SD is somewhat safer. and even if the flash fails usually its not bricked anyway but you may have to try again or t the rom image on the sd card fro a card reader then goto boot menu again to flash.
Psyberd said:
The risk isn't much. Think of it as Flashing your BIOS on your PC. if you lose power or something goes wrong u can brick your PC the same way.
Click to expand...
Click to collapse
Thats a very bad comparision. As already said the bootloader doesn't get touched, so you can't brick something at all.
My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Does it automatically do the update? was your Nook Color rooted?
foxfire235 said:
My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Click to expand...
Click to collapse
Yeah, does it do it automatically. I have my Nook Color at home connected to my Wi-Fi. Hopefully, it doesn't download just download it without me being there =T
foxfire235 said:
My Nook just auto downloaded and installed an update that screwed up my device! Anyone else see this? WTF?
Click to expand...
Click to collapse
How did it screw it up? I haven't received an update, been tethering all day
What is your software version in settings after the update?
I was using a rooted nook. It bricked it, and I couldn't get past the B&N logo on boot. I just had to do a factory reset.
After the factory reset, I got a confirmation dialog that said - "your nook has been updated to software version 1.0.0" ??? that doesn't seem like an update. Although maybe that's the factory default?
foxfire235 said:
I was using a rooted nook. It bricked it, and I couldn't get past the B&N logo on boot. I just had to do a factory reset.
Click to expand...
Click to collapse
Not to be a pr*ck, but if you're still able to do a factory reset, that would mean it wasn't "bricked", or did I miss something there?
Did the unit want to auto-update again once you reset?
-CC
clockcycle said:
Not to be a pr*ck, but if you're still able to do a factory reset, that would mean it wasn't "bricked", or did I miss something there?
-CC
Click to expand...
Click to collapse
I guess we have different definitions of brick. What would you call a device that doesn't boot?
A
A device that doesn't boot is a soft-brick
a brick cannot be fixed through trivial methods.
foxfire235 said:
I guess we have different definitions of brick. What would you call a device that doesn't boot?
Click to expand...
Click to collapse
As I understood "brick" means it's totally useless, other than as a paper weight or a door stop, essentially just dead weight.
I think if your device doesn't boot, but you can still recover, would be exactly that. {my device didn't boot, I had to factory reset it}
-CC
I wonder if they have something in there to detect a change to the OS that forces it to re-download ?
clockcycle said:
As I understood "brick" means it's totally useless, other than as a paper weight or a door stop, essentially just dead weight.
I think if your device doesn't boot, but you can still recover, would be exactly that. {my device didn't boot, I had to factory reset it}
-CC
Click to expand...
Click to collapse
in the venacular, "brick" means that the device is dead and cannot be fixed without replacing hardware. If a 'simple' reset will restore the device to working order, it isn't bricked it is just in a bad state.
We try to avoid the term "brick" when describing anything else because we don't want to gve the impression that we might be saying "I just did what I read in your post on the forum and now my device is broken beyond repair".
I'm fairly certain (but not 100% positive) that FW version 1.0.0 is installed automatically when you are registering the NC for the first time (like when the OOB setup is first done). After my initial setup I checked the version and 1.0.0 was installed.
And I've also noticed that if you do a factory reset and re-initiate the device 1.0.0 is automatically installed.
I'd like to see some verification that there is new software out there than this one user's report. Confirmation?
PHiZ said:
I'd like to see some verification that there is new software out there than this one user's report. Confirmation?
Click to expand...
Click to collapse
I remember somewhere, that there was a way to trigger it, or something like that... but its not a new firmware but just a redownload of 1.0
I think this is a known issue for some users after they root. I've read it before on here somewhere and in IRC.
MBM or Pokey9000 can confirm but i'm pretty sure it's nothing to be concerned with. Just re-root and see if you have anymore issues.
Mine was updated to 1.0.0 as well but I was still able to root it and do Angry Birds though.
nk414 said:
Mine was updated to 1.0.0 as well but I was still able to root it and do Angry Birds though.
Click to expand...
Click to collapse
People need to clarify more what they are talking about here.
Did you have it rooted before it was "updated" ?
Apparently these devices were rooted. While I'm sure there's a small, very small minority of XDA-ers who don't mess with their devices, the rest of us do. From a statistical standpoint it would stand to reason that these NCs were rooted.
hi guys sort of a noobish question but does flashing to many roms damage your sgs?
No, it will not.
It is like installing windows or linux on your computer.
You can do it hundreds of time, you will never damage anything.
The best point is that you can always flash back the original samsung rom and have your original phone back
Etienne38 said:
No, it will not.
It is like installing windows or linux on your computer.
You can do it hundreds of time, you will never damage anything.
The best point is that you can always flash back the original samsung rom and have your original phone back
Click to expand...
Click to collapse
yea i know so flashing tons of roms wont damage my sgs thanks
But be careful with bootloaders.. when flashing these, it might brick your phone.
Erakko said:
But be careful with bootloaders.. when flashing these, it might brick your phone.
Click to expand...
Click to collapse
I'm not that noobish I was just wondering and the system is allmost unbrickable
Sent from my GT-I9000 using Tapatalk
My phone is bricked by ROM manager. My phone can't boot into recovery mode, downloading mode nor normal phone. The phone charges the battery so there is still hope to fix it. I also have a JIG Usb just incase. if you got any questions you need to ask, please ask. I really want my phone back.
Darth343 said:
I also have a JIG Usb
Click to expand...
Click to collapse
see this video
Can someone answer me - WHY are you using ROM manager when it's known that it kills our Galaxy Mini? Is it really that hard to use Odin, or just flash CWM recovery through the stock one?
Guess some people love to learn it the hard way. You have a unrepairable (at least at home) BRICK!
domcale said:
Can someone answer me - WHY are you using ROM manager when it's known that it kills our Galaxy Mini? Is it really that hard to use Odin, or just flash CWM recovery through the stock one?
Guess some people love to learn it the hard way. You have a unrepairable (at least at home) BRICK!
Click to expand...
Click to collapse
Sorry! Just a thought came to my mind can it b there any solution for this evergreen problem? Like newbies r bricking their phone again & again. ( like warning in stickies) . Just thinking! !! That's all.....
Sent from my GT-S5570 using xda app-developers app
You have no reason to be sorry . It's a great idea to put a warning message about ROM Manager in a sticky. However, i once was a total noob too, and i flashed CWM using Odin, it didn't even came to my mind to use ROM Manager.
Reading a couple of different tutorials and educationg yourself before doing anything is the best possible thing someone can do to prevent situations like this.But, like i said, some people have money to waste
lol ... ROM Manager is screwing up everyones phone. Even my friend's mini bricked. He was unlucky that his warranty had got over. He asked the samsung service center and they told him that it would cost $90 for a new motherboard. He uses his galaxy mini as a paper weight now. Rather buy a new phone than buy a motherboard for $90.
If your phone is under warranty, you can get your phone fixed for free in samsung service center( free new motherboard ). Even I bricked my phone when I was a noob with ROM Manager thankfully my warranty was valid that time.
Although I was able to use ROM Manager with no problems.
domcale said:
You have no reason to be sorry . It's a great idea to put a warning message about ROM Manager in a sticky. However, i once was a total noob too, and i flashed CWM using Odin, it didn't even came to my mind to use ROM Manager.
Reading a couple of different tutorials and educationg yourself before doing anything is the best possible thing someone can do to prevent situations like this.But, like i said, some people have money to waste
Click to expand...
Click to collapse
One real problem is that Rom Manager comes by default on most CM7 based roms. So most new users while experimenting might brick their phone by accident.
TheWhisp said:
Although I was able to use ROM Manager with no problems.
Click to expand...
Click to collapse
You were lucky, I guess
anshul sood said:
One real problem is that Rom Manager comes by default on most CM7 based roms. So most new users while experimenting might brick their phone by accident.
Click to expand...
Click to collapse
I agree, but nobody forces them to experiment with something they have no knowledge of. Phones are not toys to play with (to some extent )
A big warning in the general and development section would be enough.
domcale said:
I agree, but nobody forces them to experiment with something they have no knowledge of. Phones are not toys to play with (to some extent )
A big warning in the general and development section would be enough.
Click to expand...
Click to collapse
Most new users don't browse the stickies, just notice the large no. of redundant and useless threads. They just open the thread pertaining to the rom they want and that's that. It would be nice if each Rom had either the rom manager removed or a warning with the download link itself
never say to anyone that rom manager's brick cannot be recovered in home, it can be
the only step is just press volume down home power button but without panicking, panicking is the main reason of can't able to get into download mode
then just flash with odin, dont think it cannot get into dl mode, dl mode is controlled by bootloader and bootloader is not removed by rom manager
Unsuccesfull flash of bootloader hard-bricks our device, so you can't enter DL mode.
You can always give it a shot with a USB JIG* tho. But in most cases, the only thing that helps is JTAG.
*USB JIG - a 301k resistor between the 4th and 5th pin on the microUSB connector.
Tried that.
I've seen that video like about a thousand times. No luck i even went to a repair men today, he said your phone is dead if it can't go in to recovery menu. Is there any other way i can repair my phone? Sorry for late VERY reply
Yes, either use JTAG or send it to the service center.
Brick caused by rom manager is absolute
Nothing can be done
Sent from my GT-S5570 using xda premium
Me to I used it for making backups, but currently, I'm using cm 10 without ROM Manager.
Same problem with me the board was not responding so Samsung service centre changed my board.
Sent from my GT-S5570 using xda premium
If there isn't really anyway, then i'll just buy a new phone.
Darth343 said:
If there isn't really anyway, then i'll just buy a new phone.
Click to expand...
Click to collapse
Sorry you had to learn it the hard way. When you're new in this world it's easy to 'trust' all CM standard apps. Nevertheless: using CM means you're a root user. Your phone is rooted which means you can seriously damage your phone when you don't know what youre doing. That's exactly the reason why your phone is NOT rooted when you buy it, and your garantee is void when you root it yourself!
Some of these apps provide a warning: with great power comes great responsability!
Nevertheless: the first thing i do when i buy a new Android is rooting it! But a general warning is at place: root apps can damage your phone. Especially those to install roms. Even with a proper CWM you can flash a wrong or faulty Rom. The risk of bricking your phone is always there.
So think twice when you buy a new phone and read all about flashing on XDA!
Hi.
A friend asked my help with his Yarvik tab10-410. Being a bit more easy to me, I'm forced to ask help.
This tablet was infected with malware. According to what I can see and read about, it might have been rooted before. Every time I go to recovery and apply factory reset, the malware keeps annoying. even without internet connection.
Tried safe mode and nothing. In comparison to my son's Chuwi alike, I noticed that there is no internal sdcard (at least it won't mount).
Don't know what I can do beside applying some based code: custom rom, stock OS, whatever.
But neither of them appeared in my googling hours.
Does anybody have a solution? My knowledge is Android matters is very limited, but I follow instructions very well.
I only was able to root my smartphone to remove some bloatware.
Thanks.
kAbUkIx said:
Hi.
A friend asked my help with his Yarvik tab10-410. Being a bit more easy to me, I'm forced to ask help.
This tablet was infected with malware. According to what I can see and read about, it might have been rooted before. Every time I go to recovery and apply factory reset, the malware keeps annoying. even without internet connection.
Tried safe mode and nothing. In comparison to my son's Chuwi alike, I noticed that there is no internal sdcard (at least it won't mount).
Don't know what I can do beside applying some based code: custom rom, stock OS, whatever.
But neither of them appeared in my googling hours.
Does anybody have a solution? My knowledge is Android matters is very limited, but I follow instructions very well.
I only was able to root my smartphone to remove some bloatware.
Thanks.
Click to expand...
Click to collapse
Are you able to boot into Android at all ?
DrGreenway said:
Are you able to boot into Android at all ?
Click to expand...
Click to collapse
First of all, thank you for replying.
Yes. I can boot the Android 4.2.2 installed in this brick. Normal and Safe mode.
kAbUkIx said:
First of all, thank you for replying.
Yes. I can boot the Android 4.2.2 installed in this brick. Normal and Safe mode.
Click to expand...
Click to collapse
Chanced are that you've already tried this but just in case, there is a hard reset option for this specific tablet.
http://www.hardreset.info/devices/yarvik/yarvik-tab10-410-noble-101/
This might work if you're trying to do a factory reset.
That's what I ment by factory reset. Since even after that the malware appears, that's why I think the tablet might have been infected as root.
Hi, You need to find a factory image to flash to your device, if not you cant fix that infection.
Semseddin said:
Hi, You need to find a factory image to flash to your device, if not you cant fix that infection.
Click to expand...
Click to collapse
Does anyone know where can I find it?
Yarvik (brand) seems to be dying if not already dead. Bankruptcy was (according to news I read) part of brand's history.
Thank you
kAbUkIx said:
Does anyone know where can I find it?
Yarvik (brand) seems to be dying if not already dead. Bankruptcy was (according to news I read) part of brand's history.
Thank you
Click to expand...
Click to collapse
You solved the problem? I cant find a stock rom
Hi.
Couldn't find any rom. Had to send my friend to oficial support. It took almost 1 month to regain control of that "brick".
Bye