Related
Hi everyone,
Just a word of advice: Rooting + Flashing ROMs for the Desire may og may not brick your devices. As you can see in this thread http://android.modaco.com/content-p...-usb-connectivity-etc-and-root-a2sd/page/540/ we are quite a few with bricked devices - and no way to un-brick them so far.
Nobody yet knows what might have caused this - maybe Apps 2 SD.
I would advice for everyone to wait flashing any further until this issue is clarified!!!
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Mastoid said:
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Click to expand...
Click to collapse
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
It could be any ROM.
Sent from my HTC Desire using Tapatalk
socktug said:
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
Click to expand...
Click to collapse
I take it you have a bricked phone then? I hope this gets resolved soon especially for those who might have turned their phone into nothing more than a paper weight.
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
Click to expand...
Click to collapse
Since many people have reported this issue, is there not some kind of pattern emerging? Hopefully we can isolate the problem to something in particular, as you stated, whether it be caused by the rooting process, Apps2SD, or a USB driver issue.
For those who are experiencing this, might be an idea to post computer specs, what ROM they attempted to install, and other associated things so we can narrow down the problem.
I've flashed loads so far and have no issues - finally got a ROM I like at the mo so will leave it for now...probably
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
It happens that I flash several time in a day, I have MCR r3 A2SD+ now and I never had such a problem...
The problem is APPS2SD related.
DocRambone said:
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
Click to expand...
Click to collapse
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Could this be most of the issue happened to be with people with .80 bootloader??
kuailan said:
Could this be most of the issue happened to be with people with .80 bootloader??
Click to expand...
Click to collapse
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
abc27 said:
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
Click to expand...
Click to collapse
There are people on modaco who have bricked their phones, and were not using A2SD.
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
socktug said:
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
Click to expand...
Click to collapse
I think DocRambone is onto something here... he stated a few posts back that he thinks it may be down to the sensitivity of the connection/cable while the phone is in recovery mode during flash, and you mentioned that you bricked your phone while knocking it while flashing in recovery?
From my experience, whenever I attempted to flash Desire cutoms ROMs, I did not move the USB cable at all and it worked fine. Had the phone placed on the desk and kept it stationary while flashing. I have not had any problems with Apps2SD or USB driver issues either.
I did mine from the laptop and the phone on the sette beside me. lol. I initially thought I'd knocked it and the battery came out, but I'm fairly sure now that the battery wasn't the problem, it fits too tight to come out with a simple knock of the hand.
Anyway, all I can say is if you brick it, and can unroot it, and bought it at the carphonewarehouse, you will be fine! They took it back and gave me a new one, no questions asked. I'm not going near a root process untill there is a fix now
Afaik there are two possible solutions for the issue
1. someone needs to security unlock the spl, so that we are able to use all fastboot commands
2. In the modaco thread someone found some helpfull kernel commands
so, if anyone either is experienced in spl modifications or capable of programming c for the kernel commands, pleade send me a pm
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
I have read the last few pages of the MoDaCo thread but still I am not clear about the issue.
Is it there are some unknown factors causing the root process to brick the USB? But still you can flash stock RUU in fastboot?
you can flash back to stock cause fastboot is still working and so you can flash the signed stock roms (thoose with release keys or the testrom with testkeys) but due to the fact that adb is nomore working you can't enter the custom recovery to flash cooked roms
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
Just send a message to one of the mods, he sure will make that post sticky
--edit---
man, theese guys are fast, now it's sticky
Easy and apparently safer method of rooting?
Not sure if anyone's seen this on modaco but using the tiny core linux has worked well for me, with 3 flashes from a stock HTC ROM and currently running eViL De-SiRe after trying paul's initial boot then the Cyanogen Port.
May flash again tonight with the Kernel release the ROMs will get better and better.
I have a Droid Incredible Rooted using Unrevoked forever with S-Off. I have been running CM 6.0.2 for a while now and had an issue the other day with my SD card. The card died and when I put a new card in the phone got stuck in a boot loop. I tried reflashing CM 6.0.2 and gapps but I continue to get the same boot loop. I understand that you need to wipe all data but when I atempt to wipe the Dalvik Cache I get the the following message "E:Can't mount /dev/block/ (File Found)" what do I need to do to fix this. I have no phone right now and have become extremely dependent on using it for everything from GPS to MP3 player in my daily life so any help would be greatly appreciated. I have read some posts suggesting running logcat to find what error I am getting during the bootloop that is happening, but I have no idea how to do that. I think the main issue is that I cannot do a full wipe before flashing the ROM.
Please help! I don't want to chalk this up to a bricked device, but I won't be able to hold out much longer since I have to travel this weekend.
First of all, do not double post. It just clutters up the forums.
Second, you need to post this in the Droid Incredible forum or at the VERY LEAST, the Android Q&A forum. I'm not sure why people took the time to create all of the different forums around here if you guys are not even going to use them.
I'm just taking a shot in the dark here based on my experience flashing older Android phones. So do not tell me I'm wrong, AGAIN this is just an option to try:
Just boot into recovery and do a factory reset on the phone. AGAIN, I'm just going on what I CAN REMEMBER here. Use the hboot menu try a restore. Load a factory ROM onto the SD card (using your PC) and the flash it.
I don't know man, maybe I'm wrong about all of this. FACT is that I've had NUMEROUS phones that were in the same shape you are in right now and after google searching, a little common sense and READING I was able to fix the issues. There is a way to go back to your FACTORY ROM but I'm not going to waste my time doing the research for you here, it's your phone and you have access to the same information all of us do.
EDIT:
I mentioned common sense. With that being said, take a look at your own post bro.
talltubatom said:
I understand that you need to wipe all data but when I atempt to wipe the Dalvik Cache I get the the following message "E:Can't mount /dev/block/ (File Found)"
Click to expand...
Click to collapse
I assume you meant "(File NOT Found)". You are trying wipe data off of a NEW SD Card here. How do you expect it to wipe files that are not even there to start with? Make sure your battery is fully charged before doing anything with the phone also. You might think that sounds like it has nothing to do with your problem BUT it can cause boot loops on SOME devices (android and others). Reset to factory from hboot menu. SKIP THE WIPE ALL PART BECAUSE YOU HAVE A NEW SD CARD. Just get back into your phone running Android and then you can redo everything from there.
Thank you for the response.
Sorry for posting in the wrong thread, perhaps a mod could move this to a more resonable place for this question. I'm not trying to clog anythining up. If that isn't an option I'll just create a new thread over there, but like you said that would just be clutter.
First: I did not mean (File NOT Found) the error says (File Found), seems like an odd error on a Formated SD Card that is why I mentioned it.
Second: I tried going to a stock ROM and it would not flash to the device I think it was looking for the previous official ROM that was relesed for the phone and would not install since that did not exist. The one that I downloaded was when Verizon pushed FroYo for the DInc, perhaps I can find one that supports a different upgrade path.
After trying all logical steps, google searches and reading many thread regarding people who have been stuck in this situation I was not able to find anything that was helping me restore my phone, that is why i started a new thread.
Roll Tide <<<< so you won't be so upset with me
The only reason I said posting in the device specific forum or android forums would be better is because there would be more people that know how to fix it viewing your question.
I'm shooting in the dark here but have you tried flashing Clockwork again? Just putting the .zip on the new SDCARD and flashing it? I'm sorry man, I've searched and tried to come up with a good answer but I've not found THAT much. Post in the Incredible forum would probably get your problem solved. I'm not sure that there is much of a difference between deviceds when it comes to recovery but I'm sure that you will get more accurate answer over there, even in the Android section.
As the title says, do not partition SD card using ClockworkMod or ROM Manager.
There has been multiple bricked devices already, all after partitioning SD in CWM. The device suddenly turns off while the partitioning is in progress, and never turns on again. We do not know what causes this issue yet, but I am sure that ClockworkMod team will look into it.
Update:
Koush said:
Looking into this. I don't have a DHD but I have an idea why this is happening.
Click to expand...
Click to collapse
Update 2:
Koush said:
I have a fix ready now. I will need to release a new recovery and new ROM Manager to address this.
Click to expand...
Click to collapse
Update 3:
New ClockworkMod 3.0.2.6 and ROM Manager 4.1.0.0 are out! There has been multiple confirmations of the problem being fixed, but also ONE brick. So take the fix with a grain of salt.
Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!
have another brick here from the same reason, be aware.
MafiotuL said:
Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!
Click to expand...
Click to collapse
Easy, partition the wrong partition, iow the NAND/eMMC.
does anybody know if it affects other devices also?
MafiotuL said:
Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!
Click to expand...
Click to collapse
HOLY SHT!!!!!!!
I partitioned my sdcard thru Clockword recovery 3 months ago back then with 2.5.0.7 htc desire
it hung for 1 hour so i pulled the battery but it was paritioned rite phewwwwww..
Cant imagine if i had a bricked phone now,would prolly pee on my pants....
Darn it. I was thinking about partitioning my SDCard today but postponed it. Thanks for the information.
Are there any other known issues that the CWM might cause to the device? Last year, when I had HTC Dream, I remember reading in forums at Cyanogen that some people didn't recommend using ROM Manager. I don't know what issues it used to cause because I used Amon_Ra back then.
Anyways, thanks for the information. I won't partition the SDCard using CWM.
Ok............
This thread has been stickied by me in order to inform everybody about this situation.
Do report if you have gone through this problem only...no more thanks or OT chatter, please.
I'm in contact with the Mod team to investigate even further if this does affect any other devices as well.
Please be patient and do not pollute this thread
Cheers,
M_T_M
@jkoljo...thanks for your help on this very important matter.
Got another one here: http://www.android-hilfe.de/root-ha...t-nicht-mehr-nach-partitionierung-der-sd.html [German], thank goodness it wasn't mine
Bricked DHD
Hi There,
Had this a few days ago.
the device is indeed completely bricked, no matter what you do.
Luckily for me my HTC DHD was only 10 days old, so i went to the store and after inspection theyt gave me a new one. I must be very lucky i guess.
Thanks for the warning nevertheless.
hello. I have the same problem. it goes in the black this afternoon before I have read the forum. Is there any thing i can do to get the phone alive again. : ((
All versions of CWM ? Or is it specific to a version ?
All the best,
Sharro
We do not exactly know at this point. At least 3.0.2.5 has the problem.
There is nothing you can do to fix a brick. That is why it is called a brick.
kilavuz said:
hello. I have the same problem. it goes in the black this afternoon before I have read the forum. Is there any thing i can do to get the phone alive again. : ((
Click to expand...
Click to collapse
I believe you can still return it for manufacturer warranty. HTC phones has at least one year manufacturer. Just say to them you turn on your phone and it couldn't turn on....simplesssss
it is only 2 weeks old. : ((
Other solution
Hi guys,
I've also read somewhere, last november I think, that partitioning could be problematic. So I looked up on the internet and can recommand you what I use to partition my SDHC cards: Paragon partition manager 11 free , I used it on Win XP 32 bits without any problem with my 16gb and with my 3 other 8gb SDHC.
link: here
f.
M_T_M said:
This thread has been stickied by me in order to inform everybody about this situation.
Do report if you have gone through this problem only...no more thanks or OT chatter, please.
I'm in contact with the Mod team to investigate even further if this does affect any other devices as well.
Please be patient and do not pollute this thread
Cheers,
M_T_M
@jkoljo...thanks for your help on this very important matter.
Click to expand...
Click to collapse
Thanks
Thanks for the warning, yesterday I had considered to partition my SD ..
best would be to partition SD's via PC and to disable the partitioningfunction for the next update. I'd be bad if someone uses it again.
2-die-4 said:
best would be to partition SD's via PC and to disable the partitioningfunction for the next update. I'd be bad if someone uses it again.
Click to expand...
Click to collapse
Yep. I contacted Koush about this issue, so hopefully we get a fix (someone dare to try..? ) or it gets disabled.
I heard this from a customer so take this with a grain of salt but he told me he was an Android Developer and had heard of an interesting "trick" concerning all HTC Android phones.
These phones apparently have a SECONDARY bootloader that is completely hidden and disabled by default and that all those phones are HARDCODED to immediately enter into it the moment they get connected to a specific USB cable.
The guy was looking for the cheapest possible, well, item really, to buy and then proceed to cannibalize as a test to its' validity (he bought an old Motorola handsfree) so it seems he wasn't sure of it either.
Apparently what needs to be done is that the PLUG needs to be completely stripped and either two resistors or two capacitors (I forget which) of specific values need to be soldered to two specific lungs of the plug.
I am sorry I am being this vague but that was all the information I got from him in the matter of the couple of minutes it took him to buy the handsfree.
Perhaps there's sth to be looked into by some people better equipped than I?
EDIT: On second thought, it makes more sense if what he said was to solder A resistor/capacitor to TWO specific lugs of the plug, perhaps?
I kinda remember him saying that the plug itself doesn't even really need to lead to anywhere but it's more like the means to connecting the resistor/capacitor to those two lugs...
He also said that that's how HTC themselves un-brick bricked phones. He didn't appear to be talking just for Dev phones either.
I am sorry I really do not know any details.
Hi sorry, I couldn't find where to put this but I just rooted my ASUS transformer on 3.2 - 8.6.5.19 sucessfully and now need to or want to know what to do?
1-Ive heard of overclocking but I would want to do it safely
2-Id like to make a backup before I do anything that may mess things up
3-Ive got Rom manager on it but it asks to make sure that I have clockmodwork Recovery and I can't find where to get it.
and finally
4-What can I really do with this thing now?
Please let me know thanks
Well, browsing and searching through the forums should give you enough answers... If you had any other Android device, it is all the same here.
Anyway, if you've installed ClockWorkMod Recovery (the Rom manager can usually do this, but I am not sure as I haven't tried it for this device), you can try it by switching the device off and powering up with keeping power and volume down buttons pressed. After a while you'll get a message like "press vol-up to boot recovery in 5 seconds". If you press vol-up, you'll get into the recovery.
If you did not install CWM, you can also use this tool: http://forum.xda-developers.com/showthread.php?t=1346180
That's what I used.
As for backup - you can do nandroid backup of your current rom from the CWM recovery (in case something goes wrong, you can easily revert to the current rom). You'll have to use one of the backup apps if you want to backup data and apps from your current rom though.
If you want to install a new rom, put it into the root of your sd card (real one, not internal storage), then do a full wipe (clear data/factory reset in CWM), then select "install zip from sd card" (don't remember the exact message), confirm, wait for it to finish, select reboot and you're done.
As for overclocking, I don't know yet, I've had this device just for a few days. Check out the available ROMs, they probably have some overclocking tools/features.
I just love this device - rooting and installing CWM without even having to connect to a PC
1- search the forum
2- search the forum
3- search the forum
4-throw it into the sea
1. Search & Read
If you ask such questions, you clearly do not have an idea what are you doing. Gain some knowledge before you harm your device
However Sigismund83's post should cover it up
ROM Manager does not work with the TF101.
Everyone always says "search" but it not always as easy as it seems when your a noob .. Although there are guides for alot of things, it isnt as noob friendly as it could be.
Some guides are out of date and throw you off in the wrong direction, and it can end up taking you a fair bit of time searching and reading old topics till you finally come across / figure out the correct process...
Heres what i would suggest (as i just did this myself)
1. Root with Razorclaw (youve already done)
2. Install the easy recovery installer Tool for flashing CWM in one click
3. Download a Rom of your choice ... Prime, Revolver, Revolution etc etc and transfer it to your microSD card
4. Boot into recovery (cwm) and flash the rom (flash update from SDcard) (this is another good quick tool Reboot to recovery App
Bobs your auntie ...
Thank you!
Danny-B- said:
Everyone always says "search" but it not always as easy as it seems when your a noob .. Although there are guides for alot of things, it isnt as noob friendly as it could be.
Some guides are out of date and throw you off in the wrong direction, and it can end up taking you a fair bit of time searching and reading old topics till you finally come across / figure out the correct process...
Click to expand...
Click to collapse
Boy ain't THAT the truth! Searching these forums is agonizing for exactly those reasons. It would be nice if there were more people that would just answer if they know or if they don't want to help just move on. "Read and search the forums" is less than helpful.
gbweller said:
Boy ain't THAT the truth! Searching these forums is agonizing for exactly those reasons. It would be nice if there were more people that would just answer if they know or if they don't want to help just move on. "Read and search the forums" is less than helpful.
Click to expand...
Click to collapse
I think the point everyone is saying is, he rooted his tablet and then asks, "What do I do with it," which indicates he didn't really have a reason to root it in the first place other than for the fact that he could.
He should have researched rooting, what benefits it brings, pros & cons, etc, before just rooting for the hell of it.
I'm wondering why would someone root a device and not know what to do with it. It's like getting a tattoo and then ask now what?
Danny-B- said:
Everyone always says "search" but it not always as easy as it seems when your a noob .. Although there are guides for alot of things, it isnt as noob friendly as it could be.
Click to expand...
Click to collapse
There is nothing more noob-friendly than searching IMO. Where things get hairy for noobs is when they decide to take the easy route and ask questions that have already been asked, probably 5-10 times at least before someone really starts trolling those questions..
Searching is only difficult if you have a sub-grammar-school reading level..you have to be willing to use your eyes and actually read some, even things you may not need to know, to find what you are actually looking for...you may find that learning stuff that you didn't need actually turns out to save your ass later (as has happened to me many many times).
That is why we say over and over to search, because learning to find your own answers, a crucial skill in problem solving, is much better than simply answering a single question that has been asked over and over, you aren't teaching you are doing their work for them..you know, teach a man to fish and all that jazz. Honestly, the only time searching for your answers is difficult for noobs is when their device is brand new and not undergone a lot of development. But in the case of our TF101, there are entire websites devoted to it. It has been out for nearly a year now.
No offense to any noobs who didn't want to hear it!
I rooted mine to fix the speaker balance. No reason to root other than that, and I'll probably un-do it so I can use Movie rentals from the Market.
Basic rundown, I bought an HTC One M8 on tmoblie yesterday, coming off an iphone 4. I've heard you have have have to root your android devices, so that was one of the very first things I did. Shortly after, I was trying to figure out exactly what I could do with the root, and decided to flash a custom ROM. I tried the Google Play edition posted on the dev section of this same forum. Everything worked as planned, except for one huge problem: my data no longer works. I can connect to wifi fine, as well as send texts, but no 4g lte access anymore. Idk if this is a common problem, if I'm doing something simple wrong, etc. I made a backup in TWRP, and saved it to my desktop, and tried restoring my phone to see if that would help, but I must have dne something wrong there too, as it doesn't show any files when I try to restore under TWRP.
I would greatly appreciate any and all help or tips. I'm new to the android rooting scene and should have taken it more slowly. I thought I had done sufficient research, but I guess I ****ed the pooch somewhere along the way. Thanks in advance.
watchmuu said:
Basic rundown, I bought an HTC One M8 on tmoblie yesterday, coming off an iphone 4. I've heard you have have have to root your android devices, so that was one of the very first things I did. Shortly after, I was trying to figure out exactly what I could do with the root, and decided to flash a custom ROM. I tried the Google Play edition posted on the dev section of this same forum. Everything worked as planned, except for one huge problem: my data no longer works. I can connect to wifi fine, as well as send texts, but no 4g lte access anymore. Idk if this is a common problem, if I'm doing something simple wrong, etc. I made a backup in TWRP, and saved it to my desktop, and tried restoring my phone to see if that would help, but I must have dne something wrong there too, as it doesn't show any files when I try to restore under TWRP.
I would greatly appreciate any and all help or tips. I'm new to the android rooting scene and should have taken it more slowly. I thought I had done sufficient research, but I guess I ****ed the pooch somewhere along the way. Thanks in advance.
Click to expand...
Click to collapse
Try the Tmobile M8 forum