Related
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
EDIT
Ok guys... I found this...
forum.xda-developers.com/showthread.php?t=589642
It's about hacking spls. Any dev help is appreciated
-------------------------------------
Sent via the XDA Tapatalk App
philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
dude, are you out of your mind????????????
what do you mean? we did not do as the tutorial???? i have flashed my phone over 20-30 times. i did the root perfectly and the brick happenned after 20-30 flashes.
there are even developers who bricked their phones. think before making such comments and better inform yourself first!!!!
starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Please, stop this kind of message .... You will pay a new one to the guy who will brick it ? No ...
And you are talking of something you seems to don't know very well... Some devices have been bricked only by appliyng the 2 steps of the simple root process (without custom rom, a2SD ..) ...
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Man, maybe you should first read and than not post such a s**t. I bricked mine, too, and i think i know what i'm doing. If you would know about what you talk you would see that the cause for the bricked desires is not yet adressed, and that it could happen to anyone who rooted the phone
philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
Click to expand...
Click to collapse
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
stingerpl said:
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
Click to expand...
Click to collapse
I dunno man? My usb has been playing up recently. Been rooted since r1 and now I'm having trouble getting in recovery. Get a new and wonderful message everytime!
I've just put it down to my pc being a lazy f*ck! Hahahaha!! I just keep trying 'til it decides to do what I'm telling it to. Always get there in the end, there's no way I'm "unrooting". If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
MrBadgerMilk said:
If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
Click to expand...
Click to collapse
Ditto!
10char
Seriously guys, i just don't know how you manage to **** up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
phentex said:
Seriously guys, i just don't know how you manage to f**k up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
Click to expand...
Click to collapse
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
since HTC released the kernel code, I thought it would be easier to revert back to enterily stock
Re: Unrooted :( til we get a stable root. Who's working on this? [THINK TANK?]
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
starchildx said:
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
And ? Like a lot of those who have bricked their device the 21th flash ....
Seeing as you can't flash over the SPL and radio anyway, once you are successfully rooted, it's probably impossible to get to a state of full bricking. Anything will be recoverable with a gold card and/or a RUU.
Unlike many others, I only got root because I wanted access to paid apps. AFAIK root is needed for that. So I'm running the stock rooted ROM, and the radio update, provided by Paul. I won't flash anything until a rooted 2.2 ROM is out...and who knows...maybe after 2.2 the bricking problem will be gone?
socktug said:
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
Click to expand...
Click to collapse
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Have flashed a fair few times using all the methords posted on the modaco and XDA forums. all worked flawlessly..... but i too have kept on stock ROM.
Wont flash Customem ROMs untill im either a developer or the spl gets fully opened.
And socktugs right watch your launguage please all
EDIT: As per Stingerpl Suggests if you notice a bootloop occuring take the battery out ASAP!!
It is generally a good idea to take your battery out on first bootloop, go to recovery and nandroid restore. Might save your USB from bricking
I still can't understand why someone would want to unroot because of this. You're already past the risky procedure.
I guess a fully function root need some info about the current root. Anyone know what exploits was used and how its been applied?
maybe the problem is exotic hardware in the pc/laptop. i'm using a standart motherboard with a intel chipset, i never had any problems with rooting or unlocking or flashing any device.
for the people that have problems under linux, what do dmesg say ?
potter1984 said:
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Click to expand...
Click to collapse
Maybe the boot loop has something to do with it... but there are simple ways to avoid a boot loop.
I flashed my desire several times... and had bootloops occur several times. None bricked my phone.. fortunatley!
The reason i found for my boot loops, was NOT WIPING EVERYTHING!
I have read on modaco forums, that Paul's recovery does not clear the dalvik cache, when it is on a partitioned sd card. Maybe it is something to do with the rooting process (no rw access).
The only answer I found, was to re-partition the sdcard everytime. thus wiping all partitions.
So as with any rom you download... READ THE F`ING MANUAL!! its always best to do a FULL wipe. Then your getting the rom, as the developer wanted you to have it.
So not a solution, but some words of advice for noobs! And hopefully we can avoid too many more bricks!!
I will keep monitoring this thread and will update the title if / when we have any developments.
Maybe we need to pray for an engineering SPL
Hey all,
Sorry but I'm new at rooting and android in general. I just picked up a transformer for black friday and am debating rooting it. I was wondering if nvflash will work with my tablet (B90...sbkv2) and if not, if you have any idea if/when it will be made to work with it. I don't want to root and flash another rom onto the tablet if there's a large risk of bricking it. Also, I was just wondering in general what the chances are for bricking a tablet by flashing a rom.
Thanks a lot!
dkleinrodick said:
Hey all,
Sorry but I'm new at rooting and android in general. I just picked up a transformer for black friday and am debating rooting it. I was wondering if nvflash will work with my tablet (B90...sbkv2) and if not, if you have any idea if/when it will be made to work with it. I don't want to root and flash another rom onto the tablet if there's a large risk of bricking it. Also, I was just wondering in general what the chances are for bricking a tablet by flashing a rom.
Thanks a lot!
Click to expand...
Click to collapse
NvFlash won't work, but the guide below works without problems. There is little chance of bricking it, but the chance still exists.
TBH, I have never seen someone with a completely bricked tablet due to software reasons. Software problems are fixable in most cases, altough it can take a few days to find the right fix.
One legal notice: I won't pay if you brick your tablet, so you don't have to believe me. And rooting will probably break the warranty.
http://forum.xda-developers.com/showthread.php?t=1347388
I was wondering about this too. I have a B90 and my biggest concern is if flashing a custom ROM glitches and messes up recovery.
It happened on my phone recently, and I was stuck with no recovery or firmware but luckily had an equivalent of NVFlash. I'd be worried if I didn't have this available, just in case.
How is CWM installed? Is it likely to become damaged or lost? Or is it deeper embedded to stop that from happening?
I really wanna get a custom ROM on it but I'm absolutely terrified of bricking it given there's no fallback :/
Has anyone gotten chainfire3d to work on the tf700t??
Mine simply fails to boot... was trying to get stratagus to work and thought this might help..
thx
Why would you need Chainfire? I thought that was in intermediary opengl drive to allow for non-Tegra chipsets to play Tegra games? The TF700 ... is a tegra device ...
The Play Store page clearly states that it isn't compatible with ICS or Jelly Bean, so you shouldn't use it. Trust me, I didn't read it either and tried it and "bricked" my device. Took me a while to get it back going.
Well i dont see why it would brick the device? i have tried it on my infinity and a wipe and reflash of cleanrom worked fine after...
I have also been running it on my jellybean samsung galaxy s2 and my ics motorola atrix 4g without any problem.. so it seems to me that
he hasnt updated the info....
The reason i wanted to try it is because of the app stratagus which i am trying to run does not work on tegra devices... therefore using
chainfire with a qualcomm plugin might do the magic.....
my tf700 was rendered unbootable with cf3d. had to reinstall cleanrom to fix it. didnt need to wipe.
Interesting. I tried it shortly after we received JB officially. Someone else also posted that it bricked them. It just hit me, I wasn't unlocked when I did it, so that's why. I didn't have your option of re-flashing because I couldn't access recovery. I had to use my SD and go back to ICS. Either way, it's not compatible with us for some reason.
Alitheia said:
Interesting. I tried it shortly after we received JB officially. Someone else also posted that it bricked them. It just hit me, I wasn't unlocked when I did it, so that's why. I didn't have your option of re-flashing because I couldn't access recovery. I had to use my SD and go back to ICS. Either way, it's not compatible with us for some reason.
Click to expand...
Click to collapse
If you were able to restore it, it was not bricked. You cannot restore a brick. It is the definition of the word.
Hey guys, I managed to render my device unbootable with chainfire too.
Its rooted but not unlooked. Will it work again after wiping data or what are the possibilities thaz I have?
Update: wiping data did not work. What else can I so?
Gesendet von meinem GT-I9100 mit Tapatalk
I would suggest install a custom rom like cleanrom so that in future such incidences you can easily reinstall.
liquiddarknessvi said:
If you were able to restore it, it was not bricked. You cannot restore a brick. It is the definition of the word.
Click to expand...
Click to collapse
That would be why I used quotes around the word in my first post...clearly it wasn't bricked, but it was scary nonetheless. I know the definition.
Anyone who is using the latest clemsyn kernel and can verify if chainfire is working?
Currently running cleanrom 2.3 with stock kernel as the overclocking didnt seem to improve my gaming exsperience
But if chainfire works with the new kernel then i might use it
Come ON WHAT THE ****?? LOL
Does anyone read Chainfire3D Description on Google Play it says clearly
!! For Froyo and Gingerbread ONLY. NOT COMPATIBLE with Honeycomb/Ice Cream Sandwich/Jelly Bean !!
Not mean to be rude but why people doesn't read, dont install this people...
well relax... it works on all of the 4 devices i have had running everything from ics to jellybean i dont see the problem...
Its clearly something with this particular device hmm well damn... cant realy use this device for a whole lot...
all the nice apps and games are running like crap unfortunately...
I've had a report of a unit being bricked after CF3D installation as well. In that particular case, the owner of the 700 was saved by still being inside the warranty period (and an exchange was approved), but I guess with some handiwork, the unit could have been revived.
Also: one brick is not necessarily equal to another brick. Phrased differently: there are hard bricks and soft bricks. Installation of CF3D seems to generate a soft brick, from which you can recover FI you have the right files, knowledge, and a fair bit of time and patience. A hard brick generally results in an expensive paperweight.
MartyHulskemper said:
Also: one brick is not necessarily equal to another brick. Phrased differently: there are hard bricks and soft bricks. Installation of CF3D seems to generate a soft brick, from which you can recover FI you have the right files, knowledge, and a fair bit of time and patience. A hard brick generally results in an expensive paperweight.
Click to expand...
Click to collapse
Thanks for saying this.:good:
i have basic intelligence on software development and how to do simple stuff on android and on iphone... about a year ago i got this phone samsung galaxy s 4g and im thinking about finally rooting... but im affraid im going to brick my phone... anyone now the chances of that happening and if it does how to fix it? i know how to root i just need to know the chances of bricking your phone from root...
No chance. Look at guide in first link of my signature.
Follow the instructions and you'll be fine.
sent from me
There's about a 1% chance you will ever hard brick this device.....I've done a great deal of crazy things to mine and I've found it to be unbrickable.
There is a 99% chance you will atleast soft brick it atleast once in its life time,but soft bricking it just means you screwed up flashing a rom or something....but that is child's play and can be fixed easily.
Shortbus-Driver said:
There is a 99% chance you will atleast soft brick it atleast once in its life time,but soft bricking it just means you screwed up flashing a rom or something....but that is child's play and can be fixed easily.
Click to expand...
Click to collapse
Same, I've soft bricked at least 40 times.
Just don't flash roms or bootloader from another device and you should be fine. Using other phone roms and such will result in a hard brick (I had experience when I first started)
Sent from my Galaxy Nexus using xda app-developers app
Listen to everyone here. As long as you carefully follow directions you'll be fine! Rooting your phone is the easiest part I think, and probably has the least chance to brick your phone. It gets tricky when you get into flashing a custom recovery and moving to ICS and/or back to Gingerbread.
hi,
m kinda new to android phones.have been using iphone since 2007......very much expert with jailbreaking.....never bricked any iphone....coz u can always restore if anything goes wrong.
now i got a At&t one x and its on 4.0.4 with software version 2.20...i want to upgrade to jelly bean so i was looking through this forum....but i went through many post in which people have bricked their phones permanently....
now i want to root and install custom rom but m scared if i can brick my one x.....
can anyone tell possible reasons for bricking...and bricked phones can be unbricked???
sorry if this is repost but help will be appreciated....
thanks
Piyush
You can brick by flashing clockworkmod recovery or flashing a ROM from the other one x
Stay in this forum, do tons of research, and then do more research to know the difference from these two phones so you don't brick it
Sent from my One X using Tapatalk 2
The most common reason is flashing something meant for the international (Tegra3) One X. The hardware is completely different, and the memory partitioning is different. If you flash something meant for the international One X it may overwrite the hboot partition, meaning you are pretty much done.
There have been some people that have unbricked from this condition by fixing the partitions using a Linux coputer. But its not simple or a sure thing. There is a thread about it in General, if you are curious.
Otherwise, just stick to things in the AT&T One X specific forum. Read up, and follow instructions carefully, and you will not brick.
Technically, if it doesn't overwrite the hboot, you are done
Sent from my HTC One X-
I believe that with 2.20, it overwrites the extended partition table, not hboot, but that's almost as bad since it means the CPU can't find the OS.
iElvis said:
I believe that with 2.20, it overwrites the extended partition table, not hboot, but that's almost as bad since it means the CPU can't find the OS.
Click to expand...
Click to collapse
Ok, good to know. The moral of the story is that flashing a ROM, recovery, or other mods meant for the international version may overwrite something cirtical in memory due to the different partitioning, that causes you to be fooked.
Don't flash anything meant for the international version, and you don't need to worry about it.
Reason you've never bricked an iPhone is because you can't really change the way it boots or operates.. There's 1 type of firmware that's compatable with only iphones and nothing else. On android your changing the entire operation system that is not monitored or regulated.. If you install an operating system for a totally different phone, it'll render it useless.. Apple ensures you this will never happen with them lol. Therefore they lock it down
Sent from my One X using Tapatalk 2
InflatedTitan said:
Reason you've never bricked an iPhone is because you can't really change the way it boots or operates.
Click to expand...
Click to collapse
Well, not exactly. The jailbreak process is a change in how the phone boots, and it de-sandboxes the apps, which is an operational change. But it's not on the same level of a custom rom.
It is true you can't make major firmware changes with iTunes, but there are other methods of screwing around with the firmware, if you know what you're doing. It's just that this is beyond the abilities of anyone but jailbreak devs, so you don't hear about average users bricking their iPhones with redsn0w or Cydia.