I'm trying to learn how to cook ROMs and I plan on using the Desire S leaked ROM as my first test subject. I know its been ported to the DHD but I'm a little worried with tampering and testing my ROM on my phone. I've tried flashing it once with recovery but it wouldn't boot. I used port settings also. Just for informational sake, if I were to flash the Desire S 2.3 leaked Rom into my device without any tweaking would it brick my phone? I was able to boot into recovery when my first test failed but if I flashed the test ROM without any tweaking and it fails will I still be able to use recovery to flash back to my nandroid backup or would I not be able to boot into recovery at all?
You can brick your DHD only if you DO NOT know what you are doing. Or, only if you mess up Except that no pain.
Like sphuyal said you can brick your device yea, lots of things can brick your device if your unlucky enough, flashing another rom which isn't made for your device will probably cause the phone not to boot but probably won't brick it, chances are you'll end up in a boot loop, but why would you do that when ppl r developing rom's all over the place to cater for everyone.
Just make sure what you do is tried and tested, otherwise yes you do risk bricking your device and then you'll feel like a plebb.
The only confirmed bricking on XDA, has been due to a hardware failure, so the chances of bricking it are minimal but the chances of ending up with an unbootable device are huge. In most cases ROM's for other devices will not flash without some modifications if you don't know what your doing stay away from making such mods.
Related
Hello, i have purchased my Htc desire Hd a few days ago and i love it. I came across these forums and found them very helpful. I decided to _root my phone and install the latest Cm ROM and all went well. When i bought the phone the supplier (three) said that i would be able to get speeds up to to 6mb on the mobile broadband in my area. Sadly this is not the case as i am on EDGE.
I was wondering is there anyway to boost signal either by app or a different radio or ROM.
Thanks in advance.
Well, it could be from some setting maybe, but if i was in your shoes i'd ask the people in the Original Thread.
When upgrading from an fairly old ROM to a new ROM, i'd suggest the flashing of a new radio.
BE CAREFUL, AS FLASHING RADIOS ARE EXTREMELY DANGEROUS.
See the OP of the ROM thread and see if flashing a radio is mentioned (if its not mentioned on the thread, dont flash a new radio, or you can ask them if you can). Normally, ROM are supplied with a RECOMMENDED radio that works perfectly with it.
So ask the people in that thread (or see the OP) if and which radio you should flash.
FLASHING RADIOS COULD BRICK YOUR PHONE, AND ONLY YOU ARE RESPONSIBLE FOR BRICKING IT
- just a little warning with a happy face
Thanks alot for your time I didnt know flashing radios was as dangerous :/ i've done it twice. well thanks for the warning with the happy face
Is there any fail safes for flashing ? anything like roms or radios ?
Thanks in advance
By 'Fail Safes' do you mean 'a mechanism that manages failures and results in minimum harm'? (just googled it )
If so, well, android itself has MANY mechanisms. And by flashing ROMs, all it does is overwrite the current files. So flashing something (given that the script to flash it is correct - if not, then it wont flash - or could flash it to the wrong place) doesnt have any fail safes, which is why, if an incorrect radio is flashed, the phone wont do anything, but when you come to boot it, it could be bricked (worst possible case).
Flashing ROMs with errors can be fixed easily if you know how. Just build a flashable .zip file that'll overwrite the files that have errors with correct files.... - determining the error could be done by using 'adb logcat'
Thanks ! you couldn't have done more Thanks again for everything i will be more cautious when flashing Another big thanks !
Luke
Your Welcome , anytime
OK....So im not new to XDA or android really....have been in the HTC Hero forum for a little bit, but my new phone will be here tomorrow....
So far things seem just a lil bit different on this side, please correct me if im wrong....
Kernels-cooked into the ROM cant be flashed over with a different kernel?
Root looks pretty easy to achieve, but also easy to loose/unroot?
CWM doesnt play well with this phone, and must be cooked into a ROM instead of being flashed freely?
Modem/Radio...is there a new or old better or worse...are these all just cooked up and are trial an error? It seems that there should be some kind of consensus as to which ones are good,bad,or indifferent...or which ones work better in a different markets?
And the xx14 or pgxx....different codes for ROMs, what is all of that about, a little insight into that would be GREAT!!
Again, I have been reading over the forums for a week or so now and I am just trying to wrap my head around how this new process is going to work...The Hero is a legacy device and everything seems second nature for me. Alot of people in that forum moved on the the Evo3D, but I was ready for a something new and different, so here I am! I just dont want to screw something up on this device.
Thanks in advance for any positive input.
Edit: OOPS....Guess this should have gone in the Q/A...sorry.
For the code names like FC14... is basically identification of the build date of the ROM.
F = year (2012)
C = month (March)
14 = day
Gotcha, thanks!
Recovery is packed with the kernel. You can use any kernel you want as long as you are using gingerbread kernels with gb roms and ics kernels with ics roms. You can flash them with odin or cwm.
There are currently issues with ICS kernels so it is not recommended to use recovery on any ics kernels.
Modems are basically trial and error with regards to which is best for your phone. You are free to use any modem on any build.
The absolute safest route is ODIN for sure. There is a lot of speculation on what exactly is causing bricks. It seems the worst of it is connected with ICS and Clockword Mod Touch Recovery being used together.
Odin is a very nice tool that you can use from your computer to flash rom files, kernels, and modems. There is also Mobile Odin available from the play market for a few dollars. It's a worthwhile investment because you can flash tar files without a computer. But it is a known issue that the modem won't flash, which isn't a huge deal. Just do it from your computer when you get a chance.
Root isn't necessarily easy to lose. The only way to lose it is to personally remove root using a tool, like autoroot, or to do an OTA update from a stock rooted ROM, that would also remove root. Other than that once you're rooted you are good to go.
Be sure to do AS MUCH READING AS POSSIBLE. People are BRICKING their phones. They are breaking them beyond personal repair, and Spring Tech repair, thus needed warranty replacements. READ READ READ READ READ READ. I can't say it enough, nobody can say it enough. Even the developers have bricked their phones.
Yeah, I am reading...lol
Thats what made me post this because some of it doesnt make sense compared to what I am used to...
I am pretty sure im gonna root and stay stock for at least.....a day! Just to get a feel for it, and be able to tell a difference between stock and Mod... But I must confess I am a flash-whore and have been dying for some ICS goodness!!
I came from the EVO 4G; here are some things I've picked up.
1) The recovery and kernel is combined with samsung phones (same partition). So you can't just flash 1 or the other, you install both.
2) Touch CMW on E4GT is unproven. Some fared ok, some say otherwise. To be safe, I'd avoid it for now. Regular CMW and Rogue recovery are pretty much the gold standard here.
3) Any recovery installed by Rom Manager is temporary (again kernel/recovery are combined). Meaning it won't stick past a normal reboot.
4) Until ICS source is released, any actions done specifically in the ICS kernel-based recovery could potentially brick your phone. This is especially true for any ICS aosp roms (CM9, miui v4, aokp, etc). So this means once you flash from gb to ICS, your recovery is suspect. I will say that I don't see many reports of people bricking with these TW ics leaks, as many just seem to use calk's format all script and flash away. To be 100% safe, its best to odin back to a gb kernel-recovery to anything within the recovery.
5) Learn to use Odin; its important to know if you are going to play with ICS right now.
Good luck!
modems, just like radios, are going to be different for each user.
personally i just use the latest modem since sprint sucks no matter which one i use.
root is achieved simply by using odin to flash a rooted rom.
unroot by simply using odin to flash a stock rom.
very easy!
Hi guys.
I flash the fullscreen mode with cmw recovery, and when the system was reebot it stop to a boot screen (white with HTC One written).
I tried to lock bootloader and installing RUU, but it say me who phone is not plug on the pc.
I tried to wipe cache/dalvik/etc etc but I'm not able to restart my phone.
Anyone can help me?
I just try to "fastboot erase cache" and "fastboot reboot-bootloader"...but nothing.
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Which rom you was using? The stock or a custom one?
relocking bootloader and try flashing a RUU was completly overkill.
You just need the original android.policy, which was overwritten by flashing the mod you tried to get running.
I'm sure someone can provide a flashable zip for that...just ask in teh thread of the mod.
If you got your rom runnning again, esnure to make a backup in recovery. On that way you can always restore your working rom.
...and btw: brick = cant turn device on
j4n87 said:
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Click to expand...
Click to collapse
I learn it yesterday evening, I don't forget to do it next time.
Now I'm trying to flash the RUU, before I didn't enter in fastboot.
Installing complete.........
anxiety....
...it work.
Yeah I had the same issue after installing the full screen patch too. Thankfully I'd done a Nandroid backup just after I rooted so I just did that. Would have installed a custom Rom otherwise
Sent from my Desire HD running Virtuous Affinity Sense 3.5
j4n87 said:
..you need to learn to make a backup in recovery first, when you dont have that much experience yet.
Which rom you was using? The stock or a custom one?
relocking bootloader and try flashing a RUU was completly overkill.
You just need the original android.policy, which was overwritten by flashing the mod you tried to get running.
I'm sure someone can provide a flashable zip for that...just ask in teh thread of the mod.
If you got your rom runnning again, esnure to make a backup in recovery. On that way you can always restore your working rom.
...and btw: brick = cant turn device on
Click to expand...
Click to collapse
Hi, I'm completely new to Android and just upgraded myself from my 3GS to the One X (and what an upgrade at that!). However I'm a bit dissatisfied with the Sense interface and would like to flash it with either vanilla or some cool unofficial rom.
The problem is I'm scared to death of bricking it. Especially since a friend of mine had told me the usual method of being sure you won't get a bricked phone is to simple change the rom on your SD-card. It would seem things get a little trickier when you don't have an SD though.
How does this backup in recovery work? Will it be making a backup of everything on my phone now and place it in backup? Will this ensure a corrupt rom image or whatever won't brick my phone?
From what I understand a launch from recovery is completely separate from the rest of the system, so unless you've broken the memory card (in which case I guess your screwed anyway) it shouldn't be possible to brick the phone should it?
kaminix said:
Hi, I'm completely new to Android and just upgraded myself from my 3GS to the One X (and what an upgrade at that!). However I'm a bit dissatisfied with the Sense interface and would like to flash it with either vanilla or some cool unofficial rom.
The problem is I'm scared to death of bricking it. Especially since a friend of mine had told me the usual method of being sure you won't get a bricked phone is to simple change the rom on your SD-card. It would seem things get a little trickier when you don't have an SD though.
How does this backup in recovery work? Will it be making a backup of everything on my phone now and place it in backup? Will this ensure a corrupt rom image or whatever won't brick my phone?
From what I understand a launch from recovery is completely separate from the rest of the system, so unless you've broken the memory card (in which case I guess your screwed anyway) it shouldn't be possible to brick the phone should it?
Click to expand...
Click to collapse
what you are looking to flash would be called "aosp"...android open source project, this means pure, unadulterated android from Google. At present time there are no aosp roms for the hox. They all have the HTC sense interface. Be patient. I'm sure this device will get a lot of attention from the dev community and we will have plenty of aosp roms to choose from in the near future.
Sent from my Xoom using xda premium
nooomoto said:
what you are looking to flash would be called "aosp"...android open source project, this means pure, unadulterated android from Google. At present time there are no aosp roms for the hox. They all have the HTC sense interface. Be patient. I'm sure this device will get a lot of attention from the dev community and we will have plenty of aosp roms to choose from in the near future.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Ah, yes. This is indeed what I'm looking for. Thanks, guess I'll just wait a little longer then.
my too sgs2 hard bricked becuase one for wrong bootloader and other for synah rc 3.6 kernal, so i bought one x and now lets see......will this work or not?
You have to make sure your RUU is for the same network and country and is newer then your current RUU or the CID will block it
Hello, i am not new android user but i dont know what can i do if i brick phone when flashing custom rom to HTC ONE V ... one v cost something about 300€...... how many % is to brick? /sry for english/
there's actually no brick possibilities as long as you flash correctly.
I never had brick problems so far, been flashing more than 20ROM to 4 Androids Devices
CMIIW
Softbricks are easy for rooted n00bs that mess with their ROMs when they don't know what they're doing. But HTC phones are easy to unbrick so it's usually not a disaster.
If you install ClockworkMod Recovery immediately after rooting and immediately do backup, you won't have to worry about bricking the device.
me too..
HELP me
[Q] Hard Brick i'v Got QHSUSB_DLOAD and Blank Screen
http://forum.xda-developers.com/showthread.php?t=1651149
Alright folks, this is directed more at the those that have spent a lot of time modding and flashing their GS3's. I recently got myself a GS3, and I gotta be honest, I haven't gotten the itch to customize it more than root yet because it is just that good already.
I modded the hell out of my Vibrant, constantly flashing Roms, modems, kernels, etc. Ran into a few "bumps" along the road where I thought the phone was done for, but I was always able to bring it back. For instance, a few months before I got the GS3 I was flashing a ROM and although I can't remember the details, something screwed up and I was getting the dreaded Phone to PC symbol. I have had this in the past and had a JIG that would always get me into download mode. This time however, it wouldn't work. I couldn't get ADB to send it into download, nor through the hardware keys, nor with the JIG. I thought for sure I was done for.
I decided to plug it into my computer anyway with ODIN up, and even though it wasn't in download mode, ODIN showed a "yellow COM". I said what is there to lose and so I loaded stock and hit start, lo and behold a few minutes later the ol' Vibrant was booting back up to the familiar sound of the T-Mobile jingle. I thoroughly believe that phone is unbrickable.
Now I know I'm going to get the itch sooner or later, especially as more and more ROM development ensues, but how brickable is the GS3? Anyone know if it's as "tough" as the Vibrant was in that respect, or is it quite a bit easier to brick? What is your experience with it so far?
If you flash am i9300 ROM, you will brick. That's about it.
Sent from my SGH-T999
If you know how to read warnings and have a fully functional brain you won't brick.
Posted from what apple calls "basically an iPhone" SGS3
GS3 should be less likely to brick
I flashed an HTC Rom with the vibrant and was still able to get it back to functionality.. not completely for sure about the GS3. I know of someone that hardbricked their GS3, and they are actually getting close to fixing it, but not fully yet.. just read and flash what ur suppose to.
Sent from my SGH-T999 using xda app-developers app
I use to have a vibrant too. Then I switch to this. I am a flashaholic so far everything good . Havent have anu problem that odin cant fix.
Sent from my SGH-T999 using xda app-developers app
If you do eventually decide to fiddle around with your phone, here's some advice:
1. BACKUP YOUR IMEI. No one's 100% sure what causes it (though there are several theories regarding recoveries and wipe scripts). You can inject your IMEI if you don't have a backup but the process takes maybe 10 minutes and I feel like it would save alot of headaches. There are currently two methods. I recommend you do both and keep a copy of the backup files somewhere safe:
Method 1: http://forum.xda-developers.com/showthread.php?t=1808408
Method 2: http://forum.xda-developers.com/showthread.php?t=1804123 (includes instructions on injecting an IMEI.
2. Try to stick to the thread for your particular GS3. I've heard that ATT Roms and kernels are compatible with the TMO version and vice versa. I take a little more comfort knowing a particular ROM or kernel was developed for my specific GS3 variant. Feel free to experiment with ROMS and kernels from other variants but be sure you know what they contain (be especially attentive to different modems/radios, see #3).
3. IMO the biggest source for bricking involves modems/radios. I haven't flashed any because I'm on wind and most of the new modems released have been for TMO. Flashing the wrong radio can brick your phone. Most ROMS don't flash a modem but it never hurts to ask. Be especially attentive to files that require ODIN as I believe some of these files may include modems and recoveries.
4. Since your posting on TMO forum, I'm going to assume yo have a TMO/Wind/Mobilicity variant of the phone. If your looking to root, I recommend using the method in this thread: http://forum.xda-developers.com/showthread.php?t=1771687. Simply download the image for your cell phone company and follow the instructions in OP. It's basically just flash with ODIN. Then install a recovery. You can install CWM using the method in the post. Or you can install TWRP by downloading the goo.im app and installing it with that application..
5. HAVE FUN
I used to have a vibrant as well and had a few close calls. I was always able to finally get it back. The S3 appears to be just as hearty (as long as you don't flash a i9300 rom).
Flash away.
nicky9door said:
If you do eventually decide to fiddle around with your phone, here's some advice:
1. BACKUP YOUR IMEI. No one's 100% sure what causes it (though there are several theories regarding recoveries and wipe scripts). You can inject your IMEI if you don't have a backup but the process takes maybe 10 minutes and I feel like it would save alot of headaches. There are currently two methods. I recommend you do both and keep a copy of the backup files somewhere safe:
Method 1: http://forum.xda-developers.com/showthread.php?t=1808408
Method 2: http://forum.xda-developers.com/showthread.php?t=1804123 (includes instructions on injecting an IMEI.
2. Try to stick to the thread for your particular GS3. I've heard that ATT Roms and kernels are compatible with the TMO version and vice versa. I take a little more comfort knowing a particular ROM or kernel was developed for my specific GS3 variant. Feel free to experiment with ROMS and kernels from other variants but be sure you know what they contain (be especially attentive to different modems/radios, see #3).
3. IMO the biggest source for bricking involves modems/radios. I haven't flashed any because I'm on wind and most of the new modems released have been for TMO. Flashing the wrong radio can brick your phone. Most ROMS don't flash a modem but it never hurts to ask. Be especially attentive to files that require ODIN as I believe some of these files may include modems and recoveries.
4. Since your posting on TMO forum, I'm going to assume yo have a TMO/Wind/Mobilicity variant of the phone. If your looking to root, I recommend using the method in this thread: http://forum.xda-developers.com/showthread.php?t=1771687. Simply download the image for your cell phone company and follow the instructions in OP. It's basically just flash with ODIN. Then install a recovery. You can install CWM using the method in the post. Or you can install TWRP by downloading the goo.im app and installing it with that application..
5. HAVE FUN
Click to expand...
Click to collapse
I did use that method for rooting already, but I didn't realize the issue with the IMEI so that's good to know for when I get the urge to start flashing again. :laugh: